hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.2.2.3.2 Test procedure sequence | Table 5.2.2.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 private call establishment, manual commencement' as described in Annex A, Table A.4.1.2.3-1 to establish a private call with manual commencement mode and without transmission control according to option c of note in Annex A, Table A.4.1.2.3-1, from SS-UE1 (MCVideo Client) to SS-UE2 (MCVideo Client)? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E call release' as described in Annex A, Table A.4.1.5.3-1, to release the call? - - 2 P |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.2.2.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) and Annex A, in the subclauses referenced in each step. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 466 |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.3 Video Push | 5.3.1 MCVideo Server - MCVideo Server / Video push Call / One-to-one video push call / Controlling server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.3.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to SS (MCVideo Server) } ensure that { when { the SS (MCVideo Server) providing the originating participating function initiates a one- to-one video push call with transmission control } then { IUT (MCVideo Server) accepts the video push call from initiator and establishes the call with the SS (MCVideo Server) providing the terminating participating function and sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to 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 the receive media request } then { IUT (MCVideo Server) accepts the request by sending a receive media response message and SS-UE1 (MCVideo Client) starts pushing a video to SS-UE2 (MCVideo Client)} } (3) with { IUT (MCVideo Server) having established a one-to-one video push call } ensure that { when { the SS (MCVideo Server) providing the originating participating function ends the video push call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to SS (MCVideo Server) ending the call and sends a SIP BYE message to SS (MCVideo Server) providing the terminating participating function } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.3.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [5] (3GPP TS 24.281), clauses 13.2.3.2.1, 13.2.3.2.2, 10.2.2.4.1 and 10.2.5.4. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (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, 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; 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, 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; 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 ETSI TS 104 152-1 V1.1.1 (2026-02) 467 [ETSI TS 124 281 [5] (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 [5] (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; 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. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 468 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 [5] (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." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.3.1.3 Test description | |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.3.1.3.1 Pre-test conditions | System Simulator: - SS (MCVideo Server), providing the participating MCVideo functions. - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client), simulated by the SS (MCVideo Server). - SS-UE1 (MCVideo Client) has a pre-recorded video that is available to be pushed to another client. IUT: - IUT (MCVideo Server), providing the controlling MCVideo function. - 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. Preamble: - The IUT (MCVideo Server) is connected to SS (MCVideo Server). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 469 |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.3.1.3.2 Test procedure sequence | Table 5.3.1.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 private call establishment, automatic commencement' as described in Annex A, Table A.4.1.3.3-1 to push a video from SS-UE1 (MCVideo Client) to SS-UE2 (MCVideo Client), with implicit transmission control request according to option b.i of note in Annex A, Table A.4.1.3.3-1? - - 1 P 2 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 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E call release' as described in Annex A, Table A.4.1.5.3-1, to release the call? - - 3 P |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.3.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) and Annex A, in the subclauses referenced in each step, with the following clarifications. Table 5.3.1.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.3.1.3.2-1; Step 1, Annex A, Table A.4.1.3.3-1) Derivation Path: Annex A, Table A.4.1.3.4-1. Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.4.1.1.4-2 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.1.3.3-2 Table 5.3.1.3.3-2: MCVideo-Info in SIP INVITE (Table 5.3.1.3.3-1) Derivation Path: Annex A, Table A.4.1.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 152-1 V1.1.1 (2026-02) 470 Table 5.3.1.3.3-3: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.3.1.3.2-1; Step 2, Annex A, Table A.4.1.3.3-1) Derivation Path: Annex A, Table A.4.1.3.4-2. Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.4.1.1.4-5 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.3.1.3.3-4 Table 5.3.1.3.3-4: MCVideo-Info in SIP INVITE (Table 5.3.1.3.3-3) Derivation Path: Annex A, Table A.4.1.1.4-6, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params session-type "one-to-one video push" Table 5.3.1.3.3-5: SIP 200 (OK) from SS (MCVideo Server) (Step 1, Table 5.3.1.3.2-1; Step 8, Annex A, Table A.4.1.3.3-1) Derivation Path: Annex A, Table A.4.1.3.4-6 Table 5.3.1.3.3-6: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.3.1.3.2-1; Step 9, Annex A, Table A.4.1.3.3-1) Derivation Path: Annex A, Table A.4.1.3.4-7 |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.4 Video Pull | 5.4.1 MCVideo Server - MCVideo Server / Video pull Call / One-to-one video pull call / Controlling server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.4.1.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to SS (MCVideo Server) } ensure that { when { the SS (MCVideo Server) providing the originating participating function initiates a one- to-one video pull call without implicit transmission control } then { IUT (MCVideo Server) accepts the video pull call from initiator and establishes the call with the SS (MCVideo Server) providing the terminating participating function } } (2) with { IUT (MCVideo Server) having established a 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) accepts the request by sending a transmission granted message and sends media transmission notification to SS-UE1 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 471 (3) with { IUT (MCVideo Server) having established a one-to-one video pull call } ensure that { when { the SS-UE1 (MCVideo client) sends the receive media request } then { IUT (MCVideo Server) accepts the request by sending a receive media response message and SS-UE1 (MCVideo Client) starts pulling a video from SS-UE2 (MCVideo Client)} } (4) with { IUT (MCVideo Server) having established a one-to-one video pull call } ensure that { when { the SS (MCVideo Server) providing the originating participating function ends the video pull call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to SS (MCVideo Server) ending the call and sends a SIP BYE message to SS (MCVideo Server) providing the terminating participating function } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.4.1.2 Conformance requirements | References: The conformance requirements covered in the current TC are specified in: ETSI TS 124 281 [5] (3GPP TS 24.281), clauses 12.2.3.2.2, 12.2.3.2.3 and 10.2.5.4. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (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 [5] (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 152-1 V1.1.1 (2026-02) 472 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 with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, 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" with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, 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 with a SIP 488 (Not Acceptable Here) response 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; 6) if the received SIP INVITE request contains an unauthorised request for an MCVideo emergency private call as determined by clause 6.3.3.1.13.2: a) shall reject the SIP INVITE request with a SIP 403 (Forbidden) response as specified in clause 6.3.3.1.14; and b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps; 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 with a SIP 403 (Forbidden) response 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; 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. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 473 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. 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; 4) 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 3: 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. 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. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 474 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 [5] (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 [5] (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." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.4.1.3 Test description | |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.4.1.3.1 Pre-test conditions | System Simulator: - SS (MCVideo Server), providing the participating MCVideo functions. - SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client), simulated by the SS (MCVideo Server). - SS-UE2 (MCVideo Client) has a pre-recorded video that is available to be pulled from another client. IUT: - IUT (MCVideo Server), providing the controlling MCVideo function. - 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. Preamble: - The IUT (MCVideo Server) is connected to SS (MCVideo Server). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 475 |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.4.1.3.2 Test procedure sequence | Table 5.4.1.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 private call establishment, automatic commencement' as described in Annex A, Table A.4.1.3.3-1 to pull a video from SS-UE2 (MCVideo Client), without implicit transmission control request according to option a of note in Annex A, Table A.4.1.3.3-1? - - 1 P 2 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 request permission to transmit for SS-UE2 (MCVideo Client)? (Note) - - 2 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- UE2 (MCVideo Client), in SS-UE1 (MCVideo Client)? - - 3 P 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E call release' as described in Annex A, Table A.4.1.5.3-1, to release the call? - - 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 [6] (3GPP TS 24.581) clause 6.2.4.4). NOTE 2: It is not clear in ETSI TS 124 581 [6] (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 [5] (3GPP TS 24.281)) and how it shall be handled. |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.4.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) and Annex A, in the subclauses referenced in each step, with the following clarifications. Table 5.4.1.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.4.1.3.2-1; Step 1, Annex A, Table A.4.1.3.3-1) Derivation Path: Annex A, Table A.4.1.3.4-1. Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.4.1.1.4-2 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.4.1.3.3-2 Table 5.4.1.3.3-2: MCVideo-Info in SIP INVITE (Table 5.4.1.3.3-1) Derivation Path: Annex A, Table A.4.1.1.4-3, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params session-type "one-to-one video pull" ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 476 Table 5.4.1.3.3-3: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.4.1.3.2-1; Step 2, Annex A, Table A.4.1.3.3-1) Derivation Path: Annex A, Table A.4.1.3.4-2. Information Element Value/remark Comment Reference Condition Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.4.1.1.4-5 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table 5.4.1.3.3-4 Table 5.4.1.3.3-4: MCVideo-Info in SIP INVITE (Table 5.4.1.3.3-3) Derivation Path: Annex A, Table A.4.1.1.4-6, with condition PRIVATE-CALL. Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params session-type "one-to-one video pull" Table 5.4.1.3.3-5: SIP 200 (OK) from SS (MCVideo Server) (Step 1, Table 5.4.1.3.2-1; Step 8, Annex A, Table A.4.1.3.3-1) Derivation Path: Annex A, Table A.4.1.3.4-6 Table 5.4.1.3.3-6: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.4.1.3.2-1; Step 9, Annex A, Table A.4.1.3.3-1) Derivation Path: Annex A, Table A.4.1.3.4-7 Table 5.4.1.3.3-7: Media Transmission Notification (Step 2, Table 5.4.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 5.4.1.3.3-8: Media Transmission Notification (Step 2, Table 5.4.1.3.2-1; Step 3a3, Annex A, Table A.3.7.3-1) Derivation Path: Table 5.4.1.3.3-7, with condition ACK ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 477 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 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 152-1 V1.1.1 (2026-02) 478 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 152-1 V1.1.1 (2026-02) 479 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 152-1 V1.1.1 (2026-02) 480 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 152-1 V1.1.1 (2026-02) 481 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 152-1 V1.1.1 (2026-02) 482 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 [5] (3GPP TS 24.281) clause 8.2.1.3; ETSI TS 124 282 [19] (3GPP TS 24.282) clauses 8.2.3 and 22.2.1.3 Message-body MIME body part MCPTT Info ETSI TS 124 379 [3] (3GPP TS 24.379) clause 9.2.1.3 and 9A.2.1.3 MCPTT MIME-part-body MCPTT-Info as described in Table A.2.7.4-2 MIME body part MCVIDEO Info ETSI TS 124 281 [5] (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 [19] (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 [5] (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 152-1 V1.1.1 (2026-02) 483 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 [19] (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 152-1 V1.1.1 (2026-02) 484 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 152-1 V1.1.1 (2026-02) 485 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 152-1 V1.1.1 (2026-02) 486 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 152-1 V1.1.1 (2026-02) 487 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 [5] (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 [19] (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 152-1 V1.1.1 (2026-02) 488 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 152-1 V1.1.1 (2026-02) 489 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 1) --> 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 152-1 V1.1.1 (2026-02) 490 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 152-1 V1.1.1 (2026-02) 491 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 1). NOTE 1: 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 152-1 V1.1.1 (2026-02) 492 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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 493 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 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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 494 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 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). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 495 • 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 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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 496 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). 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 152-1 V1.1.1 (2026-02) 497 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 152-1 V1.1.1 (2026-02) 498 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 [8] generic-param "1800" The recommended initial value is 1 800 in IETF RFC 4028 [8]. 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 [10] port port number assigned by the SS-UE1 (even integer) The transport port to which the media stream is sent IETF RFC 6335 [11] 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 [9] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [12] "RR" 2000 IETF RFC 3556 [12] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 499 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 encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time media attribute a= line attribute =maxptime maxptime "240" maximum packet time Media description[2] Media description for 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 [12] "RR" 2500 IETF RFC 3556 [12] 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 [18] 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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 500 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 media attribute a= line attribute = fmtp fmtp format "MCVideo" format specific parameters mc_queueing not present present Parameter has no value ETSI TS 124 581 [6] (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 [6] (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 [6] (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 [6] (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 [6] (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 note 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). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 501 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 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 [13] IETF RFC 7134 [15] IETF RFC 8101 [14] 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 [8] 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 152-1 V1.1.1 (2026-02) 502 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 [6] (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 [6] (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 1 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 152-1 V1.1.1 (2026-02) 503 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 [16] 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. 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 [10] port port number assigned by the SS-UE2 (even integer) The transport port to which the media stream is sent IETF RFC 6335 [11] 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 [9] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [12] "RR" 2000 IETF RFC 3556 [12] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 504 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-2, condition SDP_ANSWER. Information Element Value/remark Comment Reference Condition 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-UE2 Bandwidth b= line "AS" 315 "RS" 0 IETF RFC 3556 [12] "RR" 2500 IETF RFC 3556 [12] 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 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. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 505 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. 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 [6] (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 [6] (3GPP TS 24.581) clause 14.2.3 PRIVATE- CALL NOTE 1: If the SS-UE requests an implicit transmission (Option b of note 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 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. 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 152-1 V1.1.1 (2026-02) 506 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 [6] (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 [6] (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 [6] (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 152-1 V1.1.1 (2026-02) 507 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 (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 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 152-1 V1.1.1 (2026-02) 508 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 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.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 152-1 V1.1.1 (2026-02) 509 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. 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 (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 - - ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 510 St Procedure Message Sequence TP Verdict U - S Message - 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.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). 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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 511 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 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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 512 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. 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. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 513 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 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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 514 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 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 [5] (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). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 515 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 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 [7] IETF RFC 3903 [17] 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 [5] (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 [5] (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 [5] (3GPP TS 24.281) clause 8.2.2.2.5 MIME-part-body PIDF as described in Table A.3.6.4-7 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 516 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 [5] (3GPP TS 24.281) clause 8.2.2.3.5 ..p-id same value as received in the SIP PUBLISH message. 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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 517 St Procedure Message Sequence TP Verdict U - S Message 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. 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 [6] (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 [6] (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 [6] (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 152-1 V1.1.1 (2026-02) 518 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 152-1 V1.1.1 (2026-02) 519 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 [6] (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 152-1 V1.1.1 (2026-02) 520 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 [6] (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 [6] (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 152-1 V1.1.1 (2026-02) 521 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 152-1 V1.1.1 (2026-02) 522 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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 523 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 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 152-1 V1.1.1 (2026-02) 524 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 152-1 V1.1.1 (2026-02) 525 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 152-1 V1.1.1 (2026-02) 526 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 152-1 V1.1.1 (2026-02) 527 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 to the Transmission End Response message. (Note) --> Transmission Control Ack - - ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 528 St Procedure Message Sequence TP Verdict U - S Message 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 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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 529 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 A.4 Generic test procedures for MCVideo Server-Server operation A.4.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 MCVideo servers or specific MCVideo relevant pre-conditions are met before a test case can be executed. A.4.1 Generic test procedures for MCVideo Controlling Server function A.4.1.1 MCVideo E2E session establishment/modification without provisional responses other than 100 Trying A.4.1.1.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 152-1 V1.1.1 (2026-02) 530 A.4.1.1.2 Definition of system information messages N/A. A.4.1.1.3 Procedure Table A.4.1.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 The SS (MCVideo Server) providing the originating participating function sends a SIP INVITE requesting the establishment/modification of a call from SS- UE1 (MCVideo Client). <-- SIP INVITE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP INVITE request to the SS (MCVideo Server) providing the terminating participating function, to establish/modify a call with SS-UE2 (MCVideo Server)? --> SIP INVITE - P 3 The SS (MCVideo Server) providing the terminating participating function sends a SIP 100 Trying to the IUT (MCVideo Server). <-- SIP 100 (Trying) - - 4 Check: Does the IUT (MCVideo Server) respond with a SIP 100 Trying to the SS (MCVideo Server) providing the originating participating function? --> SIP 100 (Trying) - P 5 The SS (MCVideo Server) providing the terminating participating function responds with a SIP 200 (OK). <-- SIP 200 (OK) - - 6 Check: Does the IUT (MCVideo Server) respond with a SIP 200 (OK) to the SS (MCVideo Server) providing the originating participating function? --> SIP 200 (OK) - P 7 The SS (MCVideo Server) providing the originating participating function sends a SIP ACK to acknowledge the session establishment/modification to the IUT (MCVideo Server). <-- SIP ACK - - 8 Check: Does the IUT (MCVideo Server) send a SIP ACK to acknowledge the session establishment/modification to the SS (MCVideo Server) providing the terminating participating function? --> SIP ACK - P - EXCEPTION: Step 9a1-9a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the SS (MCVideo Server) providing originating participating function requests implicit transmission control for SS-UE1 (MCVideo Client), in the SIP INVITE request, but it is not implicitly granted (note). - - - - 9a1 Check: Does the IUT (MCVideo Server) send a Transmission Granted message to the SS (MCVideo Server) providing originating participating function, to implicitly grant the transmission to SS-UE1 (MCVideo Client)? --> Transmission Granted - P 9a2 IF the Transmission Granted message requires acknowledgement, the SS (MCVideo Server) providing originating participating function sends a Transmission Control ACK message. <-- Transmission Control Ack - - ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 531 St Procedure Message Sequence TP Verdict U - S Message - EXCEPTION: Step 10a1-10a2 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 (MCVideo Client), either implicit or explicitly. (Note) - - - - 10a1 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to the SS (MCVideo Server) providing terminating participating function, to inform SS-UE2 (MCVideo Client) that the transmission request has been granted to SS-UE1 (MCVideo Client)? --> Media Transmission Notification - P 10a2 IF the Media Transmission Notification message requires acknowledgement, the SS (MCVideo Server) providing terminating participating function sends a Transmission Control ACK message. <-- Transmission Control Ack - - - EXCEPTION: Steps 11a1-11a2 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 (MCVideo Client). (Note) - - - - 11a1 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to the SS (MCVideo Server) providing originating participating function? --> Transmission Idle - P 11a2 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to the SS (MCVideo Server) providing terminating participating function? --> Transmission Idle - P NOTE: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS (MCVideo Server) providing originating participating function sends SDP offer with media description for transmission control but without implicit transmission request. b. SS (MCVideo Server) providing originating participating function 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 9a1). 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 (MCVideo Server) providing originating participating function sends SDP offer without media description for transmission control. A.4.1.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. Table A.4.1.1.4-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table A.4.1.1.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 Request-Line Request-URI tsc_MCVideo_PublicServiceId _B The URI of the MCVideo Server providing the controlling function. Request-URI same URI as the IUT has sent earlier in the Contact header of a response within the same dialog Contact URI of the IUT providing the controlling function. re_INVITE ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 532 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 Via sent-protocol "SIP/2.0/UDP" sent-by Address of the other endpoint (the caller) host Host name of the SIP URI being used in the From header port Same port number as in Contact-header Caller's port number via-branch Value assigned by the SS starting with 'z9hG4bK' Record-Route not present Require Not present Proxy-Require Not present From addr-spec tsc_MCVideo_PublicServiceId _A The URI of the MCVideo Server which is simulated by the SS, providing originating participating function. To addr-spec tsc_MCVideo_PublicServiceId _B The URI of the MCVideo Server providing the controlling function. Contact user-info and host tsc_MCVideo_PublicServiceId _A The URI of the MCVideo Server which is simulated by the SS, providing originating participating function. feature-param "isfocus" not present P-Asserted-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcvideo" ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.3 Call-ID IETF RFC 3261 [7] callid Value assigned by the SS providing the originating participating function Call-ID IETF RFC 3261 [7] re_INVITE callid same value as in INVITE creating the dialog Session-Expires IETF RFC 4028 [8] generic-param "1800" The recommended initial value is 1800 in IETF RFC 4028 [8]. Answer-Mode not present GROUP- CALL OR CHAT- GROUP- CALL Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.4.1.1.4-2 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table A.4.1.1.4-3 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 533 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 MIME body part Resource list PRIVATE- CALL AND NOT re_INVITE MIME-part-headers Content-Type "application/resource- lists+xml" Content-ID Unique id in format of a Message-ID assigned by the SS Unique URL identifying the Resource-lists XML MIME body; used as reference in the signature MIME body MIME-part-body Resource list as described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.3.1-2 NOTE: With condition re_INVITE for session modifications. Table A.4.1.1.4-2: SDP in SIP INVITE (Table A.4.1.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 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 Connection Data c= line Addrtype "IP4" or "IP6" depending on IP address This depends on the connection address connection-address IP address of the SS providing the originating participating function Bandwidth b= line "AS" 352 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [10] port port number assigned by the SS providing the originating participating function (even integer) The transport port to which the media stream is sent IETF RFC 6335 [11] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS providing the originating participating function Bandwidth b= line "AS" 37 "RS" 0 IETF RFC 3556 [12] ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 534 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 "RR" 2000 IETF RFC 3556 [12] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time media attribute a= line attribute =maxptime maxptime "240" maximum packet time Media description[2] Media description for 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 providing the originating participating function Bandwidth b= line "AS" 315 "RS" 0 IETF RFC 3556 [12] "RR" 2500 IETF RFC 3556 [12] 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 [18] packetization-mode "0" profile-level-id "42e00c" sprop-parameter-sets "J0LgDJWgUH6Af1A=,K M46gA==" Media description[3] Media description for media control NOT WITHOUT_ TRANSMIS SIONCONT ROL ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 535 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 media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS providing the originating participating function. 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 providing the originating participating function media attribute a= line attribute = fmtp fmtp format "MCVideo" format specific parameters mc_queueing not present present Parameter has no value ETSI TS 124 581 [6] (3GPP TS 24.581) clause 14.2.2 pc_MCVideo_ Transmission RequestQueu eing 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 [6] (3GPP TS 24.581) clause 14.2.3 GROUP- CALL OR CHAT- GROUP- CALL 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 [6] (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 [6] (3GPP TS 24.581) clause 14.2.6 GROUP- CALL OR CHAT- GROUP- CALL 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 [6] (3GPP TS 24.581) clause 14.2.6 PRIVATE- CALL ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 536 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 NOTE 1: If the SS providing the originating participating function requests a call with media transmission control and implicit transmission (Option b of note on Table A.4.1.1.3-1), apply condition IMPLICIT_GRANT_REQUESTED. NOTE 2: If the SS providing the originating participating function requests a call without media transmission (Option c of note on Table A.4.1.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.4.1.1.4-1. Otherwise, condition SDP_OFFER is applied. 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.4.1.1.4-3: MCVideo-Info in SIP INVITE (Table A.4.1.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 Information Element Value/remark Comment Reference Condition mcvideoinfo mcvideo-Params 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 mcvideo-client-id Encrypted (note) <mcvideo- client-id> with mcvideoString set to px_MCX_Client_A_ID GROUP-CALL OR CHAT-GROUP- CALL 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.4.1.1.4-4: SIP INVITE from the IUT (MCVideo-Server) (Step 2, Table A.4.1.1.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 Request-Line Request-URI tsc_MCVideo_PublicServi ceId_A The URI of the MCVideo Server providing the terminating participating function. Request-URI same URI as the SS providing the terminating participating function has sent earlier in the Contact header of a response within the same dialog Contact URI of the SS providing the terminating participating function re_INVITE Via sent-protocol "SIP/2.0/UDP" sent-by Address of the other endpoint (the caller) host Host name of the SIP URI being used in the From header port Same port number as in Contact-header Caller's port number Record-Route not present Require Not present Proxy-Require Not present Referred-By ETSI TS 124 281 [5] (3GPP TS 24.281) clauses 6.3.3.1.2 value Default public user id (px_MCX_SIP_PublicUser Id_A_1) From ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 537 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 addr-spec tsc_MCVideo_PublicServi ceId_B The URI of the MCVideo Server which is simulated by the SS, providing controlling function. To addr-spec tsc_MCVideo_PublicServi ceId_A The URI of the MCVideo Server providing the terminating participating function. Resource-Priority IETF RFC 4412 [13] IETF RFC 7134 [15] IETF RFC 8101 [14] ETSI TS 124 281 [5] (3GPP TS 24.281) clauses 9.2.1.4.1.1 and 10.2.2.4.1 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 Call-ID IETF RFC 3261 [7] callid any allowed value Call-ID IETF RFC 3261 [7] re_INVITE callid same value as in INVITE creating the dialog CSeq IETF RFC 3261 [7] value any allowed value ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 538 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 value value of CSeq sent by the endpoint within its previous request in the same dialog but increased by one re_INVITE Max-Forwards IETF RFC 3261 [7] value any allowed value Session-Expires IETF RFC 4028 [8] delta-seconds any allowed value Answer-Mode not present GROUP- CALL OR CHAT- GROUP- CALL P-Asserted-Service Service-ID "urn:urn-7:3gpp- service.ims.icsi.mcvideo" ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.2 Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.4.1.1.4-5 MIME body part MCVideo-Info MIME-part-body MCVideo-Info as described in Table A.4.1.1.4-6 NOTE: With condition re_INVITE for session modifications. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 539 Table A.4.1.1.4-5: SDP in SIP INVITE (Table A.4.1.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 4 ETSI TS 124 581 [6] (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 [6] (3GPP TS 24.581) clause 14.2.3 PRIVATE- CALL NOTE 1: If the SS providing the originating participating function requests a call without media transmission control (Option c of note on Table A.4.1.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.4.1.1.4-3. Otherwise, condition SDP_OFFER is applied. NOTE 3: Elements whose values mention the SS shall be understood as if they were referring to the IUT (MCVideo Server). 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). Table A.4.1.1.4-6: MCVideo-Info in SIP INVITE (Table A.4.1.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 mcvideo-client-id Encrypted (note) <mcvideo- client-id> with mcvideoString set to px_MCX_Client_A_ID According to ETSI TS 124 281 [5] (3GPP TS 24.281) clause 6.3.3.1.2, the controlling function shall copy the MCVideo-Info received in the incoming INVITE. ETSI TS 124 281 [5] (3GPP TS 24.281) clause 6.3.3.1.2 GROUP- CALL OR CHAT- GROUP- CALL 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 152-1 V1.1.1 (2026-02) 540 Table A.4.1.1.4-7: SIP 200 (OK) from SS (MCVideo Server) (Step 5, Table A.4.1.1.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 Supported ETSI TS 124 281 [5] (3GPP TS 24.281) clause 6.3.2.2.4.2 option-tag "tdialog" Record-Route not present Session-Expires generic-param 3600 refresher "uas" ETSI TS 124 281 [5] (3GPP TS 24.281) clause 6.3.2.2.4.2 Content-Type IETF RFC 5621 [16] value "application/sdp" Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.4.1.1.4-8 Table A.4.1.1.4-8: SDP in SIP 200 (OK) (Table A.4.1.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. Information Element Value/remark Comment Reference Condition Session description: Origin o= line username "-" "-" indicating the concept of user IDs not being supported sess-id "22222222" A numeric string such that the tuple of <username>, <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a globally unique identifier for the session. sess-version "22222222" Session Name " " s= line single empty space indicating no session name Connection Data c= line Addrtype "IP4" or "IP6" depending on IP address This depends on the connection address connection-address IP address of the SS providing the terminating participating function Bandwidth b= line "AS" 352 Media description[1] Media description for audio media description m= line media = audio IETF RFC 4867 [10] port port number assigned by the SS providing the terminating participating function (even integer) The transport port to which the media stream is sent IETF RFC 6335 [11] clause 6 fmt "99" RTP/SAVP payload type for AMR-WB is dynamic Connection Data c= line connection-address IP address of the SS providing the terminating participating function ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 541 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-2, condition SDP_ANSWER. Information Element Value/remark Comment Reference Condition Bandwidth b= line "AS" 37 ETSI TS 126 114 [9] (3GPP TS 26.114) Table K.6 "RS" 0 IETF RFC 3556 [12] "RR" 2000 IETF RFC 3556 [12] media attribute a= line attribute = rtpmap rtpmap "rtpmap" payload type "99" encoding parameter "1" Channel number media attribute a= line attribute = fmtp fmtp "fmtp" format "99" media attribute a= line attribute =ptime ptime "20" packet time media attribute a= line attribute =maxptime maxptime "240" maximum packet time Media description[2] Media description for 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 providing the terminating participating function Bandwidth b= line "AS" 315 "RS" 0 IETF RFC 3556 [12] "RR" 2500 IETF RFC 3556 [12] 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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 542 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.3.1.1-2, condition SDP_ANSWER. Information Element Value/remark Comment Reference Condition media description m= line media = application SDP media-level section for a media control entity port port number assigned by the SS providing the terminating participating function. 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 providing the terminating participating function NOTE: If the SS providing the originating participating function requests a call without media transmission (Option c of note on Table A.4.1.1.3-1) apply condition WITHOUT_TRANSMISSIONCONTROL. Table A.4.1.1.4-9: SIP 200 (OK) from IUT (MCVideo Server) (Step 6, Table A.4.1.1.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 P-Asserted-Identity ETSI TS 124 281 [5] (3GPP TS 24.281) clause 6.3.3.2.3.2 addr-spec user-info and host tsc_MCVideo_PublicService Id_B The URI of the IUT (MCVideo Server), providing controlling function. port not present Supported ETSI TS 124 281 [5] (3GPP TS 24.281) clause 6.3.3.2.3.2 option-tag "tdialog" option-tag "norefersub" option-tag "nosub" Record-Route not present Session-Expires generic-param Same value as session expires header in SIP INVITE or lower refresher "uac" ETSI TS 124 281 [5] (3GPP TS 24.281) clause 6.3.3.2.3.2 Message-body MIME body part SDP message MIME-part-body SDP Message as described in Table A.4.1.1.4-10 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 543 Table A.4.1.1.4-10: SDP in SIP 200 (OK) (Table A.4.1.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. 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 [6] (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 [6] (3GPP TS 24.581) clause 14.2.3 PRIVATE- CALL NOTE 1: If the SS providing the originating participating function requests an implicit transmission (Option b of note on Table A.4.1.1.3-1), more conditions may apply: i. If the IUT (MCVideo 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 providing the originating participating function requests a call without media transmission (Option c of note on Table A.4.1.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 IUT (MCVideo Server). Table A.4.1.1.4-11: Transmission Granted (Step 9a1, Table A.4.1.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. Table A.4.1.1.4-12: Media Transmission Notification (Step 10a1, Table A.4.1.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 [6] (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 [6] (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 [6] (3GPP TS 24.581) clause 9.2.3.21 FA ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 544 Table A.4.1.1.4-13: Transmission Idle (Steps 11a1 and 11a2, Table A.4.1.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.4.1.1.4-14: Transmission Control Ack (Steps 9a2 and 10a2, Table A.4.1.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 Table A.4.1.1.4-15: SIP ACK from SS (MCVideo Server) (Step 7, Table A.4.1.1.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.1.2-1. NOTE: Elements whose values mention the UE shall be understood as if they were referring to the IUT (MCVideo Server), and SS as SS (MCVideo Server) providing originating participating function. Table A.4.1.1.4-16: SIP ACK from IUT (MCVideo Server) (Step 8, Table A.4.1.1.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.1.2-1. Information Element Value/remark Comment Reference Condition Max-Forwards IETF RFC 3261 [7] value any allowed value Non-zero value NOTE: Elements whose values mention the UE shall be understood as if they were referring to the SS (MCVideo Server) providing terminating participating function, and SS as the IUT (MCVideo Server). A.4.1.2 MCVideo E2E private call establishment, manual commencement A.4.1.2.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.1.2.2 Definition of system information messages N/A. A.4.1.2.3 Procedure Table A.4.1.2.3-1: MCVideo E2E private call establishment, manual commencement St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the originating participating function sends a SIP INVITE requesting the establishment of a private call from SS-UE1 (MCVideo Client) to SS-UE2 (MCVideo Client), with manual commencement. <-- SIP INVITE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP INVITE request to the SS (MCVideo Server) providing the terminating participating function, to establish a private call with SS-UE2 (MCVideo Server)? --> SIP INVITE - P 3 The SS (MCVideo Server) providing the terminating participating function sends a SIP 100 Trying to the IUT (MCVideo Server). <-- SIP 100 (Trying) - - 4 Check: Does the IUT (MCVideo Server) respond with a SIP 100 Trying to the SS (MCVideo Server) providing the originating participating function? --> SIP 100 (Trying) - P ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 545 St Procedure Message Sequence TP Verdict U - S Message 5 The SS (MCVideo Server) providing the terminating participating function sends a SIP 180 Ringing to the IUT (MCVideo Server). <-- SIP 180 (Ringing) - - 6 Check: Does the IUT (MCVideo Server) respond with a SIP 180 Ringing to the SS (MCVideo Server) providing the originating participating function? --> SIP 180 (Ringing) - P 7 The SS (MCVideo Server) providing the terminating participating function responds with a SIP 200 (OK). <-- SIP 200 (OK) - - 8 Check: Does the IUT (MCVideo Server) respond with a SIP 200 (OK) to the SS (MCVideo Server) providing the originating participating function? --> SIP 200 (OK) - P 9 The SS (MCVideo Server) providing the originating participating function sends a SIP ACK to acknowledge the session establishment to the IUT (MCVideo Server). <-- SIP ACK - - 10 Check: Does the IUT (MCVideo Server) send a SIP ACK to acknowledge the session establishment to the SS (MCVideo Server) providing the terminating participating function? --> SIP ACK - P - EXCEPTION: Step 11a1-11a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the SS (MCVideo Server) providing originating participating function requests implicit transmission control for SS-UE1 (MCVideo Client), in the SIP INVITE request, but it is not implicitly granted (note). - - - - 11a1 Check: Does the IUT (MCVideo Server) send a Transmission Granted message to the SS (MCVideo Server) providing originating participating function, to implicitly grant the transmission to SS-UE1 (MCVideo Client)? --> Transmission Granted - P 11a2 IF the Transmission Granted message requires acknowledgement, the SS (MCVideo Server) providing originating participating function sends a Transmission Control ACK message. <-- Transmission Control Ack - - - EXCEPTION: Step 12a1-12a2 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 (MCVideo Client), either implicit or explicitly. (Note) - - - - 12a1 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to the SS (MCVideo Server) providing terminating participating function, to inform SS-UE2 (MCVideo Client) that the transmission request has been granted to SS-UE1 (MCVideo Client)? --> Media Transmission Notification - P 12a2 IF the Media Transmission Notification message requires acknowledgement, the SS (MCVideo Server) providing terminating participating function sends a Transmission Control ACK message. <-- Transmission Control Ack - - - EXCEPTION: Steps 13a1-13a2 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 (MCVideo Client). (Note) - - - - ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 546 St Procedure Message Sequence TP Verdict U - S Message 13a1 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to the SS (MCVideo Server) providing originating participating function? --> Transmission Idle - P 13a2 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to the SS (MCVideo Server) providing terminating participating function? --> Transmission Idle - P NOTE: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS (MCVideo Server) providing originating participating function sends SDP offer with media description for transmission control but without implicit transmission request. b. SS (MCVideo Server) providing originating participating function 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 9a1). 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 (MCVideo Server) providing originating participating function sends SDP offer without media description for transmission control. A.4.1.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. Table A.4.1.2.4-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table A.4.1.2.3-1) Derivation Path: Table A.4.1.1.4-1, with conditions PRIVATE-CALL and MANUAL. NOTE: Conditions are also applied to all body parts. Table A.4.1.2.4-2: SIP INVITE from IUT (MCVideo Server) (Step 2, Table A.4.1.2.3-1) Derivation Path: Table A.4.1.1.4-4, with conditions PRIVATE-CALL and MANUAL. NOTE: Conditions are also applied to all body parts. Table A.4.1.2.4-3: SIP 180 (Ringing) from SS (MCVideo Server) (Step 5, Table A.4.1.2.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.16.2.2-1, with conditions MCVIDEO Table A.4.1.2.4-4: SIP 180 (Ringing) from IUT (MCVideo Server) (Step 6, Table A.4.1.2.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.16.2.2-1, with conditions MCVIDEO Table A.4.1.2.4-5: SIP 200 (OK) from SS (MCVideo Server) (Step 7, Table A.4.1.2.3-1) Derivation Path: Table A.4.1.1.4-7, with condition PRIVATE-CALL. NOTE: Conditions are also applied to all body parts. Table A.4.1.2.4-6: SIP 200 (OK) from IUT (MCVideo Server) (Step 8, Table A.4.1.2.3-1) Derivation Path: Table A.4.1.1.4-9, with condition PRIVATE-CALL. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 547 Table A.4.1.2.4-7: SIP ACK from SS (MCVideo Server) (Step 9, Table A.4.1.2.3-1) Derivation Path: Table A.4.1.1.4-15 Table A.4.1.2.4-8: SIP ACK from IUT (MCVideo Server) (Step 10, Table A.4.1.2.3-1) Derivation Path: Table A.4.1.1.4-16 Table A.4.1.2.4-9: Transmission Granted (Step 11a1, Table A.4.1.2.3-1) Derivation Path: Table A.4.1.1.4-11 Table A.4.1.2.4-10: Media Transmission Notification (Step 12a1, Table A.4.1.2.3-1) Derivation Path: Table A.4.1.1.4-12 Table A.4.1.2.4-11: Transmission Idle (Steps 13a1 and 13a2, Table A.4.1.2.3-1) Derivation Path: Table A.4.1.1.4-13 Table A.4.1.2.4-12: Transmission Control Ack (Steps 11a2 and 12a2, Table A.4.1.2.3-1) Derivation Path: Table A.4.1.1.4-14 A.4.1.3 MCVideo E2E private call establishment, automatic commencement A.4.1.3.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.1.3.2 Definition of system information messages N/A. A.4.1.3.3 Procedure Table A.4.1.3.3-1: MCVideo E2E private call establishment, automatic commencement mode St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the originating participating function sends a SIP INVITE requesting the establishment of a private call from SS-UE1 (MCVideo Client) to SS-UE2 (MCVideo client), with automatic commencement. <-- SIP INVITE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP INVITE request to the SS (MCVideo Server) providing the terminating participating function, to establish a private call with SS-UE2 (MCVideo Server)? --> SIP INVITE - P 3 The SS (MCVideo Server) providing the terminating participating function sends a SIP 100 Trying to the IUT (MCVideo Server). <-- SIP 100 (Trying) - - ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 548 St Procedure Message Sequence TP Verdict U - S Message 4 Check: Does the IUT (MCVideo Server) respond with a SIP 100 Trying to the SS (MCVideo Server) providing the originating participating function? --> SIP 100 (Trying) - P 5 The SS (MCVideo Server) providing the terminating participating function sends a SIP 183 (Session Progress) reliably. <-- SIP 183 (Session Progress) - - 6 Check: Does the IUT (MCVideo Server) acknowledge the receipt of SIP 183 (Session Progress) from SS (MCVideo Server)? --> PRACK - P 7 The SS (MCVideo Server) providing the terminating participating function responds a SIP 200 (OK) to PRACK message <-- SIP 200 (OK) - - 8 The SS (MCVideo Server) providing the terminating participating function responds with a SIP 200 (OK). <-- SIP 200 (OK) - - 9 Check: Does the IUT (MCVideo Server) respond with a SIP 200 (OK) to the SS (MCVideo Server) providing the originating participating function? --> SIP 200 (OK) - P 10 The SS (MCVideo Server) providing the originating participating function sends a SIP ACK to acknowledge the session establishment to the IUT (MCVideo Server). <-- SIP ACK - - 11 Check: Does the IUT (MCVideo Server) send a SIP ACK to acknowledge the session establishment to the SS (MCVideo Server) providing the terminating participating function? --> SIP ACK - P - EXCEPTION: Step 12a1-12a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the SS (MCVideo Server) providing originating participating function requests implicit transmission control for SS-UE1 (MCVideo Client), in the SIP INVITE request, but it is not implicitly granted (note). - - - - 12a1 Check: Does the IUT (MCVideo Server) send a Transmission Granted message to the SS (MCVideo Server) providing originating participating function, to implicitly grant the transmission to SS-UE1 (MCVideo Client)? --> Transmission Granted - P 12a2 IF the Transmission Granted message requires acknowledgement, the SS (MCVideo Server) providing originating participating function sends a Transmission Control ACK message. <-- Transmission Control Ack - - - EXCEPTION: Step 13a1-13a2 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 (MCVideo Client), either implicit or explicitly. (Note) - - - - 13a1 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to the SS (MCVideo Server) providing terminating participating function, to inform SS-UE2 (MCVideo Client) that the transmission request has been granted to SS-UE1 (MCVideo Client)? --> Media Transmission Notification - P 13a2 IF the Media Transmission Notification message requires acknowledgement, the SS (MCVideo Server) providing terminating participating function sends a Transmission Control ACK message. <-- Transmission Control Ack - - ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 549 St Procedure Message Sequence TP Verdict U - S Message - EXCEPTION: Steps 14a1-14a2 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 (MCVideo Client). (Note) - - - - 14a1 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to the SS (MCVideo Server) providing originating participating function? --> Transmission Idle - P 14a2 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to the SS (MCVideo Server) providing terminating participating function? --> Transmission Idle - P NOTE: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS (MCVideo Server) providing originating participating function sends SDP offer with media description for transmission control but without implicit transmission request. b. SS (MCVideo Server) providing originating participating function 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 9a1). 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 (MCVideo Server) providing originating participating function sends SDP offer without media description for transmission control. A.4.1.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. Table A.4.1.3.4-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table A.4.1.3.3-1) Derivation Path: Table A.4.1.1.4-1, with condition PRIVATE-CALL. NOTE: Conditions are also applied to all body parts. Table A.4.1.3.4-2: SIP INVITE from IUT (MCVideo Server) (Step 2, Table A.4.1.3.3-1) Derivation Path: Table A.4.1.1.4-4, with condition PRIVATE-CALL. NOTE: Conditions are also applied to all body parts. Table A.4.1.3.4-3: SIP 183 (Session Progress) from SS (MCVideo Server) (Step 5, Table A.4.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.16.3.2-1, with conditions MCVIDEO and 100rel Table A.4.1.3.4-4: SIP PRACK from IUT (MCVideo Server) (Step 6, Table A.4.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.10.2-1. Information Element Value/remark Comment Reference Condition Max-Forwards IETF RFC 3261 [7] value any allowed value Non-zero value NOTE: Elements whose values mention the UE shall be understood as if they were referring to the SS (MCVideo Server) providing terminating participating function. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 550 Table A.4.1.3.4-5: SIP 200 (OK) to PRACK from SS (MCVideo Server) (Step 7, Table A.4.1.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1 Table A.4.1.3.4-6: SIP 200 (OK) from SS (MCVideo Server) (Step 8, Table A.4.1.3.3-1) Derivation Path: Table A.4.1.1.4-7, with condition PRIVATE-CALL. NOTE: Conditions are also applied to all body parts. Table A.4.1.3.4-7: SIP 200 (OK) from IUT (MCVideo Server) (Step 9, Table A.4.1.3.3-1) Derivation Path: Table A.4.1.1.4-9, with condition PRIVATE-CALL. NOTE: Conditions are also applied to all body parts. Table A.4.1.3.4-8: SIP ACK from SS (MCVideo Server) (Step 10, Table A.4.1.3.3-1) Derivation Path: Table A.4.1.1.4-15 Table A.4.1.3.4-9: SIP ACK from IUT (MCVideo Server) (Step 11, Table A.4.1.3.3-1) Derivation Path: Table A.4.1.1.4-16 Table A.4.1.3.4-10: Transmission Granted (Step 12a1, Table A.4.1.3.3-1) Derivation Path: Table A.4.1.1.4-11 Table A.4.1.3.4-11: Media Transmission Notification (Step 13a1, Table A.4.1.3.3-1) Derivation Path: Table A.4.1.1.4-12 Table A.4.1.3.4-12: Transmission Idle (Steps 14a1 and 14a2, Table A.4.1.3.3-1) Derivation Path: Table A.4.1.1.4-13 Table A.4.1.3.4-13: Transmission Control Ack (Steps 12a2 and 13a2, Table A.4.1.3.3-1) Derivation Path: Table A.4.1.1.4-14 A.4.1.4 MCVideo E2E group call establishment A.4.1.4.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.1.4.2 Definition of system information messages N/A. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 551 A.4.1.4.3 Procedure Table A.4.1.4.3-1: MCVideo E2E group call establishment St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the originating participating function sends a SIP INVITE requesting the establishment of a group call from SS-UE1 (MCVideo Client). <-- SIP INVITE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP INVITE request to the SS (MCVideo Server) providing the terminating participating function, to establish a group call with SS-UE2 (MCVideo Server)? --> SIP INVITE - P 3 The SS (MCVideo Server) providing the terminating participating function sends a SIP 100 Trying to the IUT (MCVideo Server). <-- SIP 100 (Trying) - - 4 Check: Does the IUT (MCVideo Server) respond with a SIP 100 Trying to the SS (MCVideo Server) providing the originating participating function? --> SIP 100 (Trying) - P 5 The SS (MCVideo Server) providing the terminating participating function sends a SIP 183 (Session Progress) reliably. <-- SIP 183 (Session Progress) - - 6 Check: Does the IUT (MCVideo Server) acknowledge the receipt of SIP 183 (Session Progress) from SS (MCVideo Server)? --> PRACK - P 7 The SS (MCVideo Server) providing the terminating participating function responds a SIP 200 (OK) to PRACK message <-- SIP 200 (OK) - - 8 The SS (MCVideo Server) providing the terminating participating function responds with a SIP 200 (OK). <-- SIP 200 (OK) - - 9 Check: Does the IUT (MCVideo Server) respond with a SIP 200 (OK) to the SS (MCVideo Server) providing the originating participating function? --> SIP 200 (OK) - P 10 The SS (MCVideo Server) providing the originating participating function sends a SIP ACK to acknowledge the session establishment to the IUT (MCVideo Server). <-- SIP ACK - - 11 Check: Does the IUT (MCVideo Server) send a SIP ACK to acknowledge the session establishment to the SS (MCVideo Server) providing the terminating participating function? --> SIP ACK - P - EXCEPTION: Step 12a1-12a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the SS (MCVideo Server) providing originating participating function requests implicit transmission control for SS-UE1 (MCVideo Client), in the SIP INVITE request, but it is not implicitly granted (note). - - - - 12a1 Check: Does the IUT (MCVideo Server) send a Transmission Granted message to the SS (MCVideo Server) providing originating participating function, to implicitly grant the transmission to SS-UE1 (MCVideo Client)? --> Transmission Granted - P 12a2 IF the Transmission Granted message requires acknowledgement, the SS (MCVideo Server) providing originating participating function sends a Transmission Control ACK message. <-- Transmission Control Ack - - ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 552 St Procedure Message Sequence TP Verdict U - S Message - EXCEPTION: Step 13a1-13a2 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 (MCVideo Client), either implicit or explicitly. (Note) - - - - 13a1 Check: Does the IUT (MCVideo Server) send a Media Transmission Notification message to the SS (MCVideo Server) providing terminating participating function, to inform SS-UE2 (MCVideo Client) that the transmission request has been granted to SS-UE1 (MCVideo Client)? --> Media Transmission Notification - P 13a2 IF the Media Transmission Notification message requires acknowledgement, the SS (MCVideo Server) providing terminating participating function sends a Transmission Control ACK message. <-- Transmission Control Ack - - - EXCEPTION: Steps 14a1-14a2 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 (MCVideo Client). (Note) - - - - 14a1 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to the SS (MCVideo Server) providing originating participating function? --> Transmission Idle - P 14a2 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to the SS (MCVideo Server) providing terminating participating function? --> Transmission Idle - P NOTE: Possibilities in SDP-offer/answer depend on the test case requirements a. SS (MCVideo Server) providing originating participating function sends SDP offer with media description for transmission control but without implicit transmission request. b. SS (MCVideo Server) providing originating participating function 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 9a1). 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 (MCVideo Server) providing originating participating function sends SDP offer without media description for transmission control. A.4.1.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. Table A.4.1.4.4-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table A.4.1.4.3-1) Derivation Path: Table A.4.1.1.4-1, with condition GROUP -CALL. NOTE 1: Conditions are also applied to all body parts. NOTE 2: For chat group calls CHAT-GROUP-CALL condition shall be used instead of GROUP-CALL. Table A.4.1.4.4-2: SIP INVITE from IUT (MCVideo Server) (Step 2, Table A.4.1.4.3-1) Derivation Path: Table A.4.1.1.4-4, with condition GROUP -CALL. NOTE 1: Conditions are also applied to all body parts. NOTE 2: For chat group calls CHAT-GROUP-CALL condition shall be used instead of GROUP-CALL. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 553 Table A.4.1.4.4-3: SIP 183 (Session Progress) from SS (MCVideo Server) (Step 5, Table A.4.1.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.16.3.2-1, with conditions MCVIDEO and 100rel. Table A.4.1.4.4-4: SIP PRACK from IUT (MCVideo Server) (Step 6, Table A.4.1.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.10.2-1. Information Element Value/remark Comment Reference Condition Max-Forwards IETF RFC 3261 [7] value any allowed value Non-zero value NOTE: Elements whose values mention the UE shall be understood as if they were referring to the SS (MCVideo Server) providing terminating participating function. Table A.4.1.4.4-5: SIP 200 (OK) to PRACK from SS (MCVideo Server) (Step 7, Table A.4.1.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1. Table A.4.1.4.4-6: SIP 200 (OK) from SS (MCVideo Server) (Step 8, Table A.4.1.4.3-1) Derivation Path: Table A.4.1.1.4-7, with condition GROUP -CALL. NOTE 1: Conditions are also applied to all body parts. NOTE 2: For chat group calls CHAT-GROUP-CALL condition shall be used instead of GROUP-CALL. Table A.4.1.4.4-7: SIP 200 (OK) from IUT (MCVideo Server) (Step 9, Table A.4.1.4.3-1) Derivation Path: Table A.4.1.1.4-9, with condition GROUP-CALL. NOTE 1: Conditions are also applied to all body parts. NOTE 2: For chat group calls CHAT-GROUP-CALL condition shall be used instead of GROUP-CALL. Table A.4.1.4.4-8: SIP ACK from SS (MCVideo Server) (Step 10, Table A.4.1.4.3-1) Derivation Path: Table A.4.1.1.4-15 Table A.4.1.4.4-9: SIP ACK from IUT (MCVideo Server) (Step 11, Table A.4.1.4.3-1) Derivation Path: Table A.4.1.1.4-16 Table A.4.1.4.4-10: Transmission Granted (Step 12a1, Table A.4.1.4.3-1) Derivation Path: Table A.4.1.1.4-11 Table A.4.1.4.4-11: Media Transmission Notification (Step 13a1, Table A.4.1.4.3-1) Derivation Path: Table A.4.1.1.4-12 Table A.4.1.4.4-12: Transmission Idle (Steps 14a1 and 14a2, Table A.4.1.4.3-1) Derivation Path: Table A.4.1.1.4-13 Table A.4.1.4.4-13: Transmission Control Ack (Steps 12a2 and 13a2, Table A.4.1.4.3-1) Derivation Path: Table A.4.1.1.4-14 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 554 A.4.1.5 MCVideo E2E call release A.4.1.5.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.1.5.2 Definition of system information messages N/A. A.4.1.5.3 Procedure Table A.4.1.5.3-1: MCVideo E2E call release St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the originating participating function sends a SIP BYE to terminate the call. <-- SIP BYE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP BYE request to the SS (MCVideo Server) providing the terminating participating function? --> SIP BYE - P 3 The SS (MCVideo Server) providing the terminating participating function responds with a 200 (OK) to the IUT (MCVideo Server). <-- SIP 200 (OK) - - 4 Check: Does the IUT (MCVideo Server) forward the SIP 200 (OK) response to the SS (MCVideo Server) providing the originating participating function? --> SIP 200 (OK) - P A.4.1.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 with condition MCVIDEO and in the test case calling the procedure with the following clarifications. Table A.4.1.5.4-1: SIP BYE from the SS (MCVideo Server) (Step 1, Table A.4.1.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.2.2-1. NOTE: References to UE in subclauses relate to the IUT (MCVideo Server) and SS references to the SS (MCVideo Server) providing the originating participating function. Table A.4.1.5.4-2: SIP BYE from the IUT (MCVideo Server) (Step 2, Table A.4.1.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.2.2-1. NOTE: References to UE in subclauses relate to the SS (MCVideo Server) providing the terminating participating function and SS references to the IUT (MCVideo Server). Table A.4.1.5.4-3: SIP 200 OK from the SS (MCVideo Server) (Step 3, Table A.4.1.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1. Table A.4.1.5.4-4: SIP 200 OK from the IUT (MCVideo Server) (Step 4, Table A.4.1.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 555 A.4.1.6 MCVideo CO session establishment/modification without provisional responses other than 100 Trying A.4.1.6.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.1.6.2 Definition of system information messages N/A. A.4.1.6.3 Procedure Table A.4.1.6.3-1: MCVideo CO session establishment/modification without provisional responses other than 100 Trying St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the originating participating function sends a SIP INVITE requesting the establishment/modification of a call from SS- UE1 (MCVideo Client). (Note 2) <-- SIP INVITE - - 2 Check: Does the IUT (MCVideo Server) respond with a SIP 100 Trying to the SS (MCVideo Server) providing the originating participating function? --> SIP 100 (Trying) - P 3 Check: Does the IUT (MCVideo Server) respond with a SIP 200 (OK) to the SS (MCVideo Server) providing the originating participating function? --> SIP 200 (OK) - P 4 The SS (MCVideo Server) providing the originating participating function sends a SIP ACK to acknowledge the session establishment/modification to the IUT (MCVideo Server). <-- SIP ACK - - - EXCEPTION: Step 5a1-5a2 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the SS (MCVideo Server) providing originating participating function requests implicit transmission control for SS-UE (MCVideo Client), in the SIP INVITE request, but it is not implicitly granted (Notes 1 and 2). - - - - 5a1 Check: Does the IUT (MCVideo Server) send a Transmission Granted message to the SS (MCVideo Server) providing originating participating function, to implicitly grant the transmission to SS-UE (MCVideo Client)? (Note 2) --> Transmission Granted - P 5a2 IF the Transmission Granted message requires acknowledgement, the SS (MCVideo Server) providing originating participating function sends a Transmission Control ACK message. <-- Transmission Control Ack - - - EXCEPTION: Step 6a1 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 (MCVideo Client). (Notes 1 and 2) - - - - ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 556 St Procedure Message Sequence TP Verdict U - S Message 6a1 Check: Does the IUT (MCVideo Server) send a Transmission Idle message to the SS (MCVideo Server) providing originating participating function? --> Transmission Idle - P NOTE 1: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS (MCVideo Server) providing originating participating function sends SDP offer with media description for transmission control but without implicit transmission request. b. SS (MCVideo Server) providing originating participating function 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 9a1). 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 (MCVideo Server) providing originating participating function 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. If not stated, SS-UE1 (MCVideo Client) will be assumed. A.4.1.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 with condition MCVIDEO and in the test case calling the procedure with the following clarifications. Table A.4.1.6.4-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table A.4.1.6.3-1) Derivation Path: Table A.4.1.1.4-1. Table A.4.1.6.4-2: SIP 200 (OK) from IUT (MCVideo Server) (Step 3, Table A.4.1.6.3-1) Derivation Path: Table A.4.1.1.4-9. Table A.4.1.6.4-3: SIP ACK from SS (MCVideo Server) (Step 4, Table A.4.1.6.3-1) Derivation Path: Table A.4.1.1.4-15 Table A.4.1.6.4-4: Transmission Granted (Step 5a1, Table A.4.1.6.3-1) Derivation Path: Table A.4.1.1.4-11 Table A.4.1.6.4-5: Transmission Idle (Step 6a1, Table A.4.1.6.3-1) Derivation Path: Table A.4.1.1.4-13 Table A.4.1.6.4-6: Transmission Control Ack (Step 5a2, Table A.4.1.6.3-1) Derivation Path: Table A.4.1.1.4-14 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 557 A.4.2 Generic test procedures for MCVideo Originating Participating Server function A.4.2.1 MCVideo CO session establishment/modification without provisional responses other than 100 Trying A.4.2.1.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.2.1.2 Definition of system information messages N/A. A.4.2.1.3 Procedure Table A.4.2.1.3-1: MCVideo CO session establishment/modification without provisional responses other than 100 Trying St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCVideo Client) sends a SIP INVITE requesting the establishment/modification of a call. <-- SIP INVITE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP INVITE request to the SS (MCVideo Server) providing the controlling function, to establish/modify a call? --> SIP INVITE - P 3 The SS (MCVideo Server) providing the controlling function sends a SIP 100 Trying to the IUT (MCVideo Server). <-- SIP 100 (Trying) - - 4 Check: Does the IUT (MCVideo Server) respond with a SIP 100 Trying to the SS-UE1 (MCVideo Client)? --> SIP 100 (Trying) - P 5 The SS (MCVideo Server) providing the controlling function responds with a SIP 200 (OK). <-- SIP 200 (OK) - - 6 Check: Does the IUT (MCVideo Server) respond with a SIP 200 (OK) to the SS-UE1 (MCVideo Client)? --> SIP 200 (OK) - P 7 The SS-UE1 (MCVideo Client) sends a SIP ACK to acknowledge the session establishment/modification to the IUT (MCVideo Server). <-- SIP ACK - - 8 Check: Does the IUT (MCVideo Server) send a SIP ACK to acknowledge the session establishment/modification to the SS (MCVideo Server) providing the controlling function? --> SIP ACK - P - EXCEPTION: Step 9a1-9a4 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the SS-UE1 (MCVideo Client) requests implicit transmission control in the SIP INVITE request, but it is not implicitly granted (Note). - - - - 9a1 The SS (MCVideo Server) providing the controlling function sends a Transmission Granted message with request for acknowledgement to the IUT (MCVideo Server), to grant the transmission to SS-UE1 (MCVideo Client). <-- Transmission Granted - - ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 558 St Procedure Message Sequence TP Verdict U - S Message 9a2 Check: Does the IUT (MCVideo Server) forward the Transmission Granted message to the SS- UE1 (MCVideo Client)? --> Transmission Granted - P 9a3 The SS-UE1 (MCVideo Client) sends a Transmission Control ACK message. <-- Transmission Control Ack - - 9a4 Check: Does the IUT (MCVideo Server) forward the acknowledgement of SS-UE1 (MCVideo Client) to SS (MCVideo Server)? --> Transmission Control Ack - P - EXCEPTION: Steps 10a1-10a2 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 (MCVideo Client). (Note) - - - - 10a1 The SS (MCVideo Server) providing the controlling function sends a Transmission Idle message to the IUT (MCVideo Server). <-- Transmission Idle - - 10a2 Check: Does the IUT (MCVideo Server) forward the Transmission Idle message to the SS-UE1 (MCVideo Client)? --> Transmission Idle - P NOTE: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS (MCVideo Server) providing originating participating function sends SDP offer with media description for transmission control but without implicit transmission request. b. SS (MCVideo Server) providing originating participating function 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 9a1). 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 (MCVideo Server) providing originating participating function sends SDP offer without media description for transmission control. A.4.2.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. Table A.4.2.1.4-1: SIP INVITE from SS-UE1 (MCVideo Client) (Step 1, Table A.4.2.1.3-1) Derivation Path: Table A.3.1.4-1 Table A.4.2.1.4-2: SIP INVITE from IUT (MCVideo Server) (Step 2, Table A.4.2.1.3-1) Derivation Path: Table A.4.1.1.4-1 Table A.4.2.1.4-3: SIP 200 (OK) from SS (MCVideo Server) (Step 5, Table A.4.2.1.3-1) Derivation Path: Table A.4.1.1.4-9 Table A.4.2.1.4-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 6, Table A.4.2.1.3-1) Derivation Path: Table A.3.1.4-9 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 559 Table A.4.2.1.4-5: SIP ACK from SS-UE1 (MCVideo Client) (Step 7, Table A.4.2.1.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.1.1-1. NOTE: Elements whose values mention the UE shall be understood as if they were referring to the SS-UE1 (MCVideo Client), and SS as IUT (MCVideo Server) providing the originating participating function. Table A.4.2.1.4-6: SIP ACK from IUT (MCVideo Server) (Step 8, Table A.4.2.1.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.1.2-1. Information Element Value/remark Comment Reference Condition Max-Forwards IETF RFC 3261 [7] value any allowed value Non-zero value NOTE: Elements whose values mention the UE shall be understood as if they were referring to the SS (MCVideo Server) providing the controlling function, and SS as the IUT (MCVideo Server). Table A.4.2.1.4-7: Transmission Granted (Steps 9a1 and 9a2, Table A.4.2.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 Table A.4.2.1.4-8: Transmission Idle (Steps 10a1 and 10a2, Table A.4.2.1.3-1) Derivation Path: Table A.4.1.1.4-13 Table A.4.2.1.4-9: Transmission Control Ack (Steps 9a3 and 9a4, Table A.4.2.1.3-1) Derivation Path: Table A.4.1.1.4-14 A.4.2.2 MCVideo CO private call establishment, manual commencement A.4.2.2.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.2.2.2 Definition of system information messages N/A. A.4.2.2.3 Procedure Table A.4.2.2.3-1: MCVideo CO private call establishment, manual commencement St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCVideo Client) sends a SIP INVITE requesting the establishment of a private call with SS-UE2 (MCVideo Client). <-- SIP INVITE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP INVITE request to the SS (MCVideo Server) providing the controlling function, to establish a call with SS-UE2 (MCVideo Client)? --> SIP INVITE - P 3 The SS (MCVideo Server) providing the controlling function sends a SIP 100 Trying to the IUT (MCVideo Server). <-- SIP 100 (Trying) - - 4 Check: Does the IUT (MCVideo Server) respond with a SIP 100 Trying to the SS-UE1 (MCVideo Client)? --> SIP 100 (Trying) - P ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 560 St Procedure Message Sequence TP Verdict U - S Message 5 The SS (MCVideo Server) providing the controlling function sends a SIP 180 Ringing to the IUT (MCVideo Server). <-- SIP 180 (Ringing) - - 6 Check: Does the IUT (MCVideo Server) respond with a SIP 180 Ringing to the SS-UE1 (MCVideo Client)? --> SIP 180 (Ringing) - P 7 The SS (MCVideo Server) providing the controlling function responds with a SIP 200 (OK). <-- SIP 200 (OK) - - 8 Check: Does the IUT (MCVideo Server) respond with a SIP 200 (OK) to the SS-UE1 (MCVideo Client)? --> SIP 200 (OK) - P 9 The SS-UE1 (MCVideo Client) sends a SIP ACK to acknowledge the session establishment to the IUT (MCVideo Server). <-- SIP ACK - - 10 Check: Does the IUT (MCVideo Server) send a SIP ACK to acknowledge the session establishment to the SS (MCVideo Server) providing the controlling function? --> SIP ACK - P - EXCEPTION: Step 11a1-11a4 describes behaviour that depends on the test case requirements; the "lower case letter" identifies a step sequence that takes place if the SS-UE1 (MCVideo Client) requests implicit transmission control in the SIP INVITE request, but it is not implicitly granted (Note). - - - - 11a1 The SS (MCVideo Server) providing the controlling function sends a Transmission Granted message with request for acknowledgement to the IUT (MCVideo Server), to grant the transmission to SS-UE1 (MCVideo Client). <-- Transmission Granted - P 11a2 Check: Does the IUT (MCVideo Server) forward the Transmission Granted message to the SS- UE1 (MCVideo Client)? --> Transmission Granted - P 11a3 The SS-UE1 (MCVideo Client) sends a Transmission Control ACK message. <-- Transmission Control Ack - - 11a4 Check: Does the IUT (MCVideo Server) forward the acknowledgement of SS-UE1 (MCVideo Client) to SS (MCVideo Server)? --> Transmission Control Ack - P - EXCEPTION: Steps 12a1-12a2 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 (MCVideo Client). (Note) - - - - 12a1 The SS (MCVideo Server) providing the controlling function sends a Transmission Idle message to the IUT (MCVideo Server). <-- Transmission Idle - - 12a2 Check: Does the IUT (MCVideo Server) forward the Transmission Idle message to the SS-UE1 (MCVideo Client)? --> Transmission Idle - P NOTE 1: Possibilities in SDP-offer/answer depend on the test case requirements: a. SS (MCVideo Server) providing originating participating function sends SDP offer with media description for transmission control but without implicit transmission request. b. SS (MCVideo Server) providing originating participating function 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 9a1). 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 (MCVideo Server) providing originating participating function sends SDP offer without media description for transmission control. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 561 A.4.2.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. Table A.4.2.2.4-1: SIP INVITE from SS-UE1 (MCVideo Client) (Step 1, Table A.4.2.2.3-1) Derivation Path: Table A.4.2.1.4-1, with conditions PRIVATE-CALL and MANUAL. NOTE: Conditions are also applied to all body parts. Table A.4.2.2.4-2: SIP INVITE from IUT (MCVideo Server) (Step 2, Table A.4.2.2.3-1) Derivation Path: Table A.4.2.1.4-2, with conditions PRIVATE-CALL and MANUAL. NOTE: Conditions are also applied to all body parts. Table A.4.2.2.4-3: SIP 180 (Ringing) from SS (MCVideo Server) (Step 5, Table A.4.2.2.3-1) Derivation Path: Table A.4.1.2.4-4 Table A.4.2.2.4-4: SIP 180 (Ringing) from IUT (MCVideo Server) (Step 6, Table A.4.2.2.3-1) Derivation Path: Table A.3.3.4-9 Table A.4.2.2.4-5: SIP 200 (OK) from SS (MCVideo Server) (Step 7, Table A.4.2.2.3-1) Derivation Path: Table A.4.2.1.4-3, with condition PRIVATE-CALL. NOTE: Conditions are also applied to all body parts. Table A.4.2.2.4-6: SIP 200 (OK) from IUT (MCVideo Server) (Step 8, Table A.4.2.2.3-1) Derivation Path: Table A.4.2.1.4-4, with condition PRIVATE-CALL. NOTE: Conditions are also applied to all body parts. Table A.4.2.2.4-7: SIP ACK from SS-UE1 (MCVideo Client) (Step 9, Table A.4.2.2.3-1) Derivation Path: Table A.4.2.1.4-5 Table A.4.2.2.4-8: SIP ACK from IUT (MCVideo Server) (Step 10, Table A.4.2.2.3-1) Derivation Path: Table A.4.2.1.4-6 Table A.4.2.2.4-9: Transmission Granted (Steps 11a1 and 11a2, Table A.4.2.2.3-1) Derivation Path: Table A.4.2.1.4-7 Table A.4.2.2.4-10: Transmission Idle (Steps 12a1 and 12a2, Table A.4.2.2.3-1) Derivation Path: Table A.4.2.1.4-8 Table A.4.2.2.4-11: Transmission Control Ack (Steps 11a3 and 11a4, Table A.4.2.2.3-1) Derivation Path: Table A.4.2.1.4-9 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 562 A.4.2.3 MCVideo CO call release A.4.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.4.2.3.2 Definition of system information messages N/A. A.4.2.3.3 Procedure Table A.4.2.3.3-1: MCVideo CO call release St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE1 (MCVideo Client) sends a SIP BYE to terminate the call. <-- SIP BYE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP BYE request to the SS (MCVideo Server) providing the controlling function? --> SIP BYE - P 3 The SS (MCVideo Server) providing the controlling function responds with a 200 (OK) to the IUT (MCVideo Server). <-- SIP 200 (OK) - - 4 Check: Does the IUT (MCVideo Server) forward the SIP 200 (OK) response to the SS-UE1 (MCVideo Client)? --> SIP 200 (OK) - P A.4.2.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. Table A.4.2.3.4-1: SIP BYE from the SS-UE1 (Step 1, Table A.4.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.2.1-1. NOTE: References to UE in subclauses relate to the SS-UE1 (MCVideo Client) and SS references to the IUT (MCVideo Server). Table A.4.2.3.4-2: SIP BYE from the IUT (MCVideo Server) (Step 2, Table A.4.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.2.2-1. NOTE: References to UE in subclauses relate to the SS (MCVideo Server) providing the controlling function and SS references to the IUT (MCVideo Server). Table A.4.2.3.4-3: SIP 200 OK from the SS (MCVideo Server) (Step 3, Table A.4.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1. Table A.4.2.3.4-4: SIP 200 OK from the IUT (MCVideo Server) (Step 4, Table A.4.2.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 563 A.4.2.4 MCVideo Transmission Request - Transmission Granted A.4.2.4.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.2.4.2 Definition of system information messages N/A. A.4.2.4.3 Procedure Table A.4.2.4.3-1: MCVideo Transmission Request - Transmission Granted St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCVideo Client) sends a Transmission Request message, with request for acknowledgement. (Note) <-- Transmission Request - - 2 Check: Does the IUT (MCVideo Server) forward the Transmission Request message to the SS (MCVideo Server) providing the controlling function? --> Transmission Request - P 3 The SS (MCVideo Server) acknowledges the Transmission Request message. <-- Transmission Control Ack - - 4 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 5 The SS (MCVideo Server) providing the controlling function sends a Transmission Granted message with request for acknowledgement to IUT (MCVideo Server). <-- Transmission Granted - - 6 Check: Does the IUT (MCVideo Server) forward the Transmission Granted message to SS-UE (MCVideo Client)? (Note) --> Transmission Granted - P 7 The SS-UE (MCVideo Client) acknowledges the Transmission Granted message. (Note) <-- Transmission Control Ack - - 8 Check: Does the IUT (MCVideo Server) forward the 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.4.2.4.4 Specific message contents All message contents are as specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), clause 5.5 and in the test case calling the procedure, with the following clarifications. Table A.4.2.4.4-1: Transmission Request (Steps 1 and 2, Table A.4.2.4.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.4.2.4.4-2: Transmission Granted (Steps 5 and 6, Table A.4.2.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 Table A.4.2.4.4-3: Transmission Control Ack (Steps 3 and 4, Table A.4.2.4.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 152-1 V1.1.1 (2026-02) 564 Table A.4.2.4.4-4: Transmission Control Ack (Steps 7 and 8, Table A.4.2.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.4.2.5 MCVideo CO Transmission End Request - Transmission End Response A.4.2.5.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.2.5.2 Definition of system information messages N/A. A.4.2.5.3 Procedure Table A.4.2.5.3-1: MCVideo CO Transmission End Request - Transmission End Response St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCVideo Client) sends a Transmission End Request message, with request for acknowledgement. (Note) <-- Transmission End Request - - 2 Check: Does the IUT (MCVideo Server) forward the Transmission End Request message to the SS (MCVideo Server) providing the controlling function? --> Transmission End Request - P 3 The SS (MCVideo Server) acknowledges the Transmission End Request message. <-- Transmission Control Ack - - 4 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 5 The SS (MCVideo Server) providing the controlling function sends a Transmission End Response message with request for acknowledgement to IUT (MCVideo Server). <-- Transmission End Response - - 6 Check: Does the IUT (MCVideo Server) forward the Transmission End Response message to SS-UE (MCVideo Client)? (Note) --> Transmission End Response - P 7 The SS-UE (MCVideo Client) acknowledges the Transmission End Response message. (Note) <-- Transmission Control Ack - - 8 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 9 The SS (MCVideo Server) providing the controlling function sends a Transmission Idle message to IUT (MCVideo Server). <-- Transmission Idle - - 10 Check: Does the IUT (MCVideo Server) forward the Transmission Idle message to SS-UE (MCVideo Client)? (Note) --> Transmission Idle - 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.4.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. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 565 Table A.4.2.5.4-1: Transmission End Request (Steps 1 and 2, Table A.4.2.5.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.4.2.5.4-2: Transmission End Response (Steps 5 and 6, Table A.4.2.5.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 DOWNLINK Table A.4.2.5.4-3: Transmission Idle (Steps 9 and 10, Table A.4.2.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.16-1 Table A.4.2.5.4-4: Transmission Control Ack (Steps 3 and 4, Table A.4.2.5.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.4.2.5.4-5: Transmission Control Ack (Steps 7 and 8, Table A.4.2.5.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.4.2.6 MCVideo CT Transmission End Request - Transmission End Response A.4.2.6.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.2.6.2 Definition of system information messages N/A. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 566 A.4.2.6.3 Procedure Table A.4.2.6.3-1: MCVideo CT Transmission End Request - Transmission End Response St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the controlling function sends a Transmission End Request message, with request for acknowledgement. <-- Transmission End Request - - 2 Check: Does the IUT (MCVideo Server) forward the Transmission End Request message to the SS-UE (MCVideo Client)? (Note) --> Transmission End Request - P 3 The SS-UE (MCVideo Client) acknowledges the Transmission End Request message. (Note) <-- Transmission Control Ack - - 4 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 5 The SS-UE (MCVideo Client) sends a Transmission End Response message with request for acknowledgement to IUT (MCVideo Server). (Note) <-- Transmission End Response - - 6 Check: Does the IUT (MCVideo Server) forward the Transmission End Response message to SS (MCVideo Server)? --> Transmission End Response - P 7 The SS (MCVideo Server) acknowledges the Transmission End Response message. <-- Transmission Control Ack - - 8 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 9 The SS (MCVideo Server) providing the controlling function sends a Transmission Idle message to IUT (MCVideo Server). <-- Transmission Idle - - 10 Check: Does the IUT (MCVideo Server) forward the Transmission Idle message to SS-UE (MCVideo Client)? (Note) --> Transmission Idle - 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.4.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. Table A.4.2.6.4-1: Transmission End Request (Steps 1 and 2, Table A.4.2.6.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 DOWNLINK Table A.4.2.6.4-2: Transmission End Response (Steps 5 and 6, Table A.4.2.6.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.4.2.6.4-3: Transmission Idle (Steps 9 and 10, Table A.4.2.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.16-1 Table A.4.2.6.4-4: Transmission Control Ack (Steps 3 and 4, Table A.4.2.6.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 152-1 V1.1.1 (2026-02) 567 Table A.4.2.6.4-5: Transmission Control Ack (Steps 7 and 8, Table A.4.2.6.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.4.2.7 MCVideo Transmission Request - Transmission Rejected A.4.2.7.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.2.7.2 Definition of system information messages N/A. A.4.2.7.3 Procedure Table A.4.2.7.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 request for acknowledgement. (Note) <-- Transmission Request - - 2 Check: Does the IUT (MCVideo Server) forward the Transmission Request message to the SS (MCVideo Server) providing the controlling function? --> Transmission Request - P 3 The SS (MCVideo Server) acknowledges the Transmission Request message. <-- Transmission Control Ack - - 4 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 5 The SS (MCVideo Server) providing the controlling function sends a Transmission Rejected message with request for acknowledgement to IUT (MCVideo Server). <-- Transmission Rejected - - 6 Check: Does the IUT (MCVideo Server) forward the Transmission Rejected message to SS-UE (MCVideo Client)? (Note) --> Transmission Rejected - P 7 The SS-UE (MCVideo Client) acknowledges the Transmission Rejected message. (Note) <-- Transmission Control Ack - - 8 Check: Does the IUT (MCVideo Server) forward the 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.4.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. Table A.4.2.7.4-1: Transmission Request (Steps 1 and 2, Table A.4.2.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.4.2.7.4-2: Transmission Rejected (Steps 5 and 6, Table A.4.2.7.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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 568 Table A.4.2.7.4-3: Transmission Control Ack (Steps 3 and 4, Table A.4.2.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 Table A.4.2.7.4-4: Transmission Control Ack (Steps 7 and 8, Table A.4.2.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 A.4.2.8 MCVideo Transmission Request - Queue Position Info A.4.2.8.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.2.8.2 Definition of system information messages N/A. A.4.2.8.3 Procedure Table A.4.2.8.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 request for acknowledgement. (Note) <-- Transmission Request - - 2 Check: Does the IUT (MCVideo Server) forward the Transmission Request message to the SS (MCVideo Server) providing the controlling function? --> Transmission Request - P 3 The SS (MCVideo Server) acknowledges the Transmission Request message. <-- Transmission Control Ack - - 4 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 5 The SS (MCVideo Server) providing the controlling function sends a Queue Position Info message with request for acknowledgement to IUT (MCVideo Server). <-- Queue Position Info - - 6 Check: Does the IUT (MCVideo Server) forward the Queue Position Info message to SS-UE (MCVideo Client)? (Note) --> Queue Position Info - P 7 The SS-UE (MCVideo Client) acknowledges the Queue Position Info message. (Note) <-- Transmission Control Ack - - 8 Check: Does the IUT (MCVideo Server) forward the 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.4.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. Table A.4.2.8.4-1: Transmission Request (Steps 1 and 2, Table A.4.2.8.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 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 569 Table A.4.2.8.4-2: Queue Position Info (Steps 5 and 6, Table A.4.2.8.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 Table A.4.2.8.4-3: Transmission Control Ack (Steps 3 and 4, Table A.4.2.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.4.2.8.4-4: Transmission Control Ack (Steps 7 and 8, Table A.4.2.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 A.4.2.9 MCVideo Queue Position Request - Queue Position Info A.4.2.9.1 Initial conditions As specified in the test case which calls the procedure in its entirety or refers to parts of it. A.4.2.9.2 Definition of system information messages N/A. A.4.2.9.3 Procedure Table A.4.2.9.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 Queue Position Request message, with request for acknowledgement. (Note) <-- Queue Position Request - - 2 Check: Does the IUT (MCVideo Server) forward the Queue Position Request message to the SS (MCVideo Server) providing the controlling function? --> Queue Position Request - P 3 The SS (MCVideo Server) acknowledges the Queue Position Request message. <-- Transmission Control Ack - - 4 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 5 The SS (MCVideo Server) providing the controlling function sends a Queue Position Info message with request for acknowledgement to IUT (MCVideo Server). <-- Queue Position Info - - 6 Check: Does the IUT (MCVideo Server) forward the Queue Position Info message to SS-UE (MCVideo Client)? (Note) --> Queue Position Info - P 7 The SS-UE (MCVideo Client) acknowledges the Queue Position Info message. (Note) <-- Transmission Control Ack - - 8 Check: Does the IUT (MCVideo Server) forward the 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.4.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. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 570 Table A.4.2.9.4-1: Queue Position Request (Steps 1 and 2, Table A.4.2.9.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.4.2.9.4-2: Queue Position Info (Steps 5 and 6, Table A.4.2.9.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 Table A.4.2.9.4-3: Transmission Control Ack (Steps 3 and 4, Table A.4.2.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 Table A.4.2.9.4-4: Transmission Control Ack (Steps 7 and 8, Table A.4.2.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 A.4.3 Generic test procedures for MCVideo Terminating Participating Server function A.4.3.1 MCVideo CT session establishment/modification without provisional responses other than 100 Trying A.4.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.4.3.1.2 Definition of system information messages N/A. A.4.3.1.3 Procedure Table A.4.3.1.3-1: MCVideo CT session establishment/modification without provisional responses other than 100 Trying St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the controlling function sends a SIP INVITE requesting the establishment/modification of a call initiated by SS-UE1 (MCVideo Client), to the IUT (MCVideo Server) providing the terminating participating function. <-- SIP INVITE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP INVITE request to establish/modify a call with SS-UE2 (MCVideo Client)? --> SIP INVITE - P 3 The SS-UE2 (MCVideo Client) sends a SIP 100 Trying to the IUT (MCVideo Server). <-- SIP 100 (Trying) - - 4 Check: Does the IUT (MCVideo Server) forward the SIP 100 Trying to the SS (MCVideo Server) providing the controlling function? --> SIP 100 (Trying) - P 5 The SS-UE2 (MCVideo Client) responds with a SIP 200 (OK). <-- SIP 200 (OK) - - 6 Check: Does the IUT (MCVideo Server) forward the SIP 200 (OK) to the SS (MCVideo Server) providing the controlling function? --> SIP 200 (OK) - P ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 571 St Procedure Message Sequence TP Verdict U - S Message 7 The SS (MCVideo Server) providing the controlling function sends a SIP ACK to acknowledge the session establishment/modification to the IUT (MCVideo Server). <-- SIP ACK - - 8 Check: Does the IUT (MCVideo Server) forward the SIP ACK to acknowledge the session establishment/modification to the SS-UE2 (MCVideo Client)? --> SIP ACK - P - EXCEPTION: Step 9a1-9a4 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 (MCVideo Client). - - - - 9a1 The SS (MCVideo Server) providing the controlling function sends a Media Transmission Notification message with request for acknowledgement to the IUT (MCVideo Server), to inform SS-UE2 (MCVideo Client) that the transmission request has been granted to SS-UE1 (MCVideo Client)? <-- Media Transmission Notification - - 9a2 Check: Does the IUT (MCVideo Server) forward the Media Transmission Notification message to SS-UE2 (MCVideo Client)? --> Media Transmission Notification - P 9a3 The SS-UE2 (MCVideo Client) sends a Transmission Control ACK message. <-- Transmission Control Ack - - 9a4 Check: Does the IUT (MCVideo Server) forward the acknowledgement of SS-UE2 (MCVideo Client) to SS (MCVideo Server)? --> Transmission Control Ack - P - EXCEPTION: Steps 10a1-10a2 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 (MCVideo Client). (NOTE 1) - - - - 10a1 The SS (MCVideo Server) providing the controlling function sends a Transmission Idle message to the IUT (MCVideo Server). <-- Transmission Idle - - 10a2 Check: Does the IUT (MCVideo Server) forward the Transmission Idle message to the SS-UE2 (MCVideo Client)? --> Transmission Idle - P A.4.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. Table A.4.3.1.4-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table A.4.3.1.3-1) Derivation Path: Table A.4.1.1.4-4 Table A.4.3.1.4-2: SIP INVITE from IUT (MCVideo Server) (Step 2, Table A.4.3.1.3-1) Derivation Path: Table A.3.1.4-4 Table A.4.3.1.4-3: SIP 200 (OK) from SS-UE2 (MCVideo Client) (Step 5, Table A.4.3.1.3-1) Derivation Path: Table A.3.1.4-7 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 572 Table A.4.3.1.4-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 6, Table A.4.3.1.3-1) Derivation Path: Table A.4.1.1.4-7 Table A.4.3.1.4-5: SIP ACK from SS (MCVideo Server) (Step 7, Table A.4.3.1.3-1) Derivation Path: Table A.4.1.1.4-16 Table A.4.3.1.4-6: SIP ACK from IUT (MCVideo Server) (Step 8, Table A.4.3.1.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.1.2-1. Information Element Value/remark Comment Reference Condition Max-Forwards IETF RFC 3261 [7] value any allowed value Non-zero value NOTE: Elements whose values mention the UE shall be understood as if they were referring to the SS-UE2 (MCVideo Client), and SS as the IUT (MCVideo Server). Table A.4.3.1.4-7: Media Transmission Notification (Steps 9a1 and 9a2, Table A.4.3.1.3-1) Derivation Path: Table A.4.1.1.4-12, with condition ACK Table A.4.3.1.4-8: Transmission Idle (Steps 10a1 and 10a2, Table A.4.3.1.3-1) Derivation Path: Table A.4.1.1.4-13 Table A.4.3.1.4-9: Transmission Control Ack (Steps 9a3 and 9a4, Table A.4.3.1.3-1) Derivation Path: Table A.4.1.1.4-14 A.4.3.2 MCVideo CT private call establishment, manual commencement A.4.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.4.3.2.2 Definition of system information messages N/A. A.4.3.2.3 Procedure Table A.4.3.2.3-1: MCVideo CT private call establishment, manual commencement St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the controlling function sends a SIP INVITE requesting the establishment of a private call from SS-UE1 (MCVideo Client) to SS-UE2 (MCVideo Client). <-- SIP INVITE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP INVITE request to establish a private call with SS-UE2 (MCVideo Client)? --> SIP INVITE - P 3 The SS-UE2 (MCVideo Client) sends a SIP 100 Trying to the IUT (MCVideo Server). <-- SIP 100 (Trying) - - ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 573 St Procedure Message Sequence TP Verdict U - S Message 4 Check: Does the IUT (MCVideo Server) forward the SIP 100 Trying to the SS (MCVideo Server) providing the controlling function? --> SIP 100 (Trying) - P 5 The SS-UE2 (MCVideo Client) sends a SIP 180 Ringing to the IUT (MCVideo Server). <-- SIP 180 (Ringing) - - 6 Check: Does the IUT (MCVideo Server) forward the SIP 180 Ringing to the SS (MCVideo Server) providing the controlling function? --> SIP 180 (Ringing) - P 7 The SS-UE2 (MCVideo Client) responds with a SIP 200 (OK). <-- SIP 200 (OK) - - 8 Check: Does the IUT (MCVideo Server) forward the SIP 200 (OK) to the SS (MCVideo Server) providing the controlling function? --> SIP 200 (OK) - P 9 The SS (MCVideo Server) providing the controlling function sends a SIP ACK to acknowledge the session establishment to the IUT (MCVideo Server). <-- SIP ACK - - 10 Check: Does the IUT (MCVideo Server) forward the SIP ACK to acknowledge the session establishment to the SS-UE2 (MCVideo Client)? --> SIP ACK - P - EXCEPTION: Step 11a1-11a4 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 (MCVideo Client). - - - - 11a1 The SS (MCVideo Server) providing the controlling function sends a Media Transmission Notification message with request for acknowledgement to the IUT (MCVideo Server), to inform SS-UE2 (MCVideo Client) that the transmission request has been granted to SS-UE1 (MCVideo Client)? <-- Media Transmission Notification - - 11a2 Check: Does the IUT (MCVideo Server) forward the Media Transmission Notification message to SS-UE2 (MCVideo Client)? --> Media Transmission Notification - P 11a3 The SS-UE2 (MCVideo Client) sends a Transmission Control ACK message. <-- Transmission Control Ack - - 11a4 Check: Does the IUT (MCVideo Server) forward the acknowledgement of SS-UE2 (MCVideo Client) to SS (MCVideo Server)? --> Transmission Control Ack - P - EXCEPTION: Steps 12a1-12a2 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 (MCVideo Client). (NOTE 1) - - - - 12a1 The SS (MCVideo Server) providing the controlling function sends a Transmission Idle message to the IUT (MCVideo Server). <-- Transmission Idle - - 12a2 Check: Does the IUT (MCVideo Server) forward the Transmission Idle message to the SS-UE2 (MCVideo Client)? --> Transmission Idle - P A.4.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. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 574 Table A.4.3.2.4-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table A.4.3.2.3-1) Derivation Path: Table A.4.3.1.4-1, with conditions PRIVATE-CALL. NOTE: Conditions are also applied to all body parts. Table A.4.3.2.4-2: SIP INVITE from IUT (MCVideo Server) (Step 2, Table A.4.3.2.3-1) Derivation Path: Table A.4.3.1.4-2, with conditions PRIVATE-CALL and MANUAL. NOTE: Conditions are also applied to all body parts. Table A.4.3.2.4-3: SIP 180 (Ringing) from SS-UE2 (MCVideo Client) (Step 5, Table A.4.3.2.3-1) Derivation Path: Table A.3.3.4-8 Table A.4.3.2.4-4: SIP 180 (Ringing) from IUT (MCVideo Server) (Step 6, Table A.4.3.2.3-1) Derivation Path: Table A.4.1.2.4-3 Table A.4.3.2.4-5: SIP 200 (OK) from SS-UE2 (MCVideo Client) (Step 7, Table A.4.3.2.3-1) Derivation Path: Table A.4.3.1.4-3, with condition PRIVATE-CALL. NOTE: Conditions are also applied to all body parts. Table A.4.3.2.4-6: SIP 200 (OK) from IUT (MCVideo Server) (Step 8, Table A.4.3.2.3-1) Derivation Path: Table A.4.3.1.4-4, with condition PRIVATE-CALL. NOTE: Conditions are also applied to all body parts. Table A.4.3.2.4-7: SIP ACK from SS (MCVideo Server) (Step 9, Table A.4.3.2.3-1) Derivation Path: Table A.4.3.1.4-5 Table A.4.3.2.4-8: SIP ACK from IUT (MCVideo Server) (Step 10, Table A.4.3.2.3-1) Derivation Path: Table A.4.3.1.4-6 Table A.4.3.2.4-9: Media Transmission Notification (Steps 11a1 and 11a2, Table A.4.3.2.3-1) Derivation Path: Table A.4.3.1.4-7 Table A.4.3.2.4-10: Transmission Idle (Steps 12a1 and 12a2, Table A.4.3.2.3-1) Derivation Path: Table A.4.3.1.4-8 Table A.4.3.2.4-11: Transmission Control Ack (Steps 11a3 and 11a4, Table A.4.3.2.3-1) Derivation Path: Table A.4.3.1.4-9 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 575 A.4.3.3 MCVideo CT group/private call establishment, automatic commencement A.4.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.4.3.3.2 Definition of system information messages N/A. A.4.3.3.3 Procedure Table A.4.3.3.3-1: MCVideo CT group/private call establishment, automatic commencement St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the controlling function sends a SIP INVITE requesting the establishment of a call from SS- UE1 (MCVideo Client). <-- SIP INVITE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP INVITE request to establish a call with SS-UE2 (MCVideo Client)? --> SIP INVITE - P 3 The SS-UE2 (MCVideo Client) sends a SIP 100 Trying to the IUT (MCVideo Server). <-- SIP 100 (Trying) - - 4 Check: Does the IUT (MCVideo Server) forward the SIP 100 Trying to the SS (MCVideo Server) providing the controlling function? --> SIP 100 (Trying) - P - EXCEPTION: Steps 5a1 to 5b3 describe behaviour that depends on the IUT (MCVideo Server) implementation; the "lower case letter" identifies a step sequence that may take place if the IUT (MCVideo Server) responds reliably or unreliably to a SIP INVITE with a SIP 183 (Session Progress) - - - - 5a1 Check: Does the IUT (MCVideo Server) send a SIP 183 (Session Progress) unreliably to the SS (MCVideo Server) providing the controlling function? --> SIP 183 (Session Progress) - P 5b1 Check: Does the IUT (MCVideo Server) send a SIP 183 (Session Progress) reliably to the SS (MCVideo Server) providing the controlling function? --> SIP 183 (Session Progress) - P 5b2 The SS (MCVideo Server) acknowledges the receipt of SIP 183 (Session Progress). <-- PRACK - - 5b3 Check: Does the IUT (MCVideo Server) respond with SIP 200 (OK) to PRACK message? --> SIP 200 (OK) - P 6 The SS-UE2 (MCVideo Client) responds with a SIP 200 (OK) to SIP INVITE message. <-- SIP 200 (OK) - - 7 Check: Does the IUT (MCVideo Server) forward the SIP 200 (OK) to the SS (MCVideo Server) providing the controlling function? --> SIP 200 (OK) - P 8 The SS (MCVideo Server) providing the controlling function sends a SIP ACK to acknowledge the session establishment to the IUT (MCVideo Server). <-- SIP ACK - - 9 Check: Does the IUT (MCVideo Server) forward the SIP ACK to acknowledge the session establishment to the SS-UE2 (MCVideo Client)? --> SIP ACK - P ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 576 St Procedure Message Sequence TP Verdict U - S Message - EXCEPTION: Step 10a1-10a4 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 (MCVideo Client). - - - - 10a1 The SS (MCVideo Server) providing the controlling function sends a Media Transmission Notification message with request for acknowledgement to the IUT (MCVideo Server), to inform SS-UE2 (MCVideo Client) that the transmission request has been granted to SS-UE1 (MCVideo Client)? <-- Media Transmission Notification - - 10a2 Check: Does the IUT (MCVideo Server) forward the Media Transmission Notification message to SS-UE2 (MCVideo Client)? --> Media Transmission Notification - P 10a3 The SS-UE2 (MCVideo Client) sends a Transmission Control ACK message. <-- Transmission Control Ack - - 10a4 Check: Does the IUT (MCVideo Server) forward the acknowledgement of SS-UE2 (MCVideo Client) to SS (MCVideo Server)? --> Transmission Control Ack - P - EXCEPTION: Steps 11a1-11a2 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 (MCVideo Client). - - - - 11a1 The SS (MCVideo Server) providing the controlling function sends a Transmission Idle message to the IUT (MCVideo Server). <-- Transmission Idle - - 11a2 Check: Does the IUT (MCVideo Server) forward the Transmission Idle message to the SS-UE2 (MCVideo Client)? --> Transmission Idle - P A.4.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. Table A.4.3.3.4-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table A.4.3.3.3-1) Derivation Path: Table A.4.3.1.4-1. Table A.4.3.3.4-2: SIP INVITE from IUT (MCVideo Server) (Step 2, Table A.4.3.3.3-1) Derivation Path: Table A.4.3.1.4-2. Table A.4.3.3.4-3: SIP 183 (Session Progress) from IUT (MCVideo Server) (Step 5a1, Table A.4.3.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.16.3.2-1, with conditions MCVIDEO. Table A.4.3.3.4-4: SIP 183 (Session Progress) from IUT (MCVideo Server) (Step 5b1, Table A.4.3.3.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.16.3.2-1, with conditions MCVIDEO and 100rel ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 577 Table A.4.3.3.4-5: SIP PRACK from SS (MCVideo Server) (Step 5b2, Table A.4.3.3.3-1) Derivation Path: Table A.4.1.4.4-4 Table A.4.3.3.4-6: SIP 200 (OK) to PRACK from IUT (MCVideo Server) (Step 5b3, Table A.4.3.3.3-1) Derivation Path: Table A.4.1.4.4-5. Table A.4.3.3.4-7: SIP 200 (OK) from SS-UE2 (MCVideo Client) (Step 6, Table A.4.3.3.3-1) Derivation Path: Table A.4.3.1.4-3 Table A.4.3.3.4-8: SIP 200 (OK) from IUT (MCVideo Server) (Step 7, Table A.4.3.3.3-1) Derivation Path: Table A.4.3.1.4-4 Table A.4.3.3.4-9: SIP ACK from SS (MCVideo Server) (Step 8, Table A.4.3.3.3-1) Derivation Path: Table A.4.3.1.4-5 Table A.4.3.3.4-10: SIP ACK from IUT (MCVideo Server) (Step 9, Table A.4.3.3.3-1) Derivation Path: Table A.4.3.1.4-6 Table A.4.3.3.4-11: Media Transmission Notification (Steps 10a1 and 10a2, Table A.4.3.3.3-1) Derivation Path: Table A.4.3.1.4-7 Table A.4.3.3.4-12: Transmission Idle (Steps 11a1 and 11a2, Table A.4.3.3.3-1) Derivation Path: Table A.4.3.1.4-8 Table A.4.3.3.4-13: Transmission Control Ack (Steps 10a3 and 10a4, Table A.4.3.3.3-1) Derivation Path: Table A.4.3.1.4-9 A.4.3.4 MCVideo CT group call establishment, manual commencement A.4.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.4.3.4.2 Definition of system information messages N/A. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 578 A.4.3.4.3 Procedure Table A.4.3.4.3-1: MCVideo CT group call establishment, manual commencement St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the controlling function sends a SIP INVITE requesting the establishment of a group call. <-- SIP INVITE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP INVITE request to establish a group call with SS-UE2 (MCVideo Client)? --> SIP INVITE - P 3 The SS-UE2 (MCVideo Client) sends a SIP 100 Trying to the IUT (MCVideo Server). <-- SIP 100 (Trying) - - 4 Check: Does the IUT (MCVideo Server) forward the SIP 100 Trying to the SS (MCVideo Server) providing the controlling function? --> SIP 100 (Trying) - P 5 The SS-UE2 (MCVideo Client) sends a SIP 183 (Session Progress) reliably to the IUT (MCVideo Server). <-- SIP 183 (Session Progress) - - 6 Check: Does the IUT (MCVideo Server) forward the SIP 183 (Session Progress) message to the SS (MCVideo Server) providing the controlling function? --> SIP 183 (Session Progress) - P 7 The SS (MCVideo Server) acknowledges the receipt of SIP 183 (Session Progress). <-- PRACK - - 8 Check: Does the IUT (MCVideo Server) forward the SIP PRACK message to SS-UE2 (MCVideo Client)? --> PRACK - P 9 The SS-UE2 (MCVideo Client) responds with SIP 200 (OK) to PRACK message. <-- SIP 200 (OK) - - 10 Check: Does the IUT (MCVideo Server) forward the SIP 200 (OK) to the SS (MCVideo Server) providing the controlling function? --> SIP 200 (OK) - P 11 The SS-UE2 (MCVideo Client) responds with a SIP 200 (OK) to SIP INVITE message. <-- SIP 200 (OK) - - 12 Check: Does the IUT (MCVideo Server) forward the SIP 200 (OK) to the SS (MCVideo Server) providing the controlling function? --> SIP 200 (OK) - P 13 The SS (MCVideo Server) providing the controlling function sends a SIP ACK to acknowledge the session establishment to the IUT (MCVideo Server). <-- SIP ACK - - 14 Check: Does the IUT (MCVideo Server) forward the SIP ACK to acknowledge the session establishment to the SS-UE2 (MCVideo Client)? --> SIP ACK - P - EXCEPTION: Step 15a1-15a4 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 (MCVideo Client). - - - - 15a1 The SS (MCVideo Server) providing the controlling function sends a Media Transmission Notification message with request for acknowledgement to the IUT (MCVideo Server), to inform SS-UE2 (MCVideo Client) that the transmission request has been granted to SS-UE1 (MCVideo Client)? <-- Media Transmission Notification - - 15a2 Check: Does the IUT (MCVideo Server) forward the Media Transmission Notification message to SS-UE2 (MCVideo Client)? --> Media Transmission Notification - P 15a3 The SS-UE2 (MCVideo Client) sends a Transmission Control ACK message. <-- Transmission Control Ack - - 15a4 Check: Does the IUT (MCVideo Server) forward the acknowledgement of SS-UE2 (MCVideo Client) to SS (MCVideo Server)? --> Transmission Control Ack - P ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 579 St Procedure Message Sequence TP Verdict U - S Message - EXCEPTION: Steps 16a1-16a2 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 (MCVideo Client). - - - - 16a1 The SS (MCVideo Server) providing the controlling function sends a Transmission Idle message to the IUT (MCVideo Server). <-- Transmission Idle - - 16a2 Check: Does the IUT (MCVideo Server) forward the Transmission Idle message to the SS-UE2 (MCVideo Client)? --> Transmission Idle - P A.4.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. Table A.4.3.4.4-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table A.4.3.4.3-1) Derivation Path: Table A.4.3.1.4-1, with conditions GROUP-CALL. NOTE 1: Conditions are also applied to all body parts. NOTE 2: For chat group calls CHAT-GROUP-CALL condition shall be used instead of GROUP-CALL. Table A.4.3.4.4-2: SIP INVITE from IUT (MCVideo Server) (Step 2, Table A.4.3.4.3-1) Derivation Path: Table A.4.3.1.4-2, with conditions GROUP -CALL and MANUAL. NOTE 1: Conditions are also applied to all body parts. NOTE 2: For chat group calls CHAT-GROUP-CALL condition shall be used instead of GROUP-CALL. Table A.4.3.4.4-3: SIP 183 (Session Progress) from SS-UE2 (MCVideo Client) (Step 5, Table A.4.3.4.3-1) Derivation Path: Table A.3.2.4-7. Table A.4.3.4.4-4: SIP 183 (Session Progress) from IUT (MCVideo Server) (Step 6, Table A.4.3.4.3-1) Derivation Path: Table A.4.1.4.4-3 Table A.4.3.4.4-5: SIP PRACK from SS (MCVideo Server) (Step 7, Table A.4.3.4.3-1) Derivation Path: Table A.4.1.4.4-4 Table A.4.3.4.4-6: SIP PRACK from IUT (MCVideo Server) (Step 8, Table A.4.3.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.10.2-1. Information Element Value/remark Comment Reference Condition Max-Forwards IETF RFC 3261 [7] Value any allowed value Non-zero value NOTE: Elements whose values mention the UE shall be understood as if they were referring to the SS-UE2 (MCVideo Client), and SS as IUT (MCVideo Server). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 580 Table A.4.3.4.4-7: SIP 200 (OK) to PRACK from SS-UE2 (MCVideo Client) (Step 9, Table A.4.3.4.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1 Table A.4.3.4.4-8: SIP 200 (OK) to PRACK from IUT (MCVideo Server) (Step 10, Table A.4.3.4.3-1) Derivation Path: Table A.4.1.4.4-5. Table A.4.3.4.4-9: SIP 200 (OK) from SS-UE2 (MCVideo Client) (Step 11, Table A.4.3.4.3-1) Derivation Path: Table A.4.3.1.4-3, with condition GROUP -CALL. NOTE: Conditions are also applied to all body parts. Table A.4.3.4.4-10: SIP 200 (OK) from IUT (MCVideo Server) (Step 12, Table A.4.3.4.3-1) Derivation Path: Table A.4.3.1.4-4, with condition GROUP -CALL. NOTE: Conditions are also applied to all body parts. Table A.4.3.4.4-11: SIP ACK from SS (MCVideo Server) (Step 13, Table A.4.3.4.3-1) Derivation Path: Table A.4.3.1.4-5 Table A.4.3.4.4-12: SIP ACK from IUT (MCVideo Server) (Step 14, Table A.4.3.4.3-1) Derivation Path: Table A.4.3.1.4-6 Table A.4.3.4.4-13: Media Transmission Notification (Steps 15a1 and 15a2, Table A.4.3.4.3-1) Derivation Path: Table A.4.3.1.4-7 Table A.4.3.4.4-14: Transmission Idle (Steps 16a1 and 16a2, Table A.4.3.4.3-1) Derivation Path: Table A.4.3.1.4-8 Table A.4.3.4.4-15: Transmission Control Ack (Steps 15a3 and 15a4, Table A.4.3.4.3-1) Derivation Path: Table A.4.3.1.4-9 A.4.3.5 MCVideo CT call release A.4.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.4.3.5.2 Definition of system information messages N/A. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 581 A.4.3.5.3 Procedure Table A.4.3.5.3-1: MCVideo CO call release St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the controlling function sends a SIP BYE to terminate the call. <-- SIP BYE - - 2 Check: Does the IUT (MCVideo Server) forward the SIP BYE request to the SS-UE2 (MCVideo Client)? --> SIP BYE - P 3 The SS-UE2 (MCVideo Client) responds with a 200 (OK) to the IUT (MCVideo Server). <-- SIP 200 (OK) - - 4 Check: Does the IUT (MCVideo Server) forward the SIP 200 (OK) response to the SS (MCVideo Server) providing the controlling function? --> SIP 200 (OK) - P A.4.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 with condition MCVIDEO and in the test case calling the procedure with the following clarifications. Table A.4.3.5.4-1: SIP BYE from the SS (MCVideo Server) (Step 1, Table A.4.3.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.2.2-1. NOTE: References to UE in subclauses relate to the SS (MCVideo Server) providing the controlling function and SS references to the IUT (MCVideo Server). Table A.4.3.5.4-2: SIP BYE from the IUT (MCVideo Server) (Step 2, Table A.4.3.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.2.2-1 NOTE: References to UE in subclauses relate to the SS-UE2 (MCVideo Client) and SS references to the IUT (MCVideo Server). Table A.4.3.5.4-3: SIP 200 OK from the SS-UE2 (MCVideo Client) (Step 3, Table A.4.3.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.1-1. Table A.4.3.5.4-4: SIP 200 OK from the IUT (MCVideo Server) (Step 4, Table A.4.3.5.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.2.17.1.2-1. A.4.3.6 MCVideo Media Transmission Notification - Receive Media Request A.4.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.4.3.6.2 Definition of system information messages N/A. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 582 A.4.3.6.3 Procedure Table A.4.3.6.3-1: MCVideo Media Transmission Notification - Receive Media Request St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the controlling function sends a Media Transmission Notification message with request for acknowledgement to IUT (MCVideo Server). <-- Media Transmission Notification - - 2 Check: Does the IUT (MCVideo Server) forward the Media Transmission Notification message to SS-UE (MCVideo Client)? (Note) --> Media Transmission Notification - P 3 The SS-UE (MCVideo Client) acknowledges the Media Transmission Notification message. (Note) <-- Transmission Control Ack - - 4 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 5 The SS-UE (MCVideo Client) sends a Receive Media Request message, with request for acknowledgement. (Note) <-- Receive Media Request - - 6 Check: Does the IUT (MCVideo Server) forward the Receive Media Request message to the SS (MCVideo Server) providing the controlling function? --> Receive Media Request - P 7 The SS (MCVideo Server) acknowledges the Receive Media Request message. <-- Transmission Control Ack - - 8 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 9 The SS (MCVideo Server) providing the controlling function sends a Receive Media Response message with request for acknowledgement to IUT (MCVideo Server). <-- Receive Media Response - - 10 Check: Does the IUT (MCVideo Server) forward the Receive Media Response message to SS- UE (MCVideo Client)? (Note) --> Receive Media Response - P 11 The SS-UE (MCVideo Client) acknowledges the Receive Media Response message. (Note) <-- Transmission Control Ack - - 12 Check: Does the IUT (MCVideo Server) forward the 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-UE2 (MCVideo Client) will be assumed. A.4.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. Table A.4.3.6.4-1: Media Transmission Notification (Steps 1 and 2, Table A.4.3.6.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 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 [6] (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 [6] (3GPP TS 24.581) clause 9.2.3.16 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 583 Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.7-1, with condition ACK Information Element Value/remark Comment Reference Condition Functional Alias Not present px_MCVideo_ID_FA_A functional alias URI of the transmitting user ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.21 FA Table A.4.3.6.4-2: Receive Media Request (Steps 5 and 6, Table A.4.3.6.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.4.3.6.4-3: Receive Media Response (Steps 9 and 10, Table A.4.3.6.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.8-1, with condition ACK Table A.4.3.6.4-4: Transmission Control Ack (Steps 7 and 8, Table A.4.3.6.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.4.3.6.4-5: Transmission Control Ack (Steps 3, 4, 11 and 12, Table A.4.3.6.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.4.3.7 MCVideo Media Reception End Request - Response A.4.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.4.3.7.2 Definition of system information messages N/A. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 584 A.4.3.7.3 Procedure Table A.4.3.7.3-1: MCVideo Media Reception End Request - Response St Procedure Message Sequence TP Verdict U - S Message 1 The SS-UE (MCVideo Client) sends a Media Reception End Request message, with request for acknowledgement. (Note) <-- Media Reception End Request - - 2 Check: Does the IUT (MCVideo Server) forward the Media Reception End Request message to the SS (MCVideo Server) providing the controlling function? --> Media Reception End Request - P 3 The SS (MCVideo Server) acknowledges the Media Reception End Request message. <-- Transmission Control Ack - - 4 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 5 The SS (MCVideo Server) providing the controlling function sends a Media Reception End Response message with request for acknowledgement to IUT (MCVideo Server). <-- Media Reception End Response - - 6 Check: Does the IUT (MCVideo Server) forward the Media Reception End Response message to SS-UE (MCVideo Client)? (Note) --> Media Reception End Response - P 7 The SS-UE (MCVideo Client) acknowledges the Media Reception End Response message. (Note) <-- Transmission Control Ack - - 8 Check: Does the IUT (MCVideo Server) forward the 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-UE2 (MCVideo Client) will be assumed. A.4.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. Table A.4.3.7.4-1: Media Reception End Request (Steps 1 and 2, Table A.4.3.7.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.4.3.7.4-2: Media Reception End Response (Steps 5 and 6, Table A.4.3.7.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 DOWNLINK Table A.4.3.7.4-3: Transmission Control Ack (Steps 3 and 4, Table A.4.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 Table A.4.3.7.4-4: Transmission Control Ack (Steps 7 and 8, Table A.4.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 A.4.3.8 MCVideo Transmission End Notification - Idle A.4.3.8.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 152-1 V1.1.1 (2026-02) 585 A.4.3.8.2 Definition of system information messages N/A. A.4.3.8.3 Procedure Table A.4.3.8.3-1: MCVideo Transmission End Notification - Idle St Procedure Message Sequence TP Verdict U - S Message 1 The SS (MCVideo Server) providing the controlling function sends a Transmission End Notify message with request for acknowledgement to IUT (MCVideo Server). <-- Transmission End Notify - - 2 Check: Does the IUT (MCVideo Server) forward the Transmission End Notify message to SS-UE (MCVideo Client)? (Note) --> Transmission End Notify - P 3 The SS-UE (MCVideo Client) acknowledges the Transmission End Notify message. (Note) <-- Transmission Control Ack - - 4 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P - EXCEPTION: Steps 5-12 describe behaviour that depends on the test case calling this procedure; it identifies a step sequence that takes place if SS-UE2 has previously requested media reception by performing procedure 'MCVideo Media Transmission Notification - Receive Media Request', as described in Table A.4.3.6.3-1. - - - - 5 The SS (MCVideo Server) providing the controlling function sends a Media Reception End Request message with request for acknowledgement to IUT (MCVideo Server). <-- Media Reception End Request - - 6 Check: Does the IUT (MCVideo Server) forward the Media Reception End Request message to SS-UE (MCVideo Client)? (Note) --> Media Reception End Request - P 7 The SS-UE (MCVideo Client) acknowledges the Media Reception End Request message. (Note) <-- Transmission Control Ack - - 8 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 9 The SS-UE (MCVideo Client) sends a Media Reception End Response message, with request for acknowledgement. (Note) <-- Media Reception End Response - - 10 Check: Does the IUT (MCVideo Server) forward the Media Reception End Response message to the SS (MCVideo Server) providing the controlling function? --> Media Reception End Response - P 11 The SS (MCVideo Server) acknowledges the Media Reception End Response message. <-- Transmission Control Ack - - 12 Check: Does the IUT (MCVideo Server) forward the Transmission Control Ack message? --> Transmission Control Ack - P 13 The SS (MCVideo Server) providing the controlling function sends a Transmission Idle message to IUT (MCVideo Server). <-- Transmission Idle - - 14 Check: Does the IUT (MCVideo Server) forward the Transmission Idle message to SS-UE (MCVideo Client)? (Note) --> Transmission Idle - P NOTE: The SS-UE being used is specified in the test case calling the procedure. If not stated, SS-UE2 (MCVideo Client) will be assumed. A.4.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. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 586 Table A.4.3.8.4-1: Transmission End Notify (Steps 1 and 2, Table A.4.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 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 [6] (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 [6] (3GPP TS 24.581) clause 9.2.3.16 Table A.4.3.8.4-2: Media Reception End Request (Steps 5 and 6, Table A.4.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 conditions ACK and DOWNLINK Table A.4.3.8.4-3: Media Reception End Response (Steps 9 and 10, Table A.4.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.4.3.8.4-4: Transmission Control Ack (Steps 11 and 12, Table A.4.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.4.3.8.4-5: Transmission Control Ack (Steps 3, 4, 7 and 8, Table A.4.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.4.3.8.4-6: Transmission Idle (Steps 13 and 14, Table A.4.3.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.16-1 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 587 History Version Date Status V1.1.1 February 2026 Publication |
e341f05abb94e155b675f29c6779693c | 104 230 | 1 Scope | The present document specifies the Use cases and Requirements for R1 interface. |
e341f05abb94e155b675f29c6779693c | 104 230 | 2 References | |
e341f05abb94e155b675f29c6779693c | 104 230 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 104 228: "Publicly Available Specification (PAS); O-RAN R1 interface General Aspects and Principles (O-RAN.WG2.TS.R1GAP-R004-v11.00)". [2] O-RAN.WG2.TS.Use-Case-Requirements-R004: "Non-RT RIC & A1/R1 Interface: Use Cases and Requirements" ("UCR"). [3] ETSI TS 103 988: "Publicly Available Specification (PAS); A1 interface: Type Definitions (O-RAN.WG2.A1TD-R004-v09.00)". [4] ETSI TS 104 104: "Publicly Available Specification (PAS); O-RAN Security Requirements and Controls Specifications (O-RAN.WG11.SecReqSpecs-R003-v09.01)". [5] ETSI TS 103 987: "Publicly Available Specification (PAS); A1 interface: Application Protocol (O-RAN.WG2.A1AP-R004-v04.03)". [6] ETSI TS 103 985: "Publicly Available Specification (PAS); A1 interface: Use Cases and Requirements (O-RAN.WG2.A1UCR-R004-v01.04)". [7] Recommendation ITU-T M.3020: "Management interface specification methodology". |
e341f05abb94e155b675f29c6779693c | 104 230 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. Not applicable. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 11 3 Definition of terms, symbols, abbreviations and conventions |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.1 Terms | For the purposes of the present document, the following terms apply: DME type: data type managed and exposed by the DME services and identified by a data type identifier O-RAN Non-Real-Time RAN Intelligent Controller (Non-RT RIC): logical function in the SMO framework that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model training and updates, and policy-based guidance of applications/features in Near-RT RIC NOTE: The Non-RT RIC is comprised of the Non-RT RIC framework and Non-RT RIC applications (rApps). Non-RT RIC application (rApp): application designed to consume and/or produce R1 Services NOTE: rApps can leverage the functionality provided by the SMO/Non-RT RIC framework to deliver value added services related to intelligent RAN optimization and operation. Non-RT RIC framework: functionality internal to the SMO framework that logically terminates the A1 interface and provides the R1 services to rApps through the R1 interface |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.2 Symbols | Void. |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface AuthN Authentication AuthZ Authorization DME Data Management and Exposure FM Fault Management FWK Framework ID Identifier Non-RT RIC Non-Real Time RAN Intelligent Controller PM Performance Management SME Service Management and Exposure SMO Service Management and Orchestration |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.4 Conventions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.4.1 General | For the purposes of the present document, the conventions in the following clauses apply. |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.4.2 Requirements | The requirements and solutions for use cases are based on the methodology specified in Recommendation ITU-T M.3020 [7], clause A.1.2. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 12 |
e341f05abb94e155b675f29c6779693c | 104 230 | 4 General | The R1 interface is defined between the rApps and the Non-RT RIC framework, as defined in R1GAP [1]. In the use case sequence flows, solid lines are used for the message interactions which are defined in O-RAN specifications. Dashed lines are used to represent the messages interactions that are not specified in O-RAN specifications or can be implementation specific interactions. |
e341f05abb94e155b675f29c6779693c | 104 230 | 5 Requirements | |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.1 General | The general R1 interface requirements are specified in UCR [2]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.2 Security | The security requirements applicable to the R1 interface are specified in SRS [4], clause 5.2.6. |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.3 SME services functional requirements | This clause specifies the SME services functional requirements. The functional requirements are specified in table 5.3-1. Table 5.3-1: SME services functional requirements REQ Description Note REQ-R1-SME-rAppreg-FUN1 The SME services shall support registration of an rApp. REQ-R1-SME-rAppreg-FUN2 The SME services shall support authentication of an rApp. REQ-R1-SME-Servicemag-FUN1 The SME services shall support registration of a service. REQ-R1-SME-Servicemag-FUN2 The SME services shall support update of a service registration. REQ-R1-SME-Servicemag-FUN3 The SME services shall support deregistration of a registered service. REQ-R1-SME-Service discovery- FUN1 The SME services shall support discovery of services. REQ-R1-SME-Servicesub-FUN1 The SME services shall support subscription to notifications of service availability changes. REQ-R1-SME-Servicesub-FUN2 The SME services shall support sending notifications for the service availability changes. REQ-R1-SME-Servicesub-FUN3 The SME services shall support unsubscription to notifications of service availability changes. |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.4 DME services functional requirements | This cause specifies the DME services functional requirements. The functional requirements are specified in table 5.4-1. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 13 Table 5.4-1: DME services functional requirements REQ Description Note REQ-R1-DME-Regdatatype-FUN1 The DME services shall support registration, query, update and deregistration of a DME type. REQ-R1-DME-Discoverydatatype- FUN1 The DME services shall support querying available DME types. REQ-R1-DME- Subscribedatatypechanges-FUN1 The DME services shall support subscription to notifications regarding changes in the availability of DME types. REQ-R1-DME- Notifydatatypechanges-FUN1 The DME services shall support sending notifications about changes in the availability of DME types. REQ-R1-DME- Unsubscribedatatypechanges-FUN1 The DME services shall support to unsubscribe from notifications regarding changes in the availability of DME types. REQ-R1-DME-Dataoffer-FUN1 The DME services shall support the creation of data offers. REQ-R1-DME-Dataoffer-FUN2 The DME services shall support the termination of data offers. REQ-R1-DME-Data subscription- FUN1 The DME services shall support the creation of data subscriptions. REQ-R1-DME-Data subscription- FUN2 The DME services shall support the termination of data subscriptions. REQ-R1-DME-Data subscription- FUN3 The DME services shall support the update of data subscriptions. REQ-R1-DME-Data subscription- FUN4 The DME services shall support the query of data subscriptions. REQ-R1-DME-Data request-FUN1 The DME services shall support the creation of data requests. REQ-R1-DME-Data request-FUN2 The DME services shall support the cancellation of data requests. REQ-R1-DME-Data delivery-FUN1 The DME services shall support the delivery of subscribed or requested data. REQ-R1-DME-Data subscription- FUN1 The DME services shall support the query the status of data subscriptions. |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.5 RAN OAM-related services functional requirements | This clause specifies the FM, CM and PM services functional requirements. The functional requirements are specified in table 5.5-1. Table 5.5-1: FM, CM and PM services functional requirements REQ Description Note REQ-R1-OAM- FMservice-FUN1 The FM service shall support querying alarm information related to the O-RAN managed entities. REQ-R1-OAM- Fmservice-FUN2 The FM service shall support changing the acknowledgement state of alarms related to the O-RAN managed entities. REQ-R1-OAM- Pmservice-FUN1 The PM service shall support querying performance information related to the O-RAN managed entities. REQ-R1-OAM- Cmservice-FUN1 The CM service should support retrieving configuration schema related to the O-RAN managed entities. REQ-R1-OAM- Cmservice-FUN2 The CM service shall support retrieving configuration data related to O-RAN managed entities. REQ-R1-OAM- Cmservice-FUN3 The CM service shall support to write configuration changes to O-RAN managed entities. NOTE: The querying of performance information, and how this relates to the Data management and exposure services, is not defined in the present document. |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.6 AI/ML workflow services functional requirements | This clause specifies the AI/ML workflow services functional requirements. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 14 The functional requirements are specified in table 5.6-1. Table 5.6-1: AI/ML workflow services functional requirements REQ Description Note REQ-R1-AIML-Deploymodel-FUN1 The AI/ML workflow services shall support the request of deployment of an AI/ML model. REQ-R1-AIML-Retrievemodel-FUN1 The AI/ML workflow services shall support retrieving the location details of a registered AI/ML model. REQ-R1-AI/ML-training-FUN1 The AI/ML workflow services shall support training of AI/ML models. REQ-R1-AI/ML-training-FUN2 The AI/ML workflow services shall support query of AI/ML training job status. REQ-R1-AI/ML-training-FUN3 The AI/ML workflow services shall support notification for AI/ML training job status changes. REQ-R1-AI/ML-Discovery-FUN1 The AI/ML workflow services shall support discovery of registered AI/ML models. REQ-R1-AIML-Registermodel-FUN1 The AI/ML workflow services shall support registration and deregistration of an AI/ML model, and query and update of a model registration. REQ-R1-AIML-Performance-FUN1 The AI/ML workflow services shall support subscription to AI/ML model performance information. REQ-R1-AIML-Performance-FUN2 The AI/ML workflow services shall support notification of AI/ML model performance information. REQ-R1-AIML-inference-FUN1 The AI/ML workflow services shall support request and cancel for the inference of an AI/ML model. REQ-R1-AIML-inference-FUN2 The AI/ML workflow services shall support query of the inference capability information for a registered AI/ML model. REQ-R1-AI/ML-Registertraincap- FUN1 The AI/ML workflow services should support registration, deregistration, update and query of an AI/ML model trainer's training capability. |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.7 A1-related services functional requirements | This clause specifies the A1 policy management services and A1 enrichment information related services functional requirements. The functional requirements are specified in table 5.7-1. Table 5.7-1: A1 policy management services functional requirements REQ Description Note REQ-R1-A1P-FUN1 The A1 policy management service shall support querying an A1 policy type. REQ-R1-A1P-FUN2 The A1 policy management service shall support querying A1 policy identifiers. REQ-R1-A1P-FUN3 The A1 policy management service shall support querying A1 policy type identifiers. REQ-R1-A1P-FUN4 The A1 policy management service shall support querying an A1 policy. REQ-R1-A1P-FUN5 The A1 policy management service shall support querying the status of an A1 policy. REQ-R1-A1P-FUN6 The A1 policy management service shall support subscription to notifications regarding status changes of an A1 policy. REQ-R1-A1P-FUN7 The A1 policy management services shall support sending notifications regarding status changes of an A1 policy. REQ-R1-A1P-FUN8 The A1 policy management service shall support unsubscription from notifications regarding status changes of an A1 policy. REQ-R1-A1P-FUN9 The A1 policy management service shall support creating, querying, updating, and deleting an A1 policy. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 15 |
e341f05abb94e155b675f29c6779693c | 104 230 | 6 Use cases for Service Management and Exposure | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1 SME use case 1: Registration and Bootstrap | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.1 Overview | This use case provides the description and requirements for registering an rApp with the SMO/Non-RT RIC framework. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.2 Background and goal of the use case | The rApp registration procedure registers the rApp to the SMO/Non-RT RIC framework. It may use the bootstrap service to discover the rApp registration API. To register an rApp, an rApp may pass relevant info that may include the rApp name, vendor, software version, and other information needed by the SMO/Non-RT RIC framework. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.3 Entities/resources involved in the use case | 1) SME functions in the role of SME services Producer: a) support functionality that allows the rApp to retrieve the bootstrap information that enables it to discover the SME services; b) support functionality to authenticate the rApp; c) assign the rApp with an ID. 2) rApp: a) retrieves the bootstrap information that enables it to discover the SME services; b) initiates the procedure of rApp registration. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 16 |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.4.1 rApp registration and bootstrap | Table 6.1.4.1-1: rApp registration and bootstrap use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal 1) Find the SME service endpoints (Optional). 2) Register the rApp to the SME services Producer in SMO/Non-RT RIC framework. Actors and Roles - rApp in the role of Service Producer and/or Service Consumer. - SME functions in the role of SME services Producer. Assumptions n/a Preconditions The rApp is instantiated. Begins when The rApp is ready for registration. Step 1 (O) The rApp will initiate a bootstrap request to find the SME endpoints. Step 2 (O) The SME functions respond with the details of the service endpoints. Step 3 (M) The rApp sends a registration request to the SME functions in the SMO/Non-RT RIC framework passing relevant information needed. Step 4 (M) The SME functions process the rApp registration request that may include. - performing authentication; - if rApp is authenticated, rAppId will be assigned to rApp. Step 5 (M) Response to the registration request along with the rAppId. Ends when The rApp is allocated with an rAppId. Exceptions n/a Post Conditions The rApp is registered with the SMO/Non-RT RIC framework and an rAppId is allocated to the rApp. Traceability REQ-R1-SME-rAppreg-FUN1, REQ-R1-SME-rAppreg-FUN2. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue participant "SME functions" as SEF endbox ==bootstrap == opt rApp -> SEF :<<R1>>Bootstrap request activate SEF SEF -> rApp :<<R1>>Bootstrap response Deactivate SEF end ==rApp registration == rApp -> SEF:<<R1>>Registration request activate SEF SEFà SEF : AuthN note right registration processing assign rAppId end note SEF -> rApp :<<R1>>Registration response (rAppId) Deactivate SEF @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 17 Figure 6.1.4.1-1: rApp registration and bootstrap use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.5 Required data | For registering, an rApp needs to provide the security credentials along with e.g. rApp name, vendor, software version, certificates etc. and the role an rApp is trying to register (Service Producer and/or Service Consumer). The response to the rApp registration includes the status of registration i.e. success or failure. For successful rApp registration, the response will also include the rAppId. For unsuccessful rApp registration, the response will also include the error code along with relevant information. The rApp may obtain information about the SME services endpoints from the producer of bootstrap service. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2 SME Use case 2: Manage Service Registration | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.1 Overview | This use case allows an rApp as Service Producer to register each of its produced services, update the service information of each of its registered services and deregister each of its registered service as specified in R1GAP [1]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.2 Background and goal of the use case | An rApp as a Service Producer can register each of the new services its produces. Other rApps that are Service Consumers can discover the registered services. After an rApp as a Service Producer has successfully registered the each of the services it produces, it can update and/or deregister each of the registered services. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 18 |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.3 Entities/resources involved in the use case | 1) SME functions in the role of SME services Producer: a) support functionality to register a service produced by an rApp; b) support authorization of an rApp to determine whether an rApp can register a service, update a registered service, and deregister a registered service; c) support validation of the new service produced by an rApp that includes determining whether there are conflicts with services registered earlier; d) provide the response of success or failure result to Register service request, Update service registration request and Deregister service request. 2) rApp: a) supports to initiate the procedure to register a service it produces, update a registered service, and deregister a registered service. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.4.1 Register Service | Table 6.2.4.1-1: Register service use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp successfully registers a service. Actors and Roles - rApp in the role of Service Producer that requests service registration. - SME functions in the role of SME services Producer that handles the service registration. Assumptions n/a Preconditions The rApp is deployed and authorized to register a service, and optionally has the bootstrap info. Begins when The rApp determines the need to register a service. Step 1 (M) The rApp requests the SME functions to register a service by providing the rAppId and service profile. Step 2 (M) The SME functions check whether the rApp is authorized to register a service. Step 3 (M) The SME functions validate the information about the new service produced by the rApp, that includes determining whether there are conflicts with services registered earlier. Step 4 (M) The SME functions register the service and make the service endpoint available for discovery. Step 5 (M) The SME functions respond to the rApp with a success result along with a service identifier. Ends when The rApp was able to register a service. Exceptions n/a Post Conditions The rApp will be able to update and de-register the registered service. Traceability REQ-R1-SME-Servicemag-FUN1. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "SME functions" as SME ETSI ETSI TS 104 230 V10.0.0 (2026-02) 19 endbox rApp->SME:<<R1>>Register service request (rAppId,service profile) activate SME SME --> SME : AuthZ note right check authorization to register a service end note SME --> SME : Validate SME --> SME : register service SME ->rApp:<<R1>>Register service response (service identifier) deactivate SME @enduml Figure 6.2.4.1-1: Register service use case flow diagram ETSI ETSI TS 104 230 V10.0.0 (2026-02) 20 |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.4.2 Update service registration | Table 6.2.4.2-1: Update service registration use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp successfully updates a service registration. Actors and Roles - rApp in the role of Service Producer that requests updating the registered information of a service. - SME functions in the role of SME services Producer in SMO/Non-RT RIC framework that handles the update to registered service. Assumptions n/a Preconditions The rApp is authorized to update service. The rApp has registered a service. Begins when The rApp determines the need to update the registered information of a service. Step 1 (M) The rApp requests the SME functions to update the service information of registered service by providing rAppId, service identifier and delta service profile. Step 2 (M) The SME functions check whether the rApp is authorized to update a registered service. Step 3 (M) The SME functions update the service information and make the updated service endpoint available for discovery. Step 4 (M) The SME functions respond to rApp with successful result. Ends when The rApp was able to update service registration. Exceptions n/a Post Conditions The rApp will be able to update and de-register the registered service. Traceability REQ-R1-SME-Servicemag-FUN2. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant "rApp" as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "SME functions" as SME endbox rApp -> SME : <<R1>>Update service registration request (rAppId,service identifier, service profile) activate SME SME --> SME : AuthZ note right check authorization to update a registered service end note SME --> SME : service update SME -> rApp :<<R1>>Update service registration response deactivate SME @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 21 Figure 6.2.4.2-1: Update service registration use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.4.3 Deregister Service | Table 6.2.4.3-1: Deregister service use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp successfully deregister a service. Actors and Roles - rApp in the role of Service Producer that requests service deregistration. - SME functions in the role of SME services Producer that handles the service deregistration. Assumptions n/a Preconditions The rApp is authorized to deregister a service. The rApp has previously registered the service that is requested to be deregistered. Begins when The rApp determines the need to deregister a registered service. Step 1 (M) The rApp requests the SME functions to deregister a service by providing the rAppId and service identifier. Step 2 (M) The SME functions check if rApp is authorized to deregister a service. Step 3 (M) The SME functions remove the registered service and remove the service endpoint from the set of endpoints that can be discovered. Step 4 (M) The SME functions respond to rApp with a successful result. Ends when The rApp was able to deregister a service. Exceptions n/a Post Conditions The rApp has deregistered a registered service; service endpoint will be no longer available for service discovery. Traceability REQ-R1-SME-Servicemag-FUN3. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant "rApp" as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "SME functions" as SME endbox rApp -> SME : <<R1>>Deregister service request (rAppId,service identifier) activate SME SME --> SME : AuthZ note right check authorization to deregister a registered service end note ETSI ETSI TS 104 230 V10.0.0 (2026-02) 22 SME --> SME : Remove service profile SME -> rApp :<<R1>>Deregister service response deactivate SME @enduml Figure 6.2.4.3-1: Deregister service use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.5 Required data | The service profile information includes e.g. the name of the service, service type, communication mechanism, interface endpoint details (such as IP address, port number, URI, protocol), version number, and data format. For registering a service, the rApp needs to provide the rAppId and the service profile. On successful registration, the SME services Producer assigns a service identifier for the newly registered service and returns it to the rApp. For updating a registered service, the rApp needs to provide the rAppId, the service identifier and the delta information that needs to be changed in the service profile. For de-registering a registered service, the rApp needs to provide the rAppId and the service identifier. NOTE: It is up to the design of the authorization mechanism whether the rAppId will be passed as a separate piece of information or will be embedded in or implied by the authorization information. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3 SME use case 3: Discovery of services | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.1 Overview | This use case allows an rApp as a Service Consumer to discover the available services. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.2 Background and goal of the use case | The discovery of services is specified as part of Service management and exposure services in R1GAP [1]. An rApp in the role of Service Consumer will be able to discover the available services. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.3 Entities/resources involved in the use case | 1) SME functions in the role of SME services Producer: a) support functionality to discover the available services; b) support authorization of an rApp to determine which services an rApp can discover; ETSI ETSI TS 104 230 V10.0.0 (2026-02) 23 c) retrieve the stored service information and performs filtering of available services based on selection criteria that may be provided by the rApp; d) provide response of success or failure to Discover service request. 2) rApp: a) supports initiating the procedure to discover available services, optionally providing selection criteria. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.4.1 Discover the services | Table 6.3.4.1-1: Discover service use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp discovers the available services. Actors and Roles - rApp in the role of Service Consumer that requests to discover the available services. - SME functions in the role of SME services Producer that handles the discovery of available services. Assumptions n/a Preconditions The rApp is authorized to discover services. Begins when The rApp determines the need to discover the available services. Step 1 (M) The rApp requests the SME functions to discover available services based on the rAppId and optional selection criteria. Step 2 (M) The SME functions check which services the rApp is authorized to discover. Step 3 (M) The SME functions respond with the set of available services and their service identifiers. The list contains only those available services that match the selection criteria if those were provided by the rApp, or all available services otherwise. Ends when The rApp was able to discover the available services. Exceptions n/a Post Conditions The rApp can request access to the available services. Traceability REQ-R1-SME-Service Discovery-FUN1. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant " SME functions" as SME endbox rApp -> SME : <<R1>>Discover service request(rAppId) activate SME SME --> SME: AuthZ note right check authorization to discover available services end note SME -> rApp :<<R1>> Discover service response(list of services) deactivate SME @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 24 Figure 6.3.4.1-1: Discover service use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.5 Required data | For discovering a service, the rApp needs to provide the rAppId and optional selection criteria such as e.g. name of the service, service type, and capabilities. The SME functions respond with information about a set of services which includes e.g. endpoint information and service identifiers. NOTE: Whether an rApp may be allowed to discover services for which it is currently not authorized but might be able to obtain authorization later is not defined in the present document. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4 SME use case 4: Subscribe service availability | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.1 Overview | This use case allows an rApp as Service Consumer to subscribe to notifications and unsubscribe from notifications regarding changes in service availability, to receive notifications about subscribed events and to update its subscriptions. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.2 Background and goal of the use case | The subscribe service availability, notify service availability changes, unsubscribe service availability and update service availability subscriptions procedures are defined as part of Service management and exposure services in R1GAP [1]. The rApp in the role of Service Consumer can subscribe to notifications and unsubscribe from notifications regarding changes in the availability of services. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.3 Entities/resources involved in the use case | 1) SME functions in the role of SME services Producer: a) support functionality to subscribe to and unsubscribe from service availability notifications by an rApp as well as to update its subscriptions; b) support notifying the rApp regarding the changes in the availability of services; c) provide response of success or failure to subscribe service availability request, update service availability subscription request and unsubscribe service availability request. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 25 2) rApp: a) supports functionality to initiate requests to subscribe to and unsubscribe from service availability notifications as well as to update its subscriptions; b) supports functionality to accept notifications of the changes in service availability from the SME services Producer. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.4.1 Subscribe to service availability notifications | Table 6.4.4.1-1: Subscribe to service availability notifications Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp subscribes to notifications about changes of the availability of services. Actors and Roles - rApp in the role of Service Consumer that requests subscription to service availability notifications. - SME functions in the role of SME services Producer entity that handles the subscription requests. Assumptions n/a Preconditions The rApp is authorized to subscribe to notifications about changes in service availability. Begins when The rApp determines to subscribe to notifications, regarding changes in the availability of services. Step 1 (M) The rApp requests the SME functions to subscribe to notifications regarding changes in the available services with rAppId and optional service identifiers. Step 2 (M) The SME functions check whether the rApp is authorized to send a subscription request. Step 3 (M) The SME functions respond with subscription identifier. Ends when The rApp was able to subscribe to notifications. Exceptions n/a Post Conditions 1) The rApp can receive notifications when there are any changes in the services availability. 2) The rApp can unsubscribe from service availability notifications. Traceability REQ-R1-SME-Servicesub-FUN1. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant" "SME functions " as SME endbox autonumber rApp -> SME : <<R1>> Subscribe service availability request(rAppId) activate SME SME --> SME : AuthZ note right check authorization to send a subscription request end note SME -> rApp : <<R1>> Subscribe service availability response (subscription identifier) deactivate SME @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 26 Figure 6.4.4.1-1: Subscribe to of services availability notifications use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.4.2 Notify service availability changes | Table 6.4.4.2-1: Notify service availability changes use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp receives notifications about changes in the available services. Actors and Roles - rApp in the role of Service Consumer that receives notifications on service availability changes. - SME functions in the role of SME services Producer that sends notifications on service availability changes. Assumptions n/a Preconditions The rApp has subscribed to notifications on service availability changes. Begins when The SME functions determine to send notifications, regarding changes in the available service/s to subscribed rApp. Step 1 (M) The SME functions detect changes in service availability (due to service registration, service update, service deregistration and heartbeat failure). Step 2 (M) The SME functions send notifications regarding the changes to be subscribed rApp with subscription identifier and information about service changes. Step 3 (M) The rApp processes the changes. Ends when The rApp was able to process the changes in the available services. Exceptions n/a Post Conditions n/a Traceability REQ-R1-SME-Servicesub-FUN2. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "SME functions " as SME endbox autonumber SME --> SME : Trigger changes in the service/s SME -> rApp : <<R1>> notify changes \n(subscription identifier, service identifier/s) rApp --> rApp : Process the changes @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 27 Figure 6.4.4.2-1: Notify service availability changes use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.4.3 Unsubscribe from service availability notifications | Table 6.4.4.3-1: Unsubscribe from service availability notifications Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp unsubscribes from service availability notifications. Actors and Roles - rApp in the role of Service Consumer that requests unsubscribe from service availability notifications. - SME functions in the role of SME services Producer that process the unsubscribe service availability request. Assumptions n/a Preconditions - The rApp is authorized to unsubscribe from service availability notifications. - The rApp has subscribed to notification changes. Begins when The rApp determines to unsubscribe from service availability notifications. Step 1 (M) The rApp requests the SME functions to unsubscribe from service availability notifications with rAppId and subscription identifier. Step 2 (M) The SME functions check whether the rApp is authorized to unsubscribe. Step 3 (M) The SME functions send a response. Ends when The rApp was able to unsubscribe from service availability notifications. Exceptions n/a Post Conditions The rApp is not subscribed to service availability notifications. Traceability REQ-R1-SME-Servicesub-FUN3. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "SME functions " as SME endbox autonumber rApp -> SME : <<R1>> Unsubscribe from service availability notifications request(subscription identifier) activate SME SME -> SME : AuthZ note right check authorization to unsubscribe ETSI ETSI TS 104 230 V10.0.0 (2026-02) 28 end note SME -> rApp : <<R1>> Unsubscribe from service availability notifications response deactivate SME @enduml Figure 6.4.4.3-1: Unsubscribe service availability use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.4.4 Update subscriptions to service availability notifications | Table 6.4.4.4-1: Update subscriptions to service availability notifications Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp updates its subscriptions to notifications about changes of the availability of services. Actors and Roles - rApp in the role of Service Consumer that requests updating one of its subscriptions to service availability notifications. - SME functions in the role of SME services Producer entity that handles the update subscription requests. Assumptions n/a Preconditions The rApp is authorized to update its subscriptions to notifications about changes in service availability. Begins when The rApp determines to update one of its subscriptions to notifications regarding changes in the availability of services. Step 1 (M) The rApp requests the SME functions to update one of its subscriptions to notifications regarding changes in the available services with rAppId and subscription identifier. Step 2 (M) The SME functions check whether the rApp is authorized to update the subscription. Step 3 (M) The SME functions send a response. Ends when The rApp was able to update one of its subscriptions to notifications. Exceptions n/a Post Conditions None Traceability REQ-R1-SME-Servicesub-FUN4. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "SME functions" as SME endbox autonumber rApp -> SME : <<R1>> Update service availability subscription request(subscriptionId, subscription update information) ETSI ETSI TS 104 230 V10.0.0 (2026-02) 29 activate SME SME --> SME : AuthZ note right check authorization to update the subscription end note SME -> rApp : <<R1>> Update service availability subscription response deactivate SME @enduml Figure 6.4.4.4-1: Update subscriptions to service availability notifications use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.5 Required data | To receive notifications regarding changes in service availability, the rApp as Service Consumer subscribes to notifications by providing rAppId and optional service identifier/s. When the SME functions have successfully processed the request, they respond by providing a subscription identifier. The SME functions send notifications to the subscribed rApp when there are changes in the availability of services by providing subscription identifier, service identifiers and information about the changes. For updating a subscription, a subscribed rApp needs to provide the subscription identifier and subscription update information. For unsubscribing from notifications, a subscribed rApp needs to provide subscription identifier. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5 SME use case 5: Query registered services | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.1 Overview | This use case allows an rApp as Service Producer to retrieve the service information of registered services as specified in R1GAP [1]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.2 Background and goal of the use case | An rApp as a Service registration service Consumer can retrieve the service information of its registered services from the Service registration services Producer. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.3 Entities/resources involved in the use case | 1) SME functions in the role of Service registration service Producer: a) support functionality to query the information of registered services; b) support authorization of an rApp to determine whether an rApp can query the information of registered services; c) retrieve the stored service information and performs filtering of available services based on the selection criteria that may be provided by rApp; ETSI ETSI TS 104 230 V10.0.0 (2026-02) 30 d) provide the response of success or failure result to Query registered services request. 2) rApp: a) supports to initiate the procedure to query the service information of its registered services. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.4.1 Query registered services | Table 6.5.4.1-1: Query registered services use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp is aware of the service information of its registered services. Actors and Roles - rApp in the role of Service registration service Consumer that queries registered services. - SME functions in the role of Service registration service Producer that handles the queries for registered services. Assumptions n/a Preconditions The rApp is authorized to query its registered services. Begins when The rApp determines the need to query registered services. Step 1 (M) The rApp requests the SME functions to query registered services based on the rAppId and optional selection criteria. Step 2 (M) The SME functions check if the rApp is authorized to query registered services. Step 3 (M) The SME functions respond with service API descriptions that match the query. Ends when The rApp was able to query registered services. Exceptions n/a Post Conditions n/a Traceability n/a @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant " SME functions" as SME endbox rApp -> SME : <<R1>> Query registered services request (rAppId) activate SME SME --> SME: AuthZ note right check authorization to query registered services end note SME -> rApp :<<R1>> Query registered services response (service API descriptions) deactivate SME @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 31 Figure 6.5.4.1-1: Query registered services use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.5 Required data | For querying registered services, the rApp needs to provide the rAppId and optional selection criteria e.g. service name, service type and capabilities. The SME functions respond with service API descriptions that match the selection criteria. 7 Use cases for Data Management and Exposure Services 7.1 DME use case 1: Data registration, update, and deregistration |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.1 Overview | This use case defines how an rApp as DME registration and discovery services consumer registers as producer of data for a DME type, queries a DME type registration, updates a DME type registration and deregisters as producer of data for a DME type. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.2 Background and goal of the use case | The Register DME type Query DME type registration, Update DME type registration and Deregister DME type procedures are defined as part of Data management and exposure services in R1GAP [1]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.3 Entities/resources involved in the use case | 1) Data management and exposure functions: a) support functionality to allow an rApp to register, query, update and deregister as producer of data for a DME type; b) support functionality to allow an rApp to register the constraints for how it can produce and deliver data for the registered DME type; c) support validation of DME type information (e.g. schema validation). 2) rApp: a) initiates the procedure to register, query, update and deregister as producer of data for a DME type. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 32 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.4.1 Register DME type | Table 7.1.4.1-1: DME type registration Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp registers as producer of data for a DME type. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registration and discovery service Producer. Assumptions n/a Preconditions - The rApp is authorized to access the Data management and exposure services. - The rApp not registered as producer of data for the DME type that they intend to register in Data management and exposure functions. Begins when The rApp determines the need to register as a producer of data for a DME type. Step 1 (M) The rApp requests the Data management and exposure functions to register as producer of data for a DME type by providing the rAppId and DME type information. Step 2 (M) The Data management and exposure functions check with SME functions whether the rApp is authorized to register as producer of data. Step 3 (M) The Data management and exposure functions validate the DME type information. Step 4 (M) The Data management and exposure functions register the rApp as Data Producer of the DME type. Further, in case this rApp is the first producer of data that registers for the DME type, the Data management and exposure functions add the DME type to the set of discoverable DME types. Step 5 (M) The Data management and exposure functions respond to rApp with successful DME type registration along with DME type registration identifier. Ends when The rApp was able to register as producer of data for a DME type. Exceptions n/a Post Conditions The DME type is discoverable. Traceability REQ-R1-DME-Regdatatype-FUN1. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME endbox rApp -> DME :<<R1>>Register DME type request (rAppId,\n{ DME type information}) activate DME DME --> DME :AuthZ note right Check authorization in collaboration with SME functions end note DME --> DME :Validate note right validation of DME type information end note DME --> DME :Register DME type ETSI ETSI TS 104 230 V10.0.0 (2026-02) 33 DME -> rApp :<<R1>>Register DME type response (DME type registration identifier) deactivate DME @enduml Figure 7.1.4.1-1: Register DME type use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.4.2 Deregister DME type | Table 7.1.4.2-1: DME type deregistration Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp deregisters as producer of data for a DME type. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registration and discovery service Producer. Assumptions The rApp is not producing any data for the DME type. Preconditions The rApp has registered as producer of data for a DME type. The rApp is authorized to access the Data management and exposure services. Begins when The rApp determines the need to deregister as producer of data for a DME type that it no longer intends to produce. Step 1 (M) The rApp requests Data management and exposure functions to be deregistered as producer of data for a DME type by providing rAppId and DME type registration identifier. Step 2 (M) The Data management and exposure functions check with SME functions whether the rApp is authorized to deregister as producer of data. Step 3 (M) The Data management and exposure functions remove the registration of the rApp as producer of data for the DME type. Further, in case no other producer of data for the DME type is registered, the Data management and exposure functions remove the DME type from the set of discoverable DME types. Step 4 (M) The Data management and exposure functions respond to the rApp with successful deregistration. Ends when The rApp was able to deregister the as producer of data for the DME type. Exceptions n/a Post Conditions The rApp will not receive any request of data for the DME type and if no other producer is registered, the DME type is not discoverable any longer. Traceability REQ-R1-DME-Regdatatype-FUN1. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 34 @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC"" #whitesmoke box #ivory participant rApp as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME endbox rApp -> DME :<<R1>>Deregister DME type request \n(rAppId,DME type registration identifier) activate DME DME --> DME :AuthZ note right Check authorization in collaboration with SME functions end note DME --> DME :Deregister DME type DME -> rApp :<<R1>>Deregister DME type response deactivate DME @enduml Figure 7.1.4.2-1: Deregister DME type use case flow diagram ETSI ETSI TS 104 230 V10.0.0 (2026-02) 35 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.4.3 Update DME type registration | Table 7.1.4.3-1: Update DME type registration Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp as producer of data updates a DME type registration it has previously created. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registration and discovery service Producer. Assumptions n/a Preconditions The rApp has registered as producer of data for a DME type. The rApp is authorized to access the Data management and exposure services. Begins when The rApp determines the need to update a DME type registration it has previously created. Step 1 (M) The rApp requests Data management and exposure functions to update a DME type registration it has previously created by providing rAppId, DME type registration identifier and DME type registration update information. Step 2 (M) The Data management and exposure functions check with SME functions whether the rApp is authorized to update its registered DME type. Step 3 (M) The Data management and exposure functions update the registered DME type. Step 4 (M) The Data management and exposure functions respond to the rApp with successful result. Ends when The rApp has updated the DME type registration. Exceptions n/a Post Conditions The updated DME type is discoverable. Traceability REQ-R1-DME-Regdatatype-FUN1. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME endbox rApp -> DME :<<R1>>Update DME type registration request \n(rAppId,DME type registration identifier, DME type registration update information) activate DME DME --> DME :AuthZ note right Check authorization in collaboration with SME functions end note DME --> DME :Update DME type registration DME -> rApp :<<R1>>Update DME type registration response deactivate DME @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 36 Figure 7.1.4.3-1: Update DME type registration use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.4.4 Query DME type registration | Table 7.1.4.4-1: Query DME type registration Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp as producer of data query a DME type registration it has previously created. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registration and discovery service Producer. Assumptions n/a Preconditions The rApp has registered as producer of data for a DME type. The rApp is authorized to access the Data management and exposure services. Begins when The rApp determines the need to query a DME type registration it has previously created. Step 1 (M) The rApp requests Data management and exposure functions to query a DME type registration it has previously created by providing rAppId and DME type registration identifier. Step 2 (M) The Data management and exposure functions check with SME functions whether the rApp is authorized to query its registered DME type. Step 3 (M) The Data management and exposure functions query the registered DME type. Step 4 (M) The Data management and exposure functions respond to the rApp with DME type registration information. Ends when The rApp has queried the DME type registration. Exceptions n/a Post Conditions n/a Traceability REQ-R1-DME-Regdatatype-FUN1. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME endbox rApp -> DME :<<R1>>Query DME type registration request (rAppId, \n DME type registration identifier) ETSI ETSI TS 104 230 V10.0.0 (2026-02) 37 activate DME DME --> DME :AuthZ note right Check authorization in collaboration with SME functions end note DME --> DME :Query DME type registration DME -> rApp :<<R1>>Query DME type registration response (DME type registration information) deactivate DME @enduml Figure 7.1.4.4-1: Query DME type registration use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.5 Required data | The DME type information includes the data type identifier, metadata describing the DME type, the schemas for the data content, and constraints for how data can be produced, delivered, and accessed. For registering a DME type, the rApp provides the rAppId and DME type information. On successful registration, Data management and exposure functions provide a DME type registration identifier for the registration of the rApp as producer of data for the DME type. For querying a DME type registration, the rApp provides the rAppId and DME type registration identifier. For updating a DME type registration, the rApp provides the rAppId, DME type registration identifier and DME type registration update information. For deregistering a DME type, the rApp provides the rAppId and the DME type registration identifier. NOTE: Data management and exposure functions are not required to check whether the rApp is not producing any data for the DME type it tries to deregister. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2 DME use case 2: Discovery of DME types | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.1 Overview | This use case enables an rApp to retrieve information about registered and available DME types and query a DME type identifier and its associated information. It also enables an rApp to subscribe to and unsubscribe from notifications regarding changes in the availability of DME types. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 38 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.2 Background and goal of the use case | The discover DME type and query DME type information, subscribe DME types changes, unsubscribe DME types changes and notify DME types changes procedure are defined as part of the Data management and exposure services in R1GAP [1]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.3 Entities/resources involved in the use case | 1) Data management and exposure functions in the role of Data registration and discovery service Producer: a) support functionality allowing rApps to discover the DME types that are available; b) support functionality allowing rApps to retrieve the information about a specific data type identified by a DME type identifier; c) support functionality allowing rApps to subscribe to and unsubscribe from notifications regarding the availability of DME types; d) support functionality to notify rApps about changes in the availability of DME types. 2) rApp in the role of Data registration and discovery service Consumer: a) initiates the procedure to discover DME types and query DME type information, subscribe DME types of changes and unsubscribe DME types changes; b) supports functionality to receive notifications regarding changes in the availability of DME types. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4.1 Discover DME type | Table 7.2.4.1-1: Discover DME types Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp retrieves the information on available DME types. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registration and discovery service Producer. Assumptions n/a Preconditions The rApp is authorized to access the Data registration and discovery services. At least one DME type is registered and available with the Data management and exposure functions. Begins when The rApp determines the need to discover the available DME types. Step 1 (M) The rApp requests the Data management and exposure functions for the information on the available DME types by providing rAppId and optional filter criteria. Step 2 (M) The Data management and exposure functions validate if the rApp is authorized to discover the available DME types. Step 3 (M) The Data management and exposure functions provide the information about available DME types. The list contains only those available DME types that match the filtering criteria if those were provided by the rApp, or all available DME types otherwise. For each DME type, the data type identifier and meta data are provided. Ends when The rApp was able to discover the available DME types. Exceptions n/a Post Conditions The rApp can retrieve specific information related to a DME type by providing its data type identifier. Traceability REQ-R1-DME-discoverydatatype-FUN1. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 39 @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC"" #whitesmoke box #ivory participant rApp as rApp endbox box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME endbox rApp -> DME :<<R1>> Discover DME types request\n(rAppId, Query information) activate DME DME --> DME :AuthZ note right Check authorization in collaboration with SME functions end note DME -> rApp :<<R1>>Discover DME types response\n(data type identifiers and metadata) deactivate DME @enduml Figure 7.2.4.1-1: Discover DME types use case flow diagram ETSI ETSI TS 104 230 V10.0.0 (2026-02) 40 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4.2 Query DME type information | Table 7.2.4.2-1: Query DME type information Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp retrieves detailed information on a specific DME type. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registration and discovery service Producer. Assumptions n/a Preconditions The rApp is authorized to access the Data registration and discovery service. The rApp is aware of the data type identifier of the DME type about which it intends to retrieve detail information. Begins when The rApp determines the need to retrieve the information on a specific DME type. Step 1 (M) The rApp requests the Data management and exposure functions for the information on a specific DME type by providing the data type identifier. Step 2 (M) The Data management and exposure functions validate if the rApp is authorized to retrieve the information. Step 3 (M) The Data management and exposure functions provide the information on the requested data type identifier. Ends when The rApp has all the information of a DME type. Exceptions n/a Post Conditions The rApp can formulate a request or subscription for data of that DME type. Traceability REQ-R1-DME-discoverydatatype-FUN1. @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC"" #whitesmoke box #ivory participant rApp as rApp endbox box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME endbox rApp -> DME :<<R1>>Query DME type information request \n(data type identifier) activate DME DME --> DME :AuthZ note right Check authorization in collaboration with SME functions end note DME -> rApp :<<R1>> Query DME type information response \n(DME type information) deactivate DME @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 41 Figure 7.2.4.2-1: Query DME type information use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4.3 Subscribe DME types changes | Table 7.2.4.3-1: Subscribe DME types changes Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp subscribes to notifications regarding changes in the availability of DME types. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registration and discovery service Producer. Assumptions n/a Preconditions - The rApp is authorized to access the Data registration and discovery service. - The rApp is aware of the data type identifier of the DME type. Begins when The rApp determines the need to subscribe to notifications regarding changes in the availability of DME types. Step 1 (M) The rApp requests the Data management and exposure functions to subscribe to notifications regarding DME types availability changes by providing the rAppId and data type identifier(s). Step 2 (M) The Data management and exposure functions validate if the rApp is authorized to subscribe to notifications. Step 3 (M) The Data management and exposure functions create the subscription. Step 4 (M) The Data management and exposure functions respond to the request with subscription ID. Ends when The rApp was able to subscribe to notifications regarding DME types changes. Exceptions n/a Post Conditions 1) The rApp can receive notifications when there are any changes in the set of DME types. 2) The rApp can unsubscribe from the notifications. Traceability n/a ETSI ETSI TS 104 230 V10.0.0 (2026-02) 42 @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC"" #whitesmoke box #ivory participant rApp as rApp endbox box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME endbox rApp -> DME :<<R1>>Subscribe DME types changes request \n(rAppId, data type identifier(s)) activate DME DME --> DME :Authz note right Check authorization in collaboration with SME functions end note DME --> DME : create subscription DME -> rApp :<<R1>> Subscribe DME types changes response \n(subscription ID) deactivate DME @enduml Figure 7.2.4.3-1: Subscribe DME types changes use case flow diagram ETSI ETSI TS 104 230 V10.0.0 (2026-02) 43 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4.4 Notify DME types changes | Table 7.2.4.4-1: Notify DME types changes Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp receives a notification regarding a change in the availability of DME types. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registration and discovery service Producer. Assumptions n/a Preconditions - The rApp is authorized to access the Data registration and discovery service. - The rApp is subscribed to notifications. Begins when The Data management and exposure functions determine to send a notification regarding a change in the availability of DME types to the subscribed rApp. Step 1 (M) The Data management and exposure functions send a notification to the subscribed rApp with subscription ID, data type identifier(s) and information about the changes in the availability of DME types. Ends when The rApp was able to receive the notification. Exceptions n/a Post Conditions n/a Traceability n/a @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC"" #whitesmoke box #ivory participant rApp as rApp endbox box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME endbox DME -> rApp : <<R1>> Notify DME types changes(subscription ID, data type identifier(s), \navailability change details) @enduml Figure 7.2.4.4-1: Notify DME types changes use case flow diagram ETSI ETSI TS 104 230 V10.0.0 (2026-02) 44 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4.5 Unsubscribe DME types changes | Table 7.2.4.5-1: Unsubscribe DME types changes Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp unsubscribes from notifications. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registration and discovery service Producer. Assumptions n/a Preconditions - The rApp is authorized to access the Data registration and discovery service. - The rApp is subscribed to notifications regarding DME types changes. Begins when The rApp determines the need to unsubscribe from notifications regarding changes in the availability of DME types. Step 1 (M) The rApp requests the Data management and exposure functions to unsubscribe from notifications regarding DME types changes by providing the rAppId and subscription ID. Step 2 (M) The Data management and exposure functions validate if the rApp is authorized to unsubscribe from notifications. Step 3 (M) The Data management and exposure functions cancel the subscription. Step 4 (M) The Data management and exposure functions respond to the request. Ends when The rApp was able to unsubscribe from notifications regarding changes in the availability of DME types. Exceptions n/a Post Conditions n/a Traceability n/a @startuml 'https://plantuml.com/sequence-diagram !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC"" #whitesmoke box #ivory participant rApp as rApp endbox box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME endbox rApp -> DME :<<R1>>Unsubscribe DME types changes request(rAppId, \nsubscription ID) activate DME DME --> DME :Authz note right Check authorization in collaboration with SME functions end note DME --> DME : cancel subscription DME -> rApp :<<R1>> Unsubscribe DME types changes response deactivate DME @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 45 Figure 7.2.4.5-1: Unsubscribe DME types of changes use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.5 Required data | For the Discover DME types request, the rApp provides the rAppId and optional query information. The Data management and exposure functions respond with information about all available DME types which includes for each DME type, the data type identifier, and related metadata information. If filtering criteria were provided in the related request, the response only contains information about those DME types that match the filtering criteria. For the Query DME type information request, the rApp provides the data type identifier. The Data management and exposure functions respond with information related to the DME type. For subscription to notifications regarding changes in the availability of DME types, the rApp provides the rAppId and the data type identifier(s). The Data management and exposure functions respond with a unique subscription identifier. The Data management and exposure functions send notifications to the subscribed rApp by providing the subscription identifier, data type identifier(s) and related information about the changes in the availability of DME types. For unsubscribing from notifications regarding changes in the availability of DME types, the subscribed rApp needs to send the rAppId and subscription identifier. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3 DME use case 3: Data offer | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.1 Overview | This use case allows a Data Producer rApp as Service Consumer to create and terminate a data offer to trigger the collection of a data instance it wishes to deliver to the Data management and exposure functions as Data management and exposure services Producer for collection. Further, it allows the Data management and exposure functions as Data management and exposure services Producer to indicate to the Data Producer rApp as Service Consumer that they intend to stop collecting the data instance related to a data offer. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.2 Background and goal of the use case | A Data Producer rApp as Service Consumer can create a data offer which indicates to the Data management and exposure functions that the rApp intends to deliver a data instance to the Data management and exposure services Producer for collection. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 46 Further, the Data Producer rApp as Service Consumer can terminate a data offer it has created earlier to indicate to the Data management and exposure functions that the Data Producer no longer wishes to deliver the data instance for collection. Finally, the Data management and exposure functions can indicate to the Data Producer rApp as Service Consumer via a data offer termination notification that they will stop collecting a data instance and will terminate the related data offer created earlier by the Data Producer rApp. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.3 Entities/resources involved in the use case | 1) Data management and exposure functions as Data management and exposure services Producer: a) support functionality to create a data offer as requested by a Data Producer rApp; b) support authorization of a Data Producer rApp to determine whether it can create a data offer; c) support to send data offer termination notifications; d) support to receive the offered data from the rApp and store them; e) provide the response of success or failure result to the create data offer request and the terminate data offer request. 2) rApp: a) supports initiating the procedure to create a data offer indicating its intent to deliver data for collection and subsequent storage; b) supports to receive data offer termination notifications; c) supports to request terminating a data offer created earlier; d) supports to produce and deliver the offered data. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.