1 / 24

TAKING A LOOK INSIDE

TAKING A LOOK INSIDE. Nicolas Damour Senior Manager for Business and Innovation Development, Sierra Wireless ndamour@sierrawireless.com oneM2M www.oneM2M.org. Agenda. The Partnership Project The Common Service Layer The Technical Reports and Specifications Use Cases and Requirements

robbd
Download Presentation

TAKING A LOOK INSIDE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TAKING A LOOK INSIDE Nicolas Damour Senior Manager for Business and Innovation Development, Sierra Wireless ndamour@sierrawireless.com oneM2Mwww.oneM2M.org

  2. Agenda • The Partnership Project • The Common Service Layer • The Technical Reports and Specifications • Use Cases and Requirements • Architecture and Information Modelling • Communication Protocols • Security • Device Management & Interworking with OMA/BBF • Interworking with 3GPP/3GPP2 and with AllJoyn

  3. The Partnership Project Over 200 member organizations in oneM2M

  4. Purpose, Work & Deliverables PurposeTo specify and promote anM2M Common Service Layer Work Six physical 1-week meetings per year About 5 conference calls per week between the meetings 200+ documents produced and discussed at each meeting 3800 docs in 2013 4200 docs in 2014 so far Deliverables Technical Reports and Technical Specifications

  5. The Common Service Layer Automotive Home Energy Health AutomotiveApplication HomeApplication EnergyApplication HealthApplication

  6. The Common Service Layer Automotive Home Energy Health AutomotiveApplication HomeApplication EnergyApplication HealthApplication Communication Networks

  7. The Common Service Layer Automotive Home Energy Health AutomotiveApplication HomeApplication EnergyApplication HealthApplication Common Service LayerCommon functions applicable to different application domains Communication Devices & Hardware Communication Technologies & Protocols Communication Networks

  8. Common Service Functions Registration Discovery Security Group Management Data Management & Repository Subscription & Notification Device Management Application & Service Management Communication Management Network Service Exposure Location Service Charging & Accounting

  9. Technical Reports ArchitectureAnalysis 1 TR-0002(WI-0002) UseCases TR-0001(WI-0001) ArchitectureAnalysis 2 TR-0003(WI-0002) ProtocolAnalysisTR-0009(WI-0008) Study of Mgt Capab. EnablntTR-0006(WI-0004) Abstraction & SemanticsTR-0007(WI-0005) SecurityAnalysisTR-0008(WI-0007) Roles &Focus AreasTR-0005(WI-0003) UseCases v2 TR-0011(WI-0014) E2E Security &Group Authent. TR-0012(WI-0011) ftp://ftp.onem2m.org/Work Programme/

  10. Technical Specifications RequirementsTS-0002(WI-0001) Functional Architecture TS-0001(WI-0002) Definitions& Acronyms TS-0011(WI-0003) Service Layer Core Protocols TS-0004(WI-0009) HTTP ProtocolBindingTS-0009(WI-0013) CoAP ProtocolBindingTS-0008(WI-0012) ManagementEnablnt - OMATS-0005(WI-0010) ManagementEnablnt - BBFTS-0006(WI-0010) MQTT ProtocolBindingTS-0010(WI-0014) SecuritySolutionsTS-0003(WI-0007) ServiceComponents TS-0007(WI-0011) ftp://ftp.onem2m.org/Work Programme/

  11. Use Cases & Requirements USE CASES Energy Enterprise Healthcare Public Services Residential Other Transportation REQUIREMENTSTS-0003

  12. Example Scenario – E-Health Tech supportApplication E-HealthWeb-application Patient Blood PressureMeter Doctor Pill dispenserwith integratedcomm. gateway Bluetooth SmartNetwork CellularNetwork Scales Medicalized support M2M Platform

  13. 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 ApplicationLayer AE AE AE Underlying Network Underlying Network NetworkLayer NSE NSE NSE NSE Application Service Node Middle Node Infrastructure Node

  14. 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 ApplicationLayer AE AE AE Mca Mca Mca ServiceLayer CSE CSE CSE CSE Mcn Mcc Mcn Mcn Mcc Mcn Mcc’ Underlying Network Underlying Network NetworkLayer NSE NSE NSE NSE Application Service Node Middle Node Infrastructure Node Inf. Node

  15. Information Modelling Resource-based information model • Information is stored in the system as Resources • A given Resource can be identified with a Uniform Resource Identifier • A given Resource is of one of the defined Resource Types • The Resource Type determines the semantics of the information in the Resource • Resources can be Created, Read, Updated or Deleted to manipulate the information • Resources are organized in a tree-like structure and connected by links • Links either as the tree hierarchy or to another part or the tree

  16. Resource Types & Flows Defined resource types • The System (nodes, CSEs, AEs…): node, CSEBase, AE, mgmtObj… • M2M Service subscriptions: m2mServiceSubscriptionProfile… • Security: accessControlPolicy… • Entity groups and memberships: group, members… • Application data: container, contentInstance… • Information dispatch and flows: subscription, delivery, request, schedule… • Location services: locationPolicy… • Service charging & accounting: statsConfig, eventConfig, statsCollect… Defined communication schemes • Direct communication and subscriptions/notifications • Synchronous (blocking or non-blocking with regular polling) communications • Asynchronous (non-blocking, with callback) communications

  17. Communication Protocols Reuse IP-based existing protocols Service Layer Core Protocols TS-0004 CoAP BindingTS-0008 HTTP BindingTS-0009 MQTT BindingTS-0010 XML or JSON Content serialization HTTP Example REQUEST GET http://provider.net/home/temperature HTTP/1.1Host: provider.netFrom: //provider.net/CSE-1234/WeatherApp42X-M2M-RI: 56398096Accept: application/onem2m-resource+json RESPONSE HTTP/1.1 200 OKX-M2M-RI: 56398096Content-Type: application/onem2m-resource+jsonContent-Length: 107{"typeOfContent":"application/json","encoding":1, "content": "{'timestamp':1413405177000,'value':25.32}"}

  18. Security Reuse existing mechanisms SecuritySolutions TS-0003 EnrolmentProvisioning/Configuration of the M2M System (Devices, Applications…) Secure communicationsProtocols (TLS/DTLS), credentials and authentication (PSK/PKI/MAF) Access ControlDefined in accessControlPolicy resourcesWhich SUBJECT can perform which ACTIONSon which OBJECT under which CIRCUMSTANCES More detailsin the oneM2M webinar#3November 14th 2014

  19. Interworking – OMA & BBF Reuse existing Device Management technologies Application Entity Mca OMA DM 1.3 OMA DM 2.0 OMA LWM2M oneM2M Domain IN-CSE DM Domain BBF TR-069 BBF Server DM Server BBF CPE More detailsin the oneM2M webinar#4November 27th 2014 BBF Device DM Client

  20. Interworking – 3GPP/3GPP2 AE MTC/M2MIWF AE(App Server)(M2M App) IN-CSE(SCS)(M2M Srv) ASN-CSE GGSNP-GW MSCMMESGSNPDSN RadioAccessNetwork NSE(UE) S-GW 3GPP MTC / 3GPP2 M2MArchitecture Models

  21. Interworking – AllJoyn Thermostat Smartphone Hospital Application TV Home G/W Vital Checker Server TV Vital Checker Fridge Application in the Smartphone Vacuum Fridge

  22. Join us for the next webinar 14 November 2014 at 1PM AEDT = 2AM UTC Facing the Challengesof M2M Security and Privacy by Philip Hawkes Principal Engineerat Qualcomm Incorporated http://www.onem2m.org/btchannel.cfm

  23. Join us at theoneM2M showcase event 9 December 2014, Sophia-Antipolis, France(free of charge, but online registration is required) • OneM2M project partners, rationale and goals • OneM2M Service Layer Specification release • Showcase demos that demonstrate oneM2M “live" http://www.onem2m.org/Showcase Followed by the ETSI M2M workshop

  24. Thank You! Q&A

More Related