SPECIALIST TASK FORCE STF 505 IOT - docbox.etsi.org · SPECIALIST TASK FORCE STF 505 ... interoperability in order to support the LSPs For this purpose ETSI has been tasked to provide

SPECIALIST TASK FORCE STF 505 ‐ IOTStandards Landscaping and IoT European Large Scale Pilots (LSP) Gap AnalysisPresented by Joachim Koss for ETSI IoT/M2M Workshop 2016STF 505‐IoT Leader

© ETSI 2016. All rights reserved

ETSI Specialist Tasks Force STF 505 ‐ IoT

The European Commission runs the EU Research and Innovation program Horizon 2020.It supports the emergence of an eco‐system capable of delivering the Internet of Things with actions like• Validation of IoT technologies and approaches through Large Scale innovation

Pilots (LSPs); • Identification of required standards in support of global deployments and

interoperability in order to support the LSPs

For this purpose ETSI has been tasked to provide two reports on“IoT Standards Landscaping“ and “IoT European LSP gap analysis“; ETSI TC SmartM2M launched a Specialist Task Force (STF505) toproceed this task

2 © ETSI 2016. All rights reserved

STF 505‐IoT Work Programme

© ETSI 2016. All rights reserved3

TR 103 375IoT Standards landscape

and future evolution

TR 103 376IoT LSP use cases and

standards gaps

Workshopsorganized by STF 505-IoT

Reportsto the EC/EFTA

StableDraft

StableDraft

FinalDraft

FinalDraft

InitialDraft

InitialDraft

Main milestones (EC)

A

B

C

D

H2020LSP Pilots

Proposal deadline StartSelection

Interim Report Final Report

Public review

phase

ETSI TR 103375 and TR 103376 published


http://www.etsi.org/deliver/etsi_tr/103300_103399/103375/01.01.01_60/tr_103375v010101p.pdf http://www.etsi.org/deliver/etsi_tr/103300_103399/103376/01.01.01_60/tr_103376v010101p.pdf

Analysing the standards landscape provides a list of existing standardised technology suggested for reuse by the LSPs

Identifying technical standards/ societal/business gaps as a good indication of the level of maturity of standardization in a given vertical domain

Highlights of TR 103375 – Landscape (1)


TR lists SDOs/SSOs and their published standards in the IoT sectorEach listed standard is generically described TR allocates these standards to vertical IoT domains (LSPs)Smart Cities, Smart Living, Smart Farming, Smart Wearables, Smart Mobility, Smart Environment, Smart Manufacturing

All listed standards are classified into Knowledge Areas (AIOTI WG3):• Communication and Connectivity• Integration/Interoperability• Application• Infrastructure• IoT Architecture• Devices and Sensor Technology• Security and Privacy

View the IoT framework as an enterprise architecture

Enterprise ArchitectureProposed view of the IoT Framework


Contents of the Enterprise ViewArchitecture Reference Modelconsists of an IoT architecture integrating all components that make up an IoT systemIoT domain holds the view of what make up an IoT Standards Information Database (SIB) holds any relevant standards that can be used and with which new enterprise architectures shall comply with. It is the main study of TR 103375Reference Library holds any re‐useable information that can be used across the pilotsGovernance Repository houses any policies, regulations that applies to any LSP

TR 103375

Complexity with IoT comes from the fact, that IoT intends to support a number of different applications covering a wide array of disciplines, that are not all part of the ICT domain.

e.g. B2C, B2B

connectivity, …

services, apps



020406080

100120140160

Allocation of standards

Communication and Connectivity Integration/ Interoperability

Application Infrastructure

IoT Architecture Devices and Sensor Technology

Security and Privacy

329 standards identifiedallocated to • 7 vertical IoT Domains (LSPs) and• 7 Knowledge Areas (AIOTI WG3)

150 Common standards(standards identified of which each being common across at least 3 vertical IoT domains)

179 Domain‐specific standards mostly identified in the IoT domains• Smart Mobility• Smart Living• Smart Manufacturing



More than 70% of the standards allocated to• Communication and Connectivity• Integration/Interoperability• IoT Architecture

Most of the common standards identified in the Knowledge Areas• Communication and Connectivity• Integration/Interoperability• Devices and Sensor Technology• Infrastructure

0

20

40

60

80

100

120

140

Allocation of standards

Common standards Smart Cities Smart Living

Smart Farming Smart Wearables Smart Mobility

Smart Environment Smart Manufacturing

Highlights of TR 103376 – Gaps (1)


Nature of gaps • Missing standards• Missing APIs• Duplications that would require harmonization• Missing interoperability profiles• Classified as: technical, business or societal (incl. security and privacy)

Gaps identification methodology• Survey to obtain inputs from the standardization and stakeholders community, 215

answers as of 30/06/2016• STF experts analysis to expand on the current standards landscape

• For each vertical, extract requirements from the AIOTI reports and other documentation

• Identify if SDOs/Alliances address the target requirement (using TR 103 375)

Resolution of the gaps• Dissemination of STF 505 results: to point to gaps and allocate them• It is left to the proper organizations of the IoT community to fill the gaps



49 main gaps result from the consolidation view (TR 103376)



Gaps in Security and Privacy• IoT platforms have to ensure data privacy, integrity and transmission accordingly to the

information sensibility• Smart environment data, especially those from utilities (energy/water) can be very

sensitive. The lack of these standards prevent large scale deployments• Since Smart Wearables and home devices are dealing with very sensitive and personal

data, the lack of these standards prevents user acceptability.• Security and privacy are addressed on an isolated basis for part of the applications.

Education of end users on these features has also been identified as a new requirement

Gaps in Data Interoperability• A lack of global data model and/or translation mechanisms between different specific

models is clearly a big issue• Alert / alarm message content should be standardized to enable full understanding and

comprehensive information by their recipients

Gaps in Service Platform• A large set of IoT architecture and service platforms. No clear winner among all existing

IoT architectures. Each service platform is currently positioning among the other one through the proposition of underlying interworking plugins

Some Results and Recommendations (1)


IoT (standardization) landscape appears currently fragmented• Generic standards or IoT platforms with seemingly identical purpose• Some clarification may be brought by refinement of the use cases

A number of the standards apply across verticals, some of them apply to specific vertical IoT domainsThe business and societal gaps, though not the subject of standardization activities, are important issues for the IoT industry as well as for the regulatory/legal frameworksDissemination fosters awareness from the different actorsMany connectivity and interoperability standards and specifications are not IoT‐specific.Make the choice for one solution (notably architecture) across verticals that allows for cross domain interoperability

Recommendations to the LSPs:• Select the architecture for the pilots based on the standards that are listed in the

TR 103375• Use as much as possible the standards which are listed as “Common Standards across

vertical domains”• Adopt as many same solutions across the verticals as possible

or at least as much solutions being interoperable amongst the different LSPs as possible• Address parts of the identified gaps

Organize "progress report" events regularly to advertise the progress made with IoT standards, specifications and Open Source towards the IoT Service Customers (in cooperation with the LSPs and CSAs)





Encourage the large SDOs/SSOs to strengthen collaboration and cooperationThe potential of standards, which are identified as “Common Standards across vertical domains” will only materialize if the development of IoT standards in vertical domains is making effective use of those standards rather than reinventing similar but not compliant ones, thus increasing the fragmentation of the IoT standards landscapeEncourage the development of education and dissemination material of IoT standards and specifications(in particular “Common Standards across vertical domains”, e.g. security related ones)Address the seamless interoperability or plug and play in the different standardised IoT architectures and platforms(e.g. exchange of data between the platforms developed by the LSPs)



Lack of usability and security may block the eco‐systems development• Complete the existing set of standards with “usability” topics: certification of

sensors IT security, quality, accuracy and reliability (possibly defining “classes” of sensors), create standards for easy installation and maintenance of all types of devices

Sensed data are collected by a wide range of sensors, then processed by all types of applications:• Enhance the definition of interoperable semantics, to ensure a unique

processing of sensed data (example is the measurement units)

Privacy is a strong concern of EU citizens: • Define regulations for data ownership and enforce the respect of privacy at all

levels of the IoT systems

Next Steps


The TRs will be complemented by additional work on• Generic findings and recommendations• Indications towards the IoT community, in particular the LSPs

Final presentation of results on February 7th in Brussels• Presentation of STF 505 results and recommendations• Feedback from IoT community stakeholders, in particular Standards

Organizations

Panel discussion on IoT & M2M Challengesfor M2M and IoT Standards


Interoperability will be essential for the deployment of the IoT and for ensuring seamless flow of data across sectors and value chains

A lot of IoT technology exists and will continue to existNo single technology satisfies the needs of all IoT domains and applicationsEnabling the emergence of IoT ecosystems needs a standardised architecture/platform which must provide integration of advanced IoT technologies interoperability across IoT domains and applications incl. sematic features scalability

My assertion

Contact Details:

Joachim Koss

JK Consulting & ProjectsEmail: jk‐[email protected]: +49 3379 379092Mobile: +49 157 32100402

18

Thank you for your attention!

© ETSI 2016. All rights reserved

STF505 Homepage: https://portal.etsi.org/stf.aspx?tbid=595&SubTB=595

ANNEX

19 © ETSI 2016. All rights reserved

AIOTI Knowledge Area 1/2


Communication and Connectivity:Covers mainly specification of communication protocol layers, including PHY, MAC, NWK, Transport, Application layer, and their types, e.g. Wireless/Radio and Wire lineIntegration/Interoperability:Covers mainly specification of common IoT features required to provide integration and interoperabilityApplications:Covers the support of the applications lifecycle including development tools/models, deployment and management; including analytics, application supporting tools and application domain specific activities

AIOTI Knowledge Area 2/2


Infrastructure:Covers aspects related to the design, deployment, and management of computational platforms tailored to support IoT‐based applications IoT Architecture:Covers integrated/complete IoT specification solutions, including architecture descriptionsDevices and sensor technology:Covers mainly device/sensor lifecycles, including operating systems, platforms, configuration management, sensor/actuators virtualization etc.Security and Privacy:Covers security and privacy topics

Documents

SPECIALIST TASK FORCE STF 505 IOT - docbox.etsi.org · SPECIALIST TASK FORCE STF 505 ... interoperability in order to support the LSPs For this purpose ETSI has been tasked to provide