1. Authors list to be completed.
IoT Standards landscape and high level architecture for LSPs – AIOTI WG3 meeting 6 and 7/07/2015 Sophia Antipolis
Authors list to be completed.

2. Outline Introduction Segmentation for IoT standards
Mapping SDO work (to different segments), status of SDO work.
High level architecture for the LSPs
Gap analysis (to be addressed in further revisions of this slide set)

3. Introduction
The purpose of this slide-set is to provide an overview of IoT standards and propose a high level architecture for LSP as a basis for discussion within WG3 and with other AIOTI WGs
NB: WG3 will not specify an IoT architecture, it will reuse existing standards.
In order to understand IoT standards landscape there is a need to create a segmentation of such standards
Understanding the relevance of each SDO work and its mapping to a specific segment will help master the landscape (perceived too complex so far). AIOTI may need to focus on a subset of standards, e.g. connectivity aspects can be delt with at a later phase
Reference architecture model will be developed considering existing landscape
A listing of discovered gaps is targeted by this work (but not for the july 2015 timeframe)
Consider requirements from ISO/IEC, other SDOs? – need to select requirements in accordance to the LSPs

4. Segmentation of IoT standards

5. Introduction
The following segments are proposed to caracterize IoT related SDOs, alliances and open source initiatives work:
Type of organization: SDO, Alliance, Open source, etc.
Domain: horizontal, domain specific
Interoperability level: connectivity, transport/application protocols, application, semantic, APIs
Topology: device to device, local network, wide area
Description
Features
Openess, availability, adoption
Security support
Privacy support
Supported protocols
IPR regime (?)
Comment: we may have to adapt domain as we progress, same for topology

6. IoT SDOs and alliances landscape
Service & App
ISO/IEC
P2413，
802.24
AIOTI
Industrial Internet
Consumer Market
Marco: If this is agreed as a playground representation then the two dimensions should be in the segmentation
Omar: AIOTI is misplaced
Ovidiu: IIC does health which is consumer
Hypercat is national
NIST is national
connectivity
Source: Huawei (company names removed) – further discussion is needed on the exact position of each SDO

7. Open source initiatives
Service & App
Linux IoTDM
Industrial Internet
Consumer Market
Fiware
Ovidiu: Different level of size maturity and membership
Network
To be completed (Omar, Georgious)

8. Wireless connectivity trends to support IoT
Range (extended)
LTE enhancements and/or CIoT
Native LPWA
(e.g. LTN)
3GPP Cellular
(GSM/LTE)
Cellular GW
Device cost (low)
Bitrate (low)
Device cost (high)
Bitrate (high)
WPAN
(e.g )
WLAN
(e.g )
Range (low)
Source: Alcatel-Lucent

9. Needs
Architecture
System
Protocols
Test
Interop
oneM2M
Type of organization: SDO producing technical specification published by ETSI, ATIS, etc..
Domain: horizontal, covering a service layer between application and communication infrastructure (data collection, device management, etc.)
Interoperability level:
Protocols: oneM2M does not develop application protocols, however specifies data structures to be transported by such protocols.
Application: oneM2M defines APIs that are exposed to applications (cloud, device, gateway)
Semantic: allows to describe data according to ontologies, semantic discovery, etc. Domain specific ontologies are not specified in oneM2M, however one M2M defines mapping rules to oneM2M data strctures.
Topology: local, wide area
Description
Features: data collection, data sharing, publish subscribe, device management, security at service level, privacy via access control policy, etc.
Openess, availability, adoption: standards available for free download, initial commercial deployments, 3 open source implementations including from Linux and Eclipse
Supported protocols: CoAP, HTTP, LWM2M, OMA DM (management), BBF (management)
IPR regime: FRAND

10. Mapping SDO work (to different segments), status of SDO work.

11. SDO 1
One slide description of SDO work according to the proposed segmentation
Before we start this piece of work we must agree in the group about the segmentation

12. High level architecture for the LSPs

13. Introduction to IoT-A

14. Gap analysis (to be addressed in further revisions of this slide set)

15. Annex

16. IoT SDOs and alliances landscape (alternative 2)
Connectivity
System / Interoperability
IoT Architecture
Communication Infrastructure
Devices / Things
Applications / Services
Connectivity:
Connecting the Things
System / Interop
Common language enabling Thing to Thing and/or Thing to Cloud interoperability
Communication Infrastructure
Sharing communication needs
IoT Architecture
- For a common understanding
Useful representation, previous slide gives a quick overview.
JP: It should be aligned with the reference architecutre if we keep this slide.
Conclusion: Put in annex for now then align with the architecture
Marco: interoperability can be at different level, a layering will help better.
Add 3GPP and IETF