onem2m AND SMART M2M INTRODUCTION, RELEASE 2/3

Transcription

1 onem2m AND SMART M2M INTRODUCTION, RELEASE 2/3 Presenter: Omar Elloumi, onem2m TP Chair, Nokia Bell Labs and CTO group onem2m onem2m

2 Outline Introduction to onem2m role of ETSI TC SmartM2M Zoom on onem2m R2 Introduction to onem2m R onem2m 2

3 onem2m Partnership Project Over 200 member organizations in onem2m All document are publically available 2016 onem2m

4 Purpose & Deliverables Purpose To specify and promote an M2M Common Service Layer Deliverables Technical Reports and Technical Specifications 2016 onem2m 4

5 2016 onem2m 5

6 2016 onem2m 6

7 2016 onem2m 7

8 What is onem2m? Application Layer Service Layer Network Layer It is a software/middleware layer It sits between applications and underlying communication networking HW/SW It typically rides on top of IP protocol stack It provides functions that applications across different industry segments commonly need It exposes common set of functions to applications via developer friendly APIs It is integrated into devices/gateways/servers and allows distributed intelligence It hides complexity of NW usage from apps It controls when communication happens It stores and shares data It supports access control It notifies applications about events 2016 onem2m 8

9 Work Process Energy Enterprise Healthcare Public Services Residential Other Transportation Industry REQUIREMENTS TS 0002 TECHNICAL REPORTS TECHNICAL SPECS 2016 onem2m 9

10 onem2m Architecture approach Pipe (vertical): 1 Application, 1 NW, 1 (or few) type of Device Point to point communications Horizontal (based on common Layer) Applications share common service and network infrastructure Multipoint communications Business Application Application Application Application Application Common Service Layer Common Service Layer Communication Network (wireline, wireless, Powerline..) Gateway Communication Network 1 S IP Communication Network 2 Digital representations (including semantics) Gateway Local NW A A Device Local NW A Device A S Device A S Device Device Things S Common Service Layer A Application 2016 onem2m 10

11 Architecture Application Entity Network Services Entity Node Provides application logic for the end to end M2M solutions Provides services to the CSEs besides the pure data transport Logical equivalent of a physical (or possibly virtualized, especially on the server side) device Application Layer AE AE AE Network Layer NSE Underlying Network NSE NSE Underlying Network NSE Application Service Node Middle Node Infrastructure Node 2016 onem2m 11

12 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 Layer CSE CSE CSE CSE Mcn Mcc McnMcn Mcc Mcn Mcc Network Layer NSE Underlying Network NSE NSE Underlying Network NSE Application Service Node Middle Node Infrastructure Node Inf. Node 2016 onem2m 12

13 Communication Protocols Reuse IP based existing protocols NB: Interworking with field area protocols and data models (OCF, AllSeen, OMA LWM2M, Zwave, etc) Service Layer Core Protocols TS 0004 CoAP HTTP MQTT Binding WebSockets XML or JSON Content serialization HTTP Example REQUEST RESPONSE GET /~/CSE 178/CSEBase/home/erature HTTP/1.1 HTTP/ OK Host: provider.net X M2M RI: X M2M Origin: /CSE 123/WeatherApp42 X M2M RSC: 2000 X M2M RI: Content Type: application/vnd.onem2m res+json Accept: application/json Content Length: 101 { m2m:cin :[ "cnf":"application/json:0", "con":"{'timestamp': ,'value':25.32}"] } 2016 onem2m 13

14 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 2016 onem2m 14

15 Strong implementation base Industry driven Open source implementations Examples of Commercial implementations /demos IotDM 2 interop. events in 2015/2016 With 30 participating organizations and 75 engineers 2016 onem2m 15

16 Ongoing collaborations Guidelines & Ref. Arch. collaborations MQTT uses interworks with Now OCF OMADM LWM2M Uses/interworks uses interworks with HTTP CoAP TLS DTLS Protocols Platforms 2016 onem2m 16

17 An overview of onem2m Release onem2m

18 onem2m Release 2 Industrial domain enablement Time series data Semantic interoperability Base ontology Semantic discovery Semantic descriptions Advanced protocol binding WebSockets Home domain enablement Home appliance information models onem2m Beyond initial release Security Dynamic Authorization End to End Security Privacy support onem2m Application Identification Registry established onem2m interworking framework Generic interworking AllJoyn/AllSeen OIC OMA LWM2M 3GPP Rel.13 Interworking 2016 onem2m 18

19 onem2m Release 2 Time Series Data Feature 2016 onem2m

20 Time Series Data AE registration CSE AE 2 Resource Tree at CSE CSEBase AE: CSE: Application Entity Common Services Entity 2016 onem2m 20

21 Time Series Data Create Time Series Container periodicintervaltime = 30 missingdatadetect = TRUE missingdatamaxnr = 5 CSE AE 2 Resource Tree at CSE CSEBase TimeSeries AE: CSE: Application Entity Common Services Entity 2016 onem2m 21

22 Time Series Data CSE AE 2 Resource Tree at CSE CSEBase Subscribe to Time Series Container TimeSeries subscription AE: CSE: Application Entity Common Services Entity 2016 onem2m 22

23 Time Series Data 1 st time series instance Time = X 32 CSE AE 2 Resource Tree at CSE CSEBase TimeSeries subscription timeseriesinstance1 Content = 32, time= X AE: CSE: Application Entity Common Services Entity 2016 onem2m 23

24 Time Series Data 2 nd time series instance Time = X CSE AE 2 Resource Tree at CSE CSEBase TimeSeries subscription timeseriesinstance1 Content = 32, time= X timeseriesinstance2 Content = 31, time= X + 30 CSE checks and verifies 2 nd instance arrived 30 seconds after 1 st instance AE: CSE: Application Entity Common Services Entity 2016 onem2m 24

25 Time Series Data 3 rd time series instance Time = X CSE AE 2 Resource Tree at CSE CSEBase TimeSeries subscription timeseriesinstance1 Content = 32, time= X AE: CSE: Application Entity Common Services Entity timeseriesinstance2 Content = 31, time= X + 30 timeseriesinstance3 Content = 33, time= X + 60 CSE checks and verifies 3 rd instance arrived 30 seconds after 2 nd instance 2016 onem2m 25

26 Time Series Data CSE detects missing time series instance Time = X + 90 No instance! CSE Missing Data Notification missingdata = 90 AE 2 Resource Tree at CSE CSEBase TimeSeries subscription timeseriesinstance1 Content = 32, time= X timeseriesinstance2 Content = 31, time= X + 30 timeseriesinstance3 Content = 33, time= X + 60 AE: CSE: Application Entity Common Services Entity 2016 onem2m 26

27 onem2m Release 2 Semantics Features 2016 onem2m

28 Semantic Annotation Resource Tree at CSE CSEBase AE 2 CSE AE: CSE: Application Entity Common Services Entity 2016 onem2m 28

29 Semantic Annotation Resource Tree at CSE CSEBase container AE 2 AE registration and container creation CSE AE: CSE: Application Entity Common Services Entity 2016 onem2m 29

30 Semantic Annotation Resource Tree at CSE CSEBase container AE 2 A reading 32 CSE AE: CSE: Application Entity Common Services Entity 2016 onem2m 30

31 Semantic Annotation CSEBase stored in container contentinstance1 Content: 32 AE 2 32 CSE AE: CSE: Application Entity Common Services Entity 2016 onem2m 31

32 Semantic Annotation CSEBase How can AE 2 know if is a erature sensor without having prior knowledge? container contentinstance1 Content: 32 AE 2 CSE How can AE 2 know 32 is measured in Celsius or Fahrenheit? AE: CSE: Application Entity Common Services Entity 2016 onem2m 32

33 Semantic Annotation onem2m Rel 2 supports adding extra semantic information to normal resources CSEBase Semantic Annotations semanticdescriptor1 container contentinstance1 Content: 32 semanticdescriptor2 AE 2 CSE AE: CSE: Application Entity Common Services Entity 2016 onem2m 33

34 Semantic Annotation Semantic descriptors formatted as RDF Triples. RDF triples expressed using ontology vocabularies (e.g. onem2m Base Ontology, SAREF, etc) CSEBase is a Temperature Sensor islocatedin Area A semanticdescriptor1 container contentinstance1 Content: 32 semanticdescriptor2 AE 2 CSE contentinstance1 is a Temperature Reading contentinstance1 ismeasuredin Celsius AE: CSE: RDF: Application Entity Common Services Entity Resource Description Framework 2016 onem2m 34

35 Semantic Resource Discovery Use Case Find erature sensor deployed in a particular location CSEBase is a Temperature Sensor islocatedin Area A semanticdescriptor1 Located in Area A AE 3 AE 3 semanticdescriptor2 AE 3 is a Temperature Sensor AE 3 islocatedin Area B CSE AE 2 I want to find a erature sensor located in Area B Located in Area B 2016 onem2m 35

36 Semantic Resource Discovery Release 2 Semantic based Resource Discovery feature can be used CSEBase is a Temperature Sensor islocatedin Area A semanticdescriptor1 Located in Area A AE 2 AE 3 Located in Area B AE 3 semanticdescriptor2 AE 3 is a Temperature Sensor AE 3 islocatedin Area B CSE SELECT?sensor WHERE {?sensor is a Temperature Sensor?sensor islocatedin Area B } semantics filter criteria expressed using SPARQL query syntax 2016 onem2m 36

37 Semantic Resource Discovery Release 2 Semantic based Resource Discovery feature can be used CSEBase is a Temperature Sensor islocatedin Area A semanticdescriptor1 Located in Area A AE 3 semanticdescriptor2 AE 3 is a Temperature Sensor AE 3 islocatedin Area B AE 2 CSE AE 3 Located in Area B 2016 onem2m 37

38 Semantic Resource Discovery Release 2 Semantic based Resource Discovery feature can be used CSEBase semanticdescriptor1 AE 3 semanticdescriptor2 Located in Area A AE 2 CSE AE 3 Located in Area B 2016 onem2m 38

39 R2 assessment, Beyond R2 Capabilities for Consumer IoT and Enterprise IoT are largely covered by R1 and R2 We do not pretend to cover the full scope as our standards are part of a bigger picture Main focus moving forward would be to add robustness, inteop and certification, developer guidelines Feedback from initial deployments 2016 onem2m 39

40 R3 initial features New work items related to industrial IoT and Smart Cities CIoT (NB IoT, LTE M, etc.) interworking is high priority for SPs (ongoing discussions with 3GPP, GSMA, OMA) Revisited interworking framework and specifications: DDS interworking OSGi interworking OPC UA interworking Smart cities use cases and best practices for use of onem2m in Smart Cities Automotive Advanced semantics as enabler of big data and analytics SAREF extensions Home domain Etc. Forging new alliances to advance work on use cases is key: smart cities, home and building and automotive 2016 onem2m 40

41 Attributes of IoT segments Consumer IoT Constrained and battery operated devices, wearables Mostly best effort communications (over the top apps) Limited to no mobility Verticals apps, silos likely to dominate for the short/medium term Centralized Analytics Enterprise IoT Less constrained devices Medium to high mobility Tracking and identification SLA and QoS may be critical for some use cases Graviation towards horizontal platforms Industrial IoT Powerful devices (Machines) High mobility SLAs and network QoS are key Deterministic networking Granular timing and synchronization (time series) Real time / largely distributed analytics Nokia Internal Use 2016 onem2m

42 Maturity levels Industrial IoT Enterprise IoT Consumer IoT 2016 onem2m 42

43 Thank You! Q&A 2016 onem2m 43