onem2m update zoom on release - directory listing · onem2m update zoom on release 3 ... erm, crm,...
TRANSCRIPT
© 2017 oneM2M
Presenter: Omar Elloumi, oneM2M TP Chair, Nokia Bell‐Labs and CTO [email protected]
oneM2M www.oneM2M.org
ONEM2M UPDATEZOOM ON RELEASE 3
© 2017 oneM2M
Metcalfe’s law
IoT is not any different but the challenge is keep the cost linear within and across IoT domains
© 2017 oneM2M
IoT value will come through Metcalfe’s law, if we solve interoperability issues within and across IoT domains
Source: CRYSTAL project/Philips
Platform based integrationopen standards and open sourceare key
Home Energy HealthAutomotive
Communication Devices & Hardware
Communication Technologies & Protocols
Common Service Layer
Communication Networks
AutomotiveApplications
HomeApplications
EnergyApplications
e‐HealthApplications
© 2017 oneM2M
What market research says• ABI Research report: “The Increasing Importance of System Integrators in the IoT Value
Chain”, august 2017
• ABI Research report, “The Role of System Integrators in M2M and IoT”, august 2017
© 2017 oneM2M
Dimensions for IoT interoperablity
Southbound: Devices, gatewaysand access technologies
Northbound: back‐end apps, Analytics, ERM, CRM, OSS/BSS, Social
Eastbound: cloud and big data
LWM2M
© 2017 oneM2M 8
Proximal IoT
• Technologies in IoT with a focus on “proximal” functionality– Targeting mostly smart home / building automation / proximal network– Simplify connecting “things” in proximity (e.g. in building), monitor, control,
automate, less focus on cloud or hierarchical structures– Enablers: Discovery, Advertisement, Introspection, On‐Boarding– Need for multi‐cast techniques to implement discovery & advertisement– A “user” is still in the center of this “proximal” paradigm (onboarding, usage)
• Examples– OCF (OIC, AllJoyn) with Open Source, Specifications– Several proprietary or open Home Automation technologies– Industrial space: OPC‐UA (client/server), DDS (bus)
Source: Qualcomm
© 2017 oneM2M 9
Distal IoT
• Technologies in IoT with a focus on “distal” functionality– Targeting larger scale deployments of M2M/IoT devices in an overlay network– Hiding complexity of network usage / routing / access control / sharing etc– Storing & sharing of data in distributed, hierarchical topology– Enablers: Proven security, access control, selective communications, addressing– Agnostic to underlying NW technology, – Desirable: Utilize optimizations for M2M / IoT, better efficiency in WAN usage
• Examples– oneM2M (open partnership of SDOs), specification openly available– Cloud components of proprietary or open Home Automation technologies– Proprietary platforms, “born in the cloud” stakeholders, massive system
integration needs
Source: Qualcomm
© 2017 oneM2M 10
Agreeing on applicability statementsis key
Access
Service Layeraka
Service PlatformMiddleware
Enablement Platform
Protocols
Network
Transport
Physical
Link
Session
Presentation
Application
CoAP RTPS HTTP
Wired
OMA LwM2M
IP
TLS /TCP
Custom IoT Applications “OSI equivalent”
Applications
Indu
stria
l Non
-IP
WebSocket
DTLS / UDP
IEEE 802.1TS
N
Proximal Distal
NB: non exhaustive mappingSource: Simplified version from original version by Qualcomm
© 2017 oneM2M
Over 200 member organizations in oneM2M
oneM2M Partnership Project
www.oneM2M.orgAll document are publically available
© 2017 oneM2M 12
M2M Common Service Layer in a nutshellA software “framework”
Located between the M2M applications andcommunication HW/SW that provide connectivity
Provides functions that M2M applicationsacross different industry segments commonly need
(eg. data transport, security/encryption, remote software update...)
Like an “Android” for the Internet of ThingsBut it sits both on the field devices/sensors and in servers
And it is a standard – not controlled by a single private company
© 2017 oneM2M 13
Industry
Work Process
Public ServicesEnterprise HealthcareEnergy
TransportationOtherResidential
REQUIREMENTSTS‐0002
TECHNICAL SPECSTECHNICAL REPORTS
© 2017 oneM2M 14
oneM2M Architecture approach
Pipe (vertical):1 Application, 1 NW,
1 (or few) type of DevicePoint to point communications
Horizontal (based on common Layer)Applications share common service and network infrastructure
Multipoint communications
Local NW
BusinessApplication
Device
CommunicationNetwork (wireline, wireless,
Powerline ..)
Gateway
CommunicationNetwork 1
CommunicationNetwork 2
Local NW
GatewayIP
Application
A
Application Application Application
Common Service Layer
Device Device
Device
AS
AA Device
AS
S Common Service Layer
S
A
Common Service Layer
A Application
Things
Thingsrepresentations(includingsemantics)
© 2017 oneM2M 15
UnderlyingNetwork
UnderlyingNetwork
CSE
AE
NSE
CSE
AE
NSE
CSE
AE
NSENSE
Application Service Node Middle Node Infrastructure Node
ApplicationLayer
ServiceLayer
NetworkLayer
McaMca
McnMcn
McaMca McaMca
McnMcnMcnMcnMccMcc MccMcc
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
RESTful Architecture
CSE
Mcc’Mcc’
Inf. Node
Multiple protocol bindings (HTTP, CoAP, MQTT, or WebSocket) over Mca, Mcc, Mcc’
© 2017 oneM2M 16
Communication ProtocolsReuse IP‐based existing protocols
NB: Interworking with field area protocols and data models (OCF, AllSeen, OMA LWM2M, Zwave, etc)
Service LayerCore Protocols
TS‐0004
CoAP MQTT BindingHTTP
XML or JSON Content serialization ‐ HTTP Example
REQUESTGET /~/CSE‐178/CSEBase/home/temperature HTTP/1.1Host: provider.netX‐M2M‐Origin: /CSE‐123/WeatherApp42X‐M2M‐RI: 56398096Accept: application/json
RESPONSEHTTP/1.1 200 OKX‐M2M‐RI: 56398096X‐M2M‐RSC: 2000Content‐Type: application/vnd.onem2m‐res+jsonContent‐Length: 101{“m2m:cin”:["cnf":"application/json:0","con":"{'timestamp':1413405177000,'value':25.32}"]
}
WebSockets
© 2017 oneM2M 17
Registration Group ManagementSecurityDiscovery &
Announcement
Data Management & Repository
Application & Service
Management
Device Management
Subscription & Notification
Communication Management
Service Charging & Accounting
LocationNetwork Service Exposure
Common Service Functions
Semantics Interworking
© 2017 oneM2M 18
Strong Implementation BaseIndustry‐driven Open source implementations
Examples of Commercial implementations /demos
4 interop. events so far
IotDMOS‐IoT
© 2017 oneM2M 19
Summary of Release 2/3 Features
Industrial Domain Enablement• Time series data management• Atomic Transactions• Action Triggering• Optimized Group Operations
oneM2MRel‐2/3 FeaturesSemantics
• Semantic Description/Annotation• Semantic Querying• Semantic Mashups• oneM2M Base Ontology
Smart City & Automotive Enablement• Service Continuity• Cross resource subscriptions
Market Adoption • Developer Guides• oneM2M Conformance Test• Feature Catalogues• Product Profiles
Security• Dynamic Authorization• End to End Security• Enrollment & Authentication APIs • Distributed Authorization• Decentralized Authentication• Interoperable Privacy Profiles• Secure Environment Abstraction
oneM2M as generic interworking framework
• 3GPP SCEF• OMA LwM2M • DDS• OPC‐UA• Modbus• AllJoyn/OCF• OSGi• W3C WoT
Management• M2M Application & Field Domain Component Configuration
Home Domain Enablement• Home Appliance Information Models & SDT• Mapping to existing standards (OCF, ECHONET, GoTAPI...)
© 2017 oneM2M 20
Product profiles
• product profiles and feature catalogue– guidebook to my oneM2M product features – fills the gap btw. function specs. and test specs.
Features Catalogue (TS‐0031)
Functional Architecture (TS‐0001)
Product Profiles (TS‐0025)
glimpse of oneM2M
summarized
guideline for product planning
prepare test cases for products
referred
Core Protocol (TS‐0004)
Test Purposes (TS‐0018)
Abstract Test Suite (TS‐0019)
which feature to be implemented?
which feature needs to be tested?
20Source: KETI
© 2017 oneM2M 21
Developer guide series
• example scenarios and binding messagesDeliverable Title Examples of
TR‐0025 Application developer guide HTTP binding,XML/JSON serialization
TR‐0034 Temperature monitoring example using CoAP binding
CoAP binding,<pollingChannel>
TR‐0035 Developer guide of Device Management <mgmtObj>, OMA DM, LwM2M, BBF TR‐069
TR‐0037 Smart Farm Example using MQTT Binding MQTT binding
TR‐0038 Developer guide ‐ Implementing security example
Provisioning, Security Association Establishment
TR‐0039 Developer guide ‐ SDT based implementation SDT for home appliances
TR‐0045 Developer Guide: Implementing Semantics Semantic annotation and discovery
TR‐0048 Developer Guide of 3GPP Interworking (TBD)
21Source: KETI
© 2017 oneM2M 22
Certification program
• TTA is the 1st Certification Body & Test House– oneM2M Release 1 certification program launched on 9th Feb. 2017
www.onem2mcert.com
Product Webpage Vendor Product Type
GWP http://www.irexnet.co.kr IREXNET End product(IN‐CSE)
AiSOP http://www.irexnet.co.kr IREXNET End product(IN‐CSE)
Insator™ https://www.samsungsds.com SAMSUNG SDS End product(IN‐CSE)
HANDYPIA IoT Platform http://www.handysoft.co.kr/ HANDYSOFT, Inc. End product(IN‐CSE)
IoT Healthcare Platform http://www.hconnect.co.kr/ HealthConnect Co., Ltd End product
ThingPlug https://www.thingplug.net SK Telecom Software component
N‐MAS http://www.ntels.com nTels End product
IoTMakers Middleware http://iotmakers.olleh.com KT Software component
IoTMakers http://iotmakers.olleh.com KT Software component
e‐IoT Energy Platform https://spin.kepco.co.kr KEPCO End product
e‐IoT Energy Gateway https://spin.kepco.co.kr KEPCO End product
certified products (Sep. 2017)
22
© 2017 oneM2M 23
R3 semantic features
• semantic query– Semantic Query Indicator request parameter
• semanticsFilter condition of Filter Criteria delivers SPARQL query, and it is executed on <semanticDescriptor> resources– returns triple data or knowledge, not oneM2M resource IDs– c.f. R2 provides semantic annotation and discovery
23
Aspects Semantic Query Semantic Resource DiscoveryObjective The objective of Semantic
Query is extracting “useful knowledge” over a set of “RDF data basis”.
Semantic resource discovery is targeted to discovery of resources for further resource use (e.g., CRUD operations).
Result The semantic query result (representing the derived “knowledge”) is provided as semantic information to answer the query not limited to resources URIs.
The processed result of a semantic resource discovery is mainly to include a list of identified resource URIs.
Source: KETI
© 2017 oneM2M 24
R3 security features
• Distributed authorization– enforcement, decision, retrieval and information points are distributed– c.f. Hosting CSE decides and enforces authorization with accessControlPolicyID based
normal authorization scheme
• Secure environment (SE) abstraction– stores secure data (e.g. certificate) using SE abstract APIb
24
< distributed authorization model >
© 2017 oneM2M 25
3GPP Rel‐13/14 interworking
• Interwork‐able 3GPP network functions to oneM2M– Device Triggering Recall/Replace, UE Monitoring, Background Data Transfer, Informing
Potential Network Issues, Network Parameter Configuration, Node Schedule Management
25
© 2017 oneM2M 26
Interworking framework
• generic interworking framework– provides guides to map non‐oneM2M devices and services into “existing” oneM2M
resource types in homogeneous way• data mgmt., device mgmt., event/notification, location, group, etc.
– intends not to invent new wheels for each technology– does not include underlying network interworking aspects
26
ZigBee
OSG
i
OPC‐UA
Modbus
OCF
Z‐Wave
generic interworking framework
to be extended in the following releases
TS‐0030TS‐0024 TR‐0043 TR‐0018 TR‐0028
resource hierarchy per
device & service
information model for resources
© 2017 oneM2M 27
Takeaway• IoT, here to stay• Interoperability will make IoT accessible for use cases where cost was prohibitive so far
• Interoperability, within and cross domain, will increase value for IoT
• Interoperability and Certification are key for IoT• Traditional approaches for integration may not scale• Semantic interoperability emerging as very promising technology for IoT interoperability