1. LWM2M Interworking Object Instantiation Group Name: Architecture Source: ALU (TIA) Meeting Date: Arc 17.2 Agenda Item: LWM2M Interworking

2. How are oneM2M representation of LWM2M Objects Instantiated? When the IPE discovers (through LWM2M Registration) LWM2M Object Instances, the IPE creates a resource for each registered Object Instance. Depending on the “object instantiation method” the IPE instantiates the resource. Each container has only 1 content instance since LWM2M doesn’t keep history of LWM2M Object Instances

3. What are the Object Instantiation Methods? Retrieval Operations Active Instantiation: The IPE creates the resource when a LWM2M Object Instance is discovered and then places a LWM2M observation on the Object Instances for any changes to keep the resources updated. Lazy Instantiation: The IPE doesn’t instantiate the resource until it is first needed, then the IPE treats the container as an Active Instantiation Delegated Instantiation: The IPE always goes to (delegates) the LWM2M client for updating the resource.

4. What are the Object Instantiation Methods? Write Operations Synchronous: Any modifications made to the is reflected back into the LWM2M Client as a write-through atomic operation. Asynchronous: Modifications made to the is reflected back into the LWM2M Client as a write-back operation with a retry mechanism until the is expired.

5. Architectural Implications of the Object Instantiation Object Instantiation Methods (Lazy, Delegated, Asynchronous) requires implementation specific assistance from the CSE. There are 2 approaches to this – We can say if these methods are supported: The IPE must be an ASN (which has its own CSE with these additions. CSEs in general must support these methods as part of Generic interworking.

6. Changes to the LWM2M Architecture if we do not have common CSE functions.