1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Y.4500.13 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2018) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Internet of things an
2、d smart cities and communities Frameworks, architectures and protocols oneM2M Interoperability testing Recommendation ITU-T Y.4500.13 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFO
3、RMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTER
4、NET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation,
5、 administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.224
6、9 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrie
7、r grade open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Y.4000Y.4049 Definitions and terminologies Y.4050Y.4099 Requirements and use cases Y.4100Y.4249 Infrastructure, connectivity and networks Y.4250
8、Y.4399 Frameworks, architectures and protocols Y.4400Y.4549 Services, applications, computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 Evaluation and assessment Y.4900Y.4999 For further details, please refer to the l
9、ist of ITU-T Recommendations. Rec. ITU-T Y.4500.13 (03/2018) i Recommendation ITU-T Y.4500.13 oneM2M Interoperability testing Summary Recommendation ITU-T Y.4500.13 specifies interoperability test descriptions for the oneM2M primitives. History Edition Recommendation Approval Study Group Unique ID*
10、1.0 ITU-T Y.4500.13 2018-03-01 20 11.1002/1000/13508 Keywords Interoperability, oneM2M. * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii
11、Rec. ITU-T Y.4500.13 (03/2018) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU
12、. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics fo
13、r study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared
14、on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may con
15、tain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to expres
16、s requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Propert
17、y Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of in
18、tellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. NOTE This Rec
19、ommendation departs slightly from the usual editorial style of ITU-T Recommendations to preserve existing cross-referencing from external documents. ITU 2018 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec.
20、 ITU-T Y.4500.13 (03/2018) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 Testing conventions 4 6.1 The test description proforma . 4 6.2 Test descript
21、ion naming convention . 5 6.3 Test settings 5 6.4 Pre-conditions . 6 6.5 Binding message convention 6 7 Test description summary . 7 7.1 Tests list 7 8 Configuration 10 8.1 Test configuration . 10 9 Test descriptions . 12 9.1 No Hop configuration testing . 12 9.2 Non blocking configuration testing 5
22、2 9.3 Single hop configuration testing . 58 9.4 Secure AE registration 76 Annex A oneM2M specification update and maintenance control procedure 78 Bibliography. 79 Rec. ITU-T Y.4500.13 (03/2018) 1 Recommendation ITU-T Y.4500.13 oneM2M Interoperability testing 1 Scope This Recommendation specifies in
23、teroperability test descriptions (TDs) for the oneM2M primitives as specified in ITU-T Y.4500.1, ITU-T Y.4500.4, the bindings ITU-T Y.4500.8, ITU-T Y.4500.9 and ITU-T Y.4500.10. The Recommendation contains oneM2M Release 2 specification oneM2M Interoperability Testing V1.0.0 and is equivalent to sta
24、ndards of oneM2M partners including ARIB, ATIS, CCSA, ETSI b-ETSI TS 118 113, TIA, TSDSI, TTA b-TTA MM-TS.0013 and TTC b-TTC TS-M2M-0013. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Reco
25、mmendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other refer
26、ences listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Y.4500.1 Recommendation ITU-T Y.4500.1 (2018), oneM2M- Functional
27、architecture. ITU-T Y.4500.4 Recommendation ITU-T Y.4500.4 (2018), oneM2M - Service layer core protocol specification. ITU-T Y.4500.5 Recommendation ITU-T Y.4500.5 (2018), oneM2M -Management Enablement (OMA). ITU-T Y.4500.6 Recommendation ITU-T Y.4500.6 (2018), oneM2M -Management enablement (BBF). I
28、TU-T Y.4500.8 Recommendation ITU-T Y.4500.8 (2018), oneM2M - CoAP protocol binding. ITU-T Y.4500.9 Recommendation ITU-T Y.4500.9 (2018), oneM2M - HTTP protocol binding. ITU-T Y.4500.10 Recommendation ITU-T Y.4500.10 (2018), oneM2M - MQTT protocol binding. ITU-T Y.4500.11 Recommendation ITU-T Y.4500.
29、11 (2018), oneM2M -Common terminology. ITU-T Y.4500.15 Recommendation ITU-T Y.4500.15 (2018), oneM2M -Testing framework. IETF RFC 3986 IETF RFC 3986 (2005), Uniform Resource Identifier (URI): Generic Syntax. https:/www.ietf.org/rfc/rfc3986.txt IETF RFC 7230 IETF RFC 7230 (2014), Hypertext Transfer P
30、rotocol (HTTP/1.1): Message Syntax and Routing. https:/tools.ietf.org/html/rfc7230 2 Rec. ITU-T Y.4500.13 (03/2018) ETSI TS 118 103 ETSI TS 118 103 - V2.4.1 (2016), Security solutions. 3 Definitions For the purposes of the present document, the terms and definitions given in oneM2M TS-0011 ITU-T Y.4
31、500.11 apply. 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 Application entity ITU-T Y.4500.11: Represents an instantiation of application logic for end-to-end M2M solutions. 3.1.2 Common services entity (CSE) ITU-T Y.4500.11: Represents an instant
32、iation of a set of common service functions of the M2M environments. Such service functions are exposed to other entities through reference points. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 hosting CSE: CSE where the addressed resource is hosted.
33、 3.2.2 M2M service provider domain: Part of the M2M system that is associated with a specific M2M service provider. 3.2.3 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
34、DM, etc. 3.2.4 receiver CSE: Any CSE that receives a request. 3.2.5 registree: AE or CSE that registers with another CSE. 3.2.6 registrar CSE: CSE where an application or another CSE has registered. 3.2.7 resource: uniquely addressable entity in oneM2M architecture. 3.2.8 transit CSE: any receiver C
35、SE that is not a hosting CSE. 4 Abbreviations and acronyms For the purposes of the present document, the abbreviations given in oneM2M TS-0011 ITU-T Y.4500.11 and the following apply: ACP Access Control Policy AE Application Entity AE-ID Application Entity Identifier BBF Broadband Forum CoAP Constra
36、ined Application Protocol CSE Common Services Entity CSE-ID Common Service Entity Identifier DM Device Management DUT Device Under Test FQDN Fully Qualified Domain Name Rec. ITU-T Y.4500.13 (03/2018) 3 HTTP Hypertext Transfer Protocol IN Infrastructure Node IN-CSE CSE which resides in the Infrastruc
37、ture Node JSON JavaScript Object Notation 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 T
38、est Description URI Uniform Resource Identifier XML extensible Markup Language 5 Conventions The keywords “shall“, “shall not“, “should“, “should not“, “may“, “need not“ in the present Recommendation are to be interpreted as described: Shall/Shall not: Requirements: 1) Effect on this Recommendation:
39、 This Recommendation needs to describe the required feature (i.e., specify a technical solution for the requirement); 2) Effect on products: every implementation (M2M solution that complies to this standard) must support it 3) Effect on deployments: every deployment (M2M service based on this Recomm
40、endation) must use the standardized feature where applicable otherwise e.g., interoperability problems with other services could arise. Should/Should not: Recommendation: 1) Effect on this Recommendation: This Recommendation needs to describe a solution that allows the presence and the absence of th
41、e feature. 2) Effect on products: an implementation may or may not support it, however support is recommended 3) Effect on deployments: a deployment may or may not use it, however usage is recommended May/Need not: Permission/Option: 1) Effect on this Recommendation: This Recommendation needs to des
42、cribe a solution that allows the presence and the absence of the required feature; 4 Rec. ITU-T Y.4500.13 (03/2018) 2) Effect on products: an implementation may or may not support it 3) Effect on deployments: A deployment may or may not use it 6 Testing conventions 6.1 The test description proforma
43、The testing methodology used in the present document is specified in ITU-T Y.4500.15. 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 int
44、eroperable 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 eq
45、uipment (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. In order to facilitate the specification of test cases an interoperability test d
46、escription should include, 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 te
47、st 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 s
48、upported by the system under test (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 architecture A list of all required equipment for testing and possibly also including a reference to an illustration of
49、 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
