ETSI TS 118 113 V2.3.2 (2020-04)

oneM2M; Interoperability Testing (oneM2M TS-0013 version 2.3.2 Release 2A)

RTS/oneM2M-000013v2A

General Information

• Status: Published
• Publication Date: 31-Mar-2020
• Technical Committee: oneM2M - oneM2M
• Current Stage: 12 - Completion
• Due Date: 03-Mar-2020
• Completion Date: 01-Apr-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
oneM2M;
Interoperability Testing
(oneM2M TS-0013 version 2.3.2 Release 2A)

oneM2M TS-0013 version 2.3.2 Release 2A 2 ETSI TS 118 113 V2.3.2 (2020-04)

Reference
RTS/oneM2M-000013v2A
Keywords
interoperability, IoT, M2M, protocol

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

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://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
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 2020.
All rights reserved.
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.
ETSI
oneM2M TS-0013 version 2.3.2 Release 2A 3 ETSI TS 118 113 V2.3.2 (2020-04)
Contents
Intellectual Property Rights . 7
Foreword . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 8
3 Definition of terms, symbols and abbreviations . 9
3.1 Terms . 9
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Conventions . 10
5 Testing conventions . 10
5.1 The Test Description proforma . 10
5.2 Test Description naming convention . 11
5.3 Test Settings . 12
5.4 Pre-conditions . 12
5.4.1 Registration . 12
5.4.2 Security . 12
5.4.3 Service Subscription . 12
5.4.4 ID allocation . 12
5.4.5 Existence of resource . 13
5.4.6 Management Session between Management Server and Management Client . 13
5.5 Binding message convention . 13
6 Test Description Summary . 14
6.1 Tests list . 14
7 Configuration . 17
7.1 Test Configuration . 17
7.1.1 No hop . 17
7.1.1.1 M2M_CFG_01 . 17
7.1.1.2 M2M_CFG_02 . 17
7.1.2 Single hop . 18
7.1.2.1 M2M_CFG_03 . 18
7.1.2.2 M2M_CFG_04 . 18
7.1.2.3 M2M_CFG_05 . 18
7.1.2.4 M2M_CFG_08 . 18
7.1.2.5 M2M_CFG_09 . 19
7.1.3 Multi hops . 19
7.1.3.1 M2M_CFG_06 . 19
7.1.3.2 M2M_CFG_07 . 20
8 Test Descriptions . 20
8.1 No Hop configuration testing . 20
8.1.1 CSEBase Management . 20
8.1.1.1 CSEBase Retrieve on Mca . 20
8.1.2 RemoteCSE Management . 21
8.1.2.1 RemoteCSE Create. 21
8.1.2.2 remoteCSE Retrieve . 21
8.1.2.3 remoteCSE Update . 22
8.1.2.4 remoteCSE Delete . 22
8.1.3 Application Entity Registration . 23
8.1.3.1 AE Create . 23
8.1.3.2 AE Retrieve . 23
8.1.3.3 AE Update . 24
ETSI
oneM2M TS-0013 version 2.3.2 Release 2A 4 ETSI TS 118 113 V2.3.2 (2020-04)
8.1.3.4 AE Delete . 24
8.1.4 Container Management . 25
8.1.4.1 Container Create . 25
8.1.4.2 Container Retrieve . 25
8.1.4.3 Container Update . 26
8.1.4.4 Container Delete . 26
8.1.5 ContentInstance Management . 27
8.1.5.1 ContentInstance Create . 27
8.1.5.2 ContentInstance Retrieve . 27
8.1.5.3 ContentInstance Delete . 28
8.1.5.4 ContentInstance Delete. 29
8.1.5.5 ContentInstance Delete . 29
8.1.5.6 ContentInstance Create when currentNrOfInstance equals to maxNrOfInstances in parent
resource . 30
8.1.5.7 ContentInstance Retrieve . 31
8.1.5.8 ContentInstance Retrieve . 31
8.1.6 Discovery . 32
8.1.6.1 Discovery of all resources . 32
8.1.6.2 Discovery with label filter criteria . 32
8.1.6.3 Discovery with limit filter criteria . 33
8.1.6.4 Discovery with multiple filter criteria . 33
8.1.6.5 Discovery with level filter criteria . 34
8.1.6.6 Discovery with offset filter criteria . 36
8.1.7 Subscription Management . 38
8.1.7.1 Subscription Create . 38
8.1.7.2 Subscription Retrieve . 38
8.1.7.3 Subscription Update . 39
8.1.7.4 Subscription Delete . 39
8.1.8 accessControlPolicy Management . 40
8.1.8.1 accessControlPolicy Create . 40
8.1.8.2 accessControlPolicy Retrieve . 40
8.1.8.3 accessControlPolicy Update . 41
8.1.8.4 accessControlPolicy Delete . 41
8.1.8.5 Unauthorized operation (Insufficient Access Rights, operations) . 42
8.1.8.6 Unauthorized operation (Insufficient Access Rights, originators) . 42
8.1.8.7 Authorized operation . 43
8.1.9 Group Management . 44
8.1.9.1 Group Retrieve . 44
8.1.9.2 Group Create . 44
8.1.9.3 Group Update . 45
8.1.9.4 Group Delete . 45
8.1.10 Node Management . 46
8.1.10.1 Node Create. 46
8.1.10.2 Node Retrieve . 46
8.1.10.3 Node Update . 47
8.1.10.4 Node Delete. 47
8.1.11 PollingChannel Management . 48
8.1.11.1 PollingChannel Create . 48
8.1.11.2 PollingChannel Retrieve . 48
8.1.11.3 pollingChannel Update . 49
8.1.11.4 pollingChannel Delete . 49
8.1.11.5 Long Polling on a PollingChannel Retrieve . 50
8.1.12 FanoutPoint Management . 50
8.1.12.1 FanoutPoint Create . 50
8.1.12.2 FanoutPoint Retrieve . 51
8.1.12.3 FanoutPoint Update . 51
8.1.12.4 FanoutPoint Delete . 52
8.1.13 Notification Management . 52
8.1.13.1 Notification . 52
8.1.14 FlexContainer Management . 53
8.1.14.1 FlexContainer Create . 53
8.1.14.2 FlexContainer Retrieve . 53
ETSI
oneM2M TS-0013 version 2.3.2 Release 2A 5 ETSI TS 118 113 V2.3.2 (2020-04)
8.1.14.3 FlexContainer Update . 54
8.1.14.4 FlexContainer Delete . 54
8.1.14.5 Notification Create . 55
8.1.14.6 Discovery with attribute filter criteria over custo mAttribute s . 55
8.1.15 External Management Operations Management . 56
8.1.15.1 mgmtCmd Create . 56
8.1.15.2 mgmtCmd Retrieve . 56
8.1.15.3 mgmtCmd Update (Normal) . 57
8.1.15.4 mgmtCmd Update (Execute) . 57
8.1.15.5 mgmtCmd Delete . 58
8.1.15.6 execInstance Retrieve . 58
8.1.15.7 execInstance Update (Cancel) . 59
8.1.15.8 execInstance Delete . 59
8.1.16 SemanticDescriptor Management . 60
8.1.16.1 SemanticDescriptor Create . 60
8.1.16.2 SemanticDescriptor Retrieve. 60
8.1.16.3 SemanticDescriptor Update. 61
8.1.16.4 SemanticDescriptor Delete . 61
8.1.17 Semantic Resource Discovery . 62
8.1.17.1 Discovery with semanticFilter filter criteria . 62
8.2 Non-blocking configuration testing . 62
8.2.1 Synchronous request . 62
8.2.1.1 Container management . 62
8.2.1.1.1 Container Create . 62
8.2.1.1.2 Container Retrieve . 63
8.2.1.1.3 Container Update . 64
8.2.1.1.4 Container Delete . 65
8.2.2 Asynchronous request . 66
8.2.2.1 Container management . 66
8.2.2.1.1 Container Create . 66
8.2.2.1.2 Container Retrieve . 67
8.2.2.1.3 Container Update . 68
8.2.2.1.4 Container Delete . 69
8.3 Single hop configuration testing . 70
8.3.1 Retargeting . 70
8.3.1.1 RetargetingResource Create (Generic Test Description) . 70
8.3.1.2 Create . 71
8.3.1.3 Resource Retrieve (Generic Test Description) . 71
8.3.1.4 retrieve . 72
8.3.1.5 Resource Update (Generic Test Description) . 73
8.3.1.6 update . 73
8.3.1.7 Resource Delete (Generic Test Description) . 74
8.3.1.8 delete . 75
8.3.1.9 Discovery with multiple filter criteria . 76
8.3.1.10 Unauthorized operation (Insufficient Access Rights) . 77
8.3.1.11 Notification . 78
8.3.2 Test Description . 79
8.3.2.1 Create . 79
8.3.2.2 Update . 80
8.3.2.3 Retrieve . 81
8.3.2.4 Delete . 81
8.3.3 Announcement Management . 82
8.3.3.1 AEAnnc Create . 82
8.3.3.2 ContainerAnnc Create . 83
8.3.3.3 ContainerAnnc Update . 84
8.3.3.4 ContainerAnnc Retrieve . 84
8.3.3.5 ContainerAnnc Retrieve Original . 85
8.3.4 Single Hop operations . 86
8.3.4.1 Create . 86
8.3.4.2 Retrieve . 86
8.3.4.3 Update . 87
8.3.4.4 Delete . 88
ETSI
oneM2M TS-0013 version 2.3.2 Release 2A 6 ETSI TS 118 113 V2.3.2 (2020-04)
8.4 Secure AE Registration . 89
8.4.1 PSK Security Association Establishment Framework . 89
History . 90

ETSI
oneM2M TS-0013 version 2.3.2 Release 2A 7 ETSI TS 118 113 V2.3.2 (2020-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 IPR Policy, no investigation, 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.
Foreword
This Technical Specification (TS) has been produced by ETSI Partnership Project oneM2M (oneM2M).
ETSI
oneM2M TS-0013 version 2.3.2 Release 2A 8 ETSI TS 118 113 V2.3.2 (2020-04)
1 Scope
The present document specifies Interoperability Test Descriptions (TDs) for the oneM2M Primitives as specified in
ETSI TS 118 101 [1], ETSI TS 118 104 [2], the bindings ETSI TS 118 108 [3], ETSI TS 118 109 [4] and ETSI
TS 118 110 [5].
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 101: "oneM2M; Functional Architecture (oneM2M TS-0001 Release 2)".
[2] ETSI TS 118 104: "oneM2M; Service Layer Core Protocol Specification (oneM2M TS-0004
Release 2)".
[3] ETSI TS 118 108: "oneM2M; CoAP Protocol Binding (oneM2M TS-0008 Release 2A)".
[4] ETSI TS 118 109: "oneM2M; HTTP Protocol Binding (oneM2M TS-0009 Release 2A)".
[5] ETSI TS 118 110: "oneM2M; MQTT Protocol Binding (oneM2M TS-0010 Release 2)".
[6] ETSI TS 118 115: "oneM2M; Testing Framework (oneM2M TS-0015 Release 2)".
[7] ETSI TS 118 111: "oneM2M; Common Terminology (oneM2M TS-0011 Release 2)".
[8] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
[9] IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing".
[10] ETSI TS 118 105: "oneM2M; Management Enablement (OMA) (oneM2M TS-0005 Release 2A)".
[11] ETSI TS 118 106: "oneM2M; Management Enablement (BBF) (oneM2M TS-0006 Release 2A)".
[12] ETSI TS 118 103: "oneM2M; Security solutions (oneM2M TS-0003 Release 2A)".
[13] oneM2M TS-0034: "Semantics Support - Release 3".
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.
ETSI
oneM2M TS-0013 version 2.3.2 Release 2A 9 ETSI TS 118 113 V2.3.2 (2020-04)
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.
NOTE: Available at http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf.
[i.2] BBF TR-069: "CPE WAN Management Protocol".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI TS 118 111 [7] and the following apply:
NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in
ETSI TS 118 111 [7].
hosting CSE: CSE where the addressed resource is hosted
M2M service provider domain: part of the M2M System that is associated with a specific M2M Service Provider
mc: interface between the management server and the management client
NOTE: This interface can be realized by the existing device management technologies such as BBF TR-069 [i.2],
OMA DM [10], etc.
receiver CSE: any CSE that receives a request
registrar CSE: CSE where an Application or another CSE has registered
registree: AE or CSE that registers with another CSE
resource: uniquely addressable entity in oneM2M architecture
transit CSE: any receiver CSE that is not a Hosting CSE
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACP Access Control Policy
AE Application Entity
AE-ID Application Entity Identifier
APP-ID Application Identifier
BBF BroadBand Forum
CFG Configuration
CoAP Constrained Application Protocol
CSE Common Services Entity
CSE-ID Common Service Entity Identifier
DM Device Management
DTLS Datagram Transport Layer Security
DUT Device Under Test
HTTP HyperText Transfer Protocol
IN Infrastructure Node
IN-CSE CSE which resides in the Infrastructure Node
ETSI
oneM2M TS-0013 version 2.3.2 Release 2A 10 ETSI TS 118 113 V2.3.2 (2020-04)
IOP Interoperability
IP Internet Protocol
JSON JavaScript Object Notation
LWM2M Lightweight M2M
M2M Machine to Machine
MA Mandatory Announced
Mca Reference Point for M2M Communication with AE
Mcc Reference Point for M2M Communication with CSE
MH Multi Hop
MO Management Object
MQTT Message Queuing Telemetry Transport
NB Non-Blocking
NH No Hop
OMA Open Mobile Alliance
PRO Protocol
PSK Pre-Shared Key
RFC Request For Comments
RP Reference Point
RPC Remote Procedure Calls
RQI Request-ID
SE Security
SH Single Hop
SP Service Provider
SUT System Under Test
TCP Transmission Control Protocol
TD Test Description
TLS Transport Layer Security
UDP User Datagram Protocol
URI Uniform Resource Identifier
XML eXtensible Markup Language
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 Testing conventions
5.1 The Test Description proforma
The testing methodology used in the present document is specified in ETSI TS 118 115 [6].
A Test Description (TD) is a well detailed description of a process that aims to test one or more functionalities of an
implementation. Applying to interoperability testing, these testing objectives address the interoperable functionalities
between two or more vendor implementations.
In order to ensure the correct execution of an interoperability test, the following information should be provided by the
test description:
• The proper configuration of the vendor implementations.
• The availability of additional equipment (protocol monitors, functional equipment, etc.) required to achieve the
correct behaviour of the vendor implementations.
• The correct initial conditions.
• The correct sequence of the test events and test results.
ETSI
oneM2M TS-0013 version 2.3.2 Release 2A 11 ETSI TS 118 113 V2.3.2 (2020-04)
In order to facilitate the specification of test cases an interoperability test description should include, at a minimum, the
following fields as indicated table 5.1-1.
Table 5.1-1: Interoperability test description
Identifier A unique test description ID.
Objective A concise summary of the test which should reflect the purpose of the test and enable
readers to easily distinguish this test from any other test in the document.
References A list of references to the base specification section(s), use case(s), requirement(s) and
TP(s) which are either used in the test or define the functionality being tested.
Applicability A list of features and capabilities which are required to be supported by the SUT in order to
execute this test (e.g. if this list contains an optional feature to be supported, then the test is
optional).
Configuration or A list of all required equipment for testing and possibly also including a reference to an
Architecture illustration of a test architecture or test configuration.
Pre-Test Conditions A list of test specific pre-conditions that need to be met by the SUT including information
about equipment configuration, i.e. precise description of the initial state of the SUT
required to start executing the test sequence.
Test Sequence An ordered list of equipment operation and observations. The test sequence may also
contain the conformance checks as part of the observations.

The test descriptions are provided in proforma tables. In order to ensure the correct execution of an interoperability test,
the following information is provided in the test description:
• The configuration applied for the test.
• The need of additional equipment (protocol monitors, functional equipment, etc.) required to achieve the
correct behaviour of the implementations.
• The initial conditions.
• The sequence of the test events and test results.
The following different types of test operator actions are considered during the test execution:
• A stimulus corresponds to an event that enforces a DUT to proceed with a specific protocol action, such as
sending a message.
• A configure corresponds to an action to modify the DUT configuration.
• An IOP check consists of observing that one DUT behaves as described in the standard: i.e. resource creation,
update, deletion, etc. For each IOP check in the Test Sequence, a result can be recorded. The overall IOP
Verdict will be considered OK if all the IOP checks in the sequence are OK.
• In the context of Interoperability Testing with Conformance Checks, an additional step type, PRO checks can
be used to verify the appropriate sequence and contents of protocol messages, this is helpful for debugging
purposes. PRO Verdict will be PASS if all the PRO checks are PASS.
5.2 Test Description naming convention
TD///
= root M2M oneM2M
= group NH No Hop: Testing on Mca reference point
NB Non-Blocking scenario
Single Hop: management of remote resources
SH
on Mca + Mcc
MH Multi Hop
SE Security
= sequential number 01 to 99

ETSI
oneM2M TS-0013 version 2.3.2 Release 2A 12 ETSI TS 118 113 V2.3.2 (2020-04)
5.3 Test Settings
This clause contains some test requirements applied to the testing, some constraints, restrictions for executions or some
recommendations.
In order to ease test setup and execution, the CSE and AE are requested to support the following settings:
• Security shall be disable as it is out of scope of this interoperability testing.
• Resource names are pre-provisioned, except for content instance resources that are automatically assigned by
the hosting CSE.
• After each "Delete" primitive on a resource, the user shall check the resource is effectively deleted.
• Unless it is indicated in the test cases prerequisites by default, all the applications shall have the required
access rights to manage resources on the CSE.
In order to address the TBDs in the oneM2M CoAP binding specification (ETSI TS 118 108 [3]), basic XML and JSON
media-type numbers shall be used in the contentFormat option.
In the test descriptions specified below, the following definitions of terms used for short-hand notation apply:
Serialized Representation: refers to either an XML or a JSON representation of data in text-string format as
defined in clauses 8.3 and 8.4 of ETSI TS 118 104 [2].
Host Address: refers to the authority part of a target URI as defined in IETF RFC 3986 [8] and IETF
RFC 7230 [9] which can be represented as an IP literal encapsulated within square
brackets, an IPv4 address in dotted decimal form, or a registered name, and optionally
extended by a port identifier.
5.4 Pre-conditions
5.4.1 Registration
The AE or CSE that originates the request has been successfully registered to its corresponding CSE. The registration of
the AE includes the creation of resource under the of its registrar CSE. The registration of the CSE
includes the creation of resource representing itself under the of its registrar CSE as well as
the creation of resource representing the registrar CSE under its own resource. The creation
of resource representing the registrar CSE can be achieved by remotely retrieving the
resource of the registrar CSE.
5.4.2 Security
The Originator and
...