-
Notifications
You must be signed in to change notification settings - Fork 4
1. LWM2M and LWMQN Interfaces
Interface | LWM2M | LWMQN |
---|---|---|
Bootstrap | O | Simple auth. |
Client Registration | ||
Register | O | O |
Deregister | O | O |
Update | O | O |
Schedule [1] | Q mode | Schedule |
Device Mgmt and Service En. | ||
Read | O | O |
Write | O | O |
Discover | O | O |
Write Attributes | O | O |
Execute | O | O |
Create [2] | O | X |
Delete [2] | O | X |
Ping | X | O |
Announce | X | O |
Information Reporting | ||
Observe [3] | O | O |
Notify [4] | O | O |
Cancel Observation | O | O |
Note:
[1] LWMQN has an interface for clients to checkin and checkout from the network. Once checked out, a client can be powered down (deep sleep) or even powered off.
[2] LWMQN doesn't support Create and Delete to keep things simple, this is for the reasons of security and resource-constrained environment at client-side (machines).
[3] At this moment, LWMQN doesn't support the observation upon an Object. Thus notifying an Object is also not allowed.
[4] LWMQN supports partial update for a notification. Assume you have an Object Instance like { resrc1: 1, resrc2: 2, resrc3: 'hello' }
. When LWMQN server receives a notification of this Instance like { resrc3: 'world' }
, it will internally be updated to { resrc1: 1, resrc2: 2, resrc3: 'world' }
.
Overview
- APIs
- Events
- 'ready'
- 'error'
- 'permitJoinin'g
-
'ind'
- devIncoming, devLeaving, devUpdate, devNotify, devChange, devStatus
- 'message'
- APIs
Advanced Topics
Appendix