2 - onem2m common architecture for iot · 2 - onem2m common architecture for iot dr. mahdi ben...
TRANSCRIPT
2 - oneM2M Common Architecture for IoT
Dr. Mahdi Ben AlayaFounder & CEO, Sensinov
November 14, 2016
M2M world of connected services
2
• 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.
IoT market fragmentation
Source: CRYSTAL project/Philips
3
IoT cross-domain interoperability
• 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.
Invert the pipe
• End-to-end platform: common service capabilities layer.
• Interoperability at the level of communications and data.
• Seamless interaction between heterogeneous applications and devices. 4
• 143 organizations around the world are involved in M2Mstandardization according to the Global StandardsCollaboration M2MTask Force.
M2M
Buildings
EnergyConsumer
Health careIndustrial
TransportationRetail Security
Standards landscape for IoT
5
http://www.etsi.org/technologies-clusters/technologies/m2m
IoT high level architecture
6
Standards for Wide Area Networks(3GPP, fixed NW, WiMax…):Target: protect networks against negative effects of M2M traffic (many devices, non-human traffic …)
Standards for Wide Area Networks
http://www.etsi.org/technologies-clusters/technologies/m2m 7
Standards for Local Area Networks (ZigBee, BLE, Enocean, PLC, etc.)Target: foster use of LAN technology by supporting diverse ecosystem of service providers and device manufacturers.
Standards for M2M Area Networks
http://www.etsi.org/technologies-clusters/technologies/m2m 8
Standards for vertical Industries applicationsTarget: enable interoperable, cost-efficient Solutions.
Standards for vertical industries
http://www.etsi.org/technologies-clusters/technologies/m2m 9
Standards for M2M service capabilities
http://www.etsi.org/technologies-clusters/technologies/m2m
Standards for M2M Service capabilities:Target: end-to end enablement across servers, gateways, and devices.Standardized service interfaces.
10
oneM2M: The Partnership Project
11
Over 200 member organizations in oneM2M
12
oneM2M liaisons
13
PurposeTo specify and promote an
M2M Common Service Layer
WorkSix physical 1-week meetings per year
About 5 conference calls per week between the meetings200+ documents produced and discussed at each meeting
3800 docs in 2013 4200 docs in 2014
DeliverablesTechnical Reports and Technical Specifications
Purpose, Work & Deliverables
14
Use Cases & Requirements
Public ServicesEnterprise HealthcareEnergy
TransportationOtherResidential
REQUIREMENTSTS-0002
15
ServiceComponents
TS-0007
MQTT ProtocolBinding
TS-0010
Service LayerCore Protocols
TS-0004
FunctionalArchitecture
TS-0001
Definitions& Acronyms
TS-0011
Requirements
TS-0002
Technical Specifications
ManagementEnablnt - BBF
TS-0006
ManagementEnablnt - OMA
TS-0005
CoAP ProtocolBinding
TS-0008
HTTP ProtocolBinding
TS-0009
SecuritySolutions
TS-0003
…
16
Planning for Release 2 - Timeline
R2 normative work
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep
Stage 1
R3 non-normative work
R3 normative work
Stage1 Freeze
R2 normative work
Stage 2
R3 non normative work
R3 normative work
R2 normative work
Stage 3
R3 normative work
Stage3 Freeze
2015 2016
TP24
R3 start norm work
Oct Nov
TP25
Stage2 Freeze
TP18 TP19 TP20 TP21 TP22 TP23
R2 approval
R2 ratification
TP26
ARC 19.4
Release 2
Release 3
Color Code
Planning for Release 2 – Planned Features
Industrial domainenablement
• Time series, etc.• In conjunction with the TR
oneM2MBeyond
initial release
Semanticinteroperability
• base ontology• semantic discovery• semanticdescriptions
Security• Enhancement for authorization• privacy support• e2e security
Home domain enablement• Home applianceinformation models
oneM2M Application Identification Registry established
Advanced protocol binding•WebSocket
oneM2M interworking framework
• Generic interworking• AllJoyn/AllSeen• OIC• OMA LightWeight M2M•3GPP Rel.13 interworking
oneM2M high level architecture
UnderlyingNetwork
UnderlyingNetwork
CSE
AE
NSE
CSE
AE
NSE
CSE
AE
NSENSE
Device Gateway Server
ApplicationLayer
ServiceLayer
NetworkLayer
Mca
Mcn
Mca Mca
McnMcnMcnMcc Mcc
Entities: AE (Application Entity), CSE (Common Services Entity) and NSE (Network Services Entity)
Reference Point: One or more interfaces - Mca, Mcn, Mcc and Mcc’
CSE
Mcc’
OtherServer
19
MN Node
MN-AE
REG
SEC RF
ASM
CMDHGMG
LOC
SUB
MN-CSE
ASN-AE
ASN-CSE
IN Node
IN-AE
Security(SEC)
Data Mgmt and Repository (DMR)
RoutingFunction
(RF)
Application and Service Layer Mgmt (ASM)
Communication Mgmt & Delivery Handling (CMDH)
Location(LOC)
Subscription and Notification
(SUB)
Registration(REG)
IN-CSE
ADN Node
ASNNode
Non oneM2M
Nodes
ADN-AE
ADN Node
ADN-AE
OtherMN Node
oneM2M functional architecture
Group Management
(GMG)
OtherIN Node
DMR
REG
SEC RF
ASM
CMDHGMG
LOC
SUB
DMR
IN-NSE
MN-NSE
ASN-NSE
20
OneM2M resource structure
OneM2M Resource structure
Resource type representation
Mgmt ObjectPolling Channel
Application Entity
Access Control Policy
Node
oneM2M resource types
SubscriptionGroupContent Instance
Container
Remote CSECse BASE
…
MN-CSE-HOME
AE-SMART-METER
CIN-MEASUREMENT_3
CNT-DATA
CIN-MEASUREMENT_2
CIN-DESCRIPTION_1
CNT-DESCRIPTOR
Server/Cloud(IN-CSE)
Smart Meter(ADN)
End user(DA)
Gateway (MN-CSE)
CIN-MEASUREMENT_1
oneM2M resource tree example
CseBase
Application Entity
Container
Content Instance
Resource Type
23
24
Blocking requests
Accessing resources in oneM2M(Blocking)
25Non blocking synchronous requests
Accessing resources in oneM2M(Non blocking Synchronous)
26
Non blocking asynchronous requests
Accessing resources in oneM2M(Non blocking asynchronous)
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.
Zigbee Zwave
Modbus
Canbus
Enocean
LWM2M
OIC
AllJoin
Others
KNX
LORA
InterworkingProxy Entity
CSE
Non oneM2M entities oneM2M entities
oneM2M resources
27
oneM2M implementations
Open source
Commercial & Demo
28
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
29
Scenario 1Nodes mutual authentication and applications
registration
30
ASN-CSECseBase-SmartMeter
ASN-AE
mca
mcc
SmartMeterDevice
Initial state
Scenario 1
IN-CSECseBase-MeteringServer
IN-AE
mca
Smart Metering
Server
31
Scenario 1
ASN-CSECseBase-SmartMeter
ASN-AE
mca
mcc
SmartMeterDevice
IN-CSE
IN-AEAE-PowerProcessing
AE-PowerProcessing
Smart Metering
Server
POST
mca
CseBase-MeteringServer
Step 1- AE-PowerProcessing Registers to the Metering Server IN-CSE 32
ASN-CSE IN-CSE
ASN-AE
mca
mcc
mca
SmartMeterDevice
Smart Metering
Server
RemoteCSE-SmartMeter
POST
Scenario 1
AE-PowerProcessing
IN-AEAE-PowerProcessing
CseBase-MeteringServerCseBase-SmartMeter
Step 2- The Smart Meter ASN-CSE registers to the Metering Server IN-CSE 33
ASN-CSE IN-CSECseBase-SmartMeter
ASN-AE
mca
mcc
mca
RemoteCSE-MeteringServer
SmartMeterDevice
Smart Metering
Server
RemoteCSE-SmartMeter
Scenario 1
AE-PowerProcessing
CseBase-MeteringServer
IN-AEAE-PowerProcessing
Step 3- The Smart Meter ASN-CSE Creates locally RemoteCSE-MeteringServer resource 34
ASN-CSE IN-CSE
ASN-AEAE-SmartMeter
SmartMeterDevice
Smart Metering
Server
POST
Scenario 1
CseBase-SmartMeter
IN-AEAE-PowerProcessing
CseBase-MeteringServer
RemoteCSE-MeteringServer
AE-SmartMeter
mca
mcc
mca
RemoteCSE-SmartMeter
AE-PowerProcessing
Step 4- AE-SmartMeter registers to the Smart Meter ASN-CSE 35
Scenario 2Retrieve data from smart meter
36
ASN-CSE IN-CSE
ASN-AEAE-SmartMeter
SmartMeterDevice
Smart Metering
Server
Scenario 2
CseBase-SmartMeter
IN-AEAE-PowerProcessing
CseBase-MeteringServer
RemoteCSE-MeteringServer
AE-SmartMeter
mca
mcc
mca
RemoteCSE-SmartMeter
AE-PowerProcessing
Initial state 37
ASN-CSE
ASN-AE
mca
SmartMeterDevice
POST
Scenario 2
IN-CSE
Smart Metering
Server
IN-AEAE-PowerProcessing
CseBase-MeteringServer
mca
mcc
CseBase-SmartMeter
AE-SmartMeter
RemoteCSE-SmartMeter
AE-PowerProcessing
AE-SmartMeter
RemoteCSE-MeteringServer
Container-Power
Step 1- AE-SmartMeter Creates Container-Power sub-resource 38
ASN-CSE
ASN-AE
mca
SmartMeterDevice
POST
Scenario 2
IN-CSE
Smart Metering
Server
IN-AEAE-PowerProcessing
CseBase-MeteringServer
mca
mcc
CseBase-SmartMeter
AE-SmartMeter
RemoteCSE-SmartMeter
AE-PowerProcessing
AE-SmartMeter
RemoteCSE-MeteringServer
Container-Power
ContentInstance-Power
Step 2- AE-SmartMeter creates ContentInstance-Power sub-resource 39
ASN-CSE
ASN-AE
mca
SmartMeterDevice
Scenario 2
IN-CSE
Smart Metering
Server
IN-AEAE-PowerProcessing
CseBase-MeteringServer
mca
mcc
CseBase-SmartMeter
AE-SmartMeter
RemoteCSE-SmartMeter
AE-PowerProcessing
AE-SmartMeter
RemoteCSE-MeteringServer
Container-Power
ContentInstance-Power
GET
GET
Step 3- AE-PowerProcessing retrieves the ContentInstance-Power resource 40
Scenario 3Get notified when new metering
data is created
41
ASN-CSE
ASN-AE
mca
SmartMeterDevice
Scenario 3
IN-CSE
Smart Metering
Server
IN-AEAE-PowerProcessing
CseBase-MeteringServer
mca
mcc
CseBase-SmartMeter
AE-SmartMeter
RemoteCSE-SmartMeter
AE-PowerProcessing
AE-SmartMeter
RemoteCSE-MeteringServer
Container-Power
Initial state 42
ASN-CSE
ASN-AE
mca
SmartMeterDevice
Scenario 3
IN-CSE
Smart Metering
Server
IN-AEAE-PowerProcessing
CseBase-MeteringServer
mca
mcc
CseBase-SmartMeter
AE-SmartMeter
RemoteCSE-SmartMeter
AE-PowerProcessing
AE-SmartMeter
RemoteCSE-MeteringServer
Container-Power
POST
POST
Subscription-Power
Step 1- AE-PowerProcessing subscribes to Container-Power of AE-SmartMeter 43
ASN-CSE
ASN-AE
mca
SmartMeterDevice
Step 2- AE-SmartMeter creates ContentInstance-Power. AE-PowerProcessing is notified.
Scenario 3
IN-CSE
Smart Metering
Server
IN-AEAE-PowerProcessing
CseBase-MeteringServer
mca
mcc
CseBase-SmartMeter
AE-SmartMeter
RemoteCSE-SmartMeter
AE-PowerProcessing
AE-SmartMeter
RemoteCSE-MeteringServer
Container-Power
Subscription-Power
POST
POST
PO
ST
ContentInstance-Power
44
Scenario 4Get notified when new smart a meter is
registered
45
Scenario 4
ASN-CSECseBase-SmartMeter
ASN-AE
mca
mcc
SmartMeterDevice
IN-CSE
IN-AEAE-PowerProcessing
Smart Metering
Server
mca
CseBase-MeteringServer
Initial state
AE-PowerProcessing
46
Scenario 4
ASN-CSECseBase-SmartMeter
ASN-AE
mca
mcc
SmartMeterDevice
IN-CSE
IN-AEAE-PowerProcessing
Smart Metering
Server
POST
mca
CseBase-MeteringServer
Step 1- AE-PowerProcessing creates Subscription-devices resource to get notified of new meters
Subscription-remoteCSE
AE-PowerProcessing
47
ASN-CSE IN-CSE
ASN-AE
mca
mcc
mca
SmartMeterDevice
Smart Metering
Server
POST
Scenario 4
IN-AEAE-PowerProcessing
CseBase-SmartMeter
Step 2- The Smart Meter registers to the Metering Server. AE-PowerProcessing is notified
Subscription-remoteCSE
CseBase-MeteringServer
AE-PowerProcessing
RemoteCSE-SmartMeter
PO
ST
48
ASN-CSECseBase-SmartMeter
ASN-AE
mca
mcc
RemoteCSE-MeteringServer
SmartMeterDevice
Scenario 4
Step 3- The Smart Meter ASN-CSE Creates locally RemoteCSE-SmartMeter resource
IN-CSE
mca
Smart Metering
Server
IN-AEAE-PowerProcessing
Subscription-remoteCSE
CseBase-MeteringServer
AE-PowerProcessing
RemoteCSE-SmartMeter
49
Scenario 5Store smart meter data remotely using
announcement
50
IN-CSE
mcc
mca
Smart Metering
Server
Scenario 5
IN-AEAE-PowerProcessing
Initial state
Subscription-remoteCSE
CseBase-MeteringServer
AE-PowerProcessing
RemoteCSE-SmartMeter
ASN-CSE
ASN-AE
SmartMeterDevice
CseBase-SmartMeter
RemoteCSE-MeteringServer
mca
51
IN-CSE
mcc
mca
Smart Metering
Server
IN-AEAE-PowerProcessing
Step 1- AE-SmartMeter registers to the Smart Meter ASN-CSE with announcement.
Subscription-remoteCSE
CseBase-MeteringServer
AE-PowerProcessing
RemoteCSE-SmartMeter
ASN-CSE
ASN-AEAE-SmartMeter
SmartMeterDevice
POST
CseBase-SmartMeter
RemoteCSE-MeteringServer
AE-SmartMeter
mca
POST
AE-SmartMeter-Announced
Scenario 5
52
IN-CSE
mcc
mca
Smart Metering
Server
Scenario 5
IN-AEAE-PowerProcessing
Step 2- AE-SmartMeter remotely creates Container-Power on AE-SmartMeter-Announced
Subscription-remoteCSE
CseBase-MeteringServer
AE-PowerProcessing
RemoteCSE-SmartMeter
ASN-CSE
ASN-AEAE-SmartMeter
SmartMeterDevice
POST
CseBase-SmartMeter
RemoteCSE-MeteringServer
AE-SmartMeter
mca
POST
AE-SmartMeter-Announced
Container-Power
53
IN-CSE
mcc
mca
Smart Metering
Server
Scenario 5
IN-AEAE-PowerProcessing
Step 3- AE-SmartMeter creates remotely ContentInstance-Power
Subscription-remoteCSE
CseBase-MeteringServer
AE-PowerProcessing
RemoteCSE-SmartMeter
ASN-CSE
ASN-AEAE-SmartMeter
SmartMeterDevice
POST
CseBase-SmartMeter
RemoteCSE-MeteringServer
AE-SmartMeter
mca
POST
AE-SmartMeter-Announced
Container-Power
ContentInstance-Power
54
IN-CSE
mcc
mca
Smart Metering
Server
Scenario 5
IN-AEAE-PowerProcessing
Step 4- AE-PowerProcessing retrieves the ContentInstance-Power resource direcly from IN-CSE
Subscription-remoteCSE
CseBase-MeteringServer
AE-PowerProcessing
RemoteCSE-SmartMeter
ASN-CSE
ASN-AEAE-SmartMeter
SmartMeterDevice
CseBase-SmartMeter
RemoteCSE-MeteringServer
AE-SmartMeter
mca
AE-SmartMeter-Announced
Container-Power
ContentInstance-Power
GET
55
