ETSI TR 103 536 V1.1.1 (2019-12)

TECHNICAL REPORT
SmartM2M;
Strategic/technical approach on how to achieve
interoperability/interworking
of existing standardized IoT Platforms

2 ETSI TR 103 536 V1.1.1 (2019-12)

Reference
DTR/SmartM2M-103536
Keywords
interoperability, IoT, IoT platforms, oneM2M,
SAREF, semantic
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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.

© ETSI 2019.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 ETSI TR 103 536 V1.1.1 (2019-12)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
Introduction . 7
1 Scope . 9
1.1 Context for the present document . 9
1.2 Scope of the present document . 9
2 References . 9
2.1 Normative references . 9
2.2 Informative references . 9
3 Definition of terms, symbols and abbreviations . 13
3.1 Terms . 13
3.2 Symbols . 14
3.3 Abbreviations . 14
4 Platforms Interoperability in the context of IoT . 17
4.1 A global approach to IoT Systems . 17
4.1.1 Major characteristics of IoT systems . 17
4.1.2 The need for an "IoT-centric" view . 18
4.1.2.1 Introduction . 18
4.1.2.2 Roles . 18
4.1.2.3 Reference Architecture(s) . 18
4.1.2.4 Guidelines . 18
4.2 Main objectives of the present document . 18
4.3 Purpose and target group . 19
4.4 Content of the present document . 19
5 The IoT Platforms Landscape . 19
5.1 A framework for IoT Platforms . 19
5.1.1 Expectations and definition. 19
5.1.2 Challenges. 20
5.1.2.1 Flexibility, versatility . 20
5.1.2.2 Semantic Interoperability . 21
5.1.2.3 Flexible deployment models . 21
5.1.2.4 Open and efficient implementations. 22
5.1.2.5 Non-functional properties . 22
5.1.2.6 Security . 22
5.1.2.7 Privacy and data confidentiality . 22
5.1.2.7 Integration with legacy . 22
5.2 An IoT Platforms Landscape . 23
5.2.1 Fragmentation and lack of maturity . 23
5.2.2 A typology of platforms . 23
5.2.2.1 Main dimensions for platform analysis . 23
5.2.2.2 Scope and breadth . 23
5.2.2.3 Openness . 24
5.2.2.4 Origin and governance . 24
5.2.2.5 Ecosystem . 26
5.2.2.6 Maturity . 26
5.2.2.7 A classification of Platforms . 27
5.2.3 Finding a way in the jungle of platforms . 28
5.2.3.1 Introduction . 28
5.2.3.2 Platforms identified by UNIFY-IoT and the IoT-EPI . 28
5.2.3.3 Platforms in the IoT Large Scale Pilots. 28
5.2.3.4 Emerging approaches: Marketplaces and APIs . 30
5.3 Standardized IoT Platforms . 31
ETSI
4 ETSI TR 103 536 V1.1.1 (2019-12)
5.3.1 Characterization of Standardized IoT Platforms . 31
5.3.2 oneM2M . 31
5.3.2.1 Scope . 31
5.3.2.2 Architecture . 32
5.3.2.3 Interoperability and other aspects . 33
5.3.3 The OCF Platform . 34
5.3.3.1 The Ecosystem . 34
5.3.3.2 The Interoperability . 34
5.3.3.3 The Architecture . 34
5.3.4 The Apache Platform . 35
5.3.4.1 The Ecosystem . 35
5.3.4.2 Some elements of the platform. 36
5.3.5 Point solutions and the challenge of integration . 37
5.3.5.1 Fitting point solutions in global platforms . 37
5.3.5.2 Stand-alone or cloud-based solutions: two examples . 37
5.3.5.3 The role of integration . 38
6 Dealing with Interoperability . 38
6.1 Strategic Approaches to Interoperability . 38
6.2 Technical Approaches to Interoperability . 39
6.2.1 A program for evolution . 39
6.2.2 The Internet of Things (IoT): The basic objectives of IoT platforms . 40
6.2.3 The WoT: a step towards interoperability of IoT platforms . 40
6.2.4 The SWoT: The foundations for semantic interoperability of IoT platforms . 40
6.3 Interoperability Frameworks . 40
6.3.1 The AIOTI Reference Framework . 40
6.3.2 Other Interoperability Frameworks . 41
6.3.3 Interoperability examples of use-cases . 42
6.4 The challenge of IoT Deployment . 42
6.4.1 Key technologies and design requirements . 42
6.4.2 Interoperability in Smart Cities . 43
6.5 Criteria for Interoperability . 43
7 The case of Industrial IoT . 45
7.1 The challenges of Industrial IoT . 45
7.1.1 The role of Industrial IoT in Smart Manufacturing . 45
7.1.1.1 Smart Manufacturing . 45
7.1.1.2 Industrial IoT. 46
7.1.2 IIoT: a major segment of the IoT with significant specificities . 47
7.1.2.1 A major business segment . 47
7.1.2.2 Differences with traditional Operational Technology (OT) . 47
7.1.2.3 Differences with consumer IoT . 47
7.1.3 Expected Benefits of IIoT . 48
7.1.4 Challenges and barriers to, and strategies for the adoption of IIoT . 50
7.1.4.1 The current situation: A Progressive Adoption . 50
7.1.4.2 On the importance of legacy: Greenfield vs Brownfield . 50
7.1.4.3 Technical barriers to adoption . 50
7.1.4.4 Strategic choices and their impact on platforms . 51
7.2 Using Standardized Platforms in IIoT . 52
7.2.1 Technical aspects . 52
7.2.2 Connectivity . 52
7.2.2.1 The importance of legacy . 52
7.2.2.2 Greenfield: starting from scratch . 52
7.2.2.3 Brownfield: integrating (with) legacy . 53
7.2.3 Interoperability and the role of Semantics . 54
7.2.4 IoT Virtualization and the role of Cloud . 55
7.2.4.1 IoT Virtualization . 55
7.2.4.2 Virtualization in the context of IIoT . 56
7.2.5 Data Management and Analysis . 56
7.2.6 Business Processes and Enterprise view . 57
7.2.6.1 The need for Vertical Integration . 57
7.2.6.2 The Impact of IIoT . 58
ETSI
5 ETSI TR 103 536 V1.1.1 (2019-12)
7.2.7 Software Development . 59
7.3 Platform adoption: proprietary or open/standardized . 60
7.3.1 Proprietary platforms . 60
7.3.1.1 Benefits and limits of proprietary platforms . 60
7.3.1.2 Issues in coupling proprietary platforms and open/standardized platforms . 60
7.3.2 A review of IIoT Platforms . 61
7.3.2.1 Introduction . 61
7.3.2.2 Standardized Platforms . 61
7.3.2.3 Open Source Platforms . 61
7.3.2.4 Industry Groups Platforms . 61
7.3.2.5 Proprietary Platforms . 63
7.3.3 Conclusions. 64
8 Conclusions . 64
8.1 Lessons learned . 64
8.2 Guidelines and Recommendations . 65
8.2.1 Introduction. 65
8.2.2 Strategy Recommendations . 66
8.2.3 Technical Recommendations . 68
8.2.4 Recommendations to oneM2M . 68
Annex A: IoT Platforms identified by UNIFY-IoT and IoT-EPI . 70
A.1 The platforms identified by UNIFY-IoT . 70
A.2 The platforms in the IoT-EPI projects . 70
History . 72

ETSI
6 ETSI TR 103 536 V1.1.1 (2019-12)
Figures
Figure 1: AIOTI 3-Layer Functional Model.20
Figure 2: The Three IoT Software Stacks .21
Figure 3: Functional components of ACTIVAGE IoT platforms .29
Figure 4: The platforms across the AUTOPILOT Use Cases .30
Figure 5: oneM2M high level architecture .32
Figure 6: oneM2M functional architecture .33
Figure 7: Building Blocks of OCF architecture .35
Figure 8: The example of the Apache Hadoop ecosystem .35
Figure 9: AIOTI HLA Functional Model .41
Figure 10: Synthetic view of interoperability dimensions .44
Figure 11: Manufacturing Pyramid .46
Figure 12: Cyber-Physical Production Systems .46
Figure 13: The potential of Cloud-Native Infrastructures .55
Figure 14: An HLA for IoT Virtualization .56
Figure 15: OPC-UA multiple queries support .59
Figure 16: OPC-UA support for Information Models .62
Figure 17: OPC UA Companion Specifications - The example of EUROMAP .63
Figure 18: Risk of double work and approaches in the Companion Specifications .63
Figure 19: oneM2M OPC-UA Interworking and Functional Architecture with IPE .69
Figure A.1: UNIFY-IoT: Leading IoT Platforms selected for in-depth analysis.70

Tables
Table 1: A classification of platforms .27
Table 2: Examples of Apache Software Components .36
Table 3: Expected benefits of Industrial IoT .48
Table 4: IIoT Platform selection scenarios .51
Table 5: Scenarios for Control Systems modifications .53
Table 6: Functional Level of Activities .58
Table A.1: Platforms used by the IoT EPI Projects .71

ETSI
7 ETSI TR 103 536 V1.1.1 (2019-12)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Report (TR) has been produced by ETSI Technical Committee Smart Machine-to-Machine
communications (SmartM2M).
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.
Introduction
The initial project of Machine-to-Machine (M2M) communications was addressing the possibility for a device to
interact with other devices (point-to-point or via gateways). This project has been handled at the very start by a variety
of specialized (often sector-specific) platforms and solutions. Soon, it has been clear that this approach was bearing a
strong risk of fragmentation with great difficulty in ensuring interoperability of such platforms when required. The
Standard Development Organizations (SDOs) and Standard Setting Organizations (SSOs) have started to address the
question of the M2M communications and have developed a number of approaches focusing on interoperability, in
particular at the network level. Amongst the standards developed, some have addressed the possibility to serve as a
basis for the development of platforms that could use these standards to deal with interoperability in a generic manner,
across a variety of business sectors, with a variety of possible implementations. Such "standardized platforms" are
relying on reference architectures, interoperability stacks addressing different layers, generic protocol adaptors, etc.
Gradually, the focus of the industry has shifted to the design and development of IoT systems with the purpose to offer
full-fledge systems dealing with a vast number of devices (with various computing and interaction capabilities) and
potentially integrating these devices into larger systems implementing often complex business processes. This has been
enabled by the emergence of IoT devices with higher computing capacity and the possibility of producing massive
amounts of data that will be collected, transformed, stored and managed by larger (non IoT specific) information
systems which transform it into qualitative information to trigger useful actions.
ETSI
8 ETSI TR 103 536 V1.1.1 (2019-12)
This incorporation of IoT with Big Data is one new challenge for IoT platforms, a significant one but not the only one.
Another example is the use of Virtualization technologies coming from Cloud Computing that wants to get the benefits
of Cloud in terms of flexibility and cost effectiveness. In the case of Big Data or Virtualization, the role of standards is
challenged by new approaches based on the usage of Open Source Software (OSS) components. The "standardized IoT
platforms" will have to address the challenges and probably not all of the existing ones will be able to make it.
An important business sector for the validation of the approach of generic standardized platforms is Industrial IoT. The
need for the Industry to have a holistic approach to the use of Information Technologies to foster innovation and
competitiveness has been addressed by a variety of initiatives coming from business sectors (such as Industrie 4.0 in
Germany and similar national initiatives) or from the European Commission (such as Digitizing European Industry -
DEI). The approaches taken will have to combine the benefits of existing technology solutions (including established
standards) with the flexibility offered by new approaches such as Big Data, Virtualization, or Semantic Interoperability.
Two main challenges have to be addressed by IoT standardization (organizations) and by the "standardized" platforms
(an example is oneM2M, see ETSI TS 118 101 [i.13] that some of these organizations are developing:
• The "advanced technology" challenge posed by e.g. the incorporation of Big Data or Virtualization.
• The "business sector" challenge with the question of which level of genericity can be provided in support of
the development of large IoT systems for Smart Cities, Intelligent Transport or Industrial IoT.
• The "standards" challenge posed by the role of emerging approaches such as Open Source.
The example of Industrial IoT is addressed in detail, based on considerations and questions such as the following:
• Considering that Industrial IoT is a business sector in which the Return on Investment (RoI) of IoT is expected
to be positive in the short/medium period, how is it possible to foster the adoption of IoT standards and
standardized IoT platforms in this particular sector.
• The adoption of standards and platforms for interoperability should benefit not only to the technology
providers but, first and foremost, to those who purchase and use these solutions, in particular the SMEs who
do not always have the technical knowledge and the leverage available to large businesses.
The present document addresses these questions first by carefully outlining the nature, the role of IoT platforms and
proposing elements for the identification of the most relevant ones. It also addresses detailed examples such as
Industrial IoT to outline the challenges posed to generic IoT platforms.

ETSI
9 ETSI TR 103 536 V1.1.1 (2019-12)
1 Scope
1.1 Context for the present document
The design, development and deployment of - potentially large - IoT systems require to address a number of topics -
such as security, interoperability or privacy - that are related and should be treated in a concerted manner. In this
context, several Technical Reports have been developed that each address a specific facet of IoT systems.
In order to provide a global a coherent view of all the topics addressed, a common approach has been outlined across
the Technical Reports concerned with the objective to ensure that the requirements and specificities of the IoT systems
are properly addressed and that the overall results are coherent and complementary.
The present document has been built with this common approach also applied in all of the other documents listed
below:
• ETSI TR 103 533 [i.1].
• ETSI TR 103 534 [i.2].
• ETSI TR 103 535 [i.3].
• ETSI TR 103 537 [i.4].
• ETSI TR 103 591 [i.5].
1.2 Scope of the present document
The present document is addressing the issues related to the interoperability and interworking of IoT platforms, in
particular standardized IoT platforms, and how the way they are handled can foster their adoption by the IoT
community. The following points are discussed:
• What is a platform and what are the relevant ones for IoT?
• What are the main requirements of Interoperability and Interworking?
• How these requirements are taken into account by typical platforms.
• How those elements are taken into account in specific sectors such as Industrial IoT.
• Which recommendations can be made for an effective selection and usage?
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.
ETSI
10 ETSI TR 103 536 V1.1.1 (2019-12)
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 533 (V1.1.1): "SmartM2M; Security; Standards Landscape and best practices".
[i.2] ETSI TR 103 534 (Parts 1 and 2) (V1.1.1): "SmartM2M; Teaching material".
[i.3] ETSI TR 103 535 (V1.1.1): "SmartM2M; Guidelines for using semantic interoperability in the
industry".
TM
[i.4] ETSI TR 103 537 (V1.1.1): "SmartM2M; Plugtests preparation on Semantic Interoperability".
[i.5] ETSI TR 103 591 (V1.1.1): "SmartM2M; Privacy study report; Standards Landscape and best
practices".
[i.6] White Paper: "IoT Platforms Interoperability Approaches", IoT-EPI Platform Interoperability Task
Force, 2017.
[i.7] AIOTI: "IoT LSP Standards Framework Concepts", Release 2.8, White Paper, 2017.
[i.8] AIOTI: "High Level Architecture (HLA)", Release 4.0, June 2018.
[i.9] "Semantic Interoperability", Release 2.0, AIOTI, 2015.
NOTE: Two new AIOTI Joint White Papers on Semantic Interoperability have been issued by AIOTI on 22
October 2019. See https://aioti.eu/aioti-iso-iec-jtc1-etsi-onem2m-and-w3c-collaborate-on-two-joint-
white-papers-on-semantic-interoperability-targeting-developers-and-standardization-engineers/.
[i.10] UNIFY-IoT Deliverable D03.01: "Report on IoT platform activities", 2017.
NOTE: Available at http://www.internet-of-things-research.eu/pdf/D03_01_WP03_H2020_UNIFY-
IoT_Final.pdf.
[i.11] UNIFY-IoT Deliverable D03.02: "Analysis on IoT Platforms Adoption Activities", 2017.
NOTE: Available at http://www.internet-of-things-research.eu/pdf/D03_02_WP03_H2020_UNIFY-
IoT_Final.pdf.
[i.12] UNIFY-IoT Deliverable D05.01:"Interoperable IoT Platforms Standards Framework", 2017.
[i.13] ETSI TS 118 101 (V2.10.0): "Functional Architecture (oneM2M TS-0001 version 2.10.0
Release 2)".
[i.14] ETSI TS 118 102 (V2.7.1): "oneM2M Requirements (oneM2M TS-0002 version 2.7.1
Release 2)".
[i.15] oneM2M-TS-0012 (2018): "Base Ontology".
[i.16] oneM2M-TS-0023 (2018): "Home Appliances Information Model and Mapping".
[i.17] ETSI TS 118 121 (V2.0.0): "oneM2M; oneM2M and AllJoyn® Interworking (oneM2M TS-0021
version 2.0.0 Release 2)".
[i.18] oneM2M-TS-0014 (2017): "LWM2M Interworking".
[i.19] oneM2M-TS-0024 (2017): "OIC Interworking".
[i.20] oneM2M-TS-0033 (2017): "Interworking Framework".
[i.21] ETSI TR 103 527 (V1.1.1):"SmartM2M; Virtualized IoT Architectures with Cloud Back-ends".
[i.22] ETSI TR 103 528 (V1.1.1): "SmartM2M; Landscape for open source and standards for cloud
native software applicable for a Virtualized IoT service layer".
[i.23] ETSI TR 103 529 (V1.1.1): "SmartM2M; IoT over Cloud back-ends: A Proof of Concept".
ETSI
11 ETSI TR 103 536 V1.1.1 (2019-12)
[i.24] ETSI TS 103 378 (V1.1.1): "Smart Body Area Networks (SmartBAN) Unified data representation
formats, semantic and open data model".
[i.25] ACTIVAGE Deliverable D3.1: "Report on IoT European Platforms". .
NOTE: Available at
https://www.activageproject.eu/docs/downloads/activage_public_deliverables/ACTIVAGE_D3.1_M3_Re
port%20on%20IoT%20European%20Platforms_V1.0.pdf.
[i.26] T. Berners-Lee, J. Hendler and O. Lassila: "The Semantic Web" Scientific American, 2001, vol.
284, no 5, p. 28-37.
[i.27] Recommendation ITU-T Y.2063: "Framework of the web of things".
NOTE: Available at https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-Y.2063-201207-I!!PDF-
E&type=items.
[i.28] Recommendation ITU-T Y.2060: "Overview of the web of things".
[i.29] EUROMAP 83: "OPC UA interfaces for plastics and rubber machinery - General Type
definitions".
[i.30] G. Hatzivasilis, I. Askoxylakis, G. Alexandris, G. Spanoudakis, et al.: "The Interoperability of
Things: Interoperable solutions as an enabler for IoT and Web 3.0", Conference: IEEE
International Workshop on Computer-Aided Modeling Analysis and Design of Communication
Links and Networks (CAMAD) 2018, Barcelona, Spain. Project: SEMIoTICS, September 2018
DOI:10.1109/CAMAD.2018.8514952.
[i.31] Linked Open Vocabularies for Internet of Things (LOV4IoT).
NOTE: Available at http://lov4iot.appspot.com/?p=ontologies.
[i.32] ETSI TS 103 264 (V1.1.1): "SmartM2M; Smart Appliances; Reference Ontology and oneM2M
Mapping".
NOTE: Available at
http://www.etsi.org/deliver/etsi_ts/103200_103299/103264/01.01.01_60/ts_103264v010101p.pdf.
[i.33] European Research Cluster on the Internet of Things: "Internet of Things. IoT Semantic
Interoperability: Research Challenges, Best Practices, Recommendations and Next Steps", March
2015.
NOTE: Available at http://www.internet-of-things-
research.eu/pdf/IERC_Position_Paper_IoT_Semantic_Interoperability_Final.pdf.
[i.34] Sarogini Grace Pease, Paul P. Conway and Andrew A. West: "Hybrid ToF and RSSI real-time
semantic tracking with an adaptive industrial internet of things architecture", Journal of Network
and Computer Applications, 99(August 2016): 98-109, 2017. ISSN 10958592.
doi:10.1016/j.jnca.2017.10.010.
[i.35] Paul Murdock et al.: "Semantic Interoperability for the Web of Things", 2016. .
NOTE: See note in [i.9].
[i.36] ETSI GS CIM 009: "Context Information Management (CIM); NGSI-LD API".
[i.37] Mahdi Ben Alaya, Khalil Drira, Ghada Gharbi: "Semantic-aware IoT platforms", IEEE
AIMS2017. Honolulu Jul 2017.
[i.38] ETSI TS 102 690 (V1.2.1): "Machine-to-Machine communications (M2M); Functional
architecture".
[i.39] Web of Things Working Group.
NOTE: Available at https://www.w3.org/WoT/WG.
ETSI
12 ETSI TR 103 536 V1.1.1 (2019-12)
[i.40] European Innovation Partnership for Smart Cities & Communities, EIP-SCC: "6-Nations Smart
Cities Forum Smart Cities National Market Blueprint", Version 3, March 2016.
NOTE: Available at https://eu-smartcities.eu/sites/default/files/2018-09/6-Nations SC BLUEPRINT v3.pdf.
[i.41] AIOTI: "Smart City LSP Recommendations Report", AIOTI WG08 - Smart Cities, 2015.
NOTE: Available at https://aioti.eu/wp-content/uploads/2017/03/AIOTIWG08Report2015-Smart-Cities.pdf.
[i.42] Thomas Casey, Ville Valovirta, Immo Heino, Janne Porkka, Ville Kotovirta, Sampsa Ruutu:
"Interoperability Environment for Smart Cities (InterCity) - Report of Phase 2 -Smart City
Interoperability Environment Concept", September 2016.
NOTE: Available at https://www.vtt.fi/sites/InterCity/en/Documents/InterCity_Report_Phase_2_FINAL.pdf.
[i.43] Omer Ozdemir, José Manuel Cantera, Martino Maggio, Nicola Muratore, Francesco Arigliano,
Eunah Kim, Luis Muñoz, Ignacio Elicegui Maestro, Andrea Gaglione and Angelo Capossele:
"Reference Architecture for IoT Enabled Smart Cities SynchroniCity: Delivering an IoT enabled
Digital Single Market for Europe and Beyond".
[i.44] The British Standards Institution, PAS 182:2014: "Smart city concept model - Guide to
establishing a model for data interoperability".
[i.45] Eurostat: "Urban Europe - statistics on cities, towns and suburbs - executive summary".
NOTE: Available at https://ec.europa.eu/eurostat/statistics-explained/index.php/Urban_Europe_-
_statistics_on_cities,_towns_and_suburbs_-_executive_summary#People_and_life_in_cities.
[i.46] IEC 62264 (Parts 1 to 6): "Enterprise-control system integration".
[i.47] Industrial Internet Consortium: "A Practical Way to
...