oneM2M TS-0030

Release Notes

Fri, 10 Jul 2026 16:27:42 +0000

Navigate through the changes at:

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

Download Release Notes for TS-0030 ve...

Download

Fri, 10 Jul 2026 16:27:42 +0000

Download baseline for TS-0030 version v5.0.0:

A.2

Fri, 10 Jul 2026 16:27:42 +0000

A.2.5 XSD for the Operation type ToggleBinary

Fri, 10 Jul 2026 16:27:42 +0000

Following the principles of clause 7.2.3 a Service is represented as <flexContainer>.

According to the the convention in table 7.2.1.2-1 the placeholde...

A.2.4 XSD for the Service type MonitorService

Fri, 10 Jul 2026 16:27:42 +0000

Following the principles of clause 7.2.3 a Service is represented as <flexContainer>.

According to the the convention in table 7.2.1.2-1 the placeholde...

A.2.3 XSD for the Service type SwitchOnService

Fri, 10 Jul 2026 16:27:42 +0000

Following the principles of clause 7.2.3 a Service is represented as <flexContainer>.

According to the the convention in table 7.2.1.2-1 the placeholde...

A.2.2 XSD for the Interworked Device type XYZ\_Cool

Fri, 10 Jul 2026 16:27:42 +0000

Following the principles of clause 7.2.2 an Interworked Device is represented as <flexContainer>.

According to the the convention in table 7.2.1.2-1 th...

A.2.1 XSD storage <_container >

Fri, 10 Jul 2026 16:27:42 +0000

According to clause 7.2.1.1 the IPE creates a <container> resource that acts as a XSD-storage and that is a child resource of the IPE's <AE> .

Der...

A.1 Overview

Fri, 10 Jul 2026 16:27:42 +0000

This example extends the example - a (simplified) washing machine - of clause B.1.3.3 of oneM2M TS-0012 [3].
However in con...

7

Fri, 10 Jul 2026 16:27:42 +0000

7.2 XSD creation rules

Fri, 10 Jul 2026 16:27:42 +0000

7.2.1 General rules

7.2.1.1 General principle for creating XSDs

During initialization (clause 6.2.1) a Ontology-based Interworking IPE creates XSD...

7.1 General information

Fri, 10 Jul 2026 16:27:41 +0000

When the non-oneM2M data model is described in the form of a oneM2M compliant ontology which is derived (as sub-classes and sub-properties) from the oneM2M B...

6

Fri, 10 Jul 2026 16:27:41 +0000

6.2 Specification of the IPE for Ontology-based Interworking

Fri, 10 Jul 2026 16:27:41 +0000

6.2.1 Initialization of the Ontology-based Interworking IPE

6.2.1.1 General functionality of a Ontology-based Interworking IPE

Ontology-based Inte...

6.1 oneM2M resources for IPE communication

Fri, 10 Jul 2026 16:27:41 +0000

6.1.1 General design principles

For Ontology-based Interworking the oneM2M resource types <AE > and specializations of <flexContainer > are in...

5

Fri, 10 Jul 2026 16:27:41 +0000

5.3 Principles of data flows

Fri, 10 Jul 2026 16:27:41 +0000

5.3.1 Preconditions on the communicating entity

Data flows between a communicating entity and the IPE involve oneM2M resources - specialized _<flexCo...

5.2 Using Ontology-based Interworking with Device Abstraction

Fri, 10 Jul 2026 16:27:41 +0000

5.2.1 General description

As explained in clause 5.1 it is the task of an IPE to interact via the Area Network with the Interworked Devices and to provi...

5.1 Basic concepts of Ontology-based Interworking

Fri, 10 Jul 2026 16:27:41 +0000

5.1.1 Ontology-based Interworking vs. specific interworking

oneM2M supports interworking with several specific non-oneM2M solutions. Examples are: LWM2M...

4 Conventions

Fri, 10 Jul 2026 16:27:41 +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...