hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.3.2 Test procedure sequence | Table 5.6.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to update the existing CSK between the MCData Server and SS-UE1 (MCData Client)? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perform steps 1-2 of procedure 'MCDATA Server - MCDATA Client / Short Data Service (SDS) / Standalone SDS Using Signalling Control Plane / One-to-one Standalone SDS' as described in Table 6.1.1.3.2-1 to forward a standalone one-to-one SDS message from SS-UE1 (MCData client) to SS-UE2 (MCData Client)? - - 2 P |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.6.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.6.3.3-1: SIP MESSAGE from the MCData Server (Step 1, Table 5.6.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, with condition MCData Information Element Value/remark Comment Reference Condition P-Asserted-Service ETSI TS 124 282 [13] (3GPP TS 24.282) clause 7.3.7 Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcdata" Content-Type media-type "application/mikey" Message-body MIKEY message base64 encoded MIKEY message as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.9.1-1A MIKEY message, containing the updated CSK 5.7 MCDATA Server - MCDATA Client / Configuration / Functional Alias / Functional alias status determination / Activate functional alias / Deactivate functional alias |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.7.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData client ) requests to subscribe to functional alias status change notifications 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) 115 (2) with { IUT (MCData Server) having received subscription to determine the status of a functional alias } ensure that { when { the SS-UE1 (MCData client) requests to activate a functional alias 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 subscription to determine the status of a functional alias } ensure that { when { the SS-UE1 (MCData client) requests to deactivate a functional alias 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 } } (4) with { IUT (MCData Server) having received subscription to determine the status of a functional alias } ensure that { when { the SS-UE1 (MCData client ) requests to de-subscribe from functional alias status change notifications 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.7.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 22.2.2.2.3, 22.2.2.2.4, 22.2.2.2.5, 22.2.2.3.3, 22.2.2.3.4, 22.2.2.3.5, 22.2.2.3.6. Unless otherwise stated these are Rel-16 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 22.2.2.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 functional alias information according to subclause 22.3.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; … ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 116 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 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; 10) 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 22.2.2.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; 11) shall consider a copy of the list of the MCData functional alias entries of the served MCData user information entry as the served list of the MCData functional alias information entries; 12) if the candidate expiration interval is nonzero, shall construct the candidate list of the MCData functional alias entries as follows: a) for each functional alias ID which has a functional alias information entry in the served list of the functional alias information entries, such that the expiration time of the functional alias information entry has not expired yet, and which is indicated in a "functionalAliasID" attribute of a <functionalAlias> 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: i) shall copy the functional alias information entry into a new functional alias information entry of the candidate list of the functional alias information entries; ii) if the functional alias status of the functional alias information entry is "deactivating" or "deactivated", shall set the functional alias status of the new functional alias information entry to the "activated" state and shall reset the activating p-id-fa of the new functional alias information entry; and iii) shall set the expiration time of the new functional alias information entry to the current time increased with the candidate expiration interval; b) for each functional alias ID which has a functional alias information entry in the served list of the functional alias information entries, such that the expiration time of the functional alias information entry has not expired yet, and which is not indicated in any "functionalAliasID" attribute of the <functionalAlias> 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: i) shall copy the functional alias information entry into a new functional alias information entry of the candidate list of the functional alias information entries; and ii) if the functional alias status of the functional alias information entry is "activated" or "activating": - shall set the functional alias status of the new functional alias entry to the "deactivating" state; and - shall set the expiration time of the new functional alias information entry to the current time increased with twice the value of timer F; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 117 c) for each functional alias ID: i) which does not have a functional alias information entry in the served list of the functional alias entries; or ii) which has a functional alias information entry in the served list of the functional alias information entries, such that the expiration time of the functional alias information entry has already expired; and which is indicated in a "functionalAliasID" element of the <functionalAlias> 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: i) shall add a new functional alias information entry in the candidate list of the functional alias information list for the functional alias ID; ii) shall set the functional alias status of the new functional alias information entry to the "activating" state; iii) shall set the expiration time of the new functional alias information entry to the current time increased with the candidate expiration interval; and iv) shall reset the activating p-id-fa of the new functional alias information entry; 13) if the candidate expiration interval is zero, constructs the candidate list of the functional alias information entries as follows: a) for each functional alias ID which has an entry in the served list of the functional alias information entries: i) shall copy the functional alias entry of the served list of the functional alias information into a new functional alias information entry of the candidate list of the functional alias information entries; ii) shall set the functional alias status of the new functional alias information entry to the "de- activating" state; and iii) shall set the expiration time of the new functional alias information entry to the current time increased with twice the value of timer F; 14) shall replace the list of the functional alias information entries stored in the served MCData user information entry with the candidate list of the functional alias information entries; 15) shall perform the procedures specified in subclause 22.2.2.2.6 for the served MCData ID and each functional alias: a) which does not have a functional alias information entry in the served list of the functional alias information entries and which has a functional alias information entry in the candidate list of the functional alias information entries with the functional alias status set to the "activating" state; b) which has a functional alias information entry in the served list of the functional alias information entries with the expiration time already expired, and which has a functional alias information entry in the candidate list of the functional alias information entries with the functional alias status set to the "activating" state; c) which has a functional alias information entry in the served list of the functional alias information entries with the functional alias status set to the "deactivating" state or the "deactivated" state and with the expiration time not expired yet, and which has an functional alias information entry in the candidate list of the functional alias information entries with the functional alias status set to the "activating" state; or d) which has a functional alias information entry in the served list of the functional alias information entries with the functional alias status set to the "activated" state and with the expiration time not expired yet, and which has an functional alias information entry in the candidate list of the functional alias information entries with the functional alias status set to the "deactivating" state; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 118 16) shall identify the handled p-id-fa in the <p-id-fa> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and 17) shall perform the procedures specified in subclause 22.2.2.2.5 for the served MCData ID." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 22.2.2.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: a) the<mcdata-request-uri> element which identifies an MCData ID served by the MCData server; and b) the <mcdatainfo> element with the <mcdata-Params> element with the <request-type> element set to a value of "functional-alias-status-determination"; 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 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 functional alias status of the served MCData ID, shall send a SIP 403 (Forbidden) response and shall not continue with the rest of the steps; and 5) shall generate a SIP 200 (OK) response to the SIP SUBSCRIBE request according to 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 22.2.2.2.5." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 22.2.2.2.5] "In order to notify the subscriber about changes of functional aliases 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 22.2.2.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 generate an application/pidf+xml MIME body indicating per-user functional alias information according to clause 22.3.1 and the served list of the MCData user information entries with the following clarifications: a) the MCData server shall not include information from functional alias information entry with the expiration time already expired; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 119 b) the MCData server shall not include information from a functional alias information entry with the functional alias status set to the "deactivated" state; c) if this procedures is invoked by procedure in clause 22.2.2.2.3 where the handled p-id-fa value was identified, the MCData server shall set the <p-id-fa> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request to the handled p-id-fa value; and 3) send a SIP NOTIFY request according to 3GPP TS 24.229 [5], and IETF RFC 6665 [36] for the subscription created in clause 22.2.2.2.4. In the SIP NOTIFY request, the MCData server shall include the generated application/pidf+xml MIME body indicating per-user functional alias information." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 22.2.2.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 functional alias; 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 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-functional alias information constructed according to clause 22.2.3.2; then the MCData server: 1) shall identify the served functional alias 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; … 4) if the functional alias does not exist in the MCData server, shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [5], IETF RFC 3903 [34] and IETF RFC 3856 [39] and skip the rest of the steps; 4a) if SIP PUBLISH request is for activation of a functional alias then: a) if handled MCPTT ID does not match with any of the entries in the <mcptt-user-list> which contains the MCPTT IDs of MCPTT users which are allowed to activate the functional alias; or b) if no local policy exists that authorizes the request by the handled MCPTT ID; … 5) if SIP PUBLISH request is for activation of a functional alias and the number of activations for the handled functional alias is equal <max-simultaneous-activations>, shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [5], IETF RFC 3903 [34] and IETF RFC 3856 [39] and skip the rest of the steps; … 7) shall respond with SIP 200 (OK) response to the SIP PUBLISH request according to 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; 8) 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 functional alias ID, shall not continue with the rest of the steps; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 120 9) 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; 10) shall consider a functional alias information entry such that: a) the functional alias information entry is in the list of functional alias information entries described in clause 22.2.2.3.2; and b) the functional alias ID of the functional alias information entry is equal to the served functional alias ID; as the served functional alias information entry; 11) 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 functional alias information entry; and ii) the MCData user information entry has the MCData ID set to the served MCData ID; 12) 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 functional alias 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 functional alias information entry; and ii) shall consider the inserted MCData user information entry as the served MCData user information entry; and c) shall set the expiration time in the served MCData user information entry according to the selected expiration time; 13) shall identify the handled p-id-fa in the <p-id-fa> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and 14) shall perform the procedures specified in clause 22.2.2.3.5 for the served functional alias ID." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 22.2.2.3.4] "NOTE: Usage of one SIP SUBSCRIBE request to subscribe for notification about change of functional alias 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 functional alias; 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]; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 121 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 clause 22.3.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 functional alias 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 clause 22.2.2.3.5." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 22.2.2.3.5] "In order to notify the subscriber identified by the handled MCData ID about changes of the functional alias status of the served functional alias ID, the MCData server: 1) shall consider a functional alias information entry such that: a) the functional alias information entry is in the list of functional alias information entries described in clause 22.2.2.3.2; and b) the functional alias ID of the functional alias information entry is equal to the served functional alias 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 functional alias 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-functional alias information according to clause 22.3.1 and the served list of the served MCData user information entry of the functional alias information entry with following clarifications: a) the MCData server shall include the "expires" attribute in the <functionalAlias> element; and b) if this procedures is invoked by procedure in subclause 22.2.2.3.3 where the handled p-id-fa was identified, the MCData server shall set the <p-id-fa> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request to the handled p-id-fa 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 clause 22.2.2.3.4. In the SIP NOTIFY request, the MCData server shall include the generated application/pidf+xml MIME body indicating per-functional alias information." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 22.2.2.3.6] "In order to deactivate a functional alias associated with a target MCData ID: 1) externally triggered by an MCData administrator by a mechanism outside of the scope of the standard; or 2) directly by the MCData function owning the functional alias as a result of an internal trigger like the expiration of the functional alias association; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 122 the MCData server 1) shall consider a functional alias information entry such that: a) the functional alias information entry is in the list of functional alias information entries described in clause 22.2.2.3.2; and b) the functional alias ID of the functional alias information entry is equal to the served functional alias ID; as the served functional alias information entry; 2) shall remove the 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 functional alias information entry; and b) the MCData user information entry has the MCData ID set to the target MCData ID; and 3) shall perform the procedures specified in subclause 22.2.2.3.5 for the served functional alias ID." |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.7.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.7.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) 123 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.7.3.2 Test procedure sequence | Table 5.7.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server correctly perform procedure 'MCData Functional Alias Status Determination and Subscription' as described in Annex A, Table A.4.13.3-1 to determine the current status of a functional alias and to get later notification of status changes of a functional alias? - - 1 P 2 Check: Does the MCData Server correctly perform procedure 'MCData Functional Alias Status Change' as described in Annex A, Table A.4.14.3-1 to activate a functional alias? - - 2 P 3 Check: Does the MCData Server correctly perform procedure 'MCData Functional Alias Status Change' as described in Annex A, Table A.4.14.3-1 to deactivate a functional alias? - - 3 P 4 Check: Does the MCData Server correctly perform procedure 'MCData Functional Alias Status Determination and Subscription' as described in Annex A, Table A.4.13.3-1 to de-subscribe from functional alias status change notifications? - - 4 P |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 5.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 5.7.3.3-1: SIP PUBLISH from the SS-UE1 (Step 3, Table 5.7.3.2-1; Step 1, Annex A, Table A.4.14.3-1) Derivation Path: Annex A, Table A.4.14.4-1 Information Element Value/remark Comment Reference Condition Expires delta-seconds "0" Table 5.7.3.3-2: SIP NOTIFY from the MCData Server (Step 3, Table 5.7.3.2-1; Step 3, Annex A, Table A.4.14.3-1) Derivation Path: Annex A, Table A.4.14.4-4 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 282 [13] (3GPP TS 24.282) clause 22.3.1 MIME-part-body PIDF as described in Table 5.7.3.3-3 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 124 Table 5.7.3.3-3: PIDF in SIP NOTIFY (Table 5.7.3.3-2) Derivation Path: Annex A, Table A.4.14.4-5 Information Element Value/remark Comment Reference Condition presence tuple status functionalAlias status "deactivating" expires Current time plus the value set in the Expires header of the SIP PUBLISH response. ETSI TS 124 282 [13] (3GPP TS 24.282) clause 22.2.2.3.5 Table 5.7.3.3-4: SIP NOTIFY from the MCData Server (Step 3, Table 5.7.3.2-1; Step 5, Annex A, Table A.4.14.3-1) Derivation Path: Annex A, Table A.4.14.4-6 Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 282 [13] (3GPP TS 24.282) clause 22.3.1 MIME-part-body PIDF as described in Table 5.7.3.3-5 Table 5.7.3.3-5: PIDF in SIP NOTIFY (Table 5.7.3.3-4) Derivation Path: Annex A, Table A.4.14.4-7 Information Element Value/remark Comment Reference Condition presence tuple status not present Table 5.7.3.3-6: SIP NOTIFY from the MCData Server (Step 4, Table 5.7.3.2-1; Step 3, Annex A, Table A.4.13.3-1) Derivation Path: Annex A, Table A.4.13.4-3 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.7.3.3-5 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 125 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6 MCData Server - MCData Client operation | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1 Short Data Service | 6.1.1 MCDATA Server - MCDATA Client / Short Data Service (SDS) / Standalone SDS Using Signalling Control Plane / One-to-one Standalone SDS |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.1.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { SS-UE1 (MCData Client) requests one-to-one Standalone SDS by sending a SIP MESSAGE message with disposition request "DELIVERY" } then { IUT (MCData Server) sends a SIP MESSAGE message to UE2 (MCData Client) and responds with a SIP 202 (Accepted) to UE1 (MCData Client) } } (2) with { IUT (MCData Server) having requested an one-to-one Standalone SDS } ensure that { when { SS-UE2 (MCData Client) sends a disposition notification "DELIVERED" } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } (3) with { IUT (MCData Server) having requested an one-to-one Standalone SDS } ensure that { when { SS-UE1 (MCData Client) requests the one-to-one Standalone SDS by sending a SIP MESSAGE message with disposition request "READ" } then { IUT (MCData Server) sends a SIP MESSAGE message to UE2 (MCData Client) and responds with a SIP 202 (Accepted) to UE1 (MCData Client) } } (4) with { IUT (MCData Server) having requested an one-to-one Standalone SDS } ensure that { when { SS-UE2 (MCData Client) sends a disposition notification "READ" by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } (5) with { IUT (MCData Server) having requested an one-to-one Standalone SDS } ensure that { when { SS-UE1 (MCData Client) requests the one-to-one Standalone SDS by sending a SIP MESSAGE message with disposition request "DELIVERY AND READ" } then { IUT (MCData Server) sends a SIP MESSAGE message to UE2 (MCData Client) and responds with a SIP 202 (Accepted) to UE1 (MCData Client) } } (6) with { IUT (MCData Server) having requested an one-to-one Standalone SDS } ensure that { when { SS-UE2 (MCData Client) sends a disposition notification "UNDELIVERED" by sending a SIP MESSAGE message } then { IUT (MCData Server) responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 126 (7) with { IUT (MCData Server) having requested an one-to-one Standalone SDS } ensure that { when { SS-UE2 (MCData Client) sends a disposition notification "DELIVERED AND READ" by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 9.2.2.3.1, 9.2.2.3.2, 9.2.2.4.1, 9.2.2.4.2, 9.2.2.2.1, 6.2.2.1. Unless otherwise stated, these are Rel-14 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.3.1] "Upon receipt of a "SIP MESSAGE request for standalone SDS for originating participating MCData function", the participating MCData function: … 2) shall determine the MCData ID of the originating user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request, and shall authorise the calling user; NOTE: 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) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request is: … b) set to a value of "one-to-one-sds", shall determine the public service identity of the controlling MCData function hosting the one-to-one standalone SDS service for the calling user; … 6) shall determine whether the MCData user identified by the MCData ID is authorised for MCData communications by following the procedures in subclause 11.1; … 9) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]; 10) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCData function as determined by step 4) in this subclause; 11) shall copy all MIME bodies included in the incoming SIP MESSAGE request to the outgoing SIP MESSAGE request; 12) shall include the MCData ID of the originating user in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP MESSAGE request; 12A) if the incoming SIP MESSAGE request contains an application/vnd.3gpp.mcdata-info+xml MIME body that contains a <functional-alias-URI> element, shall check if the status of the functional alias is activated for the MCData ID. If the functional alias status is activated, then the participating MCData function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request to the received value, otherwise shall not include a <functional-alias-URI> element; 13) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; 14) 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; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 127 15) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [5]. Upon receipt of a SIP 202 (Accepted) response in response to the SIP MESSAGE request in step 15): 1) shall generate a SIP 202 (Accepted) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 202 (Accepted) response to the MCData client according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the SIP MESSAGE request in step 15): 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 200 (OK) response to the MCData client according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request in step 15) the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the MCData client according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.3.2] "Upon receipt of a "SIP MESSAGE request for standalone SDS for terminating participating MCData function", the participating MCData function: … 2) shall use the MCData ID present in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata- info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCData ID and public user identity of the terminating MCData user; … 4) shall generate an outgoing SIP MESSAGE request as specified in subclause 6.3.2.1; 5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and 6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the above SIP MESSAGE request, the participating MCData function: 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 200 (OK) response to the controlling MCData function according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP MESSAGE request, the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the controlling MCData function according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.4.1] "This subclause describes the procedures for sending a SIP MESSAGE from the controlling MCData function and is initiated by the controlling MCData function as a result of an action in subclause 9.2.2.4.2. The controlling MCData function: 1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 128 2) shall include an Accept-Contact header field containing the g.3gpp.mcdata.sds media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request; 3) 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.mcdata.sds" along with parameters "require" and "explicit" according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request; 4) shall copy the following MIME bodies in the received SIP MESSAGE request into the outgoing SIP MESSAGE request by following the guidelines in subclause 6.4: a) application/vnd.3gpp.mcdata-info+xml MIME body; b) application/vnd.3gpp.mcdata-signalling MIME body; and c) application/vnd.3gpp.mcdata-payload MIME body 5) in the application/vnd.3gpp.mcdata-info+xml MIME body: a) shall set the <mcdata-request-uri> element set to the MCData ID of the terminating user; and b) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP MESSAGE request was set to a value of "group-sds", shall set the <mcdata-calling-group-id> element to the group identity; 6) shall set the Request-URI to the public service identity of the terminating participating MCData function associated to the MCData user to be invited; 7) shall copy the public user identity of the calling MCData user from the P-Asserted-Identity header field of the incoming SIP MESSAGE request into the P-Asserted-Identity header field of the outgoing SIP MESSAGE request; 8) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds"; and 9) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.4.2] "Upon receipt of a "SIP MESSAGE request for standalone SDS for controlling MCData function", the controlling MCData function: … 3) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body contained in the SIP MESSAGE; 4) if the application/vnd.3gpp.mcdata-signalling MIME body contains a SDS SIGNALLING PAYLOAD message with a SDS disposition request type IE, shall store the value of the Conversation ID IE and the value of the Message ID IE in the SDS SIGNALLING PAYLOAD message; NOTE: The controlling MCData function uses the Conversation ID and Message ID for correlation with disposition notifications. … 7) shall generate a SIP 202 (Accepted) response in response to the "SIP MESSAGE request for standalone SDS for controlling MCData function"; and 8) shall send the SIP 202 (Accepted) response towards the originating participating MCData function according to 3GPP TS 24.229 [5]." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 129 [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.2.1] "The MCData client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6] with the clarifications given below. The MCData client: 1) shall build the SIP MESSAGE request as specified in subclause 6.2.4.1; 2) if a one-to-one standalone SDS message is to be sent, shall insert in the SIP MESSAGE request: a) an application/resource-lists+xml MIME body with the MCData ID of the target MCData user, according to rules and procedures of IETF RFC 4826 [9]; b) an application/vnd.3gpp.mcdata-info+xml MIME body with: i) a <request-type> element set to a value of "one-to-one-sds"; and ii) if the MCData client is aware of active functional aliases and if an active functional alias is to be included in the SIP MESSAGE request, the <functional-alias-URI> element set to the URI of the used functional alias; and c) if end-to-end security is required and the security context does not exist or if the existing security context has expired, an application/mikey MIME body with the MIKEY-SAKKE I_MESSAGE as specified in 3GPP TS 33.180 [26]. The MCData client: i) if necessary, shall instruct the key management client to request keying material from the key management server as described in 3GPP TS 33.180 [26]; ii) shall use the keying material to generate a PCK as described in 3GPP TS 33.180 [26]; iii) 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 one-to-one communications and with the remaining twenty eight bits being randomly generated as described in 3GPP TS 33.180 [26]; iv) shall encrypt the PCK to a UID associated to the MCData client using the MCData ID of the invited user and a time related parameter as described in 3GPP TS 33.180 [26]; v) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated PCK and PCK-ID as specified in 3GPP TS 33.180 [26]; and vi) shall add the MCData ID of the originating MCData to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [26]; vii) shall sign the MIKEY-SAKKE I_MESSAGE using the originating MCData user's signing key provided in the keying material together with a time related parameter; and viii) shall include the MIKEY-SAKKE I_MESSAGE in an application/mikey MIME body as specified in 3GPP TS 33.180 [26]; … 4) shall generate a standalone SDS message as specified in subclause 6.2.2.1; and 5) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 6.2.2.1] "In order to generate an SDS message, the MCData client: 1) shall generate an SDS SIGNALLING PAYLOAD message as specified in subclause 15.1.2; 2) shall generate a DATA PAYLOAD message as specified in subclause 15.1.4; 3) shall include in the SIP request, the SDS SIGNALLING PAYLOAD message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in subclause E.1; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 130 4) shall include in the SIP request, the DATA PAYLOAD message in an application/vnd.3gpp.mcdata-payload MIME body as specified in subclause E.2. When generating an SDS SIGNALLING PAYLOAD message as specified in subclause 15.1.2, the MCData client: 1) shall set the Date and time IE to the current time as specified in subclause 15.2.8; 2) if the SDS message starts a new conversation, shall set the Conversation ID IE to a newly generated Conversation ID value as specified in subclause 15.2.9; 3) if the SDS message continues an existing unfinished conversation, shall set the Conversation ID IE to the Conversation ID value of the existing conversation as specified in subclause 15.2.9; 4) shall set the Message ID IE to a newly generated Message ID value as specified in subclause 15.2.10; 5) if the SDS message is in reply to a previously received SDS message, shall include the InReplyTo message ID IE with the Message ID value in the previously received SDS message; 6) if the SDS message is for user consumption, shall not include an Application ID IE as specified in subclause 15.2.7and shall not include an Extended application ID IE as specified in subclause 15.2.24; 7) if the SDS message is intended for an application on the terminating MCData client, shall include: a) an Application ID IE with a Application ID value representing the intended application as specified in subclause 15.2.7; or b) an Extended application ID IE with an Extended application ID value representing the intended application as specified in subclause 15.2.24; NOTE: The value chosen for the Application ID value is decided by the mission critical organisation. 8) if only a delivery disposition notification is required shall include a SDS disposition request type IE set to "DELIVERY" as specified in subclause 15.2.3; 9) if only a read disposition notification is required shall include a SDS disposition request type IE set to "READ" as specified in subclause 15.2.3; 10) if both a delivery and read disposition notification is required shall include a SDS disposition request type IE set to "DELIVERY AND READ" as specified in subclause 15.2.3; and 11) may set the User location IE to the current location of the UE as specified in subclause 15.2.25. When generating an DATA PAYLOAD message for SDS as specified in subclause 15.1.4, the MCData client: 1) shall set the Number of payloads IE to the number of Payload IEs that needs to be encoded, as specified in subclause 15.2.12; 2) if end-to-end security is required for a one-to-one communication, shall include the Security parameters and Payload IE with security parameters as described in 3GPP TS 33.180 [26]. Otherwise, if end-to-end security is not required for a one-to-one communication, shall include the Payload IE as specified in subclause 15.1.4; and 3) for each Payload IE included: a) if the payload is text, shall set the Payload content type as "TEXT" as specified in subclause 15.2.13; b) if the payload is binary data, shall set the Payload content type as "BINARY" as specified in subclause 15.2.13; c) if the payload is hyperlinks, shall set the Payload content type as "HYPERLINKS" as specified in subclause 15.2.13; d) if the payload is location, shall set the Payload content type as "LOCATION" as specified in subclause 15.2.13; e) if payload is enhanced status for a group, shall set the Payload content type as "ENHANCED STATUS" as specified in subclase 15.2.13; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 131 f) shall include the data to be sent in the Payload data." |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.1.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.1.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 Storage Function, the MCData User Database, the SIP AS, the HTP Server, the HTTP Client, the MSRP TCP Server and the MSRP TCP Client. - The IUT (MCData Server) is the acting Participating Server and Controlling Server. Preamble: - The <max-payload-size-sds-cplane-bytes> element shall not be present in the MCData Service Configuration document so that according to ETSI TS 124 484 [8] (3GPP TS 24.484) there is no size limit imposed for the use of C-plane procedures for the SDS message. - The IUT (MCData Server) is connected to PLMN1. - 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 | 6.1.1.3.2 Test procedure sequence | Table 6.1.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a standalone one-to-one SDS message from SS-UE1 (MCData client) to SS- UE2 (MCData Client), with disposition request "DELIVERY"? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a disposition notification of "DELIVERED", from SS-UE2 (MCData client) to SS-UE1 (MCData Client)? - - 2 P 3 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a standalone one-to-one SDS message from SS-UE1 (MCData client) to SS- - - 3 P ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 132 St Procedure Message Sequence TP Verdict U - S Message UE2 (MCData Client), with disposition request "READ"? 4 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a disposition notification of "READ", from SS-UE2 (MCData client) to SS-UE1 (MCData Client)? - - 4 P 5 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a standalone one-to-one SDS message from SS-UE1 (MCData client) to SS- UE2 (MCData Client), with disposition request "DELIVERY AND READ"? - - 5 P 6 Check: Does the MCData Server (IUT) correctly perform procedure 'MCData Participating Terminated SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.2.3-1 to receive a disposition notification of "UNDELIVERED" from SS-UE2 (MCData client)? (Note 1) - - 6 P 7 Wait until timer TDP1 expires - - - - 8 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to re-deliver the standalone one-to-one SDS message sent in step 5 to SS-UE2? (Note 2) - - 5 P 9 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a disposition notification of "DELIVERED AND READ", from SS-UE2 (MCData client) to SS-UE1 (MCData Client)? - - 7 P 10 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a standalone one-to-one SDS message from SS-UE1 (MCData client) to SS- UE2 (MCData Client), with disposition request "DELIVERY AND READ"? - - 5 P 11 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a disposition notification of "DELIVERED", from SS-UE2 (MCData client) to SS-UE1 (MCData Client)? - - 2 P 12 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a disposition notification of "READ", from SS-UE2 (MCData client) to SS-UE1 (MCData Client)? - - 4 P NOTE 1: Timer TDP1 (SDS re-delivery timer) is started upon receipt of the SIP MESSAGE message that contains an"UNDELIVERED" disposition request. clause F.2.1 Timer TDP1 (SDS re-delivery timer)=60s according to the default value defined in ETSI TS 124 282 [13] (3GPP TS 24.282). NOTE 2: Upon TDP1 (SDS re-delivery timer) timer expiration, the MCData Participating Server shall re-deliver previously sent message, as described in ETSI TS 124 282 [13] (3GPP TS 24.282), clause F.2.1. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 133 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.1.3.3 Specific message contents | Table 6.1.1.3.3-1: SIP MESSAGE from the SS-UE1 (Step 1, Table 6.1.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.1.3.3-1 Table 6.1.1.3.3-2: SIP MESSAGE from the MCData Server (IUT) to SS-UE2 (Step 1, Table 6.1.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-1 Information Element Value/remark Comment Reference Condition Request-Line IETF RFC 3261 [21] IETF RFC 5031 [22] Request-URI px_MCX_SIP_PublicUserI d_B P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServic eId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.4.1 Message-body MIME body part not present Resource lists MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.1.1.3.3-3 MIME body part MCData Data signalling message MIME-part-body MCData Protected Payload Message containing SDS SIGNALLING PAYLOAD as described in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-3 MIME body part MCData Data message MIME-part-body DATA PAYLOAD as described in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-4 Table 6.1.1.3.3-3: MCData-Info (Table 6.1.1.3.3-2) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-2 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params mcdata-request-uri Encrypted <mcdata-request- uri> with mcdataURI set to px_MCData_ID_User_B mcdata-calling-user-id Encrypted <mcdata-calling- user-id> with mcdataURI set to px_MCData_ID_User_A ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 134 Table 6.1.1.3.3-4: SIP MESSAGE from the SS-UE2 (Step 2 and 11, Table 6.1.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-6 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) The URI of the SS-UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.1.1.3.3-5 Table 6.1.1.3.3-5: Resource-lists (Table 6.1.1.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3 Information Element Value/remark Comment Reference Condition resource-lists list name attribute display-name entry[1] uri attribute px_MCData_ID_User_A The MCData ID of the target MCData user Table 6.1.1.3.3-6: SIP MESSAGE from the MCData Server (IUT) to SS-UE1 (Step 2 and 11, Table 6.1.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.1.3.3-5 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServ iceId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 Table 6.1.1.3.3-7: SIP MESSAGE from the SS-UE1 (Step 3, Table 6.1.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.1.3.3-9 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 135 Table 6.1.1.3.3-8: SIP MESSAGE from the MCData Server (IUT) to SS-UE2 (Step 3, Table 6.1.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-8 Information Element Value/remark Comment Reference Condition Request-Line IETF RFC 3261 [21] IETF RFC 5031 [22] Request-URI px_MCX_SIP_PublicUserId _B P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServiceI d_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.4.1 Message-body MIME body part not present Resource lists MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.1.1.3.3-9 MIME body part MCData Data signalling message MIME-part-body MCData Protected Payload Message containing SDS SIGNALLING PAYLOAD as described in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-9 MIME body part MCData Data message MIME-part-body DATA PAYLOAD as described in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-4 Table 6.1.1.3.3-9: MCData-Info (Table 6.1.1.3.3-8) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-2 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params mcdata-request-uri Encrypted <mcdata-request- uri> with mcdataURI set to px_MCData_ID_User_B mcdata-calling-user-id Encrypted <mcdata-calling- user-id> with mcdataURI set to px_MCData_ID_User_A Table 6.1.1.3.3-10: SIP MESSAGE from the SS-UE2 (Step 4 and 12, Table 6.1.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-10 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) The URI of the SS-UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.1.1.3.3-11 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 136 Table 6.1.1.3.3-11: Resource-lists (Table 6.1.1.3.3-10) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3 Information Element Value/remark Comment Reference Condition resource-lists list name attribute display-name entry[1] uri attribute px_MCData_ID_User_A The MCData ID of the target MCData user Table 6.1.1.3.3-12: SIP MESSAGE from the MCData Server (IUT) to SS-UE1 (Step 4 and 12, Table 6.1.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.1.3.3-11 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServ iceId_A The public service identity identifying the controlling MCData function ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 Table 6.1.1.3.3-13: SIP MESSAGE from the SS-UE1 (Step 5 and 10, Table 6.1.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.1.3.3-13 Table 6.1.1.3.3-14: SIP MESSAGE from the MCData Server (IUT) to SS-UE2 (Steps 5, 8 and 10, Table 6.1.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-12 Information Element Value/remark Comment Reference Condition Request-Line IETF RFC 3261 [21] IETF RFC 5031 [22] Request-URI px_MCX_SIP_PublicUserId_ B P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServiceId _A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.4.1 Message-body MIME body part not present Resource lists MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.1.1.3.3-15 MIME body part MCData Data signalling message MIME-part-body MCData Protected Payload Message containing SDS SIGNALLING PAYLOAD as described in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-13 MIME body part MCData Data message MIME-part-body DATA PAYLOAD as described in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-4 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 137 Table 6.1.1.3.3-15: MCData-Info (Table 6.1.1.3.3-14) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-2 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params mcdata-request-uri Encrypted <mcdata-request- uri> with mcdataURI set to px_MCData_ID_User_B mcdata-calling-user-id Encrypted <mcdata-calling- user-id> with mcdataURI set to px_MCData_ID_User_A Table 6.1.1.3.3-16: SIP MESSAGE from the SS-UE2 (Step 6, Table 6.1.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-14 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) The URI of the SS- UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.1.1.3.3-17 MIME body part MCData Data signalling message MIME-part-body MCData Protected Payload Message containing SDS NOTIFICATION as described in Table 6.1.1.3.3-18 Table 6.1.1.3.3-17: Resource-lists (Table 6.1.1.3.3-16) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3 Information Element Value/remark Comment Reference Condition resource-lists list name attribute display-name entry[1] uri attribute px_MCData_ID_User_A The MCData ID of the target MCData user Table 6.1.1.3.3-18: SDS SIGNALLING PAYLOAD (Table 6.1.1.3.3-16) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.8.3-1 Information Element Value/remark Comment Reference Condition SDS disposition notification type '00000010'B ETSI TS 124 282 [13] (3GPP TS 24.282) clause 15.2.5 UNDELIVE RED ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 138 Table 6.1.1.3.3-19: SIP MESSAGE from the SS-UE2 (Step 9, Table 6.1.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.2.3.3-14 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) The URI of the SS- UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.1.1.3.3-20 Table 6.1.1.3.3-20: Resource-lists (Table 6.1.1.3.3-20) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3 Information Element Value/remark Comment Reference Condition resource-lists list name attribute display-name entry[1] uri attribute px_MCData_ID_User_A The MCData ID of the target MCData user Table 6.1.1.3.3-21: SIP MESSAGE from the MCData Server (IUT) to SS-UE1 (Step 9, Table 6.1.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.1.3.3-15 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServic eId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 6.1.2 MCDATA Server - MCDATA Client / Short Data Service (SDS) / Standalone SDS Using Media Plane / Group Standalone SDS |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData Client) initiates establishment of a group standalone SDS } then { IUT (MCData Server) accepts the call from the initiator and establishes the call with SS- UE2 (MCData Client) and responds/forwards empty MSRP messages } } (2) with { IUT (MCData Server) having requested a group Standalone SDS } ensure that { when { the SS-UE1 (MCData Client) sends an MSRP SEND message with disposition request "DELIVERY"} then { IUT (MCData Server) forwards an MSRP SEND message to UE2 (MCData Client) and responds with an MSRP 200 (Ok) to UE1 (MCData Client) } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 139 (3) with { IUT (MCData Server) having requested a group Standalone SDS } ensure that { when { the SS-UE1 (MCData client) ends the group Standalone SDS } then { IUT (MCData Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to SS-UE2 (MCData Client) and waits to close MSRP TCP connections } } (4) with { IUT (MCData Server) having released a group Standalone SDS } ensure that { when { SS-UE2 (MCData Client) sends a disposition notification "DELIVERED" by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 9.2.3.3.3, 9.2.3.3.4, 9.2.3.3.1, 9.2.3.3.2, 9.2.3.4.3, 9.2.3.4.4, 9.2.3.4.1, 9.2.3.4.2, ETSI TS 124 582 [40] (3GPP TS 24.582), clauses 6.2.1.4.1, 6.2.1.4.2, 6.2.1.4.3, 6.2.1.5.1, 6.2.1.5.2, 6.2.1.5.3, 6.2.1.2, 6.2.1.3, 6.3.1.2.1, 6.3.1.2.2, 6.3.1.3. Unless otherwise stated, these are Rel-14 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.3.3.3] "Upon receipt of a "SIP INVITE request for standalone SDS over media plane for originating participating MCData function", the participating MCData function: … 2) shall determine the MCData ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and shall authorise the calling user; NOTE: 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) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP INVITE request is: a) set to a value of "group-sds", shall determine the public service identity of the controlling MCData function associated with the MCData group identity in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the SIP INVITE request; or … 6) shall determine whether the MCData user identified by the MCData ID a) is authorised for MCData communications by following the procedures in subclause 11.1; and … 8) shall generate a SIP INVITE request in accordance with 3GPP TS 24.229 [5]; 9) shall include the option tag "timer" in the Supported header field; 10) should include the Session-Expires header field according to IETF RFC 4028 [38]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 11) shall set the Request-URI of the outgoing SIP INVITE request to the public service identity of the controlling MCData function as determined by step 4) in this subclause; 12) shall include the MCData ID of the originating user in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP INVITE request; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 140 12A) if the incoming SIP INVITE request contains an application/vnd.3gpp.mcdata-info+xml MIME body that contains a <functional-alias-URI> element, shall check if the status of the functional alias is activated for the MCData ID. If the functional alias status is activated, then the participating MCData function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request to the received value, otherwise shall not include a <functional-alias-URI> element; 13) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; 14) shall set the P-Asserted-Identity in the outgoing SIP INVITE request to the public user identity in the P- Asserted-Identity header field contained in the received SIP INVITE request; 15) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCData client as specified in subclause 9.2.3.3.1; and 16) shall send the SIP INVITE request as specified to 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the SIP INVITE request in step 16): 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; 2) shall include in the SIP 200 (OK) response an SDP answer as specified in the subclause 9.2.3.3.2; 3) shall include the option tag "timer" in a Require header field; 4) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [38], "UAS Behavior". If the "refresher" parameter is not included in the received request, the "refresher" parameter in the Session-Expires header field shall be set to "uac"; 5) shall include the following in the Contact header field: a) the g.3gpp.mcdata.sds media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.sds"; and c) the isfocus media feature tag; 6) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 7) shall include an MCData session identity mapped to the MCData session identity provided in the Contact header field of the received SIP 200 (OK) response; 8) if the incoming SIP 200 (OK) response contained an application/vnd.3gpp.mcdata-info+xml MIME body, shall copy the application/vnd.3gpp.mcdata-info+xml MIME body to the outgoing SIP 200 (OK) response. 9) shall include the public service identity received in the P-Asserted-Identity header field of the incoming SIP 200 (OK) response into the P-Asserted-Identity header field of the outgoing SIP 200 (OK) response; and 10) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 6.2.1.4 11) shall send the SIP 200 (OK) response to the MCData client according to 3GPP TS 24.229 [5]; and 12) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [38]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP INVITE request in step 16) the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the MCData client according to 3GPP TS 24.229 [5]." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 141 [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.3.3.4] "Upon receipt of a "SIP INVITE request for standalone SDS over media plane for terminating participating MCData function", the participating MCData function: … 3) shall use the MCData ID present in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCData ID and public user identity of the terminating MCData user; … 5) shall generate a SIP INVITE request accordance with 3GPP TS 24.229 [5]; 6) should include the Session-Expires header field according to IETF RFC 4028 [38]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 7) shall include the option tag "timer" in the Supported header field; 8) shall include the following in the Contact header field: a) the g.3gpp.mcdata.sds media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.sds"; c) the isfocus media feature tag; d) an MCData session identity mapped to the MCData session identity provided in the Contact header field of the incoming SIP INVITE request; and e) any other uri-parameter provided in the Contact header field of the incoming SIP INVITE request; 9) shall include in the SIP INVITE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [8] that were received (if any) in the incoming SIP INVITE request; 10) shall set the Request-URI of the outgoing SIP INVITE request to the public user identity associated to the MCData ID of the terminating MCData user; 11) shall populate the outgoing SIP INVITE request with the MIME bodies that were present in the incoming SIP INVITE request; 12) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP INVITE request to the P- Asserted-Identity header field of the outgoing SIP INVITE request; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for standalone SDS over media plane for terminating participating MCData function" as specified in subclause 9.2.3.3.1; and 14) shall send the SIP INVITE request as specified in 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the above SIP INVITE request, the participating MCData function: 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; 2) shall include in the SIP 200 (OK) response an SDP answer based on the SDP answer in the received SIP 200 (OK) response as specified in subclause 9.2.3.3.2; 3) shall include the option tag "timer" in a Require header field; 4) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [38], "UAS Behavior". If no "refresher" parameter was included in the SIP INVITE request, the "refresher" parameter in the Session-Expires header field shall be set to "uas"; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 142 5) shall include the following in the Contact header field: a) the g.3gpp.mcdata.sds media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.sds"; and c) an MCData session identity mapped to the MCData session identity provided in the Contact header field of the received SIP INVITE request from the controlling MCData function; 6) if the incoming SIP response contained an application/vnd.3gpp.mcdata-info+xml MIME body, shall copy the application/vnd.3gpp.mcdata-info+xml MIME body to the outgoing SIP 200 (OK) response. 7) shall copy the P-Asserted-Identity header field from the incoming SIP 200 (OK) response to the outgoing SIP 200 (OK) response; 8) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [38]; 9) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 6.2.1.5; and 10) shall send the SIP 200 (OK) response to the controlling MCData function according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request, the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the controlling MCData function according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.3.3.1] "The SDP offer is generated based on the received SDP offer. The SDP offer generated by the participating MCData function: 1) shall contain only one SDP media-level section for SDS message as contained in the received SDP offer; and 2) shall contain an "a=key-mgmt" attribute field with a "mikey" attribute value, if present in the received SDP offer. When composing the SDP offer according to 3GPP TS 24.229 [5], the participating MCData function: 1) shall replace the IP address and port number for the offered media stream in the received SDP offer with the IP address and port number of the participating MCData function, if required; and … 2) if the IP address is replaced, shall insert its MSRP URI before the MSRP URI in the "a=path" attribute in the SDP offer." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.3.3.2] "When composing the SDP answer according to 3GPP TS 24.229 [5], the participating MCData function: 1) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCData function, for the accepted media stream in the received SDP offer, if required; and … 2) if the IP address is replaced shall insert its MSRP URI before the MSRP URI in the "a=path" attribute in the SDP answer." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 143 [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.3.4.3] "This subclause describes the procedures for inviting an MCData user to an MCData session. The procedure is initiated by the controlling MCData function as the result of an action in subclause 9.2.3.4.4. The controlling MCData function: 1) shall generate a SIP INVITE request according to 3GPP TS 24.229 [5]; 2) shall include the Supported header field set to "timer"; 3) should include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [38]. The refresher parameter shall be omitted; 4) shall include an Accept-Contact header field containing the g.3gpp.mcdata.sds media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [8]; 5) 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.mcdata.sds" along with parameters "require" and "explicit" according to IETF RFC 3841 [8]; 6) shall include a Referred-By header field with the public user identity of the inviting MCData client; 7) shall include in the Contact header field an MCData session identity for the MCData session with the g.3gpp.mcdata.sds media feature tag, the isfocus media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" according to IETF RFC 3840 [16]; 8) shall include in the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcdata-request-uri> element set to the MCData ID of the terminating user; and b) the <mcdata-calling-group-id> element set to the group identity; 9) shall set the Request-URI to the public service identity of the terminating participating MCData function associated to the MCData user to be invited; NOTE 1: How the controlling MCData function finds the address of the terminating participating MCData function is out of the scope of the current release. 10) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCData function; 11) shall include 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-Id header field according to IETF RFC 6050 [7] in the SIP INVITE request; 12) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating client according to the procedures specified in subclause 9.2.3.4.1; and 13) shall send the SIP INVITE request towards the terminating client in accordance with 3GPP TS 24.229 [5]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCData function: 1) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 6.3.1. NOTE 2: The procedures executed by the controlling MCData function prior to sending a response to the inviting MCData client are specified in subclause 9.2.3.4.4." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.3.4.4] "In the procedures in this subclause: 1) MCData ID in an incoming SIP INVITE request refers to the MCData ID of the originating user from the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP INVITE request; 2) group identity in an incoming SIP INVITE request refers to the group identity from the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP INVITE request; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 144 3) MCData ID in an outgoing SIP INVITE request refers to the MCData ID of the called user in the <mcdata- request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP INVITE request; Upon receipt of a "SIP INVITE request for controlling MCData function for standalone SDS over media plane", the controlling MCData function: … 4) shall cache SIP feature tags, if received in the Contact header field and if the specific feature tags are supported; 5) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [38]; … 7) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP INVITE request is set to a value of "group-sds": a) shall retrieve the necessary group document(s) from the group management server for the group identity contained in the SIP INVITE request and carry out initial processing as specified in subclause 6.3.3, and shall continue with the remaining steps if the procedures in subclause 6.3.3 were successful; … h) shall determine targeted group members for MCData communications by following the procedures in subclause 6.3.4; … j) shall invite each group member determined in step h) above, to the group session, as specified in subclause 9.2.3.4.3; and k) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 6.3.1. Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in subclause 9.2.3.4.3 and if the MCData ID in the SIP 200 (OK) response matches to the MCData ID in the corresponding SIP INVITE request. the controlling MCData function: 1) shall generate SIP 200 (OK) response to the SIP INVITE request according to 3GPP TS 24.229 [5]; 2) shall include the option tag "timer" in a Require header field; 3) shall include the Session-Expires header field and start supervising the SIP session according to rules and procedures of IETF RFC 4028 [38], "UAS Behavior". The "refresher" parameter in the Session-Expires header field shall be set to "uac"; 4) shall include a P-Asserted-Identity header field with the public service identity of the controlling MCData function; 5) shall include a SIP URI for the MCData session identity in the Contact header field identifying the MCData session at the controlling MCData function; 6) shall include the following in the Contact header field: a) the g.3gpp.mcdata.sds media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.sds"; and c) the isfocus media feature tag; 7) shall include Warning header field(s) received in incoming responses to the SIP INVITE request; 8) 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 subclause 9.2.3.4.2; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 145 9) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 6.3.1; and 10) shall send a SIP 200 (OK) response to the inviting MCData client according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.3.4.1] "When composing an SDP offer according to 3GPP TS 24.229 [5], IETF RFC 4975 [17], IETF RFC 6135 [19] and IETF RFC 6714 [20] the controlling MCData function: 1) shall include an "m=message" media-level section for the MCData media stream received from the originating MCData client consisting of: a) the port number; b) a protocol field value of "TCP/MSRP" or "TCP/TLS/MSRP" for TLS; c) a format list field set to '*'; d) an "a=sendonly" attribute; e) an "a=path" attribute containing its own MSRP URI; f) set the content type as "a=accept-types:application/vnd.3gpp.mcdata-signalling application/vnd.3gpp.mcdata-payload"; and g) set the a=setup attribute as "actpass"." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.3.4.2] "When composing the SDP answer according to 3GPP TS 24.229 [5], the controlling MCData function: 1) shall include an "m=message" media-level section for the accepted MCData media stream consisting of: a) the port number; b) a protocol field value of "TCP/MSRP" or "TCP/TLS/MSRP" for TLS according to the received SDP offer; c) a format list field set to '*'; d) an "a=recvonly" attribute; e) an "a=path" attribute containing its own MSRP URI; f) set the content type as a=accept-types: application/vnd.3gpp.mcdata-signalling application/vnd.3gpp.mcdata-payload; and g) set the a=setup attribute set to "passive" according to IETF RFC 6135 [19]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.4.1] "The originating participating MCData function should establish the MSRP session with the originating MCData client as specified in subclause 6.2.1.2." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.4.2] "The originating participating MCData function should establish the MSRP session with the controlling MCData function as specified in subclause 6.2.1.3." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.4.3] "Upon receiving an MSRP SEND request from the originating MCData client, the originating participating MCData function: 1. if in a standalone one-to-one SDS using media plane, shall verify the SDS message size is less than or equal to <MacData1To1> element of the MCData user profile document for the originating MCData client (see the MCData user profile document in 3GPP TS 24.484 [7]); ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 146 2. if the verifications in 1 above fails, shall send the MSRP response with the error code 403 to the originating MCData client and shall not continue with the rest of the procedure; 3. if an MSRP connection is not established with the controlling MCData function then, shall establish the MSRP connection as specified in subclause 6.2.1.4.2. Otherwise, shall use the existing MSRP connection; and 4. shall forward the received MSRP SEND request to the controlling MCData function according to the rules and procedures of IETF RFC 4975 [11]. Upon receiving an MSRP 200 (OK) response from the controlling MCData function, the participating MCData function shall forward the MSRP 200 (OK) response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]. Upon receiving an error MSRP response from the controlling MCData function, the participating MCData function shall forward the error MSRP response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.5.1] "The terminating participating MCData function should establish the MSRP session with the controlling MCData function as specified in subclause 6.2.1.2." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.5.2] "The terminating participating MCData function should establish MSRP session to terminating MCData client as specified in subclause 6.2.1.3." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.5.3] "Upon receiving an MSRP SEND request from the controlling MCData function, the terminating participating MCData function: 1. shall generate and send a MSRP 200 (OK) response for the received MSRP SEND request to the controlling MCData function, according to the rules and procedures of IETF RFC 4975 [11]; and 2. shall forward the received MSRP SEND request to the terminating MCData client according to the rules and procedures of IETF RFC 4975 [11]. Upon receiving an error MSRP response from the terminating MCData client, the participating MCData function shall forward the error MSRP response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.2] "To receive a SDS message over MSRP, the participating MCData function: 1. shall act according to IETF RFC 6135 [12], as: a. an "passive" endpoint, if a=setup attribute in the sent SDP answer was set to "passive"; and b. an "active" endpoint, if a=setup attribute in the sent SDP answer was set to "active"; and 2. shall establish an MSRP connection according to the MSRP connection parameters in the sent SDP answer response as described in IETF RFC 4976 [14]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.3] "To send a SDS message over MSRP, the participating MCData function: 1. shall act according to IETF RFC 6135 [12], as: a. an "active" endpoint, if a=setup attribute in the received SDP answer is set to "passive"; and b. an "passive" endpoint, if a=setup attribute in the received SDP answer is set to "active"; and 2. shall establish the MSRP connection according to the MSRP connection parameters in the received SDP answer response as described in IETF RFC 4976 [14]." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 147 [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.3.1.2.1] "To establish the MSRP connection with the originating MCData client, the controlling MCData function performs below procedures: 1. shall act as an MSRP client and establish TLS connection with the originating participating MCData function, if exists, otherwise the originating MCData client, according to the rules and procedures as described in IETF RFC 4975 [11]; 2. shall act as an MSRP client to send MSRP SEND requests according to the rules and procedures described in IETF RFC 6135 [12]; 3. shall act as an "passive" endpoint according to the rules and procedures described in IETF RFC 6135 [12]; 4. shall establish the MSRP connection with originating MCData client, according to the rules and procedures described in IETF RFC 6135 [12]; and 5. as a passive endpoint, shall wait for MSRP SEND request on established MSRP connection, to bind the MSRP connection to the MSRP session according to the rules and procedures of IETF RFC 4975 [11] and IETF RFC 6135 [12]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.3.1.2.2] "To establish the MSRP connection with the terminating MCData client, the controlling MCData function performs below procedures: 1. shall act as an MSRP client and establish TLS connection with the terminating participating MCData function, if exists, otherwise the terminating MCData client, according to the rules and procedures as described in IETF RFC 4975 [11]; 2. shall act as an MSRP client to send MSRP SEND requests according to the rules and procedures described in IETF RFC 6135 [12]; 3. shall act according to IETF RFC 6135 [12], as: a. an "active" endpoint, if a=setup attribute in the received SDP answer is set to "passive"; and b. an "passive" endpoint, if a=setup attribute in the received SDP answer is set to "active"; 4. shall establish the MSRP connection with each terminating MCData client identified in the 3GPP TS 24.282 [8], according to the rules and procedures described in IETF RFC 6135 [12]; and 5. if acting as an "active" endpoint, shall send an empty MSRP SEND request on each established MSRP connection, to bind the MSRP connection to the MSRP session according to the rules and procedures of IETF RFC 4975 [11] and IETF RFC 6135 [12]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.3.1.3] "Upon receiving a MSRP SEND request from the originating participating MCData function, the controlling MCData function: 1. if in a standalone one-to-one SDS using media plane, shall verify the SDS message size is less than or equal to <max-data-size-sds-bytes> element in the MCData service configuration document as specified in 3GPP TS 24.484 [7]; 2. if in a standalone group SDS using media plane shall verify: a. the SDS message size is less than or equal to <mcdata-max-data-in-single-request> element of the MCData group document for the (see the MCData group document in 3GPP TS 24.481 [4]); and b. the SDS message size is less than or equal to <mcdata-on-network-max-data-size-for-SDS> element of the MCData group document (see the MCData group document in 3GPP TS 24.481 [4]); 3. if the verifications in either 1 or 2 a or 2 b above fails, shall send the MSRP response with the error code 403 to the MCData client which sent the SDS message and shall not continue with the rest of the procedure; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 148 4. shall generate and send a MSRP 200 (OK) response for the received MSRP SEND requests to the originating participating MCData function, according to the rules and procedures of IETF RFC 4975 [11]; and 5. shall forward the received MSRP SEND requests to each terminating MCData client with which a successful MSRP connection was established, according to the rules and procedures of IETF RFC 4975 [11]. Following clarifications apply to the generated MSRP SEND request: a. shall modify the To-Path header according to the MSRP URI received in the answer SDP from the MCData client in accordance with rules and procedures of IETF RFC 4975 [11]; and b. shall modify the From-Path header to the controlling MCData function's own MSRP URI, according to the rules and procedures of IETF RFC 4975 [11]." |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.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 Storage Function, the MCData User Database, the SIP AS, the HTP Server, the HTTP Client, the MSRP TCP Server and the MSRP TCP Client. - The IUT (MCData Server) is the acting Participating Server and Controlling Server. Preamble: - The <max-payload-size-sds-cplane-bytes> element of the MCData Service Configuration document shall be set to 0 to force the MCData client to send the data using the media plane. - The IUT (MCData Server) is connected to PLMN1. - 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. - SS-UE1 (MCData client) and SS-UE2 (MCData client) are affiliated to the Prearranged group. - The IUT (MCData Server) is the controlling server of the Prearranged group. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 149 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.3.2 Test procedure sequence | Table 6.1.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Establishment' as described in Annex A, Table A.4.3.3-1 to establish a media plane connection for a group? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MSRP message transfer' as described in Annex A, Table A.4.4.3-1 to send a group SDS message from SS-UE1 (MCData client), with disposition request "DELIVERY"? - - 2 P 3 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Release' as described in Annex A, Table A.4.5.3-1? - - 3 P 4 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a disposition notification of "DELIVERED", from SS-UE2 (MCData client) to SS-UE1 (MCData Client)? - - 4 P |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.2.3.3 Specific message contents | Table 6.1.2.3.3-1: SIP INVITE from the SS-UE1 (Step 1, Table 6.1.2.3.2-1; Step 1, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.7.3.3-1 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 6.1.2.3.3-2 MIME body part MCData-Info MIME-part-body MCData-Info as described in Table ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.7.3.3-2 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 150 Table 6.1.2.3.3-2: SDP for SIP INVITE (Table 6.1.2.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.7.3.3-1A 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-UE1 The transport port to which the media stream is sent Connection Data c= line connection-address IP address of the SS-UE1 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-UE1 port same value as in the media line session id assigned by the SS-UE1 transport "tcp" URI-parameter not present Table 6.1.2.3.3-3: SIP INVITE from the MCData Server (IUT) to the SS-UE2 (Step 1, Table 6.1.2.3.2-1; Step 2, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.8.3.3-1 Information Element Value/remark Comment Reference Condition To addr-spec user-info and host px_MCX_SIP_PublicUserId_B Max-Forwards value any allowed value Session-Expires generic-param any allowed value Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.1.2.3.3-4 MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.1.2.3.3-5 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 151 Table 6.1.2.3.3-4: SDP for SIP INVITE (Table 6.1.2.3.3-4) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.8.3.3-1A 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 152 Table 6.1.2.3.3-5: MCData-Info (Table 6.1.2.3.3-3) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.8.3.3-2 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params mcdata-request-uri Encrypted <mcdata- request-uri> with mcdataURI set to px_MCData_ID_User_B Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A mcdata-calling-user-id Encrypted <mcdata- calling-user-id> with mcdataURI set to px_MCData_ID_User_A Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A mcdata-client-id Encrypted <mcdata-client- id> with mcdataString set to px_MCX_Client_A_ID Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A Table 6.1.2.3.3-6: SIP 200 (OK) from the SS-UE2 (Step 1, Table 6.1.2.3.2-1; Step 4, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.8.3.3-3 Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.1.2.3.3-7 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 153 Table 6.1.2.3.3-7: SDP for SIP 200 (OK) (Table 6.1.2.3.3-6) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.8.3.3-4 Information Element Value/remark Comment Reference Condition Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "22222222" 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 "22222222" 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-UE2 The transport port to which the media stream is sent Connection Data c= line connection-address IP address of the SS-UE2 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-UE2 port same value as in the media line session id assigned by the SS-UE2 transport "tcp" URI-parameter not present Table 6.1.2.3.3-8: SIP 200 (OK) from the MCData Server (IUT) to the SS-UE1 (Step 1, Table 6.1.2.3.2-1; Step 5, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.7.3.3-3 Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.1.2.3.3-9 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 154 Table 6.1.2.3.3-9: SDP for SIP 200 (OK) (Table 6.1.2.3.3-8) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.7.3.3-4 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 Table 6.1.2.3.3-10: MSRP SEND from the SS-UE1 (Step 2, Table 6.1.2.3.2-1; Step 1, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.7.3.3-5 Information Element Value/remark Comment Reference Condition data Message or chunk of message as specified in Table 6.1.2.3.3-10A IETF RFC 3261 [21] ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 155 Table 6.1.2.3.3-10A: MIME Message (Table 6.1.2.3.3-10) Derivation Path: IETF RFC 2046 [18] Information Element Value/remark Comment Reference Condition MIME body part MCData Data signalling message MIME-part-headers Content-Type "application/vnd.3gpp.mcdata- signalling" MIME-part-body MCData Protected Payload Message containing SDS SIGNALLING PAYLOAD as described in Table 6.1.2.3.3-10B MIME body part MCData Data message MIME-part-headers Content-Type "application/vnd.3gpp.mcdata- payload" MIME-part-body MCData Protected Payload Message containing DATA PAYLOAD as described in Table 6.1.2.3.3-10C Table 6.1.2.3.3-10B: SDS SIGNALLING PAYLOAD (Table 6.1.2.3.3-10A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.8.2-1, condition DELIVERED Table 6.1.2.3.3-10C: Data Payload (Table 6.1.2.3.3-10A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.9.1-2 Table 6.1.2.3.3-11: MSRP SEND from the MCData Server (IUT) to SS-UE2 (Step 2, Table 6.1.2.3.2-1; Step 3, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.8.3.3-5 Table 6.1.2.3.3-12: SIP MESSAGE from the SS-UE2 (Step 4, Table 6.1.2.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.8.3.3-9 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) The URI of the SS- UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.1.2.3.3-13 MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.1.2.3.3-14 MIME body part MCData Data signalling message MIME-part-body MCData Protected Payload Message containing SDS NOTIFICATION as described in Table 6.1.2.3.3-15 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 156 Table 6.1.2.3.3-13: Resource-lists (Table 6.1.2.3.3-12) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3 Information Element Value/remark Comment Reference Condition resource-lists list name attribute display-name entry[1] uri attribute px_MCData_ID_User_A The MCData ID of the target MCData user Table 6.1.2.3.3-14: MCData-Info (Table 6.1.2.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 mcdata-info mcdata-Params mcdata-calling-group-id Encrypted <mcdata-request- uri> with mcdataURI set to px_MCData_Group_A_ID Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-3A mcdata-client-id not present Table 6.1.2.3.3-15: SDS NOTIFICATION (Table 6.1.2.3.3-12) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.8.3.3-11 Information Element Value/remark Comment Reference Condition Date and time The current date and time The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds). ETSI TS 124 282 [13] (3GPP TS 24.282) clause 15.2.8 Table 6.1.2.3.3-16: SIP MESSAGE from the MCData Server (IUT) to SS-UE1 (Step 4, Table 6.1.2.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.7.3.3-11 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServic eId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 157 6.1.3 MCDATA Server - MCDATA Client / Short Data Service (SDS) / SDS Session / One-to-one SDS Session |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.3.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData Client) initiates establishment of a one-to-one SDS session } then { IUT (MCData Server) accepts the call from the initiator and establishes the call with SS- UE2 (MCData Client) and responds/forwards empty MSRP messages } } (2) with { IUT (MCData Server) having requested an one-to-one SDS session } ensure that { when { the SS-UE1 (MCData Client) sends an MSRP SEND message with disposition request "DELIVERY"} then { IUT (MCData Server) forwards an MSRP SEND message to SS-UE2 (MCData Client) and responds with an MSRP 200 (Ok) to SS-UE1 (MCData Client) } } (3) with { IUT (MCData Server) having requested an one-to-one SDS session } ensure that { when { SS-UE2 (MCData Client) sends a disposition notification "DELIVERED" by sending an MSRP SEND message } then { IUT (MCData Server) sends a SIP MESSAGE message to SS-UE1 (MCData Client) and responds with a SIP 202 (Accepted) to SS-UE2 (MCData Client) } } (4) with { IUT (MCData Server) having requested an one-to-one SDS session } ensure that { when { the SS-UE2 (MCData Client) sends an MSRP SEND message with disposition request "READ"} then { IUT (MCData Server) forwards an MSRP SEND message to SS-UE1 (MCData Client) and responds with an MSRP 200 (Ok) to SS-UE2 (MCData Client) } } (5) with { IUT (MCData Server) having requested an one-to-one SDS session } ensure that { when { SS-UE1 (MCData Client) sends a disposition notification "READ" by sending an MSRP SEND message } then { IUT (MCData Server) sends a SIP MESSAGE message to SS-UE2 (MCData Client) and responds with a SIP 202 (Accepted) to SS-UE1 (MCData Client) } } (6) with { IUT (MCData Server) having requested an one-to-one SDS session } ensure that { when { the SS-UE1 (MCData client) ends the one-to-one SDS session } then { IUT (MCData Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to SS-UE2 (MCData Client) and waits to close MSRP TCP connections } } |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.3.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 9.2.4.3.3, 9.2.4.3.4, 9.2.4.3.1, 9.2.4.3.2, 9.2.4.4.3, 9.2.4.4.4, 9.2.4.4.1, 9.2.4.4.2, ETSI TS 124 582 [40] (3GPP TS 24.582), clauses 6.2.2.4.1, 6.2.2.4.2, 6.2.2.4.3, 6.2.2.5.1, 6.2.2.5.2, 6.2.2.5.3, 6.2.2.2, 6.2.2.3, 6.3.2.2.1, 6.3.2.2.2, 6.3.2.3. Unless otherwise stated, these are Rel-14 requirements. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 158 [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.4.3.3] "Upon receipt of a "SIP INVITE request for SDS session for originating participating MCData function", the participating MCData function: … 2) shall determine the MCData ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and shall authorise the calling user; NOTE: 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) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP INVITE request is: … b) set to a value of "one-to-one-sds-session", shall determine the public service identity of the controlling MCData function hosting the one-to-one SDS session service for the calling user; … 6) shall determine whether the MCData user identified by the MCData ID is authorised for MCData communications by following the procedures in subclause 11.1; … 8) shall generate a SIP INVITE request in accordance with 3GPP TS 24.229 [5]; 9) shall include the option tag "timer" in the Supported header field; 10) should include the Session-Expires header field according to IETF RFC 4028 [38]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 11) shall set the Request-URI of the outgoing SIP INVITE request to the public service identity of the controlling MCData function as determined by step 4) in this subclause; 12) shall include the MCData ID of the originating user in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP INVITE request; 12A) if the incoming SIP MESSAGE request contains an application/vnd.3gpp.mcdata-info+xml MIME body that contains a <functional-alias-URI> element, shall check if the status of the functional alias is activated for the MCData ID. If the functional alias status is activated, then the participating MCData function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request to the received value, otherwise shall not include a <functional-alias-URI> element; 13) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; 14) shall set the P-Asserted-Identity in the outgoing SIP INVITE request to the public user identity in the P- Asserted-Identity header field contained in the received SIP INVITE request; 15) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCData client as specified in subclause 9.2.4.3.1; and 16) shall send the SIP INVITE request as specified to 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the SIP INVITE request in step 16): 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; 2) shall include in the SIP 200 (OK) response an SDP answer as specified in the subclause 9.2.4.3.2; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 159 3) shall include the option tag "timer" in a Require header field; 4) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [38], "UAS Behavior". If the "refresher" parameter is not included in the received request, the "refresher" parameter in the Session-Expires header field shall be set to "uac"; 5) shall include the following in the Contact header field: a) the g.3gpp.mcdata.sds media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.sds"; and c) the isfocus media feature tag; 6) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 7) shall include an MCData session identity mapped to the MCData session identity provided in the Contact header field of the received SIP 200 (OK) response; 8) if the incoming SIP 200 (OK) response contained an application/vnd.3gpp.mcdata-info+xml MIME body, shall copy the application/vnd.3gpp.mcdata-info+xml MIME body to the outgoing SIP 200 (OK) response. 9) shall include the public service identity received in the P-Asserted-Identity header field of the incoming SIP 200 (OK) response into the P-Asserted-Identity header field of the outgoing SIP 200 (OK) response; and 10) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 6.2.2.4; 11) shall send the SIP 200 (OK) response to the MCData client according to 3GPP TS 24.229 [5]; and 12) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [38]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP INVITE request in step 16) the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the MCData client according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.4.3.4] "Upon receipt of a "SIP INVITE request for SDS session for terminating participating MCData function", the participating MCData function: … 3) shall use the MCData ID present in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCData ID and public user identity of the terminating MCData user; … 5) shall generate a SIP INVITE request accordance with 3GPP TS 24.229 [5]; 6) should include the Session-Expires header field according to IETF RFC 4028 [38]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 7) shall include the option tag "timer" in the Supported header field; 8) shall include the following in the Contact header field: a) the g.3gpp.mcdata.sds media feature tag; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 160 b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.sds"; c) the isfocus media feature tag; d) an MCData session identity mapped to the MCData session identity provided in the Contact header field of the incoming SIP INVITE request; and e) any other uri-parameter provided in the Contact header field of the incoming SIP INVITE request; 9) shall include in the SIP INVITE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [8] that were received (if any) in the incoming SIP INVITE request; 10) shall set the Request-URI of the outgoing SIP INVITE request to the public user identity associated to the MCData ID of the terminating MCData user; 11) shall populate the outgoing SIP INVITE request with the MIME bodies that were present in the incoming SIP INVITE request; 12) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP INVITE request to the P- Asserted-Identity header field of the outgoing SIP INVITE request; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for SDS session for terminating participating MCData function" as specified in subclause 9.2.4.3.1; and 14) shall send the SIP INVITE request as specified in 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the above SIP INVITE request, the participating MCData function: 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; 2) shall include in the SIP 200 (OK) response an SDP answer based on the SDP answer in the received SIP 200 (OK) response as specified in subclause 9.2.4.3.2; 3) shall include the option tag "timer" in a Require header field; 4) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [38], "UAS Behavior". If no "refresher" parameter was included in the SIP INVITE request, the "refresher" parameter in the Session-Expires header field shall be set to "uas"; 5) shall include the following in the Contact header field: a) the g.3gpp.mcdata.sds media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.sds"; and c) an MCData session identity mapped to the MCData session identity provided in the Contact header field of the received SIP INVITE request from the controlling MCData function; 6) if the incoming SIP response contained an application/vnd.3gpp.mcdata-info+xml MIME body, shall copy the application/vnd.3gpp.mcdata-info+xml MIME body to the outgoing SIP 200 (OK) response. 7) shall copy the P-Asserted-Identity header field from the incoming SIP 200 (OK) response to the outgoing SIP 200 (OK) response; 8) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [38]. 9) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 6.2.2.5; and 10) shall send the SIP 200 (OK) response to the controlling MCData function according to 3GPP TS 24.229 [5]. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 161 Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request, the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the controlling MCData function according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.4.3.1] "The SDP offer is generated based on the received SDP offer. The SDP offer generated by the participating MCData function: 1) shall contain only one SDP media-level section for SDS message as contained in the received SDP offer;and 2) shall contain an "a=key-mgmt" attribute field with a "mikey" attribute value, if present in the received SDP offer. When composing the SDP offer according to 3GPP TS 24.229 [5], the participating MCData function: 1) shall replace the IP address and port number for the offered media stream in the received SDP offer with the IP address and port number of the participating MCData function, if required; and … 2) if the IP address is replaced, shall insert its MSRP URI before the MSRP URI in the "a=path" attribute in the SDP offer." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.4.3.2] "When composing the SDP answer according to 3GPP TS 24.229 [5], the participating MCData function: 1) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCData function, for the accepted media stream in the received SDP offer, if required; and … 2) if the IP address is replaced shall insert its MSRP URI before the MSRP URI in the "a=path" attribute in the SDP answer." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.4.4.3] "This subclause describes the procedures for inviting an MCData user to an MCData session. The procedure is initiated by the controlling MCData function as the result of: - an action in subclause 9.2.4.4.4; or - for group SDS session, when an MCData client successfully affiliates the MCData group after the SDS session has been established. The controlling MCData function: 1) shall generate a SIP INVITE according to 3GPP TS 24.229 [5]; 2) shall include the Supported header field set to "timer"; 3) should include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [38]. The refresher parameter shall be omitted; 4) shall include an Accept-Contact header field containing the g.3gpp.mcdata.sds media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [8]; 5) 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.mcdata.sds" along with parameters "require" and "explicit" according to IETF RFC 3841 [8]; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 162 6) shall include a Referred-By header field with the public user identity of the inviting MCData client; 7) shall include in the Contact header field an MCData session identity for the MCData session with the g.3gpp.mcdata.sds media feature tag, the isfocus media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" according to IETF RFC 3840 [16]; 8) shall include in the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcdata-request-uri> element set to the MCData ID of the terminating user; and b) the <mcdata-calling-group-id> element set to the group identity if the request is for group sds; 9) shall set the Request-URI to the public service identity of the terminating participating MCData function associated to the MCData user to be invited; NOTE 1: How the controlling MCData function finds the address of the terminating participating MCData function is out of the scope of the current release. 10) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCData function; 11) shall include 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-Id header field according to IETF RFC 6050 [7] in the SIP INVITE request; 12) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating client according to the procedures specified in subclause 9.2.4.4.1; and 13) shall send the SIP INVITE request towards the terminating client in accordance with 3GPP TS 24.229 [5]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCData function: 1) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 6.3.2. NOTE 2: The procedures executed by the controlling MCData function prior to sending a response to the inviting MCData client are specified in subclause 9.2.4.4.4." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.4.4.4] "In the procedures in this subclause: 1) MCData ID in an incoming SIP INVITE request refers to the MCData ID of the originating user from the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP INVITE request; 2) group identity in an incoming SIP INVITE request refers to the group identity from the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP INVITE request; and 3) MCData ID in an outgoing SIP INVITE request refers to the MCData ID of the called user in the <mcdata- request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP INVITE request; Upon receipt of a "SIP INVITE request for controlling MCData function for SDS session", the controlling MCData function: … 4) shall cache SIP feature tags, if received in the Contact header field and if the specific feature tags are supported; 6) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [38]; 7) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP INVITE request is set to a value of "one-to-one-sds-session" and the SIP INVITE request: … ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 163 b) contains an application/resource-lists MIME body with exactly one <entry> element, shall invite the MCData user identified by the <entry> element of the MIME body, as specified in subclause 9.2.4.4.3; and c) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 6.3.2; … Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in subclause 9.2.4.4.3 and if the MCData ID in the SIP 200 (OK) response matches to the MCData ID in the corresponding SIP INVITE request the controlling MCData function: 1) shall generate SIP 200 (OK) response to the SIP INVITE request according to 3GPP TS 24.229 [5]; 2) shall include the option tag "timer" in a Require header field; 3) shall include the Session-Expires header field and start supervising the SIP session according to rules and procedures of IETF RFC 4028 [38], "UAS Behavior". The "refresher" parameter in the Session-Expires header field shall be set to "uac"; 4) shall include a P-Asserted-Identity header field with the public service identity of the controlling MCData function; 5) shall include a SIP URI for the MCData session identity in the Contact header field identifying the MCData session at the controlling MCData function; 6) shall include the following in the Contact header field: a) the g.3gpp.mcdata.sds media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.sds"; and c) the isfocus media feature tag; 7) shall include Warning header field(s) received in incoming responses to the SIP INVITE request; 8) 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 subclause 9.2.4.4.2; 9) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 6.3.2; and 10) shall send a SIP 200 (OK) response to the inviting MCData client according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.4.4.1] "When composing an SDP offer according to 3GPP TS 24.229 [5], IETF RFC 4975 [17], IETF RFC 6135 [19] and IETF RFC 6714 [20] the controlling MCData function: 1) shall include an "m=message" media-level section for the MCData media stream received from the originating MCData client consisting of: a) the port number; b) a protocol field value of "TCP/MSRP" or "TCP/TLS/MSRP" for TLS; c) an "a=sendrecv" attribute; d) an "a=path" attribute containing its own MSRP URI; e) set the content type as "a=accept-types:application/vnd.3gpp.mcdata-signalling application/vnd.3gpp.mcdata-payload"; and f) set the a=setup attribute as "actpass"." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 164 [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.4.4.2] "When composing the SDP answer according to 3GPP TS 24.229 [5], the controlling MCData function: 1) shall include an "m=message" media-level section for the accepted MCData media stream consisting of: a) the port number; b) a protocol field value of "TCP/MSRP" or "TCP/TLS/MSRP" for TLS according to the received SDP offer; c) an "a=sendrecv" attribute; d) an "a=path" attribute containing its own MSRP URI; e) set the content type as a=accept-types: application/vnd.3gpp.mcdata-signalling application/vnd.3gpp.mcdata-payload; and f) set the a=setup attribute set to "passive" according to IETF RFC 6135 [19]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.2.4.1] "The originating participating MCData function should establish the MSRP session with the originating MCData client as specified in subclause 6.2.2.2." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.2.4.2] "The originating participating MCData function should establish the MSRP session with the controlling MCData function as specified in subclause 6.2.2.3." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.2.4.3] "Upon receiving an MSRP SEND request from the originating MCData client, the originating participating MCData function: 1. if an MSRP connection is not established with the controlling MCData function then, shall establish the MSRP connection as specified in subclause 6.2.2.4.2. Otherwise, shall use the existing MSRP connection; and 2. shall forward the received MSRP SEND request to the controlling MCData function according to the rules and procedures of IETF RFC 4975 [11]. Upon receiving an MSRP 200 (OK) response from the controlling MCData function, the participating MCData function shall forward the MSRP 200 (OK) response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]. Upon receiving an error MSRP response from the controlling MCData function, the participating MCData function shall forward the error MSRP response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.2.5.1] "The terminating participating MCData function should establish the MSRP session with the controlling MCData function as specified in subclause 6.2.2.2." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.2.5.2] "The terminating participating MCData function should establish MSRP session to terminating MCData client as specified in subclause 6.2.2.3." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.2.5.3] "Upon receiving an MSRP SEND request from the controlling MCData function, the terminating participating MCData function: 1. shall generate and send a MSRP 200 (OK) response for the received MSRP SEND request to the controlling MCData function, according to the rules and procedures of IETF RFC 4975 [11]; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 165 2. shall forward the received MSRP SEND request to the terminating MCData client according to the rules and procedures of IETF RFC 4975 [11]. Upon receiving an error MSRP response from the terminating MCData client, the participating MCData function shall forward the error MSRP response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.2.2] "To receive a SDS message over MSRP, the participating MCData function: 1. shall act according to IETF RFC 6135 [12], as: a. an "passive" endpoint, if a=setup attribute in the sent SDP answer was set to "passive"; and b. an "active" endpoint, if a=setup attribute in the sent SDP answer was set to "active"; and 2. shall establish an MSRP connection according to the MSRP connection parameters in the sent SDP answer response as described in IETF RFC 4976 [14]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.2.3] "To send a SDS message over MSRP, the participating MCData function: 1. shall act according to IETF RFC 6135 [12], as: a. an "active" endpoint, if a=setup attribute in the received SDP answer is set to "passive"; and b. an "passive" endpoint, if a=setup attribute in the received SDP answer is set to "active"; and 2. shall establish the MSRP connection according to the MSRP connection parameters in the received SDP answer response as described in IETF RFC 4976 [14]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.3.2.2.1] "To establish the MSRP connection with the originating MCData client, the controlling MCData function performs below procedures: 1. shall act as an MSRP client and establish TLS connection with the originating participating MCData function, if exists, otherwise the originating MCData client, according to the rules and procedures as described in IETF RFC 4975 [11]; 2. shall act as an MSRP client to send MSRP SEND requests according to the rules and procedures described in IETF RFC 6135 [12]; 3. shall act as an "passive" endpoint according to the rules and procedures described in IETF RFC 6135 [12]; 4. shall establish the MSRP connection with originating MCData client, according to the rules and procedures described in IETF RFC 6135 [12]; and 5. acting as a "passive" endpoint, shall wait for MSRP SEND request on established MSRP connection, to bind the MSRP connection to the MSRP session according to the rules and procedures of IETF RFC 4975 [11] and IETF RFC 6135 [12]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.3.2.2.2] "To establish the MSRP connection with the terminating MCData client, the controlling MCData function performs below procedures: 1. shall act as an MSRP client and establish TLS connection with the terminating participating MCData function, if exists, otherwise the terminating MCData client, according to the rules and procedures as described in IETF RFC 4975 [11]; 2. shall act as an MSRP client to send MSRP SEND requests according to the rules and procedures described in IETF RFC 6135 [12]; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 166 3. shall act according to IETF RFC 6135 [12], as: a. an "active" endpoint, if a=setup attribute in the received SDP answer is set to "passive"; and b. an "passive" endpoint, if a=setup attribute in the received SDP answer is set to "active"; 4. shall establish the MSRP connection with each terminating MCData client identified in the 3GPP TS 24.282 [8], according to the rules and procedures described in IETF RFC 6135 [12]; and 5. if acting as an "active" endpoint, shall send an empty MSRP SEND request on each established MSRP connection, to bind the MSRP connection to the MSRP session according to the rules and procedures of IETF RFC 4975 [11] and IETF RFC 6135 [12]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.3.2.3] "Upon receiving a MSRP SEND request from the originating participating MCData function, the controlling MCData function: 1. shall generate and send a MSRP 200 (OK) response for the received MSRP SEND requests to the originating participating MCData function, according to the rules and procedures of IETF RFC 4975 [11]; and 2. shall forward the received MSRP SEND requests to each terminating MCData client with which a successful MSRP connection was established, according to the rules and procedures of IETF RFC 4975 [11]. Following clarifications apply to the generated MSRP SEND request: a. shall modify the To-Path header according to the MSRP URI received in the answer SDP from the MCData client in accordance with rules and procedures of IETF RFC 4975 [11]; and b. shall modify the From-Path header to the controlling MCData function's own MSRP URI, according to the rules and procedures of IETF RFC 4975 [11]." |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.3.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.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 Storage Function, the MCData User Database, the SIP AS, the HTP Server, the HTTP Client, the MSRP TCP Server and the MSRP TCP Client. - The IUT (MCData Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCData Server) is connected to PLMN1. - 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) 167 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.3.3.2 Test procedure sequence | Table 6.1.3.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Establishment' as described in Annex A, Table A.4.3.3-1 to establish a media plane connection between SS-UE1 (MCData Client) and SS-UE2 (MCData Client)? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MSRP message transfer' as described in Annex A, Table A.4.4.3-1 to forward a SDS message from SS-UE1 (MCData client) to SS-UE2 (MCData Client), with disposition request "DELIVERY"? - - 2 P 3 Check: Does the MCData Server (IUT) correctly perform procedure'E2E MSRP message transfer' as described in Annex A, Table A.4.4.3-1 to forward a disposition notification of "DELIVERED", from SS-UE2 (MCData client) to SS-UE1 (MCData Client)? - - 3 P 4 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MSRP message transfer' as described in Annex A, Table A.4.4.3-1 to forward a SDS message from SS-UE2 (MCData client) to SS-UE1 (MCData Client), with disposition request "READ"? - - 4 P 5 Check: Does the MCData Server (IUT) correctly perform procedure'E2E MSRP message transfer' as described in Annex A, Table A.4.4.3-1 to forward a disposition notification of "READ", from SS-UE1 (MCData client) to SS-UE2 (MCData Client)? - - 5 P 6 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Release' as described in Annex A, Table A.4.5.3-1? - - 6 P |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.3.3.3 Specific message contents | Table 6.1.3.3.3-1: SIP INVITE from the SS-UE1 (Step 1, Table 6.1.3.3.2-1; Step 1, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.9.3.3-1 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 6.1.3.3.3-2 MIME body part MCData-Info MIME-part-body MCData-Info as described in Table ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.9.3.3-3 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 168 Table 6.1.3.3.3-2: SDP for SIP INVITE (Table 6.1.3.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.9.3.3-2 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-UE1 The transport port to which the media stream is sent Connection Data c= line connection-address IP address of the SS-UE1 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-UE1 port same value as in the media line session id assigned by the SS-UE1 transport "tcp" URI-parameter not present media attribute a= line attribute = key-mgmt key-mgmt mikey MIKEY-SAKKE I_MESSAGE as specified in Table 6.1.3.3.3-2A Table 6.1.3.3.3-2A: MIKEY-SAKKE I_MESSAGE (Table 6.1.3.3.3-2) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.9.1-2 Information Element Value/remark Comment Reference Condition IDRi payload ID data px_MCPTT_ID_User_A MCPTT ID associated with the initiating user IDRr payload ID data px_MCPTT_ID_User_B MCPTT ID associated to the receiving user ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 169 Table 6.1.3.3.3-3: SIP INVITE from the MCData Server (IUT) to the SS-UE2 (Step 1, Table 6.1.3.3.2-1; Step 2, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.10.3.3-1 Information Element Value/remark Comment Reference Condition To addr-spec user-info and host px_MCX_SIP_PublicUserId_B Max-Forwards value any allowed value Session-Expires generic-param any allowed value Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.1.3.3.3-4 MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.1.3.3.3-5 Table 6.1.3.3.3-4: SDP for SIP INVITE (Table 6.1.3.3.3-4) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.10.3.3-2 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 Session attribute present only if there is no key- mgmt media attribute in the media description for data a= line attribute = key-mgmt key-mgmt mikey MIKEY-SAKKE I_MESSAGE as specified in Table 6.1.3.3.3-2A 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 170 Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.10.3.3-2 Information Element Value/remark Comment Reference Condition 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 present only if there is no key- mgmt attribute at session level key-mgmt mikey MIKEY-SAKKE I_MESSAGE as specified in Table 6.1.3.3.3-2A Table 6.1.3.3.3-5: MCData-Info (Table 6.1.3.3.3-3) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.10.3.3-3 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params mcdata-request-uri Encrypted <mcdata-request-uri> with mcdataURI set to px_MCData_ID_User_B Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A mcdata-calling-user-id Encrypted <mcdata-calling-user- id> with mcdataURI set to px_MCData_ID_User_A Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A request-type "one-to-one-sds-session" Table 6.1.3.3.3-6: SIP 200 (OK) from the SS-UE2 (Step 1, Table 6.1.3.3.2-1; Step 4, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.10.3.3-4 Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.1.3.3.3-7 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 171 Table 6.1.3.3.3-7: SDP for SIP 200 (OK) (Table 6.1.3.3.3-6) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.10.3.3-5 Information Element Value/remark Comment Reference Condition Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "22222222" 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 "22222222" 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-UE2 The transport port to which the media stream is sent Connection Data c= line connection-address IP address of the SS-UE2 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-UE2 port same value as in the media line session id assigned by the SS-UE2 transport "tcp" URI-parameter not present Table 6.1.3.3.3-8: SIP 200 (OK) from the MCData Server (IUT) to SS-UE1 (Step 1, Table 6.1.3.3.2-1; Step 5, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.9.3.3-4 Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.1.3.3.3-9 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 172 Table 6.1.3.3.3-9: SDP for SIP 200 (OK) (Table 6.1.3.3.3-8) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.9.3.3-5 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 Table 6.1.3.3.3-10: MSRP SEND from the SS-UE1 (Step 2, Table 6.1.3.3.2-1; Step 1, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.9.3.3-6 Information Element Value/remark Comment Reference Condition data Message or chunk of message as specified in table 6.1.3.3.3-10A IETF RFC 3261 [21] ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 173 Table 6.1.3.3.3-10A: MIME Message (Table 6.1.3.3.3-10) Derivation Path: IETF RFC 2046 [18] Information Element Value/remark Comment Reference Condition MIME body part MCData Data signalling message MIME-part-headers Content-Type "application/vnd.3gpp.mcdata- signalling" MIME-part-body MCData Protected Payload Message containing SDS SIGNALLING PAYLOAD as described in table 6.1.2.3.3-10B MIME body part MCData Data message MIME-part-headers Content-Type "application/vnd.3gpp.mcdata- payload" MIME-part-body MCData Protected Payload Message containing DATA PAYLOAD as described in Table 6.1.2.3.3-10C Table 6.1.3.3.3-10B: SDS SIGNALLING PAYLOAD (Table 6.1.3.3.3-10A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.8.2-1, condition DELIVERED Table 6.1.3.3.3-10C: Data Payload (Table 6.1.3.3.3-10A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.9.2-2 Table 6.1.3.3.3-11: MSRP SEND from the MCData Server (IUT) to SS-UE2 (Step 2, Table 6.1.3.3.2-1; Step 3, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.10.3.3-6 Table 6.1.3.3.3-12: MSRP SEND from the SS-UE2 (Step 3, Table 6.1.3.3.2-1; Step 1, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.10.3.3-8 Information Element Value/remark Comment Reference Condition data MCData Protected Payload Message containing SDS NOTIFICATION as specified in Table 6.1.3.3.3-13 Table 6.1.3.3.3-13: SDS SIGNALLING PAYLOAD (Table 6.1.3.3.3-12) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.8.4-1, condition DELIVERED Table 6.1.3.3.3-14: MSRP SEND from the MCData Server (IUT) to SS-UE1 (Step 3, Table 6.1.3.3.2-1; Step 3, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.9.3.3-10 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 174 Table 6.1.3.3.3-15: MSRP SEND from the SS-UE2 (Step 4, Table 6.1.3.3.2-1; Step 1, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.10.3.3-10 Information Element Value/remark Comment Reference Condition data Message or chunk of message as specified in Table 6.1.3.3.3-15A IETF RFC 3261 [21] Table 6.1.3.3.3-15A: MIME Message (Table 6.1.3.3.3-15) Derivation Path: IETF RFC 2046 [18] Information Element Value/remark Comment Reference Condition MIME body part MCData Data signalling message MIME-part-headers Content-Type "application/vnd.3gpp.mcdata- signalling" MIME-part-body MCData Protected Payload Message containing SDS SIGNALLING PAYLOAD as described in Table 6.1.2.3.3-15B MIME body part MCData Data message MIME-part-headers Content-Type "application/vnd.3gpp.mcdata- payload" MIME-part-body MCData Protected Payload Message containing DATA PAYLOAD as described in Table 6.1.2.3.3-10C Table 6.1.3.3.3-15B: SDS SIGNALLING PAYLOAD (Table 6.1.3.3.3-15A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.8.2-1, condition READ Table 6.1.3.3.3-16: MSRP SEND from the MCData Server (IUT) to SS-UE1 (Step 4, Table 6.1.3.3.2-1; Step 3, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.9.3.3-12 Table 6.1.3.3.3-17: MSRP SEND from the SS-UE1 (Step 5, Table 6.1.3.3.2-1; Step 1, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.9.3.3-14 Information Element Value/remark Comment Reference Condition data MCData Protected Payload Message containing SDS NOTIFICATION as specified in Table 6.1.3.3.3-18 Table 6.1.3.3.3-18: SDS SIGNALLING PAYLOAD (Table 6.1.3.3.3-17) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.8.4-1, condition READ Table 6.1.3.3.3-19: MSRP SEND from the MCData Server (IUT) to SS-UE2 (Step 5, Table 6.1.3.3.2-1; Step 3, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.10.3.3-15 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 175 6.1.4 MCDATA Server - MCDATA Client / Short Data Service (SDS) / Standalone SDS Using Media Plane / One-to-one Standalone SDS / Pre-established session |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 and having established a pre-established session with the clients} ensure that { when { the SS-UE1 (MCData Client) requests the call establishment using a pre-established session with SIP REFER message } then { IUT (MCData Server) responds with a SIP 200 (OK) and establishes the call and responds/forwards empty MSRP messages } } (2) with { IUT (MCData Server) having established a pre-established session with the clients } ensure that { when { the SS-UE1 (MCData Client) sends an MSRP SEND message with disposition request "DELIVERY"} then { IUT (MCData Server) forwards an MSRP SEND message to UE2 (MCData Client) and responds with an MSRP 200 (Ok) to UE1 (MCData Client) } } (3) with { IUT (MCData Server) having established a pre-established session with the clients } ensure that { when { the SS-UE1 (MCData Client) requests the call release keeping the pre-established with SIP REFER message } then { IUT (MCData Server) responds with a SIP 200 (OK) and releases the SS-UE2 (MCData Client) } } (4) with { IUT (MCData Server) having established a pre-established session with the clients } ensure that { when { SS-UE2 (MCData Client) sends a disposition notification "DELIVERED" by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 18.3.2.2, 18.3.3.1.2, 18.3.3.2.2, 9.2.5.2.2.1, 9.2.5.2.2.2, 9.2.5.4.2.1, 9.2.5.4.2.2, 9.2.5.1.1, 9.2.5.1.2, 9.2.5.1.3, ETSI TS 124 582 [40] (3GPP TS 24.582), clauses 12.2, 6.2.1.4.1, 6.2.1.4.2, 6.2.1.4.3, 6.2.1.5.1, 6.2.1.5.2, 6.2.1.5.3, 6.2.1.2, 6.2.1.3, 6.3.1.2.1, 6.3.1.2.2, 6.3.1.3. Unless otherwise stated, these are Rel-16 requirements. [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: … 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"; … ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 176 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 TS 124 282 [13] (3GPP TS 24.282), clause 18.3.3.1.2] "Upon receiving a SIP BYE request from the participating MCData function within a pre-established session the MCData client shall check whether there are any MCData sessions using the pre-established session, and: 1) if there is an established MCData session then the MCData client shall remove the MCData client from the MCData session by performing the procedures for session release for each MCData session as specified in 3GPP TS 24.582 [15]; and 2) if there is no MCData session using the pre-established session, then the MCData client shall follow the procedure described in subclause 13.2.3.2.2." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 18.3.3.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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 177 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 9.2.5.2.2.1] "Upon receiving a SIP REFER request, with: 1) the Request-URI set to a public service identity identifying the pre-established session on the participating MCData function; 2) the Refer-To header field containing a Content-ID ("cid") URL as specified in IETF RFC 2392 [33] that points to an application/resource-lists MIME body as specified in IETF RFC 5366 [18] containing one or more <entry> element(s) with a "uri" attribute containing a SIP URI set to the MCData ID of the called user(s); 3) an hname "body" parameter in the headers portion of the SIP URI specified above containing an application/vnd.3gpp.mcdata-info MIME body with the <request-type> element set to "one-to-one-sds" or "one-to-one-sds-session"; and 4) a Content-ID header field set to the "cid" URL; the participating function: … 2) shall determine the MCData ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP REFER request; … 4) shall determine whether the MCData user identified by the MCData ID is authorised for MCData communications by following the procedures in subclause 11.1; … 6) if the received SIP REFER request contains an application/resource-lists MIME body referenced by a "cid" URL in the Refer-To header field with more than one <entry> element each with an application/vnd.3gpp.mcdata-info MIME body with the <request-type> element set to "one-to-one-sds" or "one-to-one-sds-session", determine that the communication type is one-to-one standalone SDS or one-to-one SDS session; 7) shall determine the public service identity of the controlling MCData function associated with the originating user's MCData ID; … 8) if the SIP REFER request contained a Refer-Sub header field containing "false" value and a Supported header field containing "norefersub" value, shall handle the SIP REFER request as specified in 3GPP TS 24.229 [5], IETF RFC 3515 [51] as updated by IETF RFC 6665 [36], and IETF RFC 4488 [53] without establishing an implicit subscription; 9) shall generate a final SIP 200 (OK) response to the SIP REFER request according to 3GPP TS 24.229 [5]; NOTE: In accordance with IETF RFC 4488 [53], the participating MCData function inserts the Refer-Sub header field containing the value "false" in the SIP 200 (OK) response to the SIP REFER request to indicate that it has not created an implicit subscription. 10) shall send the response to the SIP REFER request towards the MCData client according to 3GPP TS 24.229 [5]; 11) shall generate SIP INVITE request as described in subclause 9.2.5.1.1; 12) shall set the Request-URI of the SIP INVITE request to the public service identity of the controlling MCData function serving the calling MCData user as determined above in step 7); and 13) shall forward the SIP INVITE request according to 3GPP TS 24.229 [4]. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 178 Upon receiving a SIP 200 (OK) response for the SIP INVITE request the participating MCData function: 1) shall interact with the media plane as specified in 3GPP TS 24.582 [15]; 2) shall generate a SIP re-INVITE request as specified in subclause 9.2.5.1.2 with following clarifications: i) shall set the Request-URI to a public service identity identifying the pre-established session; 3) shall send the SIP re-INVITE request towards the originating MCData client according to 3GPP TS 24.229 [5]; and 4) upon receipt of a SIP 2xx response to the SIP re-INVITE, shall interact with the media plane as specified in 3GPP TS 24.582 [15]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.5.2.2.2] "Upon receipt of a "SIP INVITE request for standalone SDS over media plane for terminating participating MCData function" or "SIP INVITE request for SDS session for terminating participating MCData function", the participating MCData function: … 2) shall use the MCData ID present in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCData ID and public user identity; .. 3) shall generate a SIP re-INVITE request as specified in subclause 9.2.5.1.3 with following clarifications: i) shall set the Request-URI to a public service identity identifying the pre-established session; ii) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcdata-info+xml MIME body, shall copy the application/vnd.3gpp.mcdata-info+xml MIME body to the outgoing SIP INVITE request with following clarification: a) shall include <mcdata-communication-state> element with a value set to "establish-request"; and iii) shall include the following in the Contact header field: a) the g.3gpp.mcdata.sds media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.sds"; c) the isfocus media feature tag; d) an MCData session identity mapped to the MCData session identity provided in the Contact header field of the incoming SIP INVITE request; and e) any other uri-parameter provided in the Contact header field of the incoming SIP INVITE request; 4) shall send the SIP re-INVITE request towards the terminating MCData client according to 3GPP TS 24.229 [5]; and 5) upon receipt of a SIP 2xx response to the SIP re-INVITE, shall interact with the media plane as specified in 3GPP TS 24.582 [15]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.5.4.2.1] "Upon receiving a SIP REFER request with the "method" SIP URI parameter set to value "BYE" in the URI in the Refer-To header field from the MCData client, the participating MCData function: 1) shall determine the MCData ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP REFER request; … ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 179 3) if the SIP REFER request contained a Refer-Sub header field containing "false" value and a Supported header field containing "norefersub" value, shall handle the SIP REFER request as specified in 3GPP TS 24.229 [5], IETF RFC 3515 [53] as updated by IETF RFC 6665 [36], and IETF RFC 4488 [53] without establishing an implicit subscription; 4) shall generate a SIP 200 (OK) response to the SIP REFER request, and in the SIP 200 (OK) response: a) shall include the Supported header field with value "norefersub" according to rules and procedures of IETF RFC 4488 [53]; and b) shall check the presence of the Refer-Sub header field of the SIP REFER request and if it is present and set to the value "false" shall include the Refer-Sub header field with value "false" according to rules and procedures of IETF RFC 4488 [53]; 5) shall send the SIP 200 (OK) response to the SIP REFER request towards MCData client according to 3GPP TS 24.229 [5]; 6) shall generate a SIP BYE request, and in the SIP BYE request: a) shall set the Request-URI to the MCData session identity which was included at the Refer-To header field of the received REFER request; and b) shall copy the contents of the P-Asserted-Identity header field of the received REFER request to the P- Asserted-Identity header field of the outgoing SIP BYE request; and 7) shall send the SIP BYE request toward the controlling MCData function according to 3GPP TS 24.229 [5]. Upon receiving a SIP 200 (OK) response to the SIP BYE request the participating MCData function shall interact with the media plane as specified in 3GPP TS 24.582 [15] for releasing media plane resources associated with the SIP session with the controlling MCData function. The participating MCData function shall generate a SIP re-INVITE request as specified in subclause 9.2.5.1.2 with following clarifications and send the request towards the originating MCData client according to 3GPP TS 24.229 [5]: 1) shall set the Request-URI to a public service identity identifying the pre-established session; and 2) shall set the <mcdata-communication-state> element with a value of "terminated"." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.5.4.2.2] "Upon receiving a SIP BYE request from the controlling MCData function, the participating MCData function: 1) shall interact with the media plane as specified in 3GPP TS 24.582 [15]; 2) shall send a SIP 200 (OK) response to the controlling MCData function; 3) shall generate a SIP re-INVITE request as specified in subclause 9.2.5.1.2 with following clarifications: i) shall set the Request-URI to a public service identity identifying the pre-established session; and ii) shall set the <mcdata-communication-state> element with a value of "terminate-request"; 4) shall send the SIP re-INVITE request towards the originating MCData client according to 3GPP TS 24.229 [5]; and 5) upon receipt of a SIP 2xx response to the SIP re-INVITE, shall interact with the media plane as specified in 3GPP TS 24.582 [15]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.5.1.1] "This subclause is referenced from other procedures. When generating an initial SIP INVITE request according to 3GPP TS 24.229 [5], on receipt of an incoming SIP REFER request, the participating MCData function: 1) shall include in the SIP INVITE request all header fields included in the headers portion of the SIP URI contained in the <entry> element of the application/resource-lists MIME body, referenced by the "cid" URL in the Refer-To header field in the incoming SIP REFER request; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 180 2) should include the Session-Expires header field according to IETF RFC 4028 [38]. 3) shall include the option tag "timer" in the Supported header field; 4) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP REFER request to the P- Asserted-Identity header field of the outgoing SIP INVITE request; 5) shall include the g.3gpp.mcdata.sds media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" into the Contact header field of the outgoing SIP INVITE request; 6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; and 7) shall include in the SIP INVITE request the option tag "tdialog" in a Supported header field according to the rules and procedures of IETF RFC 4538 [54]; 8) shall include in the SIP INVITE request an SDP offer as specified in subclause 9.2.3.3.1 based upon: a) the SDP negotiated during the pre-established session establishment and any subsequent pre-established session modification; and b) the SDP offer (if any) included in the"body" URI parameter of the SIP URI contained in the <entry> element of the application/resource-lists MIME body, referenced by the "cid" URL in the Refer-To header field in the incoming SIP REFER request for a pre-established session; 9) shall copy the application/vnd.3gpp.mcdata-info+xml MIME body from the "body" URI parameter of the SIP URI in the application/resource-lists MIME body, referenced by the "cid" URL in the Refer-To header field of the SIP REFER request, to the outgoing SIP INVITE request; 9A) if the incoming SIP REFER request contained a <functional-alias-URI> element in an application/vnd.3gpp.mcdata-info+xml MIME body in the hname "body" parameter in the headers portion of the SIP URI in the Refer-To header field, shall check if the status of the functional alias is activated for the MCData ID. If the functional alias status is activated, then the participating MCData function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request to the received value, otherwise shall not include a <functional-alias-URI> element; and 10) if the incoming SIP REFER request contained an application/resource-lists MIME body in the "body" URI parameter of the SIP URI contained in the <entry> element of an application/resource-lists MIME body, referenced by the "cid" URL in the Refer-To header field, shall copy the application/resources-lists MIME body in the "body" URI parameter to the SIP INVITE request." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.5.1.2] "This subclause is referenced from other procedures. The participating MCData function: 1) shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [5] to be sent within the SIP dialog of the pre-established session; 2) shall include in the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing Re-INVITE request: a) the <mcdata-communication-state> element with a value set to "establish-success", if a SIP 2xx response is received to a SIP INVITE request sent to the controlling MCData function; or b) the <mcdata-communication-state> element with a value set to "establish-fail", if an error response is received to a SIP INVITE request sent to the controlling MCData function;" [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.5.1.3] "This subclause is referenced from other procedures. The participating MCData function: ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 181 1) shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [5] to be sent within the SIP dialog of the pre-established session; 2) should include the Session-Expires header field according to IETF RFC 4028 [38]. 3) shall include the option tag "timer" in the Supported header field; 4) shall include an Accept-Contact header field containing the g.3gpp.mcdata.sds media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [8]; 5) 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.mcdata.sds" along with parameters "require" and "explicit" according to IETF RFC 3841 [8]; 6) shall include in the Contact header field an MCData session identity for the MCData session with the g.3gpp.mcdata.sds media feature tag, the isfocus media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" according to IETF RFC 3840 [16];" [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 12.2] "Upon establishing one-to-one or group SDS using media plane or one-to-one or group SDS session using pre- established call, the participating MCData function shall follow the procedure as described in subclause 6.2." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.4.1] "The originating participating MCData function should establish the MSRP session with the originating MCData client as specified in subclause 6.2.1.2." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.4.2] "The originating participating MCData function should establish the MSRP session with the controlling MCData function as specified in subclause 6.2.1.3." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.4.3] "Upon receiving an MSRP SEND request from the originating MCData client, the originating participating MCData function: 1. if in a standalone one-to-one SDS using media plane, shall verify the SDS message size is less than or equal to <MacData1To1> element of the MCData user profile document for the originating MCData client (see the MCData user profile document in 3GPP TS 24.484 [7]); 2. if the verifications in 1 above fails, shall send the MSRP response with the error code 403 to the originating MCData client and shall not continue with the rest of the procedure; 3. if an MSRP connection is not established with the controlling MCData function then, shall establish the MSRP connection as specified in subclause 6.2.1.4.2. Otherwise, shall use the existing MSRP connection; and 4. shall forward the received MSRP SEND request to the controlling MCData function according to the rules and procedures of IETF RFC 4975 [11]. Upon receiving an MSRP 200 (OK) response from the controlling MCData function, the participating MCData function shall forward the MSRP 200 (OK) response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]. Upon receiving an error MSRP response from the controlling MCData function, the participating MCData function shall forward the error MSRP response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.5.1] "The terminating participating MCData function should establish the MSRP session with the controlling MCData function as specified in subclause 6.2.1.2." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 182 [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.5.2] "The terminating participating MCData function should establish MSRP session to terminating MCData client as specified in subclause 6.2.1.3." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.5.3] "Upon receiving an MSRP SEND request from the controlling MCData function, the terminating participating MCData function: 1. shall generate and send a MSRP 200 (OK) response for the received MSRP SEND request to the controlling MCData function, according to the rules and procedures of IETF RFC 4975 [11]; and 2. shall forward the received MSRP SEND request to the terminating MCData client according to the rules and procedures of IETF RFC 4975 [11]. Upon receiving an error MSRP response from the terminating MCData client, the participating MCData function shall forward the error MSRP response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.2] "To receive a SDS message over MSRP, the participating MCData function: 1. shall act according to IETF RFC 6135 [12], as: a. an "passive" endpoint, if a=setup attribute in the sent SDP answer was set to "passive"; and b. an "active" endpoint, if a=setup attribute in the sent SDP answer was set to "active"; and 2. shall establish an MSRP connection according to the MSRP connection parameters in the sent SDP answer response as described in IETF RFC 4976 [14]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.2.1.3] "To send a SDS message over MSRP, the participating MCData function: 1. shall act according to IETF RFC 6135 [12], as: a. an "active" endpoint, if a=setup attribute in the received SDP answer is set to "passive"; and b. an "passive" endpoint, if a=setup attribute in the received SDP answer is set to "active"; and 2. shall establish the MSRP connection according to the MSRP connection parameters in the received SDP answer response as described in IETF RFC 4976 [14]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.3.1.2.1] "To establish the MSRP connection with the originating MCData client, the controlling MCData function performs below procedures: 1. shall act as an MSRP client and establish TLS connection with the originating participating MCData function, if exists, otherwise the originating MCData client, according to the rules and procedures as described in IETF RFC 4975 [11]; 2. shall act as an MSRP client to send MSRP SEND requests according to the rules and procedures described in IETF RFC 6135 [12]; 3. shall act as an "passive" endpoint according to the rules and procedures described in IETF RFC 6135 [12]; 4. shall establish the MSRP connection with originating MCData client, according to the rules and procedures described in IETF RFC 6135 [12]; and 5. as a passive endpoint, shall wait for MSRP SEND request on established MSRP connection, to bind the MSRP connection to the MSRP session according to the rules and procedures of IETF RFC 4975 [11] and IETF RFC 6135 [12]." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 183 [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.3.1.2.2] "To establish the MSRP connection with the terminating MCData client, the controlling MCData function performs below procedures: 1. shall act as an MSRP client and establish TLS connection with the terminating participating MCData function, if exists, otherwise the terminating MCData client, according to the rules and procedures as described in IETF RFC 4975 [11]; 2. shall act as an MSRP client to send MSRP SEND requests according to the rules and procedures described in IETF RFC 6135 [12]; 3. shall act according to IETF RFC 6135 [12], as: a. an "active" endpoint, if a=setup attribute in the received SDP answer is set to "passive"; and b. an "passive" endpoint, if a=setup attribute in the received SDP answer is set to "active"; 4. shall establish the MSRP connection with each terminating MCData client identified in the 3GPP TS 24.282 [8], according to the rules and procedures described in IETF RFC 6135 [12]; and 5. if acting as an "active" endpoint, shall send an empty MSRP SEND request on each established MSRP connection, to bind the MSRP connection to the MSRP session according to the rules and procedures of IETF RFC 4975 [11] and IETF RFC 6135 [12]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 6.3.1.3] "Upon receiving a MSRP SEND request from the originating participating MCData function, the controlling MCData function: 1. if in a standalone one-to-one SDS using media plane, shall verify the SDS message size is less than or equal to <max-data-size-sds-bytes> element in the MCData service configuration document as specified in 3GPP TS 24.484 [7]; 2. if in a standalone group SDS using media plane shall verify: a. the SDS message size is less than or equal to <mcdata-max-data-in-single-request> element of the MCData group document for the (see the MCData group document in 3GPP TS 24.481 [4]); and b. the SDS message size is less than or equal to <mcdata-on-network-max-data-size-for-SDS> element of the MCData group document (see the MCData group document in 3GPP TS 24.481 [4]); 3. if the verifications in either 1 or 2 a or 2 b above fails, shall send the MSRP response with the error code 403 to the MCData client which sent the SDS message and shall not continue with the rest of the procedure; 4. shall generate and send a MSRP 200 (OK) response for the received MSRP SEND requests to the originating participating MCData function, according to the rules and procedures of IETF RFC 4975 [11]; and 5. shall forward the received MSRP SEND requests to each terminating MCData client with which a successful MSRP connection was established, according to the rules and procedures of IETF RFC 4975 [11]. Following clarifications apply to the generated MSRP SEND request: a. shall modify the To-Path header according to the MSRP URI received in the answer SDP from the MCData client in accordance with rules and procedures of IETF RFC 4975 [11]; and b. shall modify the From-Path header to the controlling MCData function's own MSRP URI, according to the rules and procedures of IETF RFC 4975 [11]." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 184 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.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 Storage Function, the MCData User Database, the SIP AS, the HTP Server, the HTTP Client, the MSRP TCP Server and the MSRP TCP Client. - The IUT (MCData Server) is the acting Participating Server and Controlling Server. Preamble: - The <max-payload-size-sds-cplane-bytes> element of the MCData Service Configuration document shall be set to 0 to force the MCData client to send the data using the media plane. - The IUT (MCData Server) is connected to PLMN1. - 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. - The SS-UE1 (MCData client) and the SS-UE2 (MCData client) perform the Procedure for MCData Pre- established Session Establishment as specified in step 1 on Table 5.4.3.2-1 in clause 5.4. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 185 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.3.2 Test procedure sequence | Table 6.1.4.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Establishment using pre-established session' as described in Annex A, Table A.4.6.3-1 to establish a media plane connection between SS-UE1 (MCData Client) and SS-UE2 (MCData Client)? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MSRP message transfer' as described in Annex A, Table A.4.4.3-1 to forward a SDS message from SS-UE1 (MCData client) to SS-UE2 (MCData Client), with disposition request "DELIVERY"? - - 2 P 3 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Release keeping the pre-established session ' as described in Annex A, Table A.4.7.3-1? - - 3 P 4 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a disposition notification of "DELIVERED", from SS-UE2 (MCData client) to SS-UE1 (MCData Client)? - - 4 P |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.1.4.3.3 Specific message contents | Table 6.1.4.3.3-1: SIP REFER from the SS-UE1 (Step 1, Table 6.1.4.3.2-1; Step 1, Annex A, Table A.4.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.12-1 Information Element Value/remark Comment Reference Condition Message-body MIME body part Resource list MIME-part-body Resource-lists as described in Table 6.1.4.3.3-2 Table 6.1.4.3.3-2: Resource-lists in SIP REFER (Table 6.1.4.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3, condition PRE-ESTABLISH, MCD_1to1 with the uri attribute of the entry extended with the SIP URI header fields as specified in Table 6.1.4.3.3-3 Table 6.1.4.3.3-3: SIP URI header fields extending the uri attribute of the resource-lists' single entry (Table 6.1.4.3.3-2) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.12-2 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 6.1.4.3.3-4 MIME body part MCData-Info MIME-part-body MCdata-Info as described in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.13.3.3-5 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 186 Table 6.1.4.3.3-4: SDP in SIP header fields (Table 6.1.4.3.3-3) Derivation Path: Table 5.4.3.3-2, condition MCD_1to1 and NOT SDS_SESSION Table 6.1.4.3.3-5: SIP re-INVITE from the MCData Server (IUT) to the SS-UE2 (Step 1, Table 6.1.4.3.2-1; Step 3, Annex A, Table A.4.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1, condition MCDATA_SDS, re_INVITE Information Element Value/remark Comment Reference Condition Request-Line Request-URI tsc_MCX_SessionID_B session identity of the pre-established session ETSI TS 124 282 [13] (3GPP TS 24.282) clause 9.2.5.2.2.2 Message-body MIME body part SDP message MIME-part-body SDP message as described in Table 6.1.4.3.3-6 MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.1.4.3.3-7 Table 6.1.4.3.3-6: SDP for SIP INVITE (Table 6.1.4.3.3-5) Derivation Path: Table 5.4.3.3-4, condition SDP_OFFER, MCD_1to1, NOT SDP_ANSWER and NOT SDS_SESSION Table 6.1.4.3.3-7: MCData-Info (Table 6.1.4.3.3-5) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.14.3.3-3 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params mcdata-request-uri Encrypted <mcdata- request-uri> with mcdataURI set to px_MCData_ID_User_B Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A mcdata-calling-user-id Encrypted <mcdata- calling-user-id> with mcdataURI set to px_MCData_ID_User_A Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A Table 6.1.4.3.3-8: SIP 200 (OK) from the SS-UE2 (Step 1, Table 6.1.4.3.2-1; Step 5, Annex A, Table A.4.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1, condition INVITE-RSP, MCDATA_SDS Information Element Value/remark Comment Reference Condition Content-Type value "application/sdp" Message-body SDP message As described in Table 6.1.4.3.3-9 Table 6.1.4.3.3-9: SDP for SIP 200 (OK) (Table 6.1.4.3.3-8) Derivation Path: Table 5.4.3.3-2, condition SDP_ANSWER, NOT OFFER and NOT SDS_SESSION ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 187 Table 6.1.4.3.3-10: SIP re-INVITE from the MCData Server (IUT) to the SS-UE1 (Step 1, Table 6.1.4.3.2-1; Step 7, Annex A, Table A.4.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1, condition MCDATA_SDS, re_INVITE Information Element Value/remark Comment Reference Condition Request-Line Request-URI tsc_MCX_SessionID_B session identity of the pre-established session ETSI TS 124 282 [13] (3GPP TS 24.282) clause 9.2.5.2.2.2 Message-body MIME body part not present SDP message MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.1.4.3.3-11 Table 6.1.4.3.3-11: MCData-Info (Table 6.1.4.3.3-10) Derivation Path: Table 5.5.3.2.2-3 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params mcdata-request-uri not present mcdata-calling-user-id not present anyExt mcdata-communication-state "establish-success" ETSI TS 124 282 [13] (3GPP TS 24.282) clause 9.2.5.1.2 Table 6.1.4.3.3-12: SIP 200 (OK) from the SS-UE1 (Step 1, Table 6.1.4.3.2-1; Step 9, Annex A, Table A.4.6.3-1) Derivation Path: Table 5.5.2.17.1.1-1, condition INVITE-RSP, MCDATA_SDS Information Element Value/remark Comment Reference Condition Content-Type not present Message-body not present Table 6.1.4.3.3-13: MSRP SEND from the SS-UE1 (Step 2, Table 6.1.4.3.2-1; Step 1, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.13.3.3-6 Information Element Value/remark Comment Reference Condition data Message or chunk of message as specified in table 6.1.4.3.3-13A IETF RFC 3261 [21] ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 188 Table 6.1.4.3.3-13A: MIME Message (Table 6.1.4.3.3-13) Derivation Path: IETF RFC 2046 [18] Information Element Value/remark Comment Reference Condition MIME body part MCData Data signalling message MIME-part-headers Content-Type "application/vnd.3gpp.mcdata- signalling" MIME-part-body MCData Protected Payload Message containing SDS SIGNALLING PAYLOAD as described in Table 6.1.4.3.3-13B MIME body part MCData Data message MIME-part-headers Content-Type "application/vnd.3gpp.mcdata- payload" MIME-part-body MCData Protected Payload Message containing DATA PAYLOAD as described in Table 6.1.4.3.3-13C Table 6.1.4.3.3-13B: SDS SIGNALLING PAYLOAD (Table 6.1.4.3.3-13A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.8.2-1, condition DELIVERED Table 6.1.4.3.3-13C: Data Payload (Table 6.1.4.3.3-13A) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.9.2-2 Table 6.1.4.3.3-14: MSRP SEND from the MCData Server (IUT) to SS-UE2 (Step 2, Table 6.1.4.3.2-1; Step 3, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.14.3.3-6 Table 6.1.4.3.3-15: SIP MESSAGE from the SS-UE2 (Step 4, Table 6.1.2.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.14.3.3-12 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) The URI of the SS- UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.1.4.3.3-16 MIME body part MCData Data signalling message MIME-part-body MCData Protected Payload Message containing SDS NOTIFICATION as described in Table 6.1.4.3.3-17 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 189 Table 6.1.4.3.3-16: Resource-lists (Table 6.1.4.3.3-15) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3 Information Element Value/remark Comment Reference Condition resource-lists list name attribute display-name entry[1] uri attribute px_MCData_ID_User_A The MCData ID of the target MCData user Table 6.1.4.3.3-17: SDS NOTIFICATION (Table 6.1.4.3.3-15) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.14.3.3-13 Information Element Value/remark Comment Reference Condition Date and time The current date and time The Date and time value is an unsigned integer containing UTC time of the time when a message was sent, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds). ETSI TS 124 282 [13] (3GPP TS 24.282) clause 15.2.8 Table 6.1.4.3.3-18: SIP MESSAGE from the MCData Server (IUT) to SS-UE1 (Step 4, Table 6.1.2.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.1.13.3.3-10 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServic eId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2 File Distribution | 6.2.1 MCDATA Server - MCDATA Client / File Distribution (FD) / FD Using HTTP / One-to-one Standalone FD / Non-Mandatory Download / FILE DOWNLOAD REQUEST ACCEPTED / FILE DOWNLOAD COMPLETED / FILE DOWNLOAD REQUEST REJECTED / FILE DOWNLOAD DEFERRED |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.1.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { SS-UE1 (MCData Client) requests discovery of the absolute URI by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 200 (Ok) to UE1 (MCData Client) } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 190 (2) with { IUT (MCData Server) having requested an one-to-one Standalone FD } ensure that { when { the SS-UE1 (MCData Client) initiates FD "file 1" upload by sending a HTTP POST request } then { IUT (MCData Server) responds with a HTTP 201 (Created) } } (3) with { IUT (MCData Server) having requested an one-to-one Standalone FD } ensure that { when { SS-UE1 (MCData Client) requests FD transfer by sending a SIP MESSAGE message with disposition request "FILE DOWNLOAD COMPLETED UPDATE" } then { IUT (MCData Server) sends a SIP MESSAGE message to UE2 (MCData Client) and responds with a SIP 202 (Accepted) to UE1 (MCData Client) } } (4) with { IUT (MCData Server) having requested an one-to-one Standalone FD } ensure that { when { SS-UE2 (MCData Client) sends a disposition notification "FILE DOWNLOAD REQUEST REJECTED" by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } (5) with { IUT (MCData Server) having requested an one-to-one Standalone FD } ensure that { when { the SS-UE1 (MCData Client) initiates FD "file 2" upload by sending a HTTP POST request } then { IUT (MCData Server) responds with a HTTP 201 (Created) } } (6) with { IUT (MCData Server) having requested an one-to-one Standalone FD } ensure that { when { SS-UE2 (MCData Client) sends a disposition notification "FILE DOWNLOAD DEFERRED" by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } (7) with { IUT (MCData Server) having requested an one-to-one Standalone FD } ensure that { when { SS-UE2 (MCData Client) sends a disposition notification "FILE DOWNLOAD ACCEPTED" by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } (8) with { IUT (MCData Server) having requested an one-to-one Standalone FD } ensure that { when { the SS-UE2 (MCData Client) initiates FD "file 2" download by sending a HTTP GET request } then { IUT (MCData Server) responds with a HTTP 200 (Ok) and SS-UE2 (MCData Client) contains downloaded "file 2" with same content } } (9) with { IUT (MCData Server) having requested an one-to-one Standalone FD } ensure that { when { SS-UE2 (MCData Client) sends a disposition notification "FILE DOWNLOAD COMPLETED" by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 191 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 10.2.4.1, 10.2.4.3.1, 10.2.4.3.2, 10.2.4.4.1, 10.2.4.4.2, 10.2.4.2.1, 10.2.1.2.3, 11.2, 6.2.3.2, 12.2.2.1, 15.2.6. Unless otherwise stated, these are Rel-14 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.1] "The procedures in the subclauses of the parent subclause describe the SIP signalling procedures for: - one-to-one file distribution using HTTP; and - group standalone file distribution using HTTP. When the MCData user wishes to perform file distribution via HTTP, the MCData client: 1) shall check that the file size is less than or equal to the: … b) <max-data-size-fd-bytes> element present in the service configuration document as specified in 3GPP TS 24.484 [12], if the file upload is for a one-to-one file distribution; 2) if the size of the file: a) is acceptable for upload as determined by step 1), shall determine the value of the absolute URI associated with the media storage function of the MCData content server from the <MCDataContentServerURI> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]); b) is not acceptable for upload, shall not continue with the remaining steps in this subclause; 3) shall request the media storage client to upload the file to the media storage function by following the procedures in subclause 10.2.2.1; and 4) shall initiate an FD request containing a file URL as specified in subclause 10.2.4.2.1." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.3.1] "Upon receipt of a "SIP MESSAGE request for FD using HTTP for originating participating MCData function", the participating MCData function: … 2) shall determine the MCData ID of the originating user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request, and shall authorise the calling user; NOTE: 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) if <mcdata-controller-psi> element is present in the application/vnd.3gpp.mcdata-info+xml, shall use its value as public service identity of the controlling MCData function. Otherwise, if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request is: … b) set to a value of "one-to-one-fd", shall determine the public service identity of the controlling MCData function hosting the one-to-one FD using HTTP service for the calling user; … 6) shall determine whether the MCData user identified by the MCData ID is authorised for MCData communications by following the procedures in subclause 11.1; … ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 192 8) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]; 9) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCData function as determined by step 4) in this subclause; 10) shall copy all MIME bodies included in the incoming SIP MESSAGE request to the outgoing SIP MESSAGE request; 10A) if the incoming SIP MESSAGE request contains an application/vnd.3gpp.mcdata-info+xml MIME body that contains a <functional-alias-URI> element, shall check if the status of the functional alias is activated for the MCData ID. If the functional alias status is activated, then the participating MCData function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request to the received value, otherwise shall not include a <functional-alias-URI> element; 11) shall include the MCData ID of the originating user in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP MESSAGE request; 12) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; 13) 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; and 14) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [5]. Upon receipt of a SIP 202 (Accepted) response in response to the SIP MESSAGE request in step 14): 1) shall generate a SIP 202 (Accepted) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 202 (Accepted) response to the MCData client according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the SIP MESSAGE request in step 14): 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 200 (OK) response to the MCData client according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request in step 14) the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the MCData client according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.3.2] "Upon receipt of a: - "SIP MESSAGE request for FD using HTTP for terminating participating MCData function"; or - "SIP MESSAGE network notification for FD using HTTP for terminating participating MCData function"; the participating MCData function: … 2) shall use the MCData ID present in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata- info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCData ID and public user identity of the terminating MCData user; … ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 193 4) if the SIP MESSAGE is a "SIP MESSAGE request for FD using HTTP for terminating participating MCData function", and if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message with a FD disposition request type IE, shall store the value of the Conversation ID IE, the value of the Message ID IE and the payload IE in the FD SIGNALLING PAYLOAD message; 5) if the SIP MESSAGE is a "SIP MESSAGE network notification for FD using HTTP for terminating participating MCData function", and if FD NETWORK NOTIFICATION message within the application/vnd.3gpp.mcdata-signalling MIME body contains an FD notification type IE with value set as "FILE EXPIRED UNAVAILABLE TO DOWNLOAD" as specified in subclause 15.2.6, the file identified using Conversation ID IE shall be removed from the stored file list; 5) shall generate an outgoing SIP MESSAGE request as specified in subclause 6.3.2.1; … 6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and 7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the above SIP MESSAGE request, the participating MCData function: 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 200 (OK) response to the controlling MCData function according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP MESSAGE request, the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the controlling MCData function according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.4.1] "This subclause describes the procedures for sending a SIP MESSAGE from the controlling MCData function and is initiated by the controlling MCData function as a result of an action in subclause 10.2.4.4.2. The controlling MCData function: 1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]; 2) shall include an Accept-Contact header field containing the g.3gpp.mcdata.fd media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request; 3) 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.mcdata.fd" along with parameters "require" and "explicit" according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request; 4) shall copy the following MIME bodies in the received SIP MESSAGE request into the outgoing SIP MESSAGE request by following the guidelines in subclause 6.4: a) application/vnd.3gpp.mcdata-info+xml MIME body; and b) application/vnd.3gpp.mcdata-signalling MIME body; 5) if the application/vnd.3gpp.mcdata-signalling MIME body in the received SIP MESSAGE request contained a FD SIGNALLING PAYLOAD message without the Mandatory download IE included, then: a) shall execute the procedures in subclause 11.2; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 194 b) if the procedures in subclause 11.2 indicate that the mandatory download indication needs to be included,shall include the Mandatory download IE set to a value of "MANDATORY DOWNLOAD" in the FD SIGNALLING PAYLOAD message of the outgoing SIP MESSAGE request; 6) in the application/vnd.3gpp.mcdata-info+xml MIME body: a) shall set the <mcdata-request-uri> element set to the MCData ID of the terminating user; and b) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP MESSAGE request was set to a value of "group-fd", shall set the <mcdata-calling-group-id> element to the group identity; 7) shall set the Request-URI to the public service identity of the terminating participating MCData function associated to the MCData user to be invited; 8) shall copy the public user identity of the calling MCData user from the P-Asserted-Identity header field of the incoming SIP MESSAGE request into the P-Asserted-Identity header field of the outgoing SIP MESSAGE request; 9) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd"; and 10) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.4.2] "The procedures in this subclause are executed upon: - receipt of a "SIP MESSAGE request for FD using HTTP for controlling MCData function", the controlling MCData function; or - a decision to now process a previously received "SIP MESSAGE request for FD using HTTP for controlling MCData function" that had been queued for later transmission; NOTE 1: The controlling MCData function may postpone the continuation of an FD using HTTP procedure by queuing the received "SIP MESSAGE request for FD using HTTP for controlling MCData function". The management of the queue is specified in Annex B of 3GPP TS 23.282 [2]. the controlling MCData function: … 3) if the SIP MESSAGE does not contain: a) an application/vnd.3gpp.mcdata-info+xml MIME body; and b) an application/vnd.3gpp.mcdata-signalling MIME body; … 4) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body contained in the SIP MESSAGE; 5) if the application/vnd.3gpp.mcdata-signalling MIME body does not contain only one FD SIGNALLING PAYLOAD message or FD HTTP TERMINATION message, shall reject the SIP MESSAGE request …, and shall not continue with the rest of the steps in this subclause; 6) if the FD SIGNALLING PAYLOAD message or FD HTTP TERMINATION messagedoes not contain only one Payload IE, shall reject the SIP MESSAGE request …, and shall not continue with the rest of the steps in this subclause; 7) if the Payload IE has Payload contents: a) with a Payload content type set to a value other than "FILEURL" shall reject the SIP MESSAGE request …, and shall not continue with the rest of the steps in this subclause; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 195 b) with Payload data containing a file URL identifying a file that does not exist on the media storage function, shall reject the SIP MESSAGE request …, and shall not continue with the rest of the steps in this subclause; 8) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message with a FD disposition request type IE, shall store the value of the Conversation ID IE and the value of the Message ID IE in the FD SIGNALLING PAYLOAD message; NOTE 2: The controlling MCData function uses the Conversation ID and Message ID for correlation with disposition notifications. 9) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message: a) with a Metadata IE, shall derive a timer value for the file availability timer as the minimum of the file availability information in the metadata and the value contained in the <max-file-availability> element in the MCData service configuration document as specified in 3GPP TS 24.484 [12]; and b) without a Metadata IE, shall derive a timer value for the file availability timer as the value contained in the <default-file-availability> element in the MCData service configuration document as specified in 3GPP TS 24.484 [12]; 10) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request is set to a value of "one-to-one-fd" and the SIP MESSAGE request: … b) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message contains an application/resource-lists MIME body with exactly one <entry> element, shall send a SIP MESSAGE request to the MCData user identified in the <entry> element of the MIME body, as specified in subclause 10.2.4.4.1; … … 13) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message, shall start TDC2 (file availability timer) with the value derived in step 9 of this subclause; 14) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message, shall associate the running timer TDC2 (file availability timer) to the Conversation ID, Message ID, Application ID (if included), and Extended application ID (if included) contained in the FD SIGNALLING PAYLOAD message; NOTE 3: Multiple file availability timers can be running for a file. Each file availability timer is uniquely associated to a Conversation ID and Message ID. 15) shall generate a SIP 202 (Accepted) response in response to the "SIP MESSAGE request for FD using HTTP for controlling MCData function"; and 16) shall send the SIP 202 (Accepted) response towards the originating participating MCData function according to 3GPP TS 24.229 [5]. 17) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD HTTP TERMINATION message and Termination information type IE set to "TERMINATION REQUEST" then: a) shall identify the FILE transmission with Conversation ID and Message ID and "FILE URL". If any ongoing transmission exist then execute procedure described in subclause 12.4.2.1 withfollowing clarifications: i) shall set FD notification type IE as "FILE DELETED UNAVAILABLE TO DOWNLOAD" as specified in subclause 15.2.18; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 196 b) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]. In the generation of the SIP MESSAGE request, the controlling MCData function: i) 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.mcdata.fd" along with parameters "require" and "explicit" according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request; ii) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp- service.ims.icsi.mcdata.fd"; iii) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the participating MCData function associated to the MCData ID of the originating user mentioned in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP MESSAGE request; iv) shall copy the public user identity of the calling MCData user from the P-Asserted-Identity header field of the incoming SIP MESSAGE request into the P-Asserted-Identity header field of the outgoing SIP MESSAGE request; v) shall include an application/vnd.3gpp.mcdata-info+xml MIME body in the SIP MESSAGE request, following the rules specified in subclause 6.4 for the handling of MIME bodies in a SIP message: A) fill <mcdata-request-uri> element from <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml in received SIP MESSAGE; vi) shall generate FD HTTP TERMINATION message as described in subclause 6.3.6.1; vii) shall set the Termination information type IE set to "TERMINATION RESPONSE" as specified in subclause 15.2.22. viii) if clause is successful shall set Release response type IE of FD HTTP TERMINATION MESSAGE to "RELEASE SUCCESS" else set to "RELEASE FAILED" as described in subclause 15.2.23; and ix) shall include in the SIP request, the FD HTTP TERMINATION message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in subclause E.1; c) shall send the SIP MESSAGE request towards the originating participating MCData function as specified in 3GPP TS 24.229 [5]; and 18) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD HTTP TERMINATION message and Termination information type IE set to other than "TERMINATION REQUEST" then follow procedures described on subclause 13.2.5 and subclause 13.2.6." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.2.1] "The MCData client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6] with the clarifications given below. The MCData client: 1) shall build the SIP MESSAGE request as specified in subclause 6.2.4.1; 2) if a one-to-one standalone FD message is to be sent shall insert in the SIP MESSAGE request: a) an application/resource-lists+xml MIME body with the MCData ID of the target MCData user, according to rules and procedures of IETF RFC 4826 [9]; and b) an application/vnd.3gpp.mcdata-info+xml MIME body with: i) a <request-type> element set to a value of "one-to-one-fd"; and ii) if the MCData client is aware of active functional aliases and if an active functional alias is to be included in the SIP MESSAGE request, the <functional-alias-URI> element set to the URI of the used functional alias; … ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 197 4) shall generate a standalone FD message as specified in subclause 6.2.2.2; and 5) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.1.2.3] "The MCData client: 1) if the FD SIGNALLING PAYLOAD message does not contain an Application ID IE and does not contain an Extended application ID IE: a) shall determine that the payload contained in the Payload IE in the FD SIGNALLING PAYLOAD message is for user consumption; b) shall notify the user about the incoming FD request; and c) if the FD SIGNALLING PAYLOAD message contains a Metadata IE, shall deliver the contents of the Metadata IE to the user; 2) if the FD SIGNALLING PAYLOAD message contains an Application ID IE: a) shall determine that the payload contained in the Payload IE in the FD SIGNALLING PAYLOAD message is not for user consumption; b) if the Application ID value is unknown, shall discard the FD message and exit this subclause; c) if the Application ID value is known, shall notify the application of the incoming FD request; and NOTE 1: If FD request is addressed to a non-MCData application that is not running, the MCData client starts the local non-MCData application. d) if the FD SIGNALLING PAYLOAD message contains a Metadata IE, shall deliver the contents of the Metadata IE to the application; 2A) if the FD SIGNALLING PAYLOAD message contains an Extended application ID IE: a) shall determine that the payload contained in the Payload IE in the FD SIGNALLING PAYLOAD message is not for user consumption; b) if the Extended application ID value is unknown, shall discard the FD message and exit this clause; c) if the Extended application ID value is known, shall notify the application of the incoming FD request; and NOTE 2: If the FD request is addressed to a non-MCData application that is not running, the MCData client starts the local non-MCData application. d) if the FD SIGNALLING PAYLOAD message contains a Metadata IE, shall deliver the contents of the Metadata IE to the application; 3) shall start a timer TDU2 (FD non-mandatory download timer) with the timer value as specified in subclause F.2.3; 4) shall wait for the user or application to request to download the file indicated by file URL in the Payload data in the Payload IE in the FD SIGNALLING PAYLOAD message; 5) if the user or application accepts or rejects or decides to defer the FD request, shall stop timer TDU2 (FD non-mandatory download timer); 6) if the user defered the FD request while the timer TDU2 (FD non-mandatory download timer) was running, shall generate an FD NOTIFICATION indicating deferral of the FD request as specified in subclause 12.2.1.1; NOTE 3: Once the timer TDU2 (FD non-mandatory download timer) has expired the FD request can only be accepted or rejected with an appropriate action by the MCData client. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 198 NOTE 4: Once the timer TDU2 (FD non-mandatory download timer) has expired, no action is taken by the MCData client if the FD request is deferred. 7) if the user or application rejects the FD request, shall generate an FD NOTIFICATION indicating rejection of the FD request as specified in subclause 12.2.1.1 and shall exit this subclause; and 8) if the user accepts the FD request: a) shall generate an FD NOTIFICATION indicating acceptance of the FD request as specified in subclause 12.2.1.1; b) if the FD SIGNALLING PAYLOAD message contains a new Conversation ID, shall instantiate a new conversation with the Message ID in the FD SIGNALLING PAYLOAD identifying the first message in the conversation thread; c) if the FD SIGNALLING PAYLOAD message contains an existing Conversation ID and: i) if the FD SIGNALLING PAYLOAD message does not contain an InReplyTo message ID, shall use the Message ID in the FD SIGNALLING PAYLOAD to identify a new message in the existing conversation thread; and ii) if the FD SIGNALLING PAYLOAD message contains an InReplyTo message ID, shall associate the message to an existing message in the conversation thread as identified by the InReplyTo message ID in the FD SIGNALLING PAYLOAD, and use the Message ID in the FD SIGNALLING PAYLOAD to identify the new message; d) may store the Conversation ID, Message ID, InReplyTo message ID and Date and time in local storage; e) shall attempt to download the file as identified by the file URL in the Payload IE in the FD SIGNALLING PAYLOAD message, as specified in subclause 10.2.3.1; and f) if the received FD SIGNALLING PAYLOAD message contains an FD disposition request type IE requesting a file download completed update, then after the file download has been successfully downloaded, shall generate an FD NOTIFICATION by following the procedures in subclause 12.2.1.1." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 11.2] "If the controlling MCData function receives a one-to-one file distribution using HTTP or a group standalone file distribution using HTTP without the mandatory download indication the controlling MCData function: 1) if the file distribution request contained metadata, shall retrieve the filesize contained in the fileselector of the Metadata IE in the FD request; 2) if the file distribution request did not contain metadata, shall determine the size of the file referenced by the file URL contained in FD request; 3) for one-to-one file distribution using HTTP, shall determine if the filesize is less than or equal to the value contained in the <max-data-size-auto-recv-bytes> element of the MCData service configuration document as specified in 3GPP TS 24.484 [12]; … 5) ifcondition 3) or 4) is true, shall determine that the mandatory download indication needs to be included in the file distribution request sent to the terminating MCData client;" [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 6.2.3.2] "In order to generate an FD notification, the MCData client: 1) shall generate an FD NOTIFICATION message as specified in subclause 15.1.6; and 2) shall include in the SIP request, the FD NOTIFICATION message in an application/vnd.3gpp.mcdata- signalling MIME body as specified in subclause E.1. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 199 When generating an FD NOTIFICATION message as specified in subclause 15.1.6, the MCData client: 1) if sending a file download accept notification, shall set the FD disposition notification type IE as "FILE DOWNLOAD REQUEST ACCEPTED" as specified in subclause 15.2.6; 2) if sending a file download reject notification, shall set the FD disposition notification type IE as "FILE DOWNLOAD REQUEST REJECTED" as specified in subclause 15.2.6; 3) if sending a file download deferred notification, shall set the FD disposition notification type IE as "FILE DOWNLOAD REQUEST DEFERRED" as specified in subclause 15.2.6; 4) shall set the Conversation ID to the value of the Conversation ID that was received in the FD message as specified in subclause 15.2.9; 5) shall set the Date and time IE to the current time as specified in subclause 15.2.8; and 6) if sending a file download completed notification: a) shall set the FD disposition notification type IE as "FILE DOWNLOAD COMPLETED" as specified in subclause 15.2.6; b) shall set the Message ID to the value of the Message ID that was received in the FD message as specified in subclause 15.2.10; c) if the FD message was destined for the user, shall not include an Application ID IE as specified in subclause 15.2.7 and shall not include a Extended application ID IE as specified in subclause 15.2.24; and d) if the FD message was destined for an application, shall include: i) an Application ID IE set to the value of the Application ID that was included in the FD message as specified in subclause 15.2.3; or ii) an Extended application ID IE set to the value of the Extended application ID that was included in the FD message as specified in subclause 15.2.24." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.2.1] "Upon receipt of a: - "SIP MESSAGE request for SDS disposition notification for MCData server"; or - "SIP MESSAGE request for FD disposition notification for MCData server"; the participating MCData function: … 2) shall determine the MCData ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request; NOTE: 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. … 7) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]; 8) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCData function; NOTE: How the participating MCData function determines the controlling MCData function to forward notification message is out of scope of the present document. 9) shall copy all MIME bodies included in the incoming SIP MESSAGE request to the outgoing SIP MESSAGE request; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 200 10) if not already included as part of step 8) above, shall include an application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP MESSAGE request, containing an <mcdata-calling-user-id> element set to the MCData ID of the originating user; … 12) if the SIP MESSAGE is a "SIP MESSAGE request for FD disposition notification for MCData server ", shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; 13) if the SIP MESSAGE is a "SIP MESSAGE request for FD disposition notification for MCData server", and the FD disposition notification type IE is set as "FILE DOWNLOAD REQUEST ACCEPTED" or "FILE DOWNLOAD REQUEST REJECTED"as specified in subclause 15.2.6, shall remove the file from the stored file list; 14) 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; and 15) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [5]. Upon receipt of a SIP 202 (Accepted) response in response to the above SIP MESSAGE request, the participating MCData function: 1) shall generate a SIP 202 (Accepted) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 202 (Accepted) response to the MCData client according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the above SIP MESSAGE request, the participating MCData function: 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 200 (OK) response to the MCData client according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP MESSAGE request, the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the MCData client according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 15.2.6] "The purpose of the FD disposition notification type information element is to identify the type of FD disposition notification sent from receiver to the sender. The value part of the FD disposition notification type information element is coded as shown in Table 15.2.6-1. The FD disposition notification type information element is a type 3 information element with a length of 1 octet. Table 15.2.6.1: FD disposition notification type Bits 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 1 FILE DOWNLOAD REQUEST ACCEPTED 0 0 0 0 0 0 1 0 FILE DOWNLOAD REQUEST REJECTED 0 0 0 0 0 0 1 1 FILE DOWNLOAD COMPLETED 0 0 0 0 0 1 0 0 FILE DOWNLOAD DEFERRED All other values are reserved. " ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 201 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.1.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.1.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). - Test File 1 for CO FD as specified in annex A.2.1 and test File 2 for CO FD as specified in Annex A.2.2 are available at the SS-UE1 for upload. 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 Storage Function, the MCData User Database, the SIP AS, the HTP Server, the HTTP Client, the MSRP TCP Server and the MSRP TCP Client. - The IUT (MCData Server) is the acting Participating Server and Controlling Server. Preamble: - In the <on-network> element of the MCData Service Configuration document the <max-data-size-auto-recv- bytes> element of the <tx-and-rx-control> element shall be set to 0 to indicate non-mandatory download independent from the file size. - The IUT (MCData Server) is connected to PLMN1. - 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 | 6.2.1.3.2 Test procedure sequence | Table 6.2.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'Discovery of the absolute URI of the media storage function' as described in Annex A, Table A.4.10.3-1? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perform procedure 'FD File upload using HTTP' as described in Annex A, Table A.4.8.3-1, to send test file 1 (ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), clause A.2.1)? - - 2 P 3 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a one-to-one FD SIGNALLING PAYLOAD message for non mandatory download, from SS-UE1 (MCData client) to SS-UE2 (MCData Client), containing the URL of the file and with disposition request "FILE DOWNLOAD COMPLETED UPDATE"? - - 3 P ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 202 St Procedure Message Sequence TP Verdict U - S Message 4 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a FD disposition notification of "FILE DOWNLOAD REQUEST REJECTED", from SS-UE2 (MCData client) to SS-UE1 (MCData Client), for the file sent at step 2? - - 4 P 5 Check: Does the MCData Server (IUT) correctly perform procedure 'Discovery of the absolute URI of the media storage function' as described in Annex A, Table A.4.10.3-1? - - 1 P 6 Check: Does the MCData Server (IUT) correctly perform procedure 'FD File upload using HTTP' as described in Annex A, Table A.4.8.3-1, to send test file 2 (ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), clause A.2.2)? - - 5 P 7 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a FD SIGNALLING PAYLOAD message for non mandatory download, from SS-UE1 (MCData client) to SS-UE2 (MCData Client), containing the URL of the file and with disposition request "FILE DOWNLOAD COMPLETED UPDATE"? - - 3 P 8 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a FD disposition notification of "FILE DOWNLOAD DEFERRED", from SS-UE2 (MCData client) to SS-UE1 (MCData Client), for the file sent at step 6? - - 6 P 9 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a FD disposition notification of "FILE DOWNLOAD ACCEPTED", from SS-UE2 (MCData client) to SS-UE1 (MCData Client), for the file sent at step 6? - - 7 P 10 Check: Does the MCData Server (IUT) correctly perform procedure 'FD File download using HTTP' as described in Annex A, Table A.4.9.3-1, to download test file 2 (ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), clause A.2.2)? - - 8 P 11 Check: Is the content of the downloaded file the same as specified in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), clause A.2.2? - - 8 P 12 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a FD disposition notification of "FILE DOWNLOAD COMPLETED", from SS-UE2 (MCData client) to SS-UE1 (MCData Client), for the file sent at step 6? - - 9 P |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.1.3.3 Specific message contents | Table 6.2.1.3.3-1: HTTP POST from the SS-UE1 (Step 2 and 6, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.4.8.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.1.3.3-7 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 203 Table 6.2.1.3.3-2: HTTP 201 Created from the MCData Server (IUT) to the SS-UE1 (Step 2, Table 6.2.1.3.2-1; Step 3, Annex A, Table A.4.8.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.1.3.3-11 Table 6.2.1.3.3-3: SIP MESSAGE from the SS-UE1 (Step 3 and 7, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.1.3.3-12 Table 6.2.1.3.3-4: SIP MESSAGE from the MCData Server (IUT) to the SS-UE2 (Step 3 and 7, Table 6.2.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.2.3.3-1 Information Element Value/remark Comment Reference Condition Request-Line IETF RFC 3261 [21] IETF RFC 5031 [22] Request-URI px_MCX_SIP_PublicUserId _B P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServiceI d_A The public service identity identifying the controlling MCData function ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.4.1 Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.2.1.3.3-5 Table 6.2.1.3.3-5: MCData-Info (Table 6.2.1.3.3-4) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.2.3.3-2 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params mcdata-request-uri Encrypted <mcdata-request- uri> with mcdataURI set to px_MCData_ID_User_B Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A mcdata-calling-user-id Encrypted <mcdata-calling- user-id> with mcdataURI set to px_MCData_ID_User_A Table 6.2.1.3.3-6: SIP MESSAGE from the SS-UE2 (Step 4, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.2.3.3-12 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) The URI of the SS- UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.2.1.3.3-7 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 204 Table 6.2.1.3.3-7: Resource-lists (Table 6.2.1.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3 Information Element Value/remark Comment Reference Condition resource-lists list name attribute display-name entry[1] uri attribute px_MCData_ID_User_A The MCData ID of the target MCData user Table 6.2.1.3.3-8: SIP MESSAGE from the MCData Server (IUT) to the SS-UE1 (Step 4, Table 6.2.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.1.3.3-14 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServic eId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 Table 6.2.1.3.3-9: HTTP 201 Created from the MCData Server (IUT) to the SS-UE1 (Step 6, Table 6.2.1.3.2-1; Step 3, Annex A, Table A.4.8.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.1.3.3-11 Information Element Value/remark Comment Reference Condition Location uri tsc_MCData_MSF_URI & "/file-location-2" Table 6.2.1.3.3-10: SIP MESSAGE from the SS-UE2 (Step 8, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.2.3.3-14 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) The URI of the SS- UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.2.1.3.3-7 Table 6.2.1.3.3-11: SIP MESSAGE from the MCData Server (IUT) to the SS-UE1 (Step 8, Table 6.2.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.1.3.3-17 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServic eId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 205 Table 6.2.1.3.3-12: SIP MESSAGE from the SS-UE2 (Step 9, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.2.3.3-4 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) The URI of the SS- UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.2.1.3.3-7 Table 6.2.1.3.3-13: SIP MESSAGE from the MCData Server (IUT) to the SS-UE1 (Step 9, Table 6.2.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.1.3.3-19 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServic eId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 Table 6.2.1.3.3-14: HTTP GET from the SS-UE2 (Step 10, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.4.9.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.2.3.3-6 Table 6.2.1.3.3-15: HTTP 200 (OK) from the MCData Server (IUT) to the SS-UE2 (Steps 10, Table 6.2.1.3.2-1; Step 2, Annex A, Table A.4.9.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.2.3.3-7 Table 6.2.1.3.3-16: SIP MESSAGE from the SS-UE2 (Step 12, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.2.3.3-10 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) The URI of the SS-UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.2.1.3.3-7 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 206 Table 6.2.1.3.3-17: SIP MESSAGE from the MCData Server (IUT) to the SS-UE1 (Step 12, Table 6.2.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.1.3.3-21 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServic eId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 6.2.2 MCDATA Server - MCDATA Client / File Distribution (FD) / FD Using HTTP / Group Standalone FD / Mandatory Download / Without Disposition Request |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { SS-UE1 (MCData Client) requests discovery of the absolute URI by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 200 (Ok) to UE1 (MCData Client) } } (2) with { IUT (MCData Server) having requested a Group Standalone FD } ensure that { when { the SS-UE1 (MCData Client) initiates FD "file 1" upload by sending a HTTP POST request } then { IUT (MCData Server) responds with a HTTP 201 (Created) } } (3) with { IUT (MCData Server) having requested a Group Standalone FD } ensure that { when { SS-UE1 (MCData Client) requests FD upload by sending a SIP MESSAGE message without disposition request } then { IUT (MCData Server) sends a SIP MESSAGE message to UE2 (MCData Client) and responds with a SIP 202 (Accepted) to UE1 (MCData Client) } } (4) with { IUT (MCData Server) having requested a Group Standalone FD } ensure that { when { SS-UE2 (MCData Client) requests FD transfer by sending a SIP MESSAGE message with disposition request "FILE DOWNLOAD ACCEPTED" } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } (5) with { IUT (MCData Server) having requested a Group Standalone FD } ensure that { when { the SS-UE2 (MCData Client) initiates FD "file 1" download by sending a HTTP GET request } then { IUT (MCData Server) responds with a HTTP 200 (Ok) and SS-UE2 (MCData Client) contains downloaded "file 1" with same content } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 207 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 10.2.4.1, 10.2.4.3.1, 10.2.4.3.2, 10.2.4.4.1, 10.2.4.4.2, 10.2.4.2.1, 10.2.1.2.2, 6.2.2.2, 11.2, 6.2.3.2, 15.2.16. Unless otherwise stated, these are Rel-14 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.1] "The procedures in the subclauses of the parent subclause describe the SIP signalling procedures for: - one-to-one file distribution using HTTP; and - group standalone file distribution using HTTP. When the MCData user wishes to perform file distribution via HTTP, the MCData client: 1) shall check that the file size is less than or equal to the: a) <mcdata-on-network-max-data-size-for-FD> element present in the group document retrieved by the group management client as specified in 3GPP TS 24.481 [11], if the file upload is for a group file distribution; or … 2) if the size of the file: a) is acceptable for upload as determined by step 1), shall determine the value of the absolute URI associated with the media storage function of the MCData content server from the <MCDataContentServerURI> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]); b) is not acceptable for upload, shall not continue with the remaining steps in this subclause; 3) shall request the media storage client to upload the file to the media storage function by following the procedures in subclause 10.2.2.1; and 4) shall initiate an FD request containing a file URL as specified in subclause 10.2.4.2.1." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.3.1] "Upon receipt of a "SIP MESSAGE request for FD using HTTP for originating participating MCData function", the participating MCData function: … 2) shall determine the MCData ID of the originating user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request, and shall authorise the calling user; NOTE: 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) if <mcdata-controller-psi> element is present in the application/vnd.3gpp.mcdata-info+xml, shall use its value as public service identity of the controlling MCData function. Otherwise, if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request is: a) set to a value of "group-fd", shall determine the public service identity of the controlling MCData function hosting the group standalone FD using HTTP service, associated with the MCData group identity in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the SIP MESSAGE request; or … … ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 208 6) shall determine whether the MCData user identified by the MCData ID is authorised for MCData communications by following the procedures in subclause 11.1; … 8) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]; 9) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCData function as determined by step 4) in this subclause; 10) shall copy all MIME bodies included in the incoming SIP MESSAGE request to the outgoing SIP MESSAGE request; 10A) if the incoming SIP MESSAGE request contains an application/vnd.3gpp.mcdata-info+xml MIME body that contains a <functional-alias-URI> element, shall check if the status of the functional alias is activated for the MCData ID. If the functional alias status is activated, then the participating MCData function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request to the received value, otherwise shall not include a <functional-alias-URI> element; 11) shall include the MCData ID of the originating user in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP MESSAGE request; 12) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; 13) 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; and 14) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [5]. Upon receipt of a SIP 202 (Accepted) response in response to the SIP MESSAGE request in step 14): 1) shall generate a SIP 202 (Accepted) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 202 (Accepted) response to the MCData client according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the SIP MESSAGE request in step 14): 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 200 (OK) response to the MCData client according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request in step 14) the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the MCData client according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.3.2] "Upon receipt of a: - "SIP MESSAGE request for FD using HTTP for terminating participating MCData function"; or - "SIP MESSAGE network notification for FD using HTTP for terminating participating MCData function"; the participating MCData function: … 2) shall use the MCData ID present in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata- info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCData ID and public user identity of the terminating MCData user; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 209 … 4) if the SIP MESSAGE is a "SIP MESSAGE request for FD using HTTP for terminating participating MCData function", and if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message with a FD disposition request type IE, shall store the value of the Conversation ID IE, the value of the Message ID IE and the payload IE in the FD SIGNALLING PAYLOAD message; 5) if the SIP MESSAGE is a "SIP MESSAGE network notification for FD using HTTP for terminating participating MCData function", and if FD NETWORK NOTIFICATION message within the application/vnd.3gpp.mcdata-signalling MIME body contains an FD notification type IE with value set as "FILE EXPIRED UNAVAILABLE TO DOWNLOAD" as specified in subclause 15.2.6, the file identified using Conversation ID IE shall be removed from the stored file list; 5) shall generate an outgoing SIP MESSAGE request as specified in subclause 6.3.2.1; … 6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and 7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the above SIP MESSAGE request, the participating MCData function: 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 200 (OK) response to the controlling MCData function according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP MESSAGE request, the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the controlling MCData function according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.4.1] "This subclause describes the procedures for sending a SIP MESSAGE from the controlling MCData function and is initiated by the controlling MCData function as a result of an action in subclause 10.2.4.4.2. The controlling MCData function: 1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]; 2) shall include an Accept-Contact header field containing the g.3gpp.mcdata.fd media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request; 3) 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.mcdata.fd" along with parameters "require" and "explicit" according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request; 4) shall copy the following MIME bodies in the received SIP MESSAGE request into the outgoing SIP MESSAGE request by following the guidelines in subclause 6.4: a) application/vnd.3gpp.mcdata-info+xml MIME body; and b) application/vnd.3gpp.mcdata-signalling MIME body; 5) if the application/vnd.3gpp.mcdata-signalling MIME body in the received SIP MESSAGE request contained a FD SIGNALLING PAYLOAD message without the Mandatory download IE included, then: a) shall execute the procedures in subclause 11.2; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 210 b) if the procedures in subclause 11.2 indicate that the mandatory download indication needs to be included,shall include the Mandatory download IE set to a value of "MANDATORY DOWNLOAD" in the FD SIGNALLING PAYLOAD message of the outgoing SIP MESSAGE request; 6) in the application/vnd.3gpp.mcdata-info+xml MIME body: a) shall set the <mcdata-request-uri> element set to the MCData ID of the terminating user; and b) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP MESSAGE request was set to a value of "group-fd", shall set the <mcdata-calling-group-id> element to the group identity; 7) shall set the Request-URI to the public service identity of the terminating participating MCData function associated to the MCData user to be invited; 8) shall copy the public user identity of the calling MCData user from the P-Asserted-Identity header field of the incoming SIP MESSAGE request into the P-Asserted-Identity header field of the outgoing SIP MESSAGE request; 9) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd"; and 10) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.4.2] "The procedures in this subclause are executed upon: - receipt of a "SIP MESSAGE request for FD using HTTP for controlling MCData function", the controlling MCData function; or - a decision to now process a previously received "SIP MESSAGE request for FD using HTTP for controlling MCData function" that had been queued for later transmission; NOTE 1: The controlling MCData function may postpone the continuation of an FD using HTTP procedure by queuing the received "SIP MESSAGE request for FD using HTTP for controlling MCData function". The management of the queue is specified in Annex B of 3GPP TS 23.282 [2]. The controlling MCData function: … 3) if the SIP MESSAGE does not contain: a) an application/vnd.3gpp.mcdata-info+xml MIME body; and b) an application/vnd.3gpp.mcdata-signalling MIME body; shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response, with warning text set to "199 expected MIME bodies not in the request" in a Warning header field as specified in subclause 4.9, and shall not continue with the rest of the steps in this subclause; 4) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body contained in the SIP MESSAGE; 5) if the application/vnd.3gpp.mcdata-signalling MIME body does not contain only one FD SIGNALLING PAYLOAD message or FD HTTP TERMINATION message, shall reject the SIP MESSAGE …, and shall not continue with the rest of the steps in this subclause; 6) if the FD SIGNALLING PAYLOAD message or FD HTTP TERMINATION messagedoes not contain only one Payload IE, shall reject the SIP MESSAGE request …, and shall not continue with the rest of the steps in this subclause; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 211 7) if the Payload IE has Payload contents: a) with a Payload content type set to a value other than "FILEURL" shall reject the SIP MESSAGE request …, and shall not continue with the rest of the steps in this subclause; and b) with Payload data containing a file URL identifying a file that does not exist on the media storage function, shall reject the SIP MESSAGE request …, and shall not continue with the rest of the steps in this subclause; 8) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message with a FD disposition request type IE, shall store the value of the Conversation ID IE and the value of the Message ID IE in the FD SIGNALLING PAYLOAD message; NOTE 2: The controlling MCData function uses the Conversation ID and Message ID for correlation with disposition notifications. 9) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message: a) with a Metadata IE, shall derive a timer value for the file availability timer as the minimum of the file availability information in the metadata and the value contained in the <max-file-availability> element in the MCData service configuration document as specified in 3GPP TS 24.484 [12]; and b) without a Metadata IE, shall derive a timer value for the file availability timer as the value contained in the <default-file-availability> element in the MCData service configuration document as specified in 3GPP TS 24.484 [12]; … 11) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD HTTP TERMINATION message: a) if the FD HTTP TERMINATION message doesn't contain Conversation Id or Message Id, shall reject the SIP MESSAGE request … and shall not continue with rest of the steps;and … 12) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message and if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request is set to a value of "group-fd": a) shall retrieve the group document associated with the group identity in the SIP MESSAGE request by following the procedures in subclause 6.3.3, and shall continue with the remaining steps if the procedures in subclause 6.3.3 were successful; … c) if the <entry> element of the <list> element of the <list-service> element in the group document does not contain an <mcdata-mcdata-id> element with a "uri" attribute matching the MCData ID of the originating user contained in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata- info+xml MIME body in the SIP MESSAGE request, shall send a SIP 403 (Forbidden) response with the warning text set to "116 user is not part of the MCData group" in a Warning header field as specified in subclause 4.9 and shall not continue with the rest of the steps; d) if the <list-service> element contains a <mcdata-allow-file-distribution> element in the group document set to a value of "false", shall send a SIP 403 (Forbidden) response with the warning text set to "213 file distribution not allowed for this group" in a Warning header field as specified in subclause 4.9 and shall not continue with the rest of the steps; e) if the <supported-services> element is not present in the group document or is present and contains a <service> element containing an "enabler" attribute which is not set to the value "urn:urn-7:3gpp- service.ims.icsi.mcdata.fd", shall send a SIP 488 (Not Acceptable) response with the warning text set to "214 FD services not supported for this group" in a Warning header field as specified in subclause 4.9 and shall not continue with the rest of the steps; … ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 212 j) shall determine targeted group members for MCData communications by following the procedures in subclause 6.3.4; … l) shall send SIP MESSAGE requests to the targeted group members identified in step j) above by following the procedure in subclause 10.2.4.4.1; 13) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message, shall start TDC2 (file availability timer) with the value derived in step 9 of this subclause; 14) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD SIGNALLING PAYLOAD message, shall associate the running timer TDC2 (file availability timer) to the Conversation ID, Message ID, Application ID (if included), and Extended application ID (if included) contained in the FD SIGNALLING PAYLOAD message; NOTE 3: Multiple file availability timers can be running for a file. Each file availability timer is uniquely associated to a Conversation ID and Message ID. 15) shall generate a SIP 202 (Accepted) response in response to the "SIP MESSAGE request for FD using HTTP for controlling MCData function"; and 16) shall send the SIP 202 (Accepted) response towards the originating participating MCData function according to 3GPP TS 24.229 [5]. 17) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD HTTP TERMINATION message and Termination information type IE set to "TERMINATION REQUEST" then: a) shall identify the FILE transmission with Conversation ID and Message ID and "FILE URL". If any ongoing transmission exist then execute procedure described in subclause 12.4.2.1 withfollowing clarifications: i) shall set FD notification type IE as "FILE DELETED UNAVAILABLE TO DOWNLOAD" as specified in subclause 15.2.18; b) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]. In the generation of the SIP MESSAGE request, the controlling MCData function: i) 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.mcdata.fd" along with parameters "require" and "explicit" according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request; ii) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp- service.ims.icsi.mcdata.fd"; iii) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the participating MCData function associated to the MCData ID of the originating user mentioned in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP MESSAGE request; iv) shall copy the public user identity of the calling MCData user from the P-Asserted-Identity header field of the incoming SIP MESSAGE request into the P-Asserted-Identity header field of the outgoing SIP MESSAGE request; v) shall include an application/vnd.3gpp.mcdata-info+xml MIME body in the SIP MESSAGE request, following the rules specified in subclause 6.4 for the handling of MIME bodies in a SIP message: A) fill <mcdata-request-uri> element from <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml in received SIP MESSAGE; vi) shall generate FD HTTP TERMINATION message as described in subclause 6.3.6.1; vii) shall set the Termination information type IE set to "TERMINATION RESPONSE" as specified in subclause 15.2.22. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 213 viii) if clause is successful shall set Release response type IE of FD HTTP TERMINATION MESSAGE to "RELEASE SUCCESS" else set to "RELEASE FAILED" as described in subclause 15.2.23; and ix) shall include in the SIP request, the FD HTTP TERMINATION message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in subclause E.1; c) shall send the SIP MESSAGE request towards the originating participating MCData function as specified in 3GPP TS 24.229 [5]; and 18) if the application/vnd.3gpp.mcdata-signalling MIME body contains an FD HTTP TERMINATION message and Termination information type IE set to other than "TERMINATION REQUEST" then follow procedures described on subclause 13.2.5 and subclause 13.2.6." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.4.2.1] "The MCData client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6] with the clarifications given below. The MCData client: 5) shall build the SIP MESSAGE request as specified in subclause 6.2.4.1; … 3) if a group standalone FD message is to be sent: a) if the "/<x>/<x>/Common/MCData/AllowedFD" leaf node present in the group document of the requested MCData group, configured on the group management client as specified in 3GPP TS 24.483 [42] is set to "false", shall reject the request for FD and not continue with the rest of the steps in this subclause; and b) shall insert in the SIP MESSAGE request an application/vnd.3gpp.mcdata-info+xml MIME body with: i) the <request-type> element set to a value of "group-fd"; ii) the <mcdata-request-uri> element set to the MCData group identity; iii) the <mcdata-client-id> element set to the MCData client ID of the originating MCData client; and iv) if the MCData client is aware of active functional aliases and if an active functional alias is to be included in the SIP MESSAGE request, the <functional-alias-URI> element set to the URI of the used functional alias; 4) shall generate a standalone FD message as specified in subclause 6.2.2.2; and 5) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.1.2.2] "The MCData client: 1) if the FD SIGNALLING PAYLOAD message contains a new Conversation ID, shall instantiate a new conversation with the Message ID in the FD SIGNALLING PAYLOAD identifying the first message in the conversation thread; 2) if the FD SIGNALLING PAYLOAD message contains an existing Conversation ID and: a) if the FD SIGNALLING PAYLOAD message does not contain an InReplyTo message ID, shall use the Message ID in the FD SIGNALLING PAYLOAD to identify a new message in the existing conversation thread; and b) if the FD SIGNALLING PAYLOAD message contains an InReplyTo message ID, shall associate the message to an existing message in the conversation thread as identified by the InReplyTo message ID in the FD SIGNALLING PAYLOAD, and use the Message ID in the FD SIGNALLING PAYLOAD to identify the new message; 3) may store the Conversation ID, Message ID, InReplyTo message ID and Date and time in local storage; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 214 4) if the FD SIGNALLING PAYLOAD message does not contain an Application ID IE and does not contain an Extended application ID IE: a) shall determine that the payload contained in the Payload IE in the FD SIGNALLING PAYLOAD message is for user consumption; b) shall notify the user or application that the file identified by file URL in the Payload data in the Payload IE will be downloaded automatically; and c) if the FD SIGNALLING PAYLOAD message contains a Metadata IE, shall deliver the contents of the Metadata IE to the user or application; 5) if the FD SIGNALLING PAYLOAD message contains an Application ID IE: a) shall determine that the payload contained in the Payload IE in the FD SIGNALLING PAYLOAD message is not for user consumption; b) if the Application ID value is unknown, shall discard the FD message and exit this subclause; c) if the Application ID value is known, shall notify the application that the file identified by file URL in the Payload data in the Payload IE will be downloaded automatically; and NOTE 1: If the FD request is addressed to a non-MCData application that is not running, the MCData client starts the local non-MCData application. Subsequent automatic download of the file is then started and the file is delivered to that application. d) if the FD SIGNALLING PAYLOAD message contains a Metadata IE, shall deliver the contents of the Metadata IE to the application; 6) if the FD SIGNALLING PAYLOAD message contains an Extended application ID IE: a) shall determine that the payload contained in the Payload IE in the FD SIGNALLING PAYLOAD message is not for user consumption; b) if the Extended application ID value is unknown, shall discard the FD message and exit this clause; c) if the Extended application ID value is known, shall notify the application that the file identified by file URL in the Payload data in the Payload IE will be downloaded automatically; and NOTE 2: If the FD request is addressed to a non-MCData application that is not running, the MCData client starts the local non-MCData application. Subsequent automatic download of the file is then started and the file is delivered to that application. d) if the FD SIGNALLING PAYLOAD message contains a Metadata IE, shall deliver the contents of the Metadata IE to the application; 7) shall generate an FD NOTIFICATION indicating acceptance of the FD request as specified in subclause 12.2.1.1; 8) shall attempt to download the file as identified by the file URL in the Payload IE in the FD SIGNALLING PAYLOAD message, as specified in subclause 10.2.3.1; and 9) if the received FD SIGNALLING PAYLOAD message contains an FD disposition request type IE requesting a file download completed update indication, then after the file has been successfully downloaded, shall generate an FD NOTIFICATION indicating file download completed, by following the procedures in subclause 12.2.1.1." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 6.2.2.2] "In order to generate an FD message, the MCData client: 1) shall generate an FD SIGNALLING PAYLOAD message as specified in subclause 15.1.3; and 2) shall include in the SIP request, the FD SIGNALLING PAYLOAD message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in subclause E.1. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 215 When generating an FD SIGNALLING PAYLOAD message as specified in subclause 15.1.3, the MCData client: 1) shall set the Date and time IE to the current time as specified in subclause 15.2.8; 2) if the FD message starts a new conversation, shall set the Conversation ID IE to a newly generated Conversation ID value as specified in subclause 15.2.9; 3) if the FD message continues an existing unfinished conversation, shall set the Conversation ID IE to the Conversation ID value of the existing conversation as specified in subclause 15.2.9; 4) shall set the Message ID IE to a newly generated Message ID value as specified in subclause 15.2.10; 5) if the FD message is in reply to a previously received MCData message, shall include the InReplyTo message ID IE with the Message ID value in the previously received MCData message; 6) if the FD message is for user consumption, shall not include an Application ID IE as specified in subclause 15.2.7 and shall not include an Extended application ID IE as specified in subclause 15.2.24; 7) if the FD message is intended for an application on the terminating MCData client, shall include: a) an Application ID IE with a Application ID value representing the intended application as specified in subclause 15.2.7; or b) an Extended application ID IE with an Extended application ID value representing the intended application as specified in subclause 15.2.24; NOTE: The value and field chosen for coding the identity of the application are coordinated by the mission critical organisation. 8) may include an FD disposition request type IE set to "FILE DOWNLOAD COMPLETE UPDATE" as specified in subclause 15.2.4; 9) if requiring mandatory download at the recipient side, shall include a Mandatory download IE as specified in subclause 15.2.16 set to the value of "MANDATORY DOWNLOAD"; 10) shall include a Payload IE with: a) the Payload content type set to "FILEURL" as specified in subclause 15.2.13; and b) the URL of the file in the Payload data as as specified in subclause 15.2.13; and 11) may include a Metadata IE with the required file description information and file availability information, as specified in subclause 15.2.17." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 11.2] "If the controlling MCData function receives a one-to-one file distribution using HTTP or a group standalone file distribution using HTTP without the mandatory download indication the controlling MCData function: 1) if the file distribution request contained metadata, shall retrieve the filesize contained in the fileselector of the Metadata IE in the FD request; 2) if the file distribution request did not contain metadata, shall determine the size of the file referenced by the file URL contained in FD request; … 4) for group standalone file distribution using HTTP, shall determine if the filesize is less than or equal to the value contained the <mcdata-on-network-max-data-size-auto-recv> element of the MCData group document associated with the MCData group identity in the request, as specified in 3GPP TS 24.481 [11] 5) ifcondition 3) or 4) is true, shall determine that the mandatory download indication needs to be included in the file distribution request sent to the terminating MCData client;" ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 216 [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 6.2.3.2] "In order to generate an FD notification, the MCData client: 1) shall generate an FD NOTIFICATION message as specified in subclause 15.1.6; and 2) shall include in the SIP request, the FD NOTIFICATION message in an application/vnd.3gpp.mcdata- signalling MIME body as specified in subclause E.1. When generating an FD NOTIFICATION message as specified in subclause 15.1.6, the MCData client: 1) if sending a file download accept notification, shall set the FD disposition notification type IE as "FILE DOWNLOAD REQUEST ACCEPTED" as specified in subclause 15.2.6; 2) if sending a file download reject notification, shall set the FD disposition notification type IE as "FILE DOWNLOAD REQUEST REJECTED" as specified in subclause 15.2.6; 3) if sending a file download deferred notification, shall set the FD disposition notification type IE as "FILE DOWNLOAD REQUEST DEFERRED" as specified in subclause 15.2.6; 4) shall set the Conversation ID to the value of the Conversation ID that was received in the FD message as specified in subclause 15.2.9; 5) shall set the Date and time IE to the current time as specified in subclause 15.2.8; and 6) if sending a file download completed notification: a) shall set the FD disposition notification type IE as "FILE DOWNLOAD COMPLETED" as specified in subclause 15.2.6; b) shall set the Message ID to the value of the Message ID that was received in the FD message as specified in subclause 15.2.10; c) if the FD message was destined for the user, shall not include an Application ID IE as specified in subclause 15.2.7 and shall not include a Extended application ID IE as specified in subclause 15.2.24; and d) if the FD message was destined for an application, shall include: i) an Application ID IE set to the value of the Application ID that was included in the FD message as specified in subclause 15.2.3; or ii) an Extended application ID IE set to the value of the Extended application ID that was included in the FD message as specified in subclause 15.2.24." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 15.2.16] "The purpose of the Mandatory download information element is for the originating client to inform the terminating client that a file must be downloaded immediately. The value part of the Mandatory download information element is coded as shown in Figure 15.2.16-1 and Table 15.2.16-1. The Mandatory download information element is a type 1 information element. 8 7 6 5 4 3 2 1 Mandatory download IEI Mandatory download value octet 1 Figure 15.2.16-1: Mandatory download ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 217 Table 15.2.16-1: Mandatory download Mandatory download value (octet 1) Bits 4 3 2 1 0 0 0 1 MANDATORY DOWNLOAD All other values are reserved. " |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.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). - Test File 1 for CO FD as specified in clause A.2.1 is available at the SS-UE1 for upload. 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 Storage Function, the MCData User Database, the SIP AS, the HTP Server, the HTTP Client, the MSRP TCP Server and the MSRP TCP Client. - The IUT (MCData Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCData Server) is connected to PLMN1. - 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. - SS-UE1 (MCData client) and SS-UE2 (MCData client) are affiliated to the Prearranged group. - The IUT (MCData Server) is the controlling server of the Prearranged group. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 218 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.3.2 Test procedure sequence | Table 6.2.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'Discovery of the absolute URI of the media storage function' as described in Annex A, Table A.4.10.3-1? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perform procedure 'FD File upload using HTTP' as described in Annex A, Table A.4.8.3-1, to send test file 1 (ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), clause A.2.1)? - - 2 P 3 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a group FD SIGNALLING PAYLOAD message for mandatory download, containing the URL of the file and without disposition request? - - 3 P 4 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a FD disposition notification of "FILE DOWNLOAD ACCEPTED" from SS-UE2 (MCData client), for the file sent at step 2? - - 4 P 5 Check: Does the MCData Server (IUT) correctly perform procedure 'FD File download using HTTP' as described in Annex A, Table A.4.9.3-1. to download test file 1 (ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), clause A.2.1)? - - 5 P 6 Check: Is the content of the downloaded file the same as specified in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), clause A.2.1? - - 5 P |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.2.3.3 Specific message contents | Table 6.2.2.3.3-1: HTTP POST from the SS-UE1 (Step 2, Table 6.2.2.3.2-1; Step 1, Annex A, Table A.4.8.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.7.3.3-7 Table 6.2.2.3.3-2: HTTP 201 Created from the MCData Server (IUT) to the SS-UE1 (Step 2, Table 6.2.2.3.2-1; Step 3, Annex A, Table A.4.8.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.7.3.3-10 Table 6.2.2.3.3-3: SIP MESSAGE from the SS-UE1 (Step 3, Table 6.2.2.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.7.3.3-11 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 219 Table 6.2.2.3.3-4: SIP MESSAGE from the MCData Server (IUT) to the SS-UE2 (Step 3, Table 6.2.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.8.3.3-1 Information Element Value/remark Comment Reference Condition Request-Line IETF RFC 3261 [21] IETF RFC 5031 [22] Request-URI px_MCX_SIP_PublicUserId _B P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServiceI d_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.4.1 Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.2.2.3.3-5 Table 6.2.2.3.3-5: MCData-Info (Table 6.2.2.3.3-4) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.8.3.3-2 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params mcdata-request-uri Encrypted <mcdata-request-uri> with mcdataURI set to px_MCData_ID_User_B Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A mcdata-calling-user-id Encrypted <mcdata-calling-user- id> with mcdataURI set to px_MCData_ID_User_A Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A mcdata-client-id Encrypted <mcdata-client-id> with mcdataString set to px_MCX_Client_A_ID Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A Table 6.2.2.3.3-6: SIP MESSAGE from the SS-UE2 (Step 4, Table 6.2.2.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.8.3.3-5 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) The URI of the SS- UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.2.1.3.3-7 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 220 Table 6.2.2.3.3-7: Resource-lists (Table 6.2.2.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3 Information Element Value/remark Comment Reference Condition resource-lists list name attribute display-name entry[1] uri attribute px_MCData_ID_User_A The MCData ID of the target MCData user Table 6.2.2.3.3-8: SIP MESSAGE from the MCData Server (IUT) to the SS-UE1 (Step 4, Table 6.2.2.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.7.3.3-14 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServic eId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 Table 6.2.2.3.3-9: HTTP GET from the SS-UE2 (Step 5, Table 6.2.2.3.2-1; Step 1, Annex A, Table A.4.9.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.8.3.3-8 Table 6.2.2.3.3-10: HTTP 200 (OK) from the MCData Server (IUT) to the SS-UE2 (Step 5, Table 6.2.2.3.2-1; Step 2, Annex A, Table A.4.9.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.8.3.3-9 6.2.3 MCDATA Server - MCDATA Client / File Distribution (FD) / FD Using Media Plane / One-to-one Standalone FD |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.3.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCData Client) initiates establishment of a media plane FD session } then { IUT (MCData Server) accepts the call from the initiator and establishes the call with SS- UE2 (MCData Client) and responds/forwards empty MSRP messages } } (2) with { IUT (MCData Server) having requested an one-to-one Standalone FD } ensure that { when { the SS-UE1 (MCData Client) sends an MSRP SEND message with disposition request "FILE DOWNLOADED COMPLETED UPDATE"} then { IUT (MCData Server) forwards an MSRP SEND message to UE2 (MCData Client) and responds with an MSRP 200 (Ok) to UE1 (MCData Client) } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 221 (3) with { IUT (MCData Server) having requested an one-to-one Standalone FD } ensure that { when { the SS-UE1 (MCData client) ends the FD session } then { IUT (MCData Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to SS-UE2 (MCData Client) and waits to close MSRP TCP connections } } (4) with { IUT (MCData Server) having received an one-to-one Standalone FD } ensure that { when { SS-UE2 (MCData Client) requests the one-to-one Standalone FD by sending a SIP MESSAGE message with disposition notification "FILE DOWNLOAD COMPLETED" } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.3.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 10.2.5.3.3, 10.2.5.3.4, 10.2.5.3.1, 10.2.5.3.2, 10.2.5.4.3, 10.2.5.4.4, 10.2.5.4.1, 10.2.5.4.2, ETSI TS 124 582 [40] (3GPP TS 24.582), clauses 7.2.4.1, 7.2.4.2, 7.2.4.3, 7.2.5.1, 7.2.5.2, 7.2.5.3, 7.2.2., 7.2.3, 7.3.2.1, 7.3.2.2, 7.3.3, 10.1. Unless otherwise stated, these are Rel-14 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.5.3.3] "Upon receipt of a "SIP INVITE request for file distribution for originating participating MCData function", the participating MCData function: … 2) shall determine the MCData ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and shall authorise the calling user; NOTE: 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) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP INVITE request is: … b) set to a value of "one-to-one-fd", shall determine the public service identity of the controlling MCData function hosting the file distribution service for the calling user; … 6) shall determine whether the MCData user identified by the MCData ID is authorised for MCData communications by following the procedures in subclause 11.1; … 8) shall generate a SIP INVITE request in accordance with 3GPP TS 24.229 [5]; 9) shall include the option tag "timer" in the Supported header field; 10) should include the Session-Expires header field according to IETF RFC 4028 [38]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 11) shall set the Request-URI of the outgoing SIP INVITE request to the public service identity of the controlling MCData function as determined by step 4) in this subclause; 12) shall include the MCData ID of the originating user in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP INVITE request; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 222 12A) if the incoming SIP MESSAGE request contains an application/vnd.3gpp.mcdata-info+xml MIME body that contains a <functional-alias-URI> element, shall check if the status of the functional alias is activated for the MCData ID. If the functional alias status is activated, then the participating MCData function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request to the received value, otherwise shall not include a <functional-alias-URI> element; 13) shall include in the outgoing SIP INVITE request, the application/vnd.3gpp.mcdata-signalling MIME body that was present in the incoming SIP INVITE request; 14) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; 15) shall set the P-Asserted-Identity in the outgoing SIP INVITE request to the public user identity in the P- Asserted-Identity header field contained in the received SIP INVITE request; 16) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCData client as specified in subclause 10.2.5.3.1; and 17) shall send the SIP INVITE request as specified to 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the SIP INVITE request in step 16): 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; 2) shall include in the SIP 200 (OK) response an SDP answer as specified in the subclause 10.2.5.3.2; 3) shall include the option tag "timer" in a Require header field; 4) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [38], "UAS Behavior". If the "refresher" parameter is not included in the received request, the "refresher" parameter in the Session-Expires header field shall be set to "uac"; 5) shall include the following in the Contact header field: a) the g.3gpp.mcdata.fd media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.fd"; and c) the isfocus media feature tag; 6) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 7) shall include an MCData session identity mapped to the MCData session identity provided in the Contact header field of the received SIP 200 (OK) response; 8) if the incoming SIP 200 (OK) response contained an application/vnd.3gpp.mcdata-info+xml MIME body, shall copy the application/vnd.3gpp.mcdata-info+xml MIME body to the outgoing SIP 200 (OK) response. 9) shall include the public service identity received in the P-Asserted-Identity header field of the incoming SIP 200 (OK) response into the P-Asserted-Identity header field of the outgoing SIP 200 (OK) response; and 10) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 7.2.1; 11) shall send the SIP 200 (OK) response to the MCData client according to 3GPP TS 24.229 [5]; and 12) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [38]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP INVITE request in step 16) the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the MCData client according to 3GPP TS 24.229 [5]." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 223 [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.5.3.4] "Upon receipt of a "SIP INVITE request for file distribution for terminating participating MCData function", the participating MCData function: … 2) shall check the presence of the isfocus media feature tag in the URI of the Contact header field and if it is not present then the participating MCData function shall reject the request .., and shall not continue with the rest of the steps; 3) shall use the MCData ID present in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCData ID and public user identity of the terminating MCData user; … 4A) if the <IncomingOne-to-OneCommunicationList> element exists in the MCData user profile document with one or more <One-to-One-CommunicationListEntry> elements (see the MCData user profile document in 3GPP TS 24.484 [12]) and: i) if the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP INVITE request does not match with the <entry> element of any of the <One-to-One- CommunicationListEntry> elements in the <IncomingOne-to-OneCommunicationList> element of the MCData user profile document (see the MCData user profile document in 3GPP TS 24.484 [12]); and ii) if configuration is not set in the MCData user profile document that allows the MCData user to receive one-to-one MCData communication from any user (see <allow-one-to-one-communication-from-any- user> element in MCData user profile document in 3GPP TS 24.484 [12]); then: i) shall reject the SIP INVITE request … and shall not continue with the rest of the steps; 5) shall generate a SIP INVITE request accordance with 3GPP TS 24.229 [5]; 6) should include the Session-Expires header field according to IETF RFC 4028 [38]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 7) shall include the option tag "timer" in the Supported header field; 8) shall include the following in the Contact header field: a) the g.3gpp.mcdata.fd media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.fd"; c) the isfocus media feature tag; d) an MCData session identity mapped to the MCData session identity provided in the Contact header field of the incoming SIP INVITE request; and e) any other uri-parameter provided in the Contact header field of the incoming SIP INVITE request; 9) shall include in the SIP INVITE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [8] that were received (if any) in the incoming SIP INVITE request; 10) shall set the Request-URI of the outgoing SIP INVITE request to the public user identity associated to the MCData ID of the terminating MCData user; 11) shall populate the outgoing SIP INVITE request with the MIME bodies that were present in the incoming SIP INVITE request; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 224 12) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP INVITE request to the P- Asserted-Identity header field of the outgoing SIP INVITE request; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for file distribution for terminating participating MCData function" as specified in subclause 10.2.5.3.1; and 14) shall send the SIP INVITE request as specified in 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the above SIP INVITE request, the participating MCData function: 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; 2) shall include in the SIP 200 (OK) response an SDP answer based on the SDP answer in the received SIP 200 (OK) response as specified in subclause 10.2.5.3.2; 3) shall include the option tag "timer" in a Require header field; 4) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [38], "UAS Behavior". If no "refresher" parameter was included in the SIP INVITE request, the "refresher" parameter in the Session-Expires header field shall be set to "uas"; 5) shall include the following in the Contact header field: a) the g.3gpp.mcdata.fd media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.fd"; and c) an MCData session identity mapped to the MCData session identity provided in the Contact header field of the received SIP INVITE request from the controlling MCData function; 6) if the incoming SIP response contained an application/vnd.3gpp.mcdata-info+xml MIME body, shall copy the application/vnd.3gpp.mcdata-info+xml MIME body to the outgoing SIP 200 (OK) response. 7) shall copy the P-Asserted-Identity header field from the incoming SIP 200 (OK) response to the outgoing SIP 200 (OK) response; 8) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [38]; 9) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 7.2.2; and 10) shall send the SIP 200 (OK) response to the controlling MCData function according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request, the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the controlling MCData function according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.5.3.1] "The SDP offer is generated based on the received SDP offer. The SDP offer generated by the participating MCData function: 1) shall contain only one SDP media-level section for file distribution as contained in the received SDP offer; and 2) shall contain an "a=key-mgmt" attribute field with a "mikey" attribute value, if present in the received SDP offer. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 225 When composing the SDP offer according to 3GPP TS 24.229 [5], the participating MCData function: 1) shall replace the IP address and port number for the offered media stream in the received SDP offer with the IP address and port number of the participating MCData function, if required; and … 2) if the IP address is replaced shall insert its MSRP URI before the MSRP URI in the "a=path" attribute in the SDP answer." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.5.3.2] "When composing the SDP answer according to 3GPP TS 24.229 [5], the participating MCData function: 1) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCData function, for the accepted media stream in the received SDP offer, if required; and … 2) if the IP address is replaced shall insert its MSRP URI before the MSRP URI in the "a=path" attribute in the SDP answer." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.5.4.3] "This subclause describes the procedures for inviting an MCData user to an MCData session. The procedure is initiated by the controlling MCData function as the result of an action in subclause 10.2.5.4.4. The controlling MCData function: 1) shall generate a SIP INVITE according to 3GPP TS 24.229 [5]; 2) shall include the Supported header field set to "timer"; 3) should include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [38]. The refresher parameter shall be omitted; 4) shall include an Accept-Contact header field containing the g.3gpp.mcdata.fd media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [8]; 5) 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.mcdata.fd" along with parameters "require" and "explicit" according to IETF RFC 3841 [8]; 6) shall include a Referred-By header field with the public user identity of the inviting MCData client; 7) shall include in the Contact header field an MCData session identity for the MCData session with the g.3gpp.mcdata.fd media feature tag, the isfocus media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" according to IETF RFC 3840 [16]; 8) shall include in the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcdata-request-uri> element set to the MCData ID of the terminating user; and … 9) shall include in the outgoing SIP INVITE request, the application/vnd.3gpp.mcdata-signalling MIME body that was present in the incoming SIP INVITE request; 10) shall set the Request-URI to the public service identity of the terminating participating MCData function associated to the MCData user to be invited; NOTE 1: How the controlling MCData function finds the address of the terminating participating MCData function is out of the scope of the current release. 11) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCData function; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 226 12) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" (coded as specified in 3GPP TS 24.229 [5]), in a P-Asserted-Service-Id header field according to IETF RFC 6050 [7] in the SIP INVITE request; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating client according to the procedures specified in subclause 10.2.5.4.1; and 14) shall send the SIP INVITE request towards the terminating client in accordance with 3GPP TS 24.229 [5]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCData function: 1) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 7.3. NOTE 2: The procedures executed by the controlling MCData function prior to sending a response to the inviting MCData client are specified in subclause 10.2.5.4.4." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.5.4.4] "In the procedures in this subclause: 1) MCData ID in an incoming SIP INVITE request refers to the MCData ID of the originating user from the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP INVITE request; … 3) MCData ID in an outgoing SIP INVITE request refers to the MCData ID of the called user in the <mcdata- request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP INVITE request; The procedures in this subclause are executed upon: - receipt of a "SIP INVITE request for controlling MCData function for file distribution"; or - a decision to now process a previously received "SIP INVITE request for controlling MCData function for file distribution" that had been queued for later transmission; … the controlling MCData function: … 4) if the incoming SIP INVITE request does not contain an application/vnd.3gpp.mcdata-signalling MIME body with the FD SIGNALLING PAYLOAD as described in subclause 6.2.2.3, shall reject the SIP INVITE request with appropriate reject code; 5) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if: a) an Accept-Contact header field does not include the g.3gpp.mcdata.fd media feature tag; or b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd"; 6) shall cache SIP feature tags, if received in the Contact header field and if the specific feature tags are supported; 7) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [38]; 8) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP INVITE request is set to a value of "one-to-one-fd" and: a) the conditions in subclause 11.1 indicate that the MCData user is not allowed to initiate FD communications due to file size exceeding allowed limits as determined by step 4) of subclause 11.1, shall reject the SIP INVITE request …, and shall not continue with the rest of the steps in this subclause; and ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 227 NOTE 2: The size of the file intended for transfer over the media plane is obtained from the 'size' selector of the file-selector attribute in the received SDP offer. b) the SIP INVITE request: … ii) contains an application/resource-lists MIME body with exactly one <entry> element, shall invite the MCData user identified by the <entry> element of the MIME body, as specified in subclause 10.2.5.4.3; and shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 7.3; … Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in subclause 10.2.5.4.3 and if the MCData ID in the SIP 200 (OK) response matches to the MCData ID in the corresponding SIP INVITE request the controlling MCData function: 1) shall generate SIP 200 (OK) response to the SIP INVITE request according to 3GPP TS 24.229 [5]; 2) shall include the option tag "timer" in a Require header field; 3) shall include the Session-Expires header field and start supervising the SIP session according to rules and procedures of IETF RFC 4028 [38], "UAS Behavior". The "refresher" parameter in the Session-Expires header field shall be set to "uac"; 4) shall include a P-Asserted-Identity header field with the public service identity of the controlling MCData function; 5) shall include a SIP URI for the MCData session identity in the Contact header field identifying the MCData session at the controlling MCData function; 6) shall include the following in the Contact header field: a) the g.3gpp.mcdata.fd media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcdata.fd"; and c) the isfocus media feature tag; 7) shall include Warning header field(s) received in incoming responses to the SIP INVITE request; 8) 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 subclause 10.2.5.4.2; 9) shall interact with the media plane as specified in 3GPP TS 24.582 [15] subclause 7.3; and 10) shall send a SIP 200 (OK) response to the inviting MCData client according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.5.4.1] "When composing an SDP offer according to 3GPP TS 24.229 [5], IETF RFC 5547 [69] IETF RFC 6135 [19] and IETF RFC 6714 [20] the MCData client: 1) shall include an "m=message" media-level section for the MCData media stream consisting of: a) the port number; b) a protocol field value of "TCP/MSRP" or "TCP/TLS/MSRP" for TLS; c) an "a=sendonly" attribute; d) an "a=path" attribute containing its own MSRP URI; e) set the content type as "a=accept-types:application/vnd.3gpp.mcdata-signalling"; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 228 f) set the a=setup attribute as "actpass"; g) a file-selector attribute containing: i) a 'name' selector; ii) a 'type' selector; iii) a 'size' selector; and iv) a 'hash' selector; and h) a file-date attribute;" [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 10.2.5.4.2] "When composing the SDP answer according to 3GPP TS 24.229 [5], the controlling MCData function: 1) shall include an "m=message" media-level section for the accepted MCData media stream consisting of: a) the port number; b) a protocol field value of "TCP/MSRP" or "TCP/TLS/MSRP" for TLS according to the received SDP offer; c) a format list field set to '*'; d) an "a=recvonly" attribute; e) an "a=path" attribute containing its own MSRP URI; f) set the content type as a=accept-types:application/vnd.3gpp.mcdata-signalling; and g) set the a=setup attribute set to "passive", according to IETF RFC 6135 [19]; and h) a file-selector attribute containing: i) a 'name' selector; ii) a 'type' selector; iii) a 'size' selector; and iv) a 'hash' selector." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 7.2.4.1] "The originating participating MCData function should establish the MSRP session with the originating MCData client as specified in subclause 7.2.2." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 7.2.4.2] "The originating participating MCData function should establish the MSRP session with the controlling MCData function as specified in subclause 7.2.3." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 7.2.4.3] "Upon receiving an MSRP SEND request from the originating MCData client, the originating participating MCData function: 1. if an MSRP connection is not established with the controlling MCData function then, shall establish the MSRP connection as specified in subclause 7.2.4.2. Otherwise, shall use the existing MSRP connection; and 2. shall forward the received MSRP SEND request to the controlling MCData function according to the rules and procedures of IETF RFC 4975 [11]. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 229 Upon receiving an MSRP 200 (OK) response from the controlling MCData function, the participating MCData function shall forward the MSRP 200 (OK) response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]. Upon receiving an error MSRP response from the controlling MCData function, the participating MCData function shall forward the error MSRP response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 7.2.5.1] "The terminating participating MCData function should establish the MSRP session with the controlling MCData function as specified in subclause 7.2.2." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 7.2.5.2] "The terminating participating MCData function should establish MSRP session to terminating MCData client as specified in subclause 7.2.3." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 7.2.5.3] "Upon receiving an MSRP SEND request from the controlling MCData function, the terminating participating MCData function: 1. shall generate and send a MSRP 200 (OK) response for the received MSRP SEND request to the controlling MCData function, according to the rules and procedures of IETF RFC 4975 [11]; and 2. shall forward the received MSRP SEND request to the terminating MCData client according to the rules and procedures of IETF RFC 4975 [11]. Upon receiving an error MSRP response from the terminating MCData client, the participating MCData function shall forward the error MSRP response to the originating MCData client according to the rules and procedures of IETF RFC 4975 [11]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 7.2.2] "To receive a file over MSRP, the participating MCData function: 1. shall act according to IETF RFC 6135 [12], as: a. an "passive" endpoint, if a=setup attribute in the sent SDP answer was set to "passive"; and b. an "active" endpoint, if a=setup attribute in the sent SDP answer was set to "active"; and 2. shall establish an MSRP connection according to the MSRP connection parameters in the sent SDP answer response as described in IETF RFC 4976 [14]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 7.2.3] "To send a file over MSRP, the participating MCData function: 1. shall act according to IETF RFC 6135 [12], as: a. an "active" endpoint, if a=setup attribute in the received SDP answer is set to "passive"; and b. an "passive" endpoint, if a=setup attribute in the received SDP answer is set to "active"; and 2. shall establish the MSRP connection according to the MSRP connection parameters in the received SDP answer response as described in IETF RFC 4976 [14]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 7.3.2.1] "To establish the MSRP connection with the originating MCData client, the controlling MCData function performs below procedures: 1. shall act as an MSRP client and establish TLS connection with the originating participating MCData function, if exists, otherwise the originating MCData client, according to the rules and procedures as described in IETF RFC 4975 [11]; ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 230 2. shall act as an MSRP client to send MSRP SEND requests according to the rules and procedures described in IETF RFC 6135 [12]; 3. shall act as an "passive" endpoint according to the rules and procedures described in IETF RFC 6135 [12]; 4. shall establish the MSRP connection with originating MCData client, according to the rules and procedures described in IETF RFC 6135 [12]; and 5. acting as a "passive" endpoint, shall wait for MSRP SEND request on established MSRP connection, to bind the MSRP connection to the MSRP session according to the rules and procedures of IETF RFC 4975 [11] and IETF RFC 6135 [12]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 7.3.2.2] "To establish the MSRP connection with the terminating MCData client, the controlling MCData function performs below procedures: 1. shall act as an MSRP client and establish TLS connection with the terminating participating MCData function, if exists, otherwise the terminating MCData client, according to the rules and procedures as described in IETF RFC 4975 [11]; 2. shall act as an MSRP client to send MSRP SEND requests according to the rules and procedures described in IETF RFC 6135 [12]; 3. shall act according to IETF RFC 6135 [12], as: a. an "active" endpoint, if a=setup attribute in the received SDP answer is set to "passive"; and b. an "passive" endpoint, if a=setup attribute in the received SDP answer is set to "active"; 4. shall establish the MSRP connection with each terminating MCData client identified in the 3GPP TS 24.282 [8], according to the rules and procedures described in IETF RFC 6135 [12]; and 5. if acting as an "active" endpoint, shall send an empty MSRP SEND request on each established MSRP connection, to bind the MSRP connection to the MSRP session according to the rules and procedures of IETF RFC 4975 [11] and IETF RFC 6135 [12]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 7.3.3] "Upon receiving a MSRP SEND request from the originating participating MCData function, the Controlling function: 1. shall generate and send a MSRP 200 (OK) response for the received MSRP SEND requests to the originating participating MCData function, according to the rules and procedures of IETF RFC 4975 [11]; and 2. shall forward the received MSRP SEND requests to each terminating MCData client with which a successful MSRP connection was established, according to the rules and procedures of IETF RFC 4975 [11]. Following clarifications apply to the generated MSRP SEND request: a. shall modify the To-Path header according to the MSRP URI received in the answer SDP from the MCData client in accordance with rules and procedures of IETF RFC 4975 [11]; and b. shall modify the From-Path header to the controlling MCData function's own MSRP URI, according to the rules and procedures of IETF RFC 4975 [11]." [ETSI TS 124 582 [40] (3GPP TS 24.582), clause 10.1] "Media plane security provides integrity and confidentiality protection for the MCData media information and media plane control information transmitted using media plane. Media plane security also provides the authentication of MCData media information. The media plane security is based on 3GPP MCData security solution including key management as defined in 3GPP TS 33.180 [15]. NOTE: In 3GPP TS 33.180 [15] media information is denoted as MCData Data Payload and media plane control information is denoted as MCData Data signalling Payload. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 231 Various keys and associated key identifiers protect the media information and media plane control information carried in the body of an MSRP SEND message. The media plane control information may be: 1. SDS SIGNALLING PAYLOAD; or 2. SDS NOTIFICATION. The media information may be: 1. DATA PAYLOAD; or 2. File or file portion. … In an on-network one-to-one MCData communication, if protection of media is negotiated, the PCK and the PCK-ID shall be used for protecting the media sent and received by MCData clients. If protection of media control information sent using unicast between the MCData client and the participating MCData function serving the the MCData client is negotiated, the CSK and the CSK-ID shall be used for protecting the media control information sent and received using unicast by the MCData client and by a participating MCData function. … The PCK and the PCK-ID are generated by the MCData client initiating the standalone one-to-one SDS using media plane or one-to-one SDS session or one-to-one FD using media plane and provided to the MCData client receiving the SIP signalling according to 3GPP TS 24.282 [8]. The CSK and the CSK-ID are generated by the MCData client and provided to the participating MCData function serving the MCData client using SIP signalling according to 3GPP TS 24.282 [8]. … The key material for creating and verifying the authentication signature (SSK, PVT and KPAK) is provisioned to the MCData clients by the KMS as specified in 3GPP TS 33.180 [15]." |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.3.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.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). - Test File 1 for CO FD as specified in clause A.2.1 is available at the SS-UE1 for upload. 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 Storage Function, the MCData User Database, the SIP AS, the HTP Server, the HTTP Client, the MSRP TCP Server and the MSRP TCP Client. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 232 - The IUT (MCData Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCData Server) is connected to PLMN1. - 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 | 6.2.3.3.2 Test procedure sequence | Table 6.2.3.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Establishment' as described in Annex A, Table A.4.3.3-1 to establish a media plane connection between SS-UE1 (MCData Client) and SS-UE2 (MCData Client)? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MSRP message transfer' as described in Annex A, Table A.4.4.3-1 to send a FD message containing test file 1 from SS-UE1 (MCData client) and with disposition request "FILE DOWNLOAD COMPLETED UPDATE"? - - 2 P 3 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E MCData Call Release' as described in Annex A, Table A.4.5.3-1? - - 3 P 4 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a disposition notification of "FILE DOWNLOAD COMPLETED", from SS-UE2 (MCData client) to SS-UE1 (MCData Client)? - - 4 P ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 233 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.3.3.3 Specific message contents | Table 6.2.3.3.3-1: SIP INVITE from the SS-UE1 (Step 1, Table 6.2.3.3.2-1; Step 1, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.9.3.3-1 Information Element Value/remark Comment Reference Condition Session-Expires generic-param "1800" The recommended initial value is 1800 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 6.2.3.3.3-2 MIME body part MCData-Info MIME-part-body MCData-Info as described in Table ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.9.3.3-3 MIME body part MCData Data signalling message MIME-part-headers MIME-Content-Type "application/vnd.3gpp.mcdata- signalling" MIME-part-body MCData Protected Payload Message containing FD SIGNALLING PAYLOAD as described in ETSI TS 136 579- 7 [4] (3GPP TS 36.579-7), Table 6.2.9.3.3-3A Table 6.2.3.3.3-2: SDP for SIP INVITE (Table 6.2.3.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.9.3.3-2 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-UE1 The transport port to which the media stream is sent Connection Data c= line connection-address IP address of the SS-UE1 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 234 Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.9.3.3-2 Information Element Value/remark Comment Reference Condition 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-UE1 port same value as in the media line session id assigned by the SS-UE1 transport "tcp" URI-parameter not present media attribute a= line attribute = key-mgmt key-mgmt mikey MIKEY-SAKKE I_MESSAGE as specified in Table 6.2.3.3.3-2A media attribute a= line attribute = file-transfer-id IETF RFC 5547 [25] file-transfer-id value assigned by the SS-UE1 randomly chosen globally unique identification (IETF RFC 5547 [25]) media attribute a= line attribute = file-selector IETF RFC 5547 [25] file-selector selector[1] filename name of the file to be transferred e.g. "TestFile.txt" filesize size of the file to be transferred filetype type of the file to be transferred e.g. "text/plain" hash algorithm "sha-1" value hash value of the file to be transferred media attribute a= line attribute = file-date IETF RFC 5547 [25] file-date date-param[1] type "creation" date-time date and time when the file has been created e.g. "Mon, 20 Dec 2021 15:01:31 +0100" IETF RFC 5322 [26] Table 6.2.3.3.3-2A: MIKEY-SAKKE I_MESSAGE (Table 6.2.3.3.3-2) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.9.1-2 Information Element Value/remark Comment Reference Condition IDRi payload ID data px_MCPTT_ID_User_A MCPTT ID associated with the initiating user IDRr payload ID data px_MCPTT_ID_User_B MCPTT ID associated to the receiving user ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 235 Table 6.2.3.3.3-3: SIP INVITE from the MCData Server (IUT) to the SS-UE2 (Step 1, Table 6.2.3.3.2-1; Step 2, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.10.3.3-1 Information Element Value/remark Comment Reference Condition To addr-spec user-info and host px_MCX_SIP_PublicUserId_B Max-Forwards value any allowed value Session-Expires generic-param any allowed value Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table 6.2.3.3.3-4 MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.2.3.3.3-5 MIME body part MCData Data signalling message MIME-part-body MCData Protected Payload Message containing FD SIGNALLING PAYLOAD as described in ETSI TS 136 579- 7 [4] (3GPP TS 36.579-7), Table 6.2.10.3.3-3A Table 6.2.3.3.3-4: SDP for SIP INVITE (Table 6.2.3.3.3-4) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.10.3.3-2 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 Session attribute present only if there is no key- mgmt media attribute in the media description for data a= line attribute = key-mgmt key-mgmt mikey MIKEY-SAKKE I_MESSAGE as specified in Table 6.2.3.3.3-2A 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 236 Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.10.3.3-2 Information Element Value/remark Comment Reference Condition 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 present only if there is no key- mgmt attribute at session level key-mgmt mikey MIKEY-SAKKE I_MESSAGE as specified in Table 6.2.3.3.3-2A Table 6.2.3.3.3-5: MCData-Info (Table 6.2.3.3.3-3) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.10.3.3-3 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params mcdata-request-uri Encrypted <mcdata-request- uri> with mcdataURI set to px_MCData_ID_User_B Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A mcdata-calling-user-id Encrypted <mcdata-calling- user-id> with mcdataURI set to px_MCData_ID_User_A Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A request-type "one-to-one-fd" Table 6.2.3.3.3-6: SIP 200 (OK) from the SS-UE2 (Step 1, Table 6.2.3.3.2-1; Step 4, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.10.3.3-4 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.3.3.3-7 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 237 Table 6.2.3.3.3-7: SDP for SIP 200 (OK) (Table 6.2.3.3.3-6) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.10.3.3-5 Information Element Value/remark Comment Reference Condition Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "22222222" 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 "22222222" 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-UE2 The transport port to which the media stream is sent Connection Data c= line connection-address IP address of the SS-UE2 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-UE2 port same value as in the media line session id assigned by the SS-UE2 transport "tcp" URI-parameter not present Table 6.2.3.3.3-8: SIP 200 (OK) from the MCData Server (IUT) to SS-UE1 (Step 1, Table 6.2.3.3.2-1; Step 5, Annex A, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.9.3.3-4 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.3.3.3-9 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 238 Table 6.2.3.3.3-9: SDP for SIP 200 (OK) (Table 6.2.3.3.3-8) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.9.3.3-5 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 Table 6.2.3.3.3-10: MSRP SEND from the SS-UE1 (Step 2, Table 6.2.3.3.2-1; Step 1, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.9.3.3-6 Table 6.2.3.3.3-11: MSRP SEND from the MCData Server (IUT) to SS-UE2 (Step 2, Table 6.2.3.3.2-1; Step 3, Annex A, Table A.4.4.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.10.3.3-6 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 239 Table 6.2.3.3.3-12: SIP MESSAGE from the SS-UE2 (Step 4, Table 6.1.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.10.3.3-11 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) The URI of the SS-UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.2.3.3.3-5 MIME body part MCData Data signalling message MIME-part-body MCData Protected Payload Message containing FD NOTIFICATION as described in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.10.3.3-12 Table 6.2.3.3.3-13: Resource-lists (Table 6.2.3.3.3-12) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3 Information Element Value/remark Comment Reference Condition resource-lists list name attribute display-name entry[1] uri attribute px_MCData_ID_User_A The MCData ID of the target MCData user Table 6.2.3.3.3-14: SIP MESSAGE from the MCData Server (IUT) to SS-UE1 (Step 4, Table 6.1.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.9.3.3-13 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServ iceId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 6.2.4 MCDATA Server - MCDATA Client / File Distribution (FD) / Accessing list of deferred data group communications |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { SS-UE1 (MCData Client) requests discovery of the absolute URI by sending a SIP MESSAGE message } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 200 (Ok) to UE1 (MCData Client) } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 240 (2) with { IUT (MCData Server) having requested an FD } ensure that { when { the SS-UE1 (MCData Client) initiates FD "file 1" upload by sending a HTTP POST request } then { IUT (MCData Server) responds with a HTTP 201 (Created) } } (3) with { IUT (MCData Server) having requested an FD } ensure that { when { SS-UE1 (MCData Client) requests FD upload by sending a SIP MESSAGE message with disposition request "FILE DOWNLOAD COMPLETED" } then { IUT (MCData Server) sends a SIP MESSAGE message to UE2 (MCData Client) and responds with a SIP 202 (Accepted) to UE1 (MCData Client) } } (4) with { IUT (MCData Server) having requested an FD } ensure that { when { SS-UE2 (MCData Client) requests FD upload by sending a SIP MESSAGE message with disposition notification "FILE DOWNLOAD DEFERRED" } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } (5) with { IUT (MCData Server) having requested an FD } ensure that { when { SS-UE1 (MCData Client) requests the list of deferred data group communications by sending a SIP MESSAGE message } then { IUT (MCData Server) responds with a SIP 200 (Ok) to UE1 (MCData Client) and sends a SIP MESSAGE message to UE1 (MCData Client) containing the list of deferred data group communications } } |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 11.3.1, 11.3.3.1, 11.3.3.2, 6.3.2.1, 15.1.12.1, 11.3.2.1, 6.2.4.1, 15.1.11.1. Unless otherwise stated, these are Rel-14 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 11.3.1] "Accessing list of deferred data group communication allows a MCData user to request for the list of files that have been deferred for future download. The procedures are applicable for FD using HTTP." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 11.3.3.1] "Upon receipt of a "SIP MESSAGE request for the list of deferred group communications", the participating MCData function: 1) shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [5]; 2) shall send SIP 200 (OK) response towards MCData server according to 3GPP TS 24.229 [5]; and 3) shall follow the procedure described in subclause 11.3.3.2 to send response." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 11.3.3.2] "To send the list of deferred group communications, the participating MCData function: 1) shall build the SIP MESSAGE request as specified in subclause 6.3.2.1; 2) shall generate DEFERRED DATA RESPONSE message as specified in subclause 15.1.12.1; 3) shall include in the SIP request, the DEFERRED DATA RESPONSE message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in subclause E.1; and 4) shall send the SIP MESSAGE request towards the participating MCData function according to rules and procedures of 3GPP TS 24.229 [5]. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 241 When generating a DEFERRED DATA RESPONSE message as specified in subclause 15.1.12, the MCData client: 1) shall set the number of payloads IE to the number of FD using HTTP communication which are deferred as per the stored file list: a) for each deferred file from the list, shall copy the payload IE value from the stored list to the payload IE value of the outgoing message being generated;" [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 6.3.2.1] "This subclause is referenced from other procedures. The participating MCData function shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6] and: 1) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [8] that were received (if any) in the incoming SIP MESSAGE request; 2) shall set the Request-URI of the outgoing SIP MESSAGE request to the public user identity associated to the MCData ID of the terminating MCData user; 3) shall populate the outgoing SIP MESSAGE request MIME bodies as specified in subclause 6.4 and 4) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP MESSAGE request to the P- Asserted-Identity header field of the outgoing SIP MESSAGE request." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 15.1.12.1] "This message is sent by the MCData server to the MCData UE as response to the list of deferred group communications request from the MCData UE. Message type: DEFERRED DATA RESPONSE Direction: Server to UE Table 15.1.12.1-1: DEFERRED DATA RESPONSE message content IEI Information Element Type/Reference Presence Format Length Deferred data response message identity Message type 15.2.2 M V 1 Number of payloads Number of payloads 15.2.12 M V 1 7A Security parameters and Payload MCData Protected Payload message 3GPP TS 33.180 [26] O TLV-E 32-x 78 Payload Payload 15.2.13 O TLV-E 3-x " [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 11.3.2.1] "Upon receiving a request from the MCData user to access the list of deferred data group communications, the MCData client: 1) shall build the SIP MESSAGE request as specified in subclause 6.2.4.1; 2) shall generate DEFERRED DATA REQUEST message as specified in subclause 15.1.11.1; 3) shall include in the SIP request, the DEFERRED DATA GROUP COMM message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in subclause E.1; and 4) shall send the SIP MESSAGE request towards the participating MCData function according to rules and procedures of 3GPP TS 24.229 [5]." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 242 [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 6.2.4.1] "This subclause is referenced from other procedures. In a SIP MESSAGE request, the MCData client: … 2) when sending FD messages, FD disposition notifications or FD media storage function discovery messages: a) shall include an Accept-Contact header field containing the g.3gpp.mcdata.fd media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [8]; b) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [8]; and c) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" (coded as specified in 3GPP TS 24.229 [5]), in a P-Preferred-Service header field according to IETF RFC 6050 [7] in the SIP MESSAGE request; 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 [5]; and 4) shall set the Request-URI to the public service identity identifying the participating MCData function serving the MCData user." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 15.1.11.1] "This message is sent by the MCData UE to MCData server to request the list of group communications which was deferred by the MCData user. Message type: DEFERRED DATA REQUEST Direction: UE to server Table 15.1.11.1-1: DEFERRED DATA REQUEST message content IEI Information Element Type/Reference Presence Format Length Deferred data request message identity Message type 15.2.2 M V 1 " |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.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). - Test File 1 for CO FD as specified in clause A.2.1 is available at the SS-UE1 for upload. IUT: - IUT (MCData Server). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 243 - 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 Storage Function, the MCData User Database, the SIP AS, the HTP Server, the HTTP Client, the MSRP TCP Server and the MSRP TCP Client. - The IUT (MCData Server) is the acting Participating Server and Controlling Server. Preamble: - In the MCData Group Configuration document the <mcdata-on-network-max-data-size-auto-recv> shall be set to 0 to indicate non-mandatory download independent from the file size. - The IUT (MCData Server) is connected to PLMN1. - 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. - In the MCData Group Configuration document the <mcdata-on-network-max-data-size-auto-recv> shall be set to 0 to indicate non-mandatory download independent from the file size. - SS-UE1 (MCData client) and SS-UE2 (MCData client) are affiliated to the Prearranged group. - The IUT (MCData Server) is the controlling server of the Prearranged group. |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.3.2 Test procedure sequence | Table 6.2.4.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'Discovery of the absolute URI of the media storage function' as described in Annex A, Table A.4.10.3-1? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perform procedure 'FD File upload using HTTP' as described in Annex A, Table A.4.8.3-1, to send test file 1 (ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), clause A.2.1)? - - 2 P 3 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a group FD SIGNALLING PAYLOAD message for non mandatory download, containing the URL of the file and with disposition request "FILE DOWNLOAD COMPLETED UPDATE"? - - 3 P 4 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a FD disposition notification of "FILE DOWNLOAD DEFERRED" from SS-UE2 (MCData client), for the file sent at step 2? - - 4 P 5 The SS-UE1 (MCData Client) sends a SIP MESSAGE to request the list of deferred data group communications. --> SIP MESSAGE - - 6 Check: Does the MCData Server (IUT) respond with a SIP 200 (OK) message? <-- SIP 200 (OK) 5 P 7 Check: Does the MCData Server (IUT) send a SIP MESSAGE containing the list of deferred data group communications? <-- SIP MESSAGE 5 P 8 The SS-UE1 (MCData Client) responds with a SIP 200 (OK) message. --> SIP 200 (OK) - - ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 244 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.2.4.3.3 Specific message contents | Table 6.2.4.3.3-1: HTTP POST from the SS-UE1 (Step 2, Table 6.2.4.3.2-1; Step 1, Annex A, Table A.4.8.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.13.3.3-7 Table 6.2.4.3.3-2: HTTP 201 Created from the MCData Server (IUT) to the SS-UE1 (Step 2, Table 6.2.4.3.2-1; Step 3, Annex A, Table A.4.8.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.13.3.3-10 Table 6.2.4.3.3-3: SIP MESSAGE from the SS-UE1 (Step 3, Table 6.2.4.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.13.3.3-11 Table 6.2.4.3.3-4: SIP MESSAGE from the MCData Server (IUT) to the SS-UE2 (Step 3, Table 6.2.4.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCDATA_FD, MCDATA_SIGNALLING Information Element Value/remark Comment Reference Condition Request-Line IETF RFC 3261 [21] IETF RFC 5031 [22] Request-URI px_MCX_SIP_PublicUserId_B P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServiceId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.4.1 Message-body MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.2.4.3.3-5 MIME body part MCData Data signalling message MIME-part-body MCData Protected Payload Message containing FD SIGNALLING PAYLOAD as described in Table 6.2.4.3.3-6 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 245 Table 6.2.4.3.3-5: MCData-Info (Table 6.2.4.3.3-4) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 5.5.3.2.2-3, condition MCD_grp Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params request-type "group-fd" mcdata-request-uri Encrypted <mcdata-request-uri> with mcdataURI set to px_MCData_ID_User_B Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A mcdata-calling-user-id Encrypted <mcdata-calling-user- id> with mcdataURI set to px_MCData_ID_User_A Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A mcdata-client-id Encrypted <mcdata-client-id> with mcdataString set to px_MCX_Client_A_ID Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.2-3A Table 6.2.4.3.3-6: FD SIGNALLING PAYLOAD (Table 6.2.4.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.8.5-1, condition FD_HTTP Table 6.2.4.3.3-7: SIP MESSAGE from the SS-UE2 (Step 4, Table 6.2.4.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCDATA_FD, RESOURCE_LISTS, MCDATA_SIGNALLING 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) The URI of the SS-UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.2.4.3.3-8 MIME body part MCData-Info MIME-part-headers MCData-Info as described in Table 6.2.4.3.3-9 MIME body part MCData Data signalling message MIME-part-body MCData Protected Payload Message containing FD NOTIFICATION as described in Table 6.2.4.3.3-10 Table 6.2.4.3.3-8: Resource-lists (Table 6.2.4.3.3-7) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3 Information Element Value/remark Comment Reference Condition resource-lists list name attribute display-name entry[1] uri attribute px_MCData_ID_User_A The MCData ID of the target MCData user ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 246 Table 6.2.4.3.3-9: MCData-Info (Table 6.2.4.3.3-7) 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 mcdata-info mcdata-Params mcdata-calling-group-id Encrypted <mcdata-request- uri> with mcdataURI set to px_MCData_Group_A_ID Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.2.1-3A Table 6.2.4.3.3-10: FD NOTIFICATION (Table 6.2.4.3.3-7) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.8.7-1, condition FD_DEFERRED Table 6.2.4.3.3-11: SIP MESSAGE from the MCData Server (IUT) to the SS-UE1 (Step 4, Table 6.2.4.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.13.3.3-13 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServiceId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 Table 6.2.4.3.3-12: SIP MESSAGE from the SS-UE1 (Step 5, Table 6.2.4.3.2-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.13.3.3-16 Table 6.2.4.3.3-13: SIP MESSAGE from the MCData Server (IUT) to the SS-UE1 (Step 7, Table 6.2.4.3.2-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.2.13.3.3-18 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServ iceId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3 Enhanced Status (ES) | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1 MCDATA Server - MCDATA Client / Enhanced Status (ES) | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1.1 Test Purpose (TP) | (1) with { IUT (MCData Server) connected to PLMN1 } ensure that { when { SS-UE1 (MCData Client) requests one-to-one Standalone SDS by sending a SIP MESSAGE message with disposition request "DELIVERY" and an enhanced status payload with id = 0} then { IUT (MCData Server) sends a SIP MESSAGE message to UE2 (MCData Client) and responds with a SIP 202 (Accepted) to UE1 (MCData Client) } } ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 247 (2) with { IUT (MCData Server) having requested Enhanced Status } ensure that { when { SS-UE2 (MCData Client) requests one-to-one Standalone SDS by sending a SIP MESSAGE message with disposition notification "DELIVERED" } then { IUT (MCData Server) sends a SIP MESSAGE message to UE1 (MCData Client) and responds with a SIP 202 (Accepted) to UE2 (MCData Client) } } |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 282 [13] (3GPP TS 24.282), clauses 14.2.2.1, 14.2.2.2, 14.2.3.1, 14.2.3.2, 9.2.2.3.1, 9.2.2.3.2, 9.2.2.4.1, 9.2.2.4.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 14.2.2.1] "Upon receipt of a "SIP MESSAGE request for standalone SDS for originating participating MCData function", the participating MCData function should follow the procedure described in subclause 9.2.2.3.1." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 14.2.2.2] "Upon receipt of a "SIP MESSAGE request for standalone SDS for terminating participating MCData function", the participating MCData function should follow the procedure described in subclause 9.2.2.3.2." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 14.2.3.1] "Upon receipt of a "SIP MESSAGE request for standalone SDS for controlling MCData function", the controlling MCData function should follow the procedure described in subclause 9.2.2.4.1." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 14.2.3.2] "Upon receipt of a "SIP MESSAGE request for standalone SDS for controlling MCData function", the controlling MCData function should follow the procedure described in subclause 9.2.2.4.2." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.3.1] "Upon receipt of a "SIP MESSAGE request for standalone SDS for originating participating MCData function", the participating MCData function: … 2) shall determine the MCData ID of the originating user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request, and shall authorise the calling user; NOTE: 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) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request is: a) set to a value of "group-sds", shall determine the public service identity of the controlling MCData function associated with the MCData group identity in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the SIP MESSAGE request; or b) set to a value of "one-to-one-sds", shall determine the public service identity of the controlling MCData function hosting the one-to-one standalone SDS service for the calling user; … 6) shall determine whether the MCData user identified by the MCData ID is authorised for MCData communications by following the procedures in subclause 11.1; … ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 248 9) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]; 10) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCData function as determined by step 4) in this subclause; 11) shall copy all MIME bodies included in the incoming SIP MESSAGE request to the outgoing SIP MESSAGE request; 12) shall include the MCData ID of the originating user in the <mcdata-calling-user-id> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP MESSAGE request; 12A) if the incoming SIP MESSAGE request contains an application/vnd.3gpp.mcdata-info+xml MIME body that contains a <functional-alias-URI> element, shall check if the status of the functional alias is activated for the MCData ID. If the functional alias status is activated, then the participating MCData function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the outgoing SIP INVITE request to the received value, otherwise shall not include a <functional-alias-URI> element; 13) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; 14) 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; and 15) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [5]. Upon receipt of a SIP 202 (Accepted) response in response to the SIP MESSAGE request in step 15): 1) shall generate a SIP 202 (Accepted) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 202 (Accepted) response to the MCData client according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 200 (OK) response in response to the SIP MESSAGE request in step 15): 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 200 (OK) response to the MCData client according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request in step 15) the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the MCData client according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.3.2] "Upon receipt of a "SIP MESSAGE request for standalone SDS for terminating participating MCData function", the participating MCData function: … 2) shall use the MCData ID present in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata- info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCData ID and public user identity of the terminating MCData user; … 4) shall generate an outgoing SIP MESSAGE request as specified in subclause 6.3.2.1; 5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" (coded as specified in 3GPP TS 24.229 [5]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and 6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [5]. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 249 Upon receipt of a SIP 200 (OK) response in response to the above SIP MESSAGE request, the participating MCData function: 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [5]; and 2) shall send the SIP 200 (OK) response to the controlling MCData function according to 3GPP TS 24.229 [5]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP MESSAGE request, the participating MCData function: 1) shall generate a SIP response according to 3GPP TS 24.229 [5]; 2) shall include Warning header field(s) that were received in the incoming SIP response; and 3) shall forward the SIP response to the controlling MCData function according to 3GPP TS 24.229 [5]." [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.4.1] "This subclause describes the procedures for sending a SIP MESSAGE from the controlling MCData function and is initiated by the controlling MCData function as a result of an action in subclause 9.2.2.4.2. The controlling MCData function: 1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [5] and IETF RFC 3428 [6]; 2) shall include an Accept-Contact header field containing the g.3gpp.mcdata.sds media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request; 3) 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.mcdata.sds" along with parameters "require" and "explicit" according to IETF RFC 3841 [8] in the outgoing SIP MESSAGE request; 4) shall copy the following MIME bodies in the received SIP MESSAGE request into the outgoing SIP MESSAGE request by following the guidelines in subclause 6.4: a) application/vnd.3gpp.mcdata-info+xml MIME body; b) application/vnd.3gpp.mcdata-signalling MIME body; and c) application/vnd.3gpp.mcdata-payload MIME body 5) in the application/vnd.3gpp.mcdata-info+xml MIME body: a) shall set the <mcdata-request-uri> element set to the MCData ID of the terminating user; and b) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP MESSAGE request was set to a value of "group-sds", shall set the <mcdata-calling-group-id> element to the group identity; 6) shall set the Request-URI to the public service identity of the terminating participating MCData function associated to the MCData user to be invited; 7) shall copy the public user identity of the calling MCData user from the P-Asserted-Identity header field of the incoming SIP MESSAGE request into the P-Asserted-Identity header field of the outgoing SIP MESSAGE request; 8) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds"; and 9) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [5]. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 250 [ETSI TS 124 282 [13] (3GPP TS 24.282), clause 9.2.2.4.2] "Upon receipt of a "SIP MESSAGE request for standalone SDS for controlling MCData function", the controlling MCData function: … 2) if the SIP MESSAGE does not contain: a) an application/vnd.3gpp.mcdata-info+xml MIME body; b) an application/vnd.3gpp.mcdata-signalling MIME body; and c) an application/vnd.3gpp.mcdata-payload MIME body; shall reject the SIP MESSAGE request …, and shall not continue with the rest of the steps in this subclause; 3) shall decode the contents of the application/vnd.3gpp.mcdata-signalling MIME body contained in the SIP MESSAGE; 4) if the application/vnd.3gpp.mcdata-signalling MIME body contains a SDS SIGNALLING PAYLOAD message with a SDS disposition request type IE, shall store the value of the Conversation ID IE and the value of the Message ID IE in the SDS SIGNALLING PAYLOAD message; NOTE: The controlling MCData function uses the Conversation ID and Message ID for correlation with disposition notifications. 5) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request is set to a value of "one-to-one-sds" and: … b) the SIP MESSAGE request: … ii) contains an application/resource-lists MIME body with exactly one <entry> element, shall send a SIP MESSAGE request to the MCData user identified in the <entry> element of the MIME body, as specified in subclause 9.2.2.4.1; 6) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request is set to a value of "group-sds": a) shall retrieve the group document associated with the group identity in the SIP MESSAGE request by following the procedures in subclause 6.3.3, and shall continue with the remaining steps if the procedures in subclause 6.3.3 were successful; … h) shall determine targeted group members for MCData communications by following the procedures in subclause 6.3.4; j) if the procedures in subclause 6.3.4 result in no affiliated members found in the selected MCData group, shall return a SIP 403 (Forbidden) response with the warning text set to "198 no users are affiliated to this group" in a Warning header field as specified in subclause 4.9, and skip the rest of the steps below; and k) shall send SIP MESSAGE requests to the targeted group members identified in step h) above by following the procedure in subclause 9.2.2.4.1; 7) shall generate a SIP 202 (Accepted) response in response to the "SIP MESSAGE request for standalone SDS for controlling MCData function"; and 8) shall send the SIP 202 (Accepted) response towards the originating participating MCData function according to 3GPP TS 24.229 [5]." ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 251 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1.3 Test description | |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1.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 Storage Function, the MCData User Database, the SIP AS, the HTP Server, the HTTP Client, the MSRP TCP Server and the MSRP TCP Client. - The IUT (MCData Server) is the acting Participating Server and Controlling Server. Preamble: - The <max-payload-size-sds-cplane-bytes> element in the MCData service configuration document as specified in 3GPP ETSI TS 124 484 [8] (3GPP TS 24.484), shall be large enough to allow the sending of the standalone SDS message using the signalling plane. - The IUT (MCData Server) is connected to PLMN1. - 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 | 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 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward an Enhanced Status from SS-UE1 (MCData client) to SS-UE2 (MCData Client), with disposition request "DELIVERY" and an enhanced status payload with id=0 ("going to the operation site")? - - 1 P 2 Check: Does the MCData Server (IUT) correctly perform procedure 'E2E SDS or FD message transfer using signalling plane' as described in Annex A, Table A.4.1.3-1 to forward a disposition notification of "DELIVERED", from SS-UE2 (MCData client) to SS-UE1 (MCData Client)? - - 2 P ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 252 |
f2b123fa8157b4e7912783c4f4ab1824 | 104 149-1 | 6.3.1.3.3 Specific message contents | Table 6.3.1.3.3-1: SIP MESSAGE from the SS-UE1 (Step 1, Table 6.3.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.3.1.3.3-1 Table 6.3.1.3.3-2: SIP MESSAGE from the MCData Server (IUT) to SS-UE2 (Step 1, Table 6.3.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.3.2.3.3-1 Information Element Value/remark Comment Reference Condition Request-Line IETF RFC 3261 [21] IETF RFC 5031 [22] Request-URI px_MCX_SIP_PublicUserId_B P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServiceId_A The public service identity identifying the controlling MCData function. Message-body MIME body part not present Resource lists MIME body part MCData-Info MIME-part-body MCData-Info as described in Table 6.3.1.3.3-3 MIME body part MCData Data signalling message MIME-part-body MCData Protected Payload Message containing SDS SIGNALLING PAYLOAD as described in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.3.2.3.3-3 MIME body part MCData Data message MIME-part-body DATA PAYLOAD as described in ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.3.2.3.3-4 Table 6.3.1.3.3-3: MCData-Info (Table 6.3.1.3.3-2) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.3.2.3.3-2 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params mcdata-request-uri Encrypted <mcdata-request- uri> with mcdataURI set to px_MCData_ID_User_B mcdata-calling-user-id Encrypted <mcdata-calling- user-id> with mcdataURI set to px_MCData_ID_User_A ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 253 Table 6.3.1.3.3-4: SIP MESSAGE from the SS-UE2 (Step 2, Table 6.3.1.3.2-1; Step 1, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.3.2.3.3-6 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) The URI of the SS-UE2 Message-body MIME body part Resource lists MIME-part-body Resource-lists as described in Table 6.3.1.3.3-5 Table 6.3.1.3.3-5: Resource-lists (Table 6.3.1.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-3 Information Element Value/remark Comment Reference Condition resource-lists list name attribute display-name entry[1] uri attribute px_MCData_ID_User_A The MCData ID of the target MCData user Table 6.3.1.3.3-6: SIP MESSAGE from the MCData Server (IUT) to SS-UE1 (Step 2, Table 6.1.1.3.2-1; Step 3, Annex A, Table A.4.1.3-1) Derivation Path: ETSI TS 136 579-7 [4] (3GPP TS 36.579-7), Table 6.3.1.3.3-4 Information Element Value/remark Comment Reference Condition P-Asserted-Identity IETF RFC 3261 [21] name-addr tsc_MCData_PublicServic eId_A The public service identity identifying the controlling MCData function. ETSI TS 124 282 [13] (3GPP TS 24.282), clause 12.2.3 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 254 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 ETSI TS 136 579-3 [2] (3GPP TS 36.579-3), 3GPP TS 36.579-8 [31] and the present document. The procedures specified are required to ensure that any MC service can take place 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. A.2.3.2 Definition of system information messages N/A. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 255 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 - - 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 • 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 7.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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 256 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. 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. (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 • 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 257 A.2.5.3 Procedure 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. (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. A.2.5.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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. 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. (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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 258 A.2.6.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 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. 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 259 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 [5] (3GPP TS 24.379) clauses 9.2.1.3 and 9A.2.1.3; ETSI TS 124 281 [32] (3GPP TS 24.281) clause 8.2.1.3; ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 8.2.3 and 22.2.1.3 Message-body MIME body part MCPTT Info ETSI TS 124 379 [5] (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 MIME body part MCVIDEO Info ETSI TS 124 281 [32] (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 [13] (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 (note) <mcptt- request-uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [5] (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 (note) <mcvideo- request-uri> with mcvideoURI set to px_MCVIDEO_ID_User_A ETSI TS 124 281 [32] (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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 260 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 (note) <mcdata- request-uri> with mcdataURI set to px_MCDATA_ID_User_A ETSI TS 124 282 [13] (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.3.7.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 SUBSCRIBE-RSP 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. 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 (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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 261 A.2.9.2 Definition of system information messages N/A. 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 (Note) SIP 200 (OK) - - NOTE: The SS-UE being used is specified in the test case calling the procedure. A.2.9.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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. 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 262 A.2.10.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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. 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 263 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. 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) - - 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (note) <mcptt-request- uri> with mcpttURI set to px_MCPTT_ID_User_A ETSI TS 124 379 [5] (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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 264 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 (note) <mcvideo- request-uri> with mcvideoURI set to px_MCVIDEO_ID_User_A ETSI TS 124 281 [32] (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-request-uri encrypted (note) <mcdata- request-uri> with mcdataURI set to px_MCDATA_ID_User_A ETSI TS 124 282 [13] (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 Table A.2.12.4-6: 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-7: 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 265 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 266 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 (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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (Note) NOTE: With condition re_INVITE for session modifications. 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 267 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 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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. 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 (note) --> SIP 100 (Trying) - - 3 The SS-UE (MCX Client) responds with a SIP 200 (OK) (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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 268 A.2.16.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (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. 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 (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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 269 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. 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 - - 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (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 (note) NOTE: With condition re_INVITE for session modifications. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 270 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. 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 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 271 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. 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) - - 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 272 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. 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 273 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 operation 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 274 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 (NOTE1) - - - - 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 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.1.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 149-1 V1.1.1 (2026-02) 275 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 (note), with condition MCPTT NOTE: With condition re_INVITE for session modifications. Information Element Value/remark Comment Reference Condition Session-Expires IETF RFC 4028 [23] generic-param "1800" The recommended initial value is 1800 in IETF RFC 4028 [23]. 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 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 [33] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [34] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [35] 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 [33] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [36] "RR" 2000 IETF RFC 3556 [36] ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 276 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 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 [37] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [37] (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.A.2.1-1) Note 3 ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 GROUP- CALL OR CHAT- GROUP- CALL ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 277 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 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 [37] (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 NOTE1 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 (note), with condition MCPTT NOTE: With condition re_INVITE for session modifications. Information Element Value/remark Comment Reference Condition Resource-Priority IETF RFC 4412 [38] IETF RFC 7134 [20] IETF RFC 8101 [39] 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 278 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1 (note), with condition MCPTT NOTE: With condition re_INVITE for session modifications. Information Element Value/remark Comment Reference Condition 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 [23] delta-seconds any allowed value 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 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.A.2.1-1) Note 2 ETSI TS 124 380 [37] (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 [37] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_queueing not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [37] (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). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 279 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 (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.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 [19] value "application/sdp" 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" Session Name " " s= line single empty space indicating no session name Bandwidth b= line "AS" 38 ETSI TS 126 114 [33] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [34] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [35] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 280 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 Connection Data c= line connection-address IP address of the SS- UE Bandwidth b= line "AS" 38 ETSI TS 126 114 [33] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [36] "RR" 2000 IETF RFC 3556 [36] 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 NOT WITHOUT_ FLOORCO NTROL mc_queueing present if included in the offer Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 281 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 [37] (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.A.2.1-1) ETSI TS 124 380 [37] (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 [37] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_granted not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_F LOOR_GR ANTED mc_implicit_request not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 282 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 [37] (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 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_no_floor_ctrl not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 NOTE 1: If the SS-UE requests an implicit floor (Option b of NOTE 1 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 1 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 283 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 (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. (NOTE1) - - - - 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 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 149-1 V1.1.1 (2026-02) 284 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 [23] generic-param "1800" The recommended initial value is 1800 in IETF RFC 4028 [23] 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 [33] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [34] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [35] 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 [33] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [36] "RR" 2000 IETF RFC 3556 [36] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 285 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 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 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 [37] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [37] (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.A.2.1-1) Note ETSI TS 124 380 [37] (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 149-1 V1.1.1 (2026-02) 286 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 [38] IETF RFC 7134 [20] IETF RFC 8101 [39] 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 [23] 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 149-1 V1.1.1 (2026-02) 287 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.A.2.1-1) Note ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 mc_queueing not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [37] (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 (note 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 [19] 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 149-1 V1.1.1 (2026-02) 288 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 [33] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [34] port port number assigned by the SS- UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [35] 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 [33] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [36] "RR" 2000 IETF RFC 3556 [36] 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 289 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[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-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 [37] (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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 290 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.A.2.1-1) ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 mc_ssrc any value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 NOTE 1: If the SS-UE requests an implicit floor (Option b of NOTE 1 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 291 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. (NOTE1) - - - - 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 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 149-1 V1.1.1 (2026-02) 292 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 [23] generic-param "1800" The recommended initial value is 1800 in IETF RFC 4028 [23]. 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" Session Name " " s= line single empty space indicating no session name Bandwidth b= line "AS" 38 ETSI TS 126 114 [33] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [34] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [35] 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 [33] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [36] "RR" 2000 IETF RFC 3556 [36] ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 293 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 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 [37] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [37] (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 [37] (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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 294 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 [38] IETF RFC 7134 [20] IETF RFC 8101 [39] 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 [23] 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 295 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 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. 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 [37] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 mc_queueing not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 pc_MCPTT _FloorRequ estQueuein g 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 [19] value "application/sdp" Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.3.4-8 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 296 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 Bandwidth b= line "AS" 38 ETSI TS 126 114 [33] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [34] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [35] 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 [33] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [36] "RR" 2000 IETF RFC 3556 [36] 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 297 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-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 [37] (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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 298 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. 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. 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 [37] (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 [37] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 mc_granted not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_F LOOR_GR ANTED mc_implicit_request not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_ssrc not present ETSI TS 124 380 [37] (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 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_no_floor_ctrl not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 299 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. 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 - - 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 - - ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 300 A.3.4.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 [21] MIME body part Resource list IETF RFC 5366 [17] 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" 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 301 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 Bandwidth b= line "AS" 38 ETSI TS 126 114 [33] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [34] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [35] 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 [33] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [36] "RR" 2000 IETF RFC 3556 [36] 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 [29] candidate candidate for RTP foundation 1234 arbitrarily selected priority 2130706431 IETF RFC 5245 [29] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id media attribute a=line attribute="candidate" IETF RFC 5245 [29] candidate candidate for RTCP foundation 1234 Same as for RTP priority 2130706430 IETF RFC 5245 [29] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id Media description[2] Media description for media control ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 302 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 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 [37] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [37] (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.A.2.1- 1) Note 2 ETSI TS 124 380 [37] (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 [37] (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 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_ssrc any value if present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_no_floor_ctrl not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 format specific parameters WITHOUT_ FLOORCO NTROL mc_queueing not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 303 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 not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 mc_granted not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_implicit_request not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_ssrc not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_no_floor_ctrl present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 media attribute a=line attribute="candidate" IETF RFC 5245 [29] candidate candidate for Media Control messages foundation 4321 arbitrarily selected; different than for RTP/RTCP priority 2130706430 IETF RFC 5245 [29] 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 [34] media attribute a=line attribute="candidate" IETF RFC 5245 [29] ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 304 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 candidate candidate for RTP foundation any value priority any value IETF RFC 5245 [29] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id media attribute a=line attribute="candidate" IETF RFC 5245 [29] candidate candidate for RTCP foundation any value priority any value IETF RFC 5245 [29] 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 [37] (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.A.2.1-1) ETSI TS 124 380 [37] (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 [37] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_granted not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_F LOOR_GR ANTED mc_implicit_request not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 305 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_ssrc not present ETSI TS 124 380 [37] (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 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_no_floor_ctrl not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 format specific parameters WITHOUT_ FLOORCO NTROL mc_queueing not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_priority not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 mc_granted not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_implicit_request not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_ssrc not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_no_floor_ctrl present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 media attribute a=line attribute="candidate" IETF RFC 5245 [29] candidate candidate for Media Control messages foundation any value priority any value IETF RFC 5245 [29] 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 306 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 [38] IETF RFC 7134 [20] IETF RFC 8101 [39] 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 [23] 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 307 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.A.2.1-1) Note 2 ETSI TS 124 380 [37] (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 [37] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_queueing not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [37] (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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 308 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 [19] 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 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 [33] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [34] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [35] 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 [33] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [36] "RR" 2000 IETF RFC 3556 [36] 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" ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 309 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 =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 NOT WITHOUT_ FLOORCO NTROL mc_queueing present if included in the offer Parameter has no value ETSI TS 124 380 [37] (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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 310 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 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. 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 311 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 [21] MIME body part Resource list IETF RFC 5366 [17] MIME-part-body Resource-lists as described in Table A.3.5.4-2 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 [33] (3GPP TS 26.114) Table K.6 Media description[1] Media description for audio ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 312 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 description m= line media = audio IETF RFC 4867 [34] port port number assigned by the SS-UE (even integer) The transport port to which the media stream is sent IETF RFC 6335 [35] 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 [33] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [36] "RR" 2000 IETF RFC 3556 [36] 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 [29] candidate candidate for RTP foundation 1234 arbitrarily selected priority 2130706431 IETF RFC 5245 [29] clause 4.2: 224 * 126 + 28 * 65535 + 256 - component id media attribute a=line attribute="candidate" IETF RFC 5245 [29] candidate candidate for RTCP foundation 1234 Same as for RTP priority 2130706430 IETF RFC 5245 [29] 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 313 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 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 [37] (3GPP TS 24.380) cl. 12.1.2.3 Present Parameter has no value ETSI TS 124 380 [37] (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.A.2.1-1) Note 2 ETSI TS 124 380 [37] (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 [37] (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 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_ssrc any value if present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_no_floor_ctrl not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 format specific parameters WITHOUT_ FLOORCO NTROL mc_queueing not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_priority not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 314 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_granted not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_implicit_request not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_ssrc not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_no_floor_ctrl present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 media attribute a=line attribute="candidate" IETF RFC 5245 [29] candidate candidate for Media Control messages foundation 4321 arbitrarily selected; different than for RTP/RTCP priority 2130706430 IETF RFC 5245 [29] 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 [34] media attribute a=line attribute="candidate" IETF RFC 5245 [29] candidate candidate for RTP foundation any value priority any value IETF RFC 5245 [29] clause 4.2: ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 315 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 224 * 126 + 28 * 65535 + 256 - component id media attribute a=line attribute="candidate" IETF RFC 5245 [29] candidate candidate for RTCP foundation any value priority any value IETF RFC 5245 [29] 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 [37] (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.A.2.1-1) ETSI TS 124 380 [37] (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 [37] (3GPP TS 24.380) cl. 4.1.1.4 and cl. 14.3.3 PRIVATE- CALL mc_granted not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_F LOOR_GR ANTED mc_implicit_request not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_ssrc not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 316 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 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 [37] (3GPP TS 24.380) cl. 12.1.2.3 IMPLICIT_ GRANT_RE QUESTED mc_no_floor_ctrl not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 format specific parameters WITHOUT_ FLOORCO NTROL mc_queueing not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_priority not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 and cl. 14.3.3 mc_granted not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_implicit_request not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_ssrc not present ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 mc_no_floor_ctrl present Parameter has no value ETSI TS 124 380 [37] (3GPP TS 24.380) cl. 12.1.2.3 media attribute a=line attribute="candidate" IETF RFC 5245 [29] candidate candidate for Media Control messages foundation any value priority any value IETF RFC 5245 [29] 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 317 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 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. 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 149-1 V1.1.1 (2026-02) 318 A.3.6.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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. 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 149-1 V1.1.1 (2026-02) 319 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 [5] (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. 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 149-1 V1.1.1 (2026-02) 320 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 [21] IETF RFC 3903 [16] 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-6, condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 379 [5] (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 [5] (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-6, condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 379 [5] (3GPP TS 24.379) clause 9.2.2.2.5 MIME-part-body PIDF as described in Table A.3.8.4-7 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 [5] (3GPP TS 24.379) clause 9.2.2.3.5 ..p-id same value as received in the SIP PUBLISH message. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 321 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. 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 [5] (3GPP TS 24.379) clause 9A.2.1.3 MIME-part-body MCPTT-Info as described in Table A.2.7.4-2 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 request-type functional-alias-status- determination ETSI TS 124 379 [5] (3GPP TS 24.379) clause 9A.2.1.3 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 322 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 [5] (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. 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 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 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 323 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 [21] IETF RFC 3903 [16] 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-6, condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 379 [5] (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 [5] (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-6, condition MCPTT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 379 [5] (3GPP TS 24.379) clause 9A.2.2.2.5 MIME-part-body PIDF as described in Table A.3.10.4-7 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 [5] (3GPP TS 24.379) clause 9A.2.2.3.5 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 324 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. 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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.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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 325 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 326 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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. A.3.14.2 Definition of system information messages N/A. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 327 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 328 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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. A.3.16.2 Definition of system information messages N/A. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 329 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 ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 A.4 Generic test procedures for MCData Server operation A.4.1 E2E SDS or FD message transfer using signalling plane A.4.1.1 Initial conditions As specified in the test case which calls the procedure. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 330 A.4.1.2 Definition of system information messages N/A. A.4.1.3 Procedure Table A.4.1.3-1: E2E SDS or FD message transfer using signalling plane St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCData Client) sends a SIP MESSAGE request. --> SIP MESSAGE - - - EXCEPTION: Depending on the MCData Server implementation, steps 2 and 3 might be performed in parallel. - - - - 2 Check: Does the MCData Server (IUT) send a SIP 202 (Accepted) response? <-- SIP 202 (Accepted) - P 3 Check: Does the MCData Server (IUT) forward the SIP Message request to SS-UE2? <-- SIP MESSAGE - P 4 The SS-UE2 (MCData Client) sends a SIP 200 (OK) response. --> SIP 200 (OK) - - NOTE: The test case calling this procedure may switch the role of SS-UE1 and SS-UE2 clients. A.4.1.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCData Client) or SS-UE2 (MCData Client). A.4.2 MCData Participating Terminated SDS or FD message transfer using signalling plane A.4.2.1 Initial conditions As specified in the test case which calls the procedure. A.4.2.2 Definition of system information messages N/A. A.4.2.3 Procedure Table A.4.2.3-1: Participating Terminated SDS or FD message transfer using signalling plane St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCData Client) sends a SIP MESSAGE request. --> SIP MESSAGE - - 2 Check: Does the MCData Server (IUT) send a SIP 202 (Accepted) response? <-- SIP 202 (Accepted) - P ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 331 A.4.2.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to SS-UE (MCData Client). A.4.3 E2E MCData Call Establishment A.4.3.1 Initial conditions As specified in the test case which calls the procedure. A.4.3.2 Definition of system information messages N/A. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 332 A.4.3.3 Procedure Table A.4.3.3-1: E2E MCData Call Establishment St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCData client) sends a SIP INVITE requesting the establishment of an MCData call. --> SIP INVITE - - 2 Check: Does the MCData Server (IUT) send a SIP INVITE requesting the establishment of an MCData call to SS-UE2 (MCData Client)? <-- SIP INVITE P - EXCEPTION: Step 3 describes behaviour that depends on the MCData server implementation; it identifies a step sequence that take place if the MCDATA Server responds to a SIP INVITE with a SIP 100 (Trying). - - - - 3 The MCData server (IUT) sends a SIP 100 Trying <-- SIP 100 (Trying) - - 4 The SS-UE2 (MCData Client) responds with a SIP 200 (OK). --> SIP 200 (OK) - 5 Check: Does the MCData Server (IUT) respond with a SIP 200 (OK) to SS-UE1 (MCData Client)? <-- SIP 200 (OK) - P 6 The SS-UE1 (MCData Client) sends a SIP ACK to acknowledge the session establishment. --> SIP ACK - - 7 Check: Does the MCData server (IUT) send a SIP ACK to acknowledge the session establishment to SS-UE2 (MCData client)? <-- SIP ACK - P 8 The SS-UE1 (MCData client) connects to the TCP server at the MCData server side to establish an MSRP connection. (Note 1) - - - - 9 The SS-UE1 (MCData client) sends an empty MSRP SEND request to bind the TCP connection to the MSRP session. --> MSRP SEND - - 10 Check: Does the MCData server (IUT) send an MSRP 200 (OK) response? <-- MSRP 200 (OK) - P - EXCEPTION: Steps 11a1 - 11b3 describe behaviour that depends on which role of an endpoint the SS-UE2 (MCData client) has chosen in its SDP answer sent at step 4. - - - - 11a1 IF the SS-UE2 (MCData client) acts as passive endpoint (Note 2) THEN the MCData Server connects to the TCP server at the SS-UE2 side to establish an MSRP connection. Depending on the MCData Server implementation, steps 11a1-11a3 might be performed in parallel to steps 8-10. - - - - 11a2 Check: Does the MCData Server (IUT) send an empty MSRP SEND request to bind the TCP connection to the MSRP session? <-- MSRP SEND - P 11a3 The SS-UE2 (MCData client) sends an MSRP 200 (OK) response. --> MSRP 200 (OK) - - 11b1 ELSE (Note 3) the SS-UE2 (MCData client) connects to the TCP server at the MCData Server side to establish an MSRP connection. - - - - 11b2 The SS-UE2 (MCData client) sends an empty MSRP SEND request to bind the TCP connection to the MSRP session. --> MSRP SEND - - 11b3 Check: Does the MCData server (IUT) send an MSRP 200 (OK) response? <-- MSRP 200 (OK) - P NOTE 1: According to ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 9.2.3.4.2, 9.2.4.4.2 and 10.2.5.4.2 the MCData Server sets the a=setup attribute set to "passive" (see ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-3) The SS-UE's MCData client has the role of the active endpoint. NOTE 2: The MCData client indicates to act as passive endpoint by setting the a=setup attribute of the SDP answer at step 4 to "passive" (according to IETF RFC 4145 [15]). NOTE 3: The MCData client indicates to act as active endpoint by setting the a=setup attribute of the SDP answer at step 4 to "active" (according to IETF RFC 4145 [15]). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 333 A.4.3.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCData Client) or SS-UE2 (MCData Client). Table A.4.3.4-1: MSRP SEND (Steps 9 and 11b2, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.12.1.1-1, condition EMPTY_SEND_REQ Table A.4.3.4-2: MSRP SEND (Step 11a2, Table A.4.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.12.1.2-1, condition EMPTY_SEND_REQ A.4.4 E2E MSRP message transfer A.4.4.1 Initial conditions As specified in the test case which calls the procedure. A.4.4.2 Definition of system information messages N/A. A.4.4.3 Procedure Table A.4.4.3-1: E2E MSRP message transfer St Procedure Message Sequence TP Verdict U - S Message - EXCEPTION: Steps 1-2 are repeated until the SS-UE1 (MCData client) indicates the end of the message by setting the continuation-flag to "$" in the End-line of the MSRP SEND request at step 1. (Note 1) - - - - 1 The SS-UE1 (MCData client) sends an MSRP SEND request. --> MSRP SEND - - 2 Check: Does the MCData server (IUT) send an MSRP 200 (OK) response? <-- MSRP 200 (OK) - P 3 Check: Does the MCData Server (IUT) send an MSRP SEND request to SS-UE2 (MCData Client), containing the message received from the SS-UE1 (MCData Client)? (Note 2) <-- MSRP SEND - P 4 The SS-UE2 (MCData client) sends an MSRP 200 (OK) response. --> MSRP 200 (OK) - - NOTE 1: In case of no chunking there is only one MSRP SEND request which contains the entire data. In case of chunking there are more than one MSRP SEND requests containing the chunks of data and the content type shall be the same for all MSRP SEND requests. NOTE 2: It is assumed that in general there is no chunking in DL for MCData test cases and the MCData Server reassembles the data contained in the bodies of the MSRP SEND requests of step 1. NOTE 3: The test case calling this procedure may switch the role of SS-UE1 and SS-UE2 clients. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 334 A.4.4.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCData Client) or SS-UE2 (MCData Client). A.4.5 E2E MCData Call Release A.4.5.1 Initial conditions As specified in the test case which calls the procedure. A.4.5.2 Definition of system information messages N/A. A.4.5.3 Procedure Table A.4.5.3-1: E2E MCData Call Release St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCData Server (IUT) correctly perform procedure 'MCX E2E call release' as described in Table A.2.19.3-1 to release the call? - - - P 2 The SS-UE1 (MCData Client) closes the MSRP TCP connection. (Note 1) - - - - 3 Check: Does the MCData Server (IUT) wait for the SS- UE1 (MCData Client) to close the MSRP TCP connection? - - - P - EXCEPTION: Steps 4a1 - 4b2 describe behaviour that depends on the endpoint role the SS-UE2 (MCData client) has chosen at call establishment. (Note 2) - - - - 4a1 IF the SS-UE2 (MCData Client) is the active endpoint THEN - - - - 4a2 Check: Does the MCData Server (IUT) wait for the SS- UE2 (MCData Client) to close the MSRP TCP connection? - - - P 4b1 ELSE the MCData Server closes the MSRP TCP connection. - - - - 4b2 Check: Does the MCDATA Server (IUT) close the MSRP TCP connection? - - - P NOTE 1: The MCData Originating Participating Server chooses the role of the passive endpoint during call establishment (Table A.4.3.3-1). NOTE 2: The endpoint role is negotiated in the SDP signalling at call establishment (Table A.4.3.3-1). A.4.5.4 Specific message contents All message contents are as specified in, ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 335 • Subclauses referring to messages from UE relate to either SS-UE1 (MCData Client) or SS-UE2 (MCData Client). Table A.4.5.4-1: SIP BYE from the SS-UE1 (Step 1, Table A.4.5.3-1; 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 Information Element Value/remark Comment Reference Condition Reason IETF RFC 3326 [14] reason-value "SIP" protocol-cause "cause="200"" reason-text "text="transmission succeeded"" Table A.4.5.4-2: SIP BYE from the MCPTT Server (Step 1, Table A.4.5.3-1; 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 Information Element Value/remark Comment Reference Condition Reason IETF RFC 3326 [14] reason-value "SIP" protocol-cause "cause="200"" reason-text "text="transmission succeeded"" A.4.6 E2E MCData Call Establishment using pre-established session A.4.6.1 Initial conditions As specified in the test case which calls the procedure. A.4.6.2 Definition of system information messages N/A. A.4.6.3 Procedure Table A.4.6.3-1: E2E MCData Call Establishment using a pre-established session St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCData Client) sends a SIP REFER message to request the establishment of an MCData call using a pre-established session. --> SIP REFER - - 2 Check: Does the MCData Server (IUT) respond with a SIP 200 (OK) message to SS-UE1 (MCData Client) indicating that the MCData call has been properly requested? <-- SIP 200 (OK) - P 3 Check: Does the MCData Server (IUT) send a SIP re- INVITE requesting the establishment of a call to SS- UE2 (MCData Client)? <-- SIP re-INVITE - P 4 The SS-UE2 (MCData Client) responds a SIP 100 Trying. --> SIP 100 (Trying) - - 5 The SS-UE2 (MCData Client) responds with a SIP 200 (OK). --> SIP 200 (OK) - - 6 Check: Does the MCData server (IUT) send a SIP ACK to acknowledge the session establishment to SS- UE2? <-- SIP ACK - P ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 336 St Procedure Message Sequence TP Verdict U - S Message 7 Check: Does the MCData Server (IUT) send a SIP re- INVITE to SS-UE1, to confirm that the MCData call has been successfully established? <-- SIP re-INVITE - P 8 The SS-UE1 (MCData Client) responds a SIP 100 Trying --> SIP 100 (Trying) - - 9 The SS-UE1 (MCData Client) responds with a SIP 200 (OK) --> SIP 200 (OK) - - 10 Check: Does the MCData Server (IUT) sends a SIP ACK in response to the SIP 200 (OK) message. <-- SIP ACK - P 11 The SS-UE1 (MCData client) connects to the TCP server at the MCData server side to establish an MSRP connection. (Note 1) - - - - 12 The SS-UE1 (MCData client) sends an empty MSRP SEND request to bind the TCP connection to the MSRP session. --> MSRP SEND - - 13 Check: Does the MCData server (IUT) send an MSRP 200 (OK) response? <-- MSRP 200 (OK) - P - EXCEPTION: Steps 14a1 - 14b3 describe behaviour that depends on which role of an endpoint the SS-UE2 (MCData client) has chosen in its SDP answer sent at step 5. - - - - 14a1 IF the SS-UE2 (MCData client) acts as passive endpoint (Note 2) THEN the MCData Server connects to the TCP server at the SS-UE2 side to establish an MSRP connection. Depending on the MCData Server implementation, steps 14a1-14a3 might be performed in parallel to steps 11-13. - - - - 14a2 Check: Does the MCData Server (IUT) send an empty MSRP SEND request to bind the TCP connection to the MSRP session? <-- MSRP SEND - P 14a3 The SS-UE2 (MCData client) sends an MSRP 200 (OK) response. --> MSRP 200 (OK) - - 14b1 ELSE (Note 3) the SS-UE2 (MCData client) connects to the TCP server at the MCData Server side to establish an MSRP connection. - - - - 14b2 The SS-UE2 (MCData client) sends an empty MSRP SEND request to bind the TCP connection to the MSRP session. --> MSRP SEND - - 14b3 Check: Does the MCData server (IUT) send an MSRP 200 (OK) response? <-- MSRP 200 (OK) - P NOTE 1: According to ETSI TS 124 282 [13] (3GPP TS 24.282) clauses 9.2.3.4.2, 9.2.4.4.2 and 10.2.5.4.2 the MCData Server sets the a=setup attribute set to "passive" (see ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-3) The SS-UE's MCData client has the role of the active endpoint NOTE 2: The MCData client indicates to act as passive endpoint by setting the a=setup attribute of the SDP answer at step 4 to "passive" (according to IETF RFC 4145 [15]) NOTE 3: The MCData client indicates to act as active endpoint by setting the a=setup attribute of the SDP answer at step 4 to "active" (according to IETF RFC 4145 [15]) A.4.6.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCData Client) or SS-UE2 (MCData Client). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 337 Table A.4.6.4-1: MSRP SEND (Steps 12 and 14b2, Table A.4.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.12.1.1-1, condition EMPTY_SEND_REQ Table A.4.6.4-2: MSRP SEND (Step 14a2, Table A.4.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.12.1.2-1, condition EMPTY_SEND_REQ A.4.7 E2E MCData Call Release keeping the pre-established session A.4.7.1 Initial conditions As specified in the test case which calls the procedure. A.4.7.2 Definition of system information messages N/A. A.4.7.3 Procedure Table A.4.7.3-1: E2E MCData Call Release keeping the pre-established session St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCData Client) sends a SIP REFER message with method "BYE" to release the MCData session and keep the pre-established session. --> SIP REFER - - 2 Check: Does the MCData Server (IUT) respond with a SIP 200 (OK) message to SS-UE1 (MCData Client)? <-- SIP 200 (OK) - P 3 Check: Does the MCData Server (IUT) send a SIP re- INVITE informing about the call release to SS-UE2 (MCData Client)? <-- SIP re-INVITE - P 4 The SS-UE2 (MCData Client) responds a SIP 100 Trying. --> SIP 100 (Trying) - - 5 The SS-UE2 (MCData Client) responds with a SIP 200 (OK). --> SIP 200 (OK) - - 6 Check: Does the MCData server (IUT) send a SIP ACK to acknowledge the session establishment to SS-UE2? <-- SIP ACK - P 7 Check: Does the MCData Server (IUT) send a SIP re- INVITE to SS-UE1, to confirm that the MCData call has been successfully released? <-- SIP re-INVITE - P 8 The SS-UE1 (MCData Client) responds a SIP 100 Trying --> SIP 100 (Trying) - - 9 The SS-UE1 (MCData Client) responds with a SIP 200 (OK) --> SIP 200 (OK) - - 10 Check: Does the MCData Server (IUT) sends a SIP ACK in response to the SIP 200 (OK) message. <-- SIP ACK - P 11 The SS-UE1 (MCData Client) closes the MSRP TCP connection. (Note 1) - - - - 12 Check: Does the MCData Server (IUT) wait for the SS- UE1 (MCData Client) to close the MSRP TCP connection? - - - P - EXCEPTION: Steps 13a1 - 13b2 describe behaviour that depends on the endpoint role the SS-UE2 (MCData client) has chosen at call establishment. (Note 2) - - - - 13a1 IF the SS-UE2 (MCData Client) is the active endpoint THEN - - - - ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 338 St Procedure Message Sequence TP Verdict U - S Message 13a2 Check: Does the MCData Server (IUT) wait for the SS- UE2 (MCData Client) to close the MSRP TCP connection? - - - P 13b1 ELSE the MCData Server closes the MSRP TCP connection. - - - - 13b2 Check: Does the MCDATA Server (IUT) close the MSRP TCP connection? - - - P NOTE 1: The MCData Originating Participating Server chooses the role of the passive endpoint during call establishment (Table A.4.6.3-1). NOTE 2: The endpoint role is negotiated in the SDP signalling at call establishment (Table A.4.6.3-1). A.4.7.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCData Client) or SS-UE2 (MCData Client). Table A.4.7.4-1: SIP REFER (Step 1, Table A.4.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.12-1 with conditions MCDATA and METHOD-BYE Table A.4.7.4-2: SIP 200 (OK) (Step 2, Table A.4.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 MCDATA and REFER-RSP Table A.4.7.4-3: SIP re-INVITE from the MCData Server (IUT) to SS-UE2 (Step 3, Table A.4.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.5.2-1, condition MCDATA_SDS, re_INVITE Information Element Value/remark Comment Reference Condition Request-Line Request-URI tsc_MCX_SessionID_B session identity of the pre-established session ETSI TS 124 282 [13] (3GPP TS 24.282) clause 9.2.5.4.2.1 Message-body MIME body part not present SDP message MIME body part MCData Info MIME-part-body MCData-Info message as described in Table A.4.7.4-4 Table A.4.7.4-4: MCData-Info (Table A.4.7.4-3) 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 mcdata-info mcdata-Params mcdata-request-uri not present mcdata-calling-user-id not present anyExt mcdata-communication-state "terminate request" ETSI TS 124 282 [13] (3GPP TS 24.282) clause 9.2.5.4.2.2 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 339 Table A.4.7.4-5: SIP re-INVITE from the MCData Server (IUT) to SS-UE1 (Step 7, Table A.4.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3C.13.4-3 Table A.4.7.4-6: SIP 200 (OK) from the SS-UE1 and SS-UE2 (Steps 5 and 9, Table A.4.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3C.13.4-5 A.4.8 FD file upload using HTTP A.4.8.1 Initial conditions As specified in the test case which calls the procedure. A.4.8.2 Definition of system information messages N/A. A.4.8.3 Procedure Table A.4.8.3-1: FD file upload using HTTP St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCData client) sends an HTTP POST request to upload a file to the media storage function? --> HTTP POST - - 2 Check: Does the MCData server (IUT) send an HTTP 201 Created response containing a Location header field with a URL identifying the location of the resource where the file has been stored at the media storage function? <-- HTTP 201 Created - P A.4.8.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to SS-UE1 (MCData Client). A.4.9 FD file download using HTTP A.4.9.1 Initial conditions As specified in the test case which calls the procedure. A.4.9.2 Definition of system information messages N/A. ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 340 A.4.9.3 Procedure Table A.4.9.3-1: FD file download using HTTP St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE2 (MCData client) sends an HTTP GET request to download the file. --> HTTP GET - - 2 Check: Does the MCData server (IUT) send an HTTP 200 OK response containing the requested file? <-- HTTP 200 OK - P A.4.9.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to SS-UE2 (MCData Client). A.4.10 Discovery of the absolute URI of the media storage function A.4.10.1 Initial conditions As specified in the test case which calls the procedure. A.4.10.2 Definition of system information messages N/A. A.4.10.3 Procedure Table A.4.10.3-1: Discovery of the absolute URI of the media storage function St Procedure Message Sequence TP Verdict U - S Message - EXCEPTION: Steps 1a1 - 1b1 describe behaviour that depends on the MCData Server implementation. - - - - 1a1 IF pc_MCData_MSFDiscoverySignalling THEN The SS-UE1 (MCData client) sends a SIP MESSAGE request to discover the absolute URI of the media storage function. --> SIP MESSAGE - - 1a2 Check: Does the MCData server (IUT) send an SIP 200 OK response? <-- SIP 200 (OK) - P 1a3 Check: Does the MCData server (IUT) send a SIP MESSAGE containing the absolute URI of the media storage function in the <mcdata-controller-psi> element of the mcdata-info? <-- SIP MESSAGE - P 1a4 The SS-UE sends SIP 200 OK response. --> SIP 200 (OK) - - 1b1 ELSE the SS-UE determines the value of the absolute URI associated with the media storage function of the MCData content server from the <MCDataContentServerURI> element of the MCData user profile document - - - - ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 341 A.4.10.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to SS-UE1 (MCData Client). All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), clause 5.5 and in the test case calling the procedure, with the following clarifications. Table A.4.10.4-1: SIP MESSAGE from the SS-UE (Step 1a1, Table A.4.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3C.8.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 A.4.10.4-2 Table A.4.10.4-2: MCDATA-Info from the SS-UE (Table A.4.10.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3C.8.4-2 Information Element Value/remark Comment Reference Condition mcdata-info mcdata-Params request-type "msf-disc-req" mcdata-calling-group-id Encrypted <mcdata-calling- group-id> with mcdataURI set to px_MCData_Group_A_ID Encrypted according to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-3A MCD_grp Table A.4.10.4-3: SIP MESSAGE from the MCData Server (IUT) (Step 1a3, Table A.4.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3C.8.4-3 A.4.11 MCData Group Affiliation Status Determination and Subscription A.4.11.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.11.2 Definition of system information messages N/A. A.4.11.3 Procedure Table A.4.11.3-1: MCData Group affiliation status determination and subscription Same procedure as defined in: Table A.2.7.3-1 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 342 A.4.11.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCData Client) or SS-UE2 (MCData Client). Table A.4.11.4-1: SIP SUBSCRIBE (Step 1, Table A.4.11.3-1) Derivation Path: Table A.2.7.4-1, conditions MCDATA and PRESENCE-EVENT Table A.4.11.4-2: SIP NOTIFY (Step 3, Table A.4.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, conditions MCDATA and PRESENCE- EVENT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.4.1 MIME-part-body PIDF as described in Table A.4.11.4-3 Table A.4.11.4-3: PIDF in SIP NOTIFY (Table A.4.11.4-2) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3 (note) NOTE: PIDF document contains tuple with empty <status> element. A.4.12 MCData Group Affiliation Status Change A.4.12.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.12.2 Definition of system information messages N/A. A.4.12.3 Procedure Table A.4.12.3-1: MCData Group Affiliation Status Change Same procedure as defined in Table A.2.12.3-1 A.4.12.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCData Client) or SS-UE2 (MCData Client). ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 343 Table A.4.12.4-1: SIP PUBLISH (Step 1, Table A.4.12.3-1) Derivation Path: Table A.2.12.4-1, condition MCDATA Table A.4.12.4-2: PIDF in SIP PUBLISH (Table A.4.12.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.1-3, condition AFFILIATION Table A.4.12.4-3: SIP 200 (OK) (Step 2, Table A.4.12.3-1) Derivation Path: Table A.2.12.4-5 Information Element Value/remark Comment Reference Condition Expires IETF RFC 3261 [21] IETF RFC 3903 [16] value same value as in the request or lower Table A.4.12.4-4: SIP NOTIFY (Step 3, Table A.4.12.3-1) Derivation Path: Table A.2.12.4-6, condition MCDATA Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.4.1 MIME-part-body PIDF as described in Table A.4.12.4-5 Table A.4.12.4-5: PIDF in SIP NOTIFY (Table A.4.12.4-4) 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" expires Current time plus the value set in the Expires header of the SIP PUBLISH response. ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.3.5 ..p-id same value as received in the SIP PUBLISH message. Table A.4.12.4-6: SIP NOTIFY (Step 5, Table A.4.12.3-1) Derivation Path: Table A.2.12.4-6, condition MCDATA Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.4.1 MIME-part-body PIDF as described in Table A.4.12.4-7 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 344 Table A.4.12.4-7: PIDF in SIP NOTIFY (Table A.4.12.4-5) 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" expires Current time plus the value set in the Expires header of the SIP PUBLISH response. ETSI TS 124 282 [13] (3GPP TS 24.282) clause 8.3.3.5 ..p-id same value as received in the SIP PUBLISH message. A.4.13 MCData Functional Alias Status Determination and Subscription A.4.13.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.13.2 Definition of system information messages N/A. A.4.13.3 Procedure Table A.4.13.3-1: MCData Functional Alias Status Determination and Subscription Same procedure as defined in Table A.2.7.3-1 A.4.13.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCData Client) or SS-UE2 (MCData Client). Table A.4.13.4-1: SIP SUBSCRIBE (Step 1, Table A.4.13.3-1) Derivation Path: Table A.2.7.4-1, condition MCDATA Information Element Value/remark Comment Reference Condition Message-body MIME body part MCData Info ETSI TS 124 282 [13] (3GPP TS 24.282) clause 22.2.1.3 MIME-part-body MCData-Info as described in Table A.2.7.4-2 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 345 Table A.4.13.4-2: MCData-Info in SIP SUBSCRIBE (Table A.4.13.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 request-type functional-alias-status- determination ETSI TS 124 282 [13] (3GPP TS 24.282) clause 22.2.1.3 Table A.4.13.4-3: SIP NOTIFY (Step 3, Table A.4.13.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1 with conditions MCDATA and PRESENCE-EVENT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 282 [13] (3GPP TS 24.282) clause 22.3.1 MIME-part-body PIDF as described in Table A.4.13.4-4 Table A.4.13.4-4: PIDF in SIP NOTIFY (Table A.4.13.4-2) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3 (note) NOTE: PIDF document contains tuple with empty <status> element A.4.14 MCData Functional Alias Status Change A.4.14.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.14.2 Definition of system information messages N/A. A.4.14.3 Procedure Table A.4.14.3-1: MCData Functional Alias Status Change Same procedure as defined in Table A.2.12.3-1 A.4.14.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), 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 (MCData Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCData Client) or SS-UE2 (MCData Client). Table A.4.14.4-1: SIP PUBLISH (Step 1, Table A.4.14.3-1) Derivation Path: Table A.2.12.4-1, condition MCDATA ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 346 Table A.4.14.4-2: PIDF in SIP PUBLISH (Table A.4.14.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.1-3, condition FUNCTIONAL_ALIAS_STATUS_CHANGE Table A.4.14.4-3: SIP 200 (OK) (Step 2, Table A.4.14.3-1) Derivation Path: Table A.2.12.4-5 Information Element Value/remark Comment Reference Condition Expires IETF RFC 3261 [21] IETF RFC 3903 [16] value same value as in the request or lower Table A.4.14.4-4: SIP NOTIFY (Step 3, Table A.4.14.3-1) Derivation Path: Table A.2.12.4-6, condition MCDATA Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 282 [13] (3GPP TS 24.282) clause 22.3.1 MIME-part-body PIDF as described in Table A.4.14.4-5 Table A.4.14.4-5: PIDF in SIP NOTIFY (Table A.4.14.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, 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 282 [13] (3GPP TS 24.282) clause 22.2.2.3.5 Table A.4.14.4-6: SIP NOTIFY (Step 5, Table A.4.14.3-1) Derivation Path: Table A.2.12.4-6, condition MCDATA Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 282 [13] (3GPP TS 24.282) clause 22.3.1 MIME-part-body PIDF as described in Table A.4.14.4-7 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 347 Table A.4.14.4-7: PIDF in SIP NOTIFY (Table A.4.14.4-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-3, 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 282 [13] (3GPP TS 24.282) clause 22.2.2.3.5 ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 348 Annex B (informative): Bibliography • 3GPP TS 33.179: "Security of Mission Critical Push To Talk (MCPTT) over LTE". • 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.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". • 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2". • 3GPP TS 24.109: "Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details". • 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 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging". • IETF RFC 3515: "The Session Initiation Protocol (SIP) Refer Method". • IETF RFC 3830: "MIKEY: Multimedia Internet KEYing". • 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 3856: "A Presence Event Package for the Session Initiation Protocol (SIP)". • IETF RFC 4354: "A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service". • IETF RFC 4488: "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription". • IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)". • IETF RFC 4826: "Extensible Markup Language (XML) Formats for Representing Resource Lists". • IETF RFC 4976: "Relay Extensions for the Message Sessions Relay Protocol (MSRP)". • 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 6135: "An Alternative Connection Model for the Message Session Relay Protocol (MSRP)". • IETF RFC 6509: "MIKEY-SAKKE: Sakai-Kasahara Key Encryption in Multimedia Internet KEYing (MIKEY)". • IETF RFC 6714: "Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)". • IETF RFC 6749: "The OAuth 2.0 Authorization Framework". • IETF RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage". • W3C.REC-html401-19991224: "HTML 4.01 Specification". • OMA-TS-XDM_Core-V2_1-20120403-A: "XML Document Management (XDM) Specification". ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 349 • OMA-TS-XDM_Group-V1_1_1: "Group XDM Specification". • OpenID Connect 1.0: "OpenID Connect Core 1.0 incorporating errata set 2". ETSI ETSI TS 104 149-1 V1.1.1 (2026-02) 350 History Version Date Status V1.1.1 February 2026 Publication |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 1 Scope | The present document assesses the importance of low frequency bands in wireless backhaul networks collecting information on current use by Fixed Services of the bands lower than 10 GHz, expected use on medium term and reporting technical considerations on why bands below 10 GHz are necessary to deploy long haul links, supported by link planning examples and bands performances comparison in different areas. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 2 References | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 2.1 Normative references | Normative references are not applicable in the present document. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 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 White Paper No. 25 (February 2018): "Microwave and Millimetre-wave for 5G Transport". [i.2] Recommendation ITU-R P.530-17: "Propagation data and prediction methods required for the design of terrestrial line-of-sight systems". [i.3] Recommendation ITU-R F.746-11: "Radio-frequency arrangements for fixed service systems". [i.4] ETSI GR mWT 012 (V1.1.1): "5G Wireless Backhaul/X-Haul". [i.5] Radio Regulation, Edition of 2024: Articles (Vol.1) and WRC-23 Final Acts (Vol.3). [i.6] ETSI White Paper No. 58 (July 2023): "Worldwide Analysis and proposals to promote and facilitate the wireless transport networks as the key enabler for fat mobile backhaul network modernization". [i.7] GSMA Wireless Backhaul Evolution-Delivering next-generation connectivity (2021). [i.8] ECC Report 173: "Fixed Service in Europe Current use and future trends post 2022". [i.9] ECC Report 365: "Fixed Links in CEPT; Technical characteristics and statistical review". [i.10] Recommendation ITU-R P.530-19: "Propagation data and prediction methods required for the design of terrestrial line-of-sight systems". [i.11] Recommendation ITU-R P.837-8: "Characteristics of precipitation for propagation". [i.12] Recommendation ITU-R PN.837-1: "Characteristics of precipitation for propagation". ETSI ETSI TR 104 142 V1.1.1 (2026-02) 9 |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 3 Definition of terms, symbols and abbreviations | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 3.1 Terms | For the purposes of the present document, the following terms apply: access link: last mile connection to site (fixed or mobile) dense urban: location in highly populated areas (malls, business districts, city centres) very close to fibre PoP: distances less than 1 km and very high capacity, up to 50 Gbps NOTE: Usually, one single hop is enough to connect the base station to fibre PoP. feeder link: connection aggregating traffic from more than one site long haul: long distance multichannel connections in frequency bands ≤ 13 GHz. NOTE: Long haul systems are typically designed for easily deliver multichannel (N ≥ 8), BCA, space diversity combiner, narrow band filters and could be either all indoor mount or split mount. n+0: multi-channel link configuration where n channels in one or more than one band are transmitted together NOTE: In Ethernet era, the channels are aggregated together at Layer-1 level to increase the capacity of the link; this type of configuration is generally addressed also as Band and Carrier Aggregation. rural: locations like small communities or scarcely populated areas generally far from fibre PoP: distances higher than 10 km and capacity up to 5 Gbps short haul: split mount systems delivering connectivity in all bands NOTE: Typical configurations are up to 4 + 0 according to the network layer they are used. Short haul radio in bands ≤ 13 GHz can be used for delivering long haul connections in configuration simpler than long haul systems. sub-urban: location in less populated areas (like suburbs or small cities) with distances in the range of 5 km to 10 km to fibre PoP and delivering capacity up to 10 Gbps NOTE: Usually one/two hops are enough to connect the base station to fibre PoP. trunk / trunking: general terminology including both Long Haul and Short haul radio in multi-channel configuration delivering feeder long distance multichannel connections in frequency bands ≤ 13 GHz NOTE: Capacity may vary according to type of service backhauled and number of mobile sites aggregated reaching 10 Gbps to 15 Gbps. urban: location in populated areas close to fibre PoP: distances less than 5 km and relatively high capacity up to 20 Gbps NOTE: Usually, one single hop is enough to connect the base station to fibre PoP. 6 GHz: 5 925 MHz to 7 110 MHz L6 GHz: Lower 6 GHz: 5 925 MHz to 6 425 MHz U6 GHz: Upper 6 GHz: 6 425 MHz to 7 110 MHz 7 GHz: 7,11 GHz to 7,9 GHz L7 GHz: Lower 7 GHz: 7,125 GHz to 7,425 GHz U7 GHz: Upper 7 GHz: 7,425 GHz to 7,725 GHz 8 GHz: 7,725 GHz to 8,5 GHz L8 GHz: Lower 8 GHz: 7,725 GHz to 8,8275 GHz ETSI ETSI TR 104 142 V1.1.1 (2026-02) 10 U8 GHz: Upper 8 GHz: 8,275 GHz to 8,5 GHz |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: p0 Multipath occurrence factor R0.01 Rainfall intensity exceeded for 0,01 % of an average year (mm/h) dN1 Point refractivity gradient in the lowest 65 m of the atmosphere not exceeded for 1 % of an average year sa Area terrain roughness as defined in Recommendation ITU-R P.530-17 [i.2] |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 4G 4th Generation Mobile Networks 5G 5th Generation Mobile Networks AI Action Item APAC Asia-Pacific APT Asia-Pacific Telecommunity ASMG Arab Spectrum Management Group ATU African Telecommunications Union BCA Band and Carrier Aggregation CCDP Co-Channel Dual Polarization CDF Cumulative Distribution Function CEPT European Conference of Postal and Telecommunications Administrations CIS Commonwealth of Independent States CITEL Inter-American Telecommunications Commission CS Channel Spacing ECC Electronic Communications Commitee FCC Federal Communication Commission FDD Frequency Division Duplex FS Fixed Services FSS Fixed Satellite Services IMT International Mobile Telecommunications ISP Internet Service Providers KPI Key Performance Indicator LATAM Latin America LTE Long Term Evolution MBH Mobile Backhaul MEA Middle East and Africa MIMO Multiple Input Multiple Output mmW millimeter Wave MNO Mobile Network Operator MW Microwave NAM North America OLO Other Local Operators PoP Point of Presence PtP Point-to-Point QAM Quadrature Amplitude Modulation RCC Regional Commonwealth in the field of Communications RLAN Radio Local Area Networks SD Space Diversity WISP Wireless Internet Service Providers WRC-19 World Radiocommunication Conference (WRC) 2019 WRC-23 World Radiocommunication Conference (WRC) 2023 WRC-27 World Radiocommunication Conference (WRC) 2027 WRC-31 World Radiocommunication Conference (WRC) 2031 XPIC Cross Polar Interference Canceller ETSI ETSI TR 104 142 V1.1.1 (2026-02) 11 |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 4 Spectrum Considerations | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 4.1 Available Microwave Spectrum | Frequency bands used in modern Wireless Backhaul Networks range from 4 GHz to 86 GHz and studies for going beyond 90 GHz are in an advanced stage with prototypes showcased in W-Band (92 GHz to 114,25 GHz) and D-Band (130 GHz to 174,8 GHz). Figure 3: Microwave Spectrum Frequency band choice takes into account different aspects as the required capacity, link distance and required KPI: • Frequency bands up to 13 GHz allow to cope medium-long distances but the limited spectrum availability limits the capacity per channel and typically Bands and Carrier Aggregation is required to scale up the throughput. • Frequency bands from 15 GHz to 42 GHz achieve shorter distances but thanks to higher spectrum amount wider channels are feasible allowing to deliver high throughput with simpler systems. • E-Band (71 GHz to 76 GHz and 81 GHz to 86 GHz) is suitable for short ultra-high capacity links Microwave radio systems work in Frequency Division Duplex (FDD) scheme: Recommendation ITU-R F.746 (1st edition 1991) (Recommendation ITU-R F.746-11 [i.3]) defines radio patterns general rules for minimizing the carrier-to-interference and allowing the deployment of single carrier system (one go channel + one return channel) or multi-carrier system (n go channels + n return channels). Figure 4: FDD channel arrangement The net band available for wireless backhaul typically considers only the number of channels available per band and actual backhaul capacity of a FDD microwave link is calculated on one single channel (see note), being the transmission symmetrical. NOTE: Air Capacity is calculated according to the Nyquist Law: Air Capacity Where: BW = Channel Bandwidth [MHz] N log X are the bits per symbol of Xth modulation level ETSI ETSI TR 104 142 V1.1.1 (2026-02) 12 α = Nyquist Filter Roll-Off Channel allocation on link basis or per block to different users (e.g. MNO, Utilities, Government, Army, WISP and OLO) and limitations on frequency channel reuse to avoid interferences, prevent to use the entire amount of available channels and therefore the available backhaul capacity per link. Moreover, the available spectrum greatly varies from country to country in term of bands open to commercial use and channel bandwidth allowed. Table 1 updates the one reported in ETSI GR mWT 012 [i.4] and gives an overview of the wireless backhaul spectrum providing information on: • the total available bandwidth and the maximum channel size as per ITU-R Recommendations; • the typical area of deployment in single-carrier and band and carrier aggregation arrangements; • which bands are candidate for access technologies, focusing on bands below 10 GHz. Table 1: Spectrum Availability Candidate/Allocated Access Bands Frequency Band Total BW Max Channel Size Areas of Deployment (Typical) Single Carrier BCA RLAN L6 GHz 533,7 MHz 59,3 MHz Rural Long Haul/Trunking IMT WRC-23 (see note 1) U6 GHz 640 MHz 80 MHz Rural Long Haul/Trunking IMT WRC-27 (candidate within AI 1.7) L7 GHz 238 MHz 56 MHz Rural Long Haul/Trunking U7 GHz 224 MHz 56 MHz Rural Long Haul/Trunking L8 GHz 533,7 MHz 59,3 MHz Rural Long Haul/Trunking U8 GHz 168 MHz 28 MHz Rural Long Haul/Trunking IMT WRC-23 (see note 2) 10 GHz 664 MHz 28 MHz Rural Long Haul/Trunking 11 GHz 960 MHz 80 MHz Rural Long Haul/Trunking 13 GHz 448 MHz 56 MHz Rural Long Haul/Trunking IMT WRC-27 (candidate within AI 1.7) 15 GHz 336 MHz 112 MHz Sub-Urban/ Semi-Rural/Rural 18 GHz 1 870 MHz 220 MHz Sub-Urban Semi-Rural/Rural 23 GHz 1 008 MHz 224 MHz Urban/Sub-Urban Semi-Rural/Rural IMT WRC-19 (see note 3) 26 GHz 1 736 MHz 112 MHz Urban Mobile (Selected Countries (see note 4)) 28 GHz 1 750 MHz 224 MHz Urban Sub-Urban/Rural 32 GHz 1 484 MHz 224 MHz Urban Sub-Urban/Rural IMT WRC-19 (see note 5) 38 GHz 2 240 MHz 224 MHz Urban 42 GHz 3 GHz 224 MHz Urban FSS WRC-27 AI 1.10 E-Band 10 GHz nx250 MHz Dense Urban / Urban Sub-Urban IMT (WRC-31 candidate AI (see note 6)) W-Band 12 GHz nx250 MHz Dense Urban / Urban Sub-Urban D-Band 32 GHz nx250 MHz Dense Urban / Urban NOTE 1: Radio Regulation [i.5]: • IMT identification according to WRC-23 footnotes RR 5.457E (Region 1), 5.457D (Cambodia, Lao P.D.R., Maldives), 5.457F (Brazil and Mexico). • Resolution 220 (WRC-23) applies. NOTE 2: IMT identification in 10 GHz to 10,5 GHz in some Region 2 countries according to WRC-23 footnotes RR 5.480A [i.5]. NOTE 3: Radio Regulation [i.5]: • Global IMT identification for 24,25 GHz to 27,5 GHz according to RR footnote 5.532AB. Resolution 242 (WRC-19) applies. NOTE 4: No regional harmonization, some initiatives at national level. NOTE 5: Radio Regulation [i.5]: • Global IMT identification for 37 GHz to 43,5 GHz (or portions thereof) according to RR footnote 5.550B. • Resolution 243 (WRC-19) applies. NOTE 6: WRC-31 preliminary AI 2.6 [i.5]. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 13 |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 4.2 Spectrum Requirements | In past years, evolution of MW application from medium-long distance infrastructure network to Wireless Backhaul of thousands mobile sites and wider fibre availability, shifted major requirements from low bands to high bands: higher spectrum amount allows to serve multiple sites minimizing the interferences and achieve wide channels for delivering high throughput (ETSI White Paper No. 25 [i.1]). Figure 5: Microwave Spectrum Capacity vs. Coverage Nevertheless, 5G coverage extension from urban to rural areas and national plans for extending broadband services to white areas are increasing wireless backhaul capacity demand over medium-long distances. Moreover, not only in developing countries the fibre availability is still scarce or even negligible outside the big cities, but also in developed countries there could be areas not yet reached or not easy reachable by fiber that require high capacity on medium/long BCA microwave links. Finally, vertical players, like power utilities or broadcasters, and small operators and WISP/ISP rely on microwave radios for building their infrastructure network. Access site distance to the closest fiber PoP greatly varies across different networks. Mobile Backhaul capacity required according to different deployment scenario are summarized in Table 2 (ETSI GR mWT 012 [i.4]). ETSI ETSI TR 104 142 V1.1.1 (2026-02) 14 Table 2: Backhaul/X-Haul Capacity Requirements Area Type Sites Configurations Cell Type Tail Link Capacity Requirements Access (Pre-)Aggregation Capacity Requirements 5G "Early Stage" 5G "Mature Stage" Dense Urban ('DU') • 5G 100 MHz 16L MIMO ~4 GHz • 5G ≤ 800 MHz 4L MIMO ~30 GHz • Small-cell < 5 Gbps Mix of 5 Gbps to 10 Gbps & ≥ 10 Gbps sites - (single-hop) Urban ('U') • LTE 50 - 100 MHz • 5G 100 MHz 16L MIMO ~4 GHz • 5G ≤ 800 MHz 4L MIMO ~30 GHz • Macro- cell Sub- Urban ('SU') • LTE 50-100 MHz • 5G 100 MHz 8L MIMO ~4 GHz • Macro- cell < 3 Gbps < 5 Gbps < 10 Gbps (2nd hop 'U') Semi- Rural ('SR') Rural ('R') • LTE 50-100 MHz • 5G 50 MHz 4L MIMO ~2 GHz • 5G 20 MHz 4L MIMO ~700 MHz • Macro- cell < 2 Gbps < 3 Gbps < 5 Gbps (2nd hop 'SU') < 10 Gbps (3rd hop 'U') Even though advanced coding modulation schemes allow to reach 16k levels and cross Polar Interference Cancellation (XPIC) technique doubles the spectral efficiency per channels, the capacity delivered by microwave links ranges from 250 Mbps per channel up to 1 Gbps per channel (x2 using XPIC) on traditional bands forcing to bundle more channels or bands in multicarrier systems for delivering ultra-Gbps capacity. Figure 6: 4G and 5G requirements vs Spectrum bands and channel size The availability of enough spectrum resources is necessary to enable wireless backhaul and wide channels allow to deliver the capacity required for fulfilling broadband targets set by government to enable the digital transformation (ETSI White Paper No. 58 [i.6]). |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5 Spectrum Segmentation in Wireless Backhaul | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.1 Wireless Backhaul Trends | The study in on evolution of wireless backhaul published by ABI Research for GSMA in 2021 [i.7] touched multiple aspects, from technology innovation to spectrum availability, allocation and pricing, including capacity analysis and link forecasts. According to this study there will be 17,2 million backhaul links to collect traffic from Macro and Small Cells by 2027 (see note): 66 % (9,6 million) will be backhauled by Fixed Services, 42 % by fibre and only 2 % by satellite, confirming that microwave will be a key asset for transport networks of MNOs (Figure 7). ETSI ETSI TR 104 142 V1.1.1 (2026-02) 15 Figure 7: Macro and Small Cell Backhaul Links Technology Segmentation (2027) NOTE: Research takes into account operators and regulators feedbacks in 40 countries involving and insights of backhaul vendors. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.2 Low Bands Application Scenarios | Frequency band segmentation is related to region/country specific reasons related to applications and propagation conditions: • Long haul high capacity backbone. Countries lacking nationwide fibre infrastructure rely on MW technology deploying multichannel links to carry 5-10 Gbps. These links are in the uppermost layer of aggregation network and are designed with very high availability over medium long distances. • Remote area connections. This type of application could be either a feeder link or a last mile link to connect sites to the first fibre PoP: typical locations include but are not limited to islands, remote rural community, mountain sites. High availability and medium long distances require multichannel configurations on feeder links, while access sites direct connection may have antenna diameter limitations on the tail site. • Remote areas disaster recovery/fibre backup. infrastructure networks rely on MW links to guarantee connectivity continuity especially in mountain areas and islands. Figure 8: Low Bands application scenarios |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3 Bands below 10 GHz Statistics | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3.1 Worldwide wireless backhaul statistics | Starting from ABI Research for GSMA study [i.7] snapshot of technologies used for mobile backhaul in 2021, it is possible to extrapolate traditional band segmentation: out of 5,1 million links installed in 2021, about 2 million are deployed in low bands (< 13 GHz) representing more than 30 % of the overall installed MW links and 40 % of traditional bands links (Figure 9). ETSI ETSI TR 104 142 V1.1.1 (2026-02) 16 Figure 9: Frequency Band segmentation in 2021 |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3.2 CEPT Countries - ECC Report 173 and ECC Report 365 | CEPT has analysed Fixed Service use and trends several times since 1997 asking Administrations to answer to questionnaires: ECC Report 3 was issued in 1997 and revised in 2001, ECC Report 173 was issued in 2012 and revised in 2018 and 2022. Latest ECC Report 173 [i.8] collected the feedbacks of 26 administrations: deployment statistics includes all responding administrations feedbacks, while trends have been evaluated considering only those administrations that answered also to 2018 revision. Responding countries in 2022 and 2018 have been reported in Annex A. About 690 000 FS active links have been declared in traditional bands (1 GHz to 42 GHz), out of which about 66 000 are in bands below 10 GHz: frequency bands statistics are reported in Figure 10. Figure 10: PtP links 1 GHz to 42 GHz frequency bands distribution Responding administrations will continue using bands below 10 GHz for reaching sites on islands, rural areas and location not yet reached by fibre and in many countries is even expected an increase in 6 GHz and 7 GHz with consequent increase of congestion in such bands. ECC Report 365 [i.9] is a statistical review of fixed services characteristics: it collects the feedbacks of 14 administrations and provides an update on links per frequency band. Figure 11 reports the statistics of countries with more than 1 000 links in bands below 10 GHz. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 17 Figure 11: 1 GHz to 42 GHz frequency bands distribution |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3.3 Real Networks - Tier 1 Operators | Bands segmentation of links deployed by Tier-1 Operators with affiliates across Europe and MEA countries is reported in Figure 12. About 3 600 links are deployed in Europe and more than 11 000 in MEA leading to two considerations: 1) In Europe, where fibre has a deeper penetration, links in bands below 10 GHz are deployed to connect remote locations such as islands and mountains where fibre is either not yet available or it is too difficult to lay. 2) In MEA links in these bands are key part of the operators' infrastructure network for building nationwide long haul backbones. Figure 12: Bands below 10 GHz deployment segmentation - Tier 1 Operators Configurations vary from 2+0/4+0 for access links to 8+0/10+0 for feeder links and backbones, with capacities requested up to 10 Gbps. Low bands are used for delivering high availability, since these links are deployed in the highest hierarchy of the access network and on backbones, aggregating the traffic of 10 to 20 sites and, due to narrow channels available in these bands, BCA is required for delivering the requested capacity. The capacity is expected to increase to meet mobile traffic growth, therefore configurations will bundle more and more channels and eventually different bands. Bands usage re-shuffle is expected due to L6 GHz and U6 GHz allocation to RLAN and IMT. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3.4 USA statistics | Basic licenses attributes of MW point-to-point link installed in USA can be retrieved searching FCC Universal Licensing Scheme database. Six bands are included in the analysis: 6 GHz, 11 GHz, 18 GHz, 23 GHz and 38 GHz. U4 GHz, 7 GHz and 8 GHz are not available for fixed service. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 18 More than 360 000 MW links are deployed across USA: high fibre availability in the cities is confirmed by the small deployment in high frequency bands, while the large use of low bands suggests wide deployment to connect rural areas and small/remote communities (Figure 13). Figure 13: USA 6 GHz to 38 GHz Bands Distribution |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.3.5 Vendors statistics | Vendors delivery statistics from 2019 to 2024 have been collected to define the band distribution across different regions: Europe, Commonwealth of Independent States, Asia Pacific, Middle East, Africa, North and Latin America. Country split is reported in Annex B. Notwithstanding country split may not completely overlap across different vendors sales organization, the countries that may belong to two different regions are not many and the statistical error can be considered reasonably low. About 3 million links have been delivered considered period in traditional bands (see note): low bands represent about 20 % of the overall traditional bands confirming their importance in infrastructure networks; out of them 7 GHz and 8 GHz are more than 65 % (Figure 14). NOTE: Link configuration is 1+0 (bidirectional) to better track the spectrum required for implementing N+0 BCA configurations avoiding mutual interference. Figure 14: 2019-2024 deliveries bands segmentation Microwave deployment segmentation confirms the importance of wireless backhaul in regions where fibre is not widely deployed, while the band segmentation reflects the region-specific application (Figure 15). ETSI ETSI TR 104 142 V1.1.1 (2026-02) 19 Figure 15: Traditional bands 2019-2024 deliveries regional segmentation mmWave (V/E-Band) and subTHz (W/D-Band) are not included in the band's segmentations reported in this clause and in clause 5.4 since their applications are mainly in dense urban and urban scenarios in stand-alone configuration and sub-urban scenario in BCA configurations. Traditional bands are widely deployed in regions where fibre is not available even in urban areas, high bands fitting the capacity requirements in the access layer and low bands deployed in the rural areas and for the long haul high capacity backbones. Apart from North America where L6 GHz and U6 GHz are almost the only bands < 10 GHz deployed, in all the other region 7 GHz and 8 GHz are the most deployed ones, with 50 % to 80 % of share (Figure 16). Figure 16: Bands below 10 GHz, 2019-2024 deliveries regional segmentation |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 5.4 Bands < 10 GHz Trends | Focusing on wireless backhaul links forecast reported in ABI Research for GSMA report [i.7], bands up to 13 GHz will represent almost one fourth of the overall installed links (Figure 17), increasing from 2,1 million links (2021) to more than 2,2 million links in 2027 and confirming that medium-long haul applications will not be completely replaced by fibre. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 20 Figure 17: Frequency Band segmentation by 2027 |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6 Planning Considerations and Link Lengths Statistics | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1 Microwave Planning Basic Concepts | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.1 Overview | Prediction methods required for Line-Of-Sight MW link design are described in Recommendation ITU-R P.530-19 [i.10] and takes into account both clear-air and rainfall conditions. Propagation loss includes different contributions: • Attenuation due to atmospheric gases: attenuation due to oxygen and water vapour ais always present and it is included in the total propagation loss for frequencies above 10 GHz. • Diffraction fading due to obstruction or partial obstruction. • Fading due to multipath, beam spreading and scintillation. • Attenuation due to variation of the angle-of arrival/launch. • Attenuation due to precipitation: it depends on rainfall rate; link length and frequency band and it is relevant for frequencies above 10 GHz. • Attenuation due to sand and dust storm. Each contribution depends on the frequency, the path length and the geographic location. Rainfall and multipath are the main phenomena affecting the availability of a MW link: brief descriptions based on Recommendation ITU-R P.530-17 [i.2] are reported in next clauses. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2 Multipath fading | |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2.1 Multipath fading highlights | In case of atmosphere stratification (refractivity gradient varying with altitude), the MW signal may be divided in different rays along the path. These rays arrive on the receiver antenna with different delays due to the length of their paths and are combined together causing attenuation (down-fading) or enhancement (up-fading) in comparison of the signal received in normal propagation conditions. Recommendation ITU-R P.530-17 [i.2] gives formulas to calculate the outage of the link caused by multipath divided in two categories: outage due to non-selective fading and outage due to distortion caused by selective fading. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 21 |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2.2 Outage due to non-selective fading | The graph in Figure 18 shows the relation between the fade depth A (dB) on the X axis and the percentage of time in which this fade depth is exceeded (on the Y axis) according to the values of a parameter named p0. Link will be in outage when the fade depth is bigger or equal to the fade margin of the link. p0 depends on various parameters combined by the Recommendation ITU-R P.530-17 [i.2] formulas: • Geographical: Inclination of the path, flatness of the surfaces, link length. • Frequency band used. • Atmospheric: Refractivity gradient variability in the area. Figure 18: Percentage of time fade depth exceeded in average worst month |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2.3 Outage due to selective fading | Selective fading can cause an in-band distortion that may not be recovered by the system equalizer therefore causing an outage of the link. Calculation of the outage cause by selective fading is based on the p0 parameter and on the signature of the modem that gives the system capability of recovering the distortion. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2.4 Space Diversity improvement | Space diversity is the most used technique to counteract multipath fading, in particular for long haul links. SD is based on the use of two antennas on the receiver side and on the combination/switching of the signal coming from the two antennas to improve the Rx signal quality. Recommendation ITU-R P.530-17 [i.2] defines an SD Improvement Factor based on p0, Frequency band, Spacing between the two receiving antennas, link length. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.2.5 Total outage caused by multipath | Total outage caused by multipath is given by the combination of the contributions of Pns (outage due to non-selective fading) and Ps (outage due to selective fading). ETSI ETSI TR 104 142 V1.1.1 (2026-02) 22 |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.3 Rain attenuation | Recommendation ITU-R P.837-8 [i.11] provides the rainfall statistics required for rain attenuation prediction described in Recommendation ITU-R P.530-17 [i.2]. Notwithstanding ITU-R has updated the rainfall database reported in in past years (latest update in 2017) and common planning tools utilize it as option for predicting outages due to rain, it is common practice to refer to rainfall area and relevant rainfall rate R0.01 (mm/hr) as defined in the earlier versions: Figure 19 and Table 3 report rainfall areas and relevant rain rate as defined in Recommendation ITU-R PN.837-1 [i.12]. For sake of simplicity planning results presented in next clauses consider these rainfall areas. Figure 19: Rain climatic zones Table 3: Rainfall Areas, Rainfall intensity exceeded for 0,01 % of an average year (mm/h) A B C D E F G H J K L M N P Q 0,01 % 8 12 15 19 22 28 30 32 35 42 60 63 95 145 115 Recommendation ITU-R P.530-17 [i.2] defines outage caused by rain using formulas based on the rain rate, link length and frequency band used. |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.1.4 Availability prediction | The total bi-directional outage of the link is usually given by the sum of the outage due to rain plus two times the outage given by multipath fading. The rain outage is considered correlated in two directions (attenuation in the two direction is the same at the same time), but is considered un-correlated for the multipath fading (attenuation is different in the two directions at the same time). Link availability is the percentage of time of the year when the link is not in outage condition. ETSI ETSI TR 104 142 V1.1.1 (2026-02) 23 |
f542fe8f074a9581076fc76f655c34bd | 104 142 | 6.2 Low Bands Performances Comparison |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.