Skip to content

6.7 LWM2M IPE Administration and Maintenance

6.7.1 Introduction

The IPE described in clause 5.4 is comprised functionality that includes the LWM2M Server and the IPE's AE. This clause describes the administration and maintenance of these functional elements.

6.7.2 Administration and Maintenance of the LWM2M Server Functionality

6.7.2.1 Introduction

The LWM2M IPE provides the functionality that plays the role of the LWM2M Server in order to communicate with LWM2M Clients.

In order for communication to be established information needs to be provisioned into the LWM2M Client and LWM2M Server where the following artefacts are necessary to be established for the LWM2M Server:

  • LWM2M Server and Client Credentials.
  • LWM2M Access control lists.

In addition, the LWM2M Server maintains information about each LWM2M Client and has actions that are used to maintain the LWM2M Server.

These aspects of the LWM2M Server are further described in clause E.2 of the LWM2M Server resource [3].

The mechanisms used to administer and maintain the LWM2M Server functionality within the LWM2M IPE is out of scope of the present document.

6.7.2.2 LWM2M Server Maintenance

The LWM2M Server maintains a set of LWM2M Server account information for each LWM2M Client that allows the LWM2M Server to access and communicate with LWM2M Client. These are:

  • LWM2M Server identifier associated with and assigned by the LWM2M Client (LWM2M Server identifier, registration lifetime).
  • Policies for default observation behavior.

The following actions can also be performed that affects the state of the LWM2M Server's interaction with the LWM2M Client:

  • On-demand request for the LWM2M Client to update its registration.

6.7.3 Maintenance of the LWM2M IPE AE Context

6.7.3.1 Introduction

The LWM2M IPE AE maintains information related to the operational context of the LWM2M IPE AE. Specifically the following elements are maintained for the LWM2M IPE AE:

  • List of currently registered LWM2M Endpoints.
  • Configuration of the Interworking Functions to be used for the LWM2M Objects and Object Instances.

6.7.3.2 LWM2M Endpoint List

Whenever an LWM2M Endpoint <AE> resource is created, updated or deleted as described in clause 6.2, the LWM2M IPE also manages the list of LWM2M Endpoint <AE> resources using a oneM2M <group> resource.

The oneM2M <group> resource's lifecycle is linked to the LWM2M IPE <AE> resource's lifecycle.

Table 6.7.3.2-1: LWM2M IPE <AE> resource - Group Lifecycle

LWM2M IPE <AE> resource Operation oneM2M Resource and Operation
create create <group>. The group resourceName is the AE-ID of the LWM2M IPE <AE>.resource
update update <group>
delete delete <group>

The LWM2M Endpoint <AE> resources' lifecycle operation maps to the following operations on the oneM2M <group> resource.

Table 6.7.3.2-2: LWM2M Endpoint <AE> resource - Group member Lifecycle

LWM2M Endpoint <AE> resource Operation oneM2M Resource and Operation
Create update <group> (add member)
Delete update <group> (delete member)

6.7.3.3 Configuration of Interworking Functions

Clause 5.3 describes the types of interworking functions as Transparent Interworking Function and Semantically Enabled Interworking Function. An IPE provides the capability to perform one or both types of interworking functions. The granularity (e.g. Object/Object Instance, IPE) that is used to define which interworking function(s) to use is implementation specific.