1. IoT in ODL
Lionel Florit, Principal Engineer, ODL ID lflorit
John Burns, Principal Engineer, ODL ID Jburns
Yunchul Choi , ETRI
Kevin Blomseth, Echelon, ODL ID kblomseth
Thursday, December 4, 14

2. The problem we want to solve
1 Application – 1 Device
Any Application – Any Device
ODL IoT Data Store G G G G
In M2M, information is originated from a device and consumed by an application.
In IoT, some information is originated from any devices and is queried by any applications
Application aware of device specifics.
Data formats & semantics
Application dependency on device protocols.
Protocol proliferation compounds the problem.
Applications must coordinate to access data from same device.

3. Cisco Live 2014
4/16/2017
oneM2M
Background
Partnership project founded by 7 SDOs to minimize standards fragmentation
USA: TIA, ATSI
Japan: ARIB, TTC
China: CCSA
Europe: ETSI
Korea: TTA
Focus on M2M horizontal common services which may be offered by M2M Service Providers across multiple verticals.
Founders agreed to transfer & stop their own overlapping M2M service layer work.
Established July 2012

4. Underlying Network Services
oneM2M
Scope
Applications
Common Services Entity (CSE)
Data Exchange
Storing & sharing data between apps; event notification
Remote Device Management
Configuration & Diagnostics functions
Security & Access control
Access to data: Who, what, when, why
Connectivity Handling
Efficient, reliable, scalable use of underlying network
Reference point
Reference point
Other common services
Common Services
Reference point
oneM2M scope
Underlying Network Services
Underlying Network provides value added services to the CSEs. Such as QoS, device management, location services and device triggering.

5. oneM2M Common Service Functions

6. oneM2M Functional Architecture
Application Entity (AE): provides Application logic
Common Services Entity (CSE): sets of "service functions”
Infrastructure nodes ~ servers
Middle Nodes ~ gateways
Application Service Nodes: smart oneM2M devices
Application Dedicated Nodes: dumb oneM2M devices
Non-oneM2M devices
Mca reference point: communication flows between AE & CSE
Mcc reference point: communication flows between two CSEs
Mcn reference point: communication flows between CSE & Underlying Network Services Entity (NSE)
Mcc' reference point: goal to be as similar as possible to Mcc reference point - some differences anticipated

7. ... Controller OneM2M Core Other IOT Middleware Other IoT Protocols
Validates queries
Authorize
Resource tree ops and maintenance
Observer
Notify
Other IDM Instance
Other IDM Instance
Device Manager
Device Manager
Device
Device
Application
Application
Other IOTDM Instance
Device Manager
Device
Application
Controller
OneM2M Core
Other IOT Middleware
...
Federation
Other IoT Protocols
HTTP
MQTT
COAP
Security Manager
RPC Dispatch
MD-SAL
OneM2M
DataStore
Other IOT
DataStores
Implements oneM2M JSON ReST API
Translate to internal RPCs
Initiate outbound calls
Resources Tree lives here

8. Thank You

9. Move to proposal