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
Identifier:			TD_M2M_NH_01
Objective:			AE retrieves the CSEBase resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.3.2 oneM2M TS-0004 [2], clause 7.3.2
Pre-test conditions:			CSEBase resource has been automatically created in CSE
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) To (to) = Resource-ID of requested resource, assumed CSE-relative here From (from) = AE-ID of request originator Request Identifier (rqi) = (token-string)
3	Mca	PRO Check Primitive	Response Status Code (rsc) = 2000 (OK) Request Identifier (rqi) = same string as received in request message Content (pc) = Serialized Representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.2 RemoteCSE Management

8.1.2.1 RemoteCSE Create

Interoperability Test Description
Identifier:			TD_M2M_NH_02
Objective:			Registree CSE registers to Registrar CSE
Configuration:			M2M_CFG_02
References:			oneM2M TS-0001 [1], clause 10.2.2.1 oneM2M TS-0004 [2], clause 7.3.3.2.1
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	Registree CSE is requested to send a RemoteCSE Create request to Registrar CSE
2	Mcc	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = Registree CSE-ID rqi = (token-string) ty = 16 (RemoteCSE) pc = Serialized representation of resource
3	Mcc	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	Check if possible that the resource has been created in registrar CSE.
5		IOP Check	Check if possible that the corresponding resource has been also created in registree CSE.
6		IOP Check	Registree CSE indicates successful operation.
IOP Verdict
PRO Verdict

8.1.2.2 remoteCSE Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_03
Objective:			Registree CSE retrieves RemoteCSE from Registrar CSE
Configuration:			M2M_CFG_02
References:			oneM2M TS-0001 [1], clause 10.2.2.2 oneM2M TS-0004 [2], clause 7.3.3.2.2
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	Registree CSE is requested to send a RemoteCSE retrieve request to Registrar CSE
2	Mcc	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{remoteCSEName} fr = Registree CSE-ID rqi = (token-string) pc = empty
3	Mcc	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	Registree CSE indicates successful operation
IOP Verdict
PRO Verdict

8.1.2.3 remoteCSE Update

Interoperability Test Description
Identifier:			TD_M2M_NH_04
Objective:			Registree CSE updates RemoteCSE from Registrar CSE
Configuration:			M2M_CFG_02
References:			oneM2M TS-0001 [1], clause 10.2.2.3 oneM2M TS-0004 [2], clause 7.3.3.2.3
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	Registree CSE is requested to send a RemoteCSE update request to Registrar CSE
2	Mcc	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{remoteCSEName} fr = Registree CSE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource has been updated in registrar CSE.
4	Mcc	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	Registree CSE indicates successful operation
IOP Verdict
PRO Verdict

8.1.2.4 remoteCSE Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_05
Objective:			Registree CSE deletes RemoteCSE from Registrar CSE
Configuration:			M2M_CFG_02
References:			oneM2M TS-0001 [1], clause 10.2.2.4 oneM2M TS-0004 [2], clause 7.3.3.2.4
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	Registree CSE is requested to send a RemoteCSE delete request to Registrar CSE
2	Mcc	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/{remoteCSEName} fr = Registree CSE-ID rqi = (token-string) pc = empty
3	Mcc	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
4		IOP Check	Check if possible that the resource has been removed from registrar CSE.
5		IOP Check	Check if possible that the resource is also removed from registree CSE.
6		IOP Check	Registree CSE indicates successful operation.
IOP Verdict
PRO Verdict

8.1.3 Application Entity Registration

8.1.3.1 AE Create

Interoperability Test Description
Identifier:			TD_M2M_NH_06
Objective:			AE registers to its registrar CSE via an AE Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.1.1 oneM2M TS-0004 [2], clause 7.3.5.2.1
Pre-test conditions:			CSEBase resource has been created in CSE with name {CSEBaseName} AE does not have an AE-ID, i.e. it registers from scratch
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a AE Create request to register to the Registrar CSE
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 2 (AE) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.3.2 AE Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_07
Objective:			AE retrieves resource via an AE Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.1.2 oneM2M TS-0004 [2], clause 7.3.5.2.2
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created a resource on registrar CSE with name {AE}bgf
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a AE retrieve request to Registrar CSE
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{AE} fr = AE-ID of request originator rqi = (token-string)
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.3.3 AE Update

Interoperability Test Description
Identifier:			TD_M2M_NH_08
Objective:			AE updates attribute in resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.1.3 oneM2M TS-0004 [2], clause 7.3.5.2.3
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created a resource on registrar CSE with name {AE}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an AE Update Request
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{AE} fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource has been updated in registrar CSE.
4	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.3.4 AE Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_09
Objective:			AE de-registers by deleting resource via an AE Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.1.4 oneM2M TS-0004 [2], clause 7.3.5.2.4
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created a resource on registrar CSE with name {AE}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an AE Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/{AE} fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
4		IOP Check	Check if possible that the resource has been removed from registrar CSE.
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.4 Container Management

8.1.4.1 Container Create

Interoperability Test Description
Identifier:			TD_M2M_NH_10
Objective:			AE creates a container resource in registrar CSE via a container Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.1 oneM2M TS-0004 [2], clause 7.3.5.2.1
Pre-test conditions:			AE has created an application resource on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) ty = 3 (Container) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.4.2 Container Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_11
Objective:			AE retrieves information of a container resource via a container Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.2 oneM2M TS-0004 [2], clause 7.3.5.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.4.3 Container Update

Interoperability Test Description
Identifier:			TD_M2M_NH_12
Objective:			AE updates attribute in application resource via a container Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.3 oneM2M TS-0004 [2], clause 7.3.5.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE
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	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the < container > resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.4.4 Container Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_13
Objective:			AE deletes a specific container resource via a container Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.4 oneM2M TS-0004 [2], clause 7.3.5.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a container Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in registrar CSE.
6		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.1.5 ContentInstance Management

8.1.5.1 ContentInstance Create

Interoperability Test Description
Identifier:			TD_M2M_NH_14
Objective:			AE adds a contentInstance resource to a specific container in Registrar CSE via a contentInstance Create Request and the Registrar CSE updates the parent resource with stateTag, currentNrOfInstances, and CurrentByteSize attributes correspondingly
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.19.2 oneM2M TS-0004 [2], clause 7.3.6.2.1
Pre-test conditions:			AE has created an application resource on registrar CSE AE has created a container resource on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the resource and AE sends a request to create a < contentInstance > resource
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of < container > resource fr = AE-ID rqi = (token-string) ty = 4 (contentInstance) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE and AE sends a RETRIEVE request to the 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 resource.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful CREATE operation of and indicates Registrar CSE has updated stateTag, currentNrOfInstances, and CurrentByteSize attribute correspondingly by checking the response of a request to the resource
IOP Verdict		Set verdict to pass if IOP check goal is achieved exactly, otherwise verdict fail is set with corresponding error message.
PRO Verdict

8.1.5.2 ContentInstance Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_15
Objective:			AE retrieves information of a contentInstance resource via a contentInstance Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.19.3 oneM2M TS-0004 [2], clause 7.3.6.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE AE has created a contentInstance resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.5.3 ContentInstance Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_17
Objective:			AE deletes contentInstance resource via a contentInstance Delete Request and the Registrar CSE updates the parent resource with currentNrOfInstances, and CurrentByteSize attributes correspondingly
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.19.5 oneM2M TS-0004 [2], clause 7.3.6.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE AE has created a contentInstance resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the resource and AE is requested to send a contentInstance Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in Registrar CSE and AE sends a RETRIEVE request to the parent resource to check that if the Registrar CSE has updated currentNrOfInstances, and CurrentByteSize attribute correspondingly which is resulted from the successful deletion of child resource.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in registrar CSE.
6		IOP Check	AE indicates successful DELETE operation of and indicates Registrar CSE has updated currentNrOfInstances, and CurrentByteSize attribute correspondingly
IOP Verdict		Set the verdict to pass if both the is deleted and the Registrar CSE updated_currentNrOfInstances,_ and CurrentByteSize attribute. Otherwise, set the verdict to fail with corresponding error message.
PRO Verdict

8.1.5.4 ContentInstance Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_49
Objective:			AE deletes a resource of a and the Registrar CSE points a latest among the existing contentInstances to the resource of the
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.22.2 oneM2M TS-0004 [2], clause 7.4.28.2.5
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE AE has created more than one contentInstances as child of on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE retrieves a resource in a and then sends a DELETE request to the resource of the
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource of a fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = representation of deleted resource of a
4		IOP Check	AE indicates successful DELETE operation of a resource and AE sends a RETRIEVE request to resource of a to check if the retrieved resource in the is different with that one that was retrieved before DELETE request of the resource in terms of resourceID and resourceName attribute value.
IOP Verdict		Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message.
PRO Verdict

8.1.5.5 ContentInstance Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_50
Objective:			AE deletes a resource of a and the Registrar CSE points an oldest among the existing contentInstances to the resource of the
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.22.2 oneM2M TS-0004 [2], clause 7.4.28.2.5
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE AE has created more than one contentInstances as child of on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE retrieves a resource of a and AE sends a DELETE Request to the resource of the
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource of a fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = representation of deleted resource of a



4		IOP Check	AE indicates successful DELETE operation of a resource and AE sends a RETRIEVE request to resource of a to check if the retrieved resource in the is different with that one that was retrieved before DELETE request of the resource in terms of resourceID and resourceName attribute values.
IOP Verdict		Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message.
PRO Verdict

8.1.5.6 ContentInstance Create when currentNrOfInstance equals to maxNrOfInstances in parent resource

Interoperability Test Description
Identifier:			TD_M2M_NH_51
Objective:			AE sends a CREATE request to a which contains attribute currentNrOfInstances whose value equals to that of maxNrOfInstances and Registrar CSE deletes the oldest from the parent and then creates the requested resource for the originator AE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.19.2 oneM2M TS-0004 [2], clause 7.3.6.2.1
Pre-test conditions:			AE has created an application resource on registrar CSE AE has created a container resource (where the number of contentInstances equals to the value set in maxNrOfInstance) on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the contentInstance resource and AE sends a request to create a resource
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) ty = 4 (contentInstance) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource of a is deleted
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful CREATE operation of and indicates the representation of the recent resource in the is different with that of resource retrieved at the beginning of test in terms of resourceID and resourceName attribute value
IOP Verdict		Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message.
PRO Verdict

8.1.5.7 ContentInstance Retrieve

8.1.5.7.1 Attribute locationID of the resource configured

Interoperability Test Description
Identifier:			TD_M2M_NH_102
Objective:			AE retrieves a resource of a for which attribute locationID is configured, value of locationUpdatePeriod is marked '0' or not defined and locationSource attribute is 'Network Based'.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.22.1 oneM2M TS-0004 [2], clause 7.4.27.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE AE has created a resource on Registrar CSE having its resourceID and locationContainerID attribute set to locationID and resourceID attribute of the resource respectively. In resource , value of locationUpdatePeriod is marked '0' or not defined and locationSource attribute is 'Network Based'.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource/la fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of latest 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
PRO Verdict

8.1.5.7.2 Attribute locationID of the resource not configured

Interoperability Test Description
Identifier:			TD_M2M_NH_71
Objective:			AE retrieves a resource of a and the Registrar CSE points a latest among the existing contentInstances to the resource of the
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.22.1 oneM2M TS-0004 [2], clause 7.4.27.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE AE has created multiple contentInstance resources as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource/la fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of latest resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.5.8 ContentInstance Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_72
Objective:			AE retrieves a resource of a and the Registrar CSE points a oldest among the existing contentInstances to the resource of the
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.23.1 oneM2M TS-0004 [2], clause 7.4.28.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE AE has created multiple contentInstance resources as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource/ol fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of oldest resource
4		IOP Check	AE indicates successful operation

8.1.6 Discovery

8.1.6.1 Discovery of all resources

Interoperability Test Description
Identifier:			TD_M2M_NH_18
Objective:			AE discovers all accessible resources from registrar CSE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.2.3.13
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a discovery request to registrar CSE
2	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE-ID rqi = (token-string) fu=1 pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing addresses of all discovered resources
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.6.2 Discovery with label filter criteria

Interoperability Test Description
Identifier:			TD_M2M_NH_19
Objective:			AE discovers accessible resources residing in Registrar CSE using the label filter criteria
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.2.3.13
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} A resource with label "key1" is created on Registrar CSE.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Discovery request in order to discover the resource using the label filter criteria
2	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE-ID rqi = (token-string) fu=1 lbl=key1 pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing the address of the address
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.6.3 Discovery with limit filter criteria

Interoperability Test Description
Identifier:			TD_M2M_NH_20
Objective:			AE discovers accessible resources residing in Registrar CSE limiting the number of matching resources to the specified value.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.2.3.13
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName}
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	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE-ID rqi = (token-string) fu=1 lim=2 pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message cnst=1 cnot=2 pc = Serialized representation of data object containing the address of the address
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.6.4 Discovery with multiple filter criteria

Interoperability Test Description
Identifier:			TD_M2M_NH_21
Objective:			AE discovers accessible resources residing in Registrar CSE using multiple Filter Criteria
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.2.3.13
Pre-test conditions:			Two resources with labels "key1" and "key2" are created in Registrar CSE. A resources with labels "key1" and "key2" is created in Registrar CSE.
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	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE-ID rqi = (token-string) fu=1 lbl=key1 lbl=key2 ty=3 lim=1 pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing the address of one of the resources
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.6.5 Discovery with level filter criteria

Interoperability Test Description
Identifier:			TD_M2M_NH_58
Objective:			AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 1
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.3.3.14
			A resource is created under both resources in Registrar CSE. A resource is created under both resources in Registrar CSE.
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	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE1-ID rqi = (token-string) fu=1 lvl=1 pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing the address of both resources
4		IOP Check	AE1 indicates successful operation
IOP Verdict
PRO Verdict

Interoperability Test Description
Identifier:			TD_M2M_NH_59
Objective:			AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 2
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.3.3.14
Pre-test conditions:			and resources are created in Registrar CSE. A resource is created under both resources in Registrar CSE. A resource is created under both resources in Registrar CSE.
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	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE1-ID rqi = (token-string) fu=1 lvl=2 pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing the address of all and resources
4		IOP Check	AE1 indicates successful operation
IOP Verdict
PRO Verdict

Interoperability Test Description
Identifier:			TD_M2M_NH_60
Objective:			AE1 discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 3
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.3.3.14
Pre-test conditions:			and resources are created in Registrar CSE. A resource is created under both resources in Registrar CSE. A resource is created under both resources in Registrar CSE.
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	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE1-ID rqi = (token-string) fu=1 lvl=3 pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing the address of all , and resources
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.6.6 Discovery with offset filter criteria

Interoperability Test Description
Identifier:			TD_M2M_NH_61
Objective:			AE discovers accessible resources residing in Registrar CSE using the offset filter criteria value set to 3
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.3.3.14
Pre-test conditions:			and resources are created in Registrar CSE. A resource is created under both resources in Registrar CSE. A resource is created under both resources in Registrar CSE.
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	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE1-ID rqi = (token-string) fu=1 ofst=3 pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing only 3 of the 6 , and resources hosted by the Registrar CSE
4		IOP Check	AE1 indicates successful operation
IOP Verdict
PRO Verdict

Interoperability Test Description
Identifier:			TD_M2M_NH_62
Objective:			AE discovers all the accessible resources residing in Registrar CSE using the offset filter criteria
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.3.3.14
Pre-test conditions:			and resources are created in Registrar CSE. A resource is created under both resources in Registrar CSE. A resource is created under both resources in Registrar CSE.
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	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE1-ID rqi = (token-string) fu=1 lim=2 pc = empty
3		IOP Check	Registrar CSE sends success response to AE1
4	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message cnst=1 cnot=2 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	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE1-ID rqi = (token-string) fu=1 ofst=2 lim=2 pc = empty
7		IOP Check	Registrar CSE sends success response to AE1
8	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message cnst=1 cnot=4 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	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE1-ID rqi = (token-string) fu=1 ofst=4 lim=2 pc = empty
11		IOP Check	Registrar CSE sends success response to AE1
12	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message cnst =2 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
PRO Verdict

8.1.6.7 Discovery with geoQuery filter criteria

Interoperability Test Description
Identifier:			TD_M2M_NH_168
Objective:			AE discovers using geoQuery filter criteria when geoSpatialFunctionType set to 1 (within)
Configuration:			M2M_CFG_01
Applicable Release s			From Rel-4
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.3.3.17
Pre-test conditions:			and resources are created in Registrar CSE. A resource is created under the resource in Registrar CSE. The resource has location attribute set to type as 2(LineString) and coordinates as [[100.0, 0.0], [101.0, 1,0]].
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a Discovery request in order to discover resources located in Registrar CSE using geoQuery filter criteria
2	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE1-ID rqi = (token-string) fu = 1 (Discovery Criteria) gq = {gmty=3(Polygon), geom=[[99.0,0.0],[99.0,1.0],[101.0,0.0],[101.0,1.0]], gsf=1(within)} pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing which fulfill the geoQuery discovery hosted by the Registrar CSE
4		IOP Check	AE1 indicates successful operation
IOP Verdict
PRO Verdict

Interoperability Test Description
Identifier:			TD_M2M_NH_169
Objective:			AE discovers using geoQuery filter criteria when geoSpatialFunctionType set to 2 (contains)
Configuration:			M2M_CFG_01
Applicable Releases			From Rel-4
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.3.3.17
Pre-test conditions:			and resources are created in Registrar CSE. A resource is created under the resource in Registrar CSE. The resource has location attribute set to type as 3(Polygon) and coordinates as [99.0,0.0],[99.0,1.0],[101.0,0.0],[101.0,1.0].
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a Discovery request in order to discover resources located in Registrar CSE using geoQuery filter criteria
2	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE1-ID rqi = (token-string) fu = 1 (Discovery Criteria) gq = {gmty=2(LineString), geom=[[100.0, 0.0], [101.0, 1,0]], gsf=2(contains)} pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing which fulfill the geoQuery discovery hosted by the Registrar CSE
4		IOP Check	AE1 indicates successful operation
IOP Verdict
PRO Verdict

Interoperability Test Description
Identifier:			TD_M2M_NH_170
Objective:			AE discovers using geoQuery filter criteria when geoSpatialFunctionType set to 3 (intersects)
Configuration:			M2M_CFG_01
Applicable Release			From Rel-4
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.3.3.17
Pre-test conditions:			and resources are created in Registrar CSE. A resource is created under the resource in Registrar CSE. The resource has location attribute set to type as 3(Polygon) and coordinates as [99.0,0.0],[99.0,1.0],[101.0,0.0],[101.0,1.0].
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a Discovery request in order to discover resources located in Registrar CSE using geoQuery filter criteria
2	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE1-ID rqi = (token-string) fu = 1 (Discovery Criteria) gq = {gmty=3(Polygon), geom=[[101.0,0.0],[101.0,1.0],[103.0,0.0],[103.0,1.0]], gsf=3(intersects)} pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing which fulfill the geoQuery discovery hosted by the Registrar CSE
4		IOP Check	AE1 indicates successful operation
IOP Verdict
PRO Verdict

8.1.7 Subscription Management

8.1.7.1 Subscription Create

Interoperability Test Description
Identifier:			TD_M2M_NH_22
Objective:			AE creates a subscription to Application Entity resource via subscription Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.11.2 oneM2M TS-0004 [2], clause 7.3.7.2
Pre-test conditions:			AE has created an application resource on registrar CSE AE has created a container resource on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a subscription Create request to the Registrar CSE
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) ty = 23 (Subscription) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.7.2 Subscription Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_23
Objective:			AE retrieves subscription resource from Registrar CSE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.11.3 oneM2M TS-0004 [2], clause 7.3.7.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE AE has created a subscription resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.7.3 Subscription Update

Interoperability Test Description
Identifier:			TD_M2M_NH_24
Objective:			AE updates information about a subscription via subscription Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.11.4 oneM2M TS-0004 [2], clause 7.3.7.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE AE has created a subscription resource on Registrar CSE
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	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.7.4 Subscription Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_25
Objective:			AE cancels subscription via an subscription Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.11.5 oneM2M TS-0004 [2], clause 7.3.7.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE AE has created a subscription resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a subscription Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in registrar CSE.
6		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.8 accessControlPolicy Management

8.1.8.1 accessControlPolicy Create

Interoperability Test Description
Identifier:			TD_M2M_NH_26
Objective:			AE creates an accessControlPolicy resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1] clause 10.2.21.1 oneM2M TS-0004 [2], clause 7.3.1.2
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created a resource on registrar CSE with name {AE}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an accessControlPolicy Create Request
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/{AE} fr = AE-ID rqi = (token-string) ty = 1 (accessControlPolicy) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.8.2 accessControlPolicy Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_27
Objective:			AE retrieves accessControlPolicy resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.21.2 oneM2M TS-0004 [2], clause 7.3.1.2
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created a resource on registrar CSE with name {AE} accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a accessControlPolicy retrieve request to Registrar CSE
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{AE}/{accessControlPolicyName} fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.8.3 accessControlPolicy Update

Interoperability Test Description
Identifier:			TD_M2M_NH_28
Objective:			AE updates attribute in accessControlPolicy resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.21.3 oneM2M TS-0004 [2], clause 7.3.1.2
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created a resource on registrar CSE with name {AE} accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an accessControlPolicy update request to Registrar CSE
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{AE}/{accessControlPolicyName} fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource has been updated in registrar CSE.
4	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.8.4 accessControlPolicy Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_29
Objective:			AE deletes accessControlPolicy resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.21.4 oneM2M TS-0004 [2], clause 7.3.1.2
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created a resource on registrar CSE with name {AE} accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an accessControlPolicy delete request to Registrar CSE
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/{AE}/{accessControlPolicyName} fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
4		IOP Check	Check if possible that the resource has been removed from registrar CSE.
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.8.5 Unauthorized operation (Insufficient Access Rights, operations)

Interoperability Test Description
Identifier:			TD_M2M_NH_30
Objective:			AE delete request is rejected due to accessControlPolicy (accessControlOperations)
Configuration:			M2M_CFG_01
References:			oneM2M TS-0004 [2], clause 7.3.3.15
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created a resource on registrar CSE with name {AE} accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName}, and accessControlOperations with no delete privilege AE has created a resource on registrar CSE under , with name {containerName} and accessControlPolicyIDs including proper identifier of accessControlPolicy resource.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a container Delete Request for resource
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/{AE}/{containerName} fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 4103 (ACCESS_DENIED) rqi = (token-string) same as received in request message pc = empty
4		IOP Check	Check if possible that the resource has not been removed in registrar CSE.
5		IOP Check	AE indicates unsuccessful operation (Delete error - no privilege)
IOP Verdict
PRO Verdict

8.1.8.6 Unauthorized operation (Insufficient Access Rights, originators)

Interoperability Test Description
Identifier:			TD_M2M_NH_73
Objective:			AE delete request is rejected due to accessControlPolicy (accessControlOriginators)
Configuration:			M2M_CFG_01
References:			oneM2M TS-0004 [2], clause 7.3.3.15
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created a resource on registrar CSE with name {AE} accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName}, and accessControlOriginators with no privilege for AE. AE has created a resource on registrar CSE under , with name {containerName} and accessControlPolicyIDs including proper identifier of accessControlPolicy resource.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a container Delete Request for resource
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/{AE}/{containerName} fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 4103 (ACCESS_DENIED) rqi = (token-string) same as received in request message pc = empty
4		IOP Check	Check if possible that the resource has not been removed in registrar CSE.
5		IOP Check	AE indicates unsuccessful operation (Delete error - no privilege)
IOP Verdict
PRO Verdict

8.1.8.7 Authorized operation

Interoperability Test Description
Identifier:			TD_M2M_NH_74
Objective:			AE delete request is allowed due to accessControlPolicy
Configuration:			M2M_CFG_01
References:			oneM2M TS-0004 [2], clause 7.3.3.15
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created a resource on registrar CSE with name {AE} accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName}, and accessControlOperations with delete privilege and accessControlOriginators with privilege for AE. AE has created a resource on registrar CSE under , with name {containerName} and accessControlPolicyIDs including proper identifier of accessControlPolicy resource.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a container Delete Request for resource
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/{AE}/{containerName} fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
4		IOP Check	Check if possible that the resource has been removed in registrar CSE.
5		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.1.9 Group Management

8.1.9.1 Group Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_32
Objective:			AE retrieves group resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.7.3 oneM2M TS-0004 [2], clause 7.4.14.2.2
Pre-test conditions:			AE has created a resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a group Retrieve Request
2	Mca	PRO Check Primitive	op = 2 (RETRIEVE) to = {CSEBaseName}/{group} fr = AE-ID rqi = (token-string)
3	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.9.2 Group Create

Interoperability Test Description
Identifier:			TD_M2M_NH_31
Objective:			AE creates a group resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.7.2 oneM2M TS-0004 [2], clause 7.4.14.2.2
Pre-test conditions:			void
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a group Create Request
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 9 (group) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.9.3 Group Update

Interoperability Test Description
Identifier:			TD_M2M_NH_33
Objective:			AE updates attribute in group resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.7.4 oneM2M TS-0004 [2], clause 7.4.14.2.4
Pre-test conditions:			AE has created a resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a group Update Request
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{group} fr = AE-ID rqi = (token-string) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE..
4	Mca	PRO Check Primitive	rsc = 2004 (CHANGED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.9.4 Group Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_34
Objective:			AE deletes group resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.7.5 oneM2M TS-0004 [2], clause 7.4.14.2.5
Pre-test conditions:			AE has created a resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a group Delete Request
2	Mca	PRO Check Primitive	op = 4 (DELETE) to = {CSEBaseName}/{group} fr = AE-ID rqi = (token-string)
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message
4		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
5		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.1.10 Node Management

8.1.10.1 Node Create

Interoperability Test Description
Identifier:			TD_M2M_NH_35
Objective:			AE creates a node resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.14.1 oneM2M TS-0004 [2], clause 7.3.18.2.1
Pre-test conditions:			void
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a node Create Request
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 14 (node) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.10.2 Node Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_36
Objective:			AE retrieves node resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.14.2 oneM2M TS-0004 [2], clause 7.3.18.2.2
Pre-test conditions:			AE has created a resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a node Retrieve Request
2	Mca	PRO Check Primitive	op = 2 (RETRIEVE) to = {CSEBaseName}/{node} fr = AE-ID rqi = (token-string)
3	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.10.3 Node Update

Interoperability Test Description
Identifier:			TD_M2M_NH_37
Objective:			AE updates attribute in node resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.14.3 oneM2M TS-0004 [2], clause 7.3.18.2.3
Pre-test conditions:			AE has created a resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a node Update Request
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{node} fr = AE-ID rqi = (token-string) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE..
4	Mca	PRO Check Primitive	rsc = 2004 (CHANGED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.10.4 Node Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_38
Objective:			AE deletes node resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.14.4 oneM2M TS-0004 [2], clause 7.3.18.2.4
Pre-test conditions:			AE has created a resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a node Delete Request
2	Mca	PRO Check Primitive	op = 4 (DELETE) to = {CSEBaseName}/{node} fr = AE-ID rqi = (token-string)
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message
4		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.11 PollingChannel Management

8.1.11.1 PollingChannel Create

Interoperability Test Description
Identifier:			TD_M2M_NH_39
Objective:			AE creates a resource in registrar CSE via a Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.13.2 oneM2M TS-0004 [2], clause 7.3.21.2.1
Pre-test conditions:			AE has created an application resource on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a < pollingChannel >
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) ty = 15 (pollingChannel) pc = Serialized representation of < pollingChannel > resource
3		IOP Check	Check if possible that the < pollingChannel > resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of < pollingChannel > resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.11.2 PollingChannel Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_40
Objective:			AE retrieves information of a pollingChannel resource via a Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.13.3 oneM2M TS-0004 [2], clause 7.3.21.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource < pollingChannel > on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a < pollingChannel >
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of < pollingChannel > resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of < pollingChannel > resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.11.3 pollingChannel Update

Interoperability Test Description
Identifier:			TD_M2M_NH_41
Objective:			AE updates attribute in pollingChannel resource via a Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.13.4 oneM2M TS-0004 [2], clause 7.3.21.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE
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	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of < pollingChannel > resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated < pollingChannel > resource
3		IOP Check	Check if possible that the < pollingChannel > resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of < pollingChannel > resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.11.4 pollingChannel Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_42
Objective:			AE deletes a pollingChannel resource via a Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.13.5 oneM2M TS-0004 [2], clause 7.3.21.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a container resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a subscription Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of < pollingChannel > resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the < pollingChannel > resource is deleted in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message 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
PRO Verdict

8.1.11.5 Long Polling on a PollingChannel Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_43
Objective:			AE retrieves information of a pollingChannel resource via a Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.13.7 oneM2M TS-0004 [2], clause 7.3.22.2.2
Pre-test conditions:			A pollingChannel resource < pollingChannel > has been created in application on the Registrar CSE A subscription to a resource has been created using the as a notificationURI in the subscription. A single resource is created in the subscribed to resource.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a pollingChannelURI Retrieve Request for
2	Mca	PRO Check Primitive	Sent RETRIEVE request contains To: ///pollingChannelURI Fr: AE-ID
3	Mca	PRO Check Primitive	Sent RETRIEVE response contains To: AE-ID Fr: CSE-ID Response Status Code: OK 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	Mca	PRO Check Primitive	Sent RETRIEVE response contains To: AE-ID Fr: CSE-ID Response Status Code: REQUEST_TIMEOUT
IOP Verdict
PRO Verdict

8.1.12 FanoutPoint Management

8.1.12.1 FanoutPoint Create

Interoperability Test Description
Identifier:			TD_M2M_NH_44
Objective:			AE creates a resource in each group member
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.7.6 oneM2M TS-0004 [2], clause 7.3.14.3.1
Pre-test conditions:			A group is created containing 2 members of type
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Create Request to create in each group member
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/{group}/fopt fr = AE-ID rqi = (token-string) ty = 4 (contentInstance) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in each member hosting CSE
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = aggregated response
5		IOP Check	AE indicates successful operation
IOP Verdict		Verify that the aggregate response includes responses from each member of the group
PRO Verdict

8.1.12.2 FanoutPoint Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_45
Objective:			AE retrieves the resource from in each group member
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.7.8 oneM2M TS-0004 [2], clause 7.3.14.3.2
Pre-test conditions:			A group is created containing 2 members of type
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request to the fanoutPoint of resource
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{group}/fopt fr = AE-ID rqi = (token-string)
3		IOP Check
4	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = aggregated response
5		IOP Check	AE indicates successful operation
IOP Verdict		Verify that the aggregate response includes responses from each member of the group
PRO Verdict

8.1.12.3 FanoutPoint Update

Interoperability Test Description
Identifier:			TD_M2M_NH_46
Objective:			AE updates an resource of each member resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.7.9 oneM2M TS-0004 [2], clause 7.3.14.3.3
Pre-test conditions:			A group is created containing 2 members of type
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Update Request to the fanoutPoint of resource to lifetime of the resource.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{group}/fopt fr = AE-ID rqi = (token-string) pc = Serialized representation of resource
3		IOP Check	Check if possible that both of the resources have been updated in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (CHANGED) rqi = (token-string) same as received in request message pc = aggregated response
5		IOP Check	AE indicates successful operation
IOP Verdict		Verify that the aggregate response includes responses from each member of the group
PRO Verdict

8.1.12.4 FanoutPoint Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_47
Objective:			AE deletes a of each member
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.7.10 oneM2M TS-0004 [2], clause 7.3.14.3.4
Pre-test conditions:			A group is created containing 2 members of type
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Delete 'oldest' Request to the fanoutPoint of resource
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/{group}/fopt fr = AE-ID rqi = (token-string)
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = aggregated response
4		Verify	Check if possible that the oldest resource has been removed in registrar CSE.
5		Verify	AE indicates successful operation
IOP Verdict		Verify that the aggregate response includes responses from each member of the group
PRO Verdict

8.1.13 Notification Management

8.1.13.1 Notification

Interoperability Test Description
Identifier:			TD_M2M_NH_48
Objective:			AE receives a notification request from the HOST CSE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.12 oneM2M TS-0004 [2], clause 7.4.1
Pre-test conditions:			AE1 has created an application resource on registrar CSE AE1 has created a container resource on registrar CSE AE1 has created a as a child resource of a AE2 has created an application resource on registrar CSE AE2 has permissions to UPDATE the container created by AE1
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a Update request to the created by AE1. This triggers or causes the HOST CSE to send a notification to AE1.
2	Mca	PRO Check Primitive	op = 5 (Notify) to = notificationURI of subscription resource from = Registrar CSE-ID rqi = (token-string) pc = Serialized representation of Notification data object
3		IOP Check	Check if the notification representation
4	Mca	PRO Check Primitive	Sent response contains rsc = 2000 (OK) rqi = (token-string) same as received in request message
5		IOP Check	AE1 indicates notification received
IOP Verdict
PRO Verdict

8.1.13.2 Update Notification

Interoperability Test Description
Identifier:			TD_M2M_NH_80
Objective:			AE2 sends maxNrOfInstances UPDATE request to which has been set to subscribed-to resource. Since resource has specific setting in eventNotificationCriteria, Hosting CSE send notification to AE1
Configuration:			M2M_CFG_10
References:			oneM2M TS-0001 [1], clause 9.6.8 oneM2M TS-0004 [2], clause 6.3.4.2.19
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE1 has created a resource on registrar CSE AE1 has created resources under the 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) AE2 has permissions to UPDATE the
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a Update Request to the . This triggers or causes the Hosting CSE to send a notification to AE1.
2	Mca	PRO Check Primitive	op = 3 (Update) to = ID of resource from = AE2-ID rqi = (token-string) pc = Serialized representation of maxNrOfInstances update
3		IOP Check	Hosting CSE successfully updated mxNrOfInsatnce of the resource
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE2 successfully received response of Update request
6	Mca	PRO Check Primitive	op = 5 (Notify) to = ID of resource from = Registrar CSE-ID rqi = (token-string) pc = Serialized representation of Notify request which contain notificationEventType equal to 1(Update of Resource)
7		IOP Check	AE1 successfully received Notify request
8	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message
9		IOP Check	Hosting CSE successfully received response of Notify request
10	Mca	PRO Check Primitive	op = 3 (Update) to = ID of resource from = AE2-ID rqi = (token-string) pc = Serialized representation of labels update(can be any other attribute)
11		IOP Check	Hosting CSE successfully updated labels of the resource
12	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
13		IOP Check	AE2 successfully received response of Update request, notify request will not be sent
IOP Verdict		Check that the notification is only sent when there is update of maxNrOfInstances due to setting of the eventNotificationCriteria
PRO Verdict

8.1.13.3 Delete Notification

Interoperability Test Description
Identifier:			TD_M2M_NH_81
Objective:			AE2 sends DELETE request to which has been set to subscribed-to resource. Since resource has notificationEventType with 'Delete of Resource', Hosting CSE send notification to AE1
Configuration:			M2M_CFG_10
References:			oneM2M TS-0001 [1], clause 9.6.8 oneM2M TS-0004 [2], clause 6.3.4.2.19
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE1 has created a resource on registrar CSE AE1 has created a under the resource, with notificationEventType set to 2(Delete of Resource) AE2 has permissions to DELETE the
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a Delete Request to the . This triggers or causes the Hosting CSE to send a notification to AE1.
2	Mca	PRO Check Primitive	op = 4 (Delete) to = ID of resource fr = AE2-ID rqi = (token-string) pc = empty
3		IOP Check	Hosting CSE successfully deleted the resource
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	AE2 successfully received response of Delete request
6	Mca	PRO Check Primitive	op = 5 (Notify) to = ID of resource from = Registrar CSE-ID rqi = (token-string) pc = Serialized representation of Notify request which contain notificationEventType equal to 2(Delete of Resource)
7		IOP Check	AE1 successfully received Notify request
8	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message
9		IOP Check	Hosting CSE successfully received response of Notify request
IOP Verdict
PRO Verdict

8.1.13.4 Creation of Direct Child Resource Notification

Interoperability Test Description
Identifier:			TD_M2M_NH_82
Objective:			AE2 sends CREATE request to which has been set to subscribed-to resource. Since resource has notificationEventType with 'Create of Direct Child Resource', Hosting CSE send notification to AE1
Configuration:			M2M_CFG_10
References:			oneM2M TS-0001 [1], clause 9.6.8 oneM2M TS-0004 [2], clause 6.3.4.2.19
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE1 has created a resource on registrar CSE AE1 has created a under the resource, with notificationEventType set to 3(Create of Direct Child Resource) AE2 has permissions to CREATE child resource under the
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a Create Request of resource to the resource. This triggers or causes the Hosting CSE to send a notification to AE1
2	Mca	PRO Check Primitive	op = 1 (Create) to = ID of resource fr = AE2-ID rqi = (token-string) ty = 4 (contentInstance) pc = Serialized representation of resource
3		IOP Check	Hosting CSE successfully created the resource under the resource
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE2 successfully received response of Create request
6	Mca	PRO Check Primitive	op = 5 (Notify) to = ID of resource from = Registrar CSE-ID rqi = (token-string) 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	Mca	PRO Check Primitive	Sent response contains rsc = 2000 (OK) rqi = (token-string) same as received in request message
9		IOP Check	Hosting CSE successfully received response of Notify request
IOP Verdict
PRO Verdict

8.1.13.5 Deletion of Direct Child Resource Notification

Interoperability Test Description
Identifier:			TD_M2M_NH_83
Objective:			AE2 sends DELETE request to the which is located under the subscribed-to resource. Since resource has notificationEventType with 'Delete of Direct Child Resource', Hosting CSE send notification to AE1
Configuration:			M2M_CFG_10
References:			oneM2M TS-0001 [1], clause 9.6.8 oneM2M TS-0004 [2], clause 6.3.4.2.19
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE1 has created a resource on registrar CSE AE1 has created a as a child resource of created by AE1 AE1 has created a under the resource, with notificationEventType set to 4(Delete of Direct Child Resource) AE2 has permissions to DELETE the
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a Delete Request to the . This triggers or causes the Hosting CSE to send a notification to AE1.
2	Mca	PRO Check Primitive	op = 4 (Delete) to = ID of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Hosting CSE successfully deleted the resource
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	AE2 successfully received response of Delete request
6	Mca	PRO Check Primitive	op = 5 (Notify) to = ID of resource from = Registrar CSE-ID rqi = (token-string) 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	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message
9		IOP Check	Hosting CSE successfully received response of Notify request
IOP Verdict
PRO Verdict

8.1.13.6 Notifcation Aggregation

Interoperability Test Description
Identifier:			TD_M2M_NH_89
Objective:			AE creates resources by sending Create Request to the fanOutPoint. Since AE has set notifyAggregation to 2, Hosting CSE aggregate notification and send aggregated notification to AE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.7.11 oneM2M TS-0004 [2], clause 7.4.14.2.4
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created two resources on registrar CSE AE has created a resource with memberIDs set to two resources. AE has set number in notifyAggregation to 2 AE has created resources under the members of resources by sending Create Request to the fanOutPoint. AE has set notificationForwardingURI and notificationEventType set to 3(Create of Direct Child Resource)
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Create Request of resource to the fanOutPoint
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/{group}/fopt fr = AE-ID rqi = (token-string) ty = 4 (contentInstance) pc = Serialized representation of resource
3		IOP Check	Hosting CSE successfully created the resources in each member
4	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = aggregated response
5		IOP Check	AE successfully received converged response
6	Mca	PRO Check Primitive	op = 5 (Notify) to = ID of resource from = Registrar CSE-ID rqi = (token-string) pc = aggregated Notify request which contain the occurrence of child resource creation
7		IOP Check	AE successfully received aggregated Notify request
8	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message
9		IOP Check	Group Hosting CSE successfully received response of Notify request
IOP Verdict		Check that the response is aggregated by the group Hosting CSE and successfully parse to AE
PRO Verdict

8.1.14 FlexContainer Management

8.1.14.1 FlexContainer Create

Interoperability Test Description
Identifier:			TD_M2M_NH_52
Objective:			AE creates a flexContainer resource in Registrar CSE via a flexContainer Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.29.1, 9.6.1.2.2 oneM2M TS-0004 [2], clause 7.4.37.2.1
Pre-test conditions:			AE has created an application resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 28 (flexContainer) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.14.2 FlexContainer Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_53
Objective:			AE retrieves information of a flexContainer resource via a flexContainer Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clauses 10.2.29.2, 9.6.1.2.2 oneM2M 0004 [2], clause 7.4.37.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a flexContainer resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.14.3 FlexContainer Update

Interoperability Test Description
Identifier:			TD_M2M_NH_54
Objective:			AE updates attribute in application resource via a flexContainer Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clauses 10.2.29.3, 9.6.1.2.2 oneM2M 0004 [2], clause 7.4.37.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a flexContainer resource on Registrar CSE
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	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the < flexContainer > resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.14.4 FlexContainer Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_55
Objective:			AE deletes a specific container resource via a container Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clauses 10.2.29.4, 9.6.1.2.2 oneM2M 0004 [2], clause 7.4.37.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a flexContainer resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a flexContainer Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in Registrar CSE.
6		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.1.14.5 Notification Create

Interoperability Test Description
Identifier:			TD_M2M_NH_56
Objective:			AE receives a notification request on flexContainer update from the HOST CSE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clauses 10.2.1.5, 9.6.1.2.2 oneM2M 0004 [2], clause 7.4.1
Pre-test conditions:			AE1 has created an application resource on Registrar CSE AE1 has created a flexContainer resource on Registrar CSE AE1 has created a as a child resource of a AE2 has created an application resource on Registrar CSE AE2 has permissions to UPDATE customAttributes of flexContainer.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a update request to for updating customAttribute. This triggers or causes the HOST CSE to send a notification to AE1.
2	Mca	PRO Check Primitive	op = 5 (Notify) to = notificationURI of subscription resource from = Registrar CSE-ID rqi = (token-string) pc = Serialized representation of Notification data object
3		IOP Check	Check if the notification representation
4	Mca	PRO Check Primitive	Sent response contains rsc = 2000 (OK) rqi = (token-string) same as received in request message
5		IOP Check	AE1 indicates notification received
IOP Verdict
PRO Verdict

Interoperability Test Description
Identifier:			TD_M2M_NH_57
Objective:			AE discovers accessible resources residing in Registrar CSE using attribute filter criteria which has a customAttribute name and value assigned to it.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clauses 10.2.6, 9.6.1.2.2 oneM2M 0004 [2], clause 7.3.3.14
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a flexContainer resource on Registrar CSE with customAttribute set to a specific value "x", created on Registrar CSE.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Discovery request in order to discover the resource using attribute filter criteria
2	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} fr = AE-ID rqi = (token-string) fu=1 atr=, pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing the address of the address
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.15 External Management Operations Management

8.1.15.1 mgmtCmd Create

Interoperability Test Description
Identifier:			TD_M2M_NH_63
Objective:			AE creates a mgmtCmd resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.9.2 oneM2M TS-0004 [2], clause 7.4.16.2.1
Pre-test conditions:			AE has created an application resource on Registrar CSE AE has created a node resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a mgmtCmd Create Request
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 12 (mgmtCmd) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict		Set verdict to pass if IOP check goal is achieved exactly, otherwise verdict fail is set with corresponding error message.
PRO Verdict

8.1.15.2 mgmtCmd Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_64
Objective:			AE retrieves mgmtCmd resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.9.3 oneM2M TS-0004 [2], clause 7.4.16.2.2
Pre-test conditions:			AE has created an application resource on Registrar CSE AE has created a node resource on Registrar CSE AE has created a mgmtCmd resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a mgmtCmd Retrieve Request
2	Mca	PRO Check Primitive	op = 2 (RETRIEVE) to = {CSEBaseName}/{mgmtCmd} fr = AE-ID rqi = (token-string)
3	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.15.3 mgmtCmd Update (Normal)

Interoperability Test Description
Identifier:			TD_M2M_NH_65
Objective:			AE updates attribute (not with 'true' in execEnable attribute) in mgmtCmd resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.9.4 oneM2M TS-0004 [2], clause 7.4.16.2.3.1
Pre-test conditions:			AE has created an application resource on Registrar CSE AE has created a node resource on Registrar CSE AE has created a mgmtCmd resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a mgmtCmd Update Request
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{mgmtCmd} fr = AE-ID rqi = (token-string) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.15.4 mgmtCmd Update (Execute)

Interoperability Test Description
Identifier:			TD_M2M_NH_66
Objective:			AE updates attribute (with 'true' in execEnable attribute) in mgmtCmd resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.9.6 oneM2M TS-0004 [2], clause 7.4.16.2.3.2
Pre-test conditions:			AE has created an application resource on Registrar CSE AE has created a node resource on Registrar CSE AE has created a mgmtCmd resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a mgmtCmd Update Request
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{mgmtCmd} fr = AE-ID rqi = (token-string) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.15.5 mgmtCmd Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_67
Objective:			AE deletes mgmtCmd resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.9.5 oneM2M TS-0004 [2], clause 7.4.16.2.4
Pre-test conditions:			AE has created an application resource on Registrar CSE AE has created a node resource on Registrar CSE AE has created a mgmtCmd resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a mgmtCmd Delete Request
2	Mca	PRO Check Primitive	op = 4 (DELETE) to = {CSEBaseName}/{mgmtCmd} fr = AE-ID rqi = (token-string)
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message
4		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.15.6 execInstance Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_68
Objective:			AE retrieves execInstance resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.9.8 oneM2M TS-0004 [2], clause 7.4.17.2.2
Pre-test conditions:			AE has created an application resource on Registrar CSE AE has created a node resource on Registrar CSE AE has created a mgmtCmd resource on Registrar CSE AE has executed the mgmtCmd resource on Registrar CSE (update execEnable attribute with 'true')
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a execInstance Retrieve Request
2	Mca	PRO Check Primitive	op = 2 (RETRIEVE) to = {CSEBaseName}/{mgmtCmd}/{execInstance} fr = AE-ID rqi = (token-string)
3	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.15.7 execInstance Update (Cancel)

Interoperability Test Description
Identifier:			TD_M2M_NH_69
Objective:			AE updates attribute 'execDisable' to true in execInstance resource to cancel pending management command.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.9.7 oneM2M TS-0004 [2], clause 7.4.17.2.1
Pre-test conditions:			AE has created an application resource on Registrar CSE AE has created a node resource on Registrar CSE AE has created a mgmtCmd resource on Registrar CSE AE has executed the mgmtCmd resource on Registrar CSE (update execEnable attribute with 'true')
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a execInstance Update Request
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{mgmtCmd}/{execInstance} fr = AE-ID rqi = (token-string) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.15.8 execInstance Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_70
Objective:			AE deletes execInstance resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.9.9 oneM2M TS-0004 [2], clause 7.4.17.2.3
Pre-test conditions:			AE has created an application resource on Registrar CSE AE has created a node resource on Registrar CSE AE has created a mgmtCmd resource on Registrar CSE AE has executed the mgmtCmd resource on Registrar CSE (update execEnable attribute with 'true')
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a execInstance Delete Request
2	Mca	PRO Check Primitive	op = 4 (DELETE) to = {CSEBaseName}/{mgmtCmd}/{execInstance} fr = AE-ID rqi = (token-string)
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message
4		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.16 SemanticDescriptor Management

8.1.16.1 SemanticDescriptor Create

Interoperability Test Description
Identifier:			TD_M2M_NH_75
Objective:			AE creates a SemanticDescriptor resource in Registrar CSE via a SemanticDescriptor Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.1.2 oneM2M TS-0004 [2], clause 7.4.34.2.1
Pre-test conditions:			AE has created an application resource on Registrar CSE AE has created a container resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of < container > resource fr = AE-ID rqi = (token-string) ty = 24 (semanticDescriptor) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.16.2 SemanticDescriptor Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_76
Objective:			AE retrieves information of a semanticDescriptor resource via a semanticDescriptor Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.1.3 oneM2M TS-0004 [2], clause 7.4.34.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticDescriptor resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.16.3 SemanticDescriptor Update

Interoperability Test Description
Identifier:			TD_M2M_NH_77
Objective:			AE updates attribute in resource via a semanticDescriptor Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.1.4 oneM2M TS-0004 [2], clause 7.4.34.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticDescriptor resource as child resource of resource
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	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.16.4 SemanticDescriptor Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_78
Objective:			AE deletes SemanticDescriptor resource via a SemanticDescriptor Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.1.5 oneM2M TS-0004 [2], clause 7.4.34.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticDescriptor resource as child of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a semanticDescriptor Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in Registrar CSE.
6		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.1.17 Semantic Resource Discovery

8.1.17.1 Discovery with semanticFilter filter criteria

Interoperability Test Description
Identifier:			TD_M2M_NH_79
Objective:			AE discovers accessible resources residing in Registrar CSE using the semanticFilter filter criteria
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.4 oneM2M TS-0004 [2], clause 7.3.3.18
Pre-test conditions:			AE1 has created an application resource on Registrar CSE AE1 has created a container resource on Registrar CSE AE1 has created a as a child resource of a
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a Discovery request to discover the resource using the semanticFilter filterCriteria
2	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} from = AE-ID rqi = (token-string) fu=1 smf=sparqlQuery1 pc = empty
3	Mca	PRO Check Primitive	Sent response contains rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing the address
4		IOP Check	AE1 indicates notification received
IOP Verdict
PRO Verdict

8.1.18 ResultContent

8.1.18.1 ResultContent=0

Interoperability Test Description
Identifier:			TD_M2M_NH_84
Objective:			Check creation of resource with result content set to 0(nothing)
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 8.1.2 oneM2M TS-0004 [2], clause 6.3.4.2.7
Pre-test conditions:			CSEBase resource has been created in CSE with name {CSEBaseName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a resource Create Request to the Registrar CSE with rcn=0
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 3 (container) rcn = 0 pc = Serialized representation of resource which contain {containerName} as a rn
3		IOP Check	Hosting CSE successfully created the resource
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message
5		IOP Check	AE successfully received response of Create request
IOP Verdict		Check that the response body does not include any message
PRO Verdict

8.1.18.2 ResultContent=1

Interoperability Test Description
Identifier:			TD_M2M_NH_85
Objective:			Check creation of resource with result content set to 1(attributes)
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 8.1.2 oneM2M TS-0004 [2], clause 6.3.4.2.7
Pre-test conditions:			CSEBase resource has been created in CSE with name {CSEBaseName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a resource Create Request to the Registrar CSE with rcn=1
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 3 (container) rcn = 1 pc = Serialized representation of resource
3		IOP Check	Hosting CSE successfully created the resource
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource which contain attributes
5		IOP Check	AE successfully received response of Create request
IOP Verdict		Check that the response body include attributes
PRO Verdict

8.1.18.3 ResultContent=2

Interoperability Test Description
Identifier:			TD_M2M_NH_86
Objective:			Check creation of resource with result content set to 2(hierarchical address)
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 8.1.2 oneM2M TS-0004 [2], clause 6.3.4.2.7
Pre-test conditions:			CSEBase resource has been created in CSE with name {CSEBaseName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a resource Create Request to the Registrar CSE with rcn=2
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 3 (container) rcn = 2 pc = Serialized representation of resource
3		IOP Check	Hosting CSE successfully created the resource
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Hierarchical address of resource
5		IOP Check	AE successfully received response of Create request
IOP Verdict		Check that the response body include hierarchical address
PRO Verdict

8.1.18.4 ResultContent=3

Interoperability Test Description
Identifier:			TD_M2M_NH_87
Objective:			Check creation of resource with result content set to 3(hierarchical address and attributes)
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 8.1.2 oneM2M TS-0004 [2], clause 6.3.4.2.7
Pre-test conditions:			CSEBase resource has been created in CSE with name {CSEBaseName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Create Request to the Registrar CSE with rcn=3
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 3 (container) rcn = 3 pc = Serialized representation of resource
3		IOP Check	Hosting CSE successfully created the resource
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource with hierarchical address
5		IOP Check	AE successfully received response of Create request
IOP Verdict		Check that the response body include hierarchical address and attributes
PRO Verdict

8.1.18.5 ResultContent=4

Interoperability Test Description
Identifier:			TD_M2M_NH_88
Objective:			Check retrievability of resource with result content set to 4(attributes and child resources)
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 8.1.2 oneM2M TS-0004 [2], clause 6.3.4.2.7
Pre-test conditions:			CSEBase resource has been created in CSE with name {CSEBaseName} AE has created a resource on registrar CSE AE has created two resources under the resources
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request to the Registrar CSE with rcn=4
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = ID of resource fr = AE-ID rqi = (token-string) rcn = 4
3		IOP Check	Hosting CSE successfully received Retrieve request of the resource
4	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of and child resources
5		IOP Check	AE successfully received response of Retrieve request
IOP Verdict		Check that the response body include attributes and child resources
PRO Verdict

8.1.19 timeSeries Management

8.1.19.1 timeSeries Create

Interoperability Test Description
Identifier:			TD_M2M_NH_90
Objective:			AE creates a resource in registrar CSE via a Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.30.1 oneM2M TS-0004 [2], clause 7.4.38.2.1
Pre-test conditions:			AE has created a resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Create Request of the resource
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) ty = 29 (timeSeries) pc = Serialized representation of resource
3		IOP Check	Registrar CSE successfully created the resource
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE successfully received response of Create Request
IOP Verdict
PRO Verdict

8.1.19.2 timeSeries Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_91
Objective:			AE retrieves information of a resource via a Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.30.2 oneM2M TS-0004 [2], clause 7.4.38.2.2
Pre-test conditions:			AE has created a resource on Registrar CSE AE has created a resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request of the resource
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Registrar CSE successfully received Retrieve Request of the resource
4	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE successfully received response of Retrieve Request
IOP Verdict
PRO Verdict

8.1.19.3 timeSeries Update

Interoperability Test Description
Identifier:			TD_M2M_NH_92
Objective:			AE updates attribute in resource via a Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.30.3 oneM2M TS-0004 [2], clause 7.4.38.2.3
Pre-test conditions:			AE has created a resource on Registrar CSE AE has created a resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Update Request to the resource to update the maxNrOfInstances
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of maxNrOfInstances update(can be any other attribute)
3		IOP Check	Registrar CSE successfully updated the maxNrOfInstances of the resource
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE successfully received response of Update Request
IOP Verdict
PRO Verdict

8.1.19.4 timeSeries Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_93
Objective:			AE deletes a resource via a Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.30.4 oneM2M TS-0004 [2], clause 7.4.38.2.4
Pre-test conditions:			AE has created a resource on Registrar CSE AE has created a resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Delete Request of the resource
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Registrar CSE successfully deleted the resource
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	AE successfully received response of Delete Request
IOP Verdict
PRO Verdict

8.1.20 timeSeriesInstance Management

8.1.20.1 timeSeriesInstance Create

Interoperability Test Description
Identifier:			TD_M2M_NH_94
Objective:			AE sends Create Request of a resource to a resource in Registrar CSE. Registrar CSE creates the resource and updates the parent resource with currentNrOfInstances and currentByteSize attributes correspondingly
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.31.1 oneM2M TS-0004 [2], clause 7.4.39.2.1
Pre-test conditions:			AE has created a resource on Registrar CSE AE has created a resource on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Create Request of the resource
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) ty = 30 (timeSeriesInstance) pc = Serialized representation of resource
3		IOP Check	Registrar CSE successfully created resource and updated currentNrOfInstances and currentByteSize of the resource
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE successfully received response of Create Request
IOP Verdict
PRO Verdict

8.1.20.2 timeSeriesInstance Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_95
Objective:			AE retrieves information of a resource via a Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.31.2 oneM2M TS-0004 [2], clause 7.4.39.2.2
Pre-test conditions:			AE has created a resource on Registrar CSE AE has created a resource on registrar CSE AE has created a resource as child resource of the resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a resource
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Registrar CSE successfully received Retrieve Request of the resource
4	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE successfully received response of Retrieve Request
IOP Verdict
PRO Verdict

8.1.20.3 timeSeriesInstance Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_96
Objective:			AE sends Delete Request of a resource in Registrar CSE. Registrar CSE delete the resource and updates the parent resource with currentNrOfInstances and currentByteSize attributes correspondingly
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.31.4 oneM2M TS-0004 [2], clause 7.4.39.2.4
Pre-test conditions:			AE has created a resource on Registrar CSE AE has created a resource on registrar CSE AE has created a resource as child resource of the resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Delete Requeest a resource
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Registrar CSE successfully deleted resource and updated currentNrOfInstances and currentByteSize of the resource
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	AE successfully received response of Delete Request
IOP Verdict
PRO Verdict

8.1.20.4 timeSeriesInstance Create when currentNrOfInstance equals to maxNrOfInstances in parent resource

Interoperability Test Description
Identifier:			TD_M2M_NH_97
Objective:			AE sends a resource Create Request to a resource which contains currentNrOfInstances value equals to that of maxNrOfInstances and Registrar CSE delets the oldest resource from the resource and then creates the requested resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.31.1 oneM2M TS-0004 [2], clause 7.4.38.2.1
Pre-test conditions:			AE has created a resource on Registrar CSE AE has created a resource on registrar CSE AE has created several resources and currentNrOfInstances of the resource reach the maxNrOfInstances
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Create Request of the resource
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) ty = 30 (timeSeriesInstance) pc = Serialized representation of resource
3		IOP Check	Registrar CSE successfully deleted resource with the oldest dataGenerationTime and created resource
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE successfully received response of Create Request
IOP Verdict
PRO Verdict

8.1.21 Location Management

8.1.21.1 LocationPolicy Create

Interoperability Test Description
Identifier:			TD_M2M_NH_98
Objective:			AE creates a resource in registrar CSE via a locationPolicy Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.1.1 oneM2M TS-0004 [2], clause 7.4.10.2.1
Pre-test conditions:			AE has created an application resource on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 10 (LocationPolicy) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in registrar CSE. Check if possible that the resource is created on registrar CSE having its resourceID and locationID attribute set to locationContainerID and resourceID attribute of the resource respectively.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.21.2 LocationPolicy Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_99
Objective:			AE retrieves information of a resource via a locationPolicy Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.1.2 oneM2M TS-0004 [2], clause 7.4.10.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a locationPolicy resource on Registrar CSE AE has created a container resource on Registrar CSE having its resourceID and locationID attribute set to locationContainerID and resourceID attribute of the resource respectively.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.21.3 LocationPolicy Update

Interoperability Test Description
Identifier:			TD_M2M_NH_100
Objective:			AE updates attribute in resource via a locationPolicy Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.1.3 oneM2M TS-0004 [2], clause 7.4.10.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a locationPolicy resource on Registrar CSE AE has created a container resource on Registrar CSE having its resourceID and locationID attribute set to locationContainerID and resourceID attribute of the resource respectively.
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	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the < locationPolicy > resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.21.4 LocationPolicy Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_101
Objective:			AE deletes a specific resource via a locationPolicy Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.1.4 oneM2M TS-0004 [2], clause 7.4.10.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a locationPolicy resource on Registrar CSE AE has created a container resource on Registrar CSE having its resourceID and locationID attribute set to locationContainerID and resourceID attribute of the resource respectively.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a locationPolicy Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in registrar CSE.
6		IOP Check	Check if possible that the associated resources (e.g. , resources) are removed from the registrar CSE.
7		IOP Check	Check if possible that if the locationSource attribute and the locationUpdatePeriod attribute of the resource were set with appropriate value, the session with underlying network are torn down.
8		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.1.22 Schedule management

8.1.22.1 Schedule Create

Interoperability Test Description
Identifier:			TD_M2M_NH_155
Objective:			AE creates a resource in Registrar CSE via a Schedule Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.17.2 oneM2M TS-0004 [2], clause 7.4.9.2.1
Pre-test conditions:			AE has created an application resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 18 (schedule) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.22.2 Schedule Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_156
Objective:			AE retrieves information of a resource via a schedule Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.17.3 oneM2M TS-0004 [2], clause 7.4.9.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a schedule resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.22.3 Schedule Update

Interoperability Test Description
Identifier:			TD_M2M_NH_157
Objective:			AE updates attribute in resource via a schedule Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.17.4 oneM2M TS-0004 [2], clause 7.4.9.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a schedule resource as child resource of resource
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	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.1.22.4 Schedule Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_158
Objective:			AE deletes resource via a Schedule Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.17.5 oneM2M TS-0004 [2], clause 7.4.9.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a resource as child of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a schedule Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in Registrar CSE.
6		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.1.22.5 Notification to AE with configured Schedule resource

Interoperability Test Description
Identifier:			TD_M2M_NH_159
Objective:			CSE sends a notification request to the AE when resource is configured
Configuration:			M2M_CFG_10
References:			oneM2M TS-0001 [1], clause 9.6.9, 10.2.12 oneM2M TS-0004 [2], clause 7.4.1
Pre-test conditions:			AE1 has created an application resource on registrar CSE AE1 has created a container resource on registrar CSE AE1 has created a as a child resource of a AE1 has created a as a child resource of a AE2 has created an application resource on registrar CSE AE2 has permissions to UPDATE the container created by AE1
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a Update request to the created by AE1.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	The HOST CSE prepares a notification to AE1 and sends it within the time window indicated in scheduleElement attribute of resource
4	Mca	PRO Check Primitive	op = 5 (Notify) to = notificationURI of subscription resource from = Registrar CSE-ID rqi = (token-string) pc = Serialized representation of Notification data object
5	Mca	PRO Check Primitive	Sent response contains rsc = 2000 (OK) rqi = (token-string) same as received in request message
6		IOP Check	Check that AE1 has received the notification within the time window indicated in scheduleElement attribute of resource
IOP Verdict
PRO Verdict

8.2 Non-blocking configuration testing

8.2.1 Synchronous request

8.2.1.1 Container management

8.2.1.1.1 Container Create

Interoperability Test Description
Identifier:			TD_M2M_NB_01
Objective:			AE creates a resource using non-blocking synchronous request in registrar CSE.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.1 oneM2M TS-0004 [2], clause 7.3.6.2.1
Pre-test conditions:
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a non-blocking synchronous request to create a resource in registrar CSE
2	Mca	PRO Check Primitive	Sent request contains op = 1 (Create) to = {CSEBaseName} fr= AE-ID rqi = (token-string) rt = 1 (non-blocking synchronous) ty = 3 (container) pc = Serialized Representation of the resource
3	Mca	PRO Check Primitive	Registrar CSE creates an internal resource and sends acknowledgement response containing: rsc = 1000 (Accepted) rqi = token-string) same as received in request message pc = Reference to the created resource
4		IOP Check	AE indicates successful operation
5		Stimulus	AE is requested to wait then send a retrieve request to reference
6	Mca	PRO Check Primitive	Sent Retrieve request contains op = 2 (Retrieve) to = reference fr = AE-ID rqi = (token-string) pc = empty
7	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = resource with the parameter "requestStatus" set to 1 (COMPLETED) and the "operationResult" parameter containing the resource.
8		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.2.1.1.2 Container Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NB_02
Objective:			AE retrieves a resource using non-blocking synchronous request from registrar CSE.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.1 oneM2M TS-0004 [2], clause 7.3.6.2.1
Pre-test conditions:			AE has created a resource in registrar CSE.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a non-blocking synchronous request to retrieve the resource from registrar CSE.
2	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr= AE-ID rqi = (token-string) rt = 1 (non-blocking synchronous) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE creates an internal resource and sends acknowledgement response containing: rsc = 1000 (Accepted) rqi = token-string) same as received in request message pc = Reference to the created resource
4		IOP Check	AE indicates successful operation
5		Stimulus	AE is requested to send a retrieve request to reference
6	Mca	PRO Check Primitive	Sent Retrieve request contains op = 2 (Retrieve) to = reference fr = AE-ID rqi = (token-string) pc = empty
7	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = resource with the parameter "requestStatus" set to 1 (COMPLETED) and the "operationResult" parameter containing the resource.
8		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.2.1.1.3 Container Update

Interoperability Test Description
Identifier:			TD_M2M_NB_03
Objective:			AE updates a resource using non-blocking synchronous request in registrar CSE.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.1 oneM2M TS-0004 [2], clause 7.3.6.2.1
Pre-test conditions:			AE has created a resource in registrar CSE.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a non-blocking synchronous request to update the resource.
2	Mca	PRO Check Primitive	Sent request contains op = 3 (Update) to = {CSEBaseName}/URI of resource fr= AE-ID rqi = (token-string) rt = 1 (non-blocking synchronous) pc = Serialized Representation of the updated resource
3	Mca	PRO Check Primitive	Registrar CSE creates an internal resource and sends acknowledgement response containing: rsc = 1000 (Accepted) rqi = token-string) same as received in request message pc = Reference to the created resource
4		IOP Check	AE indicates successful operation
5		Stimulus	AE is requested to wait then send a retrieve request to reference
6	Mca	PRO Check Primitive	Sent Retrieve request contains op = 2 (Retrieve) to = reference fr = AE-ID rqi = (token-string) pc = empty
7	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = resource with the parameter "requestStatus" set to 1 (COMPLETED) and the "operationResult" parameter containing the resource.
8		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.2.1.1.4 Container Delete

Interoperability Test Description
Identifier:			TD_M2M_NB_04
Objective:			AE deletes a Container resource using non-blocking synchronous request.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.1 oneM2M TS-0004 [2], clause 7.3.6.2.1
Pre-test conditions:			AE has created resource on registrar CSE.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a non-blocking synchronous request to delete the resource.
2	Mca	PRO Check Primitive	Sent request contains op = 4 (Delete) to = {CSEBaseName}/URI of resource fr= AE-ID rqi = (token-string) rt = 1 (non-blocking synchronous) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE creates an internal resource and sends acknowledgement response containing: rsc = 1000 (Accepted) rqi = token-string) same as received in request message pc = Reference to the created resource
4		IOP Check	AE indicates successful operation
5		Stimulus	AE is requested to send a retrieve request to reference
6	Mca	PRO Check Primitive	Sent Retrieve request contains op = 2 (Retrieve) to = reference fr = AE-ID rqi = (token-string) pc = empty
7	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = resource with the parameter "requestStatus" set to 1 (COMPLETED)
8		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.2.2 Asynchronous request

8.2.2.1 Container management

8.2.2.1.1 Container Create

Interoperability Test Description
Identifier:			TD_M2M_NB_05
Objective:			AE creates a resource using non-blocking asynchronous request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.1 oneM2M TS-0004 [2], clause 7.3.6.2.1
Pre-test conditions:			AE is reachable on the URI: "AE-Notification-URI"
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a non-blocking asynchronous request to create the resource in registrar CSE.
2	Mca	PRO Check Primitive	Sent request contains op = 1 (Create) to = {CSEBaseName} fr= AE-ID rqi = (token-string) rt = 2 (non-blocking asynchronous) ty = 3 (container) nu= AE-Notification-URI oneM2M-RQI: Request-ID pc = Serialized Representation of the resource
3	Mca	PRO Check Primitive	Registrar CSE creates an internal resource and sends acknowledgement response containing: rsc = 1000 (Accepted) rqi = token-string) same as received in request message pc = Reference to the created resource
4		IOP Check	AE indicates successful operation
5		IOP Check	Registrar CSE sends notify request to AE
6	Mca	PRO Check Primitive	Sent request contains op = 5 (Notify) to = AE-Notification-URI fr = registrar CSE-ID rqi = (token-string) pc = Serialized representation of notification data object
7	Mca	PRO Check Primitive	AE sends notify response to Registrar CSE containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message
8		IOP Check	Registrar CSE indicates successful operation
IOP Verdict
PRO Verdict

8.2.2.1.2 Container Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NB_06
Objective:			AE retrieves a resource using non-blocking asynchronous request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.1 oneM2M TS-0004 [2], clause 7.3.6.2.1
Pre-test conditions:			AE has created a resource on registrar CSE. AE is reachable on the URI: "AE-Notification-URI"
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a non-blocking asynchronous request to retrieve the resource from registrar CSE
2	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) rt = 2 (non-blocking asynchronous) nu = AE-Notification-URI pc = empty
Mca	PRO Check Primitive	Registrar CSE creates an internal resource and sends acknowledgement response containing: rsc = 1000 (Accepted) rqi = (token-string) same as received in request message pc = Reference to the created resource
4		IOP Check	AE indicates successful operation
5		IOP Check	Registrar CSE sends notify request to AE
6	Mca	PRO Check Primitive	Sent request contains op = 5 (Notify) to = AE-Notification-URI fr = registrar CSE-ID rqi = (token-string) pc = Serialized representation of notification data object
7	Mca	PRO Check Primitive	AE sends notify response to Registrar CSE containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message
8		IOP Check	Registrar CSE indicates successful operation
IOP Verdict
PRO Verdict

8.2.2.1.3 Container Update

Interoperability Test Description
Identifier:			TD_M2M_NB_07
Objective:			AE updates a resource using non-blocking asynchronous request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.1 oneM2M TS-0004 [2], clause 7.3.6.2.1
Pre-test conditions:			AE has created a Container resource on registrar CSE AE is reachable on the URI: "AE-Notification-URI"
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a non-blocking asynchronous request to update the resource in registrar CSE.
2	Mca	PRO Check Primitive	Sent request contains op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) rt = 2 (non-blocking asynchronous) nu = AE-Notification-URI pc = Serialized Representation of the updated resource
3	Mca	PRO Check Primitive	Registrar CSE creates an internal resource and sends acknowledgement response containing: rsc = 1000 (Accepted) rqi = token-string) same as received in request message pc = Reference to the created resource
4		IOP Check	AE indicates successful operation
5		IOP Check	Registrar CSE sends notify request to AE
6	Mca	PRO Check Primitive	Sent request contains op = 5 (Notify) to = AE-Notification-URI fr = registrar CSE-ID rqi = (token-string) pc = Serialized representation of notification data object
7	Mca	PRO Check Primitive	AE sends notify response to Registrar CSE containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message
8		IOP Check	Registrar CSE indicates successful operation
IOP Verdict
PRO Verdict

8.2.2.1.4 Container Delete

Interoperability Test Description
Identifier:			TD_M2M_NB_08
Objective:			AE deletes a Container resource using non-blocking asynchronous request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.4.1 oneM2M TS-0004 [2], clause 7.3.6.2.1
Pre-test conditions:			AE has created a resource on registrar CSE AE is reachable on the URI: "AE-Notification-URI"
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a non-blocking asynchronous request to delete the resource in registrar CSE.
2	Mca	PRO Check Primitive	Sent request contains op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) rt = 2 (non-blocking asynchronous) nu = AE-Notification-URI pc = empty
3	Mca	PRO Check Primitive	Registrar CSE creates an internal resource and sends acknowledgement response containing: rsc = 1000 (Accepted) rqi = token-string) same as received in request message pc = Reference to the created resource
4		IOP Check	AE indicates successful operation
5		IOP Check	Registrar CSE sends notify request to AE
6	Mca	PRO Check Primitive	Sent request contains op = 5 (Notify) to = AE-Notification-URI fr = registrar CSE-ID rqi = (token-string) pc = Serialized representation of notification data object
7	Mca	PRO Check Primitive	AE sends notify response to Registrar CSE containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message
8		IOP Check	Registrar CSE indicates successful operation
IOP Verdict
PRO Verdict

8.3 Single hop configuration testing

8.3.1 Retargeting

8.3.1.1 RetargetingResource Create (Generic Test Description)

Interoperability Test Description
Identifier:			TD_M2M_SH_01
Objective:			AE creates a remote resource
Configuration:			M2M_CFG_03
References:
Pre-test conditions			Parents resources need to be created on the hosting CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Create Request to create on the Hosting CSE.
2	Mca	PRO Check Primitive	op = 1 (Create) to = URI of the parent resource fr = AE-ID rqi = (token-string) ty = type number pc = Serialized representation of resource
3		IOP Check	Check if possible that the request is forwarded by the registrar CSE to the Hosting CSE.
4	Mcc	PRO Check Primitive	op = 1 (Create) to = URI of the parent resource fr = AE-ID rqi = (token-string) ty = m2m:resourceType pc = Serialized representation of resource
5		IOP Check	Check if possible that the resource is created in the Hosting CSE.
6	Mcc	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
7		IOP Check	Check if possible that the response is forwarded by the registrar CSE to the AE.
8	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.1.2 Create

	Identifier	Refs	IOP Verdict	PRO Verdict
	TD_M2M_SH_01#01	oneM2M TS-0001 [1], clause 10.2.4.1 oneM2M TS-0004 [2], clause 7.3.5.2.1
	TD_M2M_SH_01#02	oneM2M TS-0001 [1], clause 10.2.19.2 oneM2M TS-0004 [2], clause 7.3.7.2
	TD_M2M_SH_01#03	oneM2M TS-0001 [1], clause 10.2.11.2 oneM2M TS-0004 [2], clause 7.3.7.2
	TD_M2M_SH_01#04	oneM2M TS-0001 [1], clause 10.2.21.1 oneM2M TS-0004 [2], clause 7.3.1.2
	TD_M2M_SH_01#05	oneM2M TS-0001 [1], clause 10.2.7.2 oneM2M TS-0004 [2], clause 7.3.12.2.1
	TD_M2M_SH_01#06	oneM2M TS-0001 [1], clause 10.2.13.2 oneM2M TS-0004 [2], clause 7.3.21.2.1
	TD_M2M_SH_01#07	oneM2M TS-0001 [1], clause 10.2.7.6 oneM2M TS-0004 [2], clause 7.3.14.3.1
	TD_M2M_SH_01#08	oneM2M TS-0001 [1], clause 10.2.14.1 oneM2M TS-0004 [2], clause 7.3.18.2.1

8.3.1.3 Resource Retrieve (Generic Test Description)

Interoperability Test Description
Identifier:			TD_M2M_SH_02
Objective:			AE retrieves a remote resource
Configuration:			M2M_CFG_03
References:
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request to retrieve on the remote Hosting CSE.
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = URI of the resource U fr = AE-ID rqi = (token-string)
3		IOP Check	Check if possible that the request is forwarded by the registrar CSE to the Hosting CSE.
4	Mcc	PRO Check Primitive	op = 2 (Retrieve) to URI of the resource fr = AE-ID rqi = (token-string)
5	Mcc	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
6		IOP Check	Check if possible that the response is forwarded by the registrar CSE to the AE.
7	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
8		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.1.4 retrieve

	Identifier	Refs	IOP Verdict	PRO Verdict
	TD_M2M_SH_02#01	oneM2M TS-0001 [1], clause 10.2.4.2 oneM2M TS-0004 [2], clause 7.3.5.2.2
	TD_M2M_SH_02#02	oneM2M TS-0001 [1], clause 10.2.19.3 oneM2M TS-0004 [2], clause 7.3.6.2.2
	TD_M2M_SH_02#03	oneM2M TS-0001 [1], clause 10.2.11.3 oneM2M TS-0004 [2], clause 7.3.7.2
	TD_M2M_SH_02#04	oneM2M TS-0001 [1], clause 10.2.21.2 oneM2M TS-0004 [2], clause 7.3.1.2
	TD_M2M_SH_02#05	oneM2M TS-0001 [1], clause 10.2.7.3 oneM2M TS-0004 [2], clause 7.3.12.2.2
	TD_M2M_SH_02#06	oneM2M TS-0001 [1], clause 10.2.13.3 oneM2M TS-0004 [2], clause 7.3.21.2.2
	TD_M2M_SH_02#07	oneM2M TS-0001 [1], clause 10.2.7.8 oneM2M TS-0004 [2], clause 7.3.14.3.2
	TD_M2M_SH_02#08	oneM2M TS-0001 [1], clause 10.2.14.2 oneM2M TS-0004 [2], clause 7.3.18.2.2
	TD_M2M_SH_02#09	oneM2M TS-0001 [1], clause 10.2.2.3 oneM2M TS-0004 [2], clause 7.3.3.2.3
	TD_M2M_SH_02#10	oneM2M TS-0001 [1], clause 10.2.1.2 oneM2M TS-0004 [2], clause 7.3.5.2.2
	TD_M2M_SH_02#11	oneM2M TS-0001 [1], clause 10.2.3.2 oneM2M TS-0004 [2], clause 7.3.2

8.3.1.5 Resource Update (Generic Test Description)

Interoperability Test Description
Identifier:			TD_M2M_SH_03
Objective:			AE updates a remote resource
Configuration:			M2M_CFG_03
References:
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an Update Request to update the on the Hosting CSE
2	Mca	PRO Check Primitive	op = 3 (Update) to = URI of the resource fr = AE-ID rqi = (token-string) pc = Serialized representation of resource
3		IOP Check	Check if possible that the request is forwarded by the registrar CSE to the Hosting CSE
4	Mcc	PRO Check Primitive	op = 3 (Update) to = URI of the resource fr = AE-ID rqi = (token-string) pc = Serialized representation of resource
5		IOP Check	Check if possible that the resource is updated in the Hosting CSE.
6	Mcc	PRO Check Primitive	rsc = 2004 (CHANGED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
7		IOP Check	Check if possible that the response is forwarded by the registrar CSE to the AE.
8	Mca	PRO Check Primitive	rsc = 2004 (CHANGED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.1.6 update

	Identifier	Refs	IOP Verdict	PRO Verdict
	TD_M2M_SH_03#01	oneM2M TS-0001 [1], clause 10.2.4.3 oneM2M TS-0004 [2], clause 7.3.5.2.3
	TD_M2M_SH_03#02	oneM2M TS-0001 [1], clause 10.2.11.4 oneM2M TS-0004 [2], clause 7.3.7.2
	TD_M2M_SH_03#03	oneM2M TS-0001 [1], clause 10.2.21.3 oneM2M TS-0004 [2], clause 7.3.1.2
	TD_M2M_SH_03#04	oneM2M TS-0001 [1], clause 10.2.7.4 oneM2M TS-0004 [2], clause 7.3.12.2.3
	TD_M2M_SH_03#05	oneM2M TS-0001 [1], clause 10.2.13.4 oneM2M TS-0004 [2], clause 7.3.21.2.3
	TD_M2M_SH_03#06	oneM2M TS-0001 [1], clause 10.2.7.9 oneM2M TS-0004 [2], clause 7.3.14.3.3
	TD_M2M_SH_03#07	oneM2M TS-0001 [1], clause 10.2.14.3 oneM2M TS-0004 [2], clause 7.3.18.2.3
	TD_M2M_SH_03#08	oneM2M TS-0001 [1], clause 10.2.2.3 oneM2M TS-0004 [2], clause 7.3.3.2.3
	TD_M2M_SH_03#09	oneM2M TS-0001 [1], clause 10.2.1.3 oneM2M TS-0004 [2], clause 7.3.5.2.3

8.3.1.7 Resource Delete (Generic Test Description)

Interoperability Test Description
Identifier:			TD_M2M_SH_04
Objective:			AE delete a remote resource
Configuration:			M2M_CFG_03
References:
Pre-test conditions:			Parents resources need to be created on the hosting CSE Resource has been created in Hosting CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Delete Request to delete on the Hosting CSE.
2	Mca	PRO Check Primitive	op = 4 (Delete) to = URI of the resource fr = AE-ID rqi = (token-string)
3		IOP Check	Check if possible that the request is forwarded by the registrar CSE to the Hosting CSE.
4	Mcc	PRO Check Primitive	op = 4 (Delete) to = URI of the resource fr = AE-ID rqi = (token-string)
5		IOP Check	Check if possible that the resource is deleted in the Hosting CSE.
6	Mcc	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message
7		IOP Check	Check if possible that the response is forwarded by the registrar CSE to the AE.
8	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.1.8 delete

	Identifier	Refs	IOP Verdict	PRO Verdict
	TD_M2M_SH_04#01	oneM2M TS-0001 [1], clause 10.2.4.4 oneM2M TS-0004 [2], clause 7.3.5.2.4
	TD_M2M_SH_04#02	oneM2M TS-0001 [1], clause 10.2.19.5 oneM2M TS-0004 [2], clause 7.3.6.2.4
	TD_M2M_SH_04#03	oneM2M TS-0001 [1], clause 10.2.11.5 oneM2M TS-0004 [2], clause 7.3.7.2
	TD_M2M_SH_04#04	oneM2M TS-0001 [1], clause 10.2.21.4 oneM2M TS-0004 [2], clause 7.3.1.2
	TD_M2M_SH_04#05	oneM2M TS-0001 [1], clause 10.2.7.5 oneM2M TS-0004 [2], clause 7.3.12.2.4
	TD_M2M_SH_04#06	oneM2M TS-0001 [1], clause 10.2.13.5 oneM2M TS-0004 [2], clause 7.3.21.2.4
	TD_M2M_SH_04#07	oneM2M TS-0001 [1], clause 10.2.7.10 oneM2M TS-0004 [2], clause 7.3.14.3.4
	TD_M2M_SH_04#08	oneM2M TS-0001 [1], clause 10.2.14.4 oneM2M TS-0004 [2], clause 7.3.18.2.4

8.3.1.9 Discovery with multiple filter criteria

Interoperability Test Description
Identifier:			TD_M2M_SH_09
Objective:			AE discovers accessible resources residing in the remote Hosting CSE using multiple Filter Criteria
Configuration:			M2M_CFG_03
References:			oneM2M TS-0001 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.2.3.13
Pre-test conditions:			Two resources with labels "key1" and "key2" are created in Hosting CSE. A resources with labels "key1" and "key2" is created in Hosting CSE.
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a discovery request to discover specific resources located in hosting CSE using multiple filter criteria (label, resource type and limit)
2	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = URI of hosting CSEBase fr = AE-ID rqi = (token-string) fu=1 lbl=key1 lbl=key2 rty=3 lim=1 pc = empty
3		IOP Check	Check if possible that the request is forwarded by the registrar CSE to the Hosting CSE.
4	Mcc	PRO Check Primitive	Forwarded request contains op = 2 (Retrieve) to = hosting CSEBase fr = AE-ID rqi = (token-string) fu=1 lbl=key1 lbl=key2 rty=3 lim=1 pc = empty
5		IOP Check	Check if possible that the response is sent by the hosting CSE to the registrar CSE.
6	Mcc	PRO Check Primitive	Hosting CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing the address of one of the resources
7		IOP Check	Check if possible that the response is forwarded from the registrar CSE to AE
6	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing the address of one of the resources
7		IOP Check	AE indicates successful operation

8.3.1.10 Unauthorized operation (Insufficient Access Rights)

Interoperability Test Description
Identifier:			TD_M2M_SH_10
Objective:			AE delete request is rejected after access rights verification using retargeting.
Configuration:			M2M_CFG_03
References:			oneM2M TS-0004 [2], clause 7.3.1.2
Pre-test conditions:			An resource with name {ACPName} has been created in remote hosting CSE, not allowing delete operation. AE has created an resource on registrar CSE with name {AEName} AE has created a sub-resource in the resource with name {containerName} and having as accessControlPolicy-ID the ID of the remote .
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Request to delete the resource from the registrar CSE.
2	Mca	PRO Check Primitive	op = 4 (Delete) to = URI of addressed resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that a request is sent by the registrar CSE to the Hosting CSE to retrieve the corresponding remote resource.
4	Mcc	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = URI of addressed resource fr = Registrar CSE-ID rqi = (token-string) pc = empty
5		IOP Check	Check if possible that the response is sent by the hosting CSE to the registrar CSE.
6	Mcc	PRO Check Primitive	Hosting CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
7		IOP Check	Check if possible that an access denied error response is sent by registrar CSE to AE
8	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 4103 (ACCESS_DENIED) rqi = (token-string) same as received in request message pc = empty
9		IOP Check	Check if possible that the resource has not been deleted.
10		IOP Check	AE indicates unsuccessful operation (Delete error - no privilege)

8.3.1.11 Notification

Interoperability Test Description
Identifier:			TD_M2M_SH_11
Objective:			AE receives a notification request from the remote hosting CSE
Configuration:			M2M_CFG_03
References:			oneM2M TS-0001 [1], clause 10.2.12 oneM2M TS-0004 [2], clause 7.4.1
Pre-test conditions:			A resource has been created on hosting CSE AE has created an resource on registrar CSE AE has created a resource for the resource on the remote hosting CSE.
Test Sequence
Step	RP	Type	Description
1		Stimulus	A sub-resource is created on the resource. This triggers or causes the hosting CSE to send a notification to AE.
2	Mca	PRO Check Primitive	op = 5 (Notify) to = URI of AE resource from = Hosting CSE-ID rqi = (token-string) pc = Serialized representation of Notification data object
3		IOP Check	Check if possible that the Notify request is forwarded by the registrar CSE to the AE-ID.
4	Mcc	PRO Check Primitive	op = 5 (Notify) to = AE from = Hosting CSE-ID rqi = (token-string) pc = Serialized representation of Notification data object
5		IOP Check	Check if possible that the response is sent by the AE to the registrar CSE.
6	Mcc	PRO Check Primitive	AE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = empty
7		IOP Check	Check if possible that the response is forwarded by registrar CSE to Hosting CSE
8	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = empty
9		IOP Check	Check if possible that the resource has not been deleted.
10		IOP Check	AE indicates unsuccessful operation (Delete error - no privilege).

8.3.2 Test Description

8.3.2.1 Create

Interoperability Test Description
Identifier:			TD_M2M_SH_05
Objective:			AE creates a resource
Configuration:			M2M_CFG_03
References:			oneM2M TS-0001 [1], clause 10.2.8.2
Pre-test conditions:			Management Session between Management Server and Management Client
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an Create Request to create an on IN-CSE.
2	Mca	PRO Check Primitive	op: 1 (CREATE) fr: AE-ID to: {CSEBaseName}/{node} rqi = (token-string) ty = 13 (mgmtObj) pc: Serialized representation of the resource
3		IOP Check	Check if possible that the resource is created in IN-CSE
4	mc	PRO Check Primitive	N/A
		PRO Check OMA DM	Requests to create the corresponding MO using Add DM command. The mapping of and MO can be referenced from clause 5.3 of oneM2M TS-0005 [10].
		PRO Check BBF TR069	Requests to create the corresponding information model using AddObject RPC. The mapping of and information model or RPC can be referenced from clause 7 of oneM2M TS-0006 [11].
		PRO Check OMA LWM2M	Requests to create the corresponding Objects using Create LWM2M Create operations. The mapping of and Object can be referenced from clause 6.3 of oneM2M TS-0005 [10].
5		IOP Check	Check if possible that the corresponding MO for OMA DM, information model for BBF TR069 or Object for OMA LWM2M is created on the Managed Entity.
6	mc	PRO Check Primitive	N/A
		PRO Check OMA DM	Response with status code (200) OK. Details can be found in clause 5.4 oneM2M TS-0005 [10].
		PRO Check BBF TR069	Successful response of the RPC. Details can be found in clause 8.1 oneM2M TS-0006 [11].
		PRO Check OMA LWM2M	Response with status code 2.01 Created. Details can be found in clause 6.4 oneM2M TS-0005 [10].
7	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
8		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.2.2 Update

Interoperability Test Description
Identifier:			TD_M2M_SH_06
Objective:			AE updates a resource
Configuration:			M2M_CFG_03
References:			oneM2M TS-0001 [1], clause 10.2.8.4
Pre-test conditions:			Management Session between Management Server and Management Client
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an Update Request to update an on IN-CSE.
2	Mca	PRO Check Primitive	op: 3 (UPDATE) fr: AE-ID to: {CSEBaseName}/{node}/{mgmtObj} rqi = (token-string) pc: Serialized representation of the resource
3		IOP Check	Check if possible that the resource is updated in IN-CSE
4	mc	PRO Check Primitive	N/A
		PRO Check OMA DM	Requests to update the corresponding MO using Replace DM command. The mapping of and MO can be referenced from clause 5.3 of oneM2M TS-0005 [10].
		PRO Check BBF TR069	Requests to Update the corresponding information model using SetParameterValues RPC. The mapping of and information model or RPC can be referenced from clause 7 of oneM2M TS-0006 [11].
		PRO Check OMA LWM2M	Requests to Update the corresponding Objects using LWM2M Write operations. The mapping of and Object can be referenced from clause 6.3 of oneM2M TS-0005 [10].
5		IOP Check	Check if possible that the corresponding MO for OMA DM, information model for BBF TR069 or Object for OMA LWM2M is Updated on the Managed Entity.
6	mc	PRO Check Primitive	N/A
		PRO Check OMA DM	Response with status code (200) OK. Details can be found in clause 5.4 oneM2M TS-0005 [10].
		PRO Check BBF TR069	Successful response of the RPC. Details can be found in clause 8.1 oneM2M TS-0006 [11].
		PRO Check OMA LWM2M	Response with status code 2.04 Changed. Details can be found in clause 6.4 oneM2M TS-0005 [10].
7	Mca	PRO Check Primitive	rsc = 2004 (CHANGED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
8		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.2.3 Retrieve

Interoperability Test Description
Identifier:			TD_M2M_SH_07
Objective:			AE retrieves a resource
Configuration:			M2M_CFG_03
References:			oneM2M TS-0001 [1], clause 10.2.8.3
Pre-test conditions:			Management Session between Management Server and Management Client
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an Retrieve Request to retrieve an on IN-CSE.
2	Mca	PRO Check Primitive	op = 2 (RETRIEVE) to = {CSEBaseName}/{node}/{mgmtObj} fr = AE-ID rqi = (token-string)
3		IOP Check	Check if possible that the resource is retrieved in IN-CSE
4	mc	PRO Check Primitive	N/A
		PRO Check OMA DM	Requests to retrieve the corresponding MO using Get DM command.
		PRO Check BBF TR069	Requests to retrieve the corresponding information model using GetParametersValue RPC.
		PRO Check OMA LWM2M	Requests to retrieve the corresponding Objects using Retrieve LWM2M Read operation.
5		IOP Check
6	mc	PRO Check Primitive	N/A
		PRO Check OMA DM	Response with status code (200) OK with the information of the MO. Details can be found in clause 5.4 oneM2M TS-0005 [10].
		PRO Check BBF TR069	Successful response of the RPC with the information about the management related information. Details can be found in clause 8.1 oneM2M TS-0006 [11].
		PRO Check OMA LWM2M	Response with status code 2.05 Content with the information of the Object. Details can be found in clause 6.4 oneM2M TS-0005 [10].
7	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
8		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.2.4 Delete

Interoperability Test Description
Identifier:			TD_M2M_SH_08
Objective:			AE deletes a resource
Configuration:			M2M_CFG_03
References:			oneM2M TS-0001 [1], clause 10.2.8.5
Pre-test conditions:			Management Session between Management Server and Management Client
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an Delete Request to delete an on IN-CSE.
2	Mca	PRO Check Primitive	op = 4 (DELETE) to = {CSEBaseName}/{node}/{mgmtObj} fr = AE-ID rqi = (token string)
3		IOP Check	Check if possible that the resource is deleted in IN-CSE
4	mc	PRO Check Primitive	N/A
		PRO Check OMA DM	Requests to delete the corresponding MO using Delete DM command.
		PRO Check BBF TR069	Requests to delete the corresponding information model using DeleteObject RPC.
		PRO Check OMA LWM2M	Requests to delete the corresponding Objects using LWM2M Delete operation.
5		IOP Check	Check if possible that the corresponding MO for OMA DM, information model for BBF TR069 or Object for OMA LWM2M is deleted on the Managed Entity.
6	mc	PRO Check Primitive	N/A
		PRO Check OMA DM	Response with status code (200) OK. Details can be found in clause 5.4 oneM2M TS-0005 [10].
		PRO Check BBF TR069	Successful response of the RPC. Details can be found in clause 8.1 oneM2M TS-0006 [11].
		PRO Check OMA LWM2M	Response with status code 2.02 Deleted. Details can be found in clause 6.4 oneM2M TS-0005 [10]
7	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message
8		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.3 Announcement Management

8.3.3.1 AEAnnc Create

Interoperability Test Description
Identifier:			TD_M2M_SH_12
Objective:			AE1 announces itself to CSE2
Configuration:			M2M_CFG_04
References:
Pre-test conditions			resource has been created in CSE1 with name {CSEBaseName1} AE1 has created a resource on registrar CSE with name {AE1} resource has been created in CSE2 with name {CSEBaseName2} CSE1 is registered to CSE2
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send an AE Update Request with announceTo attribute set to CSE2 CSE-ID
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{AE} fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the CREATE is sent from CSE1 to CSE2.
4	Mcc	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName2}/{CSEBaseName1} fr = CSE1-ID rqi = (token-string) ty = 10002 (AEAnnc) pc = Serialized representation of resource
5		IOP Check	Check if possible that the resource is created in CSE2 with only MA attributes.
6	Mcc	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
7		IOP Check	CSE1 sends a UPDATED response to the AE1.
8	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.3.2 ContainerAnnc Create

Interoperability Test Description
Identifier:			TD_M2M_SH_13
Objective:			AE1 announces a child container to CSE2
Configuration:			M2M_CFG_04
References:
Pre-test conditions			resource has been created in CSE1 with name {CSEBaseName1} AE1 has created a resource on registrar CSE with name {AE1} resource has been created in CSE2 with name {CSEBaseName2} AE2 has created a resource on registrar CSE with name {AE2} CSE1 is registered to CSE2 resource is created as a child of AE1 AE1 is announced on CSE2
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a an Update Request with announceTo attribute set to CSE2 CSE-ID
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{container} fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the CREATE is sent from CSE1 to CSE2.
4	Mcc	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName2}/{AE1Annc} fr = CSE1-ID rqi = (token-string) ty = 10003 (containerAnnc) pc = Serialized representation of < containerAnnc > resource
5		IOP Check	Check if possible that the < containerAnnc > resource is created in CSE2 with only MA attributes.
6	Mcc	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of < containerAnnc > resource
7		IOP Check	CSE1 sends a UPDATED response to the AE1.
8	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.3.3 ContainerAnnc Update

Interoperability Test Description
Identifier:			TD_M2M_SH_14
Objective:			AE1 announces an Optional Announce attribute to CSE2
Configuration:			M2M_CFG_04
References:
Pre-test conditions			resource has been created in CSE1 with name {CSEBaseName1} AE1 has created a resource on registrar CSE with name {AE1} resource has been created in CSE2 with name {CSEBaseName2} AE2 has created a resource on registrar CSE with name {AE2} CSE1 is registered to CSE2 resource is created as a child of AE1 AE1 is announced on CSE2 is announced on CSE2
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a an Update Request with announcedAttribute = maxNrOfInstances
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{container} fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the UPDATE is sent from CSE1 to CSE2.
4	Mcc	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName2}/{ ContainerAnnc } fr = CSE1-ID rqi = (token-string) pc = Serialized representation of < containerAnnc > resource
5		IOP Check	Check if possible that the < containerAnnc > resource is update in CSE2 with maxNrOfInstances attributes.
6	Mcc	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of < containerAnnc > resource
7		IOP Check	CSE1 sends a UPDATED response to the AE1.
8	Mca		rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
9		IOP Check	AE1 indicates successful operation
IOP Verdict
PRO Verdict

8.3.3.4 ContainerAnnc Retrieve

Interoperability Test Description
Identifier:			TD_M2M_SH_15
Objective:			AE2 retrieves an Announced Resource
Configuration:			M2M_CFG_04
References:
Pre-test conditions:			resource has been created in CSE1 with name {CSEBaseName1} AE1 has created a resource on registrar CSE with name {AE1} resource has been created in CSE2 with name {CSEBaseName2} AE2 has created a resource on registrar CSE with name {AE2} CSE1 is registered to CSE2 resource is created as a child of AE1 AE1 is announced on CSE2 is announced on CSE2
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a Retrieve Request for a < containerAnnc >
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName2}/URI of < containerAnnc > resource fr = AE2-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict		Verify that this is a containAnnc resource
PRO Verdict

8.3.3.5 ContainerAnnc Retrieve Original

Interoperability Test Description
Identifier:			TD_M2M_SH_16
Objective:			AE2 retrieves the original resource representation of an announced resource
Configuration:			M2M_CFG_04
References:
Pre-test conditions			resource has been created in CSE1 with name {CSEBaseName1} AE1 has created a resource on registrar CSE with name {AE1} resource has been created in CSE2 with name {CSEBaseName2} AE2 has created a resource on registrar CSE with name {AE2} CSE1 is registered to CSE2 resource is created as a child of AE1 AE1 is announced on CSE2 is announced on CSE2
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a Retrieve Request to a < containerAnnc > with rcn = 7
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName2}/URI of < containerAnnc > resource fr = AE2-ID rqi = (token-string) rcn = 7 (original) pc = empty
3		IOP Check	Check if possible that the GET is sent from CSE2 to CSE1.
4	Mcc	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName1}/{ Container} fr = AE2-ID rqi = (token-string) pc = empty
5		IOP Check
6	Mcc	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
7		IOP Check	Check if possible that the response is forwarded by the registrar CSE to the AE.
8	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.3.6 ContainerAnnc Delete by updating announceTo attribute

Interoperability Test Description
Identifier:			TD_M2M_SH_21
Objective:			AE1 deletes its announced child container from CSE2
Configuration:			M2M_CFG_04
References:			10.2.13.4
Pre-test conditions			resource has been created in CSE1 with name {CSEBaseName1} AE1 has created a resource on registrar CSE with name {AE1} resource has been created in CSE2 with name {CSEBaseName2} CSE1 is registered to CSE2 AE1 is announced on CSE2 resource is created as a child of AE1 and announced on CSE2
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a an container Update Request with announceTo attribute set to NULL
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName1}/{AE1}/{container} fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the DELETE is sent from CSE1 to CSE2.
4	Mcc	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName2}/{AE1Annc}/{containerAnnc} fr = CSE1-ID rqi = (token-string)
5		IOP Check	Check if possible that the resource is deleted in CSE2
6	Mcc	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message
7		IOP Check	CSE1 sends a UPDATED response to the AE1.
8	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.3.7 ContainerAnnc Delete by deleting original resource

Interoperability Test Description
Identifier:			TD_M2M_SH_22
Objective:			AE1 deletes its announced child container from CSE2
Configuration:			M2M_CFG_04
References:			10.2.13.4
Pre-test conditions			resource has been created in CSE1 with name {CSEBaseName1} AE1 has created a resource on registrar CSE with name {AE1} resource has been created in CSE2 with name {CSEBaseName2} CSE1 is registered to CSE2 AE1 is announced on CSE2 resource is created as a child of AE1 and announced on CSE2
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a an container Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName1}/{AE1}/{container} fr = AE-ID rqi = (token-string)
3		IOP Check	Check if possible that the DELETE is sent from CSE1 to CSE2.
4	Mcc	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName2}/{AE1Annc}/{containerAnnc} fr = CSE1-ID rqi = (token-string)
5		IOP Check	Check if possible that the resource is deleted in CSE2
6	Mcc	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message
7		IOP Check	CSE1 sends a DELETE response to the AE1.
8	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.3.8 Announced attribute Create by addition to announcedAttribute attribute

Interoperability Test Description
Identifier:			TD_M2M_SH_23
Objective:			AE1 announces an announcable attribute of its child container to CSE2
Configuration:			M2M_CFG_04
References:			10.2.13.7
Pre-test conditions			resource has been created in CSE1 with name {CSEBaseName1} AE1 has created a resource on registrar CSE with name {AE1} resource has been created in CSE2 with name {CSEBaseName2} CSE1 is registered to CSE2 AE1 is announced on CSE2 resource is created as a child of AE1 and announced on CSE2
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a an Update Request with announcedAttribute attribute containing currentNrOfInstances
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName1}/{AE1}/{container} fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the UPDATE is sent from CSE1 to CSE2.
4	Mcc	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName2}/{AE1Annc}/{containerAnnc} fr = CSE1-ID rqi = (token-string) pc = Serialized representation of < containerAnnc > resource
5		IOP Check	Check if possible that the < containerAnnc > resource is updated in CSE2 with currentNrOfInstances attribute.
6	Mcc	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of < containerAnnc > resource
7		IOP Check	CSE1 sends a UPDATED response to the AE1.
8	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.3.9 Announced attribute Create by creation of a MA attribute at the original resource

Interoperability Test Description
Identifier:			TD_M2M_SH_24
Objective:			AE1 announces an MA attribute of its child container to CSE2
Configuration:			M2M_CFG_04
References:
Pre-test conditions			resource has been created in CSE1 with name {CSEBaseName1} AE1 has created a resource on registrar CSE with name {AE1} resource has been created in CSE2 with name {CSEBaseName2} CSE1 is registered to CSE2 AE1 is announced on CSE2 resource is created as a child of AE1 and announced on CSE2
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a an Update Request with labels attribute
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName1}/{AE1}/{container} fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the UPDATE is sent from CSE1 to CSE2.
4	Mcc	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName2}/{AE1Annc}/{containerAnnc} fr = CSE1-ID rqi = (token-string) pc = Serialized representation of < containerAnnc > resource
5		IOP Check	Check if possible that the < containerAnnc > resource is updated in CSE2 with labels attribute.
6	Mcc	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of < containerAnnc > resource
7		IOP Check	CSE1 sends a UPDATED response to the AE1.
8	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.3.10 Announced attribute Delete by deletion from announcedAttribute attribute

Interoperability Test Description
Identifier:			TD_M2M_SH_25
Objective:			AE1 de-announces an announcable attribute of its child container to CSE2
Configuration:			M2M_CFG_04
References:			10.2.13.8
Pre-test conditions			resource has been created in CSE1 with name {CSEBaseName1} AE1 has created a resource on registrar CSE with name {AE1} resource has been created in CSE2 with name {CSEBaseName2} CSE1 is registered to CSE2 AE1 is announced on CSE2 resource is created as a child of AE1 and announced on CSE2 with currentNrOfInstances attribute announced
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a Update Request with announcedAttribute attribute set to NULL
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName1}/{AE1}/{container} fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the UPDATE is sent from CSE1 to CSE2.
4	Mcc	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName2}/{AE1Annc}/{containerAnnc} fr = CSE1-ID rqi = (token-string) pc = Serialized representation of < containerAnnc > resource
5		IOP Check	Check if possible that the < containerAnnc > resource is updated in CSE2 with no currentNrOfInstances attribute.
6	Mcc	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of < containerAnnc > resource
7		IOP Check	CSE1 sends a UPDATED response to the AE1.
8	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.3.11 Announced attribute Delete by deletion of a MA attribute at the original resource

Interoperability Test Description
Identifier:			TD_M2M_SH_26
Objective:			AE1 de-announces an MA attribute (conditionally mandatory) of its child container to CSE2
Configuration:			M2M_CFG_04
References:
Pre-test conditions			resource has been created in CSE1 with name {CSEBaseName1} AE1 has created a resource on registrar CSE with name {AE1} resource has been created in CSE2 with name {CSEBaseName2} CSE1 is registered to CSE2 AE1 is announced on CSE2 resource is created as a child of AE1 and announced on CSE2 with labels attribute announced
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a Update Request with labels attribute set to NULL
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName1}/{AE1}/{container} fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the UPDATE is sent from CSE1 to CSE2.
4	Mcc	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName2}/{AE1Annc}/{containerAnnc} fr = CSE1-ID rqi = (token-string) pc = Serialized representation of < containerAnnc > resource
5		IOP Check	Check if possible that the < containerAnnc > resource is updated in CSE2 with no labels attribute.
6	Mcc	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of < containerAnnc > resource
7		IOP Check	CSE1 sends a UPDATED response to the AE1.
8	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.4 Single Hop operations

8.3.4.1 Create

Interoperability Test Description
Identifier:			TD_M2M_SH_17
Objective:			AE creates a resource in each group member, where some memberIDs are on a remoteCSE
Configuration:			M2M_CFG_08
References:			oneM2M TS-0001 [1], clause 10.2.7.7 oneM2M TS-0004 [2], clause 7.4.15.2, 7.4.15.3
Pre-test conditions			Two or more resources of type exist on the member hosting CSE A group exists containing these two members of type
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Create Request to create in each group member
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/{group}/fopt fr = AE-ID rqi = (token-string) ty = 4 (contentInstance) pc = Serialized representation of resource
3		IOP Check	Check if possible that the request is forwarded by the registrar/Group Hosting CSE to the Member Hosting CSE.
4	Mcc	PRO Check Primitive	op = 1 (Create) to = {MemberCSEBaseName}/{subgroupId}/fopt or {MemberCSEBaseName}/{memberId} fr = AE-ID rqi = (token-string) gid = (grpId-token-string) ty = 4 (contentInstance) pc = Serialized representation of resource
5		IOP Check	Check if possible that the resource is created in the Member Hosting CSE.
6	Mcc	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message gid = (grpId-token-string) same as received in request message pc = Serialized representation of resource or
7		IOP Check	Check that the response is aggregated by the group hosting CSE and sent to the AE.
8	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.4.2 Retrieve

Interoperability Test Description
Identifier:			TD_M2M_SH_18
Objective:			AE retrieves a resource from each group member, where some memberIDs are on a remoteCSE
Configuration:			M2M_CFG_08
References:
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request to the fanoutPoint of resource
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{group}/fopt fr = AE-ID rqi = (token-string)
3		IOP Check	Check if possible that the request is forwarded by the registrar/group hosting CSE to the Member Hosting CSE.
4	Mcc	PRO Check Primitive	op = 2 (Retrieve) to = {MemberCSEBaseName}/{subgroupId}/fopt or {MemberCSEBaseName}/{memberId} fr = AE-ID rqi = (token-string) gid = (grpId-token-string)
5	Mcc	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message gid = (grpId-token-string) same as received in request message pc = Serialized representation of resource
6		IOP Check	Check that the response is aggregated by the group hosting CSE and sent to the AE.
7	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of
8		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.4.3 Update

Interoperability Test Description
Identifier:			TD_M2M_SH_19
Objective:			AE updates a resource in each group member, where some memberIDs are on a remoteCSE
Configuration:			M2M_CFG_08
References:
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Update Request to the fanoutPoint of resource to lifetime of the resource.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{group}/fopt fr = AE-ID rqi = (token-string) pc = Serialized representation of resource
3		IOP Check	Check if possible that the request is forwarded by the registrar/group hosting CSE to the Member Hosting CSE.
4	Mcc	PRO Check Primitive	op = 3 (Update) to = {MemberCSEBaseName}/{subgroupId}/fopt or {MemberCSEBaseName}/{memberId} fr = AE-ID rqi = (token-string) pc = Serialized representation of resource
5		IOP Check	Check if possible that the resource is updated in the Hosting CSE.
6	Mcc	PRO Check Primitive	rsc = 2004 (CHANGED) rqi = (token-string) same as received in request message gid = (grpId-token-string) same as received in request message pc = Serialized representation of resource or
7		IOP Check	Check that the response is aggregated by the group hosting CSE and sent to the AE.
8	Mca	PRO Check Primitive	rsc = 2004 (CHANGED) rqi = (token-string) same as received in request message pc = Serialized representation of
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.3.4.4 Delete

Interoperability Test Description
Identifier:			TD_M2M_SH_20
Objective:			AE deletes a resource from each group member, where some memberIDs are on a remoteCSE
Configuration:			M2M_CFG_08
References:
Pre-test conditions:			Two or more resources of type exist on the member hosting CSE Each has at least 1 A group exists containing these two members of type
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Delete 'oldest' Request to the fanoutPoint of resource
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/{group}/fopt/ol fr = AE-ID rqi = (token-string)
3		IOP Check	Check if possible that the request is forwarded by the registrar CSE to the Hosting CSE.
4	Mcc	PRO Check Primitive	op = 4 (Delete) to = {MemberCSEBaseName}/{subgroupId}/fopt/ol or {MemberCSEBaseName}/{memberId}/ol fr = AE-ID rqi = (token-string) gid = (grpId-token-string)
5		IOP Check	Check if possible that the resource is deleted in the Hosting CSE.
6	Mcc	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message gid = (grpId-token-string) same as received in request message
7		IOP Check	Check that the response is aggregated by the group hosting CSE and sent to the AE.
8	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = Serialized representation of
9		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.4 Security management

8.4.1 Secure AE Registration

8.4.1.1 PSK Security Association Establishment Framework

Interoperability Test Description
Identifier:			TD_M2M_SE_01
Objective:			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.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.2.2.1 oneM2M TS-0001 [1], clauses 9.6.29, 9.6.19, 9.16.20
Pre-test conditions:			AE and Registrar CSE are pre-Provisioned with Kpsa = 123456,KpsaId = test@onem2m.com and Cipher Suites = TLS_PSK_WITH_AES_128_CBC_SHA256, TLS_PSK_WITH_AES_128_CCM_8 Registrar CSE is provisioned with Service Subscribed Profile and Service Subscribed Node Resources. Service Subscribed Node contains csi and rlk < URI of serviceSubscribedAppRule > attributes. Registrar CSE is configured with resource having a CredentialD, APP-ID and AE-ID with the following values: 00-test@onem2m.com APP01 AE-ID
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a primitive to the Registrar CSE
2	Mca	PRO Check Primitive	Security Association Establishment
		PRO Check TCP	TLS Handshake Cipher Suite:TLS_PSK_WITH_AES_128_CBC_SHA256 Version: TLS v1.2 KpsaId = test@onem2m.com
		PRO Check UDP	DTLS Handshake Cipher Suite:TLS_PSK_WITH_AES_128_CCM_8 Version: DTLS v1.2 KpsaId = test@onem2m.com
3		IOP Check	Check if possible that Handshake was successful
4	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 2 (AE) pc = Serialized representation of resource
5		IOP Check	Check that APP-ID, AE-ID, Credential ID are in Check if possible that the resource is created in registrar CSE.
6	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
7		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.4.2 Authentication

8.4.2.1 Authentication using the Provisioned Symmetric Key Security Association Establishment Framework with TLS

Interoperability Test Description
Identifier:			TD_M2M_SE_ 02
Objective:			AE establishes mutual authentication with the Registrar CSE using Provisioned Symmetric Key Security Association Establishment Framework.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.2.2.1
Pre-test conditions:			AE and Registrar CSE are pre-Provisioned with Kpsa = 123456,KpsaId = test@onem2m.com and Cipher Suites = TLS_PSK_WITH_AES_128_CBC_SHA256
Test Sequence
Step	RP	Type	Description
1		Stimulus	The TLS client on AE sends a Client Hello Handshake message
2	Mca	PRO Check TCP	Client Hello handshake message Handshake Type = 0x01 (Client Hello) Cipher Suite:TLS_PSK_WITH_AES_128_CBC_SHA256 Version: TLS v1.2
3	Mca	PRO Check TCP	Server Hello handshake message Handshake Type = 0x02 (Server Hello) Cipher Suite:TLS_PSK_WITH_AES_128_CBC_SHA256 Version: TLS v1.2 Server Hello Done handshake message Handshake Type = 0x0e (Server Hello Done)
4		Stimulus	The TLS client on AE sends Client Key Exchange, Change Cipher Spec, Finished messages
5	Mca	PRO Check TCP	The TLS client Key Exchange handshake message Handshake Type = 0x10 (Client Key Exchange) psk_identity = test@onem2m.com Version: TLS v1.2 Client Change Cipher Spec message Content type = 0x14 (Change Cipher Spec) Client Finished handshake message Handshake Type = 0x14 (Client Finished) Version: TLS v1.2
6		IOP Check	Check that The TLS server authenticated the Client by validating Verify Data Check that AE associated the established TLS session with the CSE-ID
7	Mca	PRO Check TCP	Server New Session Ticket handshake message Handshake Type = 0x04 (New Session Ticket) psk_identity = test@onem2m.com Version: TLS v1.2 Server Change Cipher Spec message Content type = 0x14 (Change Cipher Spec) Server Finished handshake message Handshake Type = 0x14 (Client Finished) Version: TLS v1.2
8		IOP Check	Check that The TLS client authenticated the Server by validating Verify Data
IOP Verdict
PRO Verdict

8.4.2.2 Authentication using the Certificate-Based Security Association Establishment Framework with TLS

Interoperability Test Description
Identifier:			TD_M2M_SE_ 03
Objective:			AE establishes mutual authentication with the Registrar CSE using Certificate-Based Security Association Establishment Framework.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.2.2.2
Pre-test conditions:			The Registrar CSE uses the CSE-ID certificate signed by a root CA certificate AE uses the AE-ID certificate signed by a root CA certificate Cipher Suite = TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Test Sequence
Step	RP	Type	Description
1		Stimulus	The TLS client on AE sends a client Hello Handshake message
2	Mca	PRO Check TCP	The TLS client sends a Hello handshake message to the TLS server Handshake Type = 0x01 (Client Hello) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Version: TLS v1.2
3	Mca	PRO Check TCP	The TLS server sends Hello, Certificate, Key Exchange, Certificate Request, Hello Done messages to the TLS client Server Hello handshake message Handshake Type = 0x02 (Server Hello) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Version: TLS v1.2 Server Certificate handshake message Handshake Type = 0x0b (Server Certificate) Certificate: the Registrar CSE certificate Server Key Exchange handshake message Handshake Type = 0x0c (Server Key Exchange) Public key: ECDHE generated key Server Certificate Request handshake message Handshake Type = 0x0d (Certificate Request) Server Hello Done handshake message Handshake Type = 0x0e (Server Hello Done)
4		IOP Check	The TLS client on AE checks if the certificate of the Server is valid
5		Stimulus	The TLS client on AE sends Certificate, Client Key exchange, Certificate Verify, Change Cipher Spec, Finished messages
6	Mca	PRO Check TCP	Client Certificate handshake message Handshake Type = 0x0b (Client Certificate) Certificate: AE certificate Client Key Exchange message Handshake Type = 0x10 (Client Key Exchange) Public key: ECDHE generated key Client Certificate Verify message Handshake Type = 0x0f (Certificate Verify) Client Change Cipher Spec message Content type = 0x14 (Change Cipher Spec) Client Finished handshake message Handshake Type = 0x14 (Client Finished)
7		IOP Check	The TLS server on CSE checks if the certificate of the Client is valid
8	Mca	PRO Check TCP	The TLS server sends New Session Ticket, Change Cipher Spec, and Finished messages to the TLS client Server New Session Ticket message Handshake Type = 0x04 (New Session Ticket) Server Change Cipher Spec message Content type = 0x14 (Change Cipher Spec) Server Finished message Handshake Type = 0x14 (Client Finished) Version: TLS v1.2
9		IOP Check	Check that The TLS client authenticated the Server by validating Verify Data
IOP Verdict
PRO Verdict

8.4.3 Authorization

8.4.3.1 Authorization using selfPrivileges

Interoperability Test Description
Identifier:			TD_M2M_SE_ 04
Objective:			AE accesses resource using its selfPrivileges credentials
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1] clause 9.6.2.0
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created an resource on registrar CSE with name {AE} accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName} selfPrivileges attribute of {accessControlPolicyName} contains the following access control tuple: acor = AE-ID acop = 63
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an accessControlPolicy Retrieve Request
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{AE}/{accessControlPolicyName} fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.4.3.2 Authorization using accessControlPolicy privileges

Interoperability Test Description
Identifier:			TD_M2M_SE_ 05
Objective:			AE accesses resource using its accessControlPolicyIDs attribute
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1] clause 9.6.2.0
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created an resource on registrar CSE with name {AE} accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName} accessControlPolicyIDs attribute of {AE} is set to resource id of {accessControlPolicyName} privileges attribute of {accessControlPolicyName} contains the following access control tuple: acor = AE-ID acop = 34
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an AE Retrieve Request
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{AE} fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
5		Stimulus	AE is requested to send an AE Delete Request
6	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/{AE} fr = AE-ID rqi = (token-string) pc = empty
7	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 4103 (ACCESS_DENIED) rqi = (token-string) same as received in request message pc = empty
8		IOP Check	Check if possible that the resource has not been removed in registrar CSE.
9		IOP Check	AE indicates unsuccessful operation (Delete error - no privilege)
IOP Verdict
PRO Verdict

8.4.3.3 Authorization using default access privileges (owner is configured)

Interoperability Test Description
Identifier:			TD_M2M_SE_ 06
Objective:			AE accesses resource using default access privileges
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1] clause 9.6.2.0
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created an resource on registrar CSE with name {AE} resource has been created in registrar CSE under resource with name {containerName} accessControlPolicyIDs attribute of {containerName} is NULL owner attribute of {containerName} = AE-ID
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a container Retrieve Request
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{AE}/{containerName} fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
5		Stimulus	AE2 is requested to send a container Retrieve Request
6	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{AE}/{containerName} fr = AE2-ID rqi = (token-string) pc = empty
7	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 4103 (ACCESS_DENIED) rqi = (token-string) same as received in request message pc = empty
8		IOP Check	AE indicates unsuccessful operation (Retrieve error - no privilege)
IOP Verdict
PRO Verdict

8.4.3.4 Authorization using default access privileges (owner is not configured)

Interoperability Test Description
Identifier:			TD_M2M_SE_ 07
Objective:			AE accesses resource using default access privileges
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1] clause 9.6.2.0
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created an resource on registrar CSE with name {AE} resource has been created in registrar CSE under resource with name {containerName} accessControlPolicyIDs attribute of {containerName} is NULL owner attribute of {containerName} is not set creator attribute of {containerName} = AE-ID
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a ContainerRetrieve Request
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{AE}/{containerName} fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
5		Stimulus	AE2 is requested to send a Container Retrieve Request
6	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{AE}/{containerName} fr = AE2-ID rqi = (token-string) pc = empty
7	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 4103 (ACCESS_DENIED) rqi = (token-string) same as received in request message pc = empty
8		IOP Check	AE indicates unsuccessful operation (Retrieve error - no privilege)
IOP Verdict
PRO Verdict

8.4.3.5 Direct Dynamic Authorization

Interoperability Test Description
Identifier:			TD_M2M_SE_ 08
Objective:			AE accesses resource using Direct Dynamic Authorization
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [1] clause 7.3.2.2
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created an resource on registrar CSE with name {AE} resource has been created in registrar CSE under resource with name {containerName} Arbitrary set of resources are linked to the {containerName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Container Retrieve Request
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{AE}/{containerName} fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that Tokens or Token-Ids have not been included in the request
4		IOP Check	Check if possible that CSE selected a DAS Server based on accessControlRules linked to the requested resource
5	Mca	PRO Check Primitive	Registrar CSE sends a Notify request to the DAS server: op = 6 (Notify) pc: securityInfo: Direct Dynamic Authorization Originator = AE-ID Originator Resource Type = 3 (Container) Operation = 2 (Retrieve)
6		IOP Check	Check that if the DAS Server issued token(s), they conform to the Token structure (TS-0003, clause 7.3.2.4)
7	Mca	PRO Check Primitive	The DAS server responds to the Registrar CSE: op = 6 (Notify response) pc: securityInfo: Direct Dynamic Authorization (optional) token(s): authorization token(s) (optional) dynamicACPInfo: information for creating accessControlPolicy dynamicaly
8		IOP Check	Check that if token(s) present in response content, the token is validated in the Registrar CSE successfully (TS-0003, clause 7.3.2.5)
9		IOP Check	Check that if dynamicACPInfo present in response content, the Registrar CSE created resource matching the dynamicACPInfo.
10	Mca	PRO Check Primitive	If access is granted, the Registrar CSE responds to the AE: rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource If access is not granted, the Registrar CSE responds to the AE: rsc = 4103 (ACCESS_DENIED) rqi = (token-string) same as received in request message pc = empty
11		IOP Check	If access is granted, AE indicates successful operation, otherwise AE indicates unsuccessful operation (Retrieve error - no privilege)
IOP Verdict
PRO Verdict

8.4.3.6 Indirect Dynamic Authorization

Interoperability Test Description
Identifier:			TD_M2M_SE_ 09
Objective:			AE accesses resource using Indirect Dynamic Authorization
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [1] clause 7.3.2.3
Pre-test conditions:			CSEBase resource has been created in registrar CSE with name {CSEBaseName} AE has created an resource on registrar CSE with name {AE} resource has been created in registrar CSE under resource with name {containerName} Arbitrary set of resources are linked to the {containerName}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Container Retrieve Request
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{AE}/{containerName} fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc = 4103 (ACCESS_DENIED) rqi = (token-string) same as received in request message tqf: DAS Server PoA pc = empty
4		IOP Check	AE indicates unsuccessful operation (Retrieve error - no privilege)
5		Stimulus	AE is requested to send a token request to the DAS using original request data. AuthorSignIndicator parameter is optional.
6		IOP Check	Check that if the DAS Server issued token(s), they conform to the Token structure (TS-0003, clause 7.3.2.4)
7		Stimulus	AE is requested to send a Container Retrieve Request with additional token(s) information
8	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{AE}/{containerName} fr = AE-ID rqi = (token-string) (optional) tkns: token(s) if ESData-protected Token(s) are provided (optional) tids: token Id(s) if ESData-protected Token(s) are not provided pc = empty
9	Mca	PRO Check Primitive	If the request in step 7 includes token Id(s), the Registrar CSE sends a Notify request to the DAS Server: op = 6 (Notify) securityInfo Type: Indirect Dynamic Authorization pc: tids: token Id(s)
10	Mca	PRO Check Primitive	The DAS server responds to the Registrar CSE: op = 6 (Notify response) pc: securityInfo: Indirect Dynamic Authorization token(s): authorization token(s) corresponding token Id(s)
12		IOP Check	Check that the token(s) are validated in the Registrar CSE successfully (TS-0003, clause 7.3.2.5)
13		IOP Check	If access is granted, AE indicates successful operation, otherwise AE indicates unsuccessful operation (Retrieve error - no privilege)
14	Mca	PRO Check Primitive	If access is granted, the Registrar CSE responds to the AE: rsc = 2000 (OK) ltids: Local-Token-ID(s) tkns: Token(s) rqi = (token-string) same as received in request message pc = Serialized representation of resource If access is not granted, the Registrar CSE responds to the AE: rsc = 4103 (ACCESS_DENIED) rqi = (token-string) same as received in request message pc = empty
15		IOP Check	If access is granted, AE indicates successful operation, otherwise AE indicates unsuccessful operation (Retrieve error - no privilege)
IOP Verdict
PRO Verdict

8.4.4 Key provisioning management

8.4.4.1 MEF Handshake Procedure using certificates

Interoperability Test Description
Identifier:			TD_M2M_SE_10
Objective:			A MEF Handshake procedure establishes a mutually authenticated TLS session for protecting the communication between an MEF Client and MEF using pre-provisioned certificates.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.3.5.2.2
Pre-test conditions:			The MEF Client and MEF have been provisioned with certificates and Cipher Suite = TLS_PSK_WITH_AES_128_CBC_SHA256
Test Sequence
Step	RP	Type	Description
1		Stimulus	MEF Client and MEF establish the TLS or DTLS session using the certificate-based TLS handshake
2		IOP Check	Check that MEF Handshake is successful Check that the MEF's certificate is verified against the set of provisioned MEF certificate trust anchors (as described in TS-0003 [12])
IOP Verdict
PRO Verdict

8.4.4.2 MEF Handshake Procedure using Master Credentials

Interoperability Test Description
Identifier:			TD_M2M_SE_ 11
Objective:			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.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.3.5.2.2
Pre-test conditions:			The MEF Client and MEF have been provisioned with Kpm = 123456, KpmID = psk_identity, and Cipher Suites = TLS_PSK_WITH_AES_128_CBC_SHA256, TLS_PSK_WITH_AES_128_CCM_8
Test Sequence
Step	RP	Type	Description
1		Stimulus	MEF Client and MEF establish the TLS or DTLS session using the certificate-based TLS handshake
2	Mca	PRO Check TCP/UDP	psk_identity = test@onem2m.com psk = 123456
3		IOP Check	Check that MEF Handshake is successful

IOP Verdict
PRO Verdict

8.4.4.3 MEF Client Registration Procedure

Interoperability Test Description
Identifier:			TD_M2M_SE_ 12
Objective:			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
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.3.5.2.3
Pre-test conditions:			The MEF Client, and MEF have been provisioned with the parameters described in TS-0003 [12], clause 8.3.7
Test Sequence
Step	RP	Type	Description
1		Stimulus	The MEF Client establishes a TLS (or DTLS) connection with the MEF by performing the MEF Handshake procedure
2		Stimulus	The MEF Client sends a MEF Client Registration request
3	Mca	PRO Check TCP/UDP	MEF-FQDN = FQDN of the MEF adminFQDN = FQDN of the administrating stakeholder expirationTime = time when the registration shall expire
4		IOP Check	Check if possible that MEF has created a MEF Client Registration record
5	Mca	PRO Check TCP/UDP	The MEF sends a MEF Client Registration response MEFClientRegID = Identifier for the new MEF Client Registration expirationTime = time when the MEF Client Registration record shall expire MEF Client ID = Identifier of the MEF Client adminFQDN = FQDN of the administrating stakeholder
6		IOP Check	Check if possible that MEF Client has stored parameters provided by the MEF
IOP Verdict
PRO Verdict

8.4.4.4 MEF Client Configuration Retrieval Procedure

Interoperability Test Description
Identifier:			TD_M2M_SE_ 13
Objective:			The MEF Client retrieves MEF Client Configurations provided by the administrating stakeholder to the MEF.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.3.5.2.4
Pre-test conditions:			The MEF Client has previously performed the MEF Client Registration procedure to create the MEF Client Registration record. The MEF Client Registration record is not expired.
Test Sequence
Step	RP	Type	Description
1		Stimulus	The MEF Client establishes a TLS (or DTLS) connection with the MEF by performing the MEF Handshake procedure
2		Stimulus	The MEF Client sends a MEF Client Configuration Retrieval request
3	Mca	PRO Check TCP/UDP	MEF-FQDN = FQDN of the MEF, from MEF Instruction Configuration MEFClientRegID = Identifier for the MEF Client registration record being updated
4	Mca	PRO Check TCP/UDP	The MEF sends a MEF Client Configuration Retrieval response MEFClientCfg = MEF Client Configuration currently associated with the identified MEF Client registration record
IOP Verdict
PRO Verdict

8.4.4.5 MEF Client Configuration Update Procedure

Interoperability Test Description
Identifier:			TD_M2M_SE_ 14
Objective:			MEF Client updates the MEF Client registration by any combination of extending the expirationTime of the MEF Client Registration record or updating the labels.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.3.5.2.5
Pre-test conditions:			The MEF Client has previously performed the MEF Client Registration procedure to create the MEF Client Registration record. The MEF Client Registration record is not expired.
Test Sequence
Step	RP	Type	Description
1		Stimulus	The MEF Client establishes a TLS (or DTLS) connection with the MEF by performing the MEF Handshake procedure
2		Stimulus	The MEF Client shall send a MEF Client Registration Update request
3	Mca	PRO Check TCP/UDP	MEF-FQDN = FQDN of the MEF MEFClientRegID = Identifier for the MEF Client registration record being updated (optional) expirationTime = time when the MEF Client registration record shall expire (optional) labels = labels to aid discovery of the MEF Client registration record NOTE: At least one of expirationTime and labels shall be included.
4		IOP Check	Check if possible that MEF has updated the MEF Client Registration record with the proposed values
5	Mca	PRO Check TCP/UDP	The MEF sends a MEF Client Registration Update response (optional) expirationTime = time when the MEF Client registration record shall expire (optional) labels = labels to aid discovery of the MEF Client registration record NOTE: The response only includes expirationTime and/or labels if those parameters were present in the corresponding request.
6		IOP Check	Check if possible that MEF Client has stored parameters provided by the MEF
IOP Verdict
PRO Verdict

8.4.4.6 MEF Client De-Registration Procedure

Interoperability Test Description
Identifier:			TD_M2M_SE_ 15
Objective:			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
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.3.5.2.6
Pre-test conditions:			The MEF Client has previously performed the MEF Client Registration procedure to create the MEF Client Registration record. The MEF Client Registration record is not expired.
Test Sequence
Step	RP	Type	Description
1		Stimulus	The MEF Client establishes a TLS (or DTLS) connection with the MEF by performing the MEF Handshake procedure
2		Stimulus	The MEF Client sends a MEF Client De-Registration request
3	Mca	PRO Check TCP/UDP	MEF-FQDN = FQDN of the MEF MEFClientRegID = Identifier for the MEF Client Registration record being ended
4		IOP Check	Check if possible that MEF has deleted the information associated with the identified MEF Client Registration record
5		IOP Check	The MEF sends a MEF Client Registration Update response. The MEF Client indicates the success of the operation.
IOP Verdict
PRO Verdict

8.4.4.7 MEF Key Registration Procedure

Interoperability Test Description
Identifier:			TD_M2M_SE_ 16
Objective:			Source MEF Client establishes a symmetric key with the MEF which can be retrieved for use by one or more Target MEF Clients
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.3.5.2.7
Pre-test conditions:			The Source MEF Client is provided with (or has otherwise determined) the information in the MEF Key Registration Configuration (TS-0003 [12], clause 8.3.7.3) The Source MEF Client has performed the MEF Client Registration procedure (TS-0003 [12], clause 8.3.5.2.3) with the MEF for the administrating stakeholder identified in the MEF Key Registration Configuration
Test Sequence
Step	RP	Type	Description
1		Stimulus	The Source MEF Client establishes a TLS (or DTLS) connection with the MEF by performing the MEF Handshake procedure
2		Stimulus	The MEF Client sends a MEF Key Registration request
3	Mca	PRO Check TCP/UDP	MEF-FQDN = FQDN of the MEF expirationTime = time when the MEF Client Registration shall expire adminFQDN = Identifier for the administrating stakeholder SUID = The Security Usage Identifier limiting the security feature in which the symmetric key may be used (optional) targetIDs = list of identifiers for the initial set of Target MEF Clients authorized to retrieve the symmetric key (optional) Key Value = output symmetric key value which is self-generated by the Source MEF Client
4		IOP Check	If the MEF Key Registration request included Key Value, check that MEF has stored the value. Otherwise, MEF generates Key Value from the (D)TLS session using TLS Key Export.
5	Mca	PRO Check TCP/UDP	The MEF sends a MEF Key Registration response RelativeKeyID = the relative part of the Key Identifier associated with the Key Registration expirationTime = time when the MEF Client Registration record shall expire Source MEF Client ID = Identifier of the Source MEF Client adminFQDN = FQDN of the administrating stakeholder SUID = the Security Usage Identifier limiting the security feature in which the symmetric key may be used targetIDs =list of identifiers for the initial set of Target MEF Clients authorized to retrieve the symmetric key
6		IOP Check	Check if possible that the Source MEF Client and MEF has stored the output symmetric key value and corresponding Key Identifier
IOP Verdict
PRO Verdict

8.4.4.8 MEF Key Retrieval Procedure

Interoperability Test Description
Identifier:			TD_M2M_SE_ 17
Objective:			The Target MEF Client to retrieve the Key Value from a MEF corresponding to a RelativeKeyID received by the Target MEF Client
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.3.5.2.8
Pre-test conditions:			The Target MEF Client has performed the MEF Client Credential Configuration with the MEF, including configuration of the MEF Key Retrieval URI The Source MEF Client has performed the MEF Key Registration procedure with the MEF, resulting in a registered Key Value and assigned RelativeKeyID for a specific administrating stakeholder and Security Usage Identifier The Target MEF Client received a Key Identifier from the Initiating-MEF Client in a security feature with the SUID which the Source MEF Client provided to the MEF during the MEF Key Registration procedure The Target MEF Client may expect that it is authorized to obtain the corresponding output symmetric key value.
Test Sequence
Step	RP	Type	Description
1		Stimulus	The MEF Client establishes a TLS (or DTLS) connection with the MEF by performing the MEF Handshake procedure
2		Stimulus	The MEF Client sends a MEF Key Retrieval request
3	Mca	PRO Check Primitive	RelativeKeyID = The relative part of the Key Identifier received from the Source MEF Client in a security feature
4	Mca	PRO Check TCP/UDP	The MEF sends a MEF Key Retrieval response expirationTime = time when the Key Registration shall expire Source MEF Client ID = Identifier of the Source MEF Client adminFQDN = Identifier for the administrating stakeholder SUID = the Security Usage Identifier limiting the security feature in which the symmetric key may be used Key Value = The registered value of the output symmetric key
IOP Verdict
PRO Verdict

8.4.4.9 MEF Key Registration Update Procedure

Interoperability Test Description
Identifier:			TD_M2M_SE_ 18
Objective:			MEF Client updates the MEF Client registration by any combination of extending the expirationTime of the MEF Client Registration record or updating the labels.
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.3.5.2.9
Pre-test conditions:			The MEF Client has previously performed the MEF Key Registration procedure to create the key registration The key registration is not expired
Test Sequence
Step	RP	Type	Description
1		Stimulus	The MEF Client establishes a TLS (or DTLS) connection with the MEF by performing the MEF Handshake procedure
2		Stimulus	The MEF Client shall send a MEF Key Registration Update request
3	Mca	PRO Check TCP/UDP	MEF-FQDN = FQDN of the MEF RelativeKeyID = the relative part of the Key Identifier associated with the Key Registration (optional) expirationTime = time when the Key Registration shall expire (optional) labels = labels to aid discovery of the registered key (optional) targetIDs = proposed list of identifiers for the set of Target MEF Clients authorized to retrieve the symmetric key NOTE: At least one of expirationTime, labels or targetIDs shall be included.
4		IOP Check	Check if possible that MEF has updated the metadata with the proposed values
5	Mca	PRO Check TCP/UDP	The MEF sends a MEF Key Registration Update response (optional) expirationTime = current time when the key registration shall expire (optional) labels = Updated list of labels to aid discovery of the Key Registration, if any (optional) targetIDs = current list of identifiers for the initial set of Target MEF Clients authorized to retrieve the symmetric key NOTE: The response includes only those parameters that were present in the corresponding request.
IOP Verdict
PRO Verdict

8.4.4.10 MEF Key De-Registration Procedure

Interoperability Test Description
Identifier:			TD_M2M_SE_ 19
Objective:			Source MEF Client requests the MEF to stop distributing the registered key
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.3.5.2.10
Pre-test conditions:			The MEF Client has previously performed the MEF Key Registration procedure to create the key registration. The key registration is not expired.
Test Sequence
Step	RP	Type	Description
1		Stimulus	The MEF Client establishes a TLS (or DTLS) connection with the MEF by performing the MEF Handshake procedure
2		Stimulus	The MEF Client sends a MEF Key De-Registration request
3	Mca	PRO Check TCP/UDP	MEF-FQDN = FQDN of the MEF RelativeKeyID = the relative part of the Key Identifier associated with the Key Registration
4		IOP Check	Check if possible that MEF has deleted the information associated with the identified key registration
5		IOP Check	The MEF sends a MEF Client De-Registration response. The MEF client indicates success of the operation.
IOP Verdict
PRO Verdict

8.4.5 End-to-End security management

8.4.5.1 End-to-End Security of Primitives (ESPrim) Architecture

Interoperability Test Description
Identifier:			TD_M2M_SE_ 20
Objective:			AE sends an arbitrary request primitive inside of ESPrim Object to CSE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [12], clause 8.4.2
Pre-test conditions:			AE and CSE has established a secure ESPrim connection, so that both are able to extract ESPrim Objects sent from each other AE has produced an ESPrim Object from the serialization of the arbitrary request primitive
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a NOTIFY Request Message with ESPrim Object
2	Mca	PRO Check Primitive	op = 5 (Notify) to = {CSEBaseName} from = AE-ID rqi = (token-string) pc: {seci: {sit = "esprimObject ", epo: serialized ESPrim Object }}
3		IOP Check	Check if possible that the CSE successfully extracted the inner request primitive. Check if possible that the CSE successfully processed the inner request primitive.
4	Mca	PRO Check Primitive	The CSE sends a NOTIFY response to the AE op = 5 (Notify) to = AE-ID from = CSE-ID rqi = (token-string) pc: {seci: {sit = "esprimObject ", epo: serialized ESPrim Object }}
5		IOP Check	Check that the AE successfully extracted the inner response primitive. Check that the AE successfully processed the inner response primitive.
IOP Verdict
PRO Verdict

8.4.5.2 End-to-End Certificate-based Key Establishment (ESCertKE)

Interoperability Test Description
Identifier:			TD_M2M_SE_21
Objective:			AE establishes a connection with the Registrar CSE using pairwiseE2EKey
Configuration:			M2M_CFG_01
References:			oneM2M TS-0003 [Error! Reference source not found. ], clause 8.7.2
Pre-test conditions:			Both the Registrar CSE and AE support ESCertKE and are provisioned with private key and certificates. Both entities are configured with the information needed for the authentication and identification. Cipher Suite = TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends an ESCertKE Message 1 in Notify request
2	Mca	PRO Check Primitive	op = 5 (Notify) to = {CSEBaseName} from = AE-ID rqi = (token-string) pc: {seci: {sit = "escertkeMessage",eckm: ESCertKE Message 1 }} ESCertKE Message 1 includes TLS a Client Hello handshake message: Handshake Type = 0x01 (Client Hello) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Version: TLS v1.2
3	Mca	PRO Check Primitive	The Registrar CSE sends an ESCertKE Message 2 in Notify response op = 5 (Notify) to = AE-ID from = CSE-ID rqi = (token-string) pc: {seci: {sit = "escertkeMessage",eckm: ESCertKE Message 2 }} ESCertKE Message 2 includes Server Hello, Certificate, Server Key Exchange, Certificate Request, Server Hello Done messages Server Hello handshake message Handshake Type = 0x02 (Server Hello) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Version: TLS v1.2 Certificate handshake message Handshake Type = 0x0b (Server Certificate) Certificate: the Registrar CSE certificate Server Key Exchange handshake message Handshake Type = 0x0c (Server Key Exchange) Public key: ECDHE generated key Certificate Request handshake message Handshake Type = 0x0d (Certificate Request) Server Hello Done handshake message Handshake Type = 0x0e (Server Hello Done)
4		IOP Check	The TLS client on AE checks if the certificate of the Server is valid
5		Stimulus	AE sends an ESCertKE Message 3 in Notify request
6	Mca	PRO Check Primitive	op = 5 (Notify) to = {CSEBaseName} from = AE-ID rqi = (token-string) pc: {seci: {sit = "escertkeMessage",eckm: ESCertKE Message 3 }} ESCertKE Message 3 includes Certificate, Client Key exchange, Certificate Verify, Change Cipher Spec, Finished messages Certificate handshake message Handshake Type = 0x0b (Client Certificate) Certificate: AE certificate Client Key Exchange message Handshake Type = 0x10 (Client Key Exchange) Public key: ECDHE generated key Certificate Verify message Handshake Type = 0x0f (Certificate Verify) Change Cipher Spec message Content type = 0x14 (Change Cipher Spec) Finished handshake message Handshake Type = 0x14 (Client Finished)
7		IOP Check	The TLS server on CSE checks if the certificate of the Client is valid
8	Mca	PRO Check Primitive	The Registrar CSE sends an ESCertKE Message 2 in Notify response op = 5 (Notify) to = AE-ID from = CSE-ID rqi = (token-string) pc: {seci: {sit = "escertkeMessage",eckm: ESCertKE Message 4 }} ESCertKE Message 4 includes Change Cipher Spec, and Finished messages Server Change Cipher Spec message Content type = 0x14 (Change Cipher Spec) Server Finished message Handshake Type = 0x14 (Client Finished)
9		IOP Check	Check that The TLS client authenticated the Server by validating Verify Data
10		IOP Check	Check that AE and the Registrar CSE has generated and cached a pairwiseE2EKey
IOP Verdict
PRO Verdict

8.5 HAIM Device Model

8.5.1 HAIM Light Device Creation

Interoperability Test Description
Identifier:			TD_M2M_NH_102
Objective:			AE1 creates a HAIM Light Device Model
Configuration:			M2M_CFG_10
References:			oneM2M TS-0023 [14], clause 5.5.27
Pre-test conditions:			AE1 has created an application resource on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 sends a request to create a for deviceLight
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) ty = 28 (flexContainer) pc = Serialized representation of resource with proper containerDefinition
3		IOP Check	Check if possible that the resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
6		Stimulus	AE1 sends a request to create a for binarySwitch
7	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource/resource name of deviceLight fr = AE-ID rqi = (token-string) ty = 28 (flexContainer) pc = Serialized representation of resource with proper containerDefinition
8		IOP Check	Check if possible that the resource is created in registrar CSE.
9	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
10		IOP Check	AE indicates successful operation
Note		Optional: Repeat steps 5-10 for additional deviceLight Modules
IOP Verdict
PRO Verdict

8.5.2 HAIM Light Device Status Read

Interoperability Test Description
Identifier:			TD_M2M_NH_103
Objective:			AE2 reads the status of a HAIM Light Device Model
Configuration:			M2M_CFG_10
References:			oneM2M TS-0023 [14], clause 5.5.27, 5.3.12
Pre-test conditions:			AE2 has created an application resource on registrar CSE AE1 has created a HAIM Light Device model
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 sends a request to retrieve a for binarySwitch
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource/binarySwitch fr = AE-ID rqi = (token-string)
3	Mca	PRO Check Primitive	rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE2 indicates successful operation
Note		Optional: Repeat steps 1-4 for additional deviceLight Modules
IOP Verdict
PRO Verdict

8.5.3 HAIM Light Device Update

Interoperability Test Description
Identifier:			TD_M2M_NH_104
Objective:			AE2 turns the binarySwitch of a HAIM Light Device Model "ON" or "OFF"
Configuration:			M2M_CFG_10
References:			oneM2M TS-0023 [14], clause 5.5.27
Pre-test conditions:			AE2 has created an application resource on registrar CSE AE1 has created a HAIM Light Device model
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 sends a request to create a for deviceLight
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/ URI of resource/binarySwitch fr = AE-ID rqi = (token-string) pc = Serialized representation of resource with new value for powerState
3		IOP Check	Check if possible that the resource is updates in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
Note		Optional: Repeat steps 1-5 for additional device states and settings
IOP Verdict
PRO Verdict

8.5.4 HAIM Light Device Toggle Action

Interoperability Test Description
Identifier:			TD_M2M_NH_105
Objective:			AE2 toggles the state of a HAIM Light Device Model
Configuration:			M2M_CFG_10
References:			oneM2M TS-0023 [14], clause 5.5.27
Pre-test conditions:			AE2 has created an application resource on registrar CSE AE1 has created a HAIM Light Device model
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 sends a request to create a for deviceLight
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/ URI of resource/binarySwitch/toggle fr = AE-ID rqi = (token-string) pc = Serialized representation of resource for toggle action
3		IOP Check	Check if possible that the resource is updates in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE2 indicates successful operation. Check that the powerState of the binarySwitch is updated.
Note		Optional: Repeat steps 1-5 for additional device states and settings
IOP Verdict
PRO Verdict

8.5.5 HAIM Power Outlet SubDevice Create

Interoperability Test Description
Identifier:			TD_M2M_NH_160
Objective:			AE1 creates a Power Outlet SubDevice Model
Configuration:			M2M_CFG_10
References:			oneM2M TS-0023 [14], clause 5.4.1.2
Pre-test conditions:			AE1 has created an application resource on registrar CSE AE1 has created a for deviceSmartPlug
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 sends a request to create a for subDevicePowerOutlet
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource/resource name of deviceSmartPlug fr = AE-ID rqi = (token-string) ty = 28 (flexContainer) pc = Serialized representation of resource with proper containerDefinition
3		IOP Check	Check if possible that the resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
6		Stimulus	AE1 sends a request to create a for binarySwitch
7	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource/resource name of subDevicePowerOutlet fr = AE-ID rqi = (token-string) ty = 28 (flexContainer) pc = Serialized representation of resource with proper containerDefinition
8		IOP Check	Check if possible that the resource is created in registrar CSE.
9	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
10		IOP Check	AE indicates successful operation
Note		Optional: Repeat steps 6-10 for additional subDevicePowerOutlet Modules
IOP Verdict
PRO Verdict

8.5.6 HAIM Toggle Action Create

Interoperability Test Description
Identifier:			TD_M2M_NH_161
Objective:			AE1 creates a Toggle Action Model
Configuration:			M2M_CFG_10
References:			oneM2M TS-0023 [14], clause 5.3.1.12
Pre-test conditions:			AE1 has created an application resource on registrar CSE AE1 has created a for deviceSmartPlug AE1 has created a for binarySwtich as a child of deviceSmartPlug
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 sends a request to create a for Toggle
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource/resource name of binarySwtich fr = AE-ID rqi = (token-string) ty = 28 (flexContainer) pc = Serialized representation of resource with proper containerDefinition
3		IOP Check	Check if possible that the resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.5.7 HAIM Device Properties Create

Interoperability Test Description
Identifier:			TD_M2M_NH_162
Objective:			AE1 creates Device Properties Model
Configuration:			M2M_CFG_10
References:			oneM2M TS-0023 [14], clause 6.2.5
Pre-test conditions:			AE1 has created an application resource on registrar CSE AE1 has created a for deviceLight AE1 has created a resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 sends a request to create a [deviceInfo] resource
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource/ fr = AE-ID rqi = (token-string) ty = 13 (mgmtObj) pc = Serialized representation of [deviceInfo] resource with with properties set as attributes of the resource
3		IOP Check	Check if possible that the [deviceInfo] resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of [deviceInfo] resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6 Semantics management

8.6.1 Semantic Access Control Policy management

8.6.1.1 Procedure for creating ACP triples when a new resource is created

Interoperability Test Description
Identifier:			TD_M2M_NH_106
Objective:			ACP triples are created when a new resource is created
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.2.1.5.2
Pre-test conditions:			AE has created an application resource on Registrar CSE The Registrar CSE has SGS available
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create an < accessControlPolicy_>_ resource
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/ fr = AE-ID rqi = (token-string) ty = 1 (accessControlPolicy) pc = Serialized representation of < accessControlPolicy > resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE. Check if possible that Registrar CSE has created ACP Triples in SGS for the new resource
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of < accessControlPolicy > resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.1.2 Procedure for updating ACP triples when a new resource is updated

Interoperability Test Description
Identifier:			TD_M2M_NH_107
Objective:			ACP triples are updated when an existing resource is updated
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.2.1.5.3
Pre-test conditions:			AE has created an application resource on Registrar CSE accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName} The Registrar CSE has SGS available
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to update a privileges attribute of {accessControlPolicyName}
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/{AE}/{accessControlPolicyName} fr = AE-ID rqi = (token-string) ty = 1 (accessControlPolicy) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource has been updated in Registrar CSE Check if possible that Registrar CSE has updated corresponding ACP Triples in SGS
4	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.1.3 Procedure for deleting ACP triples when an existing resource is deleted

Interoperability Test Description
Identifier:			TD_M2M_NH_108
Objective:			ACP triples are deleted when an existing resource is deleted
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.2.1.5.4
Pre-test conditions:			AE has created an application resource on Registrar CSE accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName} The Registrar CSE has SGS available
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send an accessControlPolicy delete request to Registrar CSE
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/{AE}/{accessControlPolicyName} fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource has been removed from registrar CSE. Check if possible that Registrar CSE has deleted corresponding ACP Triples in SGS
4	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.1.4 Procedure for creating ACP-SD binding triples and SD relationship in SGS

Interoperability Test Description
Identifier:			TD_M2M_NH_109
Objective:			ACP-SD Binding Triples and SD relationship in SGS are created when AE creates a resource in Registrar CSE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.2.1.5.5
Pre-test conditions:			AE has created an application resource on Registrar CSE accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName} The Registrar CSE has SGS available
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create an < semanticDescriptor_>_ resource
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/ fr = AE-ID rqi = (token-string) ty = 24 (semanticDescriptor) pc = Serialized representation of resource acpi = URI of {accessControlPolicyName}
3		IOP Check	Check if possible that the resource is created in Registrar CSE. Check if possible that Registrar CSE has created SD Relationship Triples and ACP-SD Binding Triples for the new in SGS
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.1.5 Procedure for updating ACP-SD binding triples in SGS

Interoperability Test Description
Identifier:			TD_M2M_NH_110
Objective:			ACP-SD Binding Triples are updated when the accessControlPolicyIDs attribute of a resource is updated
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.2.1.5.6
Pre-test conditions:			AE has created an application resource on Registrar CSE accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName} AE has created a semanticDescriptor resource as child resource of resource The Registrar CSE has SGS available
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to update an accessControlPolicyIDs attribute of the resource
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE. Check if possible that Registrar CSE has updated corresponding ACP-SD Binding Triples in SGS
4	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.1.6 Procedure for updating SD relationship triples in SGS

Interoperability Test Description
Identifier:			TD_M2M_NH_111
Objective:			SD Relationship Triples are updated when the descriptor attribute of a resource is changed
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.2.1.5.7
Pre-test conditions:			AE has created an application resource on Registrar CSE accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName} AE has created a semanticDescriptor resource as child resource of resource The Registrar CSE has SGS available
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	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE. Check if possible that Registrar CSE has updated old SD Relationship Triples and/or add new SD Relationship Triple in the SGS.
4	Mca	PRO Check Primitive	Registrar CSE sends response containing: rsc = 2004 (UPDATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.1.7 Procedure for deleting SD relationship triples and ACP-SD binding triples in SGS

Interoperability Test Description
Identifier:			TD_M2M_NH_112
Objective:			SD Relationship Triples are deleted when the descriptor attribute of a resource is deleted
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.2.1.5.8
Pre-test conditions:			AE has created an application resource on Registrar CSE accessControlPolicy resource has been created in registrar CSE under resource with name {accessControlPolicyName} AE has created a semanticDescriptor resource as child resource of resource The Registrar CSE has SGS available
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a semanticDescriptor Delete Request to update the descriptor attribute of the resource.
2	Mca	PRO Check Primitive	op = 4 (Detete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in Registrar CSE. Check if possible that Registrar CSE has removed SD Original Triples, SD Relationship Triples, and ACP-SD Binding Triples related to the from SGS
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.2 Semantic Filtering and discovery

8.6.2.1 Semantic Filtering and Discovery using resource

Interoperability Test Description
Identifier:			TD_M2M_NH_113
Objective:			AE discovers accessible resources residing in Registrar CSE using the
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.4.1
Pre-test conditions:			AE has created an application resource on Registrar CSE AE has created resources {container1} and {container2} in registrar CSE under resource AE has created a group resource with semanticSupportIndicator attribute set to TRUE and memberIds set to {container1} and {container2} ids AE has created as a child resources of a resources {container1} and {container2}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Discovery request to discover the < semanticFanOutPoint > virtual resource of
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}///sfopt from = AE-ID rqi = (token-string) fu=1 smf=sparqlQuery1 pc = empty
4	Mca	PRO Check Primitive	Sent response contains rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing the resources addresses
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.2.2 Resource link-based Semantic Discovery

Interoperability Test Description
Identifier:			TD_M2M_NH_114
Objective:			AE discovers accessible resources residing in Registrar CSE using the resource link-based Semantic Discovery
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.4.3
Pre-test conditions:			AE has created an application resource on Registrar CSE AE has created resources {container1} and {container2} in registrar CSE under resource AE has created a group resource with semanticSupportIndicator attribute set to TRUE and memberIds set to {container1} and {container2} ids AE has created resources as a child resources of a resources {container1} and {container2} named {descriptor1} and {descriptor2} {descriptor1} has relatedSemantics attribute set to ID of {descriptor2} {descriptor2} has relatedSemantics attribute set to ID of {descriptor1}
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a Discovery request to discover the resource using the semanticFilter filterCriteria
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/ from = AE-ID rqi = (token-string) fu=1 smf=sparqlQuery1 pc = empty
4	Mca	PRO Check Primitive	Sent response contains rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of data object containing the resources addresses
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.2.3 Semantic query

Interoperability Test Description
Identifier:			TD_M2M_NH_115
Objective:			AE performs a Semantic Query request in Registrar CSE using the semanticFilter filter criteria
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.4 oneM2M TS-0004 [2], clause 7.3.3.18
Pre-test conditions:			AE1 has created an application resource on Registrar CSE AE1 has created a container resource on Registrar CSE AE1 has created a as a child resource of a
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 is requested to send a Semantic Query Operation request to query the resource using a SPARQL query
2	Mca	PRO Check Primitive	Sent request contains op = 2 (Retrieve) to = {CSEBaseName} from = AE-ID rqi = (token-string) sqi = TRUE smf=sparqlQuery1 rcn = 10 (semantic content) pc = empty
3	Mca	PRO Check Primitive	Sent response contains rsc = 2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation semantic query result
4		IOP Check	AE indicates notification received
IOP Verdict
PRO Verdict

8.6.3 Semantic Mashup management

8.6.3.1 SemanticMashupJobProfile Create

Interoperability Test Description
Identifier:			TD_M2M_NH_116
Objective:			AE creates a SemanticMashupJobProfile resource in Registrar CSE via a SemanticMashupJobProfile Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.3.2 oneM2M TS-0004 [2], clause 7.4.49.2.1
Pre-test conditions:			AE has created an application resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 40 (semanticMashupJobProfile) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.3.2 SemanticMashupJobProfile Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_117
Objective:			AE retrieves information of a semanticMashupJobProfile resource via a semanticMashupJobProfile Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.3.3 oneM2M TS-0004 [2], clause 7.4.49.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticMashupJobProfile resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.3.3 SemanticMashupJobProfile Update

Interoperability Test Description
Identifier:			TD_M2M_NH_118
Objective:			AE updates attribute in resource via a semanticMashupJobProfile Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.3.4 oneM2M TS-0004 [2], clause 7.4.49.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticMashupJobProfile resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a semanticMashupJobProfile Update Request to update the memberFilter attribute of the resource.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.3.4 SemanticMashupJobProfile Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_119
Objective:			AE deletes semanticMashupJobProfile resource via a semanticMashupJobProfile Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.3.5 oneM2M TS-0004 [2], clause 7.4.49.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticMashupJobProfile resource as child of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a semanticMashupJobProfile Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in Registrar CSE.
6		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.6.3.5 SemanticMashupInstance Create

Interoperability Test Description
Identifier:			TD_M2M_NH_120
Objective:			AE creates a semanticMashupInstance resource in Registrar CSE via a semanticMashupInstance Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.4.2 oneM2M TS-0004 [2], clause 7.4.50.2.1
Pre-test conditions:			AE has created an application resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 41 (semanticMashupInstance) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.3.6 SemanticMashupInstance Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_121
Objective:			AE retrieves information of a semanticMashupInstance resource via a semanticMashupInstance Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.4.3 oneM2M TS-0004 [2], clause 7.4.50.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticMashupInstance resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.3.7 SemanticMashupInstance Update

Interoperability Test Description
Identifier:			TD_M2M_NH_122
Objective:			AE updates attribute in resource via a semanticMashupInstance Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.4.4 oneM2M TS-0004 [2], clause 7.4.50.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticMashupInstance resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a semanticMashupInstance Update Request to update the smjpInputParameter attribute of the resource.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.3.8 SemanticMashupInstance Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_123
Objective:			AE deletes semanticMashupInstance resource via a semanticMashupInstance Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.4.5 oneM2M TS-0004 [2], clause 7.4.50.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticMashupInstance resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a semanticMashupInstance Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/ URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in Registrar CSE.
6		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.6.3.9 SemanticMashupResult Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_124
Objective:			AE retrieves information of a semanticMashupResult resource via a semanticMashupResult Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.6.2 oneM2M TS-0004 [2], clause 7.4.52.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticMashupInstance resource as child resource of resource resource is created as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.3.10 SemanticMashupResult Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_125
Objective:			AE deletes semanticMashupResult resource via a semanticMashupResult Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.6.3 oneM2M TS-0004 [2], clause 7.4.52.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticMashupInstance resource as child resource of resource resource is created as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a semanticMashupResult Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/ URI of resource/ URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in Registrar CSE.
6		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.6.3.11 Mashup Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_126
Objective:			AE triggers a calculation and generation of the mashup result by sending a / Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.5.2 oneM2M TS-0004 [2], clause 7.4.51.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticMashupInstance resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE retrieves a resource in a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource/msp fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that a resource is created under the resource
4	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.4 Ontology Repository management

8.6.5.1 OntologyRepository Create

Interoperability Test Description
Identifier:			TD_M2M_NH_127
Objective:			AE creates a OntologyRepository resource in Registrar CSE via a OntologyRepository Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.7.2 oneM2M TS-0004 [2], clause 7.4.46.2.1
Pre-test conditions:			AE has created an application resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 38 (ontologyRepository) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.4.2 OntologyRepository Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_128
Objective:			AE retrieves information of a ontologyRepository resource via a ontologyRepository Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.7.3 oneM2M TS-0004 [2], clause 7.4.46.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a ontologyRepository resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.4.3 OntologyRepository Update

Interoperability Test Description
Identifier:			TD_M2M_NH_129
Objective:			AE updates attribute in resource via a ontologyRepository Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.7.4 oneM2M TS-0004 [2], clause 7.4.46.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a ontologyRepository resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a ontologyRepository Update Request to update an attribute of the resource.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.4.4 OntologyRepository Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_130
Objective:			AE deletes OntologyRepository resource via a OntologyRepository Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.7.5 oneM2M TS-0004 [2], clause 7.4.46.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a ontologyRepository resource as child of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a ontologyRepository Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in Registrar CSE.
6		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.6.5 Semantic validation management

8.6.5.1 Semantic validation independent of resource operation

Interoperability Test Description
Identifier:			TD_M2M_NH_131
Objective:			AE checks the validity of the resource via a Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.10.2 oneM2M TS-0004 [2], clause 7.4.48.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a semanticDescriptor resource as child of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Update Request to check the validity of the resource
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource/smv fr = AE-ID rqi = (token-string) pc = Serialized representation of parameters
3		IOP Check	Check if possible that the received resource with the semanticValidated attribute is set to 'true' in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.5.2 Semantic validation triggered when Create a semanticDescriptor resource

Interoperability Test Description
Identifier:			TD_M2M_NH_132
Objective:			AE creates a resource visa SemanticDescriptor Create Request and Registrar CSE checks the validity of the created resource
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 7.10.3 oneM2M TS-0004 [2], clause 7.4.34.2.1
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a < semanticDescriptor > Create Request with validationEnable attribute set to 'true'
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 24 (semanticDescriptor) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE. Check if possible that the semanticValidated attribute of the is set to 'true'.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.6 Ontology Mapping management

8.6.6.1 OntologyMapping Create

Interoperability Test Description
Identifier:			TD_M2M_NH_133
Objective:			AE creates an OntologyMapping resource in Registrar CSE via an OntologyMapping Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.10.2 oneM2M TS-0004 [2], clause 7.4.62.2.1
Pre-test conditions:			AE has created an application resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a resource
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 52 (ontologyMapping) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.6.2 OntologyMapping Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_134
Objective:			AE retrieves information of an ontology mapping result via a ontologyMapping Retrieve Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.10.3 oneM2M TS-0004 [2], clause 7.4.62.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a ontologyMapping resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.6.3 OntologyMapping Update

Interoperability Test Description
Identifier:			TD_M2M_NH_135
Objective:			AE updates attribute in resource via a ontologyMapping Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.10.4 oneM2M TS-0004 [2], clause 7.4.62.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a ontologyMapping resource as child resource of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a ontologyMapping Update Request to update the mappingPolicy attribute of the resource.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.6.6.4 OntologyMapping Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_136
Objective:			AE deletes OntologyMapping resource via a OntologyMapping Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0034 [13], clause 6.10.5 oneM2M TS-0004 [2], clause 7.4.62.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a ontologyMapping resource as child of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a ontologyMapping Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3		IOP Check	Check if possible that the resource is deleted in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
5		IOP Check	Check if possible that the resource has been removed in Registrar CSE.
6		IOP Check	AE indicates successful operation.
IOP Verdict
PRO Verdict

8.7 3GPP Interworking

8.7.1 Cellular IoT non-IP data delivery (NIDD)

8.7.1.1 SCEF Configuration for NIDD

Interoperability Test Description
Identifier:			TD_M2M_SH_27
Objective:			IN-CSE establishes SCEF Configuration for NIDD
Configuration:			M2M_CFG_09
References:			oneM2M TS-0026 [15], clause 7.1.1.1
Pre-test conditions:			UE hosts an ADN-AE node IN-CSE has a resource created as a child of resource resource is created as a child of Node-ID attribute of resource is set to M2M-Ext-ID of UE and niddRequired attribute is set to TRUE SCEF identifier is pre-provisioned to IN-CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	IN-CSE issues a NIDD Configuration Request to SCEF for ADN-AE hosted on a UE
2	(T8) Mcn	PRO Check HTTP	Method = POST URI = {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/ The {apiRoot} and_{scsAsId}_ segments are configured based on Service Provider and MNO policies. Payload shall include NiddConfiguration data structure with the following attributes included in the request: externalId, notificationDestination, duration, pdnEstablishmentOption, duration, pdnEstablishmentOption, reliableDataService, rdsPorts, supportedFeatures
3		IOP Check	Check if possible that the SCEF has successfully processes the NIDD Configuration Request
4	(T8) Mcn	PRO Check HTTP	SCEF responds for the NIDD Configuration Response: Status code = 201 (CREATED) Location header = {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId} Payload shall include NiddConfiguration data structure with the following attributes included in the request: maximumPacketSize, status, self
5		IOP Check	IN-CSE indicates successful operation.
IOP Verdict
PRO Verdict

8.7.1.2 SCEF-based Mobile Terminated NIDD

Interoperability Test Description
Identifier:			TD_M2M_SH_28
Objective:			IN-AE sends a downlink non-IP data to a UE hosting ADN-AE
Configuration:			M2M_CFG_11
References:			oneM2M TS-0026 [], clause 7.1.1.2
Pre-test conditions:			IN-AE has created an Application Entity resource on IN-CSE ADN-AE has created an Application Entity resource on IN-CSE IN-CSE has a resource created as a child of resource resource is created as a child of Node-ID attribute of resource is set to M2M-Ext-ID of UE and niddRequired attribute is set to TRUE SCEF identifier is pre-provisioned to IN-CSE NIDD configuration procedure is competed successfully
Test Sequence
Step	RP	Type	Description
1		Stimulus	(Optional) IN-AE issues an arbitrary oneM2M request targeting an ADN-AE.
2		Stimulus	IN-CSE issues a SCEF-based Mobile Terminated (MT) NIDD Downlink Data Transfer Request
3	(T8) Mcn	PRO Check HTTP	Method = POST URI = {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId}/downlink-data-deliveries Payload shall include NiddDownlinkDataTransfer data structure with the following attributes included in the request: externalId, maximumLatency, priority, pdnEstablishmentOption, pdnEstablishmentOption, reliableDataService, rdsPorts, data (containing onem2m primitive)
4		IOP Check	Check if possible that the SCEF has successfully processes the NIDD Downlink Data Transfer Request
5	(T8) Mcn	PRO Check HTTP	SCEF responds for the NIDD Downlink Data Transfer Request: Status code = 201 (CREATED) Location header = {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId} Payload shall include NiddConfiguration data structure with the following attributes included in the request: maximumPacketSize, status, self
6		IOP Check	In case the UE does not have an active NIDD PDN connection to the SCEF, check that SCEF buffered the request until the UE establishes the connection
7	(T8) Mcn	PRO Check HTTP	SCEF responds with NIDD Downlink Data Transfer Response: Status code = 200 (OK) / 201 (CREATED, Buffered request) Location header = {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId}/downlink-data-deliveries/{downlinkDataDeliveryId} Payload shall include NiddDownlinkDataTransfer data structure with the following attributes included in the request: deliviryStatus, self, requestedRetransmissionTime.
8	(T8) Mcn	PRO Check HTTP	(Optional) SCEF returns a MT NIDD Downlink Data Delivery Status Notification to IN-CSE: Method = POST URI = {notification_uri} Payload shall include a NiddDownlinkDataDeliveryStatusNotification data structure with the following attributes included in the request: niddDownlinkDataTransfer, deliveryStatus, requestedRetransmissionTime
9	(T8) Mcn	PRO Check HTTP	IN-CSE responds to the MT NIDD Downlink Data Delivery Status Acknowledgement: Status code = 204 (NO CONTENT)
10		IOP Check	Check that ADN-AE on UE has executed the oneM2M request primitive accordingly
11		Stimulus	(Optional) ADN-AE hosted on the UE issues a MO NIDD Uplink Data Notification to deliver a oneM2M response primitive back to the Originator
12	(T8) Mcn	PRO Check HTTP	(Optional) SCEF sends for the NIDD Uplink Data Notification: Method = POST URI = {notification_uri} Payload shall include NiddUplinkDataNotification data structure with the following attributes included in the request: niddConfiguration, externalId, reliableDataService, rdsPort, data
13	(T8) Mcn	PRO Check HTTP	(Optional) IN-CSE responds with MO NIDD Uplink Data Acknowledgement and sends oneM2M response primitive to IN-AE Status code = 204 (NO CONTENT)
14		IOP Check	(Optional) Check that IN-AE received a corresponding oneM2M response primitive.
IOP Verdict
PRO Verdict

8.7.1.3 SCEF-based Mobile Originated NIDD

Interoperability Test Description
Identifier:			TD_M2M_SH_29
Objective:			IN-AE sends a downlink non-IP data to a UE hosting ADN-AE
Configuration:			M2M_CFG_11
References:			oneM2M TS-0026 [], clause 7.1.1.3
Pre-test conditions:			IN-AE has created an Application Entity resource on IN-CSE ADN-AE has created an Application Entity resource on IN-CSE IN-CSE has a resource created as a child of resource resource is created as a child of Node-ID attribute of resource is set to M2M-Ext-ID of UE and niddRequired attribute is set to TRUE SCEF identifier is pre-provisioned to IN-CSE NIDD configuration procedure is competed successfully RDS source and destination port numbers are pre-provisioned in ADN-AE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AND-AE issues MO NIDD Uplink Data Notification to deliver an arbitrary primitive to the IN-CSE
2	(T8) Mcn	PRO Check HTTP	SCEF triggers a MO NIDD Uplink Data Notification carrying request primitive Method = POST URI = notification_uri} Payload shall include NiddUplinkDataNotification data structure with the following attributes included in the request: niddConfiguration, externalId, reliableDataService, rdsPort, data (containing onem2m primitive)
3	(T8) Mcn	PRO Check HTTP	IN-CSE responds with MO NIDD Uplink Data Acknowledgement Status code = 204 (NO CONTENT)
4		IOP Check	Check if possible that SCEF has processed the MO NIDD Uplink Data Acknowledgement from the IN-CSE
5		PRO Check	SCEF sends an RDS acknowledgment to the UE Status code = 204 (NO CONTENT)
6		IOP Check	Check if possible that IN-CSE processes the oneM2M request primitive
7	(T8) Mcn	PRO Check HTTP	(Optional) If a response is required, IN-CSE generates a oneM2M response and sends a MT NIDD Downlink Data Transfer Request Method = POST URI = {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId}/downlink-data-deliveries Payload shall include NiddDownlinkDataTransfer data structure with the following attributes included in the request:externalId, maximumLatency, priority, pdnEstablishmentOption, (optional) reliableDataService, rdsPort, data (containing response to oneM2M primitive)
8	(T8) Mcn	PRO Check HTTP	(Optional) Scef returns MT NIDD Downlink Data Transfer Response to IN-CSE Status code = 200 (OK) / 201 (Created) URI = {apiRoot}/3gpp-nidd/v1/{scsAsId}/configurations/{configurationId}/downlink-data-deliveries/{downlinkDataDeliveryId} Payload may include NiddDownlinkDataTransfer data structure with the following attributes included in the response: deliveryStatus, self, requestedRetransmissionTime
9		IOP Check	(Optional) Check if possible that SCEF has processed the request and delivered it to the targeted UE (Optional) Check if possible that UE has responded with an RDS acknowledgment
10	(T8) Mcn	PRO Check HTTP	(Optional) SCEF returns MT NIDD Downlink Data Delivery Status Notification to IN-CSE Method = POST URI = {notification_uri} Payload shall include NiddDownlinkDataDeliveryStatusNotification data structure with the following attributes included in the request: niddDownlinkDataTransfer, deliveryStatus, requestedRetransmissionTime
11	(T8) Mcn	PRO Check HTTP	(Optional) IN-CSE responds to SCEF Status code = 204 (NO CONTENT)
12		IOP Check	(Optional) Check if possible that ADN-AE has processed the oneM2M response primitive
IOP Verdict
PRO Verdict

8.7.2 Monitoring events

8.7.2.1 UE Reachability monitoring

Interoperability Test Description
Identifier:			TD_M2M_SH_30
Objective:			IN-AE monitors UE Reachability status
Configuration:			M2M_CFG_10
References:			oneM2M TS-0026 [15], clause 7.4.1
Pre-test conditions:			UE, SCEF and IN-CSE are attached to the underlying 3GPP network IN-AE has created an Application Entity resource on IN-CSE ADN-AE has created an Application Entity resource on IN-CSE ADN-AE has created a Node resource on IN-CSE representing UE ADN-AE has created a Schedule resource on IN-CSE under resource. The networkCoordinated attribute is set to TRUE. IN-AE has subscribed to the resource by creating a child resource. IN-CSE has subscribed to to the SCEF to receive notifications (monitoringType = UE_REACHABILITY). UE is in idle mode
Test Sequence
Step	RP	Type	Description
1		Stimulus	UE transitions to connected mode
2		IOP Check	Check if possible that the 3GPP network entities (e.g. HSS) has detected the condition and sent a Monitoring Event Report to SCEF
3	(T8) Mcn	PRO Check HTTP	SCEF receives the report and sends Monitoring Notification UE for_REACHABILITY to IN-CSE: Method = POST URI = {notification_uri} Payload shall include MonitoringNotification data structure with the following attributes included in the request: subscription, configResults, cancelInd, monitoringEventReports (externalIDs, monitoringType, idleStatusInfo, reachabilityType)
4	(T8) Mcn	PRO Check HTTP	IN-CSE responds to the UE Reachability Monitoring Notification: Status code = 204 (NO CONTENT)
5		IOP Check	Check if possible that if idleStatusInfo information is provided in the report, IN-CSE has updated scheduleElement attribute of the resource
6	(T8) Mcn	PRO Primitive	IN-CSE sends a Notify message to IN-CSE: op = 6 (Notify) pc = serialized representation of the updated resource
7		IOP Check	Check if possible that ADN-AE on UE has updated its local resource (if applicable)
IOP Verdict
PRO Verdict

8.7.2.2 UE Availability after DDN Failure

Interoperability Test Description
Identifier:			TD_M2M_SH_31
Objective:			UE Availability after DDN Failure scenario
Configuration:			M2M_CFG_11
References:			oneM2M TS-0026 [15], clause 7.4.2
Pre-test conditions:			UE, SCEF and IN-CSE are attached to the underlying 3GPP network IN-AE has created an Application Entity resource on IN-CSE ADN-AE has created an Application Entity resource on IN-CSE ADN-AE has created a Node resource on IN-CSE representing UE ADN-AE has created a Schedule resource on IN-CSE under resource. The networkCoordinated attribute is set to TRUE. IN-AE has subscribed to the resource by creating a child resource. IN-CSE has subscribed to to the SCEF to receive notifications (monitoringType = AVAILABILITY_AFTER_DDN_FAILURE) UE is in unreachable for Downlink data and in state that DDN Failure condition can be reproduced
Test Sequence
Step	RP	Type	Description
1		Stimulus	IN-AE issues an arbitrary oneM2M request targeting an ADN-AE.
2		IOP Check	Check that no response for UE paging is received. Check if possible that if UE is in PSM mode, the UE subscription has been updated to reflect that a notification of availability should be sent after this DDN failure
3		Stimulus	UE contacts the network
4		IOP Check	Check if possible that SCEF has received a Monitoring Indication that the UE is available
5	(T8) Mcn	PRO Check HTTP	SCEF receives the report and sends Monitoring Notification for AVAILABILITY_AFTER_DDN_FAILURE to IN-CSE: Method = POST URI = {notification_uri} Payload shall include MonitoringNotification data structure with the following attributes included in the request: subscription, configResults, cancelInd, monitoringEventReports (externalIDs, monitoringType, idleStatusInfo)
6	(T8) Mcn	PRO Check HTTP	IN-CSE responds to the DDN Failure Monitoring Notification: Status code = 204 (NO CONTENT)
7		IOP Check	Check if possible that IN-CSE has updated the resource to indicate that UE is available and created new scheduleElement. Check if possible that notification has been sent to the resource subscribed entities.
8		Stimulus	UE transitions to Idle
9	(T8) Mcn	PRO Check HTTP	SCEF sends a UE Reachability Monitoring Event Notification Request to IN-CSE: Method = POST URI = {notification_uri} Payload shall include MonitoringNotification data structure with the following attributes included in the request: subscription, configResults, cancelInd, monitoringEventReports (externalIDs, monitoringType, idleStatusInfo).
10	(T8) Mcn	PRO Check HTTP	IN-CSE responds to the UE Reachability Monitoring Notification: Status code = 204 (NO CONTENT)
11		IOP Check	Check if possible that IN-CSE has updated the resource to indicate that UE is idle. Check if possible that notification has been sent to the resource subscribed entities.
IOP Verdict
PRO Verdict

8.7.2.3 UE Communication Failure

Interoperability Test Description
Identifier:			TD_M2M_SH_32
Objective:			UE Communication Failure scenario
Configuration:			M2M_CFG_11
References:			oneM2M TS-0026 [15], clause 7.4.3
Pre-test conditions:			UE, SCEF and IN-CSE are attached to the underlying 3GPP network IN-AE has created an Application Entity resource on IN-CSE ADN-AE has created an Application Entity resource on IN-CSE ADN-AE has created a Node resource on IN-CSE representing UE ADN-AE has created a Schedule resource on IN-CSE under resource. The networkCoordinated attribute is set to TRUE IN-AE has subscribed to the resource by creating a child resource. IN-CSE has subscribed to to the SCEF to receive notifications (monitoringType = COMMUNICATION_FAILURE)
Test Sequence
Step	RP	Type	Description
1		Stimulus	UE communication failure occurs
2		IOP Check	Check if possible SCEF has received a Monitoring Event Report
3	(T8) Mcn	PRO Check HTTP	SCEF receives the report and sends Monitoring Notification Report for COMMUNICATION_FAILURE to IN-CSE: Method = POST URI = {notification_uri} Payload shall include MonitoringNotification data structure with the following attributes included in the request: subscription, configResults, cancelInd, monitoringEventReports (externalIDs, monitoringType, failureCause).
4	(T8) Mcn	PRO Check HTTP	IN-CSE responds to the Monitoring Notification Report request: Status code = 204 (NO CONTENT)
5		IOP Check	Check if possible that IN-CSE has updated the resource to indicate that UE is available and created new scheduleElement.
6	(T8) Mcn	PRO Check HTTP	SCEF sends a UE Communication Failure Monitoring Event Notification Request to IN-CSE: Method = POST URI = {notification_uri} Payload shall include MonitoringNotification data structure with the following attributes included in the request: subscription, configResults, cancelInd, monitoringEventReports (externalIDs, monitoringType, failureCause).
7	(T8) Mcn	PRO Check HTTP	IN-CSE responds to the UE Communication Failure Monitoring Notification: Status code = 204 (NO CONTENT)
8		IOP Check	Check if possible that IN-CSE has updated the scheduleElement of the _ resource to indicate that no communications are currently available. Check if possible that notification has been sent to the resource subscribed entities.
IOP Verdict
PRO Verdict

8.7.2.4 Roaming Status

Interoperability Test Description
Identifier:			TD_M2M_SH_33
Objective:			Roaming status scenario
Configuration:			M2M_CFG_09
References:			oneM2M TS-0026 [15], clause 7.4.6
Pre-test conditions:			UE, SCEF and IN-CSE are attached to the underlying 3GPP network IN-CSE can make Roaming Status Reports requests ADN-AE has created an Application Entity resource on IN-CSE ADN-AE has created a Node resource on IN-CSE representing UE. roamingStatus and networkID attributes of resource are configured. IN-CSE has subscribed to to the SCEF to receive notifications (monitoringType = ROAMING_STATUS)
Test Sequence
Step	RP	Type	Description
1		Stimulus	Roaming status of UE has changed
2		IOP Check	Check if possible SCEF has received a Monitoring Event Report
3	(T8) Mcn	PRO Check HTTP	SCEF receives the report and sends Monitoring Notification Report for ROAMING_STATUS to IN-CSE: Method = POST URI = {notification_uri} Payload shall include MonitoringNotification data structure with the following attributes included in the request: subscription, configResults, cancelInd, monitoringEventReports (externalIDs, monitoringType, plmnId, roamingStatus).
4	(T8) Mcn	PRO Check HTTP	IN-CSE responds to the DDN Failure Monitoring Notification: Status code = 204 (NO CONTENT)
5		IOP Check	Check if possible that IN-CSE has updated roamingStatus and networkID attributes the resource.
IOP Verdict
PRO Verdict

8.7.2.5 Location updating triggered by retrieval

Interoperability Test Description
Identifier:			TD_M2M_SH_34
Objective:			Location Reporting scenario
Configuration:			M2M_CFG_09
References:			oneM2M TS-0026 [15], clause 7.4.7.2
Pre-test conditions:			UE, SCEF and IN-CSE are attached to the underlying 3GPP network ADN-AE has created an Application Entity resource on IN-CSE IN-CSE has subscribed to to the SCEF to receive notifications (monitoringType = LOCATION_REPORTING)
Test Sequence
Step	RP	Type	Description
1		Stimulus	IN-AE sends a < locationPolicy> CREATE request
2	(T8) Mcn	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = IN-AE-ID rqi = (token-string) ty = 10 (LocationPolicy) pc = Serialized representation of resource locationSource = Netwrork based locationUpdatePeriod = 0 locationTargetID = M2M-Ext-ID of the UE locationInformationType = position fix retrieveLastKnownLocation = TRUE/FALSE
3		IOP Check	Check if possible that IN-CSE has created resource
4		Stimulus	AE is requested to send a Retrieve Request for a content instance.
5	(T8) Mcn	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource/la fr = IN-AE-ID rqi = (token-string) pc = empty
6	(T8) Mcn	PRO Check HTTP	IN-CSE makes Monitoring Event Subscription request to retrieve current location of UE Method = POST URI = {apiRoot}/3gpp-monitoring-event/v1/{scsAsId}/subscriptions/ Payload shall include_MonitoringEventSubscription_ data structure with the following attributes included in the request: externalId, notificationDestination, monitoringType, supportedFeatures, maximumNumberOfReports, monitorExpireTime, accuracy. locationType = CURRENT_KNOWNLOCATION
7	(T8) Mcn	PRO Check HTTP	SCEF sends a Monitoring Event Subscription Response message to the IN-CSE Status code = 201 (CREATED) Location header = {apiRoot}/3gpp-monitoring-event/v1/{scsAsId}/subscriptions/{subscriptionId} Payload shall include NiddConfiguration data structure with the following attributes included in the request: monitoringEventReport, self
8		IOP Check	Check if possible that SCEF detected and retrieved location of UE.
9	(T8) Mcn	PRO Check HTTP	SCEF sends a Monitoring Event Report message to the IN-CSE Method = POST URI = {notification_uri} Payload shall include_MonitoringEventSubscription_ data structure with the following attributes included in the request: subscription, configResults, cancelid,monitoring, EventReports (externalID, monitoringType, locatonInfo)
10	(T8) Mcn	PRO Check HTTP	IN-CSE responds to the DDN Failure Monitoring Notification: Status code = 204 (NO CONTENT)
11		IOP Check	Check if possible that IN-CSE has created a new child resource of the . The contains the UE's current location
12	(T8) Mcn	PRO Check HTTP	IN-CSE sends a Monitoring Event Subscription message to the SCEF Method = POST URI = {apiRoot}/3gpp-monitoring-event/v1/{scsAsId}/subscriptions/ Payload shall include MonitoringEventSubscription with the following attributes included in the request: subscription, configResults, cancelid,monitoringEventReports (externalID, monitoringType, locatonInfo) locationType = LAST_KNOWNLOCATION
13	(T8) Mcn	PRO Check HTTP	SCEF sends a Monitoring Event Report message to the IN-CSE Method = POST Response code = 201 (CREATED) URI = {apiRoot}/3gpp-monitoring-vent/v1/{scsAsId}/subscriptions/{subscriptionId} Payload shall include_MonitoringEventSubscription_ data structure with the following attributes included in the request: self, monitoringEnentReport
14		IOP Check	Check if possible that SCEF receives a last known location information of UE
15	(T8) Mcn	PRO Check HTTP	SCEF sends a Monitoring Notification Report message to the IN-CSE for LOCATION_REPORTING: Method = POST URI = {notification_uri} Payload shall include_MonitoringEventSubscription_ data structure with the following attributes included in the request: subscription, configResults, cancelid,monitoringEventReports
16	(T8) Mcn	PRO Check HTTP	IN-CSE responds to the Monitoring Notification: Status code = 204 (NO CONTENT)
17		IOP Check	Check if possible that IN-CSE has created a new > child resource of the <container > containing the UE's last known location in this <contentInstance>
18	(T8) Mcn	PRO Check HTTP	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of latest resource, created after acquiring location info from SCEF
19		IOP Check	AE indicates successful operation
NOTE: Steps: 12-17 are only applicable, if retrieveLastKnownLocation is set to TRUE
PRO Verdict

8.7.3 3GPP Based Device triggering

8.7.3.1 General Procedure for 3GPP Based Device Triggering

Interoperability Test Description
Identifier:			TD_M2M_SH_35
Objective:			IN-AE triggers ADN-AE hosted on UE
Configuration:			M2M_CFG_09
References:			oneM2M TS-0026 [15], clause 7.5.1
Pre-test conditions:			UE, SCEF and IN-CSE are attached to the underlying 3GPP network ADN-AE has created an Application Entity resource on IN-CSE ADN-AE is available to receive the Device Trigger Requests (triggerEnable = "TRUE")
Test Sequence
Step	RP	Type	Description
1		Stimulus	IN-AE sends a request to create a
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/{AE-ID}/ fr = AE-ID rqi = (token-string) ty = 47 (triggerRequest) pc = Serialized representation of < triggerRequest > resource
3		IOP Check	Check if possible that IN-CSE has created resource
4	(T8) Mcn	PRO Check HTTP	IN-CSE sends a Device Triggering request to the SCEF Method = POST URI = {apiRoot}/3gpp-device-triggering/v1/{scsAsId}/transactions Payload shall include DeviceTriggering data structure with the following attributes included in the request: supportedFeatures, validityPeriod, triggerPayload, externalId, applicationPortID, notificationDestination, priority
5		IOP Check	Check that SCEF has responded to IN-CSE for Device Triggering request Check that SCEF has delivered the device trigger message to the UE hosting ADN-AE Check that SCEF has delivered the Device Triggering Delivery Report Notification request to IN-CSE
6		IOP Check	Check that IN-CSE has responded to SCEF the Device Triggering Delivery Report Notification request Check if possible that IN-CSE has updated triggerStatus attribute of resource Check that IN-CSE has responded to IN-AE for Create request
7		IOP Check	Check that ADN-AE has performed the trigger actions
IOP Verdict
PRO Verdict

8.7.3.2 3GPP Based Device Trigger Recall/Replace Procedure

Interoperability Test Description
Identifier:			TD_M2M_SH_36
Objective:			IN-AE recalls/replaces a trigger request targeting AND-AE hosted on UE that has been already created in IN-CSE
Configuration:			M2M_CFG_09
References:			oneM2M TS-0026 [15], clause 7.5.2
Pre-test conditions:			UE, SCEF and IN-CSE are attached to the underlying 3GPP network ADN-AE has created an Application Entity resource on IN-CSE ADN-AE is available to receive the Device Trigger Requests (triggerEnable = "TRUE") resource targeting ADN-AE has been created in IN-CSE IN-CSE has already sent a device trigger request to the underlying 3GPP network
Test Sequence
Step	RP	Type	Description
1		Stimulus	IN-AE sends a request to UPDATE/DELETE a
2	Mca	PRO Check Primitive	op = 3 (Update) / 4 (Delete) to = {CSEBaseName}/{AE-ID}/{URI of resource} fr = AE-ID rqi = (token-string) pc = Serialized representation of < triggerRequest > resource (for UPDATE only)
3		IOP Check	Check if possible that IN-CSE has created resource
4	(T8) Mcn	PRO Check HTTP	IN-CSE sends a Trigger UPDATE (Replace) / DELETE (Recall) Request to the SCEF Method = PUT/DELETE URI = {apiRoot}/3gpp-device-triggering/v1/{scsAsId}/transactions (For Trigger UPDATE only) Payload shall include DeviceTriggering data structure with the following attributes included in the request: supportedFeatures, validityPeriod, triggerPayload, externalId, applicationPortID_,_ notificationDestination, priority
5		IOP Check	Check that SCEF has recalled/replaced the trigger Check that SCEF responded to IN-CSE for Device Trigger Recall/Replace Check that SCEF has delivered the device trigger message to the UE hosting ADN-AE Check that SCEF has delivered the Device Triggering Delivery Report Notification request to IN-CSE
6		IOP Check	Check if possible that IN-CSE has updated triggerStatus attribute of resource / deleted resource Check that IN-CSE has responded to IN-AE for UPDATE/DELETE request
IOP Verdict
PRO Verdict

8.7.4 Configuration of traffic patterns

Interoperability Test Description
Identifier:			TD_M2M_SH_37
Objective:			IN-CSE translates the oneM2M Node Traffic Pattern (TP) into a 3GPP Device Communication Pattern
Configuration:			M2M_CFG_09
References:			oneM2M TS-0026 [15], clause 7.6
Pre-test conditions:			UE, SCEF and IN-CSE are attached to the underlying 3GPP network ADN-AE hosted on UE has created an Application Entity resource on IN-CSE IN-CSE has established relationship with MNO and is allowed to request Configuration of Device Communication Patterns.
Test Sequence
Step	RP	Type	Description
1		Stimulus	ADN-AE sends a request to create an activityPatternElements attribute in resource
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/{AE-ID} fr = AE-ID rqi = (token-string) pc = Serialized representation of resource
3		IOP Check	Check if possible that IN-CSE has updated resource
4	(T8) Mcn	PRO Check HTTP	IN-CSE sends a Communication Patterns Configuration creation request to the SCEF Method = POST URI = {apiRoot}/3gpp-cp-parameter-provisioning/v1/{scsAsId}/subscriptions Payload shall include DeviceTriggering data structure with the following attributes included in the request: externalId, supportedFeatures, cpParameterSets
5		IOP Check	Check if possible that underlying 3GPP network elements has stored the new/updated CP parameter Check that SCEF has responded to IN-CSE for Communication Patterns Configuration request
IOP Verdict
PRO Verdict

8.7.5 Group message delivery using MBMS

8.7.5.1 Create MBMS Group

Interoperability Test Description
Identifier:			TD_M2M_SH_38
Objective:			IN-AE creates a MBMS Group for handling group related requests
Configuration:			M2M_CFG_12
References:			oneM2M TS-0026 [15], clause 7.7.3.1
Pre-test conditions:			Member Hosting CSE, SCEF and Group Hosting CSE are attached to the underlying 3GPP network Member Hosting CSE on UE has created a resource on Group Hosting CSE IN-AE has created an Application Entity resource on Group Hosting CSE The MBMS service area information provided by the MNO is configured in the oneM2M System External Group Identifiers for the devices have been pre-provisioned in the oneM2M System
Test Sequence
Step	RP	Type	Description
1		Stimulus	IN-AE is requested to send a group Create Request
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 9 (group) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in Registrar CSE. Check if possible that multicastType attribute of the Multicast Group Information is set to 3GPP_MBMS_group
4	Mca	PRO Check Primitive	Group Hosting CSE responds to IN-AE: rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5	(T8) Mcn	PRO Check HTTP	Group Hosting CSE sends a Allocate TMGI Request to the SCEF Method = POST URI = {apiRoot}/3gpp-group-message-delivery-mb2 /v1/{scsAsId}/ tmgi-allocation Payload shall include TMGIAllocation data structure with the following attributes included in the request: externalGroupId, mbmsLocArea, supportedFeatures
6		IOP Check	Check that SCEF has delivered Allocate TMGI Response to Group Hosting CSE
7		IOP Check	Check if possible that the Group Hosting CSE has stored the tmgi and tmgiExpiration in the local Multicast Group Information Check that Group Hosting CSE has sent < localMulticastGroup_>_ creation requests to the Member Hosting CSE Check that Member Hosting CSE has created < localMulticastGroup_>_ resource
IOP Verdict
PRO Verdict

8.7.5.2 Group message delivery using MBMS

Interoperability Test Description
Identifier:			TD_M2M_SH_39
Objective:			IN-AE sends a request for accessing member resources to the Group Hosting CSE
Configuration:			M2M_CFG_12
References:			oneM2M TS-0026 [15], clause 7.7.3.1
Pre-test conditions:			Member Hosting CSE, SCEF and Group Hosting CSE are attached to the underlying 3GPP network Member Hosting CSE on UE has created a resource on Group Hosting CSE resource representing UE has been created on Group Hosting CSE <schedule > resource has been created as a child of the resource on Group Hosting CSE IN-AE has created a resource in Group Hosting CSE resource is the member of the Group Hosting CSE has created a < localMulticastGroup_>_ in the Member Hosting CSE Group Hosting CSE stores tmgi and tmgiExpiration in the local Multicast Group Information
Test Sequence
Step	RP	Type	Description
1		Stimulus	IN-AE is requested to send a Retrieve Request to the fanoutPoint of resource
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/{group}/fopt fr = AE-ID rqi = (token-string)
3	(T8) Mcn	PRO Check HTTP	Group Hosting CSE sends a Group Message Delivery Request to the SCEF Method = POST URI = to {apiRoot}/3gpp-group-message-delivery-mb2 /v1/{scsAsId}/ tmgi-allocation{tmgi }/delivery-via-mbms Payload shall include GMDViaMBMSByMb2data structure with the following attributes included in the request: externalGroupId, mbmsLocArea, messageDeliveryStartTime, notificationDestination
4		IOP Check	Check that SCEF has responded to the Group Message Check that SCEF has sent Group Message Delivery Notification to Group Hosting CSE
5		IOP Check	Check that Group Hosting CSE has responded to the Group Message Delivery Notification
6		IOP Check	Check that Member Hosting CSE has sent response message within the scope of responseTimeWindow
7		IOP Check	Check that Group Hosting CSE has received the response messages from Member Hosting CSEs until responseTimeWindow expires and returned the aggregated group member responses to the IN-AE/CSE
IOP Verdict
PRO Verdict

8.8 Advanced Subscriptions & Notifications management

8.8.1 Notification Target removal procedure

Interoperability Test Description
Identifier:			TD_M2M_NH_137
Objective:			AE removes notificationTargetMgmtPolicyRef via a notificationTargetMgmtPolicyRef Delete Request
Configuration:			M2M_CFG_10
References:			oneM2M TS-0001 [1], clause 10.2.10.8 oneM2M TS-0004 [2], clause 7.4.33.2.4
Pre-test conditions:			AE1 has created an Application Entity resource on Registrar CSE AE1 has created a resource on Registrar CSE AE1 has created a resource on Registrar CSE, where policyLabel = "default", action = "accept" AE2 has created an Application Entity resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a notificationTargetSelfReference Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource/ntsr fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
4		IOP Check	Check if possible that the registrar CSE has removed the AE2 in the notificationURI attribute in the resource
5		IOP Check	AE2 indicates successful operation
IOP Verdict
PRO Verdict

8.8.2 NotificationTargetMgmtPolicyRef management

8.8.2.1 NotificationTargetMgmtPolicyRef Create

Interoperability Test Description
Identifier:			TD_M2M_NH_138
Objective:			AE creates a notificationTargetMgmtPolicyRef resource in registrar CSE via a notificationTargetMgmtPolicyRef Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.10 oneM2M TS-0004 [2], clause 7.4.30.2.1
Pre-test conditions:			AE has created an application resource on registrar CSE AE has created a resource on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a notificationTargetMgmtPolicyRef>
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) ty = 25 (notificationTargetMgmtPolicyRef) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.2.2 NotificationTargetMgmtPolicyRef Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_139
Objective:			AE retrieves notificationTargetMgmtPolicyRef resource from Registrar CSE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.11 oneM2M TS-0004 [2], clause 7.4.30.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a subscription resource on Registrar CSE AE has created a on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.2.3 NotificationTargetMgmtPolicyRef Update

Interoperability Test Description
Identifier:			TD_M2M_NH_140
Objective:			AE updates information about a notificationTargetMgmtPolicyRef via notificationTargetMgmtPolicyRef>Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.12 oneM2M TS-0004 [2], clause 7.4.30.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a subscription resource on Registrar CSE AE has created a subscription resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a notificationTargetMgmtPolicyRef Update Request to update the notificationlPolicyID attribute of the resource.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.2.4 NotificationTargetMgmtPolicyRef Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_141
Objective:			AE removes notificationTargetMgmtPolicyRef via a notificationTargetMgmtPolicyRef Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.12 oneM2M TS-0004 [2], clause 7.4.30.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a notificationTargetMgmtPolicyRef resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a notificationTargetMgmtPolicyRef Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
4		IOP Check	Check if possible that the resource has been removed in registrar CSE.
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

Editor's Note: it should be added some tests to verify the functionality brought by the resource is accomplished.

8.8.3 NotificationTargetPolicy management

8.8.3.1 NotificationTargetPolicy Create

Interoperability Test Description
Identifier:			TD_M2M_NH_142
Objective:			AE creates a notificationTargetPolicy resource in registrar CSE via a notificationTargetPolicy Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.14 oneM2M TS-0004 [2], clause 7.4.31.2.1
Pre-test conditions:			AE has created an application resource on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 26 (notificationTargetPolicy) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.3.2 NotificationTargetPolicy Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_143
Objective:			AE retrieves notificationTargetPolicy resource from Registrar CSE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.15 oneM2M TS-0004 [2], clause 7.4.31.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.3.3 NotificationTargetPolicy Update

Interoperability Test Description
Identifier:			TD_M2M_NH_144
Objective:			AE updates information about a notificationTargetPolicy via Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.16 oneM2M TS-0004 [2], clause 7.4.31.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a notificationTargetPolicy resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a notificationTargetPolicy Update Request to update the policyLabel attribute of the resource.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.3.4 NotificationTargetPolicy Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_145
Objective:			AE removes notificationTargetPolicy via a Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.17 oneM2M TS-0004 [2], clause 7.4.31.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a notificationTargetPolicy resource on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a notificationTargetPolicy Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
4		IOP Check	Check if possible that the resource is deleted in registrar CSE.
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

Editor's Note: It should be added sopme tests to verify the functionality brought by the resource is accomplished.

8.8.4 PolicyDeletionRules management

8.8.4.1 PolicyDeletionRules Create

Interoperability Test Description
Identifier:			TD_M2M_NH_146
Objective:			AE creates a policyDeletionRules resource in registrar CSE via a policyDeletionRules Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.18 oneM2M TS-0004 [2], clause 7.4.32.2.1
Pre-test conditions:			AE has created an application resource on registrar CSE AE has created a on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/ URI of fr = AE-ID rqi = (token-string) ty = 27 (policyDeletionRules) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.4.2 PolicyDeletionRules Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_147
Objective:			AE retrieves policyDeletionRules resource from Registrar CSE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.19 oneM2M TS-0004 [2], clause 7.4.32.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a on Registrar CSE AE has created a as a child of on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.4.3 PolicyDeletionRules Update

Interoperability Test Description
Identifier:			TD_M2M_NH_148
Objective:			AE updates information about a policyDeletionRules via Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.20 oneM2M TS-0004 [2], clause 7.4.32.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a on Registrar CSE AE has created a as a child of on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a policyDeletionRules Update Request to update the deletionRulesRelation attribute of the resource.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.4.4 PolicyDeletionRules Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_149
Objective:			AE removes policyDeletionRules via a Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.21 oneM2M TS-0004 [2], clause 7.4.32.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a on Registrar CSE AE has created a as a child of on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a policyDeletionRules Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
4		IOP Check	Check if possible that the resource has been removed in registrar CSE.
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

Editor's Note: It should be added some tests to verify the functionality brought by the resource is accomplished.

8.8.5 CrossResourceSubscription management

8.8.5.1 CrossResourceSubscription Create

Interoperability Test Description
Identifier:			TD_M2M_NH_150
Objective:			AE creates a crossResourceSubscription resource in registrar CSE via a crossResourceSubscription Create Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.22 oneM2M TS-0004 [2], clause 7.4.58.2.1
Pre-test conditions:			AE has created an application resource on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE sends a request to create a where regularResourcesAsTarget = AE-ID
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName} fr = AE-ID rqi = (token-string) ty = 48 (crossResourceSubscription) pc = Serialized representation of resource
3		IOP Check	Check if possible that the resource is created in registrar CSE Check if possible that the resource is created as a child of resource in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.5.2 CrossResourceSubscription Retrieve

Interoperability Test Description
Identifier:			TD_M2M_NH_151
Objective:			AE retrieves crossResourceSubscription resource from Registrar CSE
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.23 oneM2M TS-0004 [2], clause 7.4.58.2.2
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a Retrieve Request for a
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc =2000 (OK) rqi = (token-string) same as received in request message pc = Serialized representation of resource
4		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.5.3 CrossResourceSubscription Update

Interoperability Test Description
Identifier:			TD_M2M_NH_152
Objective:			AE updates information about a crossResourceSubscription via Update Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.24 oneM2M TS-0004 [2], clause 7.4.58.2.3
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a on Registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a crossResourceSubscription Update Request to update the regularResourcesAsTarget attribute of the resource.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check if possible that the resource is updated in Registrar CSE. If regularResourcesAsTarget contains new target resources, check if possible that resources are created to each new target resource.
4	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.5.4 CrossResourceSubscription Delete

Interoperability Test Description
Identifier:			TD_M2M_NH_153
Objective:			AE removes crossResourceSubscription via a Delete Request
Configuration:			M2M_CFG_01
References:			oneM2M TS-0001 [1], clause 10.2.10.21 oneM2M TS-0004 [2], clause 7.4.32.2.4
Pre-test conditions:			AE has created an Application Entity resource on Registrar CSE AE has created a on Registrar CSE Registrar CSE has created resources as targets of
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE is requested to send a crossResourceSubscription Delete Request
2	Mca	PRO Check Primitive	op = 4 (Delete) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = empty
3	Mca	PRO Check Primitive	rsc = 2002 (DELETED) rqi = (token-string) same as received in request message pc = empty
4		IOP Check	Check if possible that the resource is deleted in registrar CSE. Check if possible that the target resources are deleted in registrar CSE.
5		IOP Check	AE indicates successful operation
IOP Verdict
PRO Verdict

8.8.5.5 Cross-Resource Notification

Interoperability Test Description
Identifier:			TD_M2M_NH_154
Objective:			AE receives a notification request from the HOST CSE
Configuration:			M2M_CFG_10
References:			oneM2M TS-0001 [1], clause 10.2.10.26
Pre-test conditions:			AE1 has created an application resource on registrar CSE AE1 has created on registrar CSE AE1 has created a container1 resource on registrar CSE AE1 has created a container2 resource on registrar CSE AE2 has permissions to UPDATE the container1 and container2 created by AE1 Registrar CSE has created resources as a child resource of a container1 and container2 as a target of resource
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send an Update request to the container1 created by AE1. This triggers the timer as indicated in timeWindowSize attribute of
2		Stimulus	AE2 is requested to send an Update request to the container2 created by AE1 within the time frame indicated in timeWindowSize after the 1st request. This triggers or causes the Registrar CSE to send a notification to AE1.
3	Mca	PRO Check Primitive	op = 5 (Notify) to = notificationURI of subscription resource from = Registrar CSE-ID rqi = (token-string) pc = Serialized representation of Notification data object
3		IOP Check	Check if the notification representation
4	Mca	PRO Check Primitive	Sent response contains rsc = 2000 (OK) rqi = (token-string) same as received in request message
5		IOP Check	AE1 indicates notification received
IOP Verdict
PRO Verdict

8.9 Modbus Interworking

8.9.1 Modbus Thermometer Device Create

Interoperability Test Description
Identifier:			TD_M2M_NH_163
Objective:			AE1 creates Device Model for Modbus device
Configuration:			M2M_CFG_10
References:			oneM2M TS-0040 [], clause 6.3
Pre-test conditions:			AE1 is running in Modbus IPE AE1 has created an application resource on registrar CSE
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 sends a request to create a resource for Modbus deviceThermometer
2	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource fr = AE1-ID rqi = (token-string) ty = 28 (flexContainer) pc = Serialized representation of resource with proper containerDefinition
3		IOP Check	Check if possible that the resource is created in registrar CSE.
4	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
5		IOP Check	AE indicates successful operation
6		Stimulus	AE1 sends a request to create a for temperature
7	Mca	PRO Check Primitive	op = 1 (Create) to = {CSEBaseName}/URI of resource/resource name of Modbus deviceLight fr = AE1-ID rqi = (token-string) ty = 28 (flexContainer) pc = Serialized representation of resource with proper containerDefinition and nodnProperties
8		IOP Check	Check if possible that the resource is created in registrar CSE.
9	Mca	PRO Check Primitive	rsc = 2001 (CREATED) rqi = (token-string) same as received in request message pc = Serialized representation of resource
10		IOP Check	AE indicates successful operation
Note		Optional: Repeat steps 5-10 for battery Module
IOP Verdict
PRO Verdict

8.9.2 Retrieve data from a Modbus Thermometer device

Interoperability Test Description
Identifier:			TD_M2M_NH_164
Objective:			Modbus IPE reads data from Modbus device and updates Registrar CSE with the read data
Configuration:			M2M_CFG_10
References:			oneM2M TS-0040 [], clause 6.5.1
Pre-test conditions:			AE1 is running in Modbus IPE AE1 has created an application resource on registrar CSE AE1 has created a for deviceThermometer AE1 has created a for temperature as a child of deviceThermometer AE2 has created an application resource on registrar CSE AE2 has created a resource as a child of temperature
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 sends a request to retrieve a resource for temperature
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of resource/ temperature fr = AE1-ID rqi = (token-string)
3	Mca	PRO Check Primitive	pc = Serialized representation of resource rsc = 2000 (OK)
4		IOP Check	AE1 indicates successful operation
5		Stimulus	Modbus IPE sends a request(s) to retrieve data from Modbus Thermometer device
6		IOP Check	Check if possible that Modbus IPE has successfully retrieved data from Modbus device
7		Stimulus	AE1 sends a request to update a resource for deviceThermometer
8	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of deviceThermometer/temperature fr = AE1-ID rqi = (token-string) pc = Serialized representation of updated resource
9	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
10		IOP Check	Check if possible that the < flexContainer > resource for temperature is updated in Registrar CSE. Registrar CSE sends a notification to AE2
11	Mca	PRO Check Primitive	op = 5 (Notify) to = AE2-ID from = Registrar CSE-ID rqi = (token-string) pc = Serialized representation of Notification data object
12	Mca	PRO Check Primitive	AE2 responds to notification rsc = 2000 (OK) rqi = (token-string) same as received in request message
13		IOP Check	AE2 indicates notification received
IOP Verdict
PRO Verdict

8.9.3 Write data to a Modbus Thermometer device

Interoperability Test Description
Identifier:			TD_M2M_NH_165
Objective:			AE writes data into a Modbus device by updating resource in Registrar CSE
Configuration:			M2M_CFG_10
References:			oneM2M TS-0040 [], clause 6.5.2
Pre-test conditions:			AE1 is running in Modbus IPE AE1 has created an application resource on registrar CSE AE1 has created a for deviceThermometer AE1 has created a for temperature as a child of deviceThermometer AE2 has created an application resource on registrar CSE AE2 has created a resource as a child of temperature (notificationEventType = Blocking_Update)
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a flexContainer Update Request to update the any customAttribute of the resource.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of resource fr = AE-ID rqi = (token-string) pc = Serialized representation of updated resource
3		IOP Check	Check that Registrar CSE sent a notification to AE1
4	Mca	PRO Check Primitive	op = 5 (Notify) to = AE1-ID from = Registrar CSE-ID rqi = (token-string) pc = Serialized representation of Notification data object
5		Stimulus	Modbus IPE sends a request(s) to write data to Modbus Thermometer device
6		IOP Check	Check if possible that Modbus IPE has successfully written data to Modbus device
7		Stimulus	AE1 sends a response to notification to Registrar CSE
8	Mca	PRO Check Primitive	Sent response contains rsc = 2000 (OK) rqi = (token-string) same as received in request message
9	Mca	PRO Check Primitive	Registrar CSE sends a response to AE2 rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
10		IOP Check	AE2 indicates successful operation
IOP Verdict
PRO Verdict

8.10 NoDN Interworking

8.10.1 Retrieve data from a NoDN device

Interoperability Test Description
Identifier:			TD_M2M_NH_166
Objective:			NoDN IPE reads data from a NoDN device and updates Registrar CSE with the read data
Configuration:			M2M_CFG_10
References:
Pre-test conditions:			AE1 is running in NoDN IPE AE1 has created an application resource on registrar CSE AE1 has created a representing NoDN DeviceClass AE1 has created a for the ModuleClass as a child of the DeviceClass representing the NoDN device AE2 has created an application resource on registrar CSE AE2 has created a resource as a child of the ModuleClass
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE1 sends a request to retrieve a resource for the ModuleClass
2	Mca	PRO Check Primitive	op = 2 (Retrieve) to = {CSEBaseName}/URI of ModuleClass fr = AE1-ID rqi = (token-string)
3	Mca	PRO Check Primitive	pc = Serialized representation of resource rsc = 2000 (OK)
4		IOP Check	AE1 indicates successful operation
5		Stimulus	NoDN IPE retrieves data from NoDN device
6		IOP Check	Check if possible that NoDN IPE has successfully retrieved data from NoDN device
7		Stimulus	AE1 sends a request to update a resource for the ModuleClass
8	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of the ModuleClass fr = AE1-ID rqi = (token-string) pc = Serialized representation of the updated ModuleClass
9	Mca	PRO Check Primitive	rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of resource
10		IOP Check	Check if possible that the resource for the ModuleClass is updated in Registrar CSE. Registrar CSE sends a notification to AE2
11	Mca	PRO Check Primitive	op = 5 (Notify) to = AE2-ID from = Registrar CSE-ID rqi = (token-string) pc = Serialized representation of Notification data object
12	Mca	PRO Check Primitive	AE2 responds to notification rsc = 2000 (OK) rqi = (token-string) same as received in request message
13		IOP Check	AE2 indicates notification received
IOP Verdict
PRO Verdict

8.10.2 Write data to a NoDN device

Interoperability Test Description
Identifier:			TD_M2M_NH_167
Objective:			AE writes data into a NoDN device by updating resource in Registrar CSE
Configuration:			M2M_CFG_10
References:
Pre-test conditions:			AE1 is running in NoDN IPE AE1 has created an application resource on registrar CSE AE1 has created a representing the NoDN DeviceClass AE1 has created a for the ModuleClass as a child of the DeviceClass representing the NoDN device AE2 has created an application resource on registrar CSE AE2 has created a resource as a child of the ModuleClass (notificationEventType = Blocking_Update)
Test Sequence
Step	RP	Type	Description
1		Stimulus	AE2 is requested to send a flexContainer Update Request to update any customAttribute of the ModuleClass.
2	Mca	PRO Check Primitive	op = 3 (Update) to = {CSEBaseName}/URI of the ModuleClass fr = AE-ID rqi = (token-string) pc = Serialized representation of the updated ModuleClass
3		IOP Check	Check that Registrar CSE sent a notification to AE1
4	Mca	PRO Check Primitive	op = 5 (Notify) to = AE1-ID from = Registrar CSE-ID rqi = (token-string) pc = Serialized representation of Notification data object
5		Stimulus	NoDN IPE sends a request(s) to write data to NoDN device
6		IOP Check	Check if possible that NoDN IPE has successfully written data to NoDN device
7		Stimulus	AE1 sends a response to notification to Registrar CSE
8	Mca	PRO Check Primitive	Sent response contains rsc = 2000 (OK) rqi = (token-string) same as received in request message
9	Mca	PRO Check Primitive	Registrar CSE sends a response to AE2 rsc = 2004 (Updated) rqi = (token-string) same as received in request message pc = Serialized representation of the ModuleClass
10		IOP Check	AE2 indicates successful operation
IOP Verdict
PRO Verdict