Help Center > > Developer Guide> SDK Usage Guide on the Device Side> LiteOS SDK Integration Development Guide> Appendix 1 LWM2M> API Defined by LWM2M

API Defined by LWM2M

Updated at: Jun 26, 2019 GMT+08:00

Overview

The LWM2M Enabler consists of two components: LWM2M Server and LWM2M Client. LWM2M designs the following four types of APIs for the interaction between the two components:

  • API for device discovery and registration
  • Bootstrap API
  • API for device management and service enablement
  • Information reporting API

API Model

The following figure shows an API model defined by LWM2M.

Figure 1 API model defined by LWM2M

Message Interaction Process

The following figure shows the message interaction process defined by LWM2M.

Figure 2 Message interaction process defined by LWM2M

API for Device Management and Service Enablement

Each type of LWM2M APIs represents a type of functions. The API for device management and service implementation is one of the four types of APIs defined by LWM2M.

The functions of the four types of APIs are implemented by the following two operations:

  • Upstream operation: LWM2M Client –> LWM2M Server
  • Downstream operation: LWM2M Server –> LWM2M Client

LWM2M Server accesses object instances and resources of the LWM2M Client through the API for device management and service enablement. This API implements seven operations including create, read, write, delete, execute, write attributes, and discover.

Figure 3 Operations implemented by the API for device management and service enablement

API

Operation

Direction

Device management and service enablement

Create, read, write, delete, execute, write attributes, and discover

Downstream

The following figure shows the interaction process implemented by the API for device management and service enablement.

Figure 4 Interaction process implemented by the API for device management and service enablement
Figure 5 Creating and deleting an object

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel