hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.5.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 11.1.5.2.1, 11.1.5.2.2, 11.1.5.2.3, 11.1.5.3.1, 11.1.5.3.1. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core specification they have been copied from. Unless otherwise stated these are Rel- 14 requirements. [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.5.2.1] "… The MCPTT client: 1) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 247 2) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6]; 3) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4]; 4) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; 5) shall include in an application/resource-lists+xml MIME body, the MCPTT ID of the targeted MCPTT user, according to rules and procedures of IETF RFC 5366 [20]; 6) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <anyExt> element containing: a) if the request is a private call call-back request: i) the <request-type> set to a value of "private-call-call-back-request>; ii) the <urgency-ind> set to a value of "low", "normal" or "high" to indicate the urgency of the call- back request; and iii) the <time-of-request> set to the date and time of the request using the format specified in clause F.1.3; and b) if the request is a private call call-back cancel request, the <request-type> set to a value of "private- call-call-back-cancel-request"; … 8) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4]. …" [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.5.2.2] "… The MCPTT client: 1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]: 2) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request; 3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6] in the SIP MESSAGE request 4) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4]; 5) shall set the Request-URI in the SIP MESSAGE request to the public service identity identifying the participating MCPTT function serving the MCPTT user; 6) shall include in an application/resource-lists+xml MIME body, the MCPTT ID contained in the <mcptt- calling-user-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request; 7) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <anyExt> element containing: a) if the received SIP MESSAGE was a "SIP MESSAGE request for private call call-back request for terminating MCPTT client", the <response-type> element set to a value of "private-call-call-back- response"; and ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 248 b) if the received SIP MESSAGE was a "SIP MESSAGE request for private call call-back cancel request for terminating MCPTT client", the <response-type> element set to a value of "private-call-call-back- cancel-response"; and 8) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4]. …" [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.5.2.3] "When the target MCPTT user wants to make a private call call-back, the target MCPTT client shall initiate a private call in manual commencement mode towards the requesting MCPTT client using the MCPTT ID of the requesting MCPTT user as found in the "PCCB target client entry" stored on the UE, by following the procedures in: 1) clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 for private call with floor control; or 2) clause 11.1.2.2 for private call without floor control; …" [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.5.3.1] "Upon receiving a "SIP MESSAGE request for private call call-back for originating participating MCPTT function" the participating MCPTT function: … 2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request; NOTE: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 5) shall determine the public service identity of the controlling MCPTT function for the private call call-back service for the MCPTT user; 6) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]; 7) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function associated with the private call call-back service for the MCPTT user; 8) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request; 9) shall set the <mcptt-calling-user-id> element of the <mcpttinfo> element containing the <mcptt-Params> element to the MCPTT ID determined in step 2) above; 10) shall copy the contents of the application/resource-lists MIME body in the received SIP MESSAGE request into an application/resource-lists MIME body in the outgoing SIP MESSAGE request; 11) shall set the P-Asserted-Identity in the outgoing SIP MESSAGE request to the public user identity in the P- Asserted-Identity header field contained in the received SIP MESSAGE request; 12) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6]; 13) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6]; 14) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and 15) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4]. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 249 Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 13), the participating MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the MCPTT client." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.5.3.1] "Upon receiving a "SIP MESSAGE request for private call call-back for terminating participating MCPTT function" the participating MCPTT function: … 2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt- info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity; … 4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11; 5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; and 6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall forward the SIP 2xx response to the controlling MCPTT function." |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.5.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.5.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) and SS-UE2 (MCPTT Client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client), the SS-UE2 (MCPTT client) and the MCPTT Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined 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) and the SS-UE2 (MCPTT client) as defined in Annex A, Figure A.4.1. - The SS-UE1 (MCPTT client) and the SS-UE2 (MCPTT client) perform the Procedure for MCPTT Authorization, Configuration and Key Generation as specified in clause 5.1. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 250 |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.5.3.2 Test procedure sequence | Table 6.2.7.3.2-1: Main behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE2 (MCPTT client) sends a private call call-back request to SS-UE1 (MCPTT client) - - - - 2 Check: Does the MCPTT Server correctly perform procedure 'MCX E2E SIP MESSAGE' as described in Annex A, Table A.2.10.3-1 to request the private call call-back for targeted user A from user B? - - 1 P 3 Check: Does the MCPTT Server correctly perform procedure 'MCX E2E SIP MESSAGE' as described in Annex A, Table A.2.10.3-1 to respond the private call call-back request to user B? (see note) - - 1 P 4 The SS-UE2 (MCPTT client) cancels the private call call-back request sent to SS-UE1 (MCPTT client) - - - 5 Check: Does the MCPTT Server correctly perform procedure 'MCX E2E SIP MESSAGE' as described in Annex A, Table A.2.10.3-1 to cancel the private call call-back for targeted user A from user B? - - 2 P 6 Check: Does the MCPTT Server correctly perform procedure 'MCX E2E SIP MESSAGE' as described in Annex A, Table A.2.10.3-1 to respond the private call call-back cancellation request to user B? (see note) - - 2 P 7 The SS-UE2 (MCPTT client) sends a private call call-back request to SS-UE1 (MCPTT client) - - - - 8 Check: Does the MCPTT Server correctly perform procedure 'MCX E2E SIP MESSAGE' as described in Annex A, Table A.2.10.3-1 to request the private call call-back for targeted user A from user B? - - 1 P 9 Check: Does the MCPTT Server correctly perform procedure 'MCX E2E SIP MESSAGE' as described in Annex A, Table A.2.10.3-1 to respond the private call call-back request to user B? (see note) - - 1 P 10 The SS-UE1 (MCPTT client) requests a private call to SS-UE2 (MCPTT client) with manual commencement mode and implicit floor request - - - - 11 Check: Does the MCPTT server correctly perform procedure 'MCPTT E2E private call establishment, manual commencement' as described in Annex A, Table A.3.3.3-1 to establish a private call with manual commencement mode and implicit floor control according to option b.ii of note in Annex A, Table A.3.3.3-1, from user A to user B? - - 3 P 12 The SS-UE1 (MCPTT client) releases the call - - - - 13 Check: Does the MCPTT server correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 4 P NOTE: During this procedure the SS-UE1 performs the role of SS-UE2 and viceversa. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 251 |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.5.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.2.7.3.3-1: SIP MESSAGE from the SS-UE2 (Steps 2 and 8, Table 6.2.7.3.2-1; Step 1, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 with condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info ETSI TS 124 379 [4] (3GPP TS 24.379) clause F.1 MIME-part-body MCPTT-Info as described in Table 6.2.7.3.3-2 MIME body part Resource-lists MIME-part-body Resource-lists as described in Table 6.2.7.3.3-3 Table 6.2.7.3.3-2: MCPTT-Info in SIP MESSAGE (Table 6.2.7.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params anyExt request-type "private-call-call-back- request" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.1 urgency-ind "normal" Arbitrarily choosen ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.1 time-of-request "YYYY-MM- DDThh:mm:ss" set to the date and time of the request ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.1 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. Table 6.2.7.3.3-3: Resource lists in SIP MESSAGE (Table 6.2.7.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-1 Information Element Value/remark Comment Reference Condition resource-lists list entry[1] uri attribute px_MCPTT_ID_User_A The targeted MCPTT user ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.1 Table 6.2.7.3.3-4: SIP MESSAGE from the MCPTT-Server to SS-UE1 (Steps 2 and 8, Table 6.2.7.3.2-1; Step 3, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with condition MCPTT and ACCEPT- CONTACT-WITH-MEDIA-FEATURE-TAG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.2.7.3.3-5 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 252 Table 6.2.7.3.3-5: MCPTT-Info in SIP MESSAGE (Table 6.2.7.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.4 mcptt-calling-user-id Encrypted (see note) <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_B anyExt request-type "private-call-call-back- request" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 12.1.5.2.1 urgency-ind "normal" Arbitrarily choosen ETSI TS 124 379 [4] (3GPP TS 24.379) clause 12.1.5.2.1 time-of-request "YYYY-MM-DDThh:mm:ss" set to the date and time of the request ETSI TS 124 379 [4] (3GPP TS 24.379) clause 12.1.5.2.1 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. Table 6.2.7.3.3-6: SIP MESSAGE from the SS-UE1 (Steps 3 and 9, Table 6.2.7.3.2-1; Step 1, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 with condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info ETSI TS 124 379 [4] (3GPP TS 24.379) clause F.1 MIME-part-body MCPTT-Info as described in Table 6.2.7.3.3-7 MIME body part Resource-lists MIME-part-body Resource-lists as described in Table 6.2.7.3.3-8 Table 6.2.7.3.3-7: MCPTT-Info in SIP MESSAGE (Table 6.2.7.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params anyExt response-type "private-call-call-back- response" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.2 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. Table 6.2.7.3.3-8: Resource lists in SIP MESSAGE (Table 6.2.7.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-1 Information Element Value/remark Comment Reference Condition resource-lists list entry[1] uri attribute px_MCPTT_ID_User_B The targeted MCPTT user ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.2 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 253 Table 6.2.7.3.3-9: SIP MESSAGE from the MCPTT-Server to SS-UE2 (Steps 3 and 9, Table 6.2.7.3.2-1; Step 3, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with condition MCPTT and ACCEPT- CONTACT-WITH-MEDIA-FEATURE-TAG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.2.7.3.3-10 Table 6.2.7.3.3-10: MCPTT-Info in SIP MESSAGE (Table 6.2.7.3.3-9) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_B ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.4 mcptt-calling-user-id Encrypted (see note) <mcptt- calling-user-id> with mcpttURI set to px_MCPTT_ID_User_A anyExt response-type "private-call-call-back- response" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.2 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. Table 6.2.7.3.3-11: SIP MESSAGE from the SS-UE2 (Step 5, Table 6.2.7.3.2-1; Step 1, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 with condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info ETSI TS 124 379 [4] (3GPP TS 24.379) clause F.1 MIME-part-body MCPTT-Info as described in Table 6.2.7.3.3-12 MIME body part Resource-lists MIME-part-body Resource-lists as described in Table 6.2.7.3.3-13 Table 6.2.7.3.3-12: MCPTT-Info in SIP MESSAGE (Table 6.2.7.3.3-11) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params anyExt request-type "private-call-call-back- cancel-request" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.1 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 254 Table 6.2.7.3.3-13: Resource lists in SIP MESSAGE (Table 6.2.7.3.3-11) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-1 Information Element Value/remark Comment Reference Condition resource-lists list entry[1] uri attribute px_MCPTT_ID_User_A The targeted MCPTT user ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.1 Table 6.2.7.3.3-14: SIP MESSAGE from the MCPTT-Server to SS-UE1 (Step 5, Table 6.2.7.3.2-1; Step 3, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with condition MCPTT and ACCEPT- CONTACT-WITH-MEDIA-FEATURE-TAG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.2.7.3.3-15 Table 6.2.7.3.3-15: MCPTT-Info in SIP MESSAGE (Table 6.2.7.3.3-14) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.4 mcptt-calling-user-id Encrypted (see note) <mcptt- calling-user-id> with mcpttURI set to px_MCPTT_ID_User_B anyExt request-type "private-call-call-back-cancel- request" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 12.1.5.2.1 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. Table 6.2.7.3.3-16: SIP MESSAGE from the SS-UE1 (Steps 6, Table 6.2.7.3.2-1; Step 1, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 with condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info ETSI TS 124 379 [4] (3GPP TS 24.379) clause F.1 MIME-part-body MCPTT-Info as described in Table 6.2.7.3.3-17 MIME body part Resource-lists MIME-part-body Resource-lists as described in Table 6.2.7.3.3-18 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 255 Table 6.2.7.3.3-17: MCPTT-Info in SIP MESSAGE (Table 6.2.7.3.3-16) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params anyExt response-type "private-call-call-back- cancel-response" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.2 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. Table 6.2.7.3.3-18: Resource lists in SIP MESSAGE (Table 6.2.7.3.3-16) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-1 Information Element Value/remark Comment Reference Condition resource-lists list entry[1] uri attribute px_MCPTT_ID_User_B The targeted MCPTT user ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.2 Table 6.2.7.3.3-19: SIP MESSAGE from the MCPTT-Server to SS-UE2 (Step 6, Table 6.2.7.3.2-1; Step 3, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with condition MCPTT and ACCEPT- CONTACT-WITH-MEDIA-FEATURE-TAG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.2.7.3.3-20 Table 6.2.7.3.3-20: MCPTT-Info in SIP MESSAGE (Table 6.2.7.3.3-19) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_B ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.4 mcptt-calling-user-id Encrypted (see note) <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_A anyExt response-type "private-call-call-back- cancel-response" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.5.2.2 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 256 6.2.6 MCPTT Server - MCPTT Client / Ambient listening call / On-demand / Remotely initiated Ambient listening call / Remotely initiated ambient listening call release |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.6.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCPTT Client) initiates establishment of a private call with automatic commencement mode and without floor control } then { IUT (MCPTT Server) accepts the call from the initiator and establishes the call with SS- UE2 (MCPTT Client) } } (2) with { IUT (MCPTT Server) having established a private call with automatic commencement mode and without floor control } ensure that { when { the SS-UE1 (MCPTT client) establishes a private call with automatic commencement mode } then { IUT (MCPTT Server) enforces floor granted to the SS-UE2 (MCPTT client) and floor taken with the Permission to Request the Floor field to SS-UE1 (MCPTT client) } } (3) with { IUT (MCPTT Server) having established a private call with automatic commencement mode and without floor control } ensure that { when { the SS-UE1 (MCPTT client) ends the private call } then { IUT (MCPTT Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the other participants } |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.6.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 11.1.6.2.1.1, 11.1.6.3.1.1, 11.1.6.3.1.2, 11.1.6.3.2.1, 11.1.6.3.2.2, 11.1.6.4.1, 11.1.6.4.2, ETSI TS 124 380 [5] (3GPP TS 24.380) clauses 6.3.4.2.2, 6.3.4.4.2, 6.3.5.2.2, 6.3.5.4.4. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core specification they have been copied from. Unless otherwise stated these are Rel-14 requirements. [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.6.2.1.1] "… The MCPTT client: 1) shall set the Request-URI of the SIP INVITE request to a public service identity of the participating MCPTT function serving the MCPTT user; 2) may include a P-Preferred-Identity header field in the SIP INVITE request containing a public user identity as specified in 3GPP TS 24.229 [4]; 3) shall include the g.3gpp.mcptt media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" in the Contact header field of the SIP INVITE request according to IETF RFC 3840 [16]; 4) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6]; 5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP INVITE request; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 257 6) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref contain with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6]; 7) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "ambient-listening"; 8) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <ambient-listening-type> element set to a value of: … b) "remote-init", if the MCPTT user has requested a remotely initiated ambient listening call; 9) shall insert in the SIP INVITE request a MIME resource-lists body with the MCPTT ID of the targeted MCPTT user, according to rules and procedures of IETF RFC 5366 [20]; NOTE 1: the targeted MCPTT user is the listened-to MCPTT user in the case of a remotely initiated ambient listening call or the listening MCPTT user in the case of a locally initiated listening call. 10) if an end-to-end security context needs to be established then: a) if necessary, shall instruct the key management client to request keying material from the key management server as described in 3GPP TS 33.180 [78]; b) shall use the keying material to generate a PCK as described in 3GPP TS 33.180 [78]; c) shall use the PCK to generate a PCK-ID with the four most significant bits set to "0001" to indicate that the purpose of the PCK is to protect private call communications and with the remaining twenty eight bits being randomly generated as described in 3GPP TS 33.180 [78]; d) shall encrypt the PCK to a UID associated to the MCPTT client using the MCPTT ID and KMS URI of the invited user and a time related parameter as described in 3GPP TS 33.180 [78]; e) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated PCK and PCK-ID as specified in 3GPP TS 33.180 [78]; f) shall add the MCPTT ID of the originating MCPTT to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78]; and g) shall sign the MIKEY-SAKKE I_MESSAGE using the originating MCPTT user's signing key provided in the keying material together with a time related parameter, and add this to the MIKEY-SAKKE payload, as described in 3GPP TS 33.180 [78]; 11) shall include an SDP offer according to 3GPP TS 24.229 [4] with the clarification given in clause 6.2.1 and with a media stream of the offered media-floor control entity; … 13) if this is a remotely initiated ambient listening call, shall comply with the conditions for an implicit request to grant the floor to the terminating MCPTT client as specified in clause 6.4; 14) shall include in the SIP INVITE request a Priv-Answer-Mode header field with the value "Auto" according to the rules and procedures of IETF RFC 5373 [18]; and 15) shall send the SIP INVITE request towards the participating MCPTT function according to 3GPP TS 24.229 [4]." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.6.3.1.1] "Upon receipt of a "SIP INVITE request for originating participating MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "ambient- listening", the participating MCPTT function: … ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 258 2) shall determine the MCPTT ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request; NOTE 1: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 10) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3; 11) shall set the Request-URI to the public service identity of the controlling MCPTT function hosting the private call service; 12) shall set the <mcptt-calling-user-id> element in an application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request to the MCPTT ID of the calling user; 13) if the Priv-Answer-Mode header field specified in IETF RFC 5373 [18] was received in the incoming SIP INVITE request with a value of "Auto" or if no Priv-Answer-Mode header field was received in the incoming SIP INVITE request or a Priv-Answer-Mode header field was received containing a value other than "Auto", shall include the Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request; 14) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for originating participating MCPTT function", as specified in clause 6.3.2.1.1.1; … 16) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [4]. Upon receiving a SIP 200 (OK) response to the SIP INVITE request, the participating MCPTT function: 1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2; 2) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 3) shall include Warning header field(s) received in the incoming SIP 200 (OK) response; 4) shall include the P-Asserted-Identity header field received in the incoming SIP 200 (OK) response into the outgoing SIP 200 (OK) response; 5) shall include an MCPTT session identity mapped to the MCPTT session identity provided in the Contact header field of the received SIP 200 (OK) response; 6) shall include the answer state into the P-Answer-State header field of the outgoing SIP 200 (OK) response, if received in the P-Answer-State header field of the incoming SIP 200 (OK) response; 7) shall send the SIP 200 (OK) response to the inviting MCPTT client according to 3GPP TS 24.229 [4]; and 8) shall interact with the media plane as specified in 3GPP TS 24.380 [5]." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.6.3.1.2] "Upon receiving from the MCPTT client a SIP BYE request the participating MCPTT function: 1) shall follow the procedures as specified in clause 11.1.3.2.1.1. [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.6.3.2.1] Upon receipt of a "SIP INVITE request for terminating participating MCPTT function", the participating MCPTT function: NOTE: The procedures in the present clause are applicable for both on-demand and pre-established sessions. … 3) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCPTT ID and public user identity; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 259 … 6) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [18]." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.6.3.2.2] "Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 11.1.3.2.2.1." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.6.4.1] "This clause describes the procedures for inviting an MCPTT user to an MCPTT ambient listening session. The procedure is initiated by the controlling MCPTT function as the result of an action in clause 11.1.6.4.2. The controlling MCPTT function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; NOTE 1: As a result of calling clause 6.3.3.1.2, the <mcptt-calling-user-id> containing the calling user's MCPTT ID is copied into the outgoing SIP INVITE. 2) shall copy the MCPTT ID of the MCPTT user listed in the MIME resources body of the incoming SIP INVITE request, into the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP INVITE request; 3) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated to the MCPTT user to be invited; NOTE 2: How the controlling MCPTT function finds the address of the terminating MCPTT participating function is out of the scope of the current release. NOTE 3: If the terminating MCPTT user is part of a partner MCPTT system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCPTT function. 4) shall copy the public user identity of the calling MCPTT user from the P-Asserted-Identity header field of the incoming SIP INVITE request into the P-Asserted-Identity header field of the SIP INVITE request; 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; … 7) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request is set to a value of "remote-init", shall include in the outgoing SIP INVITE request an alert-info header field set to a value of "<file:///dev/null>" according to IETF RFC 3261 [24]; 8) shall send the SIP INVITE request towards the core network according to 3GPP TS 24.229 [4]; and 9) shall start a private call timer with a value set to the configured max private call duration for the user. Upon receiving SIP 200 (OK) response for the SIP INVITE request the controlling MCPTT function: 1) shall cache the contact received in the Contact header field; and 2) shall interact with the media plane as specified in 3GPP TS 24.380 [5]. Upon expiry of the private call timer, the controlling MCPTT function shall follow the procedure for releasing the ambient listening call session as specified in clause 11.1.6.4.3 with the clarification that the <release-reason> element included in the SIP BYE request shall be set to "private-call-timer-expiry"." ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 260 [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.6.4.2] "Upon receiving of a "SIP INVITE request for controlling MCPTT function of an ambient listening call" the controlling MCPTT function: 1) shall check whether the public service identity contained in the Request-URI is allocated for ambient listening call and perform the actions specified in clause 6.3.7.1 if it is not allocated and skip the rest of the steps; 2) shall perform actions to verify the MCPTT ID of the inviting MCPTT user in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request, and authorise the request according to local policy; and … 5) shall perform actions as described in clause 6.3.3.2.2; 6) shall allocate an MCPTT session identity for the MCPTT ambient listening call session; and 7) shall invite the MCPTT user listed in the MIME resource-lists body of received SIP INVITE request as specified in clause 11.1.6.4.1. Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 11.1.6.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [34], the controlling MCPTT function supports media buffering and the SIP final response is not yet sent to the inviting MCPTT client, the controlling MCPTT function: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; 2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 3) shall include a P-Answer-State header field with the value "Unconfirmed"; 4) shall include in the SIP 200 (OK) response the g.3gpp.mcptt.ambient-listening-call-release feature-capability indicator as described in clause D.3 in the Feature-Caps header field according to IETF RFC 6809 [60]; NOTE 1: The originator of the ambient listening call is either the initiator of a "remote-init" ambient listening type call or the originator of a "local-init" ambient listening type call. In either case, the originating user is allowed to release the ambient listening call. 5) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; 6) shall send the SIP 200 (OK) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4]; 7) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request is set to a value of "remote-init": a) shall cache the MCPTT ID contained in the <mcptt-calling-user-id> element of the received SIP INVITE request as the listening MCPTT user of the ambient listening call and cache the MCPTT ID contained in the MIME resource-lists body of the received SIP INVITE request as the listened-to MCPTT user; and b) shall cache the ambient listening type of the ambient listening call as "remote-init"; and … If the procedures of clause 11.1.6.4.1 were successful in inviting the MCPTT user listed in the MIME resource-lists body of received SIP INVITE request and the SIP final response is not yet sent to the inviting MCPTT client, the controlling MCPTT function: 1) shall generate a SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.2; 3) shall include in the SIP 200 (OK) response the g.3gpp.mcptt.ambient-listening-call-release feature-capability indicator as described in clause D.3 in the Feature-Caps header field according to IETF RFC 6809 [60]; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 261 NOTE 2: The originator of the ambient listening call is either the initiator of a "remote-init" ambient listening type call or the originator of a "local-init" ambient listening type call. In either case, the originating user is allowed to release the ambient listening call. 4) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; 5) shall send a SIP 200 (OK) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4]; 6) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request is set to a value of "remote-init": a) shall cache the MCPTT ID contained in the <mcptt-calling-user-id> element of the received SIP INVITE request as the listening MCPTT user of the ambient listening call and cache the MCPTT ID contained in the MIME resource-lists body of the received SIP INVITE request as the listened-to MCPTT user; and b) shall cache the ambient listening type of the ambient listening call as "remote-init"; and … The controlling MCPTT function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [4]." [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 6.3.4.2.2] "… 3. when the 'basic floor control operation towards the floor participant' state machine is initialized and the initialised session is not a temporary group session: a. if the "mc_granted" fmtp attribute is not negotiated as specified in clause 14 or this is an ambient listening call: i. if the floor control server is granting an implicit floor request at MCPTT call establishment, shall act as if a Floor Request message was received and perform the actions specified in subclause 6.3.4.3.3; or ii. if the floor control server is not granting an implicit floor request at MCPTT call establishment, shall enter the'G: Floor Idle' state as specified in subclause 6.3.4.3.2; or …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 6.3.4.4.2] "When entering this state the floor control arbitration logic in the floor control server: 1. shall send a Floor Granted message to the floor participant to which the floor is granted. The Floor Granted message: … e. if the call is a remotely initiated ambient listening call, shall set the first bit in the subtype of the Floor Granted message to '1' (Acknowledgment is required) as described in subclause 8.2.2; NOTE: If the call is an ambient listening call and the ambient listening call type is remote-initiated, then the floor participant to which the floor is granted is the terminating floor participant of the call. Otherwise the floor is granted to the participant which requested the floor. …" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 262 [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 6.3.5.2.2] "… When a SIP Session is established and if the session is an ambient listening call session then the floor control interface towards the MCPTT client: 1. if the floor is granted to the associated floor participant a. shall forward the "Floor Granted" message to the associated floor participant; and b. shall enter the state 'U: permitted' as specified in the subclause 6.3.5.5.2; and 2. if the floor is not granted to the associated floor participant a. shall forward the "Floor Taken" message to the associated floor participant; and b. shall enter the state 'U: not permitted Floor Taken' as specified in the subclause 6.3.5.4.2." [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 6.3.5.4.4] "… Upon receiving a Floor Request message from the associated floor participant and the session is a broadcast group call or an ambient listening call, the floor control interface towards the MCPTT client in the floor control server: 1. shall send a Floor Deny message to the associated floor participant. The Floor Deny message: a. shall include in the Reject Cause field the <Reject Cause> value cause #5 (Receive only); b. may include in the Reject Cause field an additional text string explaining the reason for rejecting the floor request in the <Reject Phrase> value; and c. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; 2. may set the first bit in the subtype of the Floor Deny message to '1' (Acknowledgment is required) as described in subclause 8.2.2; and NOTE 2: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received. 3. shall remain in the 'U: not permitted and Floor Taken' state. …" |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.6.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.6.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) and SS-UE2 (MCPTT Client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client), the SS-UE2 (MCPTT client) and the MCPTT Server will communicate, Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined 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) ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 263 - 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) and the SS-UE2 (MCPTT client) as defined in Annex A, Figure A.4.1. - The SS-UE1 (MCPTT client) and the SS-UE2 (MCPTT client) perform the Procedure for MCPTT Authorization, Configuration and Key Generation as specified in clause 5.1. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.6.3.2 Test procedure sequence | Table 6.2.8.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCPTT client) requests the establishment of a remotely initiated ambient listening call to SS-UE2 (MCPTT client) - - - - 2 Check: Does the MCPTT server correctly perform step 1 of procedure 'MCPTT E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to establish a remotely initiated ambient listening call with automatic commencement mode and without implicit floor control according to option a of note in Annex A, Table A.3.1.3-1? - - 1 P 3 Check: Does the MCPTT server send a Floor Granted to SS-UE2? <- Floor Granted 2 P 4 Check: Does the MCPTT server send a Floor Taken to SS-UE1, with the Permission to Request the Floor field set to '0'? <- Floor Taken 2 P 5 The SS-UE1 (MCPTT client) releases the call - - - - 6 Check: Does the MCPTT server correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 3 P All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.2.8.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.2.6.3.2-1; Step 1, Annex A, Table A.3.1.3-1 Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1 Information Element Value/remark Comment Reference Condition Answer-Mode not present Priv-Answer-Mode answer-mode-value "Auto" answer-mode-param "require" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 264 Derivation Path: Annex A, Table A.3.1.4-1 Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.2.6.3.3-2. MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.2.6.3.3-3. Table 6.2.6.3.3-2: SDP in SIP INVITE (Table 6.2.6.3.3-1) Derivation Path: Annex A, Table A.3.1.4-2, condition PRIVATE-CALL Information Element Value/remark Comment Reference Condition Media description[1] Media description for audio media attribute a=line attribute=recvonly recvonly Table 6.2.8.3.3-3: MCPTT-Info in SIP INVITE (Table 6.2.6.3.3-1) Derivation Path: Annex A, Table A.3.1.4-3, condition PRIVATE-CALL Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params session-type "ambient-listening" anyExt ambient-listening-type "remote-init" The anyExt field may contain other values - these need not be checked Table 6.2.6.3.3-4: SIP INVITE from MCPTT Server to SS-UE2 (Step 2, Table 6.2.6.3.2-1; Step 1, Annex A, Table A.3.1.3-1 Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4 Information Element Value/remark Comment Reference Condition Answer-Mode not present Priv-Answer-Mode answer-mode-value "Auto" answer-mode-param "require" Alert-Info value "<file:///dev/null>" MIME body part SDP message MIME-part-body SDP Message as described in Table 6.2.6.3.3-5. MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.2.6.3.3-6. Table 6.2.6.3.3-5: SDP in SIP INVITE (Table 6.2.6.3.3-4) Derivation Path: Annex A, Table A.3.1.4-5, condition PRIVATE-CALL Information Element Value/remark Comment Reference Condition Media description[1] Media description for audio media attribute a=line attribute=recvonly recvonly ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 265 Table 6.2.6.3.3-6: MCPTT-Info in SIP INVITE (Table 6.2.6.3.3-4) Derivation Path: Annex A, Table A.3.1.4-6, condition PRIVATE-CALL, INVITE_REFER Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params session-type "ambient-listening" anyExt ambient-listening-type "remote-init" The anyExt field may contain other values - these need not be checked Table 6.2.6.3.3-6: SIP 200 (OK) from SS-UE2 (Step 2, Table 6.2.6.3.2-1; Step 1, Annex A, Table A.3.1.3-1 Step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7 Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.2.6.3.3-7 Table 6.2.6.3.3-7: SDP in SIP 200 (OK) (Table 6.2.6.3.3-6) Derivation Path: Annex A, Table A.3.1.4-8, condition PRIVATE-CALL Information Element Value/remark Comment Reference Condition Media description[1] Media description for audio media attribute a=line attribute=sendonly sendonly Table 6.2.6.3.3-9: SIP 200 (OK) from MCPTT Server to SS-UE1 (Step 2, Table 6.2.6.3.2-1; Step 1, Annex A, Table A.3.1.3-1 Step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9 Information Element Value/remark Comment Reference Condition Feature-Caps fcap-name "g.3gpp.mcptt.ambient- listening-call-release" Indicates that the MCPTT server is capable of receiving a SIP BYE from an MCPTT client to release an ambient-listening call Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.2.6.3.3-10 Table 6.2.6.3.3-10: SDP in SIP 200 (OK) (Table 6.2.6.3.3-9) Derivation Path: Annex A, Table A.3.1.4-10, condition PRIVATE-CALL Information Element Value/remark Comment Reference Condition Media description[1] Media description for audio media attribute a=line attribute=sendonly sendonly ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 266 Table 6.2.6.3.3-11: Floor Taken (Step 4, Table 6.2.6.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.7-1 Information Element Value/remark Comment Condition Permission to Request the Floor Permission to Request the Floor "0" The receiver is NOT permitted to request floor 6.2.7 MCPTT Server - MCPTT Client / First-to-answer call / On-demand / With Floor Control |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.7.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCPTT Client) initiates establishment of a first-to-answer call to targeting users without implicit floor control with SIP INVITE message } then { IUT (MCPTT Server) accepts the request and sends SIP INVITE message to SS-UE2 (MCPTT Client) and sends SIP INVITE message to SS-UE3 (MCPTT Client) } } (2) with { IUT (MCPTT Server) having in process a first-to-answer call } ensure that { when { the SS-UE2 (MCPTT Client) responds with SIP 180 Ringing message } then { IUT (MCPTT Server) receives the response and sends SIP 183 Session Progress message to SS-UE1 (MCPTT Client) } } (3) with { IUT (MCPTT Server) having in process a first-to-answer call } ensure that { when { the SS-UE2 (MCPTT client) responds with SIP 200 OK message } then { IUT (MCPTT Server) receives the response and sends SIP 200 OK message to SS-UE1 (MCPTT Client) } } (4) with { IUT (MCPTT Server) having in process a first-to-answer call } ensure that { when { the SS-UE2 (MCPTT client) responds with SIP 200 OK message } then { IUT (MCPTT Server) sends SIP CANCEL message to SS-UE3 (MCPTT Client) and sends SIP ACK message to SS-UE3 (MCPTT Client) after received SIP 487 Request Terminated message } } (5) with { IUT (MCPTT Server) having established a first-to-answer call } ensure that { when { the SS-UE1 (MCPTT client) ends the a first-to-answer call } then { IUT (MCPTT Server) responds by sending a SIP 200 (OK) message to SS-UE1 (MCPTT client) and sends a SIP BYE message to SS-UE2 (MCPTT client) } ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 267 |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.7.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 11.1.1.3.1.1, 11.1.1.4.1, 11.1.1.4.2, 11.1.3.2.1.1, 11.1.3.2.2.1, 11.1.3.3.1. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core specification they have been copied from. Unless otherwise stated these are Rel-15 requirements. [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.1.3.1.1] "Upon receipt of a "SIP INVITE request for originating participating MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "private" or "first- to-answer", the participating MCPTT function: 1) may reject the SIP INVITE request depending on the value of the Resource-Priority header field if the Resource-Priority header field is included in the received SIP INVITE request according to rules and procedures specified in IETF RFC 4412 [29] and shall not continue with the rest of the steps; … 3) shall determine the MCPTT ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request; … 5) shall: .. b) if the <session-type> is set to "first-to-answer", determine that the call is a first-to-answer-call; 6) if the call is a: … b) first-to-answer, determine the public service identity of the controlling MCPTT function for the first-to- answer call service associated with the originating user's MCPTT ID identity; … 15) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3 with the following clarifications: a) if the call is a first-to-answer call and if the <PrivateCall> element exists in the MCPTT user profile document with one or more <entry> elements (see the MCPTT user profile document in 3GPP TS 24.484 [50]), then only the <entry> elements of the application/resource-lists MIME body that have a "uri" attribute that matched with an <entry> elements of the <PrivateCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) are included in the application/resource-lists MIME body and the <session-type> is set to "first-to-answer" in the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request generated in clause 6.3.2.1.3; 16) shall set the Request-URI to the public service identity of the controlling MCPTT function hosting the private call service or first-to-answer call service as determined by step 6); 17) shall set the <mcptt-calling-user-id> element in an application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request to the MCPTT ID of the calling user; … 19) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for originating participating MCPTT function", as specified in clause 6.3.2.1.1.1; … ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 268 20) shall include a Resource-Priority header field according to rules and procedures of 3GPP TS 24.229 [4] set to the value indicated in the Resource-Priority header field if included in the SIP INVITE request from the MCPTT client; … 22) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [4]. Upon receiving a SIP 180 (Ringing) response, the participating MCPTT function: 1) shall generate a SIP 180 (Ringing) response to the SIP INVITE request as specified in the clause 6.3.2.1.5.1; 2) shall include the P-Asserted-Identity header field as received in the incoming SIP 180 (Ringing) response; 3) shall include Warning header field(s) received in the incoming SIP 180 (Ringing) response; and 4) shall send the SIP 180 (Ringing) response to the inviting MCPTT client according to 3GPP TS 24.229 [4]. Upon receiving a SIP 200 (OK) response, the participating MCPTT function: 1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2; 2) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 3) shall include Warning header field(s) received in the incoming SIP 200 (OK) response; 4) shall include the P-Asserted-Identity header field received in the incoming SIP 200 (OK) response into the outgoing SIP 200 (OK) response; 5) shall include an MCPTT session identity mapped to the MCPTT session identity provided in the Contact header field of the received SIP 200 (OK) response; 5A) shall include the answer state into the P-Answer-State header field of the outgoing SIP 200 (OK) response, if received in the P-Answer-State header field of the incoming SIP 200 (OK) response; 6) shall send the SIP 200 (OK) response to the inviting MCPTT client according to 3GPP TS 24.229 [4]; 7) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and 8) shall start the SIP session timer according to rules and procedures of IETF RFC 4028 [7]. The participating MCPTT function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [4]." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.1.4.1] "The controlling MCPTT function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; NOTE 1: As a result of calling clause 6.3.3.1.2, the <mcptt-calling-user-id> containing the calling user's MCPTT ID is copied into the outgoing SIP INVITE. 2) if the received SIP INVITE request contains an authorised request for an MCPTT emergency private call as determined by clause 6.3.3.1.13.2: a) shall set the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true"; 3) if the received SIP INVITE request contained a <session-type> element in an application/vnd.3gpp.mcptt- info+xml MIME body set to "first-to-answer" shall include in the SIP INVITE request a Priv-Answer-Mode header field with the value "Manual" according to the rules and procedures of IETF RFC 5373 [18]; 4) shall copy the MCPTT ID of the MCPTT user listed in the MIME resources body of the incoming SIP INVITE request, into the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP INVITE request; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 269 5) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated to the MCPTT user to be invited; NOTE 2: How the controlling MCPTT function finds the address of the terminating MCPTT participating function is out of the scope of the current release. NOTE 3: If the terminating MCPTT user is part of a partner MCPTT system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCPTT function. 6) shall copy the public user identity of the calling MCPTT user from the P-Asserted-Identity header field of the incoming SIP INVITE request into the P-Asserted-Identity header field of the SIP INVITE request; 7) shall include a Resource-Priority header field populated with the values for an MCPTT emergency private call as specified in clause 6.3.3.1.19, if either of the following conditions is met: a) if the received SIP INVITE request contains an authorised request for an MCPTT emergency private call as determined in step 2 above; or b) the originating MCPTT user is in an in-progress emergency private call state with the targeted MCPTT user; 8) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; 9) shall send the SIP INVITE request towards the core network according to 3GPP TS 24.229 [4]; and 10) shall start a private call timer with a value set to the configured max private call duration for the user. Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request containing a Require header field with the option tag "100rel" and a P-Answer-State header field with the value "Unconfirmed" in response, the controlling MCPTT function: 1) shall send a SIP PRACK request towards the terminating network according to 3GPP TS 24.229 [4]. Upon receiving SIP 200 (OK) response for the SIP INVITE request the controlling MCPTT function: 1) shall cache the contact received in the Contact header field; and 2) shall interact with the media plane as specified in 3GPP TS 24.380 [5]. Upon expiry of the private call timer, the controlling MCPTT function shall follow the procedure for releasing private call session as specified in clause 11.1.4.4.". [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.1.4.2] "Upon receipt of: - a "SIP INVITE request for controlling MCPTT function of a private call"; or - a "SIP INVITE request for controlling MCPTT function of a first-to-answer call"; the controlling MCPTT function: 2) if the <session-type> in the SIP INVITE request is set to "first-to-answer" shall check whether the public service identity contained in the Request-URI is allocated for first-to-answer call and perform the actions specified in clause 6.3.7.1 if it is not allocated and skip the rest of the steps; … 10) shall perform actions as described in clause 6.3.3.2.2; 11) shall allocate an MCPTT session identity for the MCPTT session; and 12) if the <session-type> in the received SIP INVITE request is set to "first-to-answer" and if the SIP INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <call-to-functional-alias-ind> element set to "true": ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 270 … otherwise shall invite the MCPTT user(s) listed in the MIME resource-lists body of received SIP INVITE request as specified in clause 11.1.1.4.1. Upon receiving a SIP 180 (Ringing) response and if the SIP 180 (Ringing) response or the SIP final response has not yet been sent to the inviting MCPTT client, the controlling MCPTT function: … 2) if the SIP 180 (Ringing) response is associated with a SIP INVITE that contained a <session-type> set to "first-to-answer", and no other SIP 180 (Ringing) responses have been received that are associated with a SIP INVITE that contained a <session-type> set to "first-to-answer", shall generate a SIP 183 (Session Progress) response to the SIP INVITE request and send the SIP 183 (Session Progress) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4]. Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 11.1.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [34], if the <session-type> in the SIP INVITE request is set to "private", the controlling MCPTT function supports media buffering and the SIP final response is not yet sent to the inviting MCPTT client, the controlling MCPTT function: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; 2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 3) shall include a P-Answer-State header field with the value "Unconfirmed"; … 5) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and 6) shall send the SIP 200 (OK) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request, the SIP dialog was established as a result of receiving a SIP INVITE request with a <session-type> element set to the value of "first-to-answer" and the SIP final response has not yet been sent to the inviting MCPTT client the controlling MCPTT function: 1) shall generate a SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; … 5) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; NOTE 4: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4]; 7) for all other MCPTT clients that were invited due to the controlling MCPTT function receiving a SIP INVITE request with a <session-type> element set to the value of "first-to-answer": a) shall send a SIP BYE request to release a SIP dialog that has been established since the SIP 200 (OK) response was sent in step 5) by following the procedures in clause 6.3.3.1.5 with the clarification that the SIP BYE request contain an application/vnd.3gpp.mcptt-info+xml MIME body including a <release- reason> element set to a value of "not selected for call"; b) shall generate and send a SIP CANCEL request according SIP IETF RFC 3261 [24], to cancel a SIP dialog that has not yet been established since the SIP 200 (OK) response was sent in step 5); c) on receiving a SIP 200 (OK) to a SIP CANCEL request, shall wait to receive a SIP 487 (Request Terminated) to the original SIP INVITE request sent to the client; and ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 271 d) if a SIP 487 (Request Terminated) from the MCPTT client is not received within a time determined by the MCPTT server implementation, shall send a SIP BYE towards the MCPTT client by following the procedures in clause 6.3.3.1.5 with the clarification that the SIP BYE request contain an application/vnd.3gpp.mcptt-info+xml MIME body including a <release-reason> element set to a value of "not selected for call"; and 8) if not successful in cancelling or terminating SIP dialogs in step 6) above, may repeat the SIP CANCEL and SIP BYE requests. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCPTT client, where the SIP 200 (OK) response was sent with a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149", the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.18. The controlling MCPTT function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [4]. Upon receiving a SIP BYE request from the originating MCPTT client containing an application/vnd.3gpp.mcptt- info+xml MIME body containing a <release-reason> element set to a value of "authentication of the MIKEY-SAKE I_MESSAGE failed", the controlling MCPTT function: … 2) shall follow the procedures in clause 11.1.3.3.1." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.3.2.1.1] "Upon receiving from the MCPTT client a SIP BYE request the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.6." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.3.2.2.1] "Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.1." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.3.3.1] "Upon receiving a SIP BYE request the controlling MCPTT function shall follow the procedures as specified in clause 6.3.3.2.4." |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.7.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.7.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client), SS-UE2 (MCPTT Client) and SS-UE3 (MCPTT Client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client), the SS-UE2 (MCPTT client) , the SS-UE3 (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. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 272 Preamble: - The IUT (MCPTT Server) is connected to PLMN1 - The IUT (MCPTT Server) is connected to the SS-UE1 (MCPTT client), the SS-UE2 (MCPTT client) and the SS-UE3 (MCPTT client) as defined in Annex A, Figure A.4.1. - The SS-UE1 (MCPTT client), the SS-UE2 (MCPTT client) and the SS-UE3 (MCPTT client) perform the Procedure for MCPTT Authorization, Configuration and Key Generation as specified in clause 5.1. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.7.3.2 Test procedure sequence | Table 6.2.7.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCPTT client) requests the establishment of a first-to-answer call to targeting users B and C, in SS-UE2 and SS- UE3 respectively. - - - - 2 Check: Does the MCPTT server correctly perform steps 1-4 within step 1 of procedure 'MCPTT E2E private call establishment, manual commencement' as described in Annex A, Table A.3.3.3-1 to request the establishment of a first-to-answer call without implicit floor request with user B? - - 1 P 3 Check: Does the MCPTT server correctly perform steps 2-3 within step 1 of procedure 'MCPTT E2E private call establishment, manual commencement' as described in Annex A, Table A.3.3.3-1 to request the establishment of a first-to-answer call without implicit floor request with user C? (see note) - - 1 P 4 The SS-UE2 (MCPTT Client) sends a SIP 180 Ringing to the MCPTT Server -> SIP 180 (Ringing) - - 5 Check: Does the MCPTT server send a SIP 183 (session Progress) to SS-UE1? <- SIP 183 (Session Progress) 2 P 6 The SS-UE2 (MCPTT Client) accepts the call. - - - - 7 Check: Does the MCPTT server correctly performs procedure 'MCPTT E2E private call establishment, manual commencement' except steps 7-8 within step 1, as described in Annex A, Table A.3.3.3-1 to complete the first-to- answer call establishment with user B? - - 3 P 8 Check: Does the MCPTT server send a SIP CANCEL to cancel the request (another Client has answered) towards user C. <-- SIP CANCEL 4 P 9 The SS-UE3 (MCPTT client) responds with a SIP 200 (OK)? --> SIP 200 (OK) - - 10 The SS-UE3 (MCPTT client) sends a SIP 487 (Request Terminated) to confirm terminating of the dialog --> SIP 487 (Request Terminated) - - 10A Check: Does the MCPTT server send a SIP ACK? <-- SIP ACK 4 P 12 The SS-UE1 (MCPTT client) releases the call - - - - 13 Check: Does the MCPTT server correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 5 P NOTE: During this procedure the SS-UE3 performs the role of SS-UE2. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 273 |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.7.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.2.7.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.2.7.3.2-1; Step 1, Annex A, Table A.3.3.3-1; Step 1, Annex A, Table A.2.21.3-1) Derivation Path: Annex A, Table A.3.3.4-1 with FIRST-TO-ANSWER instead of MANUAL condition Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Annex A, Table A.3.3.4-2 without PRIVATE-CALL condition MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Annex A, Table A.3.3.4-3 with FIRST-TO-ANSWER condition instead of PRIVATE-CALL. MIME body part Resource lists MIME-part-body Resource list as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.3.1-1 with FIRST-TO-ANSWER condition. Table 6.2.7.3.3-2: SIP INVITE from MCPTT Server to SS-UE2 (Step 2, Table 6.2.7.3.2-1; Step 1, Annex A, Table A.3.3.3-1; Step 2, Annex A, Table A.2.21.3-1) Derivation Path: Annex A, Table A.3.3.4-4 with FIRST-TO-ANSWER instead of MANUAL condition Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Annex A, Table A.3.3.4-6 with FIRST-TO-ANSWER condition instead of PRIVATE-CALL. Table 6.2.7.3.3-3: SIP INVITE from MCPTT Server to SS-UE3 (Step 3, Table 6.2.7.3.2-1; Step 1, Annex A, Table A.3.3.3-1; Step 2, Annex A, Table A.2.21.3-1) Derivation Path: Annex A, Table A.3.3.4-4 with FIRST-TO-ANSWER instead of MANUAL condition Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.2.7.3.3-4. Table 6.2.7.3.3-4: MCPTT-Info in SIP INVITE (Table 6.2.7.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1, condition FIRST-TO-ANSWER Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_C The URI of the called user mcptt-calling-user-id Encrypted (see note) <mcptt- calling-user-id> with mcpttURI set to px_MCPTT_ID_User_A The URI of the calling user NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1A. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 274 Table 6.2.7.3.3-5: SIP 200 (OK) from SS-UE2 (Step 6, Table 6.2.7.3.2-1; Step 1, Annex A, Table A.3.3.3-1; Step 7, Annex A, Table A.2.21.3-1) Derivation Path: Annex A, Table A.3.3.4-7 Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Annex A, Table A.3.3.4-8 with WITH_SECURITY condition Table 6.2.7.3.3-5: SIP 200 (OK) from MCPTT Server to SS-UE1 (Step 6, Table 6.2.7.3.2-1; Step 1, Annex A, Table A.3.3.3-1; Step 8, Annex A, Table A.2.21.3-1) Derivation Path: Annex A, Table A.3.3.4-9 Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Annex A, Table A.3.3.4-10 with WITH_SECURITY condition Table 6.2.7.3.3-6: SIP ACK from the SS-UE3 (Step 10A, Table 6.2.21.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.1.2-1, condition NON-2XX 6.2.8 MCPTT Server - MCPTT Client / Remotely initiated private call / On- demand |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { SS-UE3 (MCPTT Client) requests the remote initiation of a private call by sending a SIP MESSAGE message } then { IUT (MCPTT Server) sends a SIP MESSAGE message to SS-UE1 (MCPTT Client) and responds with a SIP 200 (OK) to SS-UE3 (MCPTT Client) } } (2) with { IUT (MCPTT Server) having requested a remotely initiated private call } ensure that { when { the SS-UE1 (MCPTT Client) initiates establishment of a private call with automatic commencement mode and implicit floor request } then { IUT (MCPTT Server) accepts the call from the initiator and establishes the call with SS- UE2 (MCPTT Client) } } (3) with { IUT (MCPTT Server) having established a remotely initiated private call } ensure that { when { the SS-UE1 (MCPTT client) ends remotely initiated private call } then { IUT (MCPTT Server) responds by sending a SIP 200 (OK) message to SS-UE1 (MCPTT client) and sends a SIP BYE message to SS-UE2 (MCPTT client) } ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 275 |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 11.1.7.2.1, 11.1.7.2.2, 11.1.7.3.1, 11.1.7.3.2, 11.1.7.4. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core specification they have been copied from. Unless otherwise stated these are Rel- 15 requirements. [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.7.2.1] "Upon receiving a request from the MCPTT to send a remotely initiated private call request to the remote MCPTT user to originate a private call to an identified MCPTT user, the MCPTT client: … 2) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications: a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request; b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6]; c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4]; d) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing: i) the <mcptt-called-party-id> element set to the MCPTT ID of the identified MCPTT user of the remotely initiated private call; and ii) an <anyExt> element containing: A) the <request-type> element set to a value of "remotely-initiated-private-call-request"; B) the <notify-remote-user> element set to a value of "true" if the requesting MCPTT user has indicated that the remote MCPTT user be notified of the remotely initiated private call request; and C) the <notify-remote-user> element set to a value of "false" if the requesting MCPTT user has indicated that the remote MCPTT user not be notified of the remotely initiated private call request; e) shall insert in the SIP MESSAGE request a MIME resource-lists body with the MCPTT ID of the remote MCPTT user, according to rules and procedures of IETF RFC 5366 [20]; and f) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and 3) shall send the SIP MESSAGE request towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4]." ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 276 [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.7.2.2] "… Upon completion of the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1, the MCPTT client: 1) if: a) the MCPTT ID of the identified MCPTT user is identical to the <mcptt-calling-user-id> element contained in the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request: and b) the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were successful in originating an MCPTT private call to the identified MCPTT user; then: a) shall skip the remaining steps of the current clause; NOTE: In this case, it is not necessary to send a response to the sender of the remotely initiated private call request as the sender and the terminating party of the successful private call origination are the same user and will be aware of the request's outcome. 2) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications: a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request; b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6]; c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4]; d) shall include in an application/resource-lists+xml MIME body the MCPTT ID contained in the <mcptt- calling-user-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request; and e) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing: i) the <mcptt-called-party-id> set to the MCPTT ID of the identified MCPTT user called by the remote MCPTT user; and ii) an <anyExt> element containing: A) the <response-type> element set to a value of "remotely-initiated-private-call-response"; B) if the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were successful in originating an MCPTT private call to the identified MCPTT user, a <remotely-initiated-call-outcome> element set to a value of "success"; and C) if the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were not successful in originating an MCPTT private call to the identified MCPTT user, a <remotely-initiated-call- outcome> element set to a value of "fail"; 3) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and 4) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4]." ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 277 [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.7.3.1] "Upon receiving a "SIP MESSAGE request for remotely initiated private call for originating participating MCPTT function" the participating MCPTT function: … 2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request; NOTE: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3 … 4) shall determine the public service identity of the controlling MCPTT function for the remotely initiated private call service for the requesting MCPTT user; 5) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]; 6) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function associated with the remotely initiated private call service for the requesting MCPTT user; 7) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request; 8) shall set the <mcptt-calling-user-id> element of the <mcpttinfo> element containing the <mcptt-Params> element to the MCPTT ID determined in step 2) above; 9) shall copy the contents of the application/resource-lists MIME body in the received SIP MESSAGE request into an application/resource-lists MIME body in the outgoing SIP MESSAGE request; 10) shall set the P-Asserted-Identity in the outgoing SIP MESSAGE request to the public user identity in the P- Asserted-Identity header field contained in the received SIP MESSAGE request; 11) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6]; 12) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6]; 13) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and 14) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4]. Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 13), the participating MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the MCPTT client." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.7.3.2] "Upon receiving a "SIP MESSAGE request for remotely initiated private call for terminating participating MCPTT function" the participating MCPTT function: … 2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt- info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity; … 4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 278 5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; and 6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall forward the SIP 2xx response to the controlling MCPTT function. [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 11.1.7.4] Upon receiving a: - "SIP MESSAGE request for remotely initiated private call request for controlling MCPTT function"; or - "SIP MESSAGE request for remotely initiated private call response for controlling MCPTT function"; the controlling MCPTT function: … 4) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]; … 7) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request; 8) shall copy the MCPTT ID of the MCPTT user listed in the MIME resources body of the incoming SIP MESSAGE request, into the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request; … 12) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4]. Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the originating participating MCPTT function." |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client), SS-UE2 (MCPTT Client) and SS-UE3 (MCPTT Client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client), the SS-UE2 (MCPTT client) , the SS-UE3 (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. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 279 - 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), the SS-UE2 (MCPTT client) and the SS-UE3 (MCPTT client) as defined in Annex A, Figure A.4.1. - The SS-UE1 (MCPTT client), the SS-UE2 (MCPTT client) and the SS-UE3 (MCPTT client) perform the Procedure for MCPTT Authorization, Configuration and Key Generation as specified in clause 5.1. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.3.2 Test procedure sequence | Table 6.2.8.3.2-1: Main behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE3 (MCPTT client) requests the remote initiation of a private call by SS-UE1 (MCPTT client) to SS-UE2 (MCPTT client) - - - - 2 Check: Does the MCPTT Server correctly perform procedure 'MCX E2E SIP MESSAGE' as described in Annex A, Table A.2.10.3-1 to request the remote initiation of a private call from SS-UE1 to SS-UE2? (see note) - - 1 P 3 The SS-UE1 (MCPTT client) requests the establishment of a private call to SS-UE2 (MCPTT client) with manual commencement mode and implicit floor request. - - - - 4 Check: Does the MCPTT server correctly perform procedure 'MCPTT E2E private call establishment, manual commencement' as described in Annex A, Table A.3.3.3-1 to establish a private call with manual commencement mode and implicit floor control according to option b.ii of note in Annex A, Table A.3.3.3-1? - - 2 P 5 The SS-UE1 (MCPTT client) notifies the successful remote initiation of the private call to SS-UE3 (MCPTT client). - - - - 6 Check: Does the MCPTT Server correctly perform procedure 'MCX E2E SIP MESSAGE' as described in Annex A, Table A.2.10.3-1 to notify to SS-UE3 the successful remote initiation of a private call between SS-UE1 and SS-UE2? - - 1 P 7 The SS-UE1 (MCPTT client) releases the call - - - - 8 Check: Does the MCPTT server correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 3 P NOTE: During this procedure, SS-UE3 performs the role of SS-UE1, and SS-UE1 the role of SS-UE2. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.2.8.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 280 Table 6.2.8.3.3-1: SIP MESSAGE from the SS-UE3 (Step 2, Table 6.2.8.3.2-1; Step 1, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 with condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info ETSI TS 124 379 [4] (3GPP TS 24.379) clause F.1 MIME-part-body MCPTT-Info as described in Table 6.2.8.3.3-2 MIME body part Resource-lists MIME-part-body Resource-lists as described in Table 6.2.8.3.3-3 Table 6.2.8.3.3-2: MCPTT-Info in SIP MESSAGE (Table 6.2.8.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri not present mcptt-calling-user-id not present mcptt-called-party-id Encrypted (see note) <mcptt- called-party-id> with mcpttURI set to px_MCPTT_ID_User_B User to be called ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.1 anyExt request-type "remotely-initiated-private- call-request" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.1 notify-remote-user "true" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.1 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. Table 6.2.8.3.3-3: Resource lists in SIP MESSAGE (Table 6.2.8.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-1 Information Element Value/remark Comment Reference Condition resource-lists list entry[1] uri attribute px_MCPTT_ID_User_A The targeted MCPTT user initiating the call ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.1 Table 6.2.8.3.3-4: SIP MESSAGE from the MCPTT-Server to SS-UE1 (Step 2, Table 6.2.8.3.2-1; Step 3, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with condition MCPTT and ACCEPT- CONTACT-WITH-MEDIA-FEATURE-TAG Information Element Value/remark Comment Reference Condition P-Asserted-Identity name-addr px_MCX_SIP_PublicUse rId_C ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.4 Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.2.8.3.3-5 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 281 Table 6.2.8.3.3-5: MCPTT-Info in SIP MESSAGE (Table 6.2.8.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A The targeted MCPTT user initiating the call ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.4 mcptt-calling-user-id Encrypted (see note) <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_C The MCPTT user requesting a remote private call ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.3.1 mcptt-called-party-id Encrypted (see note) <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_B The MCPTT user to be called ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.2 anyExt request-type "remotely-initiated- private-call-request" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.1 notify-remote-user "true" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.1 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. Table 6.2.8.3.3-6: SIP MESSAGE from the SS-UE1 (Step 6, Table 6.2.8.3.2-1; Step 1, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 with condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info ETSI TS 124 379 [4] (3GPP TS 24.379) clause F.1 MIME-part-body MCPTT-Info as described in Table 6.2.8.3.3-7 MIME body part Resource-lists MIME-part-body Resource-lists as described in Table 6.2.8.3.3-8 Table 6.2.8.3.3-7: MCPTT-Info in SIP MESSAGE (Table 6.2.8.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri not present mcptt-calling-user-id not present mcptt-called-party-id Encrypted (see note) <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_B ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.2 anyExt response-type "remotely-initiated- private-call-response" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.2 remotely-initiated-call- outcome "success" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.2 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 282 Table 6.2.8.3.3-8: Resource lists in SIP MESSAGE (Table 6.2.8.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-1 Information Element Value/remark Comment Reference Condition resource-lists list entry[1] uri attribute px_MCPTT_ID_User_C The targeted MCPTT user ETSI TS 124 379 [4] (3GPP TS 24.379) clause 10.1.5.2.2 Table 6.2.8.3.3-9: SIP MESSAGE from the MCPTT-Server to SS-UE3 (Step 6, Table 6.2.8.3.2-1; Step 3, Annex A, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with condition MCPTT and ACCEPT- CONTACT-WITH-MEDIA-FEATURE-TAG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.2.8.3.3-14 Table 6.2.8.3.3-10: MCPTT-Info in SIP MESSAGE (Table 6.2.8.3.3-9) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_C ETSI TS 124 379 [4] (3GPP TS 24.379) clause 10.1.5.4 mcptt-calling-user-id Encrypted (see note) <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [4] (3GPP TS 24.379) clause 10.1.5.4 mcptt-called-party-id Encrypted (see note) <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_B ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.2 anyExt response-type "remotely-initiated-private- call-response" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.2 remotely-initiated-call- outcome "success" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 11.1.7.2.2 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 283 |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3 Location | 6.3.1 MCPTT Server - MCPTT Client / Location / Event Triggered Location Information report |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { IUT (MCPTT Server) requests to send a location reporting configuration } then { IUT (MCPTT Server) sends a SIP MESSAGE message containing the cell change trigger criteria and the minimum report interval to the SS-UE1 (MCPTT Client) } } (2) with { IUT (MCPTT Server) having received Location Information report } ensure that { when { SS-UE1 (MCPTT Client) requests location report containing the cell change trigger identification along with the location information report, the current location coordinates and the current serving ECGI by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379), clauses 13.2.2, 13.2.4, 13.3.4.1, 13.3.4.2. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core specification they have been copied from. Unless otherwise stated, these are Rel-13 requirements. [ETSI TS 124 379 [4] (3GPP TS 24.379) clause 13.2.2] "The participating MCPTT function may configure the location reporting in the MCPTT client by generating a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. The participating MCPTT function: 1) shall include a Request-URI set to the URI corresponding to the identity of the MCPTT client; 2) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [6]; 3) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-request-uri> element containing the MCPTT ID of the MCPTT user to receive the configuration; 4) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with the <Configuration> element contained in the <location-info> root element set to the desired configuration; 5) shall include the TriggerId attribute where defined for the sub-elements defining the trigger criterion ; 6) shall include the public service identity of the participating MCPTT function in the P-Asserted-Identity header field; 7) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and 8) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]." [ETSI TS 124 379 [4] (3GPP TS 24.379) clause 13.2.4] "If the participating MCPTT function receives a SIP request containing: 1) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 284 2) an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; then the participating MCPTT function shall authorise the location report based on the MCPTT ID received. If the MCPTT user is authorised to send a location report the participating MCPTT function: 1) shall use the location information as needed; and 2) shall follow the procedure of clause 6.3.2.4.1, if the MCPTT client has entered into or exited from an emergency alert area ;and 3) shall follow the procedure of clause 6.3.2.4.2, if the MCPTT client has entered into or exited from a group geographic area." [ETSI TS 124 379 [4] (3GPP TS 24.379) clause 13.3.4.1] "If a location reporting trigger fires the MCPTT client checks if the minimumReportInterval timer is running. If the timer is running the MCPTT client waits until the timer expires. When the minimumReportInterval timer fires, the MCPTT client: 1) shall, if any of the reporting triggers are still true, send a location information report as specified in clause 13.3.4.2. If the MCPTT client receives a location information request as specified in clause 13.3.3, the MCPTT client shall send a location report as specified in clause 13.3.4.2." [ETSI TS 124 379 [4] (3GPP TS 24.379) clause 13.3.4.2] "… If the MCPTT client does not need to send a SIP request for other reasons, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. The MCPTT client; 1) shall include in the Request-URI, the SIP URI received in the P-Asserted-Identity header field in the received SIP MESSAGE request for location report configuration; 2) shall include a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; 3) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body and in the <location-info> root element include: a) a <Report> element and if the Report was triggered by a location request include the <ReportID> attribute set to the value of the <RequestID> attribute in the received Request; b) a <TriggerId> child element set to the value of each <Trigger-Id> value of the triggers that have fired; and c) the location reporting elements corresponding to the triggers that have fired; 4) shall include an Accept-Contact header field with the media feature tag g.3gpp.mcptt along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [6]; 5) shall set the minimumReportInterval timer to the minimumReportInterval time and start the timer; 6) shall reset all triggers; and 7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]." |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 285 - 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 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. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.3.2 Test procedure sequence | Table 6.3.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the MCPTT Server send a location reporting configuration to SS-UE1 (see note 1) - - - - 2 Check: Does the MCPTT Server correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to send a location reporting configuration message containing the cell change trigger criteria and the minimum report interval to SS-UE1? - - 1 P 3 Check: Does the MCPTT Server correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to send a location report from SS-UE1 containing the cell change trigger identification along with the location information report, the current location coordinates, and the current serving ECGI? (see note 2) - - 2 P NOTE 1: This is expected to be done via a suitable implementation dependent MMI. NOTE 2: This action represents the UE changing from cell. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 286 Table 6.3.1.3.3-1: SIP MESSAGE from the MCPTT Server (Step 2, Table 6.3.1.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT and LOCATION- CONFIG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-info as described in Table 6.3.1.3.3-2 MIME body part Location-info ETSI TS 124 379 [4] (3GPP TS 24.379) clause F.3 MIME-part-body Location-info as described in Table 6.3.1.3.3-3 Table 6.3.1.3.3-2: MCPTT-Info in SIP MESSAGE (Table 6.3.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [4] (3GPP TS 24.379) clause 13.2.2 mcptt-calling-user-id not present NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. Table 6.3.1.3.3-3: Location-Info in SIP MESSAGE (Table 6.3.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.2-1 Information Element Value/remark Comment Reference Condition location-info Configuration NonEmergencyLocationInformati on ServingEcgi present Provision of information in the report is requested. NeighbouringEcgi present Provision of information in the report is requested. MbmsSaId not present Provision of information in the report is not requested. MbsfnArea not present Provision of information in the report is not requested. GeographicalCoordinate present minimumIntervalLength "25" the value in seconds EmergencyLocationInformation" ServingEcgi present Provision of information in the report is requested. NeighbouringEcgi present Provision of information in the report is requested. MbmsSaId not present Provision of information in the report is not requested. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 287 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.2-1 Information Element Value/remark Comment Reference Condition MbsfnArea not present Provision of information in the report is not requested. GeographicalCoordinate present Provision of information in the report is requested. minimumIntervalLength "30" the value in seconds TriggeringCriteria CellChange AnyCellChange TriggerID any value Table 6.3.1.3.3-3: SIP MESSAGE (Step 3, Table 6.3.1.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 Information Element Value/remark Comment Reference Condition Message-body MIME body not including MCPTT-Info and not including MCPTT- Affiliation-Command not including any MIME body part with Content- Type being "application/vnd.3gpp.m cptt-info+xml" or "application/vnd.3gpp.m cptt-affiliation- command+xml" MIME body part Location info ETSI TS 124 379 [4] (3GPP TS 24.379) clause F.3 MIME-part-headers Content-Type "application/vnd.3gpp.mcp tt-location-info+xml" MIME-part-body Location-info as described in Table 6.3.1.3.3-4 Table 6.3.1.3.3-4: Location-Info in SIP MESSAGE (Table 6.3.1.3.3-3) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.1-1 Information Element Value/remark Comment Reference Condition location-info Report TriggerID Same value as in the location configuration Value included in Table 6.3.1.3.3-2 CurrentLocation CurrentServingEcgi The E-UTRAN Cell Global Identification (ECGI) of Cell 2 NeighbouringEcgi The ECGI of Cell 1 CurrentCoordinate The location simulated by the GNSS simulator at the time of transmission of the message. longitude px_MCX_CoordinateLon gitude_Client_A (see note) latitude px_MCX_CoordinateLati tude_Client_A (see note) ReportType "NonEmergency" NOTE: Shall be encrypted as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.4.1-1A. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 288 6.3.2 MCPTT Server - MCPTT Client / Location / On-demand Location Information Request |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.2.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { IUT (MCPTT Server) requests to send a location reporting configuration } then { IUT (MCPTT Server) sends a SIP MESSAGE message containing the periodic trigger criteria and the minimum report interval to the SS-UE1 (MCPTT Client) } } (2) with { IUT (MCPTT Server) having received Location Information report } ensure that { when { IUT (MCPTT Server) requests to send an on-demand location report } then { IUT (MCPTT Server) sends a SIP MESSAGE message to the SS-UE1 (MCPTT Client) } } (3) with { IUT (MCPTT Server) having received Location Information report } ensure that { when { SS-UE1 (MCPTT Client) requests location report containing the location information report, the current location coordinates and the current serving ECGI by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.2.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379), clauses 13.2.3, 13.3.3, 13.3.4.1, 13.3.4.2. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core specification they have been copied from. Unless otherwise stated, these are Rel-13 requirements. [ETSI TS 124 379 [4] (3GPP TS 24.379) clause 13.2.3] "If the participating MCPTT function needs to request the MCPTT client to report its location, the participating MCPTT functions shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. The participating MCPTT function: 1) shall include a Request-URI set to the URI corresponding to the identity of the MCPTT client; 2) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [6]; 3) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-request-uri> element containing the MCPTT ID of the MCPTT user; 4) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Request> element contained in the <location-info> root element; 5) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and 6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]." [ETSI TS 124 379 [4] (3GPP TS 24.379) clause 13.3.3] "Upon receiving a SIP MESSAGE request containing 1) an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp- service.ims.icsi.mcptt"; 2) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 289 3) an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Request> element included in the <location-info> root element; then the MCPTT client: 1) shall send a location report as specified in clause 13.3.4; and 2) shall reset the minimumReportInterval timer." [ETSI TS 124 379 [4] (3GPP TS 24.379) clause 13.3.4.1] "… If the MCPTT client receives a location information request as specified in clause 13.3.3, the MCPTT client shall send a location report as specified in clause 13.3.4.2." [ETSI TS 124 379 [4] (3GPP TS 24.379) clause 13.3.4.2] "… If the MCPTT client does not need to send a SIP request for other reasons, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. The MCPTT client; 1) shall include in the Request-URI, the SIP URI received in the P-Asserted-Identity header field in the received SIP MESSAGE request for location report configuration; 2) shall include a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; 3) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body and in the <location-info> root element include: a) a <Report> element and if the Report was triggered by a location request include the <ReportID> attribute set to the value of the <RequestID> attribute in the received Request; b) a <TriggerId> child element set to the value of each <Trigger-Id> value of the triggers that have fired; and c) the location reporting elements corresponding to the triggers that have fired; 4) shall include an Accept-Contact header field with the media feature tag g.3gpp.mcptt along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [6]; 5) shall set the minimumReportInterval timer to the minimumReportInterval time and start the timer; 6) shall reset all triggers; and 7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]." |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.2.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.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). IUT: - IUT (MCPTT Server) ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 290 - 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. 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. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.2.3.2 Test procedure sequence | Table 6.3.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the MCPTT Server send a location reporting configuration to SS-UE1? (see note) - - - - 2 Check: Does the MCPTT Server correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to send a location reporting configuration message containing the periodic trigger criteria and the minimum report interval to SS-UE1? - - 1 P 3 Check: Does the MCPTT Server correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to send an on- demand location report request to SS-UE1? - - 2 P 4 Check: Does the MCPTT Server correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to send a location report from SS-UE1 containing the location information report, the current location coordinates, and the current serving ECGI? - - 3 P NOTE: This is expected to be done via a suitable implementation dependent MMI. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.3.2.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.3.1.3.3-1: SIP MESSAGE from the MCPTT Server (Step 2, Table 6.3.1.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT and LOCATION- CONFIG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-info as described in Table 6.3.1.3.3-2 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 291 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT and LOCATION- CONFIG Information Element Value/remark Comment Reference Condition MIME body part Location-info ETSI TS 124 379 [4] (3GPP TS 24.379) clause F.3 MIME-part-body Location-info as described in Table 6.3.1.3.3-3 Table 6.3.1.3.3-2: MCPTT-Info in SIP MESSAGE (Table 6.3.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [4] (3GPP TS 24.379) clause 13.2.2 mcptt-calling-user-id not present NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-1A. Table 6.3.1.3.3-3: Location-Info in SIP MESSAGE (Table 6.3.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.2-1 Information Element Value/remark Comment Reference Condition location-info Configuration NonEmergencyLocationInformati on ServingEcgi present Provision of information in the report is requested. NeighbouringEcgi present Provision of information in the report is requested. MbmsSaId not present Provision of information in the report is not requested. MbsfnArea not present Provision of information in the report is not requested. GeographicalCoordinate present minimumIntervalLength "25" the value in seconds EmergencyLocationInformation" ServingEcgi present Provision of information in the report is requested. NeighbouringEcgi present Provision of information in the report is requested. MbmsSaId not present Provision of information in the report is not requested. MbsfnArea not present Provision of information in the report is not requested. GeographicalCoordinate present Provision of information in the report is requested. minimumIntervalLength "30" the value in seconds TriggeringCriteria PeriodicReport ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 292 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.2-1 Information Element Value/remark Comment Reference Condition extension base "15" periodicity of the reports (in seconds) TiggerID any value Table 6.3.1.3.3-4: SIP MESSAGE from the MCPTT Server (Step 3, Table 6.3.1.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT and LOCATION- CONFIG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-info as described in Table 6.3.1.3.3-2 MIME body part Location-info ETSI TS 124 379 [4] (3GPP TS 24.379) clause F.3 MIME-part-body Location-info as described in Table 6.3.1.3.3-5 Table 6.3.1.3.3-5: Location-Info in SIP MESSAGE (Table 6.3.1.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.3-1 Table 6.3.1.3.3-6: SIP MESSAGE (Step 4, Table 6.3.1.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 Information Element Value/remark Comment Reference Condition Message-body MIME body not including MCPTT-Info and not including MCPTT-Affiliation- Command not including any MIME body part with Content-Type being "application/vnd.3gpp. mcptt-info+xml" or "application/vnd.3gpp. mcptt-affiliation- command+xml" MIME body part Location info ETSI TS 124 379 [4] (3GPP TS 24.379) clause F.3 MIME-part-headers Content-Type "application/vnd.3gpp.mcptt- location-info+xml" MIME-part-body Location-info as described in Table 6.3.1.3.3-7 Table 6.3.1.3.3-7: Location-Info in SIP MESSAGE (Table 6.3.1.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.1-1 Information Element Value/remark Comment Reference Condition location-info Report ReportID attribute "1" The same as the ID in the request message. ReportType attribute "NonEmergency" CurrentLocation CurrentServingEcgi The E-UTRAN Cell Global Identification (ECGI) of Cell 2 NeighbouringEcgi The ECGI of Cell 1 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 293 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.1-1 Information Element Value/remark Comment Reference Condition CurrentCoordinate The location simulated by the GNSS simulator at the time of transmission of the message. longitude px_MCX_CoordinateLon gitude_Client_A (see note latitude px_MCX_CoordinateLati tude_Client_A (see note) NOTE: Shall be encrypted as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.4.1-1A. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4 MBMS | 6.4.1 MCPTT Server - MCPTT Client / MBMS / MBMS Bearer Announcement / MBMS Bearer Listening Status / Transition to MBMS from Unicast / MBMS Floor Control / Transition to Unicast from MBMS |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCPTT Client) initiates establishment of a group call with automatic commencement mode and without implicit floor request } then { IUT (MCPTT Server) accepts the call from the initiator and establishes a pre-arranged group call } } (2) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { IUT (MCPTT Server) requests to send an MBMS bearer announcement to notify bearer availability } then { IUT (MCPTT Server) sends a SIP MESSAGE message to the SS-UE1 (MCPTT Client) } } (3) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { SS-UE1 (MCPTT Client) sends a MBMS Bearer listening status report by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (4) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { IUT (MCPTT Server) requests to send an MBMS bearer announcement to notify bearer availability } then { IUT (MCPTT Server) sends a SIP MESSAGE message to the SS-UE2 (MCPTT Client) } } ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 294 (5) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { SS-UE2 (MCPTT Client) sends a MBMS Bearer listening status report to notify listening general-purpose subchannel by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (6) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { the SS-UE1 (MCPTT client) requests to use MBMS subchannel for the conversation } then { IUT (MCPTT Server) sends a Map Group To Bearer message } } (7) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { SS-UE1 (MCPTT Client) sends a MBMS Bearer listening status report to notify listening audio and floor control subchannel by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (8) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { SS-UE2 (MCPTT Client) sends a MBMS Bearer listening status report to notify listening audio and floor control subchannel by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (9) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { IUT (MCPTT Server) requests to send floor Granted } then { IUT (MCPTT Server) sends a Floor Granted message with request for acknowledgement using unicast bearer } } (10) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { IUT (MCPTT Server) requests to set the explicit MuSiK key } then { IUT (MCPTT Server) sends a SIP MESSAGE message containing a MuSiK download message to the SS-UE1 (MCPTT Client) and to the SS-UE2 (MCPTT Client) } } (11) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { the SS-UE1(MCPTT Client) performs floor control interactions } then { IUT (MCPTT Server) respondes floor control (Floor Ack, Floor Idle) } } (12) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { the SS-UE1 (MCPTT client) stops using MBMS subchannel for the conversation } then { IUT (MCPTT Server) sends a Unmap Group To Bearer message } } ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 295 (13) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { SS-UE1 (MCPTT Client) sends a MBMS Bearer listening status report to stop notify listening audio and floor control subchannel by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (14) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { SS-UE2 (MCPTT Client) sends a MBMS Bearer listening status report to stop notify listening audio and floor control subchannel by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (15) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { IUT (MCPTT Server) requests to send an MBMS bearer cancellation announcement to notify bearer unavailability } then { IUT (MCPTT Server) sends a SIP MESSAGE message to the SS-UE1 (MCPTT Client) and to the SS-UE2 (MCPTT Client) } } (16) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { the SS-UE1 (MCPTT Client) sends MBMS Bearer listening status report message to MCPTT Server, to notify not being listening to general-purpose subchannel } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (17) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { the SS-UE2 (MCPTT Client) sends MBMS Bearer listening status report message to MCPTT Server, to notify not being listening to general-purpose subchannel } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (18) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and having stopped using a MBMS subchannel for the conversation } ensure that { when { the SS-UE1 (MCPTT client) sends Floor Request } then { IUT (MCPTT Server) replies with Floor Taken, Floor Idle, Floor Granted } } (19) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and having stopped using a MBMS subchannel for the conversation }} ensure that { when { the SS-UE1 (MCPTT client) ends the Pre-arranged group call } then { IUT (MCPTT Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the other participants } } ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 296 |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 14.2.2.2, 14.2.3, 14.3.3.1, ETSI TS 124 380 [5] (3GPP TS 24.380) clauses 10.2.2.2, 10.2.3.2, 10.2.3.3, 10.2.3.4, 10.2.3.5, 10.2.3.11, 10.2.3.12, 6.3.4.3.3, 6.3.4.4.2, 6.3.4.4.6. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core specification they have been copied from. Unless otherwise stated these are Rel-13 requirements. [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 14.2.2.2] "For each MCPTT client that the participating MCPTT function is sending an MBMS bearer announcement to, the participating MCPTT function: 1) shall generate an SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]; 2) shall set the Request-URI to the URI received in the To header field in a third-party SIP REGISTER request; 3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6]; 4) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt"; 5) shall include one application/sdp MIME body conforming to 3GPP TS 24.229 [4], where the application/sdp MIME body: a) shall include the Content-Disposition header field with the value "render"; b) should include one or more "m=audio" media lines and media line attributes as defined in 3GPP TS 24.380 [5] to be used as the MBMS subchannel for audio and media control. Additionally, the participating MCPTT function: i) shall set c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the ".invalid" DNS top-level domain, if IPv6; ii) shall set port number of the media line to 9; ii) shall include the "a=rtcp-mux" attribute as specified in IETF RFC 5761 [39]; and iii) shall include the "a=rtcp:9" as specified in IETF RFC 5761 [39]. c) should include one or more "m=audio" media lines and media line attributes as defined in 3GPP TS 24.380 [5] to be used as the MBMS subchannel for audio only. Additionally, the participating MCPTT function: i) shall set the c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the ".invalid" DNS top-level domain, if IPv6; and ii) shall set the port number of the media line to 9; NOTE 1: If an MBMS subchannel for audio only is included, the "a=rtcp-mux" and "a=rtcp:" attributes are not included in the media line. d) shall include one "m=application" media line as defined in 3GPP TS 24.380 [5] to be used as the general purpose MBMS subchannel. The media line shall include a valid multicast IP address and a valid port number. If the protection of MBMS subchannel control messages sent over the general purpose MBMS subchannel of the MBMS bearer is required, the participating MCPTT function also includes an "a=key-mgmt" media-level attribute. The participating MCPTT function: i) shall encrypt the MSCCK to a UID associated to the targeted MCPTT ID and a time related parameter as described in 3GPP TS 33.180 [78]; ii) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated MSCCK and MSCCK-ID as specified in 3GPP TS 33.180 [78]; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 297 iii) shall add the public service identity of the participating MCPTT function to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78]; iv) shall sign the MIKEY-SAKKE I_MESSAGE using the public service identity of the participating MCPTT function signing key provided in the keying material together with a time related parameter, and add this to the MIKEY-SAKKE payload, as described in 3GPP TS 33.180 [78]; and v) shall include the "mikey" key management and protocol identifier and the signed MIKEY-SAKKE I_MESSAGE in the value of the a=key-mgmt" media-level attribute according to IETF RFC 4567 [47]; and NOTE 2: The media parameters to be used by the MBMS subchannel for media is included in the Map Group To Bearer message defined in 3GPP TS 24.380 [5] and not included in this application/sdp MIME body. e) if "m=audio" media lines to be used in an MBMS subchannel for audio only are included above, shall include one or more "m=application" media line as defined in 3GPP TS 24.380 [5] to be used as the MBMS subchannel for floor control messages. The media line: i) shall set c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the ".invalid" DNS top-level domain, if IPv6; and ii) shall set the port number of the media line to 9; NOTE 3: The use of a separate MBMS subchannel for floor control is optional. When a separate MBMS subchannel for floor control is not used, floor control messages are sent in the MBMS subchannel for media. 6) shall include an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body defined in clause F.2 with the <version> element set to "1" and one or more <announcement> elements associated with the pre-activated MBMS bearers. Each set of an <announcement> element: a) shall include a TMGI value in the <TMGI> element; NOTE 4: The same TMGI value can only appear in one <announcement> element. The TMGI value is also used to identify the <announcement> when updating or cancelling the <announcement> element. NOTE 5: The security key active for the general purpose MBMS subchannel on which the mapping (i.e. the Map Group To Bearer message) of media or media control to this MBMS bearer was indicated, is used for MBMS subchannels on this MBMS bearer, unless a different key or an indication of not using encryption is in place. b) shall include the QCI value in the <QCI> element; c) if multiple carriers are supported, shall include the frequency to be used in the <frequency> element; NOTE 6: In the current release if the <frequency> element is included, the frequency in the <frequency> element is the same as the frequency used for unicast. d) shall include one or more MBMS service area IDs in <mbms-service-area-id> elements in the <mbms- service-areas> element; NOTE 7: Initial mappings of groups to MBMS subchannels on an MBMS bearer for the purpose of carrying media or media control can occur only where the MBMS service area for this bearer and the MBMS service area for the bearer carrying the general purpose MBMS subchannel on which the Map Group To Bearer message is sent intersect. However, once media or media control were successfully mapped to this bearer, the reception by the MCPTT client can continue (until Unmap Group To Bearer is received or until timeout) throughout the entire MBMS service area of this bearer. e) may include the <report-suspension> element and set it to "true" value or the "false" value; NOTE 8: The participating function can choose to direct some clients not to send an MBMS bearer suspension report when notified by RAN, by including the <report-suspension> element set to "false". The purpose is to prevent an avalanche of identical reports sent by clients roughly at the same time, to report the suspension of the same MBMS bearer. The way the participation function determines which clients are to send or not to send the report is outside the scope of the present document. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 298 f) if the MBMS bearer is carrying the general purpose MBMS subchannel, shall include one <GPMS>element, giving the number of the "m=application" media line in the application/sdp MIME body generated in step 5 above to be used for the general purpose MBMS subchannel; and g) if the packet headers are compressed with ROHC specified in RFC 5795 [80] in this MBMS bearer, the <anyExt> element in the <announcement> element in the <mcptt-mbms-usage-info> element shall include the <mcptt-mbms-rohc> element defined in clause F.2.3. 7) shall include the MBMS public service identity of the participating MCPTT function in the P-Asserted-Identity header field; 8) shall include in a MIME body with Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml", the <mcptt-request-uri> element set to the MCPTT ID of the user; and 9) shall send the SIP MESSAGE request towards the MCPTT client according to 3GPP TS 24.229 [4]." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 14.2.3] "Upon receiving a "SIP MESSAGE request for an MBMS listening status update", the participating MCPTT function shall handle the request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. If the SIP MESSAGE request contains: 1) an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body with an <mbms-listening-status> element; and 2) an application/vnd.3gpp.mcptt-info+xml MIME body containing an MCPTT ID in the <mcptt-request-uri> served by the participating MCPTT function; then the participating MCPTT function: 1) shall verify that the public user identity in the P-Asserted-Identity header field is bound to the MCPTT ID in the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body, and if that is the case: a) if the <mbms-listening-status> element is set to "listening": i) if a <session-id> element is included, shall indicate to the media plane that the MCPTT client in the session identified by the <session-id> element is now listening to the MBMS subchannel; and ii) if <general-purpose> element is included with the value "true", shall indicate to the media plane that the MCPTT client is now listening to the general purpose MBMS subchannel; and b) if the <mbms-listening-status> element is set to "not-listening": i) if a <session-id> element is included, shall indicate to the media plane that the MCPTT client in the sessions identified by the <session-id> elements is not listening to the MBMS subchannel; ii) if <general-purpose> element is included with the value "false", shall indicate to the media plane that the MCPTT client is no longer listening to the general purpose MBMS bearer; and iii) shall interact with the media plane as specified in 3GPP TS 24.380 [5]. NOTE 1: If the MCPTT client reports that the MCPTT client is no longer listening to the general purpose MBMS subchannel it is implicitly understood that the MCPTT client no longer listens to any MBMS subchannel in ongoing conversations that the MCPTT client previously reported status "listening". …" [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 14.3.3.1] "If one of the following conditions is fulfilled: 1) if the MCPTT client: a) receives a Map Group To Bearer message over the general purpose MBMS channel; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 299 b) participates in a group session identified by the Map Group To Bearer message; and c) the status "listening" is not already reported; or 2) if the MCPTT client: a) receives an announcement as described in clause 14.3.2; b) enters an MBMS service area where a general purpose MBMS is available; and c) experiences good MBMS bearer radio condition; then the MCPTT client shall report that the MCPTT client is listening to the MBMS bearer as specified in clause 14.3.3.2. If one of the following conditions is fulfilled: 1) if the MCPTT client: a) receives an MBMS bearer announcement as described in the clause 14.3.2; b) the MBMS bearer announcement contains a cancellation of an <announcement> element identified by the same TGMI value as received in a Map Group To Bearer message in an ongoing conversation; and c) the status "not-listening" is not already reported; 2) if the MCPTT client: a) receives an MBMS bearer announcement as described in the clause 14.3.2; b) the MBMS bearer announcement contains a cancellation of an <announcement> element; c) does not participate in an ongoing conversation; d) the MCPTT client has reported the "listening" status due to the availability of the general purpose MBMS subchannel in the <announcement> element; and e) the status "not-listening" is not already reported; or 3. if the MCPTT client: a) suffers from bad MBMS bearer radio condition, then the MCPTT client shall report that the MCPTT client is not listening to the MBMS subchannels as specified in clause 14.3.3.2. …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.2.2] "Upon receiving a Floor Request message or a Floor Taken message and when the participating MCPTT function decides that an MBMS subchannel shall be used for a conversation in an ongoing group session, the participating MCPTT function needs to determine if the MBMS bearer has sufficient capacity for the new conversation. If the new MBMS bearer has sufficient capacity the participating MCPTT function: NOTE: The participating MCPTT function can take that decision when receiving the first Floor Request from a floor participant or when receiving a Floor Taken message destined to one of the floor participants served by the participating MCPTT client. 1. shall create an instance of the 'Participating MCPTT function MBMS subchannel control' state machine; 2. shall send a Map Group To Bearer message over the general purpose MBMS subchannel. The Map Group To Bearer message: a. shall include TMGI; b. shall include the identifier of the media stream; and ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 300 c. shall include the MCPTT Group identifier field; 3. shall start timer T15 (Conversation); 4. shall start timer T16 (Unmap Group To Bearer); 5. shall enter the 'M: A conversation is active' state; 6. if the Floor Request was received, shall perform actions as described in subclause 6.4.2; and 7. if the Floor Taken was received, shall perform the actions described in subclause 10.2.3.3. If the MBMS bearer does not have sufficient capacity for the new conversation the participating MCPTT function: 1. may free capacity for the new conversation by transfering an existing conversation over an MBMS bearer to unicast bearers following the procedure in subclause 10.2.3.12; or 2. may use the MBMS bearer for the signaling messages, while using unicast bearers for the media message." [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.2] "When a Floor Idle message destined to a floor participant listening to the MBMS subchannel is received, the participating MCPTT function: 1. shall for each received Floor Idle message, check if there is a stored message-sequence-number value associated with the conversation; 2. if a message-sequence-number value associated with the conversation is stored, compared the value of the stored message-sequence-number value with the value in the received Floor Idle message; a. if the received message-sequence-number value is higher than the stored value: i. shall replace the stored message-sequence-number value with the received message-sequence- number field; ii. shall set the acknowledgment bit to '0' as specified in subclause 8.2.2, if not already set; and iii. shall send the received Floor Idle message over the MBMS subchannel; and b. if the received message-sequence-number value is lower or the same as the stored value, shall discard the received Floor Idle message; 3. if a message-sequence-number value associated with the conversation is not stored (i.e. this is the first floor control message received in the conversation): a. shall store the received message-sequence-number value and associate the value with the conversation; b. shall set the acknowledgment bit to '0' as specified in subclause 8.2.2, if not already set; and c. shall send the received Floor Idle message over the MBMS subchannel; …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.3] "When a Floor Taken message destined to a floor participant listening to the MBMS subchannel is received, the participating MCPTT function: 1. shall for each received Floor Taken message, check if there is a stored message-sequence-number value associated with the conversation; 2. if a message-sequence-number value associated with the conversation is stored, compare the value of the stored message-sequence-number value with the value in the received Floor Taken message; a. if the received message-sequence-number value is higher than the stored value: i. shall replace the stored message-sequence-number value with the received message-sequence- number field; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 301 ii. shall set the acknowledgment bit to '0' as specified in subclause 8.2.2, if not already set; and iii. shall send the received Floor Taken message over the MBMS subchannel; and b. if the received message-sequence-number value is lower or the same as the stored value, shall discard the received Floor Taken message; 3. if a message-sequence-number value associated with the conversation is not stored (i.e. this is the first floor control message received in the conversation): a. shall store the received message-sequence-number value and associate the value with the conversation; b. shall set the acknowledgment bit to '0' as specified in subclause 8.2.2, if not already set; and c. shall send the received Floor Taken message over the MBMS subchannel; 4. if the received Floor Taken message indicates that a Floor Ack message is expected (i.e. the acknowledgment bit is set to '1' as specified in subclause 8.2.2), shall send a Floor Ack message towards the controlling MCPTT function The Floor Ack message: a. shall include the Message Type field set to '2' (Floor Taken); and b. shall include the Source field set to '1' (participating MCPTT function is the source); …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.4] "When a floor control message other than the Floor Idle and Floor Taken message is received from a floor participant or received from the floor control server, the participating MCPTT function: 1. shall forward the floor control message as specified in subclause 6.4; …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.5] "When receiving a RTP media packet destined to one of the MCPTT client listening to the MBMS subchannel, the participating MCPTT function: NOTE: An RTP media packet not destined to an MCPTT client listening to the MBMS subchannel is forwarded to the MCPTT client over the unicast bearer. 1. shall check if the media packet is already sent over the MBMS subchannel or not; 2. if the RTP media packet is already sent over the MBMS subchannel, shall discard the RTP media packet; 3. if the RTP media packet is not already sent over the MBMS sub channel, shall instruct the media distribution function to send the RTP media packet over the MBMS subchannel; …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.11] "If the control and signalling plane indicates that the group call session is released, the participating MCPTT function: 1. shall send the Unmap Group To Bearer message over the MBMS subchannel. The Unmap Group To Bearer message: a. shall include the MCPTT Group ID field; 2. shall stop timer T15 (Conversation), timer T16 (Map Group To Bearer) and timer T17 (Unmap Group To Bearer), if running; and 3. shall release the instance of the 'Participating MCPTT function MBMS subchannel management' state machine used for the conversation." ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 302 [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.12] "If the participating MCPTT server decides that an ongoing conversation over an MBMS bearer shall start using unicast bearers, the participating MCPTT function may send an Application Paging message over the MBMS subchannel associated with this conversation. NOTE: The Application Paging message can be sent at the same time as the conversation is started using unicast bearers, this will improve the MCPTT access time since the Application Paging message in most cases will reach the client quicker than using normal paging procedures." [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 6.3.4.3.3] "Upon receiving a floor request message (from a floor participant that is permitted to make a floor request) the floor control arbitration logic in the floor control server: … 3. if the floor request is granted the floor control server: … e. shall enter the 'G: Floor Taken' state as specified in the subclause 6.3.4.4.2." [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 6.3.4.4.2] "When entering this state the floor control arbitration logic in the floor control server: 1. shall send a Floor Granted message to the floor participant to which the floor is granted. The Floor Granted message: a. shall include the value of timer T2 (Stop talking)in the Duration field; b. shall include the granted priority in the Floor priority field; … 3. shall send Floor Taken message to all other floor participants. The Floor Taken message: a. if the floor is currently granted only to one particpant: i shall include the granted MCPTT user's MCPTT ID in the Granted Party's Identity field, if privacy is not requested; ii. may include the functional alias of the granted MCPTT user in the Functional Alias field, if privacy is not requested; and iii. shall include the Location field: A. if the current location of the talker is not available or is not to be reported according to the MCPTT user profile, then the location type is set to '0' (Not provided); or B. if the current location of the talker is available and may be reported according to the MCPTT user profile, then the location type and location value are set as specified in table 8.2.3.21-3; …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 6.3.4.4.6] "Upon receiving a Floor Release message the floor control arbitration logic in the floor control server: 1. shall request the media distributor in the MCPTT server to stop forwarding RTP media packets received from the participant that sent the Floor Release message; … 4. if mutli-talker floor control is not supported shall enter the 'G: Floor Idle' state as specified in the subclause 6.3.4.3.2; and" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 303 |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) and SS-UE2 (MCPTT client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client) 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. 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. - SS-UE1 (MCPTT client) and SS-UE2 (MCPTT client) are affiliated to the Prearranged group. - The IUT (MCPTT Server) is the controlling server of the Prearranged group. - A pre-activated MBMS bearer exists. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.3.2 Test procedure sequence | Table 6.4.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCPTT client) requests the establishment of a group call to SS-UE2 (MCPTT client) with automatic commencement mode and without implicit floor request. - - - - 2 Check: Does the MCPTT server correctly perform procedure 'MCPTT E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to establish a pre- arranged group call with automatic commencement mode and without implicit floor control according to option a of note in Annex A, Table A.3.1.3-1? - - 1 P 3 Make the MCPTT Server activate an MBMS bearer and send an MBMS bearer announcement to notify bearer availability (see note) - - - - ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 304 St Procedure Message Sequence TP Verdict U - S Message - EXCEPTION: Depending on the MCPTT Server implementation, steps 4a-4d and steps 5a-5d might be performed in parallel - - - - 4a Check: Does the MCPTT Server send an MBMS bearer announcement to notify MBMS bearer availability to SS-UE1? <-- SIP MESSAGE 2 P 4b The SS-UE1 (MCPTT client) responds with a SIP 200 (OK) message to MCPTT Server --> SIP 200 (OK) - - 4c The SS-UE1 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify being listening to general-purpose subchannel --> SIP MESSAGE - - 4d Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE1? <-- SIP 200 (OK) 3 P 5a Check: Does the MCPTT Server send an MBMS bearer announcement to notify MBMS bearer availability to SS-UE2? <-- SIP MESSAGE 4 P 5b The SS-UE2 (MCPTT client) responds with a SIP 200 (OK) message to MCPTT Server --> SIP 200 (OK) - - 5c The SS-UE2 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify being listening to general-purpose subchannel. --> SIP MESSAGE - - 5d Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE2? <-- SIP 200 (OK) 5 P 6 The SS-UE1 (MCPTT client) sends a Floor Request message to MCPTT Server --> Floor Request - - 7 Make the MCPTT Server use MBMS subchannel for the conversation (see note) - - - - 8 Check: Does the MCPTT Server send a Map Group To Bearer message over general purpose MBMS subchannel? <-- Map Group To Bearer 6 P 9 The SS-UE1 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify being listening to audio and floor control over MBMS subchannel --> SIP MESSAGE - - 10 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE1? <-- SIP 200 (OK) 7 P 11 The SS-UE2 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify being listening to audio and floor control over MBMS subchannel --> SIP MESSAGE - - 12 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE2? <-- SIP 200 (OK) 8 P 13 Check: Does the MCPTT Server send a Floor Granted message with request for acknowledgement using unicast bearer to SS- UE1? <-- Floor Granted 9 P 14 The SS-UE1 (MCPTT client) responds with a Floor Ack message to MCPTT Server --> Floor Ack - - - EXCEPTION: Depending on the MCPTT Server implementation, steps 15a-15b and steps 16a- 16b might be performed in parallel - - - - 15a Check: Does the MCPTT Server send a message containing a MuSiK download message to set the explicit MuSiK key to be used for the floor control encryption over the MBMS subchannel to SS-UE1? <-- SIP MESSAGE 10 P 15b The SS-UE1 (MCPTT client) responds with a SIP 200 (OK) to MCPTT Server --> SIP 200 (OK) - - ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 305 St Procedure Message Sequence TP Verdict U - S Message 16a Check: Does the MCPTT Server send a message containing a MuSiK download message to set the explicit MuSiK key to be used for the floor control encryption over the MBMS subchannel to SS-UE2? <-- SIP MESSAGE 10 P 16b The SS-UE2 (MCPTT client) responds with a SIP 200 (OK) to MCPTT Server --> SIP 200 (OK) - - 17 Check: Does the MCPTT Server send a Floor Taken message using multicast bearer? <-- Floor Taken 11 P 18 The SS-UE1 (MCPTT client) sends a Floor Release message to MCPTT Server --> Floor Release - - 19 Check: Does the MCPTT Server send a Floor Idle message using multicast bearer? <-- Floor Idle 11 P 20 Make the MCPTT Server stop using MBMS subchannel for the conversation (Note) - - - - 21 Check: Does the MCPTT Server send an Unmap Group To Bearer message over general purpose MBMS subchannel? <-- Unmap Group To Bearer 12 P 22 The SS-UE1 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify not being listening to audio and floor control over MBMS subchannel --> SIP MESSAGE - - 23 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE1? <-- SIP 200 (OK) 13 P 24 The SS-UE2 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify not being listening to audio and floor control over MBMS subchannel --> SIP MESSAGE - - 25 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE2? <-- SIP 200 (OK) 14 P 26 Make the MCPTT Server stop using MBMS bearer - - - - - EXCEPTION: Depending on the MCPTT Server implementation, steps 27a-27b and steps 28a- 28b might be performed in parallel - - - - 27a Check: Does the MCPTT Server send a MESSAGE containing the MBMS bearer cancellation announcement for the SS-UE1 (MCPTT client)? <-- SIP MESSAGE 15 P 27b The SS-UE1 (MCPTT client) responds with a SIP 200 (OK) to MCPTT Server --> SIP 200 (OK) - - 28a Check: Does the MCPTT Server send a MESSAGE containing the MBMS bearer cancellation announcement for the SS-UE2 (MCPTT client)? <-- SIP MESSAGE 15 P 28b The SS-UE2 (MCPTT client) responds with a SIP 200 (OK) to MCPTT Server --> SIP 200 (OK) - - 29 The SS-UE1 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify not being listening to general-purpose subchannel --> SIP MESSAGE - - 30 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE1? <-- SIP 200 (OK) 16 P 31 The SS-UE2 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify not being listening to general-purpose subchannel --> SIP MESSAGE - - 32 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE2? <-- SIP 200 (OK) 17 P 33 The SS-UE1 (MCPTT client) sends a Floor Request message to MCPTT Server --> Floor Request - - 34 Check: Does the MCPTT Server send a Floor Granted message with request for acknowledgement using unicast to SS-UE1? <-- Floor Granted 18 P ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 306 St Procedure Message Sequence TP Verdict U - S Message 35 The SS-UE1 (MCPTT client) responds with a Floor Ack message to MCPTT Server --> Floor Ack - - 36 Check: Does the MCPTT Server send a Floor Taken message with request for acknowledgement using unicast bearer to SS- UE2? <-- Floor Taken 18 P 37 The SS-UE2 (MCPTT client) responds with a Floor Ack message to MCPTT Server --> Floor Ack - - 38 The SS-UE1 (MCPTT client) sends a Floor Release message to MCPTT Server --> Floor Release - - 39 Check: Does the MCPTT Server send a Floor Idle message with request for acknowledgement using unicast bearer to SS- UE1? <-- Floor Idle 18 P 40 The SS-UE1 (MCPTT client) responds with a Floor Ack message to MCPTT Server --> Floor Ack - - 41 Check: Does the MCPTT Server send a Floor Idle message with request for acknowledgement using unicast bearer to SS- UE2? <-- Floor Idle 18 P 42 The SS-UE1 (MCPTT client) responds with a Floor Ack message to MCPTT Server --> Floor Ack - - 43 The SS-UE1 (MCPTT client) releases the call. - - - - 44 Check: Does the MCPTT server correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 19 P NOTE: This is expected to be done via a suitable implementation dependent MMI. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.4.1.3.3-1: SIP MESSAGE from the MCPTT Server (Step 4a, Table 6.4.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT Information Element Value/remark Comment Reference Condition P-Asserted-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcptt" P-Asserted-Identity addr-spec px_MBMS_Service_ID URI of the participating MCPTT function Message-body MIME body part SDP message MIME-part-headers Content-Type "application/sdp" Content-Disposition "render" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.2.2.2 MIME-part-body SDP message as described in Table 6.4.1.3.3-2 MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcptt- mbms-usage-info+xml" MIME-part-body MCPTT-MBMS-Usage-Info as described in Table 6.4.1.3.3-3 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 307 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT Information Element Value/remark Comment Reference Condition MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.1.3.3-4 Table 6.4.1.3.3-2: SDP in SIP MESSAGE (Table 6.4.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1 Information Element Value/remark Comment Reference Condition Media descriptions media description m= line media = audio media "audio" port "9" proto "RTP/AVP" fmt "99" Connection Data c= line nettype "IN" addrtype "IP4" or "IP6" depending on IP address connection-address "0.0.0.0" (IPv4) or domain name within ".invalid" DNS top level domain (IPv6) media attribute a= line attribute = rtcp-mux rtcp-mux "rtcp-mux" media attribute a= line attribute = rtcp rtcp "rtcp" port "9" media description m= line media = application media "application" port "9" proto "udp" fmt "MCPTT" Connection Data c= line nettype "IN" addrtype "IP4" or "IP6" depending on IP address connection-address "0.0.0.0" (IPv4) or domain name within ".invalid" DNS top level domain (IPv6) media description m= line media = application media "application" port port number assigned by the MCPTT Server proto "udp" fmt "MCPTT" Connection Data c= line nettype "IN" addrtype "IP4" connection-address multicast IP assigned by the MCPTT Server media attribute a= line attribute = key-mgmt ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 308 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1 Information Element Value/remark Comment Reference Condition key-mgmt ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.2.2.2 mikey MIKEY-SAKKE I_MESSAGE as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.9.1- 4. MSCCK distribution as specified in ETSI TS 133 180 [31] (3GPP TS 33.180), Annex H Table 6.4.1.3.3-3: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.1.3.3-1) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status not present announcement TMGI MBMS Service ID "0F0F0F" The selected value is randomly chosen - a 6 digit hexadecimal number between 000000 and FFFFFF (see TS 23.003 [X] clause 15.2. The coding of the MBMS Service ID is the responsibility of each administration MCC The same value as for PLMN1 Mobile Country Code MNC The same value as for PLMN1 Mobile Network Code QCI "65" Mission Critical user plane Push To Talk voice mbms-service-areas "0" The selected value is randomly chosen. The value 0 has a special meaning; it shall denote the whole PLMN as the MBMS Service Area GPMS "2" The number of the "m=application" media line in the application/sdp MIME version "1" Table 6.4.1.3.3-4: MCPTT-Info in SIP MESSAGE (Table 6.4.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.2.2.2 mcptt-calling-user-id not present NOTE: Encrypted element as described in Table 5.5.3.2.1-1A. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 309 Table 6.4.1.3.3-5: SIP MESSAGE from the MCPTT Server (Step 5a, Table 6.4.1.3.2-1) Derivation Path: Table 6.4.1.3.3-1 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.1.3.3-6 Table 6.4.1.3.3-6: MCPTT-Info in SIP MESSAGE (Table 6.4.1.3.3-5) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_B ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.2.2.2 mcptt-calling-user-id not present NOTE: Encrypted element as described in Table 5.5.3.2.1-1A. Table 6.4.1.3.3-7: SIP MESSAGE from the SS-UE1 (Step 4c, Table 6.4.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCPTT Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (px_MBMS_Service_ID) Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcptt- mbms-usage-info+xml" MIME-part-body MCPTT-MBMS-Usage-Info as described in Table 6.4.1.3.3-8 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.1.3.3-9 Table 6.4.1.3.3-8: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.1.3.3-7) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status mbms-listening-status "listening" session-id not present general-purpose "true" TMGI same value as the announcement in the SIP MESSAGE of Table 6.4.1.3.3-3 announcement not present version "1" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 310 Table 6.4.1.3.3-9: MCPTT-Info in SIP MESSAGE (Table 6.4.1.3.3-7) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.3.3.2 mcptt-calling-user-id not present NOTE: Encrypted element as described in Table 5.5.3.2.1-1A. Table 6.4.1.3.3-10: SIP MESSAGE from the SS-UE2 (Step 5c, Table 6.4.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCPTT Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (px_MBMS_Service_ID) Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcptt- mbms-usage-info+xml" MIME-part-body MCPTT-MBMS-Usage-Info as described in Table 6.4.1.3.3-8 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.1.3.3-11 Table 6.4.1.3.3-11: MCPTT-Info in SIP MESSAGE (Table 6.4.1.3.3-10) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_B ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.3.3.2 mcptt-calling-user-id not present NOTE: Encrypted element as described in Table 5.5.3.2.1-1A. Table 6.4.1.3.3-12: SIP MESSAGE from the SS-UE1 (Step 9, Table 6.4.1.3.2-1) Derivation Path: Table 6.4.1.3.3-7 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcptt- mbms-usage-info+xml" MIME-part-body MCPTT-MBMS-Usage-Info as described in Table 6.4.1.3.3-13 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 311 Table 6.4.1.3.3-13: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.1.3.3-12) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status mbms-listening-status "listening" session-id px_session_A_ID general-purpose not present TMGI same value as the announcement in the SIP MESSAGE announcement not present version "1" Table 6.4.1.3.3-14: SIP MESSAGE from the SS-UE2 (Step 11, Table 6.4.1.3.2-1) Derivation Path: Table 6.4.1.3.3-10 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcptt- mbms-usage-info+xml" MIME-part-body MCPTT-MBMS-Usage-Info as described in Table 6.4.1.3.3-13 Table 6.4.1.3.3-15: SIP MESSAGE from the MCPTT Server (Steps 15a and 16a, Table 6.4.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT Information Element Value/remark Comment Reference Condition P-Asserted-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcptt" P-Asserted-Identity addr-spec px_MBMS_Service_ID URI of the participating MCPTT function Message-body not including any MIME body part other than the ones described below MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcptt- mbms-usage-info+xml" MIME-part-body MCPTT-MBMS-Usage-Info as described in Table 6.4.1.3.3- 16 MIME body part MIKEY message MIME-part-headers Content-Type "application/mikey" MIME-part-body As described in ETSI TS 136 579-1 [1] (3GPP TS 36.579- 1), Table 5.5.9.1-5. MIKEY message containing the MuSiK ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 312 Table 6.4.1.3.3-16: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.1.3.3-15) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status not present announcement not present version "1" anyExt mbms-explicitMuSiK-download group px_MCPTT_Group_ A_ID Table 6.4.1.3.3-17: SIP MESSAGE from the SS-UE1 (Step 22, Table 6.4.1.3.2-1) Derivation Path: Table 6.4.1.3.3-7 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.m cptt-mbms-usage- info+xml" MIME-part-body MCPTT-MBMS-Usage- Info as described in Table 6.4.1.3.3-18 Table 6.4.1.3.3-18: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.1.3.3-17) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status mbms-listening-status "not-listening" session-id px_sesson_A_ID general-purpose not present TMGI same value as the announcement in the SIP MESSAGE announcement not present version "1" Table 6.4.1.3.3-19: SIP MESSAGE from the SS-UE2 (Step 24, Table 6.4.1.3.2-1) Derivation Path: Table 6.4.1.3.3-10 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.m cptt-mbms-usage- info+xml" MIME-part-body MCPTT-MBMS-Usage- Info as described in Table 6.4.1.3.3-18 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 313 Table 6.4.1.3.3-20: SIP MESSAGE from the MCPTT Server (Step 27a, Table 6.4.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT Information Element Value/remark Comment Reference Condition P-Asserted-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcptt" P-Asserted-Identity addr-spec px_MBMS_Service_ID URI of the participating MCPTT function Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcptt- mbms-usage-info+xml" MIME-part-body MCPTT-MBMS-Usage-Info as described in Table 6.4.1.3.3-21 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.1.3.3-4 Table 6.4.1.3.3-21: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.1.3.3-20) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status not present announcement TMGI MBMS Service ID "0F0F0F" The selected value is randomly chosen - a 6 digit hexadecimal number between 000000 and FFFFFF (see TS 23.003 [X] clause 15.2. The coding of the MBMS Service ID is the responsibility of each administration MCC The same value as for PLMN1 Mobile Country Code MNC The same value as for PLMN1 Mobile Network Code QCI "65" Mission Critical user plane Push To Talk voice mbms-service-areas not present GPMS not present version "1" Table 6.4.1.3.3-22: SIP MESSAGE from the MCPTT Server (Step 28a, Table 6.4.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT Information Element Value/remark Comment Reference Condition P-Asserted-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcptt" P-Asserted-Identity addr-spec px_MBMS_Service_ID URI of the participating MCPTT function ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 314 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.m cptt-mbms-usage- info+xml" MIME-part-body MCPTT-MBMS-Usage- Info as described in Table 6.4.1.3.3-21 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.1.3.3-6 Table 6.4.1.3.3-23: SIP MESSAGE from the SS-UE1 (Step 29, Table 6.4.1.3.2-1) Derivation Path: Table 6.4.1.3.3-7 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.m cptt-mbms-usage- info+xml" MIME-part-body MCPTT-MBMS-Usage- Info as described in Table 6.4.1.3.3-24 Table 6.4.1.3.3-24: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.1.3.3-23) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status mbms-listening-status "not-listening" session-id not present general-purpose "false" TMGI same value as the announcement in the SIP MESSAGE announcement not present version "1" Table 6.4.1.3.3-25: SIP MESSAGE from the SS-UE2 (Step 31, Table 6.4.1.3.2-1) Derivation Path: Table 6.4.1.3.3-10 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.m cptt-mbms-usage- info+xml" MIME-part-body MCPTT-MBMS-Usage- Info as described in Table 6.4.1.3.3-24 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 315 Table 6.4.1.3.3-26: SIP INVITE from the SS-UE1 (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, condition GROUP-CALL Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.4.1.3.3-26A MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.1.3.3-26B Table 6.4.1.3.3-26A: SDP in SIP INVITE from the SS-UE1 (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-2, with conditions GROUP-CALL Table 6.4.1.3.3-26B: MCPTT-Info in SIP INVITE from the SS-UE1 (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-3, with conditions GROUP-CALL Table 6.4.1.3.3-27: SIP INVITE from the MCPTT Server (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, condition GROUP-CALL Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.4.1.3.3-27A MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.1.3.3-27B Table 6.4.1.3.3-27A: SDP in SIP INVITE from the MCPTT Server (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-5, with conditions GROUP-CALL Table 6.4.1.3.3-27B: MCPTT-Info in SIP INVITE from the MCPTT Server (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-6, with conditions GROUP-CALL Table 6.4.1.3.3-28: SIP 200 (OK) from the SS-UE2 (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7, with conditions GROUP-CALL Information Element Value/remark Comment Reference Condition Message-body SDP Message As described in Table 6.4.1.3.3-28A ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 316 Table 6.4.1.3.3-28A: SDP in SIP 200 (OK) from the SS-UE2 (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-8, with conditions GROUP-CALL Table 6.4.1.3.3-29: SIP 200 (OK) from the MCPTT Server (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9, with conditions GROUP-CALL Information Element Value/remark Comment Reference Condition Message-body SDP Message As described in Table 6.4.1.3.3-29A Table 6.4.1.3.3-29A: SDP in SIP 200 (OK) from the MCPTT Server (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-10, with conditions GROUP-CALL Table 6.4.1.3.3-30: Floor Granted (Steps 13 and 34, Table 6.4.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.3-1, with conditions ACK Table 6.4.1.3.3-31: Floor Taken (Step 36, Table 6.4.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.7-1, with conditions ACK Table 6.4.1.3.3-32: Floor Idle (Steps 39 and 41, Table 6.4.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.6-1, with conditions ACK |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2 MCPTT Server - MCPTT Client / MBMS / Multi Talker | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.1 Test Purpose (TP) | (1) with { IUT (MCPTT Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCPTT Client) initiates establishment of a group call with automatic commencement mode and without implicit floor request } then { IUT (MCPTT Server) accepts the call from the initiator and establishes a pre-arranged group call } } (2) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { IUT (MCPTT Server) requests to send an MBMS bearer announcement to notify bearer availability } then { IUT (MCPTT Server) sends a SIP MESSAGE message to the SS-UE1 (MCPTT Client) } } (3) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { SS-UE1 (MCPTT Client) sends a MBMS Bearer listening status report by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 317 (4) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { IUT (MCPTT Server) requests to send an MBMS bearer announcement to notify bearer availability } then { IUT (MCPTT Server) sends a SIP MESSAGE message to the SS-UE2 (MCPTT Client) } } (5) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { SS-UE2 (MCPTT Client) sends a MBMS Bearer listening status report to notify listening general-purpose subchannel by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (6) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { the SS-UE1 (MCPTT client) requests to use MBMS subchannel for the conversation } then { IUT (MCPTT Server) sends a Map Group To Bearer message } } (7) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { SS-UE1 (MCPTT Client) sends a MBMS Bearer listening status report to notify listening audio and floor control subchannel by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (8) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { SS-UE2 (MCPTT Client) sends a MBMS Bearer listening status report to notify listening audio and floor control subchannel by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (9) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { IUT (MCPTT Server) requests to send floor Granted } then { IUT (MCPTT Server) sends a Floor Granted message with request for acknowledgement using unicast bearer } } (10) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { IUT (MCPTT Server) requests to set the explicit MuSiK key } then { IUT (MCPTT Server) sends a SIP MESSAGE message containing a MuSiK download message to the SS-UE1 (MCPTT Client) and the SS-U2 (MCPTT Client)} } (11) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { IUT (MCPTT Server) initiates floor messages } then { IUT (MCPTT Server) enforces Flor Taken } } ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 318 (12) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { the SS-UE2 (MCPTT client) sends Floor Request } then { IUT (MCPTT Server) replies with Floor Taken to accept Multi-talker Floor Control request } } (13) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { the SS-UE2 (MCPTT client) sends Floor Release } then { IUT (MCPTT Server) replies with Floor Release Multi Talker } } (14) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { the SS-UE1 (MCPTT client) sends Floor Release } then { IUT (MCPTT Server) replies with Floor Idle and Unmap Group To Bearer } } (15) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { SS-UE1 (MCPTT Client) sends a MBMS Bearer listening status report to stop notify listening audio and floor control subchannel by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (16) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { SS-UE2 (MCPTT Client) sends a MBMS Bearer listening status report to stop notify listening audio and floor control subchannel by sending a SIP MESSAGE message } then { IUT (MCPTT Server) responds with a SIP 200 (OK) } } (17) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and having stopped using a MBMS subchannel for the conversation } ensure that { when { the SS-UE1 (MCPTT client) sends Floor Request } then { IUT (MCPTT Server) replies with Floor Taken, Floor Idle, Floor Granted } } (18) with { IUT (MCPTT Server) having established pre-arranged group call with automatic commencement mode and having stopped using a MBMS subchannel for the conversation } ensure that { when { the SS-UE1 (MCPTT client) ends the Pre-arranged group call } then { IUT (MCPTT Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the other participants } } ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 319 |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 14.2.2.2, 14.2.3, 14.3.3.1, ETSI TS 124 380 [5] (3GPP TS 24.380) clauses 10.2.2.2, 10.2.3.2, 10.2.3.3, 10.2.3.3a, 10.2.3.4, 10.2.3.5, 10.2.3.11, 6.3.4.4.2, 6.3.4.4.6, 6.3.4.4.7a. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core specification they have been copied from. Unless otherwise stated these are Rel-13 requirements. [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 14.2.2.2] "For each MCPTT client that the participating MCPTT function is sending an MBMS bearer announcement to, the participating MCPTT function: 1) shall generate an SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]; 2) shall set the Request-URI to the URI received in the To header field in a third-party SIP REGISTER request; 3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6]; 4) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt"; 5) shall include one application/sdp MIME body conforming to 3GPP TS 24.229 [4], where the application/sdp MIME body: a) shall include the Content-Disposition header field with the value "render"; b) should include one or more "m=audio" media lines and media line attributes as defined in 3GPP TS 24.380 [5] to be used as the MBMS subchannel for audio and media control. Additionally, the participating MCPTT function: i) shall set c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the ".invalid" DNS top-level domain, if IPv6; ii) shall set port number of the media line to 9; ii) shall include the "a=rtcp-mux" attribute as specified in IETF RFC 5761 [39]; and iii) shall include the "a=rtcp:9" as specified in IETF RFC 5761 [39]. c) should include one or more "m=audio" media lines and media line attributes as defined in 3GPP TS 24.380 [5] to be used as the MBMS subchannel for audio only. Additionally, the participating MCPTT function: i) shall set the c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the ".invalid" DNS top-level domain, if IPv6; and ii) shall set the port number of the media line to 9; NOTE 1: If an MBMS subchannel for audio only is included, the "a=rtcp-mux" and "a=rtcp:" attributes are not included in the media line. d) shall include one "m=application" media line as defined in 3GPP TS 24.380 [5] to be used as the general purpose MBMS subchannel. The media line shall include a valid multicast IP address and a valid port number. If the protection of MBMS subchannel control messages sent over the general purpose MBMS subchannel of the MBMS bearer is required, the participating MCPTT function also includes an "a=key-mgmt" media-level attribute. The participating MCPTT function: i) shall encrypt the MSCCK to a UID associated to the targeted MCPTT ID and a time related parameter as described in 3GPP TS 33.180 [78]; ii) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated MSCCK and MSCCK-ID as specified in 3GPP TS 33.180 [78]; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 320 iii) shall add the public service identity of the participating MCPTT function to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78]; iv) shall sign the MIKEY-SAKKE I_MESSAGE using the public service identity of the participating MCPTT function signing key provided in the keying material together with a time related parameter, and add this to the MIKEY-SAKKE payload, as described in 3GPP TS 33.180 [78]; and v) shall include the "mikey" key management and protocol identifier and the signed MIKEY-SAKKE I_MESSAGE in the value of the a=key-mgmt" media-level attribute according to IETF RFC 4567 [47]; and NOTE 2: The media parameters to be used by the MBMS subchannel for media is included in the Map Group To Bearer message defined in 3GPP TS 24.380 [5] and not included in this application/sdp MIME body. e) if "m=audio" media lines to be used in an MBMS subchannel for audio only are included above, shall include one or more "m=application" media line as defined in 3GPP TS 24.380 [5] to be used as the MBMS subchannel for floor control messages. The media line: i) shall set c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the ".invalid" DNS top-level domain, if IPv6; and ii) shall set the port number of the media line to 9; NOTE 3: The use of a separate MBMS subchannel for floor control is optional. When a separate MBMS subchannel for floor control is not used, floor control messages are sent in the MBMS subchannel for media. 6) shall include an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body defined in clause F.2 with the <version> element set to "1" and one or more <announcement> elements associated with the pre-activated MBMS bearers. Each set of an <announcement> element: a) shall include a TMGI value in the <TMGI> element; NOTE 4: The same TMGI value can only appear in one <announcement> element. The TMGI value is also used to identify the <announcement> when updating or cancelling the <announcement> element. NOTE 5: The security key active for the general purpose MBMS subchannel on which the mapping (i.e. the Map Group To Bearer message) of media or media control to this MBMS bearer was indicated, is used for MBMS subchannels on this MBMS bearer, unless a different key or an indication of not using encryption is in place. b) shall include the QCI value in the <QCI> element; c) if multiple carriers are supported, shall include the frequency to be used in the <frequency> element; NOTE 6: In the current release if the <frequency> element is included, the frequency in the <frequency> element is the same as the frequency used for unicast. d) shall include one or more MBMS service area IDs in <mbms-service-area-id> elements in the <mbms- service-areas> element; NOTE 7: Initial mappings of groups to MBMS subchannels on an MBMS bearer for the purpose of carrying media or media control can occur only where the MBMS service area for this bearer and the MBMS service area for the bearer carrying the general purpose MBMS subchannel on which the Map Group To Bearer message is sent intersect. However, once media or media control were successfully mapped to this bearer, the reception by the MCPTT client can continue (until Unmap Group To Bearer is received or until timeout) throughout the entire MBMS service area of this bearer. e) may include the <report-suspension> element and set it to "true" value or the "false" value; NOTE 8: The participating function can choose to direct some clients not to send an MBMS bearer suspension report when notified by RAN, by including the <report-suspension> element set to "false". The purpose is to prevent an avalanche of identical reports sent by clients roughly at the same time, to report the suspension of the same MBMS bearer. The way the participation function determines which clients are to send or not to send the report is outside the scope of the present document. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 321 f) if the MBMS bearer is carrying the general purpose MBMS subchannel, shall include one <GPMS>element, giving the number of the "m=application" media line in the application/sdp MIME body generated in step 5 above to be used for the general purpose MBMS subchannel; and g) if the packet headers are compressed with ROHC specified in RFC 5795 [80] in this MBMS bearer, the <anyExt> element in the <announcement> element in the <mcptt-mbms-usage-info> element shall include the <mcptt-mbms-rohc> element defined in clause F.2.3. 7) shall include the MBMS public service identity of the participating MCPTT function in the P-Asserted-Identity header field; 8) shall include in a MIME body with Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml", the <mcptt-request-uri> element set to the MCPTT ID of the user; and 9) shall send the SIP MESSAGE request towards the MCPTT client according to 3GPP TS 24.229 [4]." [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 14.2.3] "Upon receiving a "SIP MESSAGE request for an MBMS listening status update", the participating MCPTT function shall handle the request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. If the SIP MESSAGE request contains: 1) an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body with an <mbms-listening-status> element; and 2) an application/vnd.3gpp.mcptt-info+xml MIME body containing an MCPTT ID in the <mcptt-request-uri> served by the participating MCPTT function; then the participating MCPTT function: 1) shall verify that the public user identity in the P-Asserted-Identity header field is bound to the MCPTT ID in the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body, and if that is the case: a) if the <mbms-listening-status> element is set to "listening": i) if a <session-id> element is included, shall indicate to the media plane that the MCPTT client in the session identified by the <session-id> element is now listening to the MBMS subchannel; and ii) if <general-purpose> element is included with the value "true", shall indicate to the media plane that the MCPTT client is now listening to the general purpose MBMS subchannel; and b) if the <mbms-listening-status> element is set to "not-listening": i) if a <session-id> element is included, shall indicate to the media plane that the MCPTT client in the sessions identified by the <session-id> elements is not listening to the MBMS subchannel; ii) if <general-purpose> element is included with the value "false", shall indicate to the media plane that the MCPTT client is no longer listening to the general purpose MBMS bearer; and iii) shall interact with the media plane as specified in 3GPP TS 24.380 [5]. NOTE 1: If the MCPTT client reports that the MCPTT client is no longer listening to the general purpose MBMS subchannel it is implicitly understood that the MCPTT client no longer listens to any MBMS subchannel in ongoing conversations that the MCPTT client previously reported status "listening". …" [ETSI TS 124 379 [4] (3GPP TS 24.379), clause 14.3.3.1] "If one of the following conditions is fulfilled: 1) if the MCPTT client: a) receives a Map Group To Bearer message over the general purpose MBMS channel; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 322 b) participates in a group session identified by the Map Group To Bearer message; and c) the status "listening" is not already reported; or 2) if the MCPTT client: a) receives an announcement as described in clause 14.3.2; b) enters an MBMS service area where a general purpose MBMS is available; and c) experiences good MBMS bearer radio condition; then the MCPTT client shall report that the MCPTT client is listening to the MBMS bearer as specified in clause 14.3.3.2. If one of the following conditions is fulfilled: 1) if the MCPTT client: a) receives an MBMS bearer announcement as described in the clause 14.3.2; b) the MBMS bearer announcement contains a cancellation of an <announcement> element identified by the same TGMI value as received in a Map Group To Bearer message in an ongoing conversation; and c) the status "not-listening" is not already reported; 2) if the MCPTT client: a) receives an MBMS bearer announcement as described in the clause 14.3.2; b) the MBMS bearer announcement contains a cancellation of an <announcement> element; c) does not participate in an ongoing conversation; d) the MCPTT client has reported the "listening" status due to the availability of the general purpose MBMS subchannel in the <announcement> element; and e) the status "not-listening" is not already reported; or 3. if the MCPTT client: a) suffers from bad MBMS bearer radio condition, then the MCPTT client shall report that the MCPTT client is not listening to the MBMS subchannels as specified in clause 14.3.3.2. …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.2.2] "Upon receiving a Floor Request message or a Floor Taken message and when the participating MCPTT function decides that an MBMS subchannel shall be used for a conversation in an ongoing group session, the participating MCPTT function needs to determine if the MBMS bearer has sufficient capacity for the new conversation. If the new MBMS bearer has sufficient capacity the participating MCPTT function: NOTE: The participating MCPTT function can take that decision when receiving the first Floor Request from a floor participant or when receiving a Floor Taken message destined to one of the floor participants served by the participating MCPTT client. 1. shall create an instance of the 'Participating MCPTT function MBMS subchannel control' state machine; 2. shall send a Map Group To Bearer message over the general purpose MBMS subchannel. The Map Group To Bearer message: a. shall include TMGI; b. shall include the identifier of the media stream; and ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 323 c. shall include the MCPTT Group identifier field; 3. shall start timer T15 (Conversation); 4. shall start timer T16 (Unmap Group To Bearer); 5. shall enter the 'M: A conversation is active' state; 6. if the Floor Request was received, shall perform actions as described in subclause 6.4.2; and 7. if the Floor Taken was received, shall perform the actions described in subclause 10.2.3.3. If the MBMS bearer does not have sufficient capacity for the new conversation the participating MCPTT function: 1. may free capacity for the new conversation by transfering an existing conversation over an MBMS bearer to unicast bearers following the procedure in subclause 10.2.3.12; or 2. may use the MBMS bearer for the signaling messages, while using unicast bearers for the media message." [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.2] "When a Floor Idle message destined to a floor participant listening to the MBMS subchannel is received, the participating MCPTT function: 1. shall for each received Floor Idle message, check if there is a stored message-sequence-number value associated with the conversation; 2. if a message-sequence-number value associated with the conversation is stored, compared the value of the stored message-sequence-number value with the value in the received Floor Idle message; a. if the received message-sequence-number value is higher than the stored value: i. shall replace the stored message-sequence-number value with the received message-sequence- number field; ii. shall set the acknowledgment bit to '0' as specified in subclause 8.2.2, if not already set; and iii. shall send the received Floor Idle message over the MBMS subchannel; and b. if the received message-sequence-number value is lower or the same as the stored value, shall discard the received Floor Idle message; 3. if a message-sequence-number value associated with the conversation is not stored (i.e. this is the first floor control message received in the conversation): a. shall store the received message-sequence-number value and associate the value with the conversation; b. shall set the acknowledgment bit to '0' as specified in subclause 8.2.2, if not already set; and c. shall send the received Floor Idle message over the MBMS subchannel; …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.3] "When a Floor Taken message destined to a floor participant listening to the MBMS subchannel is received, the participating MCPTT function: 1. shall for each received Floor Taken message, check if there is a stored message-sequence-number value associated with the conversation; 2. if a message-sequence-number value associated with the conversation is stored, compare the value of the stored message-sequence-number value with the value in the received Floor Taken message; a. if the received message-sequence-number value is higher than the stored value: i. shall replace the stored message-sequence-number value with the received message-sequence- number field; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 324 ii. shall set the acknowledgment bit to '0' as specified in subclause 8.2.2, if not already set; and iii. shall send the received Floor Taken message over the MBMS subchannel; and b. if the received message-sequence-number value is lower or the same as the stored value, shall discard the received Floor Taken message; 3. if a message-sequence-number value associated with the conversation is not stored (i.e. this is the first floor control message received in the conversation): a. shall store the received message-sequence-number value and associate the value with the conversation; b. shall set the acknowledgment bit to '0' as specified in subclause 8.2.2, if not already set; and c. shall send the received Floor Taken message over the MBMS subchannel; 4. if the received Floor Taken message indicates that a Floor Ack message is expected (i.e. the acknowledgment bit is set to '1' as specified in subclause 8.2.2), shall send a Floor Ack message towards the controlling MCPTT function The Floor Ack message: a. shall include the Message Type field set to '2' (Floor Taken); and b. shall include the Source field set to '1' (participating MCPTT function is the source); …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.3a] "When a Floor Release Multi Talker message destined to a floor participant listening to the MBMS subchannel is received, the participating MCPTT function: 1. shall for each received Floor Release Multi Talker message, check if there is a stored message-sequence- number value associated with the conversation; 2. if a message-sequence-number value associated with the conversation is stored, compare the value of the stored message-sequence-number value with the value in the received Floor Release Multi Talker message; a. if the received message-sequence-number value is higher than the stored value: i. shall replace the stored message-sequence-number value with the received message-sequence- number field; and ii. shall send the received Floor Release Multi Talker message over the MBMS subchannel; and b. if the received message-sequence-number value is lower or the same as the stored value, shall discard the received Floor Release Multi Talker message; 3. if a message-sequence-number value associated with the conversation is not stored (i.e. this is the first floor control message received in the conversation): a. shall store the received message-sequence-number value and associate the value with the conversation; and b. shall send the received Floor Release Multi Talker message over the MBMS subchannel; …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.4] "When a floor control message other than the Floor Idle and Floor Taken message is received from a floor participant or received from the floor control server, the participating MCPTT function: 1. shall forward the floor control message as specified in subclause 6.4; …" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 325 [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.5] "When receiving a RTP media packet destined to one of the MCPTT client listening to the MBMS subchannel, the participating MCPTT function: NOTE: An RTP media packet not destined to an MCPTT client listening to the MBMS subchannel is forwarded to the MCPTT client over the unicast bearer. 1. shall check if the media packet is already sent over the MBMS subchannel or not; 2. if the RTP media packet is already sent over the MBMS subchannel, shall discard the RTP media packet; 3. if the RTP media packet is not already sent over the MBMS sub channel, shall instruct the media distribution function to send the RTP media packet over the MBMS subchannel; …" [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 10.2.3.11] "If the control and signalling plane indicates that the group call session is released, the participating MCPTT function: 1. shall send the Unmap Group To Bearer message over the MBMS subchannel. The Unmap Group To Bearer message: a. shall include the MCPTT Group ID field; 2. shall stop timer T15 (Conversation), timer T16 (Map Group To Bearer) and timer T17 (Unmap Group To Bearer), if running; and 3. shall release the instance of the 'Participating MCPTT function MBMS subchannel management' state machine used for the conversation." [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 6.3.4.4.2] "When entering this state the floor control arbitration logic in the floor control server: 1. shall send a Floor Granted message to the floor participant to which the floor is granted. The Floor Granted message: a. shall include the value of timer T2 (Stop talking)in the Duration field; b. shall include the granted priority in the Floor priority field; … 3. shall send Floor Taken message to all other floor participants. The Floor Taken message: … b. if multi-talker is supported and the floor is currently granted to multiple participants: i. shall include the Floor Indicator field with the I-bit set to '1' (Multi-talker); ii. shall include the list of granted users in the multi-talker group in List of Granted Users field, including a new granted talker; iii. shall include the list of SSRCs of granted floor participants; iv) may include the list of functional aliases of the granted floor participants in the List of Functional Aliases field; and v. shall include the List of Locations of granted floor participants;" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 326 [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 6.3.4.4.6] "Upon receiving a Floor Release message the floor control arbitration logic in the floor control server: 1. shall request the media distributor in the MCPTT server to stop forwarding RTP media packets received from the participant that sent the Floor Release message; … 5. if multi-talker floor control is supported, then: a. shall send a Floor Release Multi Talker message. The Floor Release Multi Talker message: i. shall include SSRC field set to the SSRC of the floor participant that has released the floor; and ii. shall include the User ID set to the MCPTT ID of the floor participant releasing the floor; b. shall remove the participant that sent the Floor Release message from the list of currently granted talkers; and c. if the list of currently granted talkers is empty, shall enter the 'G: Floor Idle' state as specified in the subclause 6.3.4.3.2; or if the list of currently granted talkers is not empty shall stay in state the 'G: Floor Taken'." [ETSI TS 124 380 [5] (3GPP TS 24.380), clause 6.3.4.4.7a] "On receipt of a floor request message and if the group is configured as multi-talker group the floor control arbitration logic in the floor control server: 1. shall select one of the following options: a. if the maximum number of simultaneous talkers applicable for multi-talker control is reached and if the floor request message has effective priority indicating pre-emptive priority, determine from all participants having permission to send media, the one with the lowest priority and revoke the floor from the participant with the lowest priority; or b. if the maximum number of simultaneous talkers applicable for multi-talker control is not reached, allow media from both the current speaker(s) and from the participant now requesting floor; … 3. if allow media from both the current speaker(s) and from the participant now requesting floor is selected: a. shall send a Floor Granted message to the requesting floor participant. The Floor Granted message: i. shall include the value of the T2 (Stop talking) timer in the Duration field; ii. shall include the granted priority in the Floor priority field; iii. if a Track Info field associated with the floor control server state transition diagram for 'multe- talker floor control operation' is stored, shall include the stored Track Info field; iv. shall include the Floor Indicator field with the I-bit set to '1' (Multi-talker); and v. shall include the SSRC of granted floor participant; b. shall add the MCPTT ID of the user to which the floor is granted to the list of currently granted talkers; c. shall send a Floor Taken message to any non-controlling MCPTT functions involved and to floor participants controlled by the controlling MCPTT function that will listen to the RTP media from the multi-talker MCPTT client according to local policy. The Floor Taken message: i. shall include the granted MCPTT user's MCPTT ID in the Granted Party's Identity field and may include the associated functional alias in the Functional Alias field, if privacy is not requested; ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 327 ii. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; iii. shall include the Floor Indicator field with the I-bit set to '1' (Multi-talker); iv. shall include the list of granted users in the multi-talker group in List of Granted Users field; v. shall include the list of SSRCs of granted floor participants; and vi) may include the list of functional aliases of the granted floor participants in the List of Functional Aliases field. d. shall start the T1 (End of RTP media) timer for the particpant to which the floor is granted; e. shall start timer T20 (Floor Granted) for the particpant to which the floor is granted, if the floor request was queued and initialise the counter C20 (Floor Granted) to 1; f. shall stay in the state to 'G: Floor Taken' state." |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.3 Test description | |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCPTT client) and SS-UE2 (MCPTT client) - For the underlying "transport bearer" over which the SS-UE1 (MCPTT client) 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. 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. - SS-UE1 (MCPTT client) and SS-UE2 (MCPTT client) are affiliated to the Prearranged group. - The IUT (MCPTT Server) is the controlling server of the Prearranged group. - A pre-activated MBMS bearer exists. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 328 |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.3.2 Test procedure sequence | Table 6.4.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCPTT client) requests the establishment of a group call to SS-UE2 (MCPTT client) with automatic commencement mode and without implicit floor request. - - - - 2 Check: Does the MCPTT server correctly perform procedure 'MCPTT E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to establish a pre- arranged group call with automatic commencement mode and without implicit floor control according to option a of note in Annex A, Table A.3.1.3-1? - - 1 P 3 Make the MCPTT Server activate an MBMS bearer and send an MBMS bearer announcement to notify bearer availability (Note) - - - - - EXCEPTION: Depending on the MCPTT Server implementation, steps 4a-4d and steps 5a-5d might be performed in parallel - - - - 4a Check: Does the MCPTT Server send an MBMS bearer announcement to notify MBMS bearer availability to SS-UE1? <-- SIP MESSAGE 2 P 4b The SS-UE1 (MCPTT client) responds with a SIP 200 (OK) message to MCPTT Server --> SIP 200 (OK) - - 4c The SS-UE1 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify being listening to general-purpose subchannel --> SIP MESSAGE - - 4d Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE1? <-- SIP 200 (OK) 3 P 5a Check: Does the MCPTT Server send an MBMS bearer announcement to notify MBMS bearer availability to SS-UE2? <-- SIP MESSAGE 4 P 5b The SS-UE2 (MCPTT client) responds with a SIP 200 (OK) message to MCPTT Server --> SIP 200 (OK) - - 5c The SS-UE2 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify being listening to general-purpose subchannel. --> SIP MESSAGE - - 5d Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE2? <-- SIP 200 (OK) 5 P 6 The SS-UE1 (MCPTT client) sends a Floor Request message to MCPTT Server --> Floor Request - - 7 Make the MCPTT Server use MBMS subchannel for the conversation (see note) - - - - 8 Check: Does the MCPTT Server send a Map Group To Bearer message over general purpose MBMS subchannel? <-- Map Group To Bearer 6 P 9 The SS-UE1 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify being listening to audio and floor control over MBMS subchannel --> SIP MESSAGE - - 10 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE1? <-- SIP 200 (OK) 7 P 11 The SS-UE2 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify being listening to audio and floor control over MBMS subchannel --> SIP MESSAGE - - ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 329 St Procedure Message Sequence TP Verdict U - S Message 12 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE2? <-- SIP 200 (OK) 8 P 13 Check: Does the MCPTT Server send a Floor Granted message with request for acknowledgement using unicast bearer to SS- UE1? <-- Floor Granted 9 P 14 The SS-UE1 (MCPTT client) responds with a Floor Ack message to MCPTT Server --> Floor Ack - - - EXCEPTION: Depending on the MCPTT Server implementation, steps 15a-15b and steps 16a- 16b might be performed in parallel - - - - 15a Check: Does the MCPTT Server send a message containing a MuSiK download message to set the explicit MuSiK key to be used for the floor control encryption over the MBMS subchannel to SS-UE1? <-- SIP MESSAGE 10 P 15b The SS-UE1 (MCPTT client) responds with a SIP 200 (OK) to MCPTT Server --> SIP 200 (OK) - - 16a Check: Does the MCPTT Server send a message containing a MuSiK download message to set the explicit MuSiK key to be used for the floor control encryption over the MBMS subchannel to SS-UE2? <-- SIP MESSAGE 10 P 16b The SS-UE2 (MCPTT client) responds with a SIP 200 (OK) to MCPTT Server --> SIP 200 (OK) - - 17 Check: Does the MCPTT Server send a Floor Taken message using multicast bearer? <-- Floor Taken 11 P 18 The SS-UE2 (MCPTT client) sends a Floor Request message to MCPTT Server --> Floor Request - - 19 Make the MCPTT Server accept Multi-talker Floor Control request (Note) - - - - 20 Check: Does the MCPTT Server send a Floor Taken message with l-bit in the Floor Indicator set to '1' (Multi-talker) using MBMS subchannel? <-- Floor Taken 12 P 21 The SS-UE2 (MCPTT client) sends a Floor Release message to MCPTT Server --> Floor Release - - 22 Make the MCPTT Server use accept Multi- talker Floor Control release (Note) - - - - 23 Check: Does the MCPTT Server send a Floor Release Multi Talker using MBMS subchannel? <-- Floor Release Multi Talker 13 P 24 The SS-UE1 (MCPTT client) sends a Floor Release message to MCPTT Server --> Floor Release - - 25 Check: Does the MCPTT Server send a Floor Idle message using multicast bearer? <-- Floor Idle 14 P 26 Make the MCPTT Server stop using MBMS subchannel for the conversation (see note) - - - - 27 Check: Does the MCPTT Server send an Unmap Group To Bearer message over general purpose MBMS subchannel? <-- Unmap Group To Bearer 14 P 28 The SS-UE1 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify not being listening to audio and floor control over MBMS subchannel --> SIP MESSAGE - - 29 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE1? <-- SIP 200 (OK) 15 P 30 The SS-UE2 (MCPTT client) sends MBMS Bearer listening status report message to MCPTT Server, to notify not being listening to audio and floor control over MBMS subchannel --> SIP MESSAGE - - 31 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE2? <-- SIP 200 (OK) 16 P ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 330 St Procedure Message Sequence TP Verdict U - S Message 32 The SS-UE1 (MCPTT client) sends a Floor Request message to MCPTT Server --> Floor Request - - 33 Check: Does the MCPTT Server send a Floor Granted message with request for acknowledgement using unicast to SS-UE1? <-- Floor Granted 17 P 34 The SS-UE1 (MCPTT client) responds with a Floor Ack message to MCPTT Server --> Floor Ack - - 35 Check: Does the MCPTT Server send a Floor Taken message with request for acknowledgement using unicast bearer to SS- UE2? <-- Floor Taken 17 P 36 The SS-UE2 (MCPTT client) responds with a Floor Ack message to MCPTT Server --> Floor Ack - - 37 The SS-UE1 (MCPTT client) sends a Floor Release message to MCPTT Server --> Floor Release - - 38 Check: Does the MCPTT Server send a Floor Idle message with request for acknowledgement using unicast bearer to SS- UE1? <-- Floor Idle 17 P 39 The SS-UE1 (MCPTT client) responds with a Floor Ack message to MCPTT Server --> Floor Ack - - 40 Check: Does the MCPTT Server send a Floor Idle message with request for acknowledgement using unicast bearer to SS- UE2? <-- Floor Idle 17 P 41 The SS-UE2 (MCPTT client) responds with a Floor Ack message to MCPTT Server --> Floor Ack - - 42 The SS-UE1 (MCPTT client) releases the call. - - - - 43 Check: Does the MCPTT server correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 18 P NOTE: This is expected to be done via a suitable implementation dependent MMI. |
ff02e8fbdf121d4fc0b99acb59e5bd85 | 104 147-1 | 6.4.2.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.4.2.3.3-1: SIP MESSAGE from the MCPTT Server (Step 4a, Table 6.4.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT Information Element Value/remark Comment Reference Condition P-Asserted-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcptt" P-Asserted-Identity addr-spec px_MBMS_Service_ID URI of the participating MCPTT function Message-body MIME body part SDP message MIME-part-headers Content-Type "application/sdp" Content-Disposition "render" ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.2.2.2 MIME-part-body SDP message as described in Table 6.4.2.3.3-2 MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcp tt-mbms-usage-info+xml" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 331 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT Information Element Value/remark Comment Reference Condition MIME-part-body MCPTT-MBMS-Usage- Info as described in Table 6.4.2.3.3-3 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.2.3.3-4 Table 6.4.2.3.3-2: SDP in SIP MESSAGE (Table 6.4.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1 Information Element Value/remark Comment Reference Condition Media descriptions media description m= line media = audio media "audio" port "9" proto "RTP/AVP" fmt "99" Connection Data c= line nettype "IN" addrtype "IP4" or "IP6" depending on IP address connection-address "0.0.0.0" (IPv4) or domain name within ".invalid" DNS top level domain (IPv6) media attribute a= line attribute = rtcp-mux rtcp-mux "rtcp-mux" media attribute a= line attribute = rtcp rtcp "rtcp" port "9" media description m= line media = application media "application" port "9" proto "udp" fmt "MCPTT" Connection Data c= line nettype "IN" addrtype "IP4" or "IP6" depending on IP address connection-address "0.0.0.0" (IPv4) or domain name within ".invalid" DNS top level domain (IPv6) media description m= line media = application media "application" port port number assigned by the MCPTT Server proto "udp" fmt "MCPTT" Connection Data c= line nettype "IN" addrtype "IP4" connection-address multicast IP assigned by the MCPTT Server media attribute a= line attribute = key-mgmt ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 332 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1 Information Element Value/remark Comment Reference Condition key-mgmt ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.2.2.2 mikey MIKEY-SAKKE I_MESSAGE as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.9.1- 4. MSCCK distribution as specified in ETSI TS 133 180 [31] (3GPP TS 33.180), Annex H Table 6.4.2.3.3-3: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.2.3.3-1) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status not present announcement TMGI MBMS Service ID "0F0F0F" The selected value is randomly chosen - a 6 digit hexadecimal number between 000000 and FFFFFF (see TS 23.003 [X] clause 15.2. The coding of the MBMS Service ID is the responsibility of each administration MCC The same value as for PLMN1 Mobile Country Code MNC The same value as for PLMN1 Mobile Network Code QCI "65" Mission Critical user plane Push To Talk voice mbms-service-areas "0" The selected value is randomly chosen. The value 0 has a special meaning; it shall denote the whole PLMN as the MBMS Service Area GPMS "2" The number of the "m=application" media line in the application/sdp MIME version "1" Table 6.4.2.3.3-4: MCPTT-Info in SIP MESSAGE (Table 6.4.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.2.2.2 mcptt-calling-user-id not present NOTE: Encrypted element as described in Table 5.5.3.2.1-1A. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 333 Table 6.4.2.3.3-5: SIP MESSAGE from the MCPTT Server (Step 5a, Table 6.4.2.3.2-1) Derivation Path: Table 6.4.2.3.3-1 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.2.3.3-6 Table 6.4.2.3.3-6: MCPTT-Info in SIP MESSAGE (Table 6.4.2.3.3-5) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_B ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.2.2.2 mcptt-calling-user-id not present NOTE: Encrypted element as described in Table 5.5.3.2.1-1A. Table 6.4.2.3.3-7: SIP MESSAGE from the SS-UE1 (Step 4c, Table 6.4.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCPTT Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (px_MBMS_Service_ID) Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcptt- mbms-usage-info+xml" MIME-part-body MCPTT-MBMS-Usage-Info as described in Table 6.4.2.3.3-8 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.2.3.3-9 Table 6.4.2.3.3-8: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.2.3.3-7) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status mbms-listening-status "listening" session-id not present general-purpose "true" TMGI same value as the announcement in the SIP MESSAGE of Table 6.4.2.3.3-3 announcement not present version "1" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 334 Table 6.4.2.3.3-9: MCPTT-Info in SIP MESSAGE (Table 6.4.2.3.3-7) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.3.3.2 mcptt-calling-user-id not present NOTE: Encrypted element as described in Table 5.5.3.2.1-1A. Table 6.4.2.3.3-10: SIP MESSAGE from the SS-UE2 (Step 5c, Table 6.4.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCPTT Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (px_MBMS_Service_ID) Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcptt- mbms-usage-info+xml" MIME-part-body MCPTT-MBMS-Usage-Info as described in Table 6.4.2.3.3-8 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.2.3.3-11 Table 6.4.2.3.3-11: MCPTT-Info in SIP MESSAGE (Table 6.4.2.3.3-10) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_B ETSI TS 124 379 [4] (3GPP TS 24.379) clause 14.3.3.2 mcptt-calling-user-id not present NOTE: Encrypted element as described in Table 5.5.3.2.1-1A. Table 6.4.2.3.3-12: SIP MESSAGE from the SS-UE1 (Step 9, Table 6.4.2.3.2-1) Derivation Path: Table 6.4.2.3.3-7 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.m cptt-mbms-usage- info+xml" MIME-part-body MCPTT-MBMS-Usage- Info as described in Table 6.4.2.3.3-13 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 335 Table 6.4.2.3.3-13: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.2.3.3-12) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status mbms-listening-status "listening" session-id px_session_A_ID general-purpose not present TMGI same value as the announcement in the SIP MESSAGE announcement not present version "1" Table 6.4.2.3.3-14: SIP MESSAGE from the SS-UE2 (Step 11, Table 6.4.2.3.2-1) Derivation Path: Table 6.4.2.3.3-10 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.m cptt-mbms-usage- info+xml" MIME-part-body MCPTT-MBMS-Usage- Info as described in Table 6.4.2.3.3-13 Table 6.4.2.3.3-15: SIP MESSAGE from the MCPTT Server (Steps 15a and 16a, Table 6.4.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCPTT Information Element Value/remark Comment Reference Condition P-Asserted-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcptt" P-Asserted-Identity addr-spec px_MBMS_Service_ID URI of the participating MCPTT function Message-body not including any MIME body part other than the ones described below MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcptt- mbms-usage-info+xml" MIME-part-body MCPTT-MBMS-Usage-Info as described in Table 6.4.2.3.3- 16 MIME body part MIKEY message MIME-part-headers Content-Type "application/mikey" MIME-part-body As described in ETSI TS 136 579-1 [1] (3GPP TS 36.579- 1), Table 5.5.9.1-5. MIKEY message containing the MuSiK ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 336 Table 6.4.2.3.3-16: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.2.3.3-15) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status not present announcement not present version "1" anyExt mbms-explicitMuSiK-download group px_MCPTT_Group_ A_ID Table 6.4.2.3.3-17: SIP MESSAGE from the SS-UE1 (Step 28, Table 6.4.2.3.2-1) Derivation Path: Table 6.4.2.3.3-7 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.m cptt-mbms-usage- info+xml" MIME-part-body MCPTT-MBMS-Usage- Info as described in Table 6.4.2.3.3-18 Table 6.4.2.3.3-18: MCPTT-MBMS-Usage-Info in SIP MESSAGE (Table 6.4.2.3.3-17) Derivation Path: ETSI ETSI TS 124 379 [4] (3GPP TS 24.379), Clause F.2 Information Element Value/remark Comment Reference Condition mcptt-mbms-usage-info mbms-listening-status mbms-listening-status "not-listening" session-id px_sesson_A_ID general-purpose not present TMGI same value as the announcement in the SIP MESSAGE announcement not present version "1" Table 6.4.2.3.3-19: SIP MESSAGE from the SS-UE2 (Step 30, Table 6.4.2.3.2-1) Derivation Path: Table 6.4.2.3.3-10 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.m cptt-mbms-usage- info+xml" MIME-part-body MCPTT-MBMS-Usage- Info as described in Table 6.4.2.3.3-18 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 337 Table 6.4.2.3.3-20: SIP INVITE from the SS-UE1 (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, condition GROUP-CALL Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.4.2.3.3-20A MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.2.3.3-20B Table 6.4.2.3.3-20A: SDP in SIP INVITE from the SS-UE1 (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-2, with conditions GROUP-CALL Table 6.4.2.3.3-20B: MCPTT-Info in SIP INVITE from the SS-UE1 (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-3, with conditions GROUP-CALL Table 6.4.2.3.3-21: SIP INVITE from the MCPTT Server (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1; step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, condition GROUP-CALL Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.4.2.3.3-21A MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table 6.4.2.3.3-21B Table 6.4.2.3.3-21A: SDP in SIP INVITE from the MCPTT Server (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-5, with conditions GROUP-CALL Table 6.4.2.3.3-21B: MCPTT-Info in SIP INVITE from the MCPTT Server (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-6, with conditions GROUP-CALL Table 6.4.2.3.3-22: SIP 200 (OK) from the SS-UE2 (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7, with conditions GROUP-CALL Information Element Value/remark Comment Reference Condition Message-body SDP Message As described in Table 6.4.2.3.3-22A ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 338 Table 6.4.2.3.3-22A: SDP in SIP 200 (OK) from the SS-UE2 (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-8, with conditions GROUP-CALL Table 6.4.2.3.3-23: SIP 200 (OK) from the MCPTT Server (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9, with conditions GROUP-CALL Information Element Value/remark Comment Reference Condition Message-body SDP Message As described in Table 6.4.2.3.3-23A Table 6.4.2.3.3-23A: SDP in SIP 200 (OK) from the MCPTT Server (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1, step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-10, with conditions GROUP-CALL Table 6.4.2.3.3-24: Floor Granted (Steps 13 and 33, Table 6.4.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.3-1, with conditions ACK Table 6.4.2.3.3-25: Floor Taken (Step 20, Table 6.4.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.7-1, with conditions Multi-Talker Table 6.4.2.3.3-26: Floor Taken (Step 35, Table 6.4.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.7-1, with conditions ACK Table 6.4.2.3.3-27: Floor Idle (Steps 38 and 40, Table 6.4.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.6-1, with conditions ACK ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 339 Annex A (normative): Common Test Environment A.1 Introduction This annex specifies additional generic test procedures to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), to be used by the test cases wherever applicable. A.2 Generic test procedures for Server-Client MCS operation A.2.1 General The purpose of the procedures specified in the following clauses is to facilitate test description by providing procedure sequences which can be referred from the relevant server-to-client TCs specified in the present document. The procedures specified are required to ensure that any MC service can take place between a MC client and a MC server or specific MC relevant pre-conditions are met before a test case can be executed. A.2.2 Void A.2.3 MCX Server Originated notifications regarding temporary group creation or tear down A.2.3.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.3.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.3.3 Procedure Table A.2.3.3-1: MCX Server originated notifications regarding temporary group creation or tear down St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCX Server send a SIP NOTIFY to the SS-UE informing about change of group A's configuration document? <-- SIP NOTIFY - P 2 The SS-UE (MCX Client) sends a SIP 200 (OK) message to the MCX Server. --> SIP 200 (OK) - - 3 The SS-UE (MCX Client) sends an HTTP GET Request message to the MCX Server that contains the access token and the XCAP-URI of the Group Configuration document. --> HTTP GET - - ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 340 St Procedure Message Sequence TP Verdict U - S Message 4 Check: Does the MCX Server send a HTTP 200 (OK) message including the updated Group Document? <-- HTTP 200 (OK) - P 5 Check: Does the MCX Server send a SIP NOTIFY message to the SS-UE (MCX Client) containing the group key transport payloads (GKTP) document including the group keys? <- SIP NOTIFY - P 6 The SS-UE (MCX Client) sends a SIP 200 (OK) message. --> SIP 200 (OK) - - NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.3.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). • Clarifications specified in clause 5.3.22.4 shall also be followed. Table A.2.3.4-1: SIP NOTIFY (Step 1, Table A.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3.22.4-1 Table A.2.3.4-2: SIP 200 (OK) (Steps 2, 6, Table A.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3.22.4-2 Table A.2.3.4-3: HTTP GET (Step 3, Table A.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3.22.4-3 Table A.2.3.4-4: HTTP 200 (OK) (Step 4, Table A.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3.22.4-4 Table A.2.3.4-5: SIP NOTIFY (Step 5, Table A.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3.22.4-6 A.2.4 MCX Server Terminated Group Creation A.2.4.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.4.2 Definition of system information messages N/a (out of E-UTRA coverage). ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 341 A.2.4.3 Procedure Table A.2.4.3-1: MCX Server Terminated Group Creation procedure St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCX Client) sends a HTTP PUT to the Group Management Server for requesting the creation of the new group. (see note) --> HTTP PUT - - 2 Check: Does the MCX Server respond with a HTTP 201 (Created) response message? <-- HTTP 201 (Created) - P NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.4.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.2.4.4-1: HTTP PUT (Step 1, Table A.2.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.4-1, condition GROUPCREATE A.2.5 MCX Server Terminated Temporary Group Creation A.2.5.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.5.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.5.3 Procedure Table A.2.5.3-1: MCX Participating Terminated Temporary Group Creation procedure St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCX Client) sends a HTTP POST to the MCX Server to request for creation of a temporary group. (see note) --> HTTP POST - - 2 Check: Does the MCX Server send a HTTP 200 (OK) containing the GMOP group-regroup- creation-response? <-- HTTP 200 (OK) - P NOTE: The SS-UE being used is specified in the test case calling the procedure. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 342 A.2.5.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.2.5.4-1: HTTP POST (Step 1, Table A.2.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.3-1, condition TEMPGROUP Table A.2.5.4-2: HTTP 200 (OK) (Step 2, Table A.2.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.6-1, condition TEMPGROUP A.2.6 MCX Server Terminated Temporary Group Tear Down A.2.6.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.6.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.6.3 Procedure Table A.2.6.3-1: MCX Server Terminated Temporary Group Tear Down procedure St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCX Client) sends a HTTP DELETE to the MCX Server to request for tear down of a temporary group (see note). --> HTTP DELETE - - 2 Check: Does the MCX Server send a HTTP 200 (OK) response message? <-- HTTP 200 (OK) - P NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.6.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.2.6.4-1: HTTP DELETE (Step 1, Table A.2.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.4.5-1, condition TEMPGROUP ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 343 A.2.7 MCX Subscription and Notification A.2.7.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.7.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.7.3 Procedure Table A.2.7.3-1: MCX Subscription and Notification St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCX Client) sends a SIP SUBSCRIBE message request. --> SIP SUBSCRIBE - - 2 Check: Does the MCX Server respond to the SIP SUBSCRIBE message with a SIP 200 (OK) message? <-- SIP 200 (OK) - P 3 Check: Does the MCX Server send a SIP NOTIFY message? <-- SIP NOTIFY - P 4 The SS-UE (MCX Client) responds with a SIP 200 (OK) message. --> SIP 200 (OK) NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.7.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.2.7.4-1: SIP SUBSCRIBE (Step 1, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.14-1 Information Element Value/remark Comment Reference Condition Expires value "4294967295" to receive the current status and later notification ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 9.2.1.3 and 9A.2.1.3; ETSI TS 124 281 [10] (3GPP TS 24.281) clause 8.2.1.3; ETSI TS 124 282 [9] (3GPP TS 24.282) clauses 8.2.3 and 22.2.1.3 Message-body MIME body part MCPTT Info ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9.2.1.3 and 9A.2.1.3 MCPTT MIME-part-body MCPTT-Info as described in Table A.2.7.4-2 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 344 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.14-1 Information Element Value/remark Comment Reference Condition MIME body part MCVIDEO Info ETSI TS 124 281 [10] (3GPP TS 24.281) clause 8.2.1.3 MCVIDEO MIME-part-body MCVIDEO-Info as described in Table A.2.7.4-3 MIME body part MCDATA Info ETSI TS 124 282 [9] (3GPP TS 24.282) clauses 8.2.3 and 22.2.1.3 MCDATA MIME-part-body MCDATA-Info as described in Table A.2.7.4-4 Table A.2.7.4-2: MCPTT-Info in SIP SUBSCRIBE (Table A.2.7.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri encrypted (see note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 9.2.1.3 and 9A.2.1.3 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1A. Table A.2.7.4-3: MCVideo-Info in SIP SUBSCRIBE (Table A.2.7.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-request-uri encrypted (see note) <mcvideo- request-uri> with mcvideoURI set to px_MCVIDEO_ID_User_A ETSI TS 124 281 [10] (3GPP TS 24.281) clause 8.2.1.3 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2A. Table A.2.7.4-4: MCData-Info in SIP SUBSCRIBE (Table A.2.7.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-3 Information Element Value/remark Comment Reference Condition mcdatainfo mcdata-Params mcdata-request-uri encrypted (see note) <mcdata-request-uri> with mcdataURI set to px_MCDATA_ID_User_A ETSI TS 124 282 [9] (3GPP TS 24.282) clauses 8.2.3 and 22.2.1.3 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-3A. Table A.2.7.4-5: SIP 200 (OK) (Step 2, Table A.2A.7.3-1) Derivation Path: Table ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 5.5.2.17.1.2-1 with condition SUBSCRIBE-RSP ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 345 A.2.8 MCX Participating Terminated SIP MESSAGE A.2.8.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.8.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.8.3 Procedure Table A.2.8.3-1: MCX Participating Terminated SIP MESSAGE St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCX Client) send a SIP MESSAGE message (see note) --> SIP MESSAGE - - 2 Check: Does the MCX Server responds with a SIP 200 (OK) message? <-- SIP 200 (OK) - P NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.8.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). A.2.9 MCX Participating Originated SIP MESSAGE A.2.9.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.9.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.9.3 Procedure Table A.2.9.3-1: MCX Participating Originated SIP MESSAGE St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCX Server send a SIP MESSAGE message? <-- SIP MESSAGE - P 2 The SS-UE (MCX Client) responds with a SIP 200 (OK) message (see note) SIP 200 (OK) - - NOTE: The SS-UE being used is specified in the test case calling the procedure. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 346 A.2.9.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). A.2.10 MCX E2E SIP MESSAGE A.2.10.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT or MCVideo. A.2.10.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.10.3 Procedure Table A.2.10.3-1: MCX E2E SIP MESSAGE St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCX Client) sends a SIP MESSAGE message --> SIP MESSAGE - - 2 Check: Does the MCX Server send a SIP MESSAGE to SS-UE2? <-- SIP MESSAGE - P 3 The SS-UE2 (MCX Client) responds with a SIP 200 (OK) message --> SIP 200 (OK) - - 4 Check: Does the MCX Server respond with a SIP 200 (OK) message to SS-UE1? <-- SIP 200 (OK) - P A.2.10.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). A.2.11 MCX E2E SIP MESSAGE Request - Accept A.2.11.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT or MCVideo. A.2.11.2 Definition of system information messages N/a (out of E-UTRA coverage). ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 347 A.2.11.3 Procedure Table A.2.11.3-1: MCX E2E SIP MESSAGE Request - Accept Participating Originated St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCX Client) sends a SIP MESSAGE message. --> SIP MESSAGE - - 2 Check: Does the MCX Server respond with a SIP 200 (OK) message <-- SIP 200 (OK) - P 3 Check: Does the MCX server send a SIP MESSAGE accepting the request to SS-UE1? <-- SIP MESSAGE - P 4 The SS-UE1 (MCX Client) responds with a SIP 200 (OK) message. --> SIP 200 (OK) - - - EXCEPTION: Depending on the MCX Server implementation, the following steps may be performed in parallel to steps 3-4. - - - - 5 Check: Does the MCX Server send a SIP MESSAGE message to SS-UE2? <-- SIP MESSAGE - P 6 The SS-UE2 (MCX Client) responds with a SIP 200 (OK) message. --> SIP 200 (OK) - - A.2.11.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). A.2.12 MCX Presence Event Status Change A.2.12.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.12.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.12.3 Procedure Table A.2.12.3-1: MCX Presence Event Status Change St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCX Client) sends a SIP PUBLISH message. --> SIP PUBLISH - P 2 Check: Does the MCX Server respond to the SIP PUBLISH message with a SIP 200 (OK) message? <-- SIP 200 (OK) - - 3 Check: Does the MCX Server send a SIP NOTIFY message informing about the status change progress? <-- SIP NOTIFY - P 4 The SS-UE (MCX Client) responds with a SIP 200 (OK) --> SIP 200 (OK) - - ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 348 St Procedure Message Sequence TP Verdict U - S Message 5 Check: Does the MCX Server send a SIP NOTIFY informing about the final status? <-- SIP NOTIFY - P 6 The SS-UE responds with a SIP 200 (OK). --> SIP 200 (OK) - - NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.12.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.2.12.4-1: SIP PUBLISH (Step 1, Table A.2.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.11-1, condition PRESENCE-EVENT Table A.2.12.4-2: MCPTT-Info in SIP PUBLISH (Table A.2.12.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri encrypted (see note) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [4] (3GPP TS 24.379) clauses 9.2.1.3 and 9A.2.1.3 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1A. Table A.2.12.4-3: MCVideo-Info in SIP PUBLISH (Table A.2.12.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-request-uri encrypted (see note) <mcvideo-request-uri> with mcvideoURI set to px_MCVIDEO_ID_User_A ETSI TS 124 281 [10] (3GPP TS 24.281) clause 8.2.1.3 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2A. Table A.2.12.4-4: MCData-Info in SIP PUBLISH (Table A.2.12.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-3 Information Element Value/remark Comment Reference Condition mcdatainfo mcdata-Params mcdata-request-uri encrypted (see note) <mcdata-request-uri> with mcdataURI set to px_MCDATA_ID_User_A ETSI TS 124 282 [9] (3GPP TS 24.282) clauses 8.2.3 and 22.2.1.3 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-3A. Table A.2.12.4-5: SIP 200 (OK) (Step 2, Table A.2.12.3-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 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 349 Table A.2.12.4-3: SIP NOTIFY (Steps 3 and 5, Table A.2.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, condition PRESENCE-EVENT Table A.2.12.4-4: SIP 200 (OK) (Steps 4 and 6, Table A.2.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1 A.2.13 MCX Participating Terminated pre-established session establishment A.2.13.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT or MCVideo. A.2.13.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.13.3 Procedure Table A.2.13.3-1: MCX Participating Terminated pre-established session establishment St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCX Client) sends a SIP INVITE message in order to create a pre-established session --> SIP INVITE - - - EXCEPTION: Step 2a1 describes behaviour that depends on the MCX Server implementation; the "lower case letter" identifies a step sequence that take place if the MCX Server responds to a SIP INVITE with a SIP 100 (Trying) - - - - 2a1 Check: Does the MCX Server respond with a SIP 100 (Trying) message? <-- SIP 100 Trying - P 3 Check: Does the MCX Server respond with a SIP 200 (OK) message? <-- SIP 200 (OK) - P 4 The SS-UE (MCX Client) responds with a SIP ACK message. --> SIP ACK - - NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.13.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.2.13.4-1: SIP INVITE (Step 1, Table A.2.13.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3.3.4-1 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 350 Table A.2.13.4-2: SIP 200 (OK) (Step 3, Table A.2.13.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3.3.4-2 A.2.14 MCX Participating Terminated session establishment/modification without provisional responses other than 100 Trying A.2.14.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT or MCVideo. A.2.14.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.14.3 Procedure Table A.2.14.3-1: MCX Participating Terminated session establishment/modification without provisional responses other than 100 Trying St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCX Client) sends a SIP INVITE requesting the establishment/modification of a call (see note) --> SIP INVITE - - - EXCEPTION: Step 2a1 describes behaviour that depends on the MCX Server implementation; the "lower case letter" identifies a step sequence that take place if the MCX Server responds to a SIP INVITE with a SIP 100 (Trying) - - - - 2a1 Check: Does the MCX Server respond with a SIP 100 Trying? <-- SIP 100 (Trying) - P 3 Check: Does the MCX Server respond with a SIP 200 (OK)? <-- SIP 200 (OK) - P 4 The SS-UE (MCX Client) sends a SIP ACK to acknowledge the session establishment/modification (Note) --> SIP ACK - - NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.14.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.2.14.4-1: SIP INVITE (Step 1, Table A.2.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.1-1 (see note). NOTE: With condition re_INVITE for session modifications. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 351 Table A.2.14.4-1: SIP 200 (OK) (Step 3, Table A.2.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 with condition INVITE-RSP A.2.15 MCX Participating Terminated call release A.2.15.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.15.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.15.3 Procedure Table A.2.15.3-1: MCX Participating Terminated call release St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCX Client) sends a SIP BYE request to terminate the MCX session (see note) --> SIP BYE - - 2 Check: Does the MCX Server respond with a SIP 200 (OK) message? <-- SIP 200 (OK) - P NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.15.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). A.2.16 MCX Participating Originated session establishment/modification without provisional responses other than 100 Trying A.2.16.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT or MCVideo. A.2.16.2 Definition of system information messages N/a (out of E-UTRA coverage). ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 352 A.2.16.3 Procedure Table A.2.16.3-1: MCX Participating Originated session establishment/modification without provisional responses other than 100 Trying St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCX Server send a SIP INVITE requesting the establishment/modification of a call? <-- SIP INVITE - P 2 The SS-UE (MCX Client) sends a SIP 100 Trying (see note) --> SIP 100 (Trying) - - 3 The SS-UE (MCX Client) responds with a SIP 200 (OK) (see note) --> SIP 200 (OK) - - 4 Check: Does the MCX server send a SIP ACK to acknowledge the session establishment/modification? <-- SIP ACK - P NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.16.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.2.16.4-1: SIP INVITE (Step 1, Table A.2.16.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1 (see note). NOTE: With condition re_INVITE for session modifications. Table A.2.16.4-2: SIP 200 (OK) (Step 3, Table A.2.16.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1 with condition INVITE-RSP A.2.17 MCX Participating Originated call release A.2.17.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.17.2 Definition of system information messages N/a (out of E-UTRA coverage). ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 353 A.2.17.3 Procedure Table A.2.17.3-1: MCX Participating Originated call release St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCX Server send a SIP BYE request to terminate the MCX session? <-- SIP BYE - P 2 The SS-UE (MCX Client) responds with a SIP 200 (OK) message (see note). --> SIP 200 (OK) - - NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.17.4 Specific message contents All message contents are as specified in clause 5.5. and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). A.2.18 MCX E2E session establishment/modification without provisional responses other than 100 Trying A.2.18.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT or MCVideo. A.2.18.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.18.3 Procedure Table A.2.18.3-1: MCX E2E session establishment/modification without provisional responses other than 100 Trying St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCX Client) sends a SIP INVITE requesting the establishment/modification of a call --> SIP INVITE - - 2 Check: Does the MCX Server forward the SIP INVITE requesting the establishment/modification of a call to SS-UE2 (MCX Client)? <-- SIP INVITE - P 3 The SS-UE2 (MCX Client) sends a SIP 100 Trying --> SIP 100 (Trying) - - 4 Check: Does the MCX Server respond with a SIP 100 Trying to SS-UE1 (MCX Client)? <-- SIP 100 (Trying) - P 5 The SS-UE2 (MCX Client) responds with a SIP 200 (OK) --> SIP 200 (OK) - - 6 Check: Does the MCX Server respond with a SIP 200 (OK) to SS-UE1 (MCX Client)? <-- SIP 200 (OK) - P 7 The SS-UE1 (MCX Client) sends a SIP ACK to acknowledge the session establishment/modification --> SIP ACK - - ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 354 St Procedure Message Sequence TP Verdict U - S Message 8 Check: Does the MCX server send a SIP ACK to acknowledge the session establishment/modification to SS-UE2? <-- SIP ACK - P A.2.18.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.2.18.4-1: SIP INVITE (Step 1, Table A.2.18.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.1-1 (see note). NOTE: With condition re_INVITE for session modifications. Table A.2.18.4-2: SIP INVITE (Step 2, Table A.2.18.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1 (see note). NOTE: With condition re_INVITE for session modifications. Table A.2.18.4-1: SIP 200 (OK) (Step 5, Table A.2.18.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1 with condition INVITE-RSP Table A.2.18.4-1: SIP 200 (OK) (Step 6, Table A.2.18.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 with condition INVITE-RSP A.2.19 MCX E2E call release A.2.19.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.19.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.19.3 Procedure Table A.2.19.3-1: MCX E2E call release St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCX Client) sends a SIP BYE request to terminate the MCX session --> SIP BYE - - 2 Check: Does the MCX Server respond a SIP BYE request to terminate the MCX session to SS-UE2 (MCX Client)? <-- SIP BYE - P ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 355 St Procedure Message Sequence TP Verdict U - S Message 3 The SS-UE2 (MCX Client) responds with a SIP 200 (OK) message. --> SIP 200 (OK) - - 4 Check: Does the MCX Server respond a SIP 200 (OK) message to SS-UE1? <-- SIP 200 (OK) - P A.2.19.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.2.19.4-1: SIP BYE from the SS-UE1 (Step 1, Table A.2.19.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.2.1-1 Table A.2.19.4-2: SIP BYE from the MCPTT Server (Step 2, Table A.2.19.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.2.2-1 A.2.20 MCX E2E group call establishment, manual commencement A.2.20.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.20.2 Definition of system information messages N/a (out of E-UTRA coverage). A.2.20.3 Procedure Table A.2.20.3-1: MCX E2E group call establishment, manual commencement St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCX Client) sends a SIP INVITE requesting the establishment/modification of a call --> SIP INVITE - - 2 Check: Does the MCX Server forward the SIP INVITE requesting the establishment/modification of a call to SS-UE2 (MCX Client)? <-- SIP INVITE - P 3 The SS-UE2 (MCX Client) sends a SIP 100 Trying --> SIP 100 (Trying) - - 4 Check: Does the MCX Server respond with a SIP 100 Trying to SS-UE1 (MCX Client)? <-- SIP 100 (Trying) - P 5 The SS-UE2 (MCX Client) sends a SIP 183 (Session Progress) reliably. --> SIP 183 (Session Progress) - - ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 356 St Procedure Message Sequence TP Verdict U - S Message 6 Check: Does the MCX Server acknowledge the receipt of SIP 183 (Session Progress) from SS- UE2? <-- PRACK - P 7 The SS-UE2 (MCX Client) responds a SIP 200 (OK) to PRACK message --> SIP 200 (OK) - - 8 The SS-UE2 (MCX Client) responds with a SIP 200 (OK) --> SIP 200 (OK) - - 9 Check: Does the MCX Server respond with a SIP 200 (OK) to SS-UE1 (MCX Client)? <-- SIP 200 (OK) - P 10 The SS-UE1 (MCX Client) sends a SIP ACK to acknowledge the session establishment/modification --> SIP ACK - - 11 Check: Does the MCX server send a SIP ACK to acknowledge the session establishment/modification to SS-UE2? <-- SIP ACK - P A.2.20.4 Specific message contents All message contents are as specified in clause 5.5 with conditions GROUP-CALL and MANUAL; and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). For chat group calls, CHAT-GROUP-CALL condition applies instead of GROUP-CALL. Table A.2.20.4-1: SIP 200 (OK) (Step 8, Table A.2.20.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1 with condition INVITE-RSP Table A.2.20.4-2: SIP 200 (OK) (Step 9, Table A.2.20.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 with condition INVITE-RSP A.2.21 MCX E2E private call establishment, manual commencement A.2.21.1 Initial conditions As specified in the test case which calls the procedure. Within the context of this procedure, MCX refers to MCPTT, MCVideo or MCData. A.2.21.2 Definition of system information messages N/a (out of E-UTRA coverage). ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 357 A.2.21.3 Procedure Table A.2.21.3-1: MCX E2E private call establishment, manual commencement St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCX Client) sends a SIP INVITE requesting the establishment/modification of a call --> SIP INVITE - - 2 Check: Does the MCX Server forward the SIP INVITE requesting the establishment/modification of a call to SS-UE2 (MCX Client)? <-- SIP INVITE - P 3 The SS-UE2 (MCX Client) sends a SIP 100 Trying --> SIP 100 (Trying) - - 4 Check: Does the MCX Server respond with a SIP 100 Trying to SS-UE1 (MCX Client)? <-- SIP 100 (Trying) - P 5 The SS-UE2 (MCX Client) sends a SIP 180 (Ringing) unreliably. --> SIP 180 (Ringing) - - 6 Check: Does the MCX Server respond with a unreliable SIP 180 (Ringing) to SS-UE1 (MCX Client)? <-- SIP 180 (Ringing) - P 7 The SS-UE2 (MCX Client) responds with a SIP 200 (OK) --> SIP 200 (OK) - - 8 Check: Does the MCX Server respond with a SIP 200 (OK) to SS-UE1 (MCX Client)? <-- SIP 200 (OK) - P 9 The SS-UE1 (MCX Client) sends a SIP ACK to acknowledge the session establishment/modification --> SIP ACK - - 10 Check: Does the MCX server send a SIP ACK to acknowledge the session establishment/modification to SS-UE2? <-- SIP ACK - P A.2.21.4 Specific message contents All message contents are as specified in clause 5.5 with conditions PRIVATE-CALL and MANUAL; and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.2.21.4-1: SIP 200 (OK) (Step 7, Table A.2.21.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1 with condition INVITE-RSP Table A.2.21.4-1: SIP 200 (OK) (Step 8, Table A.2.21.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 with condition INVITE-RSP A.3 Generic test procedures for MCPTT Server-Client operation A.3.0 General The purpose of the procedures specified in the following clauses is to facilitate test description by providing MCPTT procedure sequences which can be referred from the relevant TCs specified in the present document. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 358 The procedures specified are required to ensure that MCPTT service can take place between a MCPTT Client and a MCPTT server or specific MCPTT relevant pre-conditions are met before a test case can be executed. A.3.1 MCPTT E2E session establishment/modification without provisional responses other than 100 Trying A.3.1.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.1.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.1.3 Procedure Table A.3.1.3-1: MCPTT E2E session establishment/modification without provisional responses other than 100 Trying St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCPTT server correctly perform test procedure MCX E2E session establishment/modification without provisional responses other than 100 Trying' for as described in Table A.2.18.3-1 with MCPTT as MCX? - - - P - EXCEPTION: Step 2a1 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the SS-UE1 requests implicit floor control in the SIP INVITE request but it is not implicitly granted (see note) - - - - 2a1 Check: Does the MCPTT server send a Floor Granted message to SS-UE1? <-- Floor Granted - P - EXCEPTION: Step 3a1 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place when the floor is granted to SS-UE1, either implicit or explicitly (see note) - - - - 3a1 Check: Does the MCPTT server send a Floor Taken message to SS-UE2? <-- Floor Taken - P - EXCEPTION: Steps 4a1-4a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place when the floor is not granted to SS- UE1 (see note) - - - - 4a1 Check: Does the MCPTT server send a Floor Idle message to SS-UE1? <-- Floor Idle - P 4a2 Check: Does the MCPTT server send a Floor Idle message to SS-UE2? <-- Floor Idle - P NOTE: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS-UE1 sends SDP offer with media description for floor control but without implicit floor request. b. SS-UE1 sends SDP offer with media description for floor control and with implicit floor request: i. SDP answer from MCPTT Server contains "mc_implicit_request" and "mc_granted" (Floor is implicitly granted). ii. SDP answer from MCPTT Server contains "mc_implicit request" and but no "mc_granted" (Floor needs to be explicitly granted at step 2a1). iii. SDP answer from MCPTT Server contains no "mc_implicit_request"and no "mc_granted" (the UE needs to explicitly request the floor). c. SS-UE1 sends SDP offer without media description for floor control. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 359 A.3.1.4 Specific message contents All message contents are as specified in clause 5.5 with condition MCPTT and in the test case calling the procedure with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.1.4-1: SIP INVITE (Step 1, Table A.3.1.3-1; Step 1, Table A.2.18.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.1-1 (see note), with condition MCPTT Information Element Value/remark Comment Reference Condition Session-Expires IETF RFC 4028 [22] generic-param "1800" The recommended initial value is 1 800 in IETF RFC 4028 [22]. Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.1.4-2 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table A.3.1.4-3 NOTE: With condition re_INVITE for session modifications. Table A.3.1.4-2: SDP in SIP INVITE (Table A.3.1.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, with condition INITIAL_SDP_OFFER. Information Element Value/remark Comment Reference Condition Session description: Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "11111111" A numeric string such that the tuple of <username>, <sess- id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session. sess-version "11111111" Session Name " " s= line single empty space indicating no session name Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [13] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [12] clause 6 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 360 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, with condition INITIAL_SDP_OFFER. Information Element Value/remark Comment Reference Condition fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS- UE Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [8] "RR" 2000 IETF RFC 3556 [8] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time media attribute a= line attribute =maxptime maxptime "240" maximum packet time Media description[2] Media description for media control NOT WITHOUT_ FLOORCO NTROL media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS-UE being different than the port number of the audio channel (RTP) and its associated control channel (RTCP)" The port for the media control entity Connection Data c= line connection-address IP address of the SS- UE media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 pc_MCPTT _FloorRequ estQueuein g ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 361 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, with condition INITIAL_SDP_OFFER. Information Element Value/remark Comment Reference Condition mc_priority The priority value specified in the MCPTT Group configuration The value of the <user-priority> element for the user in the MCPTT Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.1-1) See note 3 ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 GROUP- CALL OR CHAT- GROUP- CALL mc_priority The max priority value specified in the MCPTT Service configuration The value of the <num-levels-priority- hierarchy> element for on-network in the MCPTT Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL NOTE 1: If the SS-UE requests a call with media floor control and implicit floor (Option b of note on Table A.3.1.3-1), apply condition IMPLICIT_GRANT_REQUESTED. NOTE 2: If the SS-UE requests a call without media floor (Option c of note on Table A.3.1.3-1), apply condition WITHOUT_FLOORCONTROL. NOTE 3: The <num-levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration has higher value than any <user-priority> element. (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1). Table A.3.1.4-3: MCPTT-Info in SIP INVITE (Table A.3.1.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1, condition INVITE_REFER Table A.3.1.4-4: SIP INVITE from the MCPTT-Server (Step 1, Table A.3.1.3-1; Step 2 Table A.2.18.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1 (see note), with condition MCPTT Information Element Value/remark Comment Reference Condition Resource-Priority IETF RFC 4412 [20] IETF RFC 7134 [16] IETF RFC 8101 [18] EMERGEN CY-CALL or IMMPERIL- CALL r-value EMERGEN CY-CALL namespace value of the <resource- priority-namespace> element contained in the <emergency-resource- priority> element contained in the <OnNetwork> element of the MCX service configuration documents As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo r-priority value of the <resource- priority-priority> element contained in the <emergency-resource- priority> element contained in the <OnNetwork> element of the MCX service configuration document As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo r-value IMMPERIL- CALL ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 362 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1 (see note), with condition MCPTT Information Element Value/remark Comment Reference Condition namespace value of the <resource- priority-namespace> element contained in the <imminent-peril- resource-priority> element contained in the <OnNetwork> element of the MCX service configuration documents As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo r-priority value of the <resource- priority-priority> element contained in the <imminent-peril- resource-priority> element contained in the <OnNetwork> element of the MCX service configuration document As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo Session-Expires IETF RFC 4028 [22] delta-seconds any allowed value Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.1.4-5 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table A.3.1.4-6 NOTE: With condition re_INVITE for session modifications. Table A.3.1.4-5: SDP in SIP INVITE (Table A.3.1.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, with condition INITIAL_SDP_OFFER Information Element Value/remark Comment Reference Condition Media description[2] NOT WITHOUT_ FLOORCO NTROL media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters mc_priority Any value lower or equal to the priority specified in the MCPTT Group configuration The value of the <user- priority> element for the user in the MCPTT Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.1-1) See note 2 ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 GROUP- CALL OR CHAT- GROUP- CALL mc_priority Any value lower or equal to the priority specified in the MCPTT Service configuration The value of the <num- levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 363 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, with condition INITIAL_SDP_OFFER Information Element Value/remark Comment Reference Condition Present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 pc_MCPTT _FloorRequ estQueuein g NOTE 1: If the SS-UE1 requests a call without media floor control (Option c of note on Table A.3.1.3-1), apply condition WITHOUT_FLOORCONTROL. NOTE 2: The <num-levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration has higher value than any <user-priority> element. (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1). Table A.3.1.4-6: MCPTT-Info in SIP INVITE (Table A.3.1.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (see note) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_B The URI of the called user mcptt-calling-user-id Encrypted (see note) <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_A The URI of the calling user NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1A Table A.3.1.4-7: SIP 200 (OK) (Step 1, Table A.3.1.3-1; Step 5, Table A.2.18.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1 with condition MCPTT and INVITE- RSP Information Element Value/remark Comment Reference Condition Content-Type IETF RFC 5621 [14] value "application/sdp" Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.1.4-8 Table A.3.1.4-8: SDP in SIP 200 (OK) (Table A.3.1.4-7) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition Session description: Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "11111111" A numeric string such that the tuple of <username>, <sess- id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session. sess-version "11111111" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 364 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition Session Name " " s= line single empty space indicating no session name Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [13] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [12] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS-UE Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [8] "RR" 2000 IETF RFC 3556 [8] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time media attribute a= line attribute =maxptime maxptime "240" maximum packet time Media description[2] Media description for media control NOT WITHOUT_ FLOORCO NTROL media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS-UE being different than the port number of the audio channel (RTP) and its associated control channel (RTCP)" The port for the media control entity Connection Data c= line connection-address IP address of the SS-UE ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 365 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters NOT WITHOUT_ FLOORCO NTROL mc_queueing present if included in the offer Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Table A.3.1.4-9: SIP 200 (OK) (Step 1, Table A.3.1.3-1; Step 6, Table A.2.18.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 with condition MCPTT and INVITE- RSP Information Element Value/remark Comment Reference Condition Session-Expires generic-param Same value as session expires header in SIP INVITE or lower Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.1.4-10 Table A.3.1.4-10: SDP in SIP 200 (OK) (Table A.3.1.4-9) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition Media description[2] NOT WITHOUT_ FLOORCO NTROL media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters mc_queueing present if included in the offer Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_priority if a value is provided in the offer: the value defined in the MCPTT Group Configuration or the value provided in the offer, whichever is the lower value; otherwise not present The value of the <user- priority> element for the user in the MCPTT Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.1-1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 GROUP- CALL OR CHAT- GROUP- CALL ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 366 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition mc_priority if a value is provided in the offer: the value defined in the MCPTT Service Configuration or the value provided in the offer, whichever is the lower value; otherwise not present The value of the <num- levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_granted not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_F LOOR_GR ANTED mc_implicit_request not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_ssrc not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 same value as in the offer if provided in the offer and there is no collision with the value used by the SS; otherwise value assigned by the SS ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_no_floor_ctrl not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 NOTE 1: If the SS-UE requests an implicit floor (Option b of note on Table A.3.1.3-1), more conditions may apply: i. If the server implicitly grants the floor, conditions IMPLICIT_GRANT_REQUESTED and IMPLICIT_FLOOR_GRANTED are also applied. ii. If the floor needs to be explicitly granted, condition IMPLICIT_GRANT_REQUESTED applies. NOTE 2: If the SS-UE requests a call without media floor (Option c of note on Table A.3.1.3-1) apply condition WITHOUT_FLOORCONTROL NOTE 3: Elements whose values mention the SS shall be understood as if they were referring to the MCPTT Server. A.3.2 MCPTT E2E group call establishment, manual commencement A.3.2.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.2.2 Definition of system information messages N/a (out of E-UTRA coverage). ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 367 A.3.2.3 Procedure Table A.3.2.3-1: MCPTT E2E group call establishment, manual commencement St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCPTT server correctly perform test procedure MCX E2E group call establishment, manual commencement' as described in Table A.2.20.3-1 with MCPTT as MCX? - - - P - EXCEPTION: Step 2a1 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the SS-UE1 requests implicit floor control in the SIP INVITE request but it is not implicitly granted (see note) - - - - 2a1 Check: Does the MCPTT server send a Floor Granted message to SS-UE1? <-- Floor Granted - P - EXCEPTION: Step 3a1 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place when the floor is granted to SS-UE1, either implicit or explicitly (see note) - - - - 3a1 Check: Does the MCPTT server send a Floor Taken message to SS-UE2? <-- Floor Taken - P - EXCEPTION: Steps 4a1-4a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place when the floor is not granted to SS- UE1. (see note) - - - - 4a1 Check: Does the MCPTT server send a Floor Idle message to SS-UE1? <-- Floor Idle - P 4a2 Check: Does the MCPTT server send a Floor Idle message to SS-UE2? <-- Floor Idle - P NOTE: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS-UE1 sends SDP offer with media description for floor control but without implicit floor request. b. SS-UE1 sends SDP offer with media description for floor control and with implicit floor request: i. SDP answer from MCPTT Server contains "mc_implicit_request" and "mc_granted" (Floor is implicitly granted). ii. SDP answer from MCPTT Server contains "mc_implicit request" and but no "mc_granted" (Floor needs to be explicitly granted at step 2a1). iii. SDP answer from MCPTT Server contains no "mc_implicit_request"and no "mc_granted" (the UE needs to explicitly request the floor). A.3.2.4 Specific message contents All message contents are as specified in clause 5.5 with condition MCPTT and in the test case calling the procedure with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 368 Table A.3.2.4-1: SIP INVITE from the SS-UE1 (Step 1, Table A.3.2.3-1;Step 1, Table A.2.20.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.1-1, with condition MCPTT and MANUAL Information Element Value/remark Comment Reference Condition Session-Expires IETF RFC 4028 [22] generic-param "1800" The recommended initial value is 1800 in IETF RFC 4028 [22]. Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.2.4-2 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table A.3.2.4-3 Table A.3.2.4-2: SDP in SIP INVITE (Table A.3.2.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, with conditions INITIAL_SDP_OFFER and IMPLICIT_GRANT_REQUESTED if the SS-UE1 requests implicit floor. Information Element Value/remark Comment Reference Condition Session description: Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "11111111" A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast- address> forms a globally unique identifier for the session. sess-version "11111111" Session Name " " s= line single empty space indicating no session name Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [13] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [12] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS-UE Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [8] "RR" 2000 IETF RFC 3556 [8] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 369 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, with conditions INITIAL_SDP_OFFER and IMPLICIT_GRANT_REQUESTED if the SS-UE1 requests implicit floor. Information Element Value/remark Comment Reference Condition media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time media attribute a= line attribute =maxptime maxptime "240" maximum packet time Media description[2] Media description for media control media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS-UE being different than the port number of the audio channel (RTP) and its associated control channel (RTCP)" The port for the media control entity Connection Data c= line connection-address IP address of the SS-UE media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 pc_MCPTT _FloorRequ estQueuein g mc_priority The priority value specified in the MCPTT Group configuration The value of the <user- priority> element for the user in the MCPTT Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.1- 1) See note ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 NOTE: The <num-levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration has higher value than any <user-priority> element. (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1). Table A.3.2.4-3: MCPTT-Info in SIP INVITE (Table A.3.2.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1, condition GROUP-CALL, INVITE_REFER ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 370 Table A.3.2.4-4: SIP INVITE from the MCPTT-Server (Step 1, Table A.3.2.3-1; Step 2, Table A.2.20.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1, with condition MCPTT and MANUAL Information Element Value/remark Comment Reference Condition Resource-Priority IETF RFC 4412 [20] IETF RFC 7134 [16] IETF RFC 8101 [18] EMERGEN CY-CALL or IMMPERIL- CALL r-value EMERGEN CY-CALL namespace value of the <resource- priority-namespace> element contained in the <emergency- resource-priority> element contained in the <OnNetwork> element of the MCX service configuration documents As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo r-priority value of the <resource- priority-priority> element contained in the <emergency- resource-priority> element contained in the <OnNetwork> element of the MCX service configuration document As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo r-value IMMPERIL- CALL namespace value of the <resource- priority-namespace> element contained in the <imminent-peril- resource-priority> element contained in the <OnNetwork> element of the MCX service configuration documents As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo r-priority value of the <resource- priority-priority> element contained in the <imminent-peril- resource-priority> element contained in the <OnNetwork> element of the MCX service configuration document As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo Session-Expires IETF RFC 4028 [22] delta-seconds any allowed value Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.2.4-5 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table A.3.2.4-6 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 371 Table A.3.2.4-5: SDP in SIP INVITE (Table A.3.2.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, with condition INITIAL_SDP_OFFER Information Element Value/remark Comment Reference Condition Media description[2] media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters mc_priority Any value lower or equal to the priority specified in the MCPTT Group configuration The value of the <user- priority> element for the user in the MCPTT Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.1-1) See note ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 pc_MCPTT _FloorRequ estQueuein g NOTE: The <num-levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration has higher value than any <user-priority> element. (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1). Table A.3.2.4-6: MCPTT-Info in SIP INVITE (Table A.3.2.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1, condition GROUP-CALL (note 1) Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (note 2) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_B The URI of the called user mcptt-calling-user-id Encrypted (ote 2) <mcptt- calling-user-id> with mcpttURI set to px_MCPTT_ID_User_A The URI of the calling user NOTE 1: For chat group calls CHAT-GROUP-CALL condition shall be used instead of GROUP-CALL. NOTE 2: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1A. Table A.3.2.4-7: SIP 200 (OK) from the SS-UE2 (Step 1, Table A.3.2.3-1; Step 8, Table A.2.20.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1, with condition MCPTT, INVITE-RSP and GROUP-CALL (note) Information Element Value/remark Comment Reference Condition Content-Type IETF RFC 5621 [14] value "application/sdp" Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.2.4-8 NOTE: For chat group calls CHAT-GROUP-CALL condition shall be used instead of GROUP-CALL. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 372 Table A.3.2.4-8: SDP in SIP 200 (OK) (Table A.3.2.4-7) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition Session description: Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "11111111" A numeric string such that the tuple of <username>, <sess- id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session. sess-version "11111111" Session Name " " s= line single empty space indicating no session name Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [13] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [12] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS-UE Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [8] "RR" 2000 IETF RFC 3556 [8] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time media attribute a= line attribute =maxptime maxptime "240" maximum packet time Media description[2] Media description for media control ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 373 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS-UE being different than the port number of the audio channel (RTP) and its associated control channel (RTCP)" The port for the media control entity Connection Data c= line connection-address IP address of the SS- UE1 media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters mc_queueing present if included in the offer Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Table A.3.2.4-9: SIP 200 (OK) from the MCPTT Server (Step 1, Table A.3.2.3-1; Step 9, Table A.2.20.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1, with condition MCPTT and INVITE- RSP Information Element Value/remark Comment Reference Condition Session-Expires generic-param Same value as session expires header in SIP INVITE or lower Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.2.4-10 Table A.3.2.4-10: SDP in SIP 200 (OK) (Table A.3.2.4-9) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition Media description [2] media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters mc_priority if a value is provided in the offer: the value defined in the MCPTT Group Configuration or the value provided in the offer, whichever is the lower value; otherwise not present The value of the <user-priority> element for the user in the MCPTT Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.1-1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 374 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition mc_ssrc any value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 NOTE 1: If the SS-UE requests an implicit floor (Option b of note on Table A.3.2.3-1), more conditions may apply: i. If the server implicitly grants the floor, conditions IMPLICIT_GRANT_REQUESTED and IMPLICIT_FLOOR_GRANTED are also applied. ii. If the floor needs to be explicitly granted, condition IMPLICIT_GRANT_REQUESTED applies. NOTE 2: Elements whose values mention the SS shall be understood as if they were referring to the MCPTT Server. Table A.3.2.4-11: SIP 183 (Session Progress) from the SS-UE2 (Step 1, Table A.3.2.3-1; Step 5, Table A.2.20.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.16.3.2-1, with condition MCPTT and 100rel A.3.3 MCPTT E2E private call establishment, manual commencement A.3.3.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.3.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.3.3 Procedure Table A.3.3.3-1: MCPTT E2E private call establishment, manual commencement St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCPTT server correctly perform test procedure MCX E2E private call establishment, manual commencement' as described in Table A.2.21.3-1 with MCPTT as MCX? - - - P - EXCEPTION: Step 2a1 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the SS-UE1 requests implicit floor control in the SIP INVITE request but it is not implicitly granted (Note) - - - - 2a1 Check: Does the MCPTT server send a Floor Granted message to SS-UE1? <-- Floor Granted - P - EXCEPTION: Step 3a1 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place when the floor is granted to SS-UE1, either implicit or explicitly. (Note) - - - - 3a1 Check: Does the MCPTT server send a Floor Taken message to SS-UE2? <-- Floor Taken - P - EXCEPTION: Steps 4a1-4a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place when the floor is not granted to SS- UE1 (Note) - - - - 4a1 Check: Does the MCPTT server send a Floor Idle message to SS-UE1? <-- Floor Idle - P ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 375 St Procedure Message Sequence TP Verdict U - S Message 4a2 Check: Does the MCPTT server send a Floor Idle message to SS-UE2? <-- Floor Idle - P NOTE: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS-UE1 sends SDP offer with media description for floor control but without implicit floor request. b. SS-UE1 sends SDP offer with media description for floor control and with implicit floor request: i. SDP answer from MCPTT Server contains "mc_implicit_request" and "mc_granted" (Floor is implicitly granted). ii. SDP answer from MCPTT Server contains "mc_implicit request" and but no "mc_granted" (Floor needs to be explicitly granted at step 2a1). iii. SDP answer from MCPTT Server contains no "mc_implicit_request"and no "mc_granted" (the UE needs to explicitly request the floor). c. SS-UE1 sends SDP offer without media description for floor control. A.3.3.4 Specific message contents All message contents are as specified in clause 5.5 with condition MCPTT and in the test case calling the procedure with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.3.4-1: SIP INVITE from the SS-UE1 (Step 1, Table A.3.3.3-1; Step 1, Table A.2.21.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.1-1, with condition MCPTT, PRIVATE- CALL and MANUAL Information Element Value/remark Comment Reference Condition Session-Expires IETF RFC 4028 [22] generic-param "1800" The recommended initial value is 1800 in IETF RFC 4028 [22]. Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.3.4-2 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table A.3.3.4-3 Table A.3.3.4-2: SDP in SIP INVITE (Table A.3.3.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, with conditions INITIAL_SDP_OFFER and PRIVATE-CALL Information Element Value/remark Comment Reference Condition Session description: Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "11111111" A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session. sess-version "11111111" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 376 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, with conditions INITIAL_SDP_OFFER and PRIVATE-CALL Information Element Value/remark Comment Reference Condition Session Name " " s= line single empty space indicating no session name Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [13] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [12] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS-UE Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [8] "RR" 2000 IETF RFC 3556 [8] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time media attribute a= line attribute =maxptime maxptime "240" maximum packet time Media description[2] Media description for media control NOT WITHOUT_ FLOORCO NTROL media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS-UE being different than the port number of the audio channel (RTP) and its associated control channel (RTCP)" The port for the media control entity ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 377 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, with conditions INITIAL_SDP_OFFER and PRIVATE-CALL Information Element Value/remark Comment Reference Condition Connection Data c= line connection-address IP address of the SS-UE media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 pc_MCPTT _FloorRequ estQueuein g mc_priority The max priority value specified in the MCPTT Service configuration The value of the <num- levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4- 1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 NOTE 1: If the SS-UE requests a call with media floor control and implicit floor (Option b of note on Table A.3.3.3-1), apply condition IMPLICIT_GRANT_REQUESTED. NOTE 2: If the SS-UE requests a call without media floor (Option c of NOTE1 on Table A.3.3.3-1), apply condition WITHOUT_FLOORCONTROL. Table A.3.3.4-3: MCPTT-Info in SIP INVITE (Table A.3.3.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1, condition PRIVATE-CALL, INVITE_REFER Table A.3.3.4-4: SIP INVITE from the MCPTT-Server to SS-UE2 (Step 1, Table A.3.3.3-1; Step 2, Table A.2.21.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1, with condition MCPTT and MANUAL Information Element Value/remark Comment Reference Condition Resource-Priority IETF RFC 4412 [20] IETF RFC 7134 [16] IETF RFC 8101 [18] EMERGEN CY-CALL or IMMPERIL- CALL r-value EMERGEN CY-CALL namespace value of the <resource- priority-namespace> element contained in the <emergency-resource- priority> element contained in the <OnNetwork> element of the MCX service configuration documents As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 378 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1, with condition MCPTT and MANUAL Information Element Value/remark Comment Reference Condition r-priority value of the <resource- priority-priority> element contained in the <emergency-resource- priority> element contained in the <OnNetwork> element of the MCX service configuration document As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in Table 5.5.8.8-1 for MCVideo r-value IMMPERIL- CALL namespace value of the <resource- priority-namespace> element contained in the <imminent-peril-resource- priority> element contained in the <OnNetwork> element of the MCX service configuration documents As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo r-priority value of the <resource- priority-priority> element contained in the <imminent-peril-resource- priority> element contained in the <OnNetwork> element of the MCX service configuration document As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo Session-Expires IETF RFC 4028 [22] delta-seconds any allowed value Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.3.4-5 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table A.3.3.4-6 Table A.3.3.4-5: SDP in SIP INVITE (Table A.3.3.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, with condition INITIAL_SDP_OFFER Information Element Value/remark Comment Reference Condition Media description[2] NOT WITHOUT_ FLOORCO NTROL media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters mc_priority Any value lower or equal to the priority specified in the MCPTT Service configuration The value of the <num-levels-priority- hierarchy> element for on-network in the MCPTT Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 379 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, with condition INITIAL_SDP_OFFER Information Element Value/remark Comment Reference Condition mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 pc_MCPTT _FloorRequ estQueuein g NOTE: If the SS-UE1 requests a call without media floor control (Option c of note on Table A.3.3.3-1), apply condition WITHOUT_FLOORCONTROL. Table A.3.3.4-6: MCPTT-Info in SIP INVITE (Table A.3.3.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1, condition PRIVATE-CALL Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_B The URI of the called user mcptt-calling-user-id Encrypted (note) <mcptt-calling- user-id> with mcpttURI set to px_MCPTT_ID_User_A The URI of the calling user NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1A. Table A.3.3.4-7: SIP 200 (OK) from the SS-UE2 to MCPTT Server (Step 1, Table A.3.3.3-1; Step 7, Table A.2.21.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1, with condition MCPTT and INVITE- RSP Information Element Value/remark Comment Reference Condition Content-Type IETF RFC 5621 [14] value "application/sdp" Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.3.4-8 Table A.3.3.4-8: SDP in SIP 200 (OK) (Table A.3.3.4-7) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition Session description: Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "11111111" A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session. sess-version "11111111" Session Name " " s= line single empty space indicating no session name ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 380 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [13] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [12] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS- UE Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [8] "RR" 2000 IETF RFC 3556 [8] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time media attribute a= line attribute =maxptime maxptime "240" maximum packet time Media description[2] Media description for media control NOT WITHOUT_ FLOORCO NTROL media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS-UE being different than the port number of the audio channel (RTP) and its associated control channel (RTCP)" The port for the media control entity Connection Data c= line connection-address IP address of the SS- UE media attribute a= line attribute = fmtp fmtp format "MCPTT" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 381 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition format specific parameters NOT WITHOUT_ FLOORCO NTROL mc_queueing present if included in the offer Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Table A.3.3.4-9: SIP 200 (OK) from the MCPTT Server to SS-UE1 (Step 1, Table A.3.3.3-1; Step 8, Table A.2.21.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1, with condition MCPTT and INVITE- RSP Information Element Value/remark Comment Reference Condition Session-Expires generic-param Same value as session expires header in SIP INVITE or lower Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.3.4-10 Table A.3.3.4-10: SDP in SIP 200 (OK) (Table A.3.3.4-9) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition Media description[2] NOT WITHOUT_ FLOORCO NTROL media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters mc_queueing present if included in the offer Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_priority if a value is provided in the offer: the value defined in the MCPTT Service Configuration or the value provided in the offer, whichever is the lower value; otherwise not present The value of the <num-levels-priority- hierarchy> element for on-network in the MCPTT Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 mc_granted not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_F LOOR_GR ANTED mc_implicit_request not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 382 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition mc_ssrc not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 same value as in the offer if provided in the offer and there is no collision with the value used by the SS; otherwise value assigned by the SS ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_no_floor_ctrl not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 NOTE 1: If the SS-UE1 request an implicit floor (Option b of note on Table A.3.3.3-1), more conditions may apply: i. If the server implicitly grants the floor, conditions IMPLICIT_GRANT_REQUESTED and IMPLICIT_FLOOR_GRANTED are also applied. ii. If the floor needs to be explicitly granted, condition IMPLICIT_GRANT_REQUESTED applies. NOTE 2: If the SS-UE1 request a call without media floor (Option c of note on Table A.3.3.3-1) apply condition WITHOUT_FLOORCONTROL. NOTE 3: Elements whose values mention the SS shall be understood as if they were referring to the MCPTT Server. Table A.3.3.4-11: SIP 180 (Ringing) response (Step 1, Table A.3.3.3-1; Steps 5, Table A.2.21.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.16.2.1-1, with condition MCPTT Table A.3.3.4-12: SIP 180 (Ringing) response (Step 1, Table A.3.3.3-1; Steps 6, Table A.2.21.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.16.2.2-1, with condition MCPTT A.3.4 MCPTT E2E call establishment using a pre-established session, manual commencement A.3.4.1 Initial conditions As specified in the test case which calls the procedure. A.3.4.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.4.3 Procedure Table A.3.4.3-1: MCPTT E2E call establishment using a pre-established session, manual commencement St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCPTT Client) sends a SIP REFER message to request the establishment of an MCPTT call using a pre-established session --> SIP REFER - - ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 383 St Procedure Message Sequence TP Verdict U - S Message 2 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE1 indicating that the MCPTT call has been properly requested? <-- SIP 200 (OK) - P 3 Check: Does the MCPTT Server send a SIP re- INVITE requesting the establishment of a call to SS-UE2 (MCPTT Client)? <-- SIP re-INVITE - P 4 The SS-UE2 (MCPTT Client) responds a SIP 100 Trying --> SIP 100 (Trying) - - 5 The SS-UE2 (MCPTT Client) responds with a SIP 200 (OK) --> SIP 200 (OK) - - 6 Check: Does the MCPTT server send a SIP ACK to acknowledge the session establishment to SS-UE2? <-- SIP ACK - P - EXCEPTION: Depending on the MCPTT Server implementation, the following steps might be performed in parallel. - - - - 7 Check: Does the MCPTT server send a Connect message to SS-UE1 (MCPTT Client)? <-- Connect - P 8 The SS-UE1 (MCPTT Client) sends an Acknowledgement in response to the Connect message. --> Acknowledge - - 9 Check: Does the MCPTT server send a Connect message to SS-UE2 (MCPTT Client)? <-- Connect - P 10 The SS-UE2 (MCPTT Client) sends an Acknowledgement in response to the Connect message. --> Acknowledge - - A.3.4.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.4.4-1: SIP REFER (Step 1, Table A.3.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.12-1 with conditions MCPTT and MANUAL Information Element Value/remark Comment Reference Condition Message-body IETF RFC 3261 [15] MIME body part Resource list IETF RFC 5366 [24] MIME-part-body Resource-lists as described in Table A.3.4.4-2 Table A.3.4.4-2: Resource-lists in SIP REFER (Table A.3.4.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-1, condition PRE-ESTABLISH with the uri attribute of the entry extended with the SIP URI header fields as specified in Table A.3.4.4-3A Table A.3.4.4-2A: SIP header fields extending the uri attribute of the resource-lists' single entry (Table A.3.4.4-2) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.12-2, condition MCPTT Information Element Value/remark Comment Reference Condition body MIME body part SDP Message MIME-part-headers Content-Type "application/sdp" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 384 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.12-2, condition MCPTT Information Element Value/remark Comment Reference Condition MIME-part-body SDP Message as described in Table A.3.4.4-2B MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table A.3.4.4-2C Table A.3.4.4-2B: SDP in SIP header fields (Table A.3.4.4-2A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_OFFER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition Session description: Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "11111111" A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast- address> forms a globally unique identifier for the session. sess-version "11111111" Session Name " " s= line single empty space indicating no session name Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [13] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [12] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS- UE Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [8] "RR" 2000 IETF RFC 3556 [8] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 385 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_OFFER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition media attribute a= line attribute =maxptime maxptime "240" maximum packet time media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for RTP foundation 1234 arbitrarily selected priority 2130706431 IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for RTCP foundation 1234 Same as for RTP priority 2130706430 IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id Media description[2] Media description for media control media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS-UE being different than the port number of the audio channel (RTP) and its associated control channel (RTCP)" The port for the media control entity Connection Data c= line connection-address IP address of the SS- UE media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters NOT WITHOUT_ FLOORCO NTROL mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 pc_MCPTT _FloorRequ estQueuein g mc_priority The priority value specified in the MCPTT Group configuration The value of the <user- priority> element for the user in the MCPTT Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.1-1) See note 2 ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 GROUP- CALL OR CHAT- GROUP- CALL ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 386 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_OFFER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition mc_priority The max priority value specified in the MCPTT Service configuration The value of the <num- levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_implicit_request not present present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_ssrc any value if present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_no_floor_ctrl not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 format specific parameters WITHOUT_ FLOORCO NTROL mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_priority not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 mc_granted not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_implicit_request not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_ssrc not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_no_floor_ctrl present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for Media Control messages foundation 4321 arbitrarily selected; different than for RTP/RTCP ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 387 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_OFFER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition priority 2130706430 IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id NOTE 1: If the SS-UE requests an implicit floor condition IMPLCIT_GRAN_REQUESTED also applies. NOTE 2: The <num-levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration has higher value than any <user-priority> element. (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1). Table A.3.4.4-2C: MCPTT-Info in SIP header fields (Table A.3.4.4-2A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1, condition INVITE-REFER Table A.3.4.4-3: SIP 200 (OK) (Step 2, Table A.3.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 with conditions MCPTT and REFER- RSP Information Element Value/remark Comment Reference Condition Content-Type media-type "application/sdp" Message-body SDP message SDP message as described in Table A.3.4.4-3A Table A.3.4.4-3A: SDP in SIP 200 (OK) (Table A.3.4.4-3) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [13] media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for RTP foundation any value priority any value IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for RTCP foundation any value priority any value IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id Media description[2] media attribute a= line attribute = fmtp fmtp format "MCPTT" ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 388 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition format specific parameters NOT WITHOUT_ FLOORCO NTROL mc_queueing present if included in the offer Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_priority if a value is provided in the offer: the value defined in the MCPTT Group Configuration or the value provided in the offer, whichever is the lower value; otherwise not present The value of the <user- priority> element for the user in the MCPTT Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.1-1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 GROUP- CALL OR CHAT- GROUP- CALL mc_priority if a value is provided in the offer: the value defined in the MCPTT Service Configuration or the value provided in the offer, whichever is the lower value; otherwise not present The value of the <num- levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4- 1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_granted not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_F LOOR_GR ANTED mc_implicit_request not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_ssrc not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 same value as in the offer if provided in the offer and there is no collision with the value used by the SS; otherwise value assigned by the SS ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_no_floor_ctrl not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 format specific parameters WITHOUT_ FLOORCO NTROL mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 389 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition mc_priority not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 mc_granted not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_implicit_request not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_ssrc not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_no_floor_ctrl present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for Media Control messages foundation any value priority any value IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id NOTE 1: If the SS-UE requests an implicit floor more conditions may apply: i. If the server implicitly grants the floor, conditions IMPLICIT_GRANT_REQUESTED and IMPLICIT_FLOOR_GRANTED are also applied. ii. If the floor needs to be explicitly granted, condition IMPLICIT_GRANT_REQUESTED applies. NOTE 2: If the SS-UE requests a call without media floor condition WITHOUT_FLOORCONTROL shall be applied. NOTE 3: Elements whose values mention the SS shall be understood as if they were referring to the MCPTT Server. Table A.3.4.4-4: SIP INVITE (Step 3, Table A.3.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1 with conditions MCPTT, MANUAL and re_INVITE Information Element Value/remark Comment Reference Condition Resource-Priority IETF RFC 4412 [20] IETF RFC 7134 [16] IETF RFC 8101 [18] EMERGEN CY-CALL or IMMPERIL- CALL r-value EMERGEN CY-CALL namespace value of the <resource- priority-namespace> element contained in the <emergency-resource- priority> element contained in the <OnNetwork> element of the MCX service configuration documents As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 390 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1 with conditions MCPTT, MANUAL and re_INVITE Information Element Value/remark Comment Reference Condition r-priority value of the <resource- priority-priority> element contained in the <emergency-resource- priority> element contained in the <OnNetwork> element of the MCX service configuration document As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo r-value IMMPERIL- CALL namespace value of the <resource- priority-namespace> element contained in the <imminent-peril-resource- priority> element contained in the <OnNetwork> element of the MCX service configuration documents As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo r-priority value of the <resource- priority-priority> element contained in the <imminent- peril-resource-priority> element contained in the <OnNetwork> element of the MCX service configuration document As configured in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1 for MCPTT and in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1 for MCVideo Session-Expires IETF RFC 4028 [22] delta-seconds any allowed value Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.4.4-5 MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table A.3.4.4-6 Table A.3.4.4-5: SDP in SIP INVITE (Table A.3.4.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, with condition INITIAL_SDP_OFFER Information Element Value/remark Comment Reference Condition Media description[2] NOT WITHOUT_ FLOORCO NTROL media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters mc_priority Any value lower or equal to the priority specified in the MCPTT Group configuration The value of the <user- priority> element for the user in the MCPTT Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.1-1) See note 2 ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 GROUP- CALL OR CHAT- GROUP- CALL ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 391 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, with condition INITIAL_SDP_OFFER Information Element Value/remark Comment Reference Condition mc_priority Any value lower or equal to the priority specified in the MCPTT Service configuration The value of the <num- levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4- 1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 pc_MCPTT _FloorRequ estQueuein g NOTE 1: If the SS-UE requests a call without media floor control condition WITHOUT_FLOORCONTROL shall be applied. NOTE 2: The <num-levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration has higher value than any <user-priority> element. (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1). Table A.3.4.4-6: MCPTT-Info in SIP INVITE (Table A.3.4.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params mcptt-request-uri Encrypted (note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_B The URI of the called user mcptt-calling-user-id Encrypted (note) <mcptt- calling-user-id> with mcpttURI set to px_MCPTT_ID_User_A The URI of the calling user NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-1A. Table A.3.4.4-7: SIP 200 (OK) (Step 4, Table A.3.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1 with conditions MCPTT and INVITE- RSP Information Element Value/remark Comment Reference Condition Content-Type IETF RFC 5621 [14] value "application/sdp" Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.4.4-8 Table A.3.4.4-8: SDP in SIP 200 (OK) (Table A.3.4.4-7) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition Session description: Origin o= line username "-" "-" indicating the concept of user IDs not being supported ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 392 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition sess-id "11111111" A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session. sess-version "11111111" Session Name " " s= line single empty space indicating no session name Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [13] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [12] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS-UE Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [8] "RR" 2000 IETF RFC 3556 [8] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time media attribute a= line attribute =maxptime maxptime "240" maximum packet time Media description[2] Media description for media control NOT WITHOUT_ FLOORCO NTROL media description m= line media = application SDP media-level section for a media control entity ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 393 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_ANSWER Information Element Value/remark Comment Reference Condition port port number assigned by the SS-UE being different than the port number of the audio channel (RTP) and its associated control channel (RTCP)" The port for the media control entity Connection Data c= line connection-address IP address of the SS-UE media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters NOT WITHOUT_ FLOORCO NTROL mc_queueing present if included in the offer Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Table A.3.4.4-9: Connect (Step 7, Table A.3.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.12-1 with condition ACK Information Element Value/remark Comment Condition RTCP header SSRC The SSRC of the MCPTT Participating Server MCPTT Session Identity field Session Type "00000000" No session type MCPTT Group Identity field GROUP- CALL OR CHAT- GROUP- CALL MCPTT Group Identity px_MCPTT_Group_A_ID a URI, which identifies the MCPTT group Inviting MCPTT User Identity field not present Table A.3.4.4-10: Connect (Step 9, Table A.3.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.12-1 with condition ACK Information Element Value/remark Comment Condition RTCP header SSRC The SSRC of the MCPTT Participating Server MCPTT Group Identity field GROUP- CALL OR CHAT- GROUP- CALL MCPTT Group Identity px_MCPTT_Group_A_ID a URI, which identifies the MCPTT group ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 394 A.3.5 MCPTT E2E call establishment using a pre-established session, automatic commencement A.3.5.1 Initial conditions As specified in the test case which calls the procedure. A.3.5.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.5.3 Procedure Table A.3.5.3-1: MCPTT E2E call establishment using a pre-established session, automatic commencement St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCPTT Client) sends a SIP REFER message to request the establishment of an MCPTT call using a pre-established session --> SIP REFER - - 2 Check: Does the MCPTT Server respond with a SIP 200 (OK) message to SS-UE1 indicating that the MCPTT call has been properly requested? <-- SIP 200 (OK) - P - EXCEPTION: Depending on the MCPTT Server implementation, the following steps might be performed in parallel. - - - - 3 Check: Does the MCPTT server send a Connect message to SS-UE1 (MCPTT Client)? <-- Connect - P 4 The SS-UE1 (MCPTT Client) sends an Acknowledgement in response to the Connect message. --> Acknowledge - - 5 Check: Does the MCPTT server send a Connect message to SS-UE2 (MCPTT Client)? <-- Connect - P 6 The SS-UE2 (MCPTT Client) sends an Acknowledgement in response to the Connect message. --> Acknowledge - - A.3.5.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.5.4-1: SIP REFER (Step 1, Table A.3.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.12-1 with conditions MCPTT Information Element Value/remark Comment Reference Condition Message-body IETF RFC 3261 [15] MIME body part Resource list IETF RFC 5366 [24] MIME-part-body Resource-lists as described in Table A.3.5.4-2 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 395 Table A.3.5.4-2: Resource-lists in SIP REFER (Table A.3.5.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-1, condition PRE-ESTABLISH with the uri attribute of the entry extended with the SIP URI header fields as specified in Table A.3.5.4-3A Table A.3.5.4-2A: SIP header fields extending the uri attribute of the resource-lists' single entry (Table A.3.5.4-2) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.12-2, condition MCPTT Information Element Value/remark Comment Reference Condition body MIME body part SDP Message MIME-part-headers Content-Type "application/sdp" MIME-part-body SDP Message as described in Table A.3.5.4-2B MIME body part MCPTT-Info MIME-part-body MCPTT-Info as described in Table A.3.5.4-2C Table A.3.5.4-2B: SDP in SIP header fields (Table A.3.5.4-2A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_OFFER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition Session description: Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "11111111" A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session. sess-version "11111111" Session Name " " s= line single empty space indicating no session name Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [13] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [12] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS-UE Bandwidth b= line "AS" 38 ETSI TS 126 114 [11] (3GPP TS 26.114) Table K.6 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 396 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_OFFER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition "RS" 0 IETF RFC 3556 [8] "RR" 2000 IETF RFC 3556 [8] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time media attribute a= line attribute =maxptime maxptime "240" maximum packet time media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for RTP foundation 1234 arbitrarily selected priority 2130706431 IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for RTCP foundation 1234 Same as for RTP priority 2130706430 IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id Media description[2] Media description for media control media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS-UE being different than the port number of the audio channel (RTP) and its associated control channel (RTCP)" The port for the media control entity Connection Data c= line connection-address IP address of the SS-UE media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters NOT WITHOUT_ FLOORCO NTROL ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 397 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_OFFER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 pc_MCPTT _FloorRequ estQueuein g mc_priority The priority value specified in the MCPTT Group configuration The value of the <user- priority> element for the user in the MCPTT Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.1-1) See note 2 ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 GROUP- CALL OR CHAT- GROUP- CALL mc_priority The max priority value specified in the MCPTT Service configuration The value of the <num- levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4- 1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_implicit_request not present present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_ssrc any value if present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_no_floor_ctrl not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 format specific parameters WITHOUT_ FLOORCO NTROL mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_priority not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 mc_granted not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_implicit_request not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_ssrc not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 398 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-1, condition SDP_OFFER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition mc_no_floor_ctrl present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for Media Control messages foundation 4321 arbitrarily selected; different than for RTP/RTCP priority 2130706430 IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id NOTE 1: If the SS-UE requests an implicit floor condition IMPLCIT_GRAN_REQUESTED also applies. NOTE 2: The <num-levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration has higher value than any <user-priority> element. (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4-1). Table A.3.5.4-2C: MCPTT-Info in SIP header fields (Table A.3.5.4-2A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1, condition INVITE-REFER Table A.3.5.4-3: SIP 200 (OK) (Step 2, Table A.3.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 with conditions MCPTT and REFER- RSP Information Element Value/remark Comment Reference Condition Content-Type media-type "application/sdp" Message-body SDP message SDP message as described in Table A.3.5.4-3A Table A.3.5.4-3A: SDP in SIP 200 (OK) (Table A.3.5.4-3) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [13] media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for RTP foundation any value priority any value IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for RTCP foundation any value ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 399 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition priority any value IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id Media description[2] media attribute a= line attribute = fmtp fmtp format "MCPTT" format specific parameters NOT WITHOUT_ FLOORCO NTROL mc_queueing present if included in the offer Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_priority if a value is provided in the offer: the value defined in the MCPTT Group Configuration or the value provided in the offer, whichever is the lower value; otherwise not present The value of the <user- priority> element for the user in the MCPTT Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.1-1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 GROUP- CALL OR CHAT- GROUP- CALL mc_priority if a value is provided in the offer: the value defined in the MCPTT Service Configuration or the value provided in the offer, whichever is the lower value; otherwise not present The value of the <num- levels-priority-hierarchy> element for on-network in the MCPTT Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.4- 1) ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_granted not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_F LOOR_GR ANTED mc_implicit_request not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_ssrc not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 same value as in the offer if provided in the offer and there is no collision with the value used by the SS; otherwise value assigned by the SS ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_no_floor_ctrl not present ETSI TS 124 380 [5] (3GPP ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 400 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-1, condition SDP_ANSWER and PRE_ESTABLISHED_SESSION Information Element Value/remark Comment Reference Condition TS 24.380) cl. 12.1.2.3 format specific parameters WITHOUT_ FLOORCO NTROL mc_queueing not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_priority not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 mc_granted not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_implicit_request not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_ssrc not present ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 mc_no_floor_ctrl present Parameter has no value ETSI TS 124 380 [5] (3GPP TS 24.380) cl. 12.1.2.3 media attribute a=line attribute="candidate" IETF RFC 5245 [7] candidate candidate for Media Control messages foundation any value priority any value IETF RFC 5245 [7] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id NOTE 1: If the SS-UE requests an implicit floor more conditions may apply: i. If the server implicitly grants the floor, conditions IMPLICIT_GRANT_REQUESTED and IMPLICIT_FLOOR_GRANTED are also applied. ii. If the floor needs to be explicitly granted, condition IMPLICIT_GRANT_REQUESTED applies. NOTE 2: If the SS-UE requests a call without media floor condition WITHOUT_FLOORCONTROL shall be applied. NOTE 3: Elements whose values mention the SS shall be understood as if they were referring to the MCPTT Server. Table A.3.5.4-4: Connect (Step 3, Table A.3.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.12-1 with condition ACK Information Element Value/remark Comment Condition RTCP header SSRC The SSRC of the MCPTT Participating Server MCPTT Session Identity field Session Type "00000000" No session type MCPTT Group Identity field GROUP- CALL OR CHAT- GROUP- CALL ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 401 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.12-1 with condition ACK Information Element Value/remark Comment Condition MCPTT Group Identity px_MCPTT_Group_A_ID a URI, which identifies the MCPTT group Inviting MCPTT User Identity field not present Table A.3.5.4-5: Connect (Step 5, Table A.3.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.12-1 with condition ACK Information Element Value/remark Comment Condition RTCP header SSRC The SSRC of the MCPTT Participating Server MCPTT Group Identity field GROUP- CALL OR CHAT- GROUP- CALL MCPTT Group Identity px_MCPTT_Group_A_ID a URI, which identifies the MCPTT group PCK I_MESSAGE field MIKEY-SAKKE I_MESSAGE as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.9.1-2A PRIVATE- CALL A.3.6 MCPTT E2E call release keeping the pre-established session A.3.6.1 Initial conditions As specified in the test case which calls the procedure. A.3.6.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.6.3 Procedure Table A.3.6.3-1: MCPTT E2E call release keeping the pre-established session St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCPTT Client) sends a SIP REFER message with method "BYE" to release the MCPTT session and keep the pre- established session. --> SIP REFER - - 2 Check: Does the MCPTT Server respond with a SIP 200 (OK) to SS-UE1? <-- SIP 200 (OK) - P 3 Check: Does the MCPTT Server release the call by sending a Disconnect message to SS- UE2 (MCPTT Client)? <-- Disconnect - P 4 The SS-UE2 (MCPTT Client) sends an Acknowledgement to accept the release of the call --> Acknowledge - - ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 402 A.3.6.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.6.4-1: SIP REFER (Step 1, Table A.3.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.12-1 with conditions MCPTT and METHOD- BYE Table A.3.6.4-2: SIP 200 (OK) (Step 2, Table A.3.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 with conditions MCPTT and REFER- RSP Table A.3.6.4-3: Disconnect (Steps 3, Table A.3.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.13-1 with condition ACK A.3.7 MCPTT Group Affiliation Status Determination and Subscription A.3.7.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.7.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.7.3 Procedure Table A.3.7.3-1: MCPTT Group affiliation status determination and subscription Same procedure as defined in: Table A.2.7.3-1 A.3.7.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.7.4-1: SIP SUBSCRIBE (Step 1, Table A.3.7.3-1) Derivation Path: Table A.2.7.4-1, conditions MCPTT and PRESENCE-EVENT ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 403 Table A.3.7.4-2: SIP NOTIFY (Step 3, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, conditions MCPTT and PRESENCE- EVENT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9.2.2.2.5 MIME-part-body PIDF as described in Table A.3.7.4-3 Table A.3.7.4-3: PIDF in SIP NOTIFY (Table A.3.7.4-2) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-1 (note) NOTE: PIDF document contains tuple with empty <status> element. A.3.8 MCPTT Group Affiliation Status Change A.3.8.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.8.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.8.3 Procedure Table A.3.8.3-1: MCPTT Group Affiliation Status Change Same procedure as defined in Table A.2.12.3-1 A.3.8.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.8.4-1: SIP PUBLISH (Step 1, Table A.3.8.3-1) Derivation Path: Table A.2.12.4-1, condition MCPTT Table A.3.8.4-2: PIDF in SIP PUBLISH (Table A.3.8.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.1-1, condition AFFILIATION ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 404 Table A.3.8.4-3: SIP 200 (OK) (Step 2, Table A.3.8.3-1) Derivation Path: Table A.2.12.4-5 Information Element Value/remark Comment Reference Condition Expires IETF RFC 3261 [15] IETF RFC 3903 [19] value same value as in the request or lower Table A.3.8.4-4: SIP NOTIFY (Step 3, Table A.3.8.3-1) Derivation Path: Table A.2.12.4-3, condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9.2.2.2.5 MIME-part-body PIDF as described in Table A.3.8.4-5 Table A.3.8.4-5: PIDF in SIP NOTIFY (Table A.3.8.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-1, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status "affiliating" expires Current time plus the value set in the Expires header of the SIP PUBLISH response. ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9.2.2.3.5 ..p-id same value as received in the SIP PUBLISH message. Table A.3.8.4-6: SIP NOTIFY (Step 5, Table A.3.8.3-1) Derivation Path: Table A.2.12.4-3, condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9.2.2.2.5 MIME-part-body PIDF as described in Table A.3.8.4-7 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 405 Table A.3.8.4-7: PIDF in SIP NOTIFY (Table A.3.8.4-5) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-1, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status "affiliated" expires Current time plus the value set in the Expires header of the SIP PUBLISH response. ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9.2.2.3.5 ..p-id same value as received in the SIP PUBLISH message. A.3.9 MCPTT Functional Alias Status Determination and Subscription A.3.9.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.9.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.9.3 Procedure Table A.3.9.3-1: MCPTT Functional Alias Status Determination and Subscription Same procedure as defined in Table A.2.7.3-1 A.3.9.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.9.4-1: SIP SUBSCRIBE (Step 1, Table A.3.9.3-1) Derivation Path: Table A.2.7.4-1, conditions MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part MCPTT Info ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9A.2.1.3 MIME-part-body MCPTT-Info as described in Table A.2.7.4-2 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 406 Table A.3.9.4-2: MCPTT-Info in SIP SUBSCRIBE (Table A.3.9.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-1 Information Element Value/remark Comment Reference Condition mcpttinfo mcptt-Params anyExt request-type functional-alias-status- determination ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9A.2.1.3 Table A.3.9.4-3: SIP NOTIFY (Step 3, Table A.3.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1 with conditions MCPTT and PRESENCE- EVENT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9A.2.2.2.5 MIME-part-body PIDF as described in Table A.3.9.4-4 Table A.3.9.4-4: PIDF in SIP NOTIFY (Table A.3.9.4-2) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-1 (note) NOTE: PIDF document contains tuple with empty <status> element. A.3.10 MCPTT Functional Alias Status Change A.3.10.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.10.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.10.3 Procedure Table A.3.10.3-1: MCPTT Functional Alias Status Change Same procedure as defined in Table A.2.12.3-1 A.3.10.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.10.4-1: SIP PUBLISH (Step 1, Table A.3.10.3-1) Derivation Path: Table A.2.12.4-1, condition MCPTT ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 407 Table A.3.10.4-2: PIDF in SIP PUBLISH (Table A.3.10.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.1-1, condition FUNCTIONAL_ALIAS_STATUS_CHANGE Table A.3.10.4-3: SIP 200 (OK) (Step 2, Table A.3.10.3-1) Derivation Path: Table A.2.12.4-5 Information Element Value/remark Comment Reference Condition Expires IETF RFC 3261 [15] IETF RFC 3903 [19] value same value as in the request or lower Table A.3.10.4-4: SIP NOTIFY (Step 3, Table A.3.10.3-1) Derivation Path: Table A.2.12.4-3, condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9A.2.2.2.5 MIME-part-body PIDF as described in Table A.3.10.4-5 Table A.3.10.4-5: PIDF in SIP NOTIFY (Table A.3.10.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-1, conditions FUNCTIONAL_ALIAS_ACTIVATED and NOTIFY_FOR_PUBLISH Information Element Value/remark Comment Reference Condition presence tuple status functionalAlias status "activating" expires Current time plus the value set in the Expires header of the SIP PUBLISH response. ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9A.2.2.3.5 Table A.3.10.4-6: SIP NOTIFY (Step 5, Table A.3.10.3-1) Derivation Path: Table A.2.12.4-3, condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9A.2.2.2.5 MIME-part-body PIDF as described in Table A.3.10.4-7 ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 408 Table A.3.10.4-7: PIDF in SIP NOTIFY (Table A.3.10.4-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-1, conditions FUNCTIONAL_ALIAS_ACTIVATED and NOTIFY_FOR_PUBLISH Information Element Value/remark Comment Reference Condition presence tuple status functionalAlias status "activated" expires Current time plus the value set in the Expires header of the SIP PUBLISH response. ETSI TS 124 379 [4] (3GPP TS 24.379) clause 9A.2.2.3.5 A.3.11 MCPTT Floor Request - Floor Granted A.3.11.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.11.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.11.3 Procedure Table A.3.11.3-1: MCPTT Floor Request - Floor Granted St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCPTT Client) sends a Floor Request message. (Note) --> Floor Request - - - EXCEPTION: Steps 2a1-2b1 describe behaviour that depends on the MCPTT Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCPTT Server requests acknowledgement of sent floor control messages. - - - - 2a1 Check: Does the MCPTT Server send a Floor Granted message with acknowledgement required? <-- Floor Granted - P 2a2 The SS-UE (MCPTT Client) sends a Floor Ack message in response to the Floor Granted message. (Note) --> Floor Ack - - 2b1 Check: Does the MCPTT Server send a Floor Granted message with no acknowledgement required? <-- Floor Granted - P NOTE: The SS-UE being used is specified in the test case calling the procedure. If not stated, SS-UE1 (MCPTT Client) will be assumed. A.3.11.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 409 • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.11.4-1: Floor Granted (Step 2a1, Table A.3.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.3-1 condition ACK A.3.12 MCPTT Floor Request - Floor Queue Position Info A.3.12.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.12.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.12.3 Procedure Table A.3.12.3-1: MCPTT Floor Request - Floor Queue Position Info St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCPTT Client) sends a Floor Request message. (Note) --> Floor Request - - - EXCEPTION: Steps 2a1-2b1 describe behaviour that depends on the MCPTT Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCPTT Server requests acknowledgement of sent floor control messages. - - - - 2a1 Check: Does the MCPTT Server send a Floor Queue Position Info message indicating that the Floor Request message was queued, with acknowledgement required? <-- Floor Queue Position Info - P 2a2 The SS-UE (MCPTT Client) sends a Floor Ack message in response to the Floor Queue Position Info message. Note) --> Floor Ack - - 2b1 Check: Does the MCPTT Server send a Floor Queue Position Info message indicating that the Floor Request message was queued, with no acknowledgement required? <-- Floor Queue Position Info - P NOTE: The SS-UE being used is specified in the test case calling the procedure. If not stated, SS-UE1 (MCPTT Client) will be assumed. A.3.12.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.12.4-1: Floor Queue Position Info (Step 2a1, Table A.3.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.10-1 condition ACK ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 410 A.3.13 MCPTT Queuing Position Request A.3.13.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.13.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.13.3 Procedure Table A.3.13.3-1: MCPTT Queuing Position Request St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCPTT Client) sends a Floor Queue Position Request message. (Note) --> Floor Queue Position Request - - - EXCEPTION: Steps 2a1-2b1 describe behaviour that depends on the MCPTT Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCPTT Server requests acknowledgement of sent floor control messages. - - - - 2a1 Check: Does the MCPTT Server send a Floor Queue Position Info message indicating that the Floor Request message was queued, with acknowledgement required? <-- Floor Queue Position Info - P 2a2 The SS-UE (MCPTT Client) sends a Floor Ack message in response to the Floor Queue Position Info message. (Note) --> Floor Ack - - 2b1 Check: Does the MCPTT Server send a Floor Queue Position Info message indicating that the Floor Request message was queued, with no acknowledgement required? <-- Floor Queue Position Info - P NOTE: The SS-UE being used is specified in the test case calling the procedure. If not stated, SS-UE1 (MCPTT Client) will be assumed. A.3.13.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.13.4-1: Floor Queue Position Info (Step 2a1, Table A.3.13.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.10-1 condition ACK A.3.14 MCPTT Floor Request - Floor Deny A.3.14.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 411 A.3.14.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.14.3 Procedure Table A.3.14.3-1: MCPTT Floor Request - Floor Deny St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCPTT Client) sends a Floor Request message. (Note) --> Floor Request - - - EXCEPTION: Steps 2a1-2b1 describe behaviour that depends on the MCPTT Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCPTT Server requests acknowledgement of sent floor control messages. - - - - 2a1 Check: Does the MCPTT Server send a Floor Deny message indicating that the Floor Request message has been rejected, with acknowledgement required? <-- Floor Deny - P 2a2 The SS-UE (MCPTT Client) sends a Floor Ack message in response to the Floor Deny message. (Note) --> Floor Ack - - 2b1 Check: Does the MCPTT Server send a Floor Deny message indicating that the Floor Request message has been rejected, with no acknowledgement required? <-- Floor Deny - P NOTE: The SS-UE being used is specified in the test case calling the procedure. If not stated, SS-UE1 (MCPTT Client) will be assumed. A.3.14.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.14.4-1: Floor Deny (Step 2a1, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.4-1 condition ACK A.3.15 MCPTT Floor Release - Floor Idle A.3.15.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.15.2 Definition of system information messages N/a (out of E-UTRA coverage). ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 412 A.3.15.3 Procedure Table A.3.15.3-1: MCPTT Floor Release - Floor Idle St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCPTT Client) sends a Floor Release message with acknowledgment required. (Note) --> Floor Release - - 2 Check: Does the MCPTT Server send a Floor Ack message in response to the Floor Release message? <-- Floor Ack - P - EXCEPTION: Steps 3a1-3b1 describe behaviour that depends on the MCPTT Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCPTT Server requests acknowledgement of sent floor control messages. - - - - 3a1 Check: Does the MCPTT Server send a Floor Idle message with acknowledgement required? <-- Floor Idle - P 3a2 The SS-UE (MCPTT Client) sends a Floor Ack message in response to the Floor Idle message. (Note) --> Floor Ack - - 3b1 Check: Does the MCPTT Server send a Floor Idle message with no acknowledgement required? <-- Floor Idle - P NOTE: The SS-UE being used is specified in the test case calling the procedure. If not stated, SS-UE1 (MCPTT Client) will be assumed. A.3.15.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.15.4-1: Floor Release (Step 1, Table A.3.15.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.5-1 Information Element Value/remark Comment Reference Condition RTCP header Subtype 10100 Table A.3.15.4-2: Floor Idle (Step 3a1, Table A.3.15.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.6-1 condition ACK A.3.16 MCPTT Floor Release - Floor Taken A.3.16.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 413 A.3.16.2 Definition of system information messages N/a (out of E-UTRA coverage). A.3.16.3 Procedure Table A.3.16.3-1: MCPTT Floor Release - Floor Taken St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCPTT Client) sends a Floor Release message with acknowledgment required. (Note) --> Floor Release - - 2 Check: Does the MCPTT Server send a Floor Ack message in response to the Floor Release message? <-- Floor Ack - P - EXCEPTION: Steps 3a1-3b1 describe behaviour that depends on the MCPTT Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCPTT Server requests acknowledgement of sent floor control messages. - - - - 3a1 Check: Does the MCPTT Server send a Floor Taken message with acknowledgement required? <-- Floor Taken - P 3a2 The SS-UE (MCPTT Client) sends a Floor Ack message in response to the Floor Taken message. (Note) --> Floor Ack - - 3b1 Check: Does the MCPTT Server send a Floor Taken message with no acknowledgement required? <-- Floor Taken - P NOTE: The SS-UE being used is specified in the test case calling the procedure. If not stated, SS-UE1 (MCPTT Client) will be assumed. A.3.16.4 Specific message contents All message contents are as specified in clause 5.5 and in the test case calling the procedure, with the following clarifications: • Subclauses referring to messages from SS relate to the IUT (MCX Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCX Client) or SS-UE2 (MCX Client). Table A.3.16.4-1: Floor Release (Step 1, Table A.3.16.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.5-1 Information Element Value/remark Comment Reference Condition RTCP header Subtype 10100 Table A.3.16.4-2: Floor Taken (Step 3a1, Table A.3.16.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.6.7-1 condition ACK ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 414 A.4 MCPTT Conformance testing test point models Based on the test points models shown in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), clause 4.1, the following section extends the test environment implementation examples provided in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), clause 4.2 for Server-Client and Server-Server conformance testing. Figure A.4.1 shows test configuration where the IUT and the system simulator, simulating MCPTT Clients, communicate, one with the other, over the LTE radio interface (test points (1)). Figures A.4.2, A.4.3, A.4.4, A.4.5 and A.4.6 show test configuration where the IUT and the System Simulator communicate, one with the other, over the MCPTT-3 or IWF-1 interfaces, as defined by ETSI TS 123 179 [3] (3GPP TS 23.179), clause 7.5.2.4, and ETSI TS 123 283 [25] (3GPP TS 23.283), clause 7.4.1, respectively (test points (4)). Figures A.4.7 shows test configuration where the IUT and the System Simulator communicate, one with the other, over the CSC-16 or IWF-3 interface, as defined by ETSI TS 123 280 [26] (3GPP TS 23.280), clause 7.5.2.16, and ETSI TS 123 283 [25] (3GPP TS 23.283), clause 7.4.3, respectively (test points (4)). MCPTT Client 1 simulation Originating/ Terminating Participating MCPTT Function Test Point (1) Server under test System Simulator MCPTT Client 2 simulation Figure A.4.1: Testing the MCPTT Server (server-to-client) Originating/ Terminating Participating MCPTT function Controlling MCPTT function Partner MCPTT System Test Point (4) MCPTT Server under test Primary MCPTT System System Simulator Figure A.4.2: Testing the MCPTT Server (server-to-server), Controlling function ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 415 Controlling MCPTT function Originating Participating MCPTT function Partner MCPTT System Test Point (4) MCPTT Server under test Primary MCPTT System System Simulator Figure A.4.3: Testing the MCPTT Server (server-to-server), Originating function Controlling MCPTT function Terminating Participating MCPTT function Partner MCPTT System Test Point (4) MCPTT Server under test Primary MCPTT System System Simulator Figure A.4.4: Testing the MCPTT Server (server-to-server), Terminating function Controlling MCPTT function Non-Controlling MCPTT function Partner MCPTT System Test Point (4) MCPTT Server under test Primary MCPTT System System Simulator Figure A.4.5: Testing the MCPTT Server (server-to-server), Non-controlling function ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 416 Non-Controlling MCPTT function Controlling MCPTT function Partner MCPTT System Test Point (4) MCPTT Server under test Primary MCPTT System System Simulator Figure A.4.6: Testing the MCPTT Server (server-to-server), Controlling function; trusted and untrusted modes Group Management function Group Management function Partner MCPTT System Test Point (4) MCPTT Server under test Primary MCPTT System System Simulator Figure A.4.7: Testing the MCPTT Server (server-to-server), Group Management function ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 417 Annex B (informative): Bibliography • 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1". • 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2". • 3GPP TS 24.109: "Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details". • 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". • 3GPP TS 24.382: "Mission Critical Push To Talk (MCPTT) identity management; Protocol specification". • 3GPP TS 29.283: "Diameter data management applications". • IETF RFC 2392: "Content-ID and Message-ID Uniform Resource Locators". • IETF RFC 2616: "Hypertext Transfer Protocol -- HTTP/1.1". • IETF RFC 3515: "The Session Initiation Protocol (SIP) Refer Method". • IETF RFC 3711: "The Secure Real-time Transport Protocol (SRTP)". • IETF RFC 3840: "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)". • IETF RFC 3841: "Caller Preferences for the Session Initiation Protocol (SIP)". • IETF RFC 4488: "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription". • IETF RFC 4538: "Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)". • IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)". • IETF RFC 4964: "The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular". • IETF RFC 5373: "Requesting Answering Modes for the Session Initiation Protocol (SIP)". • IETF RFC 5875: "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package". • IETF RFC 6050: "A Session Initiation Protocol (SIP) Extension for the Identification of Services". • IETF RFC 6749: "The OAuth 2.0 Authorization Framework". • IETF RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage". • IETF RFC 6809: "Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)". • IETF RFC 7647: "Clarifications for the Use of REFER with RFC 6665". • IETF RFC 8445: "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal". ETSI ETSI TS 104 147-1 V1.1.1 (2026-01) 418 History Version Date Status V1.1.1 January 2026 Publication |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 1 Scope | The present document specifies the protocol conformance testing for testing a MCData Server for compliance to the Mission Critical Data (MCData) over LTE protocol requirements defined by 3GPP. The present document addresses only MCData Server-Client communication scenarios. It does not cover e.g. MCData Server-EPS, MCData 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 MCData 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 [3] (3GPP TS 36.579-4) and Implementation extra Information for Testing (IXIT) ETSI TS 136 579-5 [i.2] (3GPP TS 36.579-5); • the applicability of each test case ETSI TS 136 579-4 [3] (3GPP TS 36.579-4). The present document does not specify the protocol conformance testing for the EPS (LTE) bearers which carry the MCData data sent or received by the MCData Server. The specification of such testing is out of the scope of RAN5. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 2 References | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-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-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)". [3] 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)". ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 13 [4] 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)". [5] ETSI TS 124 379: "LTE; Mission Critical Push To Talk (MCPTT) call control; Protocol specification (3GPP TS 24.379)". [6] ETSI TS 124 481: "LTE; Mission Critical Services (MCS) group management; Protocol specification (3GPP TS 24.481)". [7] ETSI TS 124 482: "LTE; Mission Critical Services (MCS) identity management; Protocol specification (3GPP TS 24.482)". [8] ETSI TS 124 484: "LTE; Mission Critical Services (MCS) configuration management; Protocol specification (3GPP TS 24.484)". [9] 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)". [10] 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)". [11] ETSI TS 133 310: "Universal Mobile Telecommunications System (UMTS); LTE; 5G; Network Domain Security (NDS); Authentication Framework (AF) (3GPP TS 33.310)". [12] ETSI TS 133 180: "LTE; Security of the Mission Critical (MC) service (3GPP TS 33.180)". [13] ETSI TS 124 282: "LTE; Mission Critical Data (MCData) signalling control; Protocol specification (3GPP TS 24.282)". [14] IETF RFC 3326 (December 2002): "The Reason Header Field for the Session Initiation Protocol (SIP)". [15] IETF RFC 4145 (September 2005): "TCP-Based Media Transport in the Session Description Protocol (SDP)". [16] IETF RFC 3903 (October 2004): "Session Initiation Protocol (SIP) Extension for Event State Publication". [17] IETF RFC 5366 (October 2008): "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)". [18] IETF RFC 2046 (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". [19] IETF RFC 5621 (September 2009): "Message Body Handling in the Session Initiation Protocol (SIP)". [20] IETF RFC 7134 (March 2014): "The Management Policy of the Resource Priority Header (RPH) Registry Changed to "IETF Review"". [21] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol". [22] IETF RFC 5031 (January 2008): "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services". [23] IETF RFC 4028 (April 2005): "Session Timers in the Session Initiation Protocol (SIP)". [24] IETF RFC 4975 (September 2007): "The Message Session Relay Protocol (MSRP)". [25] IETF RFC 5547 (May 2009): "A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer". [26] IETF RFC 5322 (October 2008): "Internet Message Format". [27] IETF RFC 2854 (June 2020): "The 'text/html' Media Type". ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 14 [28] W3C® Recommendation 24 December 1999: "HTML 4.01 Specification". [29] IETF RFC 5245 (April 2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols". [30] IETF RFC 6665 (July 2012): "SIP-Specific Event Notification". [31] 3GPP TS 36.579-8: "Mission Critical (MC) services over LTE; Part 8: Mission Critical Video (MCVideo) Server Application conformance specification". [32] ETSI TS 124 281: "LTE; Mission Critical Video (MCVideo) signalling control; Protocol specification (3GPP TS 24.281)". [33] 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)". [34] IETF RFC 4867 (April 2007): "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs". [35] IETF RFC 6335 (August 2011): "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry". [36] IETF RFC 3556 (July 2003): "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". [37] ETSI TS 124 380: "LTE; Mission Critical Push To Talk (MCPTT) media plane control; Protocol specification (3GPP TS 24.380)". [38] IETF RFC 4412 (February 2006): "Communications Resource Priority for the Session Initiation Protocol (SIP)". [39] IETF RFC 8101 (March 2017): "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk service". [40] ETSI TS 124 582: "LTE; Mission Critical Data (MCData) media plane control; Protocol specification (3GPP TS 24.582)". |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-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-5: "LTE; Mission Critical (MC) services over LTE; Part 5: Abstract test suite (ATS) (3GPP TS 36.579-5)". [i.3] ETSI TS 124 483: "LTE; Mission Critical Services (MCS) Management Object (MO) (3GPP TS 24.483)". [i.4] 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)". ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 15 [i.5] 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.6] ETSI TS 122 282: "LTE; 5G; Mission Critical (MC) data (3GPP TS 22.282)". [i.7] ETSI TS 123 282: "LTE; Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2 (3GPP TS 23.282)". [i.8] 3GPP TS 36.579-9: "Mission Critical (MC) services over LTE; Part 9: Mission Critical Data (MCData) Server Application conformance specification". |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 3 Definitions of terms, symbols and abbreviations | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 3.1 Terms | For the purposes of the present document, the terms 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 given in ETSI TS 123 282 [i.7] (3GPP TS 23.282) apply: • Auto-receive • Conversation identifier • Data stream • FD disposition • MCData client • MCData group • MCData group affiliation • MCData group communication • MCData group de-affiliation • MCData ID • MCData server • MCData service • MCData UE • MCData user • Reception control • Reply identifier • SDS data • SDS disposition • Standalone communication • Transaction identifier ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 16 • Transmission control For the purpose of the present document, the following terms given in ETSI TS 122 282 [i.6] (3GPP TS 22.282) apply: • Conversation • Conversation ID • MCData Conversation Hang Time • MCData System For the purpose of the present document, the following terms given in ETSI TS 133 180 [12] (3GPP TS 33.180) apply: • Client Server Key (CSK) • Private Call Key (PCK) • Signalling Protection Key (SPK) • XML Protection Key (XPK) |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 3.2 Symbols | Void. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-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). CSK Client-Server Key FD File Distribution GKTP Group Key Transport Payload ICE Interactive Connectivity Establishment ICS Implementation Conformance Statement IUT Implementation Under Test IXIT Implementation eXtra Information for Testing MC Mission Critical MCData group ID MCData group Identity MCData Mission Critical Data MCPTT Mission Critical Push To Talk MCS Mission Critical Service MCVideo Mission Critical Video MIME Multipurpose Internet Mail Extensions MSRP Message Sending Relay Protocol OIDC OpenID Connect PIDF Presence Information Data Format PLMN Public Land Mobile Network RTCP Real Time Control Protocol RTP Real-time Transport Protocol SDP Session Description Protocol SDS Short Data Service SIP Session Initiation Protocol SPK Signalling Protection Key SS System Simulator SSRC Synchronization SouRCe TP Test Purpose TP Transmission Point ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 17 UE User Equipment URI Uniform Resource Identifier XCAP eXtensible Markup Language (XML) Access Configuration Protocol XDMC XML Document Management Client XPK XML Protection Key |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4 General | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.1 Test methodology | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-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 MCData Server. A declaration by the MCData Server supplier (to use the Implementation Conformance Statement (ICS) proforma specified in ETSI TS 136 579-4 [3] (3GPP TS 36.579-4)) is used to determine whether an optional function/procedure has been implemented. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.1.2 Test interfaces and facilities | Detailed descriptions of the MCData test interfaces and special facilities for testing are provided in ETSI TS 136 509 [9] (3GPP TS 36.509). |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.2 Implicit testing | For some 3GPP MCData 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. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-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 document. 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 [3] (3GPP TS 36.579-4), Table 4-1: 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 18 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.5 Reference conditions | The reference environments used by all signalling and protocol tests is 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. For all test cases in the present document unless specified otherwise the condition MCDATA applies for all message contents. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 4.6 Generic setup procedures | A set of basic generic procedures for MCData Client-Server 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. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5 MCData Server - MCData Client Configuration | 5.1 MCDATA Server - MCDATA Client / Configuration / Authentication / User Authorisation / UE Configuration / User Profile / Key generation |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.1.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData client) activates an MCData application and requests MCData initialisation } then { IUT (MCData Server) provides the initial UE configuration and performs MCData User Authentication and provides id_token, access_token and refresh token to the successfully authenticated user} } (2) with { IUT (MCData Server) having authenticated the SS-UE1 (MCData client) } ensure that { when { the SS-UE1 (MCData Client) initiates key management authorization } then { IUT (MCData Server) provides identity management key material } } (3) with { IUT (MCData Server) having provided identity management key material } ensure that { when { the SS-UE1 (MCData client) requests user service authorization } then { IUT (MCData Server) responds to the SS-UE1 (MCData Client) with SIP 200 (OK) messages } } (4) with { IUT (MCData Server) having provided service authorization } ensure that { when { the SS-UE1 (MCData client) requests configuration management authorization} then { IUT (MCData 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 MCData UE Configuration Document and MCData User Profile Configuration Document MCData Service Configuration Document via HTTP 200 (OK) messages in response to HTTP GET requests } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 19 (5) with { IUT (MCData Server) having provided user configuration data } ensure that { when { the SS-UE1 (MCData client) requests group management authorization } then { IUT (MCData Server) responds to the SS-UE1 (MCData 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 MCData 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 } } (6) with { IUT (MCData Server) having provided all required configuration data } ensure that { when { the SS-UE1 (MCData client) requests to refresh its service settings } then { IUT (MCData Server) responds to the SS-UE1 (MCData Client) with a SIP 200 (OK) message } } |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.1.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 482 [7] (3GPP TS 24.482) clauses 6.3.1, A.2.1.3, A.2.3, ETSI TS 124 484 [8] (3GPP TS 24.484) clauses 4.3.1, 4.3.4, 4.4, 6.3.13.2.3, 6.3.3.2.3, 6.3.3.2.1, 4.1.4, 10.2.1, 10.2.1A, 10.3.1, 10.3.1A, 10.4.1, 6.2.3, ETSI TS 124 481 [6] (3GPP TS 24.481) clauses 5.5, 5.2A, 6.2.4, 6.2.2, 6.3.3.2.3, 6.3.3.2.1, 6.3.13.2.2, 7.2.12.1, ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 4.1, 7.1, 7.3.1, 7.3.1A, 7.3.2, 7.3.3, 7.3.5, 7.3.6.1, 7.3.6.2, 7.3.7, ETSI TS 133 180 [12] (3GPP TS 33.180) clauses 5.1.3.1, 5.1.3.2.1, 5.1.3.2.2, 5.1.3.2.3, 5.2.1, 5.2.2, 5.8.1, 5.8.2. Unless otherwise stated these are Rel-14 requirements. [ETSI TS 124 482 [7] (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 MC service user for their username and password credentials; and NOTE 1: The username will be the MC service 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 MC service user's username and password, the IdM server authenticates the MC service user and: NOTE 2: Other methods of authentication can be used by the MC service provider and are not defined by the OIDC specifications. 3GPP TS 33.180 [17] has defined username and password as a mandatory authentication method to be supported for MC services, 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.180 [17] 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 20 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 MC service ID of the MC service user; c) shall include an id_token, access_token and refresh_token and MC service ID as specified in 3GPP TS 33.180 [17]; and 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 [7] (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 MC service group ID, or an MC service ID." [ETSI TS 124 482 [7] (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 MC service 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 [8] (3GPP TS 24.484), clause 4.3.1] "The MCS server obtains the appropriate MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server. The MCS server obtains the MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 21 The MCS server subscribes to the MCS service configuration document for each mission critical organisation that is provisioned that is supported by the MCS server using the procedure specified in subclause 6.3.13.2.3. How the MCS server is provisioned with the identities of the mission critical organisations is out of scope of the present document. If the MCS service configuration document has been updated since the current version stored at the MCS server, then the MCS server will receive a SIP NOTIFY request containing an HTTPS URI of the MCS service configuration document. Retrieval by the MCS server, using the notified HTTPS URI, of the MCS service configuration document is performed as specified in subclause 6.3.3.2.3. NOTE: The MCS server can be notified of changes to the MCS service management configuration document at any time while operating the MCS." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 4.3.4] "The format of the MCData service configuration document downloaded to the MCData server is defined in subclause 10.4." [ETSI TS 124 484 [8] (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 MCS UE initial configuration document received from an MCS administrator into an appropriate format for configuration of the MCS UE initial configuration MO. If the MCS UE initial configuration MO contains a <default-user-profile> element that identifies an MCS user profile configuration document, the configuration management server needs to convert the identified MCS user profile configuration document received from an MCS administrator into an appropriate format for configuration of the MCS user profile configuration MO. Once an MCS User Profile configuration document has been created or updated by the MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to store MCS user profile configuration document as the user profile in the MC service user database. In order to download the MCS user profile configuration document to an MCS UE or to support an MCS UE updating the MCS user profile configuration document, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to obtain the MCS user profile from the MC service user database. In order to be notified of changes to an MCS user profile configuration document(s) that have been subscribed to by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to be notified of changes to the MCS user profile stored in the MC service user database. In order to delete the MCS user profile when requested by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to delete the MCS user profile from the MC service 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 [8] (3GPP TS 24.484), clause 6.3.13.2.3] "In order to subscribe to an MCS service configuration document, an MCS server shall send an initial SIP SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [22] and IETF RFC 5875 [11]. In the initial SIP SUBSCRIBE request, MCS server: a) shall set the Request URI to a SIP URI containing: 1) the base URI being equal to the public service identity of the CMS configured in the MCS server; and 2) the "auid" parameter set to the application usage identifying th MCS service configuration document; b) shall include a P-Asserted-Identity header field containing the public service identity of the MCS server; c) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [22]), in a P-Asserted-Service header field according to IETF RFC 6050 [23]; and d) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 22 Upon receiving a SIP NOTIFY request associated with a subscription created as result of the sent initial SIP SUBSCRIBE request, the MCS server shall handle the SIP NOTIFY request according to IETF RFC 5875 [11]. In order to re-subscribe to notification of changes to an MCS service configuration document, an MCS server shall send a SIP re-SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [22] and IETF RFC 5875 [11]. In the SIP re-SUBSCRIBE request, MCS server: a) shall set the Request URI to a SIP URI containing: 1) the base URI being equal to the public service identity of the CMS configured in the MCS server; and 2) the "auid" parameter set to the application usage identifying an MCS service configuration document; and b) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.3.2.3] "In order to retrieve a configuration management document via the CSC-5 reference point, an MCS Server shall perform the procedures in subclause 6.3.3.2.1 specified for GC. The MCS server shall set the Request-URI of the HTTP GET request to identify the XML document based on configuration and include the "auid" as per the appropriate application usage." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.3.2.1] "In order to retrieve a configuration management document, a GC shall send an HTTP GET request with the Request URI that references the document to be updated to the network according to procedures specified in IETF RFC 4825 [14] "Retrieve a Document"." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 4.1.4] "An MCData service administrator can, using an MCData UE configure the: - MCData UE configuration document; - MCData user profile configuration document; - MCData service configuration document; and - MCData related group configuration data in the MCS group document. The format of the MCData UE configuration document is defined in subclause 10.2. The format of the MCData user profile configuration document is defined in subclause 10.3. The format of the MCData service configuration document is defined in subclause 10.4." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.2.1] "The MCData UE configuration document is specified in this subclause. The MCData UE configuration document content is based on requirements of Annex A.2 of 3GPP TS 23.282 [24], in accordance with OMA OMA-TS- XDM_Core-V2_1-20120403-A [2]. The usage of an MCData UE configuration document in the MCData service is described in 3GPP TS 24.282 [25] and 3GPP TS 24.582 [26]. The schema definition is provided in subclause 10.2.2.3. An MCData UE configuration document may apply to all MCData UEs of a mission critical organization or apply to specific MCData UEs identified in the <mcdata-UE-id> element. If there is no <mcdata-UE-id> element in the MCData UE configuration document, then by default the MCData UE configuration document applies to all MCData UEs of the mission critical organization that are not specifically identified in the <mcdata-UE-id> element of another MCData UE configuration document of the mission critical organization. Each MCData UE of a mission critical organization is configured with an MCData UE configuration document that is identified by the instance ID of the MCData UE. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 23 MCData UE configuration documents of a MCData user are contained as "XDM collections" in the user's directory of the users tree, in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCData ID, as the user has been already authenticated. A MCData UE configuration document corresponding to a specific MCData UE the MCData user has used to authenticate and is authorised to use the MCData service with is placed in the user directory of the MCData user. The MCData UE configuration document acts as a template for the CMS to generate UE configuration documents that are downloaded to specific MCData UEs. The MCData UE configuration document that acts as a template is referred to as a "master MCData UE configuration document". The master MCData UE configuration document is stored in the users tree of that MCData system administrator. The master MCData UE configuration document does not directly apply to a specific MCData UE, but instead acts as template that the CMS uses to populate the MCData UE configuration documents of MCData UEs identified by elements of the <MCData-UE-id> element. For MCData UE configuration documents that correspond to a specific MCData UE, the name of the MCData UE configuration document is created from a value defined by the corresponding element that identifies the MCData UE within the <MCData-UE-id> element. For a master MCData UE configuration documents that does not contain a <MCData-UE- id> element, the name of the MCData UE configuration document stored in the user directory is "DEFAULT-MCData- UE.xml"." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.2.1A] "The MCData UE configuration document is accessed using the same XCAP URI, regardless of whether the MCData UE has a specific MCData UE configuration document configured or the master MCData UE configuration document applies. The CMS shall generate the UE's MCData UE configuration document from the master MCData UE configuration document if the MCData administrator did not provision a specific MCData UE configuration document. In this generated document, the <MCData-UE-id> element shall be set to the MCData client's UE ID. The UE's MCData UE configuration document shall always be stored with the filename corresponding to the UE's MCData UE ID under the user's directory of the users tree. The XCAP URI used by the MCData client to access the UE's MCData UE configuration document shall be: - CMSXCAPROOTURI/org.3gpp.mcdata.ue-config/users/sip:MCDATAID/MCSUEID." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.3.1] "The MCData user profile configuration document is specified in this subclause. The MCData user profile configuration document content is based on requirements of Annex A.3 of 3GPP TS 23.282 [24], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCData user profile in the MCData service is described in 3GPP TS 24.282 [25]. The schema definition is provided in subclause 10.3.2. MCData user profile documents are "XDM collections" in the user's directory of the users tree, in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCData ID, as the user has been already authenticated. The name of the MCData user profile document matches the value of the <ProfileName> element in the MCData user profile document." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.3.1A] "The XCAP URI used by the MCData client to access the MCData user's MCData user profile documents shall be: CMSXCAPROOTURI/org.3gpp.mcdata.user-profile/users/sip:MCDATAID/mcdata-user-profile-INDEX.xml Where INDEX is the index of the MCData user profile as defined in subclause 10.3.2.8." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.4.1] "The MCData service configuration document is specified in this subclause. The MCData service configuration document content is based on requirements of Annex A.5 of 3GPP TS 23.282 [24], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCData service configuration in the MCData service is described in 3GPP TS 24.282[25] and 3GPP TS 24.582 [26]. The schema definition is provided in subclause 10.4.2.3. Each mission critical organization is configured with an MCData service configuration document." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 24 [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.2.3] "The MCS server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.482 [6]." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 5.5] "To be compliant with the procedures in the present document, an MCData server shall support role of an MCS server as specified in subclause 5.2A." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 5.2A] "To be compliant with the procedures in the present document, an MCS server: - shall support the role of XCAP client as specified in IETF RFC 4825 [22]; - shall support the role of XDMC as specified in OMA OMA-TS-XDM_Group-V1_1_1 [3]; - shall support the procedure in subclause 6.2.4; - shall support the procedure in subclause 6.3.3.2.3; and - shall support the procedure in subclause 6.3.13.2.2." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.2.4] "The MCS server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.482 [10]. The MCS server shall perform the procedures in subclause 6.2.2 specified for GC." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.2.2] "In order to address an existing group document defining a group ID known by GC, the GC shall set the Request-URI of an HTTP request to a XCAP URI identifying a group document addressed by a group ID as described in subclause 7.2.10.2, where the group ID is set to the group ID known by GC and where the XCAP root URI is the XCAP root URI configured in the GC." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.3.3.2.3] "In order to retrieve a group document, an MCS server shall perform the procedures in subclause 6.3.3.2.1 specified for a GC." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.3.3.2.1] "In order to retrieve a group document, a GC shall send an HTTP GET request with the Request URI that references the document to be retrieved to the network according to procedures specified in IETF RFC 4825 [22] "Fetch a Document"." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.3.13.2.2] "In order to subscribe to notification of changes of: a) one or more MCS group documents of MCS groups identified by MCS group IDs; an MCS server shall send an initial SIP SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [12] and IETF RFC 5875 [13]. In the initial SIP SUBSCRIBE request, MCS server: a) shall include an application/resource-lists+xml MIME body. In the application/resource-lists+xml MIME body, the MCS server shall include one <entry> element for each document or element to be subscribed to, such that the "uri" attribute of the <entry> element: 1) contains a relative path reference: A) with the base URI being equal to the XCAP root URI configured in the MCS server; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 25 B) identifying a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is set to the MCS group ID; b) shall set the Request-URI to the configured public service identity for performing subscription proxy function of the GMS; c) shall include a P-Asserted-Identity header field containing the public service identity of the MCS server; e) shall include 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]; and f) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field. Upon receiving a SIP NOTIFY request associated with a subscription created as result of the sent initial SIP SUBSCRIBE request, the MCS server shall handle the SIP NOTIFY request according to IETF RFC 5875 [13]. In order to re-subscribe to notification of changes of a modified list of: a) one or more MCS group documents of MCS groups identified by MCS group IDs, the MCS server shall send a SIP re-SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [12] and IETF RFC 5875 [13]. In the SIP re-SUBSCRIBE request, MCS server: a) shall include an application/resource-lists+xml MIME body. In the application/resource-lists+xml MIME body, the MCS server shall include one <entry> element for each document or element to be subscribed to, such that the "uri" attribute of the <entry> element: 1) contains a relative path reference: A) with the base URI being equal to the XCAP root URI configured in the MCS server; and B) identifying a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is set to the MCS group ID; and b) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 7.2.12.1] "Authorization policies are described in the OMA OMA-TS-XDM_Group-V1_1_1 [3] "Authorization policies". An authenticated identity is authorized to read the <group> element of an MCS group document. An authenticated identity is authorized to read a <list-service> element of the <group> element of the MCS group document and any descendant elements of the <list-service> element: a) except a <list> element of the <list-service> element; and b) except descendant elements of the <list> element of the <list-service> element; if the authenticated identity is a member of an MCS group defined by the <list-service> element. An authenticated identity is authorized to read a <list> element of a <list-service> element of the <group> element of an MCS group document and any descendant elements of the <list> element if: a) the authenticated identity is a member of MCS group defined by the <list-service> element; and b) the MCS group document contains a <rule> element: 1) with the <conditions> element evaluating to true for the authenticated identity or without the <conditions> element; and 2) with the <actions> element containing the <on-network-allow-getting-member-list> element. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 26 An authenticated identity is authorized to read an <entry> element of a <list> element of a <list-service> element of the <group> element of the MCS group document and any descendant elements of the <entry> element if: a) the "uri" attribute of the <entry> element contains the authenticated identity; b) the "uri" attribute of the <mcvideo-mcvideo-id> element of the <entry> element contains the authenticated identity; or c) the "uri" attribute of the <mcdata-mcdata-id> element of the <entry> element contains the authenticated identity. An authenticated identity is authorized to read an MCS group document if the authenticated identity is listed in the authorized MCS server list specified in subclause 6.2.5.1. An authenticated identity is authorized to create, read, modify and delete an MCS group document if the MCS group document is stored: a) in users tree of the XUI equal to the authenticated identity; or b) in users tree of the another XUI, subject to MCS service provider policy. The MCS service provider policy can specified e.g. using an appropriate access permissions document specified in OMA OMA-TS-XDM_Core- V2_1 [2], stored in the user's tree of the other XUI; and unless precluded by other statement of this subclause. None is authorized to create, delete, and modify a <on-network-temporary> element of a <list-service> element of the <group> element of an existing MCS group document. None is authorized to delete a group document containing a <on-network-regrouped> element of a <list-service> element of the <group> element of an MCS group document. An authenticated identity is authorized to create and delete a <on-network-regrouped> element in the <list-service> element of the <group> element of an existing MCS group document if the authenticated identity is in authorized GMS list specified in subclause 6.2.5.1. An authenticated identity is authorized to subscribe to notification of changes of an MCS group document if: 1) the authenticated identity is a member of an MCS group defined by a <list-service> element of the <group> element of the MCS group document; 2) the authenticated identity is listed in the authorized MCS server list specified in subclause 6.2.5.1; or 3) the authenticated identity is listed in the authorized GMS list specified in subclause 6.2.5.1 and the subscription is on behalf of a constituent MCS group of the MCS group defined by the MCS group document." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 4.1] "… The present document provides the signalling control protocol enhancements to support the MCData architectural procedures specified in 3GPP TS 23.282 [2]. For on-network communications, the present document makes use of the existing IMS procedures specified in 3GPP TS 24.229 [5]. … The MCData procedures provided by the present document refer to: - the media plane procedures defined in 3GPP TS 24.582 [15]; - the group management procedures defined in 3GPP TS 24.481 [11]; - the identity management procedures defined in 3GPP TS 24.482 [24]; and - the security procedures defined in 3GPP TS 33.180 [26]. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 27 The MCData procedures provided by the present document access the configuration parameters provided by 3GPP TS 24.483 [42] and 3GPP TS 24.484 [12]. The following procedures are provided within this document: - common procedures are specified in clause 6; - procedures for registration in the IM CN subsystem and service authorisation are specified in clause 7; - procedures for affiliation are specified in clause 8; … The MCData UE primarily obtains access to the MCData service via E-UTRAN, using the procedures defined in 3GPP TS 24.301 [43]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 7.1] "This clause describes the procedures for SIP registration and MCData service authorization for the MCData client and the MCData service. The MCData UE can use SIP REGISTER or SIP PUBLISH for MCData service settings to perform service authorization for MCData. The decision which method to use is based on implementation and on availability of an access-token received as outcome of the user authentication procedure as described in 3GPP TS 24.482 [24]. If another MC service client (e.g. MCPTT, MCVideo) is operating at the same time on the same MC UE as the MCData client, then the MCData client shares the same SIP registration as the other MC service clients. The SIP REGISTER procedures in this clause are combined with the SIP REGISTER procedures for the other operating MC service clients to create a single SIP REGISTER request. If other MC service clients are already operating when the MCData client registers then a re-registration is performed containing the parameters for the other operating MC services. Although the access-token can be the same for the MCData service as for other MC services when performing service authorization for MCData along with other MC services using SIP REGISTER multipart MIME bodies for each MC service are included in the SIP REGISTER request. The MCData server can therefore receive multipart MIME bodies in the SIP REGISTER request. Multiple contact addresses (one per MC service client) can be included in a SIP REGISTER request provided they all contain the same IP address and port number (see 3GPP TS 24.229 [5] for further details of including multiple contact addresses in a single SIP REGISTER request). If the MCData client logs off from the MCData service but other MC service clients are to remain registered the MC UE performs a re-registration as specified in 3GPP TS 24.229 [5] without the supported g.3gpp.mcdata media feature tags and the g.3gpp.icsi-ref media feature tags containing the values of the supported MCData service ICSIs in the Contact header field of the SIP REGISTER request but with the parameters for the remaining operating MC service clients." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 7.3.1] "The MCData server obtains information that it needs to implement service authorization specific requirements from: a) any received third-party SIP REGISTER request (e.g. including information contained in the body of the third- party SIP REGISTER request) as specified in 3GPP TS 24.229 [5]. The body will carry the SIP REGISTER request as sent by the MCData client and may contain information needed for service authorization; or b) any received SIP PUBLISH request for MCData server settings containing the g.3gpp.mcdata.sds media feature tag along with the "require" and "explicit" header field parameters. The body of the SIP PUBLISH request will contain information needed for service authorization." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 7.3.1A] "When the MCData server receives a SIP REGISTER request sent from the MCData client contained within a message/sip MIME body of a received third-party SIP REGISTER request or a SIP PUBLISH request, it first determines whether XML MIME bodies included in the request are integrity protected. If XML MIME bodies are integrity protected the MCData server validates the signature of each of the XML MIME bodies. If the integrity protection check(s) pass or the XML MIME bodies are not integrity protected, the MCData server then determines whether the content in specific XML elements is confidentiality protected. If XML content is confidentiality protected, the MCData server decrypts the protected content. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 28 Upon receiving: - a SIP REGISTER request containing an application/vnd.3gpp.mcdata-info+xml MIME body within a message/sip MIME body of the SIP REGISTER request sent from the MCData client; or - a SIP PUBLISH request containing an application/vnd.3gpp.mcdata-info+xml MIME body and an application/poc-settings+xml MIME body; the MCData server: 1) shall determine if integrity protection has been applied to XML MIME bodies in the SIP request by following the procedures in subclause 6.5.3.4.1 for each XML MIME body; 2) if integrity protection has been applied, shall use the keying data described in subclause 6.5.3.2 and the procedures described in subclause 6.5.3.4.2 to verify the integrity of each of the XML MIME bodies; and 3) if all integrity protection checks succeed, shall continue with the remaining steps of this subclause. Upon receiving: - a SIP REGISTER request containing an application/vnd.3gpp.mcdata-info+xml MIME body with an <mcdata- access-token> element and an <mcdata-client-id> element within a message/sip MIME body of the SIP REGISTER request sent from the MCData client; or - a SIP PUBLISH request containing an application/vnd.3gpp.mcdata-info+xml MIME body with an <mcdata- access-token> element and an <mcdata-client-id> element, and an application/poc-settings+xml MIME body; the MCData server: 1) shall determine if confidentiality protection has been applied to the <mcdata-access-token> element and the <mcdata-client-id> element in the application/vnd.3gpp.mcdata-info+xml MIME body, by following the procedures in subclause 6.5.2.4.1; 2) if confidentiality protection has been applied to the <mcdata-access-token> element and <mcdata-client-id> element: a) shall use the keying information received in the MIKEY-SAKKE I_MESSAGE as specified in 3GPP TS 33.180 [26], along with the procedures described in subclause 6.5.2.4.2 to: i) decrypt the received access token in the <mcdata-access-token> element in the application/vnd.3gpp.mcdata-info+xml MIME body; and ii) decrypt the received MCData client ID in the <mcdata-client-id> element in the application/vnd.3gpp.mcdata-info+xml MIME body; b) if the decryption procedure succeeds, shall identify the MCData ID and the MCData client ID from the decrypted values; and c) if the decryption procedure fails, shall determine that confidentiality protection has not been successful; 3) if confidentiality protection has been applied to only one of the <mcdata-access-token> element or the <mcdata-client-id> element: a) shall determine that confidentiality protection has not been successful; 4) if confidentiality protection has not been applied: a) shall identify the MCData ID from <mcdata-access-token> element received in the application/vnd.3gpp.mcdata-info+xml MIME body; and b) shall identify the MCData client ID from the <mcdata-client-id> element received in the application/vnd.3gpp.mcdata-info+xml MIME body. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 29 Upon receiving a SIP PUBLISH request containing an application/vnd.3gpp.mcdata-info+xml MIME body with an <mcdata-request-uri> element, an <mcdata-client-id> element, and an application/poc-settings+xml MIME body, the MCData server: 1) shall determine if confidentiality protection has been applied to the <mcdata-request-uri> element and the <mcdata-client-id> element in the application/vnd.3gpp.mcdata-info+xml MIME body by following the procedures in subclause 6.5.2.4.1; 2) if confidentiality protection has been applied to the <mcdata-request-uri> element and the <mcdata-client- id> element: a) shall use the keying information described in subclause 6.5.2.2 along with the procedures described in subclause 6.5.2.4.2 to: i) decrypt the received encrypted MCData ID in the <mcdata-request-uri> element in the application/vnd.3gpp.mcdata-info+xml MIME body; and ii) decrypt the received encrypted MCData client ID in the <mcdata-client-id> element in the application/vnd.3gpp.mcdata-info+xml MIME body; b) if all decryption procedures succeed, shall identify the MCData ID and MCData client ID from the decrypted values; and c) if the decryption procedure fails, shall determine that confidentiality protection has not been successful; 3) if confidentiality protection has been applied to only one of the <mcdata-request-uri> element or <mcdata- client-id> element: a) shall determine that confidentiality protection has not been successful; 4) if confidentiality protection has not been applied: a) shall identify the MCData ID from the contents of the <mcdata-request-uri> element in the application/vnd.3gpp.mcdata-info+xml MIME body; and b) shall identify the MCData client ID from the <mcdata-client-id> element received in the application/vnd.3gpp.mcdata-info+xml MIME body." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 7.3.2] "The MCData server shall support obtaining service authorization specific information from the SIP REGISTER request sent from the MCData client and included in the body of a third-party SIP REGISTER request. NOTE 1: 3GPP TS 24.229 [5] 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 MCData client containing an application/vnd.3gpp.mcdata-info+xml MIME body with an <mcdata-access-token> element and an <mcdata-client-id> element within a message/sip MIME body of the SIP REGISTER request sent from the MCData client, the MCData server: 1) shall identify the IMS public user identity from the third-party SIP REGISTER request; 2) shall identify the MCData ID from the SIP REGISTER request sent from the MCData 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; 2A) shall check if the number of maximum simultaneous authorizations supported for the MCData user as specified in the <max-simultaneous-authorizations> element of the <anyExt> element contained in the <OnNetwork> element of the MCData service configuration document (see the service configuration document in 3GPP TS 24.484 [12]) has been reached. If reached, the MCData server shall not continue with the rest of the steps in this clause; 3) shall perform service authorization for the identified MCData ID as described in 3GPP TS 33.180 [26]; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 30 4) if service authorization was successful, shall bind the MCData ID and the MCData client ID to the IMS public user identity; 4A) if service authorization was successful and if the service authorization request was from an MCData user who is previously MCData service authorized on another MCData client (as determined by a comparison of the received MCData client ID with the MCData client ID of existing bindings), keep the current bindings and create a new binding between the MCData ID, the MCData client ID and the IMS public user identity; NOTE 2: The MCData server will store the binding MCData ID, MCData client ID, IMS public user identity and an identifier addressing the MCData server in an external database. 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 MCData ID and the MCData client ID to the identity of the MCData UE identified by the "+g.3gpp.registration-token" header field parameter in the Contact header field of the incoming third-party REGISTER request; and 6) if more than one binding exists for the MCData ID, shall include in the SIP 200 (OK) response an application/vnd.3gpp.mcdata-info+xml MIME body as specified in annex D.1 with a <multiple-devices-ind> element set to the value "true"." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 7.3.3] "The MCData server shall support obtaining service authorization specific information from a SIP PUBLISH request for MCData 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.mcdata-info+xml MIME body containing an <mcdata-access-token> element and an <mcdata-client-id> element; the MCData 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; … 4) shall perform service authorization for the identified MCData ID as described in 3GPP TS 33.180 [26]; 5) if service authorization was successful: a) shall bind the MCData ID and MCData client ID to the IMS public user identity; b) if the service authorization request was from an MCData user who is previously MCData service authorized on another MCData client (as determined by a comparison of the received MCData client ID with the MCData client ID of existing bindings), keep the current bindings and create a new binding between the MCData ID, MCData client ID and the IMS public user identity; and c) 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 MCData ID and MCData client ID to the identity of the MCData UE identified by 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 MCData server will store the binding MCData ID, MCData client ID, IMS public user identity and an identifier addressing the MCData server in an external database. … 7) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [34] and if processing of the SIP request was not successful, do not continue with the rest of the steps; 8) shall cache the received MCData service settings until the MCData service settings expiration timer expires; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 31 9) shall send a SIP 200 (OK) response according 3GPP TS 24.229 [5] with: a) if more than one binding exists for the MCData ID, an application/vnd.3gpp.mcdata-info+xml MIME body as specified in annex D.1 with a <multiple-devices-ind> element set to the value "true"; 10) shall download the MCData user profile from the MCData user database as defined in 3GPP TS 29.283 [37] if not already stored at the MCData server and use the <selected-user-profile-index> element of the poc- settings event package if included to identify the active MCData user profile for the MCData client; NOTE 2: If the <selected-user-profile-index> element of the poc-settings event package is included then only that MCData user profile is needed to be downloaded from the MCData user database. 11) if there is no <selected-user-profile-index> element included in the poc-settings event package then if multiple MCData user profiles are stored at the MCData server or downloaded for the MCData user from the MCData user database, shall determine the pre-selected MCData user profile to be used as the active MCData user profile by identifying the MCData user profile (see the MCData user profile document in 3GPP TS 24.484 [12]) in the collection of MCData user profiles that contains a <Pre-selected-indication> element; and NOTE 3: If only one MCData user profile is stored at the MCData server or only one MCData user profile is downloaded from the MCData user database, then by default this MCData user profile is the pre-selected MCData user profile. 12) if an <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCData user profile document with one or more <entry> elements containing an MCData group ID (see the MCData user profile document in 3GPP TS 24.484 [12]) for the served MCData ID, shall perform implicit affiliation as specified in subclause 8.3.2.15." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 7.3.5] "Upon receiving a SIP PUBLISH request containing: 1) an Event header field set to the "poc-settings" value; and 2) an Expires header field set to 0; the MCData server: 1) shall identify the IMS public user identity from the P-Asserted-Identity header field; 2) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [34] and if processing of the SIP request was successful, continue with the rest of the steps; 3) shall remove the MCData service settings; 4) shall remove the binding between the MCData ID and public user identity; and 5) shall send a SIP 200 (OK) response according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 7.3.6.1] "Upon receiving a SIP SUBSCRIBE request such that: 1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the participating MCData function of the served MCData user; 2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcdata-info+xml MIME body containing the<mcdata-request-uri> element which identifies an MCData ID served by the MCData server; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata,sds" (coded as specified in 3GPP TS 24.229 [5]), in a P-Asserted-Service header field according to IETF RFC 6050 [7]; and 3) the Event header field of the SIP SUBSCRIBE request contains the 'poc-settings' event type. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 32 the MCData server: 1) shall identify the served MCData ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request; 2) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the participating MCData function serving the MCData user, shall identify the originating MCData ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request; 3) if the originating MCData ID is different than the served MCData ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps; and 4) shall generate a 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [5], IETF RFC 6665 [36] and IETF RFC 4354 [35]. For the duration of the subscription, the MCData server shall notify subscriber about changes of the MCData service settings of the subscribed MCData user, as described in subclause 7.3.6.2." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 7.3.6.2] "In order to notify the subscriber about changes of the MCData service settings of the subscribed MCData client of the subscribed MCData user, the MCData server: 1) shall generate an application/poc-settings+xml MIME body as defined in 3GPP TS 24.379 [10] containing: a) the <selected-user-profile-index> element identifying the active MCData user profile; and 2) send a SIP NOTIFY request according to 3GPP TS 24.229 [5], IETF RFC 6665 [36] and IETF RFC 4354 [35] with the constructed application/poc-settings+xml MIME body." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 7.3.7] "If confidentiality protection is enabled as specified in subclause 6.5.2.3.1, and if the participating MCData function received a Client Server Key (CSK) within a SIP REGISTER request for service authorisation or SIP PUBLISH request for service authorisation, the participating MCData function may decide to update the CSK. In this case, the participating MCData function shall perform a key download procedure for the CSK. The participating MCData function: 1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]; 2) shall set the Request-URI to the URI received in the To header field in the third-party SIP REGISTER request; 3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata" along with parameters "require" and "explicit" according to IETF RFC 3841 [8]; 4) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcdata"; 5) shall include an application/mikey MIME body containing the algorithm to be used to protect the MCData signalling fields, the CSK-ID and the CSK encrypted within a MIKEY message to the MC client as specified in subclause 9.2.1 of 3GPP TS 33.180 [26] in the body of the SIP MESSAGE request; and 6) shall send the SIP MESSAGE request towards the MCData client according to 3GPP TS 24.229 [5]." [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.1.3.1] "… MCX User Service Authorization is the function that validates whether or not a MCX user has the authority to access certain MCX services. In order to gain access to MCX services, the MCX client in the UE presents an access token (acquired during user authentication as described in subclause 5.1.2) to each service of interest (i.e. Key Management, MCX server, Configuration Management, Group Management, etc.). If the access token is valid, then the user is granted the use of that service. Figure 5.1.3.1-1 shows the flow for user authorization which covers key management authorization, MCX user service authorization, configuration management authorization, and group management authorization. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 33 NOTE: All HTTP traffic between the UE and HTTP proxy, and all HTTP traffic between the UE and KMS (if not going through the HTTP proxy) is protected using HTTPS. For key management authorization, the KM client in the UE presents an access token to the KMS over HTTP. The access token shall be scoped for key management services as defined in annex B.4.2.2. The KMS validates the access token and if successful, provides one or more sets of user specific key material back to the UE KM client based on the MC service ID(s) present in the access token (MCPTT ID, MCVideo ID and/or MCData ID). User specific key material includes identity based key information for media and signalling protection…. This key management authorisation may be repeated for each KM service the user is authorised to use (MCPTT, MCVideo, MCData). In order to secure the transfer of user specific key material from the KMS to the KM client when using the TrK and InK, the KM client includes the TrK-ID and the InK-ID in the key management authorization request. … For MCData user service authorization, the MCData client in the UE presents an access token to the MCData server over SIP. The access token shall be scoped for MCData services as defined in annex B.4.2.2. The MCData server validates the access token and if successful, authorizes the user for full MCData services and sends an acknowledgement back to the MCData client. The MCData server then maps and maintains the IMPU to MCData ID association. The MCData ID to IMPU association shall only be known to the application layer. The SIP message used to convey the access token from the MCData client to the MCData server may be either a SIP REGISTER or SIP PUBLISH message. The UE can now perform configuration management authorization and download the user profile for the service(s) (MCPTT, MCVideo, MCData). Following the flow described in subclause 10.1.4.3 of 3GPP TS 23.280 [36] "MC service user obtains the MC service user profile(s) from the network", 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 access token shall be scoped for configuration management services as defined in annex B.4.2.2. The CM server receives the request and validates the access token, and if valid, the CM server uses the identity from the access token (MCPTT ID, MCVideo ID, MCData ID) to obtain the user profile from the MCX user database. The CM server then sends the user profile back to the CM client over HTTP. This configuration management authorisation may be repeated for each CM service the user is authorised to use (MCPTT, MCVideo, MCData). Upon receiving each user 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 profile, and following the flow shown in clause 10.1.5.2 of 3GPP TS 23.280 [36] "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 access token shall be scoped for group management services as defined in annex B.4.2.2. 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 5.7 of the present document. This group management authorisation may be repeated for each GM service the user is authorised to use (MCPTT, MCVideo, MCData). …" [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.1.3.2.1] "Depending on implementation, MCX user service authorization may be performed by sending the access token to the MCX server over the SIP-1 and SIP-2 reference points using either a SIP REGISTER message or a SIP PUBLISH message. Clause 5.1.3.2.2 describes how to use the SIP REGISTER message to transport the access token to the MCX server and clause 5.1.3.2.3 describes how to use the SIP PUBLISH message to transport the access token to the MCX server. … If an access token is available before SIP registration, or if the UE becomes de-registered and a SIP re-registration is required, the SIP REGISTER message may include the access token without requiring the user to re-authenticate. The access token may be sent over SIP to the MCX server to re-bind an IMPU and MC service ID (MCPTT ID, MCVideo ID or MCData ID) if either have changed (e.g. IMPU is different due to SIP deregistration/SIP re- registration, or user logs out and another user logs onto the same UE)." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 34 [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.1.3.2.2] "The use of a SIP REGISTER message to provide the access token to the MCX server is shown in figure 5.1.3.2.2-1. The inclusion of an access token in any particular SIP REGISTER message is optional. … Step 5 of figure 5.1.3.2.2-1 shows the access token message passed to the SIP core in a SIP REGISTER. Upon successful SIP authentication, the SIP core forwards the access token to the MCX server in the third part registration request message (Step 9). In Steps 9 through 11, the MCX server receives the third part registration request message, validates the access token, binds the IMPU and MC service ID (MCPTT ID, MCVideo ID or MCData ID) if the access token is valid, and responds to the 3rd party registration message." [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.1.3.2.3] "The use of a SIP PUBLISH message to provide the access token to the MCX server is shown in figure 5.1.3.2.3-1. The inclusion of an access token in any particular SIP PUBLISH message is optional. … As shown in Step 1 of figure 5.1.3.2.3-1, the SIP PUBLISH message carries the access token through the SIP core to the MCX server. In Steps 2 and 3, the MCX server receives the SIP PUBLISH message, validates the access token, binds the IMPU and MC service ID (MCPTT ID, MCVideo ID or MCData ID) if the access token is valid, and responds to the SIP PUBLISH message." [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.2.1] "… The primary purpose of these procedures is to allow MCX entities to communicate with each other using end-to-end security. End-to-end security provides assurance to MCX users that no unauthorized access to communications is taking place within the MCX network. End-to-end communication security may be applied to media when operating on- network and media, floor control, transmission control, and media control when operating off-network. A security domain is managed by a Key Management Server (KMS). The KMS is a component of the Common Services Core within the MCX system architecture. For any end-point to use or access end-to-end secure communications, it needs to be provisioned with key material associated to its identity by the KMS. Through the use of the KMS, MC administrators are able to manage the use of, and access to, secure communications within the MCX network. …" [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.2.2] "The security mechanism described in this clause allows a key, K, to be distributed from an initiating party to a receiving party. It provides confidentiality of the key, and integrity and authenticity of the payload. It is used within a number of different security procedures in this specification. The key, K, is distributed encrypted specifically to the receiving entity and signed by the initiating entity. Prior to call commencement, both MCX UEs shall be provisioned by the KMS with time-limited key material associated with the MCX entity's URI. The key is distributed with a 32-bit Key Identifier (K-ID). This payload is a MIKEY-SAKKE I_MESSAGE, as defined in IETF RFC 6509 [11], which ensures the confidentiality of the key, plus integrity and authenticity of the payload. The key is encrypted to the user identity (UID) associated to the receiving MCX entity using the security domain parameters provided in the public values in the certificate received from the KMS. The UID used to encrypt the data is derived from the receiving entity's URI (e.g. sip:user.002@mcptt.example.org) and a time-related parameter (e.g. the current year and month). The terminating entity's URI is added to the recipient field (IDRr) of the message. The payload includes the encrypted key and the key identifier (K-ID). The key is unique within the MC domain. On creating the key, the initiator generates a 32-bit key identifier (K-ID). The 4 most significant bits of the K-ID shall indicate the purpose of the key, the other 28-bits shall be randomly generated. The key identifier (K-ID) is stored in the CSB-ID field of the MIKEY I_MESSAGE. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 35 The payload is signed using (the KMS-provisioned key associated to) the identity of the initiating entity. The UID used to sign the data is derived from the initiating entity's URI (e.g. sip:user.001@mcptt.example.org) and a time-related parameter (e.g. the current year and month). The initiating entity's URI is added to the initiator field (IDRi) of the message. NOTE: This solution is for the end-to-end protection of keys and does not protect the identities transmitted. Identities may be masked by transmitting the UID within the MIKEY ID fields as described in Annex E.7. The security processes are summarized in figure 5.2.2-1." [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.8.1] "The 'key download' procedure is used to send keys from the MCX server to the MC client. It is used to distribute Multicast Signalling Keys (MuSiKs) to the MC clients, and it is used to update both the CSKs and MuSiKs. Within the 'key download' procedure, keys (CSK or MuSiKs) are encrypted specifically to the MC user and signed using an identity representing the MC Server. Prior to group key distribution, each MC client shall be provisioned by the KMS with time-limited key material associated with the MC User as described clause 5.3. The MC Server shall also be provisioned by the MC KMS with key material for an identity which is authorised to act as an MCX Server. The key (CSK or MuSiK) is distributed from the MCX Server to a MC client using the security mechanism described in clause 5.2.2, transported over the SIP bearer. End-point diversity is not required as end-points do not encrypt data, hence the extension in clause 5.2.3 is not applied. Additional parameters may be included as defined in clause 5.2.4. The SAKKE-to-self extension may be included as defined in clause 5.2.5. Identity hiding may be supported as defined in clause 5.2.6. The initiating entity shall be the initiating MCX Server and the receiving entity shall be the terminating MC user. The initiating entity URI shall be the FQDN of the MCX Server (e.g. MDSI of the MC Domain) and the receiving entity URI shall be the MC Service ID of the terminating user. The distributed key, K, shall be the CSK or MuSiK and the key identifier K-ID shall be the CSK-ID or MuSiK-ID (respectively). As a result of this 'key download' mechanism, the MC clients receive a new signalling key, CSK or MuSiK, identified by the 4 most significant bits of the key ID. The MCData Service server may use the Key Download procedure to indicate or modify the algorithm used to protect the MCData signalling fields (i.e. MCData signaling parameters, Data signaling payload and End to end security parameters) by including a 'signalling algorithm' parameter. The 'signalling algorithm' parameter is described in clause 8.5.4.1. The available algorithms shall be as defined in clause 8.5.4.2." [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.8.2] "The procedure for key download is described in figure 5.8.2-1: … 0. The MCX UE has been provisioned by a KMS with key material associated with the MC user. The MC UE has also registered with an MCX Server. As a consequence of this registration, the MC UE is subscribed to key download notifications from the MCX Server. 1. The MCX Server sends a key download message (SIP NOTIFY or SIP MESSAGE) to the MC UE. The MC UE extracts the signalling key from the key download message. 2. Upon successful extraction of the signalling key, the MC UE returns a key download success message (200 OK response) to the MCX Server. Upon receipt of a notification of success, the MCX Server is able to begin to use the key for protection of signalling traffic." |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.1.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 36 - For the underlying "transport bearer" over which the SS-UE1 (MCData client) and the MCData 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 [10] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCData operation in the MCData configuration document). IUT: - IUT (MCData Server) - The IUT (MCData 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 (MCData Server) also consists of all sub- systems of the MCData Server, including the Media Distribution Function, the MCData User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Floor Control Server. - The IUT (MCData Server) is the acting Participating Server and Controlling Server Preamble: - The IUT (MCData Server) is connected to PLMN1. - The IUT (MCData Server) is connected to the SS-UE1 (MCData client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4, where term "MCPTT" is replaced with "MCData". |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-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 (MCData 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 (MCData Server) respond by sending an HTTP 200 (OK) including the initial UE configuration document? <-- HTTP 200 (OK) 1 P 0C The SS-UE1 (MCData client) establishes a secure TLS tunnel as specified by ETSI TS 133 310 [11] (3GPP TS 33.310) to the authorisation endpoint of the IdM server as specified in ETSI TS 133 180 [12] (3GPP TS 33.180) using the configured URL of the authorisation endpoint of the IdM server as specified in the "<x>/OnNetwork/AppServerInfo/IDMSAuthEndpoint" leaf node, Table 5.5.8.1-1, ETSI TS 136 579-1 [1] (3GPP TS 36.579-1). - - - - 1 The SS-UE1 (MCData client) sends an OpenID Connect Authentication Request using HTTP POST --> HTTP POST (Authorization) - - 2 Check: Does the IUT (MCData 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 (MCData client) sends an HTTP POST Request message to the SS containing user name and password --> HTTP POST - - 4 Check: Does the IUT (MCData Server) send an HTTP 302 (Found) as the OpenID Connect Authentication Response? <-- HTTP 302 (Found) 1 P ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 37 St Procedure Message Sequence TP Verdict U - S Message 5 The SS-UE1 (MCData client) establishes a secure TLS tunnel as specified by ETSI TS 133 310 [11] (3GPP TS 33.310) to the token endpoint of the IdM server as specified in ETSI TS 133 180 [12] (3GPP TS 33.180) using the configured URL of the token endpoint of the IdM server as specified in the "/<x>/OnNetwork/AppServerInfo/IDMSTokenEndpoint" leaf node, Table 5.5.8.1-1, ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) - - - - 6 The SS-UE1 (MCData client) sends an HTTP POST Request message to the IUT (MCData 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 (MCData Server) send an HTTP 200 (OK) providing id_token, access_token and refresh token? <-- HTTP 200 (OK) 1 P 7A The SS-UE1 (MCData client) establishes a secure TLS tunnel as specified by ETSI TS 133 310 [11] (3GPP TS 33.310) to the HTTP Proxy as specified in ETSI TS 133 180 [12] (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 (MCData 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 (MCData Server) respond by sending identity-specific key information? <-- HTTP 200 (OK) 2 P 10 The SS-UE1 (MCData client) sends an HTTP POST message presenting an access token for Key Material Request --> HTTP POST - - 11 Check: Does the IUT (MCData Server) respond by sending identity-specific key information? <-- HTTP 200 (OK) 2 P 12 The SS-UE1 (MCData client) sends a SIP REGISTER request for service authorisation --> SIP REGISTER - - 13 Check: Does the IUT (MCData Server) respond by sending an SIP 200 (OK) message? <-- SIP 200 (OK) 3 P 14 The SS-UE1 (MCData 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: MCData UE Configuration document, MCData User Profile Configuration Document, and the MCData 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 (MCData Server) respond by sending an SIP 200 (OK) message? <-- SIP 200 (OK) 4 P 16 Check: Does the IUT (MCData Server) send a SIP NOTIFY message containing the XCAP-URI of the documents? <-- SIP NOTIFY 4 P 17 The SS-UE1 (MCData client) responds with a SIP 200 (OK) message --> SIP 200 (OK) - - 18 The SS-UE1 (MCData client) sends an HTTP GET Request message that contains the access token and the XCAP-URI of the MCData UE Configuration document --> HTTP GET - - 19 Check: Does the IUT (MCData Server) send the HTTP 200 (OK) message including the MCData UE Configuration Document? <-- HTTP 200 (OK) 4 P 20 The SS-UE1 (MCData client) sends an HTTP GET Request message that contains the access token and the XCAP-URI of the MCData User Profile Configuration Document --> HTTP GET - - ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 38 St Procedure Message Sequence TP Verdict U - S Message 21 Check: Does the IUT (MCData Server) send the HTTP 200 (OK) message including the MCData User Profile Configuration Document? <-- HTTP 200 (OK) 4 P 22 The SS-UE1 (MCData client) sends an HTTP GET Request message that contains the access token and the XCAP-URI of the MCData Service Configuration Document --> HTTP GET - - 23 Check: Does the IUT (MCData Server) send the HTTP 200 (OK) message including the MCData Service Configuration Document? <-- HTTP 200 (OK) 4 P 24 The SS-UE1 (MCData 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 MCData group ID identifies a group document --> SIP SUBSCRIBE - - 25 Check: Does the IUT (MCData Server) respond with a HTTP 200 (OK) message <-- SIP 200 (OK) 5 P 26 Check: Does the IUT (MCData 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 (MCData client) sends a SIP 200 (OK) message --> SIP 200 (OK) - - 28 The SS-UE1 (MCData 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 (MCData Server) send an HTTP 200 (OK) message including the Group Document 'MCData UE Configuration document'? <-- HTTP 200 (OK) 5 P 29A Check: Does the IUT (MCData 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 (MCData client) sends a SIP 200 (OK) message --> SIP 200 (OK) - - 30 The SS-UE1 (MCData 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 (MCData Server) send a SIP 200 (OK)? <-- SIP 200 (OK) 6 P 32-33 Void -- - - - |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-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 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 39 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 [27] 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_user auth_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 [28] 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, conditions MCDATA and UECONFIG. 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, conditions MCDATA and UEUSERPROF. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 40 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, conditions MCDATA and 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: 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, conditions MCDATA and 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, conditions MCDATA and 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, conditions MCDATA and 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_MCData_PublicServ iceId_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 149-1 V1.1.1 (2026-02) 41 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_MCData_PublicServiceId_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_MCData_PublicServiceId_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_MCData_PublicServiceId_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, conditions MCDATA and POC- SETTINGS-EVENT Information Element Value/remark Comment Reference Condition Request-Line Request-URI tsc_MCData_PublicServ iceId_B The public service identity identifying the originating participating MCData function serving the MCData user ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 42 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_MCData_PublicServiceId_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 MCDATA Server - MCDATA Client / Configuration / Group Creation / Group Regroup Creation / Group Regroup Teardown |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 and supports new MCData terminated group } ensure that { when { the UE (MCData client) initiates creation of the terminated group by sending a HTTP PUT request } then { IUT (MCData Server) responds to the UE (MCData Client) with a HTTP 201 (Created) } } (2) with { IUT (MCData Server) having establish terminated group } ensure that { when { the SS-UE1 (MCData Client) initiates creation of the terminated temporary group by sending a HTTP POST request } then { IUT (MCData Server) responds with a HTTP 200 (OK) containing the GMOP group-regroup- creation-response } } (3) with { IUT (MCData Server) having establish a temporary group } ensure that { when { the UE (MCData client) initiates tear down of the temporary group by sending a HTTP DELETE request } then { IUT (MCData Server) responds to the UE (MCData Client) with HTTP 200 (OK) message } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 43 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 484 [8] (3GPP TS 24.484) clauses 4.3.1, 4.3.4, 4.4, 6.3.13.2.3, 6.3.3.2.3, 6.3.3.2.1, 4.1.4, 10.2.1, 10.2.1A, 10.3.1, 10.3.1A, 10.4.1, 6.2.3, ETSI TS 124 481 [6] (3GPP TS 24.481) clauses 5.5, 5.2A, 6.2.4, 6.2.2, 6.3.2.2.2, 6.3.2.2.1, 6.3.3.2.3, 6.3.3.2.1, 6.3.13.2.2, 6.3.14.2, 6.3.15.2, 6.3.2.3, 6.3.14.3.1, 6.3.15.3.1, ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 6.3.3, 6.3.4, 6.3.5, 8.3.3.3, 8.3.3.4, 8.3.3.5, ETSI TS 133 180 [12] (3GPP TS 33.180) clauses 5.7.1, 5.7.3, 5.8.1, 7.3.2, 7.3.3.2. Unless otherwise stated these are Rel-14 requirements. [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 4.3.1] "The MCS server obtains the appropriate MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server. The MCS server obtains the MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server. The MCS server subscribes to the MCS service configuration document for each mission critical organisation that is provisioned that is supported by the MCS server using the procedure specified in subclause 6.3.13.2.3. How the MCS server is provisioned with the identities of the mission critical organisations is out of scope of the present document. If the MCS service configuration document has been updated since the current version stored at the MCS server, then the MCS server will receive a SIP NOTIFY request containing an HTTPS URI of the MCS service configuration document. Retrieval by the MCS server, using the notified HTTPS URI, of the MCS service configuration document is performed as specified in subclause 6.3.3.2.3. NOTE: The MCS server can be notified of changes to the MCS service management configuration document at any time while operating the MCS." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 4.3.4] "The format of the MCData service configuration document downloaded to the MCData server is defined in subclause 10.4." [ETSI TS 124 484 [8] (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 MCS UE initial configuration document received from an MCS administrator into an appropriate format for configuration of the MCS UE initial configuration MO. If the MCS UE initial configuration MO contains a <default-user-profile> element that identifies an MCS user profile configuration document, the configuration management server needs to convert the identified MCS user profile configuration document received from an MCS administrator into an appropriate format for configuration of the MCS user profile configuration MO. Once an MCS User Profile configuration document has been created or updated by the MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to store MCS user profile configuration document as the user profile in the MC service user database. In order to download the MCS user profile configuration document to an MCS UE or to support an MCS UE updating the MCS user profile configuration document, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to obtain the MCS user profile from the MC service user database. In order to be notified of changes to an MCS user profile configuration document(s) that have been subscribed to by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to be notified of changes to the MCS user profile stored in the MC service user database. In order to delete the MCS user profile when requested by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to delete the MCS user profile from the MC service user database. NOTE: The configuration management server and group management server functionality for offline configuration is out of scope of the present document." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 44 [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.13.2.3] "In order to subscribe to an MCS service configuration document, an MCS server shall send an initial SIP SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [22] and IETF RFC 5875 [11]. In the initial SIP SUBSCRIBE request, MCS server: a) shall set the Request URI to a SIP URI containing: 1) the base URI being equal to the public service identity of the CMS configured in the MCS server; and 2) the "auid" parameter set to the application usage identifying th MCS service configuration document; b) shall include a P-Asserted-Identity header field containing the public service identity of the MCS server; c) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [22]), in a P-Asserted-Service header field according to IETF RFC 6050 [23]; and d) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field. Upon receiving a SIP NOTIFY request associated with a subscription created as result of the sent initial SIP SUBSCRIBE request, the MCS server shall handle the SIP NOTIFY request according to IETF RFC 5875 [11]. In order to re-subscribe to notification of changes to an MCS service configuration document, an MCS server shall send a SIP re-SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [22] and IETF RFC 5875 [11]. In the SIP re-SUBSCRIBE request, MCS server: a) shall set the Request URI to a SIP URI containing: 1) the base URI being equal to the public service identity of the CMS configured in the MCS server; and 2) the "auid" parameter set to the application usage identifying an MCS service configuration document; and b) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.3.2.3] "In order to retrieve a configuration management document via the CSC-5 reference point, an MCS Server shall perform the procedures in subclause 6.3.3.2.1 specified for GC. The MCS server shall set the Request-URI of the HTTP GET request to identify the XML document based on configuration and include the "auid" as per the appropriate application usage." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.3.2.1] "In order to retrieve a configuration management document, a GC shall send an HTTP GET request with the Request URI that references the document to be updated to the network according to procedures specified in IETF RFC 4825 [14] "Retrieve a Document"." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 4.1.4] "An MCData service administrator can, using an MCData UE configure the: - MCData UE configuration document; - MCData user profile configuration document; - MCData service configuration document; and - MCData related group configuration data in the MCS group document. The format of the MCData UE configuration document is defined in subclause 10.2. The format of the MCData user profile configuration document is defined in subclause 10.3. The format of the MCData service configuration document is defined in subclause 10.4." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 45 [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.2.1] "The MCData UE configuration document is specified in this subclause. The MCData UE configuration document content is based on requirements of Annex A.2 of 3GPP TS 23.282 [24], in accordance with OMA OMA-TS- XDM_Core-V2_1-20120403-A [2]. The usage of an MCData UE configuration document in the MCData service is described in 3GPP TS 24.282 [25] and 3GPP TS 24.582 [26]. The schema definition is provided in subclause 10.2.2.3. An MCData UE configuration document may apply to all MCData UEs of a mission critical organization or apply to specific MCData UEs identified in the <mcdata-UE-id> element. If there is no <mcdata-UE-id> element in the MCData UE configuration document, then by default the MCData UE configuration document applies to all MCData UEs of the mission critical organization that are not specifically identified in the <mcdata-UE-id> element of another MCData UE configuration document of the mission critical organization. Each MCData UE of a mission critical organization is configured with an MCData UE configuration document that is identified by the instance ID of the MCData UE. MCData UE configuration documents of a MCData user are contained as "XDM collections" in the user's directory of the users tree, in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCData ID, as the user has been already authenticated. A MCData UE configuration document corresponding to a specific MCData UE the MCData user has used to authenticate and is authorised to use the MCData service with is placed in the user directory of the MCData user. The MCData UE configuration document acts as a template for the CMS to generate UE configuration documents that are downloaded to specific MCData UEs. The MCData UE configuration document that acts as a template is referred to as a "master MCData UE configuration document". The master MCData UE configuration document is stored in the users tree of that MCData system administrator. The master MCData UE configuration document does not directly apply to a specific MCData UE, but instead acts as template that the CMS uses to populate the MCData UE configuration documents of MCData UEs identified by elements of the <MCData-UE-id> element. For MCData UE configuration documents that correspond to a specific MCData UE, the name of the MCData UE configuration document is created from a value defined by the corresponding element that identifies the MCData UE within the <MCData-UE-id> element. For a master MCData UE configuration documents that does not contain a <MCData-UE- id> element, the name of the MCData UE configuration document stored in the user directory is "DEFAULT-MCData- UE.xml"." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.2.1A] "The MCData UE configuration document is accessed using the same XCAP URI, regardless of whether the MCData UE has a specific MCData UE configuration document configured or the master MCData UE configuration document applies. The CMS shall generate the UE's MCData UE configuration document from the master MCData UE configuration document if the MCData administrator did not provision a specific MCData UE configuration document. In this generated document, the <MCData-UE-id> element shall be set to the MCData client's UE ID. The UE's MCData UE configuration document shall always be stored with the filename corresponding to the UE's MCData UE ID under the user's directory of the users tree. The XCAP URI used by the MCData client to access the UE's MCData UE configuration document shall be: - CMSXCAPROOTURI/org.3gpp.mcdata.ue-config/users/sip:MCDATAID/MCSUEID." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.3.1] "The MCData user profile configuration document is specified in this subclause. The MCData user profile configuration document content is based on requirements of Annex A.3 of 3GPP TS 23.282 [24], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCData user profile in the MCData service is described in 3GPP TS 24.282 [25]. The schema definition is provided in subclause 10.3.2. MCData user profile documents are "XDM collections" in the user's directory of the users tree, in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCData ID, as the user has been already authenticated. The name of the MCData user profile document matches the value of the <ProfileName> element in the MCData user profile document." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 46 [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.3.1A] "The XCAP URI used by the MCData client to access the MCData user's MCData user profile documents shall be: CMSXCAPROOTURI/org.3gpp.mcdata.user-profile/users/sip:MCDATAID/mcdata-user-profile-INDEX.xml Where INDEX is the index of the MCData user profile as defined in subclause 10.3.2.8." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.4.1] "The MCData service configuration document is specified in this subclause. The MCData service configuration document content is based on requirements of Annex A.5 of 3GPP TS 23.282 [24], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCData service configuration in the MCData service is described in 3GPP TS 24.282[25] and 3GPP TS 24.582 [26]. The schema definition is provided in subclause 10.4.2.3. Each mission critical organization is configured with an MCData service configuration document." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.2.3] "The MCS server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.482 [6]." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 5.5] "To be compliant with the procedures in the present document, an MCData server shall support role of an MCS server as specified in subclause 5.2A." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 5.2A] "To be compliant with the procedures in the present document, an MCS server: - shall support the role of XCAP client as specified in IETF RFC 4825 [22]; - shall support the role of XDMC as specified in OMA OMA-TS-XDM_Group-V1_1_1 [3]; - shall support the procedure in subclause 6.2.4; - shall support the procedure in subclause 6.3.3.2.3; and - shall support the procedure in subclause 6.3.13.2.2." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.2.4] "The MCS server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.482 [10]. The MCS server shall perform the procedures in subclause 6.2.2 specified for GC." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.2.2] "In order to address an existing group document defining a group ID known by GC, the GC shall set the Request-URI of an HTTP request to a XCAP URI identifying a group document addressed by a group ID as described in subclause 7.2.10.2, where the group ID is set to the group ID known by GC and where the XCAP root URI is the XCAP root URI configured in the GC." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.2.2.2] "In order to create a group document, a GMC shall perform the procedures in subclause 6.3.2.2.1 specified for GC. NOTE: When the GMC has not received the assigned MCS group ID from the GMS, the GMC can set empty value to the "uri" attribute of the <list-service> element of the <group> element of the XML document specified in subclause 7.2.1. …" ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 47 [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.2.2.1] "In order to create a group document, a GC shall create an XML document of the application usage specified in subclause 7.2.1 and shall send the XML document to the network according to procedures specified in IETF RFC 4825 [22] "Create or Replace a Document". The GC shall set the Request-URI of the HTTP PUT request to an XCAP URI in users tree where the XUI is set to a group creation XUI configuration parameter." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.3.3.2.3] "In order to retrieve a group document, an MCS server shall perform the procedures in subclause 6.3.3.2.1 specified for a GC." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.3.3.2.1] "In order to retrieve a group document, a GC shall send an HTTP GET request with the Request URI that references the document to be retrieved to the network according to procedures specified in IETF RFC 4825 [22] "Fetch a Document"." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.3.13.2.2] "In order to subscribe to notification of changes of: a) one or more MCS group documents of MCS groups identified by MCS group IDs; an MCS server shall send an initial SIP SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [12] and IETF RFC 5875 [13]. In the initial SIP SUBSCRIBE request, MCS server: a) shall include an application/resource-lists+xml MIME body. In the application/resource-lists+xml MIME body, the MCS server shall include one <entry> element for each document or element to be subscribed to, such that the "uri" attribute of the <entry> element: 1) contains a relative path reference: A) with the base URI being equal to the XCAP root URI configured in the MCS server; and B) identifying a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is set to the MCS group ID; b) shall set the Request-URI to the configured public service identity for performing subscription proxy function of the GMS; c) shall include a P-Asserted-Identity header field containing the public service identity of the MCS server; e) shall include 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]; and f) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field. Upon receiving a SIP NOTIFY request associated with a subscription created as result of the sent initial SIP SUBSCRIBE request, the MCS server shall handle the SIP NOTIFY request according to IETF RFC 5875 [13]. In order to re-subscribe to notification of changes of a modified list of: a) one or more MCS group documents of MCS groups identified by MCS group IDs, the MCS server shall send a SIP re-SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [12] and IETF RFC 5875 [13]. In the SIP re-SUBSCRIBE request, MCS server: a) shall include an application/resource-lists+xml MIME body. In the application/resource-lists+xml MIME body, the MCS server shall include one <entry> element for each document or element to be subscribed to, such that the "uri" attribute of the <entry> element: 1) contains a relative path reference: A) with the base URI being equal to the XCAP root URI configured in the MCS server; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 48 B) identifying a group document addressed by a group ID as described in subclause 7.2.10.2 where the group ID is set to the MCS group ID; and b) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field." [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.3.14.2] "In order to form a temporary MCS group, a GMC shall send a HTTP POST request according to procedures specified in IETF RFC 2616 [21] and subclause 6.2.3. In the HTTP POST request, the GMC: a) shall set the Request-URI to an XCAP URI: 1) in users tree where the XUI is set to a group creation XUI configuration parameter; and 2) with the document selector identifying the temporary MCS group to be created; and b) shall include an application/vnd.3gpp.GMOP+xml MIME body containing a GMOP document requesting group regroup creation specified in subclause 7.3.4.3, with a <group> element containing a group document for an MCS group. In the group document, the GMC shall include the <on-network-temporary> element according to subclause 7.2. In the <on-network-temporary> element, the GMC shall include <constituent- MCPTT-group-IDs> element according to subclause 7.2. In the <constituent-MCPTT-group-IDs> element, the GMC shall include one <constituent-MCPTT-group-ID> element according to subclause 7.2 for each MCS group to be combined. Upon reception of an HTTP 2xx response to the sent HTTP POST request, the GMC shall consider the temporary MCS group formation as successful. Upon reception of an HTTP 409 (Conflict) response with at least one <alt-value> element in the <uniqueness-failure> error element, the GMC may repeat procedures of the present subclause and identify the temporary MCS group being formed with an MCS Group ID indicated in an <alt-value> element." [ETSI TS 124 481 [6] (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 [6] (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; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 49 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… 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: A) shall set the Request-URI to an XCAP URI: i) with the document selector identifying a group document addressed by a group ID as specified in subclause 7.2.10.2, where the group ID is set to the MCS group ID of the MCS group to be combined; ii) with the node selector identifying a <on-network-regrouped> element of the constituent MCS group such that the <on-network-regrouped> element has the "temporary-MCPTT-group- ID" attribute set to the content of the "uri" attribute of the <list-service> element of the group document included in the received HTTP POST request; iii) if the MCS group ID of the MCS group to be combined is owned by the MCS provider of the GMS, with the XCAP root URI of the MCS provider of the GMS; and iv) if the MCS group ID of the MCS group to be combined is owned by an MCS provider other than the MCS provider of the GMS, with XCAP root URI derived using the group ID routing database as specified in subclause 6.2.5.2 and the MCS group ID of the MCS group to be combined; B) shall set the X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.482 [10] to a public service identity of the GMS; and C) shall include an application/vnd.3gpp.GMOP+xml MIME body containing a GMOP document requesting group regroup check specified in subclause 7.3.4.4 with a <on-network-regrouped> element. In the <on-network-regrouped> element, the GMS: i) shall set the "temporary-MCPTT-group-ID" attribute to the content of the "uri" attribute of the <list-service> element of the group document included in the received HTTP POST request; ii) shall set the "temporary-MCPTT-group-requestor" attribute to the identity of the sender of the received HTTP POST request; iii) shall include the <constituent-MCPTT-group-IDs> element set to content of the <constituent-MCPTT-group-IDs> element of <on-network-temporary> element of the <list- service> element of the group document of the MCS group included in the received HTTP POST request; iv) if an <on-network-group-priority> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <on- network-group-priority> element set to content of the <on-network-group-priority> element of the <list-service> element of the group document included in the received HTTP POST request; v) if a <protect-media> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <protect-media> element set to content of the <protect-media> element of the <list-service> element of the group document included in the received HTTP POST request; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 50 vi) if a <protect-floor-control-signalling> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <protect- floor-control-signalling> element set to content of the <protect-floor-control-signalling> element of the <list-service> element of the group document included in the received HTTP POST request; and vii) if a <require-multicast-floor-control-signalling> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <require-multicast-floor-control-signalling> element. … Upon reception of HTTP 2xx responses to all sent HTTP POST requests, the GMS: a) 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> 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 an HTTP POST request according to procedures specified in IETF RFC 2616 [21] and subclause 6.2.5. In the HTTP POST request, the GMS: A) shall set the Request-URI to an XCAP URI: i) with the document selector identifying a group document addressed by a group ID as specified in subclause 7.2.10.2, where the group ID is set to the MCS group ID of the MCS group to be combined; ii) with the node selector identifying a <on-network-regrouped> element of the constituent MCS group such that the <on-network-regrouped> element has the "temporary-MCPTT-group- ID" attribute set to the content of the "uri" attribute of the <list-service> element of the group document included in the received HTTP POST request; iii) if the MCS group ID of the MCS group to be combined is owned by the MCS provider of the GMS, with the XCAP root URI of the MCS provider of the GMS; and iv) if the MCS group ID of the MCS group to be combined is owned by an MCS provider other than the MCS provider of the GMS, with XCAP root URI derived using the group ID routing database as specified in subclause 6.2.5.2 and the MCS group ID of the MCS group to be combined; B) shall set the X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.482 [10] to a public service identity of the GMS; and C) shall include an application/vnd.3gpp.GMOP+xml MIME body with a GMOP document requesting group regroup notification specified in subclause 7.3.4.5. In the GMOP document requesting group regroup notification, the GMS: i) shall include a <on-network-regrouped> element. In the <on-network-regrouped> element, the GMS: - shall set the "temporary-MCPTT-group-ID" attribute to the content of the "uri" attribute of the <list-service> element of the group document included in the received HTTP POST request; - shall set the "temporary-MCPTT-group-requestor" attribute to the identity of the sender of the received HTTP POST request; - shall include the <constituent-MCPTT-group-IDs> element set to content of the <constituent-MCPTT-group-IDs> element of <on-network-temporary> element of the <list-service> element of the group document of the MCS group included in the received HTTP POST request; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 51 - if an <on-network-group-priority> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <on-network-group-priority> element set to content of the <on-network-group- priority> element of the <list-service> element of the group document included in the received HTTP POST request; - if a <protect-media> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <protect- media> element set to content of the <protect-media> element of the <list-service> element of the group document included in the received HTTP POST request; - if a <protect-floor-control-signalling> element is included in the <list-service> element of the group document included in the received HTTP POST request, shall include the <protect-floor-control-signalling> element set to content of the <protect-floor-control- signalling> element of the <list-service> element of the group document included in the received HTTP POST request; and - if a <require-multicast-floor-control-signalling> element is included in the <list- service> element of the group document included in the received HTTP POST request, shall include the <require-multicast-floor-control-signalling> element. NOTE: GMK is not included in the GMOP document requesting group regroup notification as GMK is provided only using SIP. 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 [6] (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: A) shall set the Request-URI to an XCAP URI: i) with the document selector identifying a group document addressed by a group ID as specified in subclause 7.2.10.2, where the group ID is set to the MCS group ID of the constituent MCS group; ii) with the node selector identifying a <on-network-regrouped> element of the constituent MCS group, such that the "temporary-MCPTT-group-ID" attribute of the <on-network- regrouped> element contains the temporary MCS group ID of the temporary MCS group; iii) if the MCS group ID of the constituent MCS group is owned by the MCS provider of the GMS, with the XCAP root URI of the MCS provider of the GMS; and iv) if the MCS group ID of the constituent MCS group is owned by an MCS provider other than the MCS provider of the GMS, with XCAP root URI derived using the group ID routing database as specified in subclause 6.2.5.2 and the MCS group ID of the constituent MCS group; and B) shall set the X-3GPP-Asserted-Identity header field as specified in 3GPP TS 24.482 [10] to a public service identity of 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 ETSI TS 104 149-1 V1.1.1 (2026-02) 52 [ETSI TS 124 481 [6] (3GPP TS 24.481), clause 6.3.15.2] "In order to tear down a temporary MCS group, the GMC shall send an HTTP DELETE request with Request-URI with an XCAP URI identifying a group document of the temporary MCS group according to procedures specified in IETF RFC 4825 [22] "Delete an Element"." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 6.3.3] "This subclause describes how an MCData server accesses a group document from a group management server. Upon receipt of a SIP request: 1) if the MCData server is not yet subscribed to the group document for the group identity in the <mcdata- request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP request, the MCData server shall subscribe to the "xcap-diff" event-package for the group document of this group identity as specified in 3GPP TS 24.481 [11]; NOTE: As a group document can potentially have a large content, the MCData server can subscribe to the group document indicating support of content-indirection as defined in IETF RFC 4483 [13], by following the procedures in 3GPP TS 24.481 [11]. 2) upon receipt of a SIP 404 (Not Found) response as a result of attempting to subscribe to the "xcap-diff" event- package for the group document of the group identity in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP request as specified in 3GPP TS 24.481 [11], the MCData server shall send the SIP 404 (Not Found) response with the warning text set to "113 group document does not exist" in a Warning header field as specified in subclause 4.9. Otherwise, continue with the rest of the steps; and 3) upon receipt of any other SIP 4xx, SIP 5xx or SIP 6xx response as a result of attempting to subscribe to the "xcap-diff" event-package for the group document of the group identity in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP INVITE request as specified in 3GPP TS 24.481 [11], the MCData server shall send the SIP final response with the warning text set to "114 unable to retrieve group document" in a Warning header field as specified in subclause 4.4 and shall not continue with the rest of the steps;" [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 6.3.4] "The MCData server shall only send MCData messages to affiliated group members. The MCData server determines whether a user is affiliated to a group by following the procedures in subclause 6.3.5. The MCData server performs the affiliation check in subclause 6.3.5 on each entry contained in the <list> element of the group document." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 6.3.5] "The MCData server shall determine that the MCData user, with MCData User ID, is affiliated to the MCData group, with MCData Group ID, at the MCData client, with MCData client ID, if the elements, as described in subclause 8.3.3.2, exist with their expected values, as below: 1. an MCData group information entry with MCData group ID same as the MCData group ID under consideration; 2. in the MCData group information entry found in 1, an MCData user information entry with the MCData ID same as the MCData ID under consideration; 3. in the MCData user information entry found in 2, an MCData client information entry with MCData Client ID same as the MCData client ID under consideration; and 4. in the MCData user information entry found in 2, an expiration time, which has not expired." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 53 [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.3.3] "Upon receiving a SIP PUBLISH request such that: 1) Request-URI of the SIP PUBLISH request contains the public service identity of the controlling MCData function associated with the served MCData group; 2) the SIP PUBLISH request contains an application/vnd.3gpp.mcdata-info+xml MIME body containing the <mcdata-request-uri> element and the <mcdata-calling-user-id> element; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [5]), in a P- Asserted-Service header field according to IETF RFC 6050 [7]; 4) the Event header field of the SIP PUBLISH request contains the "presence" event type; and 5) SIP PUBLISH request contains an application/pidf+xml MIME body indicating per-group affiliation information constructed according to subclause 8.4.1; then the MCData server: 1) shall identify the served MCData group ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP PUBLISH request; 2) shall identify the handled MCData ID in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP PUBLISH request; … 6) shall respond with SIP 200 (OK) response to the SIP PUBLISH request according to 3GPP TS 24.229 [5], IETF RFC 3903 [34]. In the SIP 200 (OK) response, the MCData server: a) shall set the Expires header field according to IETF RFC 3903 [34], to the selected expiration time; 7) if the "entity" attribute of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request is different than the served MCData group ID, shall not continue with the rest of the steps; 8) if the handled MCData ID is different from the MCData ID in the "id" attribute of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request, shall not continue with the rest of the steps; 9) shall consider an MCData group information entry such that: a) the MCData group information entry is in the list of MCData group information entries described in subclause 8.3.3.2; and b) the MCData group ID of the MCData group information entry is equal to the served MCData group ID; as the served MCData group information entry; 10) if the selected expiration time is zero: a) shall remove the MCData user information entry such that: i) the MCData user information entry is in the list of the MCData user information entries of the served MCData group information entry; and ii) the MCData user information entry has the MCData ID set to the served MCData ID; 11) if the selected expiration time is not zero: a) shall consider an MCData user information entry such that: i) the MCData user information entry is in the list of the MCData user information entries of the served MCData group information entry; and ii) the MCData ID of the MCData user information entry is equal to the handled MCData ID; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 54 as the served MCData user information entry; b) if the MCData user information entry does not exist: i) shall insert an MCData user information entry with the MCData ID set to the handled MCData ID into the list of the MCData user information entries of the served MCData group information entry; and ii) shall consider the inserted MCData user information entry as the served MCData user information entry; and c) shall set the following information in the served MCData user information entry: i) set the MCData client ID list according to the "client" attributes of the <affiliation> elements of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and ii) set the expiration time according to the selected expiration time; 12) shall identify the handled p-id in the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and 13) shall perform the procedures specified in subclause 8.3.3.5 for the served MCData group ID." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.3.4] "NOTE: Usage of one SIP SUBSCRIBE request to subscribe for notification about change of affiliation state of several MCData users served by the same MCData server is not supported in this version of the specification. Upon receiving a SIP SUBSCRIBE request such that: 1) Request-URI of the SIP SUBSCRIBE request contains the public service identity of the controlling MCData function associated with the served MCData group; 2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcdata-info+xml MIME body containing the<mcdata-request-uri> element and the <mcdata-calling-user-id> element; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [5]), in a P- Asserted-Service header field according to IETF RFC 6050 [7]; 4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; and 5) the SIP SUBSCRIBE request contains an application/simple-filter+xml MIME body indicating per-user restrictions of presence event package notification information according to subclause 8.4.2 indicating the same MCData ID as in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request; then the MCData server: 1) shall identify the served MCData group ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request; 2) shall identify the handled MCData ID in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request; 3) if the Expires header field of the SIP SUBSCRIBE request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP SUBSCRIBE request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps; 4) if an MCData group for the served MCData group ID does not exist in the group management server according to 3GPP TS 24.481 [11], shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [5], IETF RFC 3903 [34] and IETF RFC 3856 [39] and skip the rest of the steps; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 55 5) if the handled MCData ID is not a member of the MCData group identified by the served MCData group ID, shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [5], IETF RFC 3903 [34] and IETF RFC 3856 [39] and skip the rest of the steps; and 6) shall generate a SIP 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [5], IETF RFC 6665 [36]. For the duration of the subscription, the MCData server shall notify subscriber about changes of the information of the served MCData ID, as described in subclause 8.3.3.5." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.3.5] "In order to notify the subscriber identified by the handled MCData ID about changes of the affiliation status of the served MCData group ID, the MCData server: 1) shall consider an MCData group information entry such that: a) the MCData group information entry is in the list of MCData group information entries described in subclause 8.3.3.2; and b) the MCData group ID of the MCData group information entry is equal to the served MCData group ID; 2) shall consider an MCData user information entry such: a) the MCData user information entry is in the list of the MCData user information entries of the served MCData group information entry; and b) the MCData ID of the MCData user information entry is equal to the handled MCData ID; as the served MCData user information entry; 3) shall generate an application/pidf+xml MIME body indicating per-group affiliation information according to subclause 8.4.1 and the served list of the served MCData user information entry of the MCData group information entry with following clarifications: a) the MCData server shall include the "expires" attribute in the <affiliation> element; and b) if this procedures is invoked by procedure in subclause 8.3.3.3 where the handled p-id was identified, the MCData server shall set the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request to the handled p-id value; and 4) send a SIP NOTIFY request according to 3GPP TS 24.229 [5], and IETF RFC 6665 [36] for the subscription created in subclause 8.3.3.4. In the SIP NOTIFY request, the MCData server shall include the generated application/pidf+xml MIME body indicating per-group affiliation information." [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.7.1] "To create the group's security association, a Group Master Key (GMK) and associated identifier (GMK-ID) is distributed to MCX UEs by a Group Management Server (GMS). The GMK is distributed encrypted specifically to a user and signed using an identity representing the Group Management Server. Prior to group key distribution, each MCX UE within the group shall be provisioned by the MCX Key Management Server (KMS) with time-limited key material associated with the MCX user as described in clause 5.3. The Group Management Server shall also be provisioned by the MCX KMS with key material for the GMS's identity (the GMS Server URI). The GMK is distributed from the GMS to a MCX client using the security mechanism described in clause 5.2.2, transported over the SIP bearer. For GMKs, end-point diversity is required and hence the extension in clause 5.2.3 is applied. Additional parameters may be included as defined in clause 5.2.4. The SAKKE-to-self extension may be included as defined in clause 5.2.5. Identity hiding may be supported as defined in clause 5.2.6. The receiving MCX client and any MCX Server through which the SIP INVITE is routed, may respond with a KMS Redirect Response (KRR) as described in clause 5.2.8. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 56 GMKs may be managed individually per Group ID or the same GMK may be assigned to multiple MC Group IDs (using the MIKEY general extension payload defined in Clause E.6). This means that each specified MC Group ID in the MIKEY general extension payload shall use this GMK for group communications. Assigned MC Group IDs may include any combination of MCPTT Group IDs, MCData Group IDs or MCVideo Group IDs. Assigning the same GMK to multiple Group IDs does not prevent individual key management at a later time or vice versa. An MC client may have multiple active GMKs associated with a Group ID. When this occurs, the MC client shall use the active GMK with the most recent Activation Time (as defined in Clause E.6.4) when encrypting group media. The initiating entity shall be the initiating GMS. The initiating entity URI shall be the URI of the GMS (e.g. sip: gp.manager@mcptt.example.org). The receiving entity shall be the terminating MCX user. The receiving entity URI shall be the MCX service ID of the terminating user. The distributed key, K, shall be the GMK, the key identifier K-ID shall be the GMK-ID and the end-point-specific key identifier, UK-ID shall be the GUK-ID. Clause E.3 provides MIKEY message structure for GMK distribution." [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.7.3] "In some situations, the membership of a group may be modified whereby an MC user may be added to or removed from an MCX group. Users are alerted to these changes by a user profile update from the CMS for which they are subscribed. The updated user configuration profile indicates the group ID to which the group membership change is associated. When users are added to a new or existing group they may be implicitly affiliated to that group in which case the user is automatically subscribed to group configuration updates from the GMS. The user shall be authorised for group management services to the GMS before the GMS provides the associated group management records and the GMK. Once the user is authorised, the GMS sends the group management record as well as the GMK to the UE. The user may join in on the group communication immediately after receiving the group update and GMK. When the user configuration record indicates the user has been added to a new or existing group but is required to explicitly affiliate to the group, the user shall be authorised for group management services to the GMS followed by a subscription to group updates from the GMS. The user shall be authorised for group management services and the subscription shall be validated before the GMS provides group management records and the GMK. Once the user is authorised and the subscription processed by the GMS, the GMS sends the group management record and the GMK to the UE. The user may then join in on the group communication immediately after receiving the group update and GMK. When a user is removed from a group, the UE receives a user profile update from the CMS indicating the user is no longer a member of the specified group ID(s). Upon receiving the user profile update, ending of any group communication(s) associated with that group, and if the GMK associated with the group ID is not associated with another group that the user remains a member, the UE shall immediately and securely delete the GMK associated with that group ID. If the group ID is associated to more than one service (i.e. MCPTT, MCData and/or MCVideo) then upon the ending of any group communication(s) associated with that group ID, and if the GMKs associated with that group ID is not associated with another group that the user remains a member, the GMKs associated with that group ID shall be immediately and securely deleted. When a user is removed from the group, the Group Management Server may choose to update the GMK associated with the group ID (depending on the security profile of the group)." [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.8.1] "The 'key download' procedure is used to send keys from the MCX server to the MC client. It is used to distribute Multicast Signalling Keys (MuSiKs) to the MC clients, and it is used to update both the CSKs and MuSiKs. Within the 'key download' procedure, keys (CSK or MuSiKs) are encrypted specifically to the MC user and signed using an identity representing the MC Server. Prior to group key distribution, each MC client shall be provisioned by the KMS with time-limited key material associated with the MC User as described clause 5.3. The MC Server shall also be provisioned by the MC KMS with key material for an identity which is authorised to act as an MCX Server. The key (CSK or MuSiK) is distributed from the MCX Server to a MC client using the security mechanism described in clause 5.2.2, transported over the SIP bearer. End-point diversity is not required as end-points do not encrypt data, hence the extension in clause 5.2.3 is not applied. Additional parameters may be included as defined in clause 5.2.4. The SAKKE-to-self extension may be included as defined in clause 5.2.5. Identity hiding may be supported as defined in clause 5.2.6. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 57 The initiating entity shall be the initiating MCX Server and the receiving entity shall be the terminating MC user. The initiating entity URI shall be the FQDN of the MCX Server (e.g. MDSI of the MC Domain) and the receiving entity URI shall be the MC Service ID of the terminating user. The distributed key, K, shall be the CSK or MuSiK and the key identifier K-ID shall be the CSK-ID or MuSiK-ID (respectively). As a result of this 'key download' mechanism, the MC clients receive a new signalling key, CSK or MuSiK, identified by the 4 most significant bits of the key ID. The MCData Service server may use the Key Download procedure to indicate or modify the algorithm used to protect the MCData signalling fields (i.e. MCData signaling parameters, Data signaling payload and End to end security parameters) by including a 'signalling algorithm' parameter. The 'signalling algorithm' parameter is described in clause 8.5.4.1. The available algorithms shall be as defined in clause 8.5.4.2." [ETSI TS 133 180 [12] (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 [12] (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." |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) - For the underlying "transport bearer" over which the SS-UE1 (MCData client) and the MCData 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 [10] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCData operation in the MCData configuration document). IUT: - IUT (MCData Server) - The IUT (MCData 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 (MCData Server) also consists of all sub- systems of the MCData Server, including the Media Distribution Function, the MCData User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Floor Control Server. - The IUT (MCData Server) is the acting Group Management Server. Preamble: - The IUT (MCData Server) is connected to PLMN1 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 58 - The IUT (MCData Server) is connected to the SS-UE1 (MCData client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4, where term "MCPTT" is replaced with "MCData". - The SS-UE1 (MCData client) performs the Procedure for MCData Authorization, Configuration and Key Generation as specified in clause 5.1. - The SS-UE1 (MCData client) is member of group A. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.3.2 Test procedure sequence | Table 5.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server correctly perform procedure 'MCX Server Terminated Group Creation' as described in Annex A, Table A.2.4.3-1 to create group B? - - 1 P 2 Check: Does the MCData Server correctly perform procedure 'MCX Server Terminated Temporary Group Creation' as described in Annex A, Table A.2.5.3-1 to create temporary group T? - - 2 P 3 Check: Does the MCData Server correctly perform procedure 'MCX Server Originated notifications regarding temporary group creation or tear down' as described in Annex A, Table A.2.3.3-1 to update the group document of group A and retrieve the GMK for the temporary group T - - 2 P 4 Check: Does the MCData Server correctly perform procedure 'MCX Server Terminated Temporary Group Tear Down ' as described in Annex A, Table A.2.6.3-1 to delete temporary group T? - - 3 P 5 Check: Does the MCData Server correctly perform procedure 'MCX Server Originated notifications regarding temporary group creation or tear down' as described in Annex A, Table A.2.3.3-1 to update the group document and the GKTP document of group A? - - 3 P |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.2.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications: • Subclauses referring to messages from UE relate to SS-UE1 (MCX Client). 5.3 MCDATA Server - MCDATA Client / Configuration / Group Affiliation / Implicit Affiliation / Remote change / De- affiliation / Home MCDATA system |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.1 Test Purpose (TP) | (1) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is authorized to affiliate with the specified group} ensure that { when { the SS-UE1 (MCData client ) requests for own affiliation status and to subscribe to affiliation status changes for the MCData User with SIP SUBSCRIBE message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 59 (2) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is authorized to affiliate with the specified group } ensure that { when { the SS-UE1 (MCData client) requests to de-affiliate user A from an MCData group with SIP PUBLISH } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } (3) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is authorized to affiliate with the specified group } ensure that { when { the SS-UE1 (MCData client) requests to affiliate user A to an MCData group with SIP PUBLISH message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } (4) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is authorized to affiliate with the specified group } ensure that { when { the SS-UE2 (MCData client) requests to de-affiliate user B from an MCData group with SIP PUBLISH message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } (5) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is allowed to make affiliation changes for another user with the specified group } ensure that { when { the SS-UE1 (MCData client ) requests to affiliate status changes of targeted user with SIP SUBSCRIBE message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (6) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is allowed to make affiliation changes for another user with the specified group } ensure that { when { the SS-UE1 (MCData client) requests to affiliate targeted user B to an MCData group via mandatory mode with SIP PUBLISH message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } (7) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is allowed to make affiliation changes for another user with the specified group } ensure that { when { the SS-UE1 (MCData client) requests to de-affiliate targeted user from an MCData group via mandatory mode with SIP PUBLISH message } then { IUT (MCData Server) responds to the SS-UE (MCData client) with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 60 (8) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is allowed to make affiliation changes for another user with the specified group } ensure that { when { SS-UE1 (MCData Client) requests that a target user B be affiliated to an MCData group via negotiated mode by sending a SIP MESSAGE message } then { IUT (MCData Server) responds with a SIP 200 (OK) } } (9) with { MCData Client already affiliated to the MCData group } ensure that { when { the SS-UE1 (MCData Client) requests to affiliate targeted user to a group via negotiated mode } then { IUT (MCData Server) informs user B about a remote request by sending a SIP MESSAGE message to the SS-UE2 (MCData Client) } } (10) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is authorized to affiliate with the specified group } ensure that { when { the SS-UE2 (MCData client) requests to affiliate user B to an MCData group with SIP PUBLISH message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends SIP NOTIFY message to inform the change progress status and sends SIP NOTIFY message to inform the final status } } (11) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is allowed to make affiliation changes for another user with the specified group } ensure that { when { SS-UE1 (MCData Client) requests that a target user B be de-affiliated to an MCData group via negotiated mode by sending a SIP MESSAGE message } then { IUT (MCData Server) responds with a SIP 200 (OK) } } (12) with { MCData Client already de-affiliated from the MCData group } ensure that { when { the SS-UE1 (MCData Client) requests to de-affiliate targeted user to a group via negotiated mode } then { IUT (MCData Server) informs user B about a remote request by sending a SIP MESSAGE message to the SS-UE2 (MCData Client) } } (13) with { IUT (MCData Server) having received the provisioned MCData Client's group information or a pointer to the group information, indicating that the MCData Client is authorized to affiliate with the specified group} ensure that { when { the SS-UE1 (MCData client ) requests to de-subscribe from affiliation status changes for the MCData User with SIP SUBSCRIBE message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 61 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 484 [8] (3GPP TS 24.484) clauses 4.3.1, 4.3.4, 4.4, 6.3.13.2.3, 6.3.3.2.3, 6.3.3.2.1, 10.2.1, 10.2.1A, 10.3.1, 10.3.1A, 10.4.1, 6.2.3, ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 6.3.5, 8.3.2.3, 8.3.2.4, 8.3.2.5, 8.3.2.8, 8.2.3.9, 8.2.3.10, 8.3.2.11, 8.3.2.12, 8.3.2.13, 8.3.2.14, 8.3.2.15, 8.3.3.3, 8.3.3.4, 8.3.3.5, 8.3.3.7. Unless otherwise stated these are Rel-14 requirements. [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 4.3.1] "The MCS server obtains the appropriate MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server. The MCS server obtains the MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server. The MCS server subscribes to the MCS service configuration document for each mission critical organisation that is provisioned that is supported by the MCS server using the procedure specified in subclause 6.3.13.2.3. How the MCS server is provisioned with the identities of the mission critical organisations is out of scope of the present document. If the MCS service configuration document has been updated since the current version stored at the MCS server, then the MCS server will receive a SIP NOTIFY request containing an HTTPS URI of the MCS service configuration document. Retrieval by the MCS server, using the notified HTTPS URI, of the MCS service configuration document is performed as specified in subclause 6.3.3.2.3. NOTE: The MCS server can be notified of changes to the MCS service management configuration document at any time while operating the MCS." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 4.3.4] "The format of the MCData service configuration document downloaded to the MCData server is defined in subclause 10.4." [ETSI TS 124 484 [8] (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 MCS UE initial configuration document received from an MCS administrator into an appropriate format for configuration of the MCS UE initial configuration MO. If the MCS UE initial configuration MO contains a <default-user-profile> element that identifies an MCS user profile configuration document, the configuration management server needs to convert the identified MCS user profile configuration document received from an MCS administrator into an appropriate format for configuration of the MCS user profile configuration MO. Once an MCS User Profile configuration document has been created or updated by the MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to store MCS user profile configuration document as the user profile in the MC service user database. In order to download the MCS user profile configuration document to an MCS UE or to support an MCS UE updating the MCS user profile configuration document, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to obtain the MCS user profile from the MC service user database. In order to be notified of changes to an MCS user profile configuration document(s) that have been subscribed to by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to be notified of changes to the MCS user profile stored in the MC service user database. In order to delete the MCS user profile when requested by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to delete the MCS user profile from the MC service user database. NOTE: The configuration management server and group management server functionality for offline configuration is out of scope of the present document." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 62 [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.13.2.3] "In order to subscribe to an MCS service configuration document, an MCS server shall send an initial SIP SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [22] and IETF RFC 5875 [11]. In the initial SIP SUBSCRIBE request, MCS server: a) shall set the Request URI to a SIP URI containing: 1) the base URI being equal to the public service identity of the CMS configured in the MCS server; and 2) the "auid" parameter set to the application usage identifying th MCS service configuration document; b) shall include a P-Asserted-Identity header field containing the public service identity of the MCS server; c) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [22]), in a P-Asserted-Service header field according to IETF RFC 6050 [23]; and d) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field. Upon receiving a SIP NOTIFY request associated with a subscription created as result of the sent initial SIP SUBSCRIBE request, the MCS server shall handle the SIP NOTIFY request according to IETF RFC 5875 [11]. In order to re-subscribe to notification of changes to an MCS service configuration document, an MCS server shall send a SIP re-SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [22] and IETF RFC 5875 [11]. In the SIP re-SUBSCRIBE request, MCS server: a) shall set the Request URI to a SIP URI containing: 1) the base URI being equal to the public service identity of the CMS configured in the MCS server; and 2) the "auid" parameter set to the application usage identifying an MCS service configuration document; and b) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.3.2.3] "In order to retrieve a configuration management document via the CSC-5 reference point, an MCS Server shall perform the procedures in subclause 6.3.3.2.1 specified for GC. The MCS server shall set the Request-URI of the HTTP GET request to identify the XML document based on configuration and include the "auid" as per the appropriate application usage." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.3.2.1] "In order to retrieve a configuration management document, a GC shall send an HTTP GET request with the Request URI that references the document to be updated to the network according to procedures specified in IETF RFC 4825 [14] "Retrieve a Document"." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.2.1] "The MCData UE configuration document is specified in this subclause. The MCData UE configuration document content is based on requirements of Annex A.2 of 3GPP TS 23.282 [24], in accordance with OMA OMA-TS- XDM_Core-V2_1-20120403-A [2]. The usage of an MCData UE configuration document in the MCData service is described in 3GPP TS 24.282 [25] and 3GPP TS 24.582 [26]. The schema definition is provided in subclause 10.2.2.3. An MCData UE configuration document may apply to all MCData UEs of a mission critical organization or apply to specific MCData UEs identified in the <mcdata-UE-id> element. If there is no <mcdata-UE-id> element in the MCData UE configuration document, then by default the MCData UE configuration document applies to all MCData UEs of the mission critical organization that are not specifically identified in the <mcdata-UE-id> element of another MCData UE configuration document of the mission critical organization. Each MCData UE of a mission critical organization is configured with an MCData UE configuration document that is identified by the instance ID of the MCData UE. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 63 …. A MCData UE configuration document corresponding to a specific MCData UE the MCData user has used to authenticate and is authorised to use the MCData service with is placed in the user directory of the MCData user. The MCData UE configuration document acts as a template for the CMS to generate UE configuration documents that are downloaded to specific MCData UEs. The MCData UE configuration document that acts as a template is referred to as a "master MCData UE configuration document". The master MCData UE configuration document is stored in the users tree of that MCData system administrator. The master MCData UE configuration document does not directly apply to a specific MCData UE, but instead acts as template that the CMS uses to populate the MCData UE configuration documents of MCData UEs identified by elements of the <MCData-UE-id> element. For MCData UE configuration documents that correspond to a specific MCData UE, the name of the MCData UE configuration document is created from a value defined by the corresponding element that identifies the MCData UE within the <MCData-UE-id> element. For a master MCData UE configuration documents that does not contain a <MCData-UE- id> element, the name of the MCData UE configuration document stored in the user directory is "DEFAULT-MCData- UE.xml"." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.2.1A] "The MCData UE configuration document is accessed using the same XCAP URI, regardless of whether the MCData UE has a specific MCData UE configuration document configured or the master MCData UE configuration document applies. The CMS shall generate the UE's MCData UE configuration document from the master MCData UE configuration document if the MCData administrator did not provision a specific MCData UE configuration document. In this generated document, the <MCData-UE-id> element shall be set to the MCData client's UE ID. The UE's MCData UE configuration document shall always be stored with the filename corresponding to the UE's MCData UE ID under the user's directory of the users tree. The XCAP URI used by the MCData client to access the UE's MCData UE configuration document shall be: - CMSXCAPROOTURI/org.3gpp.mcdata.ue-config/users/sip:MCDATAID/MCSUEID." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.3.1] "The MCData user profile configuration document is specified in this subclause. The MCData user profile configuration document content is based on requirements of Annex A.3 of 3GPP TS 23.282 [24], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCData user profile in the MCData service is described in 3GPP TS 24.282 [25]. The schema definition is provided in subclause 10.3.2. MCData user profile documents are "XDM collections" in the user's directory of the users tree, in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCData ID, as the user has been already authenticated. The name of the MCData user profile document matches the value of the <ProfileName> element in the MCData user profile document." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.3.1A] "The XCAP URI used by the MCData client to access the MCData user's MCData user profile documents shall be: CMSXCAPROOTURI/org.3gpp.mcdata.user-profile/users/sip:MCDATAID/mcdata-user-profile-INDEX.xml Where INDEX is the index of the MCData user profile as defined in subclause 10.3.2.8." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.4.1] "The MCData service configuration document is specified in this subclause. The MCData service configuration document content is based on requirements of Annex A.5 of 3GPP TS 23.282 [24], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCData service configuration in the MCData service is described in 3GPP TS 24.282[25] and 3GPP TS 24.582 [26]. The schema definition is provided in subclause 10.4.2.3. Each mission critical organization is configured with an MCData service configuration document." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.2.3] "The MCS server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.482 [6]." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 64 [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 6.3.5] "The MCData server shall determine that the MCData user, with MCData User ID, is affiliated to the MCData group, with MCData Group ID, at the MCData client, with MCData client ID, if the elements, as described in subclause 8.3.3.2, exist with their expected values, as below: 1. an MCData group information entry with MCData group ID same as the MCData group ID under consideration; 2. in the MCData group information entry found in 1, an MCData user information entry with the MCData ID same as the MCData ID under consideration; 3. in the MCData user information entry found in 2, an MCData client information entry with MCData Client ID same as the MCData client ID under consideration; and 4. in the MCData user information entry found in 2, an expiration time, which has not expired." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.2.3] "Upon receiving a SIP PUBLISH request such that: 1) Request-URI of the SIP PUBLISH request contains either the public service identity identifying the originating participating MCData function serving the MCData user, or the public service identity identifying the terminating participating MCData function serving the MCData user; 2) the SIP PUBLISH request contains an application/vnd.3gpp.mcdata-info+xml MIME body containing the<mcdata-request-uri> element which identifies an MCData ID served by the MCData server; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [5]), in a P- Asserted-Service header field according to IETF RFC 6050 [7]; 4) the Event header field of the SIP PUBLISH request contains the "presence" event type; and 5) SIP PUBLISH request contains an application/pidf+xml MIME body indicating per-user affiliation information according to subclause 8.4.1; then the MCData server: 1) shall identify the served MCData ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP PUBLISH request; 2) if the Request-URI of the SIP PUBLISH request contains the public service identity identifying the originating participating MCData function serving the MCData user, shall identify the originating MCData ID from public user identity in the P-Asserted-Identity header field of the SIP PUBLISH request; 3) if the Request-URI of the SIP PUBLISH request contains the public service identity identifying the terminating participating MCData function serving the MCData user, shall identify the originating MCData ID in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP PUBLISH request; … 6) if the Expires header field of the SIP PUBLISH request has nonzero value, shall determine the candidate expiration interval to according to IETF RFC 3903 [34]; 7) if the Expires header field of the SIP PUBLISH request has zero value, shall set the candidate expiration interval to zero; 8) shall respond with SIP 200 (OK) response to the SIP PUBLISH request according to 3GPP TS 24.229 [5], IETF RFC 3903 [34]. In the SIP 200 (OK) response, the MCData server: a) shall set the Expires header field according to IETF RFC 3903 [34], to the candidate expiration time; 9) if the "entity" attribute of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request is different than the served MCData ID, shall not continue with the rest of the steps; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 65 10) shall identify the served MCData client ID in the "id" attribute of the <tuple> element of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request; 11) shall consider an MCData user information entry such that: a) the MCData user information entry is in the list of MCData user information entries described in subclause 8.3.2.2; and b) the MCData ID of the MCData user information entry is equal to the served MCData ID; as the served MCData user information entry; 12) shall consider an MCData client information entry such that: a) the MCData client information entry is in the list of MCData client information entries of the served MCData user information entry; and b) the MCData client ID of the MCData client information entry is equal to the served MCData client ID; as the served MCData client information entry; 13) shall consider a copy of the list of the MCData group information entries of the served MCData client information entry as the served list of the MCData group information entries; 14) if the candidate expiration interval is nonzero: a) shall construct the candidate list of the MCData group information entries as follows: i) for each MCData group ID which has an MCData group information entry in the served list of the MCData group information entries, such that the expiration time of the MCData group information entry has not expired yet, and which is indicated in a "group" attribute of an <affiliation> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request: A) shall copy the MCData group information entry into a new MCData group information entry of the candidate list of the MCData group information entries; B) if the affiliation status of the MCData group information entry is "deaffiliating" or "deaffiliated", shall set the affiliation status of the new MCData group information entry to the "affiliating" state and shall reset the affiliating p-id of the new MCData group information entry; and C) shall set the expiration time of the new MCData group information entry to the current time increased with the candidate expiration interval; ii) for each MCData group ID which has an MCData group information entry in the served list of the MCData group information entries, such that the expiration time of the MCData group information entry has not expired yet, and which is not indicated in any "group" attribute of the <affiliation> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request: A) shall copy the MCData group information entry into a new MCData group information entry of the candidate list of the MCData group information entries; and B) if the affiliation status of the MCData group information entry is "affiliated" or "affiliating": - shall set the affiliation status of the new MCData group information entry to the "de- affiliating" state; and - shall set the expiration time of the new MCData group information entry to the current time increased with twice the value of timer F; and iii) for each MCData group ID: A) which does not have an MCData group information entry in the served list of the MCData group information entries; or ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 66 B) which has an MCData group information entry in the served list of the MCData group information entries, such that the expiration time of the MCData group information entry has already expired; and which is indicated in a "group" element of the <affiliation> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request: A) shall add a new MCData group information entry in the candidate list of the MCData group information list for the MCData group ID; B) shall set the affiliation status of the new MCData group information entry to the "affiliating" state; C) shall set the expiration time of the new MCData group information entry to the current time increased with the candidate expiration interval; and D) shall reset the affiliating p-id of the new MCData group information entry; b) determine the candidate number of MCData group IDs as number of different MCData group IDs which have an MCData group information entry: i) in the candidate list of the MCData group information entries; or ii) in the list of the MCData group information entries of an MCData client information entry such that: A) the MCData client information entry is in the list of the MCData client information entries of the served MCData user information entry; and B) the MCData client ID of the MCData client information entry is not equal to the served MCData client ID; with the affiliation status set to the "affiliating" state or the "affiliated" state and with the expiration time which has not expired yet; and c) if the candidate number of MCData group IDs is bigger than N2 value of the served MCData ID, shall based on MCData service provider policy reduce the candidate MCData group IDs to that equal to N2; NOTE: The MCData service provider policy can determine to remove an MCData group ID based on the order it appeared in the PUBLISH request or based on the importance or priority of the MCData group or some other policy to determine which MCData groups are preferred. 15) if the candidate expiration interval is zero, constructs the candidate list of the MCData group information entries as follows: a) for each MCData group ID which has an entry in the served list of the MCData group information entries: i) shall copy the MCData group entry of the served list of the MCData group information into a new MCData group information entry of the candidate list of the MCData group information entries; ii) shall set the affiliation status of the new MCData group information entry to the "de-affiliating" state; and iii) shall set the expiration time of the new MCData group information entry to the current time increased with twice the value of timer F; 16) shall replace the list of the MCData group information entries stored in the served MCData client information entry with the candidate list of the MCData group information entries; 17) shall perform the procedures specified in subclause 8.3.2.6 for the served MCData ID and each MCData group ID: ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 67 a) which does not have an MCData group information entry in the served list of the MCData group information entries and which has an MCData group information entry in the candidate list of the MCData group information entries with the affiliation status set to the "affiliating" state; b) which has an MCData group information entry in the served list of the MCData group information entries with the expiration time already expired, and which has an MCData group information entry in the candidate list of the MCData group information entries with the affiliation status set to the "affiliating" state; c) which has an MCData group information entry in the served list of the MCData group information entries with the affiliation status set to the "deaffiliating" state or the "deaffiliated" state and with the expiration time not expired yet, and which has an MCData group information entry in the candidate list of the MCData group information entries with the affiliation status set to the "affiliating" state; or d) which has an MCData group information entry in the served list of the MCData group information entries with the affiliation status set to the "affiliated" state and with the expiration time not expired yet, and which has an MCData group information entry in the candidate list of the MCData group information entries with the affiliation status set to the "de-affiliating" state; 18) shall identify the handled p-id in the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and 19) shall perform the procedures specified in subclause 8.3.2.5 for the served MCData ID." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.2.4] "Upon receiving a SIP SUBSCRIBE request such that: 1) Request-URI of the SIP SUBSCRIBE request contains either the public service identity identifying the originating participating MCData function serving the MCData user, or the public service identity identifying the terminating participating MCData function serving the MCData user; 2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcdata-info+xml MIME body containing the<mcdata-request-uri> element which identifies an MCData ID served by the MCData server; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [5]), in a P-Asserted-Service header field according to IETF RFC 6050 [7]; and 4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; the MCData server: 1) shall identify the served MCData ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request; 2) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCData function serving the MCData user, shall identify the originating MCData ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request; 3) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the terminating participating MCData function serving the MCData user, shall identify the originating MCData ID in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request; 4) if the originating MCData ID is different than the served MCData ID and the originating MCData ID is not authorized to modify affiliation status of the served MCData ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps; and 5) shall generate a 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [5], IETF RFC 6665 [36]. For the duration of the subscription, the MCData server shall notify the subscriber about changes of the information of the served MCData ID, as described in subclause 8.3.2.5." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 68 [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.2.5] "In order to notify the subscriber about changes of the served MCData ID, the MCData server: 1) shall consider an MCData user information entry such that: a) the MCData user information entry is in the list of MCData user information entries described in subclause 8.3.2.2; and b) the MCData ID of the MCData user information entry is equal to the served MCData ID; as the served MCData user information entry; 2) shall consider the list of the MCData client information entries of the served MCData user information entry as the served list of the MCData client information entries; 3) shall generate an application/pidf+xml MIME body indicating per-user affiliation information according to subclause 8.4.1 and the served list of the MCData client information entries with the following clarifications: a) the MCData server shall not include information from an MCData group information entry with the expiration time already expired; b) the MCData server shall not include information from an MCData group information entry with the affiliation status set to the "deaffiliated" state; c) if the SIP SUBSCRIBE request creating the subscription of this notification contains an application/simple-filter+xml MIME body indicating per-client restrictions of presence event package notification information according to subclause 8.4.2, the MCData server shall restrict the application/pidf+xml MIME body according to the application/simple-filter+xml MIME body; and d) if this procedures is invoked by procedure in subclause 8.3.2.3 where the handled p-id value was identified, the MCData server shall set the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request to the handled p-id value; and 4) send a SIP NOTIFY request according to 3GPP TS 24.229 [5], and IETF RFC 6665 [36] for the subscription created in subclause 8.3.2.4. In the SIP NOTIFY request, the MCData server shall include the generated application/pidf+xml MIME body indicating per-user affiliation information." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.2.8] "Upon receiving a SIP MESSAGE request such that: 1) Request-URI of the SIP MESSAGE request contains the public service identity identifying the terminating participating MCData function serving the MCData user; 2) the SIP MESSAGE request contains an application/vnd.3gpp.mcdata-info+xml MIME body containing the<mcdata-request-uri> element and the <mcdata-calling-user-id> element; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [5]), in a P-Asserted-Service header field according to IETF RFC 6050 [7]; and 4) the SIP MESSAGE request contains an application/vnd.3gpp.mcdata-affiliation-command+xml MIME body; then the MCData server: 1) shall identify the served MCData ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request; 2) shall identify the originating MCData ID in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request; 3) if the originating MCData ID is not authorized to send an affiliation status change request in negotiated mode to the served MCData ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps; 4) shall set the Request-URI of the SIP MESSAGE request to the public user identity bound to the served MCData ID in the MCData server; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 69 5) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [8]; before forwarding the SIP MESSAGE request further." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.2.9] "Upon receiving a SIP PUBLISH request such that: 1) Request-URI of the SIP PUBLISH request contains the public service identity identifying the originating participating MCData function serving the MCData user; 2) the SIP PUBLISH request contains an application/vnd.3gpp.mcdata-info MIME body containing the<mcdata- request-uri> element which identifies an MCData ID not served by the MCData server; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [5]), in a P- Asserted-Service header field according to IETF RFC 6050 [7]; 4) the Event header field of the SIP PUBLISH request contains the "presence" event type; and 5) SIP PUBLISH request contains an application/pidf+xml MIME body indicating per-user affiliation information according to subclause 8.4.1; then the MCData server: 1) shall identify the target MCData ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata- info MIME body of the SIP PUBLISH request; 2) shall identify the originating MCData ID from public user identity in the P-Asserted-Identity header field of the SIP PUBLISH request; 3) shall generate a SIP PUBLISH request from the received SIP PUBLISH request. In the generated SIP PUBLISH request, the MCData server: a) shall set the Request-URI to the public service identity identifying the terminating participating MCData function serving the target MCData ID; b) shall include a P-Asserted-Identity header field containing the public service identity identifying the originating participating MCData function serving the MCData user; c) shall include an application/vnd.3gpp.mcdata-info+xml MIME body. In the application/vnd.3gpp.mcdata-info+xml MIME body, the MCData server: A) shall include the <mcdata-request-uri> element set to the target MCData ID; and B) shall include the <mcdata-calling-user-id> element set to the originating MCData ID; and d) shall include other signalling elements from the received SIP PUBLISH request; and 4) shall send the generated SIP PUBLISH request according to 3GPP TS 24.229 [5]. The MCData server shall forward received SIP responses to the SIP PUBLISH request." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.2.10] "Upon receiving a SIP SUBSCRIBE request such that: 1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCData function serving the MCData user; 2) the SIP SUBCRIBE request contains an application/vnd.3gpp.mcdata-info MIME body containing the<mcdata-request-uri> element which identifies an MCData ID not served by MCData server; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [5]), in a P-Asserted-Service header field according to IETF RFC 6050 [7]; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 70 4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; then the MCData server: 1) shall identify the target MCData ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata- info MIME body of the SIP SUBSCRIBE request; 2) shall identify the originating MCData ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request; 3) shall generate a SIP SUBSCRIBE request from the received SIP SUBSCRIBE request. In the generated SIP SUBSCRIBE request, the MCData server: a) shall set the Request-URI to the public service identity identifying the terminating participating MCData function serving the target MCData ID; b) shall include a P-Asserted-Identity header field containing the public service identity identifying the originating participating MCData function serving the MCData user; c) shall include an application/vnd.3gpp.mcdata-info+xml MIME body. In the application/vnd.3gpp.mcdata-info+xml MIME body, the MCData server: A) shall include the <mcdata-request-uri> element set to the target MCData ID; and B) shall include the <mcdata-calling-user-id> element set to the originating MCData ID; and d) shall include other signalling elements from the received SIP SUBSCRIBE request; and 4) shall send the generated SIP SUBSCRIBE request according to 3GPP TS 24.229 [5]. The MCData server shall forward any received SIP responses to the SIP SUBSCRIBE request, any received SIP NOTIFY request and any received SIP responses to the SIP NOTIFY request." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.2.11] "This subclause is referenced from other procedures. If the participating MCData function needs to determine the affiliation status of an MCData user to an MCData group, the participating function: 1) shall find the user information entry in the list of MCData user information entries described in subclause 8.3.2.2 such that the MCData ID of the MCData user information entry is equal to the MCData ID of the originator of the received SIP request; a) if the applicable MCData group information entry cannot be found, then the participating MCData function shall determine that the MCData user is not affiliated to the MCData group at the MCData client and the skip the rest of the steps; 2) shall find the MCData client information entry in the list of MCData client information entries of MCData user information entry found in step 1) in which the MCData client id matches the value of the <mcdata- client-id> element contained in the application/vnd.3gpp.mcdata-info+xml MIME body in the received SIP request; a) if the applicable MCData client information entry cannot be found, then the participating MCData function shall determine that the MCData user is not affiliated to the MCData group at the MCData client and the skip the rest of the steps; 3) shall find the MCData group information entry in the list of MCData group information entries of MCData client information entry found in step 2 such that the MCData group identity matches the value of the identity of the targeted MCData group; a) if the applicable MCData group information entry was found in step 3) and the affiliation status of the MCData group information entry is "affiliating" or "affiliated", shall determine that the MCData user at the MCData client to be affiliated to the targeted MCData group and skip the rest of the steps; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 71 b) if the applicable MCData group information entry was found in step 3) and the affiliation status of the MCData group information entry is "deaffiliating" or "deaffiliated", shall determine that the MCData user at the MCData client to not be affiliated to the targeted MCData group and skip the rest of the steps; or c) if the applicable MCData group information entry was not found in step 3), shall determine that the MCData user at the MCData client is not affiliated to the targeted MCData group." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.2.12] "This subclause is referenced from other procedures. Upon receiving a SIP request that requires implicit affiliation of the sending MCData client to an MCData group, the participating MCData function: 1) shall determine the served MCData client ID from the <mcdata-client-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the received SIP request; 2) shall determine the MCData group ID from the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the received SIP request; 3) shall determine the served MCData ID by using the public user identity in the P-Asserted-Identity header field of the SIP request; NOTE 1: The MCData ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in subclause 7.3. 4) shall consider an MCData user information entry such that: a) the MCData user information entry is in the list of MCData user information entries described in subclause 8.3.2.2; and b) the MCData ID of the MCData user information entry is equal to the served MCData ID; as the served MCData user information entry; 5) shall consider an MCData client information entry such that: a) the MCData client information entry is in the list of MCData client information entries of the served MCData user information entry; and b) the MCData client ID of the MCData client information entry is equal to the served MCData client ID; as the served MCData client information entry; 6) shall consider a copy of the list of the MCData group information entries of the served MCData client information entry as the served list of the MCData group information entries; 7) shall construct the candidate list of the MCData group information entries as follows: a) for each MCData group ID which has an MCData group information entry in the served list of the MCData group information entries shall copy the MCData group information entry into a new MCData group information entry of the candidate list of the MCData group information entries; and b) if the determined MCData group ID does not have an MCData group information entry in the served list of the MCData group information entries or has an MCData group information entry in the served list of the MCData group information entries, such that the expiration time of the MCData group information entry has already expired: i) shall add a new MCData group information entry in the candidate list of the MCData group information list for the determined MCData group ID; ii) shall set the affiliation status of the new MCData group information entry to the "affiliating" state; and iii) shall set the expiration time of the new MCData group information entry to the current time increased with the candidate expiration interval; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 72 8) determine the candidate number of MCData group IDs as the number of different MCData group IDs which have an MCData group information entry: a) in the candidate list of the MCData group information entries; or b) in the list of the MCData group information entries of an MCData client information entry such that: i) the MCData client information entry is in the list of the MCData client information entries of the served MCData user information entry; and ii) the MCData client ID of the MCData client information entry is not equal to the served MCData client ID; with the affiliation status set to the "affiliating" state or the "affiliated" state and with the expiration time which has not expired yet; and 9) if the candidate number of MCData group IDs is bigger than the N2 value of the served MCData ID, shall based on MCData service provider policy reduce the candidate MCData group IDs to that equal to N2; 10) if the determined MCData group ID cannot be added to the the candidate list of the MCData group information entries due to exceeding the MCData user's N2 limit, shall discard the candidate list of the MCData group information entries and skip the remaining steps of the current procedure; and 11) shall replace the list of the MCData group information entries stored in the served MCData client information entry with the candidate list of the MCData group information entries." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.2.13] "This subclause is referenced from other procedures. If the participating MCData function has received a SIP 2xx response from the controlling MCData function to a SIP request that had triggered performing the procedures of subclause 8.3.2.12, the participating MCData function: 1) shall set the affiliation status of the MCData group information entry added to the candidate list of the MCData group information entries by the procedures of subclause 8.3.2.12 to "affiliated"; and 2) shall perform the procedures specified in subclause 8.3.2.5 for the served MCData ID." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.2.14] "This subclause is referenced from other procedures. If the participating MCData function determines that a received SIP request that had triggered performing the procedures of subclause 8.3.2.12 needs to be rejected or if the participating MCData function receives a SIP 4xx, 5xx or 6xx response from the controlling MCData function for the received SIP request, the participating MCData function: 1) shall remove the MCData group ID entry added by the procedures of subclause 8.3.2.12 such that: a) the MCData group information entry has the MCData group ID set to the MCData group ID of the MCData group targeted by the received SIP request; b) the MCData group information entry is in the list of the MCData group information entries of an MCData client information entry containing the MCData client ID included in the received SIP request; and c) the MCData client information entry is in the list of the MCData client information entries of the MCData user information entry containing the MCData ID of the sender of the received SIP request." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.2.15] "This subclause is referenced from other procedures. If the participating MCData function has successfully performed service authorization for the MCData ID identified in the service authorisation procedure as described in 3GPP TS 33.179 [56], the participating MCData function: 1) shall identify the MCData ID included in the SIP request received for service authorisation procedure as the served MCData ID; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 73 2) shall identify the MCData client ID from the <mcdata-client-id> element contained in the application/vnd.3gpp.mcdata-info+xml MIME body included in the SIP request received for service authorisation as the served MCData client ID; 3) shall download the MCData user profile from the MCData user database as defined in 3GPP TS 29.283 [37] if not already stored at the participating MCData function; 4) if no <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCData user profile document (see the MCData user profile document in 3GPP TS 24.484 [12]) for the served MCData ID or the <ImplicitAffiliations> element contains no <entry> elements containing an MCData group ID, shall skip the remaining steps; 5) shall consider an MCData user information entry such that: a) the MCData user information entry is in the list of MCData user information entries described in subclause 8.3.2.2; and b) the MCData ID of the MCData user information entry is equal to the served MCData ID; as the served MCData user information entry; 6) shall consider an MCData client information entry such that: a) the MCData client information entry is in the list of MCData client information entries of the served MCData user information entry; and b) the MCData client ID of the MCData client information entry is equal to the served MCData client ID; as the served MCData client information entry; 7) shall consider a copy of the list of the MCData group information entries of the served MCData client information entry as the served list of the MCData group information entries; 8) shall construct the candidate list of the MCData group information entries as follows: a) for each MCData group ID which has an MCData group information entry in the served list of the MCData group information entries shall copy the MCData group information entry into a new MCData group information entry of the candidate list of the MCData group information entries; b) for each MCData group ID contained in an <entry> element of the <ImplicitAffiliations> element in the <OnNetwork> element of the MCData user profile document (see the MCData user profile document in 3GPP TS 24.484 [12]) for the served MCData ID that does not have an MCData group information entry in the served list of the MCData group information entries or has an MCData group information entry in the served list of the MCData group information entries such that the expiration time of the MCData group information entry has already expired: i) shall add a new MCData group information entry in the candidate list of the MCData group information list for the MCData group ID; ii) shall set the affiliation status of the new MCData group information entry to the "affiliating" state; and iii) shall set the expiration time of the new MCData group information entry to the current time increased with the candidate expiration interval; c) if in step b) above, no new MCData group information entries were added to the candidate list of the MCData group information list for the MCData group ID: i) shall discard the candidate list; and ii) shall skip the remaining steps; 9) determine the candidate number of MCData group IDs as the number of different MCData group IDs which have an MCData group information entry: a) in the candidate list of the MCData group information entries; or ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 74 b) in the list of the MCData group information entries of an MCData client information entry such that: i) the MCData client information entry is in the list of the MCData client information entries of the served MCData user information entry; and ii) the MCData client ID of the MCData client information entry is not equal to the served MCData client ID; with the affiliation status set to the "affiliating" state or the "affiliated" state and with the expiration time which has not expired yet; and c) if the candidate number of MCData group IDs is bigger than the N2 value of the served MCData ID, shall based on MCData service provider policy reduce the candidate MCData group IDs to that equal to N2; 10) shall replace the list of the MCData group information entries stored in the served MCData client information entry with the candidate list of the MCData group information entries; and 11) for each MCData group ID contained in an <entry> element of the <ImplicitAffiliations> element in the <OnNetwork> element of the MCData user profile document (see the MCData user profile document in 3GPP TS 24.484 [12]) for the served MCData ID and which has an MCData group information entry in the candidate list of the MCData group information entries with an affiliation status of "affiliating", shall perform the procedures specified in subclause 8.3.2.6 for the served MCData ID and each MCData group ID. NOTE 2: To learn of the MCData groups successfully affiliated to, the MCData client can subscribe to that information by the procedures specified in subclause 8.2.3." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.3.3] "Upon receiving a SIP PUBLISH request such that: 1) Request-URI of the SIP PUBLISH request contains the public service identity of the controlling MCData function associated with the served MCData group; 2) the SIP PUBLISH request contains an application/vnd.3gpp.mcdata-info+xml MIME body containing the <mcdata-request-uri> element and the <mcdata-calling-user-id> element; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [5]), in a P-Asserted-Service header field according to IETF RFC 6050 [7]; 4) the Event header field of the SIP PUBLISH request contains the "presence" event type; and 5) SIP PUBLISH request contains an application/pidf+xml MIME body indicating per-group affiliation information constructed according to subclause 8.4.1; then the MCData server: 1) shall identify the served MCData group ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP PUBLISH request; 2) shall identify the handled MCData ID in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP PUBLISH request; … 6) shall respond with SIP 200 (OK) response to the SIP PUBLISH request according to 3GPP TS 24.229 [5], IETF RFC 3903 [34]. In the SIP 200 (OK) response, the MCData server: a) shall set the Expires header field according to IETF RFC 3903 [34], to the selected expiration time; 7) if the "entity" attribute of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request is different than the served MCData group ID, shall not continue with the rest of the steps; 8) if the handled MCData ID is different from the MCData ID in the "id" attribute of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request, shall not continue with the rest of the steps; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 75 9) shall consider an MCData group information entry such that: a) the MCData group information entry is in the list of MCData group information entries described in subclause 8.3.3.2; and b) the MCData group ID of the MCData group information entry is equal to the served MCData group ID; as the served MCData group information entry; 10) if the selected expiration time is zero: a) shall remove the MCData user information entry such that: i) the MCData user information entry is in the list of the MCData user information entries of the served MCData group information entry; and ii) the MCData user information entry has the MCData ID set to the served MCData ID; 11) if the selected expiration time is not zero: a) shall consider an MCData user information entry such that: i) the MCData user information entry is in the list of the MCData user information entries of the served MCData group information entry; and ii) the MCData ID of the MCData user information entry is equal to the handled MCData ID; as the served MCData user information entry; b) if the MCData user information entry does not exist: i) shall insert an MCData user information entry with the MCData ID set to the handled MCData ID into the list of the MCData user information entries of the served MCData group information entry; and ii) shall consider the inserted MCData user information entry as the served MCData user information entry; and c) shall set the following information in the served MCData user information entry: i) set the MCData client ID list according to the "client" attributes of the <affiliation> elements of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and ii) set the expiration time according to the selected expiration time; 12) shall identify the handled p-id in the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and 13) shall perform the procedures specified in subclause 8.3.3.5 for the served MCData group ID." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.3.4] "Upon receiving a SIP SUBSCRIBE request such that: 1) Request-URI of the SIP SUBSCRIBE request contains the public service identity of the controlling MCData function associated with the served MCData group; 2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcdata-info+xml MIME body containing the<mcdata-request-uri> element and the <mcdata-calling-user-id> element; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [5]), in a P- Asserted-Service header field according to IETF RFC 6050 [7]; 4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 76 5) the SIP SUBSCRIBE request contains an application/simple-filter+xml MIME body indicating per-user restrictions of presence event package notification information according to subclause 8.4.2 indicating the same MCData ID as in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request; then the MCData server: 1) shall identify the served MCData group ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request; 2) shall identify the handled MCData ID in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request; … 6) shall generate a SIP 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [5], IETF RFC 6665 [36]. For the duration of the subscription, the MCData server shall notify subscriber about changes of the information of the served MCData ID, as described in subclause 8.3.3.5." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.3.5] "In order to notify the subscriber identified by the handled MCData ID about changes of the affiliation status of the served MCData group ID, the MCData server: 1) shall consider an MCData group information entry such that: a) the MCData group information entry is in the list of MCData group information entries described in subclause 8.3.3.2; and b) the MCData group ID of the MCData group information entry is equal to the served MCData group ID; 2) shall consider an MCData user information entry such: a) the MCData user information entry is in the list of the MCData user information entries of the served MCData group information entry; and b) the MCData ID of the MCData user information entry is equal to the handled MCData ID; as the served MCData user information entry; 3) shall generate an application/pidf+xml MIME body indicating per-group affiliation information according to subclause 8.4.1 and the served list of the served MCData user information entry of the MCData group information entry with following clarifications: a) the MCData server shall include the "expires" attribute in the <affiliation> element; and b) if this procedures is invoked by procedure in subclause 8.3.3.3 where the handled p-id was identified, the MCData server shall set the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request to the handled p-id value; and 4) send a SIP NOTIFY request according to 3GPP TS 24.229 [5], and IETF RFC 6665 [36] for the subscription created in subclause 8.3.3.4. In the SIP NOTIFY request, the MCData server shall include the generated application/pidf+xml MIME body indicating per-group affiliation information." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.3.7] "This subclause is referenced from other procedures. Upon receiving a SIP request for an MCData group that the MCData user is not currently affiliated to and that requires the controlling MCData function to perform an implicit affiliation to, the controlling MCData function: 1) shall identify the served MCData group ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP request; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 77 2) shall identify the handled MCData ID in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP request; 3) shall consider an MCData group information entry such that: a) the MCData group information entry is in the list of MCData group information entries described in subclause 8.3.3.2; and b) the MCData group ID of the MCData group information entry is equal to the served MCData group ID; as the served MCData group information entry; 4) shall consider an MCData user information entry such that: a) the MCData user information entry is in the list of the MCData user information entries of the served MCData group information entry; and b) the MCData ID of the MCData user information entry is equal to the handled MCData ID; as the served MCData user information entry; c) if the MCData user information entry does not exist: i) shall insert an MCData user information entry with the MCData ID set to the handled MCData ID into the list of the MCData user information entries of the served MCData group information entry; and ii) shall consider the inserted MCData user information entry as the served MCData user information entry; and d) shall make the following modifications in the served MCData user information entry: i) add the MCData client ID derived from the received SIP request to the MCData client ID list if not already present; and ii) set the expiration time as determined by local policy; 5) shall perform the procedures specified in subclause 8.3.3.5 for the served MCData group ID." |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client) - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData client) and the MCData 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 [10] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCData operation in the MCData configuration document). IUT: - IUT (MCData Server) - The IUT (MCData 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 (MCData Server) also consists of all sub- systems of the MCData Server, including the Media Distribution Function, the MCData User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Floor Control Server. - The IUT (MCData Server) is the acting Participating Server and Controlling Server. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 78 Preamble: - The IUT (MCData Server) is connected to PLMN1 - The IUT (MCData Server) is connected to the SS-UE1 (MCData client) and the SS-UE2 (MCData client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4, where term "MCPTT" is replaced with "MCData". - The SS-UE1 (MCData client) and the SS-UE2 (MCData client) perform the Procedure for MCData Authorization, Configuration and Key Generation as specified in clause 5.1. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.3.2 Test procedure sequence | Table 5.3.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation Status Determination and Subscription' as described in Annex A, Table A.4.11.3-1 to subscribe the SS-UE1 (MCData client) to own affiliation status changes for user A? (Note) - - 1 P 2 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation status change' as described in Annex A, Table A.4.12.3-1 to de-affiliate user A from group A using the SS-UE1 (MCData client)? - - 2 P 3 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation status change' as described in Annex A, Table A.4.12.3-1 to affiliate user A to group A using the SS-UE1 (MCData client)? - - 3 P 4 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation Status Determination and Subscription' as described in Annex A, Table A.4.11.3-1 to subscribe the SS-UE2 (MCData client) to own affiliation status changes for user B? (Note) - - 1 P 5 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation status change' as described in Annex A, Table A.4.12.3-1 to de-affiliate user B from group A using the SS-UE2 (MCData client)? - - 4 P 6 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation Status Determination and Subscription' as described in Annex A, Table A.4.11.3-1 to subscribe the SS-UE1 (MCData client) to affiliation status changes of targeted user B? - - 5 P 7 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation status change' as described in Annex A, Table A.4.12.3-1 to request from the SS-UE1 (MCData Client) to affiliate targeted user B to group A (mandatory mode)? - - 6 P 8 Check: Does the MCData Server correctly perform steps 3-6 of procedure 'MCData Group Affiliation status change' as described in Annex A, Table A.4.12.3-1 to inform user B in the SS-UE2 (MCData client) that is being remotely affiliated to group A? - - 6 P 9 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation status change' as described in Annex A, Table A.4.12.3-1 to request from the SS-UE1 (MCData Client) to de-affiliate targeted user B from group A (mandatory mode)? - - 7 P ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 79 St Procedure Message Sequence TP Verdict U - S Message 10 Check: Does the MCData Server correctly perform steps 3-6 of procedure 'MCData Group Affiliation status change' as described in Annex A, Table A.4.12.3-1 to inform user B in the SS-UE2 (MCData Client) that is being remotely de-affiliated from group A? - - 7 P 11 Check: Does the MCData Server correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to request from the SS-UE1 (MCData Client) to affiliate targeted user B to group A via negotiated mode? - - 8 P 12 Check: Does the MCData Server correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to inform user B in the SS-UE2 (MCData Client) about a remote request to affiliate to group A via negotiated mode? - - 9 P 13 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation status change' as described in Annex A, Table A.4.12.3-1 to affiliate user B to group A using the SS-UE2 (MCData client)? - - 10 P 14 Check: Does the MCData Server correctly perform steps 3-6 of procedure 'MCData Group Affiliation status change' as described in Annex A, Table A.4.12.3-1 to inform user A in the SS-UE1 (MCData Client), that user B is being affiliated to group A? - - 10 P 15 Check: Does the MCData Server correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to request from the SS-UE1 (MCData Client) to de- affiliate targeted user B to group A via negotiated mode? - - 11 P 16 Check: Does the MCData Server correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to inform user B in the SS-UE2 (MCData Client) about a remote request to de-affiliate to group A via negotiated mode - - 11 P 17 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation status change' as described in Annex A, Table A.4.12.3-1 to de-affiliate user B to group A using the SS-UE2 (MCData client)? - - 4 P 18 Check: Does the MCData Server correctly perform steps 3-6 of procedure 'MCData Group Affiliation status change' as described in Annex A, Table A.4.12.3-1 to inform user A in the SS-UE1 (MCData Client), that user B is being de-affiliated from group A? - - 4 P 19 Check: Does the MCData Server correctly perform procedure 'MCData Group Affiliation Status Determination and Subscription' as described in Annex A, Table A.4.11.3-1 to de-subscribe the SS-UE1 (MCData Client) from affiliation status changes for targeted user B? - - 13 P NOTE: Affiliation status change triggered by implicit affiliation. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.3.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications: ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 80 Table 5.3.3.3-1: SIP SUBSCRIBE from the SS-UE1 (Step 1, Table 5.3.3.2-1; Step 1, Annex A, Table A.4.11.3-1) Derivation Path: Annex A, Table A.4.11.4-1 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Annex A, Table A.2.7.4-2 MIME body part SIMPLE-FILTER MIME-part-body Simple-Filter as described in Table 5.3.3.3-2 Table 5.3.3.3-2: Simple-Filter in SIP SUBSCRIBE (Table 5.3.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.6-1, condition PER-CLIENT Table 5.3.3.3-3: SIP SUBSCRIBE from the SS-UE2 (Step 4, Table 5.3.3.2-1; Step 1, Annex A, Table A.4.11.3-1) Derivation Path: Annex A, Table A.4.11.4-1 Information Element Value/remark Comment Reference Condition From IETF RFC 3261 [21] addr-spec user-info and host Default public user id (px_MCX_SIP_PublicUserId_B) Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.3.3.3-4 MIME body part SIMPLE-FILTER MIME-part-body Simple-Filter as described in Table 5.3.3.3-2 Table 5.3.3.3-4: MCData-Info in SIP SUBSCRIBE (Table 5.3.3.3-3) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-3 Information Element Value/remark Comment Reference Condition mcdatainfo mcdata-Params mcdata-request-uri Encrypted (note) <mcdata- request-uri> with mcdataURI set to px_MCData_ID_User_B NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-3A. Table 5.3.3.3-5: SIP SUBSCRIBE from the SS-UE1 (Step 6, Table 5.3.3.2-1; Step 1, Annex A, Table A.4.11.3-1) Derivation Path: Annex A, Table A.4.11.4-1 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.3.3.3-4 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 81 Table 5.3.3.3-6: SIP SUBSCRIBE from the SS-UE1 (Step 19, Table 5.3.3.2-1; Step 1, Annex A, Table A.4.11.3-1) Derivation Path: Annex A, Table A.4.11.4-1, condition re-SUBSCRIBE Information Element Value/remark Comment Reference Condition Expires delta-seconds "0" Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.3.3.3-4 Table 5.3.3.3-7: SIP PUBLISH from the SS-UE1 (Step 2, Table 5.3.3.2-1; Step 1, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.12.4-1 Information Element Value/remark Comment Reference Condition Expires delta-seconds "0" Table 5.3.3.3-8: SIP PUBLISH from the SS-UE1 (Step 3, Table 5.3.3.2-1; Step 1, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.12.4-1 Table 5.3.3.3-9: SIP PUBLISH from the SS-UE2 (Steps 5 and 17, Table 5.3.3.2-1; Step 1, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.12.4-1 Information Element Value/remark Comment Reference Condition From IETF RFC 3261 [21] addr-spec user-info and host Default public user id (px_MCX_SIP_PublicUserId_B) Expires delta-seconds "0" Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.3.3.3-10 MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-11 Table 5.3.3.3-10: MCData-Info in SIP PUBLISH (Table 5.3.3.3-9) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-3 Information Element Value/remark Comment Reference Condition mcdatainfo mcdata-Params mcdata-request-uri Encrypted (note) <mcdata- request-uri> with mcdataURI set to px_MCData_ID_User_B NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-3A. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 82 Table 5.3.3.3-11: PIDF in SIP PUBLISH (Table 5.3.3.3-9) Derivation Path: Annex A, Table A.4.12.4-2 Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCData_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status not present ..p-id any allowed value p-id shall be present acc. to ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.2.2 NOTE: Encrypted attribute as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.13.3-1. Table 5.3.3.3-12: SIP PUBLISH from the SS-UE1 (Step 7, Table 5.3.3.2-1; Step 1, Annex A, Table A.4.11.3-1) Derivation Path: Annex A, Table A.4.12.4-1 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.3.3.3-13 MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-14 Table 5.3.3.3-13: MCData-Info in SIP PUBLISH (Table 5.3.3.3-12) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-3 Information Element Value/remark Comment Reference Condition mcdatainfo mcdata-Params mcdata-request-uri Encrypted (note) <mcdata-request- uri> with mcdataURI set to px_MCData_ID_User_B NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-3A. Table 5.3.3.3-14: PIDF in SIP PUBLISH (Table 5.3.3.3-12) Derivation Path: Annex A, Table A.4.12.4-2 Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCData_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status not present ..p-id any allowed value p-id shall be present acc. to ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.2.2 NOTE: Encrypted attribute as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.13.3-1. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 83 Table 5.3.3.3-15: SIP PUBLISH from the SS-UE1 (Step 9, Table 5.3.3.2-1; Step 1, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.12.4-1 Information Element Value/remark Comment Reference Condition Expires delta-seconds "0" Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.3.3.3-13 MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-14 Table 5.3.3.3-16: SIP PUBLISH from the SS-UE2 (Step 13, Table 5.3.3.2-1; Step 1, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.12.4-1 Information Element Value/remark Comment Reference Condition From addr-spec user-info and host Default public user id (px_MCX_SIP_PublicUserId_B) Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.3.3.3-10 MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-11 Table 5.3.3.3-17: SIP NOTIFY from the MCData Server (Step 1, Table 5.3.3.2-1; Step 3, Annex A, Table A.4.11.3-1) Derivation Path: Annex A, Table A.4.11.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-18 Table 5.3.3.3-18: PIDF in SIP NOTIFY (Table 5.3.3.3-17) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status "affiliated" ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 84 Table 5.3.3.3-19: SIP NOTIFY from the MCData Server (Step 3, Table 5.3.3.2-1; Step 5, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.11.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-20 Table 5.3.3.3-20: PIDF in SIP NOTIFY (Table 5.3.3.3-19) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status "affiliated" ..p-id same value as received in corresponding SIP PUBLISH (Step 3) Table 5.3.3.3-21: SIP NOTIFY from the MCData Server (Step 3, Table 5.3.3.2-1; Step 3, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.11.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-22 Table 5.3.3.3-22: PIDF in SIP NOTIFY (Table 5.3.3.3-21) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status "affiliating" ..p-id same value as received in corresponding SIP PUBLISH (Step 3) Table 5.3.3.3-23: SIP NOTIFY from the MCData Server (Step 2, Table 5.3.3.2-1; Step 3, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.11.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-24 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 85 Table 5.3.3.3-24: PIDF in SIP NOTIFY (Table 5.3.3.3-23) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status "deaffiliating" ..p-id same value as received in corresponding SIP PUBLISH (Step 2) Table 5.3.3.3-25: SIP NOTIFY from the MCData Server (Step 2, Table 5.3.3.2-1; Step 5, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.11.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-26 Table 5.3.3.3-26: PIDF in SIP NOTIFY (Table 5.3.3.3-25) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence tuple status affiliation status not present Table 5.3.3.3-27: SIP NOTIFY from the MCData Server (Step 4, Table 5.3.3.2-1; Step 3, Annex A, Table A.4.11.3-1) Derivation Path: Annex A, Table A.4.11.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-28 Table 5.3.3.3-28: PIDF in SIP NOTIFY (Table 5.3.3.3-27) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCData_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status affiliation status "affiliated" NOTE: Encrypted attribute as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.13.3-1. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 86 Table 5.3.3.3-29: SIP NOTIFY from the MCData Server (Steps 7, 8, 13, 14, Table 5.3.3.2-1; Step 5, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.11.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-30 Table 5.3.3.3-30: PIDF in SIP NOTIFY (Table 5.3.3.3-29) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCData_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status affiliation status "affiliated" ..p-id same value as received in corresponding SIP PUBLISH (Steps 7 and 13) NOTE: Encrypted attribute as described in Table 5.5.13.3-1. Table 5.3.3.3-31: SIP NOTIFY from the MCData Server (Steps 7, 8, 13, 14, Table 5.3.3.2-1; Step 3, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.11.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-32 Table 5.3.3.3-32: PIDF in SIP NOTIFY (Table 5.3.3.3-31) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCData_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status affiliation status "affiliating" ..p-id same value as received in corresponding SIP PUBLISH (Steps 7 and 13) NOTE: Encrypted attribute as described in Table 5.5.13.3-1. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 87 Table 5.3.3.3-33: SIP NOTIFY from the MCData Server (Steps 5, 9, 10, 17, 18, Table 5.3.3.2-1; Step 3, Annex A, Table A.4.12.3-1) Derivation Path: Annex A, Table A.4.11.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-34 Table 5.3.3.3-34: PIDF in SIP NOTIFY (Table 5.3.3.3-33) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCData_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status affiliation status "deaffiliating" ..p-id same value as received in corresponding SIP PUBLISH (Steps 5, 9 and 17) NOTE: Encrypted attribute as described in Table 5.5.13.3-1. Table 5.3.3.3-35: SIP NOTIFY from the MCData Server (Steps 5, 6, 9, 10, 17, 18, Table 5.3.3.2-1; Step 5, Annex A, Table A.4.12.3-1; Step 3, Annex A, Table A.4.11.3-1) Derivation Path: Annex A, Table A.4.11.4-2 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-36 Table 5.3.3.3-35: PIDF in SIP NOTIFY (Table 5.3.3.3-36) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, condition AFFILIATION Information Element Value/remark Comment Reference Condition presence entity attribute Encrypted URI (note) with value set to px_MCData_ID_User_B tuple Id attribute Encrypted URI (note) with value set to px_MCX_Client_B_ID status not present NOTE: Encrypted attribute as described in Table 5.5.13.3-1. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 88 Table 5.3.3.3-36: SIP NOTIFY from the MCData Server (Step 19, Table 5.3.3.2-1; Step 3, Annex A, Table A.4.11.3-1) Derivation Path: Annex A, Table A.4.11.4-2 Information Element Value/remark Comment Reference Condition Subscription-State IETF RFC 6665 [30] substate-value "terminated" expires not present Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.3.3.3-35 Table 5.3.3.3-37: SIP MESSAGE from the SS-UE1 (Step 11, Table 5.3.3.2-1; Step 1, Annex A, Table A.2.16.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, conditions MCDATA and AFFILIATION Information Element Value/remark Comment Reference Condition Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.3.3.3-38 Table 5.3.3.3-38: MCData-Info in SIP MESSAGE (Table 5.3.3.3-37) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-3 Information Element Value/remark Comment Reference Condition mcdatainfo mcdata-Params mcdata-request-uri Encrypted (note) <mcdata-request- uri> with mcdataURI set to px_MCData_ID_User_B NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-3A. Table 5.3.3.3-39: SIP MESSAGE from the MCData Server (Step 12, Table 5.3.3.2-1; Step 1, Annex A, Table A.2.17.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, conditions MCDATA and AFFILIATION Information Element Value/remark Comment Reference Condition Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.3.3.3-40 Table 5.3.3.3-40: MCData-Info in SIP MESSAGE (Table 5.3.3.3-39) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-3 Information Element Value/remark Comment Reference Condition mcdatainfo mcdata-Params mcdata-request-uri Encrypted (note) <mcdata-request-uri> with mcdataURI set to px_MCData_ID_User_B mcdata-calling-user-id not present NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 89 Table 5.3.3.3-41: SIP MESSAGE from the SS-UE1 (Step 15, Table 5.3.3.2-1; Step 1, Annex A, Table A.2.16.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, conditions MCDATA and AFFILIATION Information Element Value/remark Comment Reference Condition Message-body MIME body part Affiliation-Command MIME-part-body Affiliation-Command as described in Table 5.3.3.3-43 MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.3.3.3-42 Table 5.3.3.3-42: MCData-Info in SIP MESSAGE (Table 5.3.3.3-41) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-3 Information Element Value/remark Comment Reference Condition mcdatainfo mcdata-Params mcdata-request-uri Encrypted (note) <mcdata-request- uri> with mcdataURI set to px_MCData_ID_User_B NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-3A. Table 5.3.3.3-43: Affiliation-Command in SIP MESSAGE (Table 5.3.3.3-41) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.7-3 Information Element Value/remark Comment Reference Condition command-list affiliate not present de-affiliate group[1] px_MCData_Group_A_ID MCData group name Table 5.3.3.3-44: SIP MESSAGE from the MCData Server (Step 16, Table 5.3.3.2-1; Step 1, Annex A, Table A.2.17.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, conditions MCDATA and AFFILIATION Information Element Value/remark Comment Reference Condition Message-body MIME body part Affiliation-Command MIME-part-body Affiliation-Command as described in Table 5.3.3.3-45 MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.3.3.3-46 Table 5.3.3.3-45: MCData-Info in SIP MESSAGE (Table 5.3.3.3-44) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-3 Information Element Value/remark Comment Reference Condition mcdatainfo mcdata-Params mcdata-request-uri Encrypted (note) <mcdata-request-uri> with mcdataURI set to px_MCData_ID_User_B mcdata-calling-user-id not present NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 90 Table 5.3.3.3-46: Affiliation-Command in SIP MESSAGE (Table 5.3.3.3-44) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.7-3 Information Element Value/remark Comment Reference Condition command-list affiliate not present de-affiliate group[1] px_MCData_Group_A_ID MCData group name 5.4 MCDATA Server - MCDATA Client / Configuration / Pre-established Session Establishment / Pre-established Session Modification / Pre-established Session Release |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.1 Test Purpose (TP) | (1) with { IUT (MCData Server) is able to create pre-established session } ensure that { when { the SS-UE1 (MCData client ) requests creation of pre-established session with sending SIP INVITE message } then { IUT (MCData Server) responds with optional SIP 100 Trying and mandatory 200 (OK) message } } (2) with { IUT (MCData Server) is able to release pre-established session } ensure that { when { the SS-UE1 (MCData client ) requests to terminate MCX session with sending SIP BYE message } then { IUT (MCData Server) responds with 200 (OK) message } } (3) with { IUT (MCData Server) is able to release pre-established Originating session } ensure that { when { the IUT (MCData Server) triggers release session } then { the IUT (MCData Server) requests release session sending SIP BYE message } |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 18.1, 18.3.2.2, 18.3.3.2.1, 18.3.2.2.2, 18.3.4.2.1, 18.3.4.2.2. Unless otherwise stated these are Rel-16 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 18.1] "The MCData client may establish one or more pre-established sessions to the participating MCData function at any time after SIP registration and setting the service settings as defined in subclause 7.2.2 or subclause 7.2.3. The MCData client may use the pre-established session for originating standalone SDS using media plane or SDS session after pre-established session establishment. The participating MCData function may use the pre-established session for terminating standalone SDS using media plane or SDS session after pre-established session establishment. The use of a pre-established session requires the use of resource sharing as specified in 3GPP TS 29.214 [49] and 3GPP TS 24.229 [5] by the participating MCData function. The participating MCData function use of resource sharing is defined in subclause 18.2." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 91 [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 18.3.2.2] "Upon receipt of a "SIP INVITE request for establishing a pre-established session" the participating MCData function: 1) shall check whether the public service identity is allocated and if it is not allocated, shall return a SIP 404 (Not Found) response and skip the rest of the steps; … 3) shall determine whether resource sharing is supported (see subclause 18.2); 4) if resource sharing is supported by the SIP core, determine that there is a binding between the MCData ID of the MCData user establishing the pre-established session and the MCData UE identified by the "+g.3gpp.registration-token" header field parameter in the Contact header field of the third-party REGISTER request (see subclause 18.2) and that this UE identity matches the identity in the "+g.3gpp.registration-token" header field parameter in the Feature-Caps header field in the "SIP INVITE request for establishing a pre- established session"; … 8) shall allocate a URI to be used to identify the pre-established session; 9) shall generate a SIP 200 (OK) response to the SIP INVITE request according to 3GPP TS 24.229 [5]; and a) shall include a Contact header field containing the URI that identifies the pre-established session; b) shall include the public service identity in the P-Asserted-Identity header field; c) shall include a Supported header field containing the "norefersub" option tag; d) shall if the SIP core supports resource sharing, include a Resource-Share header field answer as specified in 3GPP TS 24.229 [5] with: A) the value "media-sharing"; B) an "origin" header field parameter set to "session-initiator"; C) a "timestamp" header field parameter; and D) a "rules" header field parameter with one resource sharing rule per media stream in the same order the corresponding m-line appears in the SDP. Each resource sharing rule is constructed as follows: - a "new-sharing-key" part; and - a "directionality" part indicating the direction of the pre-established media stream; and e) shall include an SDP answer as specified in 3GPP TS 24.229 [5] with the clarifications in subclause 18.3.1.2 and include ICE candidates in the SDP answer as per IETF RFC 5245 [50]; 10) shall interact with the media plane as specified in 3GPP TS 24.582 [15]; 11) shall send the SIP 200 (OK) response towards the MCData client according to the rules and procedures of the 3GPP TS 24.229 [5]; and 12) shall evaluate the ICE candidates according to IETF RFC 5245 [50]. NOTE: If ICE candidate evaluation results in candidate pairs other than the default candidate pair being selected a further offer answer exchange using the procedures in subclause 18.3.4 will be needed." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 92 [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 18.3.3.2.1] "Upon receiving a SIP BYE request from the MCData client within a pre-established session the participating MCData function: 1) shall check whether there is a MCData session using the pre-established session, and: a) if there is an established MCData session then the participating MCData function shall remove the MCData client from the MCData session by performing the procedures as specified in subclause 13.2.2.2.3.1; b) if there is a MCData session in the process of being established, then the participating MCData function: i) shall send a SIP CANCEL request to cancel the MCData session in the process of being established as specified in 3GPP TS 24.229 [5]; and ii) shall release the MCData session as specified in the subclause 13.2.2.2.3.1, if a SIP 200 (OK) response for the SIP INVITE request is received from the remote side; and c) if there is no MCData session using the pre-established session, then the participating MCData function shall: i)_ interact with the media plane as specified in 3GPP TS 24.582 [15] for disconnecting the media plane resources towards the MCData client; and ii) shall generate and send a SIP 200 (OK) response to the SIP BYE request according to rules and procedures of 3GPP TS 24.229 [5]. Upon receiving a SIP 200 (OK) response to the SIP BYE request from the remote side, the participating MCData function: 1) shall interact with the media plane as specified in 3GPP TS 24.582 [15] for releasing media plane resources towards the remote side; 2) shall interact with the media plane as specified in 3GPP TS 24.582 [15] for releasing media plane resources towards the MCData client; and 3) shall send a SIP 200 (OK) response to the SIP BYE request to the MCData client." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 18.3.2.2.2] "When a participating MCData function needs to release a pre-established session as created in subclause 8.2.2, the participating MCData function: 1) shall first release any participants of all MCData calls that are using the pre-established session. The participating MCData function shall remove the MCData client from the MCData session by performing the procedures as specified in subclause 13.2.2.2.3.1; 2) shall generate a SIP BYE request according to rules and procedures of 3GPP TS 24.229 [5]; 3) shall set the Request-URI of the SIP BYE request to the URI that identifies the pre-established session; 4) shall send the SIP BYE request towards the MCData client within the SIP dialog of the pre-established session according to rules and procedures of the 3GPP TS 24.229 [5]; and 5) shall, upon receiving a SIP 200 (OK) response to the SIP BYE request interact with the media plane as specified in 3GPP TS 24.582 [15]." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 18.3.4.2.1] "Upon receiving a SIP UPDATE request or a SIP re-INVITE request to modify an existing pre-established session without associated MCData session, the participating MCData function: 1) shall validate that the received SDP offer includes at least one media stream for which the media parameters and the MSRP URI is acceptable by the participating MCData function and if not reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 93 2) shall generate a SIP 200 (OK) response as follows: a) include an SDP answer according to 3GPP TS 24.229 [5] based on the received SDP offer with the clarifications given in the subclause 18.3.1.2, and include ICE candidates in the SDP answer as per IETF RFC 5245 [50], if required; and b) include a Contact header field containing the URI that identifies the pre-established session and send a SIP 200 (OK) response according to the rules and procedures of 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 18.3.4.2.2] "When the participating MCData function needs to modify the pre-established session outside of an MCData session, the participating MCData function: 1) shall generate a SIP UPDATE request or a SIP re-INVITE request according to 3GPP TS 24.229 [5]; 2) shall include an SDP offer according to 3GPP TS 24.229 [5], and include ICE candidates in the SDP offer as per IETF RFC 5245 [50], if required; and 3) shall send the SIP request towards the MCData client according to the rules and procedures of 3GPP TS 24.229 [5]. On receipt of the SIP 200 (OK) response, the participating MCData function: 1) shall interact with the media plane as specified in 3GPP TS 24.582 [15], if there is change in media parameters or the MSRP URI in the received SDP answer, compared to those in the previously agreed SDP; 2) shall interact with the media plane as specified in 3GPP TS 24.582 [15], if there is a media stream, that is currently used in the pre-established session, is removed in the received SDP answer; and 3) shall interact with the media plane as specified in 3GPP TS 24.582 [15], if there is a media stream accepted in the received SDP answer, that is not currently used by the participant in the pre-established session. NOTE: The participating MCData function keeps resources for previously agreed media stream, media parameters and the MSRP URI until it receives a SIP 200 (OK) response." |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) - For the underlying "transport bearer" over which the SS-UE1 (MCData client) and the MCData 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 [10] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCData operation in the MCData configuration document). IUT: - IUT (MCData Server) - The IUT (MCData 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 (MCData Server) also consists of all sub-systems of the MCData Server, including the Media Distribution Function, the MCData User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Floor Control Server. - The IUT (MCData Server) is the acting Participating Server. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 94 Preamble: - The IUT (MCData Server) is connected to PLMN1 - The IUT (MCData Server) is connected to the SS-UE1 (MCData client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4, where term "MCPTT" is replaced with "MCData". - The SS-UE1 (MCData client) performs the Procedure for MCData Authorization, Configuration and Key Generation as specified in clause 5.1. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.3.2 Test procedure sequence | Table 5.4.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData server correctly perform test procedure 'MCX Participating Terminated pre-established session establishment' as described in Annex A, Table A.2.13.3-1 to create a pre-established session? - - 1 P 2 Check: Does the MCData Server correctly perform test procedure MCX Participating Terminated call release' as described in Annex A, Table A.2.15.3-1 to release the pre-established session? - - 2 P 3 Check: Does the MCData server correctly perform test procedure 'MCX Participating Terminated pre-established session establishment' as described in Annex A, Table A.2.13.3-1 to create a pre-established session? - - 1 P 4 Check: Does the MCData Server correctly perform test procedure MCX Participating Originated call release' as described in Annex A, Table A.2.17.3-1 to release the pre-established session? - - 3 P |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.4.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 5.4.3.3-1: SIP INVITE from the SS-UE1 (Steps 1 and 3, Table 5.4.3.2-1; Step 1, Annex A, Table A.2.13.3-1) Derivation Path: Annex A, Table A.2.13.4-1, condition MCDATA_SDS Information Element Value/remark Comment Reference Condition Session-Expires generic-param "1800" The recommended initial value is 1 800 in IETF RFC 4028 [23]. Max-Forwards value "70" The recommended initial value is 70 in IETF RFC 3261 [21]. Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 5.4.3.3-2 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 95 Table 5.4.3.3-2: SDP for SIP INVITE (Table 5.4.3.3-1) Derivation Path: Table 5.5.3.1.1-3, condition PRE_ESTABLISHED_SESSION, SDP_OFFER, SDS_SESSION, MCDATA_SDS Information Element Value/remark Comment Reference Condition Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "11111111" A numeric string such that the tuple of <username>, <sess- id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session. sess-version "11111111" Session Name " " s= line Connection Data not present c= line Media description[1] Media description for data media description m= line media = message port port number assigned by the SS-UE The transport port to which the media stream is sent Connection Data c= line connection-address IP address of the SS-UE Session attribute a=line attribute="ice-lite" IETF RFC 5245 [29] ice-lite media attribute a= line attribute = path path MSRP URI according to IETF RFC 4975 [24] clauses 6 and 9 scheme "msrp" authority userinfo not present host IP address of the SS-UE port same value as in the media line session id assigned by the SS-UE transport "tcp" URI-parameter not present media attribute a=line attribute="candidate" IETF RFC 5245 [29] candidate candidate for TCP/MSRP foundation 1234 arbitrarily selected component-id 1 according to IETF RFC 5245 [29] clause 4.1.1.1 transport "TCP/MSRP" priority 2130706431 IETF RFC 5245 [29] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id connection-address IP address of the SS-UE (same IP address as in the c=line) default candidate port same port number as in the m= line cand-type "host" ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 96 Table 5.4.3.3-3: SIP 200 (OK) from the MCData Server (Steps 1 and 3, Table 5.4.3.2-1; Step 3, Annex A, Table A.2.13.3-1) Derivation Path: Annex A, Table A.2.13.4-2, condition MCDATA_SDS Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 5.4.3.3-2 Table 5.4.3.3-4: SDP for SIP 200 (OK) (Table 5.4.3.3-3) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-3, condition PRE_ESTABLISHED_SESSION, SDP_ANSWER, SDS_SESSION, MCDATA_SDS Information Element Value/remark Comment Reference Condition Origin o= line username any allowed value "-" indicating the concept of user IDs not being supported sess-id any allowed value A numeric string such that the tuple of <username>, <sess- id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session. sess-version any allowed value Session Name any allowed value s= line Connection Data not required if included in all media c= line nettype "IN" Addrtype "IP4" or "IP6" depending on IP address" connection-address IP address of the MCData Server Media description[1] Media description for data media description m= line media = message port any allowed value The transport port to which the media stream is sent Connection Data present if session description does not contain a c=line; optional otherwise c= line connection-address IP address of the MCData Server media attribute a= line attribute = path path MSRP URI according to IETF RFC 4975 [24] clauses 6 and 9 scheme "msrp" authority userinfo any value if present host any allowed value port same value as in the media line if present session id any allowed value if present transport "tcp" URI-parameter not present media attribute a=line attribute="candidate" IETF RFC 5245 [29] candidate candidate for TCP/MSRP foundation any value component-id 1 according to IETF RFC 5245 [29] clause 4.1.1.1 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 97 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-3, condition PRE_ESTABLISHED_SESSION, SDP_ANSWER, SDS_SESSION, MCDATA_SDS Information Element Value/remark Comment Reference Condition transport "TCP/MSRP" priority any value connection-address same IP address as in media's c= line or in the session's c= line if the media does not have a c= line default candidate port same port number as in the m= line cand-type "host" Table 5.4.3.3-5: SIP BYE from the SS-UE1 (Step 2, Table 5.4.3.2-1; Step 1, Annex A, Table A.2.15.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.2.1-1 Information Element Value/remark Comment Reference Condition Request-Line Request-URI tsc_MCX_SessionID_B The URI that identifies the pre- established session Table 5.4.3.3-6: SIP BYE from the MCData-Server (Step 4, Table 5.4.3.2-1; Step 1, Annex A, Table A.2.17.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.2.2-1, condition MO_CALL Information Element Value/remark Comment Reference Condition Request-Line Request-URI tsc_MCX_SessionID_B The URI that identifies the pre-established session 5.5 MCDATA Server - MCDATA Client / Configuration / Determination of MCDATA Service Settings / Current Active MCDATA Settings / De-subscribe |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData client ) requests to determine the currently active MCData service settings with SIP SUBSCRIBE message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (2) with { IUT (MCData Server) having determined MCData service settings} ensure that { when { the SS-UE1 (MCData client ) requests to re-subscribe to MCData service settings with SIP SUBSCRIBE message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 98 (3) with { IUT (MCData Server) having determined MCData service settings } ensure that { when { the SS-UE1 (MCData client ) requests to de-subscribe from MCData service settings with SIP SUBSCRIBE message } then { IUT (MCData Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 7.1, 7.2.4, 7.3.3, 7.3.4, 7.3.1A, 7.3.5, 7.3.6.1, 7.3.6.2. Unless otherwise stated these are Rel-14 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.1] "This clause describes the procedures for SIP registration and MCData service authorization for the MCData client and the MCData service. The MCData UE can use SIP REGISTER or SIP PUBLISH for MCData service settings to perform service authorization for MCData. The decision which method to use is based on implementation and on availability of an access-token received as outcome of the user authentication procedure as described in 3GPP TS 24.482 [24]. …" [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.2.4] "In order to discover MCData service settings of another MCData client of the same MCData user or to verify the currently active MCData service settings of this MCData client, the MCData client shall generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [5], IETF RFC 6665 [36], and IETF RFC 4354 [35]. …" [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.3.3] "The MCData server shall support obtaining service authorization specific information from a SIP PUBLISH request for MCData 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.mcdata-info+xml MIME body containing an <mcdata-access-token> element and an <mcdata-client-id> element; the MCData 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; … 4) shall perform service authorization for the identified MCData ID as described in 3GPP TS 33.180 [26]; 5) if service authorization was successful: a) shall bind the MCData ID and MCData client ID to the IMS public user identity; b) if the service authorization request was from an MCData user who is previously MCData service authorized on another MCData client (as determined by a comparison of the received MCData client ID with the MCData client ID of existing bindings), keep the current bindings and create a new binding between the MCData ID, MCData client ID and the IMS public user identity; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 99 c) 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 MCData ID and MCData client ID to the identity of the MCData UE identified by 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 MCData server will store the binding MCData ID, MCData client ID, IMS public user identity and an identifier addressing the MCData server in an external database. … 7) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [34] and if processing of the SIP request was not successful, do not continue with the rest of the steps; 8) shall cache the received MCData service settings until the MCData service settings expiration timer expires; 9) shall send a SIP 200 (OK) response according 3GPP TS 24.229 [5] with: a) if more than one binding exists for the MCData ID, an application/vnd.3gpp.mcdata-info+xml MIME body as specified in annex D.1 with a <multiple-devices-ind> element set to the value "true"; 10) shall download the MCData user profile from the MCData user database as defined in 3GPP TS 29.283 [37] if not already stored at the MCData server and use the <selected-user-profile-index> element of the poc- settings event package if included to identify the active MCData user profile for the MCData client; NOTE 2: If the <selected-user-profile-index> element of the poc-settings event package is included then only that MCData user profile is needed to be downloaded from the MCData user database. 11) if there is no <selected-user-profile-index> element included in the poc-settings event package then if multiple MCData user profiles are stored at the MCData server or downloaded for the MCData user from the MCData user database, shall determine the pre-selected MCData user profile to be used as the active MCData user profile by identifying the MCData user profile (see the MCData user profile document in 3GPP TS 24.484 [12]) in the collection of MCData user profiles that contains a <Pre-selected-indication> element; and NOTE 3: If only one MCData user profile is stored at the MCData server or only one MCData user profile is downloaded from the MCData user database, then by default this MCData user profile is the pre-selected MCData user profile. 12) if an <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCData user profile document with one or more <entry> elements containing an MCData group ID (see the MCData user profile document in 3GPP TS 24.484 [12]) for the served MCData ID, shall perform implicit affiliation as specified in subclause 8.3.2.15." [ETSI TS 124 282 [13] (3GPP TS 24.282) 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.mcdata-info+xml MIME body containing an <mcdata-request-uri> element and an <mcdata-client-id> element; The MCData 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… 4) shall verify that a binding between the IMS public user identity in the Request-URI and the MCData ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml exists at the MCData server; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 100 5) if a binding exists between the IMS public user identity and the MCData ID in the request and the validity period of the binding has not expired shall download the MCData user profile from the MCData user database as defined in 3GPP TS 29.283 [37] if not already stored at the MCData server; … 7) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [34] and if processing of the SIP request was not successful, do not continue with the rest of the steps; 8) shall cache the received MCData service settings until the MCData service settings expiration timer expires; 9) shall send a SIP 200 (OK) response according 3GPP TS 24.229 [5]; 10) shall download the MCData user profile from the MCData user database as defined in 3GPP TS 29.283 [37] if not already stored at the MCData server and use the <selected-user-profile-index> element of the poc- settings event package if included to identify the active MCData user profile for the MCData client; NOTE 1: If the <selected-user-profile-index> element of the poc-settings event package is included then only that MCData user profile is needed to be downloaded from the MCData user database. 11) if there is no <selected-user-profile-index> element included in the poc-settings event package then if multiple MCData user profiles are stored at the MCData server or downloaded for the MCData user from the MCData user database, shall determine the pre-selected MCData user profile to be used as the active MCData user profile by identifying the MCData user profile (see the MCData user profile document in 3GPP TS 24.484 [12]) in the collection of MCData user profiles that contains a <Pre-selected-indication> element; and NOTE 2: If only one MCData user profile is stored at the MCData server or only one MCData user profile is downloaded from the MCData user database, then by default this MCData user profile is the pre-selected MCData user profile. 12) if an <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCData user profile document with one or more <entry> elements containing an MCData group ID (see the MCData user profile document in 3GPP TS 24.484 [12]) for the served MCData ID, shall perform implicit affiliation as specified in subclause 8.3.2.1." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.3.1A] "When the MCData server receives a SIP REGISTER request sent from the MCData client contained within a message/sip MIME body of a received third-party SIP REGISTER request or a SIP PUBLISH request, it first determines whether XML MIME bodies included in the request are integrity protected. If XML MIME bodies are integrity protected the MCData server validates the signature of each of the XML MIME bodies. If the integrity protection check(s) pass or the XML MIME bodies are not integrity protected, the MCData server then determines whether the content in specific XML elements is confidentiality protected. If XML content is confidentiality protected, the MCData server decrypts the protected content. Upon receiving: - a SIP REGISTER request containing an application/vnd.3gpp.mcdata-info+xml MIME body within a message/sip MIME body of the SIP REGISTER request sent from the MCData client; or - a SIP PUBLISH request containing an application/vnd.3gpp.mcdata-info+xml MIME body and an application/poc-settings+xml MIME body; the MCData server: 1) shall determine if integrity protection has been applied to XML MIME bodies in the SIP request by following the procedures in subclause 6.5.3.4.1 for each XML MIME body; 2) if integrity protection has been applied, shall use the keying data described in subclause 6.5.3.2 and the procedures described in subclause 6.5.3.4.2 to verify the integrity of each of the XML MIME bodies; and 3) if all integrity protection checks succeed, shall continue with the remaining steps of this subclause. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 101 Upon receiving: - a SIP REGISTER request containing an application/vnd.3gpp.mcdata-info+xml MIME body with an <mcdata- access-token> element and an <mcdata-client-id> element within a message/sip MIME body of the SIP REGISTER request sent from the MCData client; or - a SIP PUBLISH request containing an application/vnd.3gpp.mcdata-info+xml MIME body with an <mcdata- access-token> element and an <mcdata-client-id> element, and an application/poc-settings+xml MIME body; the MCData server: 1) shall determine if confidentiality protection has been applied to the <mcdata-access-token> element and the <mcdata-client-id> element in the application/vnd.3gpp.mcdata-info+xml MIME body, by following the procedures in subclause 6.5.2.4.1; 2) if confidentiality protection has been applied to the <mcdata-access-token> element and <mcdata-client-id> element: a) shall use the keying information received in the MIKEY-SAKKE I_MESSAGE as specified in 3GPP TS 33.180 [26], along with the procedures described in subclause 6.5.2.4.2 to: i) decrypt the received access token in the <mcdata-access-token> element in the application/vnd.3gpp.mcdata-info+xml MIME body; and ii) decrypt the received MCData client ID in the <mcdata-client-id> element in the application/vnd.3gpp.mcdata-info+xml MIME body; b) if the decryption procedure succeeds, shall identify the MCData ID and the MCData client ID from the decrypted values; and c) if the decryption procedure fails, shall determine that confidentiality protection has not been successful; 3) if confidentiality protection has been applied to only one of the <mcdata-access-token> element or the <mcdata-client-id> element: a) shall determine that confidentiality protection has not been successful; 4) if confidentiality protection has not been applied: a) shall identify the MCData ID from <mcdata-access-token> element received in the application/vnd.3gpp.mcdata-info+xml MIME body; and b) shall identify the MCData client ID from the <mcdata-client-id> element received in the application/vnd.3gpp.mcdata-info+xml MIME body. Upon receiving a SIP PUBLISH request containing an application/vnd.3gpp.mcdata-info+xml MIME body with an <mcdata-request-uri> element, an <mcdata-client-id> element, and an application/poc-settings+xml MIME body, the MCData server: 1) shall determine if confidentiality protection has been applied to the <mcdata-request-uri> element and the <mcdata-client-id> element in the application/vnd.3gpp.mcdata-info+xml MIME body by following the procedures in subclause 6.5.2.4.1; 2) if confidentiality protection has been applied to the <mcdata-request-uri> element and the <mcdata-client- id> element: a) shall use the keying information described in subclause 6.5.2.2 along with the procedures described in subclause 6.5.2.4.2 to: i) decrypt the received encrypted MCData ID in the <mcdata-request-uri> element in the application/vnd.3gpp.mcdata-info+xml MIME body; and ii) decrypt the received encrypted MCData client ID in the <mcdata-client-id> element in the application/vnd.3gpp.mcdata-info+xml MIME body; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 102 b) if all decryption procedures succeed, shall identify the MCData ID and MCData client ID from the decrypted values; and c) if the decryption procedure fails, shall determine that confidentiality protection has not been successful; 3) if confidentiality protection has been applied to only one of the <mcdata-request-uri> element or <mcdata- client-id> element: a) shall determine that confidentiality protection has not been successful; 4) if confidentiality protection has not been applied: a) shall identify the MCData ID from the contents of the <mcdata-request-uri> element in the application/vnd.3gpp.mcdata-info+xml MIME body; and b) shall identify the MCData client ID from the <mcdata-client-id> element received in the application/vnd.3gpp.mcdata-info+xml MIME body." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.3.5] "Upon receiving a SIP PUBLISH request containing: 1) an Event header field set to the "poc-settings" value; and 2) an Expires header field set to 0; the MCData server: 1) shall identify the IMS public user identity from the P-Asserted-Identity header field; 2) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [34] and if processing of the SIP request was successful, continue with the rest of the steps; 3) shall remove the MCData service settings; 4) shall remove the binding between the MCData ID and public user identity; and 5) shall send a SIP 200 (OK) response according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.3.6.1] "Upon receiving a SIP SUBSCRIBE request such that: 1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the participating MCData function of the served MCData user; 2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcdata-info+xml MIME body containing the<mcdata-request-uri> element which identifies an MCData ID served by the MCData server; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata,sds" (coded as specified in 3GPP TS 24.229 [5]), in a P-Asserted-Service header field according to IETF RFC 6050 [7]; and 3) the Event header field of the SIP SUBSCRIBE request contains the 'poc-settings' event type. the MCData server: 1) shall identify the served MCData ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request; 2) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the participating MCData function serving the MCData user, shall identify the originating MCData ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request; 3) if the originating MCData ID is different than the served MCData ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 103 4) shall generate a 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [5], IETF RFC 6665 [36] and IETF RFC 4354 [35]. For the duration of the subscription, the MCData server shall notify subscriber about changes of the MCData service settings of the subscribed MCData user, as described in subclause 7.3.6.2." [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.3.6.2] "In order to notify the subscriber about changes of the MCData service settings of the subscribed MCData client of the subscribed MCData user, the MCData server: 1) shall generate an application/poc-settings+xml MIME body as defined in 3GPP TS 24.379 [10] containing: a) the <selected-user-profile-index> element identifying the active MCData user profile; and 2) send a SIP NOTIFY request according to 3GPP TS 24.229 [5], IETF RFC 6665 [36] and IETF RFC 4354 [35] with the constructed application/poc-settings+xml MIME body." |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) - For the underlying "transport bearer" over which the SS-UE1 (MCData client) and the MCData 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 [10] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCData operation in the MCData configuration document). IUT: - IUT (MCData Server) - The IUT (MCData 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 (MCData Server) also consists of all sub- systems of the MCData Server, including the Media Distribution Function, the MCData User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Floor Control Server. - The IUT (MCData Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCData Server) is connected to PLMN1 - The IUT (MCData Server) is connected to the SS-UE1 (MCData client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4, where term "MCPTT" is replaced with "MCData". - The SS-UE1 (MCData client) performs the Procedure for MCData Authorization, Configuration and Key Generation as specified in clause 5.1. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 104 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.3.2 Test procedure sequence | Table 5.5.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server correctly perform procedure 'MCX Subscription and Notification' as described in Annex A, Table A.2.7.3-1 to determine the currently active MCData service settings of the UE (MCData client)? - - 1 P 2 Check: Does the MCData Server correctly perform procedure 'MCX Subscription and Notification' as described in Annex A, Table A.2.7.3-1 to re-subscribe to MCData service settings and to receive later notifications? - - 2 P 3 Check: Does the MCData Server correctly perform procedure 'MCX Subscription and Notification' as described in Annex A, Table A.2.7.3-1 to de-subscribe from MCData service settings? - - 3 P |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.5.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 5.5.3.3-1: SIP SUBSCRIBE from the SS-UE1 (Step 1, Table 5.5.3.2-1; Step 1, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.14-1, condition POC-SETTINGS-EVENT Information Element Value/remark Comment Reference Condition Expires ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.2.4 value "4294967295" Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.5.3.3-2 Table 5.5.3.3-2: MCData-Info in SIP SUBSCRIBE (Table 5.5.3.3-1, Table 5.5.3.3-4 and Table 5.5.3.3-5) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-3, condition POC-SETTINGS-EVENT Table 5.5.3.3-3: SIP 200 (OK) from the MCData Server (Steps 1, 2, 3, Table 5.5.3.2-1; Step 2, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1, conditions SUBSCRIBE-RSP ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 105 Table 5.5.3.3-4: SIP SUBSCRIBE from the SS-UE1 (Step 2, Table 5.5.3.2-1; Step 1, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.14-1, condition POC-SETTINGS-EVENT, re_SUBSCRIBE Information Element Value/remark Comment Reference Condition Expires ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.2.4 value "4294967295" Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.5.3.3-2 Table 5.5.3.3-5: SIP SUBSCRIBE from the SS-UE1 (Step 3, Table 5.5.3.2-1; Step 1, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.14-1, condition POC-SETTINGS-EVENT, re_SUBSCRIBE Information Element Value/remark Comment Reference Condition Expires ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.2.4 value "0" Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 5.5.3.3-2 Table 5.5.3.3-6: SIP NOTIFY from the MCData Server (Steps 1, 2, Table 5.5.3.2-1; Step 3, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, conditions POC-SETTINGS-EVENT Information Element Value/remark Comment Reference Condition Message-body MIME body part PoC-Settings MIME-part-body PoC-Settings as described in Table 5.5.3.3-7 Table 5.5.3.3-7: PoC-Settings in SIP NOTIFY (Table 5.5.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.11.2-1 5.6 MCDATA Server - MCDATA Client / Configuration / Download CSK |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { IUT (MCData Server) requests to update the existing CSK } then { IUT (MCData Server) sends a SIP MESSAGE message to the SS-UE1 (MCData Client) } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 106 (2) with { SS-UE1 (MCData Client) having sent a standalone one-to-one SDS message to SS-UE2 (MCData Client) with disposition notification "DELIVERY" } ensure that { when { IUT (MCData Server) forwards the SDS message to SS-UE2 (MCData Client) and SS-UE2 sends a disposition notification "DELIVERED" } then { IUT (MCData Server) forwards the disposition notification to SS-UE1 (MCData Client) } } |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 7.3.7, ETSI TS 133 180 [12] (3GPP TS 33.180) clauses 9.2.1.1, 9.2.1.2, 9.2.1.3, 9.2.1.4, 5.4, 5.2.1, 5.2.2, 5.8.1, 5.8.2, ETSI TS 124 484 [8] (3GPP TS 24.484) clauses 4.3.1, 4.3.4, 4.4, 6.3.13.2.3, 6.3.3.2.3, 6.3.3.2.1, 4.1.4, 10.2.1, 10.2.1A, 10.3.1, 10.3.1A, 10.4.1, 6.2.3, ETSI TS 124 582 [40] (3GPP TS 24.582) clause 10.3.3. Unless otherwise stated these are Rel-16 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.3.7] "If confidentiality protection is enabled as specified in subclause 6.5.2.3.1, and if the participating MCData function received a Client Server Key (CSK) within a SIP REGISTER request for service authorisation or SIP PUBLISH request for service authorisation, the participating MCData function may decide to update the CSK. In this case, the participating MCData function shall perform a key download procedure for the CSK. The participating MCData function: 1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]; 2) shall set the Request-URI to the URI received in the To header field in the third-party SIP REGISTER request; 3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata" along with parameters "require" and "explicit" according to IETF RFC 3841 [8]; 4) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcdata"; 5) shall include an application/mikey MIME body containing the algorithm to be used to protect the MCData signalling fields, the CSK-ID and the CSK encrypted within a MIKEY message to the MC client as specified in subclause 9.2.1 of 3GPP TS 33.180 [26] in the body of the SIP MESSAGE request; and 6) shall send the SIP MESSAGE request towards the MCData client according to 3GPP TS 24.229 [5]." [ETSI TS 133 180 [12] (3GPP TS 33.180) clause 9.2.1.1] "A Client-Server Key is required to protect unicast RTCP signalling between the MC client and the MCX Server. The use of the CSK in this context is defined in clause 9.4. Additionally, the MC Service provider may require that MC identities, access tokens and other sensitive information transferred between clients and MC domain on the SIP-1 and SIP-2 interfaces be protected at the application layer from any viewing, including protection from viewing at the SIP signalling layer. Symmetric key based protection of SIP payload using CSK may be used to satisfy this requirement. The use of CSK in this context is defined in clause 9.3. The uses of the CSK are shown in Figure 9.2.1-1. …" [ETSI TS 133 180 [12] (3GPP TS 33.180) clause 9.2.1.2] "The 128-bit CSK is initially generated by the client and provided encrypted to the server through the SIP interface along with the CSK-ID identifying the CSK. The key remains in use until: a new CSK is required, the SIP session is torn down, the MC user logs off, or some other indication. If during the active SIP session an update of the CSK is required, the server generates a CSK and provides it to the client using the mechanism defined in clause 5.8. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 107 [ETSI TS 133 180 [12] (3GPP TS 33.180) clause 9.2.1.3] "The CSK is initially distributed via the 'CSK upload' procedure as defined in clause 5.4. The 'CSK upload' procedure creates a security association between the MC client and the MCX Server and occurs during the client's initial connection with the MC Server. The following steps describe how the client obtains the user specific key material and securely transfers the CSK to a server within the MC domain. Prior to beginning of this procedure, the client would have obtained user-specific key material from the KMS. 1) The client randomly generates the CSK and encapsulates the CSK as described in clause 5.4. 2) The client includes the encapsulated CSK in its initial SIP REGISTER or in a SIP PUBLISH message that is used to perform the MC user authorization procedure, and sends the SIP message addressed to the PSI of the server. An illustration is provided below as an example of how this message in included in the body of the SIP REGISTER message. The MIME media type "application/mikey" IETF RFC 3830 [22] is used in this example to insert a MIKEY I_MESSAGE in the SIP payload: EXAMPLE: REGISTER sip:MCPTT_Server_PSI SIP/2.0 Via: SIP/2.0/UDP den3.level3.com Max-Forwards:70 From: MCPTT client IMPU To: Call-ID: <> CSeq: 1 REGISTER Contact: <URI> Content-Type: multipart/mixed;boundary="boundary1" Content-Length: 619 --boundary1 Content-Type: application/mikey MIKEY I_MESSAGE --boundary1 Content-Type: application/... Encrypted Access token, MCPTT ID --boundary1— The following steps describe how the MCX Server retrieves the CSK from the SIP message: 1) The server receives the SIP message and decrypts the encapsulated the CSK as described in clause 5.4. 2) Once the CSK has been extracted, MC user specific information (e.g. the access token) protected in the SIP message as defined in clause 9.3.4, may be decrypted." [ETSI TS 133 180 [12] (3GPP TS 33.180) clause 9.2.1.4] "The MCX Server may decide to update an existing CSK at any time. This may be due to CSK revocation or expiry. The CSK shall be updated by the MCX Server using the 'key download' procedure, defined in clause 5.8. Upon receipt of a CSK via a 'key download' procedure, the MC client shall identify the type of key as a CSK via the 4 most significant bits of the CSK-ID. The MC client shall: - discard any previous CSKs associated with the MC Server FQDN, and - use the new CSK for uplink signaling with the MC Server." [ETSI TS 133 180 [12] (3GPP TS 33.180) clause 5.4] "The key (CSK) is distributed from the MCX client to the MCX Server(s) using the 'CSK upload' procedure. The procedure shall use the common key distribution mechanism described in clause 5.2.2, transported over the SIP bearer. Identity hiding may be supported as defined in clause 5.2.6. The MCX Server may respond with a KMS Redirect Response (KRR) as described in clause 5.2.8 (e.g. if the MC client has migrated or is roaming). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 108 The initiating entity of the CSK upload procedure shall be the MCX UE and the receiving entity shall be the MCX Server. With respect to the common key distribution procedure, the initiating entity URI shall be the MCX Service user ID of the user andthe receiving entity URI shall be the MCX Server Domain Security Identifier (MDSI). The MDSI is added to the recipient field (IDRr) of the message. The distributed key, K, shall be the CSK and the distributed identifier K-ID shall be the CSK-ID. Clause E.4 provides MIKEY message structure for CSK distribution. Before the CSK upload procedure can be used by the client to securely share the encryption key, the MC user shall first be authorized by KMS for key management services. Once the MC user is authorized, the KMS distributes the user's key material to the client as specified in clause 5.3.3. The server receives the SIP message with the protected CSK and retrieves it from the message. It associates the MC User's SIP Core identity (IMPU), MC Service user ID (e.g. MCPTT ID) and the received CSK. Identity binding is used to uniquely identify the CSK used in protection of the SIP payload in subsequent SIP messages sent by both the client and the servers within a MC domain." [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.2.1] "… The primary purpose of these procedures is to allow MCX entities to communicate with each other using end-to-end security. End-to-end security provides assurance to MCX users that no unauthorized access to communications is taking place within the MCX network. End-to-end communication security may be applied to media when operating on- network and media, floor control, transmission control, and media control when operating off-network. A security domain is managed by a Key Management Server (KMS). The KMS is a component of the Common Services Core within the MCX system architecture. For any end-point to use or access end-to-end secure communications, it needs to be provisioned with key material associated to its identity by the KMS. Through the use of the KMS, MC administrators are able to manage the use of, and access to, secure communications within the MCX network. …" [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.2.2] "The security mechanism described in this clause allows a key, K, to be distributed from an initiating party to a receiving party. It provides confidentiality of the key, and integrity and authenticity of the payload. It is used within a number of different security procedures in this specification. The key, K, is distributed encrypted specifically to the receiving entity and signed by the initiating entity. Prior to call commencement, both MCX UEs shall be provisioned by the KMS with time-limited key material associated with the MCX entity's URI. The key is distributed with a 32-bit Key Identifier (K-ID). This payload is a MIKEY-SAKKE I_MESSAGE, as defined in IETF RFC 6509 [11], which ensures the confidentiality of the key, plus integrity and authenticity of the payload. The key is encrypted to the user identity (UID) associated to the receiving MCX entity using the security domain parameters provided in the public values in the certificate received from the KMS. The UID used to encrypt the data is derived from the receiving entity's URI (e.g. sip:user.002@mcptt.example.org) and a time-related parameter (e.g. the current year and month). The terminating entity's URI is added to the recipient field (IDRr) of the message. The payload includes the encrypted key and the key identifier (K-ID). The key is unique within the MC domain. On creating the key, the initiator generates a 32-bit key identifier (K-ID). The 4 most significant bits of the K-ID shall indicate the purpose of the key, the other 28-bits shall be randomly generated. The key identifier (K-ID) is stored in the CSB-ID field of the MIKEY I_MESSAGE. The payload is signed using (the KMS-provisioned key associated to) the identity of the initiating entity. The UID used to sign the data is derived from the initiating entity's URI (e.g. sip:user.001@mcptt.example.org) and a time-related parameter (e.g. the current year and month). The initiating entity's URI is added to the initiator field (IDRi) of the message. NOTE: This solution is for the end-to-end protection of keys and does not protect the identities transmitted. Identities may be masked by transmitting the UID within the MIKEY ID fields as described in Annex E.7. The security processes are summarized in figure 5.2.2-1." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 109 [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.8.1] "The 'key download' procedure is used to send keys from the MCX server to the MC client. It is used to distribute Multicast Signalling Keys (MuSiKs) to the MC clients, and it is used to update both the CSKs and MuSiKs. Within the 'key download' procedure, keys (CSK or MuSiKs) are encrypted specifically to the MC user and signed using an identity representing the MC Server. Prior to group key distribution, each MC client shall be provisioned by the KMS with time-limited key material associated with the MC User as described clause 5.3. The MC Server shall also be provisioned by the MC KMS with key material for an identity which is authorised to act as an MCX Server. The key (CSK or MuSiK) is distributed from the MCX Server to a MC client using the security mechanism described in clause 5.2.2, transported over the SIP bearer. End-point diversity is not required as end-points do not encrypt data, hence the extension in clause 5.2.3 is not applied. Additional parameters may be included as defined in clause 5.2.4. The SAKKE-to-self extension may be included as defined in clause 5.2.5. Identity hiding may be supported as defined in clause 5.2.6. The initiating entity shall be the initiating MCX Server and the receiving entity shall be the terminating MC user. The initiating entity URI shall be the FQDN of the MCX Server (e.g. MDSI of the MC Domain) and the receiving entity URI shall be the MC Service ID of the terminating user. The distributed key, K, shall be the CSK or MuSiK and the key identifier K-ID shall be the CSK-ID or MuSiK-ID (respectively). As a result of this 'key download' mechanism, the MC clients receive a new signalling key, CSK or MuSiK, identified by the 4 most significant bits of the key ID. The MCData Service server may use the Key Download procedure to indicate or modify the algorithm used to protect the MCData signalling fields (i.e. MCData signaling parameters, Data signaling payload and End to end security parameters) by including a 'signalling algorithm' parameter. The 'signalling algorithm' parameter is described in clause 8.5.4.1. The available algorithms shall be as defined in clause 8.5.4.2." [ETSI TS 133 180 [12] (3GPP TS 33.180), clause 5.8.2] "The procedure for key download is described in figure 5.8.2-1: … 0. The MCX UE has been provisioned by a KMS with key material associated with the MC user. The MC UE has also registered with an MCX Server. As a consequence of this registration, the MC UE is subscribed to key download notifications from the MCX Server. 1. The MCX Server sends a key download message (SIP NOTIFY or SIP MESSAGE) to the MC UE. The MC UE extracts the signalling key from the key download message. 2. Upon successful extraction of the signalling key, the MC UE returns a key download success message (200 OK response) to the MCX Server. Upon receipt of a notification of success, the MCX Server is able to begin to use the key for protection of signalling traffic." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 4.3.1] "The MCS server obtains the appropriate MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server. The MCS server obtains the MCS service configuration document that contains the mission critical organisation configured parameters that defined the behaviour of the MCS from the configuration management server. The MCS server subscribes to the MCS service configuration document for each mission critical organisation that is provisioned that is supported by the MCS server using the procedure specified in subclause 6.3.13.2.3. How the MCS server is provisioned with the identities of the mission critical organisations is out of scope of the present document. If the MCS service configuration document has been updated since the current version stored at the MCS server, then the MCS server will receive a SIP NOTIFY request containing an HTTPS URI of the MCS service configuration document. Retrieval by the MCS server, using the notified HTTPS URI, of the MCS service configuration document is performed as specified in subclause 6.3.3.2.3. NOTE: The MCS server can be notified of changes to the MCS service management configuration document at any time while operating the MCS." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 110 [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 4.3.4] "The format of the MCData service configuration document downloaded to the MCData server is defined in subclause 10.4." [ETSI TS 124 484 [8] (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 MCS UE initial configuration document received from an MCS administrator into an appropriate format for configuration of the MCS UE initial configuration MO. If the MCS UE initial configuration MO contains a <default-user-profile> element that identifies an MCS user profile configuration document, the configuration management server needs to convert the identified MCS user profile configuration document received from an MCS administrator into an appropriate format for configuration of the MCS user profile configuration MO. Once an MCS User Profile configuration document has been created or updated by the MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to store MCS user profile configuration document as the user profile in the MC service user database. In order to download the MCS user profile configuration document to an MCS UE or to support an MCS UE updating the MCS user profile configuration document, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to obtain the MCS user profile from the MC service user database. In order to be notified of changes to an MCS user profile configuration document(s) that have been subscribed to by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to be notified of changes to the MCS user profile stored in the MC service user database. In order to delete the MCS user profile when requested by an MCS UE, the configuration management server uses the procedures specified in 3GPP TS 29.283 [7] to delete the MCS user profile from the MC service 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 [8] (3GPP TS 24.484), clause 6.3.13.2.3] "In order to subscribe to an MCS service configuration document, an MCS server shall send an initial SIP SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [22] and IETF RFC 5875 [11]. In the initial SIP SUBSCRIBE request, MCS server: a) shall set the Request URI to a SIP URI containing: 1) the base URI being equal to the public service identity of the CMS configured in the MCS server; and 2) the "auid" parameter set to the application usage identifying th MCS service configuration document; b) shall include a P-Asserted-Identity header field containing the public service identity of the MCS server; c) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [22]), in a P-Asserted-Service header field according to IETF RFC 6050 [23]; and d) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field. Upon receiving a SIP NOTIFY request associated with a subscription created as result of the sent initial SIP SUBSCRIBE request, the MCS server shall handle the SIP NOTIFY request according to IETF RFC 5875 [11]. In order to re-subscribe to notification of changes to an MCS service configuration document, an MCS server shall send a SIP re-SUBSCRIBE request to the network according to the originating AS procedures specified in 3GPP TS 24.229 [22] and IETF RFC 5875 [11]. In the SIP re-SUBSCRIBE request, MCS server: a) shall set the Request URI to a SIP URI containing: 1) the base URI being equal to the public service identity of the CMS configured in the MCS server; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 111 2) the "auid" parameter set to the application usage identifying an MCS service configuration document; and b) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcptt" in the Contact header field." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.3.2.3] "In order to retrieve a configuration management document via the CSC-5 reference point, an MCS Server shall perform the procedures in subclause 6.3.3.2.1 specified for GC. The MCS server shall set the Request-URI of the HTTP GET request to identify the XML document based on configuration and include the "auid" as per the appropriate application usage." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.3.3.2.1] "In order to retrieve a configuration management document, a GC shall send an HTTP GET request with the Request URI that references the document to be updated to the network according to procedures specified in IETF RFC 4825 [14] "Retrieve a Document"." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 4.1.4] "An MCData service administrator can, using an MCData UE configure the: - MCData UE configuration document; - MCData user profile configuration document; - MCData service configuration document; and - MCData related group configuration data in the MCS group document. The format of the MCData UE configuration document is defined in subclause 10.2. The format of the MCData user profile configuration document is defined in subclause 10.3. The format of the MCData service configuration document is defined in subclause 10.4." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.2.1] "The MCData UE configuration document is specified in this subclause. The MCData UE configuration document content is based on requirements of Annex A.2 of 3GPP TS 23.282 [24], in accordance with OMA OMA-TS- XDM_Core-V2_1-20120403-A [2]. The usage of an MCData UE configuration document in the MCData service is described in 3GPP TS 24.282 [25] and 3GPP TS 24.582 [26]. The schema definition is provided in subclause 10.2.2.3. An MCData UE configuration document may apply to all MCData UEs of a mission critical organization or apply to specific MCData UEs identified in the <mcdata-UE-id> element. If there is no <mcdata-UE-id> element in the MCData UE configuration document, then by default the MCData UE configuration document applies to all MCData UEs of the mission critical organization that are not specifically identified in the <mcdata-UE-id> element of another MCData UE configuration document of the mission critical organization. Each MCData UE of a mission critical organization is configured with an MCData UE configuration document that is identified by the instance ID of the MCData UE. MCData UE configuration documents of a MCData user are contained as "XDM collections" in the user's directory of the users tree, in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCData ID, as the user has been already authenticated. A MCData UE configuration document corresponding to a specific MCData UE the MCData user has used to authenticate and is authorised to use the MCData service with is placed in the user directory of the MCData user. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 112 The MCData UE configuration document acts as a template for the CMS to generate UE configuration documents that are downloaded to specific MCData UEs. The MCData UE configuration document that acts as a template is referred to as a "master MCData UE configuration document". The master MCData UE configuration document is stored in the users tree of that MCData system administrator. The master MCData UE configuration document does not directly apply to a specific MCData UE, but instead acts as template that the CMS uses to populate the MCData UE configuration documents of MCData UEs identified by elements of the <MCData-UE-id> element. For MCData UE configuration documents that correspond to a specific MCData UE, the name of the MCData UE configuration document is created from a value defined by the corresponding element that identifies the MCData UE within the <MCData-UE-id> element. For a master MCData UE configuration documents that does not contain a <MCData-UE- id> element, the name of the MCData UE configuration document stored in the user directory is "DEFAULT-MCData- UE.xml"." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.2.1A] "The MCData UE configuration document is accessed using the same XCAP URI, regardless of whether the MCData UE has a specific MCData UE configuration document configured or the master MCData UE configuration document applies. The CMS shall generate the UE's MCData UE configuration document from the master MCData UE configuration document if the MCData administrator did not provision a specific MCData UE configuration document. In this generated document, the <MCData-UE-id> element shall be set to the MCData client's UE ID. The UE's MCData UE configuration document shall always be stored with the filename corresponding to the UE's MCData UE ID under the user's directory of the users tree. The XCAP URI used by the MCData client to access the UE's MCData UE configuration document shall be: - CMSXCAPROOTURI/org.3gpp.mcdata.ue-config/users/sip:MCDATAID/MCSUEID." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.3.1] "The MCData user profile configuration document is specified in this subclause. The MCData user profile configuration document content is based on requirements of Annex A.3 of 3GPP TS 23.282 [24], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCData user profile in the MCData service is described in 3GPP TS 24.282 [25]. The schema definition is provided in subclause 10.3.2. MCData user profile documents are "XDM collections" in the user's directory of the users tree, in accordance with OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. In this case, the term "user" in the XCAP sense refers to the MCData ID, as the user has been already authenticated. The name of the MCData user profile document matches the value of the <ProfileName> element in the MCData user profile document." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.3.1A] "The XCAP URI used by the MCData client to access the MCData user's MCData user profile documents shall be: CMSXCAPROOTURI/org.3gpp.mcdata.user-profile/users/sip:MCDATAID/mcdata-user-profile-INDEX.xml Where INDEX is the index of the MCData user profile as defined in subclause 10.3.2.8." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 10.4.1] "The MCData service configuration document is specified in this subclause. The MCData service configuration document content is based on requirements of Annex A.5 of 3GPP TS 23.282 [24], and structure and procedures of OMA OMA-TS-XDM_Core-V2_1-20120403-A [2]. The usage of an MCData service configuration in the MCData service is described in 3GPP TS 24.282[25] and 3GPP TS 24.582 [26]. The schema definition is provided in subclause 10.4.2.3. Each mission critical organization is configured with an MCData service configuration document." [ETSI TS 124 484 [8] (3GPP TS 24.484), clause 6.2.3] "The MCS server shall send the HTTP request as specified for the HTTP client in the network entity in annex A of 3GPP TS 24.482 [6]." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 113 [ETSI TS 124 582 [40] (3GPP TS 24.582) clause 10.3.3] "A participating MCData function which receives protected media information shall forward it to the next entity without any additional action related to the security framework. A participating MCData function, when receiving a protected media control information from a MCData client shall decrypt and integrity check the protected media control using the CSK and CSK-ID negotiated with the MCData client which has sent the media control. Then, the participating MCData function shall forward the media control information to the controlling MCData function by protecting the media control information using SPK and SPK-ID, if protection is configured between the participating MCData function and the controlling MCData function. A participating MCData function, when receiving a protected media control information from the controlling MCData function shall decrypt and integrity check the protected media control information using the SPK and SPK-ID configured between the participating MCData function and the controlling MCData function. Then, the participating MCData function shall forward the media control information to the destination MCData client by protecting the media control information using the CSK and CSK-ID if protection is negotiated between the participating MCData function and the MCData client." |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCData client) and SS-UE2 (MCData Client). - For the underlying "transport bearer" over which the SS-UE1 (MCData client), the SS-UE2 (MCData Client) and the MCData 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 [10] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCData operation in the MCData configuration document). IUT: - IUT (MCData Server). - The IUT (MCData 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 (MCData Server) also consists of all sub- systems of the MCData Server, including the Media Distribution Function, the MCData User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Floor Control Server. - The IUT (MCData Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCData Server) is connected to PLMN1. - The IUT (MCData Server) is connected to the SS-UE1 (MCData client) and the SS-UE2 (MCData Client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4, where term "MCPTT" is replaced with "MCData". - The SS-UE1 (MCData client) and the SS-UE2 (MCData Client) perform the Procedure for MCData Authorization, Configuration and Key Generation as specified in clause 5.1. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 114 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.