1、 ETSI TS 118 113 V1.0.0 (2016-03) oneM2M; Interoperability Testing (oneM2M TS-0013 version 1.0.0 Release 1) TECHNICAL SPECIFICATION ETSI ETSI TS 118 113 V1.0.0 (2016-03)2oneM2M TS-0013 version 1.0.0 Release 1Reference DTS/oneM2M-000013 Keywords interoperability, IoT, M2M, protocol ETSI 650 Route des
2、 Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/s
3、tandards-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 con
4、tents 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 statu
5、s. 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 Co
6、pyright 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. T
7、he copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of
8、 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 ETSI TS 118 113 V1.0.0 (2016-03)3oneM2M TS-0013 version 1.0.0 Release 1Contents Intellectual Property Rights 6g3Foreword . 6
9、g31 Scope 7g32 References 7g32.1 Normative references . 7g32.2 Informative references 8g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Conventions 9g35 Testing conventions 9g35.1 The Test Description proforma 9g35.2 Test Description naming convention 10g35.3 Test S
10、ettings . 10g35.4 Pre-conditions . 11g35.4.1 Registration . 11g35.4.2 Security . 11g35.4.3 Service Subscription . 11g35.4.4 ID allocation . 11g35.4.5 Existence of resource 11g35.4.6 Management Session between Management Server and Management Client 11g35.5 Binding message convention 11g36 Test Descr
11、iption Summary . 12g36.1 Tests list . 12g37 Configuration . 14g37.1 Test Configuration 14g37.1.1 No hop 14g37.1.1.1 M2M_CFG_01 14g37.1.1.2 M2M_CFG_02 14g37.1.2 Single hop . 14g37.1.1.1 M2M_CFG_03 14g37.1.2.2 M2M_CFG_04 15g37.1.2.3 M2M_CFG_05 15g37.1.2.4 M2M_CFG_08 15g37.1.2.5 M2M_CFG_09 16g37.1.3 Mu
12、lti hops . 16g37.1.3.1 M2M_CFG_06 16g37.1.3.2 M2M_CFG_07 16g38 Test Descriptions 17g38.1 No Hop configuration testing . 17g38.1.1 CSEBase Management . 17g38.1.1.1 CSEBase Retrieve on Mca 17g38.1.2 RemoteCSE Management . 18g38.1.2.1 RemoteCSE Create 18g38.1.2.2 remoteCSE Retrieve 20g38.1.2.3 remoteCS
13、E Update 21g38.1.2.4 remoteCSE Delete . 22g38.1.3 Application Entity Registration 23g38.1.3.1 AE Create 23g38.1.3.2 AE Retrieve . 25g38.1.3.3 AE Update. 26g38.1.3.4 AE Delete 27g38.1.4 Container Management . 28g3ETSI ETSI TS 118 113 V1.0.0 (2016-03)4oneM2M TS-0013 version 1.0.0 Release 18.1.4.1 Cont
14、ainer Create . 28g38.1.4.2 Container Retrieve 30g38.1.4.3 Container Update 31g38.1.4.4 Container Delete . 32g38.1.5 ContentInstance Management . 33g38.1.5.1 ContentInstance Create . 33g38.1.5.2 ContentInstance Retrieve 34g38.1.5.3 ContentInstance Delete . 35g38.1.6 Discovery 37g38.1.6.1 Discovery of
15、 all resources . 37g38.1.6.2 Discovery with label filter criteria 38g38.1.6.3 Discovery with limit filter criteria . 39g38.1.6.4 Discovery with multiple filter criteria . 41g38.1.7 Subscription Management 42g38.1.7.1 Subscription Create . 42g38.1.7.2 Subscription Retrieve 43g38.1.7.3 Subscription Up
16、date 45g38.1.7.4 Subscription Delete . 46g38.1.8 accessControlPolicy Management 47g38.1.8.1 accessControlPolicy Create. 47g38.1.8.2 accessControlPolicy Retrieve 48g38.1.8.3 accessControlPolicy Update 50g38.1.8.4 accessControlPolicy Delete . 51g38.1.8.5 Unauthorized operation (Insufficient Access Rig
17、hts) . 52g38.1.9 Group Management 53g38.1.9.1 53g38.1.9.2 Group Create . 55g38.1.9.3 Group Update 56g38.1.9.4 Group Delete . 57g38.1.10 Node Management 58g38.1.10.1 Node Create. 58g38.1.10.2 Node Retrieve . 59g38.1.10.3 Node Update . 60g38.1.10.4 Node Delete. 62g38.1.11 PollingChannel Management 63g
18、38.1.11.1 PollingChannel Create 63g38.1.11.2 PollingChannel Retrieve . 64g38.1.11.3 pollingChannel Update 65g38.1.11.4 pollingChannel Delete . 66g38.1.11.5 Long Polling on a PollingChannel Retrieve 67g38.1.12 FanoutPoint Management . 68g38.1.12.1 FanoutPoint Create 68g38.1.12.2 FanoutPoint Retrieve
19、. 70g38.1.12.3 FanoutPoint Update . 71g38.1.12.4 FanoutPoint Delete 72g38.1.13 Notifcation Management 73g38.1.13.1 Notification Create 73g38.2 Non blocking configuration testing 74g38.2.1 Synchronous request . 74g38.2.1.1 Container management 74g38.2.1.1.1 Container Create 74g38.2.1.1.2 Container Re
20、trieve . 77g38.2.1.1.3 Container Update . 79g38.2.1.1.4 Container Delete 81g38.2.2 Asynchronous request. 83g38.2.2.1 Container management 83g38.2.2.1.1 Container Create 83g38.2.2.1.2 Container Retrieve . 86g38.2.2.1.3 Container Update . 88g38.2.2.1.4 Container Delete 90g38.3 Single hop configuration
21、 testing . 92g38.3.1 Retargeting 92g3ETSI ETSI TS 118 113 V1.0.0 (2016-03)5oneM2M TS-0013 version 1.0.0 Release 18.3.1.1 RetargetingResource Create (Generic Test Description) 92g38.3.1.2 Create 94g38.3.1.3 Resource Retrieve (Generic Test Description) 95g38.3.1.4 retrieve 97g38.3.1.5 Resource Update
22、(Generic Test Description) 99g38.3.1.6 update 101g38.3.1.7 Resource Delete (Generic Test Description) . 101g38.3.1.8 delete . 103g38.3.1.9 Discovery with multiple filter criteria . 104g38.3.1.10 Unauthorized operation (Insufficient Access Rights) . 106g38.3.1.11 Notification . 108g38.3.2 Test Descri
23、ption . 110g38.3.2.1 Create . 110g38.3.10.2 Update 112g38.3.10.3 Retrieve 114g38.3.10.4 Delete . 115g3History 117g3ETSI ETSI TS 118 113 V1.0.0 (2016-03)6oneM2M TS-0013 version 1.0.0 Release 1Intellectual Property Rights IPRs essential or potentially essential to the present document may have been de
24、clared 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“, whi
25、ch 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 i
26、n 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 ETSI TS 118 113 V1.0.0 (2016-03)7oneM2M TS-0013 version 1.0
27、.0 Release 11 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 ei
28、ther 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 whic
29、h 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 nece
30、ssary 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
31、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:
32、“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:
33、“oneM2M; Management Enablement (BBF) (oneM2M TS-0006)“. ETSI ETSI TS 118 113 V1.0.0 (2016-03)8oneM2M TS-0013 version 1.0.0 Release 12.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific refe
34、rences, 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 followi
35、ng 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 Defin
36、itions 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 resour
37、ce 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 D
38、M, 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 Ab
39、breviations For the purposes of the present document, the following abbreviations apply: ACP Access Control Policy AE Application EntityAE-ID Application Entity Identifier BBF BroadBand Forum CoAP Constrained Application Protocol CSE Common Services Entity CSE-ID Common Service Entity Identifier DM
40、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 ETSI TS 118 113 V1.0.0 (2016-03)9oneM2M TS-0013 version 1.0.0 Release 1LWM2M Light
41、weight 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 e
42、Xtensible Markup Language4 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 Rules i.1. 5 Testing conventions 5.1 The Test Description proforma The testing methodogy used in the present
43、 document is specified in the oneM2M TS-0015: Testing framework 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 function
44、alities 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 m
45、onitors, functional equipment, ) required to achieve the correct behaviour of the vendor implementations. The correct initial conditions. The correct sequence of the test events and test results. In order to facilitate the specification of test cases an interoperability test description should inclu
46、de, at a minimum, the following fields as indicated table 1. Table 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
47、 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
48、 order to execute this test (e.g. if this list contains an optional feature to be supported, then the test is optional). Configuration or Architecture A list of all required equipment for testing and possibly also including a reference to an illustration of a test architecture or test configuration.
49、 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. ETSI ETSI TS 118 113 V1.0.0 (2016-03)10oneM2M TS-0013 version 1.0.0 Release 1The test descriptions are provided in proforma
