ONEM2M FOR SMART CITIES

Transcription

1 ONEM2M FOR SMART CITIES Presenter: Omar Elloumi, onem2m TP Chair, Nokia Bell-Labs and CTO group onem2m onem2m

2 Outline Introduction to onem2m IoT technology trends Role of onem2m in smart cities A possible Smart city blue-print Take-away 2016 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 M2M Common Service Layer in a nutshell 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) 2016 onem2m 5

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

7 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 Things representations (including semantics) Gateway Local NW A A Device Local NW A Device A S Device A S Device Device Things S A Common Service Layer Application 2016 onem2m 7

8 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 8

9 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 9

10 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/temperature 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 10

11 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 11

12 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 12

13 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 13

14 onem2m release 2 features Industrial domain enablement Real-time data collection redundancy and fault tolerance enablers for analytics onem2m Beyond initial release Home domain enablement Home appliance information models ontologies and mapping to existing standards Application developer APIs and guidelines Semantic interoperability base ontology, link to domain specific ontologies semantic descriptions semantic discovery Dynamic authorizations and end to end security device onboarding and provisioning onem2m as generic interworking framework AllJoyn/AllSeen OIC LightWeight M2M (LWM2M) 2016 onem2m 14

15 IOT TECHNOLOGY TRENDS 2016 onem2m

16 Trend1: horizontalization NICHE VERTICALS Low volumes, high ARPC, high TCO Devices and Applications are designed as stove-pipes Devices dedicated for single application use Solutions are closed and not scalable: duplication of dedicated infrastructure High development & delivery cost BROAD ADOPTION High volume, low ARPC, low TCO Devices and Applications are designed to collaborate across clouds Devices are used for multiple application purposes Devices and Applications offering continuously evolve Easy app development and device integra-tion through APIs and standard interfaces Horizontal platform with common functions and interfaces Source: Alcatel-Lucent 2016 onem2m 16

17 Trend 2: softwarization Source: ITU-T Focus Group IMT onem2m 17

18 Trend 3: connectivity, plenty to chose from Range (extended) Native Low Power Wide-area Access NB-IoT, CIoT, etc. 3GPP Cellular (GSM/LTE) Device cost (low) Bitrate (low) Device cost (high) Bitrate (high) WPAN (e.g , DECT ULE) WLAN (e.g ) Range (low) Source AIOTI, modified from an ALU contribution 2016 onem2m 18

19 Trend 4: Semantic interoperability 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. 19 Let Things become intelligent Alarm ring earlier in case of traffic or bad weather. Source: sensinov 2016 onem2m 19

20 ROLE OF ONEM2M IN SMART CITIES 2016 onem2m

21 Vision for building smart cities 2. Digitalize and «sensorise» 1. Build a vision 3. Build Dashboards 4. Expand the vision, Integrate and Innovate Source: Based on discussions with Dr. Martin Serrano, OASC and Insight centre 2016 onem2m 21

22 Example - Singapore Smart Nation initiative: Anticipation, Vision and Execution Past In Progress Future NG-NBN National Fiber Network COLLECT & COMPREHEND Deploy an operating system accessible by all stakeholders Sustain livability and position Singapore as a (regional) Digital Harbor to drive economic growth. Wireless National WiFi Network CONNECT Deploy sensors using Above Ground Boxes for electricity & connectivity Singapore Government ICT Investment in BSGD (1SGD = 0.65Euro) 2,0 1,73 1,1 1,1 1,2 1,2 1,2 1,3 1,8 Generalized Heterogeneous Network to boost Citizen Quality of Services 1,0 0,0 Source: IDA onem2m 22

23 Integration challenge Automotive Applications Home Applications Energy Applications e-health Applications Common Service Layer Communication Devices & Hardware Automotive Communication Technologies & Protocols Communication Networks Home Energy Health Platform based integration Based on open standards Source: CRYSTAL project/philips 2016 onem2m 23

24 Semantic interop challenge things represents Things representation Common Service layer Source: AIOTI Data (e.g. temperature) ontology Metadata Semantic description Other metada (e.g. digital right management and privacy related) instantiates Discovery Consistency Scalability - Efficiency 2016 onem2m 24

25 It s not about the technology! Ontology-driven approaches provides a lower costs when dealing with high number of data sources. It ensure interoperability for open and big environments. Source: Price Waterhouse Cooper 2016 onem2m 25

26 Innovation challenge How do I address the needs of app developers App developers focus on app logic: use of Restful APIs Hide WAN and Area Network technologies specificities (interworking exposed as a service by the platform) Free access to city open data Controlled access to other data 2016 onem2m 26

27 onem2m based smart city deployment example - Busan Source: SKT 2016 onem2m 27

28 Smart city Busan use case examples LoRa image 2016 onem2m Source: SKT 28

29 A POSSIBLE SMART CITY BLUE- PRINT 2016 onem2m

30 Key requirements for smart city IoT platform Horizontal platform for new deployments Existing deployments Smart city is an incremental and participatory journey New deployments should, where possible, leverage a converged networks and an horizontal service platform Open standards are key to avoid lock-in and master the total cost of ownership Do not disrupt existing vertical deployment but seek opportunities for an integration path with an horizontal approach Build value through smash-ups and open data Participatory and innovative approach Security and (device) management are key Surveys Address needs for innovation through app development: APIs Access to, eventually semantically enriched, Open data (where feasible and subject to privacy legislation/citizen consent) Despite initial focus on IoT data, there is an increased interest in security and device management (which go hand in hand). Need arises from security threat analysis conducted recently: e.g. Two researchers analyzed Smart meters widely used in Spain and discovered that can be hacked by attackers to harm the overall National power network., source: onem2m 30

31 A possible smart city blue-print Cloud apps Dashboards Dashboards I/F to other IoT platforms Data center REST APIs City City Apps Apps Group mgmt Location Discovery Device Interwor king Data Mgmt Big Data Storage 3rd party 3rd party apps apps REST APIs Smart city backend Smart city frontend Cloud VM Mgmt Big Data enablers Broker Security Device mgmt Adapter Analytics Analytics apps apps SPARQL or REST APIs Open data (Semantics) App Adapter App Existing deployments App Other data sources Field domain Gateway Gateway Device D D D DD D D D D LWM2M 2016 onem2m 31

32 Design Principles Frontend/backend scale differently. Frontend designed for massive secure connections to devices/apps, dev mgmt, interworking, protocol adaption Backend about data functions: replication, anonymization, VM management, availability etc. Semantic engine is about metadata to enrich data sets, reasoning: fast track for integration and analytics Build value for existing application through adapters Open APIs and open data are key for innovation I/F to other platforms: utility, automotive (autonomous driving), etc onem2m 32

33 TAKE AWAY 2016 onem2m

34 Take-away City Every city is unique Build a vision: initial set of use cases Build an architecture that leverages cross sector applications using open standards Integrate existing deployments Stimulate and cultivate a collaborative culture for innovation onem2m provides a fast-track and future proof IoT based smart city complementary standards and open source are needed 2016 onem2m 34

35 Big data is the new oil, clearing up mis-perceptions 2016 onem2m 35

36 Time for questions For further reading: onem2m 36