hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E group call establishment, manual commencement' as described in Annex A, Table A.3.2.3-1 to establish a group call with manual commencement mode, and with implicit transmission request but without implicit granted; as described in Option b.ii of note on Table A.3.2.3-1? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Subscription and Notification' as described in Annex A, Table A.2.7.3-1 to subscribe to group dynamic data for group call ongoing information? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Subscription and Notification' as described in Annex A, Table A.2.7.3-1 to de-subscribe to group dynamic data for group call ongoing information? - - 3 P 4 Check: Does the IUT (MCVideo server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1, to release the call? - - 4 P |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 SUBSCRIBE from the SS-UE1 (Step 2, Table 5.6.3.2-1; Step 1, Annex A, Table A.2.7.3-1) Derivation Path: Annex A, Table A.2.7.4-1, condition PRESENCE-EVENT Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-headers MIME-part-body MCVideo-Info as described in Table 5.6.3.3-2 MIME body part SIMPLE-FILTER MIME-part-headers MIME-part-body SIMPLE-FILTER as described in Table 5.6.3.3-3 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 100 Table 5.6.3.3-2: MCVideo-Info in SIP SUBSCRIBE (Table 5.6.3.3-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 <mcvideo- request-uri> with mcvideoURI set to px_MCVideo_Group_A_ID Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2A Table 5.6.3.3-3: SIMPLE-FILTER in SIP SUBSCRIBE (Table 5.6.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.6-1, conditions MCVIDEO and PER-GROUP Table 5.6.3.3-4: SIP NOTIFY from the IUT (MCVideo Server) (Step 2, Table 5.6.3.2-1; Step 3, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, conditions MCVIDEO and PRESENCE- EVENT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.6.3.3-5 Table 5.6.3.3-5: PIDF in SIP NOTIFY (Table 5.6.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2 Information Element Value/remark Comment Reference Condition presence ETSI TS 124 281 [8] (3GPP TS 24.281) clause 8.3.1 entity attribute Encrypted URI (note) with value set to px_MCVideo_Group_A_ID tuple id attribute Encrypted URI (note) with value set to px_MCVideo_ID_User_A status affiliation group not present client Encrypted URI (note) with value set to px_MCVideo_Client_A_ID status not present expires Current time plus one hour tuple id attribute Encrypted URI (note) with value set to px_MCVideo_ID_User_B status affiliation group not present client Encrypted URI (note) with value set to px_MCVideo_Client_B_ID status not present expires Current time plus one hour additionalData groupCallOngoing "true" NOTE: Encrypted attribute as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.13.3-1. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 101 Table 5.6.3.3-6: SIP SUBSCRIBE from the SS-UE1 (Step 3, Table 5.6.3.2-1; Step 1, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.14-1, condition PRESENCE-EVENT, re_SUBSCRIBE Information Element Value/remark Comment Reference Condition Expires value "0" Message-body MIME body part MCVideo-Info MIME-part-headers MIME-part-body MCVideo-Info as described in Table 5.6.3.3-2 MIME body part SIMPLE-FILTER MIME-part-headers MIME-part-body SIMPLE-FILTER as described in Table 5.6.3.3-3 Table 5.6.3.3-7: SIP NOTIFY from the IUT (MCVideo Server) (Step 2, Table 5.6.3.2-1; Step 3, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, conditions MCVIDEO and PRESENCE- EVENT Information Element Value/remark Comment Reference Condition Subscription-State IETF RFC 6665 [14] substate-value "terminated" expires not present Message-body MIME body part PIDF MIME-part-body PIDF as described in Table 5.6.3.3-5 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6 MCVideo Server - MCVideo Client operation | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1 Group call | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1 Pre-arranged Group Calls | 6.1.1.1 MCVideo Server - MCVideo Client / Pre-arranged Group Call / On-demand / Automatic Commencement Mode / Transmission Control / Upgrade to Emergency Group Call / Cancel Emergency State / Upgrade to Imminent Peril Group Call / Cancel Imminent Peril State |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 and having registered the clients} ensure that { when { the SS-UE1 (MCVideo Client) initiates a pre-arranged group call with automatic commencement mode and implicit transmission control } then { IUT (MCVideo Server) accepts the call from the initiator and establishes the call with all affiliated users of the group and sends transmission granted to the SS-UE1 (MCVideo Client) } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 102 (2) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Automatic Commencement Mode } ensure that { when { the SS-UE1 (MCVideo Client) requests the end of transmission control } then { IUT (MCVideo Server) sends transmission idle to the SS-UE1 (MCVideo Client) and sends transmission idle to the SS-UE2 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Automatic Commencement Mode} ensure that { when { the SS-UE1 (MCVideo Client) upgrades the call to emergency group call with implicit transmission control } then { IUT (MCVideo Server) accepts the upgrade from the initiator and updates the call for all affiliated users of the group and sends transmission granted to the SS-UE1 (MCVideo Client) } } (4) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Automatic Commencement Mode } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control} then { IUT (MCVideo Server) sends transmission granted to the SS-UE1 (MCVideo Client) and sends media transmission notification to the SS-UE2 (MCVideo Client) } } (5) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Automatic Commencement Mode } ensure that { when { the SS-UE1 (MCVideo Client) requests downgrade of the call to a normal group call } then { IUT (MCVideo Server) accepts the downgrade from the initiator and updates the call for all affiliated users of the group without implicit transmission request } } (6) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Automatic Commencement Mode} ensure that { when { the SS-UE1 (MCVideo Client) upgrades the call to imminent peril group call with implicit transmission request } then { IUT (MCVideo Server) accepts the upgrade from the initiator and updates the call for all affiliated users of the group and sends transmission granted to the SS-UE1 (MCVideo Client) } } (7) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Automatic Commencement Mode } ensure that { when { the SS-UE1 (MCVideo Client) ends the Pre-arranged group call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the other participants } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 9.2.1.3.1.1, 9.2.1.3.2, 9.2.1.3.3.1, 9.2.1.4.1.1, 9.2.1.4.1.2, 9.2.1.4.2, 9.2.1.4.3, 6.3.2.2.5.2, 6.2.3.1.2, 6.2.3.1.1, 9.2.1.2.1.3, 9.2.1.2.1.4, 9.2.1.2.1.5, 6.4, and ETSI TS 124 581 [9] (3GPP TS 24.581), clauses 6.3.2.2, 6.3.3, 6.4.2, 6.4.3, 6.4.4, 9.2.1. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.1.1] "In the procedures in this clause: 1) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 103 2) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 3) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "prearranged", the participating MCVideo function: … 2) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and shall authorise the calling user; NOTE 2: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 5) shall check if the number of maximum simultaneous MCVideo group calls supported for the MCVideo user as specified in the <MaxSimultaneousCallsN6> element of the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) has been exceeded. If exceeded, the participating MCVideo function shall respond with a SIP 486 (Busy Here) response with the warning text set to "103 maximum simultaneous MCVideo group calls reached" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps; NOTE 3: If the SIP INVITE request contains an emergency indication or an imminent peril indication, the participating MCVideo function can by means beyond the scope of this specification choose to allow for an exception to the limit for the maximum simultaneous MCVideo sessions supported for the MCVideo user. Alternatively, a lower priority session of the MCVideo user could be terminated to allow for the new session. 6) if the user identified by the MCVideo ID is not affiliated to the group identified in the "SIP INVITE request for originating participating MCVideo function" as determined by clause 8.2.2.2.11 and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, shall perform the actions specified in clause 8.2.2.2.12 for implicit affiliation; … 8) shall determine the public service identity of the controlling MCVideo function associated with the group identity in the SIP INVITE request; NOTE 6: The public service identity can identify the controlling MCVideo function in the primary MCVideo system or a partner MCVideo system. NOTE 7: How the participating MCVideo server discovers the public service identity of the controlling MCVideo function associated with the group identity is out of scope of the current release. 9) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3; 10) shall set the Request-URI to the public service identity of the controlling MCVideo function associated with the group identity which was present in the incoming SIP INVITE request; 11) shall not copy the following header fields from the incoming SIP INVITE request to the outgoing SIP INVITE request, if they were present in the incoming SIP INVITE request: a) Answer-Mode header field as specified in IETF RFC 5373 [27]; and b) Priv-Answer-Mode header field as specified in IETF RFC 5373 [27]; 12) shall set the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 104 14) if the received SIP INVITE request contains an application/vnd.3gpp.location-info+xml MIME body and if not already copied, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body received in the SIP INVITE request into an application/vnd.3gpp.location-info+xml MIME body included in the outgoing SIP request; 15) if a Resource-Priority header field was included in the received SIP INVITE request, shall include a Resource- Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCVideo client; and NOTE 8: The participating MCVideo function will leave verification of the Resource-Priority header field to the controlling MCVideo function. 16) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. … Upon receipt of a SIP 2xx response in response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) if the received SIP 2xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC-GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 2) shall generate a SIP 200 (OK) response as in clause 6.3.2.1.5.2; 3) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 4) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 5) 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; 6) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 7) if the procedures of clause 8.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 8.2.2.2.13; 8) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 9) shall interact with Media Plane as specified in 3GPP TS 24.581 [5]; and 10) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [23]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request in step 14) the participating MCVideo function: 1) shall generate a SIP response according to 3GPP TS 24.229 [11]; 2) shall include Warning header field(s) that were received in the incoming SIP response; 3) shall forward the SIP response to the MCVideo client according to 3GPP TS 24.229 [11]; and 4) if the implicit affiliation procedures of clause 8.2.2.2.12 were invoked in this procedure, shall perform the procedures of clause 8.2.2.2.14;..." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.2] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. NOTE 1: This clause covers on-demand session. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 105 Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: … 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; … 6) if the SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC- GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; and 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.3.1] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.1.6." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.1.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.1.4.2 or as the result of receiving a SIP 403 (Forbidden) response as described in this clause. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited.; NOTE 1: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 2: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 3) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the MCVideo ID of the terminating user; and b) the <mcvideo-calling-group-id> element set to the group identity; NOTE 3: The <mcvideo-calling-user-id> is already included in the MIME body as a result of calling clause 6.3.3.1.2 in step 1). 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 106 6) if the in-progress emergency state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.19; b) if the received SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true": i) shall include in the outgoing SIP INVITE request in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; and ii) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcvideo-info+xml MIME body and the application/vnd.3gpp.location- info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false"; and c) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.19; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; and 9) shall send the SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response containing a Require header field with the option tag "100rel" and containing a P-Answer-State header field with the value "Unconfirmed" in response to the SIP INVITE request the controlling MCVideo function: 1) shall send a SIP PRACK request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; 2) shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 9.2.3.4; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 107 3) shall increment the local counter of the number of SIP 200 (OK) responses received from invited members, by 1. NOTE 4: The notifications above could be sent prior to the SIP 200 (OK) response being sent to the inviting MCVideo client. These notifications received by MCVideo clients that are group members do not mean that the group session will be successfully established. NOTE 5: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.1.2] "The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the non-controlling MCVideo function serving the group identity of the MCVideo group owned by the partner MCVideo system; 3) shall set the P-Asserted-Identity to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the group identity of the MCVideo group hosted by the non- controlling MCVideo function in the partner MCVideo system; and b) the <mcvideo-calling-group-id> element set to the group identity of the group served by the controlling MCVideo function; 5) shall include the Recv-Info header field set to g.3gpp.mcvideo-transmission-request; 6) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and 8) shall send the SIP INVITE request towards the partner MCVideo system in accordance with 3GPP TS 24.229 [11]. … Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and NOTE 3: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2. 2) if at least one of the invited MCVideo clients has subscribed to the conference package, shall subscribe to the conference event package in the non-controlling MCVideo function as specified in clause 9.2.3.4.3." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 108 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.2] "In the procedures in this clause: 1) MCVideo ID in an incoming SIP INVITE request refers to the MCVideo ID of the originating user from the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-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 <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 3) MCVideo ID in an outgoing SIP INVITE request refers to the MCVideo ID of the called user in the <mcvideo- request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) indication of required group members in a SIP 183 (Session Progress) response refers to the <required> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to "true" in a SIP 183 (Session Progress) sent by the non-controlling MCVideo function of an MCVideo group; 5) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 6) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for controlling MCVideo function of an MCVideo group", the controlling MCVideo function: … 4) if received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; 5) 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 clause 6.3.5.2; ... 7) shall perform the actions as described in clause 6.3.3.2.2; 8) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero; 9) shall determine if an MCVideo group call for the group identity is already ongoing by determining if an MCVideo session identity has already been allocated for the group call and the MCVideo session is active; … 13) if the MCVideo group call is not ongoing then: … c) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined as determined in step 13) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; d) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; e) shall create a prearranged group session and allocate an MCVideo session identity for the prearranged group call, and shall handle timer TNG3 (group call timer) as specified in clause 6.3.3.5; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 109 f) if the group identity in the "SIP INVITE request for controlling MCVideo function of an MCVideo group" is a TGI: i) shall for each of the constituent MCVideo groups homed on the primary MCVideo system: A) if the controlling MCVideo function does not own the MCVideo group identified by the MCVideo group ID, then generate a SIP INVITE request towards the MCVideo server that owns the MCVideo group identity by following the procedures in clause 9.2.1.4.1.2; and NOTE 2: The MCVideo server that the SIP INVITE request is sent to acts as a non-controlling MCVideo function; B) if the controlling MCVideo function owns the MCVideo group identified by the MCVideo group ID then: I) determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; II) invite each group member determined in step A) above, to the group session, as specified in clause 9.2.1.4.1.1; and III) interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and ii) shall for each of the constituent MCVideo groups homed on the partner MCVideo system generate a SIP INVITE request for the MCVideo group identity homed on the partner MCVideo system as specified in clause 9.2.1.4.1.2; and g) if the group identity in the SIP INVITE request for controlling MCVideo function of an MCVideo group is an MCVideo group ID: i) shall determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; ii) if necessary, shall start timer TNG1 (acknowledged call setup timer) according to the conditions stated in clause 6.3.3.3; iii) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": A) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; and C) if the in-progress emergency state of the group is set to a value of "false": I) shall set the value of the in-progress emergency state of the group to "true"; and II) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; iv) if the in-progress emergency state of the group is set to a value of "false" and if the received SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function shall: A) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and B) if the in-progress imminent peril state of the group is set to a value of "false", shall set the in- progress imminent peril state of the group to a value of "true"; v) shall invite each group member determined in step 13)g)i) above, to the group session, as specified in clause 9.2.1.4.1.1; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 110 vi) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and 14) if the MCVideo group call is ongoing then: … c) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; … e) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined in step 14) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; f) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": i) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; iii) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; and C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.6; iv) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and v) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; g) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function: i) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and ii) if the in-progress imminent peril state of the group is set to a value of "false": A) shall set the in-progress imminent peril state of the group to a value of "true"; B) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.15; and C) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 111 iii) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; h) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.4.2; i) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; j) shall include in the SIP 200 (OK) response with the warning text set to "123 MCVideo session already exists" as specified in clause 4.4; k) if the received SIP re-INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; l) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 4: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. m) shall interact with media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 5: Resulting media plane processing is completed before the next step is performed. n) shall send the SIP 200 (OK) response towards the inviting MCVideo client or inviting non-controlling MCVideo function according to 3GPP TS 24.229 [11]; o) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; NOTE 6: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. p) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]; q) Upon receiving a SIP ACK to the above SIP 200 (OK) response and the SIP 200 (OK) response contained a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall follow the procedures in clause 6.3.3.1.18; and r) shall not continue with the rest of the clause. Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 9.2.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [30], the timer TNG1 (acknowledged call setup timer) is not running, the controlling MCVideo function supports media buffering and the SIP final response is not yet sent to the inviting MCVideo client: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; … 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) shall include a P-Answer-State header field with the value "Unconfirmed"; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 112 5) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 7: Resulting user plane processing is completed before the next step is performed. 8) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; 9) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 8: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 10) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response for a SIP INVITE request as specified in clause 9.2.1.4.1.2 containing an indication of required group members, the timer TNG1 (acknowledged call setup timer) is running and all SIP 200 (OK) responses have been received to all SIP INVITE requests sent to MCVideo clients specified in clause 9.2.1.4.1.1, then the controlling MCVideo function shall wait until the SIP 200 (OK) response has been received to the SIP INVITE request specified in clause 9.2.1.4.1.2 before generating a SIP 200 (OK) response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group". Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1 that was sent to an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24]; and 1) if the MCVideo ID in the SIP 200 (OK) response matches to the MCVideo ID in the corresponding SIP INVITE request; 2) there are no outstanding SIP 200 (OK) responses to SIP INVITE requests which were sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24]; and 3) there is no outstanding SIP 200 (OK) response to a SIP INVITE request sent in clause 9.2.1.4.1.2 where the SIP 183 (Session Progress) response contained an indication of required group members; the controlling MCVideo function: 1) shall stop timer TNG1 (acknowledged call setup timer) as described in clause 6.3.3.3; 2) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; … 4) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 5) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 9: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 7) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 113 NOTE 10: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 8) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon: 1) receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1; 2) the timer TNG1 (acknowledged call setup timer) is not running; 3) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; 4) the controlling MCVideo function supports media buffering; and 5) the SIP final response has not yet been sent to the inviting MCVideo client; the controlling MCVideo function according to local policy: 1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2; … 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 5) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 11: Resulting media plane processing is completed before the next step is performed. 7) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 8) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 12: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 9) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon expiry of timer TNG1 (acknowledged call setup timer), if there are outstanding SIP 200 (OK) responses to SIP INVITE requests sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the procedures specified in clause 6.3.3.3. … Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 114 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.3] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.3.2.2.5.2] "When receiving a "SIP INVITE request for terminating participating MCVideo function" for an on-demand session that requires automatic commencement mode the participating MCVideo function: 1) if: a) the incoming SIP INVITE request contained a Priv-Answer-Mode header field set to the value of "Auto"; b) no Answer-Mode header field or Priv-Answer-Mode header field were received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto- answer"; or c) the incoming SIP INVITE request contained an Answer-Mode header field set to "Auto" and the Answer- Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; then: a) shall generate a SIP 183 (Session Progress) response to the "SIP INVITE request for terminating participating MCVideo function" as specified in clause 6.3.2.2.4.1; and NOTE: The SIP 183 (session Progress) response can be sent reliably or unreliably depending on the content of the received SIP INVITE request. Regardless of if the SIP 183 (Session Progress) response is sent reliably or unreliably, SDP is not included in the SIP 183 (Session Progress) response. b) shall set the P-Answer-State header field to "Unconfirmed" in the SIP 183 (Session Progress) response; 2) shall copy the public user identity contained in the Request-URI of the incoming "SIP INVITE request for terminating participating MCVideo function" to the P-Asserted-Identity header field of the SIP 183 (Session Progress) response; 3) shall generate a SIP INVITE request as specified in clause 6.3.2.2.3; 4) shall set the Request-URI to the public user identity associated to the MCVideo ID of the MCVideo user to be invited; 5) shall perform the procedures specified in clause 6.3.2.2.9 to include any MIME bodies in the received SIP INVITE request, into the outgoing SIP INVITE request; 6) shall copy the contents of the P-Asserted-Identity header field of the incoming "SIP INVITE request for terminating participating MCVideo function" to the P-Asserted-Identity header field of the outgoing SIP INVITE request; 7) if the Priv-Answer-Mode header field is present in the incoming SIP INVITE request with a value of "Auto", shall include a Priv-Answer-Mode header field with the value "Auto" in the outgoing SIP INVITE request. Otherwise, if the Answer-Mode header field is present in the incoming SIP INVITE request, the participating MCVideo function shall include an Answer-Mode header field with the value "Auto" in the outgoing SIP INVITE request; 8) if no Answer-Mode header field or Priv-Answer-Mode header field were received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto-answer", shall set the Answer-Mode header field to "Auto" in the outgoing SIP INVITE request; 9) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for terminating participating MCVideo function" as specified in clause 6.3.2.2.1; 10) if the received SIP INVITE request contains a Resource-Priority header field, shall include a Resource- Priority header field with the contents set as in the received Resource-Priority header field; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 115 11) shall send the SIP INVITE request towards the MCVideo client according to 3GPP TS 24.229 [11]. If the SIP 183 (Session Progress) response was sent reliably, then upon receiving a SIP PRACK request, the participating MCVideo function shall generate a SIP 200 (OK) response to the SIP PRACK request and forward the SIP 200 (OK) response, according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the above SIP INVITE request sent to the MCVideo client, the participating MCVideo function: 1) if the SIP 183 (Session Progress) was sent unreliably, shall send the SIP 200 (OK) response immediately; and 2) if the SIP 183 (Session Progress) was sent reliably and, a) if the SIP PRACK request to the SIP 183 (Session Progress) response has been received by the participating MCVideo function and the SIP 200 (OK) response to the SIP PRACK request has been sent, shall send the SIP 200 (OK) response immediately; b) if the SIP PRACK request to the SIP 183 (Session Progress) response has not yet been received, then upon receipt of the SIP PRACK request, the participating MCVideo function shall generate a SIP 200 (OK) response to the SIP PRACK request and forward the SIP 200 (OK) response, according to 3GPP TS 24.229 [11], before sending the SIP 200 (OK) response to the "SIP INVITE request for terminating participating MCVideo function". When the participating MCVideo function sends the SIP 200 (OK) response to the "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2; 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 clause 6.3.2.2.2.1; 3) shall copy the P-Asserted-Identity header field from the incoming SIP 200 (OK) response to the outgoing SIP 200 (OK) response; 4) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 5) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [11]. The participating MCVideo function shall forward any other SIP response that does not contain SDP along the signalling path to the originating network according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.2.3.1.2] "When performing the automatic commencement mode procedures, the MCVideo client shall follow the procedures in clause 6.2.3.1.1 with the following clarification: - The MCVideo client may include a P-Answer-State header field with the value "Confirmed" as specified in IETF RFC 4964 [30] in the SIP 200 (OK) response." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.2.3.1.1] "When performing the automatic commencement mode procedures, the MCVideo client: 1) shall accept the SIP INVITE request and generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [11]; 2) shall include the option tag "timer" in a Require header field of the SIP 200 (OK) response; 3) shall include the g.3gpp.mcvideo media feature tag in the Contact header field of the SIP 200 (OK) response; 4) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcvideo" in the Contact header field of the SIP 200 (OK) response; 5) shall include the Session-Expires header field in the SIP 200 (OK) response and start the SIP session timer according to IETF RFC 4028 [23]. The "refresher" parameter in the Session-Expires header field shall be set to "uas"; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 116 6) shall, if the incoming SIP INVITE request contains a Replaces header field, include in the SDP answer in the SIP 200 (OK) response to the SDP offer the parameters used for the pre-established session identified by the contents of the Replaces header field; 7) shall, if the incoming SIP INVITE request does not contain a Replaces header field, include an SDP answer in the SIP 200 (OK) response to the SDP offer in the incoming SIP INVITE request according to 3GPP TS 24.229 [11] with the clarifications given in clause 6.2.2; NOTE: In the case of a new emergency call where the terminating client is using a pre-established session, the SIP INVITE request containing a Replaces header is used to replace the pre-established session. 8) shall send the SIP 200 (OK) response towards the MCVideo server according to rules and procedures of 3GPP TS 24.229 [11]; 9) shall, if the incoming SIP INVITE request contains a Replaces header field, release the pre-established session identified by the contents of the Replaces header field; and 10) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. When NAT traversal is supported by the MCVideo client and when the MCVideo client is behind a NAT, generation of SIP responses is done as specified in this clause and as specified in IETF RFC 5626 [35]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.2.1.3] "This clause covers both on-demand session and pre-established sessions. Upon receiving a request from an MCVideo user to upgrade the MCVideo group session to an emergency condition or an imminent peril condition on an MCVideo prearranged group, the MCVideo client shall generate a SIP re-INVITE request as specified in 3GPP TS 24.229 [11], with the clarifications given below. … 3) if the MCVideo user has requested to upgrade the MCVideo group session to an MCVideo emergency call, the MCVideo client: a) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body by following the procedures in clause 6.2.8.1.1; b) if an indication of an MCVideo emergency alert is to be included, shall perform the procedures specified in clause 6.2.9.1 for the MCVideo emergency alert trigger; and c) shall include a Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2. 4) if the MCVideo user has requested to upgrade the MCVideo group session to an MCVideo imminent peril call, the MCVideo client: a) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body by following the procedures in clause 6.2.8.1.9; and b) shall include a Resource-Priority header field and comply with the procedures in clause 6.2.8.1.12; 5) if the SIP re-INVITE request is to be sent within an on-demand session, shall include in the SIP re-INVITE request an SDP offer according to 3GPP TS 24.229 [11] with the clarifications specified in clause 6.2.1; 6) if an implicit transmission request is required, shall indicate this as specified in clause 6.4; and 7) shall send the SIP re-INVITE request according to 3GPP TS 24.229 [11]. On receiving a SIP 2xx response to the SIP re-INVITE request the MCVideo client: 1) shall interact with the user plane as specified in 3GPP TS 24.581 [5]; and 2) shall perform the actions specified in clause 6.2.8.1.4. On receiving a SIP INFO request where the Request-URI contains an MCVideo session ID identifying an ongoing group session, the MCVideo client shall follow the actions specified in clause 6.2.8.1.13. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 117 On receiving a SIP 4xx response, SIP 5xx response or a SIP 6xx response to the SIP re-INVITE request the MCVideo client shall perform the actions specified in clause 6.2.8.1.5." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.2.1.4] "This clause covers both on-demand session and pre-established sessions. Upon receiving a request from an MCVideo user to cancel the in-progress emergency condition on a prearranged MCVideo group, the MCVideo client shall generate a SIP re-INVITE request by following the UE originating session procedures specified in 3GPP TS 24.229 [11], with the clarifications given below. The MCVideo client: … 2) shall, if the MCVideo user is cancelling an in-progress emergency condition and optionally an MCVideo emergency alert originated by the MCVideo user, include an application/vnd.3gpp.mcvideo-info+xml MIME body populated as specified in clause 6.2.8.1.3; 3) shall, if the MCVideo user is cancelling an in-progress emergency condition and an MCVideo emergency alert originated by another MCVideo user, include an application/vnd.3gpp.mcvideo-info+xml MIME body populated as specified in clause 6.2.8.1.14; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with: a) the <session-type> element set to a value of "prearranged"; and b) the <mcvideo-request-uri> element set to the group identity; NOTE 1: The MCVideo ID of the originating MCVideo user is not included in the body, as this will be inserted into the body of the SIP INVITE request that is sent by the originating participating MCVideo function. 5) shall include the g.3gpp.mcvideo media feature tag in the Contact header field of the SIP re-INVITE request according to IETF RFC 3840 [22]; 6) if the SIP re-INVITE request is to be sent within an on-demand session, shall include in the SIP re-INVITE request an SDP offer according to 3GPP TS 24.229 [11] with the clarifications specified in clause 6.2.1; 7) shall include a Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2; and 8) shall send the SIP re-INVITE request according to 3GPP TS 24.229 [11]. On receiving a SIP 2xx response to the SIP re-INVITE request, the MCVideo client: 1) shall interact with the user plane as specified in 3GPP TS 24.581 [5]; 2) shall set the MCVideo emergency group state of the group to "MVEG 1: no-emergency"; 3) shall set the MCVideo emergency group call state of the group to "MVEGC 1: emergency-gc-capable"; and 4) if the MCVideo emergency alert state is set to "MVEA 4: Emergency-alert-cancel-pending", the sent SIP re- INVITE request did not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body and the SIP 2xx response to the SIP request for a priority group call does not contain a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall set the MCVideo emergency alert state to "MVEA 1: no-alert". On receiving a SIP INFO request where the Request-URI contains an MCVideo session ID identifying an ongoing group session, the MCVideo client shall follow the actions specified in clause 6.2.8.1.13. On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the SIP re-INVITE request: 1) shall set the MCVideo emergency group state as "MVEG 2: in-progress"; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 118 2) if the SIP 4xx response, SIP 5xx response or SIP 6xx response contains an application/vnd.3gpp.mcvideo- info+xml MIME body with an <alert-ind> element set to a value of "true" and the sent SIP re-INVITE request did not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, the MCVideo client shall set the MCVideo emergency alert state to "MVEA 3: emergency-alert-initiated"; and 3) if the SIP 4xx response, SIP 5xx response or SIP 6xx response did not contain an application/vnd.3gpp.mcvideo-info+xml MIME body with an <alert-ind> element and did not contain an <originated-by> element, the MCVideo emergency alert (MVEA) state shall revert to its value prior to entering the current procedure. NOTE 3: If the in-progress emergency group state cancel request is rejected, the state of the session does not change, i.e. continues with MCVideo emergency group call level priority." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.2.1.5] "This clause covers on-demand session. Upon receiving a request from an MCVideo user to cancel the in-progress imminent peril condition on a prearranged MCVideo group, the MCVideo client shall generate a SIP re-INVITE request by following the procedures specified in 3GPP TS 24.229 [11], with the clarifications given below. The MCVideo client: … 2) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body populated as specified in clause 6.2.8.1.11; and 3) shall include a Resource-Priority header field and comply with the procedures in clause 6.2.8.1.12; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with: a) the <session-type> element set to a value of "prearranged"; and b) the <mcvideo-request-uri> element set to the group identity; NOTE 1: The MCVideo ID of the originating MCVideo user is not included in the body, as this will be inserted into the body of the SIP re-INVITE request that is sent by the originating participating MCVideo function. 5) shall include the g.3gpp.mcvideo media feature tag in the Contact header field of the SIP re-INVITE request according to IETF RFC 3840 [22]; 6) if the SIP re-INVITE request is to be sent within an on-demand session, shall include in the SIP re-INVITE request an SDP offer according to 3GPP TS 24.229 [11] with the clarifications specified in clause 6.2.1; and 7) shall send the SIP re-INVITE request according to 3GPP TS 24.229 [11]. On receiving a SIP 2xx response to the SIP re-INVITE request, the MCVideo client: 1) shall interact with the user plane as specified in 3GPP TS 24.581 [5]; 2) shall set the MCVideo imminent peril group state of the group to "MVIG 1: no-imminent-peril"; and 3) shall set the MCVideo imminent peril group call state of the group to "MVIGC 1: imminent-peril-gc-capable". On receiving a SIP 4xx, SIP 5xx response or SIP 6xx response to the SIP re-INVITE request: 1) if the SIP 4xx response, SIP 5xx response or SIP 6xx response: a) contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <imminentperil-ind> element set to a value of "true"; or b) does not contain an application/vnd.3gpp.mcvideo-info+xml MIME body with an <imminentperil-ind> element; then the MCVideo client shall set the MCVideo imminent peril group state as "MVIG 2: in-progress". ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 119 NOTE 3: This is the case where the MCVideo client requested the cancellation of the MCVideo imminent peril in- progress state and was rejected." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.4] "An initial SIP INVITE request fulfilling the following criteria shall be regarded by the MCVideo server as an implicit transmit media request by the originating MCVideo client when the MCVideo client: 1) initiates an MCVideo session that is not used for a remotely initiated ambient viewing call; and 2) includes the "mc_implicit_request" 'fmtp' attribute in the associated UDP stream for the transmission control in the SDP offer/answer as specified in 3GPP TS 24.581 [5] clause 12. An initial SIP INVITE request fulfilling the following criteria shall be regarded by the MCVideo server as an implicit request to grant permission to send media to the terminating MCVideo client when the originating MCVideo client: 1) initiates an MCVideo session that is a remotely initiated ambient viewing call; and 2) includes the "mc_implicit_request" 'fmtp' attribute in the associated UDP stream for the transmission control in the SDP offer/answer as specified in 3GPP TS 24.581 [5] clause 12. A SIP re-INVITE request fulfilling the following criteria shall be regarded by the MCVideo server as an implicit transmit media request when the MCVideo client: 1) performs an upgrade of: a) an MCVideo group call to an emergency MCVideo group call; b) an MCVideo group call to an imminent peril MCVideo group call; and 2) includes the "mc_implicit_request" 'fmtp' attribute in the associated UDP stream for the transmission control in the SDP offer/answer as specified in 3GPP TS 24.581 [5] clause 12. In all other cases the SIP (re-)INVITE request shall be regarded as received without an implicit transmit media request." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.3.2.2] "When an MCVideo call is established a new instance of the transmission control server state machine for 'general transmission control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' is added. When an MCVideo call is established a new instance of the transmission control server state machine for 'general reception control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic reception control operation towards the transmission participant' is added. If the optional "mc_queueing" feature is supported and has been negotiated as specified in clause 14, the transmission control server could queue the implicit transmission control request for the media-transmission control entity. The original initial SIP INVITE request or SIP REFER request to establish an MCVideo chat group call or to rejoin an ongoing MCVideo call is not handled as an implicit transmission control request message by the transmission control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request. The permission to send media to the inviting MCVideo client due to implicit transmission control request is applicable to both confirmed indication and unconfirmed indication. When the first unconfirmed indication is received from the invited participating MCVideo function (see 3GPP TS 24.281 [2]) the transmission control server optionally can give an early indication to send RTP media packets, to the inviting MCVideo client. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 120 If an early indication to send RTP media packets is given to the inviting MCVideo client, the transmission participant is granted the permission to send media and the MCVideo server buffers RTP media packets received from the MCVideo client at least until the first invited MCVideo client accepts the invitation or until the RTP media packet buffer exceeds it maximum limit to store RTP media packets. If the MCVideo server does not support or does not allow media buffering then when an early indication to send RTP media packets is not given to the inviting MCVideo client, the transmission participant is granted the permission to send media when the first invited MCVideo client accepts the media. Before the transmission control server sends the first transmission control message in the MCVideo call, the transmission control server has to assign itself a SSRC identifier to be included in media transmission control messages and quality feedback messages if the MCVideo server is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3]. The transmission participant and the transmission control server can negotiate the maximum priority level that the transmission participant is permitted to request. The transmission control server can pre-empt the current sender based on the negotiated maximum priority level that the transmission participant is permitted to request and the priority level included in the Transmission Media Request message. NOTE: The maximum priority level that a transmission participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the controlling MCVideo function from the group management server as described in 3GPP TS 24.481 [12] and service configuration data retrieved by the controlling MCVideo function from the configuration management server as described in 3GPP TS 24.484 [13]. The transmission participant and the transmission control server can negotiate queueing of Transmission requests using the "mc_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the transmission control server queues the transmission control request if a Transmission Media Request message is received when another transmission participant has the transmission and the priority of the current speaker is the same or higher." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 121 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 122 [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 9.2.1] "The transmission control messages are coded as described in clause 9.1.2 where the transmission control message is part of the application-dependent data. For the transmission control protocol the ASCII name string is: MCVx (Mission Critical Video x) with x=0, 1 or 2 as specified in clause 9.1.2. A list of transmission control messages can be found in clause 9.2.2.1. The transmission control specific fields are specified in clause 9.2.3." |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.1.3 Test description | 6.1.1.1.3.1 Pre-test conditions System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) are affiliated to the Prearranged group. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 123 - The IUT (MCVideo Server) is the controlling server of the Prearranged group. 6.1.1.1.3.2 Test procedure sequence Table 6.1.1.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the SS-UE1 (MCVideo Client) request the establishment of a group call to SS-UE2 (MCVideo Client) with automatic commencement mode and implicit transmission request. - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to establish a pre-arranged group call with automatic commencement mode and implicit transmission control request according to option b.ii of note in Annex A, Table A.3.1.3-1? - - 1 P 3 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 2 P 5 Make the SS-UE1 (MCVideo Client) request upgrade of the call to an emergency group call with implicit transmission request. - - - - 6 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.3.1.3-1 to upgrade the call to emergency group call with implicit transmission request according to option b.ii of note in Annex A, Table A.3.1.3-1? - - 3 P 7 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 8 Check: Does the IUT (MCVideo Server) correctly perform procedure ' MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 2 P 9 Make the SS-UE1 (MCVideo Client) request transmission. - - - - 10 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1? - - 4 P 11 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 12 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 2 P 13 Make the SS-UE1 (MCVideo Client) request downgrade of the call to a normal group call. - - - - ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 124 St Procedure Message Sequence TP Verdict U - S Message 14 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.3.1.3-1 to downgrade the call without implicit transmission request, with option a of note on Table A.3.1.3-1? - - 5 P 15 Make the SS-UE1 (MCVideo Client) request transmission. - - - - 16 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1? - - 4 P 17 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 18 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 2 P 19 Make the SS-UE1 (MCVideo Client) request upgrade of the call to an imminent peril group call with implicit transmission request. - - - - 20 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.3.1.3-1 to upgrade the call to imminent peril group call with implicit transmission request according to option b.ii of note in Annex A, Table A.3.1.3-1? - - 6 P 21 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 22 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 2 P 23 Make the SS-UE1 (MCVideo Client) request transmission. - - - - 24 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1? - - 4 P 25 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 26 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 2 P 27 Make the SS-UE1 (MCVideo Client) request downgrade of the call to a normal group call. - - - - 28 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.3.1.3-1 to downgrade the call without implicit transmission request, with option a of note on Table A.3.1.3-1? - - 5 P 29 Make the SS-UE1 (MCVideo Client) release the call. - - - - ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 125 St Procedure Message Sequence TP Verdict U - S Message 30 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 7 P 6.1.1.1.3.3 Specific message contents All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.1.1.1.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.1.1.3.3-2: SIP INVITE from the IUT (MCVideo Server) (Step 2, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.1.1.3.3-3: SIP 200 (OK) from the SS-UE2 (Steps 2, 6, 14, 20 and 28, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.1.1.3.3-4: SIP 200 (OK) from the IUT (MCVideo Server) (Steps 2, 6, 14, 20 and 28, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.1.1.3.3-5: SIP re-INVITE from the SS-UE1 (Step 6, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with conditions GROUP-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 6.1.1.1.3.3-6: SIP re-INVITE from the IUT (MCVideo Server) (Step 6, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition GROUP-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 6.1.1.1.3.3-7: SIP re-INVITE from the SS-UE1 (Steps 14 and 28, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with conditions GROUP-CALL and re_INVITE. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 126 Table 6.1.1.1.3.3-8: SIP re-INVITE from the IUT (MCVideo Server) (Steps 14 and 28, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition GROUP-CALL and re_INVITE. NOTE: Conditions are also applied to all body parts. Table 6.1.1.1.3.3-9: SIP re-INVITE from the SS-UE1 (Step 20, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with conditions GROUP-CALL, re_INVITE and IMMPERIL -CALL. NOTE: Conditions are also applied to all body parts. Table 6.1.1.1.3.3-10: SIP re-INVITE from the IUT (MCVideo Server) (Step 20, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with conditions GROUP-CALL, re_INVITE and IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 6.1.1.1.3.3-11: Transmission Idle from the IUT (MCVideo Server) (Steps 8 and 12, Table 6.1.1.1.3.2-1; Steps 4 and 5, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-6 with condition EMERGENCY-CALL. Table 6.1.1.1.3.3-12: Transmission Request from the SS-UE1 (Step 10, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.7.3-1) Derivation Path: Annex A, Table A.3.7.4-1, with condition EMERGENCY-CALL. Table 6.1.1.1.3.3-13: Transmission Granted from the IUT (MCVideo Server) (Steps 6 and 10, Table 6.1.1.1.3.2-1; Step 3a1 or 3b1, Annex A, Table A.3.7.3-1; Step 2a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.7.4-2 or A.3.7.4-3 (note), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. Table 6.1.1.1.3.3-14: Media Transmission Notification from the IUT (MCVideo Server) (Steps 6 and 10, Table 6.1.1.1.3.2-1; Step 3a3 or 3b2, Annex A, Table A.3.7.3-1; Step 3a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.7.4-4 or A.3.7.4-5 (NOTE 1), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. Table 6.1.1.1.3.3-15: Transmission Idle from the IUT (MCVideo Server) (Steps 22 and 26, Table 6.1.1.1.3.2-1; Steps 4 and 5, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-6 with condition IMMPERIL-CALL. Table 6.1.1.1.3.3-16: Transmission Request from the SS-UE1 (Step 24, Table 6.1.1.1.3.2-1; Step 1, Annex A, Table A.3.7.3-1) Derivation Path: Annex A, Table A.3.7.4-1, with condition IMMPERIL-CALL. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 127 Table 6.1.1.1.3.3-17: Transmission Granted from the IUT (MCVideo Server) (Steps 20 and 24, Table 6.1.1.1.3.2-1; Step 3a1 or 3b1, Annex A, Table A.3.7.3-1; Step 2a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.7.4-2 or A.3.7.4-3 (note), with condition IMMPERIL-CALL. NOTE: Depends on server implementation. Table 6.1.1.1.3.3-18: Media Transmission Notification from the IUT (MCVideo Server) (Steps 20 and 24, Table 6.1.1.1.3.2-1; Step 3a3 or 3b2, Annex A, Table A.3.7.3-1; Step 3a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.7.4-4 or A.3.7.4-5 (note), with condition IMMPERIL-CALL. NOTE: Depends on server implementation. 6.1.1.2 MCVideo Server - MCVideo Client / Pre-arranged Group Call / On-demand / Emergency Group Call |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.2.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 and having registered the clients} ensure that { when { the SS-UE1 (MCVideo Client) initiates an emergency pre-arranged group call with automatic commencement mode and implicit transmission control } then { IUT (MCVideo Server) accepts the call from the initiator and establishes the call with all affiliated users of the group and sends transmission granted to the SS-UE1 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established an emergency MCVideo On-demand Pre-arranged Group Call with Automatic Commencement Mode } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) sends transmission control idle to the SS-UE1 (MCVideo Client) and sends transmission control idle to the SS-UE2 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established an emergency MCVideo On-demand Pre-arranged Group Call with Automatic Commencement Mode } ensure that { when { the SS-UE1 (MCVideo Client) ends the Pre-arranged group call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the other participants } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.2.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 9.2.1.3.1.1, 9.2.1.3.2, 9.2.1.3.3.1, 9.2.1.4.1.1, 9.2.1.4.1.2, 9.2.1.4.2, 9.2.1.4.3, 6.3.2.2.5.2, 6.2.3.1.2, 6.2.3.1.1, and ETSI TS 124 581 [9] (3GPP TS 24.581), clauses 6.3.2.2, 6.3.3, 6.4.2, 6.4.3, 6.4.4, 9.2.1. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.1.1] "In the procedures in this clause: 1) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 128 3) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "prearranged", the participating MCVideo function: … 2) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and shall authorise the calling user; NOTE 2: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 5) shall check if the number of maximum simultaneous MCVideo group calls supported for the MCVideo user as specified in the <MaxSimultaneousCallsN6> element of the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) has been exceeded. If exceeded, the participating MCVideo function shall respond with a SIP 486 (Busy Here) response with the warning text set to "103 maximum simultaneous MCVideo group calls reached" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps; NOTE 3: If the SIP INVITE request contains an emergency indication or an imminent peril indication, the participating MCVideo function can by means beyond the scope of this specification choose to allow for an exception to the limit for the maximum simultaneous MCVideo sessions supported for the MCVideo user. Alternatively, a lower priority session of the MCVideo user could be terminated to allow for the new session. 6) if the user identified by the MCVideo ID is not affiliated to the group identified in the "SIP INVITE request for originating participating MCVideo function" as determined by clause 8.2.2.2.11 and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, shall perform the actions specified in clause 8.2.2.2.12 for implicit affiliation; … 8) shall determine the public service identity of the controlling MCVideo function associated with the group identity in the SIP INVITE request; NOTE 6: The public service identity can identify the controlling MCVideo function in the primary MCVideo system or a partner MCVideo system. NOTE 7: How the participating MCVideo server discovers the public service identity of the controlling MCVideo function associated with the group identity is out of scope of the current release. 9) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3; 10) shall set the Request-URI to the public service identity of the controlling MCVideo function associated with the group identity which was present in the incoming SIP INVITE request; 11) shall not copy the following header fields from the incoming SIP INVITE request to the outgoing SIP INVITE request, if they were present in the incoming SIP INVITE request: a) Answer-Mode header field as specified in IETF RFC 5373 [27]; and b) Priv-Answer-Mode header field as specified in IETF RFC 5373 [27]; 12) shall set the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 129 14) if the received SIP INVITE request contains an application/vnd.3gpp.location-info+xml MIME body and if not already copied, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body received in the SIP INVITE request into an application/vnd.3gpp.location-info+xml MIME body included in the outgoing SIP request; 15) if a Resource-Priority header field was included in the received SIP INVITE request, shall include a Resource- Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCVideo client; and NOTE 8: The participating MCVideo function will leave verification of the Resource-Priority header field to the controlling MCVideo function. 16) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. … Upon receipt of a SIP 2xx response in response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) if the received SIP 2xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC-GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 2) shall generate a SIP 200 (OK) response as in clause 6.3.2.1.5.2; 3) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 4) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 5) 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; 6) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 7) if the procedures of clause 8.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 8.2.2.2.13; 8) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 9) shall interact with Media Plane as specified in 3GPP TS 24.581 [5]; and 10) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [23]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request in step 14) the participating MCVideo function: 1) shall generate a SIP response according to 3GPP TS 24.229 [11]; 2) shall include Warning header field(s) that were received in the incoming SIP response; 3) shall forward the SIP response to the MCVideo client according to 3GPP TS 24.229 [11]; and 4) if the implicit affiliation procedures of clause 8.2.2.2.12 were invoked in this procedure, shall perform the procedures of clause 8.2.2.2.14;..." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.2] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. NOTE 1: This clause covers on-demand session. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 130 Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: … 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; … 6) if the SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC- GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; and 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.3.1] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.1.6." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.1.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.1.4.2 or as the result of receiving a SIP 403 (Forbidden) response as described in this clause. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited.; NOTE 1: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 2: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 3) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the MCVideo ID of the terminating user; and b) the <mcvideo-calling-group-id> element set to the group identity; NOTE 3: The <mcvideo-calling-user-id> is already included in the MIME body as a result of calling clause 6.3.3.1.2 in step 1). 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 131 6) if the in-progress emergency state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.19; b) if the received SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true": i) shall include in the outgoing SIP INVITE request in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; and ii) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcvideo-info+xml MIME body and the application/vnd.3gpp.location- info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false"; and c) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.19; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; and 9) shall send the SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response containing a Require header field with the option tag "100rel" and containing a P-Answer-State header field with the value "Unconfirmed" in response to the SIP INVITE request the controlling MCVideo function: 1) shall send a SIP PRACK request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; 2) shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 9.2.3.4; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 132 3) shall increment the local counter of the number of SIP 200 (OK) responses received from invited members, by 1. NOTE 4: The notifications above could be sent prior to the SIP 200 (OK) response being sent to the inviting MCVideo client. These notifications received by MCVideo clients that are group members do not mean that the group session will be successfully established. NOTE 5: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.1.2] "The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the non-controlling MCVideo function serving the group identity of the MCVideo group owned by the partner MCVideo system; 3) shall set the P-Asserted-Identity to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the group identity of the MCVideo group hosted by the non- controlling MCVideo function in the partner MCVideo system; and b) the <mcvideo-calling-group-id> element set to the group identity of the group served by the controlling MCVideo function; 5) shall include the Recv-Info header field set to g.3gpp.mcvideo-transmission-request; 6) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and 8) shall send the SIP INVITE request towards the partner MCVideo system in accordance with 3GPP TS 24.229 [11]. … Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and NOTE 3: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2. 2) if at least one of the invited MCVideo clients has subscribed to the conference package, shall subscribe to the conference event package in the non-controlling MCVideo function as specified in clause 9.2.3.4.3." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 133 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.2] "In the procedures in this clause: 1) MCVideo ID in an incoming SIP INVITE request refers to the MCVideo ID of the originating user from the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-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 <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 3) MCVideo ID in an outgoing SIP INVITE request refers to the MCVideo ID of the called user in the <mcvideo- request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) indication of required group members in a SIP 183 (Session Progress) response refers to the <required> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to "true" in a SIP 183 (Session Progress) sent by the non-controlling MCVideo function of an MCVideo group; 5) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 6) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for controlling MCVideo function of an MCVideo group", the controlling MCVideo function: … 4) if received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; 5) 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 clause 6.3.5.2; ... 7) shall perform the actions as described in clause 6.3.3.2.2; 8) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero; 9) shall determine if an MCVideo group call for the group identity is already ongoing by determining if an MCVideo session identity has already been allocated for the group call and the MCVideo session is active; … 13) if the MCVideo group call is not ongoing then: … c) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined as determined in step 13) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; d) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; e) shall create a prearranged group session and allocate an MCVideo session identity for the prearranged group call, and shall handle timer TNG3 (group call timer) as specified in clause 6.3.3.5; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 134 f) if the group identity in the "SIP INVITE request for controlling MCVideo function of an MCVideo group" is a TGI: i) shall for each of the constituent MCVideo groups homed on the primary MCVideo system: A) if the controlling MCVideo function does not own the MCVideo group identified by the MCVideo group ID, then generate a SIP INVITE request towards the MCVideo server that owns the MCVideo group identity by following the procedures in clause 9.2.1.4.1.2; and NOTE 2: The MCVideo server that the SIP INVITE request is sent to acts as a non-controlling MCVideo function; B) if the controlling MCVideo function owns the MCVideo group identified by the MCVideo group ID then: I) determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; II) invite each group member determined in step A) above, to the group session, as specified in clause 9.2.1.4.1.1; and III) interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and ii) shall for each of the constituent MCVideo groups homed on the partner MCVideo system generate a SIP INVITE request for the MCVideo group identity homed on the partner MCVideo system as specified in clause 9.2.1.4.1.2; and g) if the group identity in the SIP INVITE request for controlling MCVideo function of an MCVideo group is an MCVideo group ID: i) shall determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; ii) if necessary, shall start timer TNG1 (acknowledged call setup timer) according to the conditions stated in clause 6.3.3.3; iii) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": A) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; and C) if the in-progress emergency state of the group is set to a value of "false": I) shall set the value of the in-progress emergency state of the group to "true"; and II) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; iv) if the in-progress emergency state of the group is set to a value of "false" and if the received SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function shall: A) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and B) if the in-progress imminent peril state of the group is set to a value of "false", shall set the in- progress imminent peril state of the group to a value of "true"; v) shall invite each group member determined in step 13)g)i) above, to the group session, as specified in clause 9.2.1.4.1.1; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 135 vi) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and 14) if the MCVideo group call is ongoing then: … c) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; … e) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined in step 14) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; f) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": i) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; iii) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; and C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.6; iv) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and v) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; g) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function: i) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and ii) if the in-progress imminent peril state of the group is set to a value of "false": A) shall set the in-progress imminent peril state of the group to a value of "true"; B) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.15; and C) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 136 iii) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; h) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.4.2; i) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; j) shall include in the SIP 200 (OK) response with the warning text set to "123 MCVideo session already exists" as specified in clause 4.4; k) if the received SIP re-INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; l) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 4: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. m) shall interact with media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 5: Resulting media plane processing is completed before the next step is performed. n) shall send the SIP 200 (OK) response towards the inviting MCVideo client or inviting non-controlling MCVideo function according to 3GPP TS 24.229 [11]; o) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; NOTE 6: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. p) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]; q) Upon receiving a SIP ACK to the above SIP 200 (OK) response and the SIP 200 (OK) response contained a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall follow the procedures in clause 6.3.3.1.18; and r) shall not continue with the rest of the clause. Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 9.2.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [30], the timer TNG1 (acknowledged call setup timer) is not running, the controlling MCVideo function supports media buffering and the SIP final response is not yet sent to the inviting MCVideo client: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; … 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) shall include a P-Answer-State header field with the value "Unconfirmed"; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 137 5) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 7: Resulting user plane processing is completed before the next step is performed. 8) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; 9) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 8: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 10) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response for a SIP INVITE request as specified in clause 9.2.1.4.1.2 containing an indication of required group members, the timer TNG1 (acknowledged call setup timer) is running and all SIP 200 (OK) responses have been received to all SIP INVITE requests sent to MCVideo clients specified in clause 9.2.1.4.1.1, then the controlling MCVideo function shall wait until the SIP 200 (OK) response has been received to the SIP INVITE request specified in clause 9.2.1.4.1.2 before generating a SIP 200 (OK) response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group". Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1 that was sent to an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24]; and 1) if the MCVideo ID in the SIP 200 (OK) response matches to the MCVideo ID in the corresponding SIP INVITE request; 2) there are no outstanding SIP 200 (OK) responses to SIP INVITE requests which were sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24]; and 3) there is no outstanding SIP 200 (OK) response to a SIP INVITE request sent in clause 9.2.1.4.1.2 where the SIP 183 (Session Progress) response contained an indication of required group members; the controlling MCVideo function: 1) shall stop timer TNG1 (acknowledged call setup timer) as described in clause 6.3.3.3; 2) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; … 4) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 5) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 9: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 7) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 138 NOTE 10: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 8) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon: 1) receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1; 2) the timer TNG1 (acknowledged call setup timer) is not running; 3) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; 4) the controlling MCVideo function supports media buffering; and 5) the SIP final response has not yet been sent to the inviting MCVideo client; the controlling MCVideo function according to local policy: 1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2; … 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 5) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 11: Resulting media plane processing is completed before the next step is performed. 7) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 8) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 12: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 9) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon expiry of timer TNG1 (acknowledged call setup timer), if there are outstanding SIP 200 (OK) responses to SIP INVITE requests sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the procedures specified in clause 6.3.3.3. … Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.3] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 139 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.3.2.2.5.2] "When receiving a "SIP INVITE request for terminating participating MCVideo function" for an on-demand session that requires automatic commencement mode the participating MCVideo function: 1) if: a) the incoming SIP INVITE request contained a Priv-Answer-Mode header field set to the value of "Auto"; b) no Answer-Mode header field or Priv-Answer-Mode header field were received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto- answer"; or c) the incoming SIP INVITE request contained an Answer-Mode header field set to "Auto" and the Answer- Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; then: a) shall generate a SIP 183 (Session Progress) response to the "SIP INVITE request for terminating participating MCVideo function" as specified in clause 6.3.2.2.4.1; and NOTE: The SIP 183 (session Progress) response can be sent reliably or unreliably depending on the content of the received SIP INVITE request. Regardless of if the SIP 183 (Session Progress) response is sent reliably or unreliably, SDP is not included in the SIP 183 (Session Progress) response. b) shall set the P-Answer-State header field to "Unconfirmed" in the SIP 183 (Session Progress) response; 2) shall copy the public user identity contained in the Request-URI of the incoming "SIP INVITE request for terminating participating MCVideo function" to the P-Asserted-Identity header field of the SIP 183 (Session Progress) response; 3) shall generate a SIP INVITE request as specified in clause 6.3.2.2.3; 4) shall set the Request-URI to the public user identity associated to the MCVideo ID of the MCVideo user to be invited; 5) shall perform the procedures specified in clause 6.3.2.2.9 to include any MIME bodies in the received SIP INVITE request, into the outgoing SIP INVITE request; 6) shall copy the contents of the P-Asserted-Identity header field of the incoming "SIP INVITE request for terminating participating MCVideo function" to the P-Asserted-Identity header field of the outgoing SIP INVITE request; 7) if the Priv-Answer-Mode header field is present in the incoming SIP INVITE request with a value of "Auto", shall include a Priv-Answer-Mode header field with the value "Auto" in the outgoing SIP INVITE request. Otherwise, if the Answer-Mode header field is present in the incoming SIP INVITE request, the participating MCVideo function shall include an Answer-Mode header field with the value "Auto" in the outgoing SIP INVITE request; 8) if no Answer-Mode header field or Priv-Answer-Mode header field were received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto-answer", shall set the Answer-Mode header field to "Auto" in the outgoing SIP INVITE request; 9) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for terminating participating MCVideo function" as specified in clause 6.3.2.2.1; 10) if the received SIP INVITE request contains a Resource-Priority header field, shall include a Resource- Priority header field with the contents set as in the received Resource-Priority header field; and 11) shall send the SIP INVITE request towards the MCVideo client according to 3GPP TS 24.229 [11]. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 140 If the SIP 183 (Session Progress) response was sent reliably, then upon receiving a SIP PRACK request, the participating MCVideo function shall generate a SIP 200 (OK) response to the SIP PRACK request and forward the SIP 200 (OK) response, according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the above SIP INVITE request sent to the MCVideo client, the participating MCVideo function: 1) if the SIP 183 (Session Progress) was sent unreliably, shall send the SIP 200 (OK) response immediately; and 2) if the SIP 183 (Session Progress) was sent reliably and, a) if the SIP PRACK request to the SIP 183 (Session Progress) response has been received by the participating MCVideo function and the SIP 200 (OK) response to the SIP PRACK request has been sent, shall send the SIP 200 (OK) response immediately; b) if the SIP PRACK request to the SIP 183 (Session Progress) response has not yet been received, then upon receipt of the SIP PRACK request, the participating MCVideo function shall generate a SIP 200 (OK) response to the SIP PRACK request and forward the SIP 200 (OK) response, according to 3GPP TS 24.229 [11], before sending the SIP 200 (OK) response to the "SIP INVITE request for terminating participating MCVideo function". When the participating MCVideo function sends the SIP 200 (OK) response to the "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2; 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 clause 6.3.2.2.2.1; 3) shall copy the P-Asserted-Identity header field from the incoming SIP 200 (OK) response to the outgoing SIP 200 (OK) response; 4) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 5) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [11]. The participating MCVideo function shall forward any other SIP response that does not contain SDP along the signalling path to the originating network according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.2.3.1.2] "When performing the automatic commencement mode procedures, the MCVideo client shall follow the procedures in clause 6.2.3.1.1 with the following clarification: - The MCVideo client may include a P-Answer-State header field with the value "Confirmed" as specified in IETF RFC 4964 [30] in the SIP 200 (OK) response." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.2.3.1.1] "When performing the automatic commencement mode procedures, the MCVideo client: 1) shall accept the SIP INVITE request and generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [11]; 2) shall include the option tag "timer" in a Require header field of the SIP 200 (OK) response; 3) shall include the g.3gpp.mcvideo media feature tag in the Contact header field of the SIP 200 (OK) response; 4) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcvideo" in the Contact header field of the SIP 200 (OK) response; 5) shall include the Session-Expires header field in the SIP 200 (OK) response and start the SIP session timer according to IETF RFC 4028 [23]. The "refresher" parameter in the Session-Expires header field shall be set to "uas"; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 141 6) shall, if the incoming SIP INVITE request contains a Replaces header field, include in the SDP answer in the SIP 200 (OK) response to the SDP offer the parameters used for the pre-established session identified by the contents of the Replaces header field; 7) shall, if the incoming SIP INVITE request does not contain a Replaces header field, include an SDP answer in the SIP 200 (OK) response to the SDP offer in the incoming SIP INVITE request according to 3GPP TS 24.229 [11] with the clarifications given in clause 6.2.2; NOTE: In the case of a new emergency call where the terminating client is using a pre-established session, the SIP INVITE request containing a Replaces header is used to replace the pre-established session. 8) shall send the SIP 200 (OK) response towards the MCVideo server according to rules and procedures of 3GPP TS 24.229 [11]; 9) shall, if the incoming SIP INVITE request contains a Replaces header field, release the pre-established session identified by the contents of the Replaces header field; and 10) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. When NAT traversal is supported by the MCVideo client and when the MCVideo client is behind a NAT, generation of SIP responses is done as specified in this clause and as specified in IETF RFC 5626 [35]." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.3.2.2] "When an MCVideo call is established a new instance of the transmission control server state machine for 'general transmission control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' is added. When an MCVideo call is established a new instance of the transmission control server state machine for 'general reception control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic reception control operation towards the transmission participant' is added. If the optional "mc_queueing" feature is supported and has been negotiated as specified in clause 14, the transmission control server could queue the implicit transmission control request for the media-transmission control entity. The original initial SIP INVITE request or SIP REFER request to establish an MCVideo chat group call or to rejoin an ongoing MCVideo call is not handled as an implicit transmission control request message by the transmission control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request. The permission to send media to the inviting MCVideo client due to implicit transmission control request is applicable to both confirmed indication and unconfirmed indication. When the first unconfirmed indication is received from the invited participating MCVideo function (see 3GPP TS 24.281 [2]) the transmission control server optionally can give an early indication to send RTP media packets, to the inviting MCVideo client. If an early indication to send RTP media packets is given to the inviting MCVideo client, the transmission participant is granted the permission to send media and the MCVideo server buffers RTP media packets received from the MCVideo client at least until the first invited MCVideo client accepts the invitation or until the RTP media packet buffer exceeds it maximum limit to store RTP media packets. If the MCVideo server does not support or does not allow media buffering then when an early indication to send RTP media packets is not given to the inviting MCVideo client, the transmission participant is granted the permission to send media when the first invited MCVideo client accepts the media. Before the transmission control server sends the first transmission control message in the MCVideo call, the transmission control server has to assign itself a SSRC identifier to be included in media transmission control messages and quality feedback messages if the MCVideo server is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3]. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 142 The transmission participant and the transmission control server can negotiate the maximum priority level that the transmission participant is permitted to request. The transmission control server can pre-empt the current sender based on the negotiated maximum priority level that the transmission participant is permitted to request and the priority level included in the Transmission Media Request message. NOTE: The maximum priority level that a transmission participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the controlling MCVideo function from the group management server as described in 3GPP TS 24.481 [12] and service configuration data retrieved by the controlling MCVideo function from the configuration management server as described in 3GPP TS 24.484 [13]. The transmission participant and the transmission control server can negotiate queueing of Transmission requests using the "mc_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the transmission control server queues the transmission control request if a Transmission Media Request message is received when another transmission participant has the transmission and the priority of the current speaker is the same or higher." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 143 ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 144 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 9.2.1] "The transmission control messages are coded as described in clause 9.1.2 where the transmission control message is part of the application-dependent data. For the transmission control protocol the ASCII name string is: MCVx (Mission Critical Video x) with x=0, 1 or 2 as specified in clause 9.1.2. A list of transmission control messages can be found in clause 9.2.2.1. The transmission control specific fields are specified in clause 9.2.3." |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.2.3 Test description | 6.1.1.2.3.1 Pre-test conditions System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) are affiliated to the Prearranged group. - The IUT (MCVideo Server) is the controlling server of the Prearranged group. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 145 6.1.1.2.3.2 Test procedure sequence Table 6.1.1.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the SS-UE1 (MCVideo Client) request the establishment of an emergency group call to SS- UE2 (MCVideo Client) with automatic commencement mode and implicit transmission control request. - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to establish an emergency pre-arranged group call with automatic commencement mode and implicit transmission control request according to option b.ii of note in Annex A, Table A.3.1.3-1? - - 1 P 3 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 2 P 5 Make the SS-UE1 (MCVideo Client) release the call. - - - - 6 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 3 P 6.1.1.2.3.3 Specific message contents All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.1.1.2.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.1.1.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with conditions GROUP-CALL and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 6.1.1.2.3.3-2: SIP INVITE from the IUT (MCVideo Server) (Step 2, Table 6.1.1.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with conditions GROUP-CALL and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 6.1.1.2.3.3-3: SIP 200 (OK) from the SS-UE2 (Step 2, Table 6.1.1.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7, with conditions GROUP-CALL and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 6.1.1.2.3.3-4: SIP 200 (OK) from the IUT (MCVideo Server) (Step 2, Table 6.1.1.2.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9, with conditions GROUP-CALL and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 146 Table 6.1.1.2.3.3-5: Transmission Idle from the IUT (MCVideo Server) (Step 4, Table 6.1.1.1.3.2-1; Steps 4 and 5, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-6 with condition EMERGENCY-CALL. Table 6.1.1.2.3.3-6: Transmission Granted from the IUT (MCVideo Server) (Step 2, Table 6.1.1.2.3.2-1; Step 2a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.1.4-11 (note), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. Table 6.1.1.2.3.3-7: Media Transmission Notification from the IUT (MCVideo Server) (Step 2, Table 6.1.1.2.3.2-1; Step 3a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.1.4-12 (note), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. 6.1.1.3 MCVideo Server - MCVideo Client / Pre-arranged Group Call / On-demand / Transmission Control State Transitions |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.3.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 and having registered the clients} ensure that { when { the SS-UE1 (MCVideo Client) initiates a pre-arranged group call with automatic commencement mode and without transmission control } then { IUT (MCVideo Server) accepts the call from the initiator and establishes the call with all affiliated users of the group } } (2) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions } ensure that { when { the SS-UE1 (MCVideo client) requests the transmission control with low priority} then { IUT (MCVideo Server) sends transmission granted to the SS-UE1 (MCVideo client) and sends media transmission notification to the SS-UE2 (MCVideo client) } } (3a) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions and Queueing is enabled } ensure that { when { the SS-UE2 (MCVideo client) requests the transmission control with high priority } then { IUT (MCVideo Server) sends transmission queue position info to the SS-UE1 (MCVideo client) } } (3b) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions and Queueing is not enabled } ensure that { when { the SS-UE2 (MCVideo client) requests the transmission control with high priority } then { IUT (MCVideo Server) does not send transmission queue position info to the SS-UE1 (MCVideo client) } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 147 (4) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions } ensure that { when { the SS-UE1 (MCVideo client) requests to revoke media transmission} then { IUT (MCVideo Server) sends transmission deny to the SS-UE1 (MCVideo client) and sends transmission end notify to the SS-UE2 (MCVideo client) } } (5) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions } ensure that { when { the IUT (MCVideo Server) grants transmission to the SS-UE2 (MCVideo client) } then { IUT (MCVideo Server) sends transmission granted and media transmission notification to the SS-UE2 (MCVideo client) ) } } (6) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions } ensure that { when { the SS-UE2 (MCVideo client) requests the end of transmission control } then { IUT (MCVideo Server) IUT (MCVideo Server) sends transmission idle to the SS-UE1 (MCVideo client) and sends transmission idle to the SS-UE2 (MCVideo client) } } (7) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions } ensure that { when { the IUT (MCVideo Server) grants transmission with high priority to the SS-UE2 (MCVideo client) } then { IUT (MCVideo Server) sends transmission granted to the SS-UE1 (MCVideo client) and sends media transmission notification to the SS-UE2 (MCVideo client) } } (8a) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions and Queueing is enabled } ensure that { when { the SS-UE1 (MCVideo client) requests the transmission control with low priority} then { IUT (MCVideo Server) sends transmission queue position info to the SS-UE1 (MCVideo client) } } (9a) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions and Queueing is enabled } ensure that { when { the SS-UE1 (MCVideo client) requests the end of transmission control } then { IUT (MCVideo Server) sends transmission control ack and transmission end response to the SS-UE1 (MCVideo client) } } (10a) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions and Queueing is enabled } ensure that { when { the SS-UE2 (MCVideo client) requests the transmission control with low priority} then { IUT (MCVideo Server) sends transmission queue position info to the SS-UE1 (MCVideo client) } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 148 (11a) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions and Queueing is enabled } ensure that { when { the SS-UE1 (MCVideo client) requests the end of transmission control } then { IUT (MCVideo Server) sends transmission end response to the SS-UE1 (MCVideo client) and sends transmission end notify to the SS-UE2 (MCVideo client) } } (12a) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions and Queueing is enabled } ensure that { when { the SS-UE1 (MCVideo client) requests the transmission control } then { IUT (MCVideo Server) sends transmission granted to the SS-UE1 (MCVideo client) and sends media transmission notification to the SS-UE2 (MCVideo client) } } (13a) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions and Queueing is enabled } ensure that { when { the SS-UE1 (MCVideo client) requests the end of transmission control } then { IUT (MCVideo Server) sends transmission idle to the SS-UE1 (MCVideo client) and sends transmission idle to the SS-UE2 (MCVideo client) } } (8b) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions and Queueing is not enabled } ensure that { when { IUT (MCVideo Server) requests the transmission control } then { IUT (MCVideo Server) sends transmission rejected to the SS-UE1 (MCVideo client) } } (14) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions } ensure that { when { the SS-UE1 (MCVideo client) requests the transmission control } then { IUT (MCVideo Server) sends transmission granted to the SS-UE1 (MCVideo client) and sends media transmission notification to the SS-UE2 (MCVideo client) } } (15) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions } ensure that { when { the SS-UE1 (MCVideo client) requests to revoke media transmission} then { IUT (MCVideo Server) sends transmission deny to the SS-UE1 (MCVideo client) and sends transmission idle to the SS-UE2 (MCVideo client) } } (16) with { IUT (MCVideo Server) having established an MCVideo On-demand Pre-arranged Group Call with Transmission Control State Transitions } ensure that { when { the SS-UE1 (MCVideo client) ends the group call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the SS-UE2 (MCVideo Client) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.3.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 9.2.1.3.1.1, 9.2.1.3.2, 9.2.1.3.3.1, 9.2.1.4.1.1, 9.2.1.4.1.2, 9.2.1.4.2, 9.2.1.4.3, 6.3.2.2.5.2, 6.2.3.1.2, 6.2.3.1.1, and ETSI TS 124 581 [9] (3GPP TS 24.581), clauses 6.3.2.2, 6.3.3, 6.4.2, 6.4.3, 6.4.4, 9.2.1, 6.2.1, 6.2.2, 6.2.4. Unless otherwise stated, these are Rel-15 requirements. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 149 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.1.1] "In the procedures in this clause: 1) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 3) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "prearranged", the participating MCVideo function: … 2) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and shall authorise the calling user; NOTE 2: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 5) shall check if the number of maximum simultaneous MCVideo group calls supported for the MCVideo user as specified in the <MaxSimultaneousCallsN6> element of the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) has been exceeded. If exceeded, the participating MCVideo function shall respond with a SIP 486 (Busy Here) response with the warning text set to "103 maximum simultaneous MCVideo group calls reached" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps; NOTE 3: If the SIP INVITE request contains an emergency indication or an imminent peril indication, the participating MCVideo function can by means beyond the scope of this specification choose to allow for an exception to the limit for the maximum simultaneous MCVideo sessions supported for the MCVideo user. Alternatively, a lower priority session of the MCVideo user could be terminated to allow for the new session. 6) if the user identified by the MCVideo ID is not affiliated to the group identified in the "SIP INVITE request for originating participating MCVideo function" as determined by clause 8.2.2.2.11 and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, shall perform the actions specified in clause 8.2.2.2.12 for implicit affiliation; … 8) shall determine the public service identity of the controlling MCVideo function associated with the group identity in the SIP INVITE request; NOTE 6: The public service identity can identify the controlling MCVideo function in the primary MCVideo system or a partner MCVideo system. NOTE 7: How the participating MCVideo server discovers the public service identity of the controlling MCVideo function associated with the group identity is out of scope of the current release. 9) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3; 10) shall set the Request-URI to the public service identity of the controlling MCVideo function associated with the group identity which was present in the incoming SIP INVITE request; 11) shall not copy the following header fields from the incoming SIP INVITE request to the outgoing SIP INVITE request, if they were present in the incoming SIP INVITE request: a) Answer-Mode header field as specified in IETF RFC 5373 [27]; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 150 b) Priv-Answer-Mode header field as specified in IETF RFC 5373 [27]; 12) shall set the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; 14) if the received SIP INVITE request contains an application/vnd.3gpp.location-info+xml MIME body and if not already copied, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body received in the SIP INVITE request into an application/vnd.3gpp.location-info+xml MIME body included in the outgoing SIP request; 15) if a Resource-Priority header field was included in the received SIP INVITE request, shall include a Resource- Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCVideo client; and NOTE 8: The participating MCVideo function will leave verification of the Resource-Priority header field to the controlling MCVideo function. 16) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. … Upon receipt of a SIP 2xx response in response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) if the received SIP 2xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC-GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 2) shall generate a SIP 200 (OK) response as in clause 6.3.2.1.5.2; 3) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 4) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 5) 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; 6) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 7) if the procedures of clause 8.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 8.2.2.2.13; 8) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 9) shall interact with Media Plane as specified in 3GPP TS 24.581 [5]; and 10) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [23]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request in step 14) the participating MCVideo function: 1) shall generate a SIP response according to 3GPP TS 24.229 [11]; 2) shall include Warning header field(s) that were received in the incoming SIP response; 3) shall forward the SIP response to the MCVideo client according to 3GPP TS 24.229 [11]; and 4) if the implicit affiliation procedures of clause 8.2.2.2.12 were invoked in this procedure, shall perform the procedures of clause 8.2.2.2.14;..." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 151 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.2] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. NOTE 1: This clause covers on-demand session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: … 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; … 6) if the SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC- GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; and 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.3.1] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.1.6." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.1.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.1.4.2 or as the result of receiving a SIP 403 (Forbidden) response as described in this clause. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited.; NOTE 1: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 2: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 3) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCVideo function; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 152 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the MCVideo ID of the terminating user; and b) the <mcvideo-calling-group-id> element set to the group identity; NOTE 3: The <mcvideo-calling-user-id> is already included in the MIME body as a result of calling clause 6.3.3.1.2 in step 1). 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; 6) if the in-progress emergency state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.19; b) if the received SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true": i) shall include in the outgoing SIP INVITE request in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; and ii) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcvideo-info+xml MIME body and the application/vnd.3gpp.location- info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false"; and c) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.19; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; and 9) shall send the SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [11]. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 153 Upon receiving a SIP 183 (Session Progress) response containing a Require header field with the option tag "100rel" and containing a P-Answer-State header field with the value "Unconfirmed" in response to the SIP INVITE request the controlling MCVideo function: 1) shall send a SIP PRACK request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; 2) shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 9.2.3.4; and 3) shall increment the local counter of the number of SIP 200 (OK) responses received from invited members, by 1. NOTE 4: The notifications above could be sent prior to the SIP 200 (OK) response being sent to the inviting MCVideo client. These notifications received by MCVideo clients that are group members do not mean that the group session will be successfully established. NOTE 5: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.1.2] "The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the non-controlling MCVideo function serving the group identity of the MCVideo group owned by the partner MCVideo system; 3) shall set the P-Asserted-Identity to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the group identity of the MCVideo group hosted by the non- controlling MCVideo function in the partner MCVideo system; and b) the <mcvideo-calling-group-id> element set to the group identity of the group served by the controlling MCVideo function; 5) shall include the Recv-Info header field set to g.3gpp.mcvideo-transmission-request; 6) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 154 8) shall send the SIP INVITE request towards the partner MCVideo system in accordance with 3GPP TS 24.229 [11]. … Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and NOTE 3: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2. 2) if at least one of the invited MCVideo clients has subscribed to the conference package, shall subscribe to the conference event package in the non-controlling MCVideo function as specified in clause 9.2.3.4.3." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.2] "In the procedures in this clause: 1) MCVideo ID in an incoming SIP INVITE request refers to the MCVideo ID of the originating user from the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-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 <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 3) MCVideo ID in an outgoing SIP INVITE request refers to the MCVideo ID of the called user in the <mcvideo- request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) indication of required group members in a SIP 183 (Session Progress) response refers to the <required> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to "true" in a SIP 183 (Session Progress) sent by the non-controlling MCVideo function of an MCVideo group; 5) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 6) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for controlling MCVideo function of an MCVideo group", the controlling MCVideo function: … 4) if received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; 5) 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 clause 6.3.5.2; ... 7) shall perform the actions as described in clause 6.3.3.2.2; 8) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero; 9) shall determine if an MCVideo group call for the group identity is already ongoing by determining if an MCVideo session identity has already been allocated for the group call and the MCVideo session is active; … 13) if the MCVideo group call is not ongoing then: … ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 155 c) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined as determined in step 13) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; d) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; e) shall create a prearranged group session and allocate an MCVideo session identity for the prearranged group call, and shall handle timer TNG3 (group call timer) as specified in clause 6.3.3.5; f) if the group identity in the "SIP INVITE request for controlling MCVideo function of an MCVideo group" is a TGI: i) shall for each of the constituent MCVideo groups homed on the primary MCVideo system: A) if the controlling MCVideo function does not own the MCVideo group identified by the MCVideo group ID, then generate a SIP INVITE request towards the MCVideo server that owns the MCVideo group identity by following the procedures in clause 9.2.1.4.1.2; and NOTE 2: The MCVideo server that the SIP INVITE request is sent to acts as a non-controlling MCVideo function; B) if the controlling MCVideo function owns the MCVideo group identified by the MCVideo group ID then: I) determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; II) invite each group member determined in step A) above, to the group session, as specified in clause 9.2.1.4.1.1; and III) interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and ii) shall for each of the constituent MCVideo groups homed on the partner MCVideo system generate a SIP INVITE request for the MCVideo group identity homed on the partner MCVideo system as specified in clause 9.2.1.4.1.2; and g) if the group identity in the SIP INVITE request for controlling MCVideo function of an MCVideo group is an MCVideo group ID: i) shall determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; ii) if necessary, shall start timer TNG1 (acknowledged call setup timer) according to the conditions stated in clause 6.3.3.3; iii) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": A) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; and C) if the in-progress emergency state of the group is set to a value of "false": I) shall set the value of the in-progress emergency state of the group to "true"; and II) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 156 iv) if the in-progress emergency state of the group is set to a value of "false" and if the received SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function shall: A) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and B) if the in-progress imminent peril state of the group is set to a value of "false", shall set the in- progress imminent peril state of the group to a value of "true"; v) shall invite each group member determined in step 13)g)i) above, to the group session, as specified in clause 9.2.1.4.1.1; and vi) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and 14) if the MCVideo group call is ongoing then: … c) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; … e) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined in step 14) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; f) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": i) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; iii) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; and C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.6; iv) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and v) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 157 g) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function: i) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and ii) if the in-progress imminent peril state of the group is set to a value of "false": A) shall set the in-progress imminent peril state of the group to a value of "true"; B) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.15; and C) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and iii) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; h) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.4.2; i) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; j) shall include in the SIP 200 (OK) response with the warning text set to "123 MCVideo session already exists" as specified in clause 4.4; k) if the received SIP re-INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; l) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 4: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. m) shall interact with media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 5: Resulting media plane processing is completed before the next step is performed. n) shall send the SIP 200 (OK) response towards the inviting MCVideo client or inviting non-controlling MCVideo function according to 3GPP TS 24.229 [11]; o) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; NOTE 6: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. p) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 158 q) Upon receiving a SIP ACK to the above SIP 200 (OK) response and the SIP 200 (OK) response contained a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall follow the procedures in clause 6.3.3.1.18; and r) shall not continue with the rest of the clause. Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 9.2.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [30], the timer TNG1 (acknowledged call setup timer) is not running, the controlling MCVideo function supports media buffering and the SIP final response is not yet sent to the inviting MCVideo client: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; … 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) shall include a P-Answer-State header field with the value "Unconfirmed"; 5) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 7: Resulting user plane processing is completed before the next step is performed. 8) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; 9) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 8: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 10) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response for a SIP INVITE request as specified in clause 9.2.1.4.1.2 containing an indication of required group members, the timer TNG1 (acknowledged call setup timer) is running and all SIP 200 (OK) responses have been received to all SIP INVITE requests sent to MCVideo clients specified in clause 9.2.1.4.1.1, then the controlling MCVideo function shall wait until the SIP 200 (OK) response has been received to the SIP INVITE request specified in clause 9.2.1.4.1.2 before generating a SIP 200 (OK) response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group". Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1 that was sent to an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24]; and 1) if the MCVideo ID in the SIP 200 (OK) response matches to the MCVideo ID in the corresponding SIP INVITE request; 2) there are no outstanding SIP 200 (OK) responses to SIP INVITE requests which were sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24]; and 3) there is no outstanding SIP 200 (OK) response to a SIP INVITE request sent in clause 9.2.1.4.1.2 where the SIP 183 (Session Progress) response contained an indication of required group members; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 159 the controlling MCVideo function: 1) shall stop timer TNG1 (acknowledged call setup timer) as described in clause 6.3.3.3; 2) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; … 4) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 5) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 9: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 7) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 10: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 8) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon: 1) receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1; 2) the timer TNG1 (acknowledged call setup timer) is not running; 3) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; 4) the controlling MCVideo function supports media buffering; and 5) the SIP final response has not yet been sent to the inviting MCVideo client; the controlling MCVideo function according to local policy: 1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2; … 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 5) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 11: Resulting media plane processing is completed before the next step is performed. 7) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 160 8) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 12: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 9) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon expiry of timer TNG1 (acknowledged call setup timer), if there are outstanding SIP 200 (OK) responses to SIP INVITE requests sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the procedures specified in clause 6.3.3.3. … Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.3] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.3.2.2.5.2] "When receiving a "SIP INVITE request for terminating participating MCVideo function" for an on-demand session that requires automatic commencement mode the participating MCVideo function: 1) if: a) the incoming SIP INVITE request contained a Priv-Answer-Mode header field set to the value of "Auto"; b) no Answer-Mode header field or Priv-Answer-Mode header field were received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto- answer"; or c) the incoming SIP INVITE request contained an Answer-Mode header field set to "Auto" and the Answer- Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; then: a) shall generate a SIP 183 (Session Progress) response to the "SIP INVITE request for terminating participating MCVideo function" as specified in clause 6.3.2.2.4.1; and NOTE: The SIP 183 (session Progress) response can be sent reliably or unreliably depending on the content of the received SIP INVITE request. Regardless of if the SIP 183 (Session Progress) response is sent reliably or unreliably, SDP is not included in the SIP 183 (Session Progress) response. b) shall set the P-Answer-State header field to "Unconfirmed" in the SIP 183 (Session Progress) response; 2) shall copy the public user identity contained in the Request-URI of the incoming "SIP INVITE request for terminating participating MCVideo function" to the P-Asserted-Identity header field of the SIP 183 (Session Progress) response; 3) shall generate a SIP INVITE request as specified in clause 6.3.2.2.3; 4) shall set the Request-URI to the public user identity associated to the MCVideo ID of the MCVideo user to be invited; 5) shall perform the procedures specified in clause 6.3.2.2.9 to include any MIME bodies in the received SIP INVITE request, into the outgoing SIP INVITE request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 161 6) shall copy the contents of the P-Asserted-Identity header field of the incoming "SIP INVITE request for terminating participating MCVideo function" to the P-Asserted-Identity header field of the outgoing SIP INVITE request; 7) if the Priv-Answer-Mode header field is present in the incoming SIP INVITE request with a value of "Auto", shall include a Priv-Answer-Mode header field with the value "Auto" in the outgoing SIP INVITE request. Otherwise, if the Answer-Mode header field is present in the incoming SIP INVITE request, the participating MCVideo function shall include an Answer-Mode header field with the value "Auto" in the outgoing SIP INVITE request; 8) if no Answer-Mode header field or Priv-Answer-Mode header field were received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto-answer", shall set the Answer-Mode header field to "Auto" in the outgoing SIP INVITE request; 9) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for terminating participating MCVideo function" as specified in clause 6.3.2.2.1; 10) if the received SIP INVITE request contains a Resource-Priority header field, shall include a Resource- Priority header field with the contents set as in the received Resource-Priority header field; and 11) shall send the SIP INVITE request towards the MCVideo client according to 3GPP TS 24.229 [11]. If the SIP 183 (Session Progress) response was sent reliably, then upon receiving a SIP PRACK request, the participating MCVideo function shall generate a SIP 200 (OK) response to the SIP PRACK request and forward the SIP 200 (OK) response, according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the above SIP INVITE request sent to the MCVideo client, the participating MCVideo function: 1) if the SIP 183 (Session Progress) was sent unreliably, shall send the SIP 200 (OK) response immediately; and 2) if the SIP 183 (Session Progress) was sent reliably and, a) if the SIP PRACK request to the SIP 183 (Session Progress) response has been received by the participating MCVideo function and the SIP 200 (OK) response to the SIP PRACK request has been sent, shall send the SIP 200 (OK) response immediately; b) if the SIP PRACK request to the SIP 183 (Session Progress) response has not yet been received, then upon receipt of the SIP PRACK request, the participating MCVideo function shall generate a SIP 200 (OK) response to the SIP PRACK request and forward the SIP 200 (OK) response, according to 3GPP TS 24.229 [11], before sending the SIP 200 (OK) response to the "SIP INVITE request for terminating participating MCVideo function". When the participating MCVideo function sends the SIP 200 (OK) response to the "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2; 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 clause 6.3.2.2.2.1; 3) shall copy the P-Asserted-Identity header field from the incoming SIP 200 (OK) response to the outgoing SIP 200 (OK) response; 4) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 5) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [11]. The participating MCVideo function shall forward any other SIP response that does not contain SDP along the signalling path to the originating network according to 3GPP TS 24.229 [11]. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 162 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.2.3.1.2] When performing the automatic commencement mode procedures, the MCVideo client shall follow the procedures in clause 6.2.3.1.1 with the following clarification: - The MCVideo client may include a P-Answer-State header field with the value "Confirmed" as specified in IETF RFC 4964 [30] in the SIP 200 (OK) response." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.2.3.1.1] "When performing the automatic commencement mode procedures, the MCVideo client: 1) shall accept the SIP INVITE request and generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [11]; 2) shall include the option tag "timer" in a Require header field of the SIP 200 (OK) response; 3) shall include the g.3gpp.mcvideo media feature tag in the Contact header field of the SIP 200 (OK) response; 4) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcvideo" in the Contact header field of the SIP 200 (OK) response; 5) shall include the Session-Expires header field in the SIP 200 (OK) response and start the SIP session timer according to IETF RFC 4028 [23]. The "refresher" parameter in the Session-Expires header field shall be set to "uas"; 6) shall, if the incoming SIP INVITE request contains a Replaces header field, include in the SDP answer in the SIP 200 (OK) response to the SDP offer the parameters used for the pre-established session identified by the contents of the Replaces header field; 7) shall, if the incoming SIP INVITE request does not contain a Replaces header field, include an SDP answer in the SIP 200 (OK) response to the SDP offer in the incoming SIP INVITE request according to 3GPP TS 24.229 [11] with the clarifications given in clause 6.2.2; NOTE: In the case of a new emergency call where the terminating client is using a pre-established session, the SIP INVITE request containing a Replaces header is used to replace the pre-established session. 8) shall send the SIP 200 (OK) response towards the MCVideo server according to rules and procedures of 3GPP TS 24.229 [11]; 9) shall, if the incoming SIP INVITE request contains a Replaces header field, release the pre-established session identified by the contents of the Replaces header field; and 10) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. When NAT traversal is supported by the MCVideo client and when the MCVideo client is behind a NAT, generation of SIP responses is done as specified in this clause and as specified in IETF RFC 5626 [35]." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.3.2.2] "When an MCVideo call is established a new instance of the transmission control server state machine for 'general transmission control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' is added. When an MCVideo call is established a new instance of the transmission control server state machine for 'general reception control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic reception control operation towards the transmission participant' is added. If the optional "mc_queueing" feature is supported and has been negotiated as specified in clause 14, the transmission control server could queue the implicit transmission control request for the media-transmission control entity. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 163 The original initial SIP INVITE request or SIP REFER request to establish an MCVideo chat group call or to rejoin an ongoing MCVideo call is not handled as an implicit transmission control request message by the transmission control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request. The permission to send media to the inviting MCVideo client due to implicit transmission control request is applicable to both confirmed indication and unconfirmed indication. When the first unconfirmed indication is received from the invited participating MCVideo function (see 3GPP TS 24.281 [2]) the transmission control server optionally can give an early indication to send RTP media packets, to the inviting MCVideo client. If an early indication to send RTP media packets is given to the inviting MCVideo client, the transmission participant is granted the permission to send media and the MCVideo server buffers RTP media packets received from the MCVideo client at least until the first invited MCVideo client accepts the invitation or until the RTP media packet buffer exceeds it maximum limit to store RTP media packets. If the MCVideo server does not support or does not allow media buffering then when an early indication to send RTP media packets is not given to the inviting MCVideo client, the transmission participant is granted the permission to send media when the first invited MCVideo client accepts the media. Before the transmission control server sends the first transmission control message in the MCVideo call, the transmission control server has to assign itself a SSRC identifier to be included in media transmission control messages and quality feedback messages if the MCVideo server is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3]. The transmission participant and the transmission control server can negotiate the maximum priority level that the transmission participant is permitted to request. The transmission control server can pre-empt the current sender based on the negotiated maximum priority level that the transmission participant is permitted to request and the priority level included in the Transmission Media Request message. NOTE: The maximum priority level that a transmission participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the controlling MCVideo function from the group management server as described in 3GPP TS 24.481 [12] and service configuration data retrieved by the controlling MCVideo function from the configuration management server as described in 3GPP TS 24.484 [13]. The transmission participant and the transmission control server can negotiate queueing of Transmission requests using the "mc_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the transmission control server queues the transmission control request if a Transmission Media Request message is received when another transmission participant has the transmission and the priority of the current speaker is the same or higher." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 164 Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 165 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 9.2.1] "The transmission control messages are coded as described in clause 9.1.2 where the transmission control message is part of the application-dependent data. For the transmission control protocol the ASCII name string is: MCVx (Mission Critical Video x) with x=0, 1 or 2 as specified in clause 9.1.2. A list of transmission control messages can be found in clause 9.2.2.1. The transmission control specific fields are specified in clause 9.2.3." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.2.1] "Based on the negotiations during the call establishment specified in 3GPP TS 24.281 [2], a new instance of the 'Transmission participant state transition diagram for basic transmission control operation', as specified in clause 6.2.4 and a new instance of the 'Transmission participant state transition diagram for basic reception control operation' as specified in clause 6.2.5, shall be created for this call. The SIP INVITE request sent by the application and signalling plane: 1. shall be regarded an implicit Transmission request when an implicit Transmission request is negotiated; and 2. shall not be regarded as an implicit Transmission request in case of a rejoin to an already on-going group call. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 166 NOTE: The transmission participant can negotiate the use of prioritization of the Transmission Media Request message. In that case, the transmission participant can request permission to send media at a priority level that is either the same as or lower than the highest priority that was permitted to the participant in the MCVideo call initialization. If a transmission participant is authorized for pre-emptive priority in the MCVideo call it is good practise to always request permission to send RTP media packets at a priority level that is lower than pre-emptive priority unless the user explicitly requests to pre-empt the current RTP media packets sender." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.2.2] "The MCVideo call release (whether it is initiated by the transmission participant or transmission control server) is a two-step procedure. Step 1 The transmission participant stops sending transmission control and reception control messages and the MCVideo client stops sending and receiving RTP media packets. Step 2 When the application and signalling plane has determined that the MCVideo call is released, the corresponding instance of the 'Transmission participant state transition diagram for basic transmission control operation' as specified in clause 6.2.4 and the corresponding instance of the 'Transmission participant state transition diagram for basic reception control operation' as specified in clause 6.2.5 are terminated and the transmission participant releases all the used resources. The user plane can initiate the release step 1, but the application and signalling plane always initiates the release step 2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.2.4] "The transmission participant shall behave according to the state diagram and the state transitions specified in this clause. Figure 6.2.4.1-1 shows the state diagram for 'Transmission participant state transition diagram for basic transmission control operation'. …" |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.3.3 Test description | 6.1.1.3.3.1 Pre-test conditions System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 167 Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) are affiliated to the Prearranged group. - The IUT (MCVideo Server) is the controlling server of the Prearranged group. 6.1.1.3.3.2 Test procedure sequence Table 6.1.1.3.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the SS-UE1 (MCVideo Client) request the establishment of a pre-arranged group call to SS- UE2 (MCVideo Client) with automatic commencement mode and without transmission request. - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to establish a pre- arranged group call with automatic commencement mode and without transmission control request according to option a of note in Annex A, Table A.3.1.3-1? - - 1 P 3 Make the SS-UE1 (MCVideo Client) request transmission with low priority. - - - - 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1 for SS-UE1 (MCVideo Client)? - - 2 P 5 Make the SS-UE2 (MCVideo Client) request transmission with high priority. - - - - - EXCEPTION: Steps 6a - 6b describe behaviour that depends on pc_MCVideo_TransmissionRequestQueueing. - - - - - IF pc_MCVideo_TransmissionRequestQueueing THEN: - - - - 6a Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Queue Position Info' as described in Annex A, Table A.3.12.3-1 for SS-UE2 (MCVideo Client)? - - 3a P - ELSE: - - - - 6b Check: Does the IUT (MCVideo Server) correctly perform steps 1-2 of procedure 'MCVideo Transmission Request - Queue Position Info' as described in Annex A, Table A.3.12.3-1 for SS-UE2 (MCVideo Client)? - - 3b P 7 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Revoked - Transmission End Request' as described in Annex A, Table A.3.14.3-1, to revoke SS-UE1 (MCVideo Client) media transmission, with revoke reason #4 (Media Burst pre-empted)? - - 4 P 8 Check: Does the IUT (MCVideo Server) send a Transmission End Notify message to SS-UE2 (MCVideo Client) informing that SS-UE1 (MCVideo Client) has stopped to transmit? <-- Transmission End Notify 4 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 168 St Procedure Message Sequence TP Verdict U - S Message 9 IF the IUT (MCVideo Server) requests acknowledgement, the SS-UE2 (MCVideo Client) sends a Transmission Control Ack message in response to the Transmission End Notify message. --> Transmission Control Ack - - 10 Check: Does the IUT (MCVideo Server) correctly perform steps 3a1-3b2 of procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1 to grant the transmission to SS-UE2 (MCVideo Client)? - - 5 P 11 Make the SS-UE2 (MCVideo Client) request end of transmission. - - - - 12 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1 for SS-UE2 (MCVideo Client)? - - 6 P 13 Make the SS-UE2 (MCVideo Client) request transmission with high priority. - - - - 14 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1 for SS-UE2 (MCVideo Client)? - - 7 P 15 Make the SS-UE1 (MCVideo Client) request transmission with low priority. - - - - - EXCEPTION: Steps 16a1 - 16b1 describe behaviour that depends on pc_MCVideo_TransmissionRequestQueueing. - - - - - IF pc_MCVideo_TransmissionRequestQueueing THEN: - - - - 16a1 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Queue Position Info' as described in Annex A, Table A.3.12.3-1 for SS-UE1 (MCVideo Client)? - - 8a P 16a2 Make the SS-UE1 (MCVideo Client) request queue position. - - - - 16a3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Queue Position Request - Queue Position Info', as described in Annex A, Table A.3.13.3-1 for SS-UE1 (MCVideo Client)? - - 8a P 16a4 Make the SS-UE1 (MCVideo Client) cancel queued transmission. - - - - 16a5 The SS-UE1 (MCVideo Client) sends a Transmission End Request message, with acknowledgement, to cancel queued transmission. --> Transmission End Request - - 16a6 Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack 9a P 16a7 Check: Does the IUT (MCVideo Server) send a Transmission End Response message to SS-UE1 (MCVideo Client)? <-- Transmission End Response 9a P 16a8 IF the IUT (MCVideo Server) requests acknowledgement, the SS-UE1 (MCVideo Client) sends a Transmission Control Ack message in response to the Transmission End Response message. --> Transmission Control Ack - - 16a9 Make the SS-UE1 (MCVideo Client) request transmission with low priority. - - - - ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 169 St Procedure Message Sequence TP Verdict U - S Message 16a10 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Queue Position Info' as described in Annex A, Table A.3.12.3-1 for SS-UE1 (MCVideo Client)? - - 10a P 16a11 Make the SS-UE2 (MCVideo Client) request end of transmission. - - - - 16a12 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify', except steps 3a5-3a8 and 3b3-3b4, as described in Annex A, Table A.3.8.3-1? - - 11a P 16a13 Check: Does the IUT (MCVideo Server) correctly perform steps 3a1-3b2 of procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1 to grant transmission to SS-UE1 (MCVideo Client)? - - 12a P 16a14 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 16a15 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 13a P - ELSE: - - - - 16b1 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Rejected' as described in Annex A, Table A.3.11.3-1 for SS-UE1 (MCVideo Client)? - - 8b P 17 Make the SS-UE1 (MCVideo Client) request transmission and transmit media until transmission timer expires. - - - - 18 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1 for SS-UE1 (MCVideo Client)? - - 14 P 19 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Revoked - Transmission End Request' as described in Annex A, Table A.3.14.3-1, to revoke SS-UE1 (MCVideo Client) media transmission, with revoke reason #2 (Media Burst too long)? - - 15 P 20 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1, except steps 1-3a2 and 3b1, to inform SS-UE2 (MCVideo Client) that SS-UE1 (MCVideo Client) transmission has ended? - - 15 P 21 Make the SS-UE1 (MCVideo Client) release the call. - - - - 22 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 16 P 6.1.1.3.3.3 Specific message contents All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 170 Table 6.1.1.3.3.3-1: SIP INVITE from the SS-UE1 (MCVideo Client) (Step 2, Table 6.1.1.3.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.1.3.3.3-2: SIP INVITE from the IUT (MCVideo Server) (Step 2, Table 6.1.1.3.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.1.3.3.3-3: SIP 200 (OK) from the SS-UE2 (MCVideo Client) (Step 2, Table 6.1.1.3.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.1.3.3.3-4: SIP 200 (OK) from the IUT (MCVideo Server) (Step 2, Table 6.1.1.3.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.1.3.3.3-5: Transmission Request from the SS-UE1 (MCVideo Client) (Steps 4, 16a1, 16a10 and 16b1, Table 6.1.1.3.3.2-1; Step 1, Annex A, Table A.3.7.3-1; Step 1, Annex A, Table A.3.11.3-1; Step 1, Annex A, Table A.3.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.1.1-1, with condition ACK Information Element Value/remark Comment Reference Condition Transmission Priority ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.2 Transmission Priority Value "5" Table 6.1.1.3.3.3-6: Transmission Granted from the IUT (MCVideo Server) (Steps 4 and 16a13, Table 6.1.1.3.3.2-1; Steps 3b1 and 3a1, Annex A, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.1-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Transmission Priority ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.2 Transmission Priority Value "5" Table 6.1.1.3.3.3-7: Transmission Request from the SS-UE2 (MCVideo Client) (Steps 6a, 6b and 14, Table 6.1.1.3.3.2-1; Step 1, Annex A, Table A.3.7.3-1; Step 1, Annex A, Table A.3.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.1.1-1, with condition ACK Information Element Value/remark Comment Reference Condition Transmission Priority ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.2 Transmission Priority Value "15" ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 171 Table 6.1.1.3.3.3-8: Queue Position Info from the IUT (MCVideo Server) (Steps 6a and 6b, Table 6.1.1.3.3.2-1; Steps 3a1 and 3b1, Annex A, Table A.3.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.6-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Queue Info Defines the queue position and granted transmission control priority in the queue. ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.5 Queue Priority Level "15" ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.2 Table 6.1.1.3.3.3-9: Transmission Revoked from the IUT (MCVideo Server) (Step 7, Table 6.1.1.3.3.2-1; Steps 1aA and 1aB, Annex A, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.2-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Reject Cause ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.4 Reject Cause Value 4 ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.10.2 Reject Cause Phrase "Media Burst pre-empted" A text string encoded the text string in the SDES item CNAME. ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.10.2 Table 6.1.1.3.3.3-10: Transmission End Request from the IUT (MCVideo Server) (Step 7, Table 6.1.1.3.3.2-1; Steps 1bA and 1bB, Annex A, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.1-1, with condition DOWNLINK. With condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Reject Cause ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.4 Reject Cause Value 4 ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.10.2 Reject Cause Phrase "Media Burst pre-empted" A text string encoded the text string in the SDES item CNAME. ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.10.2 Table 6.1.1.3.3.3-11: Transmission End Notify from the IUT (MCVideo Server) (Step 8, Table 6.1.1.3.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.15-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition User Id of the Transmitting User Carries the identity of the user whose media transmission has been released ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.6 User Id of the Transmitting User px_MCVideo_ID_User_A Audio SSRC of the Transmitting User Media/Audio SSRC of remote client (Client A) SSRC of the user transmitting the media ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.16 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 172 Table 6.1.1.3.3.3-12: Transmission Control Ack from the SS-UE1 (MCVideo Client) (Step 9, Table 6.1.1.3.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK Table 6.1.1.3.3.3-13: Transmission Granted from the IUT (MCVideo Server) (Steps 10 and 14, Table 6.1.1.3.3.2-1; Steps 3a1 and 3b1, Annex A, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.1-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Transmission Priority ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.2 Transmission Priority Value "15" Table 6.1.1.3.3.3-14: Media Transmission Notification from the IUT (MCVideo Server) (Steps 10 and 14, Table 6.1.1.3.3.2-1; Steps 3a3 and 3b2, Annex A, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.7-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Table 6.1.1.3.3.3-15: Transmission End Request from the SS-UE2 (MCVideo Client) (Steps 12 and 16a12, Table 6.1.1.3.3.2-1; Step 1, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-1 Information Element Value/remark Comment Reference Condition User Id of the Transmitting User identity of the user whose media transmission is requested to be terminated. ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.6 User Id of the Transmitting User px_MCVideo_ID_User_B Table 6.1.1.3.3.3-16: Transmission End Notify from the IUT (MCVideo Server) (Steps 12 and 16a12, Table 6.1.1.3.3.2-1; Steps 3a3 and 3b2, Annex A, Table A.3.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.15-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Table 6.1.1.3.3.3-17: Queue Position Info from the IUT (MCVideo Server) (Steps 16a1, 16a3 and 16a10, Table 6.1.1.3.3.2-1; Steps 3a1 and 3b1, Annex A, Table A.3.12.3-1; Steps 3a1 and 3b1, Annex A, Table A.3.13.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.6-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Queue Info Defines the queue position and granted transmission control priority in the queue. ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.5 Queue Priority Level "5" ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.2 Table 6.1.1.3.3.3-18: Transmission End Request from the SS-UE1 (MCVideo Client) (Step 16a5, Table 6.1.1.3.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.1-1, with conditions ACK and UPLINK. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 173 Table 6.1.1.3.3.3-19: Transmission Control Ack from the IUT (MCVideo Server) (Steps 16a6, Table 6.1.1.3.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, with condition DOWNLINK. Table 6.1.1.3.3.3-20: Transmission End Response from the IUT (MCVideo Server) (Step 16a7, Table 6.1.1.3.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.2-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Table 6.1.1.3.3.3-21: Transmission Control Ack from the SS-UE1 (MCVideo Client) (Steps 16a8, Table 6.1.1.3.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, with condition UPLINK. Table 6.1.1.3.3.3-22: Transmission Revoked from the IUT (MCVideo Server) (Step 19, Table 6.1.1.3.3.2-1; Steps 1aA and 1aB, Annex A, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.2-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Reject Cause ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.4 Reject Cause Value 2 ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.10.2 Reject Cause Phrase "Media burst too long" A text string encoded the text string in the SDES item CNAME. ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.10.2 Table 6.1.1.3.3.3-23: Transmission End Request from the IUT (MCVideo Server) (Step 19, Table 6.1.1.3.3.2-1; Steps 1bA and 1bB, Annex A, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.1-1, with condition DOWNLINK. With condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Reject Cause ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.4 Reject Cause Value 2 ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.10.2 Reject Cause Phrase "Media burst too long" A text string encoded the text string in the SDES item CNAME. ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.10.2 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 174 6.1.1.4 MCVideo Server - MCVideo Client / Pre-arranged Group Call / On-demand / Reception Control State Transitions |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.4.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 and having registered the clients} ensure that { when { the SS-UE1 (MCVideo Client) initiates a pre-arranged group call with automatic commencement mode and implicit transmission control } then { IUT (MCVideo Server) accepts the call from the initiator and establishes the call with all affiliated users of the group and sends transmission granted to the SS-UE1 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { the SS-UE2 (MCVideo client) requests the media reception from the SS-UE1 (MCVideo client) } then { IUT (MCVideo Server) sends transmission control ack and receive media response } } (3) with { IUT (MCVideo Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { the SS-UE2 (MCVideo client) requests end of media reception } then { IUT (MCVideo Server) sends transmission control ack and media reception end response } } (4) with { IUT (MCVideo Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { the SS-UE1 (MCVideo client) requests the end of transmission control} then { IUT (MCVideo Server) sends transmission idle to the SS-UE1 (MCVideo client) and sends transmission idle to the SS-UE2 (MCVideo client) } } (5) with { IUT (MCVideo Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { the SS-UE1 (MCVideo client) requests the transmission control } then { IUT (MCVideo Server) sends transmission granted to the SS-UE1 (MCVideo client) and sends media transmission notification to the SS-UE2 (MCVideo client) } } (6) with { IUT (MCVideo Server) having established pre-arranged group call with automatic commencement mode } ensure that { when { the SS-UE1 (MCVideo client) ends the group call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the SS-UE2 (MCVideo Client) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.4.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 9.2.1.3.1.1, 9.2.1.3.2, 9.2.1.3.3.1, 9.2.1.4.1.1, 9.2.1.4.1.2, 9.2.1.4.2, 9.2.1.4.3, 6.3.2.2.5.2, 6.2.3.1.2, 6.2.3.1.1, and ETSI TS 124 581 [9] (3GPP TS 24.581), clauses 6.3.2.2, 6.3.3, 6.4.2, 6.4.3, 6.4.4, 9.2.1, 6.2.1, 6.2.2, 6.2.5. Unless otherwise stated, these are Rel-15 requirements. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 175 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.1.1] "In the procedures in this clause: 1) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 3) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "prearranged", the participating MCVideo function: … 2) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and shall authorise the calling user; NOTE 2: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 5) shall check if the number of maximum simultaneous MCVideo group calls supported for the MCVideo user as specified in the <MaxSimultaneousCallsN6> element of the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) has been exceeded. If exceeded, the participating MCVideo function shall respond with a SIP 486 (Busy Here) response with the warning text set to "103 maximum simultaneous MCVideo group calls reached" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps; NOTE 3: If the SIP INVITE request contains an emergency indication or an imminent peril indication, the participating MCVideo function can by means beyond the scope of this specification choose to allow for an exception to the limit for the maximum simultaneous MCVideo sessions supported for the MCVideo user. Alternatively, a lower priority session of the MCVideo user could be terminated to allow for the new session. 6) if the user identified by the MCVideo ID is not affiliated to the group identified in the "SIP INVITE request for originating participating MCVideo function" as determined by clause 8.2.2.2.11 and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, shall perform the actions specified in clause 8.2.2.2.12 for implicit affiliation; … 8) shall determine the public service identity of the controlling MCVideo function associated with the group identity in the SIP INVITE request; NOTE 6: The public service identity can identify the controlling MCVideo function in the primary MCVideo system or a partner MCVideo system. NOTE 7: How the participating MCVideo server discovers the public service identity of the controlling MCVideo function associated with the group identity is out of scope of the current release. 9) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3; 10) shall set the Request-URI to the public service identity of the controlling MCVideo function associated with the group identity which was present in the incoming SIP INVITE request; 11) shall not copy the following header fields from the incoming SIP INVITE request to the outgoing SIP INVITE request, if they were present in the incoming SIP INVITE request: a) Answer-Mode header field as specified in IETF RFC 5373 [27]; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 176 b) Priv-Answer-Mode header field as specified in IETF RFC 5373 [27]; 12) shall set the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; 14) if the received SIP INVITE request contains an application/vnd.3gpp.location-info+xml MIME body and if not already copied, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body received in the SIP INVITE request into an application/vnd.3gpp.location-info+xml MIME body included in the outgoing SIP request; 15) if a Resource-Priority header field was included in the received SIP INVITE request, shall include a Resource- Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCVideo client; and NOTE 8: The participating MCVideo function will leave verification of the Resource-Priority header field to the controlling MCVideo function. 16) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. … Upon receipt of a SIP 2xx response in response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) if the received SIP 2xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC-GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 2) shall generate a SIP 200 (OK) response as in clause 6.3.2.1.5.2; 3) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 4) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 5) 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; 6) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 7) if the procedures of clause 8.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 8.2.2.2.13; 8) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 9) shall interact with Media Plane as specified in 3GPP TS 24.581 [5]; and 10) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [23]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request in step 14) the participating MCVideo function: 1) shall generate a SIP response according to 3GPP TS 24.229 [11]; 2) shall include Warning header field(s) that were received in the incoming SIP response; 3) shall forward the SIP response to the MCVideo client according to 3GPP TS 24.229 [11]; and 4) if the implicit affiliation procedures of clause 8.2.2.2.12 were invoked in this procedure, shall perform the procedures of clause 8.2.2.2.14;..." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 177 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.2] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. NOTE 1: This clause covers on-demand session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: … 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; … 6) if the SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC- GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; and 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.3.3.1] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.1.6." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.1.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.1.4.2 or as the result of receiving a SIP 403 (Forbidden) response as described in this clause. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited.; NOTE 1: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 2: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 3) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCVideo function; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 178 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the MCVideo ID of the terminating user; and b) the <mcvideo-calling-group-id> element set to the group identity; NOTE 3: The <mcvideo-calling-user-id> is already included in the MIME body as a result of calling clause 6.3.3.1.2 in step 1). 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; 6) if the in-progress emergency state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.19; b) if the received SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true": i) shall include in the outgoing SIP INVITE request in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; and ii) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcvideo-info+xml MIME body and the application/vnd.3gpp.location- info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false"; and c) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.19; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; and 9) shall send the SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [11]. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 179 Upon receiving a SIP 183 (Session Progress) response containing a Require header field with the option tag "100rel" and containing a P-Answer-State header field with the value "Unconfirmed" in response to the SIP INVITE request the controlling MCVideo function: 1) shall send a SIP PRACK request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; 2) shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 9.2.3.4; and 3) shall increment the local counter of the number of SIP 200 (OK) responses received from invited members, by 1. NOTE 4: The notifications above could be sent prior to the SIP 200 (OK) response being sent to the inviting MCVideo client. These notifications received by MCVideo clients that are group members do not mean that the group session will be successfully established. NOTE 5: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.1.2] "The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the non-controlling MCVideo function serving the group identity of the MCVideo group owned by the partner MCVideo system; 3) shall set the P-Asserted-Identity to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the group identity of the MCVideo group hosted by the non- controlling MCVideo function in the partner MCVideo system; and b) the <mcvideo-calling-group-id> element set to the group identity of the group served by the controlling MCVideo function; 5) shall include the Recv-Info header field set to g.3gpp.mcvideo-transmission-request; 6) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 180 8) shall send the SIP INVITE request towards the partner MCVideo system in accordance with 3GPP TS 24.229 [11]. … Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and NOTE 3: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2. 2) if at least one of the invited MCVideo clients has subscribed to the conference package, shall subscribe to the conference event package in the non-controlling MCVideo function as specified in clause 9.2.3.4.3." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.2] "In the procedures in this clause: 1) MCVideo ID in an incoming SIP INVITE request refers to the MCVideo ID of the originating user from the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-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 <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 3) MCVideo ID in an outgoing SIP INVITE request refers to the MCVideo ID of the called user in the <mcvideo- request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) indication of required group members in a SIP 183 (Session Progress) response refers to the <required> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to "true" in a SIP 183 (Session Progress) sent by the non-controlling MCVideo function of an MCVideo group; 5) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 6) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for controlling MCVideo function of an MCVideo group", the controlling MCVideo function: … 4) if received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; 5) 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 clause 6.3.5.2; ... 7) shall perform the actions as described in clause 6.3.3.2.2; 8) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero; 9) shall determine if an MCVideo group call for the group identity is already ongoing by determining if an MCVideo session identity has already been allocated for the group call and the MCVideo session is active; … ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 181 13) if the MCVideo group call is not ongoing then: … c) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined as determined in step 13) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; d) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; e) shall create a prearranged group session and allocate an MCVideo session identity for the prearranged group call, and shall handle timer TNG3 (group call timer) as specified in clause 6.3.3.5; f) if the group identity in the "SIP INVITE request for controlling MCVideo function of an MCVideo group" is a TGI: i) shall for each of the constituent MCVideo groups homed on the primary MCVideo system: A) if the controlling MCVideo function does not own the MCVideo group identified by the MCVideo group ID, then generate a SIP INVITE request towards the MCVideo server that owns the MCVideo group identity by following the procedures in clause 9.2.1.4.1.2; and NOTE 2: The MCVideo server that the SIP INVITE request is sent to acts as a non-controlling MCVideo function; B) if the controlling MCVideo function owns the MCVideo group identified by the MCVideo group ID then: I) determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; II) invite each group member determined in step A) above, to the group session, as specified in clause 9.2.1.4.1.1; and III) interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and ii) shall for each of the constituent MCVideo groups homed on the partner MCVideo system generate a SIP INVITE request for the MCVideo group identity homed on the partner MCVideo system as specified in clause 9.2.1.4.1.2; and g) if the group identity in the SIP INVITE request for controlling MCVideo function of an MCVideo group is an MCVideo group ID: i) shall determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; ii) if necessary, shall start timer TNG1 (acknowledged call setup timer) according to the conditions stated in clause 6.3.3.3; iii) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": A) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; and C) if the in-progress emergency state of the group is set to a value of "false": I) shall set the value of the in-progress emergency state of the group to "true"; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 182 II) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; iv) if the in-progress emergency state of the group is set to a value of "false" and if the received SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function shall: A) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and B) if the in-progress imminent peril state of the group is set to a value of "false", shall set the in- progress imminent peril state of the group to a value of "true"; v) shall invite each group member determined in step 13)g)i) above, to the group session, as specified in clause 9.2.1.4.1.1; and vi) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and 14) if the MCVideo group call is ongoing then: … c) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; … e) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined in step 14) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; f) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": i) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; iii) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; and C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.6; iv) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and v) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 183 g) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function: i) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and ii) if the in-progress imminent peril state of the group is set to a value of "false": A) shall set the in-progress imminent peril state of the group to a value of "true"; B) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.15; and C) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and iii) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; h) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.4.2; i) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; j) shall include in the SIP 200 (OK) response with the warning text set to "123 MCVideo session already exists" as specified in clause 4.4; k) if the received SIP re-INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; l) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 4: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. m) shall interact with media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 5: Resulting media plane processing is completed before the next step is performed. n) shall send the SIP 200 (OK) response towards the inviting MCVideo client or inviting non-controlling MCVideo function according to 3GPP TS 24.229 [11]; o) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; NOTE 6: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. p) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 184 q) Upon receiving a SIP ACK to the above SIP 200 (OK) response and the SIP 200 (OK) response contained a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall follow the procedures in clause 6.3.3.1.18; and r) shall not continue with the rest of the clause. Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 9.2.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [30], the timer TNG1 (acknowledged call setup timer) is not running, the controlling MCVideo function supports media buffering and the SIP final response is not yet sent to the inviting MCVideo client: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; … 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) shall include a P-Answer-State header field with the value "Unconfirmed"; 5) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 7: Resulting user plane processing is completed before the next step is performed. 8) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; 9) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 8: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 10) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response for a SIP INVITE request as specified in clause 9.2.1.4.1.2 containing an indication of required group members, the timer TNG1 (acknowledged call setup timer) is running and all SIP 200 (OK) responses have been received to all SIP INVITE requests sent to MCVideo clients specified in clause 9.2.1.4.1.1, then the controlling MCVideo function shall wait until the SIP 200 (OK) response has been received to the SIP INVITE request specified in clause 9.2.1.4.1.2 before generating a SIP 200 (OK) response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group". Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1 that was sent to an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24]; and 1) if the MCVideo ID in the SIP 200 (OK) response matches to the MCVideo ID in the corresponding SIP INVITE request; 2) there are no outstanding SIP 200 (OK) responses to SIP INVITE requests which were sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24]; and 3) there is no outstanding SIP 200 (OK) response to a SIP INVITE request sent in clause 9.2.1.4.1.2 where the SIP 183 (Session Progress) response contained an indication of required group members; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 185 the controlling MCVideo function: 1) shall stop timer TNG1 (acknowledged call setup timer) as described in clause 6.3.3.3; 2) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; … 4) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 5) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 9: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 7) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 10: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 8) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon: 1) receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1; 2) the timer TNG1 (acknowledged call setup timer) is not running; 3) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; 4) the controlling MCVideo function supports media buffering; and 5) the SIP final response has not yet been sent to the inviting MCVideo client; the controlling MCVideo function according to local policy: 1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2; … 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 5) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 11: Resulting media plane processing is completed before the next step is performed. 7) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 186 8) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 12: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 9) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon expiry of timer TNG1 (acknowledged call setup timer), if there are outstanding SIP 200 (OK) responses to SIP INVITE requests sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the procedures specified in clause 6.3.3.3. … Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.1.4.3] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.3.2.2.5.2] "When receiving a "SIP INVITE request for terminating participating MCVideo function" for an on-demand session that requires automatic commencement mode the participating MCVideo function: 1) if: a) the incoming SIP INVITE request contained a Priv-Answer-Mode header field set to the value of "Auto"; b) no Answer-Mode header field or Priv-Answer-Mode header field were received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto- answer"; or c) the incoming SIP INVITE request contained an Answer-Mode header field set to "Auto" and the Answer- Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; then: a) shall generate a SIP 183 (Session Progress) response to the "SIP INVITE request for terminating participating MCVideo function" as specified in clause 6.3.2.2.4.1; and NOTE: The SIP 183 (session Progress) response can be sent reliably or unreliably depending on the content of the received SIP INVITE request. Regardless of if the SIP 183 (Session Progress) response is sent reliably or unreliably, SDP is not included in the SIP 183 (Session Progress) response. b) shall set the P-Answer-State header field to "Unconfirmed" in the SIP 183 (Session Progress) response; 2) shall copy the public user identity contained in the Request-URI of the incoming "SIP INVITE request for terminating participating MCVideo function" to the P-Asserted-Identity header field of the SIP 183 (Session Progress) response; 3) shall generate a SIP INVITE request as specified in clause 6.3.2.2.3; 4) shall set the Request-URI to the public user identity associated to the MCVideo ID of the MCVideo user to be invited; 5) shall perform the procedures specified in clause 6.3.2.2.9 to include any MIME bodies in the received SIP INVITE request, into the outgoing SIP INVITE request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 187 6) shall copy the contents of the P-Asserted-Identity header field of the incoming "SIP INVITE request for terminating participating MCVideo function" to the P-Asserted-Identity header field of the outgoing SIP INVITE request; 7) if the Priv-Answer-Mode header field is present in the incoming SIP INVITE request with a value of "Auto", shall include a Priv-Answer-Mode header field with the value "Auto" in the outgoing SIP INVITE request. Otherwise, if the Answer-Mode header field is present in the incoming SIP INVITE request, the participating MCVideo function shall include an Answer-Mode header field with the value "Auto" in the outgoing SIP INVITE request; 8) if no Answer-Mode header field or Priv-Answer-Mode header field were received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto-answer", shall set the Answer-Mode header field to "Auto" in the outgoing SIP INVITE request; 9) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for terminating participating MCVideo function" as specified in clause 6.3.2.2.1; 10) if the received SIP INVITE request contains a Resource-Priority header field, shall include a Resource- Priority header field with the contents set as in the received Resource-Priority header field; and 11) shall send the SIP INVITE request towards the MCVideo client according to 3GPP TS 24.229 [11]. If the SIP 183 (Session Progress) response was sent reliably, then upon receiving a SIP PRACK request, the participating MCVideo function shall generate a SIP 200 (OK) response to the SIP PRACK request and forward the SIP 200 (OK) response, according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the above SIP INVITE request sent to the MCVideo client, the participating MCVideo function: 1) if the SIP 183 (Session Progress) was sent unreliably, shall send the SIP 200 (OK) response immediately; and 2) if the SIP 183 (Session Progress) was sent reliably and, a) if the SIP PRACK request to the SIP 183 (Session Progress) response has been received by the participating MCVideo function and the SIP 200 (OK) response to the SIP PRACK request has been sent, shall send the SIP 200 (OK) response immediately; b) if the SIP PRACK request to the SIP 183 (Session Progress) response has not yet been received, then upon receipt of the SIP PRACK request, the participating MCVideo function shall generate a SIP 200 (OK) response to the SIP PRACK request and forward the SIP 200 (OK) response, according to 3GPP TS 24.229 [11], before sending the SIP 200 (OK) response to the "SIP INVITE request for terminating participating MCVideo function". When the participating MCVideo function sends the SIP 200 (OK) response to the "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2; 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 clause 6.3.2.2.2.1; 3) shall copy the P-Asserted-Identity header field from the incoming SIP 200 (OK) response to the outgoing SIP 200 (OK) response; 4) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 5) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [11]. The participating MCVideo function shall forward any other SIP response that does not contain SDP along the signalling path to the originating network according to 3GPP TS 24.229 [11]." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 188 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.2.3.1.2] "When performing the automatic commencement mode procedures, the MCVideo client shall follow the procedures in clause 6.2.3.1.1 with the following clarification: - The MCVideo client may include a P-Answer-State header field with the value "Confirmed" as specified in IETF RFC 4964 [30] in the SIP 200 (OK) response. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.2.3.1.1] When performing the automatic commencement mode procedures, the MCVideo client: 1) shall accept the SIP INVITE request and generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [11]; 2) shall include the option tag "timer" in a Require header field of the SIP 200 (OK) response; 3) shall include the g.3gpp.mcvideo media feature tag in the Contact header field of the SIP 200 (OK) response; 4) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp- service.ims.icsi.mcvideo" in the Contact header field of the SIP 200 (OK) response; 5) shall include the Session-Expires header field in the SIP 200 (OK) response and start the SIP session timer according to IETF RFC 4028 [23]. The "refresher" parameter in the Session-Expires header field shall be set to "uas"; 6) shall, if the incoming SIP INVITE request contains a Replaces header field, include in the SDP answer in the SIP 200 (OK) response to the SDP offer the parameters used for the pre-established session identified by the contents of the Replaces header field; 7) shall, if the incoming SIP INVITE request does not contain a Replaces header field, include an SDP answer in the SIP 200 (OK) response to the SDP offer in the incoming SIP INVITE request according to 3GPP TS 24.229 [11] with the clarifications given in clause 6.2.2; NOTE: In the case of a new emergency call where the terminating client is using a pre-established session, the SIP INVITE request containing a Replaces header is used to replace the pre-established session. 8) shall send the SIP 200 (OK) response towards the MCVideo server according to rules and procedures of 3GPP TS 24.229 [11]; 9) shall, if the incoming SIP INVITE request contains a Replaces header field, release the pre-established session identified by the contents of the Replaces header field; and 10) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. When NAT traversal is supported by the MCVideo client and when the MCVideo client is behind a NAT, generation of SIP responses is done as specified in this clause and as specified in IETF RFC 5626 [35]." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.3.2.2] "When an MCVideo call is established a new instance of the transmission control server state machine for 'general transmission control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' is added. When an MCVideo call is established a new instance of the transmission control server state machine for 'general reception control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic reception control operation towards the transmission participant' is added. If the optional "mc_queueing" feature is supported and has been negotiated as specified in clause 14, the transmission control server could queue the implicit transmission control request for the media-transmission control entity. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 189 The original initial SIP INVITE request or SIP REFER request to establish an MCVideo chat group call or to rejoin an ongoing MCVideo call is not handled as an implicit transmission control request message by the transmission control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request. The permission to send media to the inviting MCVideo client due to implicit transmission control request is applicable to both confirmed indication and unconfirmed indication. When the first unconfirmed indication is received from the invited participating MCVideo function (see 3GPP TS 24.281 [2]) the transmission control server optionally can give an early indication to send RTP media packets, to the inviting MCVideo client. If an early indication to send RTP media packets is given to the inviting MCVideo client, the transmission participant is granted the permission to send media and the MCVideo server buffers RTP media packets received from the MCVideo client at least until the first invited MCVideo client accepts the invitation or until the RTP media packet buffer exceeds it maximum limit to store RTP media packets. If the MCVideo server does not support or does not allow media buffering then when an early indication to send RTP media packets is not given to the inviting MCVideo client, the transmission participant is granted the permission to send media when the first invited MCVideo client accepts the media. Before the transmission control server sends the first transmission control message in the MCVideo call, the transmission control server has to assign itself a SSRC identifier to be included in media transmission control messages and quality feedback messages if the MCVideo server is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3]. The transmission participant and the transmission control server can negotiate the maximum priority level that the transmission participant is permitted to request. The transmission control server can pre-empt the current sender based on the negotiated maximum priority level that the transmission participant is permitted to request and the priority level included in the Transmission Media Request message. NOTE: The maximum priority level that a transmission participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the controlling MCVideo function from the group management server as described in 3GPP TS 24.481 [12] and service configuration data retrieved by the controlling MCVideo function from the configuration management server as described in 3GPP TS 24.484 [13]. The transmission participant and the transmission control server can negotiate queueing of Transmission requests using the "mc_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the transmission control server queues the transmission control request if a Transmission Media Request message is received when another transmission participant has the transmission and the priority of the current speaker is the same or higher." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 190 Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 191 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 9.2.1] "The transmission control messages are coded as described in clause 9.1.2 where the transmission control message is part of the application-dependent data. For the transmission control protocol the ASCII name string is: MCVx (Mission Critical Video x) with x=0, 1 or 2 as specified in clause 9.1.2. A list of transmission control messages can be found in clause 9.2.2.1. The transmission control specific fields are specified in clause 9.2.3." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.2.1] "Based on the negotiations during the call establishment specified in 3GPP TS 24.281 [2], a new instance of the 'Transmission participant state transition diagram for basic transmission control operation', as specified in clause 6.2.4 and a new instance of the 'Transmission participant state transition diagram for basic reception control operation' as specified in clause 6.2.5, shall be created for this call. The SIP INVITE request sent by the application and signalling plane: 1. shall be regarded an implicit Transmission request when an implicit Transmission request is negotiated; and 2. shall not be regarded as an implicit Transmission request in case of a rejoin to an already on-going group call. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 192 NOTE: The transmission participant can negotiate the use of prioritization of the Transmission Media Request message. In that case, the transmission participant can request permission to send media at a priority level that is either the same as or lower than the highest priority that was permitted to the participant in the MCVideo call initialization. If a transmission participant is authorized for pre-emptive priority in the MCVideo call it is good practise to always request permission to send RTP media packets at a priority level that is lower than pre-emptive priority unless the user explicitly requests to pre-empt the current RTP media packets sender." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.2.2] "The MCVideo call release (whether it is initiated by the transmission participant or transmission control server) is a two-step procedure. Step 1 The transmission participant stops sending transmission control and reception control messages and the MCVideo client stops sending and receiving RTP media packets. Step 2 When the application and signalling plane has determined that the MCVideo call is released, the corresponding instance of the 'Transmission participant state transition diagram for basic transmission control operation' as specified in clause 6.2.4 and the corresponding instance of the 'Transmission participant state transition diagram for basic reception control operation' as specified in clause 6.2.5 are terminated and the transmission participant releases all the used resources. The user plane can initiate the release step 1, but the application and signalling plane always initiates the release step 2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.2.5] "The transmission participant shall behave according to the state diagrams and the state transitions specified in this clause. Figure 6.2.5.1-1 shows the state diagram for 'Transmission participant state transition diagram for general reception control operation'. …" |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.1.4.3 Test description | 6.1.1.4.3.1 Pre-test conditions System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 193 Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) are affiliated to the Prearranged group. - The IUT (MCVideo Server) is the controlling server of the Prearranged group. 6.1.1.4.3.2 Test procedure sequence Table 6.1.1.4.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the SS-UE1 (MCVideo Client) request the establishment of a pre-arranged group call to SS-UE2 (MCVideo Client) with automatic commencement mode and implicit transmission request. - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to establish a pre-arranged group call with automatic commencement mode and implicit transmission control request according to option b.ii of note in Annex A, Table A.3.1.3-1? - - 1 P 3 Make the SS-UE2 (MCVideo Client) request media reception from SS-UE1 (MCVideo Client). - - - - 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Media Reception Request and Response' as described in Annex A, Table A.3.9.3-1? - - 2 P 5 Make the SS-UE2 (MCVideo Client) request end of media reception. - - - - 6 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Media Reception End Request and Response' as described in Annex A, Table A.3.10.3-1? - - 3 P 7 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 8 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 4 P 9 Make the SS-UE1 (MCVideo Client) request transmission. - - - - 10 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1? - - 5 P 11 Make the SS-UE2 (MCVideo Client) request media reception from SS-UE1 (MCVideo Client). - - - - 12 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Media Reception Request and Response' as described in Annex A, Table A.3.9.3-1? - - 2 P 13 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 194 St Procedure Message Sequence TP Verdict U - S Message 14 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1 while the SS-UE2 (MCVideo Client) is still permitted to receive media from SS-UE1 (MCVideo Client)? - - 4 P 15 Make the SS-UE1 (MCVideo Client) release the call. - - - - 16 Check: Does the MCVideo server correctly perform procedure 'MCX E2E call release' as described in Annex A, A.2.19.3-1? - - 6 P 6.1.1.4.3.3 Specific message contents All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.1.1.4.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.1.1.4.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.1.4.3.3-2: SIP INVITE from the IUT (MCVideo Server) (Step 2, Table 6.1.1.4.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.1.4.3.3-3: SIP 200 (OK) from the SS-UE2 (Step 2, Table 6.1.1.4.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.1.4.3.3-4: SIP 200 (OK) from the IUT (MCVideo Server) (Step 2, Table 6.1.1.4.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 195 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.2 Chat Group Calls | 6.1.2.1 MCVideo Server - MCVideo Client / Chat Group Call / On-demand / Join Chat Group Session / Upgrade to Emergency / Cancel Emergency / Upgrade to Imminent Peril / Cancel Imminent Peril |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.2.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCVideo client ) requests session establishment of chat group call without implicit transmission control with sending SIP INVITE message } then { IUT (MCVideo Server) responds with optional SIP 100 Trying and mandatory 200 (OK) message } } (2) with { IUT (MCVideo Server) having established an ongoing On-demand Chat Group Call } ensure that { when { the SS-UE2 (MCVideo client ) requests session establishment of chat group call without implicit transmission control with sending SIP INVITE message } then { IUT (MCVideo Server) responds with optional SIP 100 Trying and mandatory 200 (OK) message } } (3) with { IUT (MCVideo Server) having established an ongoing On-demand Chat Group Call } ensure that { when { the SS-UE1 (MCVideo Client) upgrades the call to emergency group call with implicit transmission control } then { IUT (MCVideo Server) accepts the upgrade from the initiator and updates the call with all affiliated users of the group and sends transmission granted to the SS-UE1 (MCVideo client)} } (4) with { IUT (MCVideo Server) having established an ongoing Emergency Chat Group Call } ensure that { when { the SS-UE1 (MCVideo Client) requests the end of transmission control } then { IUT (MCVideo Server) sends transmission idle to the SS-UE1 (MCVideo Client) and sends transmission idle to the SS-UE2 (MCVideo Client) } } (5) with { IUT (MCVideo Server) having established an ongoing On-demand Chat Group Call } ensure that { when { the SS-UE1 (MCVideo Client) downgrades the call to a normal group call } then { IUT (MCVideo Server) accepts the downgrade from the initiator and updates the call with all affiliated users of the group without implicit transmission request } } (6) with { IUT (MCVideo Server) having established an ongoing On-demand Chat Group Call } ensure that { when { the SS-UE1 (MCVideo Client) upgrades the call to imminent peril group call with implicit transmission control } then { IUT (MCVideo Server) accepts the call from the initiator and establishes the call with all affiliated users of the group and sends transmission granted to the SS-UE1 (MCVideo Client) } } (7) with { IUT (MCVideo Server) having established an ongoing On-demand Pre-arranged Chat Group Call } ensure that { when { the SS-UE1 (MCVideo Client) ends the chat group call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the other participants } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 196 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.2.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 9.2.2.3.1.1, 9.2.2.3.1.2, 9.2.2.3.1.3, 9.2.2.3.1.4, 9.2.2.4.1.1, 9.2.2.4.1.2, 9.2.2.4.1.3, 9.2.2.4.2, 9.2.2.4.3.2. Unless otherwise stated, these are Rel-14 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.2.3.1.1] "In the procedures in this clause: 1) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; 3) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for originating participating MCVideo function" for a group identity identifying a chat MCVideo group containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "chat", the participating MCVideo function: … 2) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and authorise the calling user; NOTE 2: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … NOTE 3: If the SIP INVITE request contains an emergency indication set to a value of "true" or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCVideo function can according to local policy choose to allow for an exception to the limit for the maximum simultaneous MCVideo sessions supported for the MCVideo user. 6) if the user identified by the MCVideo ID is not affiliated to the group identified in the "SIP INVITE request for originating participating MCVideo function" as determined by clause 8.2.2.2.11, shall perform the actions specified in clause 8.2.2.2.12 for implicit affiliation; … 8) shall determine the public service identity of the controlling MCVideo function associated with the group identity in the SIP INVITE request; NOTE 6: The public service identity can identify the controlling MCVideo function in the primary MCVideo system or a partner MCVideo system. NOTE 7: How the participating MCVideo server discovers the public service identity of the controlling MCVideo function associated with the group identity is out of scope of the current document. 9) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3; 10) shall set the Request-URI to the public service identity of the controlling MCVideo function associated with the group identity present in the incoming SIP INVITE request; 11) shall include the MCVideo ID of the calling user in <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of 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 as specified in clause 6.3.2.1.1.1; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 197 13) if the received SIP INVITE request contains an application/vnd.3gpp.location-info+xml MIME body as specified in Annex F.3; and a) if not already included, shall include a Content-Type header field set to "application/vnd.3gpp.location- info+xml"; and b) if not already copied, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body received in the SIP INVITE request into an application/vnd.3gpp.location-info+xml MIME body included in the outgoing SIP request; NOTE 8: Note that the application/vnd.3gpp.mcvideo-info+xml MIME body will already have been copied into the outgoing SIP INVITE request by clause 6.3.2.1.3. 14) if a Resource-Priority header field was included in the received SIP INVITE request, shall include a Resource- Priority header field according to rules and procedures of IETF RFC 4412 [33] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCVideo client; and NOTE 9: The participating MCVideo function will leave verification of the Resource-Priority header field to the controlling MCVideo function. 15) shall forward the SIP INVITE request according to 3GPP TS 24.229 [11]. … Upon receipt of a SIP 2xx response to the above SIP INVITE request in step 14) the participating MCVideo function: 1) if the SIP 2xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC- GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 2) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2; 3) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 4) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 5) 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; 6) if the procedures of clause 8.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 8.2.2.2.13; 7) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; and 8) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. …" [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.2.3.1.2] "This clause covers on-demand session. Upon receipt of a SIP re-INVITE request for a served MCVideo client of a chat MCVideo group, the participating MCVideo function: … 3) shall generate an outgoing SIP re-INVITE request as specified in clause 6.3.2.1.9; 4) shall, if the SIP re-INVITE request was received within an on-demand session, include in the SIP re-INVITE request an SDP offer based on the SDP offer in the received SIP re-INVITE request as specified in clause 6.3.2.1.1.1; 5) if the received SIP re-INVITE request contains a Resource-Priority header field, shall include a Resource- Priority header field with the contents set as in the received Resource-Priority header field; 6) if the received SIP re-INVITE request contains a Resource-Priority header field, shall include a Resource- Priority header field with the contents set as in the received Resource-Priority header field; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 198 NOTE 3: The controlling MCVideo function will determine the validity of the Resource-Priority header field. 7) shall forward the SIP re-INVITE request according to 3GPP TS 24.229 [11]. Upon receipt of a SIP 2xx response to the above SIP re-INVITE request in step 7) the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2; 2) if the SIP 200 (OK) response is to be sent within an on-demand session, shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 3) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; and 4) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; …" [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.2.3.1.3] "This clause covers on-demand session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", for a terminating MCVideo client of a chat MCVideo group, the participating MCVideo function: … 3) shall generate a SIP INVITE request as specified in clause 6.3.2.2.3; 4) shall set the Request-URI to the public user identity associated with the MCVideo ID of the MCVideo user to be invited based on the contents of the Request-URI of the received "SIP INVITE request for terminating participating MCVideo function"; 5) shall copy the contents of the P-Asserted-Identity header field of the incoming "SIP INVITE request for terminating participating MCVideo function" to the P-Asserted-Identity header field of the outgoing SIP INVITE request; 6) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for terminating participating MCVideo function" as specified in clause 6.3.2.2.1; 7) if the received SIP INVITE request contains a Resource-Priority header field, shall include a Resource- Priority header field with the contents set as in the received Resource-Priority header field; 8) shall perform the procedures specified in clause 6.3.2.2.9 to include any MIME bodies in the received SIP INVITE request; and 9) shall send the SIP INVITE request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the above SIP INVITE request sent to the MCVideo client, the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2; 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 clause 6.3.2.2.2.1; 3) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 4) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [11]." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 199 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.2.3.1.4] "This clause covers both on-demand session. Upon receipt of a SIP re-INVITE request for a terminating MCVideo client of a chat MCVideo group, the participating MCVideo function: 1) shall check if a Resource-Priority header field is included in the incoming SIP re-INVITE request and may perform further actions outside the scope of this specification to act upon an included Resource-Priority header field as specified in 3GPP TS 24.229 [11]; 2) shall generate an outgoing SIP re-INVITE request as specified in clause 6.3.2.2.10; 3) shall include in the SIP re-INVITE request an SDP offer based on the SDP offer in the received SIP re-INVITE request as specified in clause 6.3.2.2.1; and 4) shall send the SIP re-INVITE request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the above SIP re-INVITE request sent to the MCVideo client, the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2; 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 clause 6.3.2.2.2.1; and 3) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.2.4.1.1] "In the procedures in this clause: 1) MCVideo ID in an incoming SIP INVITE request refers to the MCVideo ID of the originating user from the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-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 <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 3) MCVideo ID in an outgoing SIP INVITE request refers to the MCVideo ID of the called user in the <mcvideo- request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 5) alert indication in an incoming SIP INVITE request refers to the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for controlling MCVideo function of an MCVideo group" containing a group identity identifying a chat MCVideo group, the controlling MCVideo function: … 3) if received SIP INVITE request includes an application/vnd.3gpp.mcvideoinfo+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; 4) 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 clause 6.3.5.2 and continue with the rest of the steps if the checks in clause 6.3.5.2 succeed; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 200 5) if the MCVideo user identified by the MCVideo ID in the SIP INVITE request is not affiliated with the MCVideo group identified by the group identity in the SIP INVITE request as determined by the procedures of clause 6.3.6: a) shall check if the MCVideo user is eligible to be implicitly affiliated with the MCVideo chat group as determined by clause 8.2.2.3.6; and … 10) shall create a chat group session and allocate an MCVideo session identity for the chat group session if the MCVideo chat group session identity does not already exist, and may handle timer TNG3 (group call timer) as specified in clause 6.3.3.5; … 12) if the received SIP INVITE request was determined to be eligible for implicit affiliation in step 5) and if clause 8.2.2.3.7 was not previously invoked in the present clause, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; 13) if the SIP INVITE request contains an emergency indication set to a value of "true" or the in-progress emergency state of the group to "true" the controlling MCVideo function shall: a) validate that the SIP INVITE request includes a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.19, and if not: i) perform the actions specified in clause 6.3.3.1.8; ii) send the SIP UPDATE request generated in clause 6.3.3.1.8 towards the initiator of the SIP INVITE request according to 3GPP TS 24.229 [11]; and iii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.1.8, proceed with the rest of the steps. NOTE 3: Verify that the Resource-Priority header is included and properly populated for both ongoing and newly- entered in-progress emergency states of the specified group. b) if the in-progress emergency state of the group is set to a value of "true" and this MCVideo user is indicating a new emergency indication: i) for each of the other affiliated members of the group generate a SIP MESSAGE request notification of the MCVideo user's emergency indication as specified in clause 6.3.3.1.11 with the following clarifications: A) set the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, perform the procedures specified in clause 6.3.3.1.12; and C) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; ii) cache the information that this MCVideo user has initiated an MCVideo emergency call; and iii) if the SIP INVITE request contains an authorised request for an MCVideo emergency alert as determined in step i) B) above, cache the information that this MCVideo user has initiated an MCVideo emergency alert; and c) if the in-progress emergency state of the group is set to a value of "false": i) shall set the value of the in-progress emergency state of the group to "true"; ii) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 201 iii) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other affiliated and joined participants of the chat MCVideo group as specified in clause 6.3.3.1.6; iv) shall generate SIP INVITE requests for the MCVideo emergency group call to the affiliated but not joined members of the chat MCVideo group as specified in clause 6.3.3.1.7; A) for each affiliated but not joined member shall send the SIP INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and B) upon receiving a SIP 200 (OK) response to the SIP INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; v) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; and vi) if the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body is set to "true" and is an authorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; and vii) if the in-progress imminent peril state of the group is set to a value of "true", shall set it to a value of "false"; 14) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true" or the in-progress imminent peril state of the group is set to "true", the controlling MCVideo function shall: a) validate that the SIP INVITE request includes a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.19, and if not: i) perform the actions specified in clause 6.3.3.1.8; ii) send the SIP UPDATE request generated in clause 6.3.3.1.8 towards the initiator of the SIP INVITE request according to 3GPP TS 24.229 [11]; and iii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.1.8 proceed with the rest of the steps. NOTE 4: Verify that the Resource-Priority header is included and properly populated for both ongoing and newly- entered in-progress imminent peril states of the specified group. b) if the in-progress imminent peril state of the group is set to a value of "true" and this MCVideo user is indicating a new imminent peril indication: i) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11 with the following clarifications; A) set the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and ii) cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and c) if the in-progress imminent peril state of the group is set to a value of "false": i) shall set the value of the in-progress imminent peril state of the group to "true"; ii) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other affiliated and joined participants of the chat MCVideo group as specified in clause 6.3.3.1.15; iii) shall generate SIP INVITE requests for the MCVideo imminent peril call to the affiliated but not joined members of the chat MCVideo group as specified in clause 6.3.3.1.7; A) for each affiliated but not joined member shall send the SIP INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 202 B) Upon receiving a SIP 200 (OK) response to the SIP INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and iv) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; 15) shall accept the SIP request and generate a SIP 200 (OK) response to the SIP INVITE request according to 3GPP TS 24.229 [11]; 16) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [11] with the clarifications specified in clause 6.3.3.2.1 unless the procedures of clause 6.3.3.1.8 were performed in step 13)a) or step 14)a) above; 17) should include the Session-Expires header field and start supervising the SIP session according to IETF RFC 4028 [23]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 18) shall include the "timer" option tag in a Require header field; 19) shall include the following in a Contact header field: a) the g.3gpp.mcvideo media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; c) the MCVideo session identity; and d) the media feature tag isfocus; 20) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [32]; … 23) shall interact with media plane as specified in 3GPP TS 24.581 [5]; 24) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; and 25) if the chat group session was already ongoing and if at least one of the participants has subscribed to the conference event package, shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 9.2.3.4.2. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.2.4.1.2] "In the procedures in this clause: 1) emergency indication in an incoming SIP re-INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP re-INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a SIP re-INVITE request for an MCVideo session identity identifying a chat MCVideo group session, the controlling MCVideo function: ,,, 2) if the received SIP re-INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; … ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 203 4) if the SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true" and is an authorised request to initiate an MCVideo emergency group call as determined by clause 6.3.3.1.13.2, the controlling MCVideo function shall: a) validate that the SIP re-INVITE request includes a Resource-Priority header field is populated correctly for an MCVideo emergency group call as specified in clause 6.3.3.1.19, and if not: i) shall perform the actions specified in clause 6.3.3.1.8; and ii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.18 shall proceed with the rest of the steps. NOTE 2: Verify that the Resource-Priority header is included and properly populated for both ongoing and newly- entered in-progress emergency states of the specified group. b) if the in-progress emergency state of the group is set to a value of "true" and this MCVideo user is indicating a new emergency indication: i) shall cache the MCVideo ID of the MCVideo user that has initiated an MCVideo emergency call; ii) if the SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "true" and is an authorised request for an MCVideo emergency alert as determined by clause 6.3.3.1.13.1, shall cache the MCVideo ID of the MCVideo user that has initiated an MCVideo emergency alert; and iii) for each of the other affiliated members of the group, generate a SIP MESSAGE request notification of the MCVideo user's emergency indication as specified in clause 6.3.3.1.11 with the following clarifications: A) set the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; B) if the received SIP re-INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, perform the procedures specified in clause 6.3.3.1.12; and C) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and c) if the in-progress emergency state of the group is set to a value of "false": i) shall set the value of the in-progress emergency state of the group to "true"; ii) shall cache the MCVideo ID of the MCVideo user that has initiated an MCVideo emergency call; iii) if the SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "true" and this is an authorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall cache the MCVideo ID of the MCVideo user that has initiated an MCVideo emergency alert; iv) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; v) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other affiliated and joined participants of the chat MCVideo group as specified in clause 6.3.3.1.6. The MCVideo controlling function: A) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and B) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 204 vi) shall generate SIP INVITE requests for the MCVideo emergency group call to the affiliated but not joined members of the chat MCVideo group as specified in clause 6.3.3.1.7. The controlling MCVideo function: A) for each affiliated but not joined member shall send the SIP INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and B) Upon receiving a SIP 200 (OK) response to the SIP INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and vii) if the in-progress imminent peril state of the group is set to a value of "true", shall set it to a value of "false"; … 6) if the SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is determined to be an authorised request for an MCVideo emergency call cancellation as specified in clause 6.3.3.1.13.4 and the in-progress emergency state of the group to is set to a value of "true" the controlling MCVideo function shall: a) validate that the SIP re-INVITE request includes a Resource-Priority header field is populated correctly for a normal priority MCVideo group call as specified in clause 6.3.3.1.19, and if not: i) shall perform the actions specified in clause 6.3.3.1.8; and ii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.1.8 shall proceed with the rest of the steps; NOTE 3: Verify that the Resource-Priority header is included and properly populated for an in-progress emergency state cancellation of the specified group. b) shall set the in-progress emergency group state of the group to a value of "false"; c) shall clear the cache of the MCVideo ID of the MCVideo user identified by the <originated-by> element as having an outstanding MCVideo emergency group call; d) if an <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body is included and set to "false" and is determined to be an authorised request for an MCVideo emergency alert cancellation as specified in clause 6.3.3.1.13.3 and there is an outstanding MCVideo emergency alert for this MCVideo user shall: i) if the received SIP re-INVITE request contains an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, clear the cache of the MCVideo ID of the MCVideo user identified by the <originated-by> element as having an outstanding MCVideo emergency alert; and ii) if the received SIP re-INVITE request does not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, clear the cache of the MCVideo ID of the sender of the SIP re-INVITE request as having an outstanding MCVideo emergency alert; e) shall generate SIP re-INVITE requests to the other affiliated and joined members of the MCVideo group as specified in clause 6.3.3.1.6. The MCVideo controlling function: i) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and ii) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and NOTE 4: Clause 6.3.3.1.5 will inform the affiliated and joined members of the cancellation of the MCVideo group's in-progress emergency state and the cancellation of the MCVideo emergency alert if applicable. f) for each of the affiliated but not joined members of the group shall: i) generate a SIP MESSAGE request notification of the cancellation of the MCVideo user's emergency call as specified in clause 6.3.3.1.11; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 205 ii) set the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; iii) if indicated above in step d), set the <alert-ind> element of the application/vnd.3gpp.mcvideo- info+xml MIME body to a value of "false"; and iv) send the SIP MESSAGE request according to 3GPP TS 24.229 [11]; 7) if a Resource-Priority header field is included in the SIP re-INVITE request: … b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the received SIP re-INVITE request does not contain an authorised request for an MCVideo imminent peril call as determined by the procedures of clause 6.3.3.1.13.5 and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP re-INVITE request with a SIP 403 (Forbidden) response and skip the remaining steps; 8) if the received SIP re-INVITE request contains an imminent peril indication, shall perform the procedures specified in clause 9.2.2.4.1.3 and skip the rest of the steps; 9) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [11] with the clarifications specified in clause 6.3.3.2.1 unless the procedures of clause 6.3.3.1.8 were performed in step 6) a) i) above; 10) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [32]; … 13) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true", this is an authorised request for an MCVideo imminent peril group call and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 5: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. 14) shall interact with media plane as specified in 3GPP TS 24.581 [5]; and 15) shall send the SIP 200 (OK) response towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.2.4.1.3] "In the procedures in this clause: 1) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 206 When the controlling function receives a SIP re-INVITE request with and imminent peril indication, the controlling function: … 2) if the in-progress emergency group state of the group is set to a value of "false" and if the SIP re-INVITE request contains an imminent peril indication set to a value of "true" or the in-progress imminent peril state of the group to "true", the controlling MCVideo function shall: a) validate that the SIP re-INVITE request includes a Resource-Priority header field with the namespace set to the MCVideo-specific namespace and the priority set to the priority designated for imminent peril calls and if not: i) perform the actions specified in clause 6.3.3.1.8; ii) send the SIP UPDATE request generated in clause 6.3.3.1.8 towards the initiator of the SIP re- INVITE request according to 3GPP TS 24.229 [11]; and iii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.1.8 proceed with the rest of the steps. NOTE 3: Verify that the Resource-Priority header is included and properly populated for both ongoing and newly- entered in-progress imminent peril states of the specified group. b) if the in-progress imminent peril state of the group is set to a value of "true" and this MCVideo user is indicating a new imminent peril indication: i) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11 with the following clarifications; A) set the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and ii) cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and c) if the in-progress imminent peril state of the group is set to a value of "false": i) shall set the value of the in-progress imminent peril state of the group to "true"; ii) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other affiliated and joined participants of the chat MCVideo group as specified in clause 6.3.3.1.15; iii) shall generate SIP INVITE requests for the MCVideo imminent peril group call to the affiliated but not joined members of the chat MCVideo group as specified in clause 6.3.3.1.7; A) for each affiliated but not joined member shall send the SIP INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and B) Upon receiving a SIP 200 (OK) response to the SIP INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and iv) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; … 4) if the SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "false" and is determined to be an authorised request for an ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 207 MCVideo imminent peril call cancellation as specified in clause 6.3.3.1.13.6 and the in-progress imminent peril state of the group to is set to a value of "true" the controlling MCVideo function shall: a) validate that the SIP re-INVITE request includes a Resource-Priority header field with the namespace set to the MCVideo-specific namespace, and the priority set to the priority level designated for a normal priority MCVideo group call, and if not: i) shall perform the actions specified in clause 6.3.3.1.8; and ii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.1.8 shall proceed with the rest of the steps; NOTE 3: verify that the Resource-Priority header is included and properly populated for an in-progress emergency group state cancellation of the specified group. b) shall set the in-progress imminent peril state of the group to a value of "false"; c) shall cache the information that this MCVideo user no longer has an outstanding MCVideo imminent peril group call; d) shall generate SIP re-INVITES requests to the other affiliated and joined members of the MCVideo group as specified in clause 6.3.3.1.15. The MCVideo controlling function: i) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and ii) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and NOTE 4: clause 6.3.3.1.15 will inform the affiliated and joined members of the cancellation of the MCVideo group's in-progress emergency group state and the cancellation of the MCVideo emergency alert if applicable. e) for each of the affiliated but not joined members of the group shall: i) generate a SIP MESSAGE request notification of the cancellation of the MCVideo user's imminent peril call as specified in clause 6.3.3.1.11; ii) set the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; and iii) send the SIP MESSAGE request according to 3GPP TS 24.229 [11]; 5) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [11] with the clarifications specified in clause 6.3.3.2.1 unless the procedures of clause 6.3.3.1.8 were performed in step 2) or 4) above; 6) shall include the "norefersub" option tag in a Supported header field according to IETF RFC 4488 [31]; 7) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [32]; 8) shall interact with media plane as specified in 3GPP TS 24.581 [5]; and 9) shall send the SIP 200 (OK) response towards the MCVideo client according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.2.4.2] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.2.4.3.2] "When the MCVideo session for group call needs to be released as specified in clause 6.3.8.1, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.4." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 208 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.2.1.3 Test description | 6.1.2.1.3.1 Pre-test conditions System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) are affiliated to the Chat group. - The IUT (MCVideo Server) is the controlling server of the Chat group. 6.1.2.1.3.2 Test procedure sequence Table 6.1.2.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the SS-UE1 (MCVideo Client) request the establishment of a chat group call to Group A without implicit transmission request. - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Participating Terminated session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.4.3-1 to establish a chat group call without implicit transmission control request according to option a of note in Annex A, Table A.3.4.3-1? - - 1 P 3 Make the SS-UE2 (MCVideo Client) request the establishment of a chat group call to Group A, to join chat group session without implicit transmission request. - - - - ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 209 St Procedure Message Sequence TP Verdict U - S Message 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Participating Terminated session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.4.3-1 to join a chat group call without implicit transmission control request according to option a of note in Annex A, Table A.3.4.3-1? - - 2 P 5 Make the SS-UE1 (MCVideo Client) request upgrade of the call to an emergency group call with implicit transmission request. - - - - 6 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.3.1.3-1 to upgrade the call to emergency group call with implicit transmission request according to option b.ii of note in Annex A, Table A.3.1.3-1? - - 3 P 7 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 8 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 4 P 9 Make the SS-UE1 (MCVideo Client) request downgrade of the call to a normal group call. - - - - 10 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.3.1.3-1 to downgrade the call without implicit transmission request, with option a of note on Table A.3.1.3-1? - - 5 P 11 Make the SS-UE1 (MCVideo Client) request upgrade of the call to an imminent peril group call with implicit transmission request. - - - - 12 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.3.1.3-1 to upgrade the call to imminent peril group call with implicit transmission request according to option b.ii of note in Annex A, Table A.3.1.3-1? - - 6 P 13 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 14 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 4 P 15 Make the SS-UE1 (MCVideo Client) request downgrade of the call to a normal group call. - - - - 16 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.3.1.3-1 to downgrade the call without implicit transmission request, with option a of note on Table A.3.1.3-1? - - 5 P 17 Make the SS-UE1 (MCVideo Client) release the call. - - - - 18 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 7 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 210 6.1.2.1.3.3 Specific message contents All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.1.2.1.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.1.2.1.3.2-1; Step 1, Annex A, Table A.3.4.3-1; Step 1, Annex A, Table A.2.14.3-1) Derivation Path: Annex A, Table A.3.4.4-1, with condition CHAT-GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.2.1.3.3-2: SIP 200 (OK) from the IUT (MCVideo Server) (Steps 2, 4, 6, 10, 12 and 16, Table 6.1.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 6, Annex A, Table A.2.18.3-1 Step 1, Annex A, Table A.3.4.3-1, Step 3, Annex A, Table A.2.14.3-1) Derivation Path: Annex A, Table A.3.4.4-2, with condition CHAT-GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.2.1.3.3-3: SIP INVITE from the SS-UE2 (Step 4, Table 6.1.2.1.3.2-1; Step 1, Annex A, Table A.3.4.3-1; Step 1, Annex A, Table A.2.14.3-1) Derivation Path: Annex A, Table A.3.4.4-1, with condition CHAT-GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.2.1.3.3-4: SIP 200 (OK) from the SS-UE2 (Steps 6, 10, 12 and 16, Table 6.1.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7, with condition CHAT-GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.2.1.3.3-5: SIP re-INVITE from the SS-UE1 (Step 6, Table 6.1.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with conditions CHAT-GROUP-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 6.1.2.1.3.3-6: SIP re-INVITE from the IUT (MCVideo Server) (Step 6, Table 6.1.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition CHAT-GROUP-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 6.1.2.1.3.3-7: SIP re-INVITE from the SS-UE1 (Steps 10 and 16, Table 6.1.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with conditions CHAT-GROUP-CALL and re_INVITE. NOTE: Conditions are also applied to all body parts. Table 6.1.2.1.3.3-8: SIP re-INVITE from the IUT (MCVideo Server) (Steps 10 and 16, Table 6.1.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition CHAT-GROUP-CALL and re_INVITE. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 211 Table 6.1.2.1.3.3-9: SIP re-INVITE from the SS-UE1 (Step 12, Table 6.1.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with conditions CHAT-GROUP-CALL, re_INVITE and IMMPERIL -CALL. NOTE: Conditions are also applied to all body parts. Table 6.1.2.1.3.3-10: SIP re-INVITE from the IUT (MCVideo Server) (Step 12, Table 6.1.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with conditions CHAT-GROUP-CALL, re_INVITE and IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 6.1.2.1.3.3-11: Transmission Idle from the IUT (MCVideo Server) (Step 8, Table 6.1.2.1.3.2-1; Steps 4 and 5, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-6 with condition EMERGENCY-CALL. Table 6.1.2.1.3.3-12: Transmission Granted from the IUT (MCVideo Server) (Step 6, Table 6.1.2.1.3.2-1; Step 2a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.1.4-11 (note), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. Table 6.1.2.1.3.3-13: Media Transmission Notification from the IUT (MCVideo Server) (Step 6, Table 6.1.2.1.3.2-1; Step 3a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.1.4-12 (note), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. Table 6.1.2.1.3.3-14: Transmission Idle from the IUT (MCVideo Server) (Step 14, Table 6.1.2.1.3.2-1; Steps 4 and 5, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-6 with condition IMMPERIL-CALL. Table 6.1.2.1.3.3-15: Transmission Granted from the IUT (MCVideo Server) (Step 12, Table 6.1.2.1.3.2-1; Step 2a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.1.4-11 (note), with condition IMMPERIL-CALL. NOTE: Depends on server implementation. Table 6.1.2.1.3.3-16: Media Transmission Notification from the IUT (MCVideo Server) (Step 12, Table 6.1.2.1.3.2-1; Step 3a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.1.4-12 (note), with condition IMMPERIL-CALL. NOTE: Depends on server implementation. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 212 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.3 Subscription to Conference Event Package | 6.1.3.1 MCVideo Server - MCVideo Client / Conference Event Package / Subscription to Conference Event Package / Termination of subscription |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.3.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCVideo client) requests session establishment of chat group call without implicit transmisson control with sending SIP INVITE message } then { IUT (MCVideo Server) responds with optional SIP 100 Trying and mandatory 200 (OK) message } } (2) with { IUT (MCVideo Server) having established a Chat Group Call without implicit transmission control } ensure that { when { the SS-UE1 (MCVideo Client) requests to the conference event package for the ongoing group call with SIP SUBSCRIBE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (3) with { IUT (MCVideo Server) having established a Chat Group Call without implicit transmission control } ensure that { when { the SS-UE2 (MCVideo Client) requests session establishment of chat group call without implicit transmission control with sending SIP INVITE message } then { IUT (MCVideo Server) responds with optional SIP 100 Trying and mandatory 200 (OK) message } } (4) with { IUT (MCVideo Server) having established a Chat Group Call with the clients } ensure that { when { the IUT (MCVideo Server) triggers notification to indicate status joint client to the group } then { the IUT (MCVideo Server) requests notification by sending SIP NOTIFY message } } (5) with { IUT (MCVideo Server) having established a Chat Group Call with the clients } ensure that { when { the SS-UE1 (MCVideo client) requests to de-subscribe from MCVideo service settings with SIP SUBSCRIBE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) message and sends a SIP NOTIFY message } } (6) with { IUT (MCVideo Server) having established a Chat Group Call with the clients } ensure that { when { the SS-UE1 (MCVideo Client) ends the chat group call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the other participants } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 213 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.3.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 9.2.3.1, 9.2.3.3, 9.2.3.4.1, 9.2.3.4.2, 9.2.3.4.3, 9.2.3.4.4. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.3.1] "The IETF RFC 4575 [57] defines a conference state event package that shall be used to obtain the status of participants in group sessions. The MCVideo client may subscribe to the conference state event package at any time in a group session that the MCVideo client participates in. The clause 9.2.3.2 specifies the procedures in the MCVideo client when subscribing to the conference events. The participating MCVideo function shall forward conference state subscriptions and notifications as specified in clause 9.2.3.3. The controlling MCVideo function shall handle subscriptions and notification of conference state events as specified in clause 9.2.3.4. The non-controlling MCVideo function shall handle subscriptions and notification of conference state events as specified in clause 9.2.3.4. When the non-controlling MCVideo function connection model is used, the controlling MCVideo function subscribes to the conference state event package from the non-controlling MCVideo function as specified in clause 9.2.3.4.3 and the non-controlling MCVideo function subscribes to the conference state event package from the controlling MCVideo function as specified in clause 9.2.3.5.3." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.3.3] "Upon receipt of a SIP SUBSCRIBE request for conference event status subscription from a MCVideo user served by the participating MCVideo function and if the SIP SUBSCRIBE request contains: 1) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; 2) an Accept header field containing the application/conference-info+xml"MIME type; and 3) an application/vnd.3gpp.mcvideo-info+xml MIME body containing the <mcvideo-request-uri> set to a MCVideo group ID; then the participating MCVideo function: 1) shall attempt to resolve the received Request-URI to an existing MCVideo session identity; … 3) shall generate a SUBSCRIBE request as specified in TS 24.229 [11] 4) shall set the SIP URI in the Request-URI with the MCVideo session identity that is mapped to the MCVideo session identity in the received Request-URI; 5) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body the <mcvideo-calling-user-id> element set to the MCVideo ID of the served user: and 6) shall insert a Record-Route header containing a URI identifying its own address; and 7) shall send the SIP SUBSCRIBE request according to 3GPP TS 24.229 [11]. Upon receiving a SIP response to the SIP SUBSCRIBE request the participating MCVideo function: 1) shall copy the content of the incoming SIP response to an outgoing SIP response; 2) if a SIP 200 (OK) response, shall include in the Contact header field of the outgoing SIP response an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response in the outgoing SIP response; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 214 3) shall forward the SIP response according to 3GPP TS 24.229 [11]. Upon receiving a SIP NOTIFY request within the dialog created by the SIP SUBSCRIBE request destined to a served MCVideo client, the participating MCVideo function: 1) shall include the public service identity of the MCVideo user in the Request-URI; 2) shall copy the content of the incoming SIP NOTIFY request to the outgoing SIP NOTIFY request; and 3) shall send the SIP NOTIFY request according to 3GPP TS 24.229 [11]. Upon receiving a SIP response to the SIP NOTIFY request the participating MCVideo function: 1) shall copy the content of the incoming SIP response to an outgoing SIP response; 2) if a SIP 200 (OK) response, shall include an MCVideo session identity constructed from the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response in the outgoing SIP response; and 3) shall forward the SIP response according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.3.4.1] "Upon receipt of a SIP SUBSCRIBE request for event package subscription in the controlling MCVideo function and the SIP SUBSCRIBE request: 1) contains an application/vnd.3gpp.mcvideo-info+xml MIME body with a) the <mcvideo-request-uri> element set to the group identity of the group session and the <mcvideo- calling-user-id> element set to either: i) the MCVideo ID of a participant in the group session; or ii) a constituent MCVideo group ID of a non-controlling MCVideo function in a temporary group session; 2) contains the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Asserted-Service header field according to IETF RFC 6050 [14]; 3) contains an Accept header field containing the application/conference-info+xml MIME type; and 4) is not received in a group call initiated as a broadcast group call; then the controlling MCVideo function: … 2) shall handle the request according to IETF RFC 6665 [16] and IETF RFC 4575 [57]; 3) shall cache information about the subscription; 4) shall send a conference state notification as specified in clause 9.2.3.4.2; and 5) if the SIP SUBSCRIBE request is the first SUBSCRIBE request from a participant in a temporary group session, shall subscribe to the conference event package from all non-controlling MCVideo functions in the group session as specified in clause 9.2.3.4.3. Upon receipt of a SIP SUBSCRIBE request for event package subscription in the controlling MCVideo function in an group call initiated as a broadcast group call, the controlling MCVideo function: 1) shall generate a SIP 480 (Temporarily Unavailable) response to the SIP SUBSCRIBE request as specified in 3GPP TS 24.229 [11]; 2) shall include a Warning header field with the warning text set to "105 subscription not allowed in a broadcast group call" as specified in clause 4.4; and 3) send the SIP 480 (Temporarily Unavailable) response according to 3GPP TS 24.229 [11]." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 215 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.3.4.2] "The procedures in this clause is triggered by: 1) the receipt of a SIP SUBSCRIBE request as specified in clause 9.2.3.4.1; 2) the receipt of a SIP BYE request from one of the participants in a pre-arranged or a chat group session; or 3) when a new participant is added in a pre-arranged or chat group session. When sending a conference state event notification, the controlling MCVideo function: 1) shall generate a notification package as specified in clause 6.3.3.4 to all MCVideo clients which have subscribed to the conference state event package; and NOTE: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 2) shall send a SIP NOTIFY request to all participants which have subscribed to the conference state event package as specified in 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.3.4.3] "The procedure in this clause is triggered by: 1) the receipt of a SIP 200 (OK) response to a SIP INVITE request for non-controlling MCVideo function of an MCVideo group and if at least one participant already has subscribed to the conference event package in the controlling MCVideo function as specified in clause 9.2.3.4.1; or 2) the receipt of the first SIP SUBSCRIBE request as specified in clause 9.2.3.4.1 and one or more participant in the group session is a non-controlling MCVideo function; then, for each non-controlling MCVideo function from where a SIP 200 (OK) response to a SIP INVITE request for non-controlling MCVideo function of an MCVideo group has been received and where a SIP SUBSCRIBE request is not already sent, the controlling MCVideo function: 1) shall generate a SIP SUBSCRIBE request and use a new SIP-dialog according to IETF RFC 6665 [16], IETF RFC 4575 [57] and 3GPP TS 24.229 [11]; 2) shall set the Request-URI of the SIP SUBSCRIBE request to the public service identity of the non-controlling MCVideo function serving the group identity of the MCVideo group owned by the partner MCVideo system; 3) shall include the same P-Asserted-Identity header field as included in the SIP INVITE request for non- controlling MCVideo function of an MCVideo group; 4) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Preferred-Service header field according to IETF RFC 6050 [14]; 5) shall include an Accept-Contact header with the g.3gpp.mcvideo along with "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; 6) shall set the Expires header field according to IETF RFC 6665 [16], to 4294967295; NOTE: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [15]. 7) shall include an Accept header field containing the application/conference-info+xml MIME type; 8) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with: a) the <mcvideo-request-uri> element set to the constituent MCVideo group ID; and b) the <mcvideo-calling-group-id> set to the temporary MCVideo group ID; and 9) shall send the SIP SUBSCRIBE request using a new SIP dialog according to 3GPP TS 24.229 [11]. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 216 The responses to the SIP SUBSCRIBE request shall be handled according to IETF RFC 6665 [16], IETF RFC 4575 [57] and TS 24.229 [11]. Upon receiving an incoming SIP NOTIFY requests to the previously sent SIP SUBSCRIBE request, the controlling MCVideo function: 1) shall handle the request according to IETF RFC 6665 [16] and IETF RFC 4575 [57]; 2) shall modify the SIP NOTIFY request as specified in clause 6.3.3.4; and 3) shall forward the modified SIP NOTIFY request according to 3GPP TS 24.229 [11] to all other participants with a subscription to the conference event package. NOTE: A non-controlling MCVideo function of an MCVideo group is regarded as a participant in a temporary group session." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.3.4.4] "Upon receipt of a SIP SUBSCRIBE request for event status subscription in the controlling MCVideo function that terminates the subscription of the conference event package as specified in IETF RFC 6665 [16], the controlling MCVideo function: 1) shall send a SIP 200 (OK) response as specified in IETF RFC 6665 [16]; and 2) if there are no remaining subscriptions to the event package in the ongoing MCVideo call in a temporary group session, shall terminate the subscriptions to the conference event package as specified in IETF RFC 6665 [16] in all non-controlling MCVideo functions in the temporary group session. Upon expiry of the subscription timer and if there are no remaining subscriptions to the event package in the ongoing MCVideo call in a temporary group session, the controlling MCVideo function shall terminate the subscriptions to the conference event package as specified in IETF RFC 6665 [16] in all non-controlling MCVideo functions in the temporary group session." |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.3.1.3 Test description | 6.1.3.1.3.1 Pre-test conditions System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 217 Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) are affiliated to the Chat group. - The IUT (MCVideo Server) is the controlling server of the Chat group. 6.1.3.1.3.2 Test procedure sequence Table 6.1.3.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the SS-UE1 (MCVideo Client) request the establishment of a chat group call to Group A without implicit transmission request. - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Participating Terminated session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.4.3-1 to establish a chat group call without implicit transmission control request according to option a of note in Annex A, Table A.3.4.3-1? - - 1 P 3 Make the SS-UE1 (MCVideo Client) subscribe to the conference event package for the ongoing group call to receive the current status and later notifications. - - - - 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Subscription and Notification' as described in Annex A, Table A.2.7.3-1 to subscribe to the conference event package for the ongoing group call to receive the current status and later notifications? - - 2 P 5 Make the SS-UE2 (MCVideo Client) request the establishment of a chat group call to Group A, to join chat group session without implicit transmission request. - - - - 6 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Participating Terminated session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.4.3-1 to join a chat group call without implicit transmission control request according to option a of note in Annex A, Table A.3.4.3-1? - - 3 P 7 Check: Does the IUT (MCVideo Server) send a SIP NOTIFY message indicating that SS-UE2 (MCVideo Client) joined the chat group call? <-- SIP NOTIFY 4 P 8 The SS-UE1 (MCVideo Client) responds with a SIP 200 (OK) message. --> SIP 200 (OK) - - 9 Make the SS-UE1 (MCVideo Client) de-subscribe from the conference event package for the ongoing group call to stop receiving status and notifications. - - - - 10 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Subscription and Notification' as described in Annex A, Table A.2.7.3-1 to de-subscribe from the conference event package for the ongoing group call to receive the current status and later notifications? - - 5 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 218 St Procedure Message Sequence TP Verdict U - S Message 11 Make the SS-UE1 (MCVideo Client) release the call. - - - - 12 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 6 P 6.1.3.1.3.3 Specific message contents All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.1.3.1.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.1.3.1.3.2-1; Step 1, Annex A, Table A.3.4.3-1; Step 1, Annex A, Table A.2.14.3-1) Derivation Path: Annex A, Table A.3.4.4-1, with condition CHAT-GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.3.1.3.3-2: SIP 200 (OK) from the IUT (MCVideo Server) (Steps 2 and 6, Table 6.1.3.1.3.2-1; Step 1, Annex A, Table A.3.4.3-1, Step 3, Annex A, Table A.2.14.3-1) Derivation Path: Annex A, Table A.3.4.4-2, with condition CHAT-GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.3.1.3.3-3: SIP INVITE from the SS-UE2 (Step 6, Table 6.1.3.1.3.2-1; Step 1, Annex A, Table A.3.4.3-1; Step 1, Annex A, Table A.2.14.3-1) Derivation Path: Annex A, Table A.3.4.4-1, with condition CHAT-GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.1.3.1.3.3-4: SIP SUBSCRIBE from the SS-UE1 (Step 4, Table 6.1.3.1.3.2-1; Step 1, Annex A, Table A.2.7.3-1) Derivation Path: Annex A, Table A.2.7.4-1, with condition MCVIDEO Information Element Value/remark Comment Reference Condition Request-Line Request-URI MCVideo session identity of the group session as provided by the IUT (MCVideo Server) in the Contact header field of the SIP 200 OK at call establishment ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.3.2 Accept-Contact ac-value feature-param "+g.3gpp.icsi-ref=urn:urn- 7:3gpp- service.ims.icsi.mcvideo" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.3.2 req-param "require" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.3.2 explicit-param "explicit" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.3.2 Expires value "4294967295" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.3.2 Accept ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 219 Derivation Path: Annex A, Table A.2.7.4-1, with condition MCVIDEO Information Element Value/remark Comment Reference Condition media-range "application/conference- info+xml" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.3.2 Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.1.3.1.3.3-5 Table 6.1.3.1.3.3-5: MCVideo-Info in SIP SUBSCRIBE (Table 6.1.3.1.3.3-4) 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_Group_A_ID The URI of the group 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 6.1.3.1.3.3-6: SIP NOTIFY from the IUT (MCVideo Server) (Step 4, Table 6.1.3.1.3.2-1; Step 3, Annex A, Table A.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, with condition MCVIDEO Information Element Value/remark Comment Reference Condition P-Asserted-Identity addr-spec user-info and host tsc_MCVideo_PublicSer viceId_A ETSI TS 124 281 [8] (3GPP TS 24.281) clause 6.3.3.4 Event event-type "conference" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 6.3.3.4 Expires value "3600" 3600 seconds ETSI TS 124 281 [8] (3GPP TS 24.281) clause 6.3.3.4 Subscription-State expires "3600" P-Preferred-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcvideo " ETSI TS 124 281 [8] (3GPP TS 24.281) clause 6.3.3.4 Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.1.3.1.3.3-7 MIME body part Conference-Info MIME-part-body Conference-Info as described in Table 6.1.3.1.3.3-8 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 220 Table 6.1.3.1.3.3-7: MCVideo-Info in SIP NOTIFY (Table 6.1.3.1.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-calling-user- id not present mcvideo-calling- group-id Encrypted (note) <mcvideo- calling-group-id> with mcvideoURI set to px_MCVideo_Group_A_ID NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2A. Table 6.1.3.1.3.3-8: Conference-Info in SIP NOTIFY (Table 6.1.3.1.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.15-1, with condition MCVIDEO Information Element Value/remark Comment Reference Condition conference-info users user [2] not present user [3] not present Table 6.1.3.1.3.3-9: SIP NOTIFY from the MCVideo Server (Step 7, Table 6.1.3.1.3.2-1) Derivation Path: Table 6.1.3.1.3.3-6 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.1.3.1.3.3-7 MIME body part Conference-Info MIME-part-body Conference-Info as described in Table 6.1.3.1.3.3-10 Table 6.1.3.1.3.3-10: Conference-Info in SIP NOTIFY (Table 6.1.3.1.3.3-9) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.15-1, with condition MCVIDEO Information Element Value/remark Comment Reference Condition conference-info users user [2] endpoint status connected user [3] not present Table 6.1.3.1.3.3-11: SIP SUBSCRIBE from the SS-UE1 (Step 10, Table 6.1.3.1.3.2-1; Step 1, Annex A, Table A.2.7.3-1) Derivation Path: Table 6.1.3.1.3.3-4 Information Element Value/remark Comment Reference Condition Expires value "0" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.3.2 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 221 Table 6.1.3.1.3.3-12: SIP NOTIFY from the MCVideo Server (Step 10, Table 6.1.3.1.3.2-1; Step 3, Annex A, Table A.2.7.3-1) Derivation Path: Table 6.1.3.1.3.3-9 Information Element Value/remark Comment Reference Condition Subscription-State IETF RFC 6665 [14] substate-value "terminated" expires not present |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.4 Remote Change of Selected Group | 6.1.4.1 MCVideo Server - MCVideo Client / Remote Change of Selected Group / Selected Group Change of Targeted User |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.4.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { SS-UE1 (MCVideo Client) requests to change the selected group of targeted user B, in the SS-UE2 (MCVideo Client), to group A by sending a SIP MESSAGE message } then { IUT (MCVideo Server) sends a SIP MESSAGE message to UE2 (MCVideo Client) and responds with a SIP 200 (OK) to UE1 (MCVideo Client) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.4.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 9.2.4.1, 9.2.4.3.1, 9.2.4.3.2, 9.2.4.4. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.4.1] "Clause 9.2.4 specifies the MCVideo client procedures, participating MCVideo function procedures and controlling MCVideo function procedures for the on-network remote change of an MCVideo user's selected group." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.4.3.1] "Upon receiving a "SIP MESSAGE request for group-selection-change for originating participating MCVideo function" the participating MCVideo function: … 2) shall determine the MCVideo ID of the calling 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 MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 4) shall determine the public service identity of the controlling MCVideo function associated with the group identity contained in the <mcvideo-request-uri> element contained in the application/vnd.3gpp.mcvideo- info+xml MIME body; 5) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [33]; 6) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCVideo function associated with the group identity contained in the received SIP MESSAGE request; 7) shall copy the contents of the application/vnd.3gpp.mcvideo-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 222 8) shall copy the contents of the application/resource-lists MIME body into the outgoing SIP MESSAGE request; 9) shall set the <mcvideo-calling-user-id> element of the <mcvideoinfo> element containing the <mcvideo- Params> element to the MCVideo ID determined in step 2) above; 10) shall set the P-Asserted-Identity in the outgoing SIP MESSAGE request to the public user identity in the P- Asserted-Identity header field contained in the received SIP MESSAGE request; 11) shall include an Accept-Contact header field containing the g.3gpp.mcvideo media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; 12) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with parameters "require" and "explicit" according to IETF RFC 3841 [20]; 13) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and 14) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [11]. Upon receipt of a SIP 2xx response in response to the sent SIP MESSAGE request, the participating MCVideo function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the MCVideo client. …" [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.4.3.2] "Upon receiving a "SIP MESSAGE request for group-selection-change for terminating participating MCVideo function" the participating MCVideo function: … 2) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCVideo ID and public user identity; … 4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11; 5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), 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 [11]. Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCVideo function shall forward the SIP 2xx response to the controlling MCVideo function. …" [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 9.2.4.4] "Upon receiving: - a "SIP MESSAGE request for group selection change request for controlling MCVideo function"; or - a "SIP MESSAGE request for group selection change response for controlling MCVideo function"; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 223 the controlling MCVideo function: … 3) if there is a <request-type> element set to a value of "group-selection-change-request" contained in the <anyExt> element in the <mcvideo-Params> element contained in the <mcvideoinfo> root element contained in the application/vnd.3gpp.mcvideo-info+xml MIME body in the received SIP MESSAGE request: a) if the MCVideo user identified by the MCVideo ID in the application/resource-lists MIME body contained in the SIP MESSAGE request is not affiliated with the MCVideo group identified by the <mcvideo-request-uri> in the application/vnd.3gpp.mcvideo-info+xml MIME body as determined by the procedures of clause 6.3.6: i) shall determine if the MCVideo user is eligible to be affiliated with the MCVideo group as determined by clause 8.2.2.3.8; and … 4) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [33]; 5) shall include an Accept-Contact header field containing the g.3gpp.mcvideo media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; 6) 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.mcvideo" along with parameters "require" and "explicit" according to IETF RFC 3841 [20]; 7) shall copy the contents of the application/vnd.3gpp.mcvideo-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP MESSAGE request with the following clarifications: a) shall set the <mcvideo-calling-group-id> to the MCVideo group identity contained in the <mcvideo- request-uri> element contained in the application/vnd.3gpp.mcvideo-info+xml MIME body included in the received SIP MESSAGE request; and b) shall set the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP MESSAGE request to the MCVideo ID of the targeted MCVideo user contained in the application/resource-lists MIME body contained in the received SIP MESSAGE request; 8) if the received SIP MESSAGE request is a "SIP MESSAGE request for group selection change request for controlling MCVideo function": a) if the targeted MCVideo user is not affiliated to the identified MCVideo group and was determined to be eligible to be affiliated with the MCVideo group in step 3) a) i) above, shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with the <anyExt> element an <affiliation-required> element set to a value of "true"; 9) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated with the targeted MCVideo user; NOTE: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. 10) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; 11) shall copy the public user identity of the calling MCVideo 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; and 12) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [11]. Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCVideo function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the originating participating MCVideo function. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 224 …" |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.1.4.1.3 Test description | 6.1.4.1.3.1 Pre-test conditions System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) are affiliated to the Prearranged group. - The IUT (MCVideo Server) is the controlling server of the Prearranged group. 6.1.4.1.3.2 Test procedure sequence Table 6.1.4.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the SS-UE1 (MCVideo Client) request to change the selected group of user B to group A for SS-UE2 (MCVideo Client). - - - - 2 Check: Does the MCVideo Server correctly perform procedure 'MCX E2E SIP MESSAGE' as described in Table A.2.10.3-1 to change the selected group of targeted user B, in the SS-UE2 (MCVideo Client), to group A? - - 1 P 3 Check: Does the MCVideo Server correctly perform procedure 'MCX E2E SIP MESSAGE' as described in Table A.2.10.3-1 to notify SS-UE1 (MCVideo Client) about the successful change of the selected group A in the SS-UE2 (MCVideo Client)? (See note) - - 1 P NOTE: During this procedure the SS-UE1 performs the role of SS-UE2 and viceversa. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 225 6.1.4.1.3.3 Specific message contents All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.1.4.1.3.3-1: SIP MESSAGE from the SS-UE1 (Step 2, Table 6.1.4.1.3.2-1; Step 1, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 with condition MCVIDEO Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info ETSI TS 124 281 [8] (3GPP TS 24.281) clause F.1 MIME-part-body MCVideo-Info as described in Table 6.1.4.1.3.3-2 MIME body part Resource-lists MIME-part-body Resource-lists as described in Table 6.1.4.1.3.3-3 Table 6.1.4.1.3.3-2: MCVideo-Info in SIP MESSAGE (Table 6.1.4.1.3.3-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_Group_A_ID The MCVideo group identity to be selected by the targeted MCVideo user ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.4.2.1 anyExt request-type "group-selection-change- request" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.4.2.1 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.1-2A. Table 6.1.4.1.3.3-3: Resource lists in SIP MESSAGE (Table 6.1.4.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-1 Information Element Value/remark Comment Reference Condition resource-lists list entry[1] uri attribute px_MCVideo_ID_User_B The targeted MCVideo user ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.4.2.1 Table 6.1.4.1.3.3-4: SIP MESSAGE from the IUT (MCVideo Server) to SS-UE2 (Step 2, Table 6.1.4.1.3.2-1; Step 2, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with condition MCVIDEO and ACCEPT-CONTACT-WITH-MEDIA-FEATURE-TAG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.1.4.1.3.3-5 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 226 Table 6.1.4.1.3.3-5: MCVideo-Info in SIP MESSAGE (Table 6.1.4.1.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-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_B ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.4.4 mcvideo-calling-user-id Encrypted (note) <mcvideo- calling-user-id> with mcvideoURI set to px_MCVideo_ID_User_A mcvideo-calling-group-id Encrypted (note) <mcvideo- calling-group-id> with mcvideoURI set to px_MCVideo_Group_A_ID anyExt request-type "group-selection-change- request" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.4.2.1 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2A. Table 6.1.4.1.3.3-6: SIP MESSAGE from the SS-UE2 (Step 3, Table 6.1.4.1.3.2-1; Step 1, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 with condition MCVIDEO Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info ETSI TS 124 281 [8] (3GPP TS 24.281) clause F.1 MIME-part-body MCVideo-Info as described in Table 6.1.4.1.3.3-7 MIME body part Resource-lists MIME-part-body Resource-lists as described in Table 6.1.4.1.3.3-8 Table 6.1.4.1.3.3-7: MCVideo-Info in SIP MESSAGE (Table 6.1.4.1.3.3-6) 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_Group_A_ID ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.4.2.2 anyExt response-type "group-selection-change- response" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.4.2.2 selected-group- change-outcome "success" 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 151-1 V1.1.1 (2026-02) 227 Table 6.1.4.1.3.3-8: Resource lists in SIP MESSAGE (Table 6.1.4.1.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-1 Information Element Value/remark Comment Reference Condition resource-lists list entry[1] uri attribute px_MCVideo_ID_User_A The targeted MCVideo user ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.4.2.2 Table 6.1.4.1.3.3-9: SIP MESSAGE from the IUT (MCVideo Server) to SS-UE1 (Step 3, Table 6.1.4.1.3.2-1; Step 2, Table A.2.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with condition MCVIDEO and ACCEPT-CONTACT-WITH-MEDIA-FEATURE-TAG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.1.4.1.3.3-10 Table 6.1.4.1.3.3-10: MCVideo-Info in SIP MESSAGE (Table 6.1.4.1.3.3-9) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-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 [8] (3GPP TS 24.281) clause 9.2.4.4 mcvideo-calling-user-id Encrypted (note) <mcvideo- calling-user-id> with mcvideoURI set to px_MCVideo_ID_User_B mcvideo-calling-group-id Encrypted (note) <mcvideo- calling-group-id> with mcvideoURI set to px_MCVideo_Group_A_ID anyExt response-type "group-selection-change- response" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 9.2.4.4 selected-group-change- outcome "success" NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2A. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 228 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.2 Private Calls | 6.2.1 MCVideo Server - MCVideo Client / Private Call / On-demand / Automatic Commencement Mode / With Transmission Control / Upgrade to Emergency Call / Cancellation of Emergency on User request |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.2.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 and having registered the clients} ensure that { when { the SS-UE1 (MCVideo Client) initiates a private call with automatic commencement mode and implicit transmission control request } then { IUT (MCVideo Server) accepts the call from the initiator and establishes the call with SS-UE2 (MCVideo Client) and sends transmission granted to the SS-UE1 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established an MCVideo On-demand Private Call with Automatic Commencement Mode } ensure that { when { the SS-UE1 (MCVideo Client) requests the end of transmission control } then { IUT (MCVideo Server) sends transmission idle to the SS-UE1 (MCVideo Client) and sends transmission idle to SS-UE2 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established an MCVideo On-demand Private Call with Automatic Commencement Mode and implicit transmission control request } ensure that { when { the SS-UE1 (MCVideo Client) upgrades the call to emergency private call with implicit transmission control } then { IUT (MCVideo Server) accepts the upgrade from the initiator and updates the call for SS- UE2 (MCVideo Client) and sends transmission granted to the SS-UE1 (MCVideo Client) } } (4) with { IUT (MCVideo Server) having established an MCVideo On-demand Private Call with Automatic Commencement Mode } ensure that { when { the SS-UE1 (MCVideo Client) downgrades the call to a normal private call } then { IUT (MCVideo Server) accepts the downgrade from the initiator and updates the call for SS-UE2 (MCVideo Client) } } (5) with { IUT (MCVideo Server) having established an MCVideo On-demand Private Call with Automatic Commencement Mode } ensure that { when { the SS-UE1 (MCVideo Client) ends the Private call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to SS-UE2 (MCVideo Client) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.2.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 10.2.2.3.1.1, 10.2.2.3.1.3, 10.2.2.3.2, 10.2.2.3.3, 10.2.2.4.1, 10.2.2.4.2, 10.2.2.4.3, 10.2.2.4.4, 10.2.2.4.5, 10.2.2.4.6, 10.2.4.2.1.1, 10.2.4.2.2.1, 10.2.4.3.1, and ETSI TS 124 581 [9] (3GPP TS 24.581), clauses 6.3.2.2, 6.4.2, 6.4.3, 6.4.4. Unless otherwise stated, these are Rel-14 requirements. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 229 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.3.1.1] "Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "private", the participating MCVideo function: … 3) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request and shall authorise the user; NOTE 3: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 5) shall: a) if the <session-type> is set to "private", determine that the call is a private call; 6) if the call is a: a) private call, determine the public service identity of the controlling MCVideo function for the private call service associated with the originating user's MCVideo ID identity; … 8) if the incoming SIP INVITE request does not contain an application/resource-lists MIME body, shall reject the "SIP INVITE request for originating participating MCVideo function" with a SIP 403 (Forbidden) response …, and shall not continue with the rest of the steps; 9) if the call is a private call and the incoming SIP INVITE request contains an application/resource-lists MIME body with more than one <entry> element, shall reject the "SIP INVITE request for originating participating MCVideo function" with a SIP 403 (Forbidden) response … and shall not continue with the rest of the steps; … 12) shall validate the media parameters and if the MCVideo video media codec is not offered in the "SIP INVITE request for originating participating MCVideo function" shall reject the request … 13) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3 with the following clarifications: a) if the conditions in step 12) above were executed and the participating MCVideo function determined that the "uri" attribute of only one of the <entry> elements of the application/resource-lists MIME body matched with an <entry> element of the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) then the <session-type> in the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request generated in clause 6.3.2.1.3 is set to "private"; and b) if the conditions in step 12) above were executed, then only the <entry> element(s) of the application/resource-lists MIME body that have a "uri" attribute that matched with an <entry> elements of the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) are included in the application/resource-lists MIME body in the SIP INVITE request generated in clause 6.3.2.1.3; 14) shall set the Request-URI to the public service identity of the controlling MCVideo function hosting the private call service as determined by step 6); 15) shall set the <mcvideo-calling-user-id> element in an application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 16) if the call is a private call and: a) if a Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was received in the incoming SIP INVITE request with a value of "Manual", shall not include a Priv-Answer-Mode header field in the outgoing SIP INVITE request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 230 … c) if the <allow-force-auto-answer> element of the <ruleset> element is present in the MCVideo user profile document with the value "true" (see the MCVideo user profile document in 3GPP TS 24.484 [25]) on the participating MCVideo function, and the Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was received in the incoming SIP INVITE request with a value of "Auto", shall include the Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request; d) if a Priv-Answer-Mode header field containing the value of "Auto" has not been included in the outgoing SIP INVITE request as specified in step 17) above and the incoming "SIP INVITE request for originating participating MCVideo function" contained an Answer-Mode header field as specified in IETF RFC 5373 [27], then shall populate the Answer-Mode header field of the outgoing SIP INVITE request with the contents of the Answer-Mode header field from the incoming "SIP INVITE request for originating participating MCVideo function"; 17) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for originating participating MCVideo function", as specified in clause 6.3.2.1.1.1; 18) shall include a Resource-Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field if included in the SIP INVITE request from the MCVideo client; and 19) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. Upon receiving a SIP 180 (Ringing) response, the participating MCVideo function: 1) shall generate a SIP 180 (Ringing) response to the SIP INVITE request as specified in the clause 6.3.2.1.5.1; 2) shall include the P-Asserted-Identity header field as received in the incoming SIP 180 (Ringing) response; 3) shall include Warning header field(s) received in the incoming SIP 180 (Ringing) response; and 4) shall forward the SIP 180 (Ringing) response to the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response, the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2; 2) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 3) shall include Warning header field(s) received in the incoming SIP 200 (OK) response; 4) shall include the P-Asserted-Identity header field received in the incoming SIP 200 (OK) response into the outgoing SIP 200 (OK) response; 5) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 6) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 8) shall start the SIP session timer according to rules and procedures of IETF RFC 4028 [23]. The participating MCVideo function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [11]." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 231 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.3.1.3] "This clause covers both on-demand session and pre-established sessions. Upon receipt of a SIP re-INVITE request for an existing MCVideo private call session the participating MCVideo function: 1) may reject the SIP re-INVITE request depending on the value of the Resource-Priority header field if the Resource-Priority header field is included in the received SIP re-INVITE request according to rules and procedures specified in IETF RFC 4412 [33] and skip the rest of the steps; … 3) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request and shall authorise the user; NOTE 2: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. 4) shall validate the media parameters and if the MCVideo video media codec is not offered in the SIP re-INVITE request shall reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps; … 5) shall generate a SIP re-INVITE request as specified in clause 6.3.2.1.9; 6) shall set the <mcvideo-calling-user-id> element in an application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP re-INVITE request to the MCVideo ID of the calling user; 7) shall, if the SIP re-INVITE request was received within an on-demand session include in the SIP re-INVITE request an SDP containing the current media parameters used by the existing session; 8) shall, if the SIP re-INVITE request was received within a pre-established session, include in the SIP re- INVITE request an SDP offer based upon the previously negotiated SDP for the pre-established session as specified in clause 6.3.2.1.1.2; 9) shall include a Resource-Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field if included in the SIP re-INVITE request from the MCVideo client; and 10) shall forward the SIP re-INVITE request, according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response, the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2; 2) if the SIP 200 (OK) response is to be sent within an on-demand session shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 3) if the SIP 200 (OK) response is to be sent within a pre-established session shall include in the SIP 200 (OK) response an SDP answer based upon the previously negotiated SDP for the pre-established session; 4) shall include Warning header field(s) received in the incoming SIP 200 (OK) response; 5) shall include the P-Asserted-Identity header field received in the incoming SIP 200 (OK) response into the outgoing SIP 200 (OK) response; 6) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; and 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. The participating MCVideo function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [11]." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 232 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.3.2] "This clause covers both on demand session and pre-established session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: … 2) shall check the presence of the isfocus media feature tag in the URI of the Contact header field … … 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; … 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if one of the following conditions are met: a) "SIP INVITE request for terminating participating MCVideo function" contains an Answer-Mode header field with the value "Auto"; b) "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; or c) "SIP INVITE request for terminating participating MCVideo function" contains a Priv-Answer-Mode header field with the value "Auto"; and …" [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.3.3] "This clause covers the on-demand session case only. Upon receipt of a SIP re-INVITE request for an existing MCVideo private call session the participating MCVideo function: … 2) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP re-INVITE request to retrieve the binding between the MCVideo ID and public user identity; … 4) shall generate a SIP re-INVITE as specified in clause 6.3.2.2.10; NOTE 2: As this is the modification of an in-progress MCVideo private call, this procedure does not attempt modification of the existing answer-mode of the call. 5) shall include in the SIP re-INVITE request an SDP offer containing the current media parameters used by the existing session; and 6) shall send the SIP re-INVITE request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving the SIP 200 (OK) response to the SIP re-INVITE request, the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2; 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 clause 6.3.2.2.2.1; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 233 3) shall copy the P-Asserted-Identity header field from the incoming SIP 200 (OK) response to the outgoing SIP 200 (OK) response; 4) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 5) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [11]. The participating MCVideo function shall forward any other SIP response that does not contain SDP along the signalling path to the originating network according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.4.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 10.2.2.4.2 The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; NOTE 1: As a result of calling clause 6.3.3.1.2, the <mcvideo-calling-user-id> containing the calling user's MCVideo ID is copied into the outgoing SIP INVITE. 2) if the received SIP INVITE request contains an authorised request for an MCVideo emergency private call as determined by clause 6.3.3.1.13.2: a) shall set the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; b) if the received SIP INVITE request contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, perform the procedures specified in clause 6.3.3.1.12; and c) if the received SIP INVITE request did not contain an alert indication or contains an alert indication set to a value of "true" and is not an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; 3) shall copy the MCVideo ID of the MCVideo user listed in the MIME resources body of the incoming SIP INVITE request, into the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited; NOTE 2: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 3: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 5) shall copy the public user identity of the calling MCVideo user from the P-Asserted-Identity header field of the incoming SIP INVITE request into the P-Asserted-Identity header field of the SIP INVITE request; 6) shall include a Resource-Priority header field populated with the values for an MCVideo emergency private call as specified in clause 6.3.3.1.19, if either of the following conditions is met: a) if the received SIP INVITE request contains an authorised request for an MCVideo emergency private call as determined in step 2 above; or b) the originating MCVideo user is in an in-progress emergency private call state with the targeted MCVideo user; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 234 8) shall send the SIP INVITE request towards the core network according to 3GPP TS 24.229 [11]; and 9) shall start a private call timer with a value set to the configured max private call duration for the user. Upon receiving SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall cache the contact received in the Contact header field; and 2) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. Upon expiry of the private call timer, the controlling MCVideo function shall follow the procedure for releasing private call session as specified in clause 10.2.5.4." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.4.2] "In the procedures in this clause: 1) <emergency-ind> refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; 2) <alert-ind> refers to the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 3) <session-type> refers to the <session-type> element of an application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of: - a "SIP INVITE request for controlling MCVideo function of a private call"; or the controlling MCVideo function: 1) if the <session-type> in the SIP INVITE request is set to "private": a) shall check whether the public service identity contained in the Request-URI is allocated for private call and perform the actions specified in clause 6.3.7.1 if it is not allocated and skip the rest of the steps; and b) shall perform actions to verify the MCVideo ID of the inviting MCVideo user in the <mcvideo-calling- user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request, and authorise the request according to local policy, and if it is not authorised the controlling MCVideo function shall return a SIP 403 (Forbidden) response with the warning text as specified in "Warning header field" and skip the rest of the steps; 2) if the incoming SIP INVITE request does not contain an application/resource-lists MIME body shall reject the SIP INVITE request … and shall not continue with the rest of the steps; 3) if the <session-type> is set to "private" and the application/resource-lists MIME body contains more than one <entry> element, shall reject the "SIP INVITE request for originating participating MCVideo function" …, and shall not continue with the rest of the steps; 4) shall validate that the received SDP offer includes at least one media stream for which the media parameters and at least one codec or media format is acceptable by the controlling MCVideo function and if not, reject the request … and skip the rest of the steps; 5) if received SIP INVITE request includes an <emergency-ind>, shall validate the request as described in clause 6.3.3.1.17; … 7) if a Resource-Priority header field is included in the received SIP INVITE request and if the Resource-Priority header field is set to the value indicated for emergency calls, shall reject the SIP INVITE request … and skip the remaining steps if neither one of the following conditions are true: a) the SIP INVITE request does not contain an authorised request for an MCVideo emergency call as determined in step 4 above; or b) the originating MCVideo user is not in an in-progress emergency private call state with the targeted MCVideo user; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 235 8) if: a) the received SIP INVITE request contains an emergency indication set to a value of "true"; b) the originating MCVideo user is not in an in-progress emergency private call state with the targeted MCVideo user; and c) if the <session-type> in the SIP INVITE request is set to "private"; then: a) shall cache the information that the MCVideo user has initiated an MCVideo emergency private call to the targeted user; and b) shall cache the information that the MCVideo user is in an in-progress emergency private call state with the targeted MCVideo user; 9) shall perform actions as described in clause 6.3.3.2.2; 10) shall allocate an MCVideo session identity for the MCVideo session; and 11) shall invite the MCVideo user(s) listed in the MIME resource-lists body of received SIP INVITE request as specified in clause 10.2.2.4.1. Upon receiving a SIP 180 (Ringing) response and if the SIP 180 (Ringing) response or the SIP final response has not yet been sent to the inviting MCVideo client, the controlling MCVideo function: 1) if the SIP 180 (Ringing) response is associated with a SIP INVITE that contained a <session-type> set to "private", shall generate a SIP 180 (Ringing) response to the SIP INVITE request and send the SIP 180 (Ringing) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; and Upon receiving a SIP 200 (OK) response for the SIP INVITE request, the SIP dialog was established as a result of receiving a SIP INVITE request with a <session-type> element set to the value of "private" and the SIP final response has not yet been sent to the inviting MCVideo client, the controlling MCVideo function: 1) shall generate a SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.2; … 4) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and NOTE 2: Resulting media plane processing is completed before the next step is performed. 5) shall send a SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request, the SIP dialog was established as a result of receiving a SIP INVITE request with a <session-type> element set to the value of "first-to-answer" and the SIP final response has not yet been sent to the inviting MCVideo client the controlling MCVideo function: 1) shall generate a SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 3) the received SIP INVITE request contains an emergency indication set to a value of "true": a) shall cache the information that the MCVideo user has initiated an MCVideo emergency private call to the targeted user; and b) shall cache the information that the MCVideo user is in an in-progress emergency private call state with the targeted MCVideo user; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 236 … 5) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; NOTE 4: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [4]; and 7) if not successful in cancelling or terminating SIP dialogs in step 6) above, may repeat the SIP CANCEL and SIP BYE requests. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, where the SIP 200 (OK) response was sent with a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18. The controlling MCVideo function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.4.3] "In the procedures in this clause: 1) emergency indication in an incoming SIP re-INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) alert indication in an incoming SIP re-INVITE request refers to the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receiving a SIP re-INVITE request with an emergency indication set to a value of "true", the controlling MCVideo function: 1) shall validate that the received SDP offer includes at least one media stream for which the media parameters and at least one codec or media format is acceptable by the controlling MCVideo function and if not, reject the request … and skip the rest of the steps; 2) shall validate the request as described in clause 6.3.3.1.17; … 4) if a Resource-Priority header field is included in the received SIP re-INVITE request and if the Resource- Priority header field is set to the value indicated for emergency calls, shall reject the SIP re-INVITE request … and skip the remaining steps if neither of the following conditions are true: a) the SIP re-INVITE request does contains an authorised request for an MCVideo emergency call as determined in step 2 above; or b) the originating MCVideo user is in an in-progress emergency private call state with the targeted MCVideo user; 5) if the SIP re-INVITE request contains an emergency indication set to a value of "true" and the originating MCVideo user is not in an in-progress emergency private call state with the targeted MCVideo user: a) shall cache the information that the MCVideo user is in an in-progress emergency private call state with the targeted MCVideo user; and b) if the SIP re-INVITE request contains an alert indication set to "true" and this is an authorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall cache the information that the MCVideo user has sent an MCVideo emergency alert to the targeted user; and 6) shall send a SIP re-INVITE invite towards the MCVideo user listed in the MIME resource-lists body of received SIP re-INVITE request as specified in clause 11.1.1.4.5. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 237 Upon receiving a SIP 200 (OK) response for the SIP re-INVITE request and if the SIP response has not yet been sent to the inviting MCVideo client, the controlling MCVideo function: 1) shall generate a SIP 200 (OK) response to the SIP re-INVITE request as specified in the clause 6.3.3.2.3 before continuing with the rest of the steps; 2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP re-INVITE request containing the current media parameters used by the existing session; … 4) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and 5) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [4]. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18: The controlling MCVideo function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [4]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.4.4] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) alert indication in an incoming SIP INVITE request refers to the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receiving a SIP re-INVITE request with an emergency indication set to a value of "false", the controlling MCVideo function: 1) shall validate that the received SDP offer includes at least one media stream for which the media parameters and at least one codec or media format is acceptable by the controlling MCVideo function and if not, reject the request … and skip the rest of the steps; 2) shall validate the request as described in clause 6.3.3.1.17; … 4) shall reject the SIP re-INVITE request … if a Resource-Priority header field is included in the received SIP re- INVITE request set to the value configured for emergency calls, and skip the remaining steps; and 5 if the SIP re-INVITE request contains an authorised request for an MCVideo emergency private call cancellation as determined by clause 6.3.3.1.13.4: a) shall clear the cache of the MCVideo ID of the originator of the MCVideo emergency private call that is no longer in an in-progress emergency private call state with the targeted MCVideo user; and b) if the SIP re-INVITE request contains an alert indication set to "false" and this is an authorised request for an MCVideo emergency alert cancellation meeting the conditions specified in clause 6.3.3.1.13.3: i) if the received SIP re-INVITE request contains an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, shall clear the cache of the MCVideo ID of MCVideo user identified by the <originated-by> element as having an outstandingMCVideo emergency alert; and ii) if the received SIP re-INVITE request does not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, clear the cache of the MCVideo ID of the sender of the SIP re-INVITE request as having an outstanding MCVideo emergency alert; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 238 6) shall send a SIP re-INVITE request towards the MCVideo user listed in the MIME resource-lists body of received SIP re-INVITE request as specified in clause 11.1.1.4.6. Upon receiving a SIP 200 (OK) response for the SIP re-INVITE request and if the SIP response has not yet been sent to the inviting MCVideo client, the controlling MCVideo function: 1) shall generate a SIP 200 (OK) response to the SIP re-INVITE request as specified in the clause 6.3.3.2.3 before continuing with the rest of the steps; 2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP re-INVITE request as specified in the clause 6.3.3.2.2; … 4) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and 5) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [4]. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18. The controlling MCVideo function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [4]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.4.5] "This clause describes the procedures for sending a re-INVITE request to an MCVideo user in an MCVideo private call for the purpose of upgrading the session to an emergency private call session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 11.1.1.4.3. The controlling MCVideo function: 1) shall generate a SIP re-INVITE request as specified in clause 6.3.3.1.9; 2) if the received SIP re-INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body to the outgoing re-INVITE request; 3) if the received SIP re-INVITE request contains an authorised request for an MCVideo emergency private call as determined by clause 6.3.3.1.13.2: a) shall set the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; b) if the received SIP INVITE request contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, perform the procedures specified in clause 6.3.3.1.12; and c) if the received SIP INVITE request did not contain an alert indication or contains an alert indication set to a value of "true" and is not an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; 4) shall include a Resource-Priority header field populated with the values for an MCVideo emergency private call as specified in clause 6.3.3.1.19, if the received SIP re-INVITE request contains an authorised request for an MCVideo emergency private call as determined in step 2 above; and 5) shall send the SIP re-INVITE request towards the core network according to 3GPP TS 24.229 [4]. Upon receiving SIP 200 (OK) response for the SIP re-INVITE request the controlling MCVideo function: 1) shall cache the contact received in the Contact header field." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 239 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.4.6] "This clause describes the procedures for sending a re-INVITE request to an MCVideo user in an MCVideo emergency private call for the purpose of downgrading the session to a normal priority private call session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 11.1.1.4.4. The controlling MCVideo function: 1) shall generate a SIP re-INVITE request as specified in clause 6.3.3.1.9; 2) if the received SIP re-INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body to the outgoing re-INVITE request. 3) if the received SIP re-INVITE request contains an authorised request for an MCVideo emergency private call cancellation as determined by clause 6.3.3.1.13.4: a) shall set the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; b) if the received SIP INVITE request contains an alert indication set to a value of "false" and this is an authorised request for an MCVideo emergency alert cancellation meeting the conditions specified in clause 6.3.3.1.13.3: i) shall set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; and ii) if the received SIP request contains an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, copy the contents of the received <originated-by> element to an <originated-by> element in the application/vnd.3gpp.mcvideo- info+xml MIME body in the outgoing SIP re-INVITE request; c) if the received SIP INVITE request contains an alert indication set to a value of "false" and is not an authorised request for an MCVideo emergency alert cancellation meeting the conditions specified in clause 6.3.3.1.13.3, shall set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; 4) shall include a Resource-Priority header field populated with the values for a normal MCVideo private call as specified in clause 6.3.3.1.19, if the received SIP re-INVITE request contains an authorised request for an MCVideo emergency private call cancellation as determined in step 3 above; and 5) shall send the SIP re-INVITE request towards the core network according to 3GPP TS 24.229 [4]. Upon receiving SIP 200 (OK) response for the SIP re-INVITE request the controlling MCVideo function: 1) shall cache the contact received in the Contact header field." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.4.2.1.1] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.1.6." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.4.2.2.1] "Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.2.8.1." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.4.3.1] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.3.2.2] "When an MCVideo call is established a new instance of the transmission control server state machine for 'general transmission control operation' is created. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 240 For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' is added. When an MCVideo call is established a new instance of the transmission control server state machine for 'general reception control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic reception control operation towards the transmission participant' is added. If the optional "mc_queueing" feature is supported and has been negotiated as specified in clause 14, the transmission control server could queue the implicit transmission control request for the media-transmission control entity. The original initial SIP INVITE request or SIP REFER request to establish an MCVideo chat group call or to rejoin an ongoing MCVideo call is not handled as an implicit transmission control request message by the transmission control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request. The permission to send media to the inviting MCVideo client due to implicit transmission control request is applicable to both confirmed indication and unconfirmed indication. When the first unconfirmed indication is received from the invited participating MCVideo function (see 3GPP TS 24.281 [2]) the transmission control server optionally can give an early indication to send RTP media packets, to the inviting MCVideo client. If an early indication to send RTP media packets is given to the inviting MCVideo client, the transmission participant is granted the permission to send media and the MCVideo server buffers RTP media packets received from the MCVideo client at least until the first invited MCVideo client accepts the invitation or until the RTP media packet buffer exceeds it maximum limit to store RTP media packets. If the MCVideo server does not support or does not allow media buffering then when an early indication to send RTP media packets is not given to the inviting MCVideo client, the transmission participant is granted the permission to send media when the first invited MCVideo client accepts the media. Before the transmission control server sends the first transmission control message in the MCVideo call, the transmission control server has to assign itself a SSRC identifier to be included in media transmission control messages and quality feedback messages if the MCVideo server is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3]. The transmission participant and the transmission control server can negotiate the maximum priority level that the transmission participant is permitted to request. The transmission control server can pre-empt the current sender based on the negotiated maximum priority level that the transmission participant is permitted to request and the priority level included in the Transmission Media Request message. NOTE: The maximum priority level that a transmission participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the controlling MCVideo function from the group management server as described in 3GPP TS 24.481 [12] and service configuration data retrieved by the controlling MCVideo function from the configuration management server as described in 3GPP TS 24.484 [13]. The transmission participant and the transmission control server can negotiate queueing of Transmission requests using the "mc_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the transmission control server queues the transmission control request if a Transmission Media Request message is received when another transmission participant has the transmission and the priority of the current speaker is the same or higher." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 241 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 242 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.2.1.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.2.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-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 Make the SS-UE1 (MCVideo Client) request the establishment of a private call to SS-UE2 (MCVideo Client) with automatic commencement mode and implicit transmission request. - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to establish a private call with automatic commencement mode and implicit transmission control request according to option b.ii of note in Annex A, Table A.3.1.3-1? - - 1 P 3 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 243 St Procedure Message Sequence TP Verdict U - S Message 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 2 P 5 Make the SS-UE1 (MCVideo Client) request upgrade of the call to an emergency private call with implicit transmission request. - - - - 6 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.3.1.3-1 to upgrade the call to an emergency private call with implicit transmission request according to option b.ii of note in Annex A, Table A.3.1.3-1? - - 3 P 7 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 8 Check: Does the IUT (MCVideo Server) correctly perform procedure ' MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1? - - 2 P 9 Make the SS-UE1 (MCVideo Client) request downgrade of the call to a normal private call. - - - - 10 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.3.1.3-1 to downgrade the call without implicit transmission request, with option a of note on Table A.3.1.3-1? - - 4 P 11 Make the SS-UE1 (MCVideo Client) release the call. - - - - 12 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 5 P |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.2.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.2.1.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with condition PRIVATE-CALL. NOTE: Condition is also applied to all body parts. Table 6.2.1.3.3-2: SIP INVITE from the IUT (MCVideo Server) (Step 2, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition PRIVATE-CALL. NOTE: Condition is also applied to all body parts. Table 6.2.1.3.3-3: SIP 200 (OK) from the SS-UE2 (Steps 2, 6 and 10 Table 6.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7, with condition PRIVATE-CALL. NOTE: Condition is also applied to all body parts. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 244 Table 6.2.1.3.3-4: SIP 200 (OK) from the IUT (MCVideo Server) (Steps 2, 6 and 10, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9, with condition PRIVATE-CALL. NOTE: Condition is also applied to all body parts. Table 6.2.1.3.3-5: SIP re-INVITE from the SS-UE1 (Step 6, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with conditions PRIVATE-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 6.2.1.3.3-6: SIP re-INVITE from the IUT (MCVideo Server) (Step 6, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition PRIVATE-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 6.2.1.3.3-7: SIP re-INVITE from the SS-UE1 (Step 10, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with conditions PRIVATE-CALL and re_INVITE. NOTE: Conditions are also applied to all body parts. Table 6.2.1.3.3-8: SIP re-INVITE from the IUT (MCVideo Server) (Step 10, Table 6.2.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition PRIVATE-CALL and re_INVITE. NOTE: Conditions are also applied to all body parts. Table 6.2.1.3.3-9: Transmission Idle from the IUT (MCVideo Server) (Step 8, Table 6.2.1.3.2-1; Steps 4 and 5, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-6 with condition EMERGENCY-CALL. Table 6.2.1.3.3-10: Transmission Granted from the IUT (MCVideo Server) (Step 6, Table 6.2.1.3.2-1; Step 2a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.1.4-11 (note), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. Table 6.2.1.3.3-11: Media Transmission Notification from the IUT (MCVideo Server) (Step 6, Table 6.2.1.3.2-1; Step 3a1, Annex A, Table A.3.1.3-1) Derivation Path: Annex A, Table A.3.1.4-12 (note), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 245 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.3 Emergency Alert | 6.3.1 MCVideo Server - MCVideo Client / Emergency Alert / Cancel Emergency Alert |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.3.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 and having to support emergency alert} ensure that { when { SS-UE1 (MCVideo Client) requests to send an emergency alert by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) and sends SIP MESSAGE message to request an emergency alert for SS-UE1 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having to support emergency alert} ensure that { when { SS-UE1 (MCVideo Client) requests to cancel an emergency alert by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) and sends SIP MESSAGE message to cancel an emergency alert for SS-UE1 (MCVideo Client) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.3.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 11.2.2.1, 11.2.2.2, 11.2.2.3, 11.2.3.1, 11.2.3.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 11.2.2.1] "Upon receipt of a "SIP MESSAGE request for emergency notification for originating participating MCVideo function", the participating MCVideo function: … NOTE 1: if the SIP MESSAGE request contains an emergency indication set to a value of "true" or an alert indication set to a value of "true", the participating MCVideo function can, according to local policy, choose to accept the request. 2) shall determine the MCVideo ID of the calling 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 2: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. 3) if the MCVideo user is not affiliated with the MCVideo group as determined by clause 9.2.2.2.11, shall perform the actions specified in clause 9.2.2.2.12 for implicit affiliation; … NOTE 3: N2 is the total number of MCVideo groups that an MCVideo user can be affiliated to simultaneously as specified in 3GPP TS 23.379 [3]. NOTE 4: As this is a request for MCVideo emergency services, the participating MCVideo function can choose to accept the request. 5) shall determine the public service identity of the controlling MCVideo function associated with the group identity in the received SIP MESSAGE request; 6) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [33]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 246 7) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCVideo function associated with the group identified by the <mcvideo-request-uri> element contained in the <mcvideoinfo> element containing the <mcvideo-Params> element of the application/vnd.3gpp.mcvideo-info+xml MIME body in the incoming SIP MESSAGE request; 8) shall copy the contents of the application/vnd.3gpp.mcvideo-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request; 9) shall set the <mcvideo-calling-user-id> element of the <mcvideoinfo> element containing the <mcvideo- Params> element to the MCVideo ID determined in step 2) above; 10) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-location-info+xml MIME body as specified in clause F.3 shall copy the contents of the application/vnd.3gpp.mcvideo-location-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcvideo-location-info+xml MIME body included in the outgoing SIP MESSAGE request; 11) shall set the P-Asserted-Identity in the outgoing SIP MESSAGE request to the public user identity in the P- Asserted-Identity header field contained in the received SIP MESSAGE request; and 12) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [11]. Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 10): 1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [11] with the follow clarifications: a) shall include the public user 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; 2) if the procedures of clause 9.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 9.2.2.2.13; and 3) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]. …" [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 11.2.2.2] "In the procedures in this clause: 1) emergency indication in an incoming SIP MESSAGE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) alert indication in an incoming SIP MESSAGE request refers to the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP MESSAGE requests for emergency notification for terminating participating MCVideo function", the participating MCVideo function: … 2) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCVideo ID and public user identity; … 4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11; and 5) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]. Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCVideo function shall follow the procedures specified in 3GPP TS 24.229 [11]." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 247 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 11.2.2.3] "Upon receipt of a SIP MESSAGE request routed to the terminating participating MCVideo function as a result of initial filter criteria with the Request-URI set to the public service identity of the terminating participating MCVideo function and the SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <alert-ind-rcvd> element present, the participating MCVideo function: … 2) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCVideo ID and public user identity; … 4) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [33] and: a) 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 [6] that were received (if any) in the incoming SIP MESSAGE request; b) shall set the Request-URI of the outgoing SIP MESSAGE request to the public user identity associated to the MCVideo ID of the MCVideo user that was in the Request-URI of the incoming SIP MESSAGE request; c) shall copy the contents of the application/vnd.3gpp.mcvideo-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP MESSAGE request; and d) 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; and 5) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]. Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCVideo function shall follow the procedures specified in 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 11.2.3.1] "Upon receipt of a "SIP MESSAGE request for emergency notification for controlling MCVideo function", the controlling MCVideo function: … 3) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "false", shall perform the procedures specified in clause 11.2.3.2 and skip the rest of the steps; 4) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "true": … b) if the received SIP MESSAGE request is an authorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1: i) if the sending MCVideo user identified by the <mcvideo-calling-user-id> element included in the application/vnd.3gpp.mcvideo-info+xml MIME body is not affiliated with the MCVideo group identified by the <mcvideo-request-uri> element of the MIME body as determined by the procedures of clause 6.3.6: I) shall check if the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined by clause 9.2.2.3.6; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 248 … III) if the procedures of clause 9.2.2.3.6 determined the MCVideo user to be eligible to be implicitly affiliated to the MCVideo group shall, perform the implicit affiliation as specified in clause 9.2.2.3.7; ii) for each of the other affiliated members of the group: A) generate an outgoing SIP MESSAGE request notification of the MCVideo user's emergency alert indication as specified in clause 6.3.3.1.11 with the clarifications of clause 6.3.3.1.12; B) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with the <mcvideo- calling-user-id> element set to the value of the <mcvideo-calling-user-id> element in the received SIP MESSAGE request; and C) send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [11]; iii) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [11] with the following clarifications: A) shall cache the information that the MCVideo user has initiated an MCVideo emergency alert; iv) shall send the SIP 200 (OK) response to the received SIP MESSAGE according to rules and procedures of 3GPP TS 24.229 [11]. v) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of an emergency alert, and shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body: A) the <alert-ind> element set to a value of "true"; B) the <alert-ind-rcvd> element set to a value of true; and C) the <mcvideo-client-id> element with the MCVideo client ID that was included in the incoming SIP MESSAGE request; and vi) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [11]. Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCVideo function shall follow the procedures specified in 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 11.2.3.2] "Upon receipt of a "SIP MESSAGE request for emergency notification for controlling MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "false", the controlling MCVideo function: 1) if the received SIP MESSAGE request is an unauthorised request for an MCVideo emergency alert cancellation as specified in clause 6.3.3.1.13.1: … b) and if the received SIP MESSAGE request contains an <emergency-ind> element and is an authorised request for an MCVideo emergency call cancellation as specified in clause 6.3.3.1.13.4 and the in- progress emergency state of the MCVideo group is set to a value of "true": i) shall set the in-progress emergency state of the group to a value of "false"; ii) shall clear the cache of the MCVideo ID of the MCVideo user that triggered the setting of the in- progress emergency state of the MCVideo group to "true"; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 249 iii) shall generate SIP re-INVITE requests to the other affiliated and joined members of the MCVideo group as specified in clause 6.3.3.1.6. The MCVideo controlling function: A) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and B) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.380 [5]; iv) for each of the affiliated but not joined members of the group shall: A) generate a SIP MESSAGE request notification of the cancellation of the MCVideo user's emergency call as specified in clause 6.3.3.1.11; B) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with the <mcvideo- calling-user-id> element set to the value of the <mcvideo-calling-user-id> element in the received SIP MESSAGE request; and C) shall include an <emergency-ind> element set to a value of "false" in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP MESSAGE request; v) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; vi) shall send the SIP 200 (OK) response to the received SIP MESSAGE as specified in 3GPP TS 24.229 [11] and skip the rest of the steps; vii) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of the request for emergency alert cancellation viii) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP MESSAGE request: A) the <alert-ind> element set to a value of "true"; B) the <alert-ind-rcvd> element set to a value of true; C) the <emergency-ind> element set to a value of "false"; and D) the <mcvideo-client-id> element with the MCVideo client ID that was included in the incoming SIP MESSAGE request; and ix) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [11]; and 2) if the received SIP MESSAGE request is an authorised request for an MCVideo emergency alert cancellation as specified in clause 6.3.3.1.13.1: a) if the received SIP MESSAGE request contains an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, shall clear the cache of the MCVideo ID of the MCVideo user identified by the <originated-by> element as having an outstanding MCVideo emergency alert; b) if the received SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, clear the cache of the MCVideo ID of the sender of the SIP MESSAGE request as having an outstanding MCVideo emergency alert; c) if the received SIP MESSAGE request does not contain an <emergency-ind> element or is an unauthorised request for an MCVideo emergency call cancellation as specified in clause 6.3.3.1.13.4, for each of the affiliated but not joined members of the group shall: i) generate a SIP MESSAGE request notification of the cancellation of the MCVideo user's emergency alert as specified in clause 6.3.3.1.11; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 250 ii) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with the <mcvideo-calling-user-id> element set to the value of the <mcvideo-calling-user-id> element in the received SIP MESSAGE request; iii) if the received SIP MESSAGE request contains an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, copy the contents of the received <originated-by> element to an <originated-by> element in the application/vnd.3gpp.mcvideo- info+xml MIME body in the outgoing SIP MESSAGE request; iv) shall include an <alert-ind> element set to a value of "false" in the application/vnd.3gpp.mcvideo- info+xml MIME body in the outgoing SIP MESSAGE request; and v) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; d) if the received SIP MESSAGE request contains an <emergency-ind> element and is an authorised request for an MCVideo emergency call cancellation as specified in clause 6.3.3.1.13.4 and the in- progress emergency state of the MCVideo group is set to a value of "true": i) shall set the in-progress emergency state of the group to a value of "false"; ii) cache the information that the MCVideo user has cancelled the outstanding in-progress emergency state of the group; iii) shall generate SIP re-INVITES requests to the other affiliated and joined members of the MCVideo group as specified in clause 6.3.3.1.6. The MCVideo controlling function: A) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and B) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and iv) for each of the affiliated but not joined members of the group shall: A) generate a SIP MESSAGE request notification of the cancellation of the MCVideo user's emergency call as specified in clause 6.3.3.1.11; B) include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with the <mcvideo-calling-user-id> element set to the value of the <mcvideo-calling-user-id> element in the received SIP MESSAGE request; C) if the received SIP MESSAGE request contains an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, copy the contents of the received <originated-by> element to an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP MESSAGE request; D) include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <alert-ind> element set to a value of "false"; and E) shall include an <emergency-ind> element set to a value of "false" in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP MESSAGE request; e) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; f) shall send the SIP 200 (OK) response to the received SIP MESSAGE as specified in 3GPP TS 24.229 [11]. g) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of the request for emergency alert cancellation; h) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body, the <alert-ind> element set to a value of "false" and the <alert-ind-rcvd> set to "true"; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 251 i) shall populate the <mcvideo-client-id> element with the MCVideo client ID that was included in the incoming SIP MESSAGE request; j) if the received SIP MESSAGE request contains an <emergency-ind> element of the <mcvideoinfo> element set to a value of "false": A) if this is an authorised request for an MCVideo emergency call cancellation as specified in clause 6.3.3.1.13.4, shall include an <emergency-ind> element set to a value of "false" in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP MESSAGE request; and B) otherwise, if this is an unauthorised request for an MCVideo emergency call cancellation as specified in clause 6.3.3.1.13.4, and the in-progress emergency state of the group is set to a value of "true", shall include an <emergency-ind> element set to a value of "true" in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP MESSAGE request; and k) shall send the SIP MESSAGE request according to according to the rules and procedures of 3GPP TS 24.229 [11]. Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCVideo function shall follow the procedures specified in 3GPP TS 24.229 [11]." |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.3.1.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.3.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) are affiliated to the Prearranged group. - The IUT (MCVideo Server) is the controlling server of the Prearranged group. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 252 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.3.1.3.2 Test procedure sequence | Table 6.3.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the SS-UE1 (MCVideo Client) send an emergency alert to group A. - - - - 2 Check: Does the MCVideo Server correctly perform 'MCX E2E SIP MESSAGE Request - Accept' as described in Annex A, Table A.2.11.3-1 to send an emergency alert for SS-UE1 (MCVideo Client)? - - 1 P 3 Make the SS-UE1 (MCVideo Client) cancel an emergency alert. - - - - 4 Check: Does the MCVideo Server correctly perform 'MCX E2E SIP MESSAGE Request - Accept' as described in Annex A, Table A.2.11.3-1 to cancel the emergency alert of SS-UE1 (MCVideo Client)? - - 2 P |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.3.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.3.1.3.3-1: SIP MESSAGE from the SS-UE1 (Step 2, Table 6.1.1.11.3.2-1; Step 1, Annex A, Table A.2.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, with conditions MCVIDEO and LOCATION_REPORT Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info ETSI TS 124 281 [8] (3GPP TS 24.281) clause F.1 MIME-part-body MCVideo-Info as described in Table 6.3.1.3.3-2 MIME body part Location-info MIME-part-body Location-info as described in Table 6.3.1.3.3-3 Table 6.3.1.3.3-2: MCVideo-Info in SIP MESSAGE (Table 6.3.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.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_Group_A_ID ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.1.1 mcvideo-client-id Encrypted (note) <mcvideo- client-id> with mcvideoString set to px_MCVideo_Client_A_ID ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.1.1 alert-ind Encrypted (note) <alert-ind> with mcvideoBoolean set to true ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.1.1 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 151-1 V1.1.1 (2026-02) 253 Table 6.3.1.3.3-3: Location-Info in SIP MESSAGE (Table 6.3.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.1-2 Information Element Value/remark Comment Reference Condition location-info Report CurrentLocation CurrentCoordinate longitude Encrypted (note) <longitude> with px_MCX_CoordinateLongitude _Client_A value latitude Encrypted (note) <latitude> with px_MCX_CoordinateLatitude_C lient_A value NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.1-2A. Table 6.3.1.3.3-4: SIP MESSAGE from the IUT (MCVideo-Server) to SS-UE1 (Step 2, Table 6.1.1.11.3.2-1; Step 3, Annex A, Table A.2.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with conditions MCVIDEO and ACCEPT-CONTACT-WITH-MEDIA-FEATURE-TAG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.3.1.3.3-5 Table 6.3.1.3.3-5: MCVideo-Info in SIP MESSAGE (Table 6.3.1.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-calling-user-id not present ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.1 alert-ind Encrypted (note) <alert-ind> with mcvideoBoolean set to true ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.1 mcvideo-client-id Encrypted (note) <mcvideo- client-id> with mcvideoString set to the client-id as received from the SS-UE1. ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.1 alert-ind-rcvd true ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.1 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2A. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 254 Table 6.3.1.3.3-6: SIP MESSAGE from the IUT (MCVideo Server) to SS-UE2 (Step 2, Table 6.1.1.11.3.2-1; Step 5, Annex A, Table A.2.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with condition MCVIDEO and LOCATION-INFO Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.3.1.3.3-7 MIME body part Location-info MIME-part-body Location-info as described in Table 6.3.1.3.3-3 Table 6.3.1.3.3-7: MCVideo-Info in SIP MESSAGE (Table 6.3.1.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-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_B ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.2.2 mcvideo-calling-user-id Encrypted (note) <mcvideo- calling-user-id> with mcvideoURI set to px_MCVideo_ID_User_A ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.1 mcvideo-calling-group- id Encrypted (note) < mcvideo- calling-group-id> with mcvideoURI set to px_MCVideo_Group_A_ID mc-org px_MCX_DomainName_Organi zation_A Indicates the organization an MCVideo user belongs to ETSI TS 124 281 [8] (3GPP TS 24.281) clause 6.3.3.1.11 alert-ind Encrypted (NOTE 1) <alert-ind> with mcvideoBoolean set to true NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2A. Table 6.3.1.3.3-8: SIP MESSAGE from the SS-UE1 (Step 4, Table 6.1.1.11.3.2-1; Step 1, Annex A, Table A.2.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, with condition MCVIDEO Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info ETSI TS 124 281 [8] (3GPP TS 24.281) clause F.1 MIME-part-body MCVideo-Info as described in Table 6.3.1.3.3-9 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 255 Table 6.3.1.3.3-9: MCVideo-Info in SIP MESSAGE (Table 6.3.1.3.3-8) 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_Group_A_ID ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.1.2 mcvideo-client-id Encrypted (note) <mcvideo- client-id> with mcvideoString set to px_MCVideo_Client_A_ID ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.1.2 alert-ind Encrypted (note) <alert-ind> with mcvideoBoolean set to false ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.1.2 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 6.3.1.3.3-10: SIP MESSAGE from the IUT (MCVideo-Server) to SS-UE1 (Step 4, Table 6.1.1.11.3.2-1; Step 3, Annex A, Table A.2.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with conditions MCVIDEO and ACCEPT-CONTACT-WITH-MEDIA-FEATURE-TAG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.3.1.3.3-11 Table 6.3.1.3.3-11: MCVideo-Info in SIP MESSAGE (Table 6.3.1.3.3-10) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-calling-user- id not present ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.2 emergency-ind Encrypted (note) <emergency- ind> with mcvideoBoolean set to false ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.2 alert-ind Encrypted (note) <alert-ind> with mcvideoBoolean set to false ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.2 mcvideo-client-id Encrypted (note) <mcvideo-client- id> with mcvideoString set to the client-id as received from the SS- UE1. ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.2 alert-ind-rcvd true ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.2 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2A. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 256 Table 6.3.1.3.3-12: SIP MESSAGE from the IUT (MCVideo Server) to SS-UE2 (Step 4, Table 6.1.1.11.3.2-1; Step 5, Annex A, Table A.2.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1 with condition MCVIDEO Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.3.1.3.3-13 Table 6.3.1.3.3-13: MCVideo-Info in SIP MESSAGE (Table 6.3.1.3.3-12) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-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_B ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.2.2 mcvideo-calling-user-id Encrypted (note) <mcvideo- calling-user-id> with mcvideoURI set to px_MCVideo_ID_User_A ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.2 mcvideo-calling-group-id Encrypted (note) < mcvideo- calling-group-id> with mcvideoURI set to px_MCVideo_Group_A_ID alert-ind Encrypted (note) <alert-ind> with mcvideoBoolean set to false ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.2 emergency-ind Encrypted (note) <emergency-ind> with mcvideoBoolean set to false ETSI TS 124 281 [8] (3GPP TS 24.281) clause 11.2.3.2 NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2A. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4 Video Push | 6.4.1 MCVideo Server - MCVideo Client / Video push call / One-to-one video push call |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCVideo client ) initiates a video push call to push a video to the SS-UE2 (MCVideo Client) } then { IUT (MCVideo Server) accepts the video push call from initiator and pushes a video to the SS-UE2 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established a one-to-one video push call } ensure that { when { the SS-UE2 (MCVideo client ) sends receive media request } then { IUT (MCVideo Server) responds with transmission control ack to the SS-UE2 (MCVideo client) } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 257 (3) with { IUT (MCVideo Server) having established a one-to-one video push call } ensure that { when { the SS-UE1 (MCVideo client) ends the video push call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the SS-UE2 (MCVideo Client) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 13.2.3.1.1, 10.2.2.3.1.1, 13.2.3.1.2, 10.2.2.3.2, 13.2.3.1.3, 13.2.3.2.1, 10.2.2.4.1, 13.2.3.2.2, 10.2.5.4. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 13.2.3.1.1] "Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-to-one video push", the participating MCVideo function shall perform the procedures of clause 10.2.2.3.1.1." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.3.1.1] "Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "private", the participating MCVideo function: … 3) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request and shall authorise the user; NOTE 3: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 5) shall: a) if the <session-type> is set to "private", determine that the call is a private call; 6) if the call is a: a) private call, determine the public service identity of the controlling MCVideo function for the private call service associated with the originating user's MCVideo ID identity; … 12) shall validate the media parameters and if the MCVideo video media codec is not offered in the "SIP INVITE request for originating participating MCVideo function" shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; 13) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3 with the following clarifications: a) if the conditions in step 12) above were executed and the participating MCVideo function determined that the "uri" attribute of only one of the <entry> elements of the application/resource-lists MIME body matched with an <entry> element of the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) then the <session-type> in the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request generated in clause 6.3.2.1.3 is set to "private"; and b) if the conditions in step 12) above were executed, then only the <entry> element(s) of the application/resource-lists MIME body that have a "uri" attribute that matched with an <entry> elements of the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) are included in the application/resource-lists MIME body in the SIP INVITE request generated in clause 6.3.2.1.3; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 258 14) shall set the Request-URI to the public service identity of the controlling MCVideo function hosting the private call service as determined by step 6); 15) shall set the <mcvideo-calling-user-id> element in an application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 16) if the call is a private call and: a) if a Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was received in the incoming SIP INVITE request with a value of "Manual", shall not include a Priv-Answer-Mode header field in the outgoing SIP INVITE request; … c) if the <allow-force-auto-answer> element of the <ruleset> element is present in the MCVideo user profile document with the value "true" (see the MCVideo user profile document in 3GPP TS 24.484 [25]) on the participating MCVideo function, and the Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was received in the incoming SIP INVITE request with a value of "Auto", shall include the Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request; d) if a Priv-Answer-Mode header field containing the value of "Auto" has not been included in the outgoing SIP INVITE request as specified in step 17) above and the incoming "SIP INVITE request for originating participating MCVideo function" contained an Answer-Mode header field as specified in IETF RFC 5373 [27], then shall populate the Answer-Mode header field of the outgoing SIP INVITE request with the contents of the Answer-Mode header field from the incoming "SIP INVITE request for originating participating MCVideo function"; 17) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for originating participating MCVideo function", as specified in clause 6.3.2.1.1.1; 18) shall include a Resource-Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field if included in the SIP INVITE request from the MCVideo client; and 19) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. Upon receiving a SIP 180 (Ringing) response, the participating MCVideo function: 1) shall generate a SIP 180 (Ringing) response to the SIP INVITE request as specified in the clause 6.3.2.1.5.1; 2) shall include the P-Asserted-Identity header field as received in the incoming SIP 180 (Ringing) response; 3) shall include Warning header field(s) received in the incoming SIP 180 (Ringing) response; and 4) shall forward the SIP 180 (Ringing) response to the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response, the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2; 2) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 3) shall include Warning header field(s) received in the incoming SIP 200 (OK) response; 4) shall include the P-Asserted-Identity header field received in the incoming SIP 200 (OK) response into the outgoing SIP 200 (OK) response; 5) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 6) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 8) shall start the SIP session timer according to rules and procedures of IETF RFC 4028 [23]. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 259 The participating MCVideo function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 13.2.3.1.2] "Upon receipt of a "SIP INVITE request for terminating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-to-one video push", the participating MCVideo function shall perform the procedures of clause 10.2.2.3.2." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.3.2] "This clause covers both on demand session and pre-established session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: … 2) shall check the presence of the isfocus media feature tag in the URI of the Contact header field … … 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; … 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if one of the following conditions are met: a) "SIP INVITE request for terminating participating MCVideo function" contains an Answer-Mode header field with the value "Auto"; b) "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; or c) "SIP INVITE request for terminating participating MCVideo function" contains a Priv-Answer-Mode header field with the value "Auto"; and 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if either of the following conditions are met: a) "SIP INVITE request for terminating participating MCVideo function" contains an Answer-Mode header field with the value "Manual"; b) "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"; or c) "SIP INVITE request for terminating participating MCVideo function" contains a Priv-Answer-Mode header field with the value "Manual"." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 13.2.3.1.3] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 10.2.4. Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 10.2.5." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 260 [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 13.2.3.2.1] "Upon receipt of a "SIP INVITE request for controlling MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-to-one video push", the controlling MCVideo function: 1) shall check whether the public service identity contained in the Request-URI is allocated for one-to-one video push call and perform the actions specified in clause 6.3.7.1 if it is not allocated and skip the rest of the steps; 2) shall check whether the MCVideo ID of the MCVideo calling user in the <mcvideo-calling-user-id> is authorised to initiate the one-to-one video push call… 3) shall check whether the MCVideo ID of the MCVideo called party user in the <mcvideo-called-party-id> is authorised to receive the one-to-one video push call, … 4) shall allocate an MCVideo session identity for the MCVideo session; and 5) shall invite the MCVideo user listed in the MIME resource-lists body of received SIP INVITE request as specified in clause 10.2.2.4.1." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.4.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 10.2.2.4.2 The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; NOTE 1: As a result of calling clause 6.3.3.1.2, the <mcvideo-calling-user-id> containing the calling user's MCVideo ID is copied into the outgoing SIP INVITE. 2) if the received SIP INVITE request contains an authorised request for an MCVideo emergency private call as determined by clause 6.3.3.1.13.2: a) shall set the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; b) if the received SIP INVITE request contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, perform the procedures specified in clause 6.3.3.1.12; and c) if the received SIP INVITE request did not contain an alert indication or contains an alert indication set to a value of "true" and is not an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; 3) shall copy the MCVideo ID of the MCVideo user listed in the MIME resources body of the incoming SIP INVITE request, into the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited; NOTE 2: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 3: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 5) shall copy the public user identity of the calling MCVideo user from the P-Asserted-Identity header field of the incoming SIP INVITE request into the P-Asserted-Identity header field of the SIP INVITE request; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 261 6) shall include a Resource-Priority header field populated with the values for an MCVideo emergency private call as specified in clause 6.3.3.1.19, if either of the following conditions is met: a) if the received SIP INVITE request contains an authorised request for an MCVideo emergency private call as determined in step 2 above; or b) the originating MCVideo user is in an in-progress emergency private call state with the targeted MCVideo user; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; 8) shall send the SIP INVITE request towards the core network according to 3GPP TS 24.229 [11]; and 9) shall start a private call timer with a value set to the configured max private call duration for the user. Upon receiving SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall cache the contact received in the Contact header field; and 2) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. Upon expiry of the private call timer, the controlling MCVideo function shall follow the procedure for releasing private call session as specified in clause 10.2.5.4." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 13.2.3.2.2] "When the MCVideo session for one-to-one video push call needs to be released, the controlling MCVideo function shall perform the procedures of clause 10.2.5.4." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.5.4] "When the MCVideo session for private call needs to be released as specified in clause 6.3.8.2, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.5." |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.1.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - SS-UE1 (MCVideo Client) has a pre-recorded video that is available to push to another client. - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 262 Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.1.3.2 Test procedure sequence | Table 6.4.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCVideo Client) requests the establishment of a video push call to push a video to SS-UE2 (MCVideo Client). - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to push a video to SS-UE2 with implicit transmission control request according to option b.i of note in Annex A, Table A.3.1.3-1? - - 1 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Media Reception Request and Response' as described in Annex A, Table A.3.9.3-1 to start receiving media from SS-UE1 (MCVideo Client), in SS-UE2 (MCVideo Client)? - - 2 P 4 Make the SS-UE1 (MCVideo Client) release the call. - - - - 5 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 3 P |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications: Table 6.4.1.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with condition PRIVATE-CALL. NOTE 1: Condition is also applied to all body parts. Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP as described in Annex A, Table A.3.1.4-2 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.4.1.3.3-2 Table 6.4.1.3.3-2: MCVideo-Info in SIP INVITE (Table 6.4.1.3.3-1) Derivation Path: Annex A, Table A.3.1.4-3, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params session-type "one-to-one video push" ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 263 Table 6.4.1.3.3-3: SIP INVITE from the IUT (MCVideo Server) (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition PRIVATE-CALL. NOTE 1: Condition is also applied to all body parts. Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP as described in Annex A, Table A.3.1.4-5 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.4.1.3.3-4 Table 6.4.1.3.3-4: MCVideo-Info in SIP INVITE (Table 6.4.1.3.3-3) Derivation Path: Annex A, Table A.3.1.4-6 Information Element Value/remark Comment Reference Condition Mcvideoinfo mcvideo-Params session-type "one-to-one video push" Table 6.4.1.3.3-5: SIP 200 (OK) from the SS-UE2 (Step 2 Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7, with condition PRIVATE-CALL. NOTE: Condition is also applied to all body parts. Table 6.4.1.3.3-6: SIP 200 (OK) from the IUT (MCVideo Server) (Step 2, Table 6.4.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9, with condition PRIVATE-CALL. NOTE: Condition is also applied to all body parts. 6.4.2 MCVideo Server - MCVideo Client / Video push call / One-to-server video push call |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.2.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCVideo client ) initiates a video push call to push a video to the IUT (MCVideo Server) } then { IUT (MCVideo Server) responds with optional SIP 100 Trying and mandatory 200 (OK) message } } (2) with IUT (MCVideo Server) having established a one-to-server video push call } ensure that { when { the SS-UE1 (MCVideo client ) requests session establishment of video with automatic commencement mode and implicit transmission control to the IUT (MCVideo Server)} then { IUT (MCVideo Server) sends SIP INFO with push-url element to the SS-UE1 (MCVideo client) } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 264 (3) with { IUT (MCVideo Server) having established a one-to-server video push call } ensure that { when { the SS-UE1 (MCVideo client) ends the video push call by sending a SIP BYE message to the IUT (MCVideo Server) } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the SS-UE1 (MCVideo client) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.2.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 13.2.3.1.4, 10.2.2.3.1.1, 13.2.3.1.5, 13.2.3.2.3, 10.2.2.4.1, 13.2.3.2.4, 10.2.5.4. Unless otherwise stated, these are Rel-16 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 13.2.3.1.4] "Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-to-server video push", the participating MCVideo function shall perform the procedures of clause 10.2.2.3.1.1, with the following clarifications: 1) shall not check the <allow-private-call> element of the <ruleset> element; and 2) shall use the automatic commencement mode." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.3.1.1] "Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "private", the participating MCVideo function: … 3) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request and shall authorise the user; NOTE 3: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 5) shall: a) if the <session-type> is set to "private", determine that the call is a private call; 6) if the call is a: a) private call, determine the public service identity of the controlling MCVideo function for the private call service associated with the originating user's MCVideo ID identity; … 12) shall validate the media parameters and if the MCVideo video media codec is not offered in the "SIP INVITE request for originating participating MCVideo function" shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; 13) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3 with the following clarifications: a) if the conditions in step 12) above were executed and the participating MCVideo function determined that the "uri" attribute of only one of the <entry> elements of the application/resource-lists MIME body matched with an <entry> element of the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) then the <session-type> in the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request generated in clause 6.3.2.1.3 is set to "private"; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 265 b) if the conditions in step 12) above were executed, then only the <entry> element(s) of the application/resource-lists MIME body that have a "uri" attribute that matched with an <entry> elements of the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) are included in the application/resource-lists MIME body in the SIP INVITE request generated in clause 6.3.2.1.3; 14) shall set the Request-URI to the public service identity of the controlling MCVideo function hosting the private call service as determined by step 6); 15) shall set the <mcvideo-calling-user-id> element in an application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 16) if the call is a private call and: a) if a Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was received in the incoming SIP INVITE request with a value of "Manual", shall not include a Priv-Answer-Mode header field in the outgoing SIP INVITE request; … c) if the <allow-force-auto-answer> element of the <ruleset> element is present in the MCVideo user profile document with the value "true" (see the MCVideo user profile document in 3GPP TS 24.484 [25]) on the participating MCVideo function, and the Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was received in the incoming SIP INVITE request with a value of "Auto", shall include the Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request; d) if a Priv-Answer-Mode header field containing the value of "Auto" has not been included in the outgoing SIP INVITE request as specified in step 17) above and the incoming "SIP INVITE request for originating participating MCVideo function" contained an Answer-Mode header field as specified in IETF RFC 5373 [27], then shall populate the Answer-Mode header field of the outgoing SIP INVITE request with the contents of the Answer-Mode header field from the incoming "SIP INVITE request for originating participating MCVideo function"; 17) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for originating participating MCVideo function", as specified in clause 6.3.2.1.1.1; 18) shall include a Resource-Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field if included in the SIP INVITE request from the MCVideo client; and 19) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. Upon receiving a SIP 180 (Ringing) response, the participating MCVideo function: 1) shall generate a SIP 180 (Ringing) response to the SIP INVITE request as specified in the clause 6.3.2.1.5.1; 2) shall include the P-Asserted-Identity header field as received in the incoming SIP 180 (Ringing) response; 3) shall include Warning header field(s) received in the incoming SIP 180 (Ringing) response; and 4) shall forward the SIP 180 (Ringing) response to the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response, the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2; 2) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 3) shall include Warning header field(s) received in the incoming SIP 200 (OK) response; 4) shall include the P-Asserted-Identity header field received in the incoming SIP 200 (OK) response into the outgoing SIP 200 (OK) response; 5) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 266 6) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 8) shall start the SIP session timer according to rules and procedures of IETF RFC 4028 [23]. The participating MCVideo function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 13.2.3.1.5] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 10.2.4. Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 10.2.5." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 13.2.3.2.3] "Upon receipt of a "SIP INVITE request for controlling MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-to-server video push", the controlling MCVideo function: 1) shall check whether the public service identity contained in the Request-URI is allocated for one-to-server video push call and perform the actions specified in clause 6.3.7.1 … 2) shall check whether the MCVideo ID of the MCVideo calling user in the <mcvideo-calling-user-id> is authorised to initiate the one-to-server video push call, … 3) shall allocate an MCVideo session identity for the MCVideo session; 4) shall generate and send a SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; and 5) shall save the MCVideo media stream to a file. To send the URL of the file where the MCVideo media stream will be recorded, the controlling MCVideo function: 1) shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [11] and IETF RFC 6086 [21]; 2) shall include the Info-Package header field set to g.3gpp.mcvideo-info in the SIP INFO request; 3) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in annex F.1 with an <video-push-url> element set to the URL of the file where the MCVideo media stream will be recorded; and 4) shall send the SIP INFO request towards the inviting MCVideo client in the dialog of a SIP request for one-to- server video push call, as specified in 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.4.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 10.2.2.4.2 The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; NOTE 1: As a result of calling clause 6.3.3.1.2, the <mcvideo-calling-user-id> containing the calling user's MCVideo ID is copied into the outgoing SIP INVITE. 2) if the received SIP INVITE request contains an authorised request for an MCVideo emergency private call as determined by clause 6.3.3.1.13.2: a) shall set the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 267 b) if the received SIP INVITE request contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, perform the procedures specified in clause 6.3.3.1.12; and c) if the received SIP INVITE request did not contain an alert indication or contains an alert indication set to a value of "true" and is not an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; 3) shall copy the MCVideo ID of the MCVideo user listed in the MIME resources body of the incoming SIP INVITE request, into the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited; NOTE 2: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 3: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 5) shall copy the public user identity of the calling MCVideo user from the P-Asserted-Identity header field of the incoming SIP INVITE request into the P-Asserted-Identity header field of the SIP INVITE request; 6) shall include a Resource-Priority header field populated with the values for an MCVideo emergency private call as specified in clause 6.3.3.1.19, if either of the following conditions is met: a) if the received SIP INVITE request contains an authorised request for an MCVideo emergency private call as determined in step 2 above; or b) the originating MCVideo user is in an in-progress emergency private call state with the targeted MCVideo user; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; 8) shall send the SIP INVITE request towards the core network according to 3GPP TS 24.229 [11]; and 9) shall start a private call timer with a value set to the configured max private call duration for the user. Upon receiving SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall cache the contact received in the Contact header field; and 2) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. Upon expiry of the private call timer, the controlling MCVideo function shall follow the procedure for releasing private call session as specified in clause 10.2.5.4." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 13.2.3.2.4] "When the MCVideo session for one-to-server video push call needs to be released, the controlling MCVideo function shall perform the procedures of clause 10.2.5.4." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.5.4] "When the MCVideo session for private call needs to be released as specified in clause 6.3.8.2, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.5." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 268 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.2.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client). - SS-UE1 (MCVideo Client) has a pre-recorded video that is available to be pushed. - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) performs the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.2.3.2 Test procedure sequence | Table 6.4.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the SS-UE1 (MCVideo Client) request the establishment of a video push call to push a video to the IUT (MCVideo Server). - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Participating Terminated session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.4.3-1 to push a video from the SS-UE1 (MCVideo Client) to the IUT (MCVideo Server), with automatic commencement mode and implicit transmission control request according to option b.i of note in Annex A, Table A.3.4.3-1? - - 1 P 3 Check: Does the IUT (MCVideo Server) send a SIP INFO message that contains a video-push-url element? <-- SIP INFO 2 P 4 The SS-UE1 (MCVideo Client) responds with a SIP 200 (OK). --> SIP 200 (OK) - - 5 Make the SS-UE1 (MCVideo Client) release the call. - - - - 6 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated call release' as described in Annex A, Table A.2.15.3-1? - - 3 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 269 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.4.2.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.4.2.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.4.3-1; Step 1, Annex A, Table A.2.14.3-1) Derivation Path: Annex A, Table A.3.4.4-1, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP as described in Annex A, Table A.3.1.4-2 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.4.2.3.3-2 MIME body part not present Resource list NOTE: Condition is also applied to all body parts. Table 6.4.2.3.3-2: MCVideo-Info in SIP INVITE (Table 6.4.2.3.3-1) Derivation Path: Annex A, Table A.3.1.4-3, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params session-type "one-to-server video push" Table 6.4.2.3.3-3: SIP 200 (OK) from the IUT (MCVideo Server) (Step 2, Table 6.4.2.3.2-1; Step 1, Annex A, Table A.3.4.3-1, Step 3, Annex A, Table A.2.14.3-1) Derivation Path: Annex A, Table A.3.4.4-2, with condition PRIVATE-CALL. NOTE: Condition is also applied to all body parts. Table 6.4.2.3.3-4: SIP INFO from the IUT (MCVideo Server) (Step 3, Table 6.4.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.4-1, with condition MCVIDEO Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.4.2.3.3-5 Table 6.4.2.3.3-5: MCVideo-Info in SIP INFO (Table 6.4.2.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params mcvideo-request-uri not present mcvideo-calling-user-id not present anyExt video-push-url any allowed value set to the URL of the video file located in the IUT (MCVideo Server) ETSI TS 124 281 [8] (3GPP TS 24.281) clause 13.2.3.2.3 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 270 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5 Video Pull | 6.5.1 MCVideo Server - MCVideo Client / Video pull call / One-to-one video pull call |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCVideo client ) initiates an one-to-one video pull call without implicit transmission control } then { IUT (MCVideo Server) accepts the video pull call from initiator and pulls a video from the SS-UE2 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established an one-to-one video pull call } ensure that { when { the SS-UE2 (MCVideo client) sends the transmission request to the IUT (MCVideo Server) } then { IUT (MCVideo Server) sends transmission control ack to the SS-UE2 (MCVideo client) } } (3) with { IUT (MCVideo Server) having established an one-to-one video pull call } ensure that { when { the SS-UE1 (MCVideo client) sends the receive media request} then { IUT (MCVideo Server) sends transmission control ack to the SS-UE1 (MCVideo client) } } (4) with { IUT (MCVideo Server) having established an one-to-one video pull call } ensure that { when { the SS-UE1 (MCVideo client) ends the video pull call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the SS-UE2 (MCVideo Client) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 12.2.3.1.1, 10.2.2.3.1.1, 12.2.3.1.2, 10.2.2.3.2, 12.2.3.1.3, 12.2.3.2.2, 12.2.3.2.3, 10.2.5.4. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 12.2.3.1.1] "Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-to-one video pull", the participating MCVideo function determine that the call is a private call and shall perform the procedures of the clause 10.2.2.3.1.1." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.3.1.1] "Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "private", the participating MCVideo function: … 3) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request and shall authorise the user; NOTE 3: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 271 … 5) shall: a) if the <session-type> is set to "private", determine that the call is a private call; 6) if the call is a: a) private call, determine the public service identity of the controlling MCVideo function for the private call service associated with the originating user's MCVideo ID identity; … 12) shall validate the media parameters and if the MCVideo video media codec is not offered in the "SIP INVITE request for originating participating MCVideo function" shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; 13) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3 with the following clarifications: a) if the conditions in step 12) above were executed and the participating MCVideo function determined that the "uri" attribute of only one of the <entry> elements of the application/resource-lists MIME body matched with an <entry> element of the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) then the <session-type> in the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request generated in clause 6.3.2.1.3 is set to "private"; and b) if the conditions in step 12) above were executed, then only the <entry> element(s) of the application/resource-lists MIME body that have a "uri" attribute that matched with an <entry> elements of the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) are included in the application/resource-lists MIME body in the SIP INVITE request generated in clause 6.3.2.1.3; 14) shall set the Request-URI to the public service identity of the controlling MCVideo function hosting the private call service as determined by step 6); 15) shall set the <mcvideo-calling-user-id> element in an application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 16) if the call is a private call and: a) if a Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was received in the incoming SIP INVITE request with a value of "Manual", shall not include a Priv-Answer-Mode header field in the outgoing SIP INVITE request; … c) if the <allow-force-auto-answer> element of the <ruleset> element is present in the MCVideo user profile document with the value "true" (see the MCVideo user profile document in 3GPP TS 24.484 [25]) on the participating MCVideo function, and the Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was received in the incoming SIP INVITE request with a value of "Auto", shall include the Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request; d) if a Priv-Answer-Mode header field containing the value of "Auto" has not been included in the outgoing SIP INVITE request as specified in step 17) above and the incoming "SIP INVITE request for originating participating MCVideo function" contained an Answer-Mode header field as specified in IETF RFC 5373 [27], then shall populate the Answer-Mode header field of the outgoing SIP INVITE request with the contents of the Answer-Mode header field from the incoming "SIP INVITE request for originating participating MCVideo function"; 17) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for originating participating MCVideo function", as specified in clause 6.3.2.1.1.1; 18) shall include a Resource-Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field if included in the SIP INVITE request from the MCVideo client; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 272 19) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. Upon receiving a SIP 180 (Ringing) response, the participating MCVideo function: 1) shall generate a SIP 180 (Ringing) response to the SIP INVITE request as specified in the clause 6.3.2.1.5.1; 2) shall include the P-Asserted-Identity header field as received in the incoming SIP 180 (Ringing) response; 3) shall include Warning header field(s) received in the incoming SIP 180 (Ringing) response; and 4) shall forward the SIP 180 (Ringing) response to the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response, the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2; 2) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 3) shall include Warning header field(s) received in the incoming SIP 200 (OK) response; 4) shall include the P-Asserted-Identity header field received in the incoming SIP 200 (OK) response into the outgoing SIP 200 (OK) response; 5) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 6) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 8) shall start the SIP session timer according to rules and procedures of IETF RFC 4028 [23]. The participating MCVideo function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 12.2.3.1.2] "Upon receipt of a "SIP INVITE request for terminating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-to-one video pull", the participating MCVideo function determine that the call is a private call and shall perform the procedures of the clause 10.2.2.3.2." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.3.2] "This clause covers both on demand session and pre-established session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: … 2) shall check the presence of the isfocus media feature tag in the URI of the Contact header field … … 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; … 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if one of the following conditions are met: a) "SIP INVITE request for terminating participating MCVideo function" contains an Answer-Mode header field with the value "Auto"; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 273 b) "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; or c) "SIP INVITE request for terminating participating MCVideo function" contains a Priv-Answer-Mode header field with the value "Auto"; and 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if either of the following conditions are met: a) "SIP INVITE request for terminating participating MCVideo function" contains an Answer-Mode header field with the value "Manual"; b) "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"; or c) "SIP INVITE request for terminating participating MCVideo function" contains a Priv-Answer-Mode header field with the value "Manual"." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 12.2.3.1.3] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 10.2.4. Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 10.2.5." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 12.2.3.2.2] "Upon receipt of a "SIP INVITE request for controlling MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-to-one video pull", the controlling MCVideo function determine that the call is a private call and shall perform the procedures of the clause 10.2.2.4.2, with following clarifications: 1) shall check whether the MCVideo ID of the MCVideo calling user in the <mcvideo-calling-user-id> is authorised to initiate the one-to-one video pull call, and if it is not authorised the controlling MCVideo function shall return a SIP 403 (Forbidden) response with the warning text as specified in "Warning header field" and skip the rest of the steps; and 2) shall check whether the MCVideo ID of the MCVideo called party user in the <mcvideo-called-party-id> is authorised to receive the one-to-one video pull call, and if it is not authorised the controlling MCVideo function shall return a SIP 403 (Forbidden) response with the warning text as specified in "Warning header field" and skip the rest of the steps." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 12.2.3.2.3] "When the MCVideo session for one-to-one video pull call needs to be released, the controlling MCVideo function shall perform the procedures of the clause 10.2.5.4." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.5.4] "When the MCVideo session for private call needs to be released as specified in clause 6.3.8.2, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.5." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 274 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.1.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - SS-UE2 (MCVideo Client) has a pre-recorded video that is available to be pulled from another client. - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.1.3.2 Test procedure sequence | Table 6.5.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCVideo Client) requests the establishment of a video pull call to pull a video from SS-UE2 (MCVideo Client). - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to pull a video from SS-UE2 without implicit transmission control request according to option a of note in Annex A, Table A.3.1.3-1? - - 1 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1 to start transmitting media from SS-UE2? (Note 1) - - 2 P 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Media Reception Request and Response' as described in Annex A, Table A.3.9.3-1 to start receiving media from SS-UE2 (MCVideo Client), in SS-UE1 (MCVideo Client)? - - 3 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 275 St Procedure Message Sequence TP Verdict U - S Message 5 Make the SS-UE1 (MCVideo Client) release the call. - - - - 6 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 4 P NOTE 1: It is assumed that the client considers the establishment of the video pull call as implicit transmission request, i.e. that it automatically enters the 'U: pending request to transmit' state (ETSI TS 124 581 [9] (3GPP TS 24.581) clause 6.2.4.4). NOTE 2: It is not clear in ETSI TS 124 581 [9] (3GPP TS 24.581) what exactly is meant with "implicit transmit media request" in context of CT call establishment (as stated in ETSI TS 124 281 [8] (3GPP TS 24.281)) and how it shall be handled. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.5.1.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.5.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP as described in Annex A, Table A.3.1.4-2 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.5.1.3.3-2 NOTE: Condition is also applied to all body parts. Table 6.5.1.3.3-2: MCVideo-Info in SIP INVITE (Table 6.5.1.3.3-1) Derivation Path: Annex A, Table A.3.1.4-3, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params session-type "one-to-one video pull" Table 6.5.1.3.3-3: SIP INVITE from the IUT (MCVideo Server) (Step 2, Table 6.5.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP as described in Annex A, Table A.3.1.4-5 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.5.1.3.3-4 NOTE: Condition is also applied to all body parts. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 276 Table 6.5.1.3.3-4: MCVideo-Info in SIP INVITE (Table 6.5.1.3.3-3) Derivation Path: Annex A, Table A.3.1.4-6 Information Element Value/remark Comment Reference Condition Mcvideoinfo mcvideo-Params session-type "one-to-one video pull" Table 6.5.1.3.3-5: SIP 200 (OK) from the SS-UE2 (Step 2 Table 6.5.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7, with condition PRIVATE-CALL. NOTE: Condition is also applied to all body parts. Table 6.5.1.3.3-6: SIP 200 (OK) from the IUT (MCVideo Server) (Step 2, Table 6.5.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9, with condition PRIVATE-CALL. NOTE: Condition is also applied to all body parts. Table 6.5.1.3.3-7: Media Transmission Notification (Step 3, Table 6.5.1.3.2-1; Step 3b2, Annex A, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.7-1. Table 6.5.1.3.3-8: Media Transmission Notification (Step 3, Table 6.5.1.3.2-1; Step 3a3, Annex A, Table A.3.7.3-1) Derivation Path: Table 6.5.1.3.3-7, with condition ACK. 6.5.2 MCVideo Server - MCVideo Client / Video pull call / One-from-server video pull call |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.2.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCVideo client ) initiates an one-from-server video pull call without implicit transmission control with sending SIP INVITE message } then { IUT (MCVideo Server) responds with optional SIP 100 Trying and mandatory 200 (OK) message } } (2) with { IUT (MCVideo Server) having established an one-from-server video pull call } ensure that { when { the SS-UE1 (MCVideo client) initiates an one-from-server video pull call without implicit transmission control } then { IUT (MCVideo Server) sends media transmission notification to the SS-UE1 (MCVideo client) } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 277 (3) with { IUT (MCVideo Server) having established an one-from-server video pull call } ensure that { when { the SS-UE1 (MCVideo client) sends the receive media request} then { IUT (MCVideo Server) sends transmission control ack to the SS-UE1 (MCVideo client) } } (4) with { IUT (MCVideo Server) having established an one-from-server video pull call } ensure that { when { the SS-UE1 (MCVideo client) ends the video pull call by sending a SIP BYE message to the IUT (MCVideo Server) } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the SS-UE1 (MCVideo Client) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.2.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 12.2.3.1.4, 10.2.2.3.1.1, 12.2.3.1.6, 12.2.3.2.5, 10.2.2.4.2, 12.2.3.2.6, 10.2.5.4. Unless otherwise stated, these are Rel-16 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 12.2.3.1.4] "Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-from- server video pull", the participating MCVideo function determine that the call is a private call and shall perform the procedures of the clause 10.2.2.3.1.1, with the following clarifications: 1) shall not check the <allow-private-call> element of the <ruleset> element; and 2) shall use the automatic commencement mode." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.3.1.1] "Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "private", the participating MCVideo function: … 3) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request and shall authorise the user; NOTE 3: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 5) shall: a) if the <session-type> is set to "private", determine that the call is a private call; 6) if the call is a: a) private call, determine the public service identity of the controlling MCVideo function for the private call service associated with the originating user's MCVideo ID identity; … 12) shall validate the media parameters and if the MCVideo video media codec is not offered in the "SIP INVITE request for originating participating MCVideo function" shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 278 13) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3 with the following clarifications: a) if the conditions in step 12) above were executed and the participating MCVideo function determined that the "uri" attribute of only one of the <entry> elements of the application/resource-lists MIME body matched with an <entry> element of the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) then the <session-type> in the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request generated in clause 6.3.2.1.3 is set to "private"; and b) if the conditions in step 12) above were executed, then only the <entry> element(s) of the application/resource-lists MIME body that have a "uri" attribute that matched with an <entry> elements of the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) are included in the application/resource-lists MIME body in the SIP INVITE request generated in clause 6.3.2.1.3; 14) shall set the Request-URI to the public service identity of the controlling MCVideo function hosting the private call service as determined by step 6); 15) shall set the <mcvideo-calling-user-id> element in an application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 16) if the call is a private call and: a) if a Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was received in the incoming SIP INVITE request with a value of "Manual", shall not include a Priv-Answer-Mode header field in the outgoing SIP INVITE request; … c) if the <allow-force-auto-answer> element of the <ruleset> element is present in the MCVideo user profile document with the value "true" (see the MCVideo user profile document in 3GPP TS 24.484 [25]) on the participating MCVideo function, and the Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was received in the incoming SIP INVITE request with a value of "Auto", shall include the Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request; d) if a Priv-Answer-Mode header field containing the value of "Auto" has not been included in the outgoing SIP INVITE request as specified in step 17) above and the incoming "SIP INVITE request for originating participating MCVideo function" contained an Answer-Mode header field as specified in IETF RFC 5373 [27], then shall populate the Answer-Mode header field of the outgoing SIP INVITE request with the contents of the Answer-Mode header field from the incoming "SIP INVITE request for originating participating MCVideo function"; 17) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for originating participating MCVideo function", as specified in clause 6.3.2.1.1.1; 18) shall include a Resource-Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field if included in the SIP INVITE request from the MCVideo client; and 19) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. Upon receiving a SIP 180 (Ringing) response, the participating MCVideo function: 1) shall generate a SIP 180 (Ringing) response to the SIP INVITE request as specified in the clause 6.3.2.1.5.1; 2) shall include the P-Asserted-Identity header field as received in the incoming SIP 180 (Ringing) response; 3) shall include Warning header field(s) received in the incoming SIP 180 (Ringing) response; and 4) shall forward the SIP 180 (Ringing) response to the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response, the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2; 2) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 279 3) shall include Warning header field(s) received in the incoming SIP 200 (OK) response; 4) shall include the P-Asserted-Identity header field received in the incoming SIP 200 (OK) response into the outgoing SIP 200 (OK) response; 5) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 6) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 8) shall start the SIP session timer according to rules and procedures of IETF RFC 4028 [23]. The participating MCVideo function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 12.2.3.1.6] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 10.2.4. Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 10.2.5." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 12.2.3.2.5] "Upon receipt of a "SIP INVITE request for controlling MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-from- server video pull", the controlling MCVideo function determine that the call is a private call and shall perform the procedures of the clause 10.2.2.4.2, with following clarifications: 1) shall check whether the MCVideo ID of the MCVideo calling user in the <mcvideo-calling-user-id> is authorised to initiate the one-from-server video pull call, and if it is not authorised the controlling MCVideo function shall return a SIP 403 (Forbidden) response with the warning text as specified in "Warning header field" and skip the rest of the steps; and 2) shall based on the received URL of the video file contained in <video-pull-url> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to transmit media to the MCVideo client as specified in 3GPP TS 24.380 [5]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.2.4.2] "In the procedures in this clause: 1) <emergency-ind> refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; 2) <alert-ind> refers to the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 3) <session-type> refers to the <session-type> element of an application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of: - a "SIP INVITE request for controlling MCVideo function of a private call"; or the controlling MCVideo function: 1) if the <session-type> in the SIP INVITE request is set to "private": a) shall check whether the public service identity contained in the Request-URI is allocated for private call and perform the actions specified in clause 6.3.7.1 if it is not allocated and skip the rest of the steps; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 280 b) shall perform actions to verify the MCVideo ID of the inviting MCVideo user in the <mcvideo-calling- user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request, and authorise the request according to local policy, … … 4) shall validate that the received SDP offer includes at least one media stream for which the media parameters and at least one codec or media format is acceptable by the controlling MCVideo function … 5) if received SIP INVITE request includes an <emergency-ind>, shall validate the request as described in clause 6.3.3.1.17; … 8) if: a) the received SIP INVITE request contains an emergency indication set to a value of "true"; b) the originating MCVideo user is not in an in-progress emergency private call state with the targeted MCVideo user; and c) if the <session-type> in the SIP INVITE request is set to "private"; then: a) shall cache the information that the MCVideo user has initiated an MCVideo emergency private call to the targeted user; and b) shall cache the information that the MCVideo user is in an in-progress emergency private call state with the targeted MCVideo user; 9) shall perform actions as described in clause 6.3.3.2.2; 10) shall allocate an MCVideo session identity for the MCVideo session; and 11) shall invite the MCVideo user(s) listed in the MIME resource-lists body of received SIP INVITE request as specified in clause 10.2.2.4.1. Upon receiving a SIP 180 (Ringing) response and if the SIP 180 (Ringing) response or the SIP final response has not yet been sent to the inviting MCVideo client, the controlling MCVideo function: 1) if the SIP 180 (Ringing) response is associated with a SIP INVITE that contained a <session-type> set to "private", shall generate a SIP 180 (Ringing) response to the SIP INVITE request and send the SIP 180 (Ringing) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; and Upon receiving a SIP 200 (OK) response for the SIP INVITE request, the SIP dialog was established as a result of receiving a SIP INVITE request with a <session-type> element set to the value of "private" and the SIP final response has not yet been sent to the inviting MCVideo client, the controlling MCVideo function: 1) shall generate a SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.2; 3) if the received SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 1: This is the case when the MCVideo user's request for an MCVideo emergency private call was granted but the request for the MCVideo emergency alert was denied. 4) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and NOTE 2: Resulting media plane processing is completed before the next step is performed. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 281 5) shall send a SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]. … Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, where the SIP 200 (OK) response was sent with a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18. The controlling MCVideo function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 12.2.3.2.6] "When the MCVideo session for one-from-server video pull call needs to be released, the controlling MCVideo function shall perform the procedures of the clause 10.2.5.4." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.5.4] "When the MCVideo session for private call needs to be released as specified in clause 6.3.8.2, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.5." |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.2.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client). - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. - The IUT (MCVideo Client) has a pre-recorded video that is available to be pulled by using tsc_MCVideo_VSF_URI & "/file-location-1" url. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. - The SS-UE1 (MCVideo Client) has been provisioned with the url to pull the video. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 282 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.2.3.2 Test procedure sequence | Table 6.5.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the SS-UE1 (MCVideo Client) request the establishment of a video pull call to pull a video from the IUT (MCVideo Server). - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Participating Terminated session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.4.3-1 to pull a video to the SS-UE1 (MCVideo Client) from the IUT (MCVideo Server), with automatic commencement mode and without implicit transmission control request according to option a of note in Annex A, Table A.3.4.3-1? - - 1 P 3 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to SS-UE1 (MCVideo Client)? <-- Media Transmission Notification 2 P 4 IF the Media Transmission Notification message requires acknowledgement, the SS-UE1 (MCVideo Client) sends a Transmission Control ACK message. --> Transmission Control Ack - - 5 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Media Reception Request and Response' as described in Annex A, Table A.3.9.3-1 to start receiving media from the IUT (MCVideo Server)? - - 3 P 6 Make the SS-UE1 (MCVideo Client) release the call. - - - - 7 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated call release' as described in Annex A, Table A.2.15.3-1? - - 4 P NOTE: It is not clear in ETSI TS 124 581 [9] (3GPP TS 24.581) which transmission control messages should be exchanged during this procedure. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.5.2.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.5.2.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.5.2.3.2-1; Step 1, Annex A, Table A.3.4.3-1; Step 1, Annex A, Table A.2.14.3-1) Derivation Path: Annex A, Table A.3.4.4-1, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP as described in Annex A, Table A.3.1.4-2 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.5.2.3.3-2 MIME body part not present Resource list NOTE: Condition is also applied to all body parts. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 283 Table 6.5.2.3.3-2: MCVideo-Info in SIP INVITE (Table 6.5.2.3.3-1) Derivation Path: Annex A, Table A.3.1.4-3, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params session-type "one-from-server video pull" video-pull-url tsc_MCVideo_VSF_U RI & "/file-location-1" set to the URL of the video file located in the IUT (MCVideo Server) ETSI TS 124 281 [8] (3GPP TS 24.281) clause 12.2.2.4 Table 6.5.2.3.3-3: SIP 200 (OK) from the IUT (MCVideo Server) (Step 2, Table 6.5.2.3.2-1; Step 1, Annex A, Table A.3.4.3-1, Step 3, Annex A, Table A.2.14.3-1) Derivation Path: Annex A, Table A.3.4.4-2, with condition PRIVATE-CALL. NOTE: Condition is also applied to all body parts. Table 6.5.2.3.3-4: Media Transmission Notification (Step 3, Table 6.5.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.7-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition User Id of the Transmitting User not present Audio SSRC of the Transmitting User Media/Audio SSRC of IUT (MCVideo Server) SSRC of the IUT (MCVideo Server) transmitting the media ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.16 Functional Alias not present Table 6.5.2.3.3-5: Transmission Control Ack (Step 4, Table 6.5.2.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.6 Ambient Viewing Calls | 6.6.1 MCVideo Server - MCVideo Client / Ambient Viewing Call / On- demand / Remotely initiated ambient viewing call / Remotely initiated ambient viewing call release |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.6.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCVideo client ) initiates a remotely initiated ambient call } then { IUT (MCVideo Server) accepts the remotely initiated ambient call from initiator and establishes the call with the SS-UE2 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established a remotely initiated ambient call } ensure that { when { IUT (MCVideo Server) establishes the call with the SS-UE2 (MCVideo Client) } then { IUT (MCVideo Server) sends Transmission Granted to the SS-UE2 (MCVideo client) and sends Media Transmission Notification to the SS-UE1 (MCVideo client)} } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 284 (3) with { IUT (MCVideo Server) having established a remotely initiated ambient call } ensure that { when { the SS-UE1 (MCVideo client) sends the receive media request} then { IUT (MCVideo Server) sends transmission control ack to the SS-UE1 (MCVideo client) } } (4) with { IUT (MCVideo Server) having established a remotely initiated ambient call } ensure that { when { the SS-UE1 (MCVideo client) ends the video pull call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the SS-UE2 (MCVideo Client) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.6.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 15.3.1.1, 15.3.1.2, 10.2.4.2.1.1, 15.3.2.1, 10.2.4.2.2.1, 15.4.1, 15.4.2, 15.4.4. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 15.3.1.1] "Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideot-info+xml MIME body with the <session-type> element set to a value of "ambient- viewing", the participating MCVideo function: … 2) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request and shall authorise the user; NOTE: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. … 5) shall determine the public service identity of the controlling MCVideo function for the ambient viewing call service associated with the originating user's MCVideo ID identity… 6) if the incoming SIP INVITE request does not contain an application/resource-lists MIME body or contains an application/resource-lists MIME body with more than one <entry> element… shall not continue with the rest of the steps; … 8) if the <PrivateCall> element exists in the MCVideo user profile document with one or more <entry> elements (see the MCVideo user profile document in 3GPP TS 24.484 [25]) and: a) if the "uri" attribute of the <entry> element of the application/resource-lists MIME body does not match with one of the <entry> elements of the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]); and b) if configuration is not set in the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) that allows the MCVideo user to make a private call to users not contained within the <entry> elements of the <PrivateCall> element; then: a) … shall not continue with the rest of the steps; 9) shall validate the media parameters and if the MCVideo video codec is not offered in the "SIP INVITE request for originating participating MCVideo function" shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; 10) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 285 11) shall set the Request-URI to the public service identity of the controlling MCVideo function hosting the private call service; 12) shall set the <mcvideo-calling-user-id> element in an application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 13) if the Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was received in the incoming SIP INVITE request with a value of "Auto" or if no Priv-Answer-Mode header field was received in the incoming SIP INVITE request or a Priv-Answer-Mode header field was received containing a value other than "Auto", shall include the Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request; 14) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for originating participating MCVideo function", as specified in clause 6.3.2.1.1.1; and 15) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 15.3.1.2] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function: 1) shall follow the procedures as specified in clause 10.2.4.2.1.1." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.4.2.1.1] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.1.6." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 15.3.2.1] "Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: NOTE: The procedures in the present clause are applicable for both on-demand and pre-established sessions. … 2) shall check the presence of the isfocus media feature tag in the URI of the Contact header … 3) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; … 6) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 15.3.2.2] "Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 10.2.4.2.2.1." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 10.2.4.2.2.1] "Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.2.8.1." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 15.4.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo ambient viewing session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 15.4.2. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 286 NOTE 1: As a result of calling clause 6.3.3.1.2, the <mcvideo-calling-user-id> containing the calling user's MCVideo ID is copied into the outgoing SIP INVITE. 2) shall copy the MCVideo ID of the MCVideo user listed in the MIME resources body of the incoming SIP INVITE request, into the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 3) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited; NOTE 2: How the controlling MCVideo function finds the address of the terminating participating MCVideo function is out of the scope of the current release. NOTE 3: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 4) shall copy the public user identity of the calling MCVideo user from the P-Asserted-Identity header field of the incoming SIP INVITE request into the P-Asserted-Identity header field of the SIP INVITE request; 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; 6) if the <ambient-viewing-type> element contained in the application/vnd.3gpp.mcvideo-info+xml MIME body in the received SIP INVITE request is set to a value of "local-init", shall include the g.3gpp.mcvideo.ambient- viewing-call-release feature-capability indicator as described in clause D.3 in the Feature-Caps header field according to IETF RFC 6809 [63]; NOTE 4: The only case where the terminating user can release the ambient viewing call is when the terminating client is the "viewing MCVideo user"; 7) if the <ambient-viewing-type> element contained in the application/vnd.3gpp.mcvideo-info+xml MIME body in the received SIP INVITE request is set to a value of "remote-init", shall include in the outgoing SIP INVITE request an alert-info header field set to a value of "<file:///dev/null>" according to IETF RFC 3261 [15]; 8) shall send the SIP INVITE request towards the core network according to 3GPP TS 24.229 [11]; and 9) shall start a private call timer with a value set to the configured max private call duration for the user. Upon receiving SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall cache the contact received in the Contact header field; and 2) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. Upon expiry of the private call timer, the controlling MCVideo function shall follow the procedure for releasing the ambient viewing call session as specified in clause 15.4.3 with the clarification that the <release-reason> element included in the SIP BYE request shall be set to "private-call-timer-expiry"." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 15.4.2] "Upon receiving of a "SIP INVITE request for controlling MCVideo function of an ambient viewing call" the controlling MCVideo function: 1) shall check whether the public service identity contained in the Request-URI is allocated for ambient viewing call and perform the actions specified in clause 6.3.7.1 if it is not allocated and skip the rest of the steps; 2) shall perform actions to verify the MCVideo ID of the inviting MCVideo user in the <mcvideo-calling-user- id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request, and authorise the request according to local policy; … 4) shall validate that the received SDP offer includes at least one media stream for which the media parameters and at least one codec or media format is acceptable by the controlling MCVideo function … ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 287 5) shall perform actions as described in clause 6.3.3.2.2; 6) shall allocate an MCVideo session identity for the MCVideo ambient viewing call session; and 7) shall invite the MCVideo user listed in the MIME resource-lists body of received SIP INVITE request as specified in clause 15.4.1. If the procedures of clause 15.4.1 were successful in inviting the MCVideo user listed in the MIME resource-lists body of received SIP INVITE request, the controlling MCVideo function: 1) shall generate a SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.2; 3) shall include in the SIP 200 (OK) response the g.3gpp.mcvideo.ambient-viewing-call-release feature- capability indicator as described in clause D.3 in the Feature-Caps header field according to IETF RFC 6809 [63]; NOTE: The originator of the ambient viewing call is either the initiator of a "remote-init" ambient viewing type call or the originator of a "local-init" ambient viewing type call. In either case, the originating user is allowed to release the ambient viewing call. 4) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; 5) shall send a SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; 6) if the <ambient-viewing-type> element contained in the application/vnd.3gpp.mcvideo-info+xml MIME body in the received SIP INVITE request is set to a value of "remote-init": a) shall cache the MCVideo ID contained in the <mcvideo-calling-user-id> element of the received SIP INVITE request as the viewing MCVideo user of the ambient viewing call and cache the MCVideo ID contained in the MIME resource-lists body of the received SIP INVITE request as the viewed-to MCVideo user; and b) shall cache the ambient viewing type of the ambient viewing call as "remote-init"; and 7) if the <ambient-viewing-type> element contained in the application/vnd.3gpp.mcvideo-info+xml MIME body in the received SIP INVITE request is set to a value of "local-init": a) shall cache the MCVideo ID contained in the <mcvideo-calling-user-id> element of the received SIP INVITE request as the viewed-to MCVideo user of the ambient viewing call and cache the MCVideo ID contained in the MIME resource-lists body of received SIP INVITE request as the viewing MCVideo user; and b) shall cache the ambient viewing type of the ambient viewing call as "local-init". … The controlling MCVideo function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 15.4.4] "Upon receipt of a SIP BYE request for an ambient viewing session the controlling MCVideo function: 1) shall interact with the media plane as specified in clause 6.3 in 3GPP TS 24.581 [5] for releasing the media plane resource associated with the SIP session towards the MCVideo client; 2) shall generate a SIP BYE request according to 3GPP TS 24.229 [11]; and 3) shall send the SIP BYE request in the dialog of the other participant in the ambient viewing call according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the sent SIP BYE request the controlling MCVideo function: ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 288 1) shall interact with the media plane as specified in clause 6.3 in 3GPP TS 24.581 [5] for releasing media plane resources associated with the SIP session with the MCVideo ambient viewing call participant; 2) shall generate a SIP 200 (OK) response to the received SIP BYE request and send the SIP 200 (OK) response towards the MCVideo client according to 3GPP TS 24.229 [11]; and 3) shall delete the following cached data for the ambient viewing call: a) the MCVideo ID of the viewed-to MCVideo user; b) the MCVideo ID of the viewing MCVideo user; and c) the value of the ambient viewing type." |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.6.1.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.6.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client). - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 289 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.6.1.3.2 Test procedure sequence | Table 6.6.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCVideo Client) requests the establishment of a remotely initiated ambient listening call to SS-UE2 (MCVideo Client). - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform step 1 of procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to establish a remotely initiated ambient viewing call with automatic commencement mode and with implicit transmission control request according to option b.ii of note in Annex A, Table A.3.1.3-1? (Note) - - 1 P 3 Check: Does the IUT (MCVideo Server) send a Transmission Granted message to SS-UE2 (MCVideo Client)? <-- Transmission Granted 2 P 4 IF the Transmission Granted message requires acknowledgement, the SS-UE2 (MCVideo Client) sends a Transmission Control ACK message. --> Transmission Control Ack - - 5 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to SS- UE1 (MCVideo Client)? <-- Media Transmission Notification 2 P 6 IF the Media Transmission Notification message requires acknowledgement, the SS-UE1 (MCVideo Client) sends a Transmission Control ACK message. --> Transmission Control Ack - - 7 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Media Reception Request and Response' as described in Annex A, Table A.3.9.3-1 to start receiving media from SS- UE2 (MCVideo Client) in SS-UE1 (MCVideo Client)? - - 3 P 9 Make the SS-UE1 (MCVideo Client) release the call. - - - - 10 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 4 P NOTE: According to ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.4, call originator shall include "mc_implicit_request" parameter in the SDP offer. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.6.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications: ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 290 Table 6.6.1.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.6.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition Priv-Answer-Mode answer-mode-value "Auto" answer-mode-param "require" Message-body MIME body part SDP message MIME-part-body SDP as described in Table 6.6.1.3.3-2 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.6.1.3.3-3 Table 6.6.1.3.3-2: SDP Message in SIP INVITE (Table 6.6.1.3.3-1) Derivation Path: Annex A, Table A.3.1.4-2, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition Media description[2] Media description for video media attribute a=line attribute=recvonly recvonly Table 6.6.1.3.3-3: MCVideo-Info in SIP INVITE (Table 6.6.1.3.3-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 session-type "ambient-viewing" anyExt ambient-viewing-type "remote-init" Table 6.6.1.3.3-4: SIP INVITE from the IUT (MCVideo Server) (Step 2, Table 6.6.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition Answer-Mode not present Priv-Answer-Mode answer-mode-value "Auto" answer-mode-param "require" Alert-Info Value "<file:///dev/null>" Message-body MIME body part SDP message MIME-part-body SDP as described in Table 6.6.1.3.3-5 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 6.6.1.3.3-6 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 291 Table 6.6.1.3.3-5: SDP in SIP INVITE (Table 6.6.1.3.3-4) Derivation Path: Annex A, Table A.3.1.4-5, with condition PRIVATE-CALL Information Element Value/remark Comment Reference Condition Media description[2] Media description for video media attribute a=line attribute=recvonly recvonly Table 6.6.1.3.3-6: MCVideo-Info in SIP INVITE (Table 6.6.1.3.3-4) Derivation Path: Annex A, Table A.3.1.4-6 Information Element Value/remark Comment Reference Condition Mcvideoinfo mcvideo-Params session-type "ambient-viewing" anyExt ambient-viewing-type "remote-init" Table 6.6.1.3.3-7: SIP 200 (OK) from the SS-UE2 (Step 2 Table 6.6.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7 Table 6.6.1.3.3-8: SIP 200 (OK) from the IUT (MCVideo Server) (Step 2, Table 6.6.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9 Information Element Value/remark Comment Reference Condition Feature-Caps fc-value "+g.3gpp.mcvideo.ambient -viewing-call-release" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 15.4.2 Table 6.6.1.3.3-9: Transmission Granted (Step 3, Table 6.6.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.1-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Table 6.6.1.3.3-10: Media Transmission Notification (Step 5, Table 6.6.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.7-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Table 6.6.1.3.3-11: Transmission Control Ack (Steps 4 and 6, Table 6.6.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 292 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.7 Use of MBMS transmission | 6.7.1 MCVideo Server - MCVideo Client / MBMS / MBMS Bearer Announcement / MBMS Bearer Viewing Status / Transition to MBMS from Unicast / MBMS Transmission Control / Transition to Unicast from MBMS |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.7.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { the SS-UE1 (MCVideo client ) initiates establishment of a group call with automatic commencement mode and without implicit transmission control } then { IUT (MCVideo Server) accepts the call from the initiator and establishes the call with the SS-UE2 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { IUT (MCVideo Server) requests to send an MBMS bearer announcement to notify bearer availability } then { IUT (MCVideo Server) sends a SIP MESSAGE message to the SS-UE1 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { SS-UE1 (MCVideo Client) sends a MBMS bearer listening status report by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) } } (4) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { IUT (MCVideo Server) requests to send an MBMS bearer announcement to notify bearer availability } then { IUT (MCVideo Server) sends a SIP MESSAGE message to the SS-UE2 (MCVideo Client) } } (5) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { SS-UE2 (MCVideo Client) sends a MBMS Bearer listening status report to notify listening general-purpose subchannel by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) } } (6) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { the SS-UE1 (MCVideo client) requests the transmission control} then { IUT (MCVideo Server) sends transmission control ack to the SS-UE1 (MCVideo client) } } (7) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { the IUT (MCVideo Server) uses MBMS subchannel for the conversation } then { IUT (MCVideo Server) sends map group to bearer message over general purpose MBMS channel } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 293 (8) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { SS-UE1 (MCVideo Client) sends a MBMS Bearer listening status report to notify listening to media and transmission control over MBMS subchannel by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) } } (9) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { SS-UE2 (MCVideo Client) sends a MBMS Bearer listening status report to notify listening to media and transmission control over MBMS subchannel by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) } } (10) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { IUT (MCVideo Server) responds with a SIP 200 (OK) } then { IUT (MCVideo Server) sends transmission granted to the SS-UE1 (MCVideo Client) and sends Media Transmission Notification to the SS-UE2 (MCVideo Client)} } (11) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { the SS-UE2 (MCVideo client) sends the receive media request } then { IUT (MCVideo Server) sends transmission control ack to the SS-UE2 (MCVideo client) } } (12) with { IUT (MCVideo Server) having established group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { IUT (MCVideo Server) requests to set the explicit MuSiK key } then { IUT (MCVideo Server) sends a SIP MESSAGE message containing a MuSiK download message to the SS-UE1 (MCVideo Client) and to the SS-UE2 (MCVideo Client) } } (13) with { IUT (MCVideo Server) having established group call with automatic commencement mode and using a MBMS subchannel for the conversation } ensure that { when { the SS-UE1 (MCVideo client) requests the end of transmission control } then { IUT (MCVideo Server) sends transmission control ack, transmission end response and transmission end notify to all affiliated users of the group } } (14) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { IUT (MCVideo Server) stops using MBMS subchannel for the conversation } then { IUT (MCVideo Server) sends transmission idle to the SS-UE2 (MCVideo Client) and sends unmap group to bearer over MBMS subchannel } } (15) with { IUT (MCVideo Server) having established group call with automatic commencement } ensure that { when { SS-UE1 (MCVideo Client) sends a MBMS Bearer listening status report to stop notify listening media and transmission control over MBMS subchannel by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) to the SS-UE1 (MCVideo Client) } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 294 (16) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { SS-UE2 (MCVideo Client) sends a MBMS Bearer listening status report to stop notify listening media and transmission control over MBMS subchannel by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) to the SS-UE2 (MCVideo Client) } } (17) with { IUT (MCVideo Server) having established group call with automatic commencement } ensure that { when { IUT (MCVideo Server) requests to send an MBMS bearer cancellation announcement to notify bearer unavailability } then { IUT (MCVideo Server) sends a SIP MESSAGE message to the SS-UE1 (MCVideo Client) and to the SS-UE2 (MCVideo Client) } } (18) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { the SS-UE1 (MCVideo Client) sends MBMS bearer listening status report message to IUT (MCVideo Server), to notify not being listening to general-purpose subchannel } then { IUT (MCVideo Server) responds with a SIP 200 (OK) } } (19) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { the SS-UE2 (MCVideo Client) sends MBMS Bearer listening status report message to IUT (MCVideo Server), to notify not being listening to general-purpose subchannel } then { IUT (MCVideo Server) responds with a SIP 200 (OK) } } (20) with { IUT (MCVideo Server) having established group call with automatic commencement mode } ensure that { when { the SS-UE1 (MCVideo client) ends the group call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the client ending the call and sends a SIP BYE message to the SS-UE2 (MCVideo Client) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.7.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 16.3.2.1, 16.3.2.2, 16.3.2.3, 16.3.2.4, 16.3.2.5, 16.3.3, 16.3.4, and ETSI TS 124 581 [9] (3GPP TS 24.581), clauses 4.1.2.1, 4.1.2.2, 4.1.2.3, 4.1.2.4, 4.1.2.5, 6.4.2, 6.4.3, 10.2, 13.3.2, 9.3.1, 9.4.1. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 16.3.2.1] "The availability of an MBMS bearer is announced to MCVideo clients by means of an MBMS bearer announcement message. One or more MBMS bearer announcement elements are included in an application/vnd.3gpp.mcvideo-mbms- usage-info+xml MIME body. An MBMS bearer announcement message can contain new MBMS bearer announcements, updated MBMS bearer announcements or cancelled MBMS bearer announcements or a mix of all of them at the same time in an application/vnd.3gpp.mcvideo-mbms-usage-info+xml MIME body. Each initial MBMS bearer announcement message announces one MBMS bearer intended to carry a general purpose MBMS subchannel used for application level multicast signalling in a specified MBMS service area and additionally, the message could also announce zero or more extra MBMS bearers intended to carry media and media control. NOTE: A new MBMS bearer announcement does not implicitly remove previously sent MBMS bearer announcements if the previously sent MBMS bearer announcement is not included in an MBMS bearer announcement message. However, the application/sdp MIME body, if included in the new MBMS bearer announcement message, fully replaces the existing application/sdp MIME body (which includes the MSCCK security key used to protect the general purpose MBMS subchannel). ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 295 When and to whom the participating MCVideo function sends the MBMS bearer announcement is based on local policy in the participating MCVideo function. The following clauses describe how the participating MCVideo function: 1. sends an initial MBMS bearer announcement message; 2. updates a previously sent announcement of MBMS bearer(s); 3. cancels a previously sent announcement of MBMS bearer(s); and 4. keys, re-keys or un-keys MCVideo groups using Multicast Signalling Key (MuSiK) via a key download procedure. Prior to the participating MCVideo function transmitting on an MBMS bearer, the participating MCVideo function: 1. if necessary, shall instruct the local key management client to request keying material from the key management server as described in 3GPP TS 33.180 [8]; 2. shall generate MSCCK(s) with the corresponding MSCCK-ID(s) and MuSiK(s) with the corresponding MuSiK-ID(s) as necessary; and 3. shall distribute MSCCKs, MSCCK-IDs, MuSiKs and MuSiK-IDs to the MCVideo clients, as needed, using the keying material received from the key management server for security protection, as described in 3GPP TS 33.180 [8]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 16.3.2.2] "For each MCVideo client that the participating MCVideo function is sending an MBMS bearer announcement to, the participating MCVideo function: 1) shall generate an SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [17]; 2) shall set the Request-URI to the URI received in the To header field in a third-party SIP REGISTER request; 3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with parameters "require" and "explicit" according to IETF RFC 3841 [20]; 4) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; 5) shall include one application/sdp MIME body conforming to 3GPP TS 24.229 [11] where the application/sdp MIME body and: a) shall include the Content-Disposition header field with the value "render"; and b) if FEC is applied to protect one of the following media lines i) shall include a "a=FEC-declaration" session attribute set to "0", with the the "encoding-id" parameter set to "1", as specified in [67]. ii) shall include a "a=FEC-OTI-extension" session attribute, providing the FEC object transmission information, specified in clause 8.2.2.10a in [67]. iii) should include an "a=mbms-repair" session attribute, as specified in clause 8.2.2.10a in [67]. c) should include one or more "m=video" media lines and media line attributes as defined in 3GPP TS 24.581 [5] to be used as the MBMS subchannel for video. Additional the participating MCVideo function: i) shall set c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the "invalid" DNS top-level domain, if IPv6; ii) shall set port number of the media line to 9; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 296 iii) if transmission control and media control is multiplexed with video, shall include the "a=rtcp-mux" attribute as specified in IETF RFC 5761 [72]; and shall include the "a=rtcp:9" as specified in IETF RFC 5761 [72]. iv) if the declared media is protected by FEC, shall include a "a=FEC" attribute, set to 0. d) should include one or more" m=audio" media lines and media line attributes as defined in 3GPP TS 24.581 [5] to be used as the MBMS subchannel for audio. Additional the participating MCVideo function: i) shall set c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the "invalid" DNS top-level domain, if IPv6; ii) shall set port number of the media line to 9; iii) if media control is multiplexed with audio, shall include the "a=rtcp-mux" attribute as specified in IETF RFC 5761 [72]; and shall include the "a=rtcp:9" as specified in IETF RFC 5761 [72]. iv) if the declared media is protected by FEC, shall include a "a=FEC" attribute, set to 0. e) if "m=video" media lines to be used in an MBMS subchannel for video without multiplexing transmission control are included above, shall include one or more "m=application" media line as defined in 3GPP TS 24.581 [5] to be used as the MBMS subchannel for transmission control messages. The media line: i) shall set c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the ".invalid" DNS top-level domain, if IPv6; and ii) shall set the port number of the media line to 9; f) should include one or more" m=application" media lines and media line attributes as defined in 3GPP TS 24.581 [5] to be used as the MBMS subchannel for FEC repair packets. Additionally the participating MCVideo function: i) shall set c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the "invalid" DNS top-level domain, if IPv6; ii) shall set port number of the media line to 9; iii) shall include a "a=FEC" attribute, set to 0. g) shall include one "m=application" media line as defined in clause 4.3.3.1 from 3GPP TS 24.581 [5] to be used as the general purpose MBMS subchannel. The media line shall include a valid multicast IP address and a valid port number. If the protection of MBMS subchannel control messages sent over the general purpose MBMS subchannel of the MBMS bearer is required, the participating MCVideo function also includes an "a=key-mgmt" media-level attribute. The participating MCVideo function: i) shall encrypt the MSCCK to a UID associated to the targeted MCVideo ID and a time related parameter as described in 3GPP TS 33.180 [8]; ii) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated MSCCK and MSCCK-ID as specified in 3GPP TS 33.180 [8]; iii) shall add the public service identity of the participating MCVideo function to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [8]; iv) shall sign the MIKEY-SAKKE I_MESSAGE using the public service identity of the participating MCVideo function signing key provided in the keying material together with a time related parameter, and add this to the MIKEY-SAKKE payload, as described in 3GPP TS 33.180 [8]; and v) shall include the "mikey" key management and protocol identifier and the signed MIKEY-SAKKE I_MESSAGE in the value of the a=key-mgmt" media-level attribute according to IETF RFC 4567 [6]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 297 6) shall include an application/vnd.3gpp.mcvideo-mbms-usage-info+xml MIME body defined in clause F.2 with the <version> element set to "1" and one or more <announcement> elements associated with the pre- activated MBMS bearers. Each set of an <announcement> element: a) shall include a TMGI value in the <TMGI> element; NOTE 4: The same TMGI value can only appear in one <announcement> element. The TMGI value is also used to identify the <announcement> when updating or cancelling the <announcement> element. NOTE 5: The security key active for the general purpose MBMS subchannel on which the mapping (i.e. the MapGroupToBearer message) of media or media control to this MBMS bearer was indicated, is used for MBMS subchannels on this MBMS bearer, unless a different key or an indication of not using encryption is in place. b) shall include the QCI value in the <QCI> element; c) if multiple carriers are supported, shall include the frequency to be used in the <frequency> element; NOTE 6: In the current release if the <frequency> element is included, the frequency in the <frequency> element is the same as the frequency used for unicast. d) shall include one or more MBMS service area IDs in <mbms-service-area-id> elements in the <mbms- service-areas> element; NOTE 7: Initial mappings of groups to MBMS subchannels on an MBMS bearer for the purpose of carrying media or media control can occur only where the MBMS service area for this bearer and the MBMS service area for the bearer carrying the general purpose MBMS subchannel on which the MapGroupToBearer message is sent intersect. However, once media or media control were successfully mapped to this bearer, the reception by the MCVideo client can continue (until UnmapGroupToBearer is received or until timeout) throughout the entire MBMS service area of this bearer. e) may include the <report-suspension> element and set it to "true" value or the "false" value; and NOTE 8: The participating function can choose to direct some clients not to send an MBMS bearer suspension report when notified by RAN, by including the <report-suspension> element set to "false". The purpose is to prevent an avalanche of identical reports sent by clients roughly at the same time, to report the suspension of the same MBMS bearer. The way the participation function determines which clients are to send or not to send the report is outside the scope of the present document. f) if the MBMS bearer is carrying the general purpose MBMS subchannel, shall include one <GPMS>element, giving the number of the "m=application" media line in the application/sdp MIME body generated in step 5 above to be used for the general purpose MBMS subchannel; 7) shall include the MBMS public service identity of the participating MCVideo function in the P-Asserted- Identity header field; 8) shall include in a MIME body with Content-Type header field set to "application/vnd.3gpp.mcvideo- info+xml", the <mcvideo-request-uri> element set to the MCVideo ID of the user; and 9) shall send the SIP MESSAGE request towards the MCVideo client according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 16.3.2.3] "When the participating MCVideo function wants to update a previously sent announcement, the participating MCVideo function sends an MBMS bearer announcement in an SIP MESSAGE request as specified in clause 16.3.2.2 where the participating MCVideo function in the <announcement> element to be updated: 1) shall include the same TMGI value as in the MBMS bearer announcement to be updated in the <TMGI> element; NOTE 1: TMGI value is used to identify the <announcement> when updating or cancelling the <announcement> element and can't be changed. 2) shall include the same or an updated value of the QCI in the <QCI> element; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 298 3) if a frequency was included in the previously sent announcement, shall include the same value in the <frequency> element; 4) shall include the same list of MBMS service area IDs or an updated list of MBMS service area IDs in the <mbms-service-areas> element; 5) may include the same or an updated value in the <report-suspension> element; 6) shall include the <GPMS> element with the same value as in the initial <announcement> element; and 7) shall include the same application/sdp MIME body as included in the initial MBMS announcement." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 16.3.2.4] "When the participating MCVideo function wants to cancel an MBMS bearer announcement associated with an <announcement> element, the participating MCVideo function sends an MBMS bearer announcement as specified in clause 16.3.2.2 where the participating MCVideo function in the <announcement> element to be cancelled: 1) shall include the same TMGI value as in the <announcement> element to be cancelled in the <TMGI> element; 2) shall not include an <mbms-service-areas> element; 3) if the application/vnd.3gpp.mcvideo-mbms-usage-info+xml MIME body only contains <announcement> elements that are to be cancelled, shall not include an <GPMS> element; and 4) if the application/vnd.3gpp.mcvideo-mbms-usage-info+xml MIME body only contains <announcement> elements that are to be cancelled, shall not include an application/sdp MIME body." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 16.3.2.5] "For each MCVideo client that the participating MCVideo function is intending to use an MBMS bearer to transmit confidentiality protected transmission control signalling (SRTCP) to the client, the participating MCVideo function shall perform a key download procedure for each Multicast Signalling Key (MuSiK). Two kinds of MuSiK download are possible: default MuSiK download and explicit MuSiK download. The default MuSiK download is used to set, reset or unset a MuSiK and its corresponding MuSiK-ID and is applicable to all groups supported by the MCVideo client, except for certain identified groups for which MuSiKs and MUSiK-IDs are assigned, reassigned or unassigned separately via explicit MuSiK download. The default MuSiK and MUSiK-ID can apply to all the MCVideo clients supported by the participating MCVideo function and can be overridden by the explicit MuSiK download which is selectively applied only to the MCVideo clients using the explicitly identified groups. A group subject to explicit MuSiK download, can be switched to the default MuSiK protection via a default MuSiK download identifying that group. The participating MCVideo function: 1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [17]; 2) shall set the Request-URI to the URI received in the To header field in a third-party SIP REGISTER request; 3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with parameters "require" and "explicit" according to IETF RFC 3841 [20]; 4) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; 5) shall include an application/vnd.3gpp.mcvideo-mbms-usage-info+xml MIME body defined in clause F.2 with the <version> element set to "1", and either a) containing an <mbms-explicitMuSiK-download> element with at least one <group> element associated with the MuSiK being downloaded; or b) containing an <mbms-defaultMuSiK-download> element with zero or more <group> elements associated with the MuSiK being downloaded; 6) if the transmission control signaling for the group(s) in the specified list is to be protected using the MuSiK, shall include an application/mikey MIME body with the MIKEY message containing the encrypted MuSiK and the corresponding MuSiK-ID, constructed as described in clauses 5.8.1 and 5.2.2 of 3GPP TS 33.180 [8]; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 299 NOTE: Clause 9.2.1.3 of 3GPP TS 33.180 [8] shows an example on how to include an application/mikey MIME body in a SIP message. 7) shall send the SIP MESSAGE request towards the MCVideo client according to 3GPP TS 24.229 [11]. The participating MCVideo function shall consider the key download successful on receipt of a 200 (OK) message in response to the SIP MESSAGE request sent in step 7). A participating MCVideo function that does not receive a 200 (OK) message from a specific MCVideo client shall use unicast signalling for transmission control towards that MCVideo client for the groups for which the MuSiK was intended." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 16.3.3] "Upon receiving a "SIP MESSAGE request for an MBMS listening status update", the participating MCVideo function shall handle the request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [17]. If the SIP MESSAGE request contains: 1) an application/vnd.3gpp.mcvideo-mbms-usage-info+xml MIME body with an <mbms-listening-status> element; and 2) an application/vnd.3gpp.mcvideo-info+xml MIME body containing an MCVideo ID in the <mcvideo-request- uri> served by the participating MCVideo function; then the participating MCVideo function: 1) shall verify that the public user identity in the P-Asserted-Identity header field is bound to the MCVideo ID in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, and if that is the case: a) if the <mbms-listening-status> element is set to "listening": i) if <session-identifier> elements are included, shall indicate to the media plane that the MCVideo client in the session identified by the <session-identifier> element is now listening to the MBMS subchannel; and ii) if <general-purpose> element is included with the value "true", shall indicate to the media plane that the MCVideo client is now listening to the general purpose MBMS subchannel; and b) if the <mbms-listening-status> element is set to "not-listening": i) if <session-identifier> elements are included, shall indicate to the media plane that the MCVideo client in the sessions identified by the <session-identifier> elements is not listening to the MBMS subchannel; ii) if <general-purpose> element is included with the value "false", shall indicate to the media plane that the MCVideo client is no longer listening to the general purpose MBMS bearer; and iii) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. NOTE 1: If the MCVideo client reports that the MCVideo client is no longer listening to the general purpose MBMS subchannel it is implicitly understood that the MCVideo client no longer listens to any MBMS subchannel in ongoing transmissions that the MCVideo client previously reported status "listening". If the SIP MESSAGE request contains: 1) an application/vnd.3gpp.mcvideo-mbms-usage-info+xml MIME body with an <mbms-suspension-status> element; and 2) an application/vnd.3gpp.mcvideo-info+xml MIME body containing an MCVideo ID in the <mcvideo-request- uri> served by the participating MCVideo function; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 300 then the participating MCVideo function: 1) shall verify that the public user identity in the P-Asserted-Identity header field is bound to the MCVideo ID in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, and if that is the case: a) if the <mbms-suspension-status> element is set to "suspending": i) shall consider that the bearer identified by the <suspended-TMGI> element is about to be suspended and that the reduction or elimination of traffic on that bearer and/or on some of the bearers indicated in the <other-TMGI> elements can potentially avoid the suspension; and NOTE 2: An MBMS bearer is about to be suspended when RAN has notified the clients of the decision to suspend the bearer, but the actual suspension, which would occur at the end of the MCCH modification period, has not taken place yet because the MCCH modification period has not yet expired. ii) may take implementation/configuration specific immediate action for the MCVideo client that reports the suspension as well as other MCVideo clients that listen to the same bearer (e.g. moving traffic to unicast bearer(s)), reducing transmission rate, eliminating traffic, modifying pre-emption priority). b) if the <mbms-suspension-status> element is set to "not-suspending": i) shall consider that the bearer identified by the <suspended-TMGI> element is no longer about to be suspended; and NOTE 3: An MBMS bearer is no longer about to be suspended when RAN has notified the clients of the decision to no longer suspend the bearer after having previously notified the clients that the bearer would be suspended at the end of the MCCH modification period. The RAN notifications to first suspend and subsequently not to suspend the same MBMS bearer would have to come within the same MCCH modification period. ii) may take implementation/configuration specific immediate action for the MCVideo client that reports the suspension as well as other MCVideo clients that listen to the same bearer (e.g. restoring traffic previously reduced or eliminated from MBMS bearers upon reception of suspension information). NOTE 4: If the MCVideo client reports that the MCVideo client is no longer listening to MBMS subchannels associated with the MBMS bearer indicated in the suspension information, it is implicitly understood that the suspension of that MBMS bearer has actually occurred." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 4.1.2.1] "The participating MCVideo function can use an MBMS bearer for the DL transmission of the media and the media control plane. The participating MCVideo function decides to activate an MBMS bearer. After the activation of the MBMS bearer, as specified in 3GPP TS 29.468 [6], the TMGI of this MBMS bearer is announced to the MCVideo clients in the MBMS service area of this MBMS bearer. This announcement enables the MCPVideo client to listen (decode/demodulate) this MBMS bearer. The activation of an MBMS bearer and the announcement of the TMGI create a pool of MBMS subchannel resources without any association to a group or other purposes. The criteria for a participating MCPVideo function to decide to activate and use an MBMS bearer is implementation dependent. An MBMS bearer can be used for the DL transmission for more than one group. For this, additional parameters like destination UDP port are used for enabling the differentiation of messages and packets belonging to different groups over the same MBMS bearer by a receiving MCVideo client. When a TMGI is announced a general purpose MBMS subchannel is created by defining an association between the identity of the general purpose MBMS subchannel (e.g. 'general purpose') and the TMGI (of the activated and announced MBMS bearer) together with the parameters (e.g. UDP port) differentiating this general purpose MBMS subchannel in this MBMS bearer. The parameters of this general purpose MBMS subchannel can be communicated to the MCVideo clients in the MBMS service area of this MBMS bearer using unicast over-the air transmission or can be pre-defined and stored in the MCVideo user profile that is downloaded to the MCVideo UE." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 301 [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 4.1.2.2] "When a MCVideo transmission starts, the participating MCVideo function can allocate an MBMS subchannel for this group by defining an association between this group (e.g. 'group id') and the TMGI (of the activated and announced MBMS bearer) with the parameters differentiating this MBMS subchannel in this MBMS bearer. The parameters of this MBMS subchannel are sent using the general purpose MBMS subchannel using the Map Group To Bearer message. The Map Group To Bearer message is repeated as long as the communication is ongoing for improving the reception probability and to allow MCVideo clients arriving late to listen to the MBMS subchannel. The Map Group To Bearer provides the multicast IP destination address and the destination ports used to deliver the transmission control messages, the audio and video media packets, the FEC repair packets." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 4.1.2.3] "If an MBMS subchannel exists, the participating MCVideo function forwards the media plane control messages, received from the controlling MCVideo function via MBMS subchannel for media plane control. Only transmission control messages which are transmitted to more than one affiliated group member are forwarded to the MBMS bearer (e.g. the Media transmission notification, Transmission Idle and Transmission end notify messages). Transmission control messages can be repeated as long as the transmission is on going for improving the reception probability. The participating MCVideo function forwards the media packets, received from the controlling MCVideo function, via the MBMS subchannel for media. Amongst all affiliated group members under this participating MCVideo function, the participating MCVideo function is informed or is enabled to deduce the group members which do not or cannot receive the MBMS subchannels. The participating MCVideo function forwards the media packets and the media plane control messages, received from the controlling MCVideo function, to the group members which do not or cannot receive the MBMS subchannels, using unicast bearers allocated for media and media plane control respectively." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 4.1.2.4] "The participating MCVideo function can de-allocate an MBMS subchannel after a configurable period of silence in the transmission by removing the association to this group by sending the Unmap Group To Bearer message over this MBMS subchannel. The de-allocation of the MBMS subchannel frees the parameters used for differentiating this MBMS subchannel in this MBMS bearer. Therefore, the resources of a de-allocated MBMS subchannel can be reallocated for a transmission of another group. NOTE: The participating MCVideo function will activate MBMS bearers with general QoS characteristics suitable for MCVideo service and will map MBMS subchannels for media or media plane control only to MBMS bearers that can provide the QoS required by media or media plane control." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 4.1.2.5] "The participating MCVideo function can activate an MBMS bearer that previously has been announced over a unicast bearer by sending an MBMS bearer announcement over an MBMS bearer. The MCVideo client acknowledges that it can listen to the MBMS bearer by sending a listening status report." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; … 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 302 iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and … 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 10.2.1] "If the participating MCVideo function supports the MBMS subchannel control procedure, the participating MCVideo function shall support the behaviour implied by the state machine specified in this clause. The specifications are on the reception of transmission control messages from the controlling MCVideo function, sending of transmission control messages and the allocation/deallocation of MBMS subchannels for a transmission in a group session. Figure 10.2.1-1 shows the participating MCVideo function MBMS subchannel control state diagram. … If a transmission control message or RTP media packet arrives in a state where there are no procedures specified in the clauses below, the participating MCVideo function shall discard the message. …" ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 303 [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 13.3.2] "The participating MCVideo function: 1. if protection of media is negotiated, shall be transparent to RTP media streams and shall forward encrypted RTP media streams without decrypting the payload; 2. if protection of transmission control and reception control messages sent using unicast between the participating MCVideo function and the MCVideo client is negotiated and the CSK and the CSK-ID were received from the MCVideo client using SIP signalling according to 3GPP TS 24.281 [2]: A) shall encrypt transmission control and reception control messages sent using unicast to the served MCVideo client according to IETF RFC 3711 [4] and 3GPP TS 33.180 [8] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the CSK and CSK-ID as specified in clause 13.2; and B) shall decrypt transmission control and reception control messages received using unicast from the served MCVideo client according to IETF RFC 3711 [4] and 3GPP TS 33.180 [8] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the CSK and CSK-ID as specified in clause 13.2; 3. if protection of transmission control messages sent over the MBMS subchannel from the participating MCVideo function to the served MCVideo clients is required and a MuSiK and a MuSiK-ID are associated with the on-network group call of the transmission control messages: A) shall encrypt transmission control messages sent over the MBMS subchannel according to IETF RFC 3711 [16] and 3GPP TS 33.180 [8] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the MuSiK and MuSiK-ID as specified in clause 13.2; … 6. if protection of media control messages sent using unicast between the participating MCVideo function and the MCVideo client is negotiated between the participating MCVideo function and the MCVideo client and the CSK and the CSK-ID were received from the MCVideo client using SIP signalling according to 3GPP TS 24.281 [2]; A) shall encrypt media control messages sent using unicast to the served MCVideo client according to IETF RFC 3711 [4] and 3GPP TS 33.180 [8] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the CSK and CSK-ID as specified in clause 13.2; and B) shall decrypt media control messages received using unicast from the served MCVideo client according to IETF RFC 3711 [4] and 3GPP TS 33.180 [8] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the CSK and CSK-ID as specified in clause 13.2; … 9. if protection of MBMS subchannel control messages sent over the general purpose MBMS subchannel of an MBMS bearer is required and the MSCCK and the MSCCK-ID associated with the MBMS bearer were sent to one or more served MCVideo clients using SIP signalling according to 3GPP TS 24.281 [11]: A) shall encrypt MBMS subchannel control messages specified in clause 9.3 sent over the general purpose MBMS subchannel of the MBMS bearer according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the MSCCK and MSCCK-ID associated with the MBMS bearer as specified in clause 13.2." [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 9.3.1] "The MBMS subchannel control messages shall be coded as described in clause 9.1.2 where the MBMS subchannel control message is part of the application-dependent data. For the MBMS subchannel control protocol the ASCII name string shall be: MCV3. The list of MBMS subchannel control messages can be found in the clause 9.3.2. The MBMS subchannel control specific fields are specified in clause 9.3.3." ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 304 [ETSI TS 124 581 [9] (3GPP TS 24.581), clause 9.4.1] "The MBMS notifications messages shall be coded as described in clause 8.1.2 where the MBMS notifications message is part of the application-dependent data. For the MBMS notifications protocol the ASCII name string shall be: MCNC. The list of MBMS notifications messages can be found in the clause 9.4.2. The MBMS notifications specific fields are specified in clause 9.4.3." |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.7.1.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.7.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client), the SS-UE2 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server and Controlling Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The SS-UE1 (MCVideo Client) and the SS-UE2 (MCVideo Client) perform the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) are affiliated to the Prearranged group. - The IUT (MCVideo Server) is the controlling server of the Prearranged group. - A pre-activated MBMS bearer exists ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 305 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.7.1.3.2 Test procedure sequence | Table 6.7.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCVideo Client) requests the establishment of a group call to SS-UE2 (MCVideo Client) with automatic commencement mode and without implicit transmission request. - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.3.1.3-1 to establish a pre-arranged group call with automatic commencement mode and without implicit transmission control request according to option a of note in Annex A, Table A.3.1.3-1? - - 1 P 3 Make the IUT (MCVideo Server) activate an MBMS bearer and send an MBMS bearer announcement to notify bearer availability (note) - - - - - EXCEPTION: Depending on the IUT (MCVideo Server) implementation, steps 4a-4b and steps 5a-5b might be performed in parallel - - - - 4a Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to send a MBMS bearer announcement to notify MBMS bearer availability to SS-UE1 (MCVideo Client)? - - 2 P 4b Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to send a MBMS Bearer listening status report message to IUT (MCVideo Server), to notify SS-UE1 (MCVideo Client) being listening to general-purpose subchannel? - - 3 P 5a Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to send a MBMS bearer announcement to notify MBMS bearer availability to SS-UE2 (MCVideo Client)? - - 4 P 5b Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to send a MBMS Bearer listening status report message to IUT (MCVideo Server), to notify SS-UE2 (MCVideo Client) being listening to general-purpose subchannel? - - 5 P 6 Make the SS-UE1 (MCVideo Client) request transmission. - - - - 7 Check: Does the IUT (MCVideo Server) correctly perform steps 1-2 of procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1 over unicast bearer? - - 6 P 8 Make the IUT (MCVideo Server) use MBMS subchannel for the conversation. (Note) - - - - 9 Check: Does the IUT (MCVideo Server) send a Map Group To Bearer message over general purpose MBMS subchannel? <-- Map Group To Bearer 7 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 306 St Procedure Message Sequence TP Verdict U - S Message 10 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to send a MBMS Bearer listening status report message to IUT (MCVideo Server), to notify SS-UE1 (MCVideo Client) being listening to media and transmission control over MBMS subchannel? - - 8 P 11 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to send a MBMS Bearer listening status report message to IUT (MCVideo Server), to notify SS-UE2 (MCVideo Client) being listening to media and transmission control over MBMS subchannel? - - 9 P 12 Check: Does the IUT (MCVideo Server) send a Transmission Granted message using unicast bearer to SS-UE1 (MCVideo Client)? <-- Transmission Granted 10 P 13 IF the Transmission Granted message requires acknowledgement, the SS-UE1 (MCVideo Client) responds with a Transmission Control Ack message to IUT (MCVideo Server). --> Transmission Control Ack - - 14 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to SS- UE2 (MCVideo Client) using multicast bearer? <-- Media Transmission Notification 10 P 15 Make the SS-UE2 (MCVideo Client) request media reception. - - - - 16 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Media Reception Request and Response' as described in Annex A, Table A.3.9.3-1 for SS-UE2 (MCVideo Client) using unicast bearer? - - 11 P - EXCEPTION: Depending on the MCVideo Server implementation, steps 17-18 might be performed in parallel. - - - - 17 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to send a message containing a MuSiK download message to set the explicit MuSiK key to be used for the transmission control encryption over the MBMS subchannel to SS- UE1 (MCVideo Client)? - - 12 P 18 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to send a message containing a MuSiK download message to set the explicit MuSiK key to be used for the transmission control encryption over the MBMS subchannel to SS- UE2 (MCVideo Client)? - - 12 P 19 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 20 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1, except steps 3a5-3a8 and 3b3-3b4, using unicast bearer? - - 13 P 21 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) using multicast bearer? <-- Transmission Idle 14 P ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 307 St Procedure Message Sequence TP Verdict U - S Message 22 Make the IUT (MCVideo Server) stop using MBMS subchannel for the conversation. (Note) - - - - 23 Check: Does the IUT (MCVideo Server) send an Unmap Group To Bearer message over general purpose MBMS subchannel? <-- Unmap Group To Bearer 14 P 24 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to send a MBMS Bearer listening status report message to IUT (MCVideo Server), to notify SS-UE1 (MCVideo Client) not being listening to media and transmission control over MBMS subchannel? - - 15 P 25 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to send a MBMS Bearer listening status report message to IUT (MCVideo Server), to notify SS-UE2 (MCVideo Client) not being listening to media and transmission control over MBMS subchannel? - - 16 P 26 Make the IUT (MCVideo Server) stop using MBMS bearer. (Note) - - - - - EXCEPTION: Depending on the IUT (MCVideo Server) implementation, steps 27a-27b and steps 28a-28b might be performed in parallel - - - - 27a Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to send a MBMS bearer cancellation announcement to notify MBMS bearer unavailability to SS-UE1 (MCVideo Client)? - - 17 P 27b Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to send a MBMS Bearer listening status report message to IUT (MCVideo Server), to notify SS-UE1 (MCVideo Client) not being listening to general-purpose subchannel? - - 18 P 28a Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to send a MBMS bearer cancellation announcement to notify MBMS bearer unavailability to SS-UE2 (MCVideo Client)? - - 17 P 28b Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to send a MBMS Bearer listening status report message to IUT (MCVideo Server), to notify SS-UE2 (MCVideo Client) not being listening to general-purpose subchannel? - - 19 P 29 Make the SS-UE1 (MCVideo Client) request transmission. - - - - 30 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1 using unicast bearers? - - 6 P 31 Make the SS-UE2 (MCVideo Client) request media reception. - - - - ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 308 St Procedure Message Sequence TP Verdict U - S Message 32 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Media Reception Request and Response' as described in Annex A, Table A.3.9.3-1 for SS-UE2 (MCVideo Client) using unicast bearer? - - 11 P 33 Make the SS-UE1 (MCVideo Client) request end of transmission. - - - - 34 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify ' as described in Annex A, Table A.3.8.3-1, using unicast bearer? - - 13 P 35 Make the SS-UE1 (MCVideo Client) release the call. - - - - 36 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX E2E call release' as described in Annex A, Table A.2.19.3-1? - - 20 P NOTE: This is expected to be done via a suitable implementation dependent MMI. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.7.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.7.1.3.3-1: SIP INVITE from the SS-UE1 (Step 2, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 1, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-1, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.7.1.3.3-2: SIP INVITE from the IUT (MCVideo Server) (Step 2, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1; Step 2, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-4, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.7.1.3.3-3: SIP 200 (OK) from the SS-UE2 (Steps 2, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 5, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-7, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.7.1.3.3-4: SIP 200 (OK) from the IUT (MCVideo Server) (Step 2, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.3.1.3-1, Step 6, Annex A, Table A.2.18.3-1) Derivation Path: Annex A, Table A.3.1.4-9, with condition GROUP-CALL. NOTE: Condition is also applied to all body parts. Table 6.7.1.3.3-5: Transmission Granted (Step 12, Table 6.7.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.1-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 309 Table 6.7.1.3.3-6: Transmission Control Ack (Step 13, Table 6.7.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK Table 6.7.1.3.3-7: Media Transmission Notification (Step 14, Table 6.7.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.7-1 Information Element Value/remark Comment Reference Condition User Id of the Transmitting User User ID of the user transmitting the media ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.6 User Id of the Transmitting User px_MCVideo_ID_User_A Audio SSRC of the Transmitting User Media/Audio SSRC of remote client (Client A) SSRC of the user transmitting the media ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.16 Functional Alias not present Table 6.7.1.3.3-8: Transmission Idle (Step 21, Table 6.7.1.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.16-1 Table 6.7.1.3.3-9: Map Group To Bearer from the IUT (MCVideo Server) (Step 9, Table 6.7.1.3.2-1) Derivation Path: ETSI TS 124 581 [9] (3GPP TS 24.581), Table 9.3.4-1. Information Element Value/remark Comment Condition RTCP header Subtype 00000 Map Group To Bearer SSRC The SSRC of the message sender The SSRC of the IUT (MCVideo Server). Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [25]. name MCV3 MCVideo Group ID px_MCVideo_Group_A_ID The group ID of the call TMGI MBMS Service ID "0F0F0F" The selected value is randomly chosen - a 6 digit hexadecimal number between 000000 and FFFFFF (see ETSI TS 123 003 [26] (3GPP TS 23.003 clause 15.2. The coding of the MBMS Service ID is the responsibility of each administration MCC The same value as for PLMN1 specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.1-1 Mobile Country Code MNC The same value as for PLMN1 specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.1-1 Mobile Network Code MBMS Subchannel Video m-line Number "2" Audio m-line Number "1" The number of the "m=audio" m-line in the SIP MESSAGE request announcing the MBMS bearer Control m-line Number "3" ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 310 Derivation Path: ETSI TS 124 581 [9] (3GPP TS 24.581), Table 9.3.4-1. Information Element Value/remark Comment Condition FEC m-line Number "0" IP version "0" '0' = IP version 4 '1' = IP version 6 All other values are reserved for future use Transmission Control Port Number "9" The port to be used if the<Transmission Control m- line Number> value is greater than '0'. If the < Transmission Control m-line Number> value is equal to '0', the < Transmission Control control Port Number> value is not included in the MBMS Subchannel field Video Media Port Number "9" Audio Media Port Number "9" FEC Port Number not present IP Address "0.0.0.0" Table 6.7.1.3.3-10: Unmap Group To Bearer from the IUT (MCVideo Server) (Step 23, Table 6.7.1.3.2-1) Derivation Path: ETSI TS 124 581 [9] (3GPP TS 24.581), Table 9.3.5-1. Information Element Value/remark Comment Condition RTCP header Subtype "00001" Map Group To Bearer SSRC The SSRC of the message sender The SSRC of the IUT (MCVideo Server). Notation in accordance with clause 5.5.6.1. Coded as specified in IETF RFC 3550 [25]. name MCV3 MCVideo Group ID px_MCVideo_Group_A_ID The group ID of the call Table 6.7.1.3.3-11: SIP MESSAGE from the IUT (MCVideo Server) to SS-UE1 (Step 4a, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCVIDEO Information Element Value/remark Comment Reference Condition P-Asserted-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcvideo" P-Asserted-Identity addr-spec tsc_MCVideo_PublicServiceId _A Message-body MIME body part SDP message MIME-part-headers Content-Type "application/sdp" Content-Disposition "render" MIME-part-body SDP message as described in Table 6.7.1.3.3-13 MIME body part MCVideo MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcvide o-mbms-usage-info+xml" ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 311 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCVIDEO Information Element Value/remark Comment Reference Condition MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-14 MIME body part MCVideo-Info MIME-part-headers Content-Type "application/vnd.3gpp.mcvide o-info+xml " MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-15 Table 6.7.1.3.3-12: SIP MESSAGE from the IUT (MCVideo Server) to SS-UE2 (Step 5a, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: Table 6.7.1.3.3-11 Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-headers MIME-part-body SDP message as described in Table 6.7.1.3.3-13 MIME body part MCVideo MBMS usage info MIME-part-headers MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-14 MIME body part MCVideo-Info MIME-part-headers MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-16 Table 6.7.1.3.3-13: SDP in SIP MESSAGE (Tables 6.7.1.3.3-11 and 6.7.1.3.3-12) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.2-2 Information Element Value/remark Comment Referenc e Condition Media description media description[1] m= line media = audio media "audio" port "9" proto "RTP/AVP" fmt "99" media title "speech" Connection Data nettype "IN" Addrtype "IP4" or "IP6" depending on IP address connection-address "0.0.0.0" (IPv4) or domain name within ".invalid" DNS top level domain (IPv6) media description[2] m= line media = video media "video" port "9" proto "RTP/AVP" fmt "100" Connection Data nettype "IN" Addrtype "IP4" or "IP6" depending on IP address ETSI ETSI TS 104 151-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.2-2 Information Element Value/remark Comment Referenc e Condition connection-address "0.0.0.0" (IPv4) or domain name within ".invalid" DNS top level domain (IPv6) media description[3] m= line media = application media "application" port "9" proto "udp" fmt "MCVideo" Connection Data nettype "IN" Addrtype "IP4" or "IP6" depending on IP address connection-address "0.0.0.0" (IPv4) or domain name within ".invalid" DNS top level domain (IPv6) media description[4] m= line media = application media "application" port port number assigned by the IUT (MCVideo Server) proto "udp" fmt "MCVideo" Connection Data c= line nettype "IN" addrtype "IP4" connection-address multicast IP assigned by the IUT (MCVideo Server) media attribute a= line attribute = key-mgmt key-mgmt mikey MIKEY-SAKKE I_MESSAGE as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.9.1-2 MSCCK distribution as specified in ETSI TS 133 180 [7] (3GPP TS 33.180) Annex H ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 313 Table 6.7.1.3.3-14: MCVideo-MBMS-Usage-Info in SIP MESSAGE (Tables 6.7.1.3.3-11 and 6.7.1.3.3-12) Derivation Path: ETSI TS 124 281 [8] (3GPP TS 24.281), Clause F.2 Information Element Value/remark Comment Reference Condition mcvideo-mbms-usage-info mbms-listening-status not present mbms-suspension-status not present announcement TMGI MBMS Service ID "0F0F0F" The selected value is randomly chosen - a 6 digit hexadecimal number between 000000 and FFFFFF (see ETSI TS 123 003 [26] (3GPP TS 23.003) clause 15.2. The coding of the MBMS Service ID is the responsibility of each administration MCC The same value as for PLMN1 specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.1-1 Mobile Country Code MNC The same value as for PLMN1 specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.1-1 Mobile Network Code QCI "67" mbms-service-areas "0" The selected value is randomly chosen. The value 0 has a special meaning; it shall denote the whole PLMN as the MBMS Service Area GPMS "3" version "1" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.3.2 Table 6.7.1.3.3-15: MCVideo-Info in SIP MESSAGE (Table 6.7.1.3.3-11) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-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 [8] (3GPP TS 24.281) clause 16.3.2.2 mcvideo-calling-user-id not present NOTE: Encrypted element as described in Table 5.5.3.2.2-2A. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 314 Table 6.7.1.3.3-16: MCVideo-Info in SIP MESSAGE (Table 6.7.1.3.3-12) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-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_B ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.3.2.2 mcvideo-calling-user- id not present NOTE: Encrypted element as described in Table 5.5.3.2.2-2A. Table 6.7.1.3.3-17: SIP MESSAGE from the SS-UE1 (Step 4b, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCVIDEO Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (tsc_MCVideo_PublicServiceId_A) Message-body MIME body part MCVideo MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- mbms-usage-info+xml" MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-19 MIME body part MCVideo-Info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- info+xml " MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-20 Table 6.7.1.3.3-18: SIP MESSAGE from the SS-UE2 (Step 5b, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCVIDEO Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (tsc_MCVideo_PublicServiceId _A) Message-body MIME body part MCVideo MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- mbms-usage-info+xml" MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-19 MIME body part MCVideo-Info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- info+xml " MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-21 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 315 Table 6.7.1.3.3-19: MCVideo-MBMS-Usage-Info in SIP MESSAGE (Tables 6.7.1.3.3-17 and 6.7.1.3.3-18) Derivation Path: ETSI TS 124 281 [8] (3GPP TS 24.281), Clause F.2 Information Element Value/remark Comment Reference Condition mcvideo-mbms-usage-info mbms-listening-status ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.2.3.2 mbms-listening-status "listening" session-id not present general-purpose "true" TMGI same value as the announcement in the SIP MESSAGE mbms-suspension-status not present announcement not present version "1" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.2.3.2 Table 6.7.1.3.3-20: MCVideo-Info in SIP MESSAGE (Table 6.7.1.3.3-17) 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 [8] (3GPP TS 24.281) clause 16.2.3.2 mcvideo-calling-user-id not present NOTE: Encrypted element as described in Table 5.5.3.2.1-2A. Table 6.7.1.3.3-21: MCVideo-Info in SIP MESSAGE (Table 6.7.1.3.3-18) 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_B ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.2.3.2 mcvideo-calling-user-id not present NOTE: Encrypted element as described in Table 5.5.3.2.1-2A. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 316 Table 6.7.1.3.3-22: SIP MESSAGE from the SS-UE1 (Step 10, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCVIDEO Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (tsc_MCVideo_PublicServiceId _A) Message-body MIME body part MCVideo MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- mbms-usage-info+xml" MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-24 MIME body part MCVideo-Info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- info+xml " MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-20 Table 6.7.1.3.3-23: SIP MESSAGE from the SS-UE2 (Step 11, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCVIDEO Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (tsc_MCVideo_PublicServiceId _A) Message-body MIME body part MCVideo MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- mbms-usage-info+xml" MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-24 MIME body part MCVideo-Info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- info+xml " MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-21 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 317 Table 6.7.1.3.3-24: MCVideo-MBMS-Usage-Info in SIP MESSAGE (Tables 6.7.1.3.3-22 and 6.7.1.3.3-23) Derivation Path: ETSI TS 124 281 [8] (3GPP TS 24.281), Clause F.2 Information Element Value/remark Comment Reference Condition mcvideo-mbms-usage-info mbms-listening-status ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.2.3.2 mbms-listening-status "listening" session-id px_sesson_A_ID general-purpose not present TMGI same value as the announcement in the SIP MESSAGE mbms-suspension-status not present announcement not present version "1" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.2.3.2 Table 6.7.1.3.3-25: SIP MESSAGE from the IUT (MCVideo Server) to SS-UE1 and SS-UE2 (Step 17 and 18, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, with conditions MCVIDEO and MIKEY Information Element Value/remark Comment Reference Condition P-Asserted-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcvideo" P-Asserted-Identity addr-spec tsc_MCVideo_PublicServiceId_ A Message-body MIME body part MCVideo MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- mbms-usage-info+xml" MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-26 Table 6.7.1.3.3-26: MCVideo-MBMS-Usage-Info in SIP MESSAGE (Tables 6.7.1.3.3-25) Derivation Path: ETSI TS 124 281 [8] (3GPP TS 24.281), Clause F.2 Information Element Value/remark Comment Reference Condition mcvideo-mbms-usage-info mbms-listening-status not present mbms-suspension-status not present announcement not present version "1" anyExt mbms-explicitMuSiK-download group px_MCVideo_Group_A_ ID ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 318 Table 6.7.1.3.3-27: SIP MESSAGE from the SS-UE1 (Step 24, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCVIDEO Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (tsc_MCVideo_PublicServiceId _A) Message-body MIME body part MCVideo MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- mbms-usage-info+xml" MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-29 MIME body part MCVideo-Info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- info+xml " MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-20 Table 6.7.1.3.3-28: SIP MESSAGE from the SS-UE2 (Step 25, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCVIDEO Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (tsc_MCVideo_PublicServiceId _A) Message-body MIME body part MCVideo MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- mbms-usage-info+xml" MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-29 MIME body part MCVideo-Info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- info+xml " MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-21 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 319 Table 6.7.1.3.3-29: MCVideo-MBMS-Usage-Info in SIP MESSAGE (Tables 6.7.1.3.3-27 and 6.7.1.3.3-28) Derivation Path: ETSI TS 124 281 [8] (3GPP TS 24.281), Clause F.2 Information Element Value/remark Comment Reference Condition mcvideo-mbms-usage-info mbms-listening-status ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.2.3.2 mbms-listening-status "not-listening" session-id px_sesson_A_ID general-purpose not present TMGI same value as the announcement in the SIP MESSAGE mbms-suspension-status not present announcement not present version "1" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.2.3.2 Table 6.7.1.3.3-30: SIP MESSAGE from the IUT (MCVideo Server) to SS-UE1 (Step 27a, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCVIDEO Information Element Value/remark Comment Reference Condition P-Asserted-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcvideo" P-Asserted-Identity addr-spec tsc_MCVideo_PublicServiceId_ A MIME body part MCVideo MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- mbms-usage-info+xml" MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-32 MIME body part MCVideo-Info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- info+xml " MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-15 Table 6.7.1.3.3-31: SIP MESSAGE from the IUT (MCVideo Server) to SS-UE2 (Step 28a, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: Table 6.7.1.3.3-11 Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo MBMS usage info MIME-part-headers MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-32 MIME body part MCVideo-Info MIME-part-headers MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-16 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 320 Table 6.7.1.3.3-32: MCVideo-MBMS-Usage-Info in SIP MESSAGE (Tables 6.7.1.3.3-30 and 6.7.1.3.3-31) Derivation Path: ETSI TS 124 281 [8] (3GPP TS 24.281), Clause F.2 Information Element Value/remark Comment Reference Condition mcvideo-mbms-usage-info mbms-listening-status not present mbms-suspension-status not present announcement TMGI MBMS Service ID "0F0F0F" The selected value is randomly chosen - a 6 digit hexadecimal number between 000000 and FFFFFF (see ETSI TS 123 003 [26] (3GPP TS 23.003 clause 15.2. The coding of the MBMS Service ID is the responsibility of each administration MCC The same value as for PLMN1 specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.1-1 Mobile Country Code MNC The same value as for PLMN1 specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.1-1 Mobile Network Code QCI "67" mbms-service-areas not present GPMS not present version "1" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.3.2 Table 6.7.1.3.3-33: SIP MESSAGE from the SS-UE1 (Step 27b, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCVIDEO Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (tsc_MCVideo_PublicServiceId _A) Message-body MIME body part MCVideo MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- mbms-usage-info+xml" MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-35 MIME body part MCVideo-Info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- info+xml " MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-20 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 321 Table 6.7.1.3.3-34: SIP MESSAGE from the SS-UE2 (Step 28b, Table 6.7.1.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1, condition MCVIDEO Information Element Value/remark Comment Reference Condition Request-Line Request-URI The value received in the P- Asserted-Identity header field of the announcement message (tsc_MCVideo_PublicServiceId _A) Message-body MIME body part MCVideo MBMS usage info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- mbms-usage-info+xml" MIME-part-body MCVideo MBMS Usage Info as described in Table 6.7.1.3.3-35 MIME body part MCVideo-Info MIME-part-headers Content-Type "application/vnd.3gpp.mcvideo- info+xml " MIME-part-body MCVideo-Info as described in Table 6.7.1.3.3-21 Table 6.7.1.3.3-35: MCVideo-MBMS-Usage-Info in SIP MESSAGE (Tables 6.7.1.3.3-33 and 6.7.1.3.3-34) Derivation Path: ETSI TS 124 281 [8] (3GPP TS 24.281), Clause F.2 Information Element Value/remark Comment Reference Condition mcvideo-mbms-usage-info mbms-listening-status ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.2.3.2 mbms-listening-status "not-listening" session-id not present general-purpose "false" TMGI same value as the announcement in the SIP MESSAGE mbms-suspension-status not present announcement not present version "1" ETSI TS 124 281 [8] (3GPP TS 24.281) clause 16.2.3.2 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 322 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8 Location | 6.8.1 MCVideo Server - MCVideo Client / Location / Event Triggered Location Information report |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { IUT (MCVideo Server) requests to send a location reporting configuration } then { IUT (MCVideo Server) sends a SIP MESSAGE message containing the cell change trigger criteria and the minimum report interval to the SS-UE1 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having received Location Information report } ensure that { when { SS-UE1 (MCVideo Client) requests location report containing the cell change trigger identification along with the location information report, the current location coordinates and the current serving ECGI by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.1.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 18.2.2, 18.2.4, 18.3.2, 18.3.4.1, 18.3.4.2, 6.2.9.1. Unless otherwise stated these are Rel-16 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 18.2.2] "The participating MCVideo function may configure the location reporting in the MCVideo client by generating a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [17]. The participating MCVideo function: 1) shall include a Request-URI set to the URI corresponding to the identity of the MCVideo client; 2) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [20]; 3) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with an <mcvideo-request-uri> element containing the MCVideo ID of the MCVideo user to receive the configuration; 4) shall include an application/vnd.3gpp.mcvideo-location-info+xml MIME body with the <Configuration> element contained in the <location-info> root element set to the desired configuration; 5) shall include the TriggerId attribute where defined for the sub-elements defining the trigger criterion; 6) shall include the public service identity of the participating MCVideo function in the P-Asserted-Identity header field; 7) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; and 8) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 18.2.4] "If the participating MCVideo function receives a SIP request containing: 1) a Content-Type header field set to "application/vnd.3gpp.mcvideo-location-info+xml"; and ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 323 2) an application/vnd.3gpp.mcvideo-location-info+xml MIME body with a <Report> element included in the <location-info> root element; then the participating MCVideo function shall authorise the location report based on the MCVideo ID received. If the MCVideo user is authorised to send a location report the participating MCVideo function: 1) shall use the location information as needed. NOTE: The <Report> element contains the event triggering identity in the location information report from the UE, and can contain location information." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 18.3.2] "Upon receiving a SIP MESSAGE request containing: 1) an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp- service.ims.icsi.mcvideo"; 2) a Content-Type header field set to "application/vnd.3gpp.mcvideo-location-info+xml"; and 3) an application/vnd.3gpp.mcvideo-location-info+xml MIME body with a <Configuration> root element included in the <location-info> root element; then the MCVideo client: 1) shall store the contents of the <Configuration> elements; 2) shall set the location reporting triggers accordingly; and 3) shall start the minimumReportInterval timer." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 18.3.4.1] "If a location reporting trigger fires the MCVideo client checks if the minimumReportInterval timer is running. If the timer is running the MCVideo client waits until the timer expires. When the minimumReportInterval timer expires, the MCVideo client: 1) shall, if any of the reporting triggers are still true, send a location information report as specified in clause 18.3.4.2. If the MCVideo client receives a location information request as specified in clause 18.3.3, the MCVideo client shall send a location report as specified in clause 18.3.4.2." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 18.3.4.2] "If the MCVideo client needs to send a SIP request for other reasons (e.g. a SIP MESSAGE request containing an MBMS listening report as described in clause 16), the MCVideo client: 1) shall include an application/vnd.3gpp.mcvideo-location-info+xml MIME body and in the <location-info> root element the MCVideo client shall include: a) a <Report> element and if the Report was triggered by a location request include the <ReportID> attribute set to the value of the <RequestID> attribute in the received Request; b) <TriggerId> child elements, where each element is set to the value of the <Trigger-Id> attribute associated with the trigger that have fired; and c) the location reporting elements corresponding to the triggers that have fired; 2) shall set the minimumReportInterval timer to the minimumReportInterval time and start the timer; and 3) shall reset all triggers. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 324 If the MCVideo client does not need to send a SIP request for other reasons, the MCVideo client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [17]. The MCVideo client; 1) shall include in the Request-URI, the SIP URI received in the P-Asserted-Identity header field in the received SIP MESSAGE request for location report configuration; 2) shall include a Content-Type header field set to "application/vnd.3gpp.mcvideo-location-info+xml"; 3) shall include an application/vnd.3gpp.mcvideo-location-info+xml MIME body and in the <location-info> root element include: a) a <Report> element and if the Report was triggered by a location request include the <ReportID> attribute set to the value of the <RequestID> attribute in the received Request; b) a <TriggerId> child element set to the value of each <Trigger-Id> value of the triggers that have fired; and c) the location reporting elements corresponding to the triggers that have fired; 4) shall include an Accept-Contact header field with the media feature tag g.3gpp.mcvideo along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [20]; 5) shall set the minimumReportInterval timer to the minimumReportInterval time and start the timer; 6) shall reset all triggers; and 7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.2.9.1] "This procedure is initiated by the MCVideo client when it is including location report information as part of a SIP request for a specified location trigger. The MCVideo client: 1) shall include an application/vnd.3gpp.location-info+xml MIME body as specified in Annex F.3 with a <Report> element included in the <location-info> root element; and 2) shall include in the <Report> element the specific location information configured for the specified location trigger." |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.1.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.1.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 325 - The IUT (MCVideo Server) is the acting Participating Server Preamble: - The IUT (MCVideo Server) is connected to PLMN1 - The IUT (MCVideo Server) is connected to the SS-UE1 (MCVideo Client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4. - The SS-UE1 (MCVideo Client) performs the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.1.3.2 Test procedure sequence | Table 6.8.1.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the IUT (MCVideo Server) send a location reporting configuration to SS-UE1 (MCVideo Client). (Note 1) - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A, Table A.2.9.3-1 to send a location reporting configuration message containing the cell change trigger criteria and the minimum report interval to SS-UE1 (MCVideo Client)? - - 1 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A, Table A.2.8.3-1 to send a location report from SS-UE1 (MCVideo Client), containing the cell change trigger identification along with the location information report, the current location coordinates, and the current serving ECGI? (Note 2) - - 2 P NOTE 1: This is expected to be done via a suitable implementation dependent MMI. NOTE 2: This action represents the UE changing from cell. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.8.1.3.3-1: SIP MESSAGE from the IUT (MCVideo Server) (Step 2, Table 6.8.1.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCVIDEO and LOCATION- CONFIG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-info as described in Table 6.8.1.3.3-2 MIME body part Location-info ETSI TS 124 281 [8] (3GPP TS 24.281) clause F.3 MIME-part-body Location-info as described in Table 6.8.1.3.3-3 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 326 Table 6.8.1.3.3-2: MCVideo-Info in SIP MESSAGE (Table 6.8.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-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 [8] (3GPP TS 24.281) clause 18.2.2 mcvideo-calling-user-id not present NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2A. Table 6.8.1.3.3-3: Location-Info in SIP MESSAGE (Table 6.8.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.2-2 Information Element Value/remark Comment Reference Condition location-info Configuration NonEmergencyLocationInformati on ServingEcgi present Provision of information in the report is requested. NeighbouringEcgi present Provision of information in the report is requested. MbmsSaId not present Provision of information in the report is not requested. MbsfnArea not present Provision of information in the report is not requested. GeographicalCoordinate present minimumIntervalLength "25" the value in seconds EmergencyLocationInformation" ServingEcgi present Provision of information in the report is requested. NeighbouringEcgi present Provision of information in the report is requested. MbmsSaId not present Provision of information in the report is not requested. MbsfnArea not present Provision of information in the report is not requested. GeographicalCoordinate present Provision of information in the report is requested. minimumIntervalLength "30" the value in seconds TriggeringCriteria CellChange AnyCellChange TriggerID any value ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 327 Table 6.8.1.3.3-4: SIP MESSAGE (Step 3, Table 6.8.1.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 Information Element Value/remark Comment Reference Condition Message-body MIME body not including MCVideo-Info and not including MCVideo- Affiliation-Command not including any MIME body part with Content- Type being "application/vnd.3gpp.m cvideo-info+xml" or "application/vnd.3gpp.m cvideo-affiliation- command+xml" MIME body part Location info ETSI TS 124 281 [8] (3GPP TS 24.281) clause F.3 MIME-part-headers Content-Type "application/vnd.3gpp.mcvid eo-location-info+xml" MIME-part-body Location-info as described in Table 6.8.1.3.3-5 Table 6.8.1.3.3-5: Location-Info in SIP MESSAGE (Table 6.8.1.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.1-2 Information Element Value/remark Comment Reference Condition location-info Report TriggerID Same value as in the location configuration Value included in Table 6.8.1.3.3-3 CurrentLocation CurrentServingEcgi The E-UTRAN Cell Global Identification (ECGI) of Cell 2 NeighbouringEcgi The ECGI of Cell 1 CurrentCoordinate The location simulated by the GNSS simulator at the time of transmission of the message. longitude px_MCX_CoordinateLongitude _Client_A (note) latitude px_MCX_CoordinateLatitude_C lient_A (note) ReportType "NonEmergency" NOTE: Shall be encrypted as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.4.1-2A. 6.8.2 MCVideo Server - MCVideo Client / Location / On-demand Location Information Request |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.2.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to PLMN1 } ensure that { when { IUT (MCVideo Server) requests to send a location reporting configuration } then { IUT (MCVideo Server) sends a SIP MESSAGE message containing the periodic trigger criteria and the minimum report interval to the SS-UE1 (MCVideo Client) } } ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 328 (2) with { IUT (MCVideo Server) having received Location Information report } ensure that { when { IUT (MCVideo Server) requests to send an on-demand location report } then { IUT (MCVideo Server) sends a SIP MESSAGE message to the SS-UE1 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having received Location Information report } ensure that { when { SS-UE1 (MCVideo Client) requests location report containing the location information report, the current location coordinates and the current serving ECGI by sending a SIP MESSAGE message } then { IUT (MCVideo Server) responds with a SIP 200 (OK) } } |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.2.2 Conformance requirements | References: The conformance requirements covered in the present TC are specified in: ETSI TS 124 281 [8] (3GPP TS 24.281), clauses 18.2.3, 18.2.4, 18.3.3, 18.3.4.1, 18.3.4.2, 6.2.9.1. Unless otherwise stated these are Rel-16 requirements. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 18.2.3] "If the participating MCVideo function needs to request the MCVideo client to report its location, the participating MCVideo functions shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [17]. The participating MCVideo function: 1) shall include a Request-URI set to the URI corresponding to the identity of the MCVideo client; 2) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [20]; 3) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with an <mcvideo-request-uri> element containing the MCVideo ID of the MCVideo user; 4) shall include an application/vnd.3gpp.mcvideo-location-info+xml MIME body with a <Request> element contained in the <location-info> root element; 5) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; and 6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 18.2.4] "If the participating MCVideo function receives a SIP request containing: 1) a Content-Type header field set to "application/vnd.3gpp.mcvideo-location-info+xml"; and 2) an application/vnd.3gpp.mcvideo-location-info+xml MIME body with a <Report> element included in the <location-info> root element; then the participating MCVideo function shall authorise the location report based on the MCVideo ID received. If the MCVideo user is authorised to send a location report the participating MCVideo function: 1) shall use the location information as needed. NOTE: The <Report> element contains the event triggering identity in the location information report from the UE, and can contain location information." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 18.3.3] "Upon receiving a SIP MESSAGE request containing 1) an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp- service.ims.icsi.mcvideo"; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 329 2) a Content-Type header field set to "application/vnd.3gpp.mcvideo-location-info+xml"; and 3) an application/vnd.3gpp.mcvideo-location-info+xml MIME body with a <Request> element included in the <location-info> root element; then the MCVideo client: 1) shall send a location report as specified in clause 18.3.4; and 2) shall reset the minimumReportInterval timer." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 18.3.4.1] "If a location reporting trigger fires the MCVideo client checks if the minimumReportInterval timer is running. If the timer is running the MCVideo client waits until the timer expires. When the minimumReportInterval timer expires, the MCVideo client: 1) shall, if any of the reporting triggers are still true, send a location information report as specified in clause 18.3.4.2. If the MCVideo client receives a location information request as specified in clause 18.3.3, the MCVideo client shall send a location report as specified in clause 18.3.4.2. [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 18.3.4.2] If the MCVideo client needs to send a SIP request for other reasons (e.g. a SIP MESSAGE request containing an MBMS listening report as described in clause 16), the MCVideo client: 1) shall include an application/vnd.3gpp.mcvideo-location-info+xml MIME body and in the <location-info> root element the MCVideo client shall include: a) a <Report> element and if the Report was triggered by a location request include the <ReportID> attribute set to the value of the <RequestID> attribute in the received Request; b) <TriggerId> child elements, where each element is set to the value of the <Trigger-Id> attribute associated with the trigger that have fired; and c) the location reporting elements corresponding to the triggers that have fired; 2) shall set the minimumReportInterval timer to the minimumReportInterval time and start the timer; and 3) shall reset all triggers. If the MCVideo client does not need to send a SIP request for other reasons, the MCVideo client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [11] and IETF RFC 3428 [17]. The MCVideo client; 1) shall include in the Request-URI, the SIP URI received in the P-Asserted-Identity header field in the received SIP MESSAGE request for location report configuration; 2) shall include a Content-Type header field set to "application/vnd.3gpp.mcvideo-location-info+xml"; 3) shall include an application/vnd.3gpp.mcvideo-location-info+xml MIME body and in the <location-info> root element include: a) a <Report> element and if the Report was triggered by a location request include the <ReportID> attribute set to the value of the <RequestID> attribute in the received Request; b) a <TriggerId> child element set to the value of each <Trigger-Id> value of the triggers that have fired; and c) the location reporting elements corresponding to the triggers that have fired; 4) shall include an Accept-Contact header field with the media feature tag g.3gpp.mcvideo along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [20]; 5) shall set the minimumReportInterval timer to the minimumReportInterval time and start the timer; ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 330 6) shall reset all triggers; and 7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]." [ETSI TS 124 281 [8] (3GPP TS 24.281), clause 6.2.9.1] "This procedure is initiated by the MCVideo client when it is including location report information as part of a SIP request for a specified location trigger. The MCVideo client: 1) shall include an application/vnd.3gpp.location-info+xml MIME body as specified in Annex F.3 with a <Report> element included in the <location-info> root element; and 2) shall include in the <Report> element the specific location information configured for the specified location trigger." |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.2.3 Test description | |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.2.3.1 Pre-test conditions | System Simulator: - SS-UE1 (MCVideo Client) - For the underlying "transport bearer" over which the SS-UE1 (MCVideo Client) and the MCVideo 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 [5] (3GPP TS 36.508) clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document). IUT: - IUT (MCVideo Server) - The IUT (MCVideo 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 (MCVideo Server) also consists of all sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server, the HTTP Client, and the Transmission Control Server. - The IUT (MCVideo Server) is the acting Participating Server. Preamble: - The IUT (MCVideo Server) is connected to PLMN - The IUT (MCVideo Server) is connected to the SS-UE1 (MCVideo Client) as defined in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Figure 4.2.4. - The SS-UE1 (MCVideo Client) performs the Procedure for MCVideo Authorization, Configuration and Key Generation as specified in clause 5.1. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 331 |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.2.3.2 Test procedure sequence | Table 6.8.2.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Make the IUT (MCVideo Server) send a location reporting configuration to SS-UE1 (MCVideo Client)? (Note) - - - - 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A Table A.2.9.3-1 to send a location reporting configuration message containing the periodic trigger criteria and the minimum report interval to SS-UE1 (MCVideo Client)? - - 1 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Originated SIP MESSAGE' as described in Annex A Table A.2.9.3-1 to send an on-demand location report request to SS-UE1 (MCVideo Client)? - - 2 P 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCX Participating Terminated SIP MESSAGE' as described in Annex A Table A.2.8.3-1 to send a location report from SS- UE1 (MCVideo Client) containing the location information report, the current location coordinates, and the current serving ECGI? - - 3 P NOTE: This is expected to be done via a suitable implementation dependent MMI. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.8.2.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), in the subclauses referenced in each step, with the following clarifications. Table 6.8.2.3.3-1: SIP MESSAGE from the IUT (MCVideo Server) (Step 2, Table 6.8.2.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCVIDEO and LOCATION- CONFIG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-info as described in Table 6.8.2.3.3-2 MIME body part Location-info ETSI TS 124 281 [8] (3GPP TS 24.281) clause F.3 MIME-part-body Location-info as described in Table 6.8.2.3.3-3 Table 6.8.2.3.3-2: MCVideo-Info in SIP MESSAGE (Table 6.8.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-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 [8] (3GPP TS 24.281) clause 18.2.2 mcvideo-calling-user-id not present NOTE: Encrypted element as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.2.2-2A. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 332 Table 6.8.2.3.3-3: Location-Info in SIP MESSAGE (Table 6.8.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.2-2 Information Element Value/remark Comment Reference Condition location-info Configuration NonEmergencyLocationInformati on ServingEcgi present Provision of information in the report is requested. NeighbouringEcgi present Provision of information in the report is requested. MbmsSaId not present Provision of information in the report is not requested. MbsfnArea not present Provision of information in the report is not requested. GeographicalCoordinate present minimumIntervalLength "25" the value in seconds EmergencyLocationInformation" ServingEcgi present Provision of information in the report is requested. NeighbouringEcgi present Provision of information in the report is requested. MbmsSaId not present Provision of information in the report is not requested. MbsfnArea not present Provision of information in the report is not requested. GeographicalCoordinate present Provision of information in the report is requested. minimumIntervalLength "30" the value in seconds TriggeringCriteria PeriodicReport extension base "15" periodicity of the reports (in seconds) TiggerID any value Table 6.8.2.3.3-4: SIP MESSAGE from the IUT (MCVideo Server) (Step 3, Table 6.8.2.3.2-1; Step 1, Annex A, Table A.2.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.2-1, condition MCVIDEO and LOCATION- CONFIG Information Element Value/remark Comment Reference Condition Message-body MIME body part MCVideo-Info MIME-part-body MCVideo-info as described in Table 6.8.2.3.3-2 MIME body part Location-info ETSI TS 124 281 [8] (3GPP TS 24.281) clause F.3 MIME-part-body Location-info as described in Table 6.8.2.3.3-5 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 333 Table 6.8.2.3.3-5: Location-Info in SIP MESSAGE (Table 6.8.2.3.3-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.3-2 Table 6.8.2.3.3-6: SIP MESSAGE from the SS-UE1 (MCVideo Client) (Step 4, Table 6.8.2.3.2-1; Step 1, Annex A, Table A.2.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.7.1-1 Information Element Value/remark Comment Reference Condition Message-body MIME body not including MCVideo-Info and not including MCVideo- Affiliation-Command not including any MIME body part with Content-Type being "application/vnd.3gpp. mcvideo-info+xml" or "application/vnd.3gpp. mcvideo-affiliation- command+xml" MIME body part Location info ETSI TS 124 281 [8] (3GPP TS 24.281) clause F.3 MIME-part-headers Content-Type "application/vnd.3gpp.mcvid eo-location-info+xml" MIME-part-body Location-info as described in Table 6.8.2.3.3-7 Table 6.8.2.3.3-7: Location-Info in SIP MESSAGE (Table 6.8.2.3.3-6) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.4.1-2 Information Element Value/remark Comment Reference Condition location-info Report ReportID attribute "1" The same as the ID in the request message. ReportType attribute "NonEmergency" CurrentLocation CurrentServingEcgi The E-UTRAN Cell Global Identification (ECGI) of Cell 2 NeighbouringEcgi The ECGI of Cell 1 CurrentCoordinate The location simulated by the GNSS simulator at the time of transmission of the message. longitude px_MCX_CoordinateLongitud e_Client_A (note) latitude px_MCX_CoordinateLatitude_ Client_A (note) NOTE: Shall be encrypted as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) Table 5.5.3.4.1-2A. |
b66be94d4b9f9dad984e4493c1d4f66f | 104 151-1 | 6.9 Capability information sharing | This feature is not specified in the present version of the present document. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 334 Annex A (normative): Common Test Environment A.1 Introduction This annex specifies additional generic test procedures to ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), to be used by the test cases wherever applicable. A.2 Generic test procedures for Server-Client MCS operation A.2.1 General The purpose of the procedures specified in the following clauses is to facilitate test description by providing procedure sequences which can be referred from the relevant server-to-client TCs specified in the present document. The procedures specified are required to ensure that any MC service can take place between a MC client and a MC server or specific MC relevant pre-conditions are met before a test case can be executed. A.2.2 Void A.2.3 MCX Server Originated notifications regarding temporary group creation or tear down A.2.3.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.2.3.2 Definition of system information messages N/A ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 335 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 Table A.2.3.4-4: HTTP 200 (OK) (Step 4, Table A.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3.22.4-4 Table A.2.3.4-5: SIP NOTIFY (Step 5, Table A.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.3.22.4-6 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 336 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 151-1 V1.1.1 (2026-02) 337 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 151-1 V1.1.1 (2026-02) 338 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 151-1 V1.1.1 (2026-02) 339 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 [3] (3GPP TS 24.379) clauses 9.2.1.3 and 9A.2.1.3; ETSI TS 124 281 [8] (3GPP TS 24.281) clause 8.2.1.3; ETSI TS 124 282 [30] (3GPP TS 24.282) clauses 8.2.3 and 22.2.1.3 Message-body MIME body part MCPTT Info TS 124.379 [6] (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 [8] (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 [30] (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 [3] (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 [8] (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 151-1 V1.1.1 (2026-02) 340 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 [30] (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.2.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 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 151-1 V1.1.1 (2026-02) 341 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 151-1 V1.1.1 (2026-02) 342 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 151-1 V1.1.1 (2026-02) 343 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 [3] (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 151-1 V1.1.1 (2026-02) 344 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 [8] (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 [30] (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 151-1 V1.1.1 (2026-02) 345 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 151-1 V1.1.1 (2026-02) 346 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 151-1 V1.1.1 (2026-02) 347 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 151-1 V1.1.1 (2026-02) 348 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 151-1 V1.1.1 (2026-02) 349 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 151-1 V1.1.1 (2026-02) 350 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.3-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.3-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 151-1 V1.1.1 (2026-02) 351 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 (note) 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). NOTE: For chat group calls, condition CHAT-GROUP-CALL shall be used instead of GROUP-CALL. Table A.2.20.4-1: SIP 200 (OK) (Step 8, Table A.2.20.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1 with condition INVITE-RSP ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 352 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 151-1 V1.1.1 (2026-02) 353 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 MCVideo Server-Client operation A.3.0 General The purpose of the procedures specified in the following clauses is to facilitate test description by providing MCVideo procedure sequences which can be referred from the relevant TCs specified in the present document. The procedures specified are required to ensure that MCVideo service can take place between a MCVideo Client and a MCVideo server or specific MCVideo relevant pre-conditions are met before a test case can be executed. A.3.1 MCVideo 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 151-1 V1.1.1 (2026-02) 354 A.3.1.3 Procedure Table A.3.1.3-1: MCVideo E2E session establishment/modification without provisional responses other than 100 Trying St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the IUT (MCVideo 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 MCVideo as MCX? - - - P - EXCEPTION: Step 2a1-2a2 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 transmission control in the SIP INVITE request but it is not implicitly granted (note) - - - - 2a1 Check: Does the IUT (MCVideo Server) send a Transmission Granted message to SS-UE1? <-- Transmission Granted - P 2a2 IF the Transmission Granted message requires acknowledgement, the SS-UE1 sends a Transmission Control ACK message. --> Transmission Control Ack - - - EXCEPTION: Step 3a1-3a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place when the transmission is granted to SS- UE1, either implicit or explicitly. (note) - - - - 3a1 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to SS- UE2? <-- Media Transmission Notification - P 3a2 IF the Media Transmission Notification message requires acknowledgement, the SS-UE2 sends a Transmission Control ACK message. --> Transmission Control Ack - - - 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 transmission is not granted to SS-UE1. (note) - - - - 4a1 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to SS-UE1? <-- Transmission Idle - P 4a2 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to SS-UE2? <-- Transmission Idle - P NOTE: Possibilities in SDP-offer/answer depend on the test case requirements: a) SS-UE1 sends SDP offer with media description for transmission control but without implicit transmission request. b. SS-UE1 sends SDP offer with media description for transmission control and with implicit transmission request: i. SDP answer from MCVideo Server contains "mc_implicit_request" and "mc_granted" (Transmission is implicitly granted). ii. SDP answer from MCVideo Server contains "mc_implicit request" and but no "mc_granted" (Transmission needs to be explicitly granted at step 2a1). iii. SDP answer from MCVideo Server contains no "mc_implicit_request"and no "mc_granted" (the UE needs to explicitly request the transmission). c. SS-UE1 sends SDP offer without media description for transmission 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 MCVIDEO 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 151-1 V1.1.1 (2026-02) 355 Table A.3.1.4-1: SIP INVITE from SS-UE1 (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 MCVIDEO Information Element Value/remark Comment Reference Condition Session-Expires IETF RFC 4028 [11] generic-param "1800" The recommended initial value is 1 800 in IETF RFC 4028 [11]. Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.1.4-2 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table A.3.1.4-3 NOTE: With condition re_INVITE for session modifications. Table A.3.1.4-2: SDP in SIP INVITE (Table A.3.1.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-2 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" 352 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [16] port port number assigned by the SS-UE1 (even integer) The transport port to which the media stream is sent IETF RFC 6335 [17] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS-UE1 Bandwidth b= line "AS" 37 ETSI TS 126 114 [15] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [18] "RR" 2000 IETF RFC 3556 [18] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 356 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-2 Information Element Value/remark Comment Reference Condition 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 video media description m= line media = video SDP media-level section for a media-transmission control entity port port number of the audio stream incremented by 2 (resulting in even integer) The transport port from which the media stream is sent fmt "100" Connection Data c= line connection-address IP address of the SS-UE1 Bandwidth b= line "AS" 315 "RS" 0 IETF RFC 3556 [18] "RR" 2500 IETF RFC 3556 [18] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "100" media attribute a= line attribute = fmtp fmtp "fmtp" format "100" format specific parameters Parameters the H264 codec IETF RFC 6184 [24] packetization-mode "0" profile-level-id "42e00c" Media description[3] Media description for media control NOT WITHOUT_ TRANSMIS SIONCONT ROL media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS-UE1 being different than the port number of the audio and video channels (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 "MCVideo" format specific parameters mc_queueing not present ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 357 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-2 Information Element Value/remark Comment Reference Condition present Parameter has no value ETSI TS 124 581 [9] (3GPP TS 24.581) clause 14.2.2 pc_MCVide o_Transmis sionReques tQueueing mc_priority The priority value specified in the MCVideo Group configuration The value of the <user- priority> element for the user in the MCVideo Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.2-1) See note 4 ETSI TS 124 581 [9] (3GPP TS 24.581) clause 14.2.3 GROUP- CALL OR CHAT- GROUP- CALL mc_priority The max priority value specified in the MCVideo Service configuration The value of the <num- levels-priority-hierarchy> element for on-network in the MCVideo Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1) ETSI TS 124 581 [9] (3GPP TS 24.581) clause 14.2.3 PRIVATE- CALL mc_reception_priority The priority value specified in the MCVideo Group configuration The value of the <user- reception-priority> element for the user in the MCVideo Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.2-1) See note 5. ETSI TS 124 581 [9] (3GPP TS 24.581) clause 14.2.6 GROUP- CALL OR CHAT- GROUP- CALL mc_reception_priority The max priority value specified in the MCVideo Service configuration The value of the <num- levels-priority-hierarchy> element for on-network in the MCVideo Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1) ETSI TS 124 581 [9] (3GPP TS 24.581) clause 14.2.6 PRIVATE- CALL NOTE 1: If the SS-UE requests a call with media transmission control and implicit transmission (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 transmission (Option c of NOTE1 on Table A.3.1.3-1), apply condition WITHOUT_TRANSMISSIONCONTROL. NOTE 3: With condition INITIAL_SDP_OFFER if condition re_INVITE is not in use for Table A.3.1.4-1. Otherwise, apply condition SDP_OFFER. NOTE 4: the <num-levels-priority-hierarchy> element for on-network in the MCVideo 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.8-1) NOTE 5: The <num-levels-priority-hierarchy> element for on-network in the MCVideo Service Configuration has higher value than any <user-reception-priority> element. (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1). Table A.3.1.4-3: MCVideo-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-2, condition INVITE_REFER ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 358 Table A.3.1.4-4: SIP INVITE from the IUT (MCVideo-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 MCVIDEO Information Element Value/remark Comment Reference Condition Resource-Priority IETF RFC 4412 [19] IETF RFC 7134 [21] IETF RFC 8101 [20] 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.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.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.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.8-1 for MCVIdeo Session-Expires IETF RFC 4028 [11] delta-seconds any allowed value Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.1.4-5 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table A.3.1.4-6 NOTE: With condition re_INVITE for session modifications. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 359 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-2 Information Element Value/remark Comment Reference Condition Media description[3] NOT WITHOUT_ TRANSMIS SIONCONT ROL media attribute a= line attribute = fmtp fmtp format "MCVideo" format specific parameters mc_priority Any value lower or equal to the priority specified in the MCVideo Group configuration The value of the <user- priority> element for the user in the MCVideo Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.2-1) See note 3. ETSI TS 124 581 [9] (3GPP TS 24.581) clause 14.2.3 GROUP- CALL OR CHAT- GROUP- CALL mc_priority Any value lower or equal to the priority specified in the MCVideo Service configuration The value of the <num- levels-priority-hierarchy> element for on-network in the MCVideo Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1) ETSI TS 124 581 [9] (3GPP TS 24.581) clause 14.2.3 PRIVATE- CALL NOTE 1: If the SS-UE1 requests a call without media transmission control (Option c of note on Table A.3.1.3-1), apply condition WITHOUT_TRANSMISSIONCONTROL. NOTE 2: With condition INITIAL_SDP_OFFER if condition re_INVITE is not in use for Table A.3.1.4-3. Otherwise, apply condition SDP_OFFER. NOTE 3: The <num-levels-priority-hierarchy> element for on-network in the MCVideo 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.8-1). Table A.3.1.4-6: MCVideo-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-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_B The URI of the called user mcvideo-calling-user-id Encrypted (note) <mcvideo- calling-user-id> with mcvideoURI set to px_MCVideo_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-2A. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 360 Table A.3.1.4-7: SIP 200 (OK) from SS-UE2 (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 MCVIDEO and INVITE-RSP Information Element Value/remark Comment Reference Condition Content-Type IETF RFC 5621 [22] value "application/sdp" Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.1.4-8 Table A.3.1.4-8: SDP in SIP 200 (OK) (Table A.3.1.4-7) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-2, condition SDP_ANSWER. NOTE: If the SS-UE1 requests a call without media transmission control (Option c of note on Table A.3.1.3-1), apply condition WITHOUT_TRANSMISSIONCONTROL. 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" 352 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [16] port port number assigned by the SS-UE2 (even integer) The transport port to which the media stream is sent IETF RFC 6335 [17] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS- UE2 Bandwidth b= line "AS" 37 ETSI TS 126 114 [15] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [18] "RR" 2000 IETF RFC 3556 [18] 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 151-1 V1.1.1 (2026-02) 361 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-2, condition SDP_ANSWER. NOTE: If the SS-UE1 requests a call without media transmission control (Option c of note on Table A.3.1.3-1), apply condition WITHOUT_TRANSMISSIONCONTROL. 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 video media description m= line media = video SDP media-level section for a media-transmission control entity port port number of the audio stream incremented by 2 (resulting in even integer) The transport port from which the media stream is sent fmt "100" Connection Data c= line connection-address IP address of the SS- UE2 Bandwidth b= line "AS" 315 "RS" 0 IETF RFC 3556 [18] "RR" 2500 IETF RFC 3556 [18] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "100" media attribute a= line attribute = fmtp fmtp "fmtp" format "100" format specific parameters same parameters and values as sent in the corresponding SDP offer Parameters the H264 codec Media description[3] Media description for media control NOT WITHOUT_ TRANSMIS SIONCONT ROL media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS-UE2 being different than the port number of the audio and video channels (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- UE2 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 362 Table A.3.1.4-9: SIP 200 (OK) from IUT (MCVideo Server) (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 MCVIDEO 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-2, condition SDP_ANSWER. NOTE 1: If the SS-UE requests an implicit transmission (Option b of NOTE 1 on Table A.3.1.3-1), more conditions may apply: i. If the server implicitly grants the transmission, conditions IMPLICIT_GRANT_REQUESTED and IMPLICIT_FLOOR_GRANTED are also applied. ii. If the transmission needs to be explicitly granted, condition IMPLICIT_GRANT_REQUESTED applies. NOTE 2: If the SS-UE requests a call without media transmission (Option c of NOTE 1 on Table A.3.1.3-1) apply condition WITHOUT_TRANSMISSIONCONTROL. NOTE 3: Elements whose values mention the SS shall be understood as if they were referring to the MCVideo Server. Information Element Value/remark Comment Reference Condition Media description[3] NOT WITHOUT_ TRANSMIS SIONCONT ROL media attribute a= line attribute = fmtp fmtp format "MCVideo" format specific parameters mc_priority if a value is provided in the offer: the value defined in the MCVideo 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 MCVideo Group Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.7.2-1) ETSI TS 124 581 [9] (3GPP TS 24.581) clause 14.2.3 GROUP- CALL OR CHAT- GROUP- CALL mc_priority if a value is provided in the offer: the value defined in the MCVideo 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 MCVideo Service Configuration (ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.8.8-1) ETSI TS 124 581 [9] (3GPP TS 24.581) clause 14.2.3 PRIVATE- CALL Table A.3.1.4-11: Transmission Granted (Step 2a1, Table A.3.1.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.1-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 363 Table A.3.1.4-12: Media Transmission Notification (Step 3a1, Table A.3.1.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.7-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition User Id of the Transmitting User User ID of the user transmitting the media ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.6 User Id of the Transmitting User px_MCVideo_ID_User_A Audio SSRC of the Transmitting User Media/Audio SSRC of remote client (Client A) SSRC of the user transmitting the media ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.16 Functional Alias Not present px_MCVideo_ID_FA_A functional alias URI of the transmitting user ETSI TS 124 581 [9] (3GPP TS 24.581)clause 9.2.3.21 FA Table A.3.1.4-13: Transmission Idle (Steps 4a1 and 4a2, Table A.3.1.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.16-1. Table A.3.1.4-14: Transmission Control Ack (Steps 2a2 and 3a2, Table A.3.1.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK A.3.2 MCVideo 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 151-1 V1.1.1 (2026-02) 364 A.3.2.3 Procedure Table A.3.2.3-1: MCVideo E2E group call establishment, manual commencement St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the IUT (MCVideo Server) correctly perform test procedure MCX E2E group call establishment, manual commencement' as described in Table A.2.20.3-1 with MCVideo as MCX? - - - P - EXCEPTION: Step 2a1-2a2 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 transmission control in the SIP INVITE request but it is not implicitly granted (note) - - - - 2a1 Check: Does the IUT (MCVideo Server) send a Transmission Granted message to SS-UE1? <-- Transmission Granted - P 2a2 IF the Transmission Granted message requires acknowledgement, the SS-UE1 sends a Transmission Control ACK message. --> Transmission Control Ack - - - EXCEPTION: Step 3a1-3a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place when the transmission is granted to SS-UE1, either implicit or explicitly. (note) - - - - 3a1 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to SS-UE2? <-- Media Transmission Notification - P 3a2 IF the Media Transmission Notification message requires acknowledgement, the SS-UE2 sends a Transmission Control ACK message. --> Transmission Control Ack - - - 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 transmission is not granted to SS-UE1. (note) - - - - 4a1 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to SS-UE1? <-- Transmission Idle - P 4a2 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to SS-UE2? <-- Transmission Idle - P NOTE: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS-UE1 sends SDP offer with media description for transmission control but without implicit transmission request. b. SS-UE1 sends SDP offer with media description for transmission control and with implicit transmission request: i. SDP answer from MCVideo Server contains "mc_implicit_request" and "mc_granted" (Transmission media request is implicitly granted). ii. SDP answer from MCVideo Server contains "mc_implicit request" and but no "mc_granted" (Transmission media request needs to be explicitly granted at step 2a1). iii. SDP answer from MCVideo Server contains no "mc_implicit_request"and no "mc_granted" (the UE needs to explicitly send the Transmission media request). 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 MCVIDEO 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 151-1 V1.1.1 (2026-02) 365 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: Table A.3.1.4-1, with condition MANUAL Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.1.4-2 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table A.3.2.4-2 Table A.3.2.4-2: MCVideo-Info in SIP INVITE (Table A.3.2.4-1) Derivation Path: Table A.3.1.4-5, with condition GROUP-CALL (note). NOTE: For chat group calls CHAT-GROUP-CALL condition shall be used instead of GROUP-CALL. Table A.3.2.4-3: SIP INVITE from the MCVideo-Server (Step 1, Table A.3.2.3-1; Step 2, Table A.2.20.3-1) Derivation Path: Table Á.3.1.4-4, with condition MANUAL Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.1.4-5 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table A.3.2.4-4 Table A.3.2.4-4: MCVideo-Info in SIP INVITE (Table A.3.2.4-3) Derivation Path: Table A.3.1.4-6, with condition GROUP-CALL (note). NOTE: For chat group calls CHAT-GROUP-CALL condition shall be used instead of GROUP-CALL. Table A.3.2.4-5: 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: Table A.3.1.4-7, with condition GROUP-CALL (note). NOTE: For chat group calls CHAT-GROUP-CALL condition shall be used instead of GROUP-CALL. Table A.3.2.4-6: SIP 200 (OK) from the MCVideo Server (Step 1, Table A.3.2.3-1; Step 9, Table A.2.20.3-1) Derivation Path: Table A.3.1.4-9 Table A.3.2.4-7: 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.1-1, with condition MCVIDEO and 100rel Table A.3.2.4-8: Transmission Granted (Step 2a1, Table A.3.2.3-1) Derivation Path: Table A.3.1.4-11 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 366 Table A.3.2.4-9: Media Transmission Notification (Step 3a1, Table A.3.2.3-1) Derivation Path: Table A.3.1.4-12 Table A.3.2.4-10: Transmission Idle (Steps 4a1 and 4a2, Table A.3.2.3-1) Derivation Path: Table A.3.1.4-13 Table A.3.2.4-11: Transmission Control Ack (Steps 2a2 and 3a2, Table A.3.2.3-1) Derivation Path: Table A.3.1.4-14 A.3.3 MCVideo 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 151-1 V1.1.1 (2026-02) 367 A.3.3.3 Procedure Table A.3.3.3-1: MCVideo E2E private call establishment, manual commencement St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the IUT (MCVideo Server) correctly perform test procedure MCX E2E private call establishment, manual commencement' as described in Table A.2.21.3-1 with MCVideo as MCX? - - - P - EXCEPTION: Step 2a1-2a2 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 transmission control in the SIP INVITE request but it is not implicitly granted (NOTE1) - - - - 2a1 Check: Does the IUT (MCVideo Server) send a Transmission Granted message to SS-UE1? <-- Transmission Granted - P 2a2 IF the Transmission Granted message requires acknowledgement, the SS-UE1 sends a Transmission Control ACK message. --> Transmission Control Ack - - - EXCEPTION: Step 3a1-3a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place when the transmission is granted to SS- UE1, either implicit or explicitly. (NOTE1) - - - - 3a1 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to SS- UE2? <-- Media Transmission Notification - P 3a2 IF the Media Transmission Notification message requires acknowledgement, the SS-UE2 sends a Transmission Control ACK message. --> Transmission Control Ack - - - 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 transmission is not granted to SS-UE1. (NOTE1) - - - - 4a1 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to SS-UE1? <-- Transmission Idle - P 4a2 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to SS-UE2? <-- Transmission Idle - P NOTE: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS-UE1 sends SDP offer with media description for transmission control but without implicit transmission request. b. SS-UE1 sends SDP offer with media description for transmission control and with implicit transmission request: i. SDP answer from MCVideo Server contains "mc_implicit_request" and "mc_granted" (Transmission is implicitly granted). ii. SDP answer from MCVideo Server contains "mc_implicit request" and but no "mc_granted" (Transmission needs to be explicitly granted at step 2a1). iii. SDP answer from MCVideo Server contains no "mc_implicit_request"and no "mc_granted" (the UE needs to explicitly request the transmission). c. SS-UE1 sends SDP offer without media description for transmission 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 MCVIDEO 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 151-1 V1.1.1 (2026-02) 368 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: Table A.3.1.4-1, with condition PRIVATE-CALL and MANUAL Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.3.4-2 MIME body part MCVideo-Info MIME-part-body MCVideo-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: Table A.3.1.4.2-2, with condition PRIVATE-CALL Table A.3.3.4-3: MCVideo-Info in SIP INVITE (Table A.3.3.4-1) Derivation Path: Table A.3.1.4-3, with condition PRIVATE-CALL Table A.3.3.4-4: SIP INVITE from the MCVideo-Server to SS-UE2 (Step 1, Table A.3.3.3-1; Step 2, Table A.2.21.3-1) Derivation Path: Table A.3.1.4-4, with condition MANUAL Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.3.1.4-5 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table A.3.3.4-5 Table A.3.3.4-5: MCVideo-Info in SIP INVITE (Table A.3.3.4-4) Derivation Path: Table A.3.1.4-6, with condition PRIVATE-CALL Table A.3.3.4-6: SIP 200 (OK) from the SS-UE2 to MCVideo Server (Step 1, Table A.3.3.3-1; Step 7, Table A.2.21.3-1) Derivation Path: Table A.3.1.4-7 Table A.3.3.4-7: SIP 200 (OK) from the MCVideo Server to SS-UE1 (Step 1, Table A.3.3.3-1; Step 8, Table A.2.21.3-1) Derivation Path: Table A.3.1.4-9 Table A.3.3.4-8: 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 MCVIDEO ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 369 Table A.3.3.4-9: 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 MCVIDEO Table A.3.3.4-10: Transmission Granted (Step 2a1, Table A.3.3.3-1) Derivation Path: Table A.3.1.4-11 Table A.3.3.4-11: Media Transmission Notification (Step 3a1, Table A.3.3.3-1) Derivation Path: Table A.3.1.4-12 Table A.3.3.4-12: Transmission Idle (Steps 4a1 and 4a2, Table A.3.3.3-1) Derivation Path: Table A.3.1.4-13 Table A.3.3.4-13: Transmission Control Ack (Steps 2a2 and 3a2, Table A.3.3.3-1) Derivation Path: Table A.3.1.4-14 A.3.4 MCVideo Participating Terminated session establishment/modification without provisional responses other than 100 Trying A.3.4.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.4.2 Definition of system information messages N/A ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 370 A.3.4.3 Procedure Table A.3.4.3-1: MCVideo Participating Terminated session establishment/modification without provisional responses other than 100 Trying St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the MCVideo server correctly perform test procedure 'MCX Participating Terminated session establishment/modification without provisional responses other than 100 Trying' for as described in Table A.2.14.3-1 with MCVideo as MCX? (Note 2) - - - P - EXCEPTION: Step 2a1-2a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the SS-UE requests implicit transmission control in the SIP INVITE request but it is not implicitly granted (Note 1) - - - - 2a1 Check: Does the MCVideo server send a Transmission Granted message to SS-UE? <-- Transmission Granted - P 2a2 IF the Transmission Granted message requires acknowledgement, the SS-UE sends a Transmission Control ACK message. --> Transmission Control Ack - - - 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 transmission is not granted to SS- UE. (Note 1) - - - - 3a1 Check: Does the MCVideo server send a Transmission Idle message to SS-UE? <-- Transmission Idle - P NOTE 1: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS-UE sends SDP offer with media description for transmission control but without implicit transmission request. b. SS-UE sends SDP offer with media description for transmission control and with implicit transmission request: i. SDP answer from MCVideo Server contains "mc_implicit_request" and "mc_granted" (Transmission is implicitly granted). ii. SDP answer from MCVideo Server contains "mc_implicit request" and but no "mc_granted" (Transmission needs to be explicitly granted at step 2a1). iii. SDP answer from MCVideo Server contains no "mc_implicit_request"and no "mc_granted" (the UE needs to explicitly request the transmission). c. SS-UE sends SDP offer without media description for transmission control. NOTE 2: The SS-UE being used is specified in the test case calling the procedure. 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 with condition MCVIDEO 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 INVITE from SS-UE (Step 1, Table A.3.4.3-1; Step 1, Table A.2.14.3-1) Derivation Path: Table A.3.1.4-1 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 371 Table A.3.4.4-2: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table A.3.4.3-1; Step 3, Table A.2.14.3-1) Derivation Path: Table A.3.1.4-9 Table A.3.4.4-3: Transmission Granted (Step 2a1, Table A.3.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.1-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Table A.3.4.4-4: Transmission Idle (Step 3a1, Table A.3.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.16-1. Table A.3.4.4-5: Transmission Control Ack (Step 2a2, Table A.3.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK A.3.5 MCVideo Group Affiliation Status Determination and Subscription A.3.5.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.5.2 Definition of system information messages N/A A.3.5.3 Procedure Table A.3.5.3-1: MCVideo Group affiliation status determination and subscription Same procedure as defined in: Table A.2.7.3-1 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 (MCVideo Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCVideo Client) or SS-UE2 (MCVideo Client). Table A.3.5.4-1: SIP SUBSCRIBE (Step 1, Table A.3.5.3-1) Derivation Path: Table A.2.7.4-1, conditions MCVIDEO and PRESENCE-EVENT ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 372 Table A.3.5.4-2: SIP NOTIFY (Step 3, Table A.3.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.8-1, conditions MCVIDEO and PRESENCE- EVENT Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 281 [8] (3GPP TS 24.281) clause 8.2.2.2.5 MIME-part-body PIDF as described in Table A.3.5.4-3 Table A.3.5.4-3: PIDF in SIP NOTIFY (Table A.3.5.4-2) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2 (note) NOTE: PIDF document contains tuple with empty <status> element A.3.6 MCVideo Group Affiliation Status Change A.3.6.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.3.6.2 Definition of system information messages N/A A.3.6.3 Procedure Table A.3.6.3-1: MCVideo Group Affiliation Status Change Same procedure as defined in Table A.2.12.3-1 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 (MCVideo Server). • Subclauses referring to messages from UE relate to either SS-UE1 (MCVideo Client) or SS-UE2 (MCVideo Client). Table A.3.6.4-1: SIP PUBLISH (Step 1, Table A.3.6.3-1) Derivation Path: Table A.2.12.4-1, condition MCVIDEO Table A.3.6.4-2: PIDF in SIP PUBLISH (Table A.3.6.4-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.1-2, condition AFFILIATION ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 373 Table A.3.6.4-3: SIP 200 (OK) (Step 2, Table A.3.6.3-1) Derivation Path: Table A.2.12.4-5 Information Element Value/remark Comment Reference Condition Expires IETF RFC 3261 [10] IETF RFC 3903 [23] value same value as in the request or lower Table A.3.6.4-4: SIP NOTIFY (Step 3, Table A.3.6.3-1) Derivation Path: Table A.2.12.4-6, condition MCVIDEO Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 281 [8] (3GPP TS 24.281) clause 8.2.2.2.5 MIME-part-body PIDF as described in Table A.3.6.4-5 Table A.3.6.4-5: PIDF in SIP NOTIFY (Table A.3.6.4-4) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, 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 281 [8] (3GPP TS 24.281) clause 8.2.2.3.5 ..p-id same value as received in the SIP PUBLISH message. Table A.3.6.4-6: SIP NOTIFY (Step 5, Table A.3.6.3-1) Derivation Path: Table A.2.12.4-6, condition MCVIDEO Information Element Value/remark Comment Reference Condition Message-body MIME body part PIDF ETSI TS 124 281 [8] (3GPP TS 24.281) clause 8.2.2.2.5 MIME-part-body PIDF as described in Table A.3.6.4-7 Table A.3.6.4-7: PIDF in SIP NOTIFY (Table A.3.6.4-5) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.5.2-2, 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 281 [8] (3GPP TS 24.281) clause 8.2.2.3.5 ..p-id same value as received in the SIP PUBLISH message. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 374 A.3.7 MCVideo Transmission Request - Granted and Media Transmission Notification 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: MCVideo Transmission Request - Granted and Media Transmission Notification St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCVideo Client) sends a Transmission Request message, with acknowledgement. (note) --> Transmission Request - - 2 Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P - EXCEPTION: Steps 3a1-3b2 describe behaviour that depends on the MCVideo Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCVideo Server requests or not acknowledgement of sent transmission control messages. - - - - 3a1 Check: Does the IUT (MCVideo Server) send a Transmission Granted message to SS-UE1 with acknowledgement? (note) <-- Transmission Granted - P 3a2 The SS-UE1 (MCVideo Client) sends a Transmission Control Ack message in response to the Transmission Granted message. (note) --> Transmission Control Ack - - 3a3 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to SS-UE2 with acknowledgement? (note) <-- Media Transmission Notification - P 3a4 The SS-UE2 (MCVideo Client) sends a Transmission Control Ack message in response to the Media Transmission Notification message. (note) --> Transmission Control Ack - - 3b1 Check: Does the IUT (MCVideo Server) send a Transmission Granted message to SS-UE1 with no acknowledgement? <-- Transmission Granted - P 3b2 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to SS-UE2 with no acknowledgement? (note) <-- Media Transmission Notification - P NOTE: SS-UEs may switch, depending on the test case calling this procedure. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 375 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: Transmission Request (Step 1, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.1.1-1, with condition ACK Table A.3.7.4-2: Transmission Granted (Step 3b1, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.1-1 Table A.3.7.4-3: Transmission Granted (Step 3a1, Table A.3.7.3-1) Derivation Path: Table A.3.7.4-2, with condition ACK Table A.3.7.4-4: Media Transmission Notification (Step 3b2, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.7-1 Information Element Value/remark Comment Reference Condition User Id of the Transmitting User User ID of the user transmitting the media ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.6 User Id of the Transmitting User px_MCVideo_ID_User_A Audio SSRC of the Transmitting User Media/Audio SSRC of remote client (Client A) SSRC of the user transmitting the media ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.16 Functional Alias Not present px_MCVideo_ID_FA_A functional alias URI of the transmitting user ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.21 FA Table A.3.7.4-5: Media Transmission Notification (Step 3a3, Table A.3.7.3-1) Derivation Path: Table A.3.7.4-4, with condition ACK Table A.3.7.4-6: Transmission Control Ack (Steps 3a2 and 3a4, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK Table A.3.7.4-7: Transmission Control Ack (Steps 2, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition DOWNLINK ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 376 A.3.8 MCVideo Transmission End Request - Idle and Transmission End Notify 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: MCVideo Transmission End Request - Idle and Transmission End Notify St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCVideo Client) sends a Transmission End Request message, with acknowledgement. (Note 1) --> Transmission End Request - - 2 Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P - EXCEPTION: Steps 3a1-3b2 describe behaviour that depends on the MCVideo Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCVideo Server requests or not acknowledgement of sent transmission control messages. - - - - 3a1 Check: Does the IUT (MCVideo Server) send a Transmission End Response message to SS- UE1 (MCVideo Client) with acknowledgement? (Note 1) <-- Transmission End Response - P 3a2 The SS-UE1 (MCVideo Client) sends a Transmission Control Ack message in response to the Transmission End Response message. (Note 1) --> Transmission Control Ack - - 3a3 Check: Does the IUT (MCVideo Server) send a Transmission End Notify message to SS-UE2 (MCVideo Client) with acknowledgement? (Notes 1 and 2) <-- Transmission End Notify - P 3a4 The SS-UE2 (MCVideo Client) sends a Transmission Control Ack message in response to the Transmission End Notify message. (Note 1) --> Transmission Control Ack - - - EXCEPTION: Steps 3aA1-3aA4 describe behaviour that depends on the test case calling this procedure; the "upper case letter" identifies a step sequence that takes place if SS-UE2 has previously requested media reception by performing procedure 'MCVideo Media Reception Request and Response', as described in Table A.3.9.3-1. - - - - 3aA1 Check: Does the IUT (MCVideo Server) send a Media Reception End Request message to SS- UE2 (MCVideo Client) with acknowledgement? (Note 1) <-- Media Reception End Request - P 3aA2 The SS-UE2 (MCVideo Client) sends a Transmission Control Ack message in response to the Media Reception End Request message. (Note 1) --> Transmission Control Ack - - ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 377 St Procedure Message Sequence TP Verdict U - S Message 3aA3 The SS-UE2 (MCVideo Client) sends a Media Reception End Response message, with acknowledgement. (Note 1) --> Media Reception End Response - - 3aA4 Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P 3b1 Check: Does the IUT (MCVideo Server) send a Transmission End Response message to SS- UE1 (MCVideo Client) with no acknowledgement? (Note 1) <-- Transmission End Response - P 3b2 Check: Does the IUT (MCVideo Server) send a Transmission End Notify message to SS-UE2 (MCVideo Client) with no acknowledgement? (Notes 1 and 2) <-- Transmission End Notify - P - EXCEPTION: Steps 3bA1-3bA3 describe behaviour that depends on the test case calling this procedure; the "upper case letter" identifies a step sequence that takes place if SS-UE2 (MCVideo Client) has previously requested media reception by performing procedure 'MCVideo Media Reception Request and Response', as described in Table A.3.9.3-1. - - - - 3bA1 Check: Does the IUT (MCVideo Server) send a Media Reception End Request message to SS- UE2 (MCVideo Client) with no acknowledgement? (Note 1) <-- Media Reception End Request - P 3bA2 The SS-UE2 (MCVideo Client) sends a Media Reception End Response message, with acknowledgement. (Note 1) --> Media Reception End Response - - 3bA3 Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P 4 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to SS-UE1 (MCVideo Client)? <-- Transmission Idle - P 5 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to SS-UE2 (MCVideo Client)? <-- Transmission Idle - P NOTE 1: SS-UEs may switch, depending on the test case calling this procedure. NOTE 2: According to ETSI TS 124 581 [9] (3GPP TS 24.581), sections 6.3.7.3.7 and 6.3.7.4.7, the MCVideo Server sends a Transmission End Notify message when it has stopped receiving RTP media packets from the transmitter participant. 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: Transmission End Request (Step 1, Table A.3.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.1-1, with conditions ACK and UPLINK Table A.3.8.4-2: Transmission End Response (Step 3b1, Table A.3.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.2-1, with condition DOWNLINK ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 378 Table A.3.8.4-3: Transmission End Response (Step 3a1, Table A.3.8.3-1) Derivation Path: Table A.3.8.4-2, with condition ACK Table A.3.8.4-4: Transmission End Notify (Step 3b2, Table A.3.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.15-1 Information Element Value/remark Comment Reference Condition User Id of the Transmitting User Carries the identity of the user whose media transmission has been released ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.6 User Id of the Transmitting User px_MCVideo_ID_User_A Audio SSRC of the Transmitting User Media/Audio SSRC of remote client (Client A) SSRC of the user transmitting the media ETSI TS 124 581 [9] (3GPP TS 24.581) clause 9.2.3.16 Table A.3.8.4-5: Transmission End Notify (Step 3a3, Table A.3.8.3-1) Derivation Path: Table A.3.8.4-4, with condition ACK Table A.3.8.4-6: Transmission Idle (Steps 4 and 5, Table A.3.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.16-1 Table A.3.8.4-7: Transmission Control Ack (Steps 3a2, 3a4 and 3aA2, Table A.3.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK Table A.3.8.4-8: Transmission Control Ack (Steps 2, 3aA4 and 3bA3, Table A.3.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition DOWNLINK Table A.3.8.4-9: Media Reception End Response (Steps 3aA3 and 3bA2, Table A.3.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.4-1, with conditions ACK and UPLINK Table A.3.8.4-10: Media Reception End Request (Step 3bA1, Table A.3.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.3-1, with condition DOWNLINK Table A.3.8.4-11: Media Reception End Request (Step 3aA1, Table A.3.8.3-1) Derivation Path: Table A.3.8.4-10, with condition ACK A.3.9 MCVideo Media Reception Request and Response 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. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 379 A.3.9.2 Definition of system information messages N/A A.3.9.3 Procedure Table A.3.9.3-1: MCVideo Media Reception Request and Response St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCVideo Client) sends a Receive Media Request, with acknowledgement --> Receive Media Request - - 2 Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P - EXCEPTION: Steps 3a1-3b1 describe behaviour that depends on the MCVideo Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCVideo Server requests or not acknowledgement of sent transmission control messages. - - - - 3a1 Check: Does the IUT (MCVideo Server) send a Receive Media Response message to the SS-UE, with acknowledgement? <-- Receive Media Response - P 3a2 The SS-UE (MCVideo Client) sends a Transmission Control Ack message in response to the Receive Media Response message. --> Transmission Control Ack - - 3b1 Check: Does the IUT (MCVideo Server) send a Receive Media Response message to the SS-UE, with no acknowledgement? <-- Receive Media Response - P NOTE: The SS-UE being used is specified in the test case calling the procedure. 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: Receive Media Request (Step 1, Table A.3.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.1.4-1, with condition ACK Table A.3.9.4-2: Receive Media Response (Step 3b1, Table A.3.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.8-1 Table A.3.9.4-3: Receive Media Response (Step 3a1, Table A.3.9.3-1) Derivation Path: Table A.3.9.4-2, with condition ACK Table A.3.9.4-4: Transmission Control Ack (Step 3a2, Table A.3.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 380 Table A.3.9.4-5: Transmission Control Ack (Steps 2, Table A.3.9.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition DOWNLINK A.3.10 MCVideo Media Reception End Request and Response 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: MCVideo Media Reception Request and Response St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCVideo Client) sends a Media Reception End Request, with acknowledgement --> Media Reception End Request - - 2 Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P - EXCEPTION: Steps 3a1-3b1 describe behaviour that depends on the MCVideo Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCVideo Server requests or not acknowledgement of sent transmission control messages. - - - - 3a1 Check: Does the IUT (MCVideo Server) send a Media Reception End Response message to the SS-UE, with acknowledgement? <-- Media Reception End Response - P 3a2 The SS-UE (MCVideo Client) sends a Transmission Control Ack message in response to the Media Reception End Response message. --> Transmission Control Ack - - 3b1 Check: Does the IUT (MCVideo Server) send a Media Reception End Response message to the SS-UE, with no acknowledgement? <-- Media Reception End Response - P NOTE: The SS-UE being used is specified in the test case calling the procedure. 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: Media Reception End Request (Step 1, Table A.3.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.3-1, with conditions ACK and UPLINK Table A.3.10.4-2: Media Reception End Response (Step 3b1, Table A.3.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.4-1, with condition DOWNLINK ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 381 Table A.3.10.4-3: Media Reception End Response (Step 3a1, Table A.3.10.3-1) Derivation Path: Table A.3.10.4-2, with condition ACK Table A.3.10.4-4: Transmission Control Ack (Step 3a2, Table A.3.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK Table A.3.10.4-5: Transmission Control Ack (Steps 2, Table A.3.10.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition DOWNLINK A.3.11 MCVideo Transmission Request - Transmission Rejected 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: MCVideo Transmission Request - Transmission Rejected St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCVideo Client) sends a Transmission Request message, with acknowledgement. (Note) --> Transmission Request - - 2 Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P - EXCEPTION: Steps 3a1-3b1 describe behaviour that depends on the MCVideo Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCVideo Server requests or not acknowledgement of sent transmission control messages. - - - - 3a1 Check: Does the IUT (MCVideo Server) send a Transmission Rejected message to the SS-UE, with acknowledgement? <-- Transmission Rejected - P 3a2 The SS-UE (MCVideo Client) sends a Transmission Control Ack message in response to the Transmission Rejected message. --> Transmission Control Ack - - 3b1 Check: Does the IUT (MCVideo Server) send a Transmission Rejected message to the SS-UE, with no acknowledgement? <-- Transmission Rejected - P NOTE: The SS-UE being used is specified in the test case calling the procedure. If not stated, SS-UE1 (MCVideo Client) will be assumed. ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 382 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: Transmission Request (Step 1, Table A.3.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.1.1-1, with condition ACK Table A.3.11.4-2: Transmission Rejected (Step 3b1, Table A.3.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.2-1 Table A.3.11.4-3: Transmission Rejected (Step 3a1, Table A.3.11.3-1) Derivation Path: Table A.3.7.4-2, with condition ACK Table A.3.11.4-4: Transmission Control Ack (Step 3a2, Table A.3.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK Table A.3.11.4-5: Transmission Control Ack (Steps 2, Table A.3.11.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition DOWNLINK A.3.12 MCVideo Transmission Request - 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 151-1 V1.1.1 (2026-02) 383 A.3.12.3 Procedure Table A.3.12.3-1: MCVideo Transmission Request - Queue Position Info St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCVideo Client) sends a Transmission Request message, with acknowledgement. (Note) --> Transmission Request - - 2 Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P - EXCEPTION: Steps 3a1-3b1 describe behaviour that depends on the MCVideo Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCVideo Server requests or not acknowledgement of sent transmission control messages. - - - - 3a1 Check: Does the IUT (MCVideo Server) send a Queue Position Info message to the SS-UE, with acknowledgement? <-- Queue Position Info - P 3a2 The SS-UE (MCVideo Client) sends a Transmission Control Ack message in response to the Queue Position Info message. --> Transmission Control Ack - - 3b1 Check: Does the IUT (MCVideo Server) send a Queue Position Info message to the SS-UE, with no acknowledgement? <-- Queue Position Info - P NOTE: The SS-UE being used is specified in the test case calling the procedure. If not stated, SS-UE1 (MCVideo 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: Transmission Request (Step 1, Table A.3.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.1.1-1, with condition ACK Table A.3.12.4-2: Queue Position Info (Step 3b1, Table A.3.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.6-1 Table A.3.12.4-3: Queue Position Info (Step 3a1, Table A.3.12.3-1) Derivation Path: Table A.3.7.4-2, with condition ACK Table A.3.12.4-4: Transmission Control Ack (Step 3a2, Table A.3.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK Table A.3.12.4-5: Transmission Control Ack (Steps 2, Table A.3.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition DOWNLINK ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 384 A.3.13 MCVideo Queue Position Request - Queue Position Info 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 A.3.13.3 Procedure Table A.3.13.3-1: MCVideo Queue Position Request - Queue Position Info St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCVideo Client) sends a Queue Position Request message, with acknowledgement. (Note) --> Queue Position Request - - 2 Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P - EXCEPTION: Steps 3a1-3b1 describe behaviour that depends on the MCVideo Server implementation; the "lower case letter" identifies a step sequence that takes place if the MCVideo Server requests or not acknowledgement of sent transmission control messages. - - - - 3a1 Check: Does the IUT (MCVideo Server) send a Queue Position Info message to the SS-UE, with acknowledgement? <-- Queue Position Info - P 3a2 The SS-UE (MCVideo Client) sends a Transmission Control Ack message in response to the Queue Position Info message. --> Transmission Control Ack - - 3b1 Check: Does the IUT (MCVideo Server) send a Queue Position Info message to the SS-UE, with no acknowledgement? <-- Queue Position Info - P NOTE: The SS-UE being used is specified in the test case calling the procedure. If not stated, SS-UE1 (MCVideo 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: Queue Position Request (Step 1, Table A.3.13.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.1.3-1, with condition ACK Table A.3.13.4-2: Queue Position Info (Step 3b1, Table A.3.13.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.6-1 ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 385 Table A.3.13.4-3: Queue Position Info (Step 3a1, Table A.3.13.3-1) Derivation Path: Table A.3.7.4-2, with condition ACK Table A.3.13.4-4: Transmission Control Ack (Step 3a2, Table A.3.13.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK Table A.3.13.4-5: Transmission Control Ack (Steps 2, Table A.3.13.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition DOWNLINK A.3.14 MCVideo Transmission Revoked - Transmission End Request 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 A.3.14.3 Procedure Table A.3.14.3-1: MCVideo Transmission Revoked - Transmission End Request St Procedure Message Sequence TP Verdict U - S Message - EXCEPTION: Steps 1aA-3bB describe behaviour that depends on the MCVideo Server implementation; the "uppercase case letter" identifies a step sequence that takes place if the MCVideo Server requests or not acknowledgement of sent transmission control messages; the "lower case letter" identifies a step sequence that takes place if the MCVideo Server uses Transmission Revoked or Transmission End Request message to revoke the transmission control grant. - - - - 1aA Check: Does the IUT (MCVideo Server) send a Transmission Revoked message to the SS-UE, with acknowledgement? <-- Transmission Revoked - P 2aA The SS-UE (MCVideo Client) sends a Transmission Control Ack message in response to the Transmission Revoked message. --> Transmission Control Ack - - 3aA The SS-UE (MCVideo Client) sends a Transmission End Request message, with acknowledgement. (Note) --> Transmission End Request - - 4aA Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P 5aA Check: Does the IUT (MCVideo Server) send a Transmission End Response message to SS-UE with acknowledgement? (Note) <-- Transmission End Response - P 6aA The SS-UE (MCVideo Client) sends a Transmission Control Ack message in response --> Transmission Control Ack - - ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 386 St Procedure Message Sequence TP Verdict U - S Message to the Transmission End Response message. (Note) 1bA Check: Does the IUT (MCVideo Server) send a Transmission End Request message to SS-UE with acknowledgement? (Note) <-- Transmission End Request - P 2bA The SS-UE (MCVideo Client) sends a Transmission Control Ack message in response to the Transmission End Request message. (Note) --> Transmission Control Ack - - 3bA The SS-UE (MCVideo Client) sends a Transmission End Response message, with acknowledgement. (Note) --> Transmission End Response - - 4bA Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P 1aB Check: Does the IUT (MCVideo Server) send a Transmission Revoked message to the SS-UE, with no acknowledgement? <-- Transmission Revoked - P 2aB The SS-UE (MCVideo Client) sends a Transmission End Request message, with acknowledgement. (Note) --> Transmission End Request - - 3aB Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P 4aB Check: Does the IUT (MCVideo Server) send a Transmission End Response message to SS-UE with no acknowledgement? (Note) <-- Transmission End Response - P 1bB Check: Does the IUT (MCVideo Server) send a Transmission End Request message to SS-UE with no acknowledgement? (Note) <-- Transmission End Request - P 2bB The SS-UE (MCVideo Client) sends a Transmission End Response message, with acknowledgement. (Note) --> Transmission End Response - - 3bB Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack - P NOTE: The SS-UE being used is specified in the test case calling the procedure. If not stated, SS-UE1 (MCVideo 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: Transmission Revoked (Step 1aB, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.2-1 Table A.3.14.4-2: Transmission Revoked (Step 1aA, Table A.3.14.3-1) Derivation Path: Table A.3.14.4-1, with condition ACK ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 387 Table A.3.14.4-3: Transmission End Request (Steps 3aA and 2aB, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.1-1, with conditions ACK and UPLINK Table A.3.14.4-4: Transmission End Response (Step 4aB, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.2-1, with condition DOWNLINK Table A.3.14.4-5: Transmission End Response (Step 5aA, Table A.3.14.3-1) Derivation Path: Table A.3.14.4-4, with condition ACK Table A.3.14.4-6: Transmission End Request (Step 1bB, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.1-1, with condition DOWNLINK Table A.3.14.4-7: Transmission End Request (Step 1bA, Table A.3.14.3-1) Derivation Path: Table A.3.14.4-6, with condition ACK Table A.3.14.4-8: Transmission End Response (Steps 3bA and 2bB, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.2-1, with conditions ACK and UPLINK Table A.3.14.4-9: Transmission Control Ack (Steps 2aA, 6aA and 2bA, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK Table A.3.14.4-10: Transmission Control Ack (Steps 4aA, 4bA, 3aB and 3bB, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition DOWNLINK ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 388 Annex B (informative): Bibliography • 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2". • 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2". • 3GPP TS 24.109: "Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details". • 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". • 3GPP TS 29.283: "Diameter data management applications". • 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3". • IETF RFC 2616: "Hypertext Transfer Protocol -- HTTP/1.1". • IETF RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging". • IETF RFC 3711: "The Secure Real-time Transport Protocol (SRTP)". • IETF RFC 3840: "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)". • IETF RFC 3841: "Caller Preferences for the Session Initiation Protocol (SIP)". • IETF RFC 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 4483: "A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages". • IETF RFC 4567: "Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)". • IETF RFC 4575: "A Session Initiation Protocol (SIP) Event Package for Conference State". • IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)". • IETF RFC 4964: "Reflections on Internet Transparency". • IETF RFC 5373: "Requesting Answering Modes for the Session Initiation Protocol (SIP)". • IETF RFC 5626: "Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)". • IETF RFC 5761: "Multiplexing RTP Data and Control Packets on a Single Port". • 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 6507: "Elliptic Curve-Based Certificateless Signatures for Identity-Based Encryption (ECCSI)". • IETF RFC 6508: "Sakai-Kasahara Key Encryption (SAKKE)". • IETF RFC 6509: "MIKEY-SAKKE: Sakai-Kasahara Key Encryption in Multimedia Internet KEYing (MIKEY)". • IETF RFC 6749: "The OAuth 2.0 Authorization Framework". ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 389 • IETF RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage". • OpenID Connect 1.0. • OMA OMA-TS-XDM_Core-V2_1-20120403-A: "XML Document Management (XDM) Specification". • OMA OMA-TS-XDM_Group-V1_1_1: "Group XDM Specification". ETSI ETSI TS 104 151-1 V1.1.1 (2026-02) 390 History Version Date Status V1.1.1 February 2026 Publication |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 1 Scope | Article 45e of the amended eIDAS-Regulation (EU) No 910/2014 [i.33] obliges the EU Member States to ensure until 24 December 2026, that qualified trust service providers are able to verify at least the attributes listed Annex VI of the Regulation, wherever those attributes rely on authentic sources within the public sector, at the request of the user. Article 9 of CIR (EU) 2025/1569 [i.11] provides more information with respect to the verification mechanism, which can involve single points of verification for the attributes listed in Annex VI. Such a verification access point receives the attributes and the identification data of the subject of the attribute as input (see Article 9 (3) of [i.11]) and returns a verification result, which exclusively states whether the attribute under consideration has been verified or not, and the public sector body responsible for the authentic source or, where applicable, the public sector body designated to act on behalf of the authentic source against which the attribute has been verified (see Article 9 (4) of [i.11]). According to Article 10 (1) of CIR (EU) 2025/1569 [i.11], the "Member States may refer to and re-use the common services of the technical system set out in Article 14 of regulation (EU) 2018/1724 [i.35], as well as the national components connected to them". In a similar manner, according to Article 10 (2) of CIR (EU) 2025/1569 [i.11], "the European Commission shall refer to and re-use, where appropriate, the common services of the technical system pursuant to regulation (EU) 2018/1724 [i.35]". To be able to profit from the functionality of these services, the present document introduces in clause 5 the Discover Interface, which allows to access the semantic repository and the data services directory within the common services of the OOTS. The I1 (Discover) interface described in clause 5 is an HTTP-based interface according to ISO 15000-3 [24], as profiled by the European Commission in [i.16]. Annex A of the present document contains an OpenAPI specification [27] for this interface. The present document specifies in clause 6 the Authentic Source Interface. The I2 (Verify) interface allows to verify attributes against the content stored in an authentic source as requested in Article 45e of the amended eIDAS-Regulation (EU) No 910/2014 [i.33]. In addition, an optional I3 (Retrieve) interface is specified, which allows to retrieve attributes from an authentic source, or an intermediary acting on behalf the authentic source. The Authentic Source Interface specified in the present document contains in clause 6.1 an HTTP-based Application Programming Interface (API), which corresponding OpenAPI specification [27] is provided in Annex B of the present document. Furthermore, the present document also specifies in clause 6.2 a second ISO 15000-based interface, which utilizes the electronic delivery mechanisms according to ISO 15000-2 [23]. Moreover, according to Article 9 (5) of [i.11], the "Member States may impose access controls or other verification mechanisms that provide integrity, authenticity, and confidentiality to determine that the requester is a qualified trust service provider and is acting at the request of a legitimate user". For the HTTP-based API, clause 6.1.3 specifies such an authorization mechanism based on the OAuth 2.0 authorization framework according to IETF RFC 6749 [6] and related standards. For the ISO 15000-based interface, the qualified trust service status is verified and the trust service provider is registered as client in advance, under procedures out of scope of the present specification. In this case the evidence that the client is acting at the request of a legitimate user is also gathered before the request under procedures out of scope of the present specification. The present document specifies the necessary technical framework for the required access of the involved authentic sources, which includes architectures, components, interfaces, protocols and data structures. Note, that policy and security requirements for the involved resource service endpoints are beyond the scope of the present document. ETSI ETSI TS 119 478 V1.1.1 (2026-01) 7 |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 2 References | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] IETF RFC 1738: "Uniform Resource Locators (URL)". [2] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". [3] IETF RFC 4648: "The Base16, Base32, and Base64 Data Encodings". [4] IETF RFC 5141: "A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO)". [5] IETF RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". [6] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". [7] IETF RFC 6819: "OAuth 2.0 Threat Model and Security Considerations". [8] IETF RFC 6838: "Media Type Specifications and Registration Procedures". [9] IETF RFC 7519: "JSON Web Token (JWT)". [10] IETF RFC 7591: "OAuth 2.0 Dynamic Client Registration Protocol". [11] IETF RFC 7636: "Proof Key for Code Exchange by OAuth Public Clients". [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". [13] IETF RFC 8705: "OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens". [14] IETF RFC 9068: "JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens". [15] IETF RFC 9110: "HTTP Semantics". [16] IETF RFC 9449: "OAuth 2.0 Demonstrating Proof of Possession (DPoP)". [17] IETF RFC 9535: "JSONPath: Query Expressions for JSON". [18] IETF RFC 9562: "Universally Unique IDentifiers (UUIDs)". [19] IETF RFC 9700: "Best Current Practice for OAuth 2.0 Security". [20] ISO 639:2023: "Code for individual languages and language groups". [21] ISO 3166-1:2020: "Codes for the representation of names of countries and their subdivisions — Part 1: Country code". [22] ISO 8601-1:2019: "Date and time — Representations for information interchange — Part 1: Basic rules". ETSI ETSI TS 119 478 V1.1.1 (2026-01) 8 [23] ISO 15000-2:2021: "Electronic business eXtensible Markup Language (ebXML) — Part 2: Applicability Statement (AS) profile of ebXML messaging service". [24] ISO 15000-3:2023: "Electronic business eXtensible Markup Language (ebXML) — Part 3: Registry and repository". [25] ISO/IEC 27001:2022: "Information security, cybersecurity and privacy protection — Information security management systems — Requirements". [26] OASIS: "ebXML Messaging Protocol Binding for RegRep Version 1.0", Committee Specification 01, 09 March 2021. [27] OpenAPI Initiative: "OpenAPI Specification". [28] OpenID Foundation: "FAPI 2.0 Security Profile". [29] OpenID Foundation: "OpenID Connect Core 1.0 incorporating errata set 2". [30] W3C® Recommendation 21 March 2017: "W3C XML Path Language (XPath) 3.1". |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.