hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.1.4 <Resource> retrieve | <Resource> Identifier Refs IOP Verdict PRO Verdict <container> TD_M2M_SH_02#01 ETSI TS 118 101 [1], clause 10.2.4.2 oneM2M TS-0004 [2], clause 7.3.5.2.2 <contentInstance> TD_M2M_SH_02#02 ETSI TS 118 101 [1], clause 10.2.19.3 oneM2M TS-0004 [2], clause 7.3.6.2.2 <subscription> TD_M2M_SH_02#03 ETSI TS 118 101 [1], clause 10.2.11.3 oneM2M TS-0004 [2], clause 7.3.7.2 <accessControlPolicy> TD_M2M_SH_02#04 ETSI TS 118 101 [1], clause 10.2.21.2 oneM2M TS-0004 [2], clause 7.3.1.2 <group> TD_M2M_SH_02#05 ETSI TS 118 101 [1], clause 10.2.7.3 oneM2M TS-0004 [2], clause 7.3.12.2.2 <pollingChannel> TD_M2M_SH_02#06 ETSI TS 118 101 [1], clause 10.2.13.3 oneM2M TS-0004 [2], clause 7.3.21.2.2 <fanOutPoint> TD_M2M_SH_02#07 ETSI TS 118 101 [1], clause 10.2.7.8 oneM2M TS-0004 [2], clause 7.3.14.3.2 <node> TD_M2M_SH_02#08 ETSI TS 118 101 [1], clause 10.2.14.2 oneM2M TS-0004 [2], clause 7.3.18.2.2 <remoteCSE> TD_M2M_SH_02#09 ETSI TS 118 101 [1], clause 10.2.2.3 oneM2M TS-0004 [2], clause 7.3.3.2.3 <ae> TD_M2M_SH_02#10 ETSI TS 118 101 [1], clause 10.2.1.2 oneM2M TS-0004 [2], clause 7.3.5.2.2 <CSEBase> TD_M2M_SH_02#11 ETSI TS 118 101 [1], clause 10.2.3.2 oneM2M TS-0004 [2], clause 7.3.2 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 94 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.1.5 Resource Update (Generic Test Description) | Interoperability Test Description Identifier: TD_M2M_SH_03 Objective: AE updates a remote <Resource> resource Configuration: M2M_CFG_03 References: Pre-test conditions: • Parents resources need to be created on the hosting CSE • Resource <Resource> has been created in Hosting CSE Test Sequence Step RP Type Description 1 Stimulus AE is requested to send an Update Request to update the <Resource> on the Hosting CSE 2 Mca PRO Check Primitive • op = 3 (Update) • to = URI of the resource <Resource> • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of <Resource> 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 <Resource> • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of <Resource> resource 5 IOP Check Check if possible that the <Resource> 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> 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> resource 9 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.1.6 <Resource> update | <Resource> Identifier Refs IOP Verdict PRO Verdict <container> TD_M2M_SH_03#01 ETSI TS 118 101 [1], clause 10.2.4.3 oneM2M TS-0004 [2], clause 7.3.5.2.3 <subscription> TD_M2M_SH_03#02 ETSI TS 118 101 [1], clause 10.2.11.4 oneM2M TS-0004 [2], clause 7.3.7.2 <accessControlPolicy> TD_M2M_SH_03#03 ETSI TS 118 101 [1], clause 10.2.21.3 oneM2M TS-0004 [2], clause 7.3.1.2 <group> TD_M2M_SH_03#04 ETSI TS 118 101 [1], clause 10.2.7.4 oneM2M TS-0004 [2], clause 7.3.12.2.3 <pollingChannel> TD_M2M_SH_03#05 ETSI TS 118 101 [1], clause 10.2.13.4 oneM2M TS-0004 [2], clause 7.3.21.2.3 <fanOutPoint> TD_M2M_SH_03#06 ETSI TS 118 101 [1], clause 10.2.7.9 oneM2M TS-0004 [2], clause 7.3.14.3.3 <node> TD_M2M_SH_03#07 ETSI TS 118 101 [1], clause 10.2.14.3 oneM2M TS-0004 [2], clause 7.3.18.2.3 <remoteCSE> TD_M2M_SH_03#08 ETSI TS 118 101 [1], clause 10.2.2.3 oneM2M TS-0004 [2], clause 7.3.3.2.3 <ae> TD_M2M_SH_03#09 ETSI TS 118 101 [1], clause 10.2.1.3 oneM2M TS-0004 [2], clause 7.3.5.2.3 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 95 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.1.7 Resource Delete (Generic Test Description) | Interoperability Test Description Identifier: TD_M2M_SH_04 Objective: AE delete a remote <Resource> resource Configuration: M2M_CFG_03 References: Pre-test conditions: • Parents resources need to be created on the hosting CSE • Resource <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 <Resource> on the Hosting CSE 2 Mca PRO Check Primitive • op = 4 (Delete) • to = URI of the resource <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 <Resource> • fr = AE-ID • rqi = (token-string) 5 IOP Check Check if possible that the <Resource> 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.1.8 <Resource> delete | <Resource> Identifier Refs IOP Verdict PRO Verdict <container> TD_M2M_SH_04#01 ETSI TS 118 101 [1], clause 10.2.4.4 oneM2M TS-0004 [2], clause 7.3.5.2.4 <contentInstance> TD_M2M_SH_04#02 ETSI TS 118 101 [1], clause 10.2.19.5 oneM2M TS-0004 [2], clause 7.3.6.2.4 <subscription> TD_M2M_SH_04#03 ETSI TS 118 101 [1], clause 10.2.11.5 oneM2M TS-0004 [2], clause 7.3.7.2 <accessControlPolicy> TD_M2M_SH_04#04 ETSI TS 118 101 [1], clause 10.2.21.4 oneM2M TS-0004 [2], clause 7.3.1.2 <group> TD_M2M_SH_04#05 ETSI TS 118 101 [1], clause 10.2.7.5 oneM2M TS-0004 [2], clause 7.3.12.2.4 <pollingChannel> TD_M2M_SH_04#06 ETSI TS 118 101 [1], clause 10.2.13.5 oneM2M TS-0004 [2], clause 7.3.21.2.4 <fanOutPoint> TD_M2M_SH_04#07 ETSI TS 118 101 [1], clause 10.2.7.10 oneM2M TS-0004 [2], clause 7.3.14.3.4 <node> TD_M2M_SH_04#08 ETSI TS 118 101 [1], clause 10.2.14.4 oneM2M TS-0004 [2], clause 7.3.18.2.4 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 96 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 101 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.2.3.13 Pre-test conditions: • Two <Container> resources with labels "key1" and "key2" are created in Hosting CSE • A <Group> 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 <Container> 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 <Container> resources 7 IOP Check AE indicates successful operation ETSI ETSI TS 118 113 V3.3.1 (2021-09) 97 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <accessControlPolicy> resource with name {ACPName} has been created in remote hosting CSE, not allowing delete operation • AE has created an <AE> resource on registrar CSE with name {AEName} • AE has created a <container> sub-resource in the <AE> resource with name {containerName} and having as accessControlPolicy-ID the ID of the remote <accessControlPolicy> Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Request to delete the <container> 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 <accessControlPolicy> 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 <accessControlPolicy> 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 <container> resource has not been deleted 10 IOP Check AE indicates unsuccessful operation (Delete error - no privilege) |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 101 [1], clause 10.2.12 oneM2M TS-0004 [2], clause 7.4.1 Pre-test conditions: • A <container> resource has been created on hosting CSE • AE has created an <AE> resource on registrar CSE • AE has created a <subscription> resource for the <container> resource on the remote hosting CSE Test Sequence Step RP Type Description 1 Stimulus A <contentInstance> sub-resource is created on the <container> resource. This triggers or causes the hosting CSE to send a notification to AE ETSI ETSI TS 118 113 V3.3.1 (2021-09) 98 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 <container> resource has not been deleted 10 IOP Check AE indicates unsuccessful operation (Delete error - no privilege) |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.2 <mgmtObj> Test Description | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.2.1 <mgmtObj> Create | Interoperability Test Description Identifier: TD_M2M_SH_05 Objective: AE creates a <mgmtObj> resource Configuration: M2M_CFG_03 References: ETSI TS 118 101 [1], clause 10.2.8.8 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 <mgmtObj> Create Request to create an <mgmtObj> 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 <mgmtObj> resource 3 IOP Check Check if possible that the <mgmtObj> 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 <mgmtObj> and MO can be referenced from clause 5.3 of ETSI TS 118 105 [10] PRO Check BBF TR069 Requests to create the corresponding information model using AddObject RPC. The mapping of <mgmtObj> and information model or RPC can be referenced from clause 7 of ETSI TS 118 106 [11] PRO Check OMA LWM2M Requests to create the corresponding Objects using Create LWM2M Create operations. The mapping of <mgmtObj> and Object can be referenced from clause 6.3 of ETSI TS 118 105 [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 ETSI TS 118 105 [10] ETSI ETSI TS 118 113 V3.3.1 (2021-09) 99 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description PRO Check BBF TR069 Successful response of the RPC. Details can be found in clause 8.1 ETSI TS 118 106 [11] PRO Check OMA LWM2M Response with status code 2.01 Created. Details can be found in clause 6.4 ETSI TS 118 105 [10] 7 Mca PRO Check Primitive • rsc = 2001 (CREATED) • rqi = (token-string) same as received in request message • pc = Serialized representation of <mgmtObj> resource 8 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.2.2 <mgmtObj> Update | Interoperability Test Description Identifier: TD_M2M_SH_06 Objective: AE updates a <mgmtObj> resource Configuration: M2M_CFG_03 References: ETSI TS 118 101 [1], clause 10.2.8.10 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 <mgmtObj> Update Request to update an <mgmtObj> 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 <mgmtObj> resource 3 IOP Check Check if possible that the <mgmtObj> 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 <mgmtObj> and MO can be referenced from clause 5.3 of ETSI TS 118 105 [10] PRO Check BBF TR069 Requests to Update the corresponding information model using SetParameterValues RPC. The mapping of <mgmtObj> and information model or RPC can be referenced from clause 7 of ETSI TS 118 106 [11] PRO Check OMA LWM2M Requests to Update the corresponding Objects using LWM2M Write operations. The mapping of <mgmtObj> and Object can be referenced from clause 6.3 of ETSI TS 118 105 [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 ETSI TS 118 105 [10] PRO Check BBF TR069 Successful response of the RPC. Details can be found in clause 8.1 ETSI TS 118 106 [11] PRO Check OMA LWM2M Response with status code 2.04 Changed. Details can be found in clause 6.4 ETSI TS 118 105 [10] 7 Mca PRO Check Primitive • rsc = 2004 (CHANGED) • rqi = (token-string) same as received in request message • pc = Serialized representation of <mgmtObj> resource 8 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 100 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.2.3 <mgmtObj> Retrieve | Interoperability Test Description Identifier: TD_M2M_SH_07 Objective: AE retrieves a <mgmtObj> resource Configuration: M2M_CFG_03 References: ETSI TS 118 101 [1], clause 10.2.8.9 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 <mgmtObj> Retrieve Request to retrieve an <mgmtObj> 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 <mgmtObj> 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 ETSI TS 118 105 [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 ETSI TS 118 106 [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 ETSI TS 118 105 [10] 7 Mca PRO Check Primitive • rsc = 2000 (OK) • rqi = (token-string) same as received in request message • pc = Serialized representation of <mgmtObj> resource 8 IOP Check AE indicates successful operation IOP Verdict PRO Verdict 8.3.2.4 <mgmtObj> Delete Interoperability Test Description Identifier: TD_M2M_SH_08 Objective: AE deletes a <mgmtObj> resource Configuration: M2M_CFG_03 References: ETSI TS 118 101 [1], clause 10.2.8.11 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 <mgmtObj> Delete Request to delete an <mgmtObj> 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 <mgmtObj> 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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 101 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 ETSI TS 118 105 [10] PRO Check BBF TR069 Successful response of the RPC. Details can be found in clause 8.1 ETSI TS 118 106 [11] PRO Check OMA LWM2M Response with status code 2.02 Deleted. Details can be found in clause 6.4 ETSI TS 118 105 [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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.3 Announcement Management | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 • <CSEBase> resource has been created in CSE1 with name {CSEBaseName1} • AE1 has created a <AE> resource on registrar CSE with name {AE1} • <CSEBase> 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 <AE> resource 3 IOP Check Check if possible that the CREATE <AEannc> 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 <AEAnnc> resource 5 IOP Check Check if possible that the <AEAnnc> 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 <AEAnnc> 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 <AE> resource 9 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 102 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 • <CSEBase> resource has been created in CSE1 with name {CSEBaseName1} • AE1 has created a <AE> resource on registrar CSE with name {AE1} • <CSEBase> resource has been created in CSE2 with name {CSEBaseName2} • AE2 has created a <AE> resource on registrar CSE with name {AE2} • CSE1 is registered to CSE2 • <container> 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 <container> 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 <container> resource 3 IOP Check Check if possible that the CREATE <ContainerAnnc> 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 <container> resource 9 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 • <CSEBase> resource has been created in CSE1 with name {CSEBaseName1} • AE1 has created a <AE> resource on registrar CSE with name {AE1} • <CSEBase> resource has been created in CSE2 with name {CSEBaseName2} • AE2 has created a <AE> resource on registrar CSE with name {AE2} • CSE1 is registered to CSE2 • <container> resource is created as a child of AE1 • AE1 is announced on CSE2 • <container> is announced on CSE2 Test Sequence Step RP Type Description 1 Stimulus AE1 is requested to send a an <container> Update Request with announcedAttribute = maxNrOfInstances ETSI ETSI TS 118 113 V3.3.1 (2021-09) 103 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 2 Mca PRO Check Primitive • op = 3 (Update) • to = {CSEBaseName}/{container} • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of updated <container> resource 3 IOP Check Check if possible that the UPDATE <ContainerAnnc> 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 <container> resource 9 IOP Check AE1 indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: • <CSEBase> resource has been created in CSE1 with name {CSEBaseName1} • AE1 has created a <AE> resource on registrar CSE with name {AE1} • <CSEBase> resource has been created in CSE2 with name {CSEBaseName2} • AE2 has created a <AE> resource on registrar CSE with name {AE2} • CSE1 is registered to CSE2 • <container> resource is created as a child of AE1 • AE1 is announced on CSE2 • <container> 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 <containerAnnc> resource 4 IOP Check AE indicates successful operation IOP Verdict Verify that this is a containAnnc resource PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 104 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 • <CSEBase> resource has been created in CSE1 with name {CSEBaseName1} • AE1 has created a <AE> resource on registrar CSE with name {AE1} • <CSEBase> resource has been created in CSE2 with name {CSEBaseName2} • AE2 has created a <AE> resource on registrar CSE with name {AE2} • CSE1 is registered to CSE2 • <container> resource is created as a child of AE1 • AE1 is announced on CSE2 • <container> 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 <container> 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 <container> 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 <container> resource 9 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 101 [1], clause 10.2.13.4 Pre-test conditions • <CSEBase> resource has been created in CSE1 with name {CSEBaseName1} • AE1 has created a <AE> resource on registrar CSE with name {AE1} • <CSEBase> resource has been created in CSE2 with name {CSEBaseName2} • CSE1 is registered to CSE2 • AE1 is announced on CSE2 • <container> 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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 105 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 2 Mca PRO Check Primitive • op = 3 (Update) • to = {CSEBaseName1}/{AE1}/{container} • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of updated <container> resource 3 IOP Check Check if possible that the DELETE <containerAnnc> 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 <containerAnnc> 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 <container> resource 9 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 101 [1], clause 10.2.13.4 Pre-test conditions • <CSEBase> resource has been created in CSE1 with name {CSEBaseName1} • AE1 has created a <AE> resource on registrar CSE with name {AE1} • <CSEBase> resource has been created in CSE2 with name {CSEBaseName2} • CSE1 is registered to CSE2 • AE1 is announced on CSE2 • <container> 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 <containerAnnc> 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 <containerAnnc> 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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 106 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 101 [1], clause 10.2.13.7 Pre-test conditions • <CSEBase> resource has been created in CSE1 with name {CSEBaseName1} • AE1 has created a <AE> resource on registrar CSE with name {AE1} • <CSEBase> resource has been created in CSE2 with name {CSEBaseName2} • CSE1 is registered to CSE2 • AE1 is announced on CSE2 • <container> 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 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 <container> resource 3 IOP Check Check if possible that the UPDATE <ContainerAnnc> 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 <container> 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 • <CSEBase> resource has been created in CSE1 with name {CSEBaseName1} • AE1 has created a <AE> resource on registrar CSE with name {AE1} • <CSEBase> resource has been created in CSE2 with name {CSEBaseName2} • CSE1 is registered to CSE2 • AE1 is announced on CSE2 • <container> 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 labels attribute ETSI ETSI TS 118 113 V3.3.1 (2021-09) 107 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 2 Mca PRO Check Primitive • op = 3 (Update) • to = {CSEBaseName1}/{AE1}/{container} • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of updated <container> resource 3 IOP Check Check if possible that the UPDATE <ContainerAnnc> 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 <container> resource 9 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 101 [1], clause 10.2.13.8 Pre-test conditions • <CSEBase> resource has been created in CSE1 with name {CSEBaseName1} • AE1 has created a <AE> resource on registrar CSE with name {AE1} • <CSEBase> resource has been created in CSE2 with name {CSEBaseName2} • CSE1 is registered to CSE2 • AE1 is announced on CSE2 • <container> 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 <container> 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 <container> resource 3 IOP Check Check if possible that the UPDATE <ContainerAnnc> 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 <container> resource ETSI ETSI TS 118 113 V3.3.1 (2021-09) 108 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 • <CSEBase> resource has been created in CSE1 with name {CSEBaseName1} • AE1 has created a <AE> resource on registrar CSE with name {AE1} • <CSEBase> resource has been created in CSE2 with name {CSEBaseName2} • CSE1 is registered to CSE2 • AE1 is announced on CSE2 • <container> 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 <container> 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 <container> resource 3 IOP Check Check if possible that the UPDATE <ContainerAnnc> 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 <container> resource 9 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 109 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.4 Single Hop <fanOutPoint> operations | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.4.1 Create <fanOutPoint> | Interoperability Test Description Identifier: TD_M2M_SH_17 Objective: AE creates a <contentInstance> resource in each group member, where some memberIDs are on a remoteCSE Configuration: M2M_CFG_08 References: ETSI TS 118 101 [1], clause 10.2.7.6 oneM2M TS-0004 [2], clause 7.4.14.2, 7.4.14.3 Pre-test conditions • Two or more resources of type <container> exist on the member hosting CSE • A group exists containing these two members of type <container> Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Create Request to create <contentInstance> 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 <contentInstance> 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 <contentInstance> resource 5 IOP Check Check if possible that the <contentInstance> 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 <contentInstance> resource or <aggregated response> 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 <aggregated response> 9 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.4.2 Retrieve <fanOutPoint> | Interoperability Test Description Identifier: TD_M2M_SH_18 Objective: AE retrieves a <container> resource from each group member, where some memberIDs are on a remoteCSE Configuration: M2M_CFG_08 References: ETSI TS 118 101 [1], clause 10.2.7.7 Pre-test conditions: • Two or more resources of type <container> exist on the member hosting CSE • A group exists containing these two members of type <container> Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Retrieve Request to the fanoutPoint of <group> resource ETSI ETSI TS 118 113 V3.3.1 (2021-09) 110 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 <container> 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 <aggregated_response> 8 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.4.3 Update <fanOutPoint> | Interoperability Test Description Identifier: TD_M2M_SH_19 Objective: AE updates a <container> resource in each group member, where some memberIDs are on a remoteCSE Configuration: M2M_CFG_08 References: ETSI TS 118 101 [1], clause 10.2.7.8 Pre-test conditions: • Two or more resources of type <container> exist on the member hosting CSE • A <group> exists containing these two members of type <container> Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Update Request to the fanoutPoint of <group> resource to lifetime of the resource 2 Mca PRO Check Primitive • op = 3 (Update) • to = {CSEBaseName}/{group}/fopt • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of <container> 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 <container> resource 5 IOP Check Check if possible that the <Resource> 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 <container> resource or <aggregated response> 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 <aggregated response> 9 IOP Check AE indicates successful operation ETSI ETSI TS 118 113 V3.3.1 (2021-09) 111 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.3.4.4 Delete <fanOutPoint> | Interoperability Test Description Identifier: TD_M2M_SH_20 Objective: AE deletes a <contentInstance> resource from each group member, where some memberIDs are on a remoteCSE Configuration: M2M_CFG_08 References: ETSI TS 118 101 [1], clause 10.2.7.9 Pre-test conditions: • Two or more resources of type <container> exist on the member hosting CSE • Each <container> has at least 1 <contentInstance> • A group exists containing these two members of type <container> Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Delete 'oldest' Request to the fanoutPoint of <group> 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> 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 <aggregated_response> 9 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 112 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.4 Security management | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.4.1 Secure AE Registration | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [12], clause 8.2.2.1 ETSI TS 118 101 [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 <Registrar CSE-ID> and rlk < URI of serviceSubscribedAppRule > attributes • Registrar CSE is configured with <serviceSubscribedAppRule> resource having a CredentialD, APP-ID and AE-ID with the following values: • <m2m:asar rn="asar"> • <aci>00-test@onem2m.com</aci> • <aai>APP01</aai> • <aae>AE-ID</aae> • </m2m:asar> 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 <AE> resource 5 IOP Check Check that APP-ID, AE-ID, Credential ID are in <serviceSubscribedAppRule> Check if possible that the <AE> 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 <AE> resource 7 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 113 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 114 oneM2M TS-0013 version 3.3.1 Release 3 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: ETSI TS 118 103 [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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 115 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.4.3 Authorization | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.4.3.1 Authorization using selfPrivileges | Interoperability Test Description Identifier: TD_M2M_SE_04 Objective: AE accesses <accessControlPolicy> resource using its selfPrivileges credentials Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 9.6.2.0 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • AE has created an <AE> resource on registrar CSE with name {AE} • accessControlPolicy resource has been created in registrar CSE under <AE> 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 <accessControlPolicy> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 116 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.4.3.2 Authorization using accessControlPolicy privileges | Interoperability Test Description Identifier: TD_M2M_SE_05 Objective: AE accesses <AE> resource using its accessControlPolicyIDs attribute Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 9.6.2.0 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • AE has created an <AE> resource on registrar CSE with name {AE} • accessControlPolicy resource has been created in registrar CSE under <AE> 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 <accessControlPolicy> 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 <AE> resource has not been removed in registrar CSE. 9 IOP Check AE indicates unsuccessful operation (Delete error - no privilege) IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.4.3.3 Authorization using default access privileges (owner is configured) | Interoperability Test Description Identifier: TD_M2M_SE_06 Objective: AE accesses <AE> resource using default access privileges Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 9.6.2.0 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • AE has created an <AE> resource on registrar CSE with name {AE} • <container> resource has been created in registrar CSE under <AE> resource with name {containerName} • accessControlPolicyIDs attribute of {containerName} is NULL • owner attribute of {containerName} = AE-ID ETSI ETSI TS 118 113 V3.3.1 (2021-09) 117 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 <accessControlPolicy> 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.4.3.4 Authorization using default access privileges (owner is not configured) | Interoperability Test Description Identifier: TD_M2M_SE_07 Objective: AE accesses <AE> resource using default access privileges Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 9.6.2.0 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • AE has created an <AE> resource on registrar CSE with name {AE} • <container> resource has been created in registrar CSE under <AE> 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 <accessControlPolicy> 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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 118 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.4.3.5 Direct Dynamic Authorization | Interoperability Test Description Identifier: TD_M2M_SE_08 Objective: AE accesses <AE> resource using Direct Dynamic Authorization Configuration: M2M_CFG_01 References: ETSI TS 118 103 [12] , clause 7.3.2.2 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • AE has created an <AE> resource on registrar CSE with name {AE} • <container> resource has been created in registrar CSE under <AE> resource with name {containerName} • Arbitrary set of <accessControlPolicy> 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 (ETSI TS 118 103 [12], 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 (ETSI TS 118 103 [12], clause 7.3.2.5) 9 IOP Check Check that if dynamicACPInfo present in response content, the Registrar CSE created <accessControlPolicy> 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 <container> 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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 119 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 11 IOP Check If access is granted, AE indicates successful operation, otherwise AE indicates unsuccessful operation (Retrieve error - no privilege) IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.4.3.6 Indirect Dynamic Authorization | Interoperability Test Description Identifier: TD_M2M_SE_09 Objective: AE accesses <AE> resource using Indirect Dynamic Authorization Configuration: M2M_CFG_01 References: ETSI TS 118 103 [12] , clause 7.3.2.3 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • AE has created an <AE> resource on registrar CSE with name {AE} • <container> resource has been created in registrar CSE under <AE> resource with name {containerName} • Arbitrary set of <accessControlPolicy> 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 (ETSI TS 118 103 [12], 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 (ETSI TS 118 103 [12], 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) ETSI ETSI TS 118 113 V3.3.1 (2021-09) 120 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 <container> 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.4.4 Key provisioning management | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [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 ETSI TS 118 103 [12]) IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 121 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [12], clause 8.3.5.2.3 Pre-test conditions: • The MEF Client, and MEF have been provisioned with the parameters described in ETSI TS 118 103 [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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 122 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 123 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [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 (ETSI TS 118 103 [12], clause 8.3.7.3) • The Source MEF Client has performed the MEF Client Registration procedure (ETSI TS 118 103 [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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 124 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 125 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.4.5 End-to-End security management | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 126 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 103 [12], 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) ETSI ETSI TS 118 113 V3.3.1 (2021-09) 127 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 123 [14], clause 5.5.27 Pre-test conditions: • AE1 has created an application resource <AE> on registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE1 sends a request to create a <flexContainer> for deviceLight ETSI ETSI TS 118 113 V3.3.1 (2021-09) 128 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName}/URI of <AE1> resource • fr = AE-ID • rqi = (token-string) • ty = 28 (flexContainer) • pc = Serialized representation of <flexContainer> resource with proper containerDefinition 3 IOP Check Check if possible that the <flexContainer> 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 <flexContainer> resource 5 IOP Check AE indicates successful operation 6 Stimulus AE1 sends a request to create a <flexContainer> for binarySwitch 7 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName}/URI of <AE1> resource/resource name of deviceLight • fr = AE-ID • rqi = (token-string) • ty = 28 (flexContainer) • pc = Serialized representation of <flexContainer> resource with proper containerDefinition 8 IOP Check Check if possible that the <flexContainer> 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 <flexContainer> resource 10 IOP Check AE indicates successful operation Note Optional: Repeat steps 5-10 for additional deviceLight Modules IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 123 [14], clauses 5.5.27, 5.3.12 Pre-test conditions: • AE2 has created an application resource <AE> 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 <flexContainer> for binarySwitch 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <deviceLight> 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 <flexContainer> resource 4 IOP Check AE2 indicates successful operation Note Optional: Repeat steps 1-4 for additional deviceLight Modules IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 129 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 123 [14], clause 5.5.27 Pre-test conditions: • AE2 has created an application resource <AE> 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 <flexContainer> for deviceLight 2 Mca PRO Check Primitive • op = 3 (Update) • to = {CSEBaseName}/ URI of <deviceLight> resource/binarySwitch • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of <flexContainer> resource with new value for powerState 3 IOP Check Check if possible that the <flexContainer> 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 <flexContainer> resource 5 IOP Check AE indicates successful operation Note Optional: Repeat steps 1-5 for additional device states and settings IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 123 [14], clause 5.5.27 Pre-test conditions: • AE2 has created an application resource <AE> 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 <flexContainer> for deviceLight 2 Mca PRO Check Primitive • op = 3 (Update) • to = {CSEBaseName}/ URI of <deviceLight> resource/binarySwitch/toggle • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of <flexContainer> resource for toggle action 3 IOP Check Check if possible that the <flexContainer> 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 <flexContainer> 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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 130 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 123 [14], clause 5.4.1.2 Pre-test conditions: • AE1 has created an application resource <AE> on registrar CSE • AE1 has created a <flexContainer> for deviceSmartPlug Test Sequence Step RP Type Description 1 Stimulus AE1 sends a request to create a <flexContainer> for subDevicePowerOutlet 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName}/URI of <AE1> resource/resource name of deviceSmartPlug • fr = AE-ID • rqi = (token-string) • ty = 28 (flexContainer) • pc = Serialized representation of <flexContainer> resource with proper containerDefinition 3 IOP Check Check if possible that the <flexContainer> 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 <flexContainer> resource 5 IOP Check AE indicates successful operation 6 Stimulus AE1 sends a request to create a <flexContainer> for binarySwitch 7 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName}/URI of <AE1> resource/resource name of subDevicePowerOutlet • fr = AE-ID • rqi = (token-string) • ty = 28 (flexContainer) • pc = Serialized representation of <flexContainer> resource with proper containerDefinition 8 IOP Check Check if possible that the <flexContainer> 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 <flexContainer> resource 10 IOP Check AE indicates successful operation Note Optional: Repeat steps 6-10 for additional subDevicePowerOutlet Modules IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 123 [14], clause 5.3.1.12 Pre-test conditions: • AE1 has created an application resource <AE> on registrar CSE • AE1 has created a <flexContainer> for deviceSmartPlug • AE1 has created a <flexContainer> for binarySwtich as a child of deviceSmartPlug Test Sequence Step RP Type Description 1 Stimulus AE1 sends a request to create a <flexContainer> for Toggle ETSI ETSI TS 118 113 V3.3.1 (2021-09) 131 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName}/URI of <AE1> resource/resource name of binarySwtich • fr = AE-ID • rqi = (token-string) • ty = 28 (flexContainer) • pc = Serialized representation of <flexContainer> resource with proper containerDefinition 3 IOP Check Check if possible that the <flexContainer> 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 <flexContainer> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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: ETSI TS 118 123 [14], clause 6.2.5 Pre-test conditions: • AE1 has created an application resource <AE> on registrar CSE • AE1 has created a <flexContainer> for deviceLight • AE1 has created a <node> 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 <node> 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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 132 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6 Semantics management | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.1 Semantic Access Control Policy management | 8.6.1.1 Procedure for creating ACP triples when a new <accessControlPolicy> resource is created Interoperability Test Description Identifier: TD_M2M_NH_106 Objective: ACP triples are created when a new <accessControlPolicy> 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 <AE> 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}/<AE> • fr = AE-ID • rqi = (token-string) • ty = 1 (accessControlPolicy) • pc = Serialized representation of < accessControlPolicy > resource 3 IOP Check Check if possible that the <accessControlPolicy> resource is created in Registrar CSE Check if possible that Registrar CSE has created ACP Triples in SGS for the new <accessControlPolicy> 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 <accessControlPolicy> resource is updated Interoperability Test Description Identifier: TD_M2M_NH_107 Objective: ACP triples are updated when an existing <accessControlPolicy> 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 <AE> on Registrar CSE • accessControlPolicy resource has been created in registrar CSE under <AE> 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 <accessControlPolicy> resource 3 IOP Check Check if possible that the <accessControlPolicy> resource has been updated in Registrar CSE Check if possible that Registrar CSE has updated corresponding ACP Triples in SGS ETSI ETSI TS 118 113 V3.3.1 (2021-09) 133 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 <accessControlPolicy> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict 8.6.1.3 Procedure for deleting ACP triples when an existing <accessControlPolicy> resource is deleted Interoperability Test Description Identifier: TD_M2M_NH_108 Objective: ACP triples are deleted when an existing <accessControlPolicy> 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 <AE> on Registrar CSE • accessControlPolicy resource has been created in registrar CSE under <AE> 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 <accessControlPolicy> 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <semanticDescriptor> 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 <AE> on Registrar CSE • accessControlPolicy resource has been created in registrar CSE under <AE> 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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 134 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName}/<AE> • fr = AE-ID • rqi = (token-string) • ty = 24 (semanticDescriptor) • pc = Serialized representation of <semanticDescriptor> resource − acpi = URI of {accessControlPolicyName} 3 IOP Check Check if possible that the <semanticDescriptor> 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 <semanticDescriptor> in SGS 4 Mca PRO Check Primitive • rsc = 2001 (CREATED) • rqi = (token-string) same as received in request message • pc = Serialized representation of <semanticDescriptor> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <semanticDescriptor> 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 <AE> on Registrar CSE • accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName} • AE has created a semanticDescriptor resource <semanticDescriptor> as child resource of <AE> 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 <semanticDescriptor> resource • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of updated <semanticDescriptor> resource 3 IOP Check Check if possible that the <semanticDescriptor> 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 <accessControlPolicy> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 135 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <semanticDescriptor> 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 <AE> on Registrar CSE • accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName} • AE has created a semanticDescriptor resource <semanticDescriptor> as child resource of <AE> 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 <semanticDescriptor> resource • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of updated <semanticDescriptor> resource 3 IOP Check Check if possible that the <semanticDescriptor> 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 <accessControlPolicy> 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 <semanticDescriptor> 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 <AE> on Registrar CSE • accessControlPolicy resource has been created in registrar CSE under <AE> resource with name {accessControlPolicyName} • AE has created a semanticDescriptor resource <semanticDescriptor> as child resource of <AE> 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 Check Mca PRO Check Primitive • op = 4 (Detete) • to = {CSEBaseName}/URI of <semanticDescriptor> resource • fr = AE-ID • rqi = (token-string) • pc = empty 3 IOP Check Check if possible that the <semanticDescriptor> 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 <semanticDescriptor> from SGS ETSI ETSI TS 118 113 V3.3.1 (2021-09) 136 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 4 Check 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.2 Semantic Filtering and discovery | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.2.1 Semantic Filtering and Discovery using <semanticFanOutPoint> resource | Interoperability Test Description Identifier: TD_M2M_NH_113 Objective: AE discovers accessible resources residing in Registrar CSE using the <semanticFanOutPoint> Configuration: M2M_CFG_01 References: oneM2M TS-0034 [13], clause 7.4.1 Pre-test conditions: • AE has created an application resource <AE> on Registrar CSE • AE has created <container> resources {container1} and {container2} in registrar CSE under <AE> resource • AE has created a group resource with semanticSupportIndicator attribute set to TRUE and memberIds set to {container1} and {container2} ids • AE has created <semanticDescriptor> 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 <group> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/<AE>/<group>/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 <Container> resources addresses 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 137 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE has created <container> resources {container1} and {container2} in registrar CSE under <AE> resource • AE has created a group resource with semanticSupportIndicator attribute set to TRUE and memberIds set to {container1} and {container2} ids • AE has created <semanticDescriptor> 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 <container> resource using the semanticFilter filterCriteria 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/<AE> • 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 <Container> resources addresses 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE1 has created a container resource <container> on Registrar CSE • AE1 has created a <semanticDescriptor> as a child resource of a <container> Test Sequence Step RP Type Description 1 Stimulus AE1 is requested to send a Semantic Query Operation request to query the <container> resource using a SPARQL query ETSI ETSI TS 118 113 V3.3.1 (2021-09) 138 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 2 Check 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 Check 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.3 Semantic Mashup management | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE sends a request to create a <semanticMashupJobProfile> 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName} • fr = AE-ID • rqi = (token-string) • ty = 40 (semanticMashupJobProfile) • pc = Serialized representation of <semanticMashupJobProfile> resource 3 IOP Check Check if possible that the <semanticDescriptor> 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 <semanticMashupJobProfile> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 139 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE has created a semanticMashupJobProfile resource <semanticMashupJobProfile> as child resource of <AE> resource Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Retrieve Request for a <semanticMashupJobProfile> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <semanticMashupJobProfile> 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 <semanticMashupJobProfile> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.3.3 SemanticMashupJobProfile Update | Interoperability Test Description Identifier: TD_M2M_NH_118 Objective: AE updates attribute in <semanticMashupJobProfile> 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 <AE> on Registrar CSE • AE has created a semanticMashupJobProfile resource <semanticMashupJobProfile> as child resource of <AE> 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 <semanticMashupJobProfile> resource • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of updated <semanticMashupJobProfile> resource 3 IOP Check Check if possible that the <semanticDescriptor> 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 <semanticMashupJobProfile> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 140 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE has created a semanticMashupJobProfile resource <semanticMashupJobProfile> as child of <AE> 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 <semanticMashupJobProfile> resource • fr = AE-ID • rqi = (token-string) • pc = empty 3 IOP Check Check if possible that the <semanticMashupJobProfile> 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 <semanticMashupJobProfile> resource has been removed in Registrar CSE 6 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE sends a request to create a <semanticDescriptor> 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName} • fr = AE-ID • rqi = (token-string) • ty = 41 (semanticMashupInstance) • pc = Serialized representation of <semanticMashupInstance> resource 3 IOP Check Check if possible that the <semanticDescriptor> 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 <semanticMashupInstance> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 141 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE has created a semanticMashupInstance resource <semanticMashupInstance> as child resource of <CSEBase> resource Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Retrieve Request for a <semanticMashupInstance> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <semanticMashupInstance> 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 <semanticMashupInstance> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.3.7 SemanticMashupInstance Update | Interoperability Test Description Identifier: TD_M2M_NH_122 Objective: AE updates attribute in <semanticMashupInstance> 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 <AE> on Registrar CSE • AE has created a semanticMashupInstance resource <semanticMashupInstance> as child resource of <CSEBase> 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 <semanticMashupInstance> resource • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of updated <semanticMashupInstance> resource 3 IOP Check Check if possible that the <semanticDescriptor> 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 <semanticMashupInstance> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 142 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE has created a semanticMashupInstance resource <semanticMashupInstance> as child resource of <CSEBase> 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 <semanticMashupInstance> resource • fr = AE-ID • rqi = (token-string) • pc = empty 3 IOP Check Check if possible that the <semanticMashupInstance> 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 <semanticMashupInstance> resource has been removed in Registrar CSE 6 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE has created a semanticMashupInstance resource <semanticMashupInstance> as child resource of <CSEBase> resource • <semanticMashupResult> resource is created as child resource of <semanticMashupInstance> resource Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Retrieve Request for a <semanticMashupResult> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <semanticMashupInstance> 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 <semanticMashupResult> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 143 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE has created a semanticMashupInstance resource <semanticMashupInstance> as child resource of <CSEBase> resource • <semanticMashupResult> resource is created as child resource of <semanticMashupInstance> 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 <semanticMashupInstance> resource/ URI of <semanticMashupResult> resource • fr = AE-ID • rqi = (token-string) • pc = empty 3 IOP Check Check if possible that the <semanticMashupResult> 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 <semanticMashupResult> resource has been removed in Registrar CSE 6 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <semanticMashupInstance>/<mashup> 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 <AE> on Registrar CSE • AE has created a semanticMashupInstance resource <semanticMashupInstance> as child resource of <CSEBase> resource Test Sequence Step RP Type Description 1 Stimulus AE retrieves a <mashup> resource in a <semanticMashupInstance> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <semanticMashupInstance> resource/msp • fr = AE-ID • rqi = (token-string) • pc = empty 3 IOP Check Check if possible that a <semanticMashupResult> resource is created under the <semanticMashupInstance> resource 4 Mca PRO Check Primitive • rsc = 2000 (OK) • rqi = (token-string) same as received in request message • pc = Serialized representation of <semanticMashupResult> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 144 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.4 Ontology Repository management | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE sends a request to create a <ontologyRepository> 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName} • fr = AE-ID • rqi = (token-string) • ty = 38 (ontologyRepository) • pc = Serialized representation of <ontologyRepository> resource 3 IOP Check Check if possible that the <ontologyRepository> 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 <ontologyRepository> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE has created a ontologyRepository resource <ontologyRepository> as child resource of <AE> resource Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Retrieve Request for a <ontologyRepository> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <ontologyRepository> 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 <ontologyRepository> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 145 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.4.3 OntologyRepository Update | Interoperability Test Description Identifier: TD_M2M_NH_129 Objective: AE updates attribute in <ontologyRepository> 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 <AE> on Registrar CSE • AE has created a ontologyRepository resource <ontologyRepository> as child resource of <AE> 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 <ontologyRepository> resource • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of updated <ontologyRepository> resource 3 IOP Check Check if possible that the <ontologyRepository> 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 <ontologyRepository> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE has created a ontologyRepository resource <ontologyRepository> as child of <AE> 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 <ontologyRepository> resource • fr = AE-ID • rqi = (token-string) • pc = empty 3 IOP Check Check if possible that the <ontologyRepository> 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 <ontologyRepository> resource has been removed in Registrar CSE 6 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 146 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.5 Semantic validation management | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.5.1 Semantic validation independent of <semanticDescriptor> resource operation | Interoperability Test Description Identifier: TD_M2M_NH_131 Objective: AE checks the validity of the <semanticDescriptor> resource via a <semanticValidation> 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 <AE> on Registrar CSE • AE has created a semanticDescriptor resource <semanticDescriptor> as child of <AE> resource Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a <semanticValidation> Update Request to check the validity of the <semanticDescriptor>resource 2 Mca PRO Check Primitive • op = 3 (Update) • to = {CSEBaseName}/URI of <semanticDescriptor> resource/smv • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of <semanticValidation> parameters 3 IOP Check Check if possible that the received <semanticDescriptor> 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.5.2 Semantic validation triggered when Create a semanticDescriptor resource | Interoperability Test Description Identifier: TD_M2M_NH_132 Objective: AE creates a <semanticDescriptor> resource visa SemanticDescriptor Create Request and Registrar CSE checks the validity of the created <semanticDescriptor> 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 <AE> 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 <semanticDescriptor> resource 3 IOP Check Check if possible that the <semanticDescriptor> resource is created in Registrar CSE Check if possible that the semanticValidated attribute of the <semanticDescriptor> 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 <semanticDescriptor> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 147 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.6 Ontology Mapping management | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE sends a request to create a <ontologyMapping> resource 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName} • fr = AE-ID • rqi = (token-string) • ty = 52 (ontologyMapping) • pc = Serialized representation of <ontologyMapping>resource 3 IOP Check Check if possible that the <ontologyMapping> 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 <ontologyMapping> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE has created a ontologyMapping resource <ontologyMapping> as child resource of <AE> resource Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Retrieve Request for a <ontologyMapping> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <ontologyMapping> 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 <ontologyMapping> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 148 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.6.6.3 OntologyMapping Update | Interoperability Test Description Identifier: TD_M2M_NH_135 Objective: AE updates attribute in <ontologyMapping> 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 <AE> on Registrar CSE • AE has created a ontologyMapping resource <ontologyMapping> as child resource of <AE> 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 <ontologyMapping> resource • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of updated <ontologyMapping> resource 3 IOP Check Check if possible that the <ontologyMapping> 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 <ontologyMapping> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on Registrar CSE • AE has created a ontologyMapping resource <ontologyMapping> as child of <AE> 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 <ontologyMapping> resource • fr = AE-ID • rqi = (token-string) • pc = empty 3 IOP Check Check if possible that the <ontologyMapping> 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 <ontologyMapping> resource has been removed in Registrar CSE 6 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 149 oneM2M TS-0013 version 3.3.1 Release 3 8.7 3GPP Interworking |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.7.1 Cellular IoT non-IP data delivery (NIDD) | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <m2mServiceSubscriptionProfile> resource created as a child of <CSEBase> resource • <serviceSubscribedNode> resource is created as a child of <m2mServiceSubscriptionProfile> • Node-ID attribute of <serviceSubscribedNode> 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 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 [15], clause 7.1.1.2 Pre-test conditions: • IN-AE has created an Application Entity resource <AE> on IN-CSE • ADN-AE has created an Application Entity resource <AE> on IN-CSE • IN-CSE has a <m2mServiceSubscriptionProfile> resource created as a child of <CSEBase> resource • <serviceSubscribedNode> resource is created as a child of <m2mServiceSubscriptionProfile> • Node-ID attribute of <serviceSubscribedNode> 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. ETSI ETSI TS 118 113 V3.3.1 (2021-09) 150 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 151 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 [15], clause 7.1.1.3 Pre-test conditions: • IN-AE has created an Application Entity resource <AE> on IN-CSE • ADN-AE has created an Application Entity resource <AE> on IN-CSE • IN-CSE has a <m2mServiceSubscriptionProfile> resource created as a child of <CSEBase> resource • <serviceSubscribedNode> resource is created as a child of <m2mServiceSubscriptionProfile> • Node-ID attribute of <serviceSubscribedNode> 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 ADN-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 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 152 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description IOP Verdict PRO Verdict |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.7.2 Monitoring events | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on IN-CSE • ADN-AE has created an Application Entity resource <AE> on IN-CSE • ADN-AE has created a Node resource <node> on IN-CSE representing UE • ADN-AE has created a Schedule resource <schedule> on IN-CSE under <node> resource. The networkCoordinated attribute is set to TRUE. • IN-AE has subscribed to the <schedule> resource by creating a child <subscription> 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 <schedule> resource 6 (T8) Mcn PRO Check Primitive IN-CSE sends a Notify message to IN-CSE: • op = 6 (Notify) • pc = serialized representation of the updated <schedule> resource 7 IOP Check Check if possible that ADN-AE on UE has updated its local <schedule> resource (if applicable) IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 153 oneM2M TS-0013 version 3.3.1 Release 3 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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 <AE> on IN-CSE • ADN-AE has created an Application Entity resource <AE> on IN-CSE • ADN-AE has created a Node resource <node> on IN-CSE representing UE • ADN-AE has created a Schedule resource <schedule> on IN-CSE under <node> resource. The networkCoordinated attribute is set to TRUE. • IN-AE has subscribed to the <schedule> resource by creating a child <subscription> 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 <schedule> resource to indicate that UE is available and created new scheduleElement Check if possible that notification has been sent to the <schedule> 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 <schedule> resource to indicate that UE is idle Check if possible that notification has been sent to the <schedule> resource subscribed entities IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 154 oneM2M TS-0013 version 3.3.1 Release 3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.