ETSI TS 118 130 V4.0.1 (2023-06)

oneM2M; Ontology based Interworking (oneM2M TS-0030 version 4.0.1 Release 4)

RTS/oneM2M-000030v4

General Information

• Status: Not Published
• Technical Committee: oneM2M - oneM2M
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 12-Jun-2023
• Completion Date: 08-Jun-2023

Standards Content (Sample)

ETSI TS 118 130 V4.0.1 (2023-06)






TECHNICAL SPECIFICATION
oneM2M;
Ontology based Interworking
(oneM2M TS-0030 version 4.0.1 Release 4)

---------------------- Page: 1 ----------------------
oneM2M TS-0030 version 4.0.1 Release 4 2 ETSI TS 118 130 V4.0.1 (2023-06)

Reference
RTS/oneM2M-000030v4
Keywords
M2M, ontology

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
https://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2023.
All rights reserved.

ETSI

---------------------- Page: 2 ----------------------
oneM2M TS-0030 version 4.0.1 Release 4 3 ETSI TS 118 130 V4.0.1 (2023-06)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Conventions . 8
5 Introduction to Ontology based Interworking (informative) . 8
5.1 Basic concepts of Ontology based Interworking . 8
5.1.1 Ontology based Interworking vs. Specific interworking . 8
5.1.2 Use of ontologies for Ontology based Interworking with Area Networks . 8
5.2 Using Ontology based Interworking with Device Abstraction . 10
5.2.1 General description . 10
5.2.2 An example, involving ZigBee, HAIM and SAREF . 10
5.3 Priciples of data flows . 11
5.3.1 Preconditions on the communicating entity . 11
5.3.2 Data flows for communicating with the IPE using DataPoints of a Service . 12
5.3.3 Data flows for communicating with the IPE using Operations of a Service . 14
6 Functional specification of communication with the Ontology based Interworking IPE . 16
6.1 oneM2M resources for IPE communication . 16
6.1.1 General design principles . 16
6.1.2 Resource structure for modelling devices, sub-devices, services and operations . 16
6.2 Specification of the IPE for Ontology based Interworking . 20
6.2.1 Initialization of the Ontology based Interworking IPE . 20
6.2.1.1 General functionality of a Ontology based Interworking IPE . 20
6.2.1.2 Initialization sequence of a Ontology based Interworking IPE . 20
6.2.2 Interworked Device and Service discovery . 21
6.2.2.1 General handling of Interworked Device discovery . 21
6.2.2.2 Creation of resources for the Proxied Device . 21
6.2.2.2.1 General on the creation of resources for the Proxied Device by the IPE . 21
6.2.2.2.2 Creation of resources for the Proxied Device when Interworked Devices are represented as
s . 22
6.2.2.2.3 Creation of resources for the Proxied Device when Interworked Devices are represented as
s . 22
6.2.2.3 Creation of resources for sub-devices . 23
6.2.2.4 Creation of resources for Services . 24
6.2.2.5 Creation of resources for operations of a service of a device . 25
6.2.2.5.1 Introduction . 25
6.2.2.5.2 Creation of resources for operation invocation . 25
6.2.2.5.3 Creation of resources for returning operation results . 26
6.2.2.6 Subscription to the created resources . 27
6.2.3 Handling of DataPoints by the IPE . 27
6.2.4 Handling of Operations by the IPE . 27
6.2.5 Removing of resources for Proxied Devices . 28
7 Rules for creation of XSDs from ontologies . 28
7.1 General information . 28
7.2 XSD creation rules . 28
7.2.1 General rules . 28
7.2.1.1 General principle for creating XSDs . 28
ETSI

---------------------- Page: 3 ----------------------
oneM2M TS-0030 version 4.0.1 Release 4 4 ETSI TS 118 130 V4.0.1 (2023-06)
7.2.1.2 Parameters for XSD templates . 29
7.2.1.3 Data typing for Variables . 31
7.2.1.3.1 Information on datatypes contained in the ontology. 31
7.2.1.3.2 Construction of Simple Data Types . 32
7.2.1.3.3 List Data Types. 33
7.2.1.3.4 Structured Data Types . 34
7.2.2 XSD template for sub-classes of Base Ontology class: Device . 35
7.2.3 XSD template for sub-classes of Base Ontology class: Service . 38
7.2.4 XSD template for sub-classes of Base Ontology class: Operation . 41
Annex A (informative): Example for ontology based interworking . 44
A.1 Overview . 44
A.2 XSDs created by the IPE . 46
A.2.1 XSD storage . 46
A.2.2 XSD for the Interworked Device type XYZ_Cool . 46
A.2.3 XSD for the Service type SwitchOnService . 48
A.2.4 XSD for the Service type MonitorService . 50
A.2.5 XSD for the Operation type ToggleBinary . 52
History . 54

ETSI

---------------------- Page: 4 ----------------------
oneM2M TS-0030 version 4.0.1 Release 4 5 ETSI TS 118 130 V4.0.1 (2023-06)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the
®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Technical Specification (TS) has been produced by ETSI Partnership Project oneM2M (oneM2M).
ETSI

---------------------- Page: 5 ----------------------
oneM2M TS-0030 version 4.0.1 Release 4 6 ETSI TS 118 130 V4.0.1 (2023-06)
1 Scope
The present document specifies Generic Interworking of the oneM2M System with external systems (e.g. Area
Networks containing non-oneM2M devices) that can be described with ontologies that are compliant with oneM2M's
Base Ontology, specified in ETSI TS 118 112 [3].
In oneM2M Release 2 the specification for Ontology based Interworking had been contained in clauses 8 and 9 of ETSI
TS 118 112 [3].
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 118 111: "oneM2M; Common Terminology (oneM2M TS-0011)".
[2] ETSI TS 118 101: "oneM2M; Functional Architecture (oneM2M TS-0001)".
[3] ETSI TS 118 112: "oneM2M; Base Ontology (oneM2M TS-0012)".
[4] Void.
[5] ETSI TS 118 123: "oneM2M; Home Appliances Information Model and Mapping (oneM2M
TS-0023)".
[6] ETSI TS 118 114: "oneM2M; LWM2M Interworking (oneM2M TS-0014)".
[7] ETSI TS 118 124: "onem2M; OIC Interworking (oneM2M TS-0024)".
[8] ETSI TS 118 104: "oneM2M; Service Layer Core Protocol Specification (oneM2M TS-0004)".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] oneM2M Drafting Rules.
[i.2] Smart Appliances REFerence (SAREF) ontology.
ETSI

---------------------- Page: 6 ----------------------
oneM2M TS-0030 version 4.0.1 Release 4 7 ETSI TS 118 130 V4.0.1 (2023-06)
3 Definitions of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI TS 118 111 [1], ETSI TS 118 112 [3] and the
following apply:
abstract device: virtual Device (i.e. a set of oneM2M resources together with an IPE) that allows a communicating
entity to communicate with an Interworked Device, using an Abstract Information Model, without the need to know the
technology specific Device Information Model of that Interworked Device
abstract information model: Information Model of common functionalities abstracted from a set of Device
Information Models (see ETSI TS 118 111 [1])
abstraction: process of mapping between a set of Device Information Models and an Abstract Information Model
according to a specified set of rules (see ETSI TS 118 111 [1])
abstraction application entity: specialized AE that communicates with an IPE and facilitates Abstraction by providing
Services that translate between the Abstract Information Model and the Device Information Model of the IPE
communicating entity: oneM2M entity (usually an AE) that communicates with the IPE for the purpose of
sending/receiving data from the Interworked Device
device information model: Information Model of the native protocol for the physical device (see ETSI TS 118 111 [1])
interworked device: Non-oneM2M Device Nodes (NoDN) for which communication with oneM2M entities can be
achieved via an Interworking Proxy Application Entity (IPE) (see ETSI TS 118 112 [3])
interworking proxy application entity: specialized AE that facititates interworking between Non-oneM2M Device
Nodes (NoDN) and the oneM2M System
NOTE: An IPE maps data of the NoDN into oneM2M resources (interworked devices). It invokes operations in
the NoDN when the related oneM2M resources are modified and modifies oneM2M resources based on
the output of NoDN operations (see ETSI TS 118 111 [1])
ontology based interworking: ontology based Interworking allows interworking with many types of non-oneM2M
Area Networks and Devices that are described in the form of a oneM2M compliant ontology which is derived from the
oneM2M Base Ontology (see ETSI TS 118 112 [3])
NOTE: Ontology based Interworking supports the interworking variant "full mapping of the semantic of the non-
oneM2M data model to Mca" as indicated in clause F.2 of ETSI TS 118 101 [2].
proxied device: virtual Device (i.e. a set of oneM2M resources together with an IPE) that represents the Interworked
Device in the oneM2M System (see ETSI TS 118 112 [3])
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [1], ETSI TS 118 112 [3] and
the following apply:
IPE Interworking Proxy Application Entity
NOTE: See ETSI TS 118 111 [1].
ETSI

---------------------- Page: 7 ----------------------
oneM2M TS-0030 version 4.0.1 Release 4 8 ETSI TS 118 130 V4.0.1 (2023-06)
4 Conventions
The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be
interpreted as described in the oneM2M Drafting Rules [i.1].
5 Introduction to Ontology based Interworking
(informative)
5.1 Basic concepts of Ontology based Interworking
5.1.1 Ontology based Interworking vs. Specific interworking
oneM2M supports interworking with several specific non-oneM2M solutions. Examples are: LWM2M Interworking
(ETSI TS 118 114 [6]) or OIC Interworking (ETSI TS 118 124 [7]). While these examples refer to specific technologies
oneM2M also allows to specify only data models - e.g. in ETSI TS 118 123 [5] - which does not assume that a specific
technology is used. The data model in ETSI TS 118 123 could e.g. be implemented with 'native' oneM2M entities like
ASNs, ADNs and MNs or it could just as well be implemented in a non-oneM2M solution that is interworked with
oneM2M via an Interworking Proxy Application Entity (IPE).
Ontology based Interworking is taking an approach similar to ETSI TS 118 123 [5], however in this case the data model
is not specified but can flexibly be provided in form of an ontology. That ontology needs to be formally described
(e.g. in OWL format).
Ontology based Interworking can be used in cases where oneM2M does not provide a standardized datamodel but still
interworking is desired. Such a situation may arise if e.g. a company wants to publish their proprietary datamodel for
interworking purposes but does not wish to reveal their proprietary technology (radio technology, communication
protocol) for data transmission.
For Ontology based Interworking the ontology that describes the data model of the interworked technology needs to be
provided in the oneM2M solution. This ontology enables the IPE to create specific resourcetypes (specializations of
), through dynamically created XSDs that are derived from the ontology.
From these resourcetypes oneM2M resources are created by the IPE for communication of oneM2M communicating
entities with the IPE.
As with any other form of interworking, the IPE provides the translation of data in these resources into/from the
external technology.
5.1.2 Use of ontologies for Ontology based Interworking with Area
Networks
Interworking with Area Networks is accomplished in oneM2M through functionality provided by Interworking Proxy
Entities (IPEs).
ETSI

---------------------- Page: 8 ----------------------
oneM2M TS-0030 version 4.0.1 Release 4 9 ETSI TS 118 130 V4.0.1 (2023-06)
Area Network
oneM2M compliant
(e.g. KNX)
Solution
Proxied Devices (oneM2M resources)
Interworked Devices (physical
in the oneM2M System technology
devices) in the Area Network
Inter
working
Proxy
Entity
Communicating
entity

Figure 1: Interworking
The IPE creates "proxied" devices as oneM2M Resources (e.g. AEs) in the oneM2M Solution that can be accessed by
communicating entities (e.g. oneM2M Applications) in the usual way.
To accomplish the creation of proxied devices the IPE uses an ontology that describes the Device Information Model of
the interworked Area Network and its entities (device types, their operations, etc.).
EXAMPLE 1: In figure 1, an ontology that describes a KNX Area Network and its entities would be needed.
To achieve the flexibility for the IPE to create proxied devices for many different types of Area Networks each ontology
that describes a specific Device Information Model needs to be derived from the Base Ontology that is specified in
ETSI TS 118 112 [3]. This allows to specify a common scheme of mapping the classes of the ontology that describes
the Device Information Model into oneM2M resources (see clause 7).
EXAMPLE 2: The OWL representation of an ontology that describes the Device Information Model of an Area
Network of type "KNX" needs to:
a) contain an 'include' statement which includes Base Ontology;
b) the Class of "KNX Nodes" needs to be a subclass of the "Device" Class of oneM2M's Base
Ontology;
c) the Class of "KNX Communication Objects" needs to be a subclass of the "Service" Class of
the Base Ontology;
d) etc.
NOTE: For the purpose of Ontology based Interworking with Area Networks the Base Ontology is only used to
describe type information and not for describing instances of these types. E.g. the Base Ontology
describes the type "Device", but does not contain information about a specific device.The Base Ontology
therefore only contains Classes and Properties but not instances.
That principle needs to be followed by the ontology that describes the Device Information Model.
ETSI
REST-ful Resource access

---------------------- Page: 9 ----------------------
oneM2M TS-0030 version 4.0.1 Release 4 10 ETSI TS 118 130 V4.0.1 (2023-06)
5.2 Using Ontology based Interworking with Device Abstraction
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
provide oneM2M resources (Proxied Devices) to the communicating entities for communication with the Interworked
Devices. However these Proxied Devices still exhibit the native data model - the Device Information Model of the
external technology of the device - and a communicating entity needs to know that native Device Information Model
(e.g. ZigBee, KNX, information model).
Device abstraction relieves a communicating entity that wants to communicate with an Interworked Device (e.g. a
ZigBee device) from the need to know the native Device Information Model of that Interworked Device.
Additionally to providing interworking, the IPE may translate between the - technology specific - native Device
Information Model and an Abstract Information Model, that is based on of common functionalities abstracted from a set
of Device Information Models. Such Abstract Information Models can be provided by industry associations of a
specific industry sector. An example of an Abstract Information Model, which is specified in oneM2M is the Home
Appliance Information Model (HAIM), specified in ETSI TS 118 123 [5].
As in the case of a native Device Information Model that is used by the IPE also an Abstract Information Model can be
described by an ontology and that ontology needs to be derived from the Base Ontology.
5.2.2 An example, involving ZigBee, HAIM and SAREF
Figure 2 illustrates this situation for a light switch. In the example the physical implementation is a ZigBee device
implementing a ZigBee Service "On/Off Cluster". An IPE for ZigBee creates the interworking towards the ZigBee
network.
To enable abstraction, this device is abstracted as oneM2M device according to the Home Appliance Information Model
(HAIM). In HAIM the corresponding Service is a "binary Switch".
Both types of Services expose a Function "On Off Function" which is e.g. described in the SAREF ontology.
To turn the switch on SAREF defines an "On Command".
The corresponding Service in HAIM is executed by setting an Input Datapoint called "powerState" to the binary value
"TRUE".
In Zigbee an operation (ZigBee command) needs to be invoked in the On/Off Cluster with an input parameter (ZigBee
Command ID) equal to 0.
A VariableConversion can been specified in the ontology of the ZigBee Device Information Model that contains the
rules how to convert a value of InputDataPoint "powerState" into a value of OperationInput "ZigBee Command ID".
ETSI

---------------------- Page: 10 ----------------------
oneM2M TS-0030 version 4.0.1 Release 4 11 ETSI TS 118 130 V4.0.1 (2023-06)
ontology of the Device Information Model ontology of the Abstract Information Model
(example ZigBee) (example: HAIM)
Device Device
type_DD type_DA
hasFunction
hasService hasFunction hasService
exposes exposes
Function
Function
Service Function Service
“binary Switch”
“On/Off Cl
...