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

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)

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

• A listing of discovered gaps is targeted by this work (but not for the july 2015 timeframe)

Segmentation of IoT standards

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, protocols, application, semantic

Supported protocols

Security support

Topology: device to device, local network, wide area

IoT SDOs and alliances landscapeService & App

Consumer Market Industrial Internet

Network (connectivity???)

CPSPWG

SG16

ISO/IEC30141

AIOTI

P2413， 802.24

Source: Huawei (company names removed) – further discussion is needed on the exact position of each SDO

IoT SDOs and alliances landscape (alternative 2)

Connectivity

System/Interoperability IoTArchitecture

CommunicationInfrastructure

Devices/Things

Applications/Services

Connectivity:

- ConnectingtheThings

System/Interop

- CommonlanguageenablingThingtoThingand/orThingtoCloudinteroperability

CommunicationInfrastructure

- Sharingcommunicationneeds

IoTArchitecture

-Foracommonunderstanding

Open source initiativesService & App

Consumer Market Industrial Internet

NetworkTo be completed (Omar, Georgious)

Linux IoTDM

Wireless connectivity trends to support IoTRange (extended)

Range (low)

Device cost (high)

Bitrate (high)

WLAN

(e.g. WiFi)

Native LPWA

(e.g. LTN)

Device cost (low)

Bitrate (low)

3GPP Cellular

(GSM/LTE)

LTE enhancementsand/or CIoT

WPAN

(e.g. Zigbee)

CellularGW

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 communication protocols such as MQTT, 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.

Supported protocols:

Data: CoAP, MQTT, HTTP, OMA LWM2M

Management: OMA LWM2M, OMA DM, BBF TR069

Security support: TLS, mutual authentication, etc…

Marketing

Architecture

SystemProtocols

Test

InteropNeeds

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

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

High level architecture for the LSPs

Introduction to IoT-A

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