diff --git a/TS-0013-Interoperability_Testing-V3_3_1_Change.md b/TS-0013-Interoperability_Testing-V3_3_1_Change.md index bd937bc6f9b1168af6cd75d8c471daae745bda7e..6a74d1563a4b602f15e16a81abbd30910b6d0be9 100644 --- a/TS-0013-Interoperability_Testing-V3_3_1_Change.md +++ b/TS-0013-Interoperability_Testing-V3_3_1_Change.md @@ -1,2255 +1,3225 @@ -  - - - - - - - -|oneM2M<br />Technical Specification |oneM2M<br />Technical Specification | -|-|-| -|Document Number |TS-0013-V.3.3.1 | -|Document Name: |Interoperability Testing<br /> | -|Date: |2021-09-02 | -|Abstract: |The specification address the testing of the primitives on the oneM2M interfaces as specified in TS-0001 <a href="#_ref_1">[1]</a> and TS-0004 <a href="#_ref_2">[2]</a>. The purpose of the interoperability testing is to prove end-to-end functionality between Application Entities and Common Service Entities over the Mca and Mcc reference points<br /> | - - - - - - - - - - - - - -This Specification is provided for future development work within oneM2M only. The Partners accept no liability for any use of this Specification. - -The present document has not been subject to any approval process by the oneM2M Partners Type 1. Published oneM2M specifications and reports for implementation should be obtained via the oneM2M Partners' Publications Offices. - - - - - -<br />About oneM2M - -The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. - -More information about oneM2M may be found at: http//www.oneM2M.org - -Copyright Notification - -No part of this document may be reproduced, in an electronic retrieval system or otherwise, except as authorized by written permission. - -The copyright and the foregoing restriction extend to reproduction in all media. - -(c) 2021, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC). - -All rights reserved. - -Notice of Disclaimer & Limitation of Liability - -The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. - -NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. - -<br /> - -# 1 Scope -The present document specifies Interoperability Test Descriptions (TDs) for the oneM2M Primitives as specified in oneM2M TS-0001 <a href="#_ref_1">[1]</a>, oneM2M TS-0004 <a href="#_ref_2">[2]</a>, the bindings oneM2M TS-0008 <a href="#_ref_3">[3]</a>, oneM2M TS-0009 <a href="#_ref_4">[4]</a> and oneM2M TS-0010 <a href="#_ref_5">[5]</a>. - - -# 2 References - -## 2.1 Normative references -References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. - -The following referenced documents are necessary for the application of the present document. - - -- <a name="_ref_1">[1]</a> oneM2M TS-0001: "Functional Architecture- Release 3". -- <a name="_ref_2">[2]</a> oneM2M TS-0004: "Service Layer Core protocol Specification - Release 3". -- <a name="_ref_3">[3]</a> oneM2M TS-0008: "CoAP Protocol Binding Release 3". -- <a name="_ref_4">[4]</a> oneM2M TS-0009: "HTTP Protocol Binding - Release 3". -- <a name="_ref_5">[5]</a> oneM2M TS-0010: "MQTT Protocol Binding - Release 3". -- <a name="_ref_6">[6]</a> oneM2M TS-0015: "Testing Framework". -- <a name="_ref_7">[7]</a> oneM2M TS-0011: "Common Terminology". -- <a name="_ref_8">[8]</a> IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". -- <a name="_ref_9">[9]</a> IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". -- <a name="_ref_10">[10]</a> oneM2M TS-0005: "Management Enablement (OMA) - Release 3". -- <a name="_ref_11">[11]</a> oneM2M TS-0006: "Management Enablement (BBF) - Release 3". -- <a name="_ref_12">[12]</a> oneM2M TS-0003: "Security Solutions - Release 3". -- <a name="_ref_13">[13]</a> oneM2M TS-0034: "Semantics Support - Release 3". -- <a name="_ref_14">[14]</a> oneM2M TS-0023: "Home Appliances Information Model and Mapping - Release 3". -- <a name="_ref_15">[15]</a> oneM2M TS-0026: "3GPP interworking - Release 4". -- <a name="_ref_16">[16]</a> oneM2M TS-0040: "Modbus Interworking - Release 4". - -## 2.2 Informative references - -References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. - -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. - - -- <a name="_ref_i.1">[i.1]</a> oneM2M Drafting Rules. -> NOTE: Available at [http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf](http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf). - -- <a name="_ref_i.2">[i.2]</a> BBF TR-069: "CPE WAN Management Protocol". - -# 3 Definitions of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms given in oneM2M TS-0011 <a href="#_ref_7">[7]</a> and the following apply: - -> NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in oneM2M TS-0011 <a href="#_ref_7">[7]</a>. - -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 <a href="#_ref_i.2">[i.2]</a>, OMA DM <a href="#_ref_10">[10]</a>, etc. - -receiver CSE: any CSE that receives a request - -registrar CSE: CSE where an Application or another CSE has registered - -registree: AE or CSE that registers with another CSE - -resource: uniquely addressable entity in oneM2M architecture - -transit CSE: any receiver CSE that is not a Hosting CSE - - -## 3.2 Symbols -Void. - - -## 3.3 Abbreviations -For the purposes of the present document, the following abbreviations apply: - - -| abbreviation | Explanation | -| -------------- | --------------------------------------------- | -| ACP | Access Control Policy | -| ACP-SD | Access Control Policy-Semantic Descriptor | -| ADN-AE | AE which resides in the Application Dedicated Node | -| AE | Application Entity | -| AE-ID | Application Entity Identifier | -| APP-ID | Application Identifier | -| BBF | BroadBand Forum | -| CFG | Configuration | -| CoAP | Constrained Application Protocol | -| CP | Communication Patterns | -| CSE | Common Services Entity | -| CSE-ID | Common Service Entity Identifier | -| DAS | Dynamic Authorization System | -| DDN | Downlink Data Notification | -| DM | Device Management | -| DTLS | Datagram Transport Layer Security | -| DUT | Device Under Test | -| ECDHE | Elliptic-curve Diffie-Hellman | -| FQDN | Fully Qualified Domain Name | -| HAIM | Home Appliances Information Model | -| HSS | Home Subscriber Serve | -| HTTP | HyperText Transfer Protocol | -| IN | Infrastructure Node | -| IN-AE | Application Entity that is registered with the CSE in the Infrastructure Node | -| IN-CSE | CSE which resides in the Infrastructure Node | -| IOP | Interoperability | -| IP | Internet Protocol | -| IPE | Interworking Proxy Entity | -| JSON | JavaScript Object Notation | -| LWM2M | Lightweight M2M | -| M2M | Machine to Machine | -| MA | Mandatory Announced | -| MBMS | Multimedia Broadcast Multicast Service | -| Mca | Reference Point for M2M Communication with AE | -| Mcc | Reference Point for M2M Communication with CSE | -| MEF | M2M Enrolment Function | -| MH | Multi Hop | -| MNO | Mobile Network Operator | -| MO | Management Object | -| MQTT | Message Queuing Telemetry Transport | -| MT | Mobile Terminated | -| NB | Non-Blocking | -| NH | No Hop | -| NIDD | non-IP Data Delivery | -| NODN | Non oneM2M Device Node | -| OMA | Open Mobile Alliance | -| PDN | Packet Data Network | -| PRO | Protocol | -| PSK | Pre-Shared Key | -| PSM | Power Savings Mode | -| RDS | Reliable Data Service | -| RFC | Request for Comments | -| RP | Reference Point | -| RPC | Remote Procedure Calls | -| RQI | Request-ID | -| SCEF | Service Capability Exposure Function | -| SD | Semantic Descriptor | -| SE | Security | -| SGS | Semantic Graph Store | -| SH | Single Hop | -| SP | Service Provider | -| SPARQL | SPARQL Protocol and RDF Query Language | -| SUID | Security Usage Identifier | -| SUT | System Under Test | -| TCP | Transmission Control Protocol | -| TD | Test Description | -| TLS | Transport Layer Security | -| TMGI | Temporary Mobile Group Identity | -| TP | Traffic Pattern | -| UDP | User Datagram Protocol | -| URI | Uniform Resource Identifier | -| XML | eXtensible Markup Language | - - - -# 4 Conventions - -The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules <a href="#_ref_i.1">[i.1]</a>. - - -# 5 Testing conventions - -## 5.1 The Test Description proforma -The testing methodology used in the present document is specified in the oneM2M TS-0015 <a href="#_ref_6">[6]</a>. - -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 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 equipment (protocol monitors, 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 include, at a minimum, the following fields as indicated table 5.1-1. - - -**Table 5.1-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 in the document. | -|References |A list of references to the base specification section(s), use case(s), requirement(s) and Test Purposes 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 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. | -|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 descriptions are provided in proforma tables. In order to ensure the correct execution of an interoperability test, the following information is provided in the test description: - - -- The configuration applied for the test. -- The need of additional equipment (protocol monitors, functional equipment, etc.) required to achieve the correct behaviour of the implementations. -- The initial conditions. -- The sequence of the test events and test results. - -The following different types of test operator actions are considered during the test execution: - - -- A stimulus corresponds to an event that enforces a DUT to proceed with a specific protocol action, such as sending a message. -- A configure corresponds to an action to modify the DUT configuration. -- An IOP check consists of observing that one DUT behaves as described in the standard: i.e. resource creation, update, deletion, etc. For each IOP check in the Test Sequence, a result can be recorded. The overall IOP Verdict will be considered OK if all the IOP checks in the sequence are OK. -- In the context of Interoperability Testing with Conformance Checks, an additional step type, PRO checks can be used to verify the appropriate sequence and contents of protocol messages, this is helpful for debugging purposes. PRO Verdict will be PASS if all the PRO checks are PASS. - -## 5.2 Test Description naming convention - -|TD/<root>/<gr>/<nn> | | | -|-|-|-| -|<root> = root |M2M |oneM2M | -| | | | -|<gr> = group |NH |No Hop: Testing on Mca reference point | -| |NB |Non-Blocking scenario | -| |SH |Single Hop: management of remote resources on Mca + Mcc | -| |MH |Multi Hop | -| |SE |Security | -| | | | -| | | | -|<nn> = sequential number | |01 to 99 | - - - - - -## 5.3 Test Settings -This clause contains some test requirements applied to the testing, some constraints, restrictions for executions or some recommendations. - -In order to ease test setup and execution, the CSE and AE are requested to support the following settings: - - -- Security shall be disable as it is out of scope of this interoperability testing. -- Resource names are pre-provisioned, except for content instance resources that are automatically assigned by the hosting CSE. -- After each "Delete" primitive on a resource, the user shall check the resource is effectively deleted. -- Unless it is indicated in the test cases prerequisites, by default, all the applications shall have the required access rights to manage resources on the CSE. - -In order to address the TBDs in the oneM2M CoAP binding specification (oneM2M TS-0008 <a href="#_ref_3">[3]</a>), basic XML and JSON media-type numbers shall be used in the contentFormat option. - -In the test descriptions specified below, the following definitions of terms used for short-hand notation apply: - -Serialized Representation: refers to either an XML or a JSON representation of data in text-string format as defined in clauses 8.3 and 8.4 of oneM2M TS-0004 <a href="#_ref_2">[2]</a>. - -Host Address: refers to the authority part of a target URI as defined in IETF RFC 3986 <a href="#_ref_8">[8]</a> and IETF RFC 7230 <a href="#_ref_9">[9]</a> which can be represented as an IP literal encapsulated within square brackets, an IPv4 address in dotted decimal form, or a registered name, and optionally extended by a port identifier. - - -## 5.4 Pre-conditions - -### 5.4.1 Registration -The AE or CSE that originates the request has been successfully registered to its corresponding CSE. The registration of the AE includes the creation of <AE> resource under the <CSEBase> of its registrar CSE. The registration of the CSE includes the creation of <remoteCSE> resource representing itself under the <CSEBase> of its registrar CSE as well as the creation of <remoteCSE> resource representing the registrar CSE under its own <CSEBase> resource. The creation of <remoteCSE> resource representing the registrar CSE can be achieved by remotely retrieving the <CSEBase> resource of the registrar CSE. - - -### 5.4.2 Security -The Originator and the receiver have successfully established security association between each other. This may involve the exchange of key and the establishment of a security connection. - -The security pre-condition also assumes that the originator has the appropriate access control privilege towards the requested resource. - - -### 5.4.3 Service Subscription -Service subscription means that the originator is allowed to be connected with the oneM2M system by contract between the owner of the application and the service provider of the oneM2M system. This may require a corresponding information record in the <m2mServiceSubscriptionProfile> resource. - - -### 5.4.4 ID allocation -ID allocation means that the Originator has already acquired usable identity, either from its registrar CSE or the IN-CSE of the oneM2M system. The ID may be CSE relative or SP relative. The ID is then further used as the identity of the Originator to perform access control, charging, etc. - - -### 5.4.5 Existence of resource -Existence of resource means the resource been addressed and has already been created. - - -### 5.4.6 Management Session between Management Server and Management Client -Before the device management using external technologies is executed, it is required that a management session has already been established between the Management Server and Management Client. If there is no existing management session, the IN-CSE shall request the establishment of a management session between the Management Server and Management Client. - - -## 5.5 Binding message convention -In HTTP/CoAP/MQTT binding messages, the present document defines the convention for <variable>: - - -- <resourceType> represents a resource name (i.e. resourceName attribute) of a resource instance in that resourceType. For example, <CSEBase>/<AE> can represent "CSE1base/AE1" in structured resource ID format. -- <parameter> represents a value of a oneM2M request/response parameter. For example, <Request ID> can represent "0001" value of the Request ID parameter. Parameter names are case sensitive and in long names as specified in oneM2M TS-0004 <a href="#_ref_2">[2]</a>. -- <ID> represents an AE-ID or CSE-ID in MQTT Topic names. - -The value will be given at an interoperability test event. - -In oneM2M TS-0010 <a href="#_ref_5">[5]</a>, all oneM2M request/response parameters are carried in the MQTT message payload since it has no message header concept. Therefore, the MQTT message payload needs to be described more than HTTP and CoAP messages to describe those parameters in clause 8. In HTTP and CoAP binding messages, payloads are described as "empty" or "<container> resource to be created" in a very abstract way. - -Since the representation can be XML or JSON, payload should be abstract to support XML and JSON. The following example is an XML representation and its abstraction for creating a <container> resource. - + + + + + + + + + +|oneM2M<br />Technical Specification |oneM2M<br />Technical Specification | +|-|-| +|Document Number |TS-0013-V.3.3.1 | +|Document Name: |Interoperability Testing<br /> | +|Date: |2021-09-02 | +|Abstract: |The specification address the testing of the primitives on the oneM2M interfaces as specified in TS-0001 <a href="#_ref_1">[1]</a> and TS-0004 <a href="#_ref_2">[2]</a>. The purpose of the interoperability testing is to prove end-to-end functionality between Application Entities and Common Service Entities over the Mca and Mcc reference points<br /> | + + + + + + + + + + + + + +This Specification is provided for future development work within oneM2M only. The Partners accept no liability for any use of this Specification. + +The present document has not been subject to any approval process by the oneM2M Partners Type 1. Published oneM2M specifications and reports for implementation should be obtained via the oneM2M Partners' Publications Offices. + + + + + +<br />About oneM2M + +The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. + +More information about oneM2M may be found at: http//www.oneM2M.org + +Copyright Notification + +No part of this document may be reproduced, in an electronic retrieval system or otherwise, except as authorized by written permission. + +The copyright and the foregoing restriction extend to reproduction in all media. + +(c) 2021, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC). + +All rights reserved. + +Notice of Disclaimer & Limitation of Liability + +The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. + +NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. + +<br />Contents + + + +# 1 Scope +The present document specifies Interoperability Test Descriptions (TDs) for the oneM2M Primitives as specified in oneM2M TS-0001 <a href="#_ref_1">[1]</a>, oneM2M TS-0004 <a href="#_ref_2">[2]</a>, the bindings oneM2M TS-0008 <a href="#_ref_3">[3]</a>, oneM2M TS-0009 <a href="#_ref_4">[4]</a> and oneM2M TS-0010 <a href="#_ref_5">[5]</a>. + + +# 2 References + +## 2.1 Normative references +References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. + +The following referenced documents are necessary for the application of the present document. + + +- <a name="_ref_1">[1]</a> oneM2M TS-0001: "Functional Architecture- Release 3". +- <a name="_ref_2">[2]</a> oneM2M TS-0004: "Service Layer Core protocol Specification - Release 3". +- <a name="_ref_3">[3]</a> oneM2M TS-0008: "CoAP Protocol Binding Release 3". +- <a name="_ref_4">[4]</a> oneM2M TS-0009: "HTTP Protocol Binding - Release 3". +- <a name="_ref_5">[5]</a> oneM2M TS-0010: "MQTT Protocol Binding - Release 3". +- <a name="_ref_6">[6]</a> oneM2M TS-0015: "Testing Framework". +- <a name="_ref_7">[7]</a> oneM2M TS-0011: "Common Terminology". +- <a name="_ref_8">[8]</a> IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". +- <a name="_ref_9">[9]</a> IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". +- <a name="_ref_10">[10]</a> oneM2M TS-0005: "Management Enablement (OMA) - Release 3". +- <a name="_ref_11">[11]</a> oneM2M TS-0006: "Management Enablement (BBF) - Release 3". +- <a name="_ref_12">[12]</a> oneM2M TS-0003: "Security Solutions - Release 3". +- <a name="_ref_13">[13]</a> oneM2M TS-0034: "Semantics Support - Release 3". +- <a name="_ref_14">[14]</a> oneM2M TS-0023: "Home Appliances Information Model and Mapping - Release 3". +- <a name="_ref_15">[15]</a> oneM2M TS-0026: "3GPP interworking - Release 4". +- <a name="_ref_16">[16]</a> oneM2M TS-0040: "Modbus Interworking - Release 4". + +## 2.2 Informative references + +References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. + +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. + + +- <a name="_ref_i.1">[i.1]</a> oneM2M Drafting Rules. +> NOTE: Available at [http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf](http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf). + +- <a name="_ref_i.2">[i.2]</a> BBF TR-069: "CPE WAN Management Protocol". + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in oneM2M TS-0011 <a href="#_ref_7">[7]</a> and the following apply: + +> NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in oneM2M TS-0011 <a href="#_ref_7">[7]</a>. + +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 <a href="#_ref_i.2">[i.2]</a>, OMA DM <a href="#_ref_10">[10]</a>, etc. + +receiver CSE: any CSE that receives a request + +registrar CSE: CSE where an Application or another CSE has registered + +registree: AE or CSE that registers with another CSE + +resource: uniquely addressable entity in oneM2M architecture + +transit CSE: any receiver CSE that is not a Hosting CSE + + +## 3.2 Symbols +Void. + + +## 3.3 Abbreviations +For the purposes of the present document, the following abbreviations apply: + + +`ACP Access Control Policy` +`ACP-SD Access Control Policy-Semantic Descriptor` +`ADN-AE AE which resides in the Application Dedicated Node` +`AE Application Entity` +`AE-ID Application Entity Identifier` +`APP-ID Application Identifier` +`BBF BroadBand Forum` +`CFG Configuration` +`CoAP Constrained Application Protocol` +`CP Communication Patterns` +`CSE Common Services Entity` +`CSE-ID Common Service Entity Identifier` +`DAS Dynamic Authorization System` +`DDN Downlink Data Notification` +`DM Device Management` +`DTLS Datagram Transport Layer Security` +`DUT Device Under Test` +`ECDHE Elliptic-curve Diffie-Hellman` +`FQDN Fully Qualified Domain Name` +`HAIM Home Appliances Information Model` +`HSS Home Subscriber Serve` +`HTTP HyperText Transfer Protocol` +`IN Infrastructure Node` +`IN-AE Application Entity that is registered with the CSE in the Infrastructure Node` +`IN-CSE CSE which resides in the Infrastructure Node` +`IOP Interoperability` +`IP Internet Protocol` +`IPE Interworking Proxy Entity` +`JSON JavaScript Object Notation` +`LWM2M Lightweight M2M` +`M2M Machine to Machine` +`MA Mandatory Announced` +`MBMS Multimedia Broadcast Multicast Service` +`Mca Reference Point for M2M Communication with AE` +`Mcc Reference Point for M2M Communication with CSE` +`MEF M2M Enrolment Function` +`MH Multi Hop` +`MNO Mobile Network Operator` +`MO Management Object` +`MQTT Message Queuing Telemetry Transport` +`MT Mobile Terminated` +`NB Non-Blocking` +`NH No Hop` +`NIDD non-IP Data Delivery` +`NODN Non oneM2M Device Node` +`OMA Open Mobile Alliance` +`PDN Packet Data Network` +`PRO Protocol` +`PSK Pre-Shared Key` +`PSM Power Savings Mode` +`RDS Reliable Data Service` +`RFC Request for Comments` +`RP Reference Point` +`RPC Remote Procedure Calls` +`RQI Request-ID` +`SCEF Service Capability Exposure Function` +`SD Semantic Descriptor` +`SE Security` +`SGS Semantic Graph Store` +`SH Single Hop` +`SP Service Provider` +`SPARQL SPARQL Protocol and RDF Query Language` +`SUID Security Usage Identifier` +`SUT System Under Test` +`TCP [Transmission Control Protocol](Transmission Control Protocol)` +`TD Test Description` +`TLS Transport Layer Security` +`TMGI Temporary Mobile Group Identity` +`TP Traffic Pattern` +`UDP User Datagram Protocol` +`URI Uniform Resource Identifier` +`XML eXtensible Markup Language` + +# 4 Conventions + +The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules <a href="#_ref_i.1">[i.1]</a>. + + +# 5 Testing conventions + +## 5.1 The Test Description proforma +The testing methodology used in the present document is specified in the oneM2M TS-0015 <a href="#_ref_6">[6]</a>. + +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 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 equipment (protocol monitors, 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 include, at a minimum, the following fields as indicated table 5.1-1. + + +**Table 5.1-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 in the document. | +|References |A list of references to the base specification section(s), use case(s), requirement(s) and Test Purposes 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 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. | +|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 descriptions are provided in proforma tables. In order to ensure the correct execution of an interoperability test, the following information is provided in the test description: + + +- The configuration applied for the test. +- The need of additional equipment (protocol monitors, functional equipment, etc.) required to achieve the correct behaviour of the implementations. +- The initial conditions. +- The sequence of the test events and test results. + +The following different types of test operator actions are considered during the test execution: + + +- A stimulus corresponds to an event that enforces a DUT to proceed with a specific protocol action, such as sending a message. +- A configure corresponds to an action to modify the DUT configuration. +- An IOP check consists of observing that one DUT behaves as described in the standard: i.e. resource creation, update, deletion, etc. For each IOP check in the Test Sequence, a result can be recorded. The overall IOP Verdict will be considered OK if all the IOP checks in the sequence are OK. +- In the context of Interoperability Testing with Conformance Checks, an additional step type, PRO checks can be used to verify the appropriate sequence and contents of protocol messages, this is helpful for debugging purposes. PRO Verdict will be PASS if all the PRO checks are PASS. + +## 5.2 Test Description naming convention + +|TD/<root>/<gr>/<nn> | | | +|-|-|-| +|<root> = root |M2M |oneM2M | +| | | | +|<gr> = group |NH |No Hop: Testing on Mca reference point | +| |NB |Non-Blocking scenario | +| |SH |Single Hop: management of remote resources on Mca + Mcc | +| |MH |Multi Hop | +| |SE |Security | +| | | | +| | | | +|<nn> = sequential number | |01 to 99 | + + + + + +## 5.3 Test Settings +This clause contains some test requirements applied to the testing, some constraints, restrictions for executions or some recommendations. + +In order to ease test setup and execution, the CSE and AE are requested to support the following settings: + + +- Security shall be disable as it is out of scope of this interoperability testing. +- Resource names are pre-provisioned, except for content instance resources that are automatically assigned by the hosting CSE. +- After each "Delete" primitive on a resource, the user shall check the resource is effectively deleted. +- Unless it is indicated in the test cases prerequisites, by default, all the applications shall have the required access rights to manage resources on the CSE. + +In order to address the TBDs in the oneM2M CoAP binding specification (oneM2M TS-0008 <a href="#_ref_3">[3]</a>), basic XML and JSON media-type numbers shall be used in the contentFormat option. + +In the test descriptions specified below, the following definitions of terms used for short-hand notation apply: + +Serialized Representation: refers to either an XML or a JSON representation of data in text-string format as defined in clauses 8.3 and 8.4 of oneM2M TS-0004 <a href="#_ref_2">[2]</a>. + +Host Address: refers to the authority part of a target URI as defined in IETF RFC 3986 <a href="#_ref_8">[8]</a> and IETF RFC 7230 <a href="#_ref_9">[9]</a> which can be represented as an IP literal encapsulated within square brackets, an IPv4 address in dotted decimal form, or a registered name, and optionally extended by a port identifier. + + +## 5.4 Pre-conditions + +### 5.4.1 Registration +The AE or CSE that originates the request has been successfully registered to its corresponding CSE. The registration of the AE includes the creation of <AE> resource under the <CSEBase> of its registrar CSE. The registration of the CSE includes the creation of <remoteCSE> resource representing itself under the <CSEBase> of its registrar CSE as well as the creation of <remoteCSE> resource representing the registrar CSE under its own <CSEBase> resource. The creation of <remoteCSE> resource representing the registrar CSE can be achieved by remotely retrieving the <CSEBase> resource of the registrar CSE. + + +### 5.4.2 Security +The Originator and the receiver have successfully established security association between each other. This may involve the exchange of key and the establishment of a security connection. + +The security pre-condition also assumes that the originator has the appropriate access control privilege towards the requested resource. + + +### 5.4.3 Service Subscription +Service subscription means that the originator is allowed to be connected with the oneM2M system by contract between the owner of the application and the service provider of the oneM2M system. This may require a corresponding information record in the <m2mServiceSubscriptionProfile> resource. + + +### 5.4.4 ID allocation +ID allocation means that the Originator has already acquired usable identity, either from its registrar CSE or the IN-CSE of the oneM2M system. The ID may be CSE relative or SP relative. The ID is then further used as the identity of the Originator to perform access control, charging, etc. + + +### 5.4.5 Existence of resource +Existence of resource means the resource been addressed and has already been created. + + +### 5.4.6 Management Session between Management Server and Management Client +Before the device management using external technologies is executed, it is required that a management session has already been established between the Management Server and Management Client. If there is no existing management session, the IN-CSE shall request the establishment of a management session between the Management Server and Management Client. + + +## 5.5 Binding message convention +In HTTP/CoAP/MQTT binding messages, the present document defines the convention for <variable>: + + +- <resourceType> represents a resource name (i.e. resourceName attribute) of a resource instance in that resourceType. For example, <CSEBase>/<AE> can represent "CSE1base/AE1" in structured resource ID format. +- <parameter> represents a value of a oneM2M request/response parameter. For example, <Request ID> can represent "0001" value of the Request ID parameter. Parameter names are case sensitive and in long names as specified in oneM2M TS-0004 <a href="#_ref_2">[2]</a>. +- <ID> represents an AE-ID or CSE-ID in MQTT Topic names. + +The value will be given at an interoperability test event. + +In oneM2M TS-0010 <a href="#_ref_5">[5]</a>, all oneM2M request/response parameters are carried in the MQTT message payload since it has no message header concept. Therefore, the MQTT message payload needs to be described more than HTTP and CoAP messages to describe those parameters in clause 8. In HTTP and CoAP binding messages, payloads are described as "empty" or "<container> resource to be created" in a very abstract way. + +Since the representation can be XML or JSON, payload should be abstract to support XML and JSON. The following example is an XML representation and its abstraction for creating a <container> resource. + + +|XML payload example for MQTT binding |<?xml version="1.0" encoding="UTF-8"?><br /> <m2m:req xmlns:m2m="http://www.onem2m.org/xml/protocols" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.onem2m.org/xml/protocols CDT-requestPrimitive-v1_0_0.xsd"><br /> <op>1</op><br /> <to>CSE1Base</to><br /> <fr>/CSE1/C_AE1</fr><br /> <rqi>2001</rqi><br /> <ty>3</ty><br /> <nm>cont1</nm><br /> <rti><rt>3</rt></rti><br /> <pc><br /> <cnt><br /> <lbl>SmartMeter</lbl><br /> <et>20141003T112033</et><br /> </cnt><br /> </pc><br /></m2m:req> | +|-|-| +|Abstracted payload example for MQTT binding |op = 1<br />to = CSE1Base<br />fr = /CSE1/C_AE01<br />rqi = 3001<br />ty = 3<br />name = cont1<br />rti.rt = 3<br />pc.cnt.lbl = SmartMeter<br />pc.cnt.et = 20141003T112033 | +|Abstracted payload example for MQTT binding adopting the payload convention |op = 1<br />to = <CSEBase><br />fr = <From><br />rqi = <Request ID><br />ty = 3<br />name = <Name><br />rti.rt = 3<br />pc = <Content> | + + + + +# 6 Test Description Summary + +## 6.1 Tests list + +|Nb |Category |Procedure/Resource |TD ID |TD Description | +|-|-|-|-|-| +|1 |Resource management<br /><br />Single Hop |CSEBase Management |TD_M2M_NH_01 |AE retrieves the CSEBase resource | +|2 |Resource management<br /><br />Single Hop |RemoteCSE |TD_M2M_NH_02 |Registree CSE registers to Registrar CSE | +|3 |Resource management<br /><br />Single Hop |RemoteCSE |TD_M2M_NH_03 |Registree CSE retrieves RemoteCSE from Registrar CSE | +|4 |Resource management<br /><br />Single Hop |RemoteCSE |TD_M2M_NH_04 |Registree CSE updates RemoteCSE from Registrar CSE | +|5 |Resource management<br /><br />Single Hop |RemoteCSE |TD_M2M_NH_05 |Registree CSE deletes RemoteCSE from Registrar CSE | +|6 |Resource management<br /><br />Single Hop |Application Entity |TD_M2M_NH_06 |AE registers to its registrar CSE via an AE Create Request | +|7 |Resource management<br /><br />Single Hop |Application Entity |TD_M2M_NH_07 |AE retrieves <AE> resource via an AE Retrieve Request | +|8 |Resource management<br /><br />Single Hop |Application Entity |TD_M2M_NH_08 |AE updates attribute in <AE> resource via an AE Update Request | +|9 |Resource management<br /><br />Single Hop |Application Entity |TD_M2M_NH_09 |AE de-registers by deleting <AE> resource via an AE Delete Request | +|10 |Resource management<br /><br />Single Hop |Container |TD_M2M_NH_10 |AE creates a container resource in registrar CSE via a container Create Request | +|11 |Resource management<br /><br />Single Hop |Container |TD_M2M_NH_11 |AE retrieves information of a container resource via a container Retrieve Request | +|12 |Resource management<br /><br />Single Hop |Container |TD_M2M_NH_12 |AE updates attribute in application resource via a container Update Request | +|13 |Resource management<br /><br />Single Hop |Container |TD_M2M_NH_13 |AE deletes a specific container resource via a container Delete Request | +|14 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_14 |AE adds a contentInstance resource <contentInstance> to a specific container in Registrar CSE via a contentInstance Create Request and the registrar CSE updates the parent <container> resource with stateTag, and currentNrOfInstances, CurrentByteSize attributes correspondingly | +|15 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_15 |AE retrieves information of a contentInstance resource via a contentInstance Retrieve Request | +|16 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_17 |AE deletes contentInstance resource via a Delete Request and the registrar CSE updates the parent <container> resource with currentNrOfInstances, and CurrentByteSize attribute correspondingly | +|17 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_49 |AE deletes a <latest> resource in a <container> and the Registrar CSE points a latest <contentInstance> among the existing contentInstances to the <latest> resource of the <container> | +|18 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_50 |AE deletes a <oldest> resource in a <container> resource and the Registrar CSE points an oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> | +|19 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_51 |AE sends a <contentInstance> CREATE request to a <container> which contains attribute currentNrOfInstances whose value equals to that of maxNrOfInstances and Registrar CSE deletes the oldest <contentInstance> from the parent <container> and then creates the requested <contentInstance> resource | +|20 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_102 |AE retrieves a <latest> resource of a <container> for which attribute locationID is configured, value of locationUpdatePeriod is marked '0' or not defined and locationSource attribute is 'Network Based' | +|21 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_71 |AE retrieves a <latest> resource of a <container> and the Registrar CSE points a latest <contentInstance> among the existing contentInstances to the <latest> resource of the <container> | +|22 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_72 |AE retrieves a <oldest> resource of a <container> and the Registrar CSE points a oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> | +|23 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_18 |AE discovers resources residing in Registrar CSE | +|24 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_19 |AE discovers accessible resources residing in Registrar CSE using the label filter criteria | +|25 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_20 |AE discovers accessible resources residing in Registrar CSE limiting the number of matching resources to the specified value | +|26 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_21 |AE discovers accessible resources residing in Registrar CSE using multiple Filter Criteria | +|27 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_58 |AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 1 | +|28 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_59 |AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 2 | +|29 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_60 |AE1 discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 3 | +|30 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_61 |AE discovers accessible resources residing in Registrar CSE using the offset filter criteria value set to 3 | +|31 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_62 |AE discovers all the accessible resources residing in Registrar CSE using the offset filter criteria | +|32 |Resource management<br /><br />Single Hop |Subscription |TD_M2M_NH_22 |AE creates a subscription to Application Entity resource via subscription Create Request | +|33 |Resource management<br /><br />Single Hop |Subscription |TD_M2M_NH_23 |AE retrieves information about a subscription via subscription Retrieve Request such as expirationTime, labels, etc. | +|34 |Resource management<br /><br />Single Hop |Subscription |TD_M2M_NH_24 |AE updates information about a subscription via subscription Retrieve Request | +|35 |Resource management<br /><br />Single Hop |Subscription |TD_M2M_NH_25 |AE cancels subscription via an subscription Delete Request | +|36 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_26 |AE creates an accessControlPolicy resource | +|37 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_27 |AE retrieves accessControlPolicy resource | +|38 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_28 |AE updates attribute in accessControlPolicy resource | +|39 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_29 |AE deletes accessControlPolicy resource | +|40 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_30 |AE delete request is rejected due to accessControlPolicy | +|41 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_73 |AE delete request is rejected due to accessControlPolicy (accessControlOriginators) | +|42 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_74 |AE delete request is allowed due to accessControlPolicy | +|43 |Resource management<br /><br />Single Hop |Group |TD_M2M_NH_31 |AE creates a group resource | +|44 |Resource management<br /><br />Single Hop |Group |TD_M2M_NH_32 |AE retrieves group resource | +|45 |Resource management<br /><br />Single Hop |Group |TD_M2M_NH_33 |AE updates attribute in group resource | +|46 |Resource management<br /><br />Single Hop |Group |TD_M2M_NH_34 |AE deletes group resource | +|47 |Resource management<br /><br />Single Hop |Node |TD_M2M_NH_35 |AE creates a node resource | +|48 |Resource management<br /><br />Single Hop |Node |TD_M2M_NH_36 |AE retrieves node resource | +|49 |Resource management<br /><br />Single Hop |Node |TD_M2M_NH_37 |AE updates attribute in node resource | +|50 |Resource management<br /><br />Single Hop |Node |TD_M2M_NH_38 |AE deletes node resource | +|51 |Resource management<br /><br />Single Hop |PollingChannel |TD_M2M_NH_39 |AE creates a <pollingChannel> resource in registrar CSE via a Create Request | +|52 |Resource management<br /><br />Single Hop |PollingChannel |TD_M2M_NH_40 |AE retrieves information of a pollingChannel resource via a Retrieve Request | +|53 |Resource management<br /><br />Single Hop |PollingChannel |TD_M2M_NH_41 |AE updates attribute in pollingChannel resource via a Update Request | +|54 |Resource management<br /><br />Single Hop |PollingChannel |TD_M2M_NH_42 |AE deletes a pollingChannel resource via a Delete Request | +|55 |Resource management<br /><br />Single Hop |PollingChannel |TD_M2M_NH_43 |AE retrieves information of a pollingChannel resource via a Retrieve Request | +|56 |Resource management<br /><br />Single Hop |FanoutPoint |TD_M2M_NH_44 |AE creates a <contentInstance> resource in each group member | +|57 |Resource management<br /><br />Single Hop |FanoutPoint |TD_M2M_NH_45 |AE retrieves the <container> resource from in each group member | +|58 |Resource management<br /><br />Single Hop |FanoutPoint |TD_M2M_NH_46 |AE updates an <container> resource of each member resource | +|59 |Resource management<br /><br />Single Hop |FanoutPoint |TD_M2M_NH_47 |AE deletes a <container> of each member | +|60 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_48 |AE receives a notification request from the HOST CSE | +|61 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_80 |AE2 sends maxNrOfInstances UPDATE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has specific setting in eventNotificationCriteria, Hosting CSE send notification to AE1 | +|62 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_81 |AE2 sends DELETE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has notificationEventType with 'Delete of Resource', Hosting CSE send notification to AE1 | +|63 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_82 |AE2 sends <contentInstance> CREATE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has notificationEventType with ''Create of Direct Child 'Resource', Hosting CSE send notification to AE1 | +|64 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_83 |AE2 sends DELETE request to the <contentInstance> which located under the subscribed-to resource. Since <subscription> resource has notificationEventType with 'Delete of Direct Child Resource', Hosting CSE send notification to AE1 | +|65 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_89 |AE creates <subscription> resources by sending Create Request to the fanOutPoint. <br />Since AE has set notifyAggregation to 2, Hosting CSE aggregate notification and send aggregated notification to AE | +|66 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_52 |AE creates a flexcontainer resource in Registrar CSE via a flexcontainer Create Request | +|67 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_53 |AE retrieves information of a flexContainer resource via a flexContainer Retrieve Request | +|68 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_54 |AE updates attribute in application resource via a flexContainer Update Request | +|69 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_55 |AE deletes a specific container resource via a container Delete Request | +|70 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_56 |AE receives a notification request on flexContainer update from the HOST CSE | +|71 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_57 |AE discovers accessible resources residing in Registrar CSE using attribute filter criteria which has a customAttribute name and value assigned to it | +|72 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_63 |AE creates a mgmtCmd resource | +|73 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_64 |AE retrieves mgmtCmd resource | +|74 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_65 |AE updates attribute (not with 'true' in execEnable attribute) in mgmtCmd resource | +|75 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_66 |AE updates attribute (with 'true' in execEnable attribute) in mgmtCmd resource | +|76 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_67 |AE deletes mgmtCmd resource | +|77 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_68 |AE retrieves execInstance resource | +|78 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_69 |AE updates attribute 'execDisable' to true in execInstance resource to cancel pending management command | +|79 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_70 |AE deletes execInstance resource | +|80 |Resource management<br /><br />Single Hop |SemanticDescriptor Management |TD_M2M_NH_75 |AE creates a SemanticDescriptor resource in Registrar CSE via a SemanticDescriptor Create Request | +|81 |Resource management<br /><br />Single Hop |SemanticDescriptor Management |TD_M2M_NH_76 |AE retrieves information of a semanticDescriptor resource via a semanticDescriptor Retrieve Request | +|82 |Resource management<br /><br />Single Hop |SemanticDescriptor Management |TD_M2M_NH_77 |AE updates attribute in <semanticDescriptor> resource via a semanticDescriptor Update Request | +|83 |Resource management<br /><br />Single Hop |SemanticDescriptor Management |TD_M2M_NH_78 |AE deletes SemanticDescriptor resource via a SemanticDescriptor Delete Request | +|84 |Resource management<br /><br />Single Hop |Semantic Resource Discovery |TD_M2M_NH_79 |AE discovers accessible resources residing in Registrar CSE using the semanticFilter filter criteria | +|85 |Resource management<br /><br />Single Hop |ResultContent |TD_M2M_NH_84 |Check creation of <container> resource with result content set to 0(nothing) | +|86 |Resource management<br /><br />Single Hop |ResultContent |TD_M2M_NH_85 |Check creation of <container> resource with result content set to 1(attributes) | +|87 |Resource management<br /><br />Single Hop |ResultContent |TD_M2M_NH_86 |Check creation of <container> resource with result content set to 2(hierarchical address) | +|88 |Resource management<br /><br />Single Hop |ResultContent |TD_M2M_NH_87 |Check creation of <container> resource with result content set to 3(hierarchical address and attributes) | +|89 |Resource management<br /><br />Single Hop |ResultContent |TD_M2M_NH_88 |Check retrievability of <container> resource with result content set to 4(attributes and child resources) | +|90 |Resource management<br /><br />Single Hop |timeSeries |TD_M2M_NH_90 |AE creates a <timeSeries> resource in registrar CSE via a Create Request | +|91 |Resource management<br /><br />Single Hop |timeSeries |TD_M2M_NH_91 |AE retrieves information of a <timeSeries> resource via a Retrieve Request | +|92 |Resource management<br /><br />Single Hop |timeSeries |TD_M2M_NH_92 |AE updates attribute in <timeSeries> resource via a Update Request | +|93 |Resource management<br /><br />Single Hop |timeSeries |TD_M2M_NH_93 |AE deletes a <timeSeries> resource via a Delete Request | +|94 |Resource management<br /><br />Single Hop |timeSeriesInstance |TD_M2M_NH_94 |AE sends Create Request of a <timeSeriesInstance> resource to a <timeSeries> resource in Registrar CSE. Registrar CSE creates the <timeSeriesInstance> resource and updates the parent <timeSeries> resource with currentNrOfInstances and currentByteSize attributes correspondingly | +|95 |Resource management<br /><br />Single Hop |timeSeriesInstance |TD_M2M_NH_95 |AE retrieves information of a <timeSeriesInstance> resource via a Retrieve Request | +|96 |Resource management<br /><br />Single Hop |timeSeriesInstance |TD_M2M_NH_96 |AE sends Delete Request of a <timeSeriesInstance> resource in Registrar CSE. Registrar CSE delete the <timeSeriesInstance> resource and updates the parent <timeSeries> resource with currentNrOfInstances and currentByteSize attributes correspondingly | +|97 |Resource management<br /><br />Single Hop |timeSeriesInstance |TD_M2M_NH_97 |AE sends a <timeSeriesInstance> resource Create Request to a <timeSeries> resource which contains currentNrOfInstances value equals to that of maxNrOfInstances and Registrar CSE delets the oldest <timeSeriesInstance> resource from the <timeSeries> resource and then creates the requested <timeSeriesInstance> resource | +|98 |Resource management<br /><br />Single Hop |LocationPolicy |TD_M2M_NH_98 |AE creates a <locationPolicy> resource in registrar CSE via a locationPolicy Create Request | +|99 |Resource management<br /><br />Single Hop |LocationPolicy |TD_M2M_NH_99 |AE retrieves information of a <locationPolicy> resource via a locationPolicy Retrieve Request | +|100 |Resource management<br /><br />Single Hop |LocationPolicy |TD_M2M_NH_100 |AE updates attribute in <locationPolicy> resource via a locationPolicy Update Request | +|101 |Resource management<br /><br />Single Hop |LocationPolicy |TD_M2M_NH_101 |AE deletes a specific <locationPolicy> resource via a locationPolicy Delete Request | +|102 |Resource management<br /><br />Single Hop |Schedule |TD_M2M_NH_155 |AE creates a <schedule> resource in Registrar CSE via a Schedule Create Request | +|103 |Resource management<br /><br />Single Hop |Schedule |TD_M2M_NH_156 |AE retrieves information of a <schedule> resource via a schedule Retrieve Request | +|104 |Resource management<br /><br />Single Hop |Schedule |TD_M2M_NH_157 |AE updates attribute in <schedule> resource via a schedule Update Request | +|105 |Resource management<br /><br />Single Hop |Schedule |TD_M2M_NH_158 |AE deletes Schedule resource via a Schedule Delete Request | +|106 |Resource management<br /><br />Single Hop |Schedule |TD_M2M_NH_159 |CSE sends a notification request to the AE when Schedule resource is configured | +|107 |Non-Blocking |Synchronous request<br /> |TD_M2M_NB_01 |AE creates a container resource using non-blocking synchronous request in registrar CSE | +|108 |Non-Blocking |Synchronous request<br /> |TD_M2M_NB_02 |AE retrieves a Container resource using non-blocking synchronous request in registrar CSE | +|109 |Non-Blocking |Synchronous request<br /> |TD_M2M_NB_03 |AE updates a Container resource using non-blocking synchronous request in registrar CSE | +|110 |Non-Blocking |Synchronous request<br /> |TD_M2M_NB_04 |AE deletes a Container resource using non-blocking synchronous request | +|111 |Non-Blocking |Asynchronous request |TD_M2M_NB_05 |AE creates a container resource using non-blocking asynchronous request | +|112 |Non-Blocking |Asynchronous request |TD_M2M_NB_06 |AE retrieves a Container resource using non-blocking asynchronous request | +|113 |Non-Blocking |Asynchronous request |TD_M2M_NB_07 |AE updates a Container resource using non-blocking asynchronous request | +|114 |Non-Blocking |Asynchronous request |TD_M2M_NB_08 |AE deletes a Container resource using non-blocking asynchronous request | +|115 |Single Hop |Retargeting |TD_M2M_SH_01 |AE creates a remote <Resource> resource | +|116 |Single Hop |Retargeting |TD_M2M_SH_02 |AE retrieves a remote <Resource> resource | +|117 |Single Hop |Retargeting |TD_M2M_SH_03 |AE updates a remote <Resource> resource | +|118 |Single Hop |Retargeting |TD_M2M_SH_04 |AE delete a remote <Resource> resource | +|119 |Single Hop |Discovery |TD_M2M_SH_09 |AE discovers accessible resources residing in the remote Hosting CSE using multiple Filter Criteria | +|120 |Single Hop |Unauthorized operation |TD_M2M_SH_10 |AE delete request is rejected after access rights verification using retargeting | +|121 |Single Hop |Notification |TD_M2M_SH_11 |AE receives a notification request from the remote hosting CSE | +|122 |Single Hop |mgmtObj |TD_M2M_SH_05 |AE creates a <mgmtObj> resource | +|123 |Single Hop |mgmtObj |TD_M2M_SH_06 |AE updates a <mgmtObj> resource | +|124 |Single Hop |mgmtObj |TD_M2M_SH_07 |AE retrieves a <mgmtObj> resource | +|125 |Single Hop |mgmtObj |TD_M2M_SH_08 |AE deletes a <mgmtObj> resource | +|126 |Single Hop |Announcement |TD_M2M_SH_12 |AE1 announces itself to CSE2 | +|127 |Single Hop |Announcement |TD_M2M_SH_13 |AE1 announces a child container to CSE2 | +|128 |Single Hop |Announcement |TD_M2M_SH_14 |AE1 announces an Optional Announce attribute to CSE2 | +|129 |Single Hop |Announcement |TD_M2M_SH_15 |AE2 retrieves an Announced Resource | +|130 |Single Hop |Announcement |TD_M2M_SH_16 |AE2 retrieves the original resource representation of an announced resource | +|131 |Single Hop |Announcement |TD_M2M_SH_21 |ContainerAnnc Delete by updating announceTo attribute. AE1 deletes its announced child container from CSE2 | +|132 |Single Hop |Announcement |TD_M2M_SH_22 |ContainerAnnc Delete by deleting original resource. AE1 deletes its announced child container from CSE2 | +|133 |Single Hop |Announcement |TD_M2M_SH_23 |Announced attribute Create by addition to announcedAttribute attribute AE1 announces an announcable attribute of its child container to CSE2 | +|134 |Single Hop |Announcement |TD_M2M_SH_24 |Announced attribute Create by creation of a MA attribute at the original resource. AE1 announces an MA attribute of its child container to CSE2 | +|135 |Single Hop |Announcement |TD_M2M_SH_25 |Announced attribute Delete by deletion from announcedAttribute attribute. AE1 de-announces an announcable attribute of its child container to CSE2 | +|136 |Single Hop |Announcement |TD_M2M_SH_26 |Announced attribute Delete by deletion of a MA attribute at the original resource. AE1 de-announces an MA attribute (conditionally mandatory) of its child container to CSE2 | +|137 |Single Hop |fanOut |TD_M2M_SH_17 |AE creates a <contentInstance> resource in each group member, where some memberIDs are on a remoteCSE | +|138 |Single Hop |fanOut |TD_M2M_SH_18 |AE retrieves a <contentInstance> resource from each group member, where some memberIDs are on a remoteCSE | +|139 |Single Hop |fanOut |TD_M2M_SH_19 |AE updates a <container> resource in each group member, where some memberIDs are on a remoteCSE | +|140 |Single Hop |fanOut |TD_M2M_SH_20 |AE deletes a <contentInstance> resource from each group member, where some memberIDs are on a remoteCSE | +|141 |Security |Secure AE Registration |TD_M2M_SE_01 |AE uses Provisioned Symmetric Key Security Association Establishment Framework to enable mutual authentication with the Registrar CSE. Registrar CSE performs AE authorization check on incoming AE registration request | +|142 |Security |Authentication |TD_M2M_SE_02 |AE establishes mutual authentication with the Registrar CSE using Provisioned Symmetric Key Security Association Establishment Framework | +|143 |Security |Authentication |TD_M2M_SE_03 |AE establishes mutual authentication with the Registrar CSE using Certificate-Based Security Association Establishment Framework | +|144 |Security |Authorization |TD_M2M_SE_04 |AE accesses <accessControlPolicy> resource using its selfPrivileges credentials | +|145 |Security |Authorization |TD_M2M_SE_05 |AE accesses <AE> resource using its accessControlPolicyIDs attribute | +|146 |Security |Authorization |TD_M2M_SE_06 |AE accesses <AE> resource using default access privileges | +|147 |Security |Authorization |TD_M2M_SE_07 |AE accesses <AE> resource using default access privileges | +|148 |Security |Authorization |TD_M2M_SE_08 |AE accesses <AE> resource using Direct Dynamic Authorization | +|149 |Security |Authorization |TD_M2M_SE_09 |AE accesses <AE> resource using Indirect Dynamic Authorization | +|150 |Security |Key provisioning management |TD_M2M_SE_10 |A MEF Handshake procedure establishes a mutually authenticated TLS session for protecting the communication between an MEF Client and MEF using pre-provisioned certificates | +|151 |Security |Key provisioning management |TD_M2M_SE_11 |A MEF Handshake procedure establishes a mutually authenticated TLS or DTLS session for protecting the communication between an MEF Client and MEF using pre-provisioned Master Credentials | +|152 |Security |Key provisioning management |TD_M2M_SE_12 |The MEF Client registers with the MEF to confirm that it is willing to use the services of the MEF, under the authorization of the administrating stakeholder | +|153 |Security |Key provisioning management |TD_M2M_SE_13 |The MEF Client retrieves MEF Client Configurations provided by the administrating stakeholder to the MEF | +|154 |Security |Key provisioning management |TD_M2M_SE_14 |MEF Client updates the MEF Client registration by any combination of extending the expirationTime of the MEF Client Registration record or updating the labels | +|155 |Security |Key provisioning management |TD_M2M_SE_15 |The MEF Client registers with the MEF to confirm that it is willing to use the services of the MEF, under the authorization of the administrating stakeholder | +|156 |Security |Key provisioning management |TD_M2M_SE_16 |Source MEF Client establishes a symmetric key with the MEF which can be retrieved for use by one or more Target MEF Clients | +|157 |Security |Key provisioning management |TD_M2M_SE_17 |The Target MEF Client to retrieve the Key Value from a MEF corresponding to a RelativeKeyID received by the Target MEF Client | +|158 |Security |Key provisioning management |TD_M2M_SE_18 |MEF Client updates the MEF Client registration by any combination of extending the expirationTime of the MEF Client Registration record or updating the labels | +|159 |Security |Key provisioning management |TD_M2M_SE_19 |Source MEF Client requests the MEF to stop distributing the registered key | +|160 |Security |End-to-End security management |TD_M2M_SE_20 |AE sends an arbitrary request primitive inside of ESPrim Object to CSE | +|161 |Security |End-to-End security management |TD_M2M_SE_21 |AE establishes a connection with the Registrar CSE using pairwiseE2EKey | +|163 |HAIM |HAIM Device Model |TD_M2M_NH_102 |AE1 creates a HAIM Light Device Model | +|164 |HAIM |HAIM Device Model |TD_M2M_NH_103 |AE2 reads the status of a HAIM Light Device Model | +|165 |HAIM |HAIM Device Model |TD_M2M_NH_104 |AE2 turns the binarySwitch of a HAIM Light Device Model "ON" or "OFF" | +|166 |HAIM |HAIM Device Model |TD_M2M_NH_105 |AE2 toggles the state of a HAIM Light Device Model | +|167 |HAIM |HAIM Device Model |TD_M2M_NH_160 |AE1 creates a Power Outlet SubDevice Model | +|168 |HAIM |HAIM Device Model |TD_M2M_NH_161 |AE1 creates a Toggle Action Model | +|169 |HAIM |HAIM Device Model |TD_M2M_NH_162 |AE1 creates Device Properties Model | +|170 |Semantics |Semantic Access Control Policy |TD_M2M_NH_106 |ACP triples are created when a new <accessControlPolicy> resource is created | +|171 |Semantics |Semantic Access Control Policy |TD_M2M_NH_107 |ACP triples are updated when an existing <accessControlPolicy> resource is updated | +|172 |Semantics |Semantic Access Control Policy |TD_M2M_NH_108 |ACP triples are deleted when an existing <accessControlPolicy> resource is deleted | +|173 |Semantics |Semantic Access Control Policy |TD_M2M_NH_109 |ACP-SD Binding Triples and SD relationship in SGS are created when AE creates a <semanticDescriptor> resource in Registrar CSE | +|174 |Semantics |Semantic Access Control Policy |TD_M2M_NH_110 |ACP-SD Binding Triples are updated when the accessControlPolicyIDs attribute of a <semanticDescriptor> resource is updated | +|175 |Semantics |Semantic Access Control Policy |TD_M2M_NH_111 |SD Relationship Triples are updated when the descriptor attribute of a <semanticDescriptor> resource is changed | +|176 |Semantics |Semantic Access Control Policy |TD_M2M_NH_112 |SD Relationship Triples are deleted when the descriptor attribute of a <semanticDescriptor> resource is deleted | +|177 |Semantics |Semantic Filtering and discovery |TD_M2M_NH_113 |AE discovers accessible resources residing in Registrar CSE using the <semanticFanOutPoint> | +|178 |Semantics |Semantic Filtering and discovery |TD_M2M_NH_114 |AE discovers accessible resources residing in Registrar CSE using the resource link-based Semantic Discovery | +|179 |Semantics |Semantic Filtering and discovery |TD_M2M_NH_115 |AE performs a Semantic Query request in Registrar CSE using the semanticFilter filter criteria | +|180 |Semantics |Semantic Mashup |TD_M2M_NH_116 |AE creates a SemanticMashupJobProfile resource in Registrar CSE via a SemanticMashupJobProfile Create Request | +|181 |Semantics |Semantic Mashup |TD_M2M_NH_117 |AE retrieves information of a semanticMashupJobProfile resource via a semanticMashupJobProfile Retrieve Request | +|182 |Semantics |Semantic Mashup |TD_M2M_NH_118 |AE updates attribute in <semanticMashupJobProfile> resource via a semanticMashupJobProfile Update Request | +|183 |Semantics |Semantic Mashup |TD_M2M_NH_119 |AE deletes semanticMashupJobProfile resource via a semanticMashupJobProfile Delete Request | +|184 |Semantics |Semantic Mashup |TD_M2M_NH_120 |AE creates a semanticMashupInstance resource in Registrar CSE via a semanticMashupInstance Create Request | +|185 |Semantics |Semantic Mashup |TD_M2M_NH_121 |AE retrieves information of a semanticMashupInstance resource via a semanticMashupInstance Retrieve Request | +|186 |Semantics |Semantic Mashup |TD_M2M_NH_122 |AE updates attribute in <semanticMashupInstance> resource via a semanticMashupInstance Update Request | +|187 |Semantics |Semantic Mashup |TD_M2M_NH_123 |AE deletes semanticMashupInstance resource via a semanticMashupInstance Delete Request | +|188 |Semantics |Semantic Mashup |TD_M2M_NH_124 |AE retrieves information of a semanticMashupResult resource via a semanticMashupResult Retrieve Request | +|189 |Semantics |Semantic Mashup |TD_M2M_NH_125 |AE deletes semanticMashupResult resource via a semanticMashupResult Delete Request | +|190 |Semantics |Semantic Mashup |TD_M2M_NH_126 |AE triggers a calculation and generation of the mashup result by sending a <semanticMashupInstance>/<mashup> Retrieve Request | +|191 |Semantics |Ontology Repository |TD_M2M_NH_127 |AE creates a OntologyRepository resource in Registrar CSE via a OntologyRepository Create Request | +|192 |Semantics |Ontology Repository |TD_M2M_NH_128 |AE retrieves information of a ontologyRepository resource via a ontologyRepository Retrieve Request | +|193 |Semantics |Ontology Repository |TD_M2M_NH_129 |AE updates attribute in <ontologyRepository> resource via a ontologyRepository Update Request | +|194 |Semantics |Ontology Repository |TD_M2M_NH_130 |AE deletes OntologyRepository resource via a OntologyRepository Delete Request | +|195 |Semantics |Semantic validation |TD_M2M_NH_131 |AE checks the validity of the <semanticDescriptor> resource via a <semanticValidation> Update Request | +|196 |Semantics |Semantic validation |TD_M2M_NH_132 |AE creates a <semanticDescriptor> resource visa SemanticDescriptor Create Request and Registrar CSE checks the validity of the created <semanticDescriptor> resource | +|197 |Semantics |Ontology Mapping |TD_M2M_NH_133 |AE creates an OntologyMapping resource in Registrar CSE via an OntologyMapping Create Request | +|198 |Semantics |Ontology Mapping |TD_M2M_NH_134 |AE retrieves information of an ontology mapping result via a ontologyMapping Retrieve Request | +|199 |Semantics |Ontology Mapping |TD_M2M_NH_135 |AE updates attribute in <ontologyMapping> resource via a ontologyMapping Update Request | +|200 |Semantics |Ontology Mapping |TD_M2M_NH_136 |AE deletes OntologyMapping resource via a OntologyMapping Delete Request | +|201 |3GPP Interworking |Cellular IoT non-IP data delivery (NIDD) |TD_M2M_SH_27 |IN-CSE establishes SCEF Configuration for NIDD | +|202 |3GPP Interworking |Cellular IoT non-IP data delivery (NIDD) |TD_M2M_SH_28 |IN-AE sends a downlink non-IP data to a UE hosting ADN-AE | +|203 |3GPP Interworking |Cellular IoT non-IP data delivery (NIDD) |TD_M2M_SH_29 |IN-AE sends a downlink non-IP data to a UE hosting ADN-AE | +|204 |3GPP Interworking |Monitoring events |TD_M2M_SH_30 |IN-AE monitors UE Reachability status | +|205 |3GPP Interworking |Monitoring events |TD_M2M_SH_31 |UE Availability after DDN Failure scenario | +|206 |3GPP Interworking |Monitoring events |TD_M2M_SH_32 |UE Communication Failure scenario | +|207 |3GPP Interworking |Monitoring events |TD_M2M_SH_33 |Roaming status scenario | +|208 |3GPP Interworking |Monitoring events |TD_M2M_SH_34 |Location Reporting scenario | +|209 |3GPP Interworking |3GPP Based Device triggering |TD_M2M_SH_35 |IN-AE triggers ADN-AE hosted on UE | +|210 |3GPP Interworking |3GPP Based Device triggering |TD_M2M_SH_36 |IN-AE recalls/replaces a trigger request targeting ADN-AE hosted on UE that has been already created in IN-CSE | +|211 |3GPP Interworking |Configuration of traffic patterns |TD_M2M_SH_37 |IN-CSE translates the oneM2M Node Traffic Pattern (TP) into a 3GPP Device Communication Pattern | +|212 |3GPP Interworking |Group message delivery using MBMS |TD_M2M_SH_38 |IN-AE creates a MBMS Group for handling group related requests | +|213 |3GPP Interworking |Group message delivery using MBMS |TD_M2M_SH_39 |IN-AE sends a request for accessing member resources to the Group Hosting CSE | +|214 |Advanced Subscriptions & Notifications |Notification Target removal |TD_M2M_NH_137 |AE removes notificationTargetMgmtPolicyRef via a notificationTargetMgmtPolicyRef Delete Request | +|215 |Advanced Subscriptions & Notifications |NotificationTargetMgmtPolicyRef |TD_M2M_NH_138 |AE creates a notificationTargetMgmtPolicyRef resource in registrar CSE via a notificationTargetMgmtPolicyRef Create Request | +|216 |Advanced Subscriptions & Notifications |NotificationTargetMgmtPolicyRef |TD_M2M_NH_139 |AE retrieves notificationTargetMgmtPolicyRef resource from Registrar CSE | +|217 |Advanced Subscriptions & Notifications |NotificationTargetMgmtPolicyRef |TD_M2M_NH_140 |AE updates information about a notificationTargetMgmtPolicyRef via notificationTargetMgmtPolicyRef>Update Request | +|218 |Advanced Subscriptions & Notifications |NotificationTargetMgmtPolicyRef |TD_M2M_NH_141 |AE removes notificationTargetMgmtPolicyRef via a notificationTargetMgmtPolicyRef Delete Request | +|219 |Advanced Subscriptions & Notifications |NotificationTargetPolicy |TD_M2M_NH_142 |AE creates a notificationTargetPolicy resource in registrar CSE via a notificationTargetPolicy Create Request | +|220 |Advanced Subscriptions & Notifications |NotificationTargetPolicy |TD_M2M_NH_143 |AE retrieves notificationTargetPolicy resource from Registrar CSE | +|221 |Advanced Subscriptions & Notifications |NotificationTargetPolicy |TD_M2M_NH_144 |AE updates information about a notificationTargetPolicy via <notificationTargetPolicy> Update Request | +|222 |Advanced Subscriptions & Notifications |NotificationTargetPolicy |TD_M2M_NH_145 |AE removes notificationTargetPolicy via a <notificationTargetPolicy> Delete Request | +|223 |Advanced Subscriptions & Notifications |PolicyDeletionRules |TD_M2M_NH_146 |AE creates a policyDeletionRules resource in registrar CSE via a policyDeletionRules Create Request | +|224 |Advanced Subscriptions & Notifications |PolicyDeletionRules |TD_M2M_NH_147 |AE retrieves policyDeletionRules resource from Registrar CSE | +|225 |Advanced Subscriptions & Notifications |PolicyDeletionRules |TD_M2M_NH_148 |AE updates information about a policyDeletionRules via <policyDeletionRules> Update Request | +|226 |Advanced Subscriptions & Notifications |PolicyDeletionRules |TD_M2M_NH_149 |AE removes policyDeletionRules via a <policyDeletionRules> Delete Request | +|227 |Advanced Subscriptions & Notifications |CrossResourceSubscription |TD_M2M_NH_150 |AE creates a crossResourceSubscription resource in registrar CSE via a crossResourceSubscription Create Request | +|228 |Advanced Subscriptions & Notifications |CrossResourceSubscription |TD_M2M_NH_151 |AE retrieves crossResourceSubscription resource from Registrar CSE | +|229 |Advanced Subscriptions & Notifications |CrossResourceSubscription |TD_M2M_NH_152 |AE updates information about a crossResourceSubscription via <crossResourceSubscription> Update Request | +|230 |Advanced Subscriptions & Notifications |CrossResourceSubscription |TD_M2M_NH_153 |AE removes crossResourceSubscription via a <crossResourceSubscription> Delete Request | +|231 |Advanced Subscriptions & Notifications |CrossResourceSubscription |TD_M2M_NH_154 |AE receives a notification request from the HOST CSE | +|232 |Modbus Interworking |Modbus Thermometer device |TD_M2M_NH_163 |AE1 creates Device Model for Modbus device | +|233 |Modbus Interworking |Modbus Thermometer device |TD_M2M_NH_164 |Modbus IPE reads data from Modbus device and updates Registrar CSE with the read data | +|234 |Modbus Interworking |Modbus Thermometer device |TD_M2M_NH_165 |AE writes data into a Modbus device by updating <flexContainer> resource in Registrar CSE | +|235 |NoDN Interworking |Generic IPE |TD_M2M_NH_166 |NoDN IPE reads data from a NoDN device and updates Registrar CSE with the read data | +|236 |NoDN Interworking |Generic IPE |TD_M2M_NH_167 |AE writes data into a NoDN device by updating <flexContainer> resource in Registrar CSE | + + + + +# 7 Configuration + +## 7.1 Test Configuration + +### 7.1.1 No hop + +#### 7.1.1.1 M2M_CFG_01 +The AE manages resources on the registrar CSE (Hosting CSE). + +oneM2M entities model + + + + +**Figure 7.1.1.1-1** + + +#### 7.1.1.2 M2M_CFG_02 + +oneM2M entities model + + + + +**Figure 7.1.1.2-1** + + +#### 7.1.1.3 M2M_CFG_10 + +oneM2M entities model + + + + +**Figure 7.1.1.3-1** + +> NOTE: For HAIM Model tests, clause 8.5, AE1 represents a native oneM2M device that implements the HAIM models or a combined IPE(AE) plus a non-oneM2M device node (nodn). + +### 7.1.2 Single hop + +#### 7.1.2.1 M2M_CFG_03 + +The AE manages resources on the remote CSE. + +oneM2M entities model + + + + +**Figure 7.1.2.1-1** + + +#### 7.1.2.2 M2M_CFG_04 + +oneM2M entities model + + + + +**Figure 7.1.2.2-1** + + +#### 7.1.2.3 M2M_CFG_05 + +oneM2M entities model + + + + +**Figure 7.1.2.3-1** + + +#### 7.1.2.4 M2M_CFG_08 + +This configuration concerns group management when the AE is using a group to fan out requests to multiple members. The connection between the AE and the Group Hosting CSE, the Group Hosting CSE and the Member Hosting CSE may be a multi hop connection following the definition in clause 7.1.3. + +This configuration is mapped to cases including: + + +- AE sends a request addressing <group>/fanOutPoint in the Group Hosting CSE, the Group Hosting CSE then further fans out the request to each Member Hosting CSE. +- The Member Hosting CSE sends a notification to the Group Hosting CSE pertaining to the subscription made through the Group Hosting CSE. The Group Hosting CSE then further aggregates the notification and sends it back to the AE. + + + +**Figure 7.1.2.4-1** + + +#### 7.1.2.5 M2M_CFG_09 + +This configuration concerns device management using external technologies. + +This configuration is mapped to cases including: + + +- The AE sends a request addressing <mgmtObj> to IN-CSE. IN-CSE then further acts as a Management Server to send management commands to Managed Entity over the mc interface. The management command is defined in OMA DM, BBF TR069 or LWM2M. + + + +**Figure 7.1.2.5-1** + + +#### 7.1.2.6 M2M_CFG_11 + +This configuration concerns device management using 3GPP network. + + + + + +#### 7.1.2.7 M2M_CFG_12 +This configuration concerns group management when the IN-AE is using a group to fan out requests to multiple members in 3GPP interworking scenraios. The connection between the IN-AE and the Group Hosting CSE, the Group Hosting CSE and the Member Hosting CSE may be a multi hop connection following the definition in clause 7.1.3. + +This configuration is mapped to cases including: + + +- IN-AE sends a request addressing <group>/fanOutPoint in the Group Hosting CSE, the Group Hosting CSE then further fans out the request to each Member Hosting CSE through 3GPP network. + + + + +### 7.1.3 Multi hops + +#### 7.1.3.1 M2M_CFG_06 + +oneM2M entities model + + + + +**Figure 7.1.3.1-1** + + +#### 7.1.3.2 M2M_CFG_07 + +oneM2M entities model + + + + +**Figure 7.1.3.2-1** + + +# 8 Test Descriptions + +## 8.1 No Hop configuration testing + +### 8.1.1 CSEBase Management + +#### 8.1.1.1 CSEBase Retrieve on Mca + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_01 | +|Objective: |Objective: |Objective: |AE retrieves the CSEBase resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.2.11<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been automatically created in CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a retrieve Request to CSE with name {CSEBaseName} | +|2 |Mca |PRO Check Primitive |Operation (op) = 2 (Retrieve)<br />To (to) = Resource-ID of requested <CSEBase> resource, assumed CSE-relative here <br />From (from) = AE-ID of request originator<br />Request Identifier (rqi) = (token-string) | +|3 |Mca |PRO Check Primitive |Response Status Code (rsc) = 2000 (OK)<br />Request Identifier (rqi) = same string as received in request message<br />Content (pc) = Serialized Representation of <CSEBase> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + + +### 8.1.2 RemoteCSE Management + +#### 8.1.2.1 RemoteCSE Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_02 | +|Objective: |Objective: |Objective: |Registree CSE registers to Registrar CSE | +|Configuration: |Configuration: |Configuration: |M2M_CFG_02 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2.1<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |Registree CSE is requested to send a RemoteCSE Create request to Registrar CSE | +|2 |<br />Mcc |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = Registree CSE-ID<br />rqi = (token-string)<br />ty = 16 (RemoteCSE)<br />pc = Serialized representation of <RemoteCSE> resource | +|3 |<br />Mcc |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <RemoteCSE> resource | +|4 | |IOP Check |Check if possible that the <remoteCSE> resource has been created in registrar CSE | +|5 | |IOP Check |Check if possible that the corresponding <remoteCSE> resource has been also created in registree CSE | +|6 | |IOP Check |Registree CSE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.2.2 remoteCSE Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_03 | +|Objective: |Objective: |Objective: |Registree CSE retrieves RemoteCSE from Registrar CSE | +|Configuration: |Configuration: |Configuration: |M2M_CFG_02 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |Registree CSE is requested to send a RemoteCSE retrieve request to Registrar CSE | +|2 |<br />Mcc |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/{remoteCSEName}<br />fr = Registree CSE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mcc |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <RemoteCSE> resource | +|4 | |IOP Check |Registree CSE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.2.3 remoteCSE Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_04 | +|Objective: |Objective: |Objective: |Registree CSE updates RemoteCSE from Registrar CSE | +|Configuration: |Configuration: |Configuration: |M2M_CFG_02 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |Registree CSE is requested to send a RemoteCSE update request to Registrar CSE | +|2 |<br />Mcc |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{remoteCSEName}<br />fr = Registree CSE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <RemoteCSE> resource | +|3 | |IOP Check |Check if possible that the <remoteCSE> resource has been updated in registrar CSE | +|4 |<br />Mcc |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2004 (UPDATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <RemoteCSE> resource | +|5 | |IOP Check |Registree CSE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.2.4 remoteCSE Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_05 | +|Objective: |Objective: |Objective: |Registree CSE deletes RemoteCSE from Registrar CSE | +|Configuration: |Configuration: |Configuration: |M2M_CFG_02 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |Registree CSE is requested to send a RemoteCSE delete request to Registrar CSE | +|2 |<br />Mcc |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{remoteCSEName}<br />fr = Registree CSE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mcc |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|4 | |IOP Check |Check if possible that the <remoteCSE> resource has been removed from registrar CSE | +|5 | |IOP Check |Check if possible that the <remoteCSE> resource is also removed from registree CSE | +|6 | |IOP Check |Registree CSE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.3 Application Entity Registration + +#### 8.1.3.1 AE Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_06 | +|Objective: |Objective: |Objective: |AE registers to its registrar CSE via an AE Create Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.2.2 <br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.5.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in CSE with name {CSEBaseName}<br />AE does not have an AE-ID, i.e. it registers from scratch | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a AE Create request to register to the Registrar CSE | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 2 (AE)<br />pc = Serialized representation of <AE> resource | +|3 | |IOP Check |Check if possible that the <AE> resource is created in registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <AE> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.3.2 AE Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_07 | +|Objective: |Objective: |Objective: |AE retrieves <AE> resource via an AE Retrieve Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.2.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.5.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}bgf | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a AE retrieve request to Registrar CSE | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/{AE}<br />fr = AE-ID of request originator<br />rqi = (token-string) | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <AE> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.3.3 AE Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_08 | +|Objective: |Objective: |Objective: |AE updates attribute in <AE> resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.2.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.5.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: | CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send an AE Update Request | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{AE}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <AE> resource | +|3 | |IOP Check |Check if possible that the <AE> resource has been updated in registrar CSE | +|4 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2004 (UPDATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <AE> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.3.4 AE Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_09 | +|Objective: |Objective: |Objective: |AE de-registers by deleting <AE> resource via an AE Delete Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.2.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.5.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send an AE Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{AE}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|4 | |IOP Check |Check if possible that the <AE> resource has been removed from registrar CSE | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.4 Container Management + +#### 8.1.4.1 Container Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_10 | +|Objective: |Objective: |Objective: |AE creates a container resource in registrar CSE via a container Create Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.6.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE sends a request to create a <container> | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of <AE> resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 3 (Container)<br />pc = Serialized representation of <container> resource | +|3 | |IOP Check |Check if possible that the <container> resource is created in registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.4.2 Container Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_11 | +|Objective: |Objective: |Objective: |AE retrieves information of a container resource via a container Retrieve Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.6.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request for a <container> | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <container> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.4.3 Container Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_12 | +|Objective: |Objective: |Objective: |AE updates attribute in application resource via a container Update Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.6.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a container Update Request to update the lifetime of the resource | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/URI of <container> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <container> resource | +|3 | |IOP Check |Check if possible that the < container > resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.4.4 Container Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_13 | +|Objective: |Objective: |Objective: |AE deletes a specific container resource via a container Delete Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.6.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a container Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <container> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Check if possible that the <container> resource is deleted in registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |Check if possible that the <container> resource has been removed in registrar CSE | +|6 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.5 ContentInstance Management + +#### 8.1.5.1 ContentInstance Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_14 | +|Objective: |Objective: |Objective: |AE adds a contentInstance resource <contentInstance> to a specific container in Registrar CSE via a contentInstance Create Request and the Registrar CSE updates the parent <container> resource with stateTag, currentNrOfInstances, and CurrentByteSize attributes correspondingly | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.7<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.7.1.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on registrar CSE<br />AE has created a container resource <container> on registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the <container> resource and AE sends a request to create a < contentInstance > resource | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of < container > resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 4 (contentInstance)<br />pc = Serialized representation of <contentInstance> resource | +|3 | |IOP Check |Check if possible that the <contentInstance> resource is created in Registrar CSE and AE sends a RETRIEVE request to the <container> resource to check that if the Registrar CSE has updated stateTag, currentNrOfInstances, and CurrentByteSize attribute correspondingly which is resulted from the successful creation of child <contentInstance> resource | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <contentInstance> resource | +|5 | |IOP Check |AE indicates successful CREATE operation of <contentInstance> and indicates Registrar CSE has updated stateTag, currentNrOfInstances, and CurrentByteSize attribute correspondingly by checking the response of a <container> request to the <container> resource | +|IOP Verdict |IOP Verdict |Set verdict to pass if IOP check goal is achieved exactly, otherwise verdict fail is set with corresponding error message |Set verdict to pass if IOP check goal is achieved exactly, otherwise verdict fail is set with corresponding error message | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.5.2 ContentInstance Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_15 | +|Objective: |Objective: |Objective: |AE retrieves information of a contentInstance resource via a contentInstance Retrieve Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.8<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.7.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a contentInstance resource <contentInstance> as child resource of <container> resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request for a <contentInstance> | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <contentInstance> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <contentInstance> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.5.3 ContentInstance Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_17 | +|Objective: |Objective: |Objective: |AE deletes contentInstance resource via a contentInstance Delete Request and the Registrar CSE updates the parent <container> resource with currentNrOfInstances, and CurrentByteSize attributes correspondingly | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.7.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a contentInstance resource <contentInstance> as child resource of <container> resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the <container> resource and AE is requested to send a contentInstance Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <contentInstance> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Check if possible that the <contentInstance> resource is deleted in Registrar CSE and AE sends a RETRIEVE request to the parent <container> resource to check that if the Registrar CSE has updated currentNrOfInstances, and CurrentByteSize attribute correspondingly which is resulted from the successful deletion of child <contentInstance> resource | +|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |Check if possible that the <contentInstance> resource has been removed in registrar CSE. | +|6 | |IOP Check |AE indicates successful DELETE operation of <contentInstance> and indicates Registrar CSE has updated currentNrOfInstances, and CurrentByteSize attribute correspondingly | +|IOP Verdict |IOP Verdict |Set the verdict to pass if both the <contentInstance> is deleted and the Registrar CSE updated currentNrOfInstances, and CurrentByteSize attribute. Otherwise, set the verdict to fail with corresponding error message |Set the verdict to pass if both the <contentInstance> is deleted and the Registrar CSE updated currentNrOfInstances, and CurrentByteSize attribute. Otherwise, set the verdict to fail with corresponding error message | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.5.4 <latest> ContentInstance Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_49 | +|Objective: |Objective: |Objective: |AE deletes a <latest> resource of a <container> and the Registrar CSE points a latest <contentInstance> among the existing contentInstances to the <latest> resource of the <container> | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.12<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.27.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created more than one contentInstances <contentInstance> as child of <container> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE retrieves a <latest> resource in a <container> and then sends a DELETE request to the <latest> resource of the <container> | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <latest> resource of a <container><br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = representation of deleted <latest> resource of a <container> | +|4 | |IOP Check |AE indicates successful DELETE operation of a <latest> resource and AE sends a RETRIEVE request to <latest> resource of a <container> to check if the retrieved <latest> resource in the <container> is different with that one that was retrieved before DELETE request of the <latest> resource in terms of resourceID and resourceName attribute value | +|IOP Verdict |IOP Verdict |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.5.5 <oldest> ContentInstance Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_50 | +|Objective: |Objective: |Objective: |AE deletes a <oldest> resource of a <container> and the Registrar CSE points an oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.14<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.28.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created more than one contentInstances <contentInstance> as child of <container> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE retrieves a <oldest> resource of a <container> and AE sends a DELETE Request to the <oldest> resource of the <container> | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <oldest> resource of a <container><br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = representation of deleted <oldest> resource of a <container> | +|3 |<br />Mca | | | +|3 |<br />Mca | | | +|3 |<br />Mca | | | +|4 | |IOP Check |AE indicates successful DELETE operation of a <oldest> resource and AE sends a RETRIEVE request to <oldest> resource of a <container> to check if the retrieved <oldest> resource in the <container> is different with that one that was retrieved before DELETE request of the <oldest> resource in terms of resourceID and resourceName attribute values | +|IOP Verdict |IOP Verdict |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.5.6 ContentInstance Create when currentNrOfInstance equals to maxNrOfInstances in parent <container> resource + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_51 | +|Objective: |Objective: |Objective: |AE sends a <contentInstance> CREATE request to a <container> which contains attribute currentNrOfInstances whose value equals to that of maxNrOfInstances and Registrar CSE deletes the oldest <contentInstance> from the parent <container> and then creates the requested <contentInstance> resource for the originator AE | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.7<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.6.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on registrar CSE<br />AE has created a container resource <container> (where the number of contentInstances equals to the value set in maxNrOfInstance) on registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the <oldest> contentInstance resource and <br />AE sends a request to create a <contentInstance> resource | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of <container> resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 4 (contentInstance)<br />pc = Serialized representation of <contentInstance> resource | +|3 | |IOP Check |Check if possible that the <oldest> resource of a <container> is deleted | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <contentInstance> resource | +|5 | |IOP Check |AE indicates successful CREATE operation of <contentInstance> and indicates the representation of the recent <oldest> resource in the <container> is different with that of <oldest> resource retrieved at the beginning of test in terms of resourceID and resourceName attribute value | +|IOP Verdict |IOP Verdict |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.5.7 <latest> ContentInstance Retrieve + +##### 8.1.5.7.1 Attribute locationID of the <container> resource configured + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_102 | +|Objective: |Objective: |Objective: |AE retrieves a <latest> resource of a <container> for which attribute locationID is configured, value of locationUpdatePeriod is marked '0' or not defined and locationSource attribute is 'Network Based' | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.11<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.27.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a <locationPolicy> resource on Registrar CSE having its resourceID and locationContainerID attribute set to locationID and resourceID attribute of the <container> resource respectively<br />In resource <locationPolicy>, value of locationUpdatePeriod is marked '0' or not defined and locationSource attribute is 'Network Based' | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request for a <latest> | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <container> resource/la<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of latest <contentInstance> resource, created after acquiring location info from Location Server, in response to Location Request made by the CSE, using the attributes stored in the <locationPolicy> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +##### 8.1.5.7.2 Attribute locationID of the <container> resource not configured + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_71 | +|Objective: |Objective: |Objective: |AE retrieves a <latest> resource of a <container> and the Registrar CSE points a latest <contentInstance> among the existing contentInstances to the <latest> resource of the <container> | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.11<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.27.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created multiple contentInstance resources <contentInstance> as child resource of <container> resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request for a <latest> | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <container> resource/la<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of latest <contentInstance> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.5.8 <oldest> ContentInstance Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Identifier: | +|-|-|-|-|-|-| +|Identifier: |Identifier: |TD_M2M_NH_72 |TD_M2M_NH_72 |Objective: |Objective: | +|Objective: |AE retrieves a <oldest> resource of a <container> and the Registrar CSE points a oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> |AE retrieves a <oldest> resource of a <container> and the Registrar CSE points a oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> |Configuration: |Configuration: |Configuration: | +|M2M_CFG_01 |M2M_CFG_01 |References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.13<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.28.2.2 | +|oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.13<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.28.2.2 | | | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created multiple contentInstance resources <contentInstance> as child resource of <container> resource |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created multiple contentInstance resources <contentInstance> as child resource of <container> resource |Test Sequence | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence |Step |RP | +|Type |Description |Description |1 | |Stimulus | +|AE is requested to send a Retrieve Request for a <oldest> |AE is requested to send a Retrieve Request for a <oldest> |2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <container> resource/ol<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <container> resource/ol<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty |3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of oldest <contentInstance> resource |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of oldest <contentInstance> resource | +|4 | |IOP Check |AE indicates successful operation |AE indicates successful operation | +|| +|| + + + + +### 8.1.6 Discovery + +#### 8.1.6.1 Discovery of all resources + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_18 | +|Objective: |Objective: |Objective: |AE discovers all accessible resources from registrar CSE | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a discovery request to registrar CSE | +|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />fu=1<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing addresses of all discovered resources | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.6.2 Discovery with label filter criteria + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_19 | +|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using the label filter criteria | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />A <Container> resource with label "key1" is created on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Discovery request in order to discover the <Container> resource using the label filter criteria | +|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />fu=1<br />lbl=key1<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the address of the <Container> address | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.6.3 Discovery with limit filter criteria + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_20 | +|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE limiting the number of matching resources to the specified value | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Discovery request in order to discover at most 2 resources in registrar CSE | +|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />fu = 1<br />lim = 2<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />cnst = 1<br />cno t= 2<br />pc = Serialized representation of data object containing the address of the <Container> address | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.6.4 Discovery with multiple filter criteria + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_21 | +|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using multiple Filter Criteria | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |Two <Container> resources with labels "key1" and "key2" are created in Registrar CSE<br />A <Group> resources with labels "key1" and "key2" is created in Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Discovery request in order to discover specific resources located in Registrar CSE using multiple filter criteria (label, resource type and limit) | +|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />fu=1<br />lbl=key1<br />lbl=key2<br />ty=3<br />lim=1<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the address of one of the <Container> resources | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.6.5 Discovery with level filter criteria + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_58 | +|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 1 | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |<AE1> and <AE2> resources are created in Registrar CSE<br />A <Container> resource is created under both <AE> resources in Registrar CSE<br />A <ContentInstance> resource is created under both <Container> resources in Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Discovery request in order to discover specific resources located in Registrar CSE using level filter criteria value set to 1 | +|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu=1<br />lvl=1<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the address of both <AE> resources | +|4 | |IOP Check |AE1 indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_59 | +|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 2 | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |<AE1> and <AE2> resources are created in Registrar CSE. A <Container> resource is created under both <AE> resources in Registrar CSE<br />A <ContentInstance> resource is created under both <Container> resources in Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Discovery request in order to discover specific resources located in Registrar CSE using level filter criteria value set to 2 | +|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu = 1<br />lvl = 2<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the address of all <AE> and <Container> resources | +|4 | |IOP Check |AE1 indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_60 | +|Objective: |Objective: |Objective: |AE1 discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 3 | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |<AE1> and <AE2> resources are created in Registrar CSE<br />A <Container> resource is created under both <AE> resources in Registrar CSE<br />A <ContentInstance> resource is created under both <Container> resources in Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE1 is requested to send a Discovery request in order to discover specific resources located in Registrar CSE using level filter criteria value set to 3 | +|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu=1<br />lvl=3<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the address of all <AE>, <Container> and <ContentInstance>resources | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.6.6 Discovery with offset filter criteria + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_61 | +|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using the offset filter criteria value set to 3 | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |<AE1> and <AE2> resources are created in Registrar CSE. A <Container> resource is created under both <AE> resources in Registrar CSE<br />A <ContentInstance> resource is created under both <Container> resources in Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE1 is requested to send a Discovery request in order to discover specific resources located in Registrar CSE using offset filter criteria value set to 3 | +|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu=1<br />ofst=3<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing only 3 of the 6 <AE>, <container> and <contentInstance> resources hosted by the Registrar CSE | +|4 | |IOP Check |AE1 indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_62 | +|Objective: |Objective: |Objective: |AE discovers all the accessible resources residing in Registrar CSE using the offset filter criteria | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |<AE1> and <AE2> resources are created in Registrar CSE<br />A <Container> resource is created under both <AE> resources in Registrar CSE<br />A <ContentInstance> resource is created under both <Container> resources in Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE1 is requested to send a Discovery request in order to discover specific resources located in Registrar CSE using offset filter criteria attribute value set to 0 (Default value) and limit filter Criteria attribute value set to 2 | +|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu = 1<br />lim = 2<br />pc = empty | +|3 | |IOP Check |Registrar CSE sends success response to AE1 | +|4 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />cnst = 1<br />cnot = 2<br />pc = Serialized representation of data object containing the address of first 2 resources hosted by Registrar CSE | +|5 | |IOP Check |AE1 sends discovery request to Registrar CSE with offset filtercriteria value set to 2 and limit filter criteria attribute value set to 2 | +|6 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu=1<br />ofst = 2<br />lim = 2<br />pc = empty | +|7 | |IOP Check |Registrar CSE sends success response to AE1 | +|8 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />cnst=1<br />cnot=4<br />pc = Serialized representation of data object containing the address of next 2 resources hosted by Registrar CSE | +|9 | |IOP Check |AE1 sends discovery request to Registrar CSE with offset filtercriteria value set to 4 and limit filtercriteria attribute value set to 2 | +|10 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu = 1<br />ofst = 4<br />lim = 2<br />pc = empty | +|11 | |IOP Check |Registrar CSE sends success response to AE1 | +|12 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />cnst = 2<br />pc = Serialized representation of data object containing the address of last 2 resources hosted by Registrar CSE | +|13 | |IOP Check |AE1 indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.7 Subscription Management + +#### 8.1.7.1 Subscription Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_22 | +|Objective: |Objective: |Objective: |AE creates a subscription to Application Entity resource via subscription Create Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.8.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on registrar CSE<br />AE has created a container resource <container> on registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a subscription Create request to the Registrar CSE | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of <Container> resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 23 (Subscription)<br />pc = Serialized representation of <Subscription> resource | +|3 | |IOP Check |Check if possible that the <Subscription> resource is created in registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <Subscription> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.7.2 Subscription Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_23 | +|Objective: |Objective: |Objective: |AE retrieves subscription resource from Registrar CSE | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.8.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a subscription resource <subscription> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request for a <subscription> | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <Subscription> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <Subscription> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.7.3 Subscription Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_24 | +|Objective: |Objective: |Objective: |AE updates information about a subscription via subscription Update Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.8.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a subscription resource <subscription> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a subscription Update Request to update the lifetime of the resource. | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/URI of <Subscription> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <Subscription> resource | +|3 | |IOP Check |Check if possible that the <subscription> resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <Subscription> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.7.4 Subscription Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_25 | +|Objective: |Objective: |Objective: |AE cancels subscription via an subscription Delete Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.8.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a subscription resource <subscription> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a subscription Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <Subscription> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Check if possible that the <Subscription> resource is deleted in registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |Check if possible that the <subscription> resource has been removed in registrar CSE | +|6 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.8 accessControlPolicy Management + +#### 8.1.8.1 accessControlPolicy Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_26 | +|Objective: |Objective: |Objective: |AE creates an accessControlPolicy resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.3.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.2.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send an accessControlPolicy Create Request | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/{AE}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 1 (accessControlPolicy)<br />pc = Serialized representation of <accessControlPolicy > resource | +|3 | |IOP Check |Check if possible that the <container> resource is created in registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <accessControlPolicy> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.8.2 accessControlPolicy Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_27 | +|Objective: |Objective: |Objective: |AE retrieves accessControlPolicy resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.3.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.2.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a accessControlPolicy retrieve request to Registrar CSE | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/{AE}/{accessControlPolicyName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <accessControlPolicy> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.8.3 accessControlPolicy Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Identifier: | +|-|-|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_28 |Objective: |Objective: | +|Objective: |Objective: |AE updates attribute in accessControlPolicy resource |Configuration: |Configuration: |Configuration: | +|Configuration: |M2M_CFG_01 |References: |References: |References: |References: | +|oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.3.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.2.2.3 | | | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName} |Test Sequence | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence |Step |Step | +|RP |Type |Description |1 |1 | | +|Stimulus |AE is requested to send an accessControlPolicy update request to Registrar CSE |2 |2 |<br />Mca |PRO Check Primitive | +|op = 3 (Update)<br />to = {CSEBaseName}/{AE}/{accessControlPolicyName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <accessControlPolicy > resource |3 |3 | |IOP Check |Check if possible that the <accessControlPolicy> resource has been updated in registrar CSE | +|4 |4 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2004 (UPDATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <accessControlPolicy> resource |5 | +|5 | |IOP Check |AE indicates successful operation |IOP Verdict |IOP Verdict | +|IOP Verdict | | |PRO Verdict |PRO Verdict |PRO Verdict | | | | -|-|-|-| -|XML payload example for MQTT binding |<?xml version="1.0" encoding="UTF-8"?><br /> <m2m:req xmlns:m2m="http://www.onem2m.org/xml/protocols" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.onem2m.org/xml/protocols CDT-requestPrimitive-v1_0_0.xsd"><br /> <op>1</op><br /> <to>CSE1Base</to><br /> <fr>/CSE1/C_AE1</fr><br /> <rqi>2001</rqi><br /> <ty>3</ty><br /> <nm>cont1</nm><br /> <rti><rt>3</rt></rti><br /> <pc><br /> <cnt><br /> <lbl>SmartMeter</lbl><br /> <et>20141003T112033</et><br /> </cnt><br - /> </pc><br /></m2m:req> | -|-|-| -|Abstracted payload example for MQTT binding |op = 1<br />to = CSE1Base<br />fr = /CSE1/C_AE01<br />rqi = 3001<br />ty = 3<br />name = cont1<br />rti.rt = 3<br />pc.cnt.lbl = SmartMeter<br />pc.cnt.et = 20141003T112033 | -|Abstracted payload example for MQTT binding adopting the payload convention |op = 1<br />to = <CSEBase><br />fr = <From><br />rqi = <Request ID><br />ty = 3<br />name = <Name><br />rti.rt = 3<br />pc = <Content> | - - - - -# 6 Test Description Summary - -## 6.1 Tests list - -|Nb |Category |Procedure/Resource |TD ID |TD Description | -|-|-|-|-|-| -|1 |Resource management<br /><br />Single Hop |CSEBase Management |TD_M2M_NH_01 |AE retrieves the CSEBase resource | -|2 |Resource management<br /><br />Single Hop |RemoteCSE |TD_M2M_NH_02 |Registree CSE registers to Registrar CSE | -|3 |Resource management<br /><br />Single Hop |RemoteCSE |TD_M2M_NH_03 |Registree CSE retrieves RemoteCSE from Registrar CSE | -|4 |Resource management<br /><br />Single Hop |RemoteCSE |TD_M2M_NH_04 |Registree CSE updates RemoteCSE from Registrar CSE | -|5 |Resource management<br /><br />Single Hop |RemoteCSE |TD_M2M_NH_05 |Registree CSE deletes RemoteCSE from Registrar CSE | -|6 |Resource management<br /><br />Single Hop |Application Entity |TD_M2M_NH_06 |AE registers to its registrar CSE via an AE Create Request | -|7 |Resource management<br /><br />Single Hop |Application Entity |TD_M2M_NH_07 |AE retrieves <AE> resource via an AE Retrieve Request | -|8 |Resource management<br /><br />Single Hop |Application Entity |TD_M2M_NH_08 |AE updates attribute in <AE> resource via an AE Update Request | -|9 |Resource management<br /><br />Single Hop |Application Entity |TD_M2M_NH_09 |AE de-registers by deleting <AE> resource via an AE Delete Request | -|10 |Resource management<br /><br />Single Hop |Container |TD_M2M_NH_10 |AE creates a container resource in registrar CSE via a container Create Request | -|11 |Resource management<br /><br />Single Hop |Container |TD_M2M_NH_11 |AE retrieves information of a container resource via a container Retrieve Request | -|12 |Resource management<br /><br />Single Hop |Container |TD_M2M_NH_12 |AE updates attribute in application resource via a container Update Request | -|13 |Resource management<br /><br />Single Hop |Container |TD_M2M_NH_13 |AE deletes a specific container resource via a container Delete Request | -|14 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_14 |AE adds a contentInstance resource <contentInstance> to a specific container in Registrar CSE via a contentInstance Create Request and the registrar CSE updates the parent <container> resource with stateTag, and currentNrOfInstances, CurrentByteSize attributes correspondingly | -|15 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_15 |AE retrieves information of a contentInstance resource via a contentInstance Retrieve Request | -|16 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_17 |AE deletes contentInstance resource via a Delete Request and the registrar CSE updates the parent <container> resource with currentNrOfInstances, and CurrentByteSize attribute correspondingly | -|17 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_49 |AE deletes a <latest> resource in a <container> and the Registrar CSE points a latest <contentInstance> among the existing contentInstances to the <latest> resource of the <container> | -|18 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_50 |AE deletes a <oldest> resource in a <container> resource and the Registrar CSE points an oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> | -|19 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_51 |AE sends a <contentInstance> CREATE request to a <container> which contains attribute currentNrOfInstances whose value equals to that of maxNrOfInstances and Registrar CSE deletes the oldest <contentInstance> from the parent <container> and then creates the requested <contentInstance> resource | -|20 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_102 |AE retrieves a <latest> resource of a <container> for which attribute locationID is configured, value of locationUpdatePeriod is marked '0' or not defined and locationSource attribute is 'Network Based' | -|21 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_71 |AE retrieves a <latest> resource of a <container> and the Registrar CSE points a latest <contentInstance> among the existing contentInstances to the <latest> resource of the <container> | -|22 |Resource management<br /><br />Single Hop |ContentInstance |TD_M2M_NH_72 |AE retrieves a <oldest> resource of a <container> and the Registrar CSE points a oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> | -|23 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_18 |AE discovers resources residing in Registrar CSE | -|24 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_19 |AE discovers accessible resources residing in Registrar CSE using the label filter criteria | -|25 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_20 |AE discovers accessible resources residing in Registrar CSE limiting the number of matching resources to the specified value | -|26 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_21 |AE discovers accessible resources residing in Registrar CSE using multiple Filter Criteria | -|27 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_58 |AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 1 | -|28 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_59 |AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 2 | -|29 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_60 |AE1 discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 3 | -|30 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_61 |AE discovers accessible resources residing in Registrar CSE using the offset filter criteria value set to 3 | -|31 |Resource management<br /><br />Single Hop |Discovery |TD_M2M_NH_62 |AE discovers all the accessible resources residing in Registrar CSE using the offset filter criteria | -|32 |Resource management<br /><br />Single Hop |Subscription |TD_M2M_NH_22 |AE creates a subscription to Application Entity resource via subscription Create Request | -|33 |Resource management<br /><br />Single Hop |Subscription |TD_M2M_NH_23 |AE retrieves information about a subscription via subscription Retrieve Request such as expirationTime, labels, etc. | -|34 |Resource management<br /><br />Single Hop |Subscription |TD_M2M_NH_24 |AE updates information about a subscription via subscription Retrieve Request | -|35 |Resource management<br /><br />Single Hop |Subscription |TD_M2M_NH_25 |AE cancels subscription via an subscription Delete Request | -|36 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_26 |AE creates an accessControlPolicy resource | -|37 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_27 |AE retrieves accessControlPolicy resource | -|38 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_28 |AE updates attribute in accessControlPolicy resource | -|39 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_29 |AE deletes accessControlPolicy resource | -|40 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_30 |AE delete request is rejected due to accessControlPolicy | -|41 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_73 |AE delete request is rejected due to accessControlPolicy (accessControlOriginators) | -|42 |Resource management<br /><br />Single Hop |AccessControlPolicy |TD_M2M_NH_74 |AE delete request is allowed due to accessControlPolicy | -|43 |Resource management<br /><br />Single Hop |Group |TD_M2M_NH_31 |AE creates a group resource | -|44 |Resource management<br /><br />Single Hop |Group |TD_M2M_NH_32 |AE retrieves group resource | -|45 |Resource management<br /><br />Single Hop |Group |TD_M2M_NH_33 |AE updates attribute in group resource | -|46 |Resource management<br /><br />Single Hop |Group |TD_M2M_NH_34 |AE deletes group resource | -|47 |Resource management<br /><br />Single Hop |Node |TD_M2M_NH_35 |AE creates a node resource | -|48 |Resource management<br /><br />Single Hop |Node |TD_M2M_NH_36 |AE retrieves node resource | -|49 |Resource management<br /><br />Single Hop |Node |TD_M2M_NH_37 |AE updates attribute in node resource | -|50 |Resource management<br /><br />Single Hop |Node |TD_M2M_NH_38 |AE deletes node resource | -|51 |Resource management<br /><br />Single Hop |PollingChannel |TD_M2M_NH_39 |AE creates a <pollingChannel> resource in registrar CSE via a Create Request | -|52 |Resource management<br /><br />Single Hop |PollingChannel |TD_M2M_NH_40 |AE retrieves information of a pollingChannel resource via a Retrieve Request | -|53 |Resource management<br /><br />Single Hop |PollingChannel |TD_M2M_NH_41 |AE updates attribute in pollingChannel resource via a Update Request | -|54 |Resource management<br /><br />Single Hop |PollingChannel |TD_M2M_NH_42 |AE deletes a pollingChannel resource via a Delete Request | -|55 |Resource management<br /><br />Single Hop |PollingChannel |TD_M2M_NH_43 |AE retrieves information of a pollingChannel resource via a Retrieve Request | -|56 |Resource management<br /><br />Single Hop |FanoutPoint |TD_M2M_NH_44 |AE creates a - <contentInstance> resource in each group member | -|57 |Resource management<br /><br />Single Hop |FanoutPoint |TD_M2M_NH_45 |AE retrieves the <container> resource from in each group member | -|58 |Resource management<br /><br />Single Hop |FanoutPoint |TD_M2M_NH_46 |AE updates an <container> resource of each member resource | -|59 |Resource management<br /><br />Single Hop |FanoutPoint |TD_M2M_NH_47 |AE deletes a <container> of each member | -|60 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_48 |AE receives a notification request from the HOST CSE | -|61 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_80 |AE2 sends maxNrOfInstances UPDATE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has specific setting in eventNotificationCriteria, Hosting CSE send notification to AE1 | -|62 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_81 |AE2 sends DELETE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has notificationEventType with 'Delete of Resource', Hosting CSE send notification to AE1 | -|63 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_82 |AE2 sends <contentInstance> CREATE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has notificationEventType with ''Create of Direct Child 'Resource', Hosting CSE send notification to AE1 | -|64 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_83 |AE2 sends DELETE request to the <contentInstance> which located under the subscribed-to resource. Since <subscription> resource has notificationEventType with 'Delete of Direct Child Resource', Hosting CSE send notification to AE1 | -|65 |Resource management<br /><br />Single Hop |Notification |TD_M2M_NH_89 |AE creates <subscription> resources by sending Create Request to the fanOutPoint. <br />Since AE has set notifyAggregation to 2, Hosting CSE aggregate notification and send aggregated notification to AE | -|66 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_52 |AE creates a flexcontainer resource in Registrar CSE via a flexcontainer Create Request | -|67 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_53 |AE retrieves information of a flexContainer resource via a flexContainer Retrieve Request | -|68 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_54 |AE updates attribute in application resource via a flexContainer Update Request | -|69 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_55 |AE deletes a specific container resource via a container Delete Request | -|70 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_56 |AE receives a notification request on flexContainer update from the HOST CSE | -|71 |Resource management<br /><br />Single Hop |FlexContainer |TD_M2M_NH_57 |AE discovers accessible resources residing in Registrar CSE using attribute filter criteria which has a customAttribute name and value assigned to it | -|72 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_63 |AE creates a mgmtCmd resource | -|73 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_64 |AE retrieves mgmtCmd resource | -|74 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_65 |AE updates attribute (not with 'true' in execEnable attribute) in mgmtCmd resource | -|75 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_66 |AE updates attribute (with 'true' in execEnable attribute) in mgmtCmd resource | -|76 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_67 |AE deletes mgmtCmd resource | -|77 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_68 |AE retrieves execInstance resource | -|78 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_69 |AE updates attribute 'execDisable' to true in execInstance resource to cancel pending management command | -|79 |Resource management<br /><br />Single Hop |External Management Operations |TD_M2M_NH_70 |AE deletes execInstance resource | -|80 |Resource management<br /><br />Single Hop |SemanticDescriptor Management |TD_M2M_NH_75 |AE creates a SemanticDescriptor resource in Registrar CSE via a SemanticDescriptor Create Request | -|81 |Resource management<br /><br />Single Hop |SemanticDescriptor Management |TD_M2M_NH_76 |AE retrieves information of a semanticDescriptor resource via a semanticDescriptor Retrieve Request | -|82 |Resource management<br /><br />Single Hop |SemanticDescriptor Management |TD_M2M_NH_77 |AE updates attribute in <semanticDescriptor> resource via a semanticDescriptor Update Request | -|83 |Resource management<br /><br />Single Hop |SemanticDescriptor Management |TD_M2M_NH_78 |AE deletes SemanticDescriptor resource via a SemanticDescriptor Delete Request | -|84 |Resource management<br /><br />Single Hop |Semantic Resource Discovery |TD_M2M_NH_79 |AE discovers accessible resources residing in Registrar CSE using the semanticFilter filter criteria | -|85 |Resource management<br /><br />Single Hop |ResultContent |TD_M2M_NH_84 |Check creation of <container> resource with result content set to 0(nothing) | -|86 |Resource management<br /><br />Single Hop |ResultContent |TD_M2M_NH_85 |Check creation of <container> resource with result content set to 1(attributes) | -|87 |Resource management<br /><br />Single Hop |ResultContent |TD_M2M_NH_86 |Check creation of <container> resource with result content set to 2(hierarchical address) | -|88 |Resource management<br /><br />Single Hop |ResultContent |TD_M2M_NH_87 |Check creation of <container> resource with result content set to 3(hierarchical address and attributes) | -|89 |Resource management<br /><br />Single Hop |ResultContent |TD_M2M_NH_88 |Check retrievability of <container> resource with result content set to 4(attributes and child resources) | -|90 |Resource management<br /><br />Single Hop |timeSeries |TD_M2M_NH_90 |AE creates a <timeSeries> resource in registrar CSE via a Create Request | -|91 |Resource management<br /><br />Single Hop |timeSeries |TD_M2M_NH_91 |AE retrieves information of a <timeSeries> resource via a Retrieve Request | -|92 |Resource management<br /><br />Single Hop |timeSeries |TD_M2M_NH_92 |AE updates attribute in <timeSeries> resource via a Update Request | -|93 |Resource management<br /><br />Single Hop |timeSeries |TD_M2M_NH_93 |AE deletes a <timeSeries> resource via a Delete Request | -|94 |Resource management<br /><br />Single Hop |timeSeriesInstance |TD_M2M_NH_94 |AE sends Create Request of a <timeSeriesInstance> resource to a <timeSeries> resource in Registrar CSE. Registrar CSE creates the <timeSeriesInstance> resource and updates the parent <timeSeries> resource with currentNrOfInstances and currentByteSize attributes correspondingly | -|95 |Resource management<br /><br />Single Hop |timeSeriesInstance |TD_M2M_NH_95 |AE retrieves information of a <timeSeriesInstance> resource via a Retrieve Request | -|96 |Resource management<br /><br />Single Hop |timeSeriesInstance |TD_M2M_NH_96 |AE sends Delete Request of a <timeSeriesInstance> resource in Registrar CSE. Registrar CSE delete the <timeSeriesInstance> resource and updates the parent <timeSeries> resource with currentNrOfInstances and currentByteSize attributes correspondingly | -|97 |Resource management<br /><br />Single Hop |timeSeriesInstance |TD_M2M_NH_97 |AE sends a <timeSeriesInstance> resource Create Request to a <timeSeries> resource which contains currentNrOfInstances value equals to that of maxNrOfInstances and Registrar CSE delets the oldest <timeSeriesInstance> resource from the <timeSeries> resource and then creates the requested <timeSeriesInstance> resource | -|98 |Resource management<br /><br />Single Hop |LocationPolicy |TD_M2M_NH_98 |AE creates a <locationPolicy> resource in registrar CSE via a locationPolicy Create Request | -|99 |Resource management<br /><br />Single Hop |LocationPolicy |TD_M2M_NH_99 |AE retrieves information of a <locationPolicy> resource via a locationPolicy Retrieve Request | -|100 |Resource management<br /><br />Single Hop |LocationPolicy |TD_M2M_NH_100 |AE updates attribute in <locationPolicy> resource via a locationPolicy Update Request | -|101 |Resource management<br /><br />Single Hop |LocationPolicy |TD_M2M_NH_101 |AE deletes a specific <locationPolicy> resource via a locationPolicy Delete Request | -|102 |Resource management<br /><br />Single Hop |Schedule |TD_M2M_NH_155 |AE creates a <schedule> resource in Registrar CSE via a Schedule Create Request | -|103 |Resource management<br /><br />Single Hop |Schedule |TD_M2M_NH_156 |AE retrieves information of a <schedule> resource via a schedule Retrieve Request | -|104 |Resource management<br /><br />Single Hop |Schedule |TD_M2M_NH_157 |AE updates attribute in <schedule> resource via a schedule Update Request | -|105 |Resource management<br /><br />Single Hop |Schedule |TD_M2M_NH_158 |AE deletes Schedule resource via a Schedule Delete Request | -|106 |Resource management<br /><br />Single Hop |Schedule |TD_M2M_NH_159 |CSE sends a notification request to the AE when Schedule resource is configured | -|107 |Non-Blocking |Synchronous request<br /> |TD_M2M_NB_01 |AE creates a container resource using non-blocking synchronous request in registrar CSE | -|108 |Non-Blocking |Synchronous request<br /> |TD_M2M_NB_02 |AE retrieves a Container resource using non-blocking synchronous request in registrar CSE | -|109 |Non-Blocking |Synchronous request<br /> |TD_M2M_NB_03 |AE updates a Container resource using non-blocking - synchronous request in registrar CSE | -|110 |Non-Blocking |Synchronous request<br /> |TD_M2M_NB_04 |AE deletes a Container resource using non-blocking synchronous request | -|111 |Non-Blocking |Asynchronous request |TD_M2M_NB_05 |AE creates a container resource using non-blocking asynchronous request | -|112 |Non-Blocking |Asynchronous request |TD_M2M_NB_06 |AE retrieves a Container resource using non-blocking asynchronous request | -|113 |Non-Blocking |Asynchronous request |TD_M2M_NB_07 |AE updates a Container resource using non-blocking asynchronous request | -|114 |Non-Blocking |Asynchronous request |TD_M2M_NB_08 |AE deletes a Container resource using non-blocking asynchronous request | -|115 |Single Hop |Retargeting |TD_M2M_SH_01 |AE creates a remote <Resource> resource | -|116 |Single Hop |Retargeting |TD_M2M_SH_02 |AE retrieves a remote <Resource> resource | -|117 |Single Hop |Retargeting |TD_M2M_SH_03 |AE updates a remote <Resource> resource | -|118 |Single Hop |Retargeting |TD_M2M_SH_04 |AE delete a remote <Resource> resource | -|119 |Single Hop |Discovery |TD_M2M_SH_09 |AE discovers accessible resources residing in the remote Hosting CSE using multiple Filter Criteria | -|120 |Single Hop |Unauthorized operation |TD_M2M_SH_10 |AE delete request is rejected after access rights verification using retargeting | -|121 |Single Hop |Notification |TD_M2M_SH_11 |AE receives a notification request from the remote hosting CSE | -|122 |Single Hop |mgmtObj |TD_M2M_SH_05 |AE creates a <mgmtObj> resource | -|123 |Single Hop |mgmtObj |TD_M2M_SH_06 |AE updates a <mgmtObj> resource | -|124 |Single Hop |mgmtObj |TD_M2M_SH_07 |AE retrieves a <mgmtObj> resource | -|125 |Single Hop |mgmtObj |TD_M2M_SH_08 |AE deletes a <mgmtObj> resource | -|126 |Single Hop |Announcement |TD_M2M_SH_12 |AE1 announces itself to CSE2 | -|127 |Single Hop |Announcement |TD_M2M_SH_13 |AE1 announces a child container to CSE2 | -|128 |Single Hop |Announcement |TD_M2M_SH_14 |AE1 announces an Optional Announce attribute to CSE2 | -|129 |Single Hop |Announcement |TD_M2M_SH_15 |AE2 retrieves an Announced Resource | -|130 |Single Hop |Announcement |TD_M2M_SH_16 |AE2 retrieves the original resource representation of an announced resource | -|131 |Single Hop |Announcement |TD_M2M_SH_21 |ContainerAnnc Delete by updating announceTo attribute. AE1 deletes its announced child container from CSE2 | -|132 |Single Hop |Announcement |TD_M2M_SH_22 |ContainerAnnc Delete by deleting original resource. AE1 deletes its announced child container from CSE2 | -|133 |Single Hop |Announcement |TD_M2M_SH_23 |Announced attribute Create by addition to announcedAttribute attribute AE1 announces an announcable attribute of its child container to CSE2 | -|134 |Single Hop |Announcement |TD_M2M_SH_24 |Announced attribute Create by creation of a MA attribute at the original resource. AE1 announces an MA attribute of its child container to CSE2 | -|135 |Single Hop |Announcement |TD_M2M_SH_25 |Announced attribute Delete by deletion from announcedAttribute attribute. AE1 de-announces an announcable attribute of its child container to CSE2 | -|136 |Single Hop |Announcement |TD_M2M_SH_26 |Announced attribute Delete by deletion of a MA attribute at the original resource. AE1 de-announces an MA attribute (conditionally mandatory) of its child container to CSE2 | -|137 |Single Hop |fanOut |TD_M2M_SH_17 |AE creates a <contentInstance> resource in each group member, where some memberIDs are on a remoteCSE | -|138 |Single Hop |fanOut |TD_M2M_SH_18 |AE retrieves a <contentInstance> resource from each group member, where some memberIDs are on a remoteCSE | -|139 |Single Hop |fanOut |TD_M2M_SH_19 |AE updates a <container> resource in each group member, where some memberIDs are on a remoteCSE | -|140 |Single Hop |fanOut |TD_M2M_SH_20 |AE deletes a <contentInstance> resource from each group member, where some memberIDs are on a remoteCSE | -|141 |Security |Secure AE Registration |TD_M2M_SE_01 |AE uses Provisioned Symmetric Key Security Association Establishment Framework to enable mutual authentication with the Registrar CSE. Registrar CSE performs AE authorization check on incoming AE registration request | -|142 |Security |Authentication |TD_M2M_SE_02 |AE establishes mutual authentication with the Registrar CSE using Provisioned Symmetric Key Security Association Establishment Framework | -|143 |Security |Authentication |TD_M2M_SE_03 |AE establishes mutual authentication with the Registrar CSE using Certificate-Based Security Association Establishment Framework | -|144 |Security |Authorization |TD_M2M_SE_04 |AE accesses <accessControlPolicy> resource using its selfPrivileges credentials | -|145 |Security |Authorization |TD_M2M_SE_05 |AE accesses <AE> resource using its accessControlPolicyIDs attribute | -|146 |Security |Authorization |TD_M2M_SE_06 |AE accesses <AE> resource using default access privileges | -|147 |Security |Authorization |TD_M2M_SE_07 |AE accesses <AE> resource using default access privileges | -|148 |Security |Authorization |TD_M2M_SE_08 |AE accesses <AE> resource using Direct Dynamic Authorization | -|149 |Security |Authorization |TD_M2M_SE_09 |AE accesses <AE> resource using Indirect Dynamic Authorization | -|150 |Security |Key provisioning management |TD_M2M_SE_10 |A MEF Handshake procedure establishes a mutually authenticated TLS session for protecting the communication between an MEF Client and MEF using pre-provisioned certificates | -|151 |Security |Key provisioning management |TD_M2M_SE_11 |A MEF Handshake procedure establishes a mutually authenticated TLS or DTLS session for protecting the communication between an MEF Client and MEF using pre-provisioned Master Credentials | -|152 |Security |Key provisioning management |TD_M2M_SE_12 |The MEF Client registers with the MEF to confirm that it is willing to use the services of the MEF, under the authorization of the administrating stakeholder | -|153 |Security |Key provisioning management |TD_M2M_SE_13 |The MEF Client retrieves MEF Client Configurations provided by the administrating stakeholder to the MEF | -|154 |Security |Key provisioning management |TD_M2M_SE_14 |MEF Client updates the MEF Client registration by any combination of extending the expirationTime of the MEF Client Registration record or updating the labels | -|155 |Security |Key provisioning management |TD_M2M_SE_15 |The MEF Client registers with the MEF to confirm that it is willing to use the services of the MEF, under the authorization of the administrating stakeholder | -|156 |Security |Key provisioning management |TD_M2M_SE_16 |Source MEF Client establishes a symmetric key with the MEF which can be retrieved for use by one or more Target MEF Clients | -|157 |Security |Key provisioning management |TD_M2M_SE_17 |The Target MEF Client to retrieve the Key Value from a MEF corresponding to a RelativeKeyID received by the Target MEF Client | -|158 |Security |Key provisioning management |TD_M2M_SE_18 |MEF Client updates the MEF Client registration by any combination of extending the expirationTime of the MEF Client Registration record or updating the labels | -|159 |Security |Key provisioning management |TD_M2M_SE_19 |Source MEF Client requests the MEF to stop distributing the registered key | -|160 |Security |End-to-End security management |TD_M2M_SE_20 |AE sends an arbitrary request primitive inside of ESPrim Object to CSE | -|161 |Security |End-to-End security management |TD_M2M_SE_21 |AE establishes a connection with the Registrar CSE using pairwiseE2EKey | -|163 |HAIM |HAIM Device Model |TD_M2M_NH_102 |AE1 creates a HAIM Light Device Model | -|164 |HAIM |HAIM Device Model |TD_M2M_NH_103 |AE2 reads the status of a HAIM Light Device Model | -|165 |HAIM |HAIM Device Model |TD_M2M_NH_104 |AE2 turns the binarySwitch of a HAIM Light Device Model "ON" or "OFF" | -|166 |HAIM |HAIM Device Model |TD_M2M_NH_105 |AE2 toggles the state of a HAIM Light Device Model | -|167 |HAIM |HAIM Device Model |TD_M2M_NH_160 |AE1 creates a Power Outlet SubDevice Model | -|168 |HAIM |HAIM Device Model |TD_M2M_NH_161 |AE1 creates a Toggle Action Model | -|169 |HAIM |HAIM Device Model |TD_M2M_NH_162 |AE1 creates Device Properties Model | -|170 |Semantics |Semantic Access Control Policy |TD_M2M_NH_106 |ACP triples are created when a new <accessControlPolicy> resource is created | -|171 |Semantics |Semantic Access Control Policy |TD_M2M_NH_107 |ACP triples are updated when an existing <accessControlPolicy> resource is updated | -|172 |Semantics |Semantic Access Control Policy |TD_M2M_NH_108 |ACP triples are deleted when an existing <accessControlPolicy> resource is deleted | -|173 |Semantics |Semantic Access Control Policy |TD_M2M_NH_109 |ACP-SD Binding Triples and SD relationship in SGS are created when AE creates a <semanticDescriptor> resource in Registrar CSE | -|174 |Semantics |Semantic Access Control Policy |TD_M2M_NH_110 |ACP-SD Binding Triples are updated when the accessControlPolicyIDs attribute of a <semanticDescriptor> resource is updated | -|175 |Semantics |Semantic Access Control Policy |TD_M2M_NH_111 |SD Relationship Triples are updated when the descriptor attribute of a <semanticDescriptor> resource is changed | -|176 |Semantics |Semantic Access Control Policy |TD_M2M_NH_112 |SD Relationship Triples are deleted when the descriptor attribute of a <semanticDescriptor> resource is deleted | -|177 |Semantics |Semantic Filtering and discovery |TD_M2M_NH_113 |AE discovers accessible resources residing in Registrar CSE using the <semanticFanOutPoint> | -|178 |Semantics |Semantic Filtering and discovery |TD_M2M_NH_114 |AE discovers accessible resources residing in Registrar CSE using the resource link-based Semantic Discovery | -|179 |Semantics |Semantic Filtering and discovery |TD_M2M_NH_115 |AE performs a Semantic Query request in Registrar CSE using the semanticFilter - filter criteria | -|180 |Semantics |Semantic Mashup |TD_M2M_NH_116 |AE creates a SemanticMashupJobProfile resource in Registrar CSE via a SemanticMashupJobProfile Create Request | -|181 |Semantics |Semantic Mashup |TD_M2M_NH_117 |AE retrieves information of a semanticMashupJobProfile resource via a semanticMashupJobProfile Retrieve Request | -|182 |Semantics |Semantic Mashup |TD_M2M_NH_118 |AE updates attribute in <semanticMashupJobProfile> resource via a semanticMashupJobProfile Update Request | -|183 |Semantics |Semantic Mashup |TD_M2M_NH_119 |AE deletes semanticMashupJobProfile resource via a semanticMashupJobProfile Delete Request | -|184 |Semantics |Semantic Mashup |TD_M2M_NH_120 |AE creates a semanticMashupInstance resource in Registrar CSE via a semanticMashupInstance Create Request | -|185 |Semantics |Semantic Mashup |TD_M2M_NH_121 |AE retrieves information of a semanticMashupInstance resource via a semanticMashupInstance Retrieve Request | -|186 |Semantics |Semantic Mashup |TD_M2M_NH_122 |AE updates attribute in <semanticMashupInstance> resource via a semanticMashupInstance Update Request | -|187 |Semantics |Semantic Mashup |TD_M2M_NH_123 |AE deletes semanticMashupInstance resource via a semanticMashupInstance Delete Request | -|188 |Semantics |Semantic Mashup |TD_M2M_NH_124 |AE retrieves information of a semanticMashupResult resource via a semanticMashupResult Retrieve Request | -|189 |Semantics |Semantic Mashup |TD_M2M_NH_125 |AE deletes semanticMashupResult resource via a semanticMashupResult Delete Request | -|190 |Semantics |Semantic Mashup |TD_M2M_NH_126 |AE triggers a calculation and generation of the mashup result by sending a <semanticMashupInstance>/<mashup> Retrieve Request | -|191 |Semantics |Ontology Repository |TD_M2M_NH_127 |AE creates a OntologyRepository resource in Registrar CSE via a OntologyRepository Create Request | -|192 |Semantics |Ontology Repository |TD_M2M_NH_128 |AE retrieves information of a ontologyRepository resource via a ontologyRepository Retrieve Request | -|193 |Semantics |Ontology Repository |TD_M2M_NH_129 |AE updates attribute in <ontologyRepository> resource via a ontologyRepository Update Request | -|194 |Semantics |Ontology Repository |TD_M2M_NH_130 |AE deletes OntologyRepository resource via a OntologyRepository Delete Request | -|195 |Semantics |Semantic validation |TD_M2M_NH_131 |AE checks the validity of the <semanticDescriptor> resource via a <semanticValidation> Update Request | -|196 |Semantics |Semantic validation |TD_M2M_NH_132 |AE creates a <semanticDescriptor> resource visa SemanticDescriptor Create Request and Registrar CSE checks the validity of the created <semanticDescriptor> resource | -|197 |Semantics |Ontology Mapping |TD_M2M_NH_133 |AE creates an OntologyMapping resource in Registrar CSE via an OntologyMapping Create Request | -|198 |Semantics |Ontology Mapping |TD_M2M_NH_134 |AE retrieves information of an ontology mapping result via a ontologyMapping Retrieve Request | -|199 |Semantics |Ontology Mapping |TD_M2M_NH_135 |AE updates attribute in <ontologyMapping> resource via a ontologyMapping Update Request | -|200 |Semantics |Ontology Mapping |TD_M2M_NH_136 |AE deletes OntologyMapping resource via a OntologyMapping Delete Request | -|201 |3GPP Interworking |Cellular IoT non-IP data delivery (NIDD) |TD_M2M_SH_27 |IN-CSE establishes SCEF Configuration for NIDD | -|202 |3GPP Interworking |Cellular IoT non-IP data delivery (NIDD) |TD_M2M_SH_28 |IN-AE sends a downlink non-IP data to a UE hosting ADN-AE | -|203 |3GPP Interworking |Cellular IoT non-IP data delivery (NIDD) |TD_M2M_SH_29 |IN-AE sends a downlink non-IP data to a UE hosting ADN-AE | -|204 |3GPP Interworking |Monitoring events |TD_M2M_SH_30 |IN-AE monitors UE Reachability status | -|205 |3GPP Interworking |Monitoring events |TD_M2M_SH_31 |UE Availability after DDN Failure scenario | -|206 |3GPP Interworking |Monitoring events |TD_M2M_SH_32 |UE Communication Failure scenario | -|207 |3GPP Interworking |Monitoring events |TD_M2M_SH_33 |Roaming status scenario | -|208 |3GPP Interworking |Monitoring events |TD_M2M_SH_34 |Location Reporting scenario | -|209 |3GPP Interworking |3GPP Based Device triggering |TD_M2M_SH_35 |IN-AE triggers ADN-AE hosted on UE | -|210 |3GPP Interworking |3GPP Based Device triggering |TD_M2M_SH_36 |IN-AE recalls/replaces a trigger request targeting ADN-AE hosted on UE that has been already created in IN-CSE | -|211 |3GPP Interworking |Configuration of traffic patterns |TD_M2M_SH_37 |IN-CSE translates the oneM2M Node Traffic Pattern (TP) into a 3GPP Device Communication Pattern | -|212 |3GPP Interworking |Group message delivery using MBMS |TD_M2M_SH_38 |IN-AE creates a MBMS Group for handling group related requests | -|213 |3GPP Interworking |Group message delivery using MBMS |TD_M2M_SH_39 |IN-AE sends a request for accessing member resources to the Group Hosting CSE | -|214 |Advanced Subscriptions & Notifications |Notification Target removal |TD_M2M_NH_137 |AE removes notificationTargetMgmtPolicyRef via a notificationTargetMgmtPolicyRef Delete Request | -|215 |Advanced Subscriptions & Notifications |NotificationTargetMgmtPolicyRef |TD_M2M_NH_138 |AE creates a notificationTargetMgmtPolicyRef resource in registrar CSE via a notificationTargetMgmtPolicyRef Create Request | -|216 |Advanced Subscriptions & Notifications |NotificationTargetMgmtPolicyRef |TD_M2M_NH_139 |AE retrieves notificationTargetMgmtPolicyRef resource from Registrar CSE | -|217 |Advanced Subscriptions & Notifications |NotificationTargetMgmtPolicyRef |TD_M2M_NH_140 |AE updates information about a notificationTargetMgmtPolicyRef via notificationTargetMgmtPolicyRef>Update Request | -|218 |Advanced Subscriptions & Notifications |NotificationTargetMgmtPolicyRef |TD_M2M_NH_141 |AE removes notificationTargetMgmtPolicyRef via a notificationTargetMgmtPolicyRef Delete Request | -|219 |Advanced Subscriptions & Notifications |NotificationTargetPolicy |TD_M2M_NH_142 |AE creates a notificationTargetPolicy resource in registrar CSE via a notificationTargetPolicy Create Request | -|220 |Advanced Subscriptions & Notifications |NotificationTargetPolicy |TD_M2M_NH_143 |AE retrieves notificationTargetPolicy resource from Registrar CSE | -|221 |Advanced Subscriptions & Notifications |NotificationTargetPolicy |TD_M2M_NH_144 |AE updates information about a notificationTargetPolicy via <notificationTargetPolicy> Update Request | -|222 |Advanced Subscriptions & Notifications |NotificationTargetPolicy |TD_M2M_NH_145 |AE removes notificationTargetPolicy via a <notificationTargetPolicy> Delete Request | -|223 |Advanced Subscriptions & Notifications |PolicyDeletionRules |TD_M2M_NH_146 |AE creates a policyDeletionRules resource in registrar CSE via a policyDeletionRules Create Request | -|224 |Advanced Subscriptions & Notifications |PolicyDeletionRules |TD_M2M_NH_147 |AE retrieves policyDeletionRules resource from Registrar CSE | -|225 |Advanced Subscriptions & Notifications |PolicyDeletionRules |TD_M2M_NH_148 |AE updates information about a policyDeletionRules via <policyDeletionRules> Update Request | -|226 |Advanced Subscriptions & Notifications |PolicyDeletionRules |TD_M2M_NH_149 |AE removes policyDeletionRules via a <policyDeletionRules> Delete Request | -|227 |Advanced Subscriptions & Notifications |CrossResourceSubscription |TD_M2M_NH_150 |AE creates a crossResourceSubscription resource in registrar CSE via a crossResourceSubscription Create Request | -|228 |Advanced Subscriptions & Notifications |CrossResourceSubscription |TD_M2M_NH_151 |AE retrieves crossResourceSubscription resource from Registrar CSE | -|229 |Advanced Subscriptions & Notifications |CrossResourceSubscription |TD_M2M_NH_152 |AE updates information about a crossResourceSubscription via <crossResourceSubscription> Update Request | -|230 |Advanced Subscriptions & Notifications |CrossResourceSubscription |TD_M2M_NH_153 |AE removes crossResourceSubscription via a <crossResourceSubscription> Delete Request | -|231 |Advanced Subscriptions & Notifications |CrossResourceSubscription |TD_M2M_NH_154 |AE receives a notification request from the HOST CSE | -|232 |Modbus Interworking |Modbus Thermometer device |TD_M2M_NH_163 |AE1 creates Device Model for Modbus device | -|233 |Modbus Interworking |Modbus Thermometer device |TD_M2M_NH_164 |Modbus IPE reads data from Modbus device and updates Registrar CSE with the read data | -|234 |Modbus Interworking |Modbus Thermometer device |TD_M2M_NH_165 |AE writes data into a Modbus device by updating <flexContainer> resource in Registrar CSE | -|235 |NoDN Interworking |Generic IPE |TD_M2M_NH_166 |NoDN IPE reads data from a NoDN device and updates Registrar CSE with the read data | -|236 |NoDN Interworking |Generic IPE |TD_M2M_NH_167 |AE writes data into a NoDN device by updating <flexContainer> resource in Registrar CSE | - - - - -# 7 Configuration - -## 7.1 Test Configuration - -### 7.1.1 No hop - -#### 7.1.1.1 M2M_CFG_01 -The AE manages resources on the registrar CSE (Hosting CSE). - -oneM2M entities model - - - - -**Figure 7.1.1.1-1** - - -#### 7.1.1.2 M2M_CFG_02 - -oneM2M entities model - - - - -**Figure 7.1.1.2-1** - - -#### 7.1.1.3 M2M_CFG_10 - -oneM2M entities model - - - - -**Figure 7.1.1.3-1** - -> NOTE: For HAIM Model tests, clause 8.5, AE1 represents a native oneM2M device that implements the HAIM models or a combined IPE(AE) plus a non-oneM2M device node (nodn). - -### 7.1.2 Single hop - -#### 7.1.2.1 M2M_CFG_03 - -The AE manages resources on the remote CSE. - -oneM2M entities model - - - - -**Figure 7.1.2.1-1** - - -#### 7.1.2.2 M2M_CFG_04 - -oneM2M entities model - - - - -**Figure 7.1.2.2-1** - - -#### 7.1.2.3 M2M_CFG_05 - -oneM2M entities model - - - - -**Figure 7.1.2.3-1** - - -#### 7.1.2.4 M2M_CFG_08 - -This configuration concerns group management when the AE is using a group to fan out requests to multiple members. The connection between the AE and the Group Hosting CSE, - the Group Hosting CSE and the Member Hosting CSE may be a multi hop connection following the definition in clause 7.1.3. - -This configuration is mapped to cases including: - - -- AE sends a request addressing <group>/fanOutPoint in the Group Hosting CSE, the Group Hosting CSE then further fans out the request to each Member Hosting CSE. -- The Member Hosting CSE sends a notification to the Group Hosting CSE pertaining to the subscription made through the Group Hosting CSE. The Group Hosting CSE then further aggregates the notification and sends it back to the AE. - - - -**Figure 7.1.2.4-1** - - -#### 7.1.2.5 M2M_CFG_09 - -This configuration concerns device management using external technologies. - -This configuration is mapped to cases including: - - -- The AE sends a request addressing <mgmtObj> to IN-CSE. IN-CSE then further acts as a Management Server to send management commands to Managed Entity over the mc interface. The management command is defined in OMA DM, BBF TR069 or LWM2M. - - - -**Figure 7.1.2.5-1** - - -#### 7.1.2.6 M2M_CFG_11 - -This configuration concerns device management using 3GPP network. - - - - - -#### 7.1.2.7 M2M_CFG_12 -This configuration concerns group management when the IN-AE is using a group to fan out requests to multiple members in 3GPP interworking scenraios. The connection between the IN-AE and the Group Hosting CSE, the Group Hosting CSE and the Member Hosting CSE may be a multi hop connection following the definition in clause 7.1.3. - -This configuration is mapped to cases including: - - -- IN-AE sends a request addressing <group>/fanOutPoint in the Group Hosting CSE, the Group Hosting CSE then further fans out the request to each Member Hosting CSE through 3GPP network. - - - - -### 7.1.3 Multi hops - -#### 7.1.3.1 M2M_CFG_06 - -oneM2M entities model - - - - -**Figure 7.1.3.1-1** - - -#### 7.1.3.2 M2M_CFG_07 - -oneM2M entities model - - - - -**Figure 7.1.3.2-1** - - -# 8 Test Descriptions - -## 8.1 No Hop configuration testing - -### 8.1.1 CSEBase Management - -#### 8.1.1.1 CSEBase Retrieve on Mca - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_01 | -|Objective: |Objective: |Objective: |AE retrieves the CSEBase resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.2.11<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been automatically created in CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a retrieve Request to CSE with name {CSEBaseName} | -|2 |Mca |PRO Check Primitive |Operation (op) = 2 (Retrieve)<br />To (to) = Resource-ID of requested <CSEBase> resource, assumed CSE-relative here <br />From (from) = AE-ID of request originator<br />Request Identifier (rqi) = (token-string) | -|3 |Mca |PRO Check Primitive |Response Status Code (rsc) = 2000 (OK)<br />Request Identifier (rqi) = same string as received in request message<br />Content (pc) = Serialized Representation of <CSEBase> resource | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - - -### 8.1.2 RemoteCSE Management - -#### 8.1.2.1 RemoteCSE Create - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_02 | -|Objective: |Objective: |Objective: |Registree CSE registers to Registrar CSE | -|Configuration: |Configuration: |Configuration: |M2M_CFG_02 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2.1<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.2.1 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName} | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |Registree CSE is requested to send a RemoteCSE Create request to Registrar CSE | -|2 |<br />Mcc |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = Registree CSE-ID<br />rqi = (token-string)<br />ty = 16 (RemoteCSE)<br />pc = Serialized representation of <RemoteCSE> resource | -|3 |<br />Mcc |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <RemoteCSE> resource | -|4 | |IOP Check |Check if possible that the <remoteCSE> resource has been created in registrar CSE | -|5 | |IOP Check |Check if possible that the corresponding <remoteCSE> resource has been also created in registree CSE | -|6 | |IOP Check |Registree CSE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.2.2 remoteCSE Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_03 | -|Objective: |Objective: |Objective: |Registree CSE retrieves RemoteCSE from Registrar CSE | -|Configuration: |Configuration: |Configuration: |M2M_CFG_02 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName} | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |Registree CSE is requested to send a RemoteCSE retrieve request to Registrar CSE | -|2 |<br />Mcc |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/{remoteCSEName}<br />fr = Registree CSE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mcc |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <RemoteCSE> resource | -|4 | |IOP Check |Registree CSE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.2.3 remoteCSE Update - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_04 | -|Objective: |Objective: |Objective: |Registree CSE updates RemoteCSE from Registrar CSE | -|Configuration: |Configuration: |Configuration: |M2M_CFG_02 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.2.3 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName} | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |Registree CSE is requested to send a RemoteCSE update request to Registrar CSE | -|2 |<br />Mcc |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{remoteCSEName}<br />fr = Registree CSE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <RemoteCSE> resource | -|3 | |IOP Check |Check if possible that the <remoteCSE> resource has been updated in registrar CSE | -|4 |<br />Mcc |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2004 (UPDATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <RemoteCSE> resource | -|5 | |IOP Check |Registree CSE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.2.4 remoteCSE Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_05 | -|Objective: |Objective: |Objective: |Registree CSE deletes RemoteCSE from Registrar CSE | -|Configuration: |Configuration: |Configuration: |M2M_CFG_02 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.2.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName} | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |Registree CSE is requested to send a RemoteCSE delete request to Registrar CSE | -|2 |<br />Mcc |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{remoteCSEName}<br />fr = Registree CSE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mcc |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | -|4 | |IOP Check |Check if possible that the <remoteCSE> resource has been removed from registrar CSE | -|5 | |IOP Check |Check if possible that the <remoteCSE> resource is also removed from registree CSE | -|6 | |IOP Check |Registree CSE indicates successful operation - | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -### 8.1.3 Application Entity Registration - -#### 8.1.3.1 AE Create - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_06 | -|Objective: |Objective: |Objective: |AE registers to its registrar CSE via an AE Create Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.2.2 <br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.5.2.1 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in CSE with name {CSEBaseName}<br />AE does not have an AE-ID, i.e. it registers from scratch | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a AE Create request to register to the Registrar CSE | -|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 2 (AE)<br />pc = Serialized representation of <AE> resource | -|3 | |IOP Check |Check if possible that the <AE> resource is created in registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <AE> resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.3.2 AE Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_07 | -|Objective: |Objective: |Objective: |AE retrieves <AE> resource via an AE Retrieve Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.2.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.5.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}bgf | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a AE retrieve request to Registrar CSE | -|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/{AE}<br />fr = AE-ID of request originator<br />rqi = (token-string) | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <AE> resource | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.3.3 AE Update - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_08 | -|Objective: |Objective: |Objective: |AE updates attribute in <AE> resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.2.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.5.2.3 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: | CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE} | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send an AE Update Request | -|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{AE}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <AE> resource | -|3 | |IOP Check |Check if possible that the <AE> resource has been updated in registrar CSE | -|4 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2004 (UPDATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <AE> resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.3.4 AE Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_09 | -|Objective: |Objective: |Objective: |AE de-registers by deleting <AE> resource via an AE Delete Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.2.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.5.2.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE} | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send an AE Delete Request | -|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{AE}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | -|4 | |IOP Check |Check if possible that the <AE> resource has been removed from registrar CSE | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -### 8.1.4 Container Management - -#### 8.1.4.1 Container Create - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_10 | -|Objective: |Objective: |Objective: |AE creates a container resource in registrar CSE via a container Create Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.6.2.1 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE sends a request to create a <container> | -|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of <AE> resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 3 (Container)<br />pc = Serialized representation of <container> resource | -|3 | |IOP Check |Check if possible that the <container> resource is created in registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.4.2 Container Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_11 | -|Objective: |Objective: |Objective: |AE retrieves information of a container resource via a container Retrieve Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.6.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Retrieve Request for a <container> | -|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <container> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.4.3 Container Update - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_12 | -|Objective: |Objective: |Objective: |AE updates attribute in application resource via a container Update Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.6.2.3 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource - <container> on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a container Update Request to update the lifetime of the resource | -|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/URI of <container> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <container> resource | -|3 | |IOP Check |Check if possible that the < container > resource is updated in Registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.4.4 Container Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_13 | -|Objective: |Objective: |Objective: |AE deletes a specific container resource via a container Delete Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.6.2.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a container Delete Request | -|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <container> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 | |IOP Check |Check if possible that the <container> resource is deleted in registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | -|5 | |IOP Check |Check if possible that the <container> resource has been removed in registrar CSE | -|6 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -### 8.1.5 ContentInstance Management - -#### 8.1.5.1 ContentInstance Create - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_14 | -|Objective: |Objective: |Objective: |AE adds a contentInstance resource <contentInstance> to a specific container in Registrar CSE via a contentInstance Create Request and the Registrar CSE updates the parent <container> resource with stateTag, currentNrOfInstances, and CurrentByteSize attributes correspondingly | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.7<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.7.1.1 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on registrar CSE<br />AE has created a container resource <container> on registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the <container> resource and AE sends a request to create a < contentInstance > resource | -|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of < container > resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 4 (contentInstance)<br />pc = Serialized representation of <contentInstance> resource | -|3 | |IOP Check |Check if possible that the <contentInstance> resource is created in Registrar CSE and AE sends a RETRIEVE request to the <container> resource to check that if the Registrar CSE has updated stateTag, currentNrOfInstances, and CurrentByteSize attribute correspondingly which is resulted from the successful creation of child <contentInstance> resource | -|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <contentInstance> resource | -|5 | |IOP Check |AE indicates successful CREATE operation of <contentInstance> and indicates Registrar CSE has updated stateTag, currentNrOfInstances, and CurrentByteSize attribute correspondingly by checking the response of a <container> request to the <container> resource | -|IOP Verdict |IOP Verdict |Set verdict to pass if IOP check goal is achieved exactly, otherwise verdict fail is set with corresponding error message |Set verdict to pass if IOP check goal is achieved exactly, otherwise verdict fail is set with corresponding error message | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.5.2 ContentInstance Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_15 | -|Objective: |Objective: |Objective: |AE retrieves information of a contentInstance resource via a contentInstance Retrieve Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.8<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.7.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a contentInstance resource <contentInstance> as child resource of <container> resource | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Retrieve Request for a <contentInstance> | -|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <contentInstance> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <contentInstance> resource | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.5.3 ContentInstance Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_17 | -|Objective: |Objective: |Objective: |AE deletes contentInstance resource via a contentInstance Delete Request and the Registrar CSE updates the parent <container> resource with currentNrOfInstances, and CurrentByteSize attributes correspondingly | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.7.2.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a contentInstance resource <contentInstance> as child resource of <container> resource | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the <container> resource and AE is requested to send a contentInstance Delete Request | -|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <contentInstance> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 | |IOP Check |Check if possible that the <contentInstance> resource is deleted in Registrar CSE and AE sends a RETRIEVE request to the parent <container> resource to check that if the Registrar CSE has updated currentNrOfInstances, and CurrentByteSize attribute correspondingly which is resulted from the successful deletion of child <contentInstance> resource | -|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | -|5 | |IOP Check |Check if possible that the <contentInstance> resource has been removed in registrar CSE. | -|6 | |IOP Check |AE indicates successful DELETE operation of <contentInstance> and indicates Registrar CSE has updated currentNrOfInstances, and CurrentByteSize attribute correspondingly | -|IOP Verdict |IOP Verdict |Set the verdict to pass if both the <contentInstance> is deleted and the Registrar CSE updated currentNrOfInstances, and CurrentByteSize attribute. Otherwise, set the verdict to fail with corresponding error message |Set the verdict to pass if both the <contentInstance> is deleted and the Registrar CSE updated currentNrOfInstances, and CurrentByteSize attribute. Otherwise, set the verdict to fail with corresponding error message | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.5.4 <latest> ContentInstance Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_49 | -|Objective: - |Objective: |Objective: |AE deletes a <latest> resource of a <container> and the Registrar CSE points a latest <contentInstance> among the existing contentInstances to the <latest> resource of the <container> | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.12<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.27.2.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created more than one contentInstances <contentInstance> as child of <container> on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE retrieves a <latest> resource in a <container> and then sends a DELETE request to the <latest> resource of the <container> | -|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <latest> resource of a <container><br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = representation of deleted <latest> resource of a <container> | -|4 | |IOP Check |AE indicates successful DELETE operation of a <latest> resource and AE sends a RETRIEVE request to <latest> resource of a <container> to check if the retrieved <latest> resource in the <container> is different with that one that was retrieved before DELETE request of the <latest> resource in terms of resourceID and resourceName attribute value | -|IOP Verdict |IOP Verdict |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.5.5 <oldest> ContentInstance Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_50 | -|Objective: |Objective: |Objective: |AE deletes a <oldest> resource of a <container> and the Registrar CSE points an oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.14<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.28.2.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created more than one contentInstances <contentInstance> as child of <container> on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE retrieves a <oldest> resource of a <container> and AE sends a DELETE Request to the <oldest> resource of the <container> | -|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <oldest> resource of a <container><br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = representation of deleted <oldest> resource of a <container> | -|3 |<br />Mca | | | -|3 |<br />Mca | | | -|3 |<br />Mca | | | -|4 | |IOP Check |AE indicates successful DELETE operation of a <oldest> resource and AE sends a RETRIEVE request to <oldest> resource of a <container> to check if the retrieved <oldest> resource in the <container> is different with that one that was retrieved before DELETE request of the <oldest> resource in terms of resourceID and resourceName attribute values | -|IOP Verdict |IOP Verdict |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.5.6 ContentInstance Create when currentNrOfInstance equals to maxNrOfInstances in parent <container> resource - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_51 | -|Objective: |Objective: |Objective: |AE sends a <contentInstance> CREATE request to a <container> which contains attribute currentNrOfInstances whose value equals to that of maxNrOfInstances and Registrar CSE deletes the oldest <contentInstance> from the parent <container> and then creates the requested <contentInstance> resource for the originator AE | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.7<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.6.2.1 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on registrar CSE<br />AE has created a container resource <container> (where the number of contentInstances equals to the value set in maxNrOfInstance) on registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the <oldest> contentInstance resource and <br />AE sends a request to create a <contentInstance> resource | -|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of <container> resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 4 (contentInstance)<br />pc = Serialized representation of <contentInstance> resource | -|3 | |IOP Check |Check if possible that the <oldest> resource of a <container> is deleted | -|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <contentInstance> resource | -|5 | |IOP Check |AE indicates successful CREATE operation of <contentInstance> and indicates the representation of the recent <oldest> resource in the <container> is different with that of <oldest> resource retrieved at the beginning of test in terms of resourceID and resourceName attribute value | -|IOP Verdict |IOP Verdict |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message |Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.5.7 <latest> ContentInstance Retrieve - -##### 8.1.5.7.1 Attribute locationID of the <container> resource configured - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_102 | -|Objective: |Objective: |Objective: |AE retrieves a <latest> resource of a <container> for which attribute locationID is configured, value of locationUpdatePeriod is marked '0' or not defined and locationSource attribute is 'Network Based' | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.11<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.27.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a <locationPolicy> resource on Registrar CSE having its resourceID and locationContainerID attribute set to locationID and resourceID attribute of the <container> resource respectively<br />In resource <locationPolicy>, value of locationUpdatePeriod is marked '0' or not defined and locationSource attribute is 'Network Based' | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Retrieve Request for a <latest> | -|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <container> resource/la<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of latest <contentInstance> resource, created after acquiring location info from Location Server, in response to Location Request made by the CSE, using the attributes stored in the <locationPolicy> resource | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -##### 8.1.5.7.2 Attribute locationID of the <container> resource not configured - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_71 | -|Objective: |Objective: |Objective: |AE retrieves a <latest> resource of a <container> and the Registrar CSE points a latest - <contentInstance> among the existing contentInstances to the <latest> resource of the <container> | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.11<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.27.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created multiple contentInstance resources <contentInstance> as child resource of <container> resource | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Retrieve Request for a <latest> | -|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <container> resource/la<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of latest <contentInstance> resource | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.5.8 <oldest> ContentInstance Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Identifier: | -|-|-|-|-|-|-| -|Identifier: |Identifier: |TD_M2M_NH_72 |TD_M2M_NH_72 |Objective: |Objective: | -|Objective: |AE retrieves a <oldest> resource of a <container> and the Registrar CSE points a oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> |AE retrieves a <oldest> resource of a <container> and the Registrar CSE points a oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> |Configuration: |Configuration: |Configuration: | -|M2M_CFG_01 |M2M_CFG_01 |References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.13<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.28.2.2 | -|oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.13<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.28.2.2 | | | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created multiple contentInstance resources <contentInstance> as child resource of <container> resource |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created multiple contentInstance resources <contentInstance> as child resource of <container> resource |Test Sequence | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence |Step |RP | -|Type |Description |Description |1 | |Stimulus | -|AE is requested to send a Retrieve Request for a <oldest> |AE is requested to send a Retrieve Request for a <oldest> |2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <container> resource/ol<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <container> resource/ol<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty |3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of oldest <contentInstance> resource |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of oldest <contentInstance> resource | -|4 | |IOP Check |AE indicates successful operation |AE indicates successful operation | -|| -|| - - - - -### 8.1.6 Discovery - -#### 8.1.6.1 Discovery of all resources - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_18 | -|Objective: |Objective: |Objective: |AE discovers all accessible resources from registrar CSE | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName} | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a discovery request to registrar CSE | -|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />fu=1<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing addresses of all discovered resources | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.6.2 Discovery with label filter criteria - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_19 | -|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using the label filter criteria | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />A <Container> resource with label "key1" is created on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Discovery request in order to discover the <Container> resource using the label filter criteria | -|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />fu=1<br />lbl=key1<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the address of the <Container> address | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.6.3 Discovery with limit filter criteria - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_20 | -|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE limiting the number of matching resources to the specified value | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName} | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Discovery request in order to discover at most 2 resources in registrar CSE | -|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />fu = 1<br />lim = 2<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />cnst = 1<br />cno t= 2<br />pc = Serialized representation of data object containing the address of the <Container> address | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.6.4 Discovery with multiple filter criteria - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_21 | -|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using multiple Filter Criteria | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |Two <Container> resources with labels "key1" and "key2" are created in Registrar CSE<br />A <Group> resources with labels "key1" and "key2" is created in Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Discovery request in order to discover specific resources located - in Registrar CSE using multiple filter criteria (label, resource type and limit) | -|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />fu=1<br />lbl=key1<br />lbl=key2<br />ty=3<br />lim=1<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the address of one of the <Container> resources | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.6.5 Discovery with level filter criteria - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_58 | -|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 1 | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |<AE1> and <AE2> resources are created in Registrar CSE<br />A <Container> resource is created under both <AE> resources in Registrar CSE<br />A <ContentInstance> resource is created under both <Container> resources in Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Discovery request in order to discover specific resources located in Registrar CSE using level filter criteria value set to 1 | -|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu=1<br />lvl=1<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the address of both <AE> resources | -|4 | |IOP Check |AE1 indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_59 | -|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 2 | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |<AE1> and <AE2> resources are created in Registrar CSE. A <Container> resource is created under both <AE> resources in Registrar CSE<br />A <ContentInstance> resource is created under both <Container> resources in Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Discovery request in order to discover specific resources located in Registrar CSE using level filter criteria value set to 2 | -|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu = 1<br />lvl = 2<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the address of all <AE> and <Container> resources | -|4 | |IOP Check |AE1 indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_60 | -|Objective: |Objective: |Objective: |AE1 discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 3 | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |<AE1> and <AE2> resources are created in Registrar CSE<br />A <Container> resource is created under both <AE> resources in Registrar CSE<br />A <ContentInstance> resource is created under both <Container> resources in Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE1 is requested to send a Discovery request in order to discover specific resources located in Registrar CSE using level filter criteria value set to 3 | -|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu=1<br />lvl=3<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the address of all <AE>, <Container> and <ContentInstance>resources | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.6.6 Discovery with offset filter criteria - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_61 | -|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using the offset filter criteria value set to 3 | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |<AE1> and <AE2> resources are created in Registrar CSE. A <Container> resource is created under both <AE> resources in Registrar CSE<br />A <ContentInstance> resource is created under both <Container> resources in Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE1 is requested to send a Discovery request in order to discover specific resources located in Registrar CSE using offset filter criteria value set to 3 | -|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu=1<br />ofst=3<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing only 3 of the 6 <AE>, <container> and <contentInstance> resources hosted by the Registrar CSE | -|4 | |IOP Check |AE1 indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_62 | -|Objective: |Objective: |Objective: |AE discovers all the accessible resources residing in Registrar CSE using the offset filter criteria | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |<AE1> and <AE2> resources are created in Registrar CSE<br />A <Container> resource is created under both <AE> resources in Registrar CSE<br />A <ContentInstance> resource is created under both <Container> resources in Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE1 is requested to send a Discovery request in order to discover specific resources located in Registrar CSE using offset filter criteria attribute value set to 0 (Default value) and limit filter Criteria attribute value set to 2 | -|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu = 1<br />lim = 2<br />pc = empty | -|3 | |IOP Check |Registrar CSE sends success response to AE1 | -|4 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />cnst = 1<br />cnot = 2<br />pc = Serialized representation of data object containing the address of first 2 resources hosted by Registrar CSE | -|5 | |IOP Check |AE1 sends discovery request to Registrar CSE with offset filtercriteria value set to 2 and limit filter criteria attribute value set to 2 | -|6 |<br />Mca |PRO Check Primitive |Sent request - contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu=1<br />ofst = 2<br />lim = 2<br />pc = empty | -|7 | |IOP Check |Registrar CSE sends success response to AE1 | -|8 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />cnst=1<br />cnot=4<br />pc = Serialized representation of data object containing the address of next 2 resources hosted by Registrar CSE | -|9 | |IOP Check |AE1 sends discovery request to Registrar CSE with offset filtercriteria value set to 4 and limit filtercriteria attribute value set to 2 | -|10 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE1-ID<br />rqi = (token-string)<br />fu = 1<br />ofst = 4<br />lim = 2<br />pc = empty | -|11 | |IOP Check |Registrar CSE sends success response to AE1 | -|12 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />cnst = 2<br />pc = Serialized representation of data object containing the address of last 2 resources hosted by Registrar CSE | -|13 | |IOP Check |AE1 indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -### 8.1.7 Subscription Management - -#### 8.1.7.1 Subscription Create - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_22 | -|Objective: |Objective: |Objective: |AE creates a subscription to Application Entity resource via subscription Create Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.8.2.1 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on registrar CSE<br />AE has created a container resource <container> on registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a subscription Create request to the Registrar CSE | -|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of <Container> resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 23 (Subscription)<br />pc = Serialized representation of <Subscription> resource | -|3 | |IOP Check |Check if possible that the <Subscription> resource is created in registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <Subscription> resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.7.2 Subscription Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_23 | -|Objective: |Objective: |Objective: |AE retrieves subscription resource from Registrar CSE | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.8.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a subscription resource <subscription> on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Retrieve Request for a <subscription> | -|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <Subscription> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <Subscription> resource | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.7.3 Subscription Update - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_24 | -|Objective: |Objective: |Objective: |AE updates information about a subscription via subscription Update Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.8.2.3 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a subscription resource <subscription> on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a subscription Update Request to update the lifetime of the resource. | -|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/URI of <Subscription> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <Subscription> resource | -|3 | |IOP Check |Check if possible that the <subscription> resource is updated in Registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <Subscription> resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.7.4 Subscription Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_25 | -|Objective: |Objective: |Objective: |AE cancels subscription via an subscription Delete Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.8.2.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE<br />AE has created a subscription resource <subscription> on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a subscription Delete Request | -|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <Subscription> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 | |IOP Check |Check if possible that the <Subscription> resource is deleted in registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | -|5 | |IOP Check |Check if possible that the <subscription> resource has been removed in registrar CSE | -|6 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -### 8.1.8 accessControlPolicy Management - -#### 8.1.8.1 accessControlPolicy Create - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_26 | -|Objective: |Objective: |Objective: |AE creates an accessControlPolicy resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.3.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.2.2.1 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE} | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send an accessControlPolicy Create Request | -|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/{AE}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 1 (accessControlPolicy)<br />pc = Serialized representation of <accessControlPolicy > resource | -|3 | |IOP Check |Check if possible that the <container> resource is created in registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <accessControlPolicy> resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.8.2 accessControlPolicy Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_27 | -|Objective: |Objective: |Objective: - |AE retrieves accessControlPolicy resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.3.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.2.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName} | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a accessControlPolicy retrieve request to Registrar CSE | -|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/{AE}/{accessControlPolicyName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <accessControlPolicy> resource | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.8.3 accessControlPolicy Update - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Identifier: | -|-|-|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_28 |Objective: |Objective: | -|Objective: |Objective: |AE updates attribute in accessControlPolicy resource |Configuration: |Configuration: |Configuration: | -|Configuration: |M2M_CFG_01 |References: |References: |References: |References: | -|oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.3.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.2.2.3 | | | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName} |Test Sequence | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence |Step |Step | -|RP |Type |Description |1 |1 | | -|Stimulus |AE is requested to send an accessControlPolicy update request to Registrar CSE |2 |2 |<br />Mca |PRO Check Primitive | -|op = 3 (Update)<br />to = {CSEBaseName}/{AE}/{accessControlPolicyName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <accessControlPolicy > resource |3 |3 | |IOP Check |Check if possible that the <accessControlPolicy> resource has been updated in registrar CSE | -|4 |4 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2004 (UPDATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <accessControlPolicy> resource |5 | -|5 | |IOP Check |AE indicates successful operation |IOP Verdict |IOP Verdict | -|IOP Verdict | | |PRO Verdict |PRO Verdict |PRO Verdict | -| | | -|| -|| - - - - -#### 8.1.8.4 accessControlPolicy Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_29 | -|Objective: |Objective: |Objective: |AE deletes accessControlPolicy resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.3.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.2.2.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName} | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send an accessControlPolicy delete request to Registrar CSE | -|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{AE}/{accessControlPolicyName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | -|4 | |IOP Check |Check if possible that the <accessControlPolicy> resource has been removed from registrar CSE. | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.8.5 Unauthorized operation (Insufficient Access Rights, operations) - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_30 | -|Objective: |Objective: |Objective: |AE delete request is rejected due to accessControlPolicy (accessControlOperations) | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.15 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName}, and accessControlOperations with no delete privilege<br />AE has created a <container> resource on registrar CSE under <AE>, with name {containerName} and accessControlPolicyIDs including proper identifier of accessControlPolicy resource | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a container Delete Request for resource <container> | -|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{AE}/{containerName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 4103 (ACCESS_DENIED)<br />rqi = (token-string) same as received in request message<br />pc = empty | -|4 | |IOP Check |Check if possible that the <container> resource has not been removed in registrar CSE | -|5 | |IOP Check |AE indicates unsuccessful operation (Delete error - no privilege) | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.8.6 Unauthorized operation (Insufficient Access Rights, originators) - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_73 | -|Objective: |Objective: |Objective: |AE delete request is rejected due to accessControlPolicy (accessControlOriginators) | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.15 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName}, and accessControlOriginators with no privilege for AE<br />AE has created a <container> resource on registrar CSE under <AE>, with name {containerName} and accessControlPolicyIDs including proper identifier of accessControlPolicy resource | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a container Delete Request for resource <container> | -|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{AE}/{containerName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 4103 (ACCESS_DENIED)<br />rqi = (token-string) same as received in request message<br />pc = empty | -|4 | |IOP Check |Check if possible that the <container> resource has not been removed in registrar CSE | -|5 | |IOP Check |AE indicates unsuccessful operation (Delete error - no privilege) | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.8.7 Authorized operation - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_74 | -|Objective: |Objective: |Objective: |AE delete request is allowed due to accessControlPolicy | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.15 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName}, and accessControlOperations with delete privilege and accessControlOriginators with privilege for - AE<br />AE has created a <container> resource on registrar CSE under <AE>, with name {containerName} and accessControlPolicyIDs including proper identifier of accessControlPolicy resource | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a container Delete Request for resource <container> | -|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{AE}/{containerName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | -|4 | |IOP Check |Check if possible that the <container> resource has been removed in registrar CSE | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -### 8.1.9 Group Management - -#### 8.1.9.1 Group Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_32 | -|Objective: |Objective: |Objective: |AE retrieves group resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <group> resource on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a group Retrieve Request | -|2 |<br />Mca |PRO Check Primitive |op = 2 (RETRIEVE)<br />to = {CSEBaseName}/{group}<br />fr = AE-ID<br />rqi = (token-string) | -|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <group> resource | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.9.2 Group Create - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_31 | -|Objective: |Objective: |Objective: |AE creates a group resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |void | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a group Create Request | -|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 9 (group)<br />pc = Serialized representation of <group> resource | -|3 | |IOP Check |Check if possible that the <group> resource is created in Registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <group> resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.9.3 Group Update - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_33 | -|Objective: |Objective: |Objective: |AE updates attribute in group resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.2.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <group> resource on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a group Update Request | -|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{group}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of <group> resource | -|3 | |IOP Check |Check if possible that the <group> resource is updated in Registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (CHANGED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <group> resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.9.4 Group Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_34 | -|Objective: |Objective: |Objective: |AE deletes group resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.2.5 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <group> resource on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a group Delete Request | -|2 |<br />Mca |PRO Check Primitive |op = 4 (DELETE)<br />to = {CSEBaseName}/{group}<br />fr = AE-ID<br />rqi = (token-string) | -|3 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message | -|4 | |IOP Check |Check if possible that the <group> resource is deleted in Registrar CSE | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -### 8.1.10 Node Management - -#### 8.1.10.1 Node Create - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_35 | -|Objective: |Objective: |Objective: |AE creates a node resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.18.2.1 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |void | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a node Create Request | -|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 14 (node)<br />pc = Serialized representation of <node> resource | -|3 | |IOP Check |Check if possible that the <node> resource is created in Registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <node> resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.10.2 Node Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_36 | -|Objective: |Objective: |Objective: |AE retrieves node resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.18.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <node> resource on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a node Retrieve Request | -|2 |<br />Mca |PRO Check Primitive |op = 2 (RETRIEVE)<br />to = {CSEBaseName}/{node}<br />fr = AE-ID<br />rqi = (token-string) | -|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <node> resource | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.10.3 Node Update - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_37 | -|Objective: |Objective: |Objective: |AE updates attribute in node resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.18.2.3 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <node> resource on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a node Update Request | -|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{node}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized - representation of <node> resource | -|3 | |IOP Check |Check if possible that the <node> resource is updated in Registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (CHANGED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <node> resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.10.4 Node Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_38 | -|Objective: |Objective: |Objective: |AE deletes node resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.18.2.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <node> resource on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a node Delete Request | -|2 |<br />Mca |PRO Check Primitive |op = 4 (DELETE)<br />to = {CSEBaseName}/{node}<br />fr = AE-ID<br />rqi = (token-string) | -|3 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message | -|4 | |IOP Check |Check if possible that the <node> resource is deleted in Registrar CSE | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -### 8.1.11 PollingChannel Management - -#### 8.1.11.1 PollingChannel Create - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_39 | -|Objective: |Objective: |Objective: |AE creates a <pollingChannel> resource in registrar CSE via a Create Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.5.13<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.21.2.1 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE sends a request to create a < pollingChannel > | -|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of <AE> resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 15 (pollingChannel)<br />pc = Serialized representation of < pollingChannel > resource | -|3 | |IOP Check |Check if possible that the < pollingChannel > resource is created in registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of < pollingChannel > resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.11.2 PollingChannel Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_40 | -|Objective: |Objective: |Objective: |AE retrieves information of a pollingChannel resource via a Retrieve Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.5.14<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.21.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource < pollingChannel > on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Retrieve Request for a < pollingChannel > | -|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of < pollingChannel > resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of < pollingChannel > resource | -|4 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.11.3 pollingChannel Update - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_41 | -|Objective: |Objective: |Objective: |AE updates attribute in pollingChannel resource via a Update Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.5.15<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.21.2.3 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a pollingChannel Update Request to update the lifetime of the resource | -|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/URI of < pollingChannel > resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated < pollingChannel > resource | -|3 | |IOP Check |Check if possible that the < pollingChannel > resource is updated in Registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of < pollingChannel > resource | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.11.4 pollingChannel Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_42 | -|Objective: |Objective: |Objective: |AE deletes a pollingChannel resource via a Delete Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.5.16<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.21.2.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a subscription Delete Request | -|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of < pollingChannel > resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | -|3 | |IOP Check |Check if possible that the < pollingChannel > resource is deleted in registrar CSE | -|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | -|5 | |IOP Check |Check if possible that the < pollingChannel > resource has been removed in registrar CSE | -|6 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.11.5 Long Polling on a PollingChannel Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_43 | -|Objective: |Objective: |Objective: |AE retrieves information of a pollingChannel resource via a Retrieve Request | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.5.18<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.22.2.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |A pollingChannel resource < pollingChannel > has been created in application <AE> on the Registrar CSE<br />A subscription to a <container> resource has been created using the <pollingChannel> as a notificationURI in the subscription<br />A single <contentInstance> resource is created in the subscribed to resource | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a pollingChannelURI Retrieve Request for <pollingChannelURI> | -|2 |<br />Mca |PRO Check Primitive |Sent RETRIEVE request contains:<br />To: <CSEBase>/<AE>/<pollingChannel>/pollingChannelURI<br />Fr: AE-ID | -|3 |<br />Mca |PRO Check Primitive |Sent RETRIEVE response contains:<br />To: AE-ID<br />Fr: CSE-ID<br />Response Status Code: OK<br />Cn: pending Notification request | -|4 | |IOP Check |AE indicates successful operation | -|5 | | |Repeat steps 1-2. There is no pending request. When the Request Expiration Timestamp expires Registrar sends response indicating "REQUEST_TIMEOUT" | -|6 |<br />Mca |PRO Check Primitive |Sent RETRIEVE response contains:<br />To: AE-ID<br - />Fr: CSE-ID<br />Response Status Code: REQUEST_TIMEOUT | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -### 8.1.12 FanoutPoint Management - -#### 8.1.12.1 FanoutPoint Create - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_44 | -|Objective: |Objective: |Objective: |AE creates a <contentInstance> resource in each group member | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.3.1 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |A group is created containing 2 members of type <container> | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Create Request to create <contentInstance> in each group member | -|2 |Check<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/{group}/fopt<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 4 (contentInstance)<br />pc = Serialized representation of <contentInstance> resource | -|3 | |IOP Check |Check if possible that the <contentInstance> resource is created in each member hosting CSE | -|4 |Check<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = aggregated response | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict |Verify that the aggregate response includes responses from each member of the group |Verify that the aggregate response includes responses from each member of the group | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.12.2 FanoutPoint Retrieve - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_45 | -|Objective: |Objective: |Objective: |AE retrieves the <container> resource from in each group member | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.7<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.3.2 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |A group is created containing 2 members of type <container> | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Retrieve Request to the fanoutPoint of <group> resource | -|2 |Check<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/{group}/fopt<br />fr = AE-ID<br />rqi = (token-string) | -|3 | |IOP Check | | -|4 |Check<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = aggregated response | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict |Verify that the aggregate response includes responses from each member of the group |Verify that the aggregate response includes responses from each member of the group | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.12.3 FanoutPoint Update - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_46 | -|Objective: |Objective: |Objective: |AE updates an <container> resource of each member resource | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.8<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.3.3 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |A group is created containing 2 members of type <container> | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Update Request to the fanoutPoint of <group> resource to lifetime of the resource | -|2 |Check<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{group}/fopt<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of <container> resource | -|3 | |IOP Check |Check if possible that both of the <container> resources have been updated in registrar CSE | -|4 |Check<br />Mca |PRO Check Primitive |rsc = 2004 (CHANGED)<br />rqi = (token-string) same as received in request message<br />pc = aggregated response | -|5 | |IOP Check |AE indicates successful operation | -|IOP Verdict |IOP Verdict |Verify that the aggregate response includes responses from each member of the group |Verify that the aggregate response includes responses from each member of the group | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.12.4 FanoutPoint Delete - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_47 | -|Objective: |Objective: |Objective: |AE deletes a <container> of each member | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.9<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.3.4 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |A group is created containing 2 members of type <container> | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE is requested to send a Delete 'oldest' Request to the fanoutPoint of <group> resource | -|2 |Check<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{group}/fopt<br />fr = AE-ID<br />rqi = (token-string) | -|3 |Check<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = aggregated response | -|4 | |Verify |Check if possible that the oldest <contentInstance> resource has been removed in registrar CSE | -|5 | |Verify |AE indicates successful operation | -|IOP Verdict |IOP Verdict |Verify that the aggregate response includes responses from each member of the group |Verify that the aggregate response includes responses from each member of the group | -|PRO Verdict |PRO Verdict | | | - - - - -### 8.1.13 Notification Management - -#### 8.1.13.1 Notification - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_48 | -|Objective: |Objective: |Objective: |AE receives a notification request from the HOST CSE | -|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.1 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE1 has created an application resource <AE> on registrar CSE<br />AE1 has created a container resource <container> on registrar CSE <br />AE1 has created a <subscription> as a child resource of a <container><br />AE2 has created an application resource <AE> on registrar CSE<br />AE2 has permissions to UPDATE the container created by AE1 | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE2 is requested to send a Update request to the <container> created by AE1. This triggers or causes the HOST CSE to send a notification to AE1 | -|2 |Check<br />Mca |PRO Check Primitive |op = 5 (Notify)<br />to = notificationURI of subscription resource<br />from = Registrar CSE-ID <br />rqi = (token-string)<br />pc = Serialized representation of Notification data object | -|3 | |IOP Check |Check if the notification representation | -|4 |Check<br />Mca |PRO Check Primitive |Sent response contains:<br />rsc = 2000 (OK)<br /> rqi = (token-string) same as received in request message | -|5 | |IOP Check |AE1 indicates notification received | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.13.2 Update Notification - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_80 | -|Objective: |Objective: |Objective: |AE2 sends maxNrOfInstances UPDATE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has specific setting in eventNotificationCriteria, Hosting CSE send notification to AE1 | -|Configuration: |Configuration: |Configuration: |M2M_CFG_10 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.19 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE1 has created a <container> resource on registrar CSE <br />AE1 has created <subscription> resources under the <container> resource. AE1 has set attribute of eventNotificationCriteria to a specific condition (e.g. maxNrOfInstances in this scenario) and notificationEventType set to 1(Update of Resource)<br />AE2 has permissions to UPDATE the <container> | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE2 is requested to - send a Update Request to the <container>. This triggers or causes the Hosting CSE to send a notification to AE1 | -|2 |Check<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = ID of <container> resource<br />from = AE2-ID<br />rqi = (token-string)<br />pc = Serialized representation of maxNrOfInstances update | -|3 | |IOP Check |Hosting CSE successfully updated mxNrOfInsatnce of the <container> resource | -|4 |Check<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource | -|5 | |IOP Check |AE2 successfully received response of Update request | -|6 |Check<br />Mca |PRO Check Primitive |op = 5 (Notify)<br />to = ID of <subscription> resource<br />from = Registrar CSE-ID <br />rqi = (token-string)<br />pc = Serialized representation of Notify request which contain notificationEventType equal to 1(Update of Resource) | -|7 | |IOP Check |AE1 successfully received Notify request | -|8 |Check<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message | -|9 | |IOP Check |Hosting CSE successfully received response of Notify request | -|10 |Check<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = ID of <container> resource<br />from = AE2-ID<br />rqi = (token-string)<br />pc = Serialized representation of labels update(can be any other attribute) | -|11 | |IOP Check |Hosting CSE successfully updated labels of the <container> resource | -|12 |Check<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource | -|13 | |IOP Check |AE2 successfully received response of Update request, notify request will not be sent | -|IOP Verdict |IOP Verdict |Check that the notification is only sent when there is update of maxNrOfInstances due to setting of the eventNotificationCriteria |Check that the notification is only sent when there is update of maxNrOfInstances due to setting of the eventNotificationCriteria | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.13.3 Delete Notification - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_81 | -|Objective: |Objective: |Objective: |AE2 sends DELETE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has notificationEventType with 'Delete of Resource', Hosting CSE send notification to AE1 | -|Configuration: |Configuration: |Configuration: |M2M_CFG_10 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.19 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE1 has created a <container> resource on registrar CSE <br />AE1 has created a <subscription> under the <container> resource, with notificationEventType set to 2(Delete of Resource)<br />AE2 has permissions to DELETE the <container> | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE2 is requested to send a Delete Request to the <container>. This triggers or causes the Hosting CSE to send a notification to AE1 | -|2 |Check<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = ID of <container> resource<br />fr = AE2-ID<br />rqi = (token-string)<br />pc = empty | -|3 | |IOP Check |Hosting CSE successfully deleted the <container> resource | -|4 |Check<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | -|5 | |IOP Check |AE2 successfully received response of Delete request | -|6 |Check<br />Mca |PRO Check Primitive |op = 5 (Notify)<br />to = ID of <subscription> resource<br />from = Registrar CSE-ID <br />rqi = (token-string)<br />pc = Serialized representation of Notify request which contain notificationEventType equal to 2(Delete of Resource) | -|7 | |IOP Check |AE1 successfully received Notify request | -|8 |Check<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message | -|9 | |IOP Check |Hosting CSE successfully received response of Notify request | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - - - - -#### 8.1.13.4 Creation of Direct Child Resource Notification - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_82 | -|Objective: |Objective: |Objective: |AE2 sends <contentInstance> CREATE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has notificationEventType with 'Create of Direct Child Resource', Hosting CSE send notification to AE1 | -|Configuration: |Configuration: |Configuration: |M2M_CFG_10 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.19 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE1 has created a <container> resource on registrar CSE <br />AE1 has created a <subscription> under the <container> resource, with notificationEventType set to 3(Create of Direct Child Resource)<br />AE2 has permissions to CREATE child resource under the <container> | -|Test Sequence |Test Sequence |Test Sequence |Test Sequence | -|Step |RP |Type |Description | -|1 | |Stimulus |AE2 is requested to send a Create Request of <contentInstance> resource to the <container> resource. This triggers or causes the Hosting CSE to send a notification to AE1 | -|2 |Check<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = ID of <container> resource<br />fr = AE2-ID<br />rqi = (token-string)<br />ty = 4 (contentInstance)<br />pc = Serialized representation of <contentInstance> resource | -|3 | |IOP Check |Hosting CSE successfully created the <contentInstance> resource under the <container> resource | -|4 |Check<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <contentInstance> resource | -|5 | |IOP Check |AE2 successfully received response of Create request | -|6 |Check<br />Mca |PRO Check Primitive |op = 5 (Notify)<br />to = ID of <subscription> resource<br />from = Registrar CSE-ID <br />rqi = (token-string)<br />pc = Serialized representation of Notify request which contain notificationEventType equal to 3(Create of Direct Child Resource) | -|7 | |IOP Check |AE1 successfully received Notify request | -|8 |Check<br />Mca |PRO Check Primitive |Sent response contains:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message | -|9 | |IOP Check |Hosting CSE successfully received response of Notify request | -|IOP Verdict |IOP Verdict | | | -|PRO Verdict |PRO Verdict | | | - -> - -#### 8.1.13.5 Deletion of Direct Child Resource Notification - -|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | -|-|-|-|-| -|Identifier: |Identifier: |Identifier: |TD_M2M_NH_83 | -|Objective: |Objective: |Objective: |AE2 sends DELETE request to the <contentInstance> which is located under the subscribed-to resource. Since <subscription> resource has notificationEventType with 'Delete of Direct Child Resource', Hosting CSE send notification to AE1 | -|Configuration: |Configuration: |Configuration: |M2M_CFG_10 | -|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.19 | -| | | | | -|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE1 has created a <container> resource on registrar CSE <br />AE1 has created a <contentInstance> as a child resource of <cont \ No newline at end of file +|| +|| + + + + +#### 8.1.8.4 accessControlPolicy Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_29 | +|Objective: |Objective: |Objective: |AE deletes accessControlPolicy resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.3.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.2.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send an accessControlPolicy delete request to Registrar CSE | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{AE}/{accessControlPolicyName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|4 | |IOP Check |Check if possible that the <accessControlPolicy> resource has been removed from registrar CSE. | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.8.5 Unauthorized operation (Insufficient Access Rights, operations) + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_30 | +|Objective: |Objective: |Objective: |AE delete request is rejected due to accessControlPolicy (accessControlOperations) | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.15 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName}, and accessControlOperations with no delete privilege<br />AE has created a <container> resource on registrar CSE under <AE>, with name {containerName} and accessControlPolicyIDs including proper identifier of accessControlPolicy resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a container Delete Request for resource <container> | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{AE}/{containerName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 4103 (ACCESS_DENIED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|4 | |IOP Check |Check if possible that the <container> resource has not been removed in registrar CSE | +|5 | |IOP Check |AE indicates unsuccessful operation (Delete error - no privilege) | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.8.6 Unauthorized operation (Insufficient Access Rights, originators) + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_73 | +|Objective: |Objective: |Objective: |AE delete request is rejected due to accessControlPolicy (accessControlOriginators) | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.15 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName}, and accessControlOriginators with no privilege for AE<br />AE has created a <container> resource on registrar CSE under <AE>, with name {containerName} and accessControlPolicyIDs including proper identifier of accessControlPolicy resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a container Delete Request for resource <container> | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{AE}/{containerName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 4103 (ACCESS_DENIED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|4 | |IOP Check |Check if possible that the <container> resource has not been removed in registrar CSE | +|5 | |IOP Check |AE indicates unsuccessful operation (Delete error - no privilege) | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.8.7 Authorized operation + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_74 | +|Objective: |Objective: |Objective: |AE delete request is allowed due to accessControlPolicy | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.15 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created a <AE> resource on registrar CSE with name {AE}<br />accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName}, and accessControlOperations with delete privilege and accessControlOriginators with privilege for AE<br />AE has created a <container> resource on registrar CSE under <AE>, with name {containerName} and accessControlPolicyIDs including proper identifier of accessControlPolicy resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a container Delete Request for resource <container> | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{AE}/{containerName}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|4 | |IOP Check |Check if possible that the <container> resource has been removed in registrar CSE | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.9 Group Management + +#### 8.1.9.1 Group Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_32 | +|Objective: |Objective: |Objective: |AE retrieves group resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <group> resource on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a group Retrieve Request | +|2 |<br />Mca |PRO Check Primitive |op = 2 (RETRIEVE)<br />to = {CSEBaseName}/{group}<br />fr = AE-ID<br />rqi = (token-string) | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <group> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.9.2 Group Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_31 | +|Objective: |Objective: |Objective: |AE creates a group resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |void | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a group Create Request | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 9 (group)<br />pc = Serialized representation of <group> resource | +|3 | |IOP Check |Check if possible that the <group> resource is created in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <group> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.9.3 Group Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_33 | +|Objective: |Objective: |Objective: |AE updates attribute in group resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <group> resource on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a group Update Request | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{group}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of <group> resource | +|3 | |IOP Check |Check if possible that the <group> resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (CHANGED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <group> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.9.4 Group Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_34 | +|Objective: |Objective: |Objective: |AE deletes group resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.2.5 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <group> resource on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a group Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (DELETE)<br />to = {CSEBaseName}/{group}<br />fr = AE-ID<br />rqi = (token-string) | +|3 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message | +|4 | |IOP Check |Check if possible that the <group> resource is deleted in Registrar CSE | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.10 Node Management + +#### 8.1.10.1 Node Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_35 | +|Objective: |Objective: |Objective: |AE creates a node resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.18.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |void | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a node Create Request | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 14 (node)<br />pc = Serialized representation of <node> resource | +|3 | |IOP Check |Check if possible that the <node> resource is created in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <node> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.10.2 Node Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_36 | +|Objective: |Objective: |Objective: |AE retrieves node resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.18.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <node> resource on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a node Retrieve Request | +|2 |<br />Mca |PRO Check Primitive |op = 2 (RETRIEVE)<br />to = {CSEBaseName}/{node}<br />fr = AE-ID<br />rqi = (token-string) | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <node> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.10.3 Node Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_37 | +|Objective: |Objective: |Objective: |AE updates attribute in node resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.18.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <node> resource on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a node Update Request | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{node}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of <node> resource | +|3 | |IOP Check |Check if possible that the <node> resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (CHANGED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <node> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.10.4 Node Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_38 | +|Objective: |Objective: |Objective: |AE deletes node resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.18.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <node> resource on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a node Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (DELETE)<br />to = {CSEBaseName}/{node}<br />fr = AE-ID<br />rqi = (token-string) | +|3 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message | +|4 | |IOP Check |Check if possible that the <node> resource is deleted in Registrar CSE | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.11 PollingChannel Management + +#### 8.1.11.1 PollingChannel Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_39 | +|Objective: |Objective: |Objective: |AE creates a <pollingChannel> resource in registrar CSE via a Create Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.5.13<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.21.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE sends a request to create a < pollingChannel > | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of <AE> resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 15 (pollingChannel)<br />pc = Serialized representation of < pollingChannel > resource | +|3 | |IOP Check |Check if possible that the < pollingChannel > resource is created in registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of < pollingChannel > resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.11.2 PollingChannel Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_40 | +|Objective: |Objective: |Objective: |AE retrieves information of a pollingChannel resource via a Retrieve Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.5.14<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.21.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource < pollingChannel > on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request for a < pollingChannel > | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of < pollingChannel > resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of < pollingChannel > resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.11.3 pollingChannel Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_41 | +|Objective: |Objective: |Objective: |AE updates attribute in pollingChannel resource via a Update Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.5.15<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.21.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a pollingChannel Update Request to update the lifetime of the resource | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/URI of < pollingChannel > resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated < pollingChannel > resource | +|3 | |IOP Check |Check if possible that the < pollingChannel > resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of < pollingChannel > resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.11.4 pollingChannel Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_42 | +|Objective: |Objective: |Objective: |AE deletes a pollingChannel resource via a Delete Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.5.16<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.21.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a subscription Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of < pollingChannel > resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Check if possible that the < pollingChannel > resource is deleted in registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |Check if possible that the < pollingChannel > resource has been removed in registrar CSE | +|6 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.11.5 Long Polling on a PollingChannel Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_43 | +|Objective: |Objective: |Objective: |AE retrieves information of a pollingChannel resource via a Retrieve Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.5.18<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.22.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |A pollingChannel resource < pollingChannel > has been created in application <AE> on the Registrar CSE<br />A subscription to a <container> resource has been created using the <pollingChannel> as a notificationURI in the subscription<br />A single <contentInstance> resource is created in the subscribed to resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a pollingChannelURI Retrieve Request for <pollingChannelURI> | +|2 |<br />Mca |PRO Check Primitive |Sent RETRIEVE request contains:<br />To: <CSEBase>/<AE>/<pollingChannel>/pollingChannelURI<br />Fr: AE-ID | +|3 |<br />Mca |PRO Check Primitive |Sent RETRIEVE response contains:<br />To: AE-ID<br />Fr: CSE-ID<br />Response Status Code: OK<br />Cn: pending Notification request | +|4 | |IOP Check |AE indicates successful operation | +|5 | | |Repeat steps 1-2. There is no pending request. When the Request Expiration Timestamp expires Registrar sends response indicating "REQUEST_TIMEOUT" | +|6 |<br />Mca |PRO Check Primitive |Sent RETRIEVE response contains:<br />To: AE-ID<br />Fr: CSE-ID<br />Response Status Code: REQUEST_TIMEOUT | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.12 FanoutPoint Management + +#### 8.1.12.1 FanoutPoint Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_44 | +|Objective: |Objective: |Objective: |AE creates a <contentInstance> resource in each group member | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.6<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.3.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |A group is created containing 2 members of type <container> | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Create Request to create <contentInstance> in each group member | +|2 |Check<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/{group}/fopt<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 4 (contentInstance)<br />pc = Serialized representation of <contentInstance> resource | +|3 | |IOP Check |Check if possible that the <contentInstance> resource is created in each member hosting CSE | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = aggregated response | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict |Verify that the aggregate response includes responses from each member of the group |Verify that the aggregate response includes responses from each member of the group | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.12.2 FanoutPoint Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_45 | +|Objective: |Objective: |Objective: |AE retrieves the <container> resource from in each group member | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.7<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.3.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |A group is created containing 2 members of type <container> | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request to the fanoutPoint of <group> resource | +|2 |Check<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/{group}/fopt<br />fr = AE-ID<br />rqi = (token-string) | +|3 | |IOP Check | | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = aggregated response | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict |Verify that the aggregate response includes responses from each member of the group |Verify that the aggregate response includes responses from each member of the group | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.12.3 FanoutPoint Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_46 | +|Objective: |Objective: |Objective: |AE updates an <container> resource of each member resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.8<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.3.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |A group is created containing 2 members of type <container> | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Update Request to the fanoutPoint of <group> resource to lifetime of the resource | +|2 |Check<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{group}/fopt<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of <container> resource | +|3 | |IOP Check |Check if possible that both of the <container> resources have been updated in registrar CSE | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2004 (CHANGED)<br />rqi = (token-string) same as received in request message<br />pc = aggregated response | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict |Verify that the aggregate response includes responses from each member of the group |Verify that the aggregate response includes responses from each member of the group | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.12.4 FanoutPoint Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_47 | +|Objective: |Objective: |Objective: |AE deletes a <container> of each member | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.9<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.3.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |A group is created containing 2 members of type <container> | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Delete 'oldest' Request to the fanoutPoint of <group> resource | +|2 |Check<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/{group}/fopt<br />fr = AE-ID<br />rqi = (token-string) | +|3 |Check<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = aggregated response | +|4 | |Verify |Check if possible that the oldest <contentInstance> resource has been removed in registrar CSE | +|5 | |Verify |AE indicates successful operation | +|IOP Verdict |IOP Verdict |Verify that the aggregate response includes responses from each member of the group |Verify that the aggregate response includes responses from each member of the group | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.13 Notification Management + +#### 8.1.13.1 Notification + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_48 | +|Objective: |Objective: |Objective: |AE receives a notification request from the HOST CSE | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE1 has created an application resource <AE> on registrar CSE<br />AE1 has created a container resource <container> on registrar CSE <br />AE1 has created a <subscription> as a child resource of a <container><br />AE2 has created an application resource <AE> on registrar CSE<br />AE2 has permissions to UPDATE the container created by AE1 | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE2 is requested to send a Update request to the <container> created by AE1. This triggers or causes the HOST CSE to send a notification to AE1 | +|2 |Check<br />Mca |PRO Check Primitive |op = 5 (Notify)<br />to = notificationURI of subscription resource<br />from = Registrar CSE-ID <br />rqi = (token-string)<br />pc = Serialized representation of Notification data object | +|3 | |IOP Check |Check if the notification representation | +|4 |Check<br />Mca |PRO Check Primitive |Sent response contains:<br />rsc = 2000 (OK)<br /> rqi = (token-string) same as received in request message | +|5 | |IOP Check |AE1 indicates notification received | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.13.2 Update Notification + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_80 | +|Objective: |Objective: |Objective: |AE2 sends maxNrOfInstances UPDATE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has specific setting in eventNotificationCriteria, Hosting CSE send notification to AE1 | +|Configuration: |Configuration: |Configuration: |M2M_CFG_10 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.19 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE1 has created a <container> resource on registrar CSE <br />AE1 has created <subscription> resources under the <container> resource. AE1 has set attribute of eventNotificationCriteria to a specific condition (e.g. maxNrOfInstances in this scenario) and notificationEventType set to 1(Update of Resource)<br />AE2 has permissions to UPDATE the <container> | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE2 is requested to send a Update Request to the <container>. This triggers or causes the Hosting CSE to send a notification to AE1 | +|2 |Check<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = ID of <container> resource<br />from = AE2-ID<br />rqi = (token-string)<br />pc = Serialized representation of maxNrOfInstances update | +|3 | |IOP Check |Hosting CSE successfully updated mxNrOfInsatnce of the <container> resource | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource | +|5 | |IOP Check |AE2 successfully received response of Update request | +|6 |Check<br />Mca |PRO Check Primitive |op = 5 (Notify)<br />to = ID of <subscription> resource<br />from = Registrar CSE-ID <br />rqi = (token-string)<br />pc = Serialized representation of Notify request which contain notificationEventType equal to 1(Update of Resource) | +|7 | |IOP Check |AE1 successfully received Notify request | +|8 |Check<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message | +|9 | |IOP Check |Hosting CSE successfully received response of Notify request | +|10 |Check<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = ID of <container> resource<br />from = AE2-ID<br />rqi = (token-string)<br />pc = Serialized representation of labels update(can be any other attribute) | +|11 | |IOP Check |Hosting CSE successfully updated labels of the <container> resource | +|12 |Check<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource | +|13 | |IOP Check |AE2 successfully received response of Update request, notify request will not be sent | +|IOP Verdict |IOP Verdict |Check that the notification is only sent when there is update of maxNrOfInstances due to setting of the eventNotificationCriteria |Check that the notification is only sent when there is update of maxNrOfInstances due to setting of the eventNotificationCriteria | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.13.3 Delete Notification + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_81 | +|Objective: |Objective: |Objective: |AE2 sends DELETE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has notificationEventType with 'Delete of Resource', Hosting CSE send notification to AE1 | +|Configuration: |Configuration: |Configuration: |M2M_CFG_10 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.19 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE1 has created a <container> resource on registrar CSE <br />AE1 has created a <subscription> under the <container> resource, with notificationEventType set to 2(Delete of Resource)<br />AE2 has permissions to DELETE the <container> | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE2 is requested to send a Delete Request to the <container>. This triggers or causes the Hosting CSE to send a notification to AE1 | +|2 |Check<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = ID of <container> resource<br />fr = AE2-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Hosting CSE successfully deleted the <container> resource | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |AE2 successfully received response of Delete request | +|6 |Check<br />Mca |PRO Check Primitive |op = 5 (Notify)<br />to = ID of <subscription> resource<br />from = Registrar CSE-ID <br />rqi = (token-string)<br />pc = Serialized representation of Notify request which contain notificationEventType equal to 2(Delete of Resource) | +|7 | |IOP Check |AE1 successfully received Notify request | +|8 |Check<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message | +|9 | |IOP Check |Hosting CSE successfully received response of Notify request | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.13.4 Creation of Direct Child Resource Notification + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_82 | +|Objective: |Objective: |Objective: |AE2 sends <contentInstance> CREATE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has notificationEventType with 'Create of Direct Child Resource', Hosting CSE send notification to AE1 | +|Configuration: |Configuration: |Configuration: |M2M_CFG_10 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.19 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE1 has created a <container> resource on registrar CSE <br />AE1 has created a <subscription> under the <container> resource, with notificationEventType set to 3(Create of Direct Child Resource)<br />AE2 has permissions to CREATE child resource under the <container> | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE2 is requested to send a Create Request of <contentInstance> resource to the <container> resource. This triggers or causes the Hosting CSE to send a notification to AE1 | +|2 |Check<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = ID of <container> resource<br />fr = AE2-ID<br />rqi = (token-string)<br />ty = 4 (contentInstance)<br />pc = Serialized representation of <contentInstance> resource | +|3 | |IOP Check |Hosting CSE successfully created the <contentInstance> resource under the <container> resource | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <contentInstance> resource | +|5 | |IOP Check |AE2 successfully received response of Create request | +|6 |Check<br />Mca |PRO Check Primitive |op = 5 (Notify)<br />to = ID of <subscription> resource<br />from = Registrar CSE-ID <br />rqi = (token-string)<br />pc = Serialized representation of Notify request which contain notificationEventType equal to 3(Create of Direct Child Resource) | +|7 | |IOP Check |AE1 successfully received Notify request | +|8 |Check<br />Mca |PRO Check Primitive |Sent response contains:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message | +|9 | |IOP Check |Hosting CSE successfully received response of Notify request | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + +> + +#### 8.1.13.5 Deletion of Direct Child Resource Notification + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_83 | +|Objective: |Objective: |Objective: |AE2 sends DELETE request to the <contentInstance> which is located under the subscribed-to resource. Since <subscription> resource has notificationEventType with 'Delete of Direct Child Resource', Hosting CSE send notification to AE1 | +|Configuration: |Configuration: |Configuration: |M2M_CFG_10 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.19 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE1 has created a <container> resource on registrar CSE <br />AE1 has created a <contentInstance> as a child resource of <container> created by AE1<br />AE1 has created a <subscription> under the <container> resource, with notificationEventType set to 4(Delete of Direct Child Resource)<br />AE2 has permissions to DELETE the <contentInstance> | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE2 is requested to send a Delete Request to the <contentinstance>. This triggers or causes the Hosting CSE to send a notification to AE1 | +|2 |Check<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = ID of <contentInstance> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Hosting CSE successfully deleted the <contentInstance> resource | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |AE2 successfully received response of Delete request | +|6 |Check<br />Mca |PRO Check Primitive |op = 5 (Notify)<br />to = ID of <subscription> resource<br />from = Registrar CSE-ID <br />rqi = (token-string)<br />pc = Serialized representation of Notify request which contain notificationEventType equal to 4(Delete of Direct Child Resource) | +|7 | |IOP Check |AE1 successfully received Notify request | +|8 |Check<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message | +|9 | |IOP Check |Hosting CSE successfully received response of Notify request | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + + +#### 8.1.13.6 Notifcation Aggregation + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_89 | +|Objective: |Objective: |Objective: |AE creates <subscription> resources by sending Create Request to the fanOutPoint. <br />Since AE has set notifyAggregation to 2, Hosting CSE aggregate notification and send aggregated notification to AE | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.7.11<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.14.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in registrar CSE with name {CSEBaseName}<br />AE has created two <container> resources on registrar CSE<br />AE has created a <group> resource with memberIDs set to two <container> resources. AE has set number in notifyAggregation to 2<br />AE has created <subscription> resources under the members of <group> resources by sending Create Request to the fanOutPoint. AE has set notificationForwardingURI and notificationEventType set to 3(Create of Direct Child Resource) | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Create Request of <contentInstance> resource to the fanOutPoint | +|2 |Check<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/{group}/fopt<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 4 (contentInstance)<br />pc = Serialized representation of <subscription> resource | +|3 | |IOP Check |Hosting CSE successfully created the <contentInstance> resources in each member | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = aggregated response | +|5 | |IOP Check |AE successfully received converged response | +|6 |Check<br />Mca |PRO Check Primitive |op = 5 (Notify)<br />to = ID of <subscription> resource<br />from = Registrar CSE-ID <br />rqi = (token-string)<br />pc = aggregated Notify request which contain the occurrence of child resource creation | +|7 | |IOP Check |AE successfully received aggregated Notify request | +|8 |Check<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message | +|9 | |IOP Check |Group Hosting CSE successfully received response of Notify request | +|IOP Verdict |IOP Verdict |Check that the response is aggregated by the group Hosting CSE and successfully parse to AE |Check that the response is aggregated by the group Hosting CSE and successfully parse to AE | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.14 FlexContainer Management + +#### 8.1.14.1 FlexContainer Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_52 | +|Objective: |Objective: |Objective: |AE creates a flexContainer resource in Registrar CSE via a flexContainer Create Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.16, 9.6.35<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.37.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on Registrar CSE | +| | | | | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE sends a request to create a <flexContainer> | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 28 (flexContainer)<br />pc = Serialized representation of <flexContainer> resource | +|3 | |IOP Check |Check if possible that the <flexContainer> resource is created in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <flexContainer> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.14.2 FlexContainer Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_53 | +|Objective: |Objective: |Objective: |AE retrieves information of a flexContainer resource via a flexContainer Retrieve Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clauses 10.2.4.17, 9.6.35<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.37.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a flexContainer resource <flexContainer> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request for a <flexContainer> | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <flexContainer> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <flexContainer> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.14.3 FlexContainer Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_54 | +|Objective: |Objective: |Objective: |AE updates attribute in application resource via a flexContainer Update Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clauses 10.2.4.18, 9.6.35<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.37.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a flexContainer resource <flexContainer> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a flexContainer Update Request to update the any customAttribute of the resource | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/URI of <flexContainer> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <flexContainer> resource | +|3 | |IOP Check |Check if possible that the < flexContainer > resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <flexContainer> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.14.4 FlexContainer Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_55 | +|Objective: |Objective: |Objective: |AE deletes a specific container resource via a container Delete Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clauses 10.2.4.19, 9.6.35<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.37.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a flexContainer resource <flexContainer> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a flexContainer Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <flexContainer> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Check if possible that the <flexContainer> resource is deleted in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |Check if possible that the <flexContainer> resource has been removed in Registrar CSE | +|6 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.14.5 Notification Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_56 | +|Objective: |Objective: |Objective: |AE receives a notification request on flexContainer update from the HOST CSE | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clauses 10.2.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE1 has created an application resource <AE> on Registrar CSE<br />AE1 has created a flexContainer resource <flexContainer> on Registrar CSE <br />AE1 has created a <subscription> as a child resource of a <flexContainer><br />AE2 has created an application resource <AE> on Registrar CSE<br />AE2 has permissions to UPDATE customAttributes of flexContainer | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE2 is requested to send a update request to <flexContainer> for updating customAttribute. This triggers or causes the HOST CSE to send a notification to AE1 | +|2 |Check<br />Mca |PRO Check Primitive |op = 5 (Notify)<br />to = notificationURI of subscription resource<br />from = Registrar CSE-ID <br />rqi = (token-string)<br />pc = Serialized representation of Notification data object | +|3 | |IOP Check |Check if the notification representation | +|4 |Check<br />Mca |PRO Check Primitive |Sent response contains:<br />rsc = 2000 (OK)<br /> rqi = (token-string) same as received in request message | +|5 | |IOP Check |AE1 indicates notification received | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.14.6 Discovery with attribute filter criteria over customAttributes + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_57 | +|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using attribute filter criteria which has a customAttribute name and value assigned to it. | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clauses 10.2.10 <br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.14 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a flexContainer resource <flexContainer> on Registrar CSE with customAttribute set to a specific value "x", created on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Discovery request in order to discover the <Container> resource using attribute filter criteria | +|2 |<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />fu=1<br />atr=<nm>,<val><br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |Registrar CSE sends response containing:<br />rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the address of the <flexContainer> address | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.15 External Management Operations Management + +#### 8.1.15.1 mgmtCmd Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_63 | +|Objective: |Objective: |Objective: |AE creates a mgmtCmd resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.8<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.16.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on Registrar CSE<br />AE has created a node resource <node> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a mgmtCmd Create Request | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 12 (mgmtCmd)<br />pc = Serialized representation of <mgmtCmd> resource | +|3 | |IOP Check |Check if possible that the <mgmtCmd> resource is created in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <mgmtCmd> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict |Set verdict to pass if IOP check goal is achieved exactly, otherwise verdict fail is set with corresponding error message. |Set verdict to pass if IOP check goal is achieved exactly, otherwise verdict fail is set with corresponding error message. | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.15.2 mgmtCmd Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_64 | +|Objective: |Objective: |Objective: |AE retrieves mgmtCmd resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.9<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.16.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on Registrar CSE<br />AE has created a node resource <node> on Registrar CSE<br />AE has created a mgmtCmd resource <mgmtCmd> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a mgmtCmd Retrieve Request | +|2 |<br />Mca |PRO Check Primitive |op = 2 (RETRIEVE)<br />to = {CSEBaseName}/{mgmtCmd}<br />fr = AE-ID<br />rqi = (token-string) | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <mgmtCmd> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.15.3 mgmtCmd Update (Normal) + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_65 | +|Objective: |Objective: |Objective: |AE updates attribute (not with 'true' in execEnable attribute) in mgmtCmd resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.10<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.16.2.3.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on Registrar CSE<br />AE has created a node resource <node> on Registrar CSE<br />AE has created a mgmtCmd resource <mgmtCmd> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a mgmtCmd Update Request | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{mgmtCmd}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of <mgmtCmd> resource | +|3 | |IOP Check |Check if possible that the <mgmtCmd> resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (UPDATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <mgmtCmd> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.15.4 mgmtCmd Update (Execute) + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_66 | +|Objective: |Objective: |Objective: |AE updates attribute (with 'true' in execEnable attribute) in mgmtCmd resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.12<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.16.2.3.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on Registrar CSE<br />AE has created a node resource <node> on Registrar CSE<br />AE has created a mgmtCmd resource <mgmtCmd> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a mgmtCmd Update Request | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{mgmtCmd}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of <mgmtCmd> resource | +|3 | |IOP Check |Check if possible that the <mgmtCmd> resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (UPDATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <mgmtCmd> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.15.5 mgmtCmd Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_67 | +|Objective: |Objective: |Objective: |AE deletes mgmtCmd resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.11<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.16.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on Registrar CSE<br />AE has created a node resource <node> on Registrar CSE<br />AE has created a mgmtCmd resource <mgmtCmd> on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a mgmtCmd Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (DELETE)<br />to = {CSEBaseName}/{mgmtCmd}<br />fr = AE-ID<br />rqi = (token-string) | +|3 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message | +|4 | |IOP Check |Check if possible that the <mgmtCmd> resource is deleted in Registrar CSE | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.15.6 execInstance Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_68 | +|Objective: |Objective: |Objective: |AE retrieves execInstance resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.20<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.17.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on Registrar CSE<br />AE has created a node resource <node> on Registrar CSE<br />AE has created a mgmtCmd resource <mgmtCmd> on Registrar CSE<br />AE has executed the mgmtCmd resource <mgmtCmd> on Registrar CSE (update execEnable attribute with 'true') | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a execInstance Retrieve Request | +|2 |<br />Mca |PRO Check Primitive |op = 2 (RETRIEVE)<br />to = {CSEBaseName}/{mgmtCmd}/{execInstance}<br />fr = AE-ID<br />rqi = (token-string) | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <execInstance> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.15.7 execInstance Update (Cancel) + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_69 | +|Objective: |Objective: |Objective: |AE updates attribute 'execDisable' to true in execInstance resource to cancel pending management command. | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.19<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.17.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on Registrar CSE<br />AE has created a node resource <node> on Registrar CSE<br />AE has created a mgmtCmd resource <mgmtCmd> on Registrar CSE<br />AE has executed the mgmtCmd resource <mgmtCmd> on Registrar CSE (update execEnable attribute with 'true') | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a execInstance Update Request | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/{mgmtCmd}/{execInstance}<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of <execInstance> resource | +|3 | |IOP Check |Check if possible that the <execInstance> resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (UPDATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <execInstance> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.15.8 execInstance Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_70 | +|Objective: |Objective: |Objective: |AE deletes execInstance resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.8.21<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.17.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on Registrar CSE<br />AE has created a node resource <node> on Registrar CSE<br />AE has created a mgmtCmd resource <mgmtCmd> on Registrar CSE<br />AE has executed the mgmtCmd resource <mgmtCmd> on Registrar CSE (update execEnable attribute with 'true') | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a execInstance Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (DELETE)<br />to = {CSEBaseName}/{mgmtCmd}/{execInstance}<br />fr = AE-ID<br />rqi = (token-string) | +|3 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message | +|4 | |IOP Check |Check if possible that the <execInstance> resource is deleted in Registrar CSE | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.16 SemanticDescriptor Management + +#### 8.1.16.1 SemanticDescriptor Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_75 | +|Objective: |Objective: |Objective: |AE creates a SemanticDescriptor resource in Registrar CSE via a SemanticDescriptor Create Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0034 <a href="#_ref_13">[13]</a>, clause 6.1.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.34.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE | +| | | | | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE sends a request to create a <semanticDescriptor> | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of < container > resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 24 (semanticDescriptor)<br />pc = Serialized representation of <semanticDescriptor> resource | +|3 | |IOP Check |Check if possible that the <semanticDescriptor> resource is created in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <semanticDescriptor> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.16.2 SemanticDescriptor Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_76 | +|Objective: |Objective: |Objective: |AE retrieves information of a semanticDescriptor resource via a semanticDescriptor Retrieve Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0034 <a href="#_ref_13">[13]</a>, clause 6.1.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.34.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a semanticDescriptor resource <semanticDescriptor> as child resource of <AE> resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request for a <semanticDescriptor> | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <semanticDescriptor> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <semanticDescriptor> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.16.3 SemanticDescriptor Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_77 | +|Objective: |Objective: |Objective: |AE updates attribute in <semanticDescriptor> resource via a semanticDescriptor Update Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0034 <a href="#_ref_13">[13]</a>, clause 6.1.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.34.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a semanticDescriptor resource <semanticDescriptor> as child resource of <AE> resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a semanticDescriptor Update Request to update the descriptor attribute of the resource | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/URI of <semanticDescriptor> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <semanticDescriptor> resource | +|3 | |IOP Check |Check if possible that the <semanticDescriptor> resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <semanticDescriptor> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.16.4 SemanticDescriptor Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_78 | +|Objective: |Objective: |Objective: |AE deletes SemanticDescriptor resource via a SemanticDescriptor Delete Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0034 <a href="#_ref_13">[13]</a>, clause 6.1.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.34.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a semanticDescriptor resource <semanticDescriptor> as child of <AE> resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a semanticDescriptor Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <semanticDescriptor> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Check if possible that the <semanticDescriptor> resource is deleted in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |Check if possible that the <semanticDescriptor> resource has been removed in Registrar CSE | +|6 | |IOP Check |AE indicates successful operation. | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.17 Semantic Resource Discovery + +#### 8.1.17.1 Discovery with semanticFilter filter criteria + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_79 | +|Objective: |Objective: |Objective: |AE discovers accessible resources residing in Registrar CSE using the semanticFilter filter criteria | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0034 <a href="#_ref_13">[13]</a>, clause 7.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.3.3.18 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE1 has created an application resource <AE> on Registrar CSE<br />AE1 has created a container resource <container> on Registrar CSE <br />AE1 has created a <semanticDescriptor> as a child resource of a <container> | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE1 is requested to send a Discovery request to discover the <container> resource using the semanticFilter filterCriteria | +|2 |Check<br />Mca |PRO Check Primitive |Sent request contains:<br />op = 2 (Retrieve)<br />to = {CSEBaseName}<br />from = AE-ID<br />rqi = (token-string)<br />fu=1<br />smf=sparqlQuery1<br />pc = empty | +|3 |Check<br />Mca |PRO Check Primitive |Sent response contains:<br />rsc = 2000 (OK)<br /> rqi = (token-string) same as received in request message<br />pc = Serialized representation of data object containing the <Container> address | +|4 | |IOP Check |AE1 indicates notification received | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.18 ResultContent + +#### 8.1.18.1 ResultContent=0 + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_84 | +|Objective: |Objective: |Objective: |Check creation of <container> resource with result content set to 0(nothing) | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.7 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in CSE with name {CSEBaseName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a <container> resource Create Request to the Registrar CSE with rcn=0 | +|2 |Check<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 3 (container)<br />rcn = 0<br />pc = Serialized representation of <container> resource which contain {containerName} as a rn | +|3 | |IOP Check |Hosting CSE successfully created the <container> resource | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message | +|5 | |IOP Check |AE successfully received response of Create request | +|IOP Verdict |IOP Verdict |Check that the response body does not include any message |Check that the response body does not include any message | +|PRO Verdict |PRO Verdict | | | + +> + +#### 8.1.18.2 ResultContent=1 + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_85 | +|Objective: |Objective: |Objective: |Check creation of <container> resource with result content set to 1(attributes) | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.7 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in CSE with name {CSEBaseName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a <container> resource Create Request to the Registrar CSE with rcn=1 | +|2 |Check<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 3 (container)<br />rcn = 1<br />pc = Serialized representation of <container> resource | +|3 | |IOP Check |Hosting CSE successfully created the <container> resource | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource which contain attributes | +|5 | |IOP Check |AE successfully received response of Create request | +|IOP Verdict |IOP Verdict |Check that the response body include attributes |Check that the response body include attributes | +|PRO Verdict |PRO Verdict | | | + +> + +#### 8.1.18.3 ResultContent=2 + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_86 | +|Objective: |Objective: |Objective: |Check creation of <container> resource with result content set to 2(hierarchical address) | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.7 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in CSE with name {CSEBaseName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a <container> resource Create Request to the Registrar CSE with rcn = 2 | +|2 |Check<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 3 (container)<br />rcn = 2<br />pc = Serialized representation of <container> resource | +|3 | |IOP Check |Hosting CSE successfully created the <container> resource | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Hierarchical address of <container> resource | +|5 | |IOP Check |AE successfully received response of Create request | +|IOP Verdict |IOP Verdict |Check that the response body include hierarchical address |Check that the response body include hierarchical address | +|PRO Verdict |PRO Verdict | | | + +> + +#### 8.1.18.4 ResultContent=3 + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_87 | +|Objective: |Objective: |Objective: |Check creation of <container> resource with result content set to 3(hierarchical address and attributes) | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.7 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in CSE with name {CSEBaseName} | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a <container> Create Request to the Registrar CSE with rcn=3 | +|2 |Check<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 3 (container)<br />rcn = 3<br />pc = Serialized representation of <container> resource | +|3 | |IOP Check |Hosting CSE successfully created the <container> resource | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> resource with hierarchical address | +|5 | |IOP Check |AE successfully received response of Create request | +|IOP Verdict |IOP Verdict |Check that the response body include hierarchical address and attributes |Check that the response body include hierarchical address and attributes | +|PRO Verdict |PRO Verdict | | | + +> + +#### 8.1.18.5 ResultContent=4 + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_88 | +|Objective: |Objective: |Objective: |Check retrievability of <container> resource with result content set to 4 (attributes and child resources) | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 8.1.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 6.3.4.2.7 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |CSEBase resource has been created in CSE with name {CSEBaseName}<br />AE has created a <container> resource on registrar CSE<br />AE has created two <contentInstance> resources under the <container> resources | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a <container> Retrieve Request to the Registrar CSE with rcn=4 | +|2 |Check<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = ID of <container> resource<br />fr = AE-ID<br />rqi = (token-string)<br />rcn = 4 | +|3 | |IOP Check |Hosting CSE successfully received Retrieve request of the <container> resource | +|4 |Check<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <container> and child resources | +|5 | |IOP Check |AE successfully received response of Retrieve request | +|IOP Verdict |IOP Verdict |Check that the response body include attributes and child resources |Check that the response body include attributes and child resources | +|PRO Verdict |PRO Verdict | | | + + + + + +### 8.1.19 timeSeries Management + +#### 8.1.19.1 timeSeries Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_90 | +|Objective: |Objective: |Objective: |AE creates a <timeSeries> resource in registrar CSE via a Create Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.21<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.38.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <AE> resource on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Create Request of the <timeSeries> resource | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of <AE> resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 29 (timeSeries)<br />pc = Serialized representation of <timeSeries> resource | +|3 | |IOP Check |Registrar CSE successfully created the <timeSeries> resource | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <timeSeries> resource | +|5 | |IOP Check |AE successfully received response of Create Request | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.19.2 timeSeries Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_91 | +|Objective: |Objective: |Objective: |AE retrieves information of a <timeSeries> resource via a Retrieve Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.22<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.38.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <AE> resource on Registrar CSE<br />AE has created a <timeSereis> resource on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request of the <timeSeries> resource | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <timeSeries> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Registrar CSE successfully received Retrieve Request of the <timeSeries> resource | +|4 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <timeSeries> resource | +|5 | |IOP Check |AE successfully received response of Retrieve Request | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.19.3 timeSeries Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_92 | +|Objective: |Objective: |Objective: |AE updates attribute in <timeSeries> resource via a Update Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.23<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.38.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <AE> resource on Registrar CSE<br />AE has created a <timeSereis> resource on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Update Request to the <timeSeries> resource to update the maxNrOfInstances | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/URI of <timeSeries> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of maxNrOfInstances update(can be any other attribute) | +|3 | |IOP Check |Registrar CSE successfully updated the maxNrOfInstances of the <timeSeries> resource | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <timeSeries> resource | +|5 | |IOP Check |AE successfully received response of Update Request | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.19.4 timeSeries Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_93 | +|Objective: |Objective: |Objective: |AE deletes a <timeSeries> resource via a Delete Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.24<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.38.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <AE> resource on Registrar CSE<br />AE has created a <timeSeries> resource on Registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Delete Request of the <timeSeries> resource | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <timeSeries> resource <br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Registrar CSE successfully deleted the <timeSeries> resource | +|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |AE successfully received response of Delete Request | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.20 timeSeriesInstance Management + +#### 8.1.20.1 timeSeriesInstance Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_94 | +|Objective: |Objective: |Objective: |AE sends Create Request of a <timeSeriesInstance> resource to a <timeSeries> resource in Registrar CSE. Registrar CSE creates the <timeSeriesInstance> resource and updates the parent <timeSeries> resource with currentNrOfInstances and currentByteSize attributes correspondingly | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.25<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.39.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <AE> resource on Registrar CSE<br />AE has created a <timeSeries> resource on registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Create Request of the <timeSeriesInstance> resource | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of <timeSeries> resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 30 (timeSeriesInstance)<br />pc = Serialized representation of <timeSeriesInstance> resource | +|3 | |IOP Check |Registrar CSE successfully created <timeSeriesInstance> resource and updated currentNrOfInstances and currentByteSize of the <timeSeries> resource | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <timeSeriesInstance> resource | +|5 | |IOP Check |AE successfully received response of Create Request | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.20.2 timeSeriesInstance Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_95 | +|Objective: |Objective: |Objective: |AE retrieves information of a <timeSeriesInstance> resource via a Retrieve Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.26<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.39.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <AE> resource on Registrar CSE <br />AE has created a <timeSeries> resource on registrar CSE<br />AE has created a <timeSeriesInstance> resource as child resource of the <timeSeries> resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request for a <timeSeriesInstance> resource | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <timeSeriesInstance> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Registrar CSE successfully received Retrieve Request of the <timeSeriesInstance> resource | +|4 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <timeSeriesInstance> resource | +|5 | |IOP Check |AE successfully received response of Retrieve Request | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.20.3 timeSeriesInstance Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_96 | +|Objective: |Objective: |Objective: |AE sends Delete Request of a <timeSeriesInstance> resource in Registrar CSE. Registrar CSE delete the <timeSeriesInstance> resource and updates the parent <timeSeries> resource with currentNrOfInstances and currentByteSize attributes correspondingly | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.28<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.39.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <AE> resource on Registrar CSE <br />AE has created a <timeSeries> resource on registrar CSE<br />AE has created a <timeSeriesInstance> resource as child resource of the <timeSeries> resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Delete Requeest a <timeSeriesInstance> resource | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <timeSeriesInstance> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Registrar CSE successfully deleted <timeSeriesInstance> resource and updated currentNrOfInstances and currentByteSize of the <timeSeries> resource | +|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |AE successfully received response of Delete Request | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.20.4 timeSeriesInstance Create when currentNrOfInstance equals to maxNrOfInstances in parent <timeSeries> resource + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_97 | +|Objective: |Objective: |Objective: |AE sends a <timeSeriesInstance> resource Create Request to a <timeSeries> resource which contains currentNrOfInstances value equals to that of maxNrOfInstances and Registrar CSE deletes the oldest <timeSeriesInstance> resource from the <timeSeries> resource and then creates the requested <timeSeriesInstance> resource | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.4.25<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.38.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created a <AE> resource on Registrar CSE <br />AE has created a <timeSeries> resource on registrar CSE<br />AE has created several <timeSeriesInstance> resources and currentNrOfInstances of the <timeSeries> resource reach the maxNrOfInstances | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Create Request of the <timeSeriesInstance> resource | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}/URI of <timeSeries> resource<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 30 (timeSeriesInstance)<br />pc = Serialized representation of <timeSeriesInstance> resource | +|3 | |IOP Check |Registrar CSE successfully deleted <timeSeriesInstance> resource with the oldest dataGenerationTime and created <timeSeriesInstance> resource | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <timeSeriesInstance> resource | +|5 | |IOP Check |AE successfully received response of Create Request | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.21 Location Management + +#### 8.1.21.1 LocationPolicy Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_98 | +|Objective: |Objective: |Objective: |AE creates a <locationPolicy> resource in registrar CSE via a locationPolicy Create Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.9.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.10.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on registrar CSE | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE sends a request to create a <locationPolicy> | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 10 (LocationPolicy)<br />pc = Serialized representation of <locationPolicy> resource | +|3 | |IOP Check |Check if possible that the <locationPolicy> resource is created in registrar CSE<br />Check if possible that the <container> resource is created on registrar CSE having its resourceID and locationID attribute set to locationContainerID and resourceID attribute of the <locationPolicy> resource respectively | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <locationPolicy> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.21.2 LocationPolicy Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_99 | +|Objective: |Objective: |Objective: |AE retrieves information of a <locationPolicy> resource via a locationPolicy Retrieve Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.9.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.10.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a locationPolicy resource <locationPolicy> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE having its resourceID and locationID attribute set to locationContainerID and resourceID attribute of the <locationPolicy> resource respectively | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request for a <locationPolicy> | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <locationPolicy> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <locationPolicy> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.21.3 LocationPolicy Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_100 | +|Objective: |Objective: |Objective: |AE updates attribute in <locationPolicy> resource via a locationPolicy Update Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.9.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.10.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a locationPolicy resource <locationPolicy> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE having its resourceID and locationID attribute set to locationContainerID and resourceID attribute of the <locationPolicy> resource respectively | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a locationPolicy Update Request to update the lifetime of the resource | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/URI of <locationPolicy> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <locationPolicy> resource | +|3 | |IOP Check |Check if possible that the < locationPolicy > resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <locationPolicy> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.21.4 LocationPolicy Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_101 | +|Objective: |Objective: |Objective: |AE deletes a specific <locationPolicy> resource via a locationPolicy Delete Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.9.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.10.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a locationPolicy resource <locationPolicy> on Registrar CSE<br />AE has created a container resource <container> on Registrar CSE having its resourceID and locationID attribute set to locationContainerID and resourceID attribute of the <locationPolicy> resource respectively | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a locationPolicy Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <locationPolicy> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Check if possible that the <locationPolicy> resource is deleted in registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |Check if possible that the <locationPolicy> resource has been removed in registrar CSE | +|6 | |IOP Check |Check if possible that the associated resources (e.g. <container>, <contentInstance> resources) are removed from the registrar CSE | +|7 | |IOP Check |Check if possible that if the locationSource attribute and the locationUpdatePeriod attribute of the <locationPolicy> resource were set with appropriate value, the session with underlying network are torn down | +|8 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +### 8.1.22 Schedule management + +#### 8.1.22.1 Schedule Create + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_155 | +|Objective: |Objective: |Objective: |AE creates a <schedule> resource in Registrar CSE via a Schedule Create Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.17.2<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.9.2.1 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an application resource <AE> on Registrar CSE | +| | | | | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE sends a request to create a <schedule> | +|2 |<br />Mca |PRO Check Primitive |op = 1 (Create)<br />to = {CSEBaseName}<br />fr = AE-ID<br />rqi = (token-string)<br />ty = 18 (schedule)<br />pc = Serialized representation of <schedule> resource | +|3 | |IOP Check |Check if possible that the <schedule> resource is created in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2001 (CREATED)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <schedule> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.22.2 Schedule Retrieve + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_156 | +|Objective: |Objective: |Objective: |AE retrieves information of a <schedule> resource via a schedule Retrieve Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.17.3<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.9.2.2 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a schedule resource <schedule> as child resource of <CSEBase> resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a Retrieve Request for a <schedule> | +|2 |<br />Mca |PRO Check Primitive |op = 2 (Retrieve)<br />to = {CSEBaseName}/URI of <schedule> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 |<br />Mca |PRO Check Primitive |rsc = 2000 (OK)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <schedule> resource | +|4 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.22.3 Schedule Update + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_157 | +|Objective: |Objective: |Objective: |AE updates attribute in <schedule> resource via a schedule Update Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.17.4<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.9.2.3 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a schedule resource <schedule> as child resource of <AE> resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a schedule Update Request to update an attribute of the resource | +|2 |<br />Mca |PRO Check Primitive |op = 3 (Update)<br />to = {CSEBaseName}/URI of <schedule> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = Serialized representation of updated <schedule> resource | +|3 | |IOP Check |Check if possible that the <schedule> resource is updated in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2004 (Updated)<br />rqi = (token-string) same as received in request message<br />pc = Serialized representation of <schedule> resource | +|5 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.22.4 Schedule Delete + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_158 | +|Objective: |Objective: |Objective: |AE deletes <schedule> resource via a Schedule Delete Request | +|Configuration: |Configuration: |Configuration: |M2M_CFG_01 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 10.2.17.5<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.9.2.4 | +| | | | | +|Pre-test conditions: |Pre-test conditions: |Pre-test conditions: |AE has created an Application Entity resource <AE> on Registrar CSE<br />AE has created a <schedule> resource as child of <AE> resource | +|Test Sequence |Test Sequence |Test Sequence |Test Sequence | +|Step |RP |Type |Description | +|1 | |Stimulus |AE is requested to send a schedule Delete Request | +|2 |<br />Mca |PRO Check Primitive |op = 4 (Delete)<br />to = {CSEBaseName}/URI of <schedule> resource<br />fr = AE-ID<br />rqi = (token-string)<br />pc = empty | +|3 | |IOP Check |Check if possible that the <schedule> resource is deleted in Registrar CSE | +|4 |<br />Mca |PRO Check Primitive |rsc = 2002 (DELETED)<br />rqi = (token-string) same as received in request message<br />pc = empty | +|5 | |IOP Check |Check if possible that the <schedule> resource has been removed in Registrar CSE | +|6 | |IOP Check |AE indicates successful operation | +|IOP Verdict |IOP Verdict | | | +|PRO Verdict |PRO Verdict | | | + + + + +#### 8.1.22.5 Notification to AE with configured Schedule resource + +|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description | +|-|-|-|-| +|Identifier: |Identifier: |Identifier: |TD_M2M_NH_159 | +|Objective: |Objective: |Objective: |CSE sends a notification request to the AE when <schedule> resource is configured | +|Configuration: |Configuration: |Configuration: |M2M_CFG_10 | +|References: |References: |References: |oneM2M TS-0001 <a href="#_ref_1">[1]</a>, clause 9.6.9, 10.2.12<br />oneM2M TS-0004 <a href="#_ref_2">[2]</a>, clause 7.4.1 | +| | \ No newline at end of file