Community Research and Development Information Service - CORDIS

H2020

reTHINK Report Summary

Project ID: 645342
Funded under: H2020-EU.2.1.1.3.

Periodic Reporting for period 1 - reTHINK (Trustful hyper-linked entities in dynamic networks)

Reporting period: 2015-01-01 to 2016-06-30

Summary of the context and overall objectives of the project

-- Context and motivation
The Internet revolution has changed traditional business and forced it to reinvent itself. Operator services are losing their appeal due to the emergence of new communication services, like chat and social networks, which replace, not just complement traditional voice telephony. The service environment has moved on to the web, with operators providing only access and transport. The requirements of web applications to launch interactive communication are gaining momentum, fuelled by technologies that enable browsers to convey interactive sessions.
Operators need an evolution path to match the requirements depicted by Industry 4.0 and Smart City. Currently they provide a limited set of services that are tightly associated with their own network's capabilities, within their geographical reach, or through roaming agreements. These services are regulated, in contrast to Internet applications, which are global and unlicensed. To compete, operators need to gain the agility of the Internet world, and adopt Internet style tools and technologies, while exploiting their assets: trust, network management, real-time systems, and quality-of-service management.
The major structural difference between the operators approach and the web is related to a recurring concept in the deployment of ICT solutions: full de-perimeterisation of services. However, technology progress (4G, 5G) has decoupled access-control from the service, opening the door for web-based voice/video services, via any access type and on any device. This enables operators to enter the market of web-based communications. They can take the role of a ‘Communication Service Providers’ for web calling services. They can also be ‘Network Service Providers’, for delivering the media as a wholesale activity, offerring enhanced web routing with assured quality. Finally they can act as trusted identity providers, offering services that foster intra-domain mobility.

-- Challenge
The project will design and prototype a non-telecom centric, but Web-centric, P2P service architecture, enabling dynamic and interoperable trusted relationships among distributed services called “Hyperties” (Hyperlinked Entities). Hyperties support use-cases such as contextual and social communications, M2M/IoT, and content oriented services.
Today, browser based technologies enable real-time interaction, and improved media streaming over the Internet, but there are no standards for managing the signalling that establishes sessions between calling parties. The challenge is to provide tools that enable discovery and authentication of the communication parties, allowing for diverse scenarios and services, retaining global compatibility, without creating new closed communication audiences (‘silo’) or proprietary systems.

-- Solution
The framework is based on specialized P2P and Cloud services, delivered as SaaS, PaaS or IaaS. It supports communication services that rely on a mesh of ‘live’ Hyperties at the endpoints that create a ‘virtual’ network within the Internet, while the media is routed through gateways that support policy enforcement for quality and security over the Internet.
The project delivers an architecture that allows operators and service providers to offer de-perimetrised services and compete with web companies. The architecture provides extensible APIs for service developers based on secure, certified and portable independent identities.
The solution will be demonstrated through an open source prototype that supports its mid-term commercial deployment, and its suitability for the relevant use-cases.
In order to achieve this vision the project has identified the following scientific and technical objectives:
• Provide a communication framework for the future service environment that facilitates P2P communications
• Design and develop security and portability features, relying on trusted 3rd Pty user-selected identity providers
• Investigate the economic, social and business impacts of the concepts on today’s services ecosystems
• Validate the concept effectiveness by implementing use cases that represent the most important application areas
• Propose standards and increase European competence in the web-driven real-time services domain.

Work performed from the beginning of the project to the end of the period covered by the report and main results achieved so far

In this period (M01-M18) the work focused on the definition of the hyper linked entity (Hyperty) concept as well as the first phase implementation of the framework including the identity management solution.

The objectives of the reTHINK project are target and result driven. reTHINK will develop a web-centric communication framework and associated functionalities for Hyperties. To achieve its mission, reTHINK will meet the following objectives:

• Objective 1: To provide a communication framework that facilitates and supports peer to peer communications. The reTHINK framework will support application provisioning and enablement in line with the perspective of various users/stakeholders. It will consist of four layers: a Hyperty Layer, a Messaging Layer, a Transport Layer and a Trust Management Layer transversal to the first three layers. Fabrics in each layer offer scalable mechanisms for the registration, look-up and discovery of Hyperties as well as communication between them.

The main components towards this objective have been achieved mainly by the delivery of D2.1, D2.2, D3.1, and D4.1 which are major milestones for the framework and architecture. A revision of the architecture is planned for M21 in the corresponding deliverable report D2.3.
D2.1 describes the overall architecture for the reTHINK project. The document contains an architecture framework, extensive study of the state of the art and case studies. The architecture describes a new paradigm, where connectivity control is executed by downloaded software (‘hyperties’) to the endpoints, and compatibility is achieved by downloading matching software to both parties (‘ProtoFly’). This allows a single service provider to initiate communication set up directly with the destination user, and to deliver the service media over the Internet, in a peer-to-peer fashion. Quality of service and security are optionally enhanced by hosted services, using collaborating networks of special web media gateways. This architecture also utilizes independent identity providers to provide end-users greater choice and service mobility, with flexible social-network style association, for both Human-to-Human and Machine-to-Machine users.
D2.2 document describes in detail the data models to be used to describe Hyperties and the interfaces for the reTHINK architecture defined in deliverable D2.1 “Architecture Definition”. The Hyperty data model will be used to describe Hyperties capabilities and it will be used by the Governance Directory Service to support publication and discovery of Hyperties. The defined interfaces will be implemented by Hyperties, Management and Messaging Nodes.
D3.1 contains a detailed specification of reTHINK Core Framework components comprised by the runtime environment where Hyperties are executed and the messaging nodes used to support messages exchange between Hyperties. This specification is sustained by comprehensive work in terms of state of the art research and procurement of existing open source that will be used to demonstrate the feasibility of the radical reTHINK concepts. The core of this report contains a detailed specification of the Hyperty Runtime API and of the main procedures to support use cases, requirements and concepts defined in previous reports, providing the basis for the implementation tasks.
D4.1 provides an initial description and specifications of the following components of the reTHINK architecture, dealing with management functionalities, namely: Policy Management, Governance, Identity Management, Graph Connector, and Hyperty Directory services (Catalogue and Registry). The document contains a global picture of the components involved, detailed descriptions of these modules and state-of-the-art and procurement of existing products and especially candidate open source solutions that may be used as a basis for implementation. These components are used throughout reTHINK use-cases and scenarios to provide reTHINK Support Services such as authenticating users, finding their reachability addresses, or providing them a trustworthy communication environment. This document will be used by development tasks that are expected to provide in-depth specifications. Integration activities will bring feedback that will enable us to revise the specifications in order to deliver the final set of specifications that will constitute the final version of this deliverable.

• Objective 2: To design and develop security and portability features necessary to ensure a secure and trustworthy service, compatible with European/national regulations; to propose solutions to measure the confidence level of identities provided by a third party service and realize convergent and multi-party services, relying on a trusted identity provider.

Initial considerations towards this objective are included in D4.1, which includes major components in the areas of policy and identity management as described in the context of objective 1 above. Further work towards this objective is included in D4.2.
D4.2 contains documentation that accompanies release of reTHINK phase 1 Support Services (i.e. Policy Management, Identity Management, Graph Connector, Catalogue and Registry). It complements the release of phase 1 Core Runtime (corresponding to D3.2). Deliverable D4.2 provides a set of software runtime modules (Identity Module, Runtime Registry, Graph Connector, Policy Engine), of CSP infrastructure modules (Catalogue, Domain Registry) and of services (Identity Provider, Global Registry). Finally it includes a suite of detailed descriptions and user tutorials targeting external developers.

• Objective 3: To examine the business impact of the concepts developed by “reTHINK” on today’s communication and services ecosystems as well as content delivery and how they might be transformed in the future. The project will analyze who are the players now and who will participate in the future. It will also asses the impact a concept such as reTHINK will have in the economic sphere and in society in general, especially in the the European community.

The work reported in D1.1 corresponds to this objective. This is the first iteration and forms the basis for the choice of use cases that will be implemented in order to demonstrate the advantages of the framework.
D1.1. elaborates on the changes in the conventional telecommunication industry which is attacked and deprived of its central role in the world of communication. While new players are constantly stepping into the market, more and more communication silos are building. The services hardly “talk” to each other. reTHINK aims to change that and at the same time tries to identify new roles for the stakeholders in the ecosystem to reclaim status, customers and in the end revenues. D1.1 approaches the topic by defining future communication and service scenarios, use cases and business models and also examines the impact of the development onto business process and ecosystems. In a first step the service scenarios have been classed among the topic “Smart Cities/ Smart Enterprises” – corresponding Use Cases have been identified – the business role of a broker (of different characteristics) will be central for the future very agile service worlds and eco systems and the business processes for hyperty lifecycles and partnership management have been designed accordingly.
Feedback from the development of the architecture components and the use cases will feed back into the corresponding work in order to perform a final iteration towards this objective that is reported in D1.2.

• Objective 4: To validate its effectiveness by applying reTHINK to a set of use cases that represent the most important application areas, such as real-time audio/video communication, content delivery via Content Delivery Networks (CDNs), and M2M communication enabled by the Internet of Things. The selected application areas (use cases) include classic Telecom services, entertainment, Over-The-Top (OTT) communication services and smart homes.

The validation of the effectiveness of the framework is based on the work of WP5 and WP6 through the reports D5.1, D6.1, D5.2, and D6.3.
D5.1 collects a selection of Service Scenarios to be implemented and deployed in testbeds to showcase the reTHINK technology. Detailed design of all aspects of the use-cases is provided in this document, covering the end-points, the core network services and the overall communication Service Scenarios. For each Service Scenario, the role of actors, the functionalities, the requirements and the applications and Hyperties involved are fully described in this document. The objective is to provide the specifications to be used in the implementation of the Hyperties and the different Service Scenarios.
D6.1 defines the technical infrastructure of the reTHINK testbed nodes and provides manual for using, connecting to the testbed infrastructure. In particular, it describes a generic “blueprint” of a testbed node that suits for demonstrating reTHINK developments. As such, a testbed node can be instantiated regardless of the node’s location. All components required by each testbed node are provided as public docker images as such enabling sustainability of the testbed. Companies following up on a potential commercial exploitation of the results may easily instantiate a testbed at their (local) premises via the documentation provided in this report. The document is a manual providing the details on the methodology how the generic “blueprint” of a testbed node was derived based on project specific constrains as well as based on deployment constrains coming from the testbed locations chosen within the project. Details on how to setup each docker image that compose a testbed node are provided.
D5.2 contains documentation that accompanies Phase 1 release of reTHINK scenarios components stored as source code in the reTHINK Github repositories. The reTHINK scenarios Phase 1 release includes a collection of hyperties (Connector, Group Chat, MyBracelet, Location, User-Status and Hotel Guest Room Monitor & Control) and the first release of some of the applications for the scenarios (Address Book, Smart Contextual, Smart Business, Hotel Guest, Hotel Administrator, My City and Tourism) to be deployed in testbeds to validate rethink results. This deliverable also collects the most relevant improvements and limitations identified during the implementation process to be considered for phase 2.
Finally D6.3 is the first edition of a critical evaluation of the reTHINK framework performance according to phase 1 trials. This initial evaluation is more focused on technical information collected during the trials. Initial feedback from developers and hackathon participants were also considered.

• Objective 5: To realize standardisation and exploitation activities, including the dissemination of results to increase European competence in the WWW and web-driven real-time communication service domain.
The work towards this objective is reported in deliverables D7.1 and D7.2.

D7.1 presents the initial dissemination plan and identifies the elements for a successful exploitation of the project results. This plan is the basis for steering and controlling dissemination and standardisation activities. An appendix to this document covers overarching issues concerning data management. It concerns all qualitative and quantitative data generated by the project. For the creation of this Data Management Plan the EC guidelines on “Open Access to Scientific Publications and Research Data in Horizon 20201” and “Guidelines on Data Management in Horizon 20202” have been consulted.
D7.2 is the first dissemination report of reTHINK project containing midterm results of all dissemination and exploitation activities obtained in the project. It also contains an updated version of the dissemination plan to be followed till project completion.

Work Package 1
WP1 is organized in three tasks which will take care of the topics scenarios and use cases, business models and business processes. The first delivery of WP1 – D1.1 “Use Cases and Business Models” - was due in May 2015 and provided the basis for the technical work packages within project reTHINK. The second delivery – D1.2 “Use Cases and sustainable Business Models for reTHINK” then is due in July 2016.
Q1 (2015): all partners began work on WP1 with providing scenarios that represented their ideas about future communication and services. Those scenarios – clustered into 6 categories – lead to 92 use cases as a basis for Task 1.2 and the technical work packages. Two scenarios and their related use cases have been chosen by the partners for further analysis regarding actors, roles, requirements and associated use cases.
Simultaneously Task 1.2 started the analysis of eco systems and value chains in today’s telecommunication industry.
The results of both efforts then lead into the identification of potential business models for communication and service scenarios based on the reTHINK concept.
Q2 (2015): Works on scenarios, use cases and business models have been continued and finalized to be delivered with document D1.1.
Additionally, work on Task 1.3 started with an analysis of relevant frameworks for business process description and modelling. The Business Processes for the Hyperty Life-Cycle and the Partner Lifecycle Management have been designed.
Q3 (2015): WP 1 went into hiatus for the time being, awaiting feedback from other work packages. Based on the deliveries of the other WPs alignment discussions have been conducted.
Shortly after the kick-off of the work in WP1, the work in WP2, WP3 and WP4 started. Frequent interaction among all WPs took place in order to facilitate and support coherency of the framework and its components.
The work was idle in Q4 and resumed in Q5/Q6 towards the refinement of D1.1 that will reported in D1.2.
Q5 (2016): From the set of scenarios described in document D1.1, a total of 6 scenarios have been chosen to be further analysed regarding business opportunities and business models. Each scenario has been refined (in coordination with especially WP5) and an in depth analysis is being conducted on each of them.
Q6 (2016): Additionally to the two Life Cycles described in Document D1.1, a third Life Cycle (User Life Cycle) will be developed. The works on that started and finished in this quarter. Additionally, most of the business model analyses have been finished. The works to show the business potential of reTHINK have been started.
In Quarter 7 the business analysis and the demonstration of the business potential of the rethink Framework will be finished and Document D1.2 subsequently delivered. After that, WP1 will be closed.

Work package 2
The WP2 of the project is organized in four tasks closely related to the general architecture of the proposed reTHINK framework. These four tasks have been conducted successively to issue the two first deliverables of the Work Package, the D2.1 and D2.2. The task 2.1 (Technical Requirements derivation) refined the inputs of the scenarios to determine the technical requirements of reTHINK. The task 2.2 built the general, high level, architecture of the reTHINK framework to be detailed in the development work packages, and the tasks 2.3 and 2.4 proposed a data model and architecture to the development work packages.
Q1 (2015): at the beginning of the project, expectations of each partner involved in WP2 where collected to define the overall effort and the interests of each partner in the work package. Based on this initial list and also from the use-cases described in Document D1.1, the architecture requirements (functional and non-functional) have been defined (task 2.1).
During this term, the vocabulary has been defined and validated by all the stakeholders. Then WP2 work has continued by gathering “State-of-the-Art” from every technology more or less connected to reTHINK concepts. Many partners contributed to compile the state of the art section in D2.1.
Q2 (2015): reThink architecture definition work has continued by taking into account the Web Telco/Convergence in the control and media plane, the authentication and authorization mechanisms. The Data model task T2.3 and Interface Task T2.4 also began during this term. An initial draft of the reTHINK architecture was provided and described for the first release of D2.1. Each stakeholder contributed in the first release of D2.1 with the details of their work, put in perspective with the reTHINK objectives and overall architecture.
Q3 (2015) during this period, the reThink architecture was finalized, refining the descriptions and topics that had to be resolved, including the main interactions between components.
Document D2.1 that defines the architecture was delivered at the end of July. At the same time, the work defining the datamodel has been performed, and the general interface mechanisms have been designed. This work was necessary to describe in details the communication between Hyperties, and to facilitate the design of the runtime components. This resulted in the issue of the Document D2.2, presenting data model and interfaces delivered at the beginning of September 2015.
More recently, WP2 has begun the work on the “Final design architecture” document (deliverable D2.3 due at the end of September 2016).

Work package 3
WP3 “Core Framework Implementation” has achieved Phase 1 milestones by providing the specification and implementation of the initial releases for the Hyperty Runtime and Messaging nodes and associated deployment packages.
The technical details and the information needed by developers to start prototyping reTHINK Core Framework, which is comprised of the runtime environment where Hyperties are executed and the messaging nodes used to support messages exchange between Hyperties, were provided by releasing D3.1. The reTHINK Core Framework specification was based on a comprehensive state of the art research on web runtime and real-time messaging with special attention given to security as well as by an exhaustive work in terms of procurement of existing open source solutions to be used to prototype reTHINK Core Framework components. Taking as input the procurement report, some solutions were selected and some implementation considerations were made. The specification task was dedicated to the specification of the Hyperty Runtime architecture and the Core Runtime components required supporting the execution of Hyperties. The design of the Hyperty Runtime APIs were validated with detailed descriptions of the main procedures to be supported by the Hyperty Runtime, namely basic procedures (e.g. message routing and Hyperty deployment), Identity Management Procedures (e.g. registration and login of users), Human to Human communication procedures and Machine to Machine communication procedures.
Phase 1 Core Framework components were implemented and published in reTHINK Github repositories, including the Hyperty Runtime (Core Runtime Components that are reused in Hyperty Browser Runtime and Hyperty NodeJS Runtime) and three Message Node implementations: Vertx Message Node, Matrix Message Node, and NodeJS Message Node. The Hyperty Service Framework was also released and it features a comprehensive set of application program interfaces (APIs) and JavaScript libraries to facilitate the development of Hyperties. A full suite of documentation targeting external developers was provided as well. reThink Core Framework source code repositories are publicly available on GitHub at:
• Hyperty Core Runtime: https://github.com/reTHINK-project/dev-runtime-core
• Hyperty Runtime Browser: https://github.com/reTHINK-project/dev-runtime-browser
• Hyperty Runtime NodeJS: https://github.com/reTHINK-project/dev-runtime-nodejs
• Vertx Message Node: https://github.com/reTHINK-project/dev-msg-node-vertx
• Matrix Message Node : https://github.com/reTHINK-project/dev-msg-node-matrix
• NodeJS Message Node: https://github.com/reTHINK-project/dev-msg-node-nodejs
• Hyperty Service Framework: https://github.com/reTHINK-project/dev-service-framework
These components were used to implement Phase 1 reTHINK scenarios in WP5.
WP3.3 focuses on offering specialized network services for Over-The-Top (OTT) communication service providers.
It consists in two parts:
• Last Hop Connectivity Broker (LHCB) is a connectivity brokerage (Fokus).
• Specialized Network Services for OTT communication services (DT and Orange).
LHCB
LHCB focuses on last hop connectivity brokerage is based on dynamically registering end-devices at a LHCB within the reThink network architecture in order to hold at the LHCB information about currently available, alternative connection mechanisms to connect the client with the network. The methodology is based on reusing concepts from LWM2M device management which provides a standardized way for the LHCB registration and update functionality independent of network service providers' core components.
LHCB was discussed during WP3.3 meetings and its implementation is an ongoing work at Fokus.
Specialized Network Services
Specialized Network Services are used for assuring differentiated services for OTT communication services. During WP3.3 we agreed on a global architecture (for wireline and mobile networks) that allows providing differentiated services to real-time traffic, notably WebRTC.
For mobile access networks the solution was discussed theoretically.
The focus was given on evaluation of this solution in wireline access networks. The prototype developed allows choosing queuing mechanisms able to improve WebRTC in different contexts, residential or enterprise. The Proof of Concept was created developed and evaluated in a series of tests.
Furthermore, a brokering service was studied in detail and implemented. This service enables creating a single contact point allowing any OTT communication service provider to request specialized network service from different network operators.
At this point, implementation and first evaluation are finished. A paper describing the results has been submitted and accepted to SoftCom 2016 (Evaluation of network solutions for improving WebRTC quality). The integration in the runtime of an application has been done, but still to be included in the reThink runtime.
The implementations are dockerized and certain functionalities are installed on several Banana Pis (for increased mobility). Sources are available on the GitHub at:
https://github.com/reTHINK-project/dev-qos-support
A complete demo is available in a simple application available on the Orange Testbed: it necessitates the router equipment to work.

Work package 4
WP4 “Governance and Security model Implementation” worked on reTHINK support services identified during architecture design (WP2): Identity & Trust Management, Hyperty Directories (Catalogue and Registry), Discovery service, Graph Connector, and Governance & Policy Management. Task T4.1 released deliverable D4.1 “Management and Security features specifications” that contains a global picture of the components involved, descriptions of these modules and state-of-the-art and procurement of existing products (especially candidate open source solutions that may be used as a basis for implementation). The document shows how these components interact to authenticate users, discover their reachability addresses (i.e. the running Hyperty instances through which they may accept calls), and provide users a trustworthy communication environment. Notably the document presents a way to achieve identity portability throughout reTHINK service providers.
Afterwards WP4 started implementation tasks (T4.2 to T4.5) to provide detailed specifications and develop these modules, thus achieving deliverable D4.2 “Implementation of Governance and identity management components for phase 1”. reTHINK Support Services are available through several repositories:
https://github.com/reTHINK-project/dev-IdPServer-phpOIDC
https://github.com/reTHINK-project/dev-IdPServer
https://github.com/reTHINK-project/dev-registry-domain
https://github.com/reTHINK-project/dev-registry-global
https://github.com/reTHINK-project/dev-catalogue
Note that runtime modules (Identity Module, Runtime Registry, Graph Connector, Policy Engine) are part of the Core Runtime thus are installed with it.
WP4 has also worked to integrate these modules with WP3 in order to build the first demonstration scenarios (WP5) and to deploy testbeds (WP6).
Also WP4 has begun working on the phase 2 specifications (deliverable due end September 2016).

Work package 5
WP5 activity started in month M05. The methodology to be followed in this WP and the time plan to get the first milestone of the WP were defined during the first months. One of the first activities carried out was the selection of the usage scenarios defined in deliverable D1.1 to be implemented and deployed in WP6 testbeds. The details of the service scenarios to be implemented have been agreed accordingly with the functionalities designed and implemented in WP3 and WP4. The details of the architecture for these scenarios and the hyperties involved were explained in deliverable D5.1.
During the last six months WP5 activity was focused on the implementation of the basic hyperties: Connector Hyperty to support audio and video communication with users, Group Chat Hyperty to support chat communication with group of users, User-Status Hyperty to manage user’s availability context, MyBracelet Hyperty to collect and publish data from a connected bracelet, Location Hyperty to select the users for a group chat regarding their location and Hotel Guest Room Monitor & Control Hyperty to manage the sensors in the room.
First integration of these hyperties with the service Framework and the Runtime provided by WP3 allowed the implementation of the first drafts of the applications to build the phase 1 release of the reTHINK scenarios. Details and source code of these hyperties and applications implemented are described in D5.2.

Work package 6
The description of wok (DoW) foresees for Work Package 6 to contribute on the integration and validation of reTHINK results, thus having three overarching main objectives:
• Specifying and building a test bed infrastructure,
• Building demonstrations, and
• Providing an environment to allow for easy pre-commercialization of reTHINK results.
Those objectives are further detailed as such that
• Built test beds
o are to be used to validate the properties of reTHINK, and
o should span across multiple infrastructures and domain.
• Demonstrations
o are built via the applications and hyperties developed in Work Package 5, and
o are used to asses those reTHINK developments via the demonstrators
• Prototypes
o are provided the industrial partners a first prototype suitable for being used in pre-commercial and exploitation preparation activities, and
o are provided the dissemination partners a first prototype suitable for using it in conferences and technological events and shows for promoting results
WP-6 focused in the reporting period on the specification and set-up of test beds at four locations spanned across Europe (i.e., at the Deutsche Telekom and Fraunhofer premises in Germany, Orange in France, and PT in Portugal). The methodology applied for specifying the testbeds inherently coped for sustainability of test bed deployments by choosing a fully docker-based approach for creating all test bed core components; which is also a favourable way of shipping prototypes for potential pre-commercialization activities. In addition, WP-6 took the developments of applications and hyperties in WP-5 and created a set of demonstrations that were, e.g., successfully demonstrated to the external advisory board. The test beds allowed conducting an assessment of the reTHINK concepts and developments.
Those achievements of WP-6 in the reporting period are documented in the following tangible results:
• Deliverable and Milestones:
o D 6.1 – Testbed specification
o D 6.3 – Assessment Report
o MS 6.1 – Testbed provisioning and operational
o MS 6.2 – Accessible reTHINK infrastructure specification
o MS 6.3 – Intermediate Assessment Report
• Framework for docker image generation for reTHINK testbeds: https://github.com/reTHINK-project/testbeds
• Docker Images of testbed components:
o https://hub.docker.com/r/rethink/testbed-baseline/
o https://hub.docker.com/r/rethink/dev-catalogue/
o https://hub.docker.com/r/rethink/catalogue-baseline/
o https://hub.docker.com/r/rethink/catalogue-database/
o https://hub.docker.com/r/rethink/catalogue-broker/
o https://hub.docker.com/r/rethink/catalogue-test-client/
o https://hub.docker.com/r/rethink/catalogue-database-rethinkdefault/
o https://hub.docker.com/r/rethink/catalogue-database-rethink-helloworld/
o https://hub.docker.com/r/rethink/testbed-apache2-reverse-proxy-baseline/
o https://hub.docker.com/r/rethink/registry-domain-server/
o https://hub.docker.com/r/rethink/msg-node-vertx/
• Deployed testbed components:
o https://energyq.idp.rethink.orange-labs.fr/login
o https://msg-node.powercommunication.rethink.orange-labs.fr
o https://catalogue.powercommunication.rethink.orange-labs.fr/
o https://registry.powercommunication.rethink.orange-labs.fr/
o https://hybroker.rethink.ptinovacao.pt/examples/
o https://catalogue-rethink.fokus.fraunhofer.de
o http://catalogue-testpage-rethink.fokus.fraunhofer.de
The following section details on how WP-6 achieved these tangible results.
To design and set-up the test bed at the reTHINK partner locations, WP-6 adopted the following methodology: All partners that are to host a reTHINK testbed were queried to identify their operational constrains for running a project test bed. While “internet-access” could be granted to hosts running reTHINK components, company policies denied external users to install software on the test bed computers hosted at their premises, nor did they allow for remote access via rsh / rlogin. As a result, a member of the project team affiliated with the company hosting the test bed was required to install (and locally update) rethink components. That yielded to an optional constrain to provide software packages that are extremely easy to install and maintain.
Regarding the project-specific part, WP-4 indicated that all core-components would be developed under Unix (i.e. Ubuntu); WP-3 and in particular WP-5 did not impose any particular constrains. End-devices that run their developed components and applications are required to access the test bed components via http / IP which was immediately satisfied as all test bed components are accessible from the public Internet.
Considering all constrains, WP-6 decided to create a fully docker-image-based test bed set-up. WP-6 instantiated a method, which automatically creates docker-images based on updated source code in the reTHINK GitHub repositories. Docker images are provided for each functional (core) component of a reTHINK test bed node; they are by default configured to run via a “localhost” configuration, i.e., a user may download images and run all of them locally on a single machine which allows for easy development and testing of both, applications and hyperties, as well as extension of the reTHINK framework. Running the docker images that compose a test bed on publically accessible nodes (i.e., at the DT, Fraunhofer, PT, and Orange premises) allows for sharing test bed components between reTHINK partners and external users to test for, e.g., interoperability. The docker-based test bed setup was used for demonstrations presented at the external advisory board. A detailed specificaton of the test bed, including on how to use the docker images, is documented in D6.1. Docker images are publically available at https://hub.docker.com/r/rethink.
For an initial evaluation of the reTHINK developments, WP-6 focused on technical information collected during ongoing phase 1 trials with preliminary feedback from scenario developers and participants to a mini-Hackathon. Technical evaluations for phase 1 developments were conducted for the Message Node, Runtime, Global Registry, Domain Registry, Catalogue, and Identity Provider. Tests included validating conformance of the implementation with respect to the specification as well as a performance assessment of the developed components. Conformance tests revealed minor implementation

Progress beyond the state of the art and expected potential impact (including the socio-economic impact and the wider societal implications of the project so far)

The project has been initiated by leading European network operators in order to develop a Web-centric service architecture, to strengthen European industry for closer integration of the IT and telecom worlds, enabling innovation for services and applications. The framework enables dynamic trusted relationships among distributed applications that support use-cases beyond commodity voice, such as contextual and social communications, M2M/IoT and content oriented services.
The activities in the project and their market relevance will support the creation of a ‘Future Internet’ network of European researchers. The activities to engage entrepreneurs and developers to trial and exploit the technology will contribute to the sustainability of the solution.
The platform will provide opportunities for innovative developers to get their products and concepts prototyped and trialled on leading operator’s advanced service platforms. For this purpose the project plans to organise hackathons as an opportunity for intensive exposure to the project results. Through the planned testbed activities and the engagement of the developer community, the project will establish one large scale validation trial.
The project is reviewed by an advisory board with high profile experts and Internet Industry executives, to create links with related international developments, to promote world-wide visibility of the work and to receive feedback on the progress, supporting global views on open standards and interoperability.

Related information

Follow us on: RSS Facebook Twitter YouTube Managed by the EU Publications Office Top