hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.1.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.2 Query A1 policy type (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.2.1 Test description and applicability | The purpose of this test case is to test the query A1 policy type API as specified in R1AP [4], clause 9.1.4.2. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.2.2 Test entrance criteria | 1) The DUT has functionality to initiate the query A1 policy type procedure as defined in R1GAP [1], clause 5.3.2. 2) An A1 policy type exists in DUT and the policyTypeId is known to the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.2.3 Test methodology | 11.2.2.2.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. 11.2.2.2.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to query an A1 policy type. Step 2 The DUT receives the HTTP request. Step 3 The DUT does the foll... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.2.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.3 Query A1 policy identifiers (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.3.1 Test description and applicability | The purpose of this test case is to test the query A1 policy identifiers API as specified in R1AP [4], clause 9.1.4.3. The expected outcome is successful validation of the request from the DUT. 11.2.2.3.2 Test entrance criteria 1) The test simulator has functionality to initiate the Query A1 policy identifiers procedur... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.3.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.4 Create A1 policy (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.4.1 Test description and applicability | The purpose of this test case is to test the create A1 policy API as specified in R1AP [4], clause 9.1.4.4. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.4.2 Test entrance criteria | 1) The test simulator has functionality to initiate the create A1 policy procedure as defined in R1GAP [1], clause 5.3.2. 2) The PolicyObjectInformation is known to the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.4.3 Test methodology | 11.2.2.4.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 11.2.2.4.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to create an A1 policy. Step 2 The DUT receives the HTTP request. Step 3 The DUT does the followi... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.4.4 Expected result | The test is considered passed if Step 7 validation has passed. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 69 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.5 Query A1 policy (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.5.1 Test description and applicability | The purpose of this test case is to test the query A1 policy API as specified in R1AP [4], clause 9.1.4.5. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.5.2 Test entrance criteria | 1) The test simulator has functionality to initiate the query A1 policy procedure as defined in R1GAP [1], clause 5.3.2. 2) An A1 policy exists in DUT and the policyId is known to the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.5.3 Test methodology | 11.2.2.5.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. 11.2.2.5.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to query an A1 policy. Step 2 The DUT receives the HTTP request. Step 3 The DUT does the following... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.5.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.6 Update A1 policy (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.6.1 Test description and applicability | The purpose of this test case is to test the Update A1 policy API as specified in R1AP [4], clause 9.1.4.6. The expected outcome is successful validation of the request from the DUT. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 70 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.6.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Update A1 policy procedure as defined in R1GAP [1], clause 5.3.2. 2) An A1 policy exists in the DUT and the policyId and PolicyObject are known to the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.6.3 Test methodology | 11.2.2.6.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. 11.2.2.6.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to update an A1 policy identified by the policyId and PolicyObject. Step 2 The DUT receives the HT... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.7 Delete A1 policy (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.7.1 Test description and applicability | The purpose of this test case is to test the Delete A1 policy API as specified in R1AP [4], clause 9.1.4.6. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.7.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Delete A1 policy procedure as defined in R1GAP [1], clause 5.3.2. 2) An A1 policy exists in DUT and the policyId is known to the test simulator. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 71 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.7.3 Test methodology | 11.2.2.7.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 11.2.2.7.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to Delete an A1 policy. Step 2 The DUT receives the HTTP request. Step 3 The DUT does the followi... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.7.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.8 Query A1 policy status (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.8.1 Test description and applicability | The purpose of this test case is to test the query A1 policy status API as specified in R1AP [4], clause 9.1.4.8. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.8.2 Test entrance criteria | 1) The DUT has functionality to initiate the query A1 policy procedure as defined in R1GAP [1], clause 5.3.2. 2) An A1 policy exists in DUT and the policyId is known to the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.8.3 Test methodology | 11.2.2.8.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. 11.2.2.8.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to query an A1 policy status. Step 2 The DUT receives the HTTP request. ETSI ETSI TS 104 229 V3.0.... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.8.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.9 Subscribe A1 policy status (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.9.1 Test description and applicability | The purpose of this test case is to test the subscribe A1 policy status API as specified in R1AP [4], clause 9.1.4.9. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.9.2 Test entrance criteria | 1) The test simulator has functionality to initiate the subscribe A1 policy status procedure as defined in R1GAP [1], clause 5.3.2. 2) The PolicyStatusSubscription is known to the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.9.3 Test methodology | 11.2.2.9.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. 11.2.2.9.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to create an A1 policy status subscription. Step 2 At the test simulator the contents of the recei... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.9.4 Expected result | The test is considered passed if Step 7 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.10 Update A1 policy status subscription (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.10.1 Test description and applicability | The purpose of this test case is to test the Update A1 policy status subscription API as specified in R1AP [4], clause 9.1.4.10. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.10.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Update A1 policy status subscription procedure as defined in R1GAP [1], clause 5.3.2. 2) An A1 policy status subscription exists in the DUT and the subscriptionId and PolicyStatusSubscription are known to the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.10.3 Test methodology | 11.2.2.10.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. 11.2.2.10.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to update an A1 policy status subscription identified by the subscriptionId and PolicyStatusSubs... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.10.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.11 Query A1 policy status subscription (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.11.1 Test description and applicability | The purpose of this test case is to test the query A1 policy status subscription API as specified in R1AP [4], clause 9.1.4.11. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.11.2 Test entrance criteria | 1) The DUT has functionality to initiate the query A1 policy status subscription procedure as defined in R1GAP [1], clause 5.3.2. 2) An A1 policy status subscription exists in test simulator and the subscriptionId is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.11.3 Test methodology | 11.2.2.11.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. 11.2.2.11.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to query an A1 policy status subscription. Step 2 The DUT receives the HTTP request. Step 3 The ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.11.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.12 Unsubscribe A1 policy status (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.12.1 Test description and applicability | The purpose of this test case is to test the Unsubscribe A1 policy status API as specified in R1AP [4], clause 9.1.4.12. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.12.2 Test entrance criteria | 1) The DUT has functionality to initiate the Unsubscribe A1 policy procedure as defined in R1GAP [1], clause 5.3.2. 2) An A1 policy subscription exists in DUT and the subscriptionId is known to the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.12.3 Test methodology | 11.2.2.12.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 11.2.2.12.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to delete an A1 policy status subscription. Step 2 The DUT receives the HTTP request. Step 3 Th... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.12.4 Expected result | The test is considered passed if Step 6 validation has passed. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 76 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.13 Notify A1 policy status changes (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.13.1 Test description and applicability | The purpose of this test case is to test the Notify A1 policy status changes API as specified in R1AP [4], clause 9.1.4.13. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.13.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Notify A1 policy status changes procedure as defined in R1GAP [1], clause 5.3.2. 2) An A1 policy status exists in the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.13.3 Test methodology | 11.2.2.13.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. 11.2.2.13.3.2 Procedure Step 1 The DUT as an API producer initiates the sending of a HTTP POST request. Step 2 At the test simulator the contents of the received HTTP request are recorded. S... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.13.4 Expected result | The test is considered passed if Step 3 validation has passed. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 77 Annex A (informative): Change history Date Version Information about changes 2025.03.13 03.00 Published with Conformance test of rApp and Non-RT RIC as DUT for DME, A1 policy management and SME 2024.11.21 02.00 Publi... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 1 Scope | The present document specifies the protocol conformance testing for testing a MCPTT Server for compliance to the Mission Critical Push To Talk (MCPTT) over LTE protocol requirements defined by 3GPP. The present document addresses only MCPTT Server-Client communication scenarios. It does not cover e.g. MCPTT Server-EPS,... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 2 References | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 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... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 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... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 3 Definitions of terms, symbols and abbreviations | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 3.1 Terms | For the purposes of the present document, the terms and definitions given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply. NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). For the purpose of the prese... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 3.2 Symbols | Void. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply. NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). ECGI E-UTRAN Cell G... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 4 General | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 4.1 Test methodology | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 4.1.1 Testing of optional functions and procedures | Any function or procedure which is optional may be subject to a conformance test if it is implemented in the MCPTT Server. A declaration by the Client supplier (to use the Implementation Conformance Statement (ICS) proforma specified in ETSI TS 136 579-4 [2] (3GPP TS 36.579-4)) is used to determine whether an optional ... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 4.1.2 Test interfaces and facilities | Detailed descriptions of the MCPTT Server to MCPTT Client test interfaces and special facilities for testing are provided in ETSI TS 136 509 [17] (3GPP TS 36.509). Descriptions of the MCPTT Server to MCPTT Server interface is specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1). |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 4.2 Implicit testing | For some 3GPP MCPTT protocol features conformance is not verified explicitly in the present document. This does not imply that correct functioning of these features is not essential, but that these are implicitly tested to a sufficient degree in tests which are not explicitly dedicated to test the feature. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 4.3 Repetition of tests | As a general rule, the test cases specified in the present document are highly reproducible and do not need to be repeated unless otherwise stated. 4.4 Handling of differences between conformance requirements in different releases of cores specifications The conformance requirements which determine the scope of each te... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 4.5 Reference conditions | The reference environments used by all signalling and protocol tests are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1). Where a test requires an environment that is different, this will be specified in the test itself. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 18 |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 4.6 Generic setup procedures | A set of basic generic procedures for MCPTT Client-Server and MCPTT Client-Client communication are described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1). These procedures will be used in numerous test cases throughout the present document. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5 MCPTT Server - MCPTT Client Configuration | 5.1 MCPTT Server - MCPTT Client / Configuration / Authentication / User Authorisation / UE Configuration / User Profile / Key generation |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.1.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCPTT client) activates an MCPTT application and requests MCPTT initialisation } then { IUT (MCPTT Server) provides the initial UE configuration and performs MCPTT User Authentication and provides id_token, access_token and refresh toke... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.1.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 482 [28] (3GPP TS 24.482) clause 6.3.1, clause A.2.1.3, clause A.2.3, ETSI TS 124 484 [29] (3GPP TS 24.484) clauses 4.3, 4.4, 6.2.3, 6.3.1.2, 6.3.2.3, 6.3.13.3.2.2, ETSI TS 124 481 [27] (3GPP TS 24.481) clauses 6.2.4, 6.3.3... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.1.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 29 - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client) and the MCPTT Server will communicate Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI TS 1... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.1.3.2 Test procedure sequence | Table 5.1.3.2-1: Main behaviour St Procedure Message Sequence TP Verdict U - S Message 0A The SS-UE1 (MCPTT client) sends an HTTP GET (initial UE configuration) request to retrieve the initial UE configuration from the Server. --> HTTP GET - - 0B Check: Does the IUT (MCPTT Server) respond by sending an HTTP 200 (OK) in... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.1.3.3 Specific message contents | Table 5.1.3.3-1: HTTP POST (Step 1, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.3-1, condition AUTH Table 5.1.3.3-2: HTTP POST (Step 3, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.3-1, condition USERAUTH ETSI ETSI TS 104 147-1 V1.1.... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.2.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 and supports new MCPTT terminated group } ensure that { when { the UE (MCPTT client) initiates creation of the terminated group by sending a HTTP PUT request } then { IUT (MCPTT Server) responds to the UE (MCPTT Client) with a HTTP 201 (Created) } } (2) with { IUT (MCPTT... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.2.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 481 [27] (3GPP TS 24.481) clauses 6.3.2.3, 6.3.14.3.1 and 6.3.15.3.1; ETSI TS 133 180 [31] (3GPP TS 33.180), clauses 7.3.2 and 7.3.3.2. Unless otherwise stated these are Rel-13 requirements. [ETSI TS 124 481 [27] (3GPP TS 2... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.2.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client) and the MCPTT Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI TS 136 508 [23] (3GPP TS 36.508) clause 4.4. T... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.2.3.2 Test procedure sequence | Table 5.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCPTT Server correctly perform procedure 'MCX Server Terminated Group Creation' as described in Annex A, Table A.2.4.3-1 to create group B? - - 1 P 2 Check: Does the MCPTT Server correctly perform procedure 'MCX Ser... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.2.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications: • Subclauses referring to messages from UE relate to SS-UE1 (MCX Client). ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 39 5.3 MCPTT Server - MCPTT Client / Configurati... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.3.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) having received the provisioned MCPTT Client's group information or a pointer to the group information, indicating that the MCPTT Client is authorized to affiliate with the specified group} ensure that { when { the SS-UE1 (MCPTT client ) requests for own affiliation status and to subscribe... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.3.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 9.2.2.2.3, 9.2.2.2.4, 9.2.2.2.5, 9.2.2.2.8 and 9.2.2.2.15. Unless otherwise stated these are Rel-13 requirements. [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 9.2.2.2.3] "Upon receiving a S... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.3.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.3.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) and SS-UE2 (MCPTT Client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client), the SS-UE2 (MCPTT client) and the MCPTT Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined i... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.3.3.2 Test procedure sequence | Table 5.3.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCPTT Server correctly perform procedure 'MCPTT Group Affiliation Status Determination and Subscription' as described in Annex A, Table A.3.7.3-1 to subscribe the SS-UE1 (MCPTT client) to own affiliation status chan... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.3.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 50 Table 5.3.3.3-1: SIP SUBSCRIBE from the SS-UE1 (Step 1, Table 5.3.3.2-1; Step 1, Annex A, Table A.3.7.3-1) Derivation P... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.4.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) is able to create pre-established session } ensure that { when { the SS-UE1 (MCPTT client ) requests creation of pre-established session with sending SIP INVITE message } then { IUT (MCPTT Server) responds with optional SIP 100 Trying and mandatory 200 (OK) message } } (2) with { IUT (MCPT... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.4.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 8.2.2, 8.3.2.1, 8.3.2.2, 8.4.2.1 and 8.4.2.2. Unless otherwise stated these are Rel-13 requirements. [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 8.2.2] "Upon receipt of a "SIP INVITE reque... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.4.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.4.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client) and the MCPTT Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in ETSI TS 136 508 [23] (3GPP TS 36.508) clause 4.4. T... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.4.3.2 Test procedure sequence | Table 5.4.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCPTT server correctly perform test procedure 'MCX Participating Terminated pre-established session establishment' as described in Annex A, Table A.2.13.3-1 to create a pre-established session without implicit floor... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.4.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 5.4.3.3-1: SIP INVITE from the SS-UE1 (Steps 1 and 4, Table 5.4.3.2-1; Step 1, Annex A, Table A.2.13.3-1) Derivation Path: Annex A, Table A.2.13.4-1, condit... |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 5.5.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCPTT client ) requests to determine the currently active MCPTT service settings with SIP SUBSCRIBE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (2) with { IUT (MCPTT Server... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.