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.15 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 Testing framework Recommendation ITU-T Y.4500.15 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATION
3、 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 INTERNET PRO
4、TOCOL 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, admini
5、stration 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.2249 Servi
6、ce 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 Carrier grade
7、 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.4250Y.4399
8、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 list of
9、ITU-T Recommendations. Rec. ITU-T Y.4500.15 (03/2018) i Recommendation ITU-T Y.4500.15 oneM2M Testing framework Summary The testing framework in Recommendation ITU-T Y.4500.15 provides the methodology for the development of conformance and interoperability test strategies, test systems and the resul
10、ting test specifications for oneM2M standards. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.4500.15 2018-03-01 20 11.1002/1000/13510 Keywords Certification, conformance testing, interoperability test, oneM2M, testing framework. * To access the Recommendation, type the U
11、RL 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 Rec. ITU-T Y.4500.15 (03/2018) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency i
12、n the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to s
13、tandardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations i
14、s 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 on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to
15、 indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is a
16、chieved 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 express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. NOTE The
17、structure of this Recommendation departs slightly from the usual editorial style of ITU-T Recommendations to preserve existing cross-referencing from external documents. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation may
18、involve the use of a claimed Intellectual Property 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
19、Recommendation, ITU had not received notice of intellectual 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 databa
20、se at http:/www.itu.int/ITU-T/ipr/. 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. ITU-T Y.4500.15 (03/2018) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defi
21、ned elsewhere 1 3.2 Terms defined in this Recommendation . 1 4 Abbreviations and acronyms 3 5 Conventions 4 6 Introduction to the oneM2M testing methodology . 4 7 Conformance testing . 5 7.1 Introduction 5 7.2 Test architecture . 7 7.3 Development of conformance test specifications . 8 8 Interoperab
22、ility testing 20 8.1 Introduction 20 8.2 Basic concepts 20 8.3 Development of interoperability test specifications . 22 Annex A oneM2M Specification update and maintenance control procedure . 28 Appendix I Example of ICS table . 29 I.1 Capability statement . 29 Bibliography. 30 Rec. ITU-T Y.4500.15
23、(03/2018) 1 Recommendation ITU-T Y.4500.15 oneM2M Testing framework 1 Scope This Recommendation provides a testing framework defining a methodology for development of conformance and interoperability test strategies, test systems and the resulting test specifications for oneM2M standards. The Recomm
24、endation contains oneM2M Release 2 specification oneM2M Testing Framework V2.0.0 and is equivalent to standards of oneM2M partners including Association of Radio Industries and Businesses (ARIB), Alliance for Telecommunications Industry Solutions (ATIS) b-ATIS.oneM2M, China Communications Standards
25、Association (CCSA) b-CCSA M2M-TS-0015, European Telecommunications Standards Institute (ETSI) b-ETSI-TS 118 115, Telecommunications Industry Association (TIA), Telecommunications Standards Development Society India (TSDSI) b-TSDSI STD T1.oneM2M TS-0015, Telecommunications Technology Association (TTA
26、) b-TTAT.MM-TS.0015 and Telecommunication Technology Committee (TTC) b-TTC TS-M2M-0015. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editio
27、ns 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 references listed below. A list of the currently valid
28、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 architecture. ITU-T Y.4500.4 Recommendation ITU-T Y
29、.4500.4 (2018), Service Layer Core Protocol. ITU-T Y.4500.11 Recommendation ITU-T Y.4500.11 (2018), Common terminology. 3 Definitions 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 a
30、pplication logic for end-to-end M2M solutions. 3.1.2 common services entity (CSE) ITU-T Y.4500.11: Represents an instantiation of a set of common service functions of the M2M environments. Such service functions are exposed to other entities through reference points. 3.1.3 conformance b-ITU-T X Supp
31、l.4: Compliance with requirements specified in applicable ITU-T X.290-series of Recommendations. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 2 Rec. ITU-T Y.4500.15 (03/2018) 3.2.1 conformance testing: Process for testing that an implementation is complia
32、nt with a protocol standard, which is realized by test systems simulating the protocol with test scripts executed against the implementation under test. 3.2.2 device under test (DUT): Combination of software and/or hardware items which implement the functionality of standards and interact with other
33、 DUTs via one or more reference points. 3.2.3 ICS proforma: Document, in the form of a questionnaire, which when completed for an implementation or system becomes an implementation conformance statement (ICS). 3.2.4 implementation conformance statement (ICS): Statement made by the supplier of an imp
34、lementation or system claimed to conform to a given specification, stating which capabilities have been implemented. 3.2.5 implementation extra information for testing (IXIT): Checklist which contains or references all of the information (in addition to that given in the implementation conformance s
35、tatement (ICS) related to the implementation under test (IUT) and its testing environment, which will enable the test laboratory to run an appropriate test suite against the IUT. 3.2.6 implementation under test (IUT): Implementation of one or more Open Systems Interconnection (OSI) protocols in an a
36、djacent user/provider relationship, being the part of a real open system which is to be studied by testing (b-ISO/IEC 9646). 3.2.7 inopportune behaviour (BO): Test group that handles invalid exchanges of messages, which are properly structured and correctly encoded. 3.2.8 interoperability: Ability o
37、f two systems to interoperate using the same communication protocol. 3.2.9 interoperability testing: Activity of proving that end-to-end functionality between (at least) two devices is as required by the base standard(s) on which those devices are based. 3.2.10 interworking function (IWF): Translati
38、on of one protocol into another one so that two systems using two different communication protocols are able to interoperate. 3.2.11 invalid behaviour (BI): Test group that handles valid exchanges of messages, which are either not properly structured or incorrectly encoded. 3.2.12 IXIT proforma: Doc
39、ument, in the form of a questionnaire, which when completed for an implementation or system, becomes an implementation extra information for testing (IXIT). 3.2.13 qualified equipment (QE): Grouping of one or more devices that has been shown and certified, by rigorous and well-defined testing, to in
40、teroperate with other equipment. NOTE 1 Once a device under test (DUT) has been successfully tested against a QE, it may be considered to be a QE, itself. NOTE 2 Once a QE is modified, it loses its status as QE and becomes again an DUT. 3.2.14 test case: Specification of the actions required to achi
41、eve a specific test purpose, starting in a stable testing state, ending in a stable testing state and defined in either natural language for manual operation or in a machine-readable language (such as testing and test control notation version 3 (TTCN-3) for automatic execution. 3.2.15 testing framew
42、ork: Document providing guidance and examples necessary for the development and implementation of a test specification. 3.2.16 test purpose: Description of a well-defined objective of testing, focussing on a single requirement or a set of related requirements. 3.2.17 valid behaviour (BV): test group
43、 that handles valid exchanges of messages, which are properly structured and correctly. Rec. ITU-T Y.4500.15 (03/2018) 3 4 Abbreviations and acronyms For the purposes of this Recommendation, the terms and definitions given in ITU-T Y.4500.11 and the following apply: AE Application Entity API Applica
44、tion Programming Interface APT Abstract Protocol Tester ATS Abstract Test Suite BI Invalid Behaviour BO Inopportune Behaviour BV Valid Behaviour CoAP Constrained Application Protocol CSE Common Services Entity DUT Device Under Test EUT Equipment Under Test FQDN Fully Qualified Domain Name HTTP Hyper
45、text Transfer Protocol ICS Implementation Conformance Statement IFS Interoperable Features Statement IOP Interoperability IUT Implementation Under Test IWF InterWorking Function IXIT Implementation eXtra Information for Testing JSON JavaScript Object Notation M2M Machine to Machine MMI Man-Machine I
46、nterface MQTT Message Queue Telemetry Transport PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement QE Qualified Equipment SUT System Under Test TC Test Case TCP Transmission Control Protocol TD Test Description TP Test Purpose TSS Test Suite Structure TTCN-3 Testing and Test C
47、ontrol Notation version 3 UDP User Datagram Protocol 4 Rec. ITU-T Y.4500.15 (03/2018) URI Uniform Resource Identifier XML extensible Markup Language XSD XML Schema Definition 5 Conventions The keywords “Shall“, “Shall not“, “May“, “Need not“, “Should“, “Should not“ in the present document are to be
48、interpreted as described: Shall/Shall not: Requirements 1) effect on this Recommendation: This Recommendation needs to describe the required feature (i.e., specify a technical solution for the Requirement); 2) effect on products: every implementation (machine to machine (M2M) solution that complies
49、to this Recommendation) must support it; 3) effect on deployments: every deployment (M2M service based on this Recommendation) 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 the feature; 2) effect on products: an implementation may or may not suppor
