Download to read offline
![© 2019 oneM2M
oneM2M Partnership Project
3
founded1 July, 24th 2012
TP#1: Sep 24th-29th 2012
[1] Partnership Agreement V 2.0 (Approved March 2013)
Release 2 transposition
ITU-T SG20 Y.4500.x
Partner transpositions
De jure Standard
“collaborate on standard”
focus on interoperability
“compete in implementation”
www.oneM2M.org
All documents and specifications are publically available
=> Reuse e.g.
Join forces
=> reduce fragmentation
HGI
Almost 200 member organizations in oneM2M](https://image.slidesharecdn.com/industryday-2019-0001-onem2moverview-240216110935-b309131f/85/Industry_Day-2019-0001-oneM2M_Overview-pptx-3-320.jpg)
![© 2019 oneM2M
TS 0001: Functional Architecture
TS 0002: Requirements
TS 0003: Security Solutions
TS 0004: Service Layer Core Protocol
TS 0005: Management Enablement (OMA)
TS 0006: Management Enablement (BBF)
TS 0007: Service Components
TS 0009: HTTP Protocol Binding
TS 0010: MQTT Protocol Binding
TS 0011: Common Terminology
TS 0012: oneM2M Base Ontology
TS 0014: LWM2M Interworking
TS 0015: Testing Framework
TS 0020: WebSocket Protocol Binding
TS 0021: oneM2M and AllJoyn Interworking
TS 0023: Home Appliances Information Model and Mapping
TS 0024: OIC Interworking
TR 0001: Use Cases Collection
TR 0007: Study of Abstraction and Semantic Enablements
TR 0008: Security
TR 0012: oneM2M End-to-End security and Group Authentication
TR 0016: Study of Authorization Architecture for Supporting Heterogeneous Access Control Policies
TR 0017: Home Domain Abstract Information Model
TR 0018: Industrial Domain Enablement
TR 0022: Continuation and Integration of HGI Smart Home Activities
TR 0024: 3GPP Release 13 Interworking
TS-0032 – MAF and MEF Interface Specification
TR-0025 Application developer guide
TR-0034 CoAP binding and long polling for temp. monit.
TR-0035 Device management use case
TR-0037 Smart farm example using MQTT binding
TR-0039 Developer guide-SDT-based implementation
TR-0045 Implementing semantics
Release
1
Release
2
Release
2A
oneM2M Releases and Specifications
For details see also
[1] ADM-0008-Release 1 Control Document
[2] ADM-0011-Release 2 Control Document
[3] ADM-0012-Release 2A Control Document](https://image.slidesharecdn.com/industryday-2019-0001-onem2moverview-240216110935-b309131f/85/Industry_Day-2019-0001-oneM2M_Overview-pptx-25-320.jpg)
Industry_Day-2019-0001-oneM2M_Overview.pptx
- 1. oneM2M Overview Roland Hechwartner,oneM2M TP Chair oneM2M Industry Day IIIT, Hyderabad 25 September 2019 1
- 2. © 2019 oneM2M Agenda– oneM2M @ Industry Day •oneM2M Overview – this presentation Followed by… • Do No Harm to the Network using oneM2M - oneM2M – 3GPP Interworking • oneM2M Certification • Data Semantics • oneM2M Smart Device Template - in a typical vertical industry • oneM2M in Smart Cities – Korean Smart City Initiative • C-DOT & oneM2M activities • Global oneM2M implementations - oneTransport/Bordeaux/KEPCO 2
- 3. © 2019 oneM2M oneM2MPartnership Project 3 founded1 July, 24th 2012 TP#1: Sep 24th-29th 2012 [1] Partnership Agreement V 2.0 (Approved March 2013) Release 2 transposition ITU-T SG20 Y.4500.x Partner transpositions De jure Standard “collaborate on standard” focus on interoperability “compete in implementation” www.oneM2M.org All documents and specifications are publically available => Reuse e.g. Join forces => reduce fragmentation HGI Almost 200 member organizations in oneM2M
- 4. © 2019 oneM2M4 oneM2M Structure Steering Committee Technical Plenary Finance Industry Liaison Marketing Legal Methods/Procedures Work Programme Coordination Group Methods of Work Partners Members / Partners http://onem2m.org/about-onem2m/organisation-and-structure Requirements and Domain Models System Design and Security Testing and Developers Ecosystem
- 5. © 2019 oneM2M5 oneM2M Work Process Industry Public Services Enterprise Healthcare Energy Transportation Other Residential REQUIREMENTS TS-0002 TECHNICAL SPECS TECHNICAL REPORTS Certification Program TECHNICAL SPECS TECHNICAL REPORTS TECHNICAL SPECS TECHNICAL REPORTS Interoperability Test Events
- 6. © 2019 oneM2M oneM2MBreaks Down the Silos 6 Smart Emergency Services Smart Transportation Smart Infrastructure Vertical Information Flow Vertical Information Flow Vertical Information Flow Smart Emergency Services Smart Transportation Smart Infrastructure Service Layer … … … Horizontal Information Flow
- 7. © 2019 oneM2M oneM2M isan End-to-End IoT Technology 7 Service Layer Service Layer Communication Network(s) Service Layer App App App App Non- oneM2M App Flexible Deployment Options • IoT Cloud / Enterprise • IoT Gateway • IoT Edge Device • IoT User Devices
- 8. © 2017 oneM2M ©2019 oneM2M © 2019 oneM2M oneM2M Architecture Underlying Network Underlying Network CSE AE NSE CSE AE NSE CSE AE NSE NSE Device, Sensor, Actuator Edge Device or Gateway Backend or Cloud Application Layer Service Layer Network Layer CSE Other Backend Developer API Network Interface Application Entity (AE) Provides application logic for the end-to-end M2M solutions Common Services Entity (CSE) Provides the set of "service functions" that are common to the M2M environments Network Services Entity (NSE) Provides services to the CSEs besides the pure data transport Node Logical equivalent of a physical (or possibly virtualized, especially on the server side) device Application Service Node Middle Node Infrastructure Node 8
- 9. © 2017 oneM2M ©2019 oneM2M © 2019 oneM2M oneM2M is Resource Oriented Based on REST architecture style (representational state transfer) • Access using an URI http://www.example.com/wiki/rest • Representation format: XML, JSON, BSON, … • Dependencies, hierarchy is represented by link in resource representation Based on slides provided by Thierry Monteil at the CDOT foundation Day 2019 Basic Resources • Common Service Entity (CSE) • Container (CNT) • Application Entity (AE) • Container (CNT) • Content Instance (CIN) • …. onem2m.org, TS-0001 Functional Architecture 9
- 10. © 2017 oneM2M ©2019 oneM2M © 2019 oneM2M oneM2M functions provided to applications 10 Registration Registration Group Management Security Discovery Data Management & Repository Application & Service Management Device Management Subscription & Notification Communication Management Service Charging & Accounting Location Network Service Exposure Semantics Transaction Management Service Layer Common Service Layer
- 11. © 2019 oneM2M •oneM2M complements existing proven security technologies to address IoT security challenges • oneM2M provides a common set of security capabilities to secure IoT devices and applications and prevent/ mitigate attacks • oneM2M exposes an abstracted set of security related APIs to help simplify security for IoT devices and applications 11 Registration Registration Group Management Security Discovery Data Management & Repository Application & Service Management Device Management Subscription & Notification Communicatio n Management Service Charging & Accounting Location Network Service Exposure Semantics Transaction Management Service Layer Enrollment & Provisioning Secure Communication Authorization Dynamic Authorization Privacy Policy Manager End-to-End Security oneM2M Security Framework Source: Dale Seed, oneM2M Overview 2019
- 12. © 2019 oneM2M oneM2MDevice Management Framework • oneM2M provides a common set of management capabilities to manage IoT devices, applications and the service layer • Device Management • Device Configuration (e.g. enable/ disable capabilities, provisioning) • Device Diagnostics and Monitoring (e.g. memory, battery, event logs, reboot) • Device Firmware Management • Device Topology Management (e.g. Area Network topology & characteristics) • Application & Service Layer Management • Policy Configuration • Software Management (e.g. download/ install/ activation) 12 Registration Registration Group Management Security Discovery Data Management & Repository Application & Service Management Device Management Subscription & Notification Communication Management Service Charging & Accounting Location Network Service Exposure Semantics Transaction Management Service Layer Software Configuration Software Management Device Topology Management Device Firmware Upgrade Device Diagnostics Device Configuration Source: Dale Seed, oneM2M Overview 2019
- 13. © 2019 oneM2M oneM2MInterworking Framework 13 Discovery, Security, Data Management, etc. Source: oneM2M MAS Webinar
- 14. © 2017 oneM2M ©2019 oneM2M © 2019 oneM2M oneM2M Interworking towards Domain-specific Technologies Gateway (oneM2M Middle Node) E.g. OCF, OMA LwM2M oneM2M Infrastructure - CSE oneM2M AE Application oneM2M AE Application oneM2M AE Application oneM2M CSE oneM2M AE Application Gateway (oneM2M Middle Node) Based on a slide provided by: Dr. Josef J. Blanz . ndustry Day Bangalore, September 20th 2017 oneM2M defined IPE Application KNX, Zigbee, ETSI ITS etc Network KNX, Zigbee, ETSI ITS etc App Application oneM2M CSE oneM2M IPE Application oneM2M AE Application Data Containers + Abstract Information Model Backend IPE … Interworking Proxy Entity oneM2M Release 2 & 3: • Generic IPE (Ontology-based Interworking) • IoT proximal Interworking TS-0033 14
- 15. © 2017 oneM2M ©2019 oneM2M © 2019 oneM2M oneM2M Specifications & Release 4 Current Specifications • Requirements • Functional Architecture • Security • Service Layer Protocols • Protocol Bindings e.g. HTTP, CoAP, MQTT, WebSockets • Base Ontology & Semantics • Remote Management Enablement e.g. for OMA, BBF • Vertical Domain Support e.g. Smart Home • Interworking Support e.g. LwM2M, OCF, 3GPP, OSGi • Tests & Certifications Release 4 - More Smart City & Vertical Domain Support • Smart City, e.g. Ontologies for Smart City Services • Public Warning Service Enabling • Vehicular Domain Enabling, incl. 3GPP V2X interworking • Industrial Domain Enabling, e.g. OPC-UA model mapping • Railway Domain Enabling • Interworking e.g. ZigBee, Modbus • … Release 4 - Feature Enhancement & Optimization • SDT4.0 & Data Model extension, e.g. City, Railway • Semantic Enhancement, e.g. reasoning, ontology mapping • Security Enhancement, e.g. user/data privacy • Edge & Fog Computing support, e.g. service provisioning, service pooling • System Optimizations, e.g. lightweight services, platform discovery, rule engine, users, … • 3GPP Interworking, e.g. session QoS, V2X, charging.. • Testing & Developer Guides 15
- 16. © 2019 oneM2M oneM2MTimeline 16 Industry Day 5 TP42 Hyderabad Sep 25
- 17. © 2019 oneM2M oneM2MAdoption 17 oneM2M Product Offerings oneM2M Trial Deployment oneM2M Commercial Deployment oneM2M Open Source Project oneM2M has global adoption Source: Dale Seed, oneM2M Overview 2019
- 18. © 2019 oneM2M oneM2MImplementation and Deployment Base 18 IotDM OS-IoT Industry-driven Open source implementations Regular Interop Events (6 Held from 2015-2018) Examples of Commercial implementations, Prototypes, Trials Certification Test Houses and Test Tool Vendors A vibrant and healthy ecosystem of oneM2M implementations exists! Based on slides by: Dale Seed, oneM2M Overview 2019
- 19. © 2019 oneM2M oneM2M- Common Service Layer 19 oneM2M • Open global de-jure Standard • Specifies a common set of horizontal IoT services • Interworks with existing IoT technologies • Value proposition • Simplifies the life for IoT stakeholders • Minimize development, deployment and maintenance costs • Interoperability testing and certification program • Mature and commercially deployed technology • Vendor independent => Essential building block for an IoT ecosystem Takeaways
- 20. © 2019 oneM2M Thankyou! 20
- 21. © 2019 oneM2M Backup 21 •Publicly Accessible Links • oneM2M Releases and Specifications
- 22. © 2019 oneM2M oneM2MFeature Summary by Release 22
- 23. © 2019 oneM2M PubliclyAccessible Links • Web Site • http://www.oneM2M.org • Developer Guides • http://www.onem2m.org/developer-guides • Technical Questions • http://www.onem2m.org/technical/technical-questions • Published Specifications • http://www.onem2m.org/technical/published- documents • Documents developed in oneM2M • http://www.onem2m.org/technical/latest-drafts 23 • Webinars • http://www.onem2m.org/technical/webinars • YouTube Channel • https://www.youtube.com/c/onem2morg • Events • http://www.onem2m.org/news-events/events • Certified Products • http://www.onem2mcert.com/sub/sub04_01.php
- 24. © 2019 oneM2M PubliclyAccessible Links 24 Developer Guides are now accessible via the public link: http://www.onem2m.org/developer-guides
- 25. © 2019 oneM2M TS 0001: Functional Architecture TS 0002: Requirements TS 0003: Security Solutions TS 0004: Service Layer Core Protocol TS 0005: Management Enablement (OMA) TS 0006: Management Enablement (BBF) TS 0007: Service Components TS 0009: HTTP Protocol Binding TS 0010: MQTT Protocol Binding TS 0011: Common Terminology TS 0012: oneM2M Base Ontology TS 0014: LWM2M Interworking TS 0015: Testing Framework TS 0020: WebSocket Protocol Binding TS 0021: oneM2M and AllJoyn Interworking TS 0023: Home Appliances Information Model and Mapping TS 0024: OIC Interworking TR 0001: Use Cases Collection TR 0007: Study of Abstraction and Semantic Enablements TR 0008: Security TR 0012: oneM2M End-to-End security and Group Authentication TR 0016: Study of Authorization Architecture for Supporting Heterogeneous Access Control Policies TR 0017: Home Domain Abstract Information Model TR 0018: Industrial Domain Enablement TR 0022: Continuation and Integration of HGI Smart Home Activities TR 0024: 3GPP Release 13 Interworking TS-0032 – MAF and MEF Interface Specification TR-0025 Application developer guide TR-0034 CoAP binding and long polling for temp. monit. TR-0035 Device management use case TR-0037 Smart farm example using MQTT binding TR-0039 Developer guide-SDT-based implementation TR-0045 Implementing semantics Release 1 Release 2 Release 2A oneM2M Releases and Specifications For details see also [1] ADM-0008-Release 1 Control Document [2] ADM-0011-Release 2 Control Document [3] ADM-0012-Release 2A Control Document
- 26. © 2019 oneM2M oneM2MRelease 3 Deliverables TS 0001 - Functional Architecture, V 3.13.2 TS 0002 - Requirements, V 3.1.2 TS 0003 - Security Solutions, V 3.10.2 TS 0004 - Service Layer Core Protocol, V 3.11.0 TS 0005 – Management enablement (OMA), V 3.4.2 TS 0006 – Management enablement (BBF), V 3.6.2 TS 0008 – CoAP Protocol Binding, V 3.3.1 TS 0009 – HTTP Protocol Binding, V3.2.0 TS 0010 – MQTT Protocol Binding, V 3.0.2 TS 0011 – Common Terminology, V 3.0.2 TS-0012 – Base Ontology, V 3.7.3 TS-0014 – LWM2M Interworking, V 3.1.1 TS-0016 – Secure Environment Abstraction V 3.0.2 TS-0020 – WebSocket Protocol Binding, V 3.0.1 TS-0022 – Field Device Configuration-V 3.0.1 TS-0023 – Home Appliances Information Model and Mapping, V 3.7.3 TS-0024 – OCF Interworking, V 3.2.2 TS-0026 – 3GPP Interworking V3.0.0 TS-0030 – Ontology Based Interworking V 3.0.3 TS-0031 – Feature Catalogue V 3.0.0 TS-0032 – MAF and MEF Interface Specification V 3.0.1 TS-0033 – Interworking Framework V 3.0.0 TS-0034 – Semantics Support V 3.0.0 TS-0035 – OSGi Interworking V 3.0.0 TR-0001 Use Cases Collection, V 3.1.1 TR-0026 Vehicular Domain Enablement, V 3.0.1 TR-0033 Study on Enhanced Semantic Enablement V 3.0.0 Technical Specifications Technical Reports ADM-0017 Release 3 Control Document
- 27. © 2019 oneM2M 31active Work Items* * status in ADM-0001-Work Program Management v42.0.0. Release 4 candidates marked in blue TP WIs WI-0049 - Rel-1,2 & 3 Maintenance WI-0079 - Rel-4 Small Technical Enhancements RDM WG WI-0015 - oneM2M Use Case Continuation WI-0046 – Vehicular domain enablement WI-0070 - Disaster Alert Service Enabler WI-0075 – Ind. Dom. Inf. Model Mapg. & Sem. Spt. WI-0081 - Smart Device Template 4.0 WI-0084 – SDT based Information Model and Mapping for Vert. Ind. WI-0092 - Railway Domain Enablement WI-0094- Ontologies for Smart City Services (OSCS) TDE WG WI-0054 - Developers guide series WI-0060 - Interoperability testing Release 2 WI-0078 - oneM2M API guide WI-0085 - Conformance Test Specifications Release 3 WI-0086 - Conformance Test Specifications Release 4 SDS WG WI-0053 - Enhancements on Semantic Support WI-0058 – Interworking with 3GPP networks WI-0064 - Adaptation of oneM2M for Smart City WI-0069 – Heterogen. identificat. service in oneM2M syst. WI-0071 - oneM2M and W3C Web of Things Iwk WI-0072 – Modbus interworking WI-0076 - Lightweight oneM2M Services WI-0077 - Attribute Based Access Control Policy WI-0080 - Edge and Fog Computing WI-0082 - 3GPP V2X Interworking WI-0083 - oneM2M Service Subscribers and Users WI-0088 - M2M/IoT Application and Component Configuration WI-0089 - Getting started with oneM2M WI-0090 - oneM2M and Zigbee interworking WI-0091 - oneM2M Services and Platforms Discovery WI-0093 - Action Triggering Enhancements 27
Editor's Notes
- #13 The oneM2M device management framework can manage both oneM2M and non-oneM2M based devices The oneM2M device management framework can interwork to various existing device management technologies (e.g. OMA DM, OMA LWM2M, BBF, …) oneM2M provides a common set of device management capabilities to manage IoT devices and the applications and services hosted on these devices Device Configuration (e.g. enable/ disable capabilities, provisioning) Device Diagnostics and Monitoring (e.g. memory, battery, event logs, reboot) Device Firmware Management Device Topology Management (e.g. Area Network topology & characteristics) Policy Configuration Software Management (e.g. download/ install/ activation) oneM2M exposes an abstracted set of device management related APIs to help simplify management of IoT devices