SMARTM2M/ONEM2M ARCHITECTURE AND PRINCIPLE OVERVIEW Omar Elloumi, Alcatel‐Lucent, ETSI Smart M2M Vice Chair, Chair oneM2M Architecture WG Enrico Scarrone, Telecom Italia, ETSI Smart M2M Vice Chair For DG Connect/ETSI Smart Appliances Workshop, Sophia Antipolis 14 october 2014 © ETSI 2014. All rights reserved Outline Introduction Approach Architecture and principles overview What next? © ETSI 2014. All rights reserved INTRODUCTION © ETSI 2014. All rights reserved The next step for the Internet evolution Preinternet “HUMAN TO HUMAN” • Fixed & mobile telephony • SMS Internet of CONTENT “WWW” • e-mail • Information • Entertainme nt Internet of SERVICES Internet of PEOPLE “WEB 2.0” 2 0” “SOCIAL MEDIA” • eproductivity • e-commerce •… •… • Skype • Facebook • YouTube •… Internet of THINGS “MACHINE TO MACHINE” • Identification, tracking monitoring tracking, monitoring, metering, … • Semantically structured and shared data… •… + smart + smart networks IT platforms & services © ETSI 2014. All rights reserved + smart + smart phones & devices, applications objects objects, tags + smart data & ambient context Definitions No single industry definition for Internet of Things/M2M g y g But broad agreement on following key concepts: • The Internet of Things is the framework where “Things” have g g representations in the Internet. A representation may contain semantically structured data (e.g., status, capabilities, location measurements) that can be shared processed or location, measurements) that can be shared, processed or acted upon. Sharing of information is governed according to privacy settings and access rights. • The "Things" that are represented in the Internet may be active (e.g., Zigbee sensor) or passive (e.g., RFID tag). • The representation of the The representation of the “Things” Things to the Internet is enabled to the Internet is enabled by M2M Technologies © ETSI 2014. All rights reserved IoT and M2M framework Applications A Applications Communications network Communications network GW Field area network A A Linked things g and digital g representations Things Thi representations Blood pressure Smart phone serving g as an M2M device A Device Pulse oximeter Device Device Device Things Smart bandage Pedometer © ETSI 2014. All rights reserved From M2M to IoT M2M COMMUNICATIONS © ETSI 2014. All rights reserved COMMS ENABLE D IT ENABLE D CE ENABLE D BIG DATA APPROACH © ETSI 2014. All rights reserved Use case, multi service, application friendly approach drives market impact Use cases IoT industry segments • Energy • Automotive • Home • Building, etc. Requirements Multiservice Architecture API and protocols Application pp friendly • Data exchange • RESTful & Web Services • Access right • Device lifecyle management • Location g • Interworking • Abstraction • Semantics • Security Interop., Open source, Market k deployment Market impact • Interop • Open source • Lab and field trials • Wide scale p y deployment • Leverage underlying networks, etc. • Triggering, etc. t Single communication&interworking framework - keeping the autonomy of the IoT industry segments and related innovation/differentiation potential © ETSI 2014. All rights reserved Use cases, the long-tail model © ETSI 2014. All rights reserved ARCHITECTURE AND PRINCIPLES OVERVIEW © ETSI 2014. All rights reserved M2M Evolution Pipe (vertical): 1A Application, li ti 1 NW NW, 1 (or few) type of Device Application Business Horizontal (based on common Layer) Applications pp share common infrastructure,, environments and network elements Business Application pp Application #1 Application Business Application pp Application #2 Business Application pp Application #n Things representations Common Application Infrastructure/Service layer Things representations (shared) Communication Network (mobile, fixed, Powerline ..) Communication Network 2 Communication Network 1 IP Gateway Gateway Local NW Local NW A A A A Device Device Device Device Things Things A Device Things From vertical to horizontal integation From raw data to semantic data Abstraction and Semantics M2M Platform C Communications i ti © ETSI 2014. All rights reserved Principles IP‐based, but interworks with specific IP and non IP technologies in the M2M A M2M Area networks k RESTful resource oriented APIs Some of the supported features are: • • • • • • • • • • Authentication Secure communication Service and Application Registration Announce and Discovery Data exchange through container resources: store and share Subscription and Notification Group handling Access Control Device Management Re‐use of underlying network capabilities such as location, triggering, etc. © ETSI 2014. All rights reserved Concrete example ((based on ETSI Smart M2M)) M2M Gateway Aggregation & format conversion M2M Device Measurement App. Local Connectivity GSL NSL 3G Network B M2M customer’s ’ application A Starting New Write … Ask GSL ..and NSL Measurement etc, GSL notifies checks measurement writes toetc //GSL/A assumptions: to…write aggregated network with aggregation appaggregated/transformed policies can value app simply data app and available (DB,to about when keep HRN) //NSL/B on time new about delivering data, isdata good newGSL todata. gets its //NSL/B…. keep data connected… to a copy the GSL of the data for and -Aggregation for Bootstrapping subsequent subsequent BTW, this app isuse /use low gets DM priority isalways doneand (provisioning notified you got about 12ofthe hcredentials/apps) time newforbits that! coming in GSL and store-and-forward store NSLand have forward logically aggregated/transformed connected (authentication (authentication, data at binding binding, a goodencryption) time - GSLwill NSL - Apps willhave notify authenticated DB app when to new xSL and dataaccess arrived right were established Resources => Very little effort to synch the different apps © ETSI 2014. All rights reserved ETSI M2M/SmartM2M available Specifications p Work Use Cases [Stage 0] TR 102 691 Smart Metering TR 102 935 Smart Grid impacts on M2M TR 102 966 TR 102 732 TR 102 857 TR 102 898 eHealth Connected consumer Automotive Stage 1 OMA DM compatible Management Objects 16 TR 102 725 M2M Service Requirements M2M Definitions M2M Functional Architecture Stage 3 M2M Communications; mIa, dIa and mId interfaces TR 102 167 Threat analysis & counter measures to M2M service layer TS 102 690 Stage 2 Interworking with M2M Area Networks TS 101 404 TS 102 689 TR 102 897 City automation TS 102 921 TS 101 405 TR 101 584 BBF TR-069 compatible Management Objects Semantic support for M2M Data oneM2M Similar approach ETSI Smart M2M is contributed to oneM2M ETSI Smart M2M is contributed to oneM2M Future normative work will take place in oneM2M but ETSI Smart M2M will play a key role bringing EU requirements Key specifications include: • • • • • • • • • • • Technical Report TR 0001‐ oneM2M Use Case collection Approved Technical Specification TS 0002 ‐ M2M Requirements Approved Technical Specification TS 0002 ‐ M2M Requirements Approved Technical Specification TS 0001 ‐ M2M Architecture Technical Report TR 0007 ‐ oneM2M Abstraction and Semantics Capability Enablement Technical Specification TS 0003 ‐ oneM2M Security Solutions Technical Specification TS 0004 ‐ oneM2M Protocol Technical Specification Technical Specification TS 0005 ‐ oneM2M Management Enablement (OMA) Technical Specification TS 0006 ‐ oneM2M Management Enablement (BBF) Technical Specification TS 0007 ‐ oneM2M Service Components Technical Specification TS 0008 ‐ CoAP Protocol Binding Technical Specification Technical Specification TS 0010 ‐ MQTT Protocol Binding Technical Specification, etc. © ETSI 2014. All rights reserved WHAT NEXT? From M2M to IoT © ETSI 2014. All rights reserved Wind sensor example Properties S Source W3C SSN © ETSI 2014. All rights reserved Measurements A Possible mapping Wind sensor example, native case NSCL 1.Register 2. Declare properties 4. Discover properties 3. Report measurements 5. Read measurements Windsensor 123 App Descriptor p container © ETSI 2014. All rights reserved Speed container 10 15 20 Direction container N E NW Apps Conclusion Need further validation for the mapping framework Both ETSI and oneM2M specification are ‘Semantics Both ETSI and oneM2M specification are Semantics ready ready’ Need a solid set of semantic specifications to make the vision reality Contact Details: O.Elloumi: omar.elloumi@alcatel‐lucent.com E. Scarrone: [email protected] Thank you! © ETSI 2014. All rights reserved