Download as PDF, PPTX
Uploaded byNicolas Damour
oneM2M Partnership Project
The document discusses oneM2M, an organization with over 200 member organizations that specifies and promotes a common service layer for M2M communication. It holds 6 physical meetings per year with around 100 attendees to produce technical reports and specifications. Release 1 was published in 2015 containing 10 technical specifications and 5 technical reports. The common service layer provides common functions across different application domains like home, automotive, health, and energy.
More Related Content
Similar to oneM2M Partnership Project
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
oneM2M Partnership Project
- 1. © 2015 oneM2M1 Over 200 member organizations in oneM2M oneM2M Partnership Project
- 2. © 2015 oneM2M2 Purpose To specify and promote an M2M Common Service Layer Work Six physical 1-week meetings per year with ~100 attendees 200+ documents produced and discussed at each meeting 3800 docs in 2013 4400 docs in 2014 Deliverables Technical Reports (TRs) and Technical Specifications (TSs) Release 1 published in January 2015 – 10 TSs + 5 TRs Work on Release 2 just started (2016?) Purpose, Work & Deliverables
- 3. © 2015 oneM2M3 Home Energy HealthAutomotive Communication Devices & Hardware Communication Technologies & Protocols Automotive Application Health Application Energy Application Home Application Communication Networks The Common Service Layer Common Service Layer Common functions applicable to different application domains
- 4. © 2015 oneM2M4 Registration Group Management SecurityDiscovery Data Management & Repository Application & Service Management Device Management Subscription & Notification Communication Management Service Charging & Accounting Location Network Service Exposure Common Service Functions
- 5. © 2015 oneM2M5 Underlying Network Underlying Network CSE AE NSE CSE AE NSE CSE AE NSENSE Device Gateway Server Application Layer Service Layer Network Layer Mca Mcn Mca Mca McnMcnMcnMcc Mcc Entities AE (Application Entity), CSE (Common Services Entity) and NSE (Network Services Entity) Reference Point One or more interfaces - Mca, Mcn, Mcc and Mcc’ Technical View CSE Mcc’ Other Server EXAMPLE REQUEST GET http://provider.net/home/temperature/la HTTP/1.1 Host: provider.net X-Orig: /CSE-1234/WeatherApp42 X-M2M-RI: 56398096 Accept: application/vnd.onem2m-res+json EXAMPLE RESPONSE HTTP/1.1 200 OK X-M2M-RI: 56398096 Content-Type: application/vnd.onem2m-res+json Content-Length: 94 {"ri":"28375964","cnf":"application/json:0", "con":"{'timestamp':1413405177000,'value':25.32}"}
- 6. © 2015 oneM2M6 Standards Collaboration