onem2m Common Architecture for IoT interoperability

Size: px

Start display at page:

Download "onem2m Common Architecture for IoT interoperability"

Abraham Barber
6 years ago
Views:

1 onem2m Common Architecture for IoT interoperability Dr. Mahdi Ben Alaya Founder & CEO, Sensinov October 23, 2017

Biography R&D engineer at LAAS-CNRS laboratory in Toulouse, France. Ph.

Co-founder and technical manager of the open source project Eclipse OM2M.

R&D projects at LAAS-CNRS and Sensinov including ITEA2-USENET, ITEA2-A2NETS, H2020-LSP5-AUTOPILOT, ETSI-OSM,

2 Biography R&D engineer at LAAS-CNRS laboratory in Toulouse, France. Ph.D in IoT system interoperability Founder and CEO of Sensinov startup. Vice Chairman of onem2m Testing Group. Co-founder and technical manager of the open source project Eclipse OM2M. IoT tutorials in summer schools and universities worldwide including France, Taiwan, and Korea. R&D projects at LAAS-CNRS and Sensinov including ITEA2-USENET, ITEA2-A2NETS, H2020-LSP5-AUTOPILOT, ETSI-OSM, and ETSI- SAREF. Authored more than 20 refereed publications in international journals and conferences. More than 50 contributions to IoT standards. IoT Solutions Open Source Research Standards 2

The evolution of IoT Sent packages are tracked on the web Take the world

Let the things talk to each others Communication Interoperability Data

3 The evolution of IoT Sent packages are tracked on the web Take the world online Plants action a tap to water themselves. Let the things talk to each others Communication Interoperability Data Interoperability Semantic Reasoning Brochure web site All monuments are described on the web. Take the control of the world Monitor and control home appliances. Let Things become intelligent Alarm ring earlier in case of traffic or bad weather. 3

4 IoT vs M2M M2M paradigm The ability of machines to communicate with other devices without human interventions. IoT M2M M2M as an industrial environment M2M: based on industrial protocols, closed solutions. IoT: common usage applications, open solutions for mass. IoT M2M IoT M2M M2M as a subset of IoT M2M: connects devices, electronic sensors, RFID tags. IoT: connects general things, animals, peoples. Adopted M2M as the kernel of IoT definition M2M: plumbing of IoT, required connectivity for things. IoT: depends on M2M, not possible without it. 4

5 Global Internet device installed Base Forecast 33 Billion Internet Devices By 2020: Four Connected Devices For Every Person In World. 5

6 Adoption of IoT by industry Energy and utilities leading closely followed by automotive and retails. Source: The M2M adoption Barometer 2014, Vodafone 6

7 Global IoT Market opportunities IoT market opportunity will be reach 4.3 trillion USD by Source: Machina Research,

devices, Unmanageable, high costs Security

8 IoT main challenges IoT Vertical Fragmentation vendor-specific solutions, no interoperability, semantic gap. Power Management Inefficient battery lifecycles, lack of clean energy. Increasing Complexity Large number of devices, Unmanageable, high costs Security Weakness in M2M devices, privacy, fraud, cyber attacks. Network Misalignment Devices behavior differs from humans: collapse of internet infra. *M2M Communications A Systems Approach (book) 8

9 M2M world of connected services 9

Current IoT silo model is not an efficient way to communicate, it is a barrier to further development.

10 IoT market fragmentation Source: CRYSTAL project/philips The current marketplace is extremely fragmented, which has increased the R&D cost in each specific domain. Current IoT silo model is not an efficient way to communicate, it is a barrier to further development. Many vertical IoT solutions have been designed independently and separately for different applications, which impedes large-scale M2M deployment. 10

IoT cross-domain interoperability Invert the pipe Highly fragmented market with small vendor-specific applications. Reinventing the wheel: Same services developed again and again.

11 IoT cross-domain interoperability Invert the pipe Highly fragmented market with small vendor-specific applications. Reinventing the wheel: Same services developed again and again. Each silo contains its own technologies without interop. End-to-end platform: common service capabilities layer. Interoperability at the level of communications and data. Seamless interaction between heterogeneous applications and devices. 11

12 Standards landscape for IoT 143 organizations around the world are involved in M2M standardization according to the Global Standards Collaboration M2MTask Force. Industrial Consumer Retail Buildings M2M Transportation Energy Health care Security 12

13 IoT Interoperability potential impact Source: McKinsey Global Institute

14 IoT high level architecture 14

15 Standards for Wide Area Networks Standards for Wide Area Networks (3GPP, fixed NW, WiMax ): Target: protect networks against negative effects of M2M traffic (many devices, nonhuman traffic ) 15

16 Standards for M2M Area Networks Standards for Local Area Networks (ZigBee, Bluetooth, PLC, etc.) Target: foster use of LAN technology by supporting diverse ecosystem of service providers and device manufacturers. 16

17 Standards for vertical industries Standards for vertical Industries applications Target: enable interoperable, cost-efficient Solutions. 17

18 Standards for M2M service capabilities Standards for M2M Service capabilities: Target: end-to end enablement across servers, gateways, and devices. Standardized service interfaces. 18

19 onem2m: The Partnership Project 19

20 Over 200 member organizations in onem2m 20

21 onem2m organization and Structure

22 onem2m certification

23 onem2m liaisons 23

24 Purpose, Work & Deliverables Purpose To specify and promote an M2M 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 docs in 2014 Deliverables Technical Reports and Technical Specifications 24

25 Use Cases & Requirements Energy Enterprise Healthcare Public Services Residential Other Transportation Industry REQUIREMENTS TS-0002 TECHNICAL REPORTS TECHNICAL SPECS 25

26 Technical Specifications Requirements TS-0002 Functional Architecture TS-0001 Security Solutions TS-0003 Service Layer Core Protocols TS-0004 HTTP Protocol Binding TS-0009 CoAP Protocol Binding TS-0008 Management Enabl nt - OMA TS-0005 Management Enabl nt - BBF TS-0006 MQTT Protocol Binding TS-0010 Definitions & Acronyms TS-0011 Service Components TS

27 onem2m high level architecture Application Layer AE AE AE Mca Mca Mca Service Layer CSE CSE CSE CSE Mcn Mcc Mcn Mcn Mcc Mcn Mcc Network Layer NSE Underlying Network NSE NSE Underlying Network NSE Device Gateway Server Other Server Entities: AE (Application Entity), CSE (Common Services Entity) and NSE (Network Services Entity) Reference Point: One or more interfaces - Mca, Mcn, Mcc and Mcc 27

onem2m functional architecture Other MN Node Other IN Node ADN Node Non onem2m Nodes

Notification (SUB) Security (SEC) IN-AE Registration (REG) Routing Function (RF)

ASM MN Node Data Mgmt and Repository (DMR) Group Management (GMG) Communication Mgmt &

28 onem2m functional architecture Other MN Node Other IN Node ADN Node Non onem2m Nodes ADN-AE SUB SEC DMR MN-AE REG RF GMG MN-NSE MN-CSE ASM LOC CMDH Subscription and Notification (SUB) Security (SEC) IN-AE Registration (REG) Routing Function (RF) IN-CSE Application and Service Layer Mgmt (ASM) Location (LOC) SUB ASN-AE REG ASN-CSE ASM MN Node Data Mgmt and Repository (DMR) Group Management (GMG) Communication Mgmt & Delivery Handling (CMDH) ASN Node SEC DMR RF GMG LOC CMDH ADN-AE IN-NSE ASN-NSE ADN Node IN Node 28

29 OneM2M resource structure OneM2M Resource structure Resource type representation 29

30 onem2m resource types Cse BASE Access Control Policy Remote CSE Application Entity Container Content Instance Group Subscription Polling Channel Node Mgmt Object 30

onem2m resource tree example Resource Type

CIN-MEASUREMENT_3 Meter (ADN) CIN-MEASUREMENT_2

31 onem2m resource tree example Resource Type MN-CSE-HOME AE-SMART-METER CNT-DESCRIPTOR CseBase Application Entity Container Content Instance CIN-DESCRIPTION_1 CNT-DATA CIN-MEASUREMENT_3 Meter (ADN) CIN-MEASUREMENT_2 CIN-MEASUREMENT_1 Server/Cloud (IN-CSE) End user (DA) Gateway (MN-CSE) 31

Bidrectional communication between the onem2m system and a specific technology (Monitor and Control).

32 Interworking with non onem2m devices The Interworking Proxy Entity (IPE) abstracts and maps the non-onem2m data model to the onem2m resources. Bidrectional communication between the onem2m system and a specific technology (Monitor and Control). Seamless interaction between applications and devices using the onem2m Restful API. Canbus OIC CSE Others AllJoin Enocean Zigbee LORA Modbus Zwave LWM2M KNX Interworking Proxy Entity onem2m resources Non onem2m entities onem2m entities 32

33 onem2m addressing mode Unstructured address (flat, short) CSE-Relative SP-Relative Absolute CSE AE Container Structured address (hierarchical, long) CSE-Relative SP-Relative Absolute 33

34 Accessing resources in onem2m (Blocking) Blocking requests 34

35 Accessing resources in onem2m (Non blocking Synchronous) Non blocking synchronous requests 35

36 Accessing resources in onem2m (Non blocking asynchronous) Non blocking asynchronous requests 36

37 App-ID vs AE-ID App-ID uniquely defines the application running in the onem2m environment AE-ID uniquely defines the INSTANCE of the application running in the onem2m environment 37

38 App-ID Registry to avoid App-ID collision App-ID registry: uniquely identifying applications is necessary in an interconnected world 38

39 Access to App-ID Registry 39

40 Summary of release 2 & 3 features 40

41 Open source onem2m implementations Commercial & Demo (Non exhaustive) 41

42 onem2m scenarios Scenario 1 - Nodes mutual authentication and applications registration Scenario 2 - Retrieve data from smart meter Scenario 3 - Get notified when new metering data is created Scenario 4 - Get notified when new smart a meter is registered Scenario 5 - Store smart meter data remotely using announcement 42

43 Scenario 1 Nodes mutual authentication and applications registration 43

44 ASN-AE Scenario 1 IN-AE CseBase-Meter ASN-CSE CseBase-MeteringServer IN-CSE mcc Meter Device Metering Server Initial state 44

45 CseBase-Meter ASN-AE ASN-CSE Scenario 1 CseBase-MeteringServer P O S T IN-AE IN-CSE mcc Meter Device Metering Server Step 1- Registers to the Metering Server IN-CSE 45

46 ASN-AE Scenario 1 IN-AE CseBase-Meter ASN-CSE CseBase-MeteringServer IN-CSE RemoteCSE-Meter mcc POST Meter Device Metering Server Step 2- The Meter ASN-CSE registers to the Metering Server IN-CSE 46

47 ASN-AE Scenario 1 IN-AE CseBase-Meter ASN-CSE CseBase-MeteringServer IN-CSE RemoteCSE-MeteringServer RemoteCSE-Meter mcc Meter Device Metering Server Step 3- The Meter ASN-CSE Creates locally RemoteCSE-MeteringServer resource 47

48 AE-Meter CseBase-Meter P O S T ASN-AE ASN-CSE Scenario 1 CseBase-MeteringServer IN-AE IN-CSE RemoteCSE-MeteringServer RemoteCSE-Meter AE-Meter mcc Meter Device Metering Server Step 4- AE-Meter registers to the Meter ASN-CSE 48

49 Scenario 2 Retrieve data from smart meter 49

50 AE-Meter ASN-AE Scenario 2 IN-AE CseBase-Meter ASN-CSE CseBase-MeteringServer IN-CSE RemoteCSE-MeteringServer RemoteCSE-Meter AE-Meter mcc Meter Device Metering Server Initial state 50

51 AE-Meter CseBase-Meter P O S T ASN-AE ASN-CSE Scenario 2 CseBase-MeteringServer IN-AE IN-CSE RemoteCSE-MeteringServer RemoteCSE-Meter AE-Meter Container-Power mcc Meter Device Metering Server Step 1- AE-Meter Creates Container-Power sub-resource 51

52 AE-Meter CseBase-Meter P O S T ASN-AE ASN-CSE Scenario 2 CseBase-MeteringServer IN-AE IN-CSE RemoteCSE-MeteringServer RemoteCSE-Meter AE-Meter Container-Power mcc ContentInstance-Power Meter Device Metering Server Step 2- AE-Meter creates ContentInstance-Power sub-resource 52

53 AE-Meter CseBase-Meter ASN-AE ASN-CSE Scenario 2 CseBase-MeteringServer G E T IN-AE IN-CSE RemoteCSE-MeteringServer RemoteCSE-Meter AE-Meter Container-Power mcc ContentInstance-Power GET Meter Device Metering Server Step 3- retrieves the ContentInstance-Power resource 53

54 Scenario 3 Get notified when new metering data is created 54

55 AE-Meter ASN-AE Scenario 3 IN-AE CseBase-Meter ASN-CSE CseBase-MeteringServer IN-CSE RemoteCSE-MeteringServer RemoteCSE-Meter AE-Meter Container-Power mcc Meter Device Metering Server Initial state 55

56 AE-Meter CseBase-Meter ASN-AE ASN-CSE Scenario 3 CseBase-MeteringServer P O S T IN-AE IN-CSE RemoteCSE-MeteringServer RemoteCSE-Meter AE-Meter Container-Power Subscription-Power mcc POST Meter Device Metering Server Step 1- subscribes to Container-Power of AE-Meter 56

57 POST AE-Meter CseBase-Meter P O S T ASN-AE ASN-CSE Scenario 3 CseBase-MeteringServer IN-AE IN-CSE RemoteCSE-MeteringServer RemoteCSE-Meter AE-Meter Container-Power Subscription-Power ContentInstance-Power mcc POST Meter Device Metering Server Step 2- AE-Meter creates ContentInstance-Power. is notified. 57

58 Scenario 4 Get notified when new smart a meter is registered 58

59 ASN-AE Scenario 4 IN-AE CseBase-Meter ASN-CSE CseBase-MeteringServer IN-CSE mcc Meter Device Metering Server Initial state 59

60 CseBase-Meter ASN-AE ASN-CSE Scenario 4 CseBase-MeteringServer P O S T IN-AE IN-CSE Subscription-remoteCSE mcc Meter Device Metering Server Step 1- creates Subscription-devices resource to get notified of new meters 60

61 POST ASN-AE Scenario 4 IN-AE CseBase-Meter ASN-CSE CseBase-MeteringServer IN-CSE Subscription-remoteCSE RemoteCSE-Meter mcc POST Meter Device Metering Server Step 2- The Meter registers to the Metering Server. is notified 61

62 ASN-AE Scenario 4 IN-AE CseBase-Meter ASN-CSE CseBase-MeteringServer IN-CSE Subscription-remoteCSE RemoteCSE-MeteringServer mcc RemoteCSE-Meter Meter Device Metering Server Step 3- The Meter ASN-CSE Creates locally RemoteCSE-Meter resource 62

63 Scenario 5 Store smart meter data remotely using announcement 63

64 ASN-AE Scenario 5 IN-AE CseBase-Meter ASN-CSE CseBase-MeteringServer IN-CSE Subscription-remoteCSE RemoteCSE-MeteringServer mcc RemoteCSE-Meter Meter Device Metering Server Initial state 64

65 AE-Meter CseBase-Meter P O S T ASN-AE ASN-CSE Scenario 5 CseBase-MeteringServer IN-AE IN-CSE AE-Meter Subscription-remoteCSE RemoteCSE-MeteringServer mcc RemoteCSE-Meter AE-Meter-Announced POST Meter Device Metering Server Step 1- AE-Meter registers to the Meter ASN-CSE with announcement. 65

66 AE-Meter CseBase-Meter P O S T ASN-AE ASN-CSE Scenario 5 CseBase-MeteringServer IN-AE IN-CSE AE-Meter Subscription-remoteCSE RemoteCSE-MeteringServer mcc RemoteCSE-Meter AE-Meter-Announced POST Container-Power Meter Device Metering Server Step 2- AE-Meter remotely creates Container-Power on AE-Meter-Announced 66

67 AE-Meter CseBase-Meter P O S T ASN-AE ASN-CSE Scenario 5 CseBase-MeteringServer IN-AE IN-CSE AE-Meter Subscription-remoteCSE RemoteCSE-MeteringServer mcc RemoteCSE-Meter AE-Meter-Announced POST Container-Power Meter Device Metering Server ContentInstance-Power Step 3- AE-Meter creates remotely ContentInstance-Power 67

68 AE-Meter CseBase-Meter ASN-AE ASN-CSE Scenario 5 CseBase-MeteringServer G E T IN-AE IN-CSE AE-Meter Subscription-remoteCSE RemoteCSE-MeteringServer mcc RemoteCSE-Meter AE-Meter-Announced Container-Power Meter Device Metering Server ContentInstance-Power Step 4- retrieves the ContentInstance-Power resource direcly from IN-CSE 68

69 Thank you for your Attention 69

2 - onem2m Common Architecture for IoT

2 - onem2m Common Architecture for IoT Dr. Mahdi Ben Alaya Founder & CEO, Sensinov benalaya@sensinov.com www.sensinov.com November 14, 2016 M2M world of connected services 2 Introduction Communication