@@ -56,7 +57,9 @@ The information provided in this document is directed solely to professionals wh
...
@@ -56,7 +57,9 @@ The information provided in this document is directed solely to professionals wh
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.
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/>
<br/>Contents
# 1 Scope
# 1 Scope
The present document specifies Interoperability Test Descriptions (TDs) for the oneM2M Primitives as specified in oneM2M TS-0001 <ahref="#_ref_1">[1]</a>, oneM2M TS-0004 <ahref="#_ref_2">[2]</a>, the bindings oneM2M TS-0008 <ahref="#_ref_3">[3]</a>, oneM2M TS-0009 <ahref="#_ref_4">[4]</a> and oneM2M TS-0010 <ahref="#_ref_5">[5]</a>.
The present document specifies Interoperability Test Descriptions (TDs) for the oneM2M Primitives as specified in oneM2M TS-0001 <ahref="#_ref_1">[1]</a>, oneM2M TS-0004 <ahref="#_ref_2">[2]</a>, the bindings oneM2M TS-0008 <ahref="#_ref_3">[3]</a>, oneM2M TS-0009 <ahref="#_ref_4">[4]</a> and oneM2M TS-0010 <ahref="#_ref_5">[5]</a>.
...
@@ -134,82 +137,78 @@ Void.
...
@@ -134,82 +137,78 @@ Void.
For the purposes of the present document, the following abbreviations apply:
For the purposes of the present document, the following abbreviations apply:
`ACP-SD Access Control Policy-Semantic Descriptor`
| ACP | Access Control Policy |
`ADN-AE AE which resides in the Application Dedicated Node`
| ACP-SD | Access Control Policy-Semantic Descriptor |
`AE Application Entity`
| ADN-AE | AE which resides in the Application Dedicated Node |
`AE-ID Application Entity Identifier`
| AE | Application Entity |
`APP-ID Application Identifier`
| AE-ID | Application Entity Identifier |
`BBF BroadBand Forum`
| APP-ID | Application Identifier |
`CFG Configuration`
| BBF | BroadBand Forum |
`CoAP Constrained Application Protocol`
| CFG | Configuration |
`CP Communication Patterns`
| CoAP | Constrained Application Protocol |
`CSE Common Services Entity`
| CP | Communication Patterns |
`CSE-ID Common Service Entity Identifier`
| CSE | Common Services Entity |
`DAS Dynamic Authorization System`
| CSE-ID | Common Service Entity Identifier |
`DDN Downlink Data Notification`
| DAS | Dynamic Authorization System |
`DM Device Management`
| DDN | Downlink Data Notification |
`DTLS Datagram Transport Layer Security`
| DM | Device Management |
`DUT Device Under Test`
| DTLS | Datagram Transport Layer Security |
`ECDHE Elliptic-curve Diffie-Hellman`
| DUT | Device Under Test |
`FQDN Fully Qualified Domain Name`
| ECDHE | Elliptic-curve Diffie-Hellman |
`HAIM Home Appliances Information Model`
| FQDN | Fully Qualified Domain Name |
`HSS Home Subscriber Serve`
| HAIM | Home Appliances Information Model |
`HTTP HyperText Transfer Protocol`
| HSS | Home Subscriber Serve |
`IN Infrastructure Node`
| HTTP | HyperText Transfer Protocol |
`IN-AE Application Entity that is registered with the CSE in the Infrastructure Node`
| IN | Infrastructure Node |
`IN-CSE CSE which resides in the Infrastructure Node`
| IN-AE | Application Entity that is registered with the CSE in the Infrastructure Node |
`IOP Interoperability`
| IN-CSE | CSE which resides in the Infrastructure Node |
`IP Internet Protocol`
| IOP | Interoperability |
`IPE Interworking Proxy Entity`
| IP | Internet Protocol |
`JSON JavaScript Object Notation`
| IPE | Interworking Proxy Entity |
`LWM2M Lightweight M2M`
| JSON | JavaScript Object Notation |
`M2M Machine to Machine`
| LWM2M | Lightweight M2M |
`MA Mandatory Announced`
| M2M | Machine to Machine |
`MBMS Multimedia Broadcast Multicast Service`
| MA | Mandatory Announced |
`Mca Reference Point for M2M Communication with AE`
| MBMS | Multimedia Broadcast Multicast Service |
`Mcc Reference Point for M2M Communication with CSE`
| Mca | Reference Point for M2M Communication with AE |
`MEF M2M Enrolment Function`
| Mcc | Reference Point for M2M Communication with CSE |
`MH Multi Hop`
| MEF | M2M Enrolment Function |
`MNO Mobile Network Operator`
| MH | Multi Hop |
`MO Management Object`
| MNO | Mobile Network Operator |
`MQTT Message Queuing Telemetry Transport`
| MO | Management Object |
`MT Mobile Terminated`
| MQTT | Message Queuing Telemetry Transport |
`NB Non-Blocking`
| MT | Mobile Terminated |
`NH No Hop`
| NB | Non-Blocking |
`NIDD non-IP Data Delivery`
| NH | No Hop |
`NODN Non oneM2M Device Node`
| NIDD | non-IP Data Delivery |
`OMA Open Mobile Alliance`
| NODN | Non oneM2M Device Node |
`PDN Packet Data Network`
| OMA | Open Mobile Alliance |
`PRO Protocol`
| PDN | Packet Data Network |
`PSK Pre-Shared Key`
| PRO | Protocol |
`PSM Power Savings Mode`
| PSK | Pre-Shared Key |
`RDS Reliable Data Service`
| PSM | Power Savings Mode |
`RFC Request for Comments`
| RDS | Reliable Data Service |
`RP Reference Point`
| RFC | Request for Comments |
`RPC Remote Procedure Calls`
| RP | Reference Point |
`RQI Request-ID`
| RPC | Remote Procedure Calls |
`SCEF Service Capability Exposure Function`
| RQI | Request-ID |
`SD Semantic Descriptor`
| SCEF | Service Capability Exposure Function |
`SE Security`
| SD | Semantic Descriptor |
`SGS Semantic Graph Store`
| SE | Security |
`SH Single Hop`
| SGS | Semantic Graph Store |
`SP Service Provider`
| SH | Single Hop |
`SPARQL SPARQL Protocol and RDF Query Language`
| SP | Service Provider |
`SUID Security Usage Identifier`
| SPARQL | SPARQL Protocol and RDF Query Language |
`SUT System Under Test`
| SUID | Security Usage Identifier |
`TCP [Transmission Control Protocol](Transmission Control Protocol)`
| SUT | System Under Test |
`TD Test Description`
| TCP | Transmission Control Protocol |
`TLS Transport Layer Security`
| TD | Test Description |
`TMGI Temporary Mobile Group Identity`
| TLS | Transport Layer Security |
`TP Traffic Pattern`
| TMGI | Temporary Mobile Group Identity |
`UDP User Datagram Protocol`
| TP | Traffic Pattern |
`URI Uniform Resource Identifier`
| UDP | User Datagram Protocol |
`XML eXtensible Markup Language`
| URI | Uniform Resource Identifier |
| XML | eXtensible Markup Language |
# 4 Conventions
# 4 Conventions
...
@@ -247,8 +246,6 @@ In order to facilitate the specification of test cases an interoperability test
...
@@ -247,8 +246,6 @@ In order to facilitate the specification of test cases an interoperability test
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 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:
...
@@ -346,10 +343,8 @@ In oneM2M TS-0010 <a href="#_ref_5">[5]</a>, all oneM2M request/response paramet
...
@@ -346,10 +343,8 @@ In oneM2M TS-0010 <a href="#_ref_5">[5]</a>, all oneM2M request/response paramet
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.
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> |
|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
|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> |
|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> |
...
@@ -418,8 +413,7 @@ Since the representation can be XML or JSON, payload should be abstract to suppo
...
@@ -418,8 +413,7 @@ Since the representation can be XML or JSON, payload should be abstract to suppo
|53 |Resource management<br/><br/>Single Hop |PollingChannel |TD_M2M_NH_41 |AE updates attribute in pollingChannel resource via a Update 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 |
|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 |
|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
|56 |Resource management<br/><br/>Single Hop |FanoutPoint |TD_M2M_NH_44 |AE creates a <contentInstance> resource in each group member |
<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 |
|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 |
|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 |
|59 |Resource management<br/><br/>Single Hop |FanoutPoint |TD_M2M_NH_47 |AE deletes a <container> of each member |
...
@@ -472,8 +466,7 @@ Since the representation can be XML or JSON, payload should be abstract to suppo
...
@@ -472,8 +466,7 @@ Since the representation can be XML or JSON, payload should be abstract to suppo
|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 |
|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 |
|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 |
|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
|109 |Non-Blocking |Synchronous request<br/> |TD_M2M_NB_03 |AE updates a Container resource using non-blocking synchronous request in registrar CSE |
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 |
|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 |
|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 |
|112 |Non-Blocking |Asynchronous request |TD_M2M_NB_06 |AE retrieves a Container resource using non-blocking asynchronous request |
...
@@ -542,8 +535,7 @@ Since the representation can be XML or JSON, payload should be abstract to suppo
...
@@ -542,8 +535,7 @@ Since the representation can be XML or JSON, payload should be abstract to suppo
|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 |
|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> |
|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 |
|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
|179 |Semantics |Semantic Filtering and discovery |TD_M2M_NH_115 |AE performs a Semantic Query request in Registrar CSE using the semanticFilter filter criteria |
filter criteria |
|180 |Semantics |Semantic Mashup |TD_M2M_NH_116 |AE creates a SemanticMashupJobProfile resource in Registrar CSE via a SemanticMashupJobProfile Create Request |
|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 |
|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 |
|182 |Semantics |Semantic Mashup |TD_M2M_NH_118 |AE updates attribute in <semanticMashupJobProfile> resource via a semanticMashupJobProfile Update Request |
...
@@ -679,8 +671,7 @@ oneM2M entities model
...
@@ -679,8 +671,7 @@ oneM2M entities model
#### 7.1.2.4 M2M_CFG_08
#### 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,
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.
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:
This configuration is mapped to cases including:
...
@@ -865,8 +856,7 @@ oneM2M entities model
...
@@ -865,8 +856,7 @@ oneM2M entities model
|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 |
|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 |
|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 |
|5 | |IOP Check |Check if possible that the <remoteCSE> resource is also removed from registree CSE |
|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
|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 |
|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> |
|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> |
|Objective: |Objective: |Objective: |AE retrieves a <latest> resource of a <container> and the Registrar CSE points a latest
|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> |
<contentInstance> among the existing contentInstances to the <latest> resource of the <container> |
|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 |
|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 |
|1 | |Stimulus |AE is requested to send a Discovery request in order to discover specific resources located
|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) |
in Registrar CSE using multiple filter criteria (label, resource type and limit) |
|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 |
|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 |<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 |
|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 |
|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 |
|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 |
|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 |
|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 |
...
@@ -1599,8 +1584,7 @@ oneM2M entities model
...
@@ -1599,8 +1584,7 @@ oneM2M entities model
|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |
|Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |Interoperability Test Description |
|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
|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 |
AE<br/>AE has created a <container> resource on registrar CSE under <AE>, with name {containerName} and accessControlPolicyIDs including proper identifier of accessControlPolicy resource |
|3 | |IOP Check |Check if possible that the <node> resource is updated in Registrar CSE |
|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 |
|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 | | |Repeat steps 1-2. There is no pending request. When the Request Expiration Timestamp expires Registrar sends response indicating "REQUEST_TIMEOUT" |
|5 | | |Repeat steps 1-2. There is no pending request. When the Request Expiration Timestamp expires Registrar sends response indicating "REQUEST_TIMEOUT" |
/>Fr: CSE-ID<br/>Response Status Code: REQUEST_TIMEOUT |
|IOP Verdict |IOP Verdict | | |
|IOP Verdict |IOP Verdict | | |
|PRO Verdict |PRO Verdict | | |
|PRO Verdict |PRO Verdict | | |
...
@@ -2170,8 +2151,7 @@ oneM2M entities model
...
@@ -2170,8 +2151,7 @@ oneM2M entities model
|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> |
|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> |
|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 |
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 |
|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 |
|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 |
|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 |
|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
|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> |
|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 |
|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 |
|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) |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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. |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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') |
|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 |
|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') |
|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 |
|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') |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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> |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
|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 |
