ETSI TS 118 113 V1.0.0 (2016-03)

oneM2M; Interoperability Testing (oneM2M TS-0013 version 1.0.0 Release 1)

DTS/oneM2M-000013

General Information

• Status: Published
• Publication Date: 17-Mar-2016
• Technical Committee: oneM2M - oneM2M
• Current Stage: 12 - Completion
• Due Date: 30-Mar-2016
• Completion Date: 18-Mar-2016

Standards Content (Sample)

ETSI TS 118 113 V1.0.0 (2016-03)






TECHNICAL SPECIFICATION
oneM2M;
Interoperability Testing
(oneM2M TS-0013 version 1.0.0 Release 1)

---------------------- Page: 1 ----------------------
oneM2M TS-0013 version 1.0.0 Release 1 2 ETSI TS 118 113 V1.0.0 (2016-03)



Reference
DTS/oneM2M-000013
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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
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.

© European Telecommunications Standards Institute 2016.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
oneM2M TS-0013 version 1.0.0 Release 1 3 ETSI TS 118 113 V1.0.0 (2016-03)
Contents
Intellectual Property Rights . 6
Foreword . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Conventions . 9
5 Testing conventions . 9
5.1 The Test Description proforma . 9
5.2 Test Description naming convention . 10
5.3 Test Settings . 10
5.4 Pre-conditions . 11
5.4.1 Registration . 11
5.4.2 Security . 11
5.4.3 Service Subscription . 11
5.4.4 ID allocation . 11
5.4.5 Existence of resource . 11
5.4.6 Management Session between Management Server and Management Client . 11
5.5 Binding message convention . 11
6 Test Description Summary . 12
6.1 Tests list . 12
7 Configuration . 14
7.1 Test Configuration . 14
7.1.1 No hop . 14
7.1.1.1 M2M_CFG_01 . 14
7.1.1.2 M2M_CFG_02 . 14
7.1.2 Single hop . 14
7.1.1.1 M2M_CFG_03 . 14
7.1.2.2 M2M_CFG_04 . 15
7.1.2.3 M2M_CFG_05 . 15
7.1.2.4 M2M_CFG_08 . 15
7.1.2.5 M2M_CFG_09 . 16
7.1.3 Multi hops . 16
7.1.3.1 M2M_CFG_06 . 16
7.1.3.2 M2M_CFG_07 . 16
8 Test Descriptions . 17
8.1 No Hop configuration testing . 17
8.1.1 CSEBase Management . 17
8.1.1.1 CSEBase Retrieve on Mca . 17
8.1.2 RemoteCSE Management . 18
8.1.2.1 RemoteCSE Create. 18
8.1.2.2 remoteCSE Retrieve . 20
8.1.2.3 remoteCSE Update . 21
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 . 25
8.1.3.3 AE Update . 26
8.1.3.4 AE Delete . 27
8.1.4 Container Management . 28
ETSI

---------------------- Page: 3 ----------------------
oneM2M TS-0013 version 1.0.0 Release 1 4 ETSI TS 118 113 V1.0.0 (2016-03)
8.1.4.1 Container Create . 28
8.1.4.2 Container Retrieve . 30
8.1.4.3 Container Update . 31
8.1.4.4 Container Delete . 32
8.1.5 ContentInstance Management . 33
8.1.5.1 ContentInstance Create . 33
8.1.5.2 ContentInstance Retrieve . 34
8.1.5.3 ContentInstance Delete . 35
8.1.6 Discovery . 37
8.1.6.1 Discovery of all resources . 37
8.1.6.2 Discovery with label filter criteria . 38
8.1.6.3 Discovery with limit filter criteria . 39
8.1.6.4 Discovery with multiple filter criteria . 41
8.1.7 Subscription Management . 42
8.1.7.1 Subscription Create . 42
8.1.7.2 Subscription Retrieve . 43
8.1.7.3 Subscription Update . 45
8.1.7.4 Subscription Delete . 46
8.1.8 accessControlPolicy Management . 47
8.1.8.1 accessControlPolicy Create . 47
8.1.8.2 accessControlPolicy Retrieve . 48
8.1.8.3 accessControlPolicy Update . 50
8.1.8.4 accessControlPolicy Delete . 51
8.1.8.5 Unauthorized operation (Insufficient Access Rights) . 52
8.1.9 Group Management . 53
8.1.9.1 . 53
8.1.9.2 Group Create . 55
8.1.9.3 Group Update . 56
8.1.9.4 Group Delete . 57
8.1.10 Node Management . 58
8.1.10.1 Node Create. 58
8.1.10.2 Node Retrieve . 59
8.1.10.3 Node Update . 60
8.1.10.4 Node Delete. 62
8.1.11 PollingChannel Management . 63
8.1.11.1 PollingChannel Create . 63
8.1.11.2 PollingChannel Retrieve . 64
8.1.11.3 pollingChannel Update . 65
8.1.11.4 pollingChannel Delete . 66
8.1.11.5 Long Polling on a PollingChannel Retrieve . 67
8.1.12 FanoutPoint Management . 68
8.1.12.1 FanoutPoint Create . 68
8.1.12.2 FanoutPoint Retrieve . 70
8.1.12.3 FanoutPoint Update . 71
8.1.12.4 FanoutPoint Delete . 72
8.1.13 Notifcation Management . 73
8.1.13.1 Notification Create . 73
8.2 Non blocking configuration testing . 74
8.2.1 Synchronous request . 74
8.2.1.1 Container management . 74
8.2.1.1.1 Container Create . 74
8.2.1.1.2 Container Retrieve . 77
8.2.1.1.3 Container Update . 79
8.2.1.1.4 Container Delete . 81
8.2.2 Asynchronous request . 83
8.2.2.1 Container management . 83
8.2.2.1.1 Container Create . 83
8.2.2.1.2 Container Retrieve . 86
8.2.2.1.3 Container Update . 88
8.2.2.1.4 Container Delete . 90
8.3 Single hop configuration testing . 92
8.3.1 Retargeting . 92
ETSI

---------------------- Page: 4 ----------------------
oneM2M TS-0013 version 1.0.0 Release 1 5 ETSI TS 118 113 V1.0.0 (2016-03)
8.3.1.1 RetargetingResource Create (Generic Test Description) . 92
8.3.1.2 Create . 94
8.3.1.3 Resource Retrieve (Generic Test Description) . 95
8.3.1.4 retrieve . 97
8.3.1.5 Resource Update (Generic Test Description) . 99
8.3.1.6 update . 101
8.3.1.7 Resource Delete (Generic Test Description) . 101
8.3.1.8 delete . 103
8.3.1.9 Discovery with multiple filter criteria . 104
8.3.1.10 Unauthorized operation (Insufficient Access Rights) . 106
8.3.1.11 Notification . 108
8.3.2 Test Description . 110
8.3.2.1 Create . 110
8.3.10.2 Update . 112
8.3.10.3 Retrieve . 114
8.3.10.4 Delete . 115
History . 117

ETSI

---------------------- Page: 5 ----------------------
oneM2M TS-0013 version 1.0.0 Release 1 6 ETSI TS 118 113 V1.0.0 (2016-03)
Intellectual Property Rights
IPRs essential or potentially essential to the present document 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.
Foreword
This Technical Specification (TS) has been produced by ETSI Partnership Project oneM2M (oneM2M).
ETSI

---------------------- Page: 6 ----------------------
oneM2M TS-0013 version 1.0.0 Release 1 7 ETSI TS 118 113 V1.0.0 (2016-03)
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 version 1.6.1
Release 1)".
[2] ETSI TS 118 104: "oneM2M; Service Layer Core protocol Specification (oneM2M TS-0004
version 1.3.0 Release 1).
[3] ETSI TS 118 108: "oneM2M; CoAP Protocol Binding (oneM2M TS-0008 version 1.1.0
Release 1).
[4] ETSI TS 118 109: "oneM2M; HTTP Protocol Binding (oneM2M TS-0009 version 1.2.0 Release
1).
[5] ETSI TS 118 110: "oneM2M; MQTT Protocol Binding (oneM2M ETSI TS 118 110 version 1.2.0
Release 1).
[6] oneM2M TS-0015: "Testing Framework".
[7] ETSI TS 118 111: "oneM2M; Common Terminology (oneM2M TS-0011)".
[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)".
[11] ETSI TS 118 106: "oneM2M; Management Enablement (BBF) (oneM2M TS-0006)".
ETSI

---------------------- Page: 7 ----------------------
oneM2M TS-0013 version 1.0.0 Release 1 8 ETSI TS 118 113 V1.0.0 (2016-03)
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
NOTE: Available at http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions 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,
OMA DM, etc.
receiver CSE: any CSE that receives a request
registree: AE or CSE that registers with another CSE
registrar CSE: CSE where an Application or another CSE has registered
resource: uniquely addressable entity in oneM2M architecture
transit CSE: any receiver CSE that is not a Hosting CSE
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACP Access Control Policy
AE Application Entity
AE-ID Application Entity Identifier
BBF BroadBand Forum
CoAP Constrained Application Protocol
CSE Common Services Entity
CSE-ID Common Service Entity Identifier
DM Device Management
DUT Device Under Test
FQDN Fully Qualified Domain Name
HTTP HyperText Transfer Protocol
IN Infrastructure Node
IN-CSE CSE which resides in the Infrastructure Node
JSON JavaScript Object Notation
ETSI

---------------------- Page: 8 ----------------------
oneM2M TS-0013 version 1.0.0 Release 1 9 ETSI TS 118 113 V1.0.0 (2016-03)
LWM2M Lightweight M2M
M2M Machine to Machine
Mca Reference Point for M2M Communication with AE
Mcc Reference Point for M2M Communication with CSE
MQTT Message Queuing Telemetry Transport
OMA Open Mobile Alliance
SP Service Provider
SUT System Under Test
TD Test Description
URI Uniform Resource Identifier
XML eXtensible Markup Language
4 Conventions
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 Rul
...