iot in odl lionel florit, principal engineer, [email protected], odl id [email protected]...
TRANSCRIPT
IoT in ODL
Lionel Florit, Principal Engineer, [email protected], ODL ID lfloritJohn Burns, Principal Engineer, [email protected], ODL ID JburnsYunchul Choi , [email protected], ETRIKevin Blomseth, [email protected], Echelon, ODL ID kblomseth
Thursday, December 4, 14
2
G G
The problem we want to solve
1 Application – 1 Device
G G
Any Application – Any Device
ODL IoT Data Store
3
3
oneM2MBackground
• 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.
4
4
oneM2MScope
Applications
Common Services
Underlying Network Services
Other common services
Reference point
Reference point
Reference point
oneM2M scope
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
Underlying Network provides value added services to the CSEs. Such as QoS, device management, location services and device triggering.
5
oneM2M Common Service Functions
5
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
6
7
Controller
MD-SAL OneM2MDataStore
OneM2M Core
Other IoT Protocols ...
ApplicationDeviceDevice
Manager
Security Manager
Federation
RPC Dispatch
Other IDM Instance
MQTTHTTP
ApplicationApplicationDeviceDeviceDevice
ManagerDevice Manager
Other IDM InstanceOther IOTDM Instance
COAP
Other IOT Middleware
Other IOTDataStores
Resources Tree lives here
Implements oneM2M JSON ReST
APITranslate to internal
RPCsInitiate outbound
calls
Validates queriesAuthorize
Resource tree ops and maintenance
Observer Notify
Cisco Confidential 8© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Thank You
Move to proposal