ETSI TR 103 376 V1.1.1 (2016-10)

SmartM2M; IoT LSP use cases and standards gaps

DTR/SmartM2M-103376

General Information

• Status: Published
• Publication Date: 20-Oct-2016
• Technical Committee: SmartM2M - Smart M2M
• Current Stage: 12 - Completion
• Due Date: 10-Nov-2016
• Completion Date: 21-Oct-2016

Standards Content (Sample)

TECHNICAL REPORT
SmartM2M;
IoT LSP use cases and standards gaps

2 ETSI TR 103 376 V1.1.1 (2016-10)

Reference
DTR/SmartM2M-103376
Keywords
IoT, M2M
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TR 103 376 V1.1.1 (2016-10)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 General Considerations . 10
4.1 Introduction . 10
4.1.1 Defining gaps . 10
4.1.2 Identifying gaps: user survey . 11
4.1.3 Identifying gaps: requirements analysis . 11
4.1.4 Mapping gaps. 12
4.2 Vertical domains covered . 13
4.3 Knowledge Areas . 14
5 Gap analysis in the context of Smart Cities. 16
5.1 High level description and analysis . 16
5.2 Mapping of requirements and related standard coverage . 17
5.2.0 Methodology . 17
5.2.1 Communication and Connectivity knowledge area . 17
5.2.1.1 Connectivity at Physical and Link layer. 17
5.2.1.2 Connectivity at Network layer . 17
5.2.1.3 Service level and application enablers . 17
5.2.1.4 Application Layer level, APIs, Data models and ontologies . 17
5.2.2 Integration/Interoperability knowledge area . 18
5.2.3 Applications management knowledge area . 18
5.2.4 Infrastructure knowledge area. 18
5.2.5 IoT Architecture knowledge area . 18
5.2.6 Devices and sensor technology knowledge area . 18
5.2.7 Security and privacy knowledge area . 19
5.3 Result of the survey . 19
5.4 Consolidated view of the gaps . 22
6 Gap analysis in the context of Smart Living environments for ageing well . 23
6.1 High level description and analysis . 23
6.2 Mapping of requirements and related standard coverage . 23
6.2.0 Methodology . 23
6.2.1 Communication and Connectivity knowledge area . 24
6.2.1.1 Connectivity at physical and link layer . 24
6.2.1.2 Connectivity at network layer . 24
6.2.1.3 Service level and application enablers . 24
6.2.1.4 Application layer level, APIs, data models and ontologies . 25
6.2.2 Integration/interoperability knowledge area . 25
6.2.3 Applications management knowledge area . 26
6.2.4 Infrastructure knowledge area. 26
6.2.5 IoT Architecture knowledge area . 26
6.2.6 Devices and sensor technology knowledge area . 26
6.2.7 Security and privacy knowledge area . 27
6.3 Result of the survey . 27
6.4 Consolidated view of the gaps . 30
ETSI
4 ETSI TR 103 376 V1.1.1 (2016-10)
7 Gap analysis in the context of Smart Farming and food security . 30
7.1 High level description and analysis . 30
7.2 Mapping of requirements and related standard coverage . 31
7.2.0 Methodology . 31
7.2.1 Communication and Connectivity knowledge area . 31
7.2.1.1 Connectivity at physical and link layer . 31
7.2.1.2 Connectivity at network layer . 31
7.2.1.3 Service level and application enablers . 32
7.2.1.4 Application layer level, APIs, data models and ontologies . 32
7.2.2 Integration/interoperability knowledge area . 32
7.2.3 Applications management knowledge area . 32
7.2.4 Infrastructure knowledge area. 33
7.2.5 IoT Architecture knowledge area . 33
7.2.6 Devices and sensor technology knowledge area . 34
7.2.7 Security and privacy knowledge area . 34
7.3 Result of the survey . 34
7.4 Consolidated view of the gaps . 36
8 Gap analysis in the context of Smart Wearables . 36
8.1 High level description and analysis . 36
8.2 Mapping of requirements and related standard coverage . 36
8.2.0 Methodology . 36
8.2.1 Communication and Connectivity knowledge area . 37
8.2.1.1 Connectivity at physical and link layer . 37
8.2.1.2 Connectivity at network layer . 37
8.2.1.3 Service level and application enablers . 37
8.2.1.4 Application layer level, APIs, data models and ontologies . 38
8.2.2 Integration/interoperability knowledge area . 38
8.2.3 Applications management knowledge area . 38
8.2.4 Infrastructure knowledge area. 38
8.2.5 IoT Architecture knowledge area . 39
8.2.6 Devices and sensor technology knowledge area . 39
8.2.7 Security and privacy knowledge area . 39
8.3 Result of the survey . 39
8.4 Consolidated view of the gaps . 41
9 Gap analysis in the context of Smart Mobility (smart transport/smart vehicles/connected cars). 41
9.1 High level description and analysis . 41
9.2 Mapping of requirements and related standard coverage . 42
9.2.0 Methodology . 42
9.2.1 Communication and Connectivity knowledge area . 42
9.2.1.1 Connectivity at physical and link layer . 42
9.2.1.2 Connectivity at network layer . 42
9.2.1.3 Service level and application enablers . 43
9.2.1.4 Application layer level, APIs, data models and ontologies . 43
9.2.2 Integration/interoperability knowledge area . 43
9.2.3 Applications management knowledge area . 44
9.2.4 Infrastructure knowledge area. 44
9.2.5 IoT Architecture knowledge area . 44
9.2.6 Devices and sensor technology knowledge area . 44
9.2.7 Security and privacy knowledge area . 45
9.3 Result of the survey . 45
9.4 Consolidated view of the gaps . 46
10 Gap analysis in the context of Smart Environment (smart water management) . 47
10.1 High level description and analysis . 47
10.2 Mapping of requirements and related standard coverage . 47
10.2.0 Methodology . 47
10.2.1 Communication and Connectivity knowledge area . 48
10.2.1.1 Connectivity at physical and link layer . 48
10.2.1.2 Connectivity at network layer . 48
10.2.1.3 Service level and application enablers . 48
10.2.1.4 Application layer level, APIs, data models and ontologies . 49
ETSI
5 ETSI TR 103 376 V1.1.1 (2016-10)
10.2.2 Integration/interoperability knowledge area . 49
10.2.3 Applications management knowledge area . 49
10.2.4 Infrastructure knowledge area. 49
10.2.5 IoT Architecture knowledge area . 50
10.2.6 Devices and sensor technology knowledge area . 50
10.2.7 Security and privacy knowledge area . 50
10.3 Result of the survey . 50
10.4 Consolidated view of the gaps . 51
11 Gap analysis in the context of Smart Manufacturing . 52
11.1 High level description and analysis . 52
11.2 Mapping of requirements and related standard coverage . 53
11.2.0 Methodology . 53
11.2.1 Communication and Connectivity knowledge area . 53
11.2.1.1 Connectivity at physical and link layer . 53
11.2.1.2 Connectivity at network layer . 53
11.2.1.3 Service level and application enablers . 53
11.2.1.4 Application layer level, APIs, data models and ontologies . 54
11.2.2 Integration/interoperability knowledge area . 54
11.2.3 Applications management knowledge area . 54
11.2.4 Infrastructure knowledge area. 54
11.2.5 IoT Architecture knowledge area . 54
11.2.6 Devices and sensor technology knowledge area . 55
11.2.7 Security and privacy knowledge area . 55
11.3 Result of the survey . 55
11.4 Consolidated view of the gaps . 56
12 Cross IoT platform interoperability and harmonization . 57
12.1 Result of the survey for multiple vertical domains . 57
12.2 Consolidated view of the gaps . 63
13 Conclusion . 64
Annex A: Feedback from Brussels AIOTI meeting held in November 2015 . 65
Annex B: ETSI STF 505 Gap Analysis Survey . 66
B.1 Content of the survey . 66
B.2 Some statistics on the answers . 69
History . 72

ETSI
6 ETSI TR 103 376 V1.1.1 (2016-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Report (TR) has been produced by ETSI Technical Committee Smart Machine-to-Machine
communications (SmartM2M).
TM TM TM TM TM TM TM TM
NOTE: 3GPP , AllJoyn , AllSeen Alliance , ASHRAE , AVNU Alliance , B2MML , BACnet ,
TM TM TM TM TM TM TM TM TM TM
Bluetooth , C2C-CC , DASH7 , DICOM , EnOcean , HL7 , IETF , IIC , KNX , LoRa ,
TM TM TM TM TM TM TM
LR-WPAN , LTE , LTE-Advanced , LTE-Advanced Pro , MIPI , MirrorLink , OASIS ,
TM TM TM TM TM TM TM
OCF , OGC , OMA , OMG , OPC , OSGi , SAE INTERNATIONAL , SERCOS
TM TM TM TM TM TM
International , UMTS , W3C , Wi-Fi Alliance , ZigBee and Z-Wave are tradenames registered
by their respective owners. This information is given for the convenience of users of the present
document and does not constitute an endorsement by ETSI of these products and/or associations.
Modal verbs terminology
In the present document "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be
interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
7 ETSI TR 103 376 V1.1.1 (2016-10)
1 Scope
Starting from the use case families selected for the IoT Large Scale Pilots (LSPs) the present technical report aim is:
• To provide the collection of all missing functionalities that have been identified in standards bodies (SDOs) to
offer solutions addressing the use case requirements.
• To check that there are no omissions in the standardization activity with regard to the use cases. In particular,
gaps with respect to the framework as identified by oneM2M should be identified.
• To propose some recommendations to overcome potential gaps. Particular attention will be paid on horizontal
application layer standardization and to assure an interworking framework among different vertical industrial
segments.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 103 375: "SmartM2M; IoT Standards landscape and future evolutions".
[i.2] AIOTI WG03: "IoT Large Scale Pilots (LSP) Standard Framework Concepts", Release 2.0,
October 2015.
[i.3] AIOTI WG03: "Report on High Level Architecture (HLA)", Release 2.0, October 2015.
[i.4] AIOTI WG08: "Smart City LSP Recommendations Report", October 2015.
[i.5] AIOTI WG05: "Report on Smart Living Environment for Ageing Well", October 2015.
[i.6] AIOTI WG09: "Report on Smart Mobility", October 2015.
[i.7] AIOTI WG07: "Report on Wearables", October 2015.
[i.8] AIOTI WG11: "Report on Smart Manufacturing", October 2015.
[i.9] ISO 37120: "Sustainable development of communities -- Indicators for city services and quality of
life".
[i.10] Recommendation ITU-T X.1255: "Framework for discovery of identity management information".
[i.11] AIOTI WG06 Report: "Smart Farming and Food Safety Internet of Things Applications -
Challenges for Large Scale Implementations", October 2015.
[i.12] Resolution ITU-R 66: "Studies related to wireless systems and applications for the development of
the Internet of Things".
ETSI
8 ETSI TR 103 376 V1.1.1 (2016-10)
[i.13] IEEE 802.1X-2010™: "IEEE Standard for Local and metropolitan area networks -- Port Based
Network Access Control".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
SDO: standards developing or standards setting organization
NOTE: In the present document, SDO is used equally for both types of organizations.
standardization gaps: missing or duplicate elements in the IoT standardization landscape
NOTE: Examples of standardization gaps are: missing standards or regulations, missing APIs, technical
interoperability profiles that would clarify the use cases, duplications that would require harmonization.
They may be technical, societal or business-related.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
3GPP Third Generation Partnership Project
ACEA Association des Constructeurs Européens d'Automobiles
AIOTI Alliance for IoT Innovation
API Application Programming Interface
ASHRAE American Society of Heating, Refrigerating, and Air-Conditioning Engineers
BAN Body Area Network
BBF Broad Band Forum
BSM Basic Safety Message
C2C-CC Car 2 Car Communication Consortium
CAM Cooperative Awareness Message
CCC Car Connectivity Consortium
CEN Comité Européen de Normalisation (European Committee for Standardization)
CENELEC Comité Européen de Normalisation Électrotechnique (European Committee for Electrotechnical
Standardization)
CiA CAN in Automation
CoAP Constrained Application Protocol
CPPS Cyber-Physical Production System
D2D Device-to-Device
DDS Data Distribution Service
DICOM Digital Imaging and Communications in Medicine
DNS Domain Name System
EC European Commission
ERP Enterprise Resource Planning
ETSI European Telecommunications Standards Institute
EU European Union
FIWARE Future Internet -ware
FMIS Farm Management Information Systems
GNSS Global Navigation Satellite System
HF Human Factors
HGI Home Gateway Initiative
HL7 Health Level Seven International
HLA High Level Architecture
HMI Human Machine Interface
HW Hardware
IBM International Business Machines (Corporation)
ICT Information and Communication Technology
ETSI
9 ETSI TR 103 376 V1.1.1 (2016-10)
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronics Engineers
IERC IoT European Research Cluster
IETF Internet Engineering Task Force
IHE Integrating the Healthcare Enterprise
IIC Industrial Internet Consortium
IMT International Mobile Telecommunications
IoT Internet of Things
IP Internet Protocol
IPSO Internet Protocol for Smart Object
ISO International Organization for Standardization
ISO/IEC JTC1 ISO/IEC joint technical committee
ITS Intelligent Transport Systems
ITU International Telecommunication Union
ITU-T International Telecommunication Union - Telecommunication Sector
KA Knowledge Area
KNX KoNneX
LAN Local Area Network
LE Low Energy
LON Local Operator Network
LSP Large Scale Pilot
M2M Machine-to-Machine
MAC Media Access Control
MAN Metropolitan Area Network
MES Manufacturing Execution System
MESA Manufacturing Enterprise Solutions Association International
MQTT MQ Telemetry Transport
NFC Near Field Communication
NWK NetWorK
OAA Open Automotive Alliance
OAGi Open Applications Group
OASIS Advancing Open Standards for the Information Society
OCF Open Connectivity Foundation
ODVA Open DeviceNet Vendor Association
OGC Open Geospatial Consortium
OMA Open Mobile Alliance
OMG Object Management Group
OPC Open Platform Communications
OSGi Open Services Gateway initiative
PAN Personal Area Network
PHD Personal Health Device
PHY PHYsical layer
PII Personally Identifiable Information
PLC Power Line Communication
PLC Programmable Logic Controller
PSA Protocol Standards Association
QoS Quality of Service
ROI Rate Of Interest
ROLL Routing Over Low power and Lossy networks
SAE Society of Automotive Engineers
SCADA Supervisory Control and Data Acquisition
SDO Standards Developing Organization
SERCOS SErial Real-time COmmunication System
SES Satellite Earth Stations and Systems
SLA Service Level Agreement
SME Small and Medium-sized Enterprise
SSO Standards Setting Organization
TC Technical Committee
TCP Transmission Control Protocol
TIM Transducer Interface Module
TR Technical Report
ULE Ultra Low Energy
ETSI
10 ETSI TR 103 376 V1.1.1 (2016-10)
US United States
V2I Vehicle-to-Infrastructure
V2X Vehicle-to-Everything
W3C Worldwide Web Consortium
WAN Wide Area Network
WiMAX Worldwide Interoperability for Microwave Access
WLAN Wireless Local Area Network
WPAN Wireless Personal Area Network
XMPP eXtensible Messaging and Presence Protocol
4 General Considerations
4.1 Introduction
4.1.1 Defining gaps
In ETSI TR 103 375 [i.1], an inventory of the current IoT standardization has been performed. Its objective is to assess
the degree of industry and vertical market fragmentation; and to point towards actions that can increase the
effectiveness of IoT standardization, to improve interoperability, and to allow for the building of IoT ecosystems. ETSI
TR 103 375 [i.1] identifies a number of standards that are available, i.e. that have reached a final stage in a Standards
Developing Organization by the time of writing the report, and can be used for the work of the IoT Large Scale Pilots
(LSP).
However, the coverage of the IoT landscape - and the possibility to develop large-scale interoperable solutions - is not
fully guaranteed since some elements in this landscape may be missing. These missing elements are referred to as
"gaps" in the remainder of the present document. Gaps may also be identified when harmonization or interoperability
between a large number of potential solutions is missing.
These "gaps" are the main point of interest of the present document. Three categories of gaps will be addressed:
• Technology gaps. Some examples in this category are communications paradigms, data models or ontologies,
software availability.
• Societal gaps. Some examples in this category are privacy, energy consumption, ease of use.
• Business gaps. Some examples in this category are siloed applications, value chain, and investment.
In the reminder of the present document, the identification of gaps will be specially made in view of ensuring that they
will be further understood, handled and closed within the IoT community (and possibly beyond). This identification of
gaps will rely on an approach that allows for:
• The characterization of gaps, in particular by understanding the type of gaps (see above), the scope of the gap,
the difficulties it generates, and other appropriate descriptions.
• The mapping of the gaps on an architectural framework (see clause 4.1.3) that allows for the mapping of the
gaps on a reference that can be understood by the IoT community and, in particular, that can be related to other
frameworks e.g. those developed in other organizations, for instance in Standards Setting Organizations.
This characterization and mapping are made with the objective to ensure that - whenever possible - these gaps may be
handled, and hopefully closed, by one or more organizations in the IoT community.
The present document does not have the aim to undertake the resolution of the gaps that is left to the proper
organizations of the IoT community. However, its objective is also to provide recommendations for the future standard
framework.
ETSI
11 ETSI TR 103 376 V1.1.1 (2016-10)
4.1.2 Identifying gaps: user survey
A critical part of the identification of gaps is the collection of those missing elements. Since they can be of very
different nature (see clause 4.1.1) and may have been detected by very different actors of the IoT community, there
needs to be a mechanism to collect the largest possible information. To this extent, a survey has been built in order to
identify as many gaps as possible with the help of the IoT community, in particular the IoT standardization community.
The survey aims at:
• Identifying the domain of activity of the respondent.
• Understanding what his/her objectives and main area of work are.
• Defining up to three gaps of all three types as defined in clause 4.1.1.
The detailed text of the survey can be found in annex B.
The survey has been largely distributed. At the time of writing the final version of the present document, 215 answers
have been collected and the survey is closed. A few statistics on the responders and answers received can be found in
clause B.2.
In a second step, these answers have been analysed with the objective to identify commonalities (i.e. related missing
functionalities that can be considered as one gap) and associated interoperability frameworks.
The answers received have been tentatively classified in the different clauses of the present document. Clauses 5.3, 6.3,
7.3, 8.3, 9.3, 10.3 and 11.3 provide the answers which are related to a defined vertical sector. Clause 12.1 gives the
answers which apply to the horizontal domain or are more generic. However, it should be noted that the answers
received are generally not applicable to one specific vertical sector. For example, readers willing to cover all answers
applicable to the wearable vertical sector should refer to the clauses related to Smart Living, Smart Wearables as well as
clause 12.1. The matrix provided in table 0 gives guidance in that direction.
Table 0: Cross-domain reading of the survey answers
Answers in Horizontal Smart Smart Smart Smart Smart Smart Smart
[vertical or (clause Cities Living Farming Wearables Mobility Manufacturing Environment
horizontal 12.1) (clause (clause (clause (clause 8.3) (clause (clause 10.3) (clause 11.3)
domain on the 5.3) 6.3) 7.3) 9.3)
right] may be
shared with
the [vertical
domain
below]
Smart Cities X X X  X
Smart Living X X X X
Smart Farming X  X  X X
Smart X X X
Wearables
Smart Mobility X X  X X
Smart X  X  X
Manufacturing
Smart X  X X X
Environment
4.1.3 Identifying gaps: requirements analysis
The present clause explains the methodology implemented by the editors of the present document to identify
technological requirements for each of the vertical areas and tentatively map them to organizations that provide
standards related to these requirements.
This study has been executed in parallel and independently from the user survey described in clause 4.1.2.
ETSI
12 ETSI TR 103 376 V1.1.1 (2016-10)
For each vertical sector, the main technological requirements are extracted from the vertical-specific AIOTI reports and
other available documentation describing that vertical sector. In a second step, the listed requirements are classified
according to the knowledge areas to which they belong. They are shown in the left column of the tables. For more
accuracy, the Communication and connectivity knowledge area is divided according to the main usual communication
layers:
• Connectivity at physical and link layer.
• Network layer.
• Service level and application enablers.
• Application level API, data models and ontologies.
The next step identifies which SDOs/Alliances address the target requirement. The standards found are not listed
directly in the present document, since this list maybe complex in some cases (it may be provided however in a revised
version of the present document). The reader is rather referred to the partner TR, ETSI TR 103 375 [i.1], as the
reference where existing concrete standards for each SDO/Alliance that address the specific requirement in the target
vertical domain and knowledge area can be found.
In the case where no standard could be identified for a specific requirement, the requirement is declared as a potential
standardization gap.
4.1.4 Mapping gaps
Before mentioning gaps, and in particular standards gaps that an LSP may have to address in the achievement of its
objectives, one first needs to have a target framework in mind. The AIOTI WG03 has developed a standard framework
or architecture for IoT which is similar or can be mapped to other frameworks such as ITU, oneM2M, IIC. The one
thing that the frameworks have in common is the fact that interoperability must be achived amongst the various
elements of the IoT. Interoperability means having interworking standards with less complexity. With a target model in
mind and an idea of what the current landscape looks like, which are the objectives of the ETSI TR 103 375 [i.1], it is
now possible to identify which are the remaining gaps to achieve IoT. The focus of the present document is to look at
such gaps in the standard that will be needed to achieve the various LSP and make recommendation on going forward.
The landscape analysed in ETSI TR 103 375 [i.1] has described the IoT standards from the view point of the elements
or knowledge areas that make up the IoT framework. The present document adopts a similar structure by looking at the
gaps based on the knowledge areas but it also defines the main requirements specific to each vertical sector, analyses
how they are covered and what the gaps that have been identified are.
Figure 1 shows the AIOTI High Level Target Architecture for IoT (AIOTI HLA).
ETSI
13 ETSI TR 103 376 V1.1.1 (2016-10)

Figure 1: AIOTI high level architecture for IoT (from [i.3])
Interfaces above are:
1: Defines the structure of the data exchanged between App Entities (the connectivity for exchanged data on this
interface is provided by the underlying Networks). Typical examples of the data exchanged across this
interface are: authentication and authorization, commands, measurements, etc.
2: This interface enables access to services exposed by an IoT Entity to e.g. register/subscribe for notifications,
expose/consume data, etc.
3: Enables the sending/receiving of data across the Networks to other entities.
4: Enables the requesting of network control plane services such as: device triggering (similar to "wake on LAN"
in IEEE 802.1X [i.13]), location (including subscriptions) of a device, QoS bearers, deterministic delivery for
a flow, etc.
5: Enables the exposing/requesting services to/from other IoT Entities. Examples of the usage of this interface are
to allow a gateway to upload data to a cloud server, retrieve software image of a gateway or a device, etc.
4.2 Vertical domains covered
As a support for the IoT Large Scale Pilot, the vertical domains that are addressed in the present document are those
where such LSP will be defined and, for some, selected and undertaken. These domains are the following:
• Smart Cities. The modern cities need to evolve and become structured, interconnected ecosystems where all
components (energy, mobility, buildings, water management, lighting, w
...