hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.3.3 Test methodology | 6.3.3.3.3.1 Initial conditions 1) The test simulator has A1-EI Producer service ready and available to receive HTTP request from the DUT. 6.3.3.3.3.2 Procedure Step 1. Initiate appropriate action in the DUT to initiate Query EI job request for the existing EI job identified by the eiJobId. Step 2. At the test simulator... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.4 Update EI job test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.4.1 Update EI job (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.4.1.1 Test description and applicability | The purpose of this test case is to test update EI job functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.4. The expected outcome is successful validation of the Update EI job request. This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Update EI job procedure... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.4.1.2 Test entrance criteria | 1) The DUT has functionality to initiate A1-EI Update Job procedure. 2) An EI job exists in test simulator and DUT is aware of the eiTypeId and eiJobId. 3) The eiTypeId and the JSON schemas of the EI job type used for this test are available in DUT to formulate the Update EI job request and used by the test simulator f... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.4.1.3 Test methodology | 6.3.4.1.3.1 Initial conditions 1) The test simulator has A1-EI Producer service ready and available to receive HTTP request from the DUT. 6.3.4.1.3.2 Procedure Step 1. Initiate appropriate action in the DUT to initiate Update EI job request for the existing EI job identified by the eiJobId. Step 2. At the test simulato... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.5 Delete EI job test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.5.1 Delete EI job (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.5.1.1 Test description and applicability | The purpose of this test case is to test the delete EI job functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.6. The expected outcome is successful validation of the Delete EI job request. This test case is conditionally mandatory if the DUT claims to support A1-EI service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.5.1.2 Test entrance criteria | 1) The DUT has functionality to initiate A1-EI Delete EI job procedure. 2) An EI job exists in test simulator and the eiJobId is known to DUT. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 62 |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.5.1.3 Test methodology | 6.3.5.1.3.1 Initial conditions 1) The test simulator has A1-EI Producer service ready and available to receive HTTP request from the DUT. 6.3.5.1.3.2 Procedure Step 1. Initiate appropriate action in the DUT to initiate Delete EI job request for the existing EI job identified by the eiJobId. Step 2. At the test simulato... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6 Status of EI jobs test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.1 Query EI job status (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.1.1 Test description and applicability | The purpose of this test case is to test the query EI job status functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.7. The expected outcome is successful validation of the Query EI job status request. This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query E... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.1.2 Test entrance criteria | 1) The DUT has functionality to initiate A1-EI Query EI job status procedure. 2) An EI job exists in test simulator and DUT is aware of the eiJobId. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.1.3 Test methodology | 6.3.6.1.3.1 Initial conditions 1) The test simulator has A1-EI Producer service ready and available to receive HTTP request from the DUT. 6.3.6.1.3.2 Procedure Step 1. Initiate appropriate action in the DUT to initiate Query EI job status request for the existing EI job identified by the eiJobId. Step 2. At the test si... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.2 Notify EI job status (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.2.1 Test description and applicability | This purpose of this test case is to test the notify EI job status functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.8. The expected outcome is successful EI job status notification request and reception. This test case is conditionally mandatory if the DUT claims to support A1-EI service and suppor... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.2.2 Test entrance criteria | The test entrance criteria for Create EI job specified in clause 6.3.2.1.2 applies. And in addition: 1) The DUT has the functionality to request and receive EI job status notifications. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.2.3 Test methodology | 6.3.6.2.3.1 Initial conditions The initial conditions for Create EI job specified in clause 6.3.2.1.3.1 applies. And in addition: 1) The test simulator supports generation of an EiJobStatusObject based on the EI job status schema of the agreed EI type used for this test. 2) The DUT has HTTP server ready and available t... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.3 Notify EI job status - schema validation failure (negative case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.3.1 Test description and applicability | This purpose of this test case is to test the notify EI job status functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.8. The expected outcome is failure due to schema validation failure. This test case is conditionally mandatory if the DUT claims to support A1-EI service and supports the Notify EI jo... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.3.2 Test entrance criteria | The test entrance criteria in clause 6.3.6.2.2 applies. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.3.3 Test methodology | 6.3.6.3.3.1 Initial conditions The initial conditions in clause 6.3.6.2.3.1 applies. 6.3.6.3.3.2 Procedure Steps 1-6 of clause 6.3.6.2.3.2 applies with the following modification: • In Step 5: A spelling mistake should be introduced in the EiJobStatusObject for schema validation error in DUT. 6.3.6.3.3.3 Expected resul... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.4 Notify EI job status - callback URI not supported (negative case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.4.1 Test description and applicability | This purpose of this test case is to test the notify EI job status functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.8. The expected outcome is failure due to invalid callback URI. This test case is conditionally mandatory if the DUT claims to support A1-EI service and supports the Notify EI job sta... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.4.2 Test entrance criteria | The test entrance criteria in clause 6.3.6.2.2 applies. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.6.4.3 Test methodology | 6.3.6.4.3.1 Initial conditions The initial conditions in clause 6.3.6.2.3.1 applies. 6.3.6.4.3.2 Procedure Steps 1-6 of clause 6.3.6.2.3.2 applies with the following modification: • In Step 5. A spelling mistake should be introduced in the used callback URI making it different from the provided jobStatusNotificationUri... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7 Deliver EI job result test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.1 Deliver EI job result (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.1.1 Test description and applicability | This purpose of this test case is to test the deliver EI job result functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.5.2. The expected outcome is successful EI job result request and reception. This test case is conditionally mandatory if the DUT claims to support A1-EI service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.1.2 Test entrance criteria | The test entrance criteria for Create EI job specified in clause 6.3.2.1.2 applies. NOTE: No specific functionality is needed in DUT to request EI job results as it is covered by Create EI job procedure. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.1.3 Test methodology | 6.3.7.1.3.1 Initial conditions The initial conditions for Create EI job specified in clause 6.3.2.1.3.1 applies. And in addition: 1) The test simulator supports generation of an EiJobResultObject based on the EI job result schema of the agreed EI type used for this test. 2) The DUT has HTTP server ready and available t... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.2 Deliver EI job result - schema validation failure (negative case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.2.1 Test description and applicability | This purpose of this test case is to test the deliver EI job result functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.5.2. The expected outcome is failure due to schema validation failure. This test case is conditionally mandatory if the DUT claims to support A1-EI service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.2.2 Test entrance criteria | The test entrance criteria in clause 6.3.7.1.2 applies. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.2.3 Test methodology | 6.3.7.2.3.1 Initial conditions The initial conditions in clause 6.3.7.1.3.1 applies. 6.3.7.2.3.2 Procedure Steps 1-6 of clause 6.3.7.1.3.2 applies with the following modification: • In Step 5: A spelling mistake should be introduced in the EiJobResultObject for schema validation error in DUT. ETSI ETSI TS 103 989 V4.2.... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.3 Deliver EI job result - callback URI not supported (negative case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.3.1 Test description and applicability | This purpose of this test case is to test the deliver EI job result functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.5.2. The expected outcome is failure due to invalid callback URI. This test case is conditionally mandatory if the DUT claims to support A1-EI service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.3.2 Test entrance criteria | The test entrance criteria in clause 6.3.7.1.2 applies. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.7.3.3 Test methodology | 6.3.7.3.3.1 Initial conditions The initial conditions in clause 6.3.7.1.3.1 applies. 6.3.7.3.3.2 Procedure Steps 1-6 of clause 6.3.7.1.3.2 applies with the following modification: • In Step 5. A spelling mistake should be introduced in the used callback URI making it different from the provided jobResultUri and not ide... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.1 General | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.1.1 System under test requirements | The system under test is a Non-RT RIC and a Near-RT RIC that acts as DUTs referred to Non-RTR-DUT and Near-RTR-DUT in the test scenarios of this clause. The requirements on the DUTs for these tests are that they can handle the procedures defined for a Non-RT RIC and Near-RT RIC and the purpose of the test scenarios is ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.1.2 Test tools and simulators capabilities | A TAP interface and protocol analyser is required for recording and validating A1 procedure message sequences and contents and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUTs level of interoperability. SMO framework with O1 functionality may be required to ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2 Interoperability test cases for A1-P | 7.2.1 Query policy type test scenarios |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.1.1 Query all policy type identifiers (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.1.1.1 Test description and applicability | The purpose of this test case is to test the query policy types functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.3.2. The expected outcome is successful Query all policy type identifiers operation. This test case is conditionally mandatory if the DUTs claim to support A1-P service an... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.1.1.2 Test entrance criteria | 1) The Non-RTR-DUT has functionality to initiate A1-P Query all policy type identifiers procedure: 2) A set of policy types (at least two) are supported in the Near-RTR-DUT. 3) The supported policyTypeIds are known to the "protocol analyser". |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.1.1.3 Test methodology | 7.2.1.1.3.1 Initial conditions 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non- RTR-DUT. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 69 2) The Near-RTR-DUT supports the three different test configurations listed below to test complete functionality: a) Near-RTR-DUT has ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.1.2 Query single policy type (positive) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.1.2.1 Test description and applicability | The purpose of this test case is to test the query policy types functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.3.3. The expected outcome is successful Query single policy type operation. This test case is conditionally mandatory if the DUTs claim to support A1-P service and the Que... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.1.2.2 Test entrance criteria | 1) The Non-RTR-DUT has functionality to initiate A1-P Query single policy procedure. 2) A known set of policy types are supported in the Near-RTR-DUT. 3) The supported policyTypeIds are known to the protocol analyser. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 70 |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.1.2.3 Test methodology | 7.2.1.2.3.1 Initial conditions 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. 7.2.1.2.3.2 Procedure Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. Step 1. Initiate appropriate action in th... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.2.1 Create single policy (positive) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.2.1.1 Test description and applicability | This purpose of this test case is to test the create policy functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.3. The expected outcome is successful creation of the policy. This test case is conditionally mandatory if the DUTs claim to support A1-P service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.2.1.2 Test entrance criteria | 1) The Non-RTR-DUT has functionality to initiate A1-P Create single policy procedure. 2) The DUTs have agreed on a policy type to use for this test. 3) The policyTypeId and the JSON schemas of the policy type used for this test are available and used in Non-RTR-DUT to formulate the Create single policy request, and in ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.2.1.3 Test methodology | 7.2.2.1.3.1 Initial conditions 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. 2) No policy exists in the Near-RTR-DUT for the policy type with the same policyId that will be used by the Non-RTR-DUT. 7.2.2.1.3.2 Procedure Step 0. Enable protocol analyser ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.1 Query all policy identifiers | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.1.1 Test description and applicability | The purpose of this test case is to test the query all policies functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.2. The expected outcome is successful retrieval of policy identifiers. This test case is conditionally mandatory if the DUTs claim to support A1-P service and the Query ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.1.2 Test entrance criteria | 1) The Non-RTR-DUT has functionality to initiate A1-P Query all policy identifiers procedure. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 72 2) The DUTs have agreed on a policy type to use for this test. 3) A set of policies (at least two) for the agreed policy type exist in the Near-RTR-DUT. 4) The agreed policyTypeId is kn... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.1.3 Test methodology | 7.2.3.1.3.1 Initial conditions 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. 2) The Near-RTR-DUT is supports three different test configurations listed below to test complete functionality: a) Near-RTR-DUT has no policies available for the agreed policy... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.2 Query single policy | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.2.1 Test description and applicability | The purpose of this test case is to test the query single policy functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.5. The expected outcome is successful retrieval of policy object. This test case is conditionally mandatory if the DUTs claim to support A1-P service and the Query sing... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.2.2 Test entrance criteria | 1) The Non-RTR-DUT has functionality to initiate A1-P Query single policy procedure. 2) A policy exists in the Near-RTR-DUT and the policyTypeId and policyId are known to Non-RTR-DUT. 3) The policyTypeId and policyId are known to the protocol analyser. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.2.3 Test methodology | 7.2.3.2.3.1 Initial conditions 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. 7.2.3.2.3.2 Procedure Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. Step 1. Initiate appropriate action in th... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.3 Query policy status (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.3.1 Test description and applicability | The purpose of this test case is to test the query policy status functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.7. The expected outcome is successful retrieval of policy status object. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 74 This test case is conditionally mandatory if the DUTs ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.3.2 Test entrance criteria | 1) The Non-RTR-DUT has functionality to initiate A1-P Query policy status procedure. 2) A policy exists in the Near-RTR-DUT and the policyTypeId and policyId are known to the Non-RTR-DUT. 3) The policyTypeId and policyId are known to the protocol analyser. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.3.3.3 Test methodology | 7.2.3.3.3.1 Initial conditions 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. 7.2.3.3.3.2 Procedure Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. Step 1. Initiate appropriate action in th... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.4.1 Update single policy (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.4.1.1 Test description and applicability | The purpose of this test case is to test the update policy functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.4. The expected outcome is successful update of the policy. This test case is conditionally mandatory if the DUTs claim to support A1-P service and the Update single policy p... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.4.1.2 Test entrance criteria | 1) The Non-RTR-DUT has functionality to initiate A1-P Update single policy procedure. 2) A policy exists in the Near-RTR-DUT and the policyTypeId and policyId are known to the Non-RTR-DUT. 3) The policyTypeId and the JSON schemas of the policy type used for this test are available and used in Non-RTR-DUT to formulate t... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.4.1.3 Test methodology | 7.2.4.1.3.1 Initial conditions 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. 7.2.4.1.3.2 Procedure Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. Step 1. Initiate appropriate action in th... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.5.1 Delete single policy (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.5.1.1 Test description and applicability | The purpose of this test case is to test the delete policy functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.6. The expected outcome is successful deletion of the policy. This test case is conditionally mandatory if the DUTs claim to support A1-P service. ETSI ETSI TS 103 989 V4.2.0... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.5.1.2 Test entrance criteria | 1) The Non-RTR-DUT has functionality to initiate A1-P Delete single policy procedure. 2) A policy exists in the Near-RTR-DUT and the policyTypeId and policyId are known to the Non-RTR-DUT. 3) The policyTypeId and the policyId are known to the protocol analyser. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.5.1.3 Test methodology | 7.2.5.1.3.1 Initial conditions 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. 7.2.5.1.3.2 Procedure Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. Step 1. Initiate appropriate action in th... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.6.1 Notify policy status (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.6.1.1 Test description and applicability | The purpose of this test case is to test the policy status notification functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.8. The expected outcome is successful policy status request and reception. This test case is optional if the DUTs claim to support A1-P service and supports the ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.6.1.2 Test entrance criteria | The test entrance criteria for Create single policy specified in clause 7.2.2.1.2 applies. And in addition: 1) Non-RTR-DUT has the functionality to request and receive policy status notifications. 2) Near-RTR-DUT has the functionality to provide policy status notifications. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 77 3) N... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.2.6.1.3 Test methodology | 7.2.6.1.3.1 Initial conditions The initial conditions for Create single policy specified in clause 7.2.2.1.3.1 applies. And in addition: 1) The Near-RTR-DUT supports generation of a PolicyStatusObject based on the policy status schema of the agreed policy type used for this test. 2) The Non-RTR-DUT has HTTP server read... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3 Interoperability test cases for A1-EI | 7.3.1 Query EI types test scenarios |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.1.1 Query EI type identifiers (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.1.1.1 Test description and applicability | The purpose of this test case is to test query EI type identifiers functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.3.2. The expected outcome is successful retrieval of EI type identifiers. This test case is conditionally mandatory if the DUTs claim to support A1-EI service and Que... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.1.1.2 Test entrance criteria | 1) The Near-RTR-DUT has functionality to initiate A1-EI Query EI type identifiers procedure. 2) The Non-RTR-DUT supports a known set of EI types (two or more) used for this test. 3) The supported eiTypeIds are known to the protocol analyser |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.1.1.3 Test methodology | 7.3.1.1.3.1 Initial conditions 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. 2) The Non-RTR-DUT supports the three different test configurations listed below to test complete functionality: a) Non-RTR-DUT has no EI type available. b) Non-RTR-DUT has a ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.1.2 Query EI type (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.1.2.1 Test description and applicability | The purpose of this test case is to test query EI type functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.3.3. The expected outcome is successful retrieval of EI type object. This test case is conditionally mandatory if the DUTs claim to support A1-EI service and the Query EI type pr... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.1.2.2 Test entrance criteria | 1) The Near-RTR-DUT has the functionality to initiate A1-EI Query EI type procedure. 2) A known set of EI types are supported in the Non-RTR-DUT. 3) The supported eiTypeIds are known to the protocol analyser. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.1.2.3 Test methodology | 7.3.1.2.3.1 Initial conditions 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. 7.3.1.2.3.2 Procedure Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. Step 1. Initiate appropriate action in t... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.2.1 Create EI job (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.2.1.1 Test description and applicability | This purpose of this test case is to test the create EI job functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.3. The expected outcome is successful creation of the EI job. This test case is conditionally mandatory if the DUTs claim to support A1-EI service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.2.1.2 Test entrance criteria | 1) The Near-RTR-DUT has functionality to initiate A1-EI Create EI job procedure. 2) The DUTs have agreed on an EI type to use for this test. 3) The eiTypeId and the JSON schemas of the EI type used for this test are available and used in Near-RTR-DUT to formulate the Create EI job request, and in Non-RTR-DUT to validat... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.2.1.3 Test methodology | 7.3.2.1.3.1 Initial conditions 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. 2) No EI job exists in the Non-RTR-DUT for the EI job type with the same eiJobId that will be used by the Near-RTR-DUT. 7.3.2.1.3.2 Procedure Step 0. Enable protocol analyser ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.1 Query EI job identifiers for a single EI type (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.1.1 Test description and applicability | This purpose of this test case is to test query EI job identifiers functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.2. The expected outcome is successful retrieval of all EI job identifiers of a given EI type. This test case is conditionally mandatory if the DUTs claim to support... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.1.2 Test entrance criteria | 1) The Near-RTR-DUT has functionality to initiate A1-EI Query EI job identifiers procedure. 2) The DUTs have agreed on an EI type to use for this test. 3) A set of EI jobs (at least two) for the agreed EI type exist in the Non-RT-DUT. 4) The agreed eiTypeId is known to the protocol analyser. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.1.3 Test methodology | 7.3.3.1.3.1 Initial conditions 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. 2) The Non-RTR-DUT supports three different test configurations listed below to test complete functionality: a) Non-RTR-DUT has no EI jobs available for the agreed EI type. b)... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.2 Query EI job identifiers for all EI types (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.2.1 Test description and applicability | This purpose of this test case is to test query EI job identifiers functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.2. The expected outcome is successful retrieval of all EI job identifiers of all EI types. This test case is conditionally mandatory if the DUTs claim to support A1... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.