ETSI TS 103 315-2015 SmartM2M Machine-to-Machine communications (M2M) Interoperability Test Specification for ETSI M2M Primitives (V1 1 1)《智能M2M 机器对机器通信 (M2M) ETSI M2M原语的互操作性试验规格 (.pdf

《ETSI TS 103 315-2015 SmartM2M Machine-to-Machine communications (M2M) Interoperability Test Specification for ETSI M2M Primitives (V1 1 1)《智能M2M 机器对机器通信 (M2M) ETSI M2M原语的互操作性试验规格 (.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 103 315-2015 SmartM2M Machine-to-Machine communications (M2M) Interoperability Test Specification for ETSI M2M Primitives (V1 1 1)《智能M2M 机器对机器通信 (M2M) ETSI M2M原语的互操作性试验规格 (.pdf（83页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 103 315 V1.1.1 (2015-01) SmartM2M; Machine-to-Machine communications (M2M); Interoperability Test Specification for ETSI M2M Primitives TECHNICAL SPECIFICATION ETSI ETSI TS 103 315 V1.1.1 (2015-01)2Reference DTS/SmartM2M-0028 Keywords interoperability, M2M, testing ETSI 650 Route des Luciol

2、es 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 The pres

3、ent 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 versi

4、ons 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 cu

5、rrent status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reprod

6、uced 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

7、 extend to reproduction in all media. European Telecommunications Standards Institute 2015. 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 ETSI registered for the benefit of its Me

8、mbers and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 103 315 V1.1.1 (2015-01)3Contents Intellectual Property Rights 6g3Foreword . 6g3Modal verbs terminology 6g31 Scope 7g32 References 7g32.1 Normative references

9、 . 7g32.2 Informative references 7g33 Abbreviations . 8g34 Conventions 8g34.1 The Test Description proforma 8g34.2 Test Description naming convention 8g35 Test Description Summary . 9g35.1 ETSI M2M tests . 9g36 Basic Configuration 12g36.1 Resources request samples . 12g36.1.1 Application . 12g36.1.2

10、 Container 12g36.1.3 ContentInstance 12g36.1.4 Subscription 13g36.1.5 AccessRight 13g36.1.6 Group 14g36.2 Resource Representations examples . 15g36.3 aPoc Re-Targeting Procedure . 16g36.4 M2M Settings . 17g37 Test configurations . 17g37.1 dIa M2M DA-GSCL (M2M_CFG_01) 17g37.2 mId M2M (M2M_CFG_02) . 1

11、7g37.3 mIa M2M (M2M_CFG_03) . 18g37.4 Multi-Hop M2M DA to NSCL (M2M_CFG_04) 18g37.5 Multi-Hop M2M NA to GSCL (M2M_CFG_05) 18g37.6 End to End M2M DA-NA (M2M_CFG_06) 19g37.7 dIa M2M GA-GSCL (M2M_CFG_07) 19g37.8 Multi-Hop M2M GA to NSCL (M2M_CFG_08) 19g37.9 dIa M2M DA-DSCL (M2M_CFG_09) 20g37.10 Multi-H

12、op M2M DA to NSCL (M2M_CFG_10) 20g37.11 End to End M2M GA-NA (M2M_CFG_11) 20g38 Test Descriptions 21g38.1 Point to Point configuration testing 21g38.1.1 SCL Mutual Registration 21g38.1.2 SclBase Management 21g38.1.2.1 SclBase Retrieve . 21g38.1.2.2 SclBase Update . 22g38.1.3 Application Registration

13、 . 22g38.1.3.1 Application Resource creation 22g38.1.3.2 Application Retrieve . 23g38.1.3.3 Application Update . 23g38.1.3.4 Application Delete 24g38.1.4 Container Management. 24g38.1.4.1 Container Create . 24g38.1.4.2 Container Retrieve 25g38.1.4.3 Container Update 25g3ETSI ETSI TS 103 315 V1.1.1 (

14、2015-01)48.1.4.4 Container Delete . 26g38.1.5 ContentInstance Management . 26g38.1.5.1 Content Instance Create 26g38.1.5.2 Content Instance Create using plain text . 27g38.1.5.3 Content Instance Retrieve . 28g38.1.5.4 ContentInstance Content retrieve (partial addressing) 28g38.1.5.5 Content Instance

15、 Delete 29g38.1.6 Discovery Management 29g38.1.6.1 Discovery of all resources . 29g38.1.6.2 Discovery with Filter Criteria . 30g38.1.6.3 Discovery with max size . 30g38.1.6.4 Discovery with searchPrefix . 31g38.1.6.5 Discovery with multiple parameters 31g38.1.7 Subscription Management 32g38.1.7.1 Su

16、bscription Create . 32g38.1.7.2 Subscription Retrieve 32g38.1.7.3 Subscription Update 33g38.1.7.4 Subscription Delete . 33g38.1.7.5 Subscription Notify (To server-capable application) 34g38.1.7.6 Subscription Notify (To application container) . 35g38.1.8 Notification Channel Management . 36g38.1.8.1

17、 NotificationChannel Create . 36g38.1.8.2 NotificationChannel Retrieve 36g38.1.8.3 NotificationChannel Delete . 37g38.1.8.4 Long polling based notifications . 37g38.1.9 AccessRight Management 38g38.1.9.1 AccessRight Resource creation . 38g38.1.9.2 AccessRight Retrieve 38g38.1.9.3 AccessRight Update

18、. 39g38.1.9.4 AccessRight Delete . 39g38.1.9.5 Unauthorized operation (Empty Requesting Entity) . 40g38.1.9.6 Unauthorized operation (Bad Requesting Entity) . 40g38.1.9.7 Unauthorized operation (Insufficient Access Rights) . 41g38.1.10 Group Management 41g38.1.10.1 Group Resource creation . 41g38.1.

19、10.2 Group Retrieve 42g38.1.10.3 Group Update 42g38.1.10.4 Group Delete . 43g38.1.10.5 Group Operations (Create) 43g38.1.10.6 Group Operations (Retrieve) . 44g38.2 Multi-Hop configuration testing . 44g38.2.1 Container Management on remote SCL 44g38.2.1.1 Container Create . 44g38.2.1.2 Container Retr

20、ieve 45g38.2.1.3 Container Update 46g38.2.1.4 Container Delete . 46g38.2.2 ContentInstance Management on remote SCL . 47g38.2.2.1 Content Instance Create 47g38.2.2.2 Content Instance Create using plain text . 48g38.2.2.3 Content Instance Retrieve . 49g38.2.2.4 ContentInstance Content retrieve (parti

21、al addressing) 50g38.2.2.5 Content Instance Delete 50g38.2.3 Discovery Management on remote SCL . 51g38.2.3.1 Discovery of all resources . 51g38.2.3.2 Discovery with Filter Criteria . 52g38.2.3.3 Discovery with max size . 52g38.2.3.4 Discovery with searchPrefix . 53g38.2.3.5 Discovery with multiple

22、parameters 54g38.2.4 Subscription Management on remote SCL . 54g38.2.4.1 Subscription Create . 54g38.2.4.2 Subscription Retrieve 55g38.2.4.3 Subscription Update 56g3ETSI ETSI TS 103 315 V1.1.1 (2015-01)58.2.4.4 Subscription Delete . 57g38.2.4.5 Subscription Notify (To server capable application) . 5

23、8g38.2.4.6 Subscription Notify (To application container) . 60g38.2.5 Notification Channel Management . 62g38.2.5.1 NotificationChannel Create . 62g38.2.5.2 NotificationChannel Retrieve 63g38.2.5.3 NotificationChannel Delete . 63g38.2.5.4 Long polling based notifications . 64g38.2.6 AccessRight Mana

24、gement on remote SCL . 66g38.2.6.1 AccessRight Resource creation . 66g38.2.6.2 AccessRight Retrieve 67g38.2.6.3 AccessRight Update . 67g38.2.6.4 AccessRight Delete . 68g38.2.6.5 Unauthorized operation (Empty Requesting Entity) . 69g38.2.6.6 Unauthorized operation (Bad Requesting Entity) . 69g38.2.6.

25、7 Unauthorized operation (Insufficient Access Rights) . 70g38.2.7 Group Management on remote SCL . 71g38.2.7.1 Group Resource creation . 71g38.2.7.2 Group Retrieve 72g38.2.7.3 Group Update 72g38.2.7.4 Group Delete . 73g38.2.7.5 Group Operations 74g38.2.8 Announcement 76g38.2.8.1 Application registra

26、tion with announcement 76g38.2.8.2 Application delete with announcement . 77g38.2.8.3 Application De-Announce Ressources 78g38.3 End to End configuration testing 79g38.3.1 Resource management with re-targeting . 79g3History 83g3ETSI ETSI TS 103 315 V1.1.1 (2015-01)6Intellectual Property Rights IPRs

27、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 pote

28、ntially 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 (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No

29、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 Technical Committee Smart Ma

30、chine-to-Machine communications (SmartM2M). Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “may not“, “need“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal f

31、orms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 103 315 V1.1.1 (2015-01)71 Scope The present document specifies Interoperability Test Descriptions (TDs) for the ETSI M2M Primitives as specified in ET

32、SI TS 102 921 1. The purpose of the interoperability testing is to prove that end-to-end functionality between devices such as: dIa interface; mIa interface; Multi-Hop configuration (dIa + mId) and (mId+mIa); End to End configuration (dIa + mId + mIa); and using HTTP as underlying application layer,

33、 is as required by the standard(s) on which those devices are based. 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-spec

34、ific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were vali

35、d 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 102 921: “Machine-to-Machine communications (M2M); mIa, dIa and mId interfaces“. 2 ETSI TS 102 690: “Machine-to-Machin

36、e communications (M2M); Functional architecture“. 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 ve

37、rsion of the reference 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 docume

38、nt but they assist the user with regard to a particular subject area. Not applicable. ETSI ETSI TS 103 315 V1.1.1 (2015-01)83 Abbreviations For the purposes of the present document, the following abbreviations apply: aPoC The Application Point of Contract is a URI that identifies how requests are re

39、-targeted App M2M Application (DA, GA or NA) CFG Configuration DA Device Application Device (D) Hosts App that communicates to a GSCL using the dIa reference point. dIa device application Interface DSCL Device SCL EUT Equipment Under Test GA Gateway Application GSCL Gateway SCL MH Multi-HopmIa M2M a

40、pplication Interface mId M2M device Interface NA Network Application NSCL Network SCL SCL Service Capability Layer TD Test DescriptionURI Universal Resource Identifier XML eXtensible Markup Language4 Conventions 4.1 The Test Description proforma The test descriptions are provided in proforma tables.

41、 The following different types of test operator actions are considered during the test execution: A stimulus corresponds to an event that enforces an EUT to proceed with a specific protocol action, like sending a message for instance. A verify consists of verifying that the EUT behaves according to

42、the expected behaviour (for instance the EUT behaviour shows that it receives the expected message). A configure corresponds to an action to modify the EUT configuration. A check ensures the receipt of protocol messages on reference points, with valid content. This “check“ event type corresponds to

43、the method called interoperability testing with conformance check. 4.2 Test Description naming convention Table 1: TD naming convention TD/ = root M2M = group P2P Point to Point testing on dIa, mId or mIa MH Multi-Hop: management of remote ressources E2E End to End = sequential number 01 to 99 ETSI

44、ETSI TS 103 315 V1.1.1 (2015-01)95 Test Description Summary 5.1 ETSI M2M tests Table 2: ETSI M2M Tests Nb Procedure/Resource TD ID TD Description 1 SCL Mutual Registration TD_M2M_P2P_01 GSCL registers to NSCL 2 SclBase Management TD_M2M_P2P_02 App retrieves the sclBase resource via a sclBaseRetrieve

45、Request 3 TD_M2M_P2P_03 App updates the sclBase resource via an sclBaseUpdateRequest 4 Application TD_M2M_P2P_04 App registers to its local SCL via an applicationCreateRequest 5 TD_M2M_P2P_05 App retrieves application resource via an applicationRetrieveRequest 6 TD_M2M_P2P_06 App updates attribute i

46、n application resource via an applicationUpdateRequest 7 TD_M2M_P2P_07 App de-registers by deleting application resource via an applicationDeleteRequest 8 Container TD_M2M_P2P_08 App creates a container ressource in local SCL via a containerCreateRequest 9 TD_M2M_P2P_09 App retrieves information of

47、a container resource via a containerRetrieveRequest 10 TD_M2M_P2P_10 App updates attribute in application resource via an containerUpdateRequest 11 TD_M2M_P2P_11 App delete a specific container ressource via a containerDeleteRequest 12 ContentInstance TD_M2M_P2P_12 App adds a contentInstance resourc

48、e to the contentInstances resource of a specific container in local SCL via a contentInstanceCreateRequest 13 TD_M2M_P2P_13 App adds a contentInstance resource to the contentInstances resource of a specific container in local SCL via a contentInstanceCreateRequest using plain text data 14 TD_M2M_P2P

49、_14 App retrieves information of a contentInstance resource via a containerRetrieveRequest 15 TD_M2M_P2P_15 Handle contentInstanceRetrieveRequest with targetID using partial addressing (content attribute) 16 TD_M2M_P2P_16 App deletes contentInstance resource via a containerDeleteRequest 17 Discovery TD_M2M_P2P_17 App discovers resources residing in Local SCL via DiscoveryRetrieveRequest 18 TD_M2M_P2P_18 App discovers resources residing in Local SCL using specific Filter criteria via DiscoveryRetrieveRequest 19 TD_M2M_P2P_19 App discovers resources