ONEM2M STANDARDS ACTIVITIES - IOT/M2M SERVICE LAYER - NICK NORIKAZU YAMASAKI, ONEM2M SC VICE CHAIR - WORLD WIDE WEB CONSORTIUM
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
W3C Web of Thing WG Open day 16 May 2017, Osaka
oneM2M Standards Activities
- IoT/M2M Service Layer -
Nick（Norikazu） Yamasaki, oneM2M SC Vice Chair
Tamagawa University(Consultant for KDDI)
oneM2M www.oneM2M.org
© 2017 oneM2M
Agenda
• Overview of oneM2M Partnership Project
• Standardization at IoT/M2M Service Layer
(Horizontal Platforms)
• Release 2 and Release 3 Standardizations
• oneM2M Product Certification Scheme
• oneM2M Implementations and Products
• Useful references
16-May-2017 © 2017 oneM2M
2
Agenda
• Overview of oneM2M Partnership Project
• Standardization at IoT/M2M Service Layer
(Horizontal Platforms)
• Release 2 and Release 3 Standardizations
• oneM2M Product Certification Scheme
• oneM2M Implementations and Products
• Useful references
16-May-2017 © 2017 oneM2M
3
Global Partnership Project
Over 200 member organizations in oneM2M
Partner Type 1 （Standards Development Organization）
Partner Type 2 （Vertical Players, Industry Groups）
BBF（Broadband OMA（Open New Generation Global CEN&
HGI
Forum） MobileAlliance） M2M Consortium Platform CENELEC
Merged into oneM2M 4
200+ Members Organizations
Some of the 200+ active members of oneM2M
5
Purpose & Deliverables
oneM2M Purpose
To specify and promote an
M2M Common Service Layer
oneM2M Deliverables
Technical Reports（Informative） and
Technical Specifications（Normative）
16-May-2017 © 2017 oneM2M 6
oneM2M Organization Structure
Stage 1 Stage 2 Stage 3
16-May-2017 © 2017 oneM2M
7
Work Process
Use Cases
TR-0001
Energy Enterprise Healthcare Public Services
Residential Other Transportation Industry
Requirements Stage 1
TS-0002
Stage 2 & Stage 3
Technical Specifications
Technical Reports
（Architecture, Core Protocol, Security, etc.）
16-May-2017 © 2017 oneM2M 8
Agenda
• Overview of oneM2M Partnership Project
• Standardization at M2M/IoT Service Layer
(Horizontal Platforms)
• Release 2 and Release 3 Standardizations
• oneM2M Product Certification Scheme
• oneM2M Implementations and Products
• Useful references
16-May-2017 © 2017 oneM2M
9
M2M/IoT Common Service Layer • M2M Service Layer was defined by ITU-T FG-M2M. • It is a software layer • It sits between M2M applications and communication HW/SW that provides data transport • It normally rides on top of IP • It provides functions that M2M applications across different industry segments commonly need. Those functions are exposed to Applications via developer friendly APIs. • It allows for distributed intelligence (device, gateway, cloud apps) 16-May-2017 © 2017 oneM2M 10
oneM2M Architecture Approach
Pipe (vertical) Horizontal Interoperability (based
1 Application, 1 NW,
1 (or few) type of Device
on Common Service Layer)
Point to point communications Applications share common service and network
infrastructure Multipoint communications
Business
Application
Application
Application Application Application
Common
Common Service Layer Service Layer
Communication
Network (wireline,
wireless, Powerline ..) Things
Communication Communication
Network 1 Network 2 representations
(including
Gateway IP semantics)
Gateway S
Local NW
Local NW A AA
A S S
Device
A A Device
Device
Device Device
Things S Common Service Layer
A Application
16-May-2017 © 2017 oneM2M 11M2M/IoT Architecture
Application Entity Provides application logic for the end-to-end M2M solutions
Network Services Entity 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 Server
Device Gateway
Application
Layer
AE AE AE
Management
Server
Network Underlying Underlying
NSE Network NSE NSE Network NSE
Layer
Application Service Node Middle Node Infrastructure Node
16-May-2017 © 2017 oneM2M 12oneM2M Architecture
Reference Point :One or more interfaces - Mca, Mcn, Mcc and Mcc’ (between 2 service providers)
Common Services Entity :Provides the set of "service functions" that are common to the M2M
environments
Application Entity Provides application logic for the end-to-end M2M solutions
Network Services Entity 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
Layer
AE AE AE
Mca Mca Mca
Service
CSE CSE CSE CSE
Layer
Mcn Mcc McnMcn Mcc Mcn Mcc’
Network Underlying Underlying
NSE Network NSE NSE Network NSE
Layer
Application Service Node Middle Node Infrastructure Node Inf. Node
16-May-2017 © 2017 oneM2M 13Common Service Functions（CSFs）
Group
Registration Discovery Security
Management
Data Application &
Subscription & Device
Management & Service
Notification Management
Repository Management
Network Service
Communication
Service Location Charging &
Management
Exposure Accounting
16-May-2017 © 2017 oneM2M 14oneM2M Resource Structure
Common Attributes:
n
“attribute” · resourceType
0..n · resourceID
· parentID
0..n
· expirationTime
0..n · accessControlPolicyIDs
0..n · labels
· creationTime
0..n
· lastModifiedTime
0..n · stateTag
· announceTo
0..n
· announcedAttribute
0..n
CSEBase Specific Attributes:
0..n · cseType
0..n · pointOfAccess
· CSEBase
0..n
· CSE-ID
0..n · M2M-Ext-ID
· TriggerRicipient-ID
0..n
· requestReachability
0..1 · nodeLink
16-May-2017 © 2017 oneM2M 15oneM2M Resource Example
n Common Attributes:
“attribute” · resourceType
· parentID
· expirationTime
0..n
· accessControlPolicyIDs
· creationTime
· lastModifiedTime
0..n · labels
· announceTo
· announcedAttribute
0..n Specific Attributes:
· appName
· App-ID
0..n · AE-ID
· pointOfAccess
· ontologyRef
· nodeLink
0..n
16-May-2017 © 2017 oneM2M 16Communication Protocols
Reuse IP-based existing protocols
Service Layer
Core Protocols * Release 2
TS-0004
WebSocket
CoAP Binding HTTP Binding MQTT Binding
TS-0008 TS-0009 TS-0010 Binding*
TS-0020
XML or JSON Content serialization - HTTP Example
REQUEST RESPONSE
GET /~/CSE-178/CSEBase/home/temperature HTTP/1.1 HTTP/1.1 200 OK
Host: provider.net X-M2M-RI: 56398096
X-M2M-Origin: /CSE-123/WeatherApp42 X-M2M-RSC: 2000
X-M2M-RI: 56398096 Content-Type: application/vnd.onem2m-res+json
Accept: application/json Content-Length: 101
{“m2m:cin”:[
"cnf":"application/json:0",
"con":"{'timestamp':1413405177000,'value':25.32}"]
}
16-May-2017 © 2017 oneM2M 17Agenda
• Overview of oneM2M Partnership Project
• Standardization at IoT/M2M Service Layer
(Horizontal Platforms)
• Release 2 and Release 3 Standardizations
• oneM2M Product Certification Scheme
• oneM2M Implementations and Products
• Useful references
16-May-2017 © 2017 oneM2M
18Timeline of oneM2M Key Events
Release 3
Release 1
Planned
oneM2M™ Issued
(4Q-2017)
Partnership Project (Q1-2015) Large-scale
Basic set of standards for commercializa
launch (Q3-2012) constructing a unified tion
and horizontal IoT platform
2012 2013 2014 2015 2016 2017
Interoperability
Test Event #1
(Q3-2015)
30 participating
organizations
Interoperability
Interoperability
Test Event #3
Test Event #2
(Q4-2016)
(Q2-2016) Release 2
Issued
(Q3-2016)
Industrial domain and home domain enablement, interworking framework for
different systems (e.g. AllJoyn, Lightweight M2M), security enhancements, and
semantic interoperability 19oneM2M Release 2 Features
Industrial domain Home domain
enablement enablement
• “Real-time” data • Home appliance
collection information models
• redundancy and fault • Ontologies and
tolerance mapping to existing
• enablers for analytics standards
Application developer
oneM2M APIs and guidelines
Semantic interoperability Beyond
initial release
• Base ontology, link to
domain specific oneM2M™ as generic
ontologies interworking framework
• Semantic • AllJoyn/AllSeen
descriptions • OIC
• Semantic discovery • LightWeight M2M
Dynamic authorizations (LWM2M)
and end to end security
• Device onboarding
and provisioning
20Ongoing Collaborations
SDOs
Platforms
PT1
ITU-T SG20
Merged
CLP
Interworking ＋
WoT IG
Liaison &
Collaboration PT2
Requirements
TSG SA/RAN
Collaboration
P2413
Utilization
Protocols,
WG10 OMADM LWM2M MQTT
TR-069 etc.
16-May-2017 SDT© 2017 oneM2M 21
HTTP CoAP TLS DTLS SAREFToward Release 3
• Release 3 Planning （TP-2016-0188R01-Release-3_Planning)
– Work Track 1, “Market Adoption Track” （High priority）
a. Task on Essential Corrections & Small Technical Enhancements
b. Task on development and/or enhancements of guidelines and/or TSs and best
practices documents for easier implementation and take-up of oneM2M technology
c. Task on testing
d. Task on completion of well-progressed Release-2 Work Items
– Work Track 2, “Industrial IoT and smart cities”
a. Task on reach out to IIoT （ｉｎｃｌｕｄｉｎｇ Ｖｅｈｉｃｌｅ） & smart city experts & descriptions
of deployments in IIoT/smart cities based on oneM2M
b. Task on improvement and addition of requirements for the IIoT and smart Cities
c. Task on studies on new features (targeting TRs for now)
– Work Track 3, “Forward Looking Areas”
AI, Big Data, Analytics, etc.
16-May-2017 © 2017 oneM2M 22Agenda
• Overview of oneM2M Partnership Project
• Standardization at IoT/M2M Service Layer
(Horizontal Platforms)
• Release 2 and Release 3 Standardizations
• oneM2M Product Certification Scheme
• oneM2M Implementations and Products
• Useful references
16-May-2017 © 2017 oneM2M
23Phased Approach for Certification
Initial Phase （Oct 2016 ～） Global Phase （2Q 2018? ～）
RCB(Regional Certification All the Certification Process
Body) Starts Certification will conducted under
Process. GCB(Global Certification Body).
24TTA: First Regional Certification Body
oneM2M - oneM2M CB
1st oneM2M Certification Body!
oneM2M
oneM2M
Certification Body
SC (CB)
Certi.
TP
Ad-Hoc
TST
Authorized Test Lab(ATL)
Reference : TP-2016-0295
16-May-2017 © 2017 oneM2M 25Agenda
• Overview of oneM2M Partnership Project
• Standardization at IoT/M2M Service Layer
(Horizontal Platforms)
• Release 2 and Release 3 Standardizations
• oneM2M Product Certification Scheme
• oneM2M Implementations and Products
• Useful references
16-May-2017 © 2017 oneM2M
26OSS and Implementation
Industry-driven Open Source Softwares/Platforms
OSS Open Platform
IotDM
Examples of Commercial implementations /demos
27
Source: N Damour, Sierra wirelessBusan Smart City Project/Korea
oneM2M based Service
Platform（ThingPlug）
16-May-2017 © 2017 oneM2M 28Smart City/France
16-May-2017 © 2017 oneM2M 29
29Smart Transport（oneTransport）
/Buckinghamshire Council（UK）
oneMPOWER
16-May-2017 © 2017 oneM2M 30CCSP（C-DoT* Common Service Platform）
/India
oneM2M Based
Service Platform
*Centre for Development
of Telematics
16-May-2017 © 2017 oneM2M 31World‘s First Commercial Watch
for Kids /LG Uplus（Korea）
16-May-2017 © 2017 oneM2M
32Open IoT Platform（sensinov/France） 16-May-2017 © 2017 oneM2M 33
Agenda
• Overview of oneM2M Partnership Project
• Standardization at IoT/M2M Service Layer
(Horizontal Platforms)
• Release 2 and Release 3 Standardizations
• oneM2M Product Certification Scheme
• oneM2M Implementations and Products
• Useful references
16-May-2017 © 2017 oneM2M
34Useful References
• oneM2M Published Specifications
http://www.onem2m.org/technical/published-documents
• oneM2M Deployment and Adoption Announcements
http://www.onem2m.org/news-events/news/109-iot-ecosystem-expands-significantly-with-new-global-standards-
from-onem2m
• HP-E paper - HPE Universal IoT Platform oneM2M™ and beyond
http://h41111.www4.hp.com/solutions/iot/pdf/4AA6-5470ENW.pdf
• Security Solutions and Services for the IoT
http://www.iot-today.com/main/articles/security-solutions-and-services-for-the-iot/
• oneM2M™ Executive Briefing: Solving the IoT Platform Challenge
http://www.onem2m.org/images/files/onem2m-executive-briefing_A4.pdf
• S. Korea: Master plan for Building the IoT
http://www.iotweek.kr/uploadFiles/board/KOREA-IoT(Internet of Things) Master Plan-2014.pdf
• oneTRANSPORT – large-scale, intelligent transport systems trial using
oneM2M™
http://onetransport.uk.net/
16-May-2017 © 2017 oneM2M 35Thank you for your kind attention!
16-May-2017 © 2017 oneM2M
36You can also read
