1、Geneva, Switzerland, 18 February 2014,A global Service layer platform for M2M communications,Dr. Friedbert Berens FBConsulting Sarl, Luxembourg ,ITU Workshop on the “Internet of Things - Trend and Challenges in Standardization”(Geneva, Switzerland, 18 February 2014),Mission,oneM2M is working to unif
2、y the Global M2M Community, by enabling the federation and interoperability of M2M systems, across multiple networks and topologies.,Global Partners,Scope & Objectives,To develop: Global M2M end-to-end specifications - using common use cases and architecture principles across multiple M2M applicatio
3、ns to connect M2M devices with application servers worldwide with an access independent view of end-to-end services To define: Service Layer platform with high level / detailed service architecture including: - Protocols/APIs/standard objects (open interfaces & protocols) - Interoperability, test an
4、d conformance specifications - Common use cases, terminal/module aspects - Service Layer interfaces/APIs between: Application and Service Layers Service Layer and communication functions Security and privacy aspects authentication, encryption, integrity verification, 2013 oneM2M Partners oneM2M Part
5、nership Project 4,M2M Service Layer,Middleware - supporting secure end-to-end data/control exchange between M2M devices and customer applications by providing functions for remote provisioning & activation, authentication, encryption, connectivity setup, buffering, synchronization, aggregation and d
6、evice management - software layer - sits between M2M applications and communication elements that provides data transport - normally rides on top of IP - provides commonly needed functions for M2M applications across different industry segments,Vision:,Interconnecting the Internet of Things; Connect
7、ing the Un-connected,Underlying protocols,oneM2M,Other M2M protocol,Hybrid protocol App,oneM2M protocol,Other M2M protocol App,oneM2M native App,Underlying protocol,Underlying protocol,IoT Device,IoT Device,Horizontal Platform Vision,Geneva, Switzerland, 18 February 2014,7,Pipe (vertical): 1 Applica
8、tion, 1 NW, 1 (or few) type of Device,Business Application,Device,Communication Network (mobile, fixed, Powerline ),Gateway,Horizontal (based on common Layer) Applications share common infrastructure, environments and network elements,Communication Network 1,Communication Network 2,Local NW,Device,D
9、evice,Device,Device,Common Application Infrastructure/Service layer,Gateway,IP,Business Application #1,Business Application #2,Business Application #n,oneM2M simplified Architecture,8,AE,AE,AE,CSE,CSE,CSE,M2M Applications,M2M Service layer,Underlying Transport,Mca,Mca,Mca,Mcc,Mcc,Mcn,Mcn,Mcn,Mcn,NSE
10、,NSE,Network Service Entity,oneM2M Common Service Functions,9,Ref: oneM2M TS: Functional Architecture,OneM2M architecture entities,AE: Application Entity, containing the application logic of the M2M solution like home management functions, fleet management, blood sugar monitoring CSE: Common Service
11、 Entity containing a set of common service functions (CFE) that are common to a broad range of M2M environment (verticals). This is the main part of the oneM2M specification CSF: Common Service Functions included in a CSE, CSFs can be mandatory or optional, CSF can contain sub-functions (mandatory o
12、r optional) NSE: Network Service Entity, provides network services to the CSE, like device triggering, device management support, location services. These services are related to the underlying network capabilities,10,OneM2M architecture Reference points,Mca- Reference Points: the interface point be
13、tween the AE and the CSE, the Mca point provides the M2M applications access to the common services included in the CSE. The AE and CSE my be co-located in the same physical entity or not Mcc- Reference Points: This is the reference point between two CSEs. The Mcc reference point shall allow a CSE t
14、o use the services of another CSE in order to fulfil needed functionality. Accordingly, the Mcc reference point between two CSEs shall be supported over different M2M physical entities. The services offered via the Mcc reference point are dependent on the functionality supported by the CSEs Mcn- Ref
15、erence Points: This is the reference point between a CSE and the Underlying Network Services Entity. The Mcn reference point shall allow a CSE to use the services (other than transport and connectivity services) provided by the Underlying Network Services Entity in order to fulfil the needed functio
16、nality. Mcc- Reference Point: interface between two M2M service providers, As similar as possible to the Mcc reference point. But due to the nature of inter-M2M Service Provider communications, some differences are anticipated.,11,oneM2M Organization,Steering Committee (Partners),Technical Plenary (
17、Members / Partners),Protocols WG3,Requirements WG1,Architecture WG2,Security WG4,Management, Abstraction, Semantics WG5,Legal,Methods & Processes,Method of Work,Finance,MARCOM,Work Programme,Work Areas,WG1 - Requirements Input accepted on more than 100 service requirements WG2 - Architecture Distill
18、ing service-layer architectural options WG3 - Protocols Assessing protocols for service layer, and interoperability WG4 - Security Ensuring Security and Privacy aspects are considered WG5 - Management Working on semantic library,Schedule towards Release 1,Requirements,Architecture,Protocols,Security
19、,Management, Abstraction, Semantics,Target Date: Release 1,Participation,Levels of participation: Partner Type 1 Member companies participate directly Partner Type 2 Contributes on behalf of Member companies Associate MemberJoin: http:/www.onem2m.org/join.cfm Docs: http:/www.onem2m.org/library/index.cfm News: http:/www.onem2m.org/subscribe.cfm, 2013 oneM2M Partners oneM2M Partnership Project 15,www.oneM2M.org,
