LwM2M技术规范v1.0.2官方文档

LWM2M

需积分: 9 159 浏览量更新于2024-07-19 收藏 3.15MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"OMA-TS-LightweightM2M-V1_0_2-20180209-A.pdf" 是一份由OpenMobile Alliance (OMA)发布的技术规范文档，详细介绍了LightweightM2M (LwM2M) 协议的版本1.0.2。LwM2M是一种物联网(IoT)通信标准，旨在为资源受限的设备提供高效、轻量级的机器到机器(M2M)通信。 LwM2M协议设计的核心目标是为了简化物联网设备的管理和服务，特别是针对那些计算能力有限、电池寿命要求高或者网络带宽有限的设备。它采用了简洁的协议栈和数据表示方式，以降低设备的复杂性和功耗，同时保证了可靠的数据传输和远程管理功能。在LwM2M协议中，主要有三个关键组件：LwM2M客户端、LwM2M服务器和LwM2M中间件。LwM2M客户端安装在物联网设备上，负责与服务器进行通信，执行数据收集、设备管理以及应用执行等功能。LwM2M服务器则负责接收客户端发送的数据，处理请求，执行远程配置或固件更新等操作。LwM2M中间件是连接客户端和服务器的桥梁，它处理协议转换，使得不同平台和协议的设备可以互相通信。协议采用了层次化的数据模型，称为对象、资源和实例。对象代表特定的功能集，如设备管理、传感器数据等；资源是对象内的具体数据点或功能，如温度读数、开关状态；实例则是特定对象的多个实体，每个实例可能有不同的数据值。 LwM2M支持多种传输层协议，包括CoAP（Constrained Application Protocol）和TCP，以适应不同的网络环境。CoAP是专门为物联网设计的一种低开销、基于UDP的协议，而TCP则提供了更可靠的连接性，适用于需要高稳定性的场景。此外，LwM2M还定义了安全机制，确保数据传输的安全性，包括使用DTLS（Datagram Transport Layer Security）协议进行加密和身份验证，以防止未授权访问和数据篡改。 LwM2M协议通过提供一套标准化的通信框架，降低了物联网设备开发的复杂性，提升了部署效率，同时也保证了系统的可扩展性和互操作性。这份文档详细描述了LwM2M的各个方面，包括协议结构、操作模式、数据模型、安全特性以及实现指南，对于开发者和物联网解决方案设计者来说具有极高的参考价值。

资源详情

资源推荐

OMA-TS-LightweightM2M-V1_0_2-20180209-A Page 16 (142)

Used with the permission of the Open Mobile Alliance under the terms as stated in this document. [OMA-Template-Spec-20180101-I]

LwM2M

Server

LwM2M

Client

Read, Write, Execute, Create,

Delete, Write Attribute, Discover

Figure 5: Device Management and Service Enablement

Figure 6 shows the operation model for interface “Information Reporting”. For this interface, the operations are downlink

operations “Observe” or “Cancel Observation” and an uplink operation “Notify”. This interface is used to send the LwM2M

Server a new value related to a Resource on the LwM2M Client.

LwM2M

Server

LwM2M

Client

Observe, Cancel Observation

Notify

Figure 6: Information Reporting

The relationship between operations and interfaces is listed in the following Table 1.

Interface

Direction

Operation

Bootstrap

Uplink

Bootstrap-Request

Bootstrap

Downlink

Write, Discover, Delete, Bootstrap-

Finish

Client Registration

Uplink

Device Management and Service

Enablement

Downlink

Create, Read, Write, Delete, Execute,

Write-Attributes, Discover

Information Reporting

Downlink

Observe, Cancel Observation

Information Reporting

Uplink

Notify

Table 1: Relationship of operations and interfaces

5.1 Attributes

5.1.1 Attributes Definitions and Rules

Attributes are metadata which can be attached to an Object, an Object Instance or a Resource. The value of an Attribute is

LwM2M Server specific. These attributes can fulfil various roles: from just carrying information (e.g., Discover), up to

containing parameters for Notification for example.

Attributes attached to Object, Object Instance, Resource, are respectively named O-Attribute, OI-Attribute, R-Attribute.

These Attributes MAY be carried in the message payload of Registration and Discover operations; they also MAY be

updated - when writable - through the “Write-Attributes” operation.

Regardless to the LwM2M entity a given Attribute is attached to, the value of such an Attribute can be assigned at various

levels: Object, Object Instance, Resource levels. Additionally, precedence rules apply when the same Attribute receives a

value at different levels.

Several rules govern usage of LwM2M Attributes

OMA-TS-LightweightM2M-V1_0_2-20180209-A Page 17 (142)

Used with the permission of the Open Mobile Alliance under the terms as stated in this document. [OMA-Template-Spec-20180101-I]

 The value of an O-Attribute MAY only be set at the Object level.

 The value of an OI-Attribute MAY be set at the Object Instance level, and at the Object level.

precedence rules:

 Rule 1: When set at both levels, the value of the OI-Attribute set at Object Instance level will prevail.

 Rule 2: When the Attribute value is set at the Object level, the scope of the OI-Attribute value extends to all the

Instances of that Object, as long as the Rule 1 is respected.

 An R-Attribute MAY be set at 3 different levels: the Resource level, the Object Instance level and the Object level.

precedence rules:

 Rule 3: When set at the Resource level, the value of an R-Attribute prevails for that Resource whatever a value

for this R-Attribute is also specified at an upper level (Object or Object Instance level).

 Rule 4: When set at the Object Instance level, the scope of an R-Attribute value extends to all the Resources of

that Object Instance as long as the Rule 3 is respected.

 Rule 5: When set at the Object level, the scope of an R-Attribute value extends to all the resources of any

Instance of that Object, as long as the Rule 4 is respected.

An attribute is fully determined by several characteristics which are listed in the table below:

Attribute

characteristics

Description

Name

Attribute Name used to reference a specific Attribute in that Enabler (e.g., “Minimum Period”)

CoRE Link Param

the string used when this Attribute is transferred to CoAP as a CoRE link parameter (ex pmin)

Attachment

The Object, Object Instance or Resource, to which an Attribute is logically applied

Assignation Level

The Level (Object, Object Instance, Resource) where the value of the Attribute is set (by WRITE-

ATTRIBUTES).

Class

Attributes are organized according to their purpose;

2 Class of Attributes are supported in LwM2M TS 1.0

<NOTIFICATION> gather Attributes regarding Notify operations parameters

<PROPERTIES> gather Attributes regarding general information

Access Mode

R, W, RW: operation allowed by the LwM2M Server.

Applicability

Condition to fulfil for allowing to attach such an Attribute

Default Value

<value> or “-” or “ ”

Value Type

Data Type (Refer Appendix C)

Value

The Value carried by this Attribute : its data type must be of “Value Type”

Table 2: Attribute Characteristics

Some Attributes MAY be exposed to the LwM2M Server in the payload response to a “Discover” command (Section 5.4.2).

The value of some Attributes MAY be changed by the LwM2M Server in using the “Write-Attributes” command (Section

5.4.4); which Attribute are concerned are marked as “W” (writable) in the table of the next Section.

Note: A payload response to a “Discover” command is a list of application/link-format CoRE Links [RFC6690] which will

include the LwM2M Attributes.

5.1.2 Attributes Classification

<PROPERTIES> Class Attributes

OMA-TS-LightweightM2M-V1_0_2-20180209-A Page 18 (142)

Used with the permission of the Open Mobile Alliance under the terms as stated in this document. [OMA-Template-Spec-20180101-I]

The role of these Attributes is to provide metadata which may communicate helpful information to LwM2M Server for

example easing data management.

Except when specifically mentioned as required, the LwM2M Server and LwM2M Client SHOULD support

<PROPERTIES> Class Attributes listed Table 3.

Attribute

Name

CoRE

Link

param

Attachment

Assignation

Level

Support

Required

Access

Mode

Value

Type

Default

Value

Applicabili

Notes

Dimension

dim

Resource

YES

(Client)

Integer

[0:255]

Multiple

Resource

Number of

Instantiations

for a Multiple

Resource

Object

Version

ver

Object

YES

(Server)

YES

(Client)

when able

to support

Objects in

version >

1.0

String

1.0

(Initial

Version)

Provide the

version of the

associated

Object. The

rules

governing the

usage of this

parameter are

specified in

Section 6.2

and Table 19.

Table 3: <PROPERTIES> Class Attributes

<NOTIFICATION> Class Attributes

The role of these R-Attributes is to provide parameters to the “Notify” operation; any readable Resource can have such R-

attributes.

In the message sent by a LwM2M Client in response to an “Observe” operation, the current Resource value is reported; this

event can be considered as the initial notification.

Each time a Resource notification is sent, the “Minimum Period” and “Maximum Period” timers associated to this Resource

are restarted.

Notification Conditions : the notification of a Resource value will be sent when:

₋ valid Change Value Conditions (“Greater Than”, “Less Than”, OR “Step”) - if any is defined - AND the “Minimum

Period” Timing Conditions are both fulfilled for that Resource OR

₋ the “Maximum Period” Timing Condition is fulfilled.

Additionally the following rules MUST be considered:

 a "Maximum Period" (pmax) applied to a Resource, that is smaller than the "Minimum Period" applied to the

same Resource MUST be ignored for that Resource.

 Change Value Conditions are considered as “valid”, if the 2 following rules related to the Attributes defined in

the table below (“Greater Than”, “Less Than”, “Step”) are respected :

- (“lt” value < “gt” value)

- (“lt” value + 2*“st” values <“gt” value)

Notes : when the “Change Value Conditions” Attributes are set in a single WRITE-ATTRIBUTES command, a

coherency check of the 2 rules above should lead to reject that command if these rules are violated.

The LwM2M Server MUST support and LwM2M Client SHOULD support all the <NOTIFICATION> Class Attributes

listed Table 4.

OMA-TS-LightweightM2M-V1_0_2-20180209-A Page 19 (142)

Used with the permission of the Open Mobile Alliance under the terms as stated in this document. [OMA-Template-Spec-20180101-I]

Table 4: <NOTIFICATION> class Attributes

Examples illustrating Attributes setting are provided in Section 8.2.5 (Device Management & Service Enablement Interface).

5.2 Bootstrap Interface

The Bootstrap Interface is used to provision essential information into the LwM2M Client to enable the LwM2M Client to

perform the operation “Register” with one or more LwM2M Servers.

During the Bootstrap Phase, the Client MAY ignore requests and flush all pending responses not related to the Bootstrap

sequence. There are four bootstrap modes supported by the LwM2M Enabler:

 Factory Bootstrap

Attribute

Name

CoRE

Link

param

Attachment

Assignation Level

Required

Access

Mode

Value

Type

Default

Value

Apply

Condition

Minimum

Period

pmin

Resource

Object Instance

Object

Integer

0 (sec)

Readable

Resource

Notes: The Minimum Period Attribute indicates the minimum time in seconds the LwM2M Client MUST wait between

two notifications. If a Resource value has to be notified during the specified quiet period, the notification MUST be sent

as soon as this period expires. In the absence of this parameter, the Minimum Period is defined by the Default Minimum

Period set in the LwM2M Server Account.

Maximum

Period

pmax

Resource

Object Instance

Object

Integer

Readable

Resource

Notes: The Maximum Period Attribute indicates the maximum time in seconds the LwM2M Client MAY wait between

two notifications. When this “Maximum Period” expires after the last notification, a new notification MUST be sent. In

the absence of this parameter, the “Maximum Period” is defined by the Default Maximum Period when set in the

LwM2M Server Account or considered as 0 otherwise. The maximum period parameter MUST be not smaller than the

minimum period parameter otherwise it will be ignored for the Resource to which such inconsistent Timing Conditions

applied.

Greater

Than

Resource

Float

Numerical

&Readable

Resource

Notes: This “gt” Attribute defines a threshold high value. When this Attributes is present, the LwM2M Client MUST

notify the Server each time the Observed Resource value crosses this threshold with respect to pmin parameter and valid

“Change Value Conditions” (see Notification Conditions above).

Less Than

Resource

Float

Numerical

&Readable

Resource

Notes: This “lt” Attribute defines a threshold low value. When this Attributes is present, the LwM2M Client MUST notify

the Server each time the Observed Resource value crosses this threshold with respect to pmin parameter and valid

“Change Value Conditions” (see Notification Conditions above).

Step

Resource

Float

Numerical

&Readable

Resource

Notes: This “Step” Attribute defines a minimum change value between two notifications. When this Attribute is present,

the Change Value Condition will occur when the value variation since the last notification of the Observed Resource, is

greater or equal to the “Step” Attribute value.

When the “Step” Change Value Condition occurs, the LwM2M Client MUST notify the Server with respect to pmin

parameter and valid “Change Value Conditions” (see Notification Conditions above).

OMA-TS-LightweightM2M-V1_0_2-20180209-A Page 20 (142)

Used with the permission of the Open Mobile Alliance under the terms as stated in this document. [OMA-Template-Spec-20180101-I]

 Bootstrap from Smartcard

 Client Initiated Bootstrap

 Server Initiated Bootstrap

The last two Bootstrap modes require the help of a LwM2M Bootstrap-Server to achieve the ultimate goal to connect a

LwM2M Client to their LwM2M Server(s).

The LwM2M Client MUST support at least one bootstrap mode specified in the Bootstrap Interface.

The LwM2M Bootstrap-Server MUST support Client Initiated Bootstrap and Server Initiated Bootstrap modes specified in

the Bootstrap Interface.

This section describes what information is conveyed across the Bootstrap Interface, where the LwM2M Client puts that

information and how to provision the Bootstrap Information for each of these bootstrap modes.

5.2.1 LwM2M Bootstrap-Server

The LwM2M Bootstrap-Server is used to provision the LwM2M Client with the information required to contact the LwM2M

Server(s).

In order for the LwM2M Client and the LwM2M Bootstrap-Server to establish a connection on the Bootstrap Interface, either

in Client Initiated Bootstrap mode or in Server Initiated Bootstrap mode, the LwM2M Client MUST have a LwM2M

Bootstrap-Server Account pre-provisioned in it.

5.2.2 Bootstrap Information

This section specifies the information that needs to be configured in LwM2M Client for connecting to the LwM2M Server(s)

or the LwM2M Bootstrap-Server. This Bootstrap Information can be available before performing the Bootstrap Sequence

described in Section 5.2.4 or obtained as a result of the Bootstrap Sequence.

Bootstrap Information can be categorized into two types:

 LwM2M Server Bootstrap Information

 LwM2M Bootstrap-Server Bootstrap Information

The LwM2M Client MUST have the LwM2M Server Bootstrap Information after the Bootstrap Sequence specified in

Section 5.2.4.

The LwM2M Client SHOULD have the LwM2M Bootstrap-Server Bootstrap Information.

The LwM2M Server Bootstrap Information is used by the LwM2M Client to register and connect to the LwM2M Server.

The LwM2M Server Bootstrap Information MUST contain at least a LwM2M Server Account.

Note that according to the LwM2M Server Account definition, a usual LwM2M Server Account is composed of a Security

Object Instance and a Server Object Instance which are paired by sharing (respectively in Resource 10 and Resource 0 of that

Objects) the same Short Server ID; a Short Server ID being unique in the LwM2M Client.

The LwM2M Server Bootstrap Information MAY additionally contain further Object Instances (e.g., Access Control,

Connectivity Monitoring Object).

The LwM2M Client MAY be configured to use one or more LwM2M Server Account(s).

The LwM2M Client MUST have at most one LwM2M Bootstrap-Server Account.

The LwM2M Bootstrap-Server Bootstrap Information is used by the LwM2M Client to contact the LwM2M Bootstrap-

Server to get the LwM2M Server Bootstrap Information.

The LwM2M Bootstrap-Server Bootstrap Information MUST be a LwM2M Bootstrap-Server Account.

Bootstrap Information Type

Entity

Required

The LwM2M Server Bootstrap

Information

LwM2M Server Account

Yes*

Additional Object Instances (e.g.,

Access Control, Connectivity

Monitoring Object)

剩余141页未读，继续阅读

tlfnewcsdn

粉丝: 0
资源: 5

LwM2M技术规范v1.0.2官方文档

OMA-MMS-CONF-V1_2-20050301-A

OMA-TS-MMS-ENC-V1_3-20080128-C.pdf

LWM2M协议完整版含目录

par(mfrow = c(1,3), mar = c(5, 5, 4, 2), oma = c(2, 0, 2, 0)) plot(roc.full, ylim = c(-1, 2), main = "FULL") plot(roc.aic, ylim = c(-1, 2), main = "AIC") plot(roc.bic, ylim = c(-1, 2), main = "BIC") 为何图片显示的y轴在-2到3之间？能否将y轴的范围修改到[-1,2]？

ubuntu安装omalla

par(mfrow=c(1,3)) plot(roc.full, ylim = c(-1, 2),main="FULL") plot(roc.aic, ylim = c(-1, 2),main="AIC") plot(roc.bic, ylim = c(-1, 2),main="BIC") 为何图片显示的y轴在-2到3之间？能否将y轴的范围修改到[-1,2]？

OMA-lightweightm2m

OMA DM Protocol FOMU1.0

lwm2m协议开发文档

LWM2M全称lightweight Machine to Machine，是一种物联网协议

2024-2030全球与中国硅胶婴儿用品市场现状及未来发展趋势 Sample-Li Jinpan.pdf

用于非线性模型预测控制 (NMPC) 的并行优化工具包.7z

最新资源