hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2 Conformance test cases for SMO/Non-RT RIC framework | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.1.1 Device under test requirements | The SMO/Non-RT RIC framework that acts as DUT in the test scenarios of this clause can be a function that is under development, or it can be a finalized commercial product. The requirements on the DUT for these tests are that it can handle the Data registration service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4], clause 7.1.4. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.1.2 Test simulator capabilities | The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: • Recording of received HTTP requests and responses and analysing them regarding conformance to the R1 service definitions. • Controlled initiation of procedures with configurable URIs and payload formulated and modified. Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP [4], clause 7.1.4. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 36 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2 Data registration API as API Producer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.1 Register DME type (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.1.1 Test description and applicability | The purpose of this test case is to test the Register DME type in Data registration API as specified in R1AP [4], clause 7.1. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.1.2 Test entrance criteria | The test simulator has functionality to initiate the Register DME type procedure as defined in R1GAP [1]. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.1.3 Test methodology | 8.2.2.1.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 8.2.2.1.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to register a DmeTypeRelatedCapabilities. Step 2 The DUT receives the HTTP request. Step 3 The DUT does the following validation: a) The HTTP request is a POST request. b) The URI conforms to the format specified in R1AP [4], clause 7.1.5.2.2. c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.5.2.3.1. Step 4 The DUT generates the data job and constructs the URI for the created resource. Step 5 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.2.3.1. Step 6 At the test simulator the contents of the received HTTP response are recorded. Step 7 The test simulator does the following validation: a) The HTTP response message content includes the information as specified in R1AP [4], clause 7.1.5.2.3.1, and the Location header will be present. b) The URI conforms to the format specified in R1AP [4], clause 7.1.5.2.2. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.1.4 Expected result | The test is considered passed if Step 7 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.2 Deregister DME type (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.2.1 Test description and applicability | The purpose of this test case is to test the Deregister DME type in Data registration API as specified in R1AP [4]. The expected outcome is successful validation of the request from the DUT. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 37 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.2.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Deregister DME type procedure as defined in R1GAP [1], clause 5.2.2.2. 2) A DME type exists in test simulator and the registrationId is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.2.3 Test methodology | 8.2.2.2.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 8.2.2.2.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to Deregister DME type. Step 2 The DUT receives the HTTP request. Step 3 The DUT does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. b) The HTTP request is a DELETE operation. c) The registrationId in the URI match the DME type being deregistered. d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. Step 4 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.3.3. Step 5 At the test simulator the contents of the received HTTP response are recorded. Step 6 The test simulator does the following validation: a) The URI confirms to the format specified in R1AP [4], clause 7.1.5.3.2. b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.2.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.3 Query DME type (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.3.1 Test description and applicability | The purpose of this test case is to test the Query DME type in Data registration API as specified in R1AP [4], clause 7.1.4.4. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.3.2 Test entrance criteria | 1) The test simulator has functionality to initiate the query DME type registration procedure as defined in R1Gap [1], clause 5.2.2.2. 2) A DME type exists in test simulator and the registrationId is known to the DUT. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 38 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.3.3 Test methodology | 8.2.2.3.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 8.2.2.3.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to query a DME type. Step 2 The DUT receives the HTTP request. Step 3 The DUT does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. b) The HTTP request is a GET operation. c) The registrationId in the URI match the data job status being queried. d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. Step 4 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.3.3. Step 5 At the test simulator the contents of the received HTTP response are recorded. Step 6 The test simulator does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.3.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.4 Update DME type (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.4.1 Test description and applicability | The purpose of this test case is to test the Update DME type in Data registration API as specified in R1AP [4], clause 7.1.4.3. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.4.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Update DME type registration procedure as defined in R1GAP [1], clause 5.2.2.2 2) A DME type exists in test simulator and the registrationId and DmeTypeRelatedCapabilities are known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.4.3 Test methodology | 8.2.2.4.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 39 8.2.2.4.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to update a DME type identified by the registrationId and DmeTypeRelatedCapabilities. Step 2 The DUT receives the HTTP request. Step 3 The DUT does the following validation: a) The HTTP request is a PUT request. b) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. Step 4 The DUT generates the data job and constructs the URI for the created resource. Step 5 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.3.3. Step 6 At the test simulator the contents of the received HTTP response are recorded. Step 7 The test simulator does the following validation: a) The HTTP response message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. b) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.4.4 Expected result | The test is considered passed if Step 7 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9 DME Data request service test cases | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1 Conformance test cases for rApp | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.1.1 Device under test requirements | The rApp that acts as DUT in the test scenarios of this clause can be a function that is under development, or it can be a finalized commercial product. The requirements on the DUT for these tests are that it can handle the DME Data request service, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 7.3.4. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.1.2 Test simulator capabilities | The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: • Recording of received HTTP requests and responses and analysing them regarding conformance to the R1 service definitions. • Controlled initiation of procedures with configurable URIs and payload formulated and modified. Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4], clause 7.3.4. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 40 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2 Data access API as API Consumer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.1 Create data job (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.1.1 Test description and applicability | The purpose of this test case is to test the create data job API as specified in R1AP [4], clause 7.3.4.1. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.1.2 Test entrance criteria | 1) The DUT has functionality to initiate the request data procedure as defined in R1GAP [1], clause 5.2.4. 2) The DataJobInfo is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.1.3 Test methodology | 9.1.2.1.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 9.1.2.1.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to create a data job. Step 2 At the test simulator the contents of the received HTTP request are recorded. Step 3 The test simulator does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.1. b) The HTTP request is a POST operation. c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.1. Step 4 The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.1.1. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.1.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.2 Cancel data job (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.2.1 Test description and applicability | The purpose of this test case is to test the Cancel data job API as specified in R1AP [4], clause 7.3.4.2. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.2.2 Test entrance criteria | 1) The DUT has functionality to initiate the cancel data request procedure as defined in R1GAP [1], clause 5.2.4. 2) A data job exists in test simulator and the dataJobId is known to the DUT. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 41 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.2.3 Test methodology | 9.1.2.2.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 9.1.2.2.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to cancel a data job. Step 2 At the test simulator the contents of the received HTTP request are recorded. Step 3 The test simulator does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3. b) The HTTP request is a DELETE operation. c) The dataJobID in the URI match the data job being deleted. d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.2. Step 4 The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.2.1. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.2.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.3 Query data job status (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.3.1 Test description and applicability | The purpose of this test case is to test the query data job status API as specified in R1AP [4], clause 7.3.4.6. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.3.2 Test entrance criteria | 1) The DUT has functionality to initiate the query data request status procedure as defined in R1GAP [1], clause 5.2.4. 2) A data job exists in test simulator and the dataJobId is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.3.3 Test methodology | 9.1.2.3.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 9.1.2.3.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to query a data job status. Step 2 At the test simulator the contents of the received HTTP request are recorded. Step 3 The test simulator does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.6.1. b) The HTTP request is a GET operation. c) The dataJobID in the URI match the data job being queried. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 42 d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.6.1. Step 4 The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.6.1. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.1.2.3.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2 Conformance test cases for SMO/Non-RT RIC framework | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.1.1 Device under test requirements | The SMO/Non-RT RIC framework that acts as DUT in the test scenarios of this clause can be a function that is under development, or it can be a finalized commercial product. The requirements on the DUT for these tests are that it can handle the DME Data request service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4], clause 7.3.4. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.1.2 Test simulator capabilities | The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: • Recording of received HTTP requests and responses and analysing them regarding conformance to the R1 service definitions. • Controlled initiation of procedures with configurable URIs and payload formulated and modified. Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP [4], clause 7.3.4. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2 Data access API as API Producer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.1 Create data job (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.1.1 Test description and applicability | The purpose of this test case is to test the create data job API as specified in R1AP [4], clause 7.3.4.1. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.1.2 Test entrance criteria | 1) The test simulator has functionality to initiate the request data procedure as defined in R1GAP [1], clause 5.2.4. 2) The DataJobInfo is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.1.3 Test methodology | 9.2.2.1.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 9.2.2.1.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to create a data job. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 43 Step 2 The DUT receives the HTTP request. Step 3 The DUT does the following validation: a) The HTTP request is a POST request. b) The URI conforms to the format specified in R1AP [4], clause 7.3.5.2.3.1. c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.1. Step 4 The DUT generates the data job and constructs the URI for the created resource. Step 5 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.1. Step 6 At the test simulator the contents of the received HTTP response are recorded. Step 7 The test simulator does the following validation: a) The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.1, and the Location header will be present. b) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.1.4 Expected result | The test is considered passed if Step 7 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.2 Cancel data job (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.2.1 Test description and applicability | The purpose of this test case is to test the Cancel data job API as specified in R1AP [4], clause 7.3.4.2. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.2.2 Test entrance criteria | 1) The test simulator has functionality to initiate the cancel data request procedure as defined in R1GAP [1], clause 5.2.4. 2) A data job exists in DUT and the dataJobId is known to the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.2.3 Test methodology | 9.2.2.2.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 9.2.2.2.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to cancel a data job. Step 2 The DUT receives the HTTP request. Step 3 The DUT does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3.3.1. b) The HTTP request is a DELETE operation. c) The dataJobID in the URI match the data job being deleted. d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.2. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 44 Step 4 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.2. Step 5 At the test simulator the contents of the received HTTP response are recorded. Step 6 The test simulator does the following validation: a) The URI confirms to the format specified in R1AP [4] , clause 7.3.5.3. b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.2. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.2.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.3 Query data job status (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.3.1 Test description and applicability | The purpose of this test case is to test the query data job status API as specified in R1AP [4], clause 7.3.4.6. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.3.2 Test entrance criteria | 1) The test simulator has functionality to initiate the query data request status procedure as defined in R1GAP [1], clause 5.2.4. 2) A data job exists in the DUT and the dataJobId is known to the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.3.3 Test methodology | 9.2.2.3.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 9.2.2.3.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to query a data job status. Step 2 The DUT receives the HTTP request. Step 3 The DUT does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.4. b) The HTTP request is a GET operation. c) The dataJobID in the URI match the data job status being queried. d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.6.1. Step 4 The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.6.1. Step 5 At the test simulator the contents of the received HTTP response are recorded. Step 6 The test simulator does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.4. b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.6.1. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 45 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 9.2.2.3.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10 DME Data subscription service test cases | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1 Conformance test cases for rApp | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.1.1 Device under test requirements | The rApp that acts as DUT in the test scenarios of this clause can be a function that is under development, or it can be a finalized commercial product. The requirements on the DUT for these tests are that it can handle the DME Data subscription service, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 7.3.4. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.1.2 Test simulator capabilities | The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: • Recording of received HTTP requests and responses and analysing them regarding conformance to the R1 service definitions. • Controlled initiation of procedures with configurable URIs and payload formulated and modified. Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4], clause 7.3.4. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2 Data access API as API Consumer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.1 Create data job (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.1.1 Test description and applicability | The purpose of this test case is to test the create data job API as specified in R1AP [4], clause 7.3.4.1. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.1.2 Test entrance criteria | 1) The DUT has functionality to initiate the subscribe data procedure as defined in R1GAP [1], clause 5.2.5. 2) The DataJobInfo is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.1.3 Test methodology | 10.1.2.1.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 10.1.2.1.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to create a data job. Step 2 At the test simulator the contents of the received HTTP request are recorded. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 46 Step 3 The test simulator does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.1. b) The HTTP request is a POST operation. c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.1. Step 4 The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.1.1. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.1.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.2 Cancel data job (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.2.1 Test description and applicability | The purpose of this test case is to test the Cancel data job API as specified in R1AP [4], clause 7.3.4.2. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.2.2 Test entrance criteria | 1) The DUT has functionality to initiate the unsubscribe data procedure as defined in R1GAP [1], clause 5.2.5. 2) A data job exists in test simulator and the dataJobId is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.2.3 Test methodology | 10.1.2.2.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 10.1.2.2.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to cancel a data job. Step 2 At the test simulator the contents of the received HTTP request are recorded. Step 3 The test simulator does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3. b) The HTTP request is a DELETE operation. c) The dataJobID in the URI match the data job being deleted. d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.2. Step 4 The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.2.1. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.2.4 Expected result | The test is considered passed if Step 3 validation has passed. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 47 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.3 Query data job (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.3.1 Test description and applicability | The purpose of this test case is to test the query data job API as specified in R1AP [4], clause 7.3.4.5. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.3.2 Test entrance criteria | 1) The DUT has functionality to initiate the query data subscription procedure as defined in R1GAP [1], clause 5.2.5. 2) A data job exists in test simulator and the dataJobId is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.3.3 Test methodology | 10.1.2.3.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 10.1.2.3.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to query a data job. Step 2 At the test simulator the contents of the received HTTP request are recorded. Step 3 The test simulator does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.5.1. b) The HTTP request is a GET operation. c) The dataJobID in the URI match the data job being queried. d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.5.1. Step 4 The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.6.1. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.3.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.4 Query data job status (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.4.1 Test description and applicability | The purpose of this test case is to test the query data job status API as specified in R1AP [4], clause 7.3.4.6. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.4.2 Test entrance criteria | 1) The DUT has functionality to initiate the query data subscription status procedure as defined in R1GAP [1], clause 5.2.5. 2) A data job exists in test simulator and the dataJobId is known to the DUT. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 48 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.4.3 Test methodology | 10.1.2.4.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 10.1.2.4.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to query a data job status. Step 2 At the test simulator the contents of the received HTTP request are recorded. Step 3 The test simulator does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.6.1. b) The HTTP request is a GET operation. c) The dataJobID in the URI match the data job being queried. d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.6.1. Step 4 The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.6.1. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.4.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.5 Query data job identifiers (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.5.1 Test description and applicability | The purpose of this test case is to test the query data job identifiers API as specified in R1AP [4], clause 7.3.4.7. The expected outcome is successful validation of the request from the DUT. 10.1.2.5.2 Test entrance criteria 1) The DUT has functionality to initiate the query data subscription status procedure as defined in R1GAP [1], clause 5.2.5. 2) A set of data jobs exists in test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.5.3 Test methodology | 10.1.2.5.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 10.1.2.5.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to query data job identifiers. Step 2 At the test simulator the contents of the received HTTP request are recorded. Step 3 The test simulator does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.7.1. b) The HTTP request is a GET operation. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 49 c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.7.1. Step 4 The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.7.1. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.5.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.6 Update data job (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.6.1 Test description and applicability | The purpose of this test case is to test the Update data job API as specified in R1AP [4], clause 7.3.4.5. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.6.2 Test entrance criteria | 1) The DUT has functionality to initiate the Update data job procedure as defined in R1GAP [1], clause 5.2.5. 2) A data job exists in test simulator and the dataJobId and DataJobInfo are known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 10.1.2.6.3 Test methodology | 10.1.2.6.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 10.1.2.6.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to update a data job identified by the dataJobId and DataJobInfo. Step 2 At the test simulator the contents of the received HTTP request are recorded. Step 3 The test simulator does the following validation: a) The URI confirms to the format specified in R1AP [4], clause 7.3.4.4. b) The HTTP request is a PUT operation. c) The dataJobId and DataJobInfo in the URI match the data job being updated. d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.4.1. Step 4 The test simulator updates the resource, and a representation of the updated resource shall be returned in the response body the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.4.1. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.