Embed Size (px)
DESCRIPTION
LWM2M Interworking Reference Model LWM2M Interworking aims at considering the association of a LWM2M Client and an Interworking Proxy Entity (IPE) as a oneM2M Application Entity (AE) . LWM2M Application CSE LWM2M Protocol LWM2M IPE Mca AE ASN/MN/IN Mcc/Mcc’ MN/IN LWM2M Applications communicate with oneM2M Applications across the Mca&Mcc reference points. 2
Citation preview
LWM2M Interworking
Group Name: ArchitectureSource: ALU (TIA) / Gemalto N.V(ETSI)Meeting Date: TP18Agenda Item: LWM2M Interworking
LWM2M Interworking Reference Model
LWM2M Applications communicate with oneM2M Applications across the Mca&Mcc reference points.
LWM2M Application
CSE
LWM2M Protocol
LWM2MIPE
Mca
AE
Mca
ASN/MN/IN
CSEMcc/Mcc’
MN/IN
2
LWM2M Interworking aims at considering the association of a LWM2M Client and an Interworking Proxy Entity (IPE) as a oneM2M Application Entity (AE) .
LWM2M Interworking Transport Types
The information exchanged between the LWM2M Application and the oneM2M AE are transported in oneM2M <container> resources by either encapsulating or translating the LWM2M objects.
LWM2M Application
CSE1
LWM2M Protocol
LWM2M
IPE
Mca
Mca
CSE2 Mcc/Mcc’
<container> LWM2M Objects
(Serialized)
<container>
LWM2M Objects
encapsulates
provides
uses
uses
AE LWM2M Application
CSE1
LWM2M Protocol
LWM2M
IPE
Mca
Mca
CSE2 Mcc/Mcc’
<container>
semantic<container>
LWM2M Objects
encapsulates
provides
uses
uses
AE
Transparent Transport Semantic Transport
3
LWM2M Interworking Functions
For providing the interworking functions several LWM2M aspects have to be considered :
• LWM2M Device and Endpoint Lifecycle (Client Registration)• LWM2M Object Discovery (Client Registration, Device Management and
Service Enablement)
• LWM2M Object Transport and Interworking (Device Management and Service Enablement)
• LWM2M Object Subscription and Notification (Information Reporting)• LWM2M Object Security (Device Management and Service Enablement)• LWM2M Client Pre-provisioning (Bootstrap)• LWM2M Interworking Proxy Entity Administration
4
LWM2M Interworking Key Points (1)
oneM2M <node> & LWM2M EndpointLWM2M Endpoints are instantiated as <AE> resources with the
LWM2M Client Endpoint Name used as the AE-ID. A oneM2M <node> resource is created/associated with the
LWM2M Endpoint and should use the LWM2M Client Endpoint Name as the M2M-Node-ID.
oneM2M AEs discover LWM2M Endpoints as <AE> and <node> resources using the labels associated with the resources.
5
LWM2M Interworking Key Points (2)
LWM2M Objects and Object Instances are discovered using the Registration Interface of the LWM2M Client. Discovered LWM2M Objects and Object Instances are interworked as <container> resources.
oneM2M AEs discover LWM2M Objects and Object Instances as <container> resources using the labels associated with the resources.
6
LWM2M Interworking Modes (1)
7
LWM2M Interworking Modes (2)
Lazy Interworking Mode The IPE doesn’t instantiate the <contentInstance> resource
until it is first needed by any CRUD operation On a RETRIEVE Operation, the IPE goes to the LWM2M client
for updating the <contentInstance> resource. On a WRITE Operation, modifications made to the
<contentInstance> is reflected back by the IPE into the LWM2M Client as a write-through atomic operation
8
LWM2M Interworking Modes (3)
9
