hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
5321880801ac34d054cb1c648f063969 | 104 246 | 2 References | |
5321880801ac34d054cb1c648f063969 | 104 246 | 2.1 Normative references | Normative references are not applicable in the present document. |
5321880801ac34d054cb1c648f063969 | 104 246 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
5321880801ac34d054cb1c648f063969 | 104 246 | 3 Definition of terms, symbols and abbreviations | |
5321880801ac34d054cb1c648f063969 | 104 246 | 3.1 Terms | For the purposes of the present document, the following terms apply: ETSI CVD Steering Committee: committee which, for each vulnerability report, triages the vulnerability, interacts with the Chair and the ETSI Technical Officer of the TC TCCE and the rapporteur(s) of the impacted standard(s) to resolve the vulnerabili... |
5321880801ac34d054cb1c648f063969 | 104 246 | 3.2 Symbols | Void. |
5321880801ac34d054cb1c648f063969 | 104 246 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BS Base Station CRA Cyber Resilience Act CVD Coordinated Vulnerability Disclosure DMO Direct Mode Operation EU European Union IOP InterOPerability ISG Industry Specification Group ISI Inter-System Interfaces ITSI Individual TETRA Subscriber Id... |
5321880801ac34d054cb1c648f063969 | 104 246 | 4 Overview of TETRA networks | |
5321880801ac34d054cb1c648f063969 | 104 246 | 4.1 Standardization of TETRA networks | ETSI's Technical Committee (TC) Terrestrial Trunked Radio and Critical Communications Evolution (TCCE) is responsible for the design and standardization of Terrestrial Trunked Radio (TETRA) and its evolution to critical communications mobile broadband solutions. TETRA standards define the TETRA air interface, TETRA alg... |
5321880801ac34d054cb1c648f063969 | 104 246 | 4.2 Typical TETRA network environments | TETRA is used in Private and Public Access Mobile Radio (PMR and PAMR) networks. Major markets include: • Public Safety • Transportation • Utilities • Government • Military • Commercial and Industry • Oil and Gas |
5321880801ac34d054cb1c648f063969 | 104 246 | 4.3 TETRA network architectures | In TETRA standards TETRA networks comprise Mobile Stations (MSs) and components of the Switching and Management Infrastructure (SwMI). A MS comprises all of the mobile equipment that is used to obtain TETRA services. In TETRA networks a MS may be directly provisioned with the Individual TETRA Subscriber Identity (ITSI)... |
5321880801ac34d054cb1c648f063969 | 104 246 | 4.4 TETRA network operations | Most user organizations in TETRA networks require high availability. For example police, fire brigades, emergency medical services or critical operations personnel in industrial plants form typical user organizations. Due to their mission critical duties these users demand high availability and fast remediation of comm... |
5321880801ac34d054cb1c648f063969 | 104 246 | 5 Mitigation of vulnerabilities in TETRA networks | |
5321880801ac34d054cb1c648f063969 | 104 246 | 5.1 Options to mitigate vulnerabilities in TETRA networks | As outlined in clause 4.1 implementations of the TETRA air interface, TETRA algorithms, the TETRA speech codec and external interfaces of TETRA networks follow ETSI standards. Therefore vulnerabilities in those standards may have direct impact on a high number of components in TETRA networks worldwide. Usually these vu... |
5321880801ac34d054cb1c648f063969 | 104 246 | 5.2 Update processes in TETRA networks | Update processes in TETRA networks typically contain multiple steps of different stakeholders. To update components all stakeholders have to work together. To illustrate this complexity the following list shows an example of the necessary steps in the mitigation of a vulnerability found in TETRA standards. In this exam... |
5321880801ac34d054cb1c648f063969 | 104 246 | 5.3 Vulnerability mitigation at Mobile Station | Vulnerability mitigations at the MS may comprise configuration changes and/or updates of firmware or the exchange of MS hardware. Due to bandwidth constraints MS firmware updates are not provided over the TETRA air interface. For configuration or firmware updates the MS has to be brought to a particular location where ... |
5321880801ac34d054cb1c648f063969 | 104 246 | 5.4 Vulnerability mitigation in SwMI | Vulnerability mitigations in SwMI may comprise configurations changes and/or updates of software or hardware of SwMI components. Updates of SwMI components usually temporarily decrease network availability down to service outages. Therefore updates may be scheduled to low traffic periods in order to reduce downtime or ... |
5321880801ac34d054cb1c648f063969 | 104 246 | 6 ETSI CVD in TCCE TETRA context | |
5321880801ac34d054cb1c648f063969 | 104 246 | 6.1 Roles and responsibilities | ETSI CVD contains a definition of roles and responsibilities [i.1]. The following list specifies this definition further for the context of TC TCCE in the TETRA environment: • Finder: individual or organization who has found a potential vulnerability in the TETRA standards. • ETSI CVD Steering Committee: committee whic... |
5321880801ac34d054cb1c648f063969 | 104 246 | 6.2 Reporting obligations of network operators | As outlined in clause 4, TETRA networks are in operation in critical infrastructures or public safety. Network operators in these markets have to follow particular national regulations and laws in cybersecurity. The details are subject to national legislation, but typically network operators in critical infrastructure ... |
5321880801ac34d054cb1c648f063969 | 104 246 | 6.3 Reporting obligations of manufacturers | Cybersecurity regulations may require manufacturers to report vulnerabilities in their products. These reporting obligations are independent from ETSI CVD and may require the manufacturer to follow additional processes outside the scope of the present document. ETSI ETSI TR 104 246 V1.1.1 (2026-01) 11 For example, in t... |
5321880801ac34d054cb1c648f063969 | 104 246 | 6.4 ETSI CVD process in the TCCE environment | Table 1 shows the ETSI CVD process in the TCCE environment. To illustrate the process in more detail the four steps of the ETSI CVD [i.1] have been divided into sub-steps. Table 1: ETSI CVD process in TCCE environment Step No Leading role Involved role(s) Action listed to ETSI CVD [i.1] Follow-up step(s) 0 Finder ETSI ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 1 Scope | The present document specifies test cases for conformance testing and interoperability testing of the rApps and R1 services over R1 interface. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 2 References | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 3 Definition of terms, symbols and abbreviations | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 3.1 Terms | For the purposes of the present document, the terms given in R1GAP [1], R1UCR [2] and R1TP [3] apply. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 13 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 3.2 Symbols | Void. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in R1GAP [1], R1UCR [2] and R1TP [3] apply. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4 Test methodology | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.1 General | This clause describes the methodology for conformance and interoperability testing of rApps and SMO/Non-Real Time RIC framework over R1 interface. For conformance tests, simulators are used for testing R1 procedures. These simulators will have capability of generating HTTP requests and responses. There will be flexibil... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.2 Conformance testing of rApps | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.2.1 General | For conformance testing of rApps, rApp is the device under test and SMO/Non-RT RIC framework is the test simulator. The present document specifies conformance tests for API Consumer and API Producer functionality as specified in R1AP [4]. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.2.2 Test configuration | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.2.2.1 Overview | The test configuration for R1 conformance testing of rApp is illustrated in figure 4.2.2.1-1. For testing of rApp over R1 interface, the rApp is onboarded and instantiated in the cloud environment of the test simulator. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 14 rApp E2 node functionality 4G/5G Core functionality UEs SMO... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.2.2.2 Device under test rApps | For enabling conformance testing, rApp has implemented API Consumer and/or API Producer functionality and the procedures as specified in R1AP [4] that are required to perform testing of the applicable R1 service test cases. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.2.2.3 Test simulator | For enabling conformance testing, the test simulator has implemented API Producer and/or API Consumer functionality, have HTTP Client and HTTP Server capabilities, and have flexibility to generate, receive, and validate HTTP messages for all the R1 procedures. The test simulator logs all message content during the test... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.3 Conformance testing of SMO/Non-RT RIC framework | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.3.1 General | For conformance testing of SMO/Non-RT RIC framework, SMO/Non-RT RIC framework is the device under test and rApp is the test simulator. The present document specifies conformance tests for API Consumer and API Producer functionality as specified in R1AP [4]. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.3.2 Test configuration | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.3.2.1 Overview | The test configuration for R1 conformance testing of SMO/Non-RT RIC framework is illustrated in figure 4.3.2.1-1. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 15 rApp(s) E2 node functionality 4G/5G Core functionality UEs Near-RT RIC functionality R1 Test simulator DUT O1 O-cloud functionality O2 A1 SMO/Non-RT RIC framework E2... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.3.2.2 Device under test (SMO/Non-RT RIC Framework) | For enabling conformance testing, the SMO/Non-RT RIC framework has implemented API Producer and/or API Consumer functionality, and the procedures specified in R1AP [4] that are required to perform testing of the applicable test cases. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 4.3.2.3 Test simulator | For enabling conformance testing, the test simulator rApp(s) has both API Producer and/or API Consumer and HTTP Server capabilities and have flexibility to generate, receive and validate HTTP messages for all the R1 procedures. As illustrated in figure 4.3.2.1-1, test simulator has all the capabilities required to exec... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5 SME Service Registration service test cases | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1 Conformance test cases for rApp | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.1.1 Device under test requirements | The rApp that acts as Device Under Test (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 SME service registration service, and the purpose of the test scenarios is t... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.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... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2 Register service API as API Consumer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.1 Register service (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.1.1 Test description and applicability | The purpose of this test case is to test the Register service API as specified in R1AP [4], clause 6.1.4.1. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.1.2 Test entrance criteria | The DUT has functionality to initiate the Register service procedure as defined in R1GAP [1]. NOTE: The DUT provides the service API description as defined in R1AP [4]. The service being registered can be a standard or non-standard R1 service. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.1.3 Test methodology | 5.1.2.1.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 5.1.2.1.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to register a service that it produces. Step 2 At the test simulator the contents of the received HTTP request ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.1.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.2 Update registered service (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.2.1 Test description and applicability | The purpose of this test case is to test the Update registered service API as specified in R1AP [4], clause 6.1.4.2. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.2.2 Test entrance criteria | a) The DUT has functionality to initiate the Update registered service procedure as defined in R1GAP [1]. b) A service API registration exists in test simulator and the serviceApiId and the apfId are known to DUT. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 17 c) The schema of the ServiceAPIDescription used for this test are... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.2.3 Test methodology | 5.1.2.2.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 5.1.2.2.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to update a registered service API identified by the apfId and the serviceApiId. Step 2 At the test simulator t... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.2.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.3 Deregister service (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.3.1 Test description and applicability | The purpose of this test case is to test the Deregister service API as specified in R1AP [4], clause 6.1.4.3. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.3.2 Test entrance criteria | 1) The DUT has functionality to initiate the Deregister service procedure as defined in R1GAP [1]. 2) A service API registration exists in test simulator and the serviceApiId and the apfId are known to DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.3.3 Test methodology | 5.1.2.3.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 5.1.2.3.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to deregister a service API identified by the apfID and the serviceApiId. ETSI ETSI TS 104 229 V3.0.0 (2026-02)... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.3.4 Expected result | The test is considered passed if Step 3 validation has passed. 5.1.2.4 Query registered service (positive case) |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.4.1 Test description and applicability | The purpose of this test case is to test the Query service APIs as specified in R1AP [4], clause 6.1.4.5. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.4.2 Test entrance criteria | 1) The DUT has functionality to initiate Query registered service procedure. 2) A set of service API registrations exist in the test simulator and the apfId is known to DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.4.3 Test methodology | 5.1.2.4.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 5.1.2.4.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to query service APIs that are registered by the apfId. Step 2 At the test simulator the contents of the receiv... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.2.4.4 Expected result | The test is considered passed if Step 3 validation has passed. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 19 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.5.5 Partially updated registered service (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.5.5.1 Test description and applicability | The purpose of this test case is to test the partially update registered service API as specified in R1AP [4], clause 6.1.4.4. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.5.5.2 Test entrance criteria | 1) The DUT has functionality to initiate the Partially update registered service procedure as defined in R1GAP [1]. 2) A service API registration exists in test simulator and the serviceApiId and the apfId are known to DUT. 3) The schema of the ServiceAPIDescriptionPatch used for this test are available and used in DUT... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.5.5.3 Test methodology | 5.1.5.5.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 5.1.5.5.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to partially update a registered service API identified by the apfId and the serviceApiId. Step 2 At the test s... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.1.5.5.4 Expected result | The test is considered passed if Step 3 validation has passed. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 20 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2 Conformance test cases for SMO/Non-RT RIC framework | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.1.1 Device under test requirements | The SMO/Non-RT RIC framework that acts as Device Under Test (DUT) in the test scenarios of this clause can be a product 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 SME service registration service, and the purpose of the ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.1.2 Test simulator capabilities | The test simulator has the capabilities as specified in clause 4.3.2. In addition, it has the following capabilities: 1) Recording of received HTTP requests and responses and analysing them regarding conformance to the R1 service definitions. 2) Controlled initiation of procedures with configurable URIs and payload for... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2 Register service API as API Producer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.1 Register service (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.1.1 Test description and applicability | The purpose of this test case is to test the Register service API as specified in R1AP [4], clause 6.1.4.1. The expected outcome is successful validation of the response from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.1.2 Test entrance criteria | The test simulator has functionality to initiate the Register service procedure as defined in R1GAP [1]. NOTE: The test simulator provides the service API description as defined in R1AP [4]. The service being registered can be a standard or non-standard R1 service. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.1.3 Test methodology | 5.2.2.1.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 5.2.2.1.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to register a service that it produces. Step 2 The DUT receives the HTTP request. Step 3 The DUT do... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.1.4 Expected result | The test is considered passed if Step 7 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.2 Update registered service (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.2.1 Test description and applicability | The purpose of this test case is to test the Update registered service API as specified in R1AP [4], clause 6.1.4.2. The expected outcome is successful validation of the response from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.2.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Update registered service procedure as defined in R1GAP [1]. 2) A service API registration exists in DUT and the serviceApiId and the apfId are known to test simulator. 3) The schema of the ServiceAPIDescription used for this test are available and used in test si... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.2.3 Test methodology | 5.2.2.2.3.1 Initial conditions The DUT as API Producer is ready and available to receive HTTP requests from the test simulator. 5.2.2.2.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to update a registered service API identified by the apfId and the serviceApiId. Step 2 The DUT rece... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.2.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.3 Deregister service (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.3.1 Test description and applicability | The purpose of this test case is to test the Deregister service API as specified in R1AP [4], clause 6.1.4.3. The expected outcome is successful validation of the response from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.3.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Deregister service procedure as defined in R1GAP [1]. 2) A service API registration exists in DUT and the serviceApiId and the apfId are known to test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.3.3 Test methodology | 5.2.2.3.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the test simulator. 5.2.2.3.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to deregister a service API identified by the apfID and the serviceApiId. Step 2 The DUT ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.3.4 Expected result | The test is considered passed if Step 6 validation has passed. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 23 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.4 Query registered service (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.4.1 Test description and applicability | The purpose of this test case is to test the Query service APIs as specified in R1AP [4], clause 6.1.4.5. The expected outcome is successful validation of the response from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.4.2 Test entrance criteria | 1) The test simulator has functionality to initiate Query registered service procedure. 2) A set of service API registrations exist in the DUT and the apfId is known to test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.4.3 Test methodology | 5.2.2.4.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 5.2.2.4.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to query service APIs that are registered by the apfId. Step 2 The DUT receives the HTTP request. S... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.2.4.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.5.5 Partially updated registered service (positive case) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.