Specialist Task Force 535:
Architecture and Components for Virtualised IoT
Who we are:
| Team Leader: |
|
| Team Member: |
|
What we do
In addition to interoperability and security that are two recognised key enablers to the development of large IoT systems, a new one is emerging as another key condition of success: virtualisation. The deployment of IoT systems must be possible not just within closed and secure administrative domains but also over architectures that support the dynamic usage of resources that are provided by virtualisation techniques over cloud back-ends.
This new challenge for IoT requires that the elements of an IoT system can work in a fully interoperable, secure and dynamically configurable manner with other elements (devices, gateways, storage, etc.) that are deployed in different operational and contractual conditions. To this extent, the current architectures of IoT will have to be aligned with those that support the deployment of cloud-based systems (private, public, etc.).
Moreover, these architectures will have to support very diverse and often stringent non-functional requirements such as scalability, reliability, fault tolerance, massive data, security. This will require very flexible architectures for the elements (e.g. the application servers) that will support the virtualised IoT services, as well as very efficient and highly modular implementations that will make a massive usage of Open Source components.
These architectures and these implementations form a new approach to IoT systems and the solutions that this STF will investigate will also have to be validated: to this extent, a Proof-of-Concept implementation involving a massive number of virtualised elements will be made.
This is what the STF 535 is addressing, in support of the ETSI SmartM2M Technical Committee.
For more details, see our Terms of Reference
Why we do it
A major reason to launch this STF is to expand the reach of IoT systems that are currently supported by the oneM2M standards (to which the SmartM2M TC is contributing). The extension and refinement of oneM2M standards and the possibility to validate platforms over virtualised back-ends will open new spaces in the IoT ecosystem. New applications will be more easily developed in more modular and flexible manner at lower cost of development (large reuse of open source solutions) and lower cost of ownership (less capital investment due to the easy and potentially massive usage of virtualised resources).
How we do it
Apart from the task related to the STF project management, the STF will work in three tasks that correspond to the development of the 3 Technical Reports that are the deliverables of the STF.
Deliverables
Three technical reports (TR) will be developed:
TR 103 527 Virtualized IoT Architectures with Cloud Back-ends
This report addresses the rationale and expected benefits for the use of virtualisation – and the cloud in general – in support of IoT systems, together with the identification of new architectural elements (components, mappings, APIs, etc.) that are required to address IoT on a cloud back-end. It will also make a description of some use cases that benefit from virtualization.
TR 103 528 Landscape for open source and standards for cloud native software for a Virtualized IoT service layer
This report provides a detailed description of 1/ the supporting standards (in particular the ones form the Cloud Computing space); and 2/ the supporting open source projects, their key features and their level of maturity for the purpose of building a virtualized IoT service layer.
TR 103 529 Virtualized IoT over Cloud back-ends: a Proof of Concept
This report provides an in-depth description of a use case supporting Horizontal Scalability and how it is implemented, in particular the main components developed and how they can be possibly mapped within the oneM2M framework. In addition to the TR itself, the source code of the Proof of Concept will be available on the ETSI Source Forge.
Time plan
The work of the STF has started on October 1st, 2017. It is expected to be over by the end of July 2018. The timing for the delivery of the 3 Technical Reports is as follows:
• TR 103 527 (Virtualized IoT Architectures)
Stable draft: 31/12/2017
Final report: 31/07/2018
• TR 103 528 (Landscape of Open Source and Standards)
Stable draft: 28/02/2018
Final report: 31/07/2018
• TR 103 529 (Virtualized IoT: a proof of concept)
Stable draft: 31/05/2018
Final report: 31/07/2018
Please contact us via email: Emmanuel.darmois@commledge.com