hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.1.2.11.3 Test methodology | 11.1.2.11.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 11.1.2.11.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to query an A1 policy status subscription. 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 9.1.4.11. b) The HTTP request is a GET operation. c) The subscriptionId in the URI match the A1 policy status subscription being queried. d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.11. Step 4 The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.8. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.1.2.11.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.1.2.12 Unsubscribe A1 policy status (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.1.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.1.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 status subscription exists in test simulator and the subscriptionId is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.1.2.12.3 Test methodology | 11.1.2.12.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 11.1.2.12.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to delete an A1 policy status subscription. 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 9.1.4.12. b) The HTTP request is a DELETE operation. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 65 c) The subscriptionId in the URI match the A1 policy status subscription being deleted. The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.12. Step 4 The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.8. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.1.2.12.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2 Conformance test cases for SMO/Non-RT RIC framework | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.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 subscription 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 9.1.4. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.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 9.1.4. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2 A1 policy management API as API Producer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.1 Query A1 policy type identifiers (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.1.1 Test description and applicability | The purpose of this test case is to test the query A1 policy type identifiers API as specified in R1AP [4], clause 9.1.4.1. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 11.2.2.1.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Query A1 policy type identifiers procedure as defined in R1GAP [1], clause 5.3.2. 2) A set of A1 policy types exists in the DUT. 11.2.2.1.3 Test methodology 11.2.2.1.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 66 11.2.2.1.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to query a set of A1 policy type identifiers. 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 9.1.4.1. b) The HTTP request is a GET operation. c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.1. Step 4 The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.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 9.1.5.2. b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.1. |
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 following validation: a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.3. b) The HTTP request is a GET operation. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 67 c) The policyTypeId in the URI match the A1 policy type being queried. The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.2. Step 4 The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.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 conforms to the format specified in R1AP [4], clause 9.1.5.3. b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.2. |
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 procedure as defined in R1GAP [1], clause 5.3.2. 2) A set of A1 policies exists in the DUT. 11.2.2.3.3 Test methodology 11.2.2.3.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. 11.2.2.3.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to query a set of A1 policy identifiers. 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 9.1.5.4. b) The HTTP request is a GET operation. c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.3. Step 4 The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.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 9.1.5.4. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 68 b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.3. |
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 following validation: a) The HTTP request is a POST request. b) The URI conforms to the format specified in R1AP [4], clause 9.1.5.4. c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.4. Step 4 The DUT generates the A1 policy and constructs the URI for the created resource. Step 5 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.4. 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 9.1.4.4, and the Location header will be present. b) The URI conforms to the format specified in R1AP [4], clause 9.1.5.4. |
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 validation: a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.5. b) The HTTP request is a GET operation. c) The policyId in the URI match the A1 policy being queried. d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.5. Step 4 The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.5. 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 9.1.5.5. b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.5. |
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 HTTP request. Step 3 The DUT does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.5. b) The HTTP request is a PUT operation. c) The policyId and PolicyObject in the URI match the A1 policy being updated. d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.6. Step 4 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.6. 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 9.1.5.5. b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.6. 11.2.2.6.4 Expected result The test is considered passed if Step 6 validation has passed. |
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 following validation: a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.5. b) The HTTP request is a DELETE operation. c) The policyID in the URI match the A1 policy being deleted. d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.7. Step 4 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.7. 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 9.1.5.5. b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.7. |
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.0 (2026-02) 72 Step 3 The DUT does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.36. b) The HTTP request is a GET operation. c) The policyId in the URI match the A1 policy status being queried. d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.8. Step 4 The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.8. 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 9.1.5.6. b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.8. |
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 received HTTP request are recorded. 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 9.1.5.7. c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.9. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 73 Step 4 The DUT generates the A1 policy status subscription and constructs the URI for the created resource. Step 5 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.9. 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 9.1.4.9, and the Location header will be present. b) The URI conforms to the format specified in R1AP [4], clause 9.1.5.7. |
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 PolicyStatusSubscription. 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 9.1.5.8. b) The HTTP request is a PUT operation. c) The subscriptionId and PolicyStatusSubscription in the URI match the A1 policy status subscription being updated. d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.10. Step 4 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.10. Step 5 At the test simulator the contents of the received HTTP response are recorded. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 74 Step 6 The test simulator does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.8. b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.10. |
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 DUT does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.8. b) The HTTP request is a GET operation. c) The subscriptionId in the URI match the A1 policy status subscription being queried. d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.11. Step 4 The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.5. 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 9.1.5.8. b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.11. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 75 |
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 The DUT does the following validation: a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.8. b) The HTTP request is a DELETE operation. c) The subscriptionId in the URI match the A1 policy status subscription being deleted. d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.12. Step 4 The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.12. 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 9.1.5.8. b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.12. |
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. Step 3 The test simulator does the following validation: a) The HTTP request is a POST operation. b) The callback URI matches the URI provided in the A1 policy status subscription. |
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 Published with Conformance test of Non-RT RIC as DUT for Service registration test case 2024.07.11 01.00 Published with conformance testing of rApps and SMO/Non-RT RIC Framework and with one Service registration test case ETSI ETSI TS 104 229 V3.0.0 (2026-02) 78 History Version Date Status V3.0.0 February 2026 Publication |
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, MCPTT Server-SIP Core, etc. scenarios which involve interfaces which implementation may widely vary. In particular the present specification contains: • the overall test structure; • the test configurations; • the conformance requirement and reference to the core specifications; • the test purposes; and • a brief description of the test procedure, the specific test requirements and short message exchange table. The present document is valid for MCPTT Servers implemented according to 3GPP releases starting from Release 14 up to the Release indicated on the cover page of the present document. The following information relevant to testing specified in the present document could be found in accompanying specifications: • default setting of the test parameters ETSI TS 136 579-1 [1] (3GPP TS 36.579-1); • Implementation Conformance Statement (ICS) ETSI TS 136 579-4 [2] (3GPP TS 36.579-4) and Implementation extra Information for Testing (IXIT) ETSI TS 136 579-5 [i.7] (3GPP TS 36.579-5); • the applicability of each test case ETSI TS 136 579-4 [2] (3GPP TS 36.579-4). The present document does not specify the protocol conformance testing for the EPS (LTE) bearers which carry the MCPTT data sent or received by the MCPTT Server. The specification of such testing is out of the scope of RAN5. |
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 are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 136 579-1: "LTE; Mission Critical (MC) services over LTE; Part 1: Common test environment (3GPP TS 36.579-1)". [2] ETSI TS 136 579-4: "LTE; Mission Critical (MC) services over LTE; Part 4: Test Applicability and Implementation Conformance Statement (ICS) proforma specification (3GPP TS 36.579-4)". [3] ETSI TS 123 179: "LTE; Functional architecture and information flows to support mission critical communication services; Stage 2 (3GPP TS 23.179)". ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 13 [4] ETSI TS 124 379: "LTE; Mission Critical Push To Talk (MCPTT) call control; Protocol specification (3GPP TS 24.379)". [5] ETSI TS 124 380: "LTE; Mission Critical Push To Talk (MCPTT) media plane control; Protocol specification (3GPP TS 24.380)". [6] ETSI TS 133 310: "Universal Mobile Telecommunications System (UMTS); LTE; 5G; Network Domain Security (NDS); Authentication Framework (AF) (3GPP TS 33.310)". [7] IETF RFC 5245: "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols". [8] IETF RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". [9] ETSI TS 124 282: "LTE; Mission Critical Data (MCData) signalling control; Protocol specification (3GPP TS 24.282)". [10] ETSI TS 124 281: "LTE; Mission Critical Video (MCVideo) signalling control; Protocol specification (3GPP TS 24.281)". [11] ETSI TS 126 114: "Universal Mobile Telecommunications System (UMTS); LTE; 5G; IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction (3GPP TS 26.114)". [12] IETF RFC 6335: "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry". [13] IETF RFC 4867: "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs". [14] IETF RFC 5621 (September 2009): "Message Body Handling in the Session Initiation Protocol (SIP)". [15] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol". [16] IETF RFC 7134: "The Management Policy of the Resource Priority Header (RPH) Registry Changed to "IETF Review"". [17] ETSI TS 136 509: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Special conformance testing functions for User Equipment (UE) (3GPP TS 36.509)". [18] IETF RFC 8101: "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk service". [19] IETF RFC 3903 (October 2004): "Session Initiation Protocol (SIP) Extension for Event State Publication". [20] IETF RFC 4412 (February 2006): "Communications Resource Priority for the Session Initiation Protocol (SIP)". [21] IETF RFC 6665 (July 2012): "SIP-Specific Event Notification". [22] IETF RFC 4028 (April 2005): "Session Timers in the Session Initiation Protocol (SIP)". [23] ETSI TS 136 508: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Common test environments for User Equipment (UE) conformance testing (3GPP TS 36.508)". [24] IETF RFC 5366 (October 2008): "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)". [25] ETSI TS 123 283: "LTE; Mission Critical Communication Interworking with Land Mobile Radio Systems (3GPP TS 23.283)". ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 14 [26] ETSI TS 123 280: "LTE; Common functional architecture to support mission critical services; Stage 2 (3GPP TS 23.280)". [27] ETSI TS 124 481: "LTE; Mission Critical Services (MCS) group management; Protocol specification (3GPP TS 24.481)". [28] ETSI TS 124 482: "LTE; Mission Critical Services (MCS) identity management; Protocol specification (3GPP TS 24.482)". [29] ETSI TS 124 484: "LTE; Mission Critical Services (MCS) configuration management; Protocol specification (3GPP TS 24.484)". [30] ETSI TS 133 179: "LTE; Security of Mission Critical Push To Talk (MCPTT) over LTE (3GPP TS 33.179)". [31] ETSI TS 133 180: "LTE; Security of the Mission Critical (MC) service (3GPP TS 33.180)". [32] IETF RFC 4354: "A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service". [33] IETF RFC 2854: "The 'text/html' Media Type". [34] W3C® Recommendation 24 December 1999: "HTML 4.01 Specification". |
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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; Vocabulary for 3GPP Specifications (3GPP TR 21.905)". [i.2] ETSI TS 136 579-3: "LTE; Mission Critical (MC) services over LTE; Part 3: Mission Critical Push To Talk (MCPTT) Server Application conformance specification (3GPP TS 36.579-3)". [i.3] 3GPP TS 36.579-9: "Mission Critical (MC) services over LTE; Part 9: Mission Critical Data (MCData) Server Application conformance specification". [i.4] 3GPP TS 36.579-8: "Mission Critical (MC) services over LTE; Part 8: Mission Critical Video (MCVideo) Server Application conformance specification". [i.5] ETSI TS 122 179: "LTE; 5G; Mission Critical Push to Talk (MCPTT); Stage 1 (3GPP TS 22.179)". [i.6] ETSI TS 136 579-2: "LTE; Mission Critical (MC) services over LTE; Part 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specification (3GPP TS 36.579-2)". [i.7] ETSI TS 136 579-5: "LTE; Mission Critical (MC) services over LTE; Part 5: Abstract test suite (ATS) (3GPP TS 36.579-5)". [i.8] ETSI TS 136 579-6: "LTE; Mission Critical (MC) services over LTE; Part 6: Mission Critical Video (MCVideo) User Equipment (UE) Protocol conformance specification (3GPP TS 36.579-6)". [i.9] ETSI TS 136 579-7: "LTE; Mission Critical (MC) services over LTE; Part 7: Mission Critical Data (MCData) User Equipment (UE) Protocol conformance specification (3GPP TS 36.579-7)". ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 15 |
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 present document, the following terms and definitions given in ETSI TS 124 379 [4] (3GPP TS 24.379) apply: • An MCPTT user is affiliated to an MCPTT group • An MCPTT user is affiliated to an MCPTT group at an MCPTT client • Affiliation status • Group identity • In-progress emergency private call state • In-progress imminent peril group state • MCPTT client ID • MCPTT emergency alert state • MCPTT emergency group state • MCPTT emergency group call state • MCPTT emergency private call state • MCPTT emergency private priority state • MCPTT imminent peril group call state • MCPTT imminent peril group state • MCPTT private emergency alert state • MCPTT speech • Media-floor control entity • Temporary MCPTT group identity • Trusted mutual aid • Untrusted mutual aid For the purposes of the present document, the following terms and definitions given in ETSI TS 122 179 [i.5] (3GPP TS 22.179) apply: • In-progress emergency • MCPTT emergency alert • MCPTT emergency group call • MCPTT emergency state ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 16 • Partner MCPTT system • Primary MCPTT system For the purpose of the present document, the following terms and definitions given in ETSI ETSI TS 124 380 [5] (3GPP TS 24.380) apply: • MBMS subchannel For the purpose of the present document, the following terms and definitions given in ETSI TS 123 179 [3] (3GPP TS 23.179) apply: • Pre-selected MCPTT user profile |
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 Global Identification GKTP Group Key Transport Payload ICS Implementation Conformance Statement IUT Implementation Under Test MBMS Multimedia Broadcast and Multicast Service MCPTT group ID MCPTT group IDentity MCPTT Mission Critical Push To Talk MEG MCPTT Emergency Group MEPC MCPTT Emergency Private Call MEPP MCPTT Emergency Private Priority MIG MCPTT Imminent peril Group MIME Multipurpose Internet Mail Extensions MPEA MCPTT Private Emergency Alert OIDC OpenID Connect PLMN Public Land Mobile Network QCI QoS Class Identifier RTP Real-time Transport Protocol SDP Session Description Protocol SIP Session Initiation Protocol SS System Simulator SSRC Synchronization SouRCe TMGI Temporary Mobile Group Identity TP Test Purpose TP Transmission Point URI Uniform Resource Identifier XCAP eXtensible Markup Language (XML) Access Configuration Protocol ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 17 |
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 function/procedure has been implemented. |
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 test case are explicitly copy-pasted from relevant core specifications in the especially dedicated for this clause of each test with the title 'Conformance requirements'. NOTE: When in the copy/pasted text there are references to other specifications the reference numbers will not match the reference numbers used in the present specification. This approach has been taken in order to allow easy copy and then search for conformance requirements in those specifications. When differences between conformance requirements in different releases of the cores specifications have impact on the Pre-test conditions, Test procedure sequence or/and the Specific message contents, the Conformance requirements related to different releases are specified separately with clear indication of the Release of the spec from which they were copied. When there is no Release indicated for a conformance requirement text, this should be understood either as the Conformance requirements in the latest version of the spec with release = the TC Applicability release (which can be found in ETSI TS 136 579-4 [2] (3GPP TS 36.579-4), Table 4-2: Applicability of tests and additional information for testing, column 'Release'), or, as the Conformance requirements in the latest version of the spec of the release when the feature was introduced to the core specs. |
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 token to the successfully authenticated user} } (2) with { IUT (MCPTT Server) having authenticated the SS-UE1 (MCPTT client) } ensure that { when { the SS-UE1 (MCPTT Client) initiates key management authorization } then { IUT (MCPTT Server) provides identity management key material } } (3) with { IUT (MCPTT Server) having provided identity management key material } ensure that { when { the SS-UE1 (MCPTT client) requests user service authorization } then { IUT (MCPTT Server) responds to the SS-UE1 (MCPTT Client) with SIP 200 (OK) messages } } (4) with { IUT (MCPTT Server) having provided service authorization } ensure that { when { the SS-UE1 (MCPTT client) requests configuration management authorization} then { IUT (MCPTT Server) responds to the SIP SUBSCRIBE message with a SIP 200 (OK) message and sends a SIP NOTIFY message containing the XCAP-URI of the documents and sends the MCPTT UE Configuration Document and MCPTT User Profile Configuration Document MCPTT Service Configuration Document via HTTP 200 (OK) messages in response to HTTP GET requests } } (5) with { IUT (MCPTT Server) having provided user configuration data } ensure that { when { the SS-UE1 (MCPTT client) requests group management authorization } then { IUT (MCPTT Server) responds to the SS-UE1 (MCPTT Client) with SIP 200 (OK) messages and sends the XCAP-URI of the Group documents via a SIP NOTIFY message and sends the Group Document 'MCPTT UE Configuration document' via a HTTP 200 (OK) message in response to a HTTP GET request and sends the group key transport payloads (GKTP) document via a SIP NOTIFY message } } ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 19 (6) with { IUT (MCPTT Server) having provided all required configuration data } ensure that { when { the SS-UE1 (MCPTT client) requests to refresh its service settings } then { IUT (MCPTT Server) responds to the SS-UE1 (MCPTT Client) with a SIP 200 (OK) message } } |
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.3, 6.3.13.3.2.2, ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 7.3.2, 7.3.3, 7.3.4, ETSI TS 133 179 [30] (3GPP TS 33.179) clauses 5.6.1, 7.2.3, Annex D.1. Unless otherwise stated these are Rel-13 requirements. [ETSI TS 124 482 [28] (3GPP TS 24.482), clause 6.3.1] "Upon receipt of an OIDC Authentication Request message as specified in the OpenID Connect 1.0 [6] and IETF RFC 6749 [5] via a secure TLS tunnel between the identity management client and the authorisation endpoint of the IdM server, the IdM server: 1) shall validate the received OIDC Authentication Request message as specified in the OpenID Connect 1.0 [6] and IETF RFC 6749 [5]; 2) shall generate an HTTP 200 (OK) response according to IETF RFC 2616 [4] including form data to prompt the MCPTT user for their username and password credentials; and NOTE 1: The username will be the MCPTT user's MC ID. 3) shall send the HTTP 200 (OK) response towards the IdM client. Upon receipt of an HTTP POST request method from the IdM client containing the MCPTT user's username and password, the IdM server authenticates the MCPTT user and: NOTE 2: Other methods of authentication can be used by the MCPTT service provider and are not defined by the OIDC specifications. 3GPP TS 33.179 [2] has defined username and password as a mandatory authentication method to be supported for MCPTT, hence a procedure to realize that method is included here. 1) shall generate an OIDC Authentication Response message as specified in OpenID Connect 1.0 [6] and IETF RFC 6749 [5] with the following clarifications: a) shall generate an HTTP 302 (FOUND) response according to IETF RFC 2616 [4]; and b) shall include the required parameters including the authorization_code as specified in 3GPP TS 33.179 [2] in the query component of the redirection URI contained in the Location header field of the HTTP FOUND request method using the "application/x-www-form-urlencoded" format as specified in W3C.REC-html401-19991224 [7]; and 2) shall send the HTTP 302 (FOUND) response towards the IdM client. Upon receipt of an OIDC Token Request message via a secure TLS tunnel established between the identity management client and the token endpoint of the IdM server, the IdM server: 1) shall validate the OIDC Token Request message and if valid shall generate an OIDC Token Response message as specified in OpenID Connect 1.0 [6] and IETF RFC 6749 [5] with the following clarifications: a) shall generate an HTTP 200 (OK) response according to IETF RFC 2616 [4]; b) shall based on the received MC ID obtained from the received user authentication credentials, determine the MCPTT ID of the MCPTT user; c) shall include an id_token, access_token and refresh_token and MCPTT ID as specified in 3GPP TS 33.179 [2]; and ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 20 d) shall include the other required parameters as specified in OpenID Connect 1.0 [6] and IETF RFC 6749 [5]; and 2) shall send the HTTP 200 (OK) response towards the IdM client." [ETSI TS 124 482 [28] (3GPP TS 24.482), clause A.2.1.3] "The HTTP client in the network entity is configured with the following parameters: 1) a home HTTP proxy FQDN; and 2) a home HTTP proxy port. The HTTP client in the network entity shall send and receive all HTTP messages via the home HTTP proxy. The HTTP client in the network entity shall insert an X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.109 [15] in the HTTP request and shall set X-3GPP-Asserted-Identity header field to the identity of the HTTP client in the network entity. The identity of the HTTP client in the network entity can be a public service identity, an MCPTT group ID, or an MCPTT ID." [ETSI TS 124 482 [28] (3GPP TS 24.482), clause A.2.3] "The HTTP server shall support the server role of IETF RFC 2616 [4]. Upon reception of an HTTP request: 1) if the received HTTP request does not contain an Authorization header field with the "Bearer" authentication scheme and a bearer access token as specified in IETF RFC 6750 [14] and the received HTTP request does not contain an X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.109 [15], the HTTP server shall reject the request with HTTP 403 (Forbidden) response; 2) if the received HTTP request contains an Authorization header field with the "Bearer" authentication scheme and a bearer access token as specified in IETF RFC 6750 [14]; a) the HTTP server shall validate the bearer access token as specified in IETF RFC 6750 [14]; and b) the HTTP server shall consider the MCPTT ID derived from the bearer access token as the identity of the sender of the HTTP request; and 3) if the received HTTP request does not contain an Authorization header field with the "Bearer" authentication scheme and a bearer access token as specified in IETF RFC 6750 [14] and the received HTTP request contains an X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.109 [15], the HTTP server shall consider the URI in the X-3GPP-Asserted-Identity header field as the identity of the sender of the HTTP request." [ETSI TS 124 484 [29] (3GPP TS 24.484), clause 4.3] "The MCPTT server obtains the MCPTT service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCPTT service from the configuration management server. The format of the MCPTT service configuration document downloaded to the MCPTT server is defined in subclause 7.5. The MCPTT server obtains the MCPTT service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCPTT service from the configuration management server. The MCPTT server subscribes to the MCPTT service configuration document for each mission critical organisation that is provisioned that is supported by the MCPTT server using the procedure specified in subclause 6.3.13.2.3. How the MCPTT server is provisioned with the identities of the mission critical organisations is out of scope of the present document. If the MCPTT service configuration document has been updated since the current version stored at the MCPTT server, then the MCPTT server will receive a SIP NOTIFY request containing an HTTPS URI of the MCPTT service configuration document. Retrieval by the MCPTT server, using the notified HTTPS URI, of the MCPTT service configuration document is performed as specified in subclause 6.3.3.2.3. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 21 NOTE: The MCPTT server can be notified of changes to the MCPTT service management configuration document at any time while operating the MCPTT service. The format of the MCPTT service configuration document downloaded to the MCPTT server is defined in subclause 7.5." [ETSI TS 124 484 [29] (3GPP TS 24.484), clause 4.4] "The following applies to the configuration management server used for online configuration. The configuration management server needs to convert the MCPTT UE initial configuration document received from a MCPTT administrator into an appropriate format for configuration of the MCPTT UE initial configuration MO. If the MCPTT UE initial configuration MO contains a <default-user-profile> element that identifies a MCPTT user profile configuration document, the configuration management server needs to convert the identified MCPTT user profile configuration document received from a MCPTT administrator into an appropriate format for configuration of the MCPTT user profile configuration MO. Once an MCPTT User Profile configuration document has been created or updated by the MCPTT UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to store MCPTT user profile configuration document as the user profile in the MCPTT user database. In order to download MCPTT the user profile configuration document to an MCPTT UE or to support an MCPTT UE updating the MCPTT user profile configuration document, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to obtain the MCPTT user profile from the MCPTT user database. In order to be notified of changes to an MCPTT user profile configuration document that have been subscribed to by an MCPTT UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to be notified of changes to the MCPTT user profile stored in the MCPTT user database. In order to delete the MCPTT user profile when requested by an MCPTT UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to delete the MCPTT user profile from the MCPTT user database. NOTE: The configuration management server and group management server functionality for offline configuration is out of scope of the present document." [ETSI TS 124 484 [29] (3GPP TS 24.484), clause 6.2.3] "The MCPTT server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.382 [6]." [ETSI TS 124 484 [29] (3GPP TS 24.484), clause 6.2.4] "The CMS shall handle the HTTP request as specified for the HTTP server in annex A of 3GPP TS 24.382 [6]. The CMS shall be configured with an authorized MCPTT server list, containing public service identities of MCPTT servers of the MCPTT provider of the CMS. When handling an HTTP request, the CMS shall determine the identity of the sender of the HTTP request as specified in 3GPP TS 24.382 [6], and shall use the identity of the sender of the HTTP request as an authenticated identity when performing the authorization." [ETSI TS 124 484 [29] (3GPP TS 24.484), clause 6.3.1.2] "A CMS shall support subclause 6.2.1 "Document Management", and subclause 6.2.4 "Access Permissions" of OMA OMA-TS-XDM_Core-V2_1 [2] and subclause 6.3.13.3 for accepting subscriptions to configuration management documents." [ETSI TS 124 484 [29] (3GPP TS 24.484), clause 6.3.2.3] "A CMS shall support receiving XML documents of the application usages specified in subclause 7.2.1, subclause 7.3.1, subclause 7.4.1 and subclause 7.5.1according to procedures specified in IETF RFC 4825 [14] "PUT Handling" where the Request-URI of the HTTP PUT request identifies an XML document and include the "auid" as per the appropriate application usage in clause 7." ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 22 [ETSI TS 124 484 [29] (3GPP TS 24.484), clause 6.3.13.3.2.2] "Upon reception of an initial SIP SUBSCRIBE request: a) with the Event header field set to xcap-diff; b) with the Request-URI set to own public service identity for performing subscription proxy function of the CMS; c) with a P-Asserted-Identity header field not containing an identity listed in the authorized MCPTT server list specified in subclause 6.2.4; d) with an application/vnd.3gpp.mcptt-info+xml MIME body containing the <mcptt-access-token> element; e) with an application/resource-lists+xml MIME body; and f) with the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24 229 [12]), in a P-Asserted-Service header field according to IETF RFC 6050 [23]; the CMS: a) if an <EncryptedData> XML tag is included in the application/vnd.3gpp.mcptt-info+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/vnd.3gpp.mcptt-info+xml MIME body; b) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; c) shall identify the originating MCPTT ID from <mcptt-access-token> element received in the application/vnd.3gpp.mcpttinfo+xml MIME body and shall use the originating MCPTT ID as an authenticated identity when performing the authorization; d) if the authenticated identity is not authorized to subscribe to notification of changes of any resource in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; e) act as a notifier according to IETF RFC 5875 [11]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the initial SIP SUBSCRIBE request contains an "auid" parameter set to an application usage identifying a configuration management document as described in clause 7; shall return the XCAP URI identifying the configuration management document in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request. Upon sending a SIP NOTIFY request associated with a subscription created as result of the received initial SIP SUBSCRIBE request, if the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, the CMS shall perform the confidentiality protection procedures and integrity protection procedures defined in 3GPP TS 24.379 [9] for MCPTT server. Upon reception of a SIP re-SUBSCRIBE request: a) with the Event header field set to xcap-diff; and b) with an application/resource-lists+xml MIME body; the CMS: a) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body of the received SIP re-SUBSCRIBE request and the CSK was received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; and ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 23 b) act as a notifier according to IETF RFC 5875 [11]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the SIP re-SUBSCRIBE request contains an "auid" parameter set to an application usage identifying a configuration management document as described in clause 7: and for which there is no related subscription established according to the subclause 6.3.13.3.2.3, shall return the XCAP URI identifying the configuration management document in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request." [ETSI TS 124 481 [27] (3GPP TS 24.481), clause 6.2.4] "The MCPTT server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.382 [10]. The MCPTT server shall perform the procedures in subclause 6.2.2 specified for GC." [ETSI TS 124 481 [27] (3GPP TS 24.481), clause 6.3.3.3] "A GMS shall support handling an HTTP GET request from a GMC according to procedures specified in IETF RFC 4825 [22] "GET Handling" where the Request-URI of the HTTP GET request identifies an XML document of the application usage specified in subclause 7.2." [ETSI TS 124 481 [27] (3GPP TS 24.481), clause 6.3.13.3.2.2] "Upon reception of an initial SIP SUBSCRIBE request: a) with the Event header field set to xcap-diff; b) with the Request-URI set to own public service identity for performing subscription proxy function of the GMS; c) with a P-Asserted-Identity header field not containing an identity listed in the authorized MCPTT server list specified in subclause 6.2.5.1 and not containing an identity listed in the authorized GMS list as specified in subclause 6.2.5.1; d) with an application/vnd.3gpp.mcptt-info+xml MIME body containing the <mcptt-access-token> element; e) with an application/resource-lists+xml MIME body; and f) with the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24 229 [12]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; the GMS: a) if an <EncryptedData> XML tag is included in the application/vnd.3gpp.mcptt-info+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/vnd.3gpp.mcptt-info+xml MIME body; b) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body and the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; c) shall identify the originating MCPTT ID from <mcptt-access-token> element received in the application/vnd.3gpp.mcptt-info+xml MIME body and shall use the originating MCPTT ID as an authenticated identity when performing the authorization; d) if the authenticated identity is not authorized to subscribe to notification of changes of any resource in the application/resource-lists+xml MIME body, shall reject the request with a SIP 403 (Forbidden) response and shall not continue with rest of the steps; e) act as a notifier according to IETF RFC 5875 [13]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the initial SIP SUBSCRIBE request identifies: 1) a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is an MCPTT group ID owned by an MCPTT provider other than the MCPTT provider of the GMS; or ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 24 2) a element of an MCPTT GKTP document as described in subclause 7.7.10 where the group ID is an MCPTT group ID owned by an MCPTT provider other than the MCPTT provider of GMS; shall perform the procedure in subclause 6.3.13.3.2.4 for each such MCPTT group ID and shall interwork information of received SIP NOTIFY requests in subclause 6.3.13.3.2.4 in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request. Upon sending a SIP NOTIFY request associated with a subscription created as result of the received initial SIP SUBSCRIBE request, if the CSK is received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, the GMS shall perform the confidentiality protection procedures and integrity protection procedures defined in 3GPP TS 24.379 [5] for MCPTT server. Upon reception of a SIP re-SUBSCRIBE request: a) with the Event header field set to xcap-diff; and b) with an application/resource-lists+xml MIME body; the GMS: a) if an <EncryptedData> XML tag is included in the application/resource-lists+xml MIME body of the received SIP re-SUBSCRIBE request and the CSK was received in an application/mikey MIME body of the initial SIP SUBSCRIBE request, shall decrypt the application/resource-lists+xml MIME body; and b) act as a notifier according to IETF RFC 5875 [13]. Additionally, if an XCAP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body of the SIP re-SUBSCRIBE request identifies: 1) a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is an MCPTT group ID owned by an MCPTT provider other than the MCPTT provider of the GMS; or 2) a element of an MCPTT GKTP document as described in subclause 7.7.10 where the group ID is an MCPTT group ID owned by an MCPTT provider other than the MCPTT provider of GMS; and for which there is no related subscription established according to the subclause 6.3.13.3.2.4, shall perform the procedure in subclause 6.3.13.3.2.4 for each such MCPTT group ID and shall interwork information of received SIP NOTIFY requests in subclause 6.3.13.3.2.4 in SIP NOTIFY requests associated with a subscription created as result of the received initial SIP SUBSCRIBE request." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 7.3.2] "The MCPTT server shall support obtaining service authorization specific information from the SIP REGISTER request sent from the MCPTT client and included in the body of a third-party SIP REGISTER request. NOTE 1: 3GPP TS 24.229 [4] defines how based on initial filter criteria the SIP REGISTER request sent from the UE is included in the body of the third-party SIP REGISTER request. Upon receiving a third party SIP REGISTER request with a message/sip MIME body containing the SIP REGISTER request sent from the MCPTT client containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt- access-token> element and an <mcptt-client-id> element within a message/sip MIME body of the SIP REGISTER request sent from the MCPTT client, the MCPTT server: 1) shall identify the IMS public user identity from the third-party SIP REGISTER request; 2) shall identify the MCPTT ID from the SIP REGISTER request sent from the MCPTT client and included in the message/sip MIME body of the third-party SIP REGISTER request by following the procedures in subclause 7.3.1A; 3) shall perform service authorization for the identified MCPTT ID as described in 3GPP TS 33.179 [46]; 4) if service authorization was successful, shall bind the MCPTT ID to the IMS public user identity; and NOTE 2: The MCPTT server will store the binding MCPTT ID, IMS public user identity and an identifier addressing the MCPTT server in an external database. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 25 5) if a Resource-Share header field with the value "supported" is contained in the "message/sip" MIME body of the third-party REGISTER request, shall bind the MCPTT ID to the identity of the MCPTT UE contained in the "+g.3gpp.registration-token" header field parameter in the Contact header field of the incoming third- party REGISTER request." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 7.3.3] "The MCPTT server shall support obtaining service authorization specific information from a SIP PUBLISH request for MCPTT server settings. Upon receiving a SIP PUBLISH request containing: 1) an Event header field set to the "poc-settings" value; 2) an application/poc-settings+xml MIME body; and 3) an application/vnd.3gpp.mcptt-info+xml MIME body containing an <mcptt-access-token> element and an <mcptt-client-id> element; the MCPTT server: 1) shall identify the IMS public user identity from the P-Asserted-Identity header field; 2) shall perform the procedures in subclause 7.3.1A; 3) if the procedures in subclause 7.3.1A were not successful shall send a SIP 403 (Forbidden) response towards the MCPTT server with the warning text set to: "140 unable to decrypt XML content " in a Warning header field as specified in subclause 4.4, and not continue with the rest of the steps in this subclause; 4) shall perform service authorization for the identified MCPTT ID as described in 3GPP TS 33.179 [46]; 5) if service authorization was successful: a) shall bind the MCPTT ID to the IMS public user identity; b) if a Resource-Share header field with the value "supported" was included in the "message/sip" MIME body of the third-party REGISTER request, shall bind the MCPTT ID to the identity of the MCPTT UE contained in the "+g.3gpp.registration-token" header field parameter in the Contact header field of the third-party REGISTER request that contained this IMS public user identity; NOTE 1: The MCPTT server will store the binding MCPTT ID, IMS public user identity and an identifier addressing the MCPTT server in an external database. c) shall download the MCPTT user profile from the MCPTT user database as defined in 3GPP TS 29.283 [73] if not already stored at the MCPTT server; d) if multiple MCPTT user profiles are stored at the MCPTT server or downloaded for the MCPTT user from the MCPTT user database, shall determine the pre-selected MCPTT user profile by identifying the MCPTT user profile (see the MCPTT user profile document in 3GPP TS 24.384 [50]) in the collection of MCPTT user profiles that contains a <Pre-selected-indication> element; and NOTE 2: If only one MCPTT user profile is stored at the MCPTT server or only one MCPTT user profile is downloaded from the MCPTT user database, then by default this MCPTT user profile is the pre-selected MCPTT user profile. e) if an <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCPTT user profile document with one or more <entry> elements containing an MCPTT group ID (see the MCPTT user profile document in 3GPP TS 24.384 [50]) for the served MCPTT ID, shall perform implicit affiliation as specified in subclause 9.2.2.2.15; 6) if service authorization was not successful, shall send a SIP 403 (Forbidden) response towards the MCPTT server with the warning text set to: "101 service authorisation failed" in a Warning header field as specified in subclause 4.4, and not continue with the rest of the steps in this subclause; 7) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [37] and if processing of the SIP request was not successful, do not continue with the rest of the steps; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 26 8) shall cache the received MCPTT service settings until the MCPTT service settings expiration timer expires; 9) shall send a SIP 200 (OK) response according 3GPP TS 24.229 [4]; and 10) shall use the Answer-Mode Indication setting in the <am-settings> element of the poc-settings event package as the current Answer-Mode Indication of the MCPTT client." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 7.3.4] "Upon receiving a SIP PUBLISH request containing: 1) an Event header field set to the "poc-settings" value; 2) an application/poc-settings+xml MIME body; and 3) an application/vnd.3gpp.mcptt-info+xml MIME body containing an <mcptt-request-uri> element and an <mcptt-client-id> element; The MCPTT server: 1) shall identify the IMS public user identity from the P-Asserted-Identity header field; 2) shall perform the procedures in subclause 7.3.1A; 3) if the procedures in subclause 7.3.1A were not successful, shall send a SIP 403 (Forbidden) response towards the MCPTT server with the warning text set to: "140 unable to decrypt XML content" in a Warning header field as specified in subclause 4.4, and not continue with the rest of the steps in this subclause; 4) shall verify that a binding between the IMS public user identity in the Request-URI and the MCPTT ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml exists at the MCPTT server; 5) if a binding exists between the IMS public user identity and the MCPTT ID in the request and the validity period of the binding has not expired: a) shall download the MCPTT user profile from the MCPTT user database as defined in 3GPP TS 29.283 [73] if not already stored at the MCPTT server; b) if multiple MCPTT user profiles are stored at the MCPTT server or downloaded for the MCPTT user from the MCPTT user database, shall determine the pre-selected MCPTT user profile by identifying the MCPTT user profile (see the MCPTT user profile document in 3GPP TS 24.384 [50]) in the collection of MCPTT user profiles that contains a <Pre-selected-indication> element; and NOTE: If only one MCPTT user profile is stored at the MCPTT server or only one MCPTT user profile is downloaded from the MCPTT user database, then by default this MCPTT user profile is the pre-selected MCPTT user profile. c) if an <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCPTT user profile document with one or more <entry> elements containing an MCPTT group ID (see the MCPTT user profile document in 3GPP TS 24.384 [50]) for the served MCPTT ID, shall perform implicit affiliation as specified in subclause 9.2.2.2.15. 6) if a binding does not exist between the IMS public user identity and the MCPTT ID in the request or the binding exists, but the validity period of the binding has expired, shall reject the SIP PUBLISH request with a SIP 404 (Not Found) response and not continue with any of the remaining steps; 7) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [37] and if processing of the SIP request was not successful, do not continue with the rest of the steps; 8) shall cache the received MCPTT service settings until the MCPTT service settings expiration timer expires; 9) shall send a SIP 200 (OK) response according 3GPP TS 24.229 [4]; and 10) shall use the Answer-Mode Indication setting in the <am-settings> element of the poc-settings event package as the current Answer-Mode Indication of the MCPTT client." ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 27 [ETSI TS 133 179 [30] (3GPP TS 33.179) clause 5.6.1] "For key management authorization, the KM client in the UE presents an access token to the KMS over HTTP. The KMS validates the access token and if successful, provides user specific key material back to the UE KM client based on the MCPTT ID of the user. This includes identity based key information used for media and signalling protection. For user service authorization, the MCPTT client in the UE presents an access token to the MCPTT server over SIP. The MCPTT server validates the access token and if successful, authorizes the user for full MCPTT services and sends an acknowledgement back to the MCPTT client. The MCPTT server then maps and maintains the IMPU to MCPTT ID association. The MCPTT ID to IMPU association shall only be known to the application layer. The SIP message used to convey the access token from the MCPTT client to the MCPTT server may be either a SIP REGISTER or SIP PUBLISH message. The UE can now perform configuration management authorization and download the user profile. Following the flow described in subclause 10.1.4.2 of 3GPP TS 23.179 [2] "MCPTT user obtains the user profile (UE initiated)", the Configuration Management (CM) client in the UE sends an access token in the user profile query to the Configuration Management server over HTTP. The CM server receives the request and validates the access token, and if valid, the CM server uses the MCPTT ID to obtain the user profile from the MCPTT user database. The CM server then sends the user profile back to the CM client over HTTP. Upon receiving the user's profile, the Group Management (GM) client in the UE can now perform group management authorization. The GM client obtains the user's group membership information from the user's profile, and following the flow shown in clause 10.1.5.2 of 3GPP TS 23.179 [2] "Retrieve group configurations at the group management client", the Group Management (GM) client in the UE sends an access token in the Get group configuration request to the host GM server of the group membership over HTTP. The GM server validates the access token, and if valid, completes the flow. As part of group management authorization, group key information is provided as per subclause 7.3.2 of the present document." [ETSI TS 133 179 [30] (3GPP TS 33.179) clause 7.2.3] "The procedure for the provision of identity-specific key material when the MCPTT proxy is supported between the KMS and the KMS client is described in figure 7.2.3-1. The procedure is the same whether the key management client in the MCPTT UE, MCPTT Server or group management server is making the request. Key Management Client Key Management Server 1. Request for key material 2. Provision of key material HTTP Proxy 0. Establishment of a secure connection Figure 7.2.3-1: Provisioning of key material via the HTTP proxy The procedure in figure 7.2.3-1 is now described step-by-step. 0) The key management client establishes a connection to the MCPTT KMS. As with other elements in the Common Services Core, the connection routed via, and secured by, the HTTP Proxy. The message flow below is within this secure connection. NOTE: Additionally, the connection between the MCPTT KMS and the HTTP Proxy is secured according to clause 8. 1) The key management client makes a request for user key material from the MCPTT KMS. The request contains details of the identity (e.g. the MCPTT ID) requested for key management, and the time for which the key material is required. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 28 2) The KMS provides a response containing key material. The response includes the type of key material, the period of use for the material and any domain-specific parameters required for its use. For public safety use, the key material itself shall be wrapped using a 256-bit transport key (TrK). The TrK is distributed via an out- of-band mechanism along with a 32-bit identifier, TrK-ID. The procedure for the provisioning of identity-specific key material when the MCPTT proxy is not used between the KMS and the KMS client is as described in Figure 7.2.3-2. Key Management Client Key Management Server 1. Request for key material 2. Provision of key material 0. Establishment of a secure connection Figure 7.2.3-2: Provisioning of key material without a proxy The procedure in Figure 7.2.3-2 is now described step-by-step: 0) The key management client establishes a direct HTTPS connection to the MCPTT KMS. The following message flow is within this secure connection. 1) The key management client makes a request for user key material from the MCPTT KMS. The request contains details of the identity requested for key management, and the time at which the key material is required. 2) The KMS provides a response containing key material. The response includes the type of key material, the period of use for the material and any domain-specific parameters required for its use. Optionally, the key material itself may also be wrapped using a 256-bit transport key (TrK), distributed via an out-of-band mechanism along with a 32-bit identifier (TrK-ID). As a result of this procedure, the key management client has securely obtained key material for use within the MCPTT system." [ETSI TS 133 179 [30] (3GPP TS 33.179) clause D.1] "All KMS communications are made via HTTPS. The MCPTT key management client is provisioned via XML content in the KMS's response. The XML content is designed to be extendable to allow KMS/client providers to add further information in the XML. Where the interface is extended, a different XML namespace should be used (so that may be ignored by non-compatible clients). It is assumed that transmissions between the KMS and the key management client are secure and that the KMS has authenticated the identity of the key management client. Additionally, to allow the transmission of key material securely between a secure element within the KMS and a secure element within the key management client, a security extension is defined which allows messages to be signed and key material to be encrypted using a shared Transport Key (TrK)." |
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 136 508 [23] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCPTT operation in the MCPTT configuration document). IUT: - IUT (MCPTT Server) - The IUT (MCPTT Server) consists of all sub-systems of the Common Services Core, including the Group Management Server, the Configuration Management Server, the Key Management Server, the Identity Management Server, the HTTP Server, and the SIP AS. The IUT (MCPTT Server) also consists of all sub-systems of the MCPTT Server, including the Media Distribution Function, the MCPTT User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Floor Control Server. - The IUT (MCPTT Server) is the acting Participating Server and Controlling Server Preamble: - The IUT (MCPTT Server) is connected to PLMN1. - The IUT (MCPTT Server) is connected to the SS-UE1 (MCPTT client) as defined in Annex A, Figure A.4.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) including the initial UE configuration document? <-- HTTP 200 (OK) 1 P 0C The SS-UE1 (MCPTT client) establishes a secure TLS tunnel as specified by ETSI TS 133 310 [6] (3GPP TS 33.310) to the authorisation endpoint of the IdM server as specified in ETSI TS 133 180 [31] (3GPP TS 33.180), using the configured URL of the authorisation endpoint of the IdM server as specified in the "<x>/OnNetwork/AppServerInfo/IDMSAuthEndp oint" leaf node, Table 5.5.8.1-1, ETSI TS 136 579-1 [1] (3GPP TS 36.579-1). - - - - 1 The SS-UE1 (MCPTT client) sends an OpenID Connect Authentication Request using HTTP POST --> HTTP POST (Authorization) - - 2 Check: Does the IUT (MCPTT Server) respond by sending an HTTP 200 (OK) including the HTML form requesting username and password? <-- HTTP 200 (OK) 1 P 3 The SS-UE1 (MCPTT client) sends an HTTP POST Request message to the SS containing user name and password --> HTTP POST - - 4 Check: Does the IUT (MCPTT Server) send an HTTP 302 (Found) as the OpenID Connect Authentication Response? <-- HTTP 302 (Found) 1 P ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 30 St Procedure Message Sequence TP Verdict U - S Message 5 The SS-UE1 (MCPTT client) establishes a secure TLS tunnel as specified by ETSI TS 133 310 [6] (3GPP TS 33.310) to the token endpoint of the IdM server as specified in ETSI TS 133 180 [31] (3GPP TS 33.180), using the configured URL of the token endpoint of the IdM server as specified in the "/<x>/OnNetwork/AppServerInfo/IDMSTokenEn dpoint" leaf node, Table 5.5.8.1-1, ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) - - - - 6 The SS-UE1 (MCPTT client) sends an HTTP POST Request message to the IUT (MCPTT Server) over the TLS connection established to the IdM token endpoint (OIDC Token Request message) passing the authorization code sent in step 4. --> HTTP POST - - 7 Check: Does the IUT (MCPTT Server) send an HTTP 200 (OK) providing id_token, access_token and refresh token? <-- HTTP 200 (OK) 1 P 7A The SS-UE1 (MCPTT client) establishes a secure TLS tunnel as specified by ETSI TS 133 310 [6] (3GPP TS 33.310) to the HTTP Proxy as specified in ETSI TS 133 180 [31] (3GPP TS 33.180), using the configured URL of the HTTP Proxy as specified in the "/<x>/OnNetwork/AppServerInfo/HTTPproxy" leaf node, Table 5.5.8.1-1, ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) - - - - 8 The SS-UE1 (MCPTT client) sends an HTTP POST message presenting an access token sent in step 7 for Key Management Initialisation. --> HTTP POST - - 9 Check: Does the IUT (MCPTT Server) respond by sending identity-specific key information? <-- HTTP 200 (OK) 2 P 10 The SS-UE1 (MCPTT client) sends an HTTP POST message presenting an access token for Key Material Request --> HTTP POST - - 11 Check: Does the IUT (MCPTT Server) respond by sending identity-specific key information? <-- HTTP 200 (OK) 2 P 12 The SS-UE1 (MCPTT client) sends a SIP REGISTER request for service authorisation --> SIP REGISTER - - 13 Check: Does the IUT (MCPTT Server) respond by sending an SIP 200 (OK) message? <-- SIP 200 (OK) 3 P 14 The SS-UE1 (MCPTT client) sends a SIP SUBSCRIBE - subscription to multiple documents simultaneously - containing the access token and a resource list mime body containing a list of the following documents: MCPTT UE Configuration document, MCPTT User Profile Configuration Document, and the MCPTT Service configuration document. The base URI of each list entry is set to the CMS XCAP-ROOT-URI --> SIP SUBSCRIBE - - 15 Check: Does the IUT (MCPTT Server) respond by sending an SIP 200 (OK) message? <-- SIP 200 (OK) 4 P 16 Check: Does the IUT (MCPTT Server) send a SIP NOTIFY message containing the XCAP- URI of the documents? <-- SIP NOTIFY 4 P 17 The SS-UE1 (MCPTT client) responds with a SIP 200 (OK) message --> SIP 200 (OK) - - 18 The SS-UE1 (MCPTT client) sends an HTTP GET Request message that contains the access token and the XCAP-URI of the MCPTT UE Configuration document --> HTTP GET - - ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 31 St Procedure Message Sequence TP Verdict U - S Message 19 Check: Does the IUT (MCPTT Server) send the HTTP 200 (OK) message including the MCPTT UE Configuration Document? <-- HTTP 200 (OK) 4 P 20 The SS-UE1 (MCPTT client) sends an HTTP GET Request message that contains the access token and the XCAP-URI of the MCPTT User Profile Configuration Document --> HTTP GET - - 21 Check: Does the IUT (MCPTT Server) send the HTTP 200 (OK) message including the MCPTT User Profile Configuration Document? <-- HTTP 200 (OK) 4 P 22 The SS-UE1 (MCPTT client) sends an HTTP GET Request message that contains the access token and the XCAP-URI of the MCPTT Service Configuration Document --> HTTP GET - - 23 Check: Does the IUT (MCPTT Server) send the HTTP 200 (OK) message including the MCPTT Service Configuration Document? <-- HTTP 200 (OK) 4 P 24 The SS-UE1 (MCPTT client) sends a SIP SUBSCRIBE containing the access token and a resource list mime body and a list of the Groups to be obtained. The base URI of each list entry is set to the GMS XCAP-ROOT-URI, and the MCPTT group ID identifies a group document --> SIP SUBSCRIBE - - 25 Check: Does the IUT (MCPTT Server) respond with a HTTP 200 (OK) message <-- SIP 200 (OK) 5 P 26 Check: Does the IUT (MCPTT Server) send a SIP NOTIFY message to the UE that contains the XCAP-URI of the Group documents? <-- SIP NOTIFY 5 P 27 The SS-UE1 (MCPTT client) sends a SIP 200 (OK) message --> SIP 200 (OK) - - 28 The SS-UE1 (MCPTT client) sends an HTTP GET Request message that contains the access token and the XCAP-URI of the Group Configuration document --> HTTP GET - - 29 Check: Does the IUT (MCPTT Server) send an HTTP 200 (OK) message including the Group Document 'MCPTT UE Configuration document'? <-- HTTP 200 (OK) 5 P 29A Check: Does the IUT (MCPTT Server) send a SIP NOTIFY message to the UE that contains the group key transport payloads (GKTP) document. <-- SIP NOTIFY 5 P 29B The SS-UE1 (MCPTT client) sends a SIP 200 (OK) message --> SIP 200 (OK) - - 30 The SS-UE1 (MCPTT client) sends a SIP PUBLISH request for update of PoC-settings. NOTE: The PoC-settings document contains the user profile index of the selected user profile. --> SIP PUBLISH - - 31 Check: Does the IUT (MCPTT Server) send a SIP 200 (OK)? <-- SIP 200 (OK) 6 P 32-33 Void -- - - - |
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.1 (2026-01) 32 Table 5.1.3.3-3: HTTP POST (Step 6, 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 TOKEN Table 5.1.3.3-4: HTTP POST (Step 8, 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 KMSINIT. Table 5.1.3.3-5: HTTP POST (Step 10, 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 KMSKEY. Table 5.1.3.3-5A: HTTP 200 (OK) (Step 0B, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition UEINITIALCONFIG Table 5.1.3.3-6: HTTP 200 (OK) (Step 2, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1 Information Element Value/remark Comment Reference Condition Content-Type media-type "text/html" IETF RFC 2854 [33] Message-body HTML form <!DOCTYPE html> <html> <body> <form action="/idms/userauth" method="post"> Username: <input type="text" name="user"><br> Password: <input type="password" name="password"><button type="submit">Login</button> </form> </body> </html> "/idms/userauth" given by tsc_MCX_IdMS_useraut h_UriPath is the URI to be used by the UE as request URI in the HTTP POST request for user authentication HTML 4.01 Specification [34] Table 5.1.3.3-7: HTTP 200 (OK) (Step 7, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition TOKEN Table 5.1.3.3-8: HTTP 200 (OK) (Step 9, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition KMSINIT. Table 5.1.3.3-9: HTTP 200 (OK) (Step 11, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition KMSKEY. Table 5.1.3.3-10: HTTP 200 (OK) (Step 19, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition UECONFIG. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 33 Table 5.1.3.3-11: HTTP 200 (OK) (Step 21, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition UEUSERPROF. Table 5.1.3.3-12: HTTP 200 (OK) (Step 23, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition UESERVCONFIG. Table 5.1.3.3-13: HTTP 200 (OK) (Step 29, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition GROUPCONFIG. Table 5.1.3.3-14: HTTP 302 (Found) (Step 4, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.8-1, condition AUTH. Table 5.1.3.3-14A: HTTP GET (Step 0A, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.2-1, condition UEINITIALCONFIG Table 5.1.3.3-15: HTTP GET (Step 18, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.2-1, condition UECONFIG. Table 5.1.3.3-16: HTTP GET (Step 20, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.2-1, condition UEUSERPROF. Table 5.1.3.3-17: HTTP GET (Step 22, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.2-1, condition UESERVCONFIG. Table 5.1.3.3-18: HTTP GET (Step 28, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.2-1, condition GROUPCONFIG Table 5.1.3.3-19: SIP REGISTER (Step 12, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.13-1, condition SIP_REGISTER_INITIAL, CONFIG Information Element Value/remark Comment Reference Condition Request-Line Request-URI tsc_MCPTT_PublicServiceId_B SIP URI of the home domain name Table 5.1.3.3-20: SIP SUBSCRIBE (Step 14, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.14-1, condition CONFIG ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 34 Table 5.1.3.3-20A: SIP SUBSCRIBE (Step 24, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.14-1, condition GROUPCONFIG Information Element Value/remark Comment Reference Condition Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 5.1.3.3-20B Table 5.1.3.3-20B: Resource-lists in SIP SUBSCRIBE (Table 5.1.3.3-20A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-1, condition GROUPCONFIG Table 5.1.3.3-21: SIP NOTIFY (Step 16, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, condition CONFIG Information Element Value/remark Comment Reference Condition Contact addr-spec user-info and host tsc_MCPTT_PublicServi ceId_B Table 5.1.3.3-21A: SIP NOTIFY (Step 26, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, condition GROUPCONFIG Information Element Value/remark Comment Reference Condition Contact addr-spec user-info and host tsc_MCPTT_PublicServi ceId_B Table 5.1.3.3-21B: SIP NOTIFY (Step 29A, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, condition GROUPCONFIG Information Element Value/remark Comment Reference Condition Contact addr-spec user-info and host tsc_MCPTT_PublicServi ceId_B Message-body xcap-diff document xcap-diff document as described in Table 5.1.3.3-21C Table 5.1.3.3-21C: Xcap-Diff Document (Table 5.1.3.3-21B) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.12-2, condition GROUPKEY Table 5.1.3.3-22: SIP PUBLISH (Step 30, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.11-1, condition POC-SETTINGS-EVENT Information Element Value/remark Comment Reference Condition Request-Line Request-URI tsc_MCPTT_PublicServic eId_B The public service identity identifying the originating participating MCPTT function serving the MCPTT user ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 35 Table 5.1.3.3-23: Void Table 5.1.3.3-24: SIP 200 (OK) (Steps 13, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 condition REGISTER-RSP Information Element Value/remark Comment Reference Condition Table 5.1.3.3-25: SIP 200 (OK) (Steps 15, 25, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 condition SUBSCRIBE-RSP Information Element Value/remark Comment Reference Condition Contact addr-spec user-info and host tsc_MCPTT_PublicServi ceId_B Table 5.1.3.3-26: SIP 200 (OK) (Step 31, Table 5.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 condition PUBLISH-RSP Information Element Value/remark Comment Reference Condition 5.2 MCPTT Server - MCPTT Client / Configuration / Group Creation / Group Regroup Creation / Group Regroup Teardown |
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 Server) having establish terminated group } ensure that { when { the SS-UE1 (MCPTT Client) initiates creation of the terminated temporary group by sending a HTTP POST request } then { IUT (MCPTT Server) responds with a HTTP 200 (OK) containing the GMOP group-regroup- creation-response } } (3) with { IUT (MCPTT Server) having establish a temporary group } ensure that { when { the UE (MCPTT client) initiates tear down of the temporary group by sending a HTTP DELETE request } then { IUT (MCPTT Server) responds to the UE (MCPTT Client) with HTTP 200 (OK) message } } ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 36 |
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 24.481) clause 6.3.2.3] "Upon reception of an HTTP PUT request where the Request-URI of the HTTP PUT request identifies an XML document of the application usage specified in subclause 7.2 then the GMS: a) shall determine the identity of the sender of the received HTTP PUT request as specified in subclause 6.2.5; b) if the identity of the sender of the received HTTP PUT request is not authorized to initiate group creation, shall respond with a HTTP 403 (Forbidden) response to the HTTP PUT request and shall not continue with rest of the steps; c) if value of the "uri" attribute of the <list-service> element of the <group> element of the XML document specified in subclause 7.2.1 of the received HTTP PUT request does not conform to local policy, shall respond with an HTTP 409 (Conflict) response to the HTTP PUT request. The <uniqueness-failure> error element shall identify the error condition. The GMS shall include at least one <alt-value> element in the <uniqueness- failure> error element, whereby each <alt-value> element contains an MCS Group ID acceptable for the GMS. The GMS shall not continue with rest of the steps; and d) shall support receiving an XML document of the application usage specified in subclause 7.2.1 according to procedures specified in IETF RFC 4825 [22] "PUT Handling" where the Request-URI of the HTTP PUT request identifies an XML document of the application usage specified in subclause 7.2." [ETSI TS 124 481 [27] (3GPP TS 24.481) clause 6.3.14.3.1] "Upon reception of an HTTP POST request: a) with a Request-URI with an XCAP URI identifying a non-existing group document; and b) with an application/vnd.3gpp.GMOP+xml MIME body containing a GMOP document requesting group regroup creation specified in subclause 7.3.4.3; then the GMS: a) shall determine the identity of the sender of the received HTTP POST request as specified in subclause 6.2.5; b) if the identity of the sender of the received HTTP POST request is not authorized to initiate temporary MCS group formation, shall respond with HTTP 403 (Forbidden) response to the HTTP POST request and shall not continue with rest of the steps; c) if value of the "uri" attribute of the <list-service> element of the <group> element of the GMOP document requesting group regroup creation specified in subclause 7.3.4.3 of the received HTTP POST request does not conform to local policy, shall respond with an HTTP 409 (Conflict) response to the HTTP POST request. The <uniqueness-failure> error element shall identify the error condition. The GMS shall include at least one <alt-value> element in the <uniqueness-failure> error element, whereby each <alt-value> element contains a MCS Group ID acceptable for the GMS. The GMS shall not continue with rest of the steps; and d) for each MCS group ID of an MCS group to be combined indicated in content of a <constituent-MCPTT- group-ID> element of the <constituent-MCPTT-group-IDs> element of the <on-network-temporary> element of the group document of the <group> element of the GMOP document requesting group regroup creation specified in subclause 7.3.4.3 of the received HTTP POST request: 1) shall send a HTTP POST request according to procedures specified in IETF RFC 2616 [21] and subclause 6.2.5. In the HTTP POST request, the GMS: … ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 37 Upon reception of a HTTP 3xx, 4xx, or 5xx responses to a sent HTTP POST request or upon timeout, the GMS shall send a HTTP 403 (Forbidden) response to the received HTTP request and shall not continue with rest of the steps. … Upon reception of HTTP 2xx responses to all sent HTTP POST requests, the GMS shall create the group document of the temporary MCS group at the location specified by the Request-URI of the received HTTP POST request and shall send an HTTP 2xx response to the received HTTP request. In the HTTP 2xx response, the GMS shall include an application/vnd.3gpp.GMOP+xml MIME body containing a GMOP document with group regroup creation response specified in subclause 7.3.4.6 with a <temporary-group-document-ETag> element set to the current value of the entity tag for the created group document of the temporary MCS group." [ETSI TS 124 481 [27] (3GPP TS 24.481) clause 6.3.15.3.1] "Upon reception of an HTTP DELETE request with Request-URI with an XCAP URI identifying a group document of a temporary MCS group, the GMS: a) for each constituent MCS group indicated in the group document indicated by Request-URI: 1) shall send an HTTP DELETE request. In the HTTP DELETE request, the GMS: … Upon reception of an HTTP response to all sent HTTP DELETE requests, the GMS shall remove the group document of the temporary MCS group and shall send an HTTP 2xx response to the received HTTP request." [ETSI TS 133 180 [31] (3GPP TS 33.180), clause 7.3.2] "The group creation procedure is described in clause 10.2.3 of 3GPP TS 23.280 [36] and applies to the MCPTT scenario of normal group creation by an MC administrator and user regrouping operations by an authorized user/dispatcher. To establish the security context for the group, the GMS follows the procedures in clause 5.7 to create a new GMK and GMK-ID. The encapsulated GMK and GUK-ID is sent to group members by the GMS within a notification message (Step 4 in clause 10.2.3 of 3GPP TS 23.280 [36]). The procedure is equivalent to that described in clause 5.7 of this specification." [ETSI TS 133 180 [31] (3GPP TS 33.180), clause 7.3.3.2] "Group Regroup procedures for the MC system are described in clause 10.2.4.1 of 3GPP TS 23.280 [36]. To create the security context for the temporary group, the GMS follows the procedures in clause 5.7, creating a new GMK and GMK-ID for the temporary group. An encapsulated GMK and GUK-ID is sent to the temporary group members by the GMS within a notification message (Step 5 in clause 10.2.4.1 of 3GPP TS 23.280 [36]). The procedure is equivalent to that described in clause 5.7." |
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. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCPTT operation in the MCPTT configuration document). ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 38 IUT: - IUT (MCPTT Server) - The IUT (MCPTT Server) consists of all sub-systems of the Common Services Core, including the Group Management Server, the Configuration Management Server, the Key Management Server, the Identity Management Server, the HTTP Server, and the SIP AS. The IUT (MCPTT Server) also consists of all sub-systems of the MCPTT Server, including the Media Distribution Function, the MCPTT User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Floor Control Server. - The IUT (MCPTT Server) is the acting Group Management Server. Preamble: - The IUT (MCPTT Server) is connected to PLMN1 - The IUT (MCPTT Server) is connected to the SS-UE1 (MCPTT client) as defined in Annex A, Figure A.4.1. - The SS-UE1 (MCPTT client) performs the Procedure for MCPTT Authorization, Configuration and Key Generation as specified in clause 5.1. - The SS-UE1 (MCPTT client) is member of group A. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.