oneM2M TS-0033

Release Notes

Fri, 18 Sep 2026 07:59:21 +0000

Navigate through the changes at:

Onlne Release Notes for version v5.0.1 compared to v5.0.1

Download Release Notes for TS-0033 ve...

Download

Fri, 18 Sep 2026 07:59:21 +0000

Download baseline for TS-0033 version v5.0.1:

Hanging paragraph

Fri, 18 Sep 2026 07:59:21 +0000

Editor note: This is a hanging paragraph and it must be moved to its own clause This clause specifies the procedures for managing device capabil...

8.3 Specific DM SDT modules management

Fri, 18 Sep 2026 07:59:21 +0000

8.3.1 Resource [dmDeviceInfo ]

8.3.1.1 Introduction

The detailed description of the [dmDeviceInfo] resource can be found in clause 5.8.4 of th...

8.2 Generic DM SDT modules management

Fri, 18 Sep 2026 07:59:21 +0000

!!! note This clause defines generic guidelines for handling all DM SDT modules; clause 8.3. will add detailed information for each specific module.

...

8.1 [_flexNode_] management

Fri, 18 Sep 2026 07:59:21 +0000

8.1.1 Create [flexNode]

This procedure shall be used for creating a [flexNode] resource.

Table 8.1.1-1: [flexNode] CREATE<a name="table_8.1.1...

7

Fri, 18 Sep 2026 07:59:21 +0000

7.3 Representation of non-oneM2M Proximal IoT Services

Fri, 18 Sep 2026 07:59:21 +0000

oneM2M defines different types of resources that may be used to represent services provided by a device. When representing non-oneM2M Proximal IoT services f...

7.2 Representation of non-oneM2M Proximal IoT Applications

Fri, 18 Sep 2026 07:59:21 +0000

A general pattern in oneM2M is the use of instances of an <AE> resource to represent applications running on devices/gateways if needed. In addition, al...

7.1 Representation of non-oneM2M Proximal IoT Devices

Fri, 18 Sep 2026 07:59:21 +0000

From a device management perspective in oneM2M, a device is represented using a <node> resource. All management related capabilities of a device are the...

6

Fri, 18 Sep 2026 07:59:21 +0000

6.2 Role of IPE(s)

Fri, 18 Sep 2026 07:59:21 +0000

6.2.1 Fit with the Functional Architecture

oneM2M is using an Interworking Proxy Entity (IPE) to handle the interworking between the oneM2M system and e...

6.1 Concept of Representation

Fri, 18 Sep 2026 07:59:21 +0000

In the oneM2M system, any kind of device, application or service or more generally speaking any kind of function that needs to be exposed to oneM2M-specified...

5 Introduction

Fri, 18 Sep 2026 07:59:21 +0000

The scope of Proximal IoT Interworking is to enable the exchange of information between different things, devices and applications and the use of services th...

4 Conventions

Fri, 18 Sep 2026 07:59:21 +0000

The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in this document are to be interpreted as described in the oneM2M Drafting Rule...

3

Fri, 18 Sep 2026 07:59:21 +0000

3.2 Abbreviations

Fri, 18 Sep 2026 07:59:21 +0000

For the purposes of the present document, the abbreviations given in oneM2M TS-0011 [1] and the following apply:

`DM Device Management...

3.1 Definitions

Fri, 18 Sep 2026 07:59:21 +0000

For the purposes of the present document, the terms and definitions given in oneM2M TS-0011 [1], oneM2M TS0002 [7] an...

2

Fri, 18 Sep 2026 07:59:21 +0000

2.2 Informative references

Fri, 18 Sep 2026 07:59:21 +0000

References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the ...