Registration Parameters
| Parameter | Required | Default Value | Notes |
|---|---|---|---|
| Endpoint Client Name | Yes | ||
| Lifetime | No | 86400 | If Lifetime Resource does not exist in a LWM2M Server Object Instance (see
Appendix D.1 of LWM2M specifications), the Client must
not send this parameter and the Server MUST regard lifetime of the
Client as 86400 seconds. The registration should be removed by
the Server if a new registration or update is not received within this lifetime. For more information, see Appendix D.1 of LWM2M specifications. |
| LWM2M Version | No | 1.0 | Indicates the version of the LWM2M Enabler supported by LWM2M Client. |
| Binding Mode | No | U | Indicates current binding and Queue mode of the LWM2M Client.
U means UDP binding, and S means SMS
binding. The Q can be appended to represent the binding works
in the Queue mode. For example, UQS means the Client uses both the UDP binding with Queue Mode enabled and the SMS binding with Queue Mode disabled. The valid values of the parameter are listed in the Section 5.3.1.1 of LWM2M specifications. |
| SMS Number | No | The value of this parameter is the MSISDN where the LWM2M Client can be reached for use with the SMS binding. | |
| Objects and Object Instances | Yes | The list of Objects supported and Object Instances available on the LWM2M Client. |
- If the client supports SMS mode for register update trigger, then the MSISDN of the client may be sent during the registration.
- Lifetime – When device does not include this with registration, server uses a default value of 86400 seconds (1 day).
- Binding Mode – When device does not include this with registration, server uses a default value of U.
- SMS Number – When device does not include this with registration, server does not use any default. If the device’s binding mode is UQS and server needs to send a command to device, it is expected that the SMS Number of the device is populated and made available in the IMPACT system prior to sending the command.
Note:
When a bootstrapped LWM2M device sends a registration request to the server with mandatory parameters and its endpoint name, without specifying the supported content format, the server updates its registration information.
However, if no content format is specified, then default content format, TLV is used.