hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.3.9.2 Protocol Errors | No specific protocol errors are defined in the present document. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.3.9.3 Application Errors | No additional application errors defined in the present document. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4 AI/ML model deployment API | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.1 Introduction | This API enables the API Consumer to request the deployment of an AI/ML model based on the AI/ML model deployment request service defined in R1GAP [5]. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 139 |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.2 API version | For the AI/ML model deployment API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see ETSI TS 129 501 [1] for a definition of the version fields). Consequently, the <apiVersion> URI path segment shall be set to "v1". The AI/ML model deployment API is under development and consequently the API version shall include the pre-release version "alpha.1". |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.3 Resource structure and methods | The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The <apiName> resource URI variable shall be " ai-ml-model-deployment". The <apiSpecificResourceUriPart> for each resource shall be set as described in clause 10.4.5. Figure 10.4.3-1 shows the overall resource URI structure defined for the AI/ML model deployment API. Figure 10.4.3-1: Resource URI structure of the AI/ML model deployment API Table 10.4.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. Table 10.4.3-1: Resource and methods overview of the AI/ML model deployment API Resource name Resource URI HTTP method Service Operation All AI/ML model deployments …/model-deployments POST Request AI/ML model deployment. Individual AI/ML deployment status …/model-deployments/{ modelDeploymentId }/status GET Query AI/ML model deployment status. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.4 Service operations | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.4.1 Request AI/ML model deployment | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.4.1.1 Operation definition | The API Consumer uses this operation to request AI/ML model deployment. The operation to request AI/ML model deployment is based on HTTP POST. {apiRoot}/ai-ml-model-deployment/<apiVersion> /model-deployments /{modelDeploymentId} /status ETSI ETSI TS 104 231 V8.0.0 (2026-03) 140 Figure 10.4.4.1.1-1: Request AI/ML model deployment operation The service operation is as follows: 1) The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource "/modeldeployments", the message content shall carry a ModelDeploymentInformation which includes information for deployment. The API Producer shall process the request received in the HTTP POST message and determine if the request sent by the API Consumer is authorized or not. 2) The API Producer shall generate the deployment identifier and construct the URI for the created resource. The API Producer shall return the HTTP POST response. On success, "201 Created" shall be returned. The "Location" header shall be present and shall carry the URI of the new resource. The message content shall carry a ModelDeploymentInformation structure that represents the new resource. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.4.1.2 Referenced procedures | 10.4.4.1.2.1 Request AI/ML model deployment procedure The request AI/ML model deployment operation illustrated in Figure 10.4.4.1.1-1 is based on the request AI/ML model deployment procedure defined in R1GAP [5]. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.4.2 Notify AI/ML model deployment status change | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.4.2.1 Operation definition | The API Producer uses this operation to notify the change of an AI/ML model deployment status. The operation to notify AI/ML model deployment status change is based on HTTP POST. Figure 10.4.4.2.1-1: Notify AI/ML model deployment status change operation The service operation is as follows: 1) The API Producer shall send an HTTP POST request to the API Consumer. The target URI {notificationDestination} may be provided by API Consumer during the ai/ml model deployment request, where the message content shall carry a DeploymentStatusChangeNotification which includes the updated AI/ML model deployment status. The API Consumer shall process the request received in the HTTP POST message and determine if the request sent by the API Producer is authorized or not. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 141 2) The API Consumer shall return the HTTP POST response. On success, "204 No Content" shall be returned. The message content shall be empty. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.4.2.2 Referenced procedures | 10.4.4.2.2.1 Notify AI/ML model deployment status change procedure The notify AI/ML model deployment status change operation illustrated in Figure 10.4.4.2.1-1 is based on the AI/ML model deployment procedure defined in R1GAP [5]. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.5 Resources | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.5.1 Overview | This clause defines the resource for the AI/ML model deployment API. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.5.2 Resource: "All AI/ML model deployment" | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.5.2.1 Description | The resource represents all AI/ML model deployment in the Non-RT RIC. The methods defined in clause 10.4.5.2.3 shall be supported by this resource. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.5.2.2 Resource Definition | Resource URI: {apiRoot}/ai-ml-model-deployment/<apiVersion> The resource URI variables supported by the resource is defined in Table 10.4.5.2.2-1. Table 10.4.5.2.2-1: Resource URI variable for the resource Name Definition apiRoot See clause 5.2. apiVersion See clause 10.4.2. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.5.2.3 Resource Standard Methods | 10.4.5.2.3.1 POST This method shall support the request data structures specified in Table 10.4.5.2.3.1-1 and the response data structures and response codes specified in Table 10.4.5.2.3.1-2. Table 10.4.5.2.3.1-1: Data structures supported by the HTTP POST Request Body on this resource Data type P Cardinality Description ModelDeploymentInformation M 1 Information related to the deployment of the AI/ML model. Table 10.4.5.2.3.1-2: Data structures supported by the HTTP POST Response Body on this resource Data type P Cardinality Response codes Description ModelDeploymentInformation 201 Created The operation was successful. The message content of the POST response carries ModelDeploymentInformation. ProblemDetails O 0..1 4xx/5xx Detailed problem description. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 142 |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.5.2.4 Resource Custom Methods | None. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.6 Custom operation without associated resources | None. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.7 Notifications | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.7.1 Notify AI/ML model deployment status change | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.7.1.1 Overview | The notification informs the receiver about the AI/ML model deployment status. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.7.1.2 Resource Definition | The Resource URI {notificationDestination} is a callback URI provided when requesting deployment of an AI/ML model. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.7.1.3 Resource Standard Methods | 10.4.7.1.3.1 POST This method shall support the request data structures specified in Table 10.4.7.1.3.1-1 and the response data structure and response codes specified in Table 10.4.7.1.3.1-2. Table 10.4.7.1.3.1-1: Data structures supported by the HTTP POST request body on this resource Data type P Cardinality Description DeploymentStatusChangeNotification M 1 Notify a status changes of an AI/ML model deployment status. Table 10.4.7.1.3.1-2: Data structures supported by the HTTP POST response body on this resource Data type P Cardinality Response codes Description N/A 204 No Content Confirmation of received notification ProblemDetails O 0..1 4xx/5xx The operation was unsuccessful. Detailed problem description may be carried in the response message content |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.8 Data Model | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.8.1 Structured data types | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.8.1.1 Overview | The following clauses define the structured data types and their attributes to be used by the AI/ML model deployment API. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.4.8.1.2 Data type: ModelDeploymentInformation | The ModelDeploymentInformation data type represents deployment information for an AI/ML model. It contains the attributes defined in Table 10.4.8.1.2-1. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 143 Table 10.4.8.1.2-1: Definition of type ModelDeploymentInformation Attribute Name Data type P Cardinality Description modelId ModelId M 1 Identifier of a model. See clause 10.1.8.1.3. notificationDestination Uri O 0..1 Callback URI where the notification would be delivered to, once the deployment status changes. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.5 AI/ML model retrieve API | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.5.1 Introduction | This API enables the API Consumer to request the retrieve of an AI/ML model based on the AI/ML model retrieve request service defined in R1GAP [5]. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.5.2 API version | For the AI/ML model retrieve API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see clause 4.3.1.1 of ETSI TS 129 501 [1] for a definition of the version fields). Consequently, the <apiVersion> URI path segment shall be set to "v1". The AI/ML model retrieve API is under development and consequently the API version shall include the pre-release version "alpha.1". |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 10.5.3 Resource structure and methods | The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The <apiName> resource URI variable shall be "ai-ml-model-retrieve". Figure 10.5.3-1 shows the overall resource URI structure defined for the AI/ML model retrieve API. Figure 10.5.3-1: Resource URI structure of AI/ML model retrieve API Table 10.5.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. Table 10.5.3-1: Resource and methods overview of the AI/ML model retrieve API Resource name Resource URI HTTP method Service Operation AI/ML model retrieve …/model-retrieve GET Retrieve AI/ML model {apiRoot}/ai-ml-model-retrieve/<apiVersion> /model-retrieve ETSI ETSI TS 104 231 V8.0.0 (2026-03) 144 Annex A (normative): OpenAPI specifications A.1 General A.1.1 Overview This annex formally specifies the RESTful R1 service APIs by defining OpenAPI documents in YAML format that comply with the OpenAPI Specification v3.0.3 [3]. The Open API specifications of the RESTful R1 service APIs provided in this annex are versioned as described in clause 5.2. The OpenAPIs defined in this annex has references to the common definitions defined in clause A.1.2 of the present document. A.1.2 Common schemas for general use A.1.2.1 Introduction The Open API specified in clause A.1.2.2 provides schemas for general data types and responses for usage across the R1 APIs. A.1.2.2 Common definitions openapi: 3.0.3 info: title: 'R1 Common definitions' version: 1.0.0 description: | R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' url: 'https://www.o-ran.org/specifications' paths: {} components: schemas: Uri: description: 'A string formatted according to IETF RFC 3986 [8].' type: string ProblemDetails: description: 'A problem detail to carry details in an HTTP response according to IETF RFC 7807' type: object properties: type: description: 'a URI reference according to IETF RFC 3986 that identifies the problem type' type: string title: description: 'human-readable summary of the problem type' type: string status: description: 'the HTTP status code' type: number detail: description: 'human-readable explanation ' type: string instance: description: 'URI reference that identifies the specific occurrence of the problem' type: string responses: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 145 '400': description: 'Bad Request' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '401': description: 'Unauthorized' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '403': description: 'Forbidden' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '404': description: 'Not Found' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '405': description: 'Method Not Allowed' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '406': description: 'Not Acceptable' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '409': description: 'Conflict' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '411': description: 'Length Required' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '413': description: 'Payload Too Large' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '414': description: 'URI Too Large' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '415': description: 'Unsupported Media Type' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '429': description: 'Too Many Requests' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '500': description: 'Internal Server Error' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 146 '502': description: 'Bad Gateway' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' '503': description: 'Service Unavailable' content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' A.2 Service management and exposure service A.2.1 Service registration API A.2.1.1 Introduction The Open API for this service is reusing the CAPIF_Publish_Service_API as specified in clause A.2.1.2 with exceptions specified in clause A.2.1.3 below. A.2.1.2 CAPIF_Publish_Service_API The Open API for the SME service registration API specified in clause 6.1 reuses the CAPIF_Publish_Service_API as specified in ETSI TS 129 222 [9], clause A.3. The API version of the Service registration API as specified in clause 6.1.2 shall use the CAPIF_Publish_Service_API OpenAPI version as specified in Table A.2.1.2-1. Table A.2.1.2-1 API name API version CAPIF OpenAPI version Service registration API 1.2.0 1.3.0 A.2.1.3 Adaptations and Exceptions The OpenAPI code below represents the "VersionExtensions" data type which needs to be added to the OpenAPI definitions of the CAPIF_Publish_Service_API defined in ETSI TS 129 222 [9]. components: schemas: VersionExtensions: Description: ' The VersionExtensions data structure specified in table B.3.4.1-1 in R1AP defines O-RAN extensions to the CAPIF Version data type which allows to signal the versions supported for an interface endpoint.' type: object properties: fullApiVersions: description: ' List of version strings, as defined in R1GAP clause 5.2, to signal the API versions supported by the API Producer for a particular major API version.' type: array items: type: string minItems: 1 The OpenAPI code below represents the "ServiceProperties" data type which needs to be added to the OpenAPI definitions of the CAPIF_Publish_Service_API defined in ETSI TS 129 222 [9]. components: schemas: ServiceProperties: description: 'Defines a container that can be used by individual service APIs to register and discover service-specific properties.' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 147 type: object properties: serviceCapabilities: description: ' Service capabilities. The content of this attribute is service-specific and is defined per service.' type: object Table A.2.1.3-1 below lists exceptions and adaptations related to certain attributes in certain CAPIF data types when re-using the CAPIF_Publish_Service_API in the context of the present document. Table A.2.1.3-1: Message content exceptions and adaptations when reusing the CAPIF_Publish_Service_API Data type Reference Attributes Adaptations/Exceptions ServiceAPIDescription ETSI TS 129 222 [9], clause A.3 supportedFeatures Not required to be supported. shareableInfo Not required to be supported. serviceAPICategory Not required to be supported. ccfId Not required to be supported. apiSuppFeats Not required to be supported. Not required to be supported. vendorSpecific-o- ran.org This additional attribute shall be present if service-specific registration information is available for the service API. It shall have the type ServiceProperties as specified in clause B.3.4.2 and defined in clause A.2.1.3. AefProfile ETSI TS 129 222 [9], clause A.3 aefId Shall be set to the value of "rAppId" if an rApp produces the API. aefLocation Not required to be supported. domainName Not required to be supported. serviceKpis Not required to be supported. ueIpRange Not required to be supported. Version ETSI TS 129 222 [9] clause A.3 vendorSpecific-o- ran.org This additional attribute shall be supported and shall have the type VersionExtensions as specified in clause B.3.4.1 and defined above. A.2.2 Service discovery API A.2.2.1 Introduction The Open API for this service is reusing the CAPIF_Discover_Service_API in as specified in clause A.2.2.2 with exceptions specified in clause A.2.2.3 below. A.2.2.2 CAPIF_Discovery_Service_API The Open API for the SME service discovery API specified in clause 6.2reuses the CAPIF_Discover_Service_API as specified in ETSI TS 129 222 [9], clause A.2. The API version of the Service discovery API as specified in clause 6.2.2 shall use the CAPIF_Discover_Service_API OpenAPI version as specified in Table A.2.2.2-1. Table A.2.2.2-1 API name API version CAPIF OpenAPI version Service discover API 1.2.0 1.3.0 ETSI ETSI TS 104 231 V8.0.0 (2026-03) 148 A.2.2.3 Adaptations and Exceptions Table A.2.2.3-1 lists exceptions and adaptations related to CAPIF message content when re-using the CAPIF_Discover_Service _API in the context of the present document. Table A.2.2.3-1 lists exceptions and adaptations related to CAPIF URI query parameters when re-using the CAPIF_Discover_Service_API in the context of the present document. Table A.2.2.3-1: Message content exceptions and adaptations when reusing the CAPIF_Discover_Service_API Data type Reference Attributes Exceptions/Adaptations ServiceAPIDescription ETSI TS 129 222 [9], clause A.3 supportedFeatures Not required to be supported. shareableInfo Not required to be supported. serviceAPICategory Not required to be supported. ccfId Not required to be supported. apiSuppFeats Not required to be supported. pubApiPath Not required to be supported. vendorSpecific-o-ran.org This additional attribute shall be present if service-specific registration information is available for the service API. It shall have the type ServiceProperties as specified in clause B.3.4.2 and defined in clause A.2.1.3. ue-ip-addr Not required to be supported. service-kpis Not required to be supported. AefProfile ETSI TS 129 222 [9], clause A.3 aefId Shall be set to the value of "rAppId" if an rApp produces the API. Shall be set to an identifier related to the SMO/Non-RT RIC functions if these produce the API. See note. aefLocation Not required to be supported. domainName Not required to be supported. Version ETSI TS 129 222 [9], clause A.3 vendorSpecific-o-ran.org This additional attribute shall be supported and shall have the type VersionExtensions as specified in clause B.3.4.1 and defined in clause A.2.1.3. NOTE: It is out of scope of the present document whether each SMO/Non-RT RIC framework function is identifiable by a separate identifier value or whether such decomposition information is hidden from the rApps. However, the SMO/Non-RT RIC framework shall ensure that the identifiers used for rApps as AEFs and the identifiers used for SMO/Non-RT RIC framework functions as AEFs do not collide. The Query parameters in Table A.2.2.3-2 below are not required to be supported when the CAPIF_Discover_Service_API is reused. Table A.2.2.3-2: Query parameters exceptions and adaptations when reusing the CAPIF_Discover_Service_API Resource Reference Exceptions Comment /allServiceAPIs ETSI TS 129 222 [9], clause A.2 api-invoker-id Shall be set to the value of "rAppId" for an API-consuming rApp. ETSI TS 129 222 [9], clause A.2 comm-type Not required to be supported. ETSI TS 129 222 [9], clause A.2 protocol Not required to be supported. ETSI TS 129 222 [9], clause A.2 aef-id Not required to be supported. ETSI TS 129 222 [9], clause A.2 data-format Not required to be supported. ETSI TS 129 222 [9], clause A.2 api-cat Not required to be supported. ETSI TS 129 222 [9], clause A.2 preferred-aef-loc Not required to be supported. ETSI TS 129 222 [9], clause A.2 supported-features Not required to be supported. ETSI TS 129 222 [9], clause A.2 api-supported- features Not required to be supported. ETSI TS 129 222 [9], clause A.2 ue-ip-addr Not required to be supported. ETSI TS 129 222 [9], clause A.2 service-kpis Not required to be supported. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 149 A.2.3 Service events subscription API A.2.3.1 Introduction The Open API for this service is reusing the CAPIF_Events_API as specified in clause A.2.3.2 with exceptions specified in clause A.2.3.3 below. A.2.3.2 CAPIF_Events_API The Open API for the SME service events subscription API specified in clause 6.3 reuses the CAPIF_Events_API as specified in ETSI TS 129 222 [9], clause A.4. The API version of the SME service events subscription API as specified in clause 6.3.2 shall use the CAPIF_Events_API OpenAPI version as specified in Table A.2.3.2-1 Table A.2.3.2-1 API name API version CAPIF OpenAPI version Service events subscription API 1.2.0 1.3.0 A.2.3.3 Adaptations and Exceptions Table A.2.3.3-1 lists exceptions and adaptations related to CAPIF message content when re-using the CAPIF_Events_API in the context of the present document. Table A.2.3.3-1: Message content exceptions and adaptations when reusing the CAPIF_Events_API Data type Reference Attributes Exceptions/Adaptations AccessControlPolicyListExt ETSI TS 129 222 [9], clause A.4 Not required to be supported. CAPIFEvent ETSI TS 129 222 [9], clause A.4 See clause B.3.5. CAPIFEventDetail ETSI TS 129 222 [9], clause A.4 accCtrlPolList Not required to be supported. invocationLogs Not required to be supported. apiTopoHide Not required to be supported. CAPIFEventFilter ETSI TS 129 222 [9], clause A.4 apiInvokerIds Shall be set to the value of "rAppId" for an API-consuming rApp. aefIds Shall be set to the value of "rAppId" if an rApp -produces the API. Shall be set to an identifier related to the SMO/Non-RT RIC framework functions if these produce the API. See Table A.2.2.3-1. ReportingInformation Not required to be supported. EventNotification ETSI TS 129 222 [9], clause A.4 invocationLogs Not required to be supported. apiTopoHide Not required to be supported. EventSubscription ETSI TS 129 222 [9], clause A.4 supportedFeatures Not required to be supported. eventReq Not required to be supported. TopologyHiding ETSI TS 129 222 [9], clause A.4 Not required to be supported. A.2.4 Bootstrap API A.2.4.1 Introduction The Open API for this service as specified in clause A.2.4.2. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 150 A.2.4.2 Bootstrap API openapi: 3.0.3 info: title: 'BootStrap' version: 1.0.0 description: | API for BootStrap service. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' url: 'https://www.o-ran.org/specifications' servers: - url: '{apiRoot}/bootstrap/v1/' variables: apiRoot: description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' default: 'https://example.com' paths: '/bootstrap-info': get: description: 'To discover the entry points into Service management and exposure ' responses: '200': description: '.' content: application/json: schema: $ref: '#/components/schemas/BootstrapInformation' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' components: schemas: BootstrapInformation: type: object properties: apiEndpoints: type: array items: $ref: '#/components/schemas/ApiEndpointInformation' ApiEndpointInformation: type: object properties: apiName: type: string description: 'Name of the API ("service-apis" or "published-apis")' tokenEndpoint: $ref: 'TS29122_CAPIF_publish_Service_API.yaml#/components/schemas/InterfaceDescription' description: 'Token endpoint shall be provided if the API requires authorization over OAuth2.0' nullable: true apiEndPoint: $ref: 'TS29122_CAPIF_publish_Service_API.yaml#/components/schemas/InterfaceDescription' description: 'End point of the API' nullable: true required: - apiName - apiEndPoint ETSI ETSI TS 104 231 V8.0.0 (2026-03) 151 A.3 Data management and exposure service A.3.1 Data registration API A.3.1.1 Introduction The Open API for the Data Registration API is specified in clause A.3.1.2. A.3.1.2 Data registration API openapi: 3.0.3 info: title: 'Data registration service' version: 2.0.0-alpha.2 description: | API for Data registration service. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' url: 'https://www.o-ran.org/specifications' servers: - url: '{apiRoot}/data-registration/v2/' variables: apiRoot: description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' default: 'https://example.com' apiConsumerId: description: Identifier of the API consumer that registers its data production capabilities default: '' paths: '/production-capabilities': post: description: 'To register DME type production capabilities' tags: - Registered DME type production capabilities requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/DmeTypeRelatedCapabilities' responses: '201': description: 'Success case 201 created' content: application/json: schema: $ref: '#/components/schemas/DmeTypeRelatedCapabilities' headers: Location: description: 'Contains the URI of the newly created resource' required: true schema: type: string '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '405': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' '409': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 152 '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/production-capabilities/{registrationId}': parameters: - name: registrationId in: path required: true schema: $ref: '#/components/schemas/registrationId' put: description: 'To update DME type production capabilities that it has previously registered' tags: - Individual registered DME type production capability requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/DmeTypeRelatedCapabilities' responses: '200': description: 'Success case 200 with updated information' content: application/json: schema: $ref: '#/components/schemas/DmeTypeRelatedCapabilities' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '411': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/411' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' get: description: 'To query DME type production capabilities that it has previously registered' tags: - Individual registered DME type production capability responses: '200': description: 'Success case 200 with queried information' content: application/json: schema: $ref: '#/components/schemas/DmeTypeRelatedCapabilities' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 153 '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' delete: description: 'To deregister DME type production capabilities' tags: - Individual registered DME type production capability responses: '204': description: 'The registration was deleted' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' components: schemas: registrationId: description: 'A successful registration identified by registrationId ' type: string DmeTypeRelatedCapabilities: description: 'Information related to the registration as producer of a DME type' type: object properties: dmeTypeDefinition: $ref: '#/components/schemas/DmeTypeDefinition' constraints: description: 'Formulates producer constraints or constraints applicable to the consumption related to the DME type based on the dataProductionSchema' type: object dataAccessEndpoint: $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/InterfaceDescription' dataDeliveryModes: type: array items: $ref: 'O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/DataDeliveryMode' required: [dmeTypeDefinition, dataDeliveryModes, dataAccessEndpoint] DmeTypeDefinition: description: 'Information of the DME type' type: object properties: dmeTypeId: $ref: '#/components/schemas/DmeTypeIdStruct' metadata: $ref: '#/components/schemas/Metadata' dataProductionSchema: type: object description: 'Schema that defines the information necessary to formulate a data request or data subscription. If this attribute is not present, the schema is assumed to be known from the DME type definition that is referenced by dmeTypeId' dataDeliverySchemas: description: 'List of delivery schemas supported by the producer for the DME type being registered.' type: array items: $ref: '#/components/schemas/DeliverySchema' dataDeliveryMechanisms: description: 'Defining the delivery mechanism supported by Data Producer ' type: array items: $ref: '#/components/schemas/DataDeliveryMechanism' required: ["dmeTypeId", "metadata", "dataDeliverySchemas", "dataDeliveryMechanisms"] ETSI ETSI TS 104 231 V8.0.0 (2026-03) 154 DmeTypeIdStruct: description: 'Defining the attributes of DME type identifier' type: object properties: namespace: type: string description: 'Indicating the entity responsible for the DME type definition.' name: type: string description: 'Name of the DME type. The string can be any character except ":" (colon)' pattern: '^[^:]{1,}$' version: type: string description: 'Version of the DME type. The versioning and allowed characters are according to SemVer [11]' required: ["namespace","name","version"] DeliverySchema: description: 'Delivery schema for a DME type' type: object properties: type: $ref: '#/components/schemas/SchemaTypes' deliverySchemaId: type: string description: A Data Producer may support one or more delivery schemas and for each supported schema type a delivery schema identifier is assigned. A Data Consumer uses this attribute while creating a data job and request to deliver the data using specific schema type which is identified by this attribute. schema: type: string description: 'The schema serialized to string. If this attribute is not present, the schema is assumed to be known from the DME type definition that is referenced by dmeTypeId' required: ["type","deliverySchemaId"] DataDeliveryMechanism: description: 'Defining the attributes of delivery mechanism supported' type: object properties: dataDeliveryMethod: description: 'Delivery Method supported' ref: 'O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/DataDeliveryMethod' kafkaDeliveryConfiguration: $ref: '#/components/schemas/KafkaDeliveryConfiguration' required: - dataDeliveryMethod oneOf: - required: ["kafkaDeliveryConfiguration"] Metadata: description: 'Metadata that can be used in discovering the DME type' properties: dataCategory: description: 'Defines the category of the DME type e.g. PM counters' type: array items: type: string minItems: 1 rat: description: 'Defines the radio access technology e.g. 5G' type: array items: type: string minItems: 1 required: ["dataCategory"] SchemaTypes: description: 'Type of the schema supported by Data Producers' type: string enum: - JSON_SCHEMA - XML_SCHEMA KafkaDeliveryConfiguration: description: 'These configuration will be applied if STREAMING_KAFKA is selected as delivery method' type: object properties: numPartitions: description: 'Number of partitions' type: integer cleanUpPolicy: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 155 description: 'cleanUpPolicy is based on cleanup.policy defined in the Kafka Documentation [15]. ' type: string compressionType: description: ' compressionType is based on compression.type defined in the Kafka Documentation [15] .' type: string retentionBytes: description: ' retentionBytes is based on retention.bytes defined in the Kafka Documentation [15] . This attribute is applicable ONLY when cleanUpPolicy is set to DELETE' type: integer retentionMs: description: ' retentionMs is based on retention.ms defined in the Kafka Documentation [15] . This attribute is applicable ONLY when cleanUpPolicy is set to DELETE' type: integer required: ["cleanUpPolicy", "compressionType"] A.3.2 Data discovery API A.3.2.1 Introduction The Open API for the Data Discovery API is specified in clause A.3.2.2. A.3.2.2 Data discovery API openapi: 3.0.3 info: title: 'Data discovery service' version: 2.0.0 description: | API for Data discovery service. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' url: 'https://www.o-ran.org/specifications' servers: - url: '{apiRoot}/data-discovery/v2/' variables: apiRoot: description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' default: 'https://example.com' paths: /dme-types: get: description: 'To discover the available DME types' parameters: - name: identity-namespace in: query description: 'Identity namespace to match the "namespace" part of the "dmeTypeId" attribute' schema: type: string - name: identity-name in: query description: 'Identity name to match the "name" part of the "dmeTypeId" attribute.' schema: type: string - name: data-category in: query description: 'Set of data category entries, all of which to match entries of the "dataCategory" attribute.' schema: type: array explode: false items: type: string responses: '200': description: 'The response body contains the result of the search over the list of registered APIs.' content: application/json: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 156 schema: type: array items: $ref: 'O- RAN.WG2.R1AP_DataRegistration.yaml#/components/schemas/DmeTypeRelatedCapabilities' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '414': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/414' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' /dme-types/{dmeTypeId}: get: description: To obtain information about an individual DME type. parameters: - name: dmeTypeId in: path required: true schema: $ref: '#/components/schemas/dmeTypeId' responses: '200': description: The response body contains information about the DME type. content: application/json: schema: $ref: 'O- RAN.WG2.R1AP_DataRegistration.yaml#/components/schemas/DmeTypeRelatedCapabilities' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '414': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/414' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' components: schemas: dmeTypeId: type: string description: 'The DmeTypeId is constructed based on the three parts separated by ":" (colon) {dmeTypeId} = {namespace}:{name}:{version}. See O- RAN.WG2.R1AP_DataRegistration.yaml#/components/schemas/DmeTypeIdStruct for the definition of "namespace", "name" and "version".' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 157 A.3.3 Data access API A.3.3.1 Introduction The Open API for the Data access API is specified in clause A.3.3.2. A.3.3.2 Data access API openapi: 3.0.3 info: title: 'Data access service' version: 2.0.0-alpha.2 description: | API for Data access service. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' url: 'https://www.o-ran.org/specifications' servers: - url: '{apiRoot}/data-access/v1/' variables: apiRoot: description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' default: 'https://example.com' apiConsumerId: description: 'Identifier of the API consumer ' default: '' paths: '/data-jobs': post: description: 'To create a data job' tags: - Create all data jobs requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/DataJobInfo' responses: '201': description: 'Success case 201 created' content: application/json: schema: $ref: '#/components/schemas/DataJobInfo' headers: Location: description: 'Contains the URI of the newly created resource' required: true schema: type: string '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '405': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' '409': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': ETSI ETSI TS 104 231 V8.0.0 (2026-03) 158 $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' callbacks: DataAvailabilityNotification: '{$request.body.dataAvailabilityNotificationUri}': post: description: 'Notification on the availability of requested data' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/DataAvailabilityNotification' responses: '204': description: 'The notification was delivered' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/data-jobs/{dataJobId}': parameters: - name: dataJobId in: path required: true schema: $ref: '#/components/schemas/dataJobId' delete: description: 'To delete the created data job' tags: - Individual data job responses: '204': description: 'The data job was deleted' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' components: schemas: dataJobId: description: 'A successful created data job is identified by dataJobId ' type: string DataJobInfo: description: 'Information related to a data job' allOf: - type: object properties: dataDeliveryMode: $ref: '#/components/schemas/DataDeliveryMode' dmeTypeId: $ref: 'O-RAN.WG2.R1AP_DataDiscovery.yaml#/components/schemas/dmetypeId' productionJobDefinition: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 159 description: 'Job description based on the DME type specific dataProductionSchema' type: object dataDeliveryMethod: $ref: '#/components/schemas/DeliveryMethod' dataDeliverySchemaId: description: 'A delivery schema identifier provided by a Data Producer during the data registration procedure' type: string required: [dataDeliveryMode, dmeTypeId, productionJobDefinition, dataDeliveryMethod, dataDeliverySchemaId] - type: object oneOf: - properties: pullDeliveryDetailsHttp: $ref: '#/components/schemas/PullDeliveryDetailsHttp' required: [pullDeliveryDetailsHttp] - properties: dataAvailabilityNotificationUri: $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/schemas/Uri' required: [dataAvailabilityNotificationUri] - properties: pushDeliveryDetailsHttp: $ref: '#/components/schemas/PushDeliveryDetailsHttp' required: [pushDeliveryDetailsHttp] - properties: streamingConfigurationKafka: $ref: '#/components/schemas/StreamingConfigurationKafka' required: [streamingConfigurationKafka] DataDeliveryMode: description: 'This indicates whether the data instance is created in a one-time data delivery (data request) or continuously (data subscription)' type: string enum: - ONE_TIME - CONTINUOUS DataDeliveryMethod: description: 'This indicates supported delivery method' type: string enum: - PULL_HTTP - PUSH_HTTP - STREAMING_KAFKA PullDeliveryDetailsHttp: description: 'The PullDeliveryDetailsHttp data type signals how to pull data using the HTTP protocol.' readOnly: true type: object properties: dataPullUri: $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/schemas/Uri' required: [dataPullUri] PushDeliveryDetailsHttp: description: 'The PushDeliveryDetailsHttp data type signals how to push data using the HTTP protocol.' type: object properties: dataPushUri: $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/schemas/Uri' required: [dataPushUri] StreamingConfigurationKafka: description: 'The StreamingConfigurationKafka data type signals a data streaming configuration for the Kafka protocol.' type: object properties: topicName: description: 'Name of the Kafka topic' type: string kafkaBootstrapServers: description: 'Server configuration' type: array items: $ref: '#/components/schemas/ServerAddressWithPort' required: [topicName, kafkaBootstrapServers] ServerAddressWithPort: description: 'Server configuration' type: object properties: hostname: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 160 description: 'string identifying a hostname shall be formatted according to clause 2.3.1 as defined in IETF RFC 1035 [19]' type: string portAddress: description: 'Port address, e.g. 9092' type: integer minimum: 1 maximum: 65535 required: [hostname, portAddress] DataAvailabilityNotification: description: 'Availability of the data' type: object properties: dataJobId: description: 'data job identifier' type: string pullDeliveryDetailsHttp: $ref: '#/components/schemas/PullDeliveryDetailsHttp' A.3.4 HTTP based Push data API Deliberately, no OpenAPI is specified for this API in the present document. NOTE: OpenAPI requires the definition of the valid content types for the request message content. However, this API is agnostic with respect to the content type of the data carried in the request message. Within the DME services, the valid content types are defined as part of separate data message schemas which specify the structure of the data to be carried over the API. Because of the requirement to fix the content types that can be carried over the API, defining an OpenAPI would restrict the versatility of the API. A.3.5 HTTP based Pull data API Deliberately, no OpenAPI is specified for this API in the present document. NOTE: OpenAPI requires the definition of the valid content types for the response message content. However, this API is agnostic with respect to the content type of the data carried in the response message. Within the DME services, the valid content types are defined as part of a separate data message schema which specifies the structure of the data to be carried over the API. Because of the requirement to fix the content types that can be carried over the API, defining an OpenAPI would restrict the versatility of the API. A.3.6 Data offer API A.3.6.1 Introduction The Open API for the Data offer API is specified in clause A.3.6.2. A.3.6.2 Data offer API openapi: 3.0.3 info: title: 'Data offer service' version: 1.0.0 description: | API for Data offer service. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' url: 'https://www.o-ran.org/specifications' servers: - url: '{apiRoot}/data-offer/v1' variables: apiRoot: description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' default: 'https://example.com' apiConsumerId: description: 'Identifier of API Consumer' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 161 default: '' paths: '/offers': post: description: 'Allows to create a new data offer' tags: - All data offers requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/DataOfferInfo' responses: '201': description: 'Success case 201 created' content: application/json: schema: $ref: '#/components/schemas/DataOfferInfo' headers: Location: description: 'Contains the URI of the newly created resource' required: true schema: type: string '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '405': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' '409': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' callbacks: DataAvailabilityNotification: '{$request.body.dataAvailabilityNotificationUri}': post: description: 'Notification on the availability of offered data' requestBody: required: true content: application/json: schema: $ref: ' O-RAN.WG2.R1AP_DataAccess.yaml #/components/schemas/DataAvailabilityNotification' responses: '204': description: 'The notification was delivered' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': ETSI ETSI TS 104 231 V8.0.0 (2026-03) 162 $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' DataOfferTerminationNotification: '{$request.body.dataOfferTerminationNotificationUri}': post: description: 'Notification on termination of data offer by the API producer' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/DataOfferTerminationNotification' responses: '204': description: 'The notification was delivered' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/offers/{dataOfferId}': parameters: - name: dataOfferId in: path required: true schema: type: string delete: description: 'To delete the data offer' tags: - Individual data offer responses: '204': description: 'The data offer was deleted.' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' components: schemas: DataOfferInfo: description: 'Information related to a data offer' type: object properties: dataDeliveryMode: $ref: 'O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/DataDeliveryMode' dmeTypeId: $ref: 'O-RAN.WG2.R1AP_DataDiscovery.yaml#/components/schemas/DmeTypeId' productionJobDefinition: description: 'Job description based on the DME type specific dataProductionSchema' type: object dataDeliveryMethods: type: array items: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 163 $ref: ' O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/DataDeliveryMethod' dataDeliverySchemaIds: description: 'A delivery schema identifier provided by a Data Producer during the data registration procedure' type: array items: type: string pullDeliveryDetailsHttp: $ref: ' O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/PullDeliveryDetailsHttp' dataAvailabilityNotificationUri: $ref: '/components/schemas/DataOfferAvailabilityNotification' dataOfferTerminationNotificationUri: $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/schemas/Uri' pushDeliveryDetailsHttp: $ref: 'O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/PushDeliveryDetailsHttp' streamingConfigurationKafka: $ref: 'O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/StreamingConfigurationKafka' required: [ "dataDeliveryMode", "dmeTypeId", "productionJobDefinition", " dataDeliveryMethods ", "dataDeliverySchemaIds", "dataOfferTerminationNotificationUri"] DataOfferTerminationNotification: description: 'Termination of a data offer by the API producer' type: object properties: dataOfferId: description: 'Identifies the deleted data offer' type: string required: ["dataOfferId"] DataOfferAvailabilityNotification: description: 'Availability of the data' type: object properties: dataOfferId: description: 'data offer identifier' type: string pullDeliveryDetailsHttp: $ref: 'O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/PullDeliveryDetailsHttp' required: ['dataOfferId', 'pullDeliveryDetailsHttp']: description: 'Identifies the deleted data offer' type: string required: ["dataOfferId"] A.4 RAN OAM related services A.4.1 Configuration management API A.4.1.1 Introduction The Open API for this service is reusing the provisioning management service API as specified in clause A.4.1.2 with exceptions specified in clause A.4.1.3 below. A.4.1.2 Configuration management API The Open API for the Configuration management API specified in clause 8.1 reuses the Provisioning management service API (TS28532_ProvMnS.yaml) as specified in ETSI TS 128 532 [20], clause A.1.1. The API version of the Configuration management API as specified in clause 8.1.2 shall use the Provisioning management service OpenAPI version as specified in Table A.4.1.2-1. Table A.4.1.2-1 API name API version ProvMnS OpenAPI version Configuration management API 1.0.0 17.5.0 ETSI ETSI TS 104 231 V8.0.0 (2026-03) 164 A.4.1.3 Adaptations and Exceptions Table A.4.1.3-1 lists exceptions and adaptations related to HTTP methods when re-using the TS28532_ProvMnS_API in the context of the present document. Table A.4.1.3-1: HTTP methods exceptions and adaptations when reusing the TS28532_ProvMnS_API HTTP Methods Reference Attributes Exceptions/Adaptations PUT ETSI TS 128 532 [20], clause A.1.1 HTTP operation not required to be supported in current version. POST ETSI TS 128 532 [20], clause A.1.1 HTTP operation not required to be supported in current version. DELETE ETSI TS 128 532 [20], clause A.1.1 HTTP operation not required to be supported in current version. A.4.2 Fault management API A.4.2.1 Introduction The Open API for this service is reusing the provisioning management service API as specified in clause A.4.2.2 with exceptions specified in clause A.4.2.3 below. A.4.2.2 Fault management API The Open API for the fault management API specified in clause 8.1 reuses the Provisioning management service API (TS28111_FaultNrm.yaml) as specified in ETSI TS 128 111 [26], clause A.1.3. The API version of the fault management API as specified in clause 8.2.2 shall use the FaultNRM service OpenAPI version as specified in Table A.4.2.2-1. Table A.4.2.2-1 API name API version FaultNrm OpenAPI Fault management API 1.0.0 18.1.0 A.4.2.3 Adaptations and Exceptions NOTE: The adaptations and exceptions are not specified in the present document. A.4.3 Configuration schema information API A.4.3.1 Introduction The Open API for the Configuration schema information API is specified in clause A.4.3.2. A.4.3.2 Configuration schema information API openapi: 3.0.3 info: title: 'Configuration Schema information API' version: 1.0.0-alpha.1 description:This API enables the API Consumer to retrieve configuration schema information based on the procedure defined in R1GAP [5]. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 165 url: 'https://www.o-ran.org/specifications' servers: - url: '{apiRoot}/ran-oam-cm-schema-info/v1' variables: apiRoot: description: 'apiRoot as defined in clause 10.3 in O-RAN.WG2.R1AP' default: 'https://example.com' paths: '/schemas': get: summary: Get all schema information description: 'Retrieves configuration schema information' responses: '200': description: 'The results with the schema information' content: application/json: schema: type: array items: $ref:'#/components/schemas/Schema' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '405': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' '409': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/schemas/{schemaId}': get: summary: Get individual schema information parameters: - name: schemaId in: path required: true description: Where schemaId = "name" (for latest revision or if revision is not available) or "name@revision" for a specific revision. schema: type: string responses: '200': description: The results with the schema information matching the request. content: application/json: schema: $ref: '#/components/schemas/Schema' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '405': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' '409': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 166 '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' components: schemas: Schema: type: object required: - name - location - type properties: name: type: string description: The unique name of the schema. revision: type: string description: The unique revision of the schema. location: type: string format: uri description: Location of where to find the schema content. type: $ref: '#/components/schemas/SchemaType' description:This data type is designed to provide extensibility. As specified in clause 8.3.8.2.3.1, Only YANG is supported in the present version of the present document. namespace: type: string description: The namespace of the schema, (See NOTE 1, clause 8.3.8.2.3.1, only applicable if type is YANG). features: type: array items: type: string description: List of supported features (See NOTE 1,clause 8.3.8.2.3.1, only applicable if type is YANG). deviations: type: array items: type: string description: List of schema deviation(s) (See NOTE 1,clause 8.3.8.2.3.1, only applicable if type is YANG). SchemaType: type: string enum: - YANG description: Enumeration of schema types. A.5 A1 related service A.5.1 A1 policy management API A.5.1.1 Introduction The Open API for the A1 policy management API is specified in clause A.5.1.2. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 167 A.5.1.2 A1 policy management API openapi: 3.0.3 info: title: 'A1 policy management API' version: 1.0.0 description: | API for A1 policy management service. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' url: 'https://www.o-ran.org/specifications' servers: - url: '{apiRoot}/a1-policy-management/v1' variables: apiRoot: description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' default: 'https://example.com' paths: '/policy-types': get: description: 'To query A1 policy type identifier' tags: - All A1 policy types parameters: - name: nearRtRicId in: query description: 'The identifier of Near-RT RIC' schema: type: string - name: typeName in: query description: 'The unique label of the policy type' schema: type: string responses: '200': description: 'Success case 200 with queried information' content: application/json: schema: type: array items: $ref: '#/components/schemas/PolicyTypeInformation' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/policy-types/{policyTypeId}': parameters: - name: policyTypeId in: path required: true schema: $ref: '#/components/schemas/policyTypeId' get: description: 'To query A1 policy type' tags: - Individual A1 policy type responses: '200': description: 'Success case 200 with queried information' content: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 168 application/json: schema: $ref: '#/components/schemas/PolicyTypeObject' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/policies': get: description: 'To query A1 policy type' tags: - All A1 policies parameters: - name: nearRtRicId in: query description: 'The identifier of Near-RT RIC' schema: type: string - name: policyTypeId in: query description: 'The identifier of the policy' schema: type: string responses: '200': description: 'Success case 200 with queried information' content: application/json: schema: type: array items: $ref: '#/components/schemas/PolicyInformation' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' post: description: 'To create A1 policies' tags: - All A1 policies requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/PolicyObjectInformation' responses: '201': description: 'Success case 201 created' content: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 169 application/json: schema: $ref: '#/components/schemas/PolicyObjectInformation' headers: Location: description: 'Contains the URI of the newly created resource' required: true schema: type: string '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '405': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' '409': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/policies/{policyId}': parameters: - name: policyId in: path required: true schema: $ref: '#/components/schemas/policyId' put: description: 'To update a created policy' tags: - Individual A1 policy requestBody: required: true content: application/json: schema: "$ref": "#/components/schemas/PolicyObject" responses: 200: description: 'The policy was updated' content: application/json: schema: "$ref": "#/components/schemas/PolicyObject" '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '411': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/411' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': ETSI ETSI TS 104 231 V8.0.0 (2026-03) 170 $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' get: description: 'To query created A1 policy' tags: - Individual A1 policy responses: '200': description: 'Success case 200 with queried information' content: application/json: schema: $ref: '#/components/schemas/PolicyObject' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' delete: description: 'To delete the created A1 policy' tags: - Individual A1 policy responses: '204': description: 'The created A1 policy was deleted' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/policies/subscriptions': post: summary: Create a new A1 policy status subscription description: This operation creates a new subscription for receiving A1 policy status notifications. tags: - A1 policy status subscription requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/PolicyStatusSubscription' responses: '201': description: 'Success case 201 created' content: application/json: schema: $ref: '#/components/schemas/PolicyStatusSubscription' headers: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 171 Location: description: 'Contains the URI of the newly created resource' required: true schema: type: string '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/policies/subscriptions/{subscriptionId}': parameters: - name: subscriptionId in: path required: true schema: $ref: '#/components/schemas/subscriptionId' get: summary: Get details of an A1 policy status subscription description: This operation retrieves information about a specific subscription. tags: - A1 policy status subscription responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/PolicyStatusSubscription' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' put: description: 'This operation modifies an existing subscription.' tags: - A1 policy status subscription requestBody: required: true content: application/json: schema: "$ref": "#/components/schemas/PolicyStatusSubscription" responses: 200: description: 'The policy was updated' content: application/json: schema: "$ref": "#/components/schemas/PolicyObject" '400': ETSI ETSI TS 104 231 V8.0.0 (2026-03) 172 $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '411': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/411' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' delete: summary: Delete an A1 policy status subscription description: This operation removes a subscription. tags: - A1 policy status subscription responses: '204': description: No Content components: schemas: policyTypeId: description: 'Policy Type identifier as defined in A1AP [23], clause 6.2.3.1.3' type: string policyId: description: 'Policy Identifier of a policy' type: string NearRtRicId: description: 'Near-RT RIC identifier' type: string subscriptionId: description: 'subscription identity of the policy' type: string PolicyObject: description: 'Policy Object is a JSON representation of an A1 policy; the A1 policies are specified in A1TD [24]' type: object PolicyTypeObject: description: 'policy type object as defined in A1TD' type: object PolicyTypeInformation: description: 'Available policy types and for each policy type identifier the Near-RT RIC identifiers of those Near-RT RICs that support the related A1 policy type' type: object properties: policyTypeId: description: 'Identity of the policy type' type: string nearRtRicId: $ref: '#/components/schemas/NearRtRicId' required: ["policyTypeId","nearRtRicId"] PolicyInformation: description: 'Near-RT RIC identifiers where A1 policies exist and for each Near-RT RIC identifier the policy identifiers of those policies that exist in that Near-RT RIC' type: object properties: policyId: description: $ref: '#/components/schemas/policyId' nearRtRicId: $ref: '#/components/schemas/NearRtRicId' required: ["policyId","nearRtRicId"] PolicyObjectInformation: description: 'Information related to the creation of the policy' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 173 type: object properties: policyObject: description: 'Policy Object is a JSON representation of an A1 policy; the A1 policies are specified in A1TD [24]' type: object nearRtRicId: $ref: '#/components/schemas/NearRtRicId' policyTypeId: $ref: "#/components/schemas/policyTypeId" required: ["policyObject","nearRtRicId"] PolicyStatusSubscription: description: 'PolicyStatusSubscription data type represents the subscription information of A1 policy status' type: object properties: subscriptionScope: $ref: '#/components/schemas/QueryFilter' notificationDestination: type: URI description: URI for policy status notifications policyIdList: type: array items: $ref: '#/components/schemas/policyId' policyTypeIdList: type: array items: $ref: '#/components/schemas/ policyTypeId nearRtRicIdList: type: array items: $ref: '#/components/schemas/ nearRtRicId QueryFilter: type: string enum: - OWN #'indicate the A1 policies created by API Consumer ' - OTHERS #'indicate the A1 policies created other API Consumers' - ALL #'indicate the A1 policies created by any API Consumers' A.6 AI/ML workflow service A.6.1 AI/ML model registration API A.6.1.1 Introduction The Open API for the AI/ML model registration API is specified in clause A.6.1.2. A.6.1.2 AI/ML model registration API openapi: 3.0.3 info: title: 'AI/ML Model registration API ' version: 1.0.0 description: API for registering an AI/ML model| API for AI/ML Model registration service. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' url: 'https://www.o-ran.org/specifications' servers: - url: '{apiRoot}/ai-ml-model-registration/{apiVersion}' paths: '/model-registrations': post: description: 'Register a new AI/ML model' tags: - Registered AI/ML Model registration details requestBody: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 174 required: true content: application/json: schema: $ref: '#/components/schemas/ModelRelatedInformation' responses: '201': description: 'Success case 201 created' content: application/json: schema: $ref: '#/components/schemas/ModelRelatedInformation' headers: Location: description: 'Contains the URI of the newly created resource' required: true schema: type: string '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '405': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' '409': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/model-registrations/{modelRegistrationId}': get: summary: Get details of a registered AI/ML model parameters: - in: path name: modelRegistrationId required: true schema: type: string responses: '200': description: AI/ML model details retrieved successfully content: application/json: schema: $ref: '#/components/schemas/ModelRelatedInformation' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '405': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' '409': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': ETSI ETSI TS 104 231 V8.0.0 (2026-03) 175 $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' put: summary: Update information of a registered AI/Ml model parameters: - in: path name: modelRegistrationId required: true schema: type: string requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ModelRelatedInformation' responses: '200': description: AI/ML model information updated successfully content: application/json: schema: $ref: '#/components/schemas/ModelRelatedInformation' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '405': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' '409': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' delete: summary: Deregister an AI/ML model parameters: - in: path name: modelRegistrationId required: true schema: type: string responses: '204': description: AI/ML model deregistered successfully '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 176 components: schemas: ModelRelatedInformation: type: object properties: modelId: $ref: '#/components/schemas/ModelId' description: type: string modelInformation: $ref: '#/components/schemas/ModelInformation' modelLocation: type: string format: uri required: - modelId - description - modelInformation ModelId: type: object description: 'Identifier of a model' properties: modelName: type: string description: 'name of AI/ML model as specified in R1GAP' modelVersion: type: string description: 'version of AI/ML model as specified in R1GAP' artifactVersion: type: string format: uri description: 'artifact version of AI/ML model as specified in R1GAP' required: - modelName - modelVersion ModelInformation: type: object properties: metadata: description: 'Meta data of AI/Ml Model' $ref: '#/components/schemas/MetaData' inputDataType: type: array description: 'Input data type for the model, the structure of dataTypeId is specified in clause 7.1.8' items: $ref: 'O-RAN.WG2.R1AP_DataRegistration.yaml#/components/schemas/DataTypeId' # DataTypeId is specified (clause 7.1.8) outputDataType: type: array description: 'Output data type for the model, the structure of dataTypeId is specified in (clause 7.1.8)' items: $ref: 'O-RAN.WG2.R1AP_DataRegistration.yaml#/components/schemas/DataTypeId' # DataTypeId is specified (clause 7.1.8) targetEnvironment: type: array description: 'Information on the target environment is required for deployment of an AI/ML model' items: $ref: '#/components/schemas/TargetEnvironment' required: - metadata - inputDataType - outputDataType MetaData: type: object properties: author: type: string description: 'Author of an AI/ML model' owner: type: string required: - author TargetEnvironment: type: object properties: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 177 platformName: type: string description: 'Name of the platform' environmentType: type: string description: 'Name of the platform execution service type, and this is dependent on the platformName' dependencyList: type: string format: uri description: 'Location to the template that has all the list of dependencies platform must provide needs to be installed for the model. (for example, scikit-learn 0.21.3)' required: - platformName - environmentType - dependencyList A.6.2 AI/ML model discovery API A.6.2.1 Introduction The Open API for the AI/ML model discovery API is specified in clause A.6.2.2. A.6.2.2 AI/ML model discovery API openapi: 3.0.3 info: title: 'AI/ML Model discovery API' version: 1.0.0 description: | API for AI/Ml Model discovery service. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' url: 'https://www.o-ran.org/specifications' servers: - url: '{apiRoot}/ai-ml-model-discovery/v1' variables: apiRoot: description: 'apiRoot as defined in clause 10.3 in O-RAN.WG2.R1AP' default: 'https://example.com' paths: '/models': get: description: 'This operation retrieves all registered AI/ML models' parameters: - name: model-name in: query description: 'name of the model as specified in R1GAP[5]' schema: type: string - name: model-version in: query description: 'name of the model as specified in R1GAP[5]' schema: type: string responses: '200': description: 'The response body contains the result of the search over the list of ModelRelatedInformation that includes the modelId and metadata..' content: application/json: schema: type: array items: $ref: '#/components/schemas/ModelRelatedInformation' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': ETSI ETSI TS 104 231 V8.0.0 (2026-03) 178 $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '414': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/414' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' tags: - AI/ML Model Discovery components: schemas: ModelRelatedInformation: type: object description: "The ModelRelatedInformation data type represents registration information for an AI/ML model." required: - modelId - metadata properties: modelId: $ref: 'O-RAN.WG2.R1AP_AI/Ml_model_registrtaion_API.yaml/components/schemas/ModelId' description: "Identifier of a model as specified in clause 10.1.8.1.3" metadata: type: string description: "Description of the AIML model that includes the AI/ML model related information and training related information." A.6.3 AI/ML model training API A.6.3.1 Introduction The Open API for the AI/Ml model API is specified in clause A.6.3.2. A.6.3.2 AI/ML model training API openapi: 3.0.3 info: title: 'AI/ML Model Training API' version: 1.0.0-alpha.1 description: | API for AI/Ml Model training service. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' url: 'https://www.o-ran.org/specifications' servers: - url: '{apiRoot}/ai-ml-model-training/v1' variables: apiRoot: description: 'apiRoot as defined in clause 10.3 in O-RAN.WG2.R1AP' default: 'https://example.com' paths: '/training-jobs': post: summary: Create a new AI/ML model training job tags: - Creation of AI/ML model training job requestBody: required: true content: application/json: schema: $ref: "#/components/schemas/TrainingJobDescription" ETSI ETSI TS 104 231 V8.0.0 (2026-03) 179 responses: '201': description: 'Success case 201 created' content: application/json: schema: $ref: '#/components/schemas/TrainingJobInfo' headers: Location: description: 'Contains the URI of the newly created resource' required: true schema: type: string '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '405': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' '409': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' '413': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' '415': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/training-jobs/{trainingJobId}': delete: summary: 'Delete an AI/ML model training job' tags: - Delete AI/ML model training job responses: '204': description:'The AI/ML model training job wasI/ML deleted' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' '/training-jobs/{trainingJobId}/status': get: summary: Get the status of an AI/ML model training job tags: - Status of AI/ML model training job parameters: - in: path name: trainingJobId required: true schema: type: string responses: '200': description: 'Training job status retrieved successfully' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 180 content: application/json: schema: type: array items: $ref: '#/components/schemas/TrainingJobStatus' '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '406': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' '429': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' '502': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' '503': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' components: schemas: TrainingJobDescription: type: object properties: modelId: $ref: "#O-RAN.WG2.R1AP_ai_ml_model_registration.yaml/components/schemas/modelId" description: "The model identifier which contains model name, model version, and artifact version see clause 10.1.8.1.3-1 in R1AP." modelLocation: type: string format: uri description: "Location of the AI/ML model." trainingDataset: type: string format: uri description: "Information for reference to the training dataset." validationDataset: type: string format: uri description: "Information for reference to the validation dataset." trainingConfig: type: object description: "Configuration of AI/ML model training based on training service producer specific trainingConfigSchema." notificationDestination: type: string format: uri description: "Callback URI where the notification should be delivered to." consumerRAppId: type: string description: "rAppId of the training service consumer rApp." producerRAppId: type: string description: "rAppId of the training service producer rApp." required: - modelId A.6.4 AI/ML model deployment API A.6.4.1 Introduction The Open API for the AI/Ml model deployment API is specified in clause A.6.4.2. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 181 A.6.4.2 AI/ML model deployment API openapi: 3.0.3 info: title: 'AI/ML Model Deployment API' version: 1.0.0-alpha.1 description: | API for AI/ML Model Deployment service. © 2025, O-RAN ALLIANCE. All rights reserved. externalDocs: description: 'O-RAN.WG2.R1AP-v08.00' url: 'https://www.o-ran.org/specifications' servers: - url: '{apiRoot}/ai-ml-model-deployment/v1' variables: apiRoot: description: 'apiRoot as defined in clause 5.2 in O-RAN.WG2.R1AP' default: 'https://example.com' paths: '/model-deployments': post: summary: Request AI/ML model deployment tags: - Request AI/ML model deployment requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ModelDeploymentInformation' responses: '201': description: 'AI/ML model deployment created successfully' content: application/json: schema: $ref: '#/components/schemas/ModelDeploymentInformation' headers: Location: description: 'URI of the created deployment resource' required: true schema: type: string '400': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' '401': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' '403': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' '404': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' '500': $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' components: schemas: ModelDeploymentInformation: type: object properties: modelId: $ref: '#/components/schemas/ModelId' description: 'Unique identifier for the AI/ML model.' deploymentLocation: type: string format: uri description: 'URI for the deployment location.' deploymentConfig: type: object description: 'Configuration parameters for AI/ML model deployment. required: - modelId - deploymentLocation DeploymentStatus: type: object properties: ETSI ETSI TS 104 231 V8.0.0 (2026-03) 182 deploymentId: type: string description: 'Identifier for the AI/ML model deployment.' status: type: string description: 'Current status of the deployment.' details: type: string description: 'Additional details about the deployment status.' ETSI ETSI TS 104 231 V8.0.0 (2026-03) 183 Annex B (normative): Common data types for R1 service APIs B.1 Introduction In the subsequent clauses, common data types for the following areas are defined: • Generic usage. • Service management and exposure. • Data management and exposure. • RAN OAM. B.2 Common data types for generic usage B.2.1 Introduction This clause defines common data types for generic usage. B.2.2 Simple data types Table B.2.2-1: Simple data types for generic use Type name Type Definition Description Uri string A string formatted according to IETF RFC 3986 [8]. B.2.3 Enumeration B.2.3.1 Void B.2.4 Structured data types B.2.4.1 Data type: ProblemDetails The ProblemDetails structure is specified in Table B.2.4.1-1. It is based on IETF RFC 7807 [10] and shall comply with the provisions defined there. Table B.2.4.1-1: Definition of type ProblemDetails Attribute name Data type P Cardinality Description type string O 0..1 URI reference according to IETF RFC 3986 [8] that identifies the problem type. title string O 0..1 Human-readable summary of the problem type. status number O 0..1 The HTTP status code. detail string O 0..1 Human-readable explanation. instance string O 0..1 URI reference that identifies the specific occurrence of the problem. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 184 B.2.4.2 Void B.2.4.3 Void B.2.4.4 Void B.2.5 Re-used data types Re-used data types are not defined in the present document. B.3 Common data types for Service management and exposure B.3.1 Introduction This clause defines common data types for usage in the service management and exposure APIs. Clause B.3.5 references and profiles data types defined in external specifications and defines restrictions on and adaptations of these data type for their usage within the context of the service management and exposure APIs. B.3.2 Simple data types None. B.3.3 Enumerations None. B.3.4 Structured data types B.3.4.1 Data type: VersionExtensions The VersionExtensions data structure specified in Table B.3.4.1-1 defines extensions to the CAPIF "Version" data type which allows to signal the versions supported for an interface endpoint. Table B.3.4.1-1: Definition of type VersionExtensions Attribute name Data type P Cardinality Description fullApiVersions array(string) M 1..N List of version strings, as defined in clause 5.2, to signal the API versions supported by the API Producer for a particular major API version. B.3.4.2 Data type: ServiceProperties The ServiceProperties data structure specified in Table B.3.4.2-1 defines a container to be used to register and discover service-specific properties of individual service APIs. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 185 Table B.3.4.2-1: Definition of type ServiceProperties Attribute name Data type P Cardinality Description serviceCapabilities object M 0..1 Service capabilities. The content of this attribute is service-specific and is defined per service. B.3.5 Re-used data types Table B.3.5-1 references data types that are reused from external documents by the service management and exposure APIs and defines restrictions on and adaptations of these data type for their usage within the context of the service management and exposure APIs. NOTE: All externally-defined data types that are directly used in request or response message content of the service management and exposure APIs (such as ServiceAPIDescription) are listed below. In addition, those externally-defined data types are listed that are descendants of a directly used data type and for which restrictions and adaptations are defined in the present document. Other external descendant data types are not listed, as they are referenced directly in the external specification. Table B.3.5-1: Re-used data types Data type Reference Comments Applicability ServiceAPIDescription ETSI TS 129 222 [9], clause 8.2.4.2.2 The following attributes are not applicable in the context of the R1 SME services and therefore need not be supported: "supportedFeatures", "shareableInfo", "serviceAPICategory", "ccfId", "apiSuppFeats", "pubApiPath". InterfaceDescription ETSI TS 129 222 [9], clause 8.2.4.2.3 The CAPIF feature "ExtendedIntfDesc" shall be supported. AefProfile ETSI TS 129 222 [9], clause 8.2.4.2.4 The AEF profile holds information related to the discoverable APIs produced by a single API Producer. In case the API Producer is an rApp, the "aefId" attribute shall contain the value of the rAppID. The following attributes are not applicable in the context of the R1 SME services and need therefore not be supported: "aefLocation", "domainName""serviceKpis", and "ueIpRange". Version ETSI TS 129 222 [9], clause 8.2.4.2.5 The following additional attribute shall be supported: "vendorSpecific-o-ran.org" of type VersionsList as specified in clause B.3.4.1, to signal the full API versions supported. CAPIFEvent ETSI TS 129 222 [9], clause 8.3.4.3.3 The enumeration values "SERVICE_API_AVAILABLE", "SERVICE_API_UNAVAILABLE" and "SERVICE_API_UPDATE" shall be supported. The remaining enumeration values are not applicable in the context of the R1 SME services and therefore need not be supported. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 186 B.4 Common data types for Data Management and Exposure B.4.1 Introduction This clause defines common data types for DME usage. B.4.2 Simple data types Table B.4.2-1: Simple data types Type Name Type Definition Description DmeTypeId string A DME type Id is constructed based on the three parts separated by ":" (colon): {dataTypeId} = {namespace}:{name}:{version}. See clause B.4.4.1 for the definition of "namespace", "name" and "version". B.4.3 Enumerations B.4.3.1 Enumeration: DataDeliveryMethod Table B.4.3.1-1: Enumeration: DataDeliveryMethod Enumeration value Description STREAMING_KAFKA Kafka based streaming delivery mechanism as defined in R1TP [7], clause 6. PULL_HTTP HTTP based pull delivery mechanism as defined in clause 7.5. PUSH_HTTP HTTP based push delivery mechanism as defined in clause 7.4. B.4.4 Structured data types B.4.4.1 Data type: DmeTypeIdStruct The DmeTypeIdStruct data type contains the attributes defined in Table B.4.4.1-1. Table B.4.4.1-1: Definition of type DmeTypeIdStruct Attribute Name Data type P Cardinality Description namespace string M 1 Indicating the entity responsible for the DME type definition. name string M 1 Name of the DME type. The string shall not contain the colon ":" character. version string M 1 Version of the DME type. The versioning and allowed characters are according to SemVer [11]. B.4.4.2 Data type: DataDeliveryMechanism The DataDeliveryMechanism data type contains the attributes defined in Table B.4.4.2-1. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 187 Table B.4.4.2-1: Definition of type DataDeliveryMechanism Attribute Name Data type P Cardinality Description dataDeliveryMethod DataDeliveryMethod M 1 Delivery method supported by a Data Producer. See clause B.4.3.1. kafkaDeliveryConfiguration KafkaDeliveryConfiguration C 0..1 See clause B.4.4.3 (see note). NOTE: This attribute shall be presented if the "deliveryMethod" attribute is set to STREAMING_KAFKA. B.4.4.3 Data type: KafkaDeliveryConfiguration The KafkaDeliveryConfiguration data type contains the attributes defined in Table B.4.4.3-1. Table B.4.4.3-1: Definition of type KafkaDeliveryConfiguration Attribute Name Data type P Cardinality Description numPartitions integer O 0..1 Number of partitions. cleanUpPolicy string M 1 cleanUpPolicy is based on cleanup.policy defined in the Kafka Documentation [15]. compressionType string M 1 compressionType is based on compression.type defined in the Kafka Documentation [15]. retentionBytes integer C 0..1 retentionBytes is based on retention.bytes defined in the Kafka Documentation [15]. retentionMs integer C 0..1 retentionMs is based on retention.ms defined in the Kafka Documentation [15]. NOTE: Presence condition "C" this attribute may be included when cleanUpPolicy is set to DELETE. B.4.5 Re-used data types Re-used data types are not defined in the present document. B.5 Common data types for RAN OAM related services B.5.1 Introduction This clause defines common data types for usage in the RAN OAM related service APIs. Clause B.5.5 references and profiles data types defined in external specifications and defines restrictions on and adaptations of these data type for their usage within the context of the RAN OAM related APIs. B.5.2 Simple data types None. B.5.3 Enumerations None. B.5.4 Structured data types None. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 188 B.5.5 Re-used data types Table B.5.5-1 references data types that are reused from external documents by the RAN OAM related service APIs and defines restrictions on and adaptations of these data type for their usage within the context of the RAN OAM related APIs. NOTE: All externally defined data types that are directly used in request or response message content of the RAN OAM related service APIs are listed below. In addition, those externally defined data types are listed that are descendant of a directly used data type and for which restrictions and adaptations are defined in the present document. Other external ancestor data types are not listed, as they are referenced directly in the external specification. Table B.5.5-1: Re-used data types Data type Reference Comments Applicability Resource ETSI TS 128 532 [20], clause 12.1.1.4.1a.1 All the attributes are supported. Scope ETSI TS 128 532 [20], clause 12.1.1.4.1a.2 All the attributes are supported. PatchItem ETSI TS 128 532 [20], clause 12.1.1.4.1a.9 All the attributes are supported. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 189 Annex C (informative): Bibliography • ETSI GS NFV-SOL 015 (V1.2.1): "Protocols and Data Models; Specification of Patterns and Conventions for RESTful NFV-MANO APIs". ETSI ETSI TS 104 231 V8.0.0 (2026-03) 190 Annex D (informative): Change history Date Version Information about changes 2025.03.14 V08.00 Published with updating the Bootstrap API, RAN OAM CM API's, RAN OAM FM API's, Adding Configuration schema information API, AI/ML Model deployment API, AI/Ml model retrieve API, Updates to AI/ML model registration API, AI/Ml model discovery API and AI/ML model training API. 2024.11.21 V07.00 Published with migration of all API's from Release 17 to Release 18 of 3GPP, Updated the A1 Policy management API and Model discovery API and moved the same to release version, Updated the Data registration API, Data access API and Data offer API by removing the consumerId from the uri structure. 2024.07.18 V06.00 Published with addition of Bootstrap API in SME, AI/ML model registration, AI/ML model discovery, AI/ML model training API in AI/ML workflow service, Updated A1 policy management API, Uplifted all the DME, AI/ML,A1 policy management APIs in compliance with 29.501 URI Structure, and generalized the DME API to support further enhancements. Updated the naming of data type to DME type. 2024.03.18 V05.00 Published with addition of A1 policy management API, RAN OAM CM and FM API, updates to data registration API and removing alpha indicator for data registration API. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 191 History Version Date Status V8.0.0 March 2026 Publication |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 1 Scope | The present document specifies the protocol conformance testing for testing a MCVideo Server for compliance to the Mission Critical Video (MCVideo) over LTE protocol requirements defined by 3GPP. The present document addresses only MCVideo Server-Server communication scenarios. It does not cover e.g. MCVideo Server-EPS, MCVideo Server- SIP Core, etc. scenarios which involve interfaces which implementation may widely vary. In particular the present specification contains: • the overall test structure; • the test configurations; • the conformance requirement and reference to the core specifications; • the test purposes; and • a brief description of the test procedure, the specific test requirements and short message exchange table. The present document is valid for MCVideo Servers implemented according to 3GPP releases starting from Release 14 up to the Release indicated on the cover page of the present document. The following information relevant to testing specified in the present document could be found in accompanying specifications: • default setting of the test parameters ETSI TS 136 579-1 [1] (3GPP TS 36.579-1); • Implementation Conformance Statement (ICS) ETSI TS 136 579-4 [2] (3GPP TS 36.579-4) and Implementation extra Information for Testing (IXIT) ETSI TS 136 579-5 [i.4] (3GPP TS 36.579-5); • the applicability of each test case ETSI TS 136 579-4 [2] (3GPP TS 36.579-4). The present document does not specify the protocol conformance testing for the EPS (LTE) bearers which carry the MCVideo data sent or received by the MCVideo Server. The specification of such testing is out of the scope of RAN5. |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 2 References | |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 136 579-1: "LTE; Mission Critical (MC) services over LTE; Part 1: Common test environment (3GPP TS 36.579-1)". [2] ETSI TS 136 579-4: "LTE; Mission Critical (MC) services over LTE; Part 4: Test Applicability and Implementation Conformance Statement (ICS) proforma specification (3GPP TS 36.579-4)". [3] ETSI TS 124 379: "LTE; Mission Critical Push To Talk (MCPTT) call control; Protocol specification (3GPP TS 24.379)". [4] ETSI TS 133 180: "LTE; Security of the Mission Critical (MC) service (3GPP TS 33.180)". ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 14 [5] ETSI TS 124 281: "LTE; Mission Critical Video (MCVideo) signalling control; Protocol specification (3GPP TS 24.281)". [6] ETSI TS 124 581: "LTE; Mission Critical Video (MCVideo) media plane control; Protocol specification (3GPP TS 24.581)". [7] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol". [8] IETF RFC 4028 (April 2005): "Session Timers in the Session Initiation Protocol (SIP)". [9] ETSI TS 126 114: "Universal Mobile Telecommunications System (UMTS); LTE; 5G; IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction (3GPP TS 26.114)". [10] IETF RFC 4867 (April 2007): "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs". [11] IETF RFC 6335 (August 2011): "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry". [12] IETF RFC 3556 (July 2003): "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". [13] IETF RFC 4412 (February 2006): "Communications Resource Priority for the Session Initiation Protocol (SIP)". [14] IETF RFC 8101 (March 2017): "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk service". [15] IETF RFC 7134 (March 2014): "The Management Policy of the Resource Priority Header (RPH) Registry Changed to "IETF Review"". [16] IETF RFC 5621 (September 2009): "Message Body Handling in the Session Initiation Protocol (SIP)". [17] IETF RFC 3903 (October 2004): "Session Initiation Protocol (SIP) Extension for Event State Publication". [18] IETF RFC 6184 (May 2011): "RTP Payload Format for H.264 Video". [19] ETSI TS 124 282: "LTE; Mission Critical Data (MCData) signalling control; Protocol specification (3GPP TS 24.282)". [20] ETSI TS 136 509: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Special conformance testing functions for User Equipment (UE) (3GPP TS 36.509)". |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; Vocabulary for 3GPP Specifications (3GPP TR 21.905)". ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 15 [i.2] ETSI TS 136 579-2: "LTE; Mission Critical (MC) services over LTE; Part 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specification (3GPP TS 6.579-2)". [i.3] ETSI TS 136 579-3: "LTE; Mission Critical (MC) services over LTE; Part 3: Mission Critical Push To Talk (MCPTT) Server Application conformance specification (3GPP TS 36.579-3)". [i.4] ETSI TS 136 579-5: "LTE; Mission Critical (MC) services over LTE; Part 5: Abstract test suite (ATS) (3GPP TS 36.579-5)". [i.5] ETSI TS 136 579-6: "LTE; Mission Critical (MC) services over LTE; Part 6: Mission Critical Video (MCVideo) User Equipment (UE) Protocol conformance specification (3GPP TS 36.579-6)". [i.6] ETSI TS 136 579-7: "LTE; Mission Critical (MC) services over LTE; Part 7: Mission Critical Data (MCData) User Equipment (UE) Protocol conformance specification (3GPP TS 36.579-7)". [i.7] 3GPP TS 36.579-9: "Mission Critical (MC) services over LTE; Part 9: Mission Critical Data (MCData) Server Application conformance specification". [i.8] 3GPP TS 36.579-8: "Mission Critical (MC) services over LTE; Part 8: Mission Critical Video (MCVideo) Server Application conformance specification". |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 3 Definitions of terms, symbols and abbreviations | |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply: NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). For the purpose of the present document, the following terms given in ETSI TS 124 281 [5] (3GPP TS 24.281) apply: • An MCVideo user is affiliated to an MCVideo group • An MCVideo user is affiliated to an MCVideo group at an MCVideo client • Affiliation status • Group identity • MCVideo client ID • MCVideo emergency alert state • MCVideo emergency group state • MCVideo emergency group call state • MCVideo emergency private call • MCVideo emergency private call state • MCVideo emergency private priority state • MCVideo imminent peril group call state • MCVideo imminent peril group state • MCVideo private call ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 16 • MCVideo private emergency alert state • MCVideo video media • Media-transmission control entity • Private call • Remote change of an MCVideo user's selected group • Temporary MCVideo group identity • Trusted mutual aid • Untrusted mutual aid For the purpose of the present document, the following terms given in ETSI TS 133 180 [4] (3GPP TS 33.180) apply: • Client Server Key (CSK) • Private Call Key (PCK) • Signalling Protection Key (SPK) • XML Protection Key (XPK) |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 3.2 Symbols | Void. |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply: NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). CSK Client-Server Key GKTP Group Key Transport Payload GMOP Group Management OPeration ICS Implementation Conformance Statement IUT Implementation Under Test IXIT Implementation eXtra Information for Testing MBMS Multimedia Broadcast and Multicast Service MC Mission Critical MCData Mission Critical Data MCPTT Mission Critical Push To Talk MCS Mission Critical Service MCVideo group ID MCVideo group Identity MCVideo Mission Critical Video MIME Multipurpose Internet Mail Extensions MVEA MCVideo Emergency Alert MVEG MCVideo Emergency Group MVEGC MCVideo Emergency Group Call MVIG MCVideo Imminent peril Group MVIGC MCVideo Imminent peril Group Call NAT Network Address Translation PCK Private Call Key PIDF Presence Information Data Format RTP Real-time Transport Protocol SDP Session Description Protocol ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 17 SIP Session Initiation Protocol SPK Signalling Protection Key SS System Simulator SSRC Synchronization SouRCe TGI Temporary MCVideo Group Identity TP Test Purpose TP Transmission Point UE User Equipment URI Uniform Resource Identifier XCAP eXtensible Markup Language (XML) Access Configuration Protocol XPK XML Protection Key |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 4 General | |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 4.1 Test methodology | |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 4.1.1 Testing of optional functions and procedures | Any function or procedure which is optional, may be subject to a conformance test if it is implemented in the MCVideo Server. A declaration by the MCVideo Server supplier (to use the Implementation Conformance Statement (ICS) proforma specified in ETSI TS 136 579-4 [2] (3GPP TS 36.579-4)) is used to determine whether an optional function/procedure has been implemented. |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 4.1.2 Test interfaces and facilities | Detailed descriptions of the MCVideo test interfaces and special facilities for testing are provided in ETSI TS 136 509 [20] (3GPP TS 36.509). |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 4.2 Implicit testing | For some 3GPP MCVideo protocol features conformance is not verified explicitly in the present document. This does not imply that correct functioning of these features is not essential, but that these are implicitly tested to a sufficient degree in tests which are not explicitly dedicated to test the feature. |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 4.3 Repetition of tests | As a general rule, the test cases specified in the present document are highly reproducible and do not need to be repeated unless otherwise stated. 4.4 Handling of differences between conformance requirements in different releases of core specifications The conformance requirements which determine the scope of each test case are explicitly copy-pasted from relevant core specifications in the especially dedicated for this clause of each test with the title 'Conformance requirements'. NOTE: When in the copy/pasted text there are references to other specifications the reference numbers will not match the reference numbers used in the present document. This approach has been taken in order to allow easy copy and then search for conformance requirements in those specifications. When differences between conformance requirements in different releases of the cores specifications have impact on the Pre-test conditions, Test procedure sequence or/and the Specific message contents, the Conformance requirements related to different releases are specified separately with clear indication of the Release of the spec from which they were copied. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 18 When there is no Release indicated for a conformance requirement text, this should be understood either as the Conformance requirements in the latest version of the spec with release = the TC Applicability release (which can be found in ETSI TS 136 579-4 [2] (3GPP TS 36.579-4), Table 4-1: Applicability of tests and additional information for testing, column 'Release'), or, as the Conformance requirements in the latest version of the spec of the release when the feature was introduced to the core specs. |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 4.5 Reference conditions | The reference environments used by all signalling and protocol tests is specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1). Where a test requires an environment that is different, this will be specified in the test itself. For all test cases in the present document unless specified otherwise the condition MCVIDEO applies for all message contents. |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 4.6 Generic setup procedures | A set of basic generic procedures for MCVideo Client-Server communication are described in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1). These procedures will be used in numerous test cases throughout the present document. |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5 MCVideo Server - MCVideo Server operation | |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1 Group Calls | |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1 Pre-arranged Group Call | 5.1.1.1 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Upgrade to Emergency Group Call / Cancel Emergency State / Upgrade to Imminent Peril Group call / Cancel Imminent Peril State / Controlling server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.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 pre- arranged group call with implicit transmission control } then { IUT (MCVideo Server) accepts the call from initiator and establishes the call with all affiliated users by sending call establishment requests to 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 pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) sends transmission control idle to SS-UE1 (MCVideo Client) and sends transmission control idle to SS-UE2 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 19 (3) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control } then { IUT (MCVideo Server) sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } (4) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function upgrades the call to emergency group call with implicit transmission control } then { IUT (MCVideo Server) accepts the upgrade from the initiator and updates the call for all participants and sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } (5) with { IUT (MCVideo Server) having upgraded to an emergency pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function requests to cancel the ongoing emergency state } then { IUT (MCVideo Server) accepts the emergency state cancellation and updates the call for all participants } } (6) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function upgrades the call to imminent peril group call with implicit transmission control } then { IUT (MCVideo Server) accepts the upgrade from the initiator and updates the call for all participants and sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } (7) with { IUT (MCVideo Server) having upgraded to an imminent peril pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function requests to cancel the ongoing imminent peril state } then { IUT (MCVideo Server) accepts the imminent peril state cancellation and updates the call for all participants } } (8) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function ends the pre- arranged group 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.1.1.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 9.2.1.4.2, 9.2.1.4.3, 9.2.1.4.7, 9.2.1.4.8, 9.2.1.4.1.1, 9.2.1.4.1.2, 6.3.3.1.6, 6.3.3.1.11, 6.3.3.1.12.2, 6.3.3.1.12.3, 6.3.3.1.12.4, 6.3.3.1.12.5, 6.3.3.2.1, 6.3.3.2.2, 6.3.3.2.4, 6.3.3.4 and 6.3.5.5, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.3.1, 6.3.2.2, 9.2.1, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 20 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.2] "In the procedures in this clause: 1) MCVideo ID in an incoming SIP INVITE request refers to the MCVideo ID of the originating user from the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 3) MCVideo ID in an outgoing SIP INVITE request refers to the MCVideo ID of the called user in the <mcvideo- request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) indication of required group members in a SIP 183 (Session Progress) response refers to the <required> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to "true" in a SIP 183 (Session Progress) sent by the non-controlling MCVideo function of an MCVideo group; 5) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 6) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for controlling MCVideo function of an MCVideo group", the controlling MCVideo function: … 2) shall determine if the media parameters are acceptable and the MCVideo codecs are offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps; 3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if: a) an Accept-Contact header field does not include the g.3gpp.mcvideo media feature tag; or b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; 4) if received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; 5) shall retrieve the necessary group document(s) from the group management server for the group identity contained in the SIP INVITE request and carry out initial processing as specified in clause 6.3.5.2; 6) if the result of the initial processing in clause 6.3.5.2 was: a) that authorization of the MCVideo ID is required at a non-controlling MCVideo function of an MCVideo group is required, perform the actions in clause 6.3.3.1.13.7 and do not continue with the rest of the steps in this clause; and b) that a SIP 3xx, 4xx, 5xx or 6xx response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group" has been sent, do not continue with the rest of the steps in this clause; 7) shall perform the actions as described in clause 6.3.3.2.2; 8) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero; 9) shall determine if an MCVideo group call for the group identity is already ongoing by determining if an MCVideo session identity has already been allocated for the group call and the MCVideo session is active; … ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 21 12) if a Resource-Priority header field is included in the SIP INVITE request: a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; or b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; 13) if the MCVideo group call is not ongoing then: … c) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined as determined in step 13) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; d) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; e) shall create a prearranged group session and allocate an MCVideo session identity for the prearranged group call, and shall handle timer TNG3 (group call timer) as specified in clause 6.3.3.5; f) if the group identity in the "SIP INVITE request for controlling MCVideo function of an MCVideo group" is a TGI: i) shall for each of the constituent MCVideo groups homed on the primary MCVideo system: …; B) if the controlling MCVideo function owns the MCVideo group identified by the MCVideo group ID then: I) determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; II) invite each group member determined in step A) above, to the group session, as specified in clause 9.2.1.4.1.1; and III) interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and ii) shall for each of the constituent MCVideo groups homed on the partner MCVideo system generate a SIP INVITE request for the MCVideo group identity homed on the partner MCVideo system as specified in clause 9.2.1.4.1.2; and g) if the group identity in the SIP INVITE request for controlling MCVideo function of an MCVideo group is an MCVideo group ID: i) shall determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; ii) if necessary, shall start timer TNG1 (acknowledged call setup timer) according to the conditions stated in clause 6.3.3.3; iii) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": A) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 22 B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; and C) if the in-progress emergency state of the group is set to a value of "false": I) shall set the value of the in-progress emergency state of the group to "true"; and II) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; iv) if the in-progress emergency state of the group is set to a value of "false" and if the received SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function shall: A) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and B) if the in-progress imminent peril state of the group is set to a value of "false", shall set the in- progress imminent peril state of the group to a value of "true"; v) shall invite each group member determined in step 13)g)i) above, to the group session, as specified in clause 9.2.1.4.1.1; and vi) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and 14) if the MCVideo group call is ongoing then: … c) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; … e) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined in step 14) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; f) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": i) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; iii) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; and C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.6; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 23 iv) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and v) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; g) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function: i) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and ii) if the in-progress imminent peril state of the group is set to a value of "false": A) shall set the in-progress imminent peril state of the group to a value of "true"; B) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.15; and C) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and iii) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; h) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.4.2; i) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; j) shall include in the SIP 200 (OK) response with the warning text set to "123 MCVideo session already exists" as specified in clause 4.4; k) if the received SIP re-INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; l) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 4: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. m) shall interact with media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 5: Resulting media plane processing is completed before the next step is performed. n) shall send the SIP 200 (OK) response towards the inviting MCVideo client or inviting non-controlling MCVideo function according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 24 o) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; NOTE 6: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. p) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]; q) Upon receiving a SIP ACK to the above SIP 200 (OK) response and the SIP 200 (OK) response contained a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall follow the procedures in clause 6.3.3.1.18; and r) shall not continue with the rest of the clause. Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 9.2.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [30], the timer TNG1 (acknowledged call setup timer) is not running, the controlling MCVideo function supports media buffering and the SIP final response is not yet sent to the inviting MCVideo client: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) shall include a P-Answer-State header field with the value "Unconfirmed"; 5) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 7: Resulting user plane processing is completed before the next step is performed. 8) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; 9) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 8: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 10) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response for a SIP INVITE request as specified in clause 9.2.1.4.1.2 containing an indication of required group members, the timer TNG1 (acknowledged call setup timer) is running and all SIP 200 (OK) responses have been received to all SIP INVITE requests sent to MCVideo clients specified in clause 9.2.1.4.1.1, then the controlling MCVideo function shall wait until the SIP 200 (OK) response has been received to the SIP INVITE request specified in clause 9.2.1.4.1.2 before generating a SIP 200 (OK) response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group". ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 25 Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1 that was sent to an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24]; and 1) if the MCVideo ID in the SIP 200 (OK) response matches to the MCVideo ID in the corresponding SIP INVITE request; 2) there are no outstanding SIP 200 (OK) responses to SIP INVITE requests which were sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24]; and 3) there is no outstanding SIP 200 (OK) response to a SIP INVITE request sent in clause 9.2.1.4.1.2 where the SIP 183 (Session Progress) response contained an indication of required group members; the controlling MCVideo function: 1) shall stop timer TNG1 (acknowledged call setup timer) as described in clause 6.3.3.3; 2) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 3) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has been exceeded the <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 4) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 5) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 9: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 7) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 10: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 8) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon: 1) receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1; 2) the timer TNG1 (acknowledged call setup timer) is not running; 3) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; 4) the controlling MCVideo function supports media buffering; and 5) the SIP final response has not yet been sent to the inviting MCVideo client; the controlling MCVideo function according to local policy: 1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has exceeded the <max- participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 26 4) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 5) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 11: Resulting media plane processing is completed before the next step is performed. 7) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 8) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 12: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 9) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon expiry of timer TNG1 (acknowledged call setup timer), if there are outstanding SIP 200 (OK) responses to SIP INVITE requests sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the procedures specified in clause 6.3.3.3. If timer TNG1 (acknowledged call setup timer) is running and a final SIP 4xx, 5xx or 6xx response is received from an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the relevant procedures specified in clause 6.3.3.3. If: 1) timer TNG1 (acknowledged call setup timer) is not running; 2) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; and 3) a final SIP 4xx, 5xx or 6xx response is received from an invited MCVideo client; then the controlling MCVideo function shall perform one of the following based on policy: 1) send the SIP final response towards the inviting MCVideo client, according to 3GPP TS 24.229 [11], if a SIP final response was received from all the other invited MCVideo clients and the SIP 200 (OK) response is not yet sent; or 2) remove the invited MCVideo client from the MCVideo Session as specified in clause 6.3.3.1.5, if a SIP final response other than 2xx or 3xx was received from all the invited MCVideo clients and the SIP 200 (OK) response is already sent. The controlling MCVideo function may invite an additional member of the prearranged MCVideo group as specified in clause 9.2.1.4.1 that has not already been invited, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24], and all members have not yet been invited. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.3] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 27 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.7] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a SIP re-INVITE request for an MCVideo session identity identifying an on-demand prearranged MCVideo group session, the controlling MCVideo function: … 2) if received SIP re-INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; … 4) if the received SIP re-INVITE request contains an imminent peril indication set to "true" for an MCVideo imminent peril group call and this is an unauthorised request for an MCVideo imminent peril group call as determined by clause 6.3.3.1.13.6, shall reject the SIP re-INVITE request … 5) if a Resource-Priority header field is included in the received SIP re-INVITE request: a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP re- INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP re-INVITE request … and skip the rest of the steps; and b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP re- INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request …and skip the rest of the steps; 6) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true" and is an authorised request to initiate an MCVideo emergency group call as determined by clause 6.3.3.1.13.2, the controlling MCVideo function shall: i) shall cache the MCVideo ID of the MCVideo user that has initiated an MCVideo emergency call; ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the MCVideo ID of the MCVideo user that has initiated an MCVideo emergency alert; iii) if the in-progress emergency state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's emergency indication as specified in clause 6.3.3.1.11, setting the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and C) if the in-progress imminent peril state of the group is set to a value of "true", shall set it to a value of "false"; and iv) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; NOTE 2: The interactions of TNG2 with the TNG3 (group call timer) are explained in clause 6.3.3.5.2. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 28 Editor's Note: timers need to be defined. C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other participants of the MCVideo group call as specified in clause 6.3.3.1.6; D) shall send the SIP re-INVITEs towards the other participants of the MCVideo group call; and E) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; 7) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is an unauthorised request for an MCVideo emergency group call cancellation as determined by clause 6.3.3.1.13.4: a) shall reject the SIP re-INVITE request. ... c) if an <alert-ind> element of the mcvideoinfo MIME body is included in the SIP re-INVITE request set to "false", and there is an outstanding MCVideo emergency alert for this MCVideo user, shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <alert-ind> element set to a value of "true"; and d) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [11] and skip the rest of the steps; 8) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is determined to be an authorised request for an MCVideo emergency call cancellation as specified in clause 6.3.3.1.16 and the in-progress emergency state of the group to is set to a value of "true" the controlling MCVideo function: a) shall set the in-progress emergency group state of the group to a value of "false"; b) shall clear the cache of the MCVideo ID of the MCVideo user as having an outstanding MCVideo emergency group call; c) if an <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body is included and set to "false" and is determined to be an authorised request for an MCVideo emergency alert cancellation as specified in clause 6.3.3.1.13.3 and there is an outstanding MCVideo emergency alert for this MCVideo user shall: i) if the received SIP re-INVITE request contains an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, clear the cache of the MCVideo ID of the MCVideo user identified by the <originated-by> element as having an outstanding MCVideo emergency alert; or ii) if the received SIP re-INVITE request does not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, clear the cache of the MCVideo ID of the sender of the SIP re-INVITE request as having an outstanding MCVideo emergency alert; d) shall generate SIP re-INVITE requests to the participants in the group call as specified in clause 6.3.3.1.6. The MCVideo controlling function: i) for each of the other participants in the group call shall send the SIP re-INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and ii) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; NOTE 3: Clause 6.3.3.1.5 will inform the group call participants of the cancellation of the MCVideo group's in- progress emergency state and the cancellation of the MCVideo emergency alert if applicable. e) shall stop timer TNG2 (in-progress emergency group call timer); and NOTE 4: The interactions of TNG2 with the TNG3 (group call timer) are explained in clause 6.3.3.5.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 29 f) for each of the affiliated members of the group that are not participating in the call: i) generate a SIP MESSAGE request notification of the cancellation of the MCVideo user's emergency call as specified in clause 6.3.3.1.11; ii) set the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; iii) if indicated above in step 8) c), set the <alert-ind> element of the application/vnd.3gpp.mcvideo- info+xml MIME body to a value of "false"; and iv) send the SIP MESSAGE request according to 3GPP TS 24.229 [11]; 9) if the received SIP re-INVITE request contains an imminent peril indication and the in-progress emergency group state of the group is set to a value of "false", shall perform the procedures specified in clause 9.2.1.4.8 and skip the rest of the steps. Upon receiving a SIP 200 (OK) response to a SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; 1) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [11]; 2) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [11] with the clarifications specified in clause 6.3.3.2.1; 3) shall include the "norefersub" option tag in a Supported header field according to IETF RFC 4488 [31]; 4) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [32]; 5) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "true" and if this is an unauthorised request for an MCVideo emergency alert as determined by clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "false" and if this is an unauthorised request for an MCVideo emergency alert cancellation as determined by clause 6.3.3.1.13.3, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true", this is an authorised request for an MCVideo imminent peril group call and the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 5: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. 8) shall interact with media plane as specified in 3GPP TS 24.581 [5]; and 9) shall send the SIP 200 (OK) response towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18. Upon receipt of a SIP 2xx response for an outgoing SIP MESSAGE request, shall handle according to 3GPP TS 24.229 [11]." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 30 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.8] "This procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.1.4.7. In the procedures in this clause: 1) imminent peril indication in an incoming SIP re-INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. When the controlling function receives a SIP re-INVITE request with an imminent peril indication set to "true", the controlling function: 1) if the in-progress emergency state of the group is set to a value of "false" and if the SIP re-INVITE request contains an imminent peril indication set to a value of "true" or the in-progress imminent peril state of the group to "true", the controlling MCVideo function shall: NOTE: 1 The calling procedure has already determined that this is not an unauthorised request for an MCVideo imminent peril call, therefore that check does not need to be repeated in the current procedure. a) if the in-progress imminent peril state of the group is set to a value of "true" and this MCVideo user is indicating a new imminent peril indication: i) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11 with the following clarifications; A) set the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; b) if the in-progress imminent peril state of the group is set to a value of "false"; i) set the value of the in-progress imminent peril state of the group to "true"; ii) generate SIP re-INVITE requests for the MCVideo imminent peril group call to participants in the MCVideo group call as specified in clause 6.3.3.1.15; iii) send the SIP re-INVITES to all of the other participants in the MCVideo group call; iv) for each of the affiliated members of the group not participating in the group call, generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11 with the following clarifications; A) set the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and c) cache the information that this MCVideo user has initiated an MCVideo imminent peril call; 2) if the SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "false" and is an unauthorised request for an MCVideo imminent peril group call cancellation as determined by clause 6.3.3.1.13.6 shall: a) reject the SIP re-INVITE request with a SIP 403 (Forbidden) response to the SIP re-INVITE request; and b) include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in Annex F.1 with the <mcvideoinfo> element containing the <mcvideo-Params> element with the <imminentperil-ind> element set to a value of "false"; c) send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [11]; and d) skip the rest of the steps; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 31 3) if the SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "false" and is determined to be an authorised request for an MCVideo imminent peril call cancellation as specified in clause 6.3.3.1.13.6 and the in-progress imminent peril state of the group to is set to a value of "true" the controlling MCVideo function shall: a) set the in-progress imminent peril state of the group to a value of "false"; b) cache the information that this MCVideo user no longer has an outstanding MCVideo imminent peril group call; c) generate SIP re-INVITES requests to the other participants in the MCVideo group call as specified in clause 6.3.3.1.15. The MCVideo controlling function: i) for each participant shall send the SIP re-INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and ii) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function interact with the media plane as specified in 3GPP TS 24.581 [5]; and NOTE 2: Clause 6.3.3.1.14 will inform the affiliated and joined members of the cancellation of the MCVideo group's in-progress emergency state and the cancellation of the MCVideo emergency alert if applicable. d) for each of the affiliated members of the group not participating in the call shall: i) generate a SIP MESSAGE request notification of the cancellation of the MCVideo user's imminent peril call as specified in clause 6.3.3.1.11; ii) set the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; and iii) send the SIP MESSAGE request according to 3GPP TS 24.229 [11]; 4) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [11] with the clarifications specified in clause 6.3.3.2.1; 5) shall include the "norefersub" option tag in a Supported header field according to IETF RFC 4488 [31]; 6) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [32]; 7) shall interact with media plane as specified in 3GPP TS 24.581 [5]; and 8) shall send the SIP 200 (OK) response towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receipt of a SIP 2xx response for an outgoing SIP MESSAGE request, shall handle according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.1.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.1.4.2 or as the result of receiving a SIP 403 (Forbidden) response as described in this clause. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited.; NOTE 1: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 2: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 32 3) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the MCVideo ID of the terminating user; and b) the <mcvideo-calling-group-id> element set to the group identity; NOTE 3: The <mcvideo-calling-user-id> is already included in the MIME body as a result of calling clause 6.3.3.1.2 in step 1). 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; 6) if the in-progress emergency state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.19; b) if the received SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true": i) shall include in the outgoing SIP INVITE request in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; and ii) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcvideo-info+xml MIME body and the application/vnd.3gpp.location- info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false"; and c) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.19; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; and 9) shall send the SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [11]. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 33 Upon receiving a SIP 183 (Session Progress) response containing a Require header field with the option tag "100rel" and containing a P-Answer-State header field with the value "Unconfirmed" in response to the SIP INVITE request the controlling MCVideo function: 1) shall send a SIP PRACK request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; 2) shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 9.2.3.4; and 3) shall increment the local counter of the number of SIP 200 (OK) responses received from invited members, by 1. NOTE 4: The notifications above could be sent prior to the SIP 200 (OK) response being sent to the inviting MCVideo client. These notifications received by MCVideo clients that are group members do not mean that the group session will be successfully established. NOTE 5: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.1.2] "The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the non-controlling MCVideo function serving the group identity of the MCVideo group owned by the partner MCVideo system; 3) shall set the P-Asserted-Identity to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the group identity of the MCVideo group hosted by the non- controlling MCVideo function in the partner MCVideo system; and b) the <mcvideo-calling-group-id> element set to the group identity of the group served by the controlling MCVideo function; 5) shall include the Recv-Info header field set to g.3gpp.mcvideo-transmission-request; 6) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 34 8) shall send the SIP INVITE request towards the partner MCVideo system in accordance with 3GPP TS 24.229 [11]. Upon receiving SIP 403 (Forbidden) response for the SIP INVITE request, if according to local policy and if: 1) the response contains a Warning header field with the MCVideo warning code "128"; and 2) the response contains a P-Refused-URI-List header field and an application/resource-lists+xml MIME body as specified in IETF RFC 5318 [28]; NOTE 1: The application/resource-lists+xml MIME body contains MCVideo IDs identifying MCVideo users in a partner MCVideo system that needs to be invited to the prearranged group call in case of group regrouping using interrogating method. Editor's Note: The above note currently isn't defined in the 23.280 and 23.281. then the controlling MCVideo function: 1) shall check if the number of members of the MCVideo group exceeds the value contained in the <on-network- max-participant-count> element of the group document as specified in 3GPP TS 24.481 [24]. If exceeded, the controlling MCVideo function shall invite only <on-network-max-participant-count> members from the application/resource-lists+xml MIME body; and NOTE 2: The <on-network-max-participant-count> element indicates the maximum number of participants allowed in the prearranged group session It is operator policy that determines which participants in the application/resource-lists+xml MIME body are invited to the group call. 2) shall invite MCVideo users as specified in this clause using the list of MCVideo IDs in URI-List. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and NOTE 3: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2. 2) if at least one of the invited MCVideo clients has subscribed to the conference package, shall subscribe to the conference event package in the non-controlling MCVideo function as specified in clause 9.2.3.4.3." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.6] "This clause is referenced from other procedures. This clause describes the procedures for inviting an MCVideo user to an MCVideo session associated with an MCVideo emergency group call or MCVideo imminent peril group call. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.2.4.1.1. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the address of the terminating participating MCVideo function associated with the MCVideo ID of the targeted MCVideo user; 3) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element populated as follows: a) the <mcvideo-request-uri> element set to the value of the MCVideo ID of the targeted MCVideo user; b) the <mcvideo-calling-user-id> element set to the value of the MCVideo ID of the calling MCVideo user; and c) the <mcvideo-calling-group-id> element set to the value of the MCVideo group ID of the emergency group call. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 35 4) shall include in the P-Asserted-Identity header field the public service identity of the controlling MCVideo function; 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and 6) if the in-progress emergency group state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.18; b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; c) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.12.1, shall populate the application/vnd.3gpp.mcvideo- info+xml MIME body and the application/vnd.3gpp.mcvideo-location-info+xml MIME body as specified in clause 6.3.3.1.11. Otherwise, shall set the <alert-ind> element to a value of "false" in the application/vnd.3gpp.mcvideo-info+xml MIME body; and d) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; NOTE: If the imminent peril state of the group is true at this point, the controlling function will set it to false as part of the calling procedure. 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.18; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; and 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains an <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.11] "This clause is referenced from other procedures. This clause describes the procedures for populating the application/vnd.3gpp.mcvideo-info+xml and application/vnd.3gpp.mcvideo-location-info+xml MIME bodies for an MCVideo emergency alert. The procedure is initiated by the controlling MCVideo function when it has received a SIP request initiating an MCVideo emergency alert and generates a message containing the MCVideo emergency alert information required by 3GPP TS 23.281 [26]. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 36 The controlling MCVideo function: 1) shall include, if not already present, an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in Annex F.1, and set the <alert-ind> element to a value of "true"; 2) shall determine the value of the MCVideo user's Mission Critical Organization from the <MissionCriticalOrganization> element, of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]); 3) shall include in the <mcvideoinfo> element containing the <mcvideo-Params> element containing an <mc- org> element set to the value of the MCVideo user's Mission Critical Organization; and 4) shall copy the contents of the application/vnd.3gpp.mcvideo-location-info+xml MIME body in the received SIP request into an application/vnd.3gpp.mcvideo-location-info+xml MIME body included in the outgoing SIP request." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.12.2] "If the controlling MCVideo function has received a SIP request for an MCVideo group call with the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of "true" and: 1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true" and: a) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and: i) if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) contains the identity of the MCVideo group targeted by the calling MCVideo user; and ii) if the <allow-MCVideo-emergency-call> element of the <list-service> element of the group document identified by the targeted MCVideo group identity is set to a value of "true" as specified in 3GPP TS 24.481 [24]; then the controlling MCVideo function shall consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call and skip the remaining steps; or; b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup" and if the <allow-MCVideo-emergency-call> element of the <list- service> element of the group document identified by the targeted MCVideo group identity is set to a value of "true" as specified in 3GPP TS 24.481 [24]; then the controlling MCVideo function shall consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call and skip the remaining steps; or 2) if the controlling MCVideo function does not consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call by step 1) above, then the controlling MCVideo function shall consider the MCVideo emergency group call request to be an unauthorised request for an MCVideo emergency group call. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 37 If the controlling MCVideo function has received a SIP request for an MCVideo private call with the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of "true" and: 1) if the <allow-emergency-private-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true"; and a) if the "entry-info" attribute of the <entry> element of the <MCVideoPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UsePreConfigured" and if the MCVideo ID targeted for the call is contained in the <uri-entry> element of the <entry> element of the <MCVideoPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element (see the MCVideo user profile document in 3GPP TS 24.484 [25]); or b) if the "entry-info" attribute of the <entry> element of the <MCVideoPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "LocallyDetermined"; then the controlling MCVideo function shall consider the MCVideo emergency private call request to be an authorised request for an MCVideo emergency private call and skip step 2) below; or 2) if the controlling MCVideo function does not consider the MCVideo emergency private call request to be an authorised request for an MCVideo emergency private call by step 1) above, then the controlling MCVideo function shall consider the MCVideo emergency private call request to be an unauthorised request for an MCVideo emergency private call." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.12.3] "If the controlling MCVideo function has received a SIP request with the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of "false" and: 1) if the <allow-cancel-emergency-alert> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true", then the MCVideo emergency alert cancellation request shall be considered to be an authorised request for an MCVideo emergency alert cancellation; and 2) if the <allow-cancel-emergency-alert> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "false", then the MCVideo emergency alert cancellation request shall be considered to be an unauthorised request for an MCVideo emergency alert cancellation." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.12.4] "If the controlling MCVideo function has received a SIP request with the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of "false" and: 1) if the <allow-cancel-emergency-alert> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true", then the MCVideo emergency alert cancellation request shall be considered to be an authorised request for an MCVideo emergency alert cancellation; and 2) if the <allow-cancel-emergency-alert> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "false", then the MCVideo emergency alert cancellation request shall be considered to be an unauthorised request for an MCVideo emergency alert cancellation." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 38 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.12.5] "If the controlling MCVideo function has received a SIP request with the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of "true" and: 1) if the <allow-imminent-peril-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value other than "true" the request for initiating an MCVideo imminent peril call shall be considered to be an unauthorised request for an MCVideo imminent peril call and skip the remaining steps; 2) if the <allow-imminent-peril-call> element of the <list-service> element of the group document identified by the targeted MCVideo group identity is set to a value other than "true" as specified in 3GPP TS 24.481 [24], the request for initiating an MCVideo imminent peril call shall be considered to be an unauthorised request for an MCVideo imminent peril call and skip the remaining steps; 3) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and if the MCVideo group identity targeted for the call is contained in the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element (see the MCVideo user profile document in 3GPP TS 24.484 [25]); or 4) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup". then the MCVideo imminent peril call request shall be considered to be an authorised request for an MCVideo imminent peril call. In all other cases, it shall be considered to be an unauthorised request for an MCVideo imminent peril call." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.2.1] "When composing the SDP answer according to 3GPP TS 24.229 [11], the controlling MCVideo function: 1) for the accepted media stream in the received SDP offer: a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the controlling MCVideo function; and 2) for the accepted media-transmission control entity, if present in the received SDP offer: a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the controlling MCVideo function, for the accepted media-transmission control entity, if present in the received SDP offer; and b) shall include 'fmtp' attributes as specified in 3GPP TS 24.581 clause 14." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.2.2] "On receipt of an initial SIP INVITE request the controlling MCVideo function shall cache SIP feature tags, if received in the Contact header field and if the specific feature tags are supported." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.2.4] "Upon receiving a SIP BYE request the controlling MCVideo function: 1) shall interact with the media plane as specified in clause 6.3 in 3GPP TS 24.581 [5] for releasing the media plane resource associated with the SIP session towards the MCVideo client; NOTE: The non-controlling MCVideo function is also regarded as a MCVideo client in a temporary MCVideo group session. 2) shall generate a SIP 200 (OK) response and send the SIP response towards the MCVideo client according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 39 3) shall check the MCVideo session release policy as specified in clause 6.3.8.1 and clause 6.3.8.2 whether the MCVideo session needs to be released for each participant of the MCVideo session; 4) if release of the MCVideo session is required: a) shall perform the procedures as specified in the clause 6.3.3.1.4 with the clarification that if the received SIP BYE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body, copy the application/vnd.3gpp.mcvideo-info+xml MIME body into the outgoing SIP BYE request; and 5) if a release of the MCVideo session is not required, shall send a SIP NOTIFY request to all remaining MCVideo clients in the MCVideo session with a subscription to the conference event package as specified in clause 9.2.3.4.2. Upon receiving a SIP 200 (OK) response to the SIP BYE request the controlling MCVideo function shall interact with the media plane as specified in clause 6.3 in 3GPP TS 24.581 [5] for releasing media plane resources associated with the SIP session with the MCVideo participant." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.4] "The controlling MCVideo function shall generate a SIP NOTIFY request according to 3GPP TS 24.229 [11] with the clarification in this clause. In the SIP NOTIFY request, the controlling MCVideo function: 1) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCVideo function; 2) shall include an Event header field set to the "conference" event package; 3) shall include an Expires header field set to 3600 seconds according to IETF RFC 4575 [57], as default value; 4) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Preferred-Service header field according to IETF RFC 6050 [14]; and 5) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with: a) the <mcvideo-calling-group-id> set to the value of the MCVideo group ID; b) if the target is a MCVideo user, the value of <mcvideo-request-uri> element set to the value of MCVideo ID of the targeted MCVideo user; and c) if the target is the non-controlling MCVideo function, the value of <mcvideo-request-uri> element set to the constituent MCVideo group ID. In the SIP NOTIFY request, the controlling MCVideo function shall include an application/conference-info+xml MIME body according to IETF RFC 4575 [57] with the following limitations: 1) the controlling MCVideo function shall include the MCVideo group ID of the MCVideo group in the "entity" attribute of the <conference-info> element; 2) for each participant in the MCVideo session with the exception of non-controlling MCVideo functions, the controlling MCVideo function shall include a <user> element. The <user> element shall: NOTE: Non-controlling MCVideo functions will appear as a participant in temporary group sessions. a) include the "entity" attribute. The "entity" attribute: i) shall for the MCVideo client, which initiated, joined or re-joined an MCVideo session, include the MCVideo ID of the MCVideo user which originates SIP INVITE request; and ii) shall for an invited MCVideo client include the MCVideo ID of the invited MCVideo user in case of a prearranged group call or chat group call; b) shall include a single <endpoint> element. The <endpoint> element: i) shall include the "entity" attribute; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 40 ii) shall include the <status> element indicating the status of the MCVideo session according to RFC 4575; and c) may include <roles> element. NOTE: The usage of <roles> is only applicable for human consumption." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.5.5] "The MCVideo server shall only invite affiliated group members to a group session. The MCVideo server determines the affiliated members from the entries contained in the <list> element of the group document by following the procedures specified in clause 6.3.6. NOTE 1: The term "affiliated group members" used above also includes those members that are implicitly affiliated by the controlling MCVideo function. If the number of members of the MCVideo group exceeds the value contained in the <on-network-max-participant- count> element the MCVideo server shall invite only <on-network-max-participant-count> members from the list, but shall prioritise inviting those group members to the group session that have an <entry> element in the <list> element with a <on-network-required> element present. NOTE 2: The <on-network-max-participant-count> element indicates the maximum number of participants allowed in the group session. The <on-network-required> element is used to determine which group members need to acknowledge the group call before audio transmission can proceed. NOTE 3: Other requirements for how the controlling MCVideo function selects which of the <on-network-max- participant-count> members to invite is outside the scope of this specification. NOTE 4: It is assumed that validation checks are performed at the group management server to ensure that the <on-network-max-participant-count> cannot be less than the number of <on-network-required> users." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.1] "The transmission control server arbitration logic in the transmission control server shall support the procedures in clauses 6.3.2 and 6.3.3 and shall behave according to the transmission control server state transition diagram for 'general transmission control operation' in clause 6.3.4. The transmission control interface towards the MCVideo client in the transmission control server shall behave according to the transmission control server state transition diagram for 'basic transmission control operation towards the transmission participant' as specified in clause 6.3.5. The reception control arbitration logic in the transmission control server shall support the procedures in clauses 6.3.2 and 6.3.3 and shall behave according to the reception control server state transition diagram for 'general reception control operation' in clause 6.3.6. The transmission control interface towards the MCVideo client in the transmission control server shall behave according to the transmission control server state transition diagram for 'basic reception control operation towards the transmission participant' as specified in clause 6.3.7." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.2.2] "When an MCVideo call is established a new instance of the transmission control server state machine for 'general transmission control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' is added. When an MCVideo call is established a new instance of the transmission control server state machine for 'general reception control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic reception control operation towards the transmission participant' is added. If the optional "mc_queueing" feature is supported and has been negotiated as specified in clause 14, the transmission control server could queue the implicit transmission control request for the media-transmission control entity. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 41 The original initial SIP INVITE request or SIP REFER request to establish an MCVideo chat group call or to rejoin an ongoing MCVideo call is not handled as an implicit transmission control request message by the transmission control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request. The permission to send media to the inviting MCVideo client due to implicit transmission control request is applicable to both confirmed indication and unconfirmed indication. When the first unconfirmed indication is received from the invited participating MCVideo function (see 3GPP TS 24.281 [2]) the transmission control server optionally can give an early indication to send RTP media packets, to the inviting MCVideo client. If an early indication to send RTP media packets is given to the inviting MCVideo client, the transmission participant is granted the permission to send media and the MCVideo server buffers RTP media packets received from the MCVideo client at least until the first invited MCVideo client accepts the invitation or until the RTP media packet buffer exceeds it maximum limit to store RTP media packets. If the MCVideo server does not support or does not allow media buffering then when an early indication to send RTP media packets is not given to the inviting MCVideo client, the transmission participant is granted the permission to send media when the first invited MCVideo client accepts the media. Before the transmission control server sends the first transmission control message in the MCVideo call, the transmission control server has to assign itself a SSRC identifier to be included in media transmission control messages and quality feedback messages if the MCVideo server is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3]. The transmission participant and the transmission control server can negotiate the maximum priority level that the transmission participant is permitted to request. The transmission control server can pre-empt the current sender based on the negotiated maximum priority level that the transmission participant is permitted to request and the priority level included in the Transmission Media Request message. NOTE: The maximum priority level that a transmission participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the controlling MCVideo function from the group management server as described in 3GPP TS 24.481 [12] and service configuration data retrieved by the controlling MCVideo function from the configuration management server as described in 3GPP TS 24.484 [13]. The transmission participant and the transmission control server can negotiate queueing of Transmission requests using the "mc_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the transmission control server queues the transmission control request if a Transmission Media Request message is received when another transmission participant has the transmission and the priority of the current speaker is the same or higher." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.1] "The transmission control messages are coded as described in clause 9.1.2 where the transmission control message is part of the application-dependent data. For the transmission control protocol the ASCII name string is: MCVx (Mission Critical Video x) with x=0, 1 or 2 as specified in clause 9.1.2. A list of transmission control messages can be found in clause 9.2.2.1. The transmission control specific fields are specified in clause 9.2.3." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 42 Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 43 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 44 d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine;and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and 2. shall set the general state to 'G: pending Transmission Revoke'." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 45 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 46 ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 47 b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.1.3 Test description | 5.1.1.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). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 48 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). - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are registered and authorized to use the MCVideo system. - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are affiliated to the pre-arranged group and are authorized to initiate group calls. - The IUT (MCVideo Server) is the controlling server of the pre-arranged group. 5.1.1.1.3.2 Test procedure sequence Table 5.1.1.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 group call establishment' as described in Annex A, Table A.4.1.4.3-1 to establish a pre-arranged group call with implicit transmission control request according to option b.ii of note in Annex A, Table A.4.1.4.3-1, initiated by SS-UE1 (MCVideo Client)? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1 to end SS-UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.1.1.3-1 to upgrade the call to emergency group call with implicit transmission request according to option b.ii of note in Annex A, Table A.4.1.1.3- 1? - - 4 P 4 Check: Does the IUT (MCVideo Server) correctly perform procedure ' MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1, to end SS-UE1 (MCVideo Client) transmission? - - 2 P 5 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-UE1 (MCVideo Client)? - - 3 P ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 49 St Procedure Message Sequence TP Verdict U - S Message 6 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1, to end SS-UE1 (MCVideo Client) transmission? - - 2 P 7 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.1.1.3-1 to downgrade the call without implicit transmission request, with option a of note on Table A.4.1.1.3-1? - - 5 P 8 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-UE1 (MCVideo Client)? - - 3 P 9 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1, to end SS-UE1 (MCVideo Client) transmission? - - 2 P 10 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.1.1.3-1 to upgrade the call to imminent peril group call with implicit transmission request according to option b.ii of note in Annex A, Table A.4.1.1.3-1? - - 6 P 11 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1, to end SS-UE1 (MCVideo Client) transmission? - - 2 P 12 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-UE1 (MCVideo Client)? - - 3 P 13 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1, to end SS-UE1 (MCVideo Client) transmission? - - 2 P 14 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.1.1.3-1 to downgrade the call without implicit transmission request, with option a of note on Table A.4.1.1.3-1? - - 7 P ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 50 St Procedure Message Sequence TP Verdict U - S Message 15 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? - - 8 P 5.1.1.1.3.3 Specific message contents All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) and Annex A, in the subclauses referenced in each step, with the following clarifications. Table 5.1.1.1.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.1.1.1.3.2-1; Step 1, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-1 Table 5.1.1.1.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.1.3.2-1; Step 2, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-2 Table 5.1.1.1.3.3-3: SIP 200 (OK) from SS (MCVideo Server) (Steps 1, 3, 7, 10 and 14, Table 5.1.1.1.3.2-1; Step 8, Annex A, Table A.4.1.4.3-1; Step 5, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.4.1.4.4-6 Table 5.1.1.1.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Steps 1, 3, 7, 10 and 14, Table 5.1.1.1.3.2-1; Step 9, Annex A, Table A.4.1.4.3-1; Step 6, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.4.1.4.4-7 Table 5.1.1.1.3.3-5: SIP re-INVITE from SS (MCVideo Server) (Step 3, Table 5.1.1.1.3.2-1; Step 1, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.4.1.1.4-1, with conditions GROUP-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.1.3.3-6: SIP re-INVITE from IUT (MCVideo Server) (Step 3, Table 5.1.1.1.3.2-1; Step 2, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.4.1.1.4-4, with condition GROUP-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.1.3.3-7: SIP re-INVITE from SS (MCVideo Server) (Steps 7 and 14, Table 5.1.1.1.3.2-1; Step 1, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.4.1.1.4-1, with conditions GROUP-CALL and re_INVITE. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 51 Table 5.1.1.1.3.3-8: SIP re-INVITE from IUT (MCVideo Server) (Steps 7 and 14, Table 5.1.1.1.3.2-1; Step 2, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.4.1.1.4-4, with condition GROUP-CALL and re_INVITE. NOTE: Conditions are also applied to all body parts. Table 5.1.1.1.3.3-9: SIP re-INVITE from SS (MCVideo Server) (Step 10, Table 5.1.1.1.3.2-1; Step 1, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.4.1.1.4-1, with conditions GROUP-CALL, re_INVITE and IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.1.3.3-10: SIP re-INVITE from IUT (MCVideo Server) (Step 10, Table 5.1.1.1.3.2-1; Step 2, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.4.1.1.4-4, with conditions GROUP-CALL, re_INVITE and IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.1.3.3-11: Transmission Idle from IUT (MCVideo Server) (Steps 4 and 6, Table 5.1.1.1.3.2-1; Steps 4 and 5, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-6, with condition EMERGENCY-CALL. Table 5.1.1.1.3.3-12: Transmission Request from SS (MCVideo Server) (Step 5, Table 5.1.1.1.3.2-1; Step 1, Annex A, Table A.3.7.3-1) Derivation Path: Annex A, Table A.3.7.4-1, with condition EMERGENCY-CALL. Table 5.1.1.1.3.3-13: Transmission Granted from IUT (MCVideo Server) (Steps 3 and 5, Table 5.1.1.1.3.2-1; Step 3a1 or 3b1, Annex A, Table A.3.7.3-1; Step 9a1, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.3.7.4-2 or A.3.7.4-3 (note), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. Table 5.1.1.1.3.3-14: Media Transmission Notification from IUT (MCVideo Server) (Steps 3 and 5, Table 5.1.1.1.3.2-1; Step 3a3 or 3b2, Annex A, Table A.3.7.3-1; Step 10a1, Annex A, Table 4.1.1.3-1) Derivation Path: Annex A, Table A.3.7.4-4 or A.3.7.4-5 (note), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. Table 5.1.1.1.3.3-15: Transmission Idle from IUT (MCVideo Server) (Steps 11 and 13, Table 5.1.1.1.3.2-1; Steps 4 and 5, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-6, with condition IMMPERIL-CALL. Table 5.1.1.1.3.3-16: Transmission Request from SS (MCVideo Server) (Step 12, Table 5.1.1.1.3.2-1; Step 1, Annex A, Table A.3.7.3-1) Derivation Path: Annex A, Table A.3.7.4-1, with condition IMMPERIL-CALL. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 52 Table 5.1.1.1.3.3-17: Transmission Granted from IUT (MCVideo Server) (Steps 10 and 12, Table 5.1.1.1.3.2-1; Step 3a1 or 3b1, Annex A, Table A.3.7.3-1; Step 9a1, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.3.7.4-2 or A.3.7.4-3 (note), with condition IMMPERIL-CALL. NOTE: Depends on server implementation. Table 5.1.1.1.3.3-18: Media Transmission Notification from IUT (MCVideo Server) (Steps 10 and 12, Table 5.1.1.1.3.2-1; Step 3a3 or 3b2, Annex A, Table A.3.7.3-1; Step 10a1, Annex A, Table 4.1.1.3-1) Derivation Path: Annex A, Table A.3.7.4-4 or A.3.7.4-5 (note), with condition IMMPERIL-CALL. NOTE: Depends on server implementation. 5.1.1.2 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Automatic Commencement / Upgrade to Emergency Group Call / Cancel Emergency State / Upgrade to Imminent Peril Group call / Cancel Imminent Peril State / Terminating Participating server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.2.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to SS (MCVideo Server) } ensure that { when { the SS (MCVideo Server) providing the controlling function initiates a pre-arranged group call with automatic commencement } then { IUT (MCVideo Server) accepts the call and establishes the call with SS-UE2 (MCVideo Client) and forwards the media transmission notification received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS (MCVideo Server) ends the media transmission } then { IUT (MCVideo Server) forwards the transmission end notify received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) and forwards the transmission idle received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the controlling function upgrades the call to emergency group call } then { IUT (MCVideo Server) accepts the upgrade and updates the call for SS-UE2 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } (4) with { IUT (MCVideo Server) having upgraded to an emergency pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the controlling function cancels the ongoing emergency state } then { IUT (MCVideo Server) accepts the emergency state cancellation and updates the call for SS-UE2 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 53 (5) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the controlling function upgrades the call to imminent peril group call } then { IUT (MCVideo Server) accepts the upgrade and updates the call for SS-UE2 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } (6) with { IUT (MCVideo Server) having upgraded to an imminent peril pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the controlling function cancels the ongoing imminent peril state } then { IUT (MCVideo Server) accepts the imminent peril state cancellation and updates the call for SS-UE2 (MCVideo Client) } } (7) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the controlling function ends the pre-arranged group call } then { IUT (MCVideo Server) sends a SIP BYE message to SS-UE2 (MCVideo Client) and responds by sending a SIP 200 (OK) message to SS (MCVideo Server) } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.2.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 9.2.1.3.2, 9.2.1.3.4, 9.2.1.3.6, 6.3.2.3.2, 6.3.2.2.5.1, 6.3.2.2.6.1, 6.3.2.2.8.1, 6.3.2.2.10, 6.3.2.2.4.2, 6.3.2.2.2.1 and 6.3.2.1.2.1, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.2] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. NOTE 1: This clause covers on-demand session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: … 2) shall check the presence of the isfocus media feature tag in the URI of the Contact header field and if it is not present then the participating MCVideo function shall reject the request …, and shall not continue with the rest of the steps; 3) if the Answer-Mode Indication in the application/poc-settings+xml MIME body has not yet been received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4, shall reject the request …, and shall not continue with the rest of the steps; 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; 5) if the binding between the MCVideo ID and public user identity does not exist, then the participating MCVideo function shall reject the SIP INVITE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 54 6) if the SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC- GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; and 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.4] "Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.2.8.1." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.6] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a SIP re-INVITE request for a terminating MCVideo client of a MCVideo group containing an emergency indication or imminent peril indication, the participating MCVideo function: 1) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may perform further actions outside the scope of this specification to act upon an included Resource-Priority header field as specified in 3GPP TS 24.229 [11]; 2) shall generate an outgoing SIP re-INVITE request as specified in clause 6.3.2.2.10; 3) shall include in the SIP re-INVITE request an SDP offer based on the SDP offer in the received SIP re-INVITE request as specified in clause 6.3.2.2.1; and 4) shall send the SIP re-INVITE request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the above SIP re-INVITE request sent to the MCVideo client, the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2; 2) shall include in the SIP 200 (OK) response an SDP answer based on the SDP answer in the received SIP 200 (OK) response as specified in clause 6.3.2.2.2.1; 3) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 4) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.3.2] "The participating MCVideo function: 1) shall extract the URI from the initiator field (IDRi) of the I_MESSAGE and use it together with the timer related parameter to check the signature of the I_MESSAGE as described in 3GPP TS 33.180 [8]; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 55 NOTE: If the terminating participating MCVideo function receives the SIP INVITE request from a controlling MCVideo function, then the URI in the IDRi is the controlling MCVideo function URI. If the terminating participating MCVideo function receives the SIP INVITE request from a non-controlling MCVideo function, then the URI in the IDRi is the non-controlling MCVideo function URI. 2) if the signature is not valid, shall exit this procedure. Otherwise shall validate that the contents of the recipient field (IDRr) of the I_MESSAGE to ensure it matches to the URI of the participating MCVideo function; and 3) if the contents of the IDRr do not match to the participating MCVideo function URI, shall exit this procedure. Otherwise, shall use the contents of the IDRr to decrypt the I_MESSAGE and extract the MKFC and MKFC- ID. After the MKFC(s) and MKFC-ID(s) have been extracted from the I_MESSAGE(s), the participating MCVideo function shall provide the media-transmission control entity with the MKFC(s) and MKFC-ID(s), by interacting with the media plane as specified in 3GPP TS 24.581 [5]." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.5.1] "When receiving a "SIP INVITE request for terminating participating MCVideo function" that requires automatic commencement mode: 1) if: a) the invited MCVideo client has one or more pre-established sessions without an associated MCVideo session; b) the media-level sections for the offered MCVideo video media stream are the same as the media-level sections for MCVideo video media stream in an existing pre-established session; and c) the media-level section of the offered media-transmission control entity is the same as the media-level section for media-transmission control entity in an existing pre-established session; then the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.5.3; or 2) otherwise the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.5.2." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.6.1] "When receiving a "SIP INVITE request for terminating participating MCVideo function" that requires manual commencement mode: 1) if: a) the invited MCVideo client has one or more pre-established sessions without an associated MCVideo session; b) the media-level sections for the offered MCVideo video media stream are the same as the media-level section for MCVideo video media stream in the existing pre-established session; and c) the media-level section of the offered media-transmission control entity is the same as the media-level section for media-transmission control entity in the existing pre-established session; then the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.6.3; or 2) otherwise the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.6.2." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.8.1] "Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function: 1) shall interact with the media plane as specified in clause 6.4 in 3GPP TS 24.581 [5] for releasing media plane resource associated with the SIP session with the controlling MCVideo function; 2) shall generate a SIP BYE request according to 3GPP TS 24.229 [11]; 3) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP BYE request to the P- Asserted-Identity header field of the outgoing SIP BYE request; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 56 4) if the received SIP BYE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body into the outgoing SIP BYE request; and 5) shall send the SIP BYE request to the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the SIP BYE request the participating MCVideo function: 1) shall send a SIP 200 (OK) response to the SIP BYE request received from the controlling MCVideo function according to 3GPP TS 24.229 [11]; and 2) shall interact with the media plane as specified in 3GPP TS 24.581 [5] for releasing media plane resources associated with the SIP session with the MCVideo client." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.10] "This clause is referenced from other procedures. The participating MCVideo function shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [11] and: 1) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [32]; 2) may include a Resource-Share header field in accordance with clause 5.7.1.20.3 in 3GPP TS 24.229 [11]; 3) shall perform the procedures specified in clause 6.3.2.2.9 to copy any MIME bodies in the received SIP re- INVITE request to the outgoing SIP re-INVITE request; and 4) if the received SIP re-INVITE request contains a Resource-Priority header field, shall include a Resource- Priority header field with the contents set as in the received Resource-Priority header field." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.4.2] "This clause is referenced from other procedures. When sending SIP 200 (OK) responses, the participating MCVideo function shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [11] and: 1) shall include the option tag "timer" in a Require header field; 2) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [23], "UAS Behavior". If no "refresher" parameter was included in the SIP INVITE request, the "refresher" parameter in the Session-Expires header field shall be set to "uas"; 3) shall include the following in the Contact header field: a) the g.3gpp.mcvideo media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; and c) an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP INVITE request from the controlling MCVideo function; 4) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [32]; and 5) if the incoming SIP response contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body to the outgoing SIP 200 (OK) response." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.2.1] "The participating MCVideo function shall follow the procedures in clause 6.3.2.1.2.1." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 57 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.2.1] "When composing the SDP answer according to 3GPP TS 24.229 [11], the participating MCVideo function: 1) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCVideo function, for the accepted media stream in the received SDP offer, if required; and NOTE 1: Requirements can exist for the participating MCVideo function to be always included in the path of the offered media stream, for example: for the support of features such as MBMS, lawful interception and recording. Other examples can exist. 2) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCVideo function, for the accepted media-transmission control entity, if present in the received SDP offer. NOTE 2: If the participating MCVideo function and the controlling MCVideo function are in the same MCVideo server, and the participating MCVideo function does not have a dedicated IP address or a dedicated port number for media transmission control or media stream, the replacement of the IP address or the port number is omitted." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.1] "Once an on-demand MCVideo session is established or a pre-established session is in use when the participating MCVideo function receives transmission control messages from the transmission participant in the MCVideo client or from the transmission control server in the controlling MCVideo function, the behaviour of the participating MCVideo function is described in the following clauses." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 58 NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session. " [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 59 When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 60 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 61 d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine;and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and 2. shall set the general state to 'G: pending Transmission Revoke'." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 62 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 63 ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 64 b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.2.3 Test description | 5.1.1.2.3.1 Pre-test conditions System Simulator: - SS (MCVideo Server), providing the controlling MCVideo function. - SS-UE2 (MCVideo Client). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 65 IUT: - IUT (MCVideo Server), providing the terminating participating 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 some sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server and the HTTP Client. Preamble: - The IUT (MCVideo Server) is connected to SS (MCVideo Server) and SS-UE2 (MCVideo Client). - The SS-UE2 (MCVideo client) is registered and authorized to use the MCVideo system. - The SS-UE2 (MCVideo client) is affiliated to the pre-arranged group and is authorized to initiate group calls. 5.1.1.2.3.2 Test procedure sequence Table 5.1.1.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 CT group/private call establishment, automatic commencement' as described in Annex A, Table A.4.3.3.3-1 to establish a pre-arranged group call with automatic commencement mode and notify a media transmission from SS-UE1 (MCVideo Client)? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Notification - Idle' as described in Annex A, Table A.4.3.8.3-1 to notify the end of SS-UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CT session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.3.1.3-1 to upgrade the call to emergency group call and notify a media transmission from SS-UE1 (MCVideo Client)? - - 3 P 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Notification - Idle' as described in Annex A, Table A.4.3.8.3-1 to notify the end of SS-UE1 (MCVideo Client) transmission? - - 2 P 5 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CT session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.3.1.3-1 to downgrade the call and without media transmission notification? - - 4 P 6 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CT session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.3.1.3-1 to upgrade the call to imminent peril group call and notify a media transmission from SS-UE1 (MCVideo Client)? - - 5 P 7 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Notification - Idle' as described in Annex A, Table A.4.3.8.3-1 to notify the end of SS-UE1 (MCVideo Client) transmission? - - 2 P ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 66 St Procedure Message Sequence TP Verdict U - S Message 8 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CT session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.3.1.3-1 to downgrade the call and without media transmission notification? - - 6 P 9 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E call release' as described in Annex A, Table A.4.3.5.3-1, to release the call? - - 7 P 5.1.1.2.3.3 Specific message contents All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) and Annex A, in the subclauses referenced in each step, with the following clarifications. Table 5.1.1.2.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.1.1.2.3.2-1; Step 1, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-1, with condition GROUP CALL. Table 5.1.1.2.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.2.3.2-1; Step 2, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-2, with condition GROUP CALL. Table 5.1.1.2.3.3-3: SIP 200 (OK) from SS-UE2 (MCVideo Client) (Steps 1, 3, 5, 6 and 8, Table 5.1.1.2.3.2-1; Step 6, Annex A, Table A.4.3.3.3-1; Step 5, Annex A, Table A.4.3.1.3-1) Derivation Path: Annex A, Table A.4.3.3.4-7, with condition GROUP CALL. Table 5.1.1.2.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Steps 1, 3, 5, 6 and 8, Table 5.1.1.2.3.2-1; Step 7, Annex A, Table A.4.3.3.3-1; Step 6, Annex A, Table A.4.3.1.3-1) Derivation Path: Annex A, Table A.4.3.3.4-8, with condition GROUP CALL. Table 5.1.1.2.3.3-5: SIP re-INVITE from SS (MCVideo Server) (Step 3, Table 5.1.1.2.3.2-1; Step 1, Annex A, Table A.4.3.1.3-1) Derivation Path: Annex A, Table A.4.3.1.4-1, with conditions GROUP-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.2.3.3-6: SIP re-INVITE from IUT (MCVideo Server) (Step 3, Table 5.1.1.2.3.2-1; Step 2, Annex A, Table A.4.3.1.3-1) Derivation Path: Annex A, Table A.4.3.1.4-2, with condition GROUP-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 67 Table 5.1.1.2.3.3-7: SIP re-INVITE from SS (MCVideo Server) (Steps 5 and 8, Table 5.1.1.2.3.2-1; Step 1, Annex A, Table A.4.3.1.3-1) Derivation Path: Annex A, Table A.4.3.1.4-1, with conditions GROUP-CALL, re_INVITE. NOTE: Conditions are also applied to all body parts. Table 5.1.1.2.3.3-8: SIP re-INVITE from IUT (MCVideo Server) (Steps 5 and 8, Table 5.1.1.2.3.2-1; Step 2, Annex A, Table A.4.3.1.3-1) Derivation Path: Annex A, Table A.4.3.1.4-2, with condition GROUP-CALL, re_INVITE. NOTE: Conditions are also applied to all body parts. Table 5.1.1.2.3.3-9: SIP re-INVITE from SS (MCVideo Server) (Step 6, Table 5.1.1.2.3.2-1; Step 1, Annex A, Table A.4.3.1.3-1) Derivation Path: Annex A, Table A.4.3.1.4-1, with conditions GROUP-CALL, re_INVITE and IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.2.3.3-10: SIP re-INVITE from IUT (MCVideo Server) (Step 6, Table 5.1.1.2.3.2-1; Step 2, Annex A, Table A.4.3.1.3-1) Derivation Path: Annex A, Table A.4.3.1.4-2, with condition GROUP-CALL, re_INVITE and IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.2.3.3-11: Transmission Idle (Step 4, Table 5.1.1.2.3.2-1; Steps 13 and 14, Annex A, Table A.4.3.8.3-1) Derivation Path: Annex A, Table A.4.3.8.4-6, with condition EMERGENCY-CALL. Table 5.1.1.2.3.3-12: Media Transmission Notification (Step 3, Table 5.1.1.2.3.2-1; Steps 9a1 and 9a2, Annex A, Table 4.3.1.3-1) Derivation Path: Annex A, Table A.4.3.1.4-7, with condition EMERGENCY-CALL. Table 5.1.1.2.3.3-13: Transmission Idle (Step 7, Table 5.1.1.2.3.2-1; Steps 13 and 14, Annex A, Table A.4.3.8.3-1) Derivation Path: Annex A, Table A.4.3.8.4-6, with condition IMMPERIL-CALL. Table 5.1.1.2.3.3-14: Media Transmission Notification (Step 6, Table 5.1.1.2.3.2-1; Steps 9a1 and 9a2, Annex A, Table 4.3.1.3-1) Derivation Path: Annex A, Table A.4.3.1.4-7, with condition IMMPERIL-CALL. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 68 5.1.1.3 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Upgrade to Emergency Group Call / Cancel Emergency State / Upgrade to Imminent Peril Group call / Cancel Imminent Peril State / Originating Participating server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.3.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to SS (MCVideo Server) } ensure that { when { the SS-UE1 (MCVideo Client) initiates a pre-arranged group call with implicit transmission control } then { IUT (MCVideo Server) accepts the call from initiator and establishes the call with the SS (MCVideo Server) providing the controlling function and forwards the transmission granted received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) forwards the transmission end request to SS (MCVideo Server) and forwards the transmission end response to SS-UE1 (MCVideo Client) and forwards the transmission idle received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control } then { IUT (MCVideo Server) forwards the transmission request to SS (MCVideo Server) and forwards the transmission granted received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (4) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) upgrades the call to emergency group call with implicit transmission request } then { IUT (MCVideo Server) forwards the upgrade request to SS (MCVideo Server) and forwards upgrade request confirmation from SS (MCVideo Server) to SS-UE1 (MCVideo Client) and forwards the transmission granted received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (5) with { IUT (MCVideo Server) having upgraded to an emergency pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) cancels the ongoing emergency state } then { IUT (MCVideo Server) forwards the emergency cancellation request to SS (MCVideo Server) and forwards the emergency state cancellation confirmation from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (6) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) upgrades the call to imminent peril group call with implicit transmission request } then { IUT (MCVideo Server) forwards the upgrade request to SS (MCVideo Server) and forwards upgrade request confirmation from SS (MCVideo Server) to SS-UE1 (MCVideo Client) and forwards the transmission granted received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 69 (7) with { IUT (MCVideo Server) having upgraded to an imminent peril pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) cancels the ongoing imminent peril state } then { IUT (MCVideo Server) forwards the imminent peril cancellation request to SS (MCVideo Server) and forwards the imminent peril state cancellation confirmation from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (8) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) ends the pre-arranged group call } then { IUT (MCVideo Server) sends a SIP BYE message to SS (MCVideo Server) providing the controlling function and responds by sending a SIP 200 (OK) message to SS-UE1 (MCVideo Client) } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.3.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 9.2.1.3.1.1, 9.2.1.3.1.3, 9.2.1.3.3, 6.3.1.1, 6.3.2.1.3, 6.3.2.1.1.1, 6.3.2.1.6.1 and 6.3.2.1.7, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.1.1] "In the procedures in this clause: 1) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 3) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "prearranged", the participating MCVideo function: 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The participating MCVideo function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [15]. Otherwise, continue with the rest of the steps; NOTE 1: if the SIP INVITE request contains an emergency indication or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCVideo function can according to local policy choose to accept the request. 2) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and shall authorise the calling user; NOTE 2: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. 3) if through local policy in the participating MCVideo function, the user identified by the MCVideo ID is not authorised to initiate prearranged group calls, shall reject the "SIP INVITE request for originating participating MCVideo function" with a SIP 403 (Forbidden) response to the SIP INVITE request, with warning text set to "109 user not authorised to make prearranged group calls" in a Warning header field as specified in clause 4.4; 4) shall validate the media parameters and if the MCVideo codecs are not offered in the SIP INVITE request shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 70 5) shall check if the number of maximum simultaneous MCVideo group calls supported for the MCVideo user as specified in the <MaxSimultaneousCallsN6> element of the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) has been exceeded. If exceeded, the participating MCVideo function shall respond with a SIP 486 (Busy Here) response with the warning text set to "103 maximum simultaneous MCVideo group calls reached" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps; NOTE 3: If the SIP INVITE request contains an emergency indication or an imminent peril indication, the participating MCVideo function can by means beyond the scope of this specification choose to allow for an exception to the limit for the maximum simultaneous MCVideo sessions supported for the MCVideo user. Alternatively, a lower priority session of the MCVideo user could be terminated to allow for the new session. 6) if the user identified by the MCVideo ID is not affiliated to the group identified in the "SIP INVITE request for originating participating MCVideo function" as determined by clause 8.2.2.2.11 and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, shall perform the actions specified in clause 8.2.2.2.12 for implicit affiliation; 7) if the actions for implicit affiliation specified in step 6) above were performed but not successful in affiliating the MCVideo user due to the MCVideo user already having N2 simultaneous affiliations, shall reject the "SIP INVITE request for originating participating MCVideo function" with a SIP 486 (Busy Here) response with the warning text set to "102 too many simultaneous affiliations" in a Warning header field as specified in clause 4.4. and skip the rest of the steps. NOTE 4: N2 is the total number of MCVideo groups that an MCVideo user can be affiliated to simultaneously as specified in 3GPP TS 23.281 [26]. NOTE 5: if the SIP INVITE request contains an emergency indication set to a value of "true" or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCVideo function can according to local policy choose to allow an exception to the N2 limit. Alternatively, a lower priority affiliation of the MCVideo user could be cancelled to allow for the new affiliation. 8) shall determine the public service identity of the controlling MCVideo function associated with the group identity in the SIP INVITE request; NOTE 6: The public service identity can identify the controlling MCVideo function in the primary MCVideo system or a partner MCVideo system. NOTE 7: How the participating MCVideo server discovers the public service identity of the controlling MCVideo function associated with the group identity is out of scope of the current release. 9) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3; 10) shall set the Request-URI to the public service identity of the controlling MCVideo function associated with the group identity which was present in the incoming SIP INVITE request; 11) shall not copy the following header fields from the incoming SIP INVITE request to the outgoing SIP INVITE request, if they were present in the incoming SIP INVITE request: a) Answer-Mode header field as specified in IETF RFC 5373 [27]; and b) Priv-Answer-Mode header field as specified in IETF RFC 5373 [27]; 12) shall set the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; 14) if the received SIP INVITE request contains an application/vnd.3gpp.location-info+xml MIME body and if not already copied, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body received in the SIP INVITE request into an application/vnd.3gpp.location-info+xml MIME body included in the outgoing SIP request; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 71 15) if a Resource-Priority header field was included in the received SIP INVITE request, shall include a Resource- Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCVideo client; and NOTE 8: The participating MCVideo function will leave verification of the Resource-Priority header field to the controlling MCVideo function. 16) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. Upon receipt of a SIP 302 (Moved Temporarily) response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.2.1.10; 2) shall include an SDP offer based upon the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; and 3) shall forward the SIP INVITE request according to 3GPP TS 24.229 [11]. Upon receipt of a SIP 2xx response in response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) if the received SIP 2xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC-GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 2) shall generate a SIP 200 (OK) response as in clause 6.3.2.1.5.2; 3) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 4) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 5) shall include the public service identity received in the P-Asserted-Identity header field of the incoming SIP 200 (OK) response into the P-Asserted-Identity header field of the outgoing SIP 200 (OK) response; 6) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 7) if the procedures of clause 8.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 8.2.2.2.13; 8) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 9) shall interact with Media Plane as specified in 3GPP TS 24.581 [5]; and 10) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [23]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request in step 14) the participating MCVideo function: 1) shall generate a SIP response according to 3GPP TS 24.229 [11]; 2) shall include Warning header field(s) that were received in the incoming SIP response; 3) shall forward the SIP response to the MCVideo client according to 3GPP TS 24.229 [11]; and 4) if the implicit affiliation procedures of clause 8.2.2.2.12 were invoked in this procedure, shall perform the procedures of clause 8.2.2.2.14;" ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 72 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.1.3] "This clause covers on-demand session. Upon receipt of a SIP re-INVITE request for an MCVideo session identifying an on-demand prearranged MCVideo group session, the participating MCVideo function: 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP re- INVITE request with a SIP 500 (Server Internal Error) response. The participating MCVideo function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [15] and skip the rest of the steps; NOTE 1: If the SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true", the participating MCVideo function can choose to accept the request. 2) shall determine if the media parameters are acceptable and the MCVideo codecs are offered in the SDP offer and if not, reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; 3) shall generate an outgoing SIP re-INVITE request as specified in clause 6.3.2.1.9; 4) shall, if the SIP re-INVITE request was received within an on-demand session, include in the SIP re-INVITE request an SDP offer based on the SDP offer in the received SIP re-INVITE request as specified in clause 6.3.2.1.1; 5) if the received SIP re-INVITE request contains a Resource-Priority header field, shall include a Resource- Priority header field with the contents set as in the received Resource-Priority header field; and NOTE 3: The controlling MCVideo function will determine the validity of the Resource-Priority header field. 6) shall forward the SIP re-INVITE request according to 3GPP TS 24.229 [11]. Upon receipt of a SIP 2xx response to the above SIP re-INVITE request in step 7) the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2; 2) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 3) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 4) shall copy the contents received in the P-Asserted-Identity header field of the incoming SIP 200 (OK) response into the P-Asserted-Identity header field of the outgoing SIP 200 (OK) response; 5) shall send the SIP 200 (OK) response towards the MCVideo client according to 3GPP TS 24.229 [11]; and 6) shall interact with the media plane as specified in 3GPP TS 24.581 [5]. Upon receipt of a SIP 403 (Forbidden) response to the above SIP INVITE request in step 7) the participating MCVideo function: 1) shall generate a SIP 403 (Forbidden) response according to 3GPP TS 24.229 [11]; 2) shall copy, if included in the received SIP 403 (Forbidden) response, the application/vnd.3gpp.mcvideo- info+xml MIME body MIME body to the outgoing SIP (Forbidden) response; 3) shall include Warning header field(s) that were received in the incoming SIP 403 (Forbidden) response; 4) shall forward the SIP 403 (Forbidden) response to the MCVideo client according to 3GPP TS 24.229 [11]; and 5) shall interact with the media plane as specified in 3GPP TS 24.581 [5]." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.3] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.1.6." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 73 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.1.1] "The MCVideo server needs to distinguish between the following initial SIP INVITE requests for originations and terminations: - SIP INVITE requests routed to the participating MCVideo function as a result of processing initial filter criteria at the S-CSCF in accordance with the origination procedures as specified in 3GPP TS 24.229 [11] and the Request-URI is set to a public service identity of the participating MCVideo function that does not identify the pre-established session set-up. Such requests are known as "SIP INVITE request for originating participating MCVideo function" in the procedures in the present document; - SIP INVITE requests routed to the participating MCVideo function as a result of processing initial filter criteria at the S-CSCF in accordance with the termination procedures as specified in 3GPP TS 24.229 [11] and the Request-URI contains a PSI of the terminating participating MCVideo function. Such requests are known as "SIP INVITE request for terminating participating MCVideo function" in the procedures in the present document; - SIP INVITE requests routed to the controlling MCVideo function as a result of PSI routing on the originating side in accordance with the originating procedures as specified in 3GPP TS 24.229 [11], or as a result of direct PSI routing, in accordance with the termination procedures as specified in 3GPP TS 24.229 [11], the Request-URI is set to a public service identity for MCVideo private call and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [16]. Such requests are known as "SIP INVITE request for controlling MCVideo function of a private call" in the procedures in the present document; - SIP INVITE requests routed to the controlling MCVideo function as a result of PSI routing on the originating side in accordance with the originating procedures as specified in 3GPP TS 24.229 [11], or as a result of direct PSI routing, in accordance with the termination procedures as specified in 3GPP TS 24.229 [11], the Request-URI is set to a public service identity serving an MCVideo group and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [16]. Such requests are known as "SIP INVITE request for controlling MCVideo function of an MCVideo group" in the procedures in the present document; and - SIP INVITE requests routed to the controlling MCVideo function as a result of PSI routing on the originating side in accordance with the originating procedures as specified in 3GPP TS 24.229 [11], or as a result of direct PSI routing, in accordance with the termination procedures as specified in 3GPP TS 24.229 [11], the Request-URI is set to a public service identity for MCVideo ambient viewing call and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [22]. Such requests are known as "SIP INVITE request for controlling MCVideo function of an ambient viewing call" in the procedures in the present document." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.3] "This clause is referenced from other procedures. When generating an initial SIP INVITE request according to 3GPP TS 24.229 [11], on receipt of an incoming SIP INVITE request, the participating MCVideo function: 1) shall include in the SIP INVITE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [20] if included in the incoming SIP INVITE request; 2) should include the Session-Expires header field according to IETF RFC 4028 [23]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 3) shall include the option tag "timer" in the Supported header field; 4) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP INVITE request to the P- Asserted-Identity header field of the outgoing SIP INVITE request; 5) shall include the g.3gpp.mcvideo media feature tag into the Contact header field of the outgoing SIP INVITE request; 6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 74 7) if the incoming SIP INVITE request contained a MIME resource-lists body with the MCVideo ID of the invited MCVideo user, shall copy the MIME resource-lists body, according to rules and procedures of IETF RFC 5366 [37]; 8) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the contents of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request to the outgoing SIP INVITE request; and 9) if the incoming SIP INVITE request contained an application/vnd.3gpp.location-info+xml MIME body, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body of the incoming SIP INVITE request to the outgoing SIP INVITE request." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.1.1] "This clause is referenced from other clauses. The SDP offer is generated based on the received SDP offer. The SDP offer generated by the participating MCVideo function: 1) shall contain two SDP media-level sections for MCVideo video media as contained in the received SDP offer; and 2) shall contain an SDP media-level section for one media-transmission control entity, if present in the received SDP offer. When composing the SDP offer according to 3GPP TS 24.229 [11], the participating MCVideo function: 1) shall replace the IP address and port number for the offered media stream in the received SDP offer with the IP address and port number of the participating MCVideo function, if required; NOTE 1: Requirements can exist for the participating MCVideo function to be always included in the path of the offered media stream, for example: for the support of features such as MBMS, lawful interception and recording. Other examples can exist. 2) shall replace the IP address and port number for the offered media transmission control entity, if any, in the received SDP offer with the IP address and port number of the participating MCVideo function; and NOTE 2: If the participating MCVideo function and the controlling MCVideo function are in the same MCVideo server, and the participating MCVideo function does not have a dedicated IP address or a dedicated port number for media transmission control or media stream, the replacement of the IP address or the port number is omitted. 3) shall contain an "a=key-mgmt" attribute field with a "mikey" attribute value, if present in the received SDP offer." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.6.1] "When the participating MCVideo function receives a request from the MCVideo client to originate an MCVideo emergency group call and needs to determine if the request is an authorised request for an MCVideo emergency call, the participating MCVideo function shall check the following: 1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true" and: a) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element contains the identity of the MCVideo group targeted by the calling MCVideo user; or b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup"; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 75 then the participating MCVideo function shall consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call; In all other cases, the participating MCVideo function shall consider the request to originate an MCVideo emergency group call to be an unauthorised request to originate an MCVideo emergency group call. When the participating MCVideo function receives a request from the MCVideo client to originate an MCVideo imminent peril group call and needs to determine if the request is an authorised request for an MCVideo imminent peril group call the participating MCVideo function shall check the following: 1) if the <allow-imminent-peril-call> element of <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true"; and a) if the "entry-info" attribute of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element contains the identity of the MCVideo group targeted by the calling MCVideo user; or b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup"; then the participating MCVideo function shall consider the MCVideo imminent peril group call request to be an authorised request for an MCVideo emergency group call; In all other cases, the participating MCVideo function shall consider the request to originate an MCVideo imminent peril group call to be an unauthorised request to originate an MCVideo imminent peril call." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.7] "This clause is referenced from other procedures. When generating a SIP re-INVITE request according to 3GPP TS 24.229 [11] on receipt of an incoming SIP re-INVITE request, the participating MCVideo function: 1) if the incoming SIP re-INVITE request contained a MIME resource-lists body with the MCVideo ID of the invited MCVideo user, shall copy the MIME resource-lists body, according to rules and procedures of IETF RFC 5366 [37]; 2) if the incoming SIP re-INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body; and 3) if the incoming SIP re-INVITE request contained an application/vnd.3gpp.location-info+xml MIME body, shall copy the application/vnd.3gpp.location-info+xml MIME body." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.1] "Once an on-demand MCVideo session is established or a pre-established session is in use when the participating MCVideo function receives transmission control messages from the transmission participant in the MCVideo client or from the transmission control server in the controlling MCVideo function, the behaviour of the participating MCVideo function is described in the following clauses." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 76 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 77 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 78 When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 79 c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine;and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 80 ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and 2. shall set the general state to 'G: pending Transmission Revoke'." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 81 c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 82 B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 83 NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.3.3 Test description | 5.1.1.3.3.1 Pre-test conditions System Simulator: - SS (MCVideo Server), providing the controlling MCVideo function. - SS-UE1 (MCVideo Client). IUT: - IUT (MCVideo Server), providing the originating participating 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 some sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server and the HTTP Client. Preamble: - The IUT (MCVideo Server) is connected to SS (MCVideo Server) and SS-UE1 (MCVideo Client). - The SS-UE1 (MCVideo client) is registered and authorized to use the MCVideo system. - The SS-UE1 (MCVideo client) is affiliated to the pre-arranged group and is authorized to initiate group calls. 5.1.1.3.3.2 Test procedure sequence Table 5.1.1.3.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 CO session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.4.2.1.3-1 to establish a pre- arranged group call with implicit transmission control request according to option b.ii of note in Annex A, Table A.4.2.1.3-1, initiated by SS-UE1 (MCVideo Client? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO Transmission End Request - Transmission End Response' as described in Annex A, Table A.4.2.5.3-1 to end SS-UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.2.1.3-1 to upgrade the call to emergency group call with implicit transmission request according to option b.ii of note in Annex A, Table A.4.2.1.3-1? - - 4 P ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 84 St Procedure Message Sequence TP Verdict U - S Message 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO Transmission End Request - Transmission End Response' as described in Annex A, Table A.4.2.5.3-1 to end SS-UE1 (MCVideo Client) transmission? - - 2 P 5 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Transmission Granted' as described in Annex A, Table A.4.2.4.3-1, to request permission to transmit for SS-UE1 (MCVideo Client)? - - 3 P 6 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO Transmission End Request - Transmission End Response' as described in Annex A, Table A.4.2.5.3-1 to end SS-UE1 (MCVideo Client) transmission? - - 2 P 7 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.2.1.3-1 to downgrade the call without implicit transmission request, with option a of note on Table A.4.2.1.3-1? - - 5 P 8 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Transmission Granted' as described in Annex A, Table A.4.2.4.3-1, to request permission to transmit for SS-UE1 (MCVideo Client)? - - 3 P 9 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO Transmission End Request - Transmission End Response' as described in Annex A, Table A.4.2.5.3-1 to end SS-UE1 (MCVideo Client) transmission? - - 2 P 10 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.2.1.3-1 to upgrade the call to imminent peril group call with implicit transmission request according to option b.ii of note in Annex A, Table A.4.2.1.3-1? - - 6 P 11 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO Transmission End Request - Transmission End Response' as described in Annex A, Table A.4.2.5.3-1 to end SS-UE1 (MCVideo Client) transmission? - - 2 P 12 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Transmission Granted' as described in Annex A, Table A.4.2.4.3-1, to request permission to transmit for SS-UE1 (MCVideo Client)? - - 3 P 13 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO Transmission End Request - Transmission End Response' as described in Annex A, Table A.4.2.5.3-1 to end SS-UE1 (MCVideo Client) transmission? - - 2 P 14 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO session establishment/modification without provisional responses other than 100 Trying', as described in Annex A, Table A.4.2.1.3-1 to downgrade the call without implicit transmission request, with option a of note on Table A.4.2.1.3-1? - - 7 P 15 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO call release' as described in Annex A, Table A.4.2.3.3-1, to release the call? - - 8 P ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 85 5.1.1.3.3.3 Specific message contents All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) and Annex A, in the subclauses referenced in each step, with the following clarifications. Table 5.1.1.3.3.3-1: SIP INVITE from SS-UE1 (MCVideo Client) (Step 1, Table 5.1.1.3.3.2-1; Step 1, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-1, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.3.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.3.3.2-1; Step 2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-2, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.3.3.3-3: SIP 200 (OK) from SS (MCVideo Server) (Steps 1, 3, 7, 10 and 14, Table 5.1.1.3.3.2-1; Step 5, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-3, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.3.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Steps 1, 3, 7, 10 and 14, Table 5.1.1.3.3.2-1; Step 6, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-4, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.3.3.3-5: SIP re-INVITE from SS-UE1 (MCVideo Client) (Step 3, Table 5.1.1.3.3.2-1; Step 1, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-1, with conditions GROUP-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.3.3.3-6: SIP re-INVITE from IUT (MCVideo Server) (Step 3, Table 5.1.1.3.3.2-1; Step 2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-2, with condition GROUP-CALL, re_INVITE and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.3.3.3-7: SIP re-INVITE from SS-UE1 (MCVideo Client) (Steps 7 and 14, Table 5.1.1.3.3.2-1; Step 1, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-1, with conditions GROUP-CALL and re_INVITE. NOTE: Conditions are also applied to all body parts. Table 5.1.1.3.3.3-8: SIP re-INVITE from IUT (MCVideo Server) (Steps 7 and 14, Table 5.1.1.3.3.2-1; Step 2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-2, with condition GROUP-CALL and re_INVITE. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 86 Table 5.1.1.3.3.3-9: SIP re-INVITE from SS-UE1 (MCVideo Client) (Step 10, Table 5.1.1.3.3.2-1; Step 1, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-1, with conditions GROUP-CALL, re_INVITE and IMMPERIL -CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.3.3.3-10: SIP re-INVITE from IUT (MCVideo Server) (Step 10, Table 5.1.1.3.3.2-1; Step 2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-2, with conditions GROUP-CALL, re_INVITE and IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.3.3.3-11: Transmission Idle (Steps 4 and 6, Table 5.1.1.3.3.2-1; Steps 9 and 10, Annex A, Table A.4.2.5.3-1) Derivation Path: Annex A, Table A.4.2.5.4-3, with condition EMERGENCY-CALL. Table 5.1.1.3.3.3-12: Transmission Request (Step 5, Table 5.1.1.3.3.2-1; Steps 1 and 2, Annex A, Table A.4.2.4.3-1) Derivation Path: Annex A, Table A.4.2.4.4-1, with condition EMERGENCY-CALL. Table 5.1.1.3.3.3-13: Transmission Granted (Steps 3 and 5, Table 5.1.1.3.3.2-1; Steps 5 and 6, Annex A, Table A.4.2.4.3-1; Steps 9a1 and 9a2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.4.4-2, with condition EMERGENCY-CALL. Table 5.1.1.3.3.3-14: Transmission Idle (Steps 11 and 13, Table 5.1.1.3.3.2-1; Steps 9 and 10, Annex A, Table A.4.2.5.3-1) Derivation Path: Annex A, Table A.4.2.5.4-3, with condition IMMPERIL-CALL. Table 5.1.1.3.3.3-15: Transmission Request (Step 12, Table 5.1.1.3.3.2-1; Steps 1 and 2, Annex A, Table A.4.2.4.3-1) Derivation Path: Annex A, Table A.4.2.4.4-1, with condition IMMPERIL-CALL. Table 5.1.1.3.3.3-16: Transmission Granted (Steps 10 and 12, Table 5.1.1.3.3.2-1; Steps 5 and 6, Annex A, Table A.4.2.4.3-1; Steps 9a1 and 9a2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.4.4-2, with condition IMMPERIL-CALL. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 87 5.1.1.4 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Manual Commencement / Terminating Participating server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.4.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to SS (MCVideo Server) } ensure that { when { the SS (MCVideo Server) providing the controlling function initiates a pre-arranged group call with manual commencement } then { IUT (MCVideo Server) accepts the call and establishes the call with SS-UE2 (MCVideo Client) and forwards the media transmission notification received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS (MCVideo Server) ends the media transmission } then { IUT (MCVideo Server) forwards the transmission end notify received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) and forwards the transmission idle received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the controlling function ends the pre-arranged group call } then { IUT (MCVideo Server) sends a SIP BYE message to SS-UE2 (MCVideo Client) and responds by sending a SIP 200 (OK) message to SS (MCVideo Server) } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.4.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 9.2.1.3.2, 9.2.1.3.4, 6.3.2.3.2, 6.3.2.2.6.1, 6.3.2.2.6.2, 6.3.2.2.8.1, 6.3.2.2.4.2, 6.3.2.2.2.1, 6.3.2.1.2.1 and 6.3.2.2.3, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.3.3, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.2] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. NOTE 1: This clause covers on-demand session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: … 2) shall check the presence of the isfocus media feature tag in the URI of the Contact header field and if it is not present then the participating MCVideo function shall reject the request …, and shall not continue with the rest of the steps; 3) if the Answer-Mode Indication in the application/poc-settings+xml MIME body has not yet been received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4, shall reject the request …, and shall not continue with the rest of the steps; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 88 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; 5) if the binding between the MCVideo ID and public user identity does not exist, then the participating MCVideo function shall reject the SIP INVITE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps; 6) if the SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC- GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; and 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.4] "Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.2.8.1." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.6.1] "When receiving a "SIP INVITE request for terminating participating MCVideo function" that requires manual commencement mode: 1) if: a) the invited MCVideo client has one or more pre-established sessions without an associated MCVideo session; b) the media-level sections for the offered MCVideo video media stream are the same as the media-level section for MCVideo video media stream in the existing pre-established session; and c) the media-level section of the offered media-transmission control entity is the same as the media-level section for media-transmission control entity in the existing pre-established session; then the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.6.3; or 2) otherwise the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.6.2." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.6.2] "When receiving a "SIP INVITE request for terminating participating MCVideo function" for an on-demand session that requires manual commencement mode the participating MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.2.2.3; 2) shall set the Request-URI to the public user identity associated to the MCVideo ID of the MCVideo user to be invited; 3) shall perform the procedures specified in clause 6.3.2.2.9 to include any MIME bodies in the received SIP INVITE request; 4) if the Answer-Mode header field is present in the incoming SIP INVITE request, participating MCVideo function, shall include an Answer-Mode header field with the value "Manual"; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 89 5) if no Answer-Mode header field was received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4 is set to "manual-answer", shall set the Answer-Mode header field to "Manual" in the outgoing SIP INVITE request; 6) if the Priv-Answer-Mode header field is present in the incoming SIP INVITE request, the participating MCVideo function shall include a Priv-Answer-Mode header field with the value "Manual"; 7) shall copy the contents of the P-Asserted-Identity header field of the incoming "SIP INVITE request for terminating participating MCVideo function" to the P-Asserted-Identity header field of the outgoing SIP INVITE request; 8) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for terminating participating MCVideo function" as specified in clause 6.3.2.2.1; 9) if the received SIP INVITE request contains a Resource-Priority header field, shall include a Resource- Priority header field with the contents set as in the received Resource-Priority header field; and 10) shall send the SIP INVITE request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 180 (Ringing) response to the above SIP INVITE request, the participating MCVideo function: NOTE 1: A SIP 180 (Ringing) response is received from a terminating MCVideo client in the case of a private call. 1) shall generate a SIP 180 (Ringing) response as specified in clause 6.3.2.2.4.1; 2) shall include the P-Asserted-Identity header field as received in the incoming SIP 180 (Ringing) response; and 3) shall forward the SIP 180 (Ringing) response according to 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response to the above SIP INVITE request, the participating MCVideo function: NOTE 2: A SIP 183 (Session Progress) response can be received from a terminating MCVideo client in the case of a group call. 1) shall generate a SIP 183 (Session Progress) response as specified in clause 6.3.2.2.4.1; 2) shall include the P-Asserted-Identity header field as received in the incoming SIP 183 (Session Progress) response; 3) shall include the P-Answer-State header field if received in the incoming SIP 183 (Session Progress) request; and 4) shall forward the SIP 183 (Session Progress) response according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the SIP INVITE request sent to the MCVideo client, the participating MCVideo function: When the participating MCVideo function sends the SIP 200 (OK) response the participating MCVideo function: 1) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2; 2) shall include in the SIP 200 (OK) response an SDP answer based on the SDP answer in the received SIP 200 (OK) response as specified in clause 6.3.2.2.2.1; 3) shall copy the P-Asserted-Identity header field from the incoming SIP 200 (OK) response to the outgoing SIP 200 (OK) response; 4) shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and 5) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [11]. The participating MCVideo function shall forward any other SIP response that does not contain SDP along the signalling path to the originating network according to 3GPP TS 24.229 [11]." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 90 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.8.1] "Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function: 1) shall interact with the media plane as specified in clause 6.4 in 3GPP TS 24.581 [5] for releasing media plane resource associated with the SIP session with the controlling MCVideo function; 2) shall generate a SIP BYE request according to 3GPP TS 24.229 [11]; 3) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP BYE request to the P- Asserted-Identity header field of the outgoing SIP BYE request; 4) if the received SIP BYE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body into the outgoing SIP BYE request; and 5) shall send the SIP BYE request to the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the SIP BYE request the participating MCVideo function: 1) shall send a SIP 200 (OK) response to the SIP BYE request received from the controlling MCVideo function according to 3GPP TS 24.229 [11]; and 2) shall interact with the media plane as specified in 3GPP TS 24.581 [5] for releasing media plane resources associated with the SIP session with the MCVideo client." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.4.2] "This clause is referenced from other procedures. When sending SIP 200 (OK) responses, the participating MCVideo function shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [11] and: 1) shall include the option tag "timer" in a Require header field; 2) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [23], "UAS Behavior". If no "refresher" parameter was included in the SIP INVITE request, the "refresher" parameter in the Session-Expires header field shall be set to "uas"; 3) shall include the following in the Contact header field: a) the g.3gpp.mcvideo media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; and c) an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP INVITE request from the controlling MCVideo function; 4) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [32]; and 5) if the incoming SIP response contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body to the outgoing SIP 200 (OK) response." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.2.1] "The participating MCVideo function shall follow the procedures in clause 6.3.2.1.2.1." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.2.1] "When composing the SDP answer according to 3GPP TS 24.229 [11], the participating MCVideo function: 1) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCVideo function, for the accepted media stream in the received SDP offer, if required; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 91 NOTE 1: Requirements can exist for the participating MCVideo function to be always included in the path of the offered media stream, for example: for the support of features such as MBMS, lawful interception and recording. Other examples can exist. 2) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCVideo function, for the accepted media-transmission control entity, if present in the received SDP offer. NOTE 2: If the participating MCVideo function and the controlling MCVideo function are in the same MCVideo server, and the participating MCVideo function does not have a dedicated IP address or a dedicated port number for media transmission control or media stream, the replacement of the IP address or the port number is omitted." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.3] "The participating MCVideo function shall generate an initial SIP INVITE request according to 3GPP TS 24.229 [11] and: 1) shall include in the SIP INVITE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [20] if included in the incoming SIP INVITE request; 2) should include the Session-Expires header field according to IETF RFC 4028 [23]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 3) shall include the option tag "timer" in the Supported header field; 4) shall include the following in the Contact header field: a) the g.3gpp.mcvideo media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; c) the isfocus media feature tag; d) an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the incoming SIP INVITE request; and e) any other uri-parameter provided in the Contact header field of the incoming SIP INVITE request; 5) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [32]; 6) shall include the option tag "norefersub" in a Supported header field according to rules and procedures of IETF RFC 4488 [31]; 7) may include a Resource-Share header field in accordance with clause 5.7.1.20.3 in 3GPP TS 24.229 [11]; and 8) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body to the outgoing SIP INVITE request." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.1] "Once an on-demand MCVideo session is established or a pre-established session is in use when the participating MCVideo function receives transmission control messages from the transmission participant in the MCVideo client or from the transmission control server in the controlling MCVideo function, the behaviour of the participating MCVideo function is described in the following clauses." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 92 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 93 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 94 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 95 NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 96 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.4.3 Test description | 5.1.1.4.3.1 Pre-test conditions System Simulator: - SS (MCVideo Server), providing the controlling MCVideo function. - SS-UE2 (MCVideo Client). IUT: - IUT (MCVideo Server), providing the terminating participating 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 some sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server and the HTTP Client. Preamble: - The IUT (MCVideo Server) is connected to SS (MCVideo Server) and SS-UE2 (MCVideo Client). - The SS-UE2 (MCVideo client) is registered and authorized to use the MCVideo system. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 97 - The SS-UE2 (MCVideo client) is affiliated to the pre-arranged group and is authorized to initiate group calls. 5.1.1.4.3.2 Test procedure sequence Table 5.1.1.4.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 CT group call establishment, manual commencement' as described in Annex A, Table A.4.3.4.3-1 to establish a pre-arranged group call with manual commencement mode and notify a media transmission from SS-UE1 (MCVideo Client)? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Notification - Idle' as described in Annex A, Table A.4.3.8.3-1 to notify the end of SS-UE1 (MCVideo Client) transmission? - - 2 P 9 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E call release' as described in Annex A, Table A.4.3.5.3-1, to release the call? - - 3 P 5.1.1.4.3.3 Specific message contents All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) and Annex A, in the subclauses referenced in each step. 5.1.1.5 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Emergency Group Call / Controlling server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.5.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 an emergency pre-arranged group call with implicit transmission control } then { IUT (MCVideo Server) accepts the call from initiator and establishes the call with all affiliated users by sending call establishment requests to 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 an emergency pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) sends transmission control idle to SS-UE1 (MCVideo Client) and sends transmission control idle to SS-UE2 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established an emergency pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control } then { IUT (MCVideo Server) sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 98 (4) with { IUT (MCVideo Server) having established an emergency pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function ends the pre- arranged group 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.1.1.5.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 9.2.1.4.2, 9.2.1.4.3, 9.2.1.4.1.1, 9.2.1.4.1.2, 6.3.3.1.6, 6.3.3.1.12.2, 6.3.3.1.12.4, 6.3.3.2.1 and 6.3.3.2.2, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.3.1, 6.3.2.2, 9.2.1, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.2] "In the procedures in this clause: 1) MCVideo ID in an incoming SIP INVITE request refers to the MCVideo ID of the originating user from the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 3) MCVideo ID in an outgoing SIP INVITE request refers to the MCVideo ID of the called user in the <mcvideo- request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) indication of required group members in a SIP 183 (Session Progress) response refers to the <required> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to "true" in a SIP 183 (Session Progress) sent by the non-controlling MCVideo function of an MCVideo group; 5) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 6) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for controlling MCVideo function of an MCVideo group", the controlling MCVideo function: … 2) shall determine if the media parameters are acceptable and the MCVideo codecs are offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps; 3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if: a) an Accept-Contact header field does not include the g.3gpp.mcvideo media feature tag; or b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; 4) if received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; 5) shall retrieve the necessary group document(s) from the group management server for the group identity contained in the SIP INVITE request and carry out initial processing as specified in clause 6.3.5.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 99 6) if the result of the initial processing in clause 6.3.5.2 was: a) that authorization of the MCVideo ID is required at a non-controlling MCVideo function of an MCVideo group is required, perform the actions in clause 6.3.3.1.13.7 and do not continue with the rest of the steps in this clause; and b) that a SIP 3xx, 4xx, 5xx or 6xx response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group" has been sent, do not continue with the rest of the steps in this clause; 7) shall perform the actions as described in clause 6.3.3.2.2; 8) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero; 9) shall determine if an MCVideo group call for the group identity is already ongoing by determining if an MCVideo session identity has already been allocated for the group call and the MCVideo session is active; … 12) if a Resource-Priority header field is included in the SIP INVITE request: a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; or b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; 13) if the MCVideo group call is not ongoing then: … c) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined as determined in step 13) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; d) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; e) shall create a prearranged group session and allocate an MCVideo session identity for the prearranged group call, and shall handle timer TNG3 (group call timer) as specified in clause 6.3.3.5; f) if the group identity in the "SIP INVITE request for controlling MCVideo function of an MCVideo group" is a TGI: i) shall for each of the constituent MCVideo groups homed on the primary MCVideo system: …; B) if the controlling MCVideo function owns the MCVideo group identified by the MCVideo group ID then: I) determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; II) invite each group member determined in step A) above, to the group session, as specified in clause 9.2.1.4.1.1; and III) interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 100 ii) shall for each of the constituent MCVideo groups homed on the partner MCVideo system generate a SIP INVITE request for the MCVideo group identity homed on the partner MCVideo system as specified in clause 9.2.1.4.1.2; and g) if the group identity in the SIP INVITE request for controlling MCVideo function of an MCVideo group is an MCVideo group ID: i) shall determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; ii) if necessary, shall start timer TNG1 (acknowledged call setup timer) according to the conditions stated in clause 6.3.3.3; iii) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": A) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; and C) if the in-progress emergency state of the group is set to a value of "false": I) shall set the value of the in-progress emergency state of the group to "true"; and II) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; iv) if the in-progress emergency state of the group is set to a value of "false" and if the received SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function shall: A) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and B) if the in-progress imminent peril state of the group is set to a value of "false", shall set the in- progress imminent peril state of the group to a value of "true"; v) shall invite each group member determined in step 13)g)i) above, to the group session, as specified in clause 9.2.1.4.1.1; and vi) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and 14) if the MCVideo group call is ongoing then: … c) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; … e) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined in step 14) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; f) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": i) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 101 ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; iii) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; and C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.6; iv) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and v) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; g) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function: i) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and ii) if the in-progress imminent peril state of the group is set to a value of "false": A) shall set the in-progress imminent peril state of the group to a value of "true"; B) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.15; and C) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and iii) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; h) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.4.2; i) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; j) shall include in the SIP 200 (OK) response with the warning text set to "123 MCVideo session already exists" as specified in clause 4.4; k) if the received SIP re-INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 102 l) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 4: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. m) shall interact with media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 5: Resulting media plane processing is completed before the next step is performed. n) shall send the SIP 200 (OK) response towards the inviting MCVideo client or inviting non-controlling MCVideo function according to 3GPP TS 24.229 [11]; o) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; NOTE 6: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. p) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]; q) Upon receiving a SIP ACK to the above SIP 200 (OK) response and the SIP 200 (OK) response contained a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall follow the procedures in clause 6.3.3.1.18; and r) shall not continue with the rest of the clause. Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 9.2.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [30], the timer TNG1 (acknowledged call setup timer) is not running, the controlling MCVideo function supports media buffering and the SIP final response is not yet sent to the inviting MCVideo client: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) shall include a P-Answer-State header field with the value "Unconfirmed"; 5) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 7: Resulting user plane processing is completed before the next step is performed. 8) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 103 9) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 8: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 10) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response for a SIP INVITE request as specified in clause 9.2.1.4.1.2 containing an indication of required group members, the timer TNG1 (acknowledged call setup timer) is running and all SIP 200 (OK) responses have been received to all SIP INVITE requests sent to MCVideo clients specified in clause 9.2.1.4.1.1, then the controlling MCVideo function shall wait until the SIP 200 (OK) response has been received to the SIP INVITE request specified in clause 9.2.1.4.1.2 before generating a SIP 200 (OK) response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group". Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1 that was sent to an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24]; and 1) if the MCVideo ID in the SIP 200 (OK) response matches to the MCVideo ID in the corresponding SIP INVITE request; 2) there are no outstanding SIP 200 (OK) responses to SIP INVITE requests which were sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24]; and 3) there is no outstanding SIP 200 (OK) response to a SIP INVITE request sent in clause 9.2.1.4.1.2 where the SIP 183 (Session Progress) response contained an indication of required group members; the controlling MCVideo function: 1) shall stop timer TNG1 (acknowledged call setup timer) as described in clause 6.3.3.3; 2) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 3) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has been exceeded the <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 4) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 5) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 9: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 7) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 10: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 8) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon: 1) receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1; 2) the timer TNG1 (acknowledged call setup timer) is not running; 3) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; 4) the controlling MCVideo function supports media buffering; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 104 5) the SIP final response has not yet been sent to the inviting MCVideo client; the controlling MCVideo function according to local policy: 1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has exceeded the <max- participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 5) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 11: Resulting media plane processing is completed before the next step is performed. 7) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 8) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 12: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 9) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon expiry of timer TNG1 (acknowledged call setup timer), if there are outstanding SIP 200 (OK) responses to SIP INVITE requests sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the procedures specified in clause 6.3.3.3. If timer TNG1 (acknowledged call setup timer) is running and a final SIP 4xx, 5xx or 6xx response is received from an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the relevant procedures specified in clause 6.3.3.3. If: 1) timer TNG1 (acknowledged call setup timer) is not running; 2) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; and 3) a final SIP 4xx, 5xx or 6xx response is received from an invited MCVideo client; then the controlling MCVideo function shall perform one of the following based on policy: 1) send the SIP final response towards the inviting MCVideo client, according to 3GPP TS 24.229 [11], if a SIP final response was received from all the other invited MCVideo clients and the SIP 200 (OK) response is not yet sent; or ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 105 2) remove the invited MCVideo client from the MCVideo Session as specified in clause 6.3.3.1.5, if a SIP final response other than 2xx or 3xx was received from all the invited MCVideo clients and the SIP 200 (OK) response is already sent. The controlling MCVideo function may invite an additional member of the prearranged MCVideo group as specified in clause 9.2.1.4.1 that has not already been invited, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24], and all members have not yet been invited. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.3] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.7] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a SIP re-INVITE request for an MCVideo session identity identifying an on-demand prearranged MCVideo group session, the controlling MCVideo function: … 2) if received SIP re-INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; … 4) if the received SIP re-INVITE request contains an imminent peril indication set to "true" for an MCVideo imminent peril group call and this is an unauthorised request for an MCVideo imminent peril group call as determined by clause 6.3.3.1.13.6, shall reject the SIP re-INVITE request … 5) if a Resource-Priority header field is included in the received SIP re-INVITE request: a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP re- INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP re-INVITE request … and skip the rest of the steps; and b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP re- INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request …and skip the rest of the steps; 6) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true" and is an authorised request to initiate an MCVideo emergency group call as determined by clause 6.3.3.1.13.2, the controlling MCVideo function shall: i) shall cache the MCVideo ID of the MCVideo user that has initiated an MCVideo emergency call; ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the MCVideo ID of the MCVideo user that has initiated an MCVideo emergency alert; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 106 iii) if the in-progress emergency state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's emergency indication as specified in clause 6.3.3.1.11, setting the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and C) if the in-progress imminent peril state of the group is set to a value of "true", shall set it to a value of "false"; and iv) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; NOTE 2: The interactions of TNG2 with the TNG3 (group call timer) are explained in clause 6.3.3.5.2. Editor's Note: timers need to be defined. C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other participants of the MCVideo group call as specified in clause 6.3.3.1.6; D) shall send the SIP re-INVITEs towards the other participants of the MCVideo group call; and E) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; 7) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is an unauthorised request for an MCVideo emergency group call cancellation as determined by clause 6.3.3.1.13.4: a) shall reject the SIP re-INVITE request; … c) if an <alert-ind> element of the mcvideoinfo MIME body is included in the SIP re-INVITE request set to "false", and there is an outstanding MCVideo emergency alert for this MCVideo user, shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <alert-ind> element set to a value of "true"; and d) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [11] and skip the rest of the steps; 8) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is determined to be an authorised request for an MCVideo emergency call cancellation as specified in clause 6.3.3.1.16 and the in-progress emergency state of the group to is set to a value of "true" the controlling MCVideo function: a) shall set the in-progress emergency group state of the group to a value of "false"; b) shall clear the cache of the MCVideo ID of the MCVideo user as having an outstanding MCVideo emergency group call; c) if an <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body is included and set to "false" and is determined to be an authorised request for an MCVideo emergency alert cancellation as specified in clause 6.3.3.1.13.3 and there is an outstanding MCVideo emergency alert for this MCVideo user shall: i) if the received SIP re-INVITE request contains an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, clear the cache of the MCVideo ID of the MCVideo user identified by the <originated-by> element as having an outstanding MCVideo emergency alert; or ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 107 ii) if the received SIP re-INVITE request does not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, clear the cache of the MCVideo ID of the sender of the SIP re-INVITE request as having an outstanding MCVideo emergency alert; d) shall generate SIP re-INVITE requests to the participants in the group call as specified in clause 6.3.3.1.6. The MCVideo controlling function: i) for each of the other participants in the group call shall send the SIP re-INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and ii) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; NOTE 3: Clause 6.3.3.1.5 will inform the group call participants of the cancellation of the MCVideo group's in- progress emergency state and the cancellation of the MCVideo emergency alert if applicable. e) shall stop timer TNG2 (in-progress emergency group call timer); and NOTE 4: The interactions of TNG2 with the TNG3 (group call timer) are explained in clause 6.3.3.5.2; f) for each of the affiliated members of the group that are not participating in the call: i) generate a SIP MESSAGE request notification of the cancellation of the MCVideo user's emergency call as specified in clause 6.3.3.1.11; ii) set the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; iii) if indicated above in step 8) c), set the <alert-ind> element of the application/vnd.3gpp.mcvideo- info+xml MIME body to a value of "false"; and iv) send the SIP MESSAGE request according to 3GPP TS 24.229 [11]; 9) if the received SIP re-INVITE request contains an imminent peril indication and the in-progress emergency group state of the group is set to a value of "false", shall perform the procedures specified in clause 9.2.1.4.8 and skip the rest of the steps. Upon receiving a SIP 200 (OK) response to a SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; 1) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [11]; 2) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [11] with the clarifications specified in clause 6.3.3.2.1; 3) shall include the "norefersub" option tag in a Supported header field according to IETF RFC 4488 [31]; 4) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [32]; 5) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "true" and if this is an unauthorised request for an MCVideo emergency alert as determined by clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "false" and if this is an unauthorised request for an MCVideo emergency alert cancellation as determined by clause 6.3.3.1.13.3, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true", this is an authorised request for an MCVideo imminent peril group call and the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 108 NOTE 5: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. 8) shall interact with media plane as specified in 3GPP TS 24.581 [5]; and 9) shall send the SIP 200 (OK) response towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18. Upon receipt of a SIP 2xx response for an outgoing SIP MESSAGE request, shall handle according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.1.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.1.4.2 or as the result of receiving a SIP 403 (Forbidden) response as described in this clause. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited.; NOTE 1: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 2: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 3) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the MCVideo ID of the terminating user; and b) the <mcvideo-calling-group-id> element set to the group identity; NOTE 3: The <mcvideo-calling-user-id> is already included in the MIME body as a result of calling clause 6.3.3.1.2 in step 1). 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; 6) if the in-progress emergency state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.19; b) if the received SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true": i) shall include in the outgoing SIP INVITE request in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 109 ii) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcvideo-info+xml MIME body and the application/vnd.3gpp.location- info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false"; and c) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.19; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; and 9) shall send the SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response containing a Require header field with the option tag "100rel" and containing a P-Answer-State header field with the value "Unconfirmed" in response to the SIP INVITE request the controlling MCVideo function: 1) shall send a SIP PRACK request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; 2) shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 9.2.3.4; and 3) shall increment the local counter of the number of SIP 200 (OK) responses received from invited members, by 1. NOTE 4: The notifications above could be sent prior to the SIP 200 (OK) response being sent to the inviting MCVideo client. These notifications received by MCVideo clients that are group members do not mean that the group session will be successfully established. NOTE 5: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 110 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.1.2] "The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the non-controlling MCVideo function serving the group identity of the MCVideo group owned by the partner MCVideo system; 3) shall set the P-Asserted-Identity to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the group identity of the MCVideo group hosted by the non- controlling MCVideo function in the partner MCVideo system; and b) the <mcvideo-calling-group-id> element set to the group identity of the group served by the controlling MCVideo function; 5) shall include the Recv-Info header field set to g.3gpp.mcvideo-transmission-request; 6) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and 8) shall send the SIP INVITE request towards the partner MCVideo system in accordance with 3GPP TS 24.229 [11]. Upon receiving SIP 403 (Forbidden) response for the SIP INVITE request, if according to local policy and if: 1) the response contains a Warning header field with the MCVideo warning code "128"; and 2) the response contains a P-Refused-URI-List header field and an application/resource-lists+xml MIME body as specified in IETF RFC 5318 [28]; NOTE 1: The application/resource-lists+xml MIME body contains MCVideo IDs identifying MCVideo users in a partner MCVideo system that needs to be invited to the prearranged group call in case of group regrouping using interrogating method. Editor's Note: The above note currently isn't defined in the 23.280 and 23.281. then the controlling MCVideo function: 1) shall check if the number of members of the MCVideo group exceeds the value contained in the <on-network- max-participant-count> element of the group document as specified in 3GPP TS 24.481 [24]. If exceeded, the controlling MCVideo function shall invite only <on-network-max-participant-count> members from the application/resource-lists+xml MIME body; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 111 NOTE 2: The <on-network-max-participant-count> element indicates the maximum number of participants allowed in the prearranged group session It is operator policy that determines which participants in the application/resource-lists+xml MIME body are invited to the group call. 2) shall invite MCVideo users as specified in this clause using the list of MCVideo IDs in URI-List. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and NOTE 3: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2. 2) if at least one of the invited MCVideo clients has subscribed to the conference package, shall subscribe to the conference event package in the non-controlling MCVideo function as specified in clause 9.2.3.4.3." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.6] "This clause is referenced from other procedures. This clause describes the procedures for inviting an MCVideo user to an MCVideo session associated with an MCVideo emergency group call or MCVideo imminent peril group call. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.2.4.1.1. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the address of the terminating participating MCVideo function associated with the MCVideo ID of the targeted MCVideo user; 3) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element populated as follows: a) the <mcvideo-request-uri> element set to the value of the MCVideo ID of the targeted MCVideo user; b) the <mcvideo-calling-user-id> element set to the value of the MCVideo ID of the calling MCVideo user; and c) the <mcvideo-calling-group-id> element set to the value of the MCVideo group ID of the emergency group call. 4) shall include in the P-Asserted-Identity header field the public service identity of the controlling MCVideo function; 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and 6) if the in-progress emergency group state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.18; b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; c) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.12.1, shall populate the application/vnd.3gpp.mcvideo- info+xml MIME body and the application/vnd.3gpp.mcvideo-location-info+xml MIME body as specified in clause 6.3.3.1.11. Otherwise, shall set the <alert-ind> element to a value of "false" in the application/vnd.3gpp.mcvideo-info+xml MIME body; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 112 d) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; NOTE: If the imminent peril state of the group is true at this point, the controlling function will set it to false as part of the calling procedure. 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.18; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; and 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains an <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.12.2] "If the controlling MCVideo function has received a SIP request for an MCVideo group call with the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of "true" and: 1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true" and: a) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and: i) if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) contains the identity of the MCVideo group targeted by the calling MCVideo user; and ii) if the <allow-MCVideo-emergency-call> element of the <list-service> element of the group document identified by the targeted MCVideo group identity is set to a value of "true" as specified in 3GPP TS 24.481 [24]; then the controlling MCVideo function shall consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call and skip the remaining steps; or; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 113 b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup" and if the <allow-MCVideo-emergency-call> element of the <list- service> element of the group document identified by the targeted MCVideo group identity is set to a value of "true" as specified in 3GPP TS 24.481 [24]; then the controlling MCVideo function shall consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call and skip the remaining steps; or 2) if the controlling MCVideo function does not consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call by step 1) above, then the controlling MCVideo function shall consider the MCVideo emergency group call request to be an unauthorised request for an MCVideo emergency group call. If the controlling MCVideo function has received a SIP request for an MCVideo private call with the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of "true" and: 1) if the <allow-emergency-private-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true"; and a) if the "entry-info" attribute of the <entry> element of the <MCVideoPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UsePreConfigured" and if the MCVideo ID targeted for the call is contained in the <uri-entry> element of the <entry> element of the <MCVideoPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element (see the MCVideo user profile document in 3GPP TS 24.484 [25]); or b) if the "entry-info" attribute of the <entry> element of the <MCVideoPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "LocallyDetermined"; then the controlling MCVideo function shall consider the MCVideo emergency private call request to be an authorised request for an MCVideo emergency private call and skip step 2) below; or 2) if the controlling MCVideo function does not consider the MCVideo emergency private call request to be an authorised request for an MCVideo emergency private call by step 1) above, then the controlling MCVideo function shall consider the MCVideo emergency private call request to be an unauthorised request for an MCVideo emergency private call." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.12.4] "If the controlling MCVideo function has received a SIP request with the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of "false" and: 1) if the <allow-cancel-emergency-alert> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true", then the MCVideo emergency alert cancellation request shall be considered to be an authorised request for an MCVideo emergency alert cancellation; and 2) if the <allow-cancel-emergency-alert> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "false", then the MCVideo emergency alert cancellation request shall be considered to be an unauthorised request for an MCVideo emergency alert cancellation." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 114 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.2.1] "When composing the SDP answer according to 3GPP TS 24.229 [11], the controlling MCVideo function: 1) for the accepted media stream in the received SDP offer: a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the controlling MCVideo function; and 2) for the accepted media-transmission control entity, if present in the received SDP offer: a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the controlling MCVideo function, for the accepted media-transmission control entity, if present in the received SDP offer; and b) shall include 'fmtp' attributes as specified in 3GPP TS 24.581 clause 14." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.2.2] "On receipt of an initial SIP INVITE request the controlling MCVideo function shall cache SIP feature tags, if received in the Contact header field and if the specific feature tags are supported." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.1] "The transmission control server arbitration logic in the transmission control server shall support the procedures in clauses 6.3.2 and 6.3.3 and shall behave according to the transmission control server state transition diagram for 'general transmission control operation' in clause 6.3.4. The transmission control interface towards the MCVideo client in the transmission control server shall behave according to the transmission control server state transition diagram for 'basic transmission control operation towards the transmission participant' as specified in clause 6.3.5. The reception control arbitration logic in the transmission control server shall support the procedures in clauses 6.3.2 and 6.3.3 and shall behave according to the reception control server state transition diagram for 'general reception control operation' in clause 6.3.6. The transmission control interface towards the MCVideo client in the transmission control server shall behave according to the transmission control server state transition diagram for 'basic reception control operation towards the transmission participant' as specified in clause 6.3.7." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.2.2] "When an MCVideo call is established a new instance of the transmission control server state machine for 'general transmission control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' is added. When an MCVideo call is established a new instance of the transmission control server state machine for 'general reception control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic reception control operation towards the transmission participant' is added. If the optional "mc_queueing" feature is supported and has been negotiated as specified in clause 14, the transmission control server could queue the implicit transmission control request for the media-transmission control entity. The original initial SIP INVITE request or SIP REFER request to establish an MCVideo chat group call or to rejoin an ongoing MCVideo call is not handled as an implicit transmission control request message by the transmission control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request. The permission to send media to the inviting MCVideo client due to implicit transmission control request is applicable to both confirmed indication and unconfirmed indication. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 115 When the first unconfirmed indication is received from the invited participating MCVideo function (see 3GPP TS 24.281 [2]) the transmission control server optionally can give an early indication to send RTP media packets, to the inviting MCVideo client. If an early indication to send RTP media packets is given to the inviting MCVideo client, the transmission participant is granted the permission to send media and the MCVideo server buffers RTP media packets received from the MCVideo client at least until the first invited MCVideo client accepts the invitation or until the RTP media packet buffer exceeds it maximum limit to store RTP media packets. If the MCVideo server does not support or does not allow media buffering then when an early indication to send RTP media packets is not given to the inviting MCVideo client, the transmission participant is granted the permission to send media when the first invited MCVideo client accepts the media. Before the transmission control server sends the first transmission control message in the MCVideo call, the transmission control server has to assign itself a SSRC identifier to be included in media transmission control messages and quality feedback messages if the MCVideo server is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3]. The transmission participant and the transmission control server can negotiate the maximum priority level that the transmission participant is permitted to request. The transmission control server can pre-empt the current sender based on the negotiated maximum priority level that the transmission participant is permitted to request and the priority level included in the Transmission Media Request message. NOTE: The maximum priority level that a transmission participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the controlling MCVideo function from the group management server as described in 3GPP TS 24.481 [12] and service configuration data retrieved by the controlling MCVideo function from the configuration management server as described in 3GPP TS 24.484 [13]. The transmission participant and the transmission control server can negotiate queueing of Transmission requests using the "mc_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the transmission control server queues the transmission control request if a Transmission Media Request message is received when another transmission participant has the transmission and the priority of the current speaker is the same or higher." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.1] "The transmission control messages are coded as described in clause 9.1.2 where the transmission control message is part of the application-dependent data. For the transmission control protocol the ASCII name string is: MCVx (Mission Critical Video x) with x=0, 1 or 2 as specified in clause 9.1.2. A list of transmission control messages can be found in clause 9.2.2.1. The transmission control specific fields are specified in clause 9.2.3." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 116 When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 117 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 118 d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine;and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and 2. shall set the general state to 'G: pending Transmission Revoke'." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 119 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 120 ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 121 b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.5.3 Test description | 5.1.1.5.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). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 122 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). - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are registered and authorized to use the MCVideo system. - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are affiliated to the pre-arranged group and are authorized to initiate group calls. - The IUT (MCVideo Server) is the controlling server of the pre-arranged group. 5.1.1.5.3.2 Test procedure sequence Table 5.1.1.5.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E group call establishment' as described in Annex A, Table A.4.1.4.3-1 to establish an emergency pre- arranged group call with implicit transmission control request according to option b.ii of note in Annex A, Table A.4.1.4.3-1, initiated by SS-UE1 (MCVideo Client)? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure ' MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1, to end SS- UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1, to request permission to transmit for 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 5.1.1.5.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.1.1.5.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.1.1.5.3.2-1; Step 1, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-1, with condition EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 123 Table 5.1.1.5.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.5.3.2-1; Step 2, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-2, with condition EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.5.3.3-3: SIP 200 (OK) from SS (MCVideo Server) (Step 1, Table 5.1.1.5.3.2-1; Step 8, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-6 Table 5.1.1.5.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.1.1.5.3.2-1; Step 9, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-7 Table 5.1.1.5.3.3-5: Transmission Idle from IUT (MCVideo Server) (Step 2, Table 5.1.1.5.3.2-1; Steps 4 and 5, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-6, with condition EMERGENCY-CALL. Table 5.1.1.5.3.3-6: Transmission Request from SS (MCVideo Server) (Step 3, Table 5.1.1.5.3.2-1; Step 1, Annex A, Table A.3.7.3-1) Derivation Path: Annex A, Table A.3.7.4-1, with condition EMERGENCY-CALL. Table 5.1.1.5.3.3-7: Transmission Granted from IUT (MCVideo Server) (Steps 1 and 3, Table 5.1.1.5.3.2-1; Step 3a1 or 3b1, Annex A, Table A.3.7.3-1; Step 9a1, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.3.7.4-2 or A.3.7.4-3 (note), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. Table 5.1.1.5.3.3-8: Media Transmission Notification from IUT (MCVideo Server) (Steps 1 and 3, Table 5.1.1.5.3.2-1; Step 3a3 or 3b2, Annex A, Table A.3.7.3-1; Step 10a1, Annex A, Table 4.1.1.3-1) Derivation Path: Annex A, Table A.3.7.4-4 or A.3.7.4-5 (note), with condition EMERGENCY-CALL. NOTE: Depends on server implementation. 5.1.1.6 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Emergency Group Call / Terminating Participating server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.6.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to SS (MCVideo Server) } ensure that { when { the SS (MCVideo Server) providing the controlling function initiates an emergency pre- arranged group call with automatic commencement } then { IUT (MCVideo Server) accepts the call and establishes the call with SS-UE2 (MCVideo Client) and forwards the media transmission notification received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 124 (2) with { IUT (MCVideo Server) having established an emergency pre-arranged group call } ensure that { when { the SS (MCVideo Server) ends the media transmission } then { IUT (MCVideo Server) forwards the transmission end notify received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) and forwards the transmission idle received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established an emergency pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the controlling function ends the pre-arranged group call } then { IUT (MCVideo Server) sends a SIP BYE message to SS-UE2 (MCVideo Client) and responds by sending a SIP 200 (OK) message to SS (MCVideo Server) } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.6.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 9.2.1.3.2, 9.2.1.3.4, 6.3.2.1.6.0, 6.3.2.1.6.1, 6.3.3.1.6, 6.3.2.2.5.1, 6.3.2.2.6.1, 6.3.2.2.8.1, 6.3.2.2.4.2, 6.3.2.2.2.1 and 6.3.2.1.2.1, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.2] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. NOTE 1: This clause covers on-demand session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: … 2) shall check the presence of the isfocus media feature tag in the URI of the Contact header field and if it is not present then the participating MCVideo function shall reject the request …, and shall not continue with the rest of the steps; 3) if the Answer-Mode Indication in the application/poc-settings+xml MIME body has not yet been received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4, shall reject the request …, and shall not continue with the rest of the steps; 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; 5) if the binding between the MCVideo ID and public user identity does not exist, then the participating MCVideo function shall reject the SIP INVITE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps; 6) if the SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC- GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 125 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.4] "Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.2.8.1." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.6.0] "This clause contains common procedures to be used for MCVideo emergency group calls and MCVideo imminent peril group calls." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.6.1] "When the participating MCVideo function receives a request from the MCVideo client to originate an MCVideo emergency group call and needs to determine if the request is an authorised request for an MCVideo emergency call, the participating MCVideo function shall check the following: 1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true" and: a) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element contains the identity of the MCVideo group targeted by the calling MCVideo user; or b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup"; then the participating MCVideo function shall consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call; In all other cases, the participating MCVideo function shall consider the request to originate an MCVideo emergency group call to be an unauthorised request to originate an MCVideo emergency group call. When the participating MCVideo function receives a request from the MCVideo client to originate an MCVideo imminent peril group call and needs to determine if the request is an authorised request for an MCVideo imminent peril group call the participating MCVideo function shall check the following: 1) if the <allow-imminent-peril-call> element of <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true"; and a) if the "entry-info" attribute of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element contains the identity of the MCVideo group targeted by the calling MCVideo user; or b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup"; then the participating MCVideo function shall consider the MCVideo imminent peril group call request to be an authorised request for an MCVideo emergency group call; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 126 In all other cases, the participating MCVideo function shall consider the request to originate an MCVideo imminent peril group call to be an unauthorised request to originate an MCVideo imminent peril call." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.6] "This clause is referenced from other procedures. This clause describes the procedures for inviting an MCVideo user to an MCVideo session associated with an MCVideo emergency group call or MCVideo imminent peril group call. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.2.4.1.1. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the address of the terminating participating MCVideo function associated with the MCVideo ID of the targeted MCVideo user; 3) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element populated as follows: a) the <mcvideo-request-uri> element set to the value of the MCVideo ID of the targeted MCVideo user; b) the <mcvideo-calling-user-id> element set to the value of the MCVideo ID of the calling MCVideo user; and c) the <mcvideo-calling-group-id> element set to the value of the MCVideo group ID of the emergency group call. 4) shall include in the P-Asserted-Identity header field the public service identity of the controlling MCVideo function; 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and 6) if the in-progress emergency group state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.18; b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; c) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.12.1, shall populate the application/vnd.3gpp.mcvideo- info+xml MIME body and the application/vnd.3gpp.mcvideo-location-info+xml MIME body as specified in clause 6.3.3.1.11. Otherwise, shall set the <alert-ind> element to a value of "false" in the application/vnd.3gpp.mcvideo-info+xml MIME body; and d) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; NOTE: If the imminent peril state of the group is true at this point, the controlling function will set it to false as part of the calling procedure. 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.18; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 127 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains an <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.5.1] "When receiving a "SIP INVITE request for terminating participating MCVideo function" that requires automatic commencement mode: 1) if: a) the invited MCVideo client has one or more pre-established sessions without an associated MCVideo session; b) the media-level sections for the offered MCVideo video media stream are the same as the media-level sections for MCVideo video media stream in an existing pre-established session; and c) the media-level section of the offered media-transmission control entity is the same as the media-level section for media-transmission control entity in an existing pre-established session; then the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.5.3; or 2) otherwise the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.5.2." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.6.1] "When receiving a "SIP INVITE request for terminating participating MCVideo function" that requires manual commencement mode: 1) if: a) the invited MCVideo client has one or more pre-established sessions without an associated MCVideo session; b) the media-level sections for the offered MCVideo video media stream are the same as the media-level section for MCVideo video media stream in the existing pre-established session; and c) the media-level section of the offered media-transmission control entity is the same as the media-level section for media-transmission control entity in the existing pre-established session; then the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.6.3; or 2) otherwise the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.6.2." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.8.1] "Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function: 1) shall interact with the media plane as specified in clause 6.4 in 3GPP TS 24.581 [5] for releasing media plane resource associated with the SIP session with the controlling MCVideo function; 2) shall generate a SIP BYE request according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 128 3) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP BYE request to the P- Asserted-Identity header field of the outgoing SIP BYE request; 4) if the received SIP BYE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body into the outgoing SIP BYE request; and 5) shall send the SIP BYE request to the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the SIP BYE request the participating MCVideo function: 1) shall send a SIP 200 (OK) response to the SIP BYE request received from the controlling MCVideo function according to 3GPP TS 24.229 [11]; and 2) shall interact with the media plane as specified in 3GPP TS 24.581 [5] for releasing media plane resources associated with the SIP session with the MCVideo client." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.4.2] "This clause is referenced from other procedures. When sending SIP 200 (OK) responses, the participating MCVideo function shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [11] and: 1) shall include the option tag "timer" in a Require header field; 2) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [23], "UAS Behavior". If no "refresher" parameter was included in the SIP INVITE request, the "refresher" parameter in the Session-Expires header field shall be set to "uas"; 3) shall include the following in the Contact header field: a) the g.3gpp.mcvideo media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; and c) an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP INVITE request from the controlling MCVideo function; 4) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [32]; and 5) if the incoming SIP response contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body to the outgoing SIP 200 (OK) response." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.2.1] "The participating MCVideo function shall follow the procedures in clause 6.3.2.1.2.1." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.2.1] "When composing the SDP answer according to 3GPP TS 24.229 [11], the participating MCVideo function: 1) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCVideo function, for the accepted media stream in the received SDP offer, if required; and NOTE 1: Requirements can exist for the participating MCVideo function to be always included in the path of the offered media stream, for example: for the support of features such as MBMS, lawful interception and recording. Other examples can exist. 2) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCVideo function, for the accepted media-transmission control entity, if present in the received SDP offer. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 129 NOTE 2: If the participating MCVideo function and the controlling MCVideo function are in the same MCVideo server, and the participating MCVideo function does not have a dedicated IP address or a dedicated port number for media transmission control or media stream, the replacement of the IP address or the port number is omitted." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.1] "Once an on-demand MCVideo session is established or a pre-established session is in use when the participating MCVideo function receives transmission control messages from the transmission participant in the MCVideo client or from the transmission control server in the controlling MCVideo function, the behaviour of the participating MCVideo function is described in the following clauses." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 130 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 131 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 132 d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine;and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 133 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and 2. shall set the general state to 'G: pending Transmission Revoke'." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 134 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 135 NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 136 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.6.3 Test description | 5.1.1.6.3.1 Pre-test conditions System Simulator: - SS (MCVideo Server), providing the controlling MCVideo function. - SS-UE2 (MCVideo Client). IUT: - IUT (MCVideo Server), providing the terminating participating 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 some sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server and the HTTP Client. Preamble: - The IUT (MCVideo Server) is connected to SS (MCVideo Server) and SS-UE2 (MCVideo Client). - The SS-UE2 (MCVideo client) is registered and authorized to use the MCVideo system. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 137 - The SS-UE2 (MCVideo client) is affiliated to the pre-arranged group and is authorized to initiate group calls. 5.1.1.6.3.2 Test procedure sequence Table 5.1.1.6.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CT group/private call establishment, automatic commencement' as described in Annex A, Table A.4.3.3.3-1 to establish an emergency pre-arranged group call with automatic commencement mode and notify a media transmission from SS-UE1 (MCVideo Client)? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Notification - Idle' as described in Annex A, Table A.4.3.8.3-1 to notify the end of SS-UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E call release' as described in Annex A, Table A.4.3.5.3-1, to release the call? - - 3 P 5.1.1.6.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.1.1.6.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.1.1.6.3.2-1; Step 1, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-1, with conditions GROUP-CALL and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.6.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.6.3.2-1; Step 2, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-2, with conditions GROUP-CALL and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.6.3.3-3: SIP 200 (OK) from SS-UE2 (MCVideo Client) (Step 1, Table 5.1.1.6.3.2-1; Step 6, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-7, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.6.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.1.1.6.3.2-1; Step 7, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-8, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 138 Table 5.1.1.6.3.3-5: Transmission Idle (Step 2, Table 5.1.1.6.3.2-1; Steps 13 and 14, Annex A, Table A.4.3.8.3-1) Derivation Path: Annex A, Table A.4.3.8.4-6, with condition EMERGENCY-CALL. Table 5.1.1.6.3.3-6: Media Transmission Notification (Step 1, Table 5.1.1.6.3.2-1; Steps 10a1 and 10a2, Annex A, Table 4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-11, with condition EMERGENCY-CALL. 5.1.1.7 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Emergency Group Call / Originating Participating server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.7.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to SS (MCVideo Server) } ensure that { when { the SS-UE1 (MCVideo Client) initiates an emergency pre-arranged group call with implicit transmission control } then { IUT (MCVideo Server) accepts the call from initiator and establishes the call with the SS (MCVideo Server) providing the controlling function and forwards the transmission granted received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established an emergency pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) forwards the transmission end request to SS (MCVideo Server) and forwards the transmission end response to SS-UE1 (MCVideo Client) and forwards the transmission idle received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established an emergency pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control } then { IUT (MCVideo Server) forwards the transmission request to SS (MCVideo Server) and forwards the transmission granted received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (4) with { IUT (MCVideo Server) having established an emergency pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) ends the pre-arranged group call } then { IUT (MCVideo Server) sends a SIP BYE message to SS (MCVideo Server) providing the controlling function and responds by sending a SIP 200 (OK) message to SS-UE1 (MCVideo Client) } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.7.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 9.2.1.3.1.1, 9.2.1.3.3, 6.2.8.1.1, 6.3.1.1, 6.3.2.1.3, 6.3.2.1.1.1 and 6.3.2.1.6.1, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.1.1] "In the procedures in this clause: 1) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 139 2) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 3) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "prearranged", the participating MCVideo function: 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The participating MCVideo function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [15]. Otherwise, continue with the rest of the steps; NOTE 1: if the SIP INVITE request contains an emergency indication or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCVideo function can according to local policy choose to accept the request. 2) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and shall authorise the calling user; NOTE 2: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. 3) if through local policy in the participating MCVideo function, the user identified by the MCVideo ID is not authorised to initiate prearranged group calls, shall reject the "SIP INVITE request for originating participating MCVideo function" with a SIP 403 (Forbidden) response to the SIP INVITE request, with warning text set to "109 user not authorised to make prearranged group calls" in a Warning header field as specified in clause 4.4; 4) shall validate the media parameters and if the MCVideo codecs are not offered in the SIP INVITE request shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; 5) shall check if the number of maximum simultaneous MCVideo group calls supported for the MCVideo user as specified in the <MaxSimultaneousCallsN6> element of the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) has been exceeded. If exceeded, the participating MCVideo function shall respond with a SIP 486 (Busy Here) response with the warning text set to "103 maximum simultaneous MCVideo group calls reached" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps; NOTE 3: If the SIP INVITE request contains an emergency indication or an imminent peril indication, the participating MCVideo function can by means beyond the scope of this specification choose to allow for an exception to the limit for the maximum simultaneous MCVideo sessions supported for the MCVideo user. Alternatively, a lower priority session of the MCVideo user could be terminated to allow for the new session. 6) if the user identified by the MCVideo ID is not affiliated to the group identified in the "SIP INVITE request for originating participating MCVideo function" as determined by clause 8.2.2.2.11 and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, shall perform the actions specified in clause 8.2.2.2.12 for implicit affiliation; 7) if the actions for implicit affiliation specified in step 6) above were performed but not successful in affiliating the MCVideo user due to the MCVideo user already having N2 simultaneous affiliations, shall reject the "SIP INVITE request for originating participating MCVideo function" with a SIP 486 (Busy Here) response with the warning text set to "102 too many simultaneous affiliations" in a Warning header field as specified in clause 4.4. and skip the rest of the steps. NOTE 4: N2 is the total number of MCVideo groups that an MCVideo user can be affiliated to simultaneously as specified in 3GPP TS 23.281 [26]. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 140 NOTE 5: if the SIP INVITE request contains an emergency indication set to a value of "true" or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCVideo function can according to local policy choose to allow an exception to the N2 limit. Alternatively, a lower priority affiliation of the MCVideo user could be cancelled to allow for the new affiliation. 8) shall determine the public service identity of the controlling MCVideo function associated with the group identity in the SIP INVITE request; NOTE 6: The public service identity can identify the controlling MCVideo function in the primary MCVideo system or a partner MCVideo system. NOTE 7: How the participating MCVideo server discovers the public service identity of the controlling MCVideo function associated with the group identity is out of scope of the current release. 9) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3; 10) shall set the Request-URI to the public service identity of the controlling MCVideo function associated with the group identity which was present in the incoming SIP INVITE request; 11) shall not copy the following header fields from the incoming SIP INVITE request to the outgoing SIP INVITE request, if they were present in the incoming SIP INVITE request: a) Answer-Mode header field as specified in IETF RFC 5373 [27]; and b) Priv-Answer-Mode header field as specified in IETF RFC 5373 [27]; 12) shall set the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; 14) if the received SIP INVITE request contains an application/vnd.3gpp.location-info+xml MIME body and if not already copied, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body received in the SIP INVITE request into an application/vnd.3gpp.location-info+xml MIME body included in the outgoing SIP request; 15) if a Resource-Priority header field was included in the received SIP INVITE request, shall include a Resource- Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCVideo client; and NOTE 8: The participating MCVideo function will leave verification of the Resource-Priority header field to the controlling MCVideo function. 16) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. Upon receipt of a SIP 302 (Moved Temporarily) response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.2.1.10; 2) shall include an SDP offer based upon the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; and 3) shall forward the SIP INVITE request according to 3GPP TS 24.229 [11]. Upon receipt of a SIP 2xx response in response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) if the received SIP 2xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC-GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 2) shall generate a SIP 200 (OK) response as in clause 6.3.2.1.5.2; 3) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 141 4) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 5) shall include the public service identity received in the P-Asserted-Identity header field of the incoming SIP 200 (OK) response into the P-Asserted-Identity header field of the outgoing SIP 200 (OK) response; 6) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 7) if the procedures of clause 8.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 8.2.2.2.13; 8) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 9) shall interact with Media Plane as specified in 3GPP TS 24.581 [5]; and 10) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [23]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request in step 14) the participating MCVideo function: 1) shall generate a SIP response according to 3GPP TS 24.229 [11]; 2) shall include Warning header field(s) that were received in the incoming SIP response; 3) shall forward the SIP response to the MCVideo client according to 3GPP TS 24.229 [11]; and 4) if the implicit affiliation procedures of clause 8.2.2.2.12 were invoked in this procedure, shall perform the procedures of clause 8.2.2.2.14;" [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.3] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.1.6." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.2.8.1.1] "This clause is referenced from other procedures. When the MCVideo emergency state is set and this MCVideo user and MCVideo group are authorised to initiate MCVideo emergency group calls as determined by the procedures of clause 6.2.8.1.8, the MCVideo client: 1) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the SIP INVITE request, an <emergency-ind> element set to "true" and if the MCVideo emergency group call state is set to "MVEGC 1: emergency-gc-capable", shall set the MCVideo emergency group call state to "MVEGC 2: emergency-call- requested"; 2) if the MCVideo user has also requested an MCVideo emergency alert to be sent and this is an authorised request for MCVideo emergency alert as determined by the procedures of clause 6.2.8.1.6, and the MCVideo emergency alert state is set to "MVEA 1: no-alert", shall: a) set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to "true" and set the MCVideo emergency alert state to "MVEA 2: emergency-alert-confirm-pending"; and b) perform the procedures specified in clause 6.2.9.1 for the MCVideo emergency alert trigger; 3) if the MCVideo user has not requested an MCVideo emergency alert to be sent and the MCVideo emergency alert state is set to "MVEA 1: no-alert", shall set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to "false"; and 4) if the MCVideo client emergency group state of the group is set to a value other than "MVEG 2: in-progress" set the MCVideo client emergency group state of the MCVideo group to "MVEG 3: confirm-pending". NOTE 1: This is the case of an MCVideo user already being in the MCVideo emergency state it initiated previously while originating an MCVideo emergency group call or MCVideo emergency alert. All group calls the MCVideo user originates while in MCVideo emergency state will be MCVideo emergency group calls. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 142 When the MCVideo emergency state is clear and the MCVideo emergency group call state is set to "MVEGC 1: emergency-gc-capable" and the MCVideo user is authorised to initiate an MCVideo emergency group call on the targetted MCVideo group as determined by the procedures of clause 6.2.8.1.8, the MCVideo client shall set the MCVideo emergency state and perform the following actions: 1) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the SIP INVITE request an <emergency-ind> element set to "true" and set the MCVideo emergency group call state to "MVEGC 2: emergency-call-requested" state; 2) if the MCVideo user has also requested an MCVideo emergency alert to be sent and this is an authorised request for MCVideo emergency alert as determined by the procedures of clause 6.2.8.1.6, shall: a) include in the application/vnd.3gpp.mcvideo-info+xml MIME body the <alert-ind> element set to "true" and set the MCVideo emergency alert state to "MVEA 2: emergency-alert-confirm-pending"; and b) perform the procedures specified in clause 6.2.9.1 for the MCVideo emergency alert trigger; 3) if the MCVideo user has not requested an MCVideo emergency alert to be sent, shall set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to "false"; and 4) if the MCVideo client emergency group state of the group is set to a value other than "MVEG 2: in-progress" shall set the MCVideo client emergency group state of the MCVideo group to "MVEG 3: confirm-pending". NOTE 2: This is the case of an initial MCVideo emergency group call and optionally an MCVideo emergency alert being sent. As the MCVideo emergency state is not sent, there is no MCVideo emergency alert outstanding. NOTE 3: An MCVideo group call originated by an affiliated member of an MCVideo group which is in an in- progress emergency state (as tracked on the MCVideo client by the MCVideo client emergency group state) but is not in an MCVideo emergency state of their own will also be an MCVideo emergency group call. The <emergency-ind> and <alert-ind> elements of the application/vnd.3gpp.mcvideo-info+xml MIME body do not need to be included in this case and hence no action needs to be taken in this clause." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.1.1] "The MCVideo server needs to distinguish between the following initial SIP INVITE requests for originations and terminations: - SIP INVITE requests routed to the participating MCVideo function as a result of processing initial filter criteria at the S-CSCF in accordance with the origination procedures as specified in 3GPP TS 24.229 [11] and the Request-URI is set to a public service identity of the participating MCVideo function that does not identify the pre-established session set-up. Such requests are known as "SIP INVITE request for originating participating MCVideo function" in the procedures in the present document; - SIP INVITE requests routed to the participating MCVideo function as a result of processing initial filter criteria at the S-CSCF in accordance with the termination procedures as specified in 3GPP TS 24.229 [11] and the Request-URI contains a PSI of the terminating participating MCVideo function. Such requests are known as "SIP INVITE request for terminating participating MCVideo function" in the procedures in the present document; - SIP INVITE requests routed to the controlling MCVideo function as a result of PSI routing on the originating side in accordance with the originating procedures as specified in 3GPP TS 24.229 [11], or as a result of direct PSI routing, in accordance with the termination procedures as specified in 3GPP TS 24.229 [11], the Request-URI is set to a public service identity for MCVideo private call and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [16]. Such requests are known as "SIP INVITE request for controlling MCVideo function of a private call" in the procedures in the present document; - SIP INVITE requests routed to the controlling MCVideo function as a result of PSI routing on the originating side in accordance with the originating procedures as specified in 3GPP TS 24.229 [11], or as a result of direct PSI routing, in accordance with the termination procedures as specified in 3GPP TS 24.229 [11], the Request-URI is set to a public service identity serving an MCVideo group and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [16]. Such requests are known as "SIP INVITE request for controlling MCVideo function of an MCVideo group" in the procedures in the present document; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 143 - SIP INVITE requests routed to the controlling MCVideo function as a result of PSI routing on the originating side in accordance with the originating procedures as specified in 3GPP TS 24.229 [11], or as a result of direct PSI routing, in accordance with the termination procedures as specified in 3GPP TS 24.229 [11], the Request-URI is set to a public service identity for MCVideo ambient viewing call and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [22]. Such requests are known as "SIP INVITE request for controlling MCVideo function of an ambient viewing call" in the procedures in the present document." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.3] "This clause is referenced from other procedures. When generating an initial SIP INVITE request according to 3GPP TS 24.229 [11], on receipt of an incoming SIP INVITE request, the participating MCVideo function: 1) shall include in the SIP INVITE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [20] if included in the incoming SIP INVITE request; 2) should include the Session-Expires header field according to IETF RFC 4028 [23]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 3) shall include the option tag "timer" in the Supported header field; 4) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP INVITE request to the P- Asserted-Identity header field of the outgoing SIP INVITE request; 5) shall include the g.3gpp.mcvideo media feature tag into the Contact header field of the outgoing SIP INVITE request; 6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; 7) if the incoming SIP INVITE request contained a MIME resource-lists body with the MCVideo ID of the invited MCVideo user, shall copy the MIME resource-lists body, according to rules and procedures of IETF RFC 5366 [37]; 8) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the contents of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request to the outgoing SIP INVITE request; and 9) if the incoming SIP INVITE request contained an application/vnd.3gpp.location-info+xml MIME body, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body of the incoming SIP INVITE request to the outgoing SIP INVITE request." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.1.1] "This clause is referenced from other clauses. The SDP offer is generated based on the received SDP offer. The SDP offer generated by the participating MCVideo function: 1) shall contain two SDP media-level sections for MCVideo video media as contained in the received SDP offer; and 2) shall contain an SDP media-level section for one media-transmission control entity, if present in the received SDP offer. When composing the SDP offer according to 3GPP TS 24.229 [11], the participating MCVideo function: 1) shall replace the IP address and port number for the offered media stream in the received SDP offer with the IP address and port number of the participating MCVideo function, if required; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 144 NOTE 1: Requirements can exist for the participating MCVideo function to be always included in the path of the offered media stream, for example: for the support of features such as MBMS, lawful interception and recording. Other examples can exist. 2) shall replace the IP address and port number for the offered media transmission control entity, if any, in the received SDP offer with the IP address and port number of the participating MCVideo function; and NOTE 2: If the participating MCVideo function and the controlling MCVideo function are in the same MCVideo server, and the participating MCVideo function does not have a dedicated IP address or a dedicated port number for media transmission control or media stream, the replacement of the IP address or the port number is omitted. 3) shall contain an "a=key-mgmt" attribute field with a "mikey" attribute value, if present in the received SDP offer." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.6.1] "When the participating MCVideo function receives a request from the MCVideo client to originate an MCVideo emergency group call and needs to determine if the request is an authorised request for an MCVideo emergency call, the participating MCVideo function shall check the following: 1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true" and: a) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element contains the identity of the MCVideo group targeted by the calling MCVideo user; or b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup"; then the participating MCVideo function shall consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call; In all other cases, the participating MCVideo function shall consider the request to originate an MCVideo emergency group call to be an unauthorised request to originate an MCVideo emergency group call. When the participating MCVideo function receives a request from the MCVideo client to originate an MCVideo imminent peril group call and needs to determine if the request is an authorised request for an MCVideo imminent peril group call the participating MCVideo function shall check the following: 1) if the <allow-imminent-peril-call> element of <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true"; and a) if the "entry-info" attribute of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element contains the identity of the MCVideo group targeted by the calling MCVideo user; or b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup"; then the participating MCVideo function shall consider the MCVideo imminent peril group call request to be an authorised request for an MCVideo emergency group call; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 145 In all other cases, the participating MCVideo function shall consider the request to originate an MCVideo imminent peril group call to be an unauthorised request to originate an MCVideo imminent peril call." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.1] "Once an on-demand MCVideo session is established or a pre-established session is in use when the participating MCVideo function receives transmission control messages from the transmission participant in the MCVideo client or from the transmission control server in the controlling MCVideo function, the behaviour of the participating MCVideo function is described in the following clauses." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 146 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 147 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 148 d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine;and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 149 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and 2. shall set the general state to 'G: pending Transmission Revoke'." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 150 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 151 NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 152 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.7.3 Test description | 5.1.1.7.3.1 Pre-test conditions System Simulator: - SS (MCVideo Server), providing the controlling MCVideo function. - SS-UE1 (MCVideo Client). IUT: - IUT (MCVideo Server), providing the originating participating 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 some sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server and the HTTP Client. Preamble: - The IUT (MCVideo Server) is connected to SS (MCVideo Server) and SS-UE1 (MCVideo Client). - The SS-UE1 (MCVideo client) is registered and authorized to use the MCVideo system. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 153 - The SS-UE1 (MCVideo client) is affiliated to the pre-arranged group and is authorized to initiate group calls. 5.1.1.7.3.2 Test procedure sequence Table 5.1.1.7.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 CO session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.4.2.1.3-1 to establish an emergency pre-arranged group call with implicit transmission control request according to option b.ii of note in Annex A, Table A.4.2.1.3-1, initiated by SS-UE1 (MCVideo Client? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO Transmission End Request - Transmission End Response' as described in Annex A, Table A.4.2.5.3-1 to end SS-UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Transmission Granted' as described in Annex A, Table A.4.2.4.3-1, to request permission to transmit for SS-UE1 (MCVideo Client)? - - 3 P 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO call release' as described in Annex A, Table A.4.2.3.3-1, to release the call? - - 4 P 5.1.1.7.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.1.1.7.3.3-1: SIP INVITE from SS-UE1 (MCVideo Client) (Step 1, Table 5.1.1.7.3.2-1; Step 1, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-1, with conditions GROUP-CALL and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.7.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.7.3.2-1; Step 2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-2, with conditions GROUP-CALL and EMERGENCY-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.7.3.3-3: SIP 200 (OK) from SS (MCVideo Server) (Step 1, Table 5.1.1.7.3.2-1; Step 5, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-3, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 154 Table 5.1.1.7.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.1.1.7.3.2-1; Step 6, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-4, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.7.3.3-5: Transmission Idle (Steps 2, Table 5.1.1.7.3.2-1; Steps 9 and 10, Annex A, Table A.4.2.5.3-1) Derivation Path: Annex A, Table A.4.2.5.4-3, with condition EMERGENCY-CALL. Table 5.1.1.7.3.3-6: Transmission Request (Step 3, Table 5.1.1.7.3.2-1; Steps 1 and 2, Annex A, Table A.4.2.4.3-1) Derivation Path: Annex A, Table A.4.2.4.4-1, with condition EMERGENCY-CALL. Table 5.1.1.7.3.3-7: Transmission Granted (Steps 1 and 3, Table 5.1.1.7.3.2-1; Steps 5 and 6, Annex A, Table A.4.2.4.3-1; Steps 9a1 and 9a2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.4.4-2, with condition EMERGENCY-CALL. 5.1.1.8 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Imminent Peril Group Call / Controlling server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.8.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 an imminent peril pre-arranged group call with implicit transmission control } then { IUT (MCVideo Server) accepts the call from initiator and establishes the call with all affiliated users by sending call establishment requests to 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 an imminent peril pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) sends transmission control idle to SS-UE1 (MCVideo Client) and sends transmission control idle to SS-UE2 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established an imminent peril pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control } then { IUT (MCVideo Server) sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 155 (4) with { IUT (MCVideo Server) having established an imminent peril pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function ends the pre- arranged group 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.1.1.8.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 9.2.1.4.2, 9.2.1.4.3, 9.2.1.4.1.1, 9.2.1.4.1.2, 6.3.3.1.6, 6.3.3.1.12.2, 6.3.3.1.12.4, 6.3.3.2.1 and 6.3.3.2.2, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.3.1, 6.3.2.2, 9.2.1, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.2] "In the procedures in this clause: 1) MCVideo ID in an incoming SIP INVITE request refers to the MCVideo ID of the originating user from the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 3) MCVideo ID in an outgoing SIP INVITE request refers to the MCVideo ID of the called user in the <mcvideo- request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) indication of required group members in a SIP 183 (Session Progress) response refers to the <required> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to "true" in a SIP 183 (Session Progress) sent by the non-controlling MCVideo function of an MCVideo group; 5) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 6) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for controlling MCVideo function of an MCVideo group", the controlling MCVideo function: … 2) shall determine if the media parameters are acceptable and the MCVideo codecs are offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps; 3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if: a) an Accept-Contact header field does not include the g.3gpp.mcvideo media feature tag; or b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; 4) if received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; 5) shall retrieve the necessary group document(s) from the group management server for the group identity contained in the SIP INVITE request and carry out initial processing as specified in clause 6.3.5.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 156 6) if the result of the initial processing in clause 6.3.5.2 was: a) that authorization of the MCVideo ID is required at a non-controlling MCVideo function of an MCVideo group is required, perform the actions in clause 6.3.3.1.13.7 and do not continue with the rest of the steps in this clause; and b) that a SIP 3xx, 4xx, 5xx or 6xx response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group" has been sent, do not continue with the rest of the steps in this clause; 7) shall perform the actions as described in clause 6.3.3.2.2; 8) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero; 9) shall determine if an MCVideo group call for the group identity is already ongoing by determining if an MCVideo session identity has already been allocated for the group call and the MCVideo session is active; … 12) if a Resource-Priority header field is included in the SIP INVITE request: a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; or b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; 13) if the MCVideo group call is not ongoing then: … c) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined as determined in step 13) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; d) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; e) shall create a prearranged group session and allocate an MCVideo session identity for the prearranged group call, and shall handle timer TNG3 (group call timer) as specified in clause 6.3.3.5; f) if the group identity in the "SIP INVITE request for controlling MCVideo function of an MCVideo group" is a TGI: i) shall for each of the constituent MCVideo groups homed on the primary MCVideo system: …; B) if the controlling MCVideo function owns the MCVideo group identified by the MCVideo group ID then: I) determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; II) invite each group member determined in step A) above, to the group session, as specified in clause 9.2.1.4.1.1; and III) interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 157 ii) shall for each of the constituent MCVideo groups homed on the partner MCVideo system generate a SIP INVITE request for the MCVideo group identity homed on the partner MCVideo system as specified in clause 9.2.1.4.1.2; and g) if the group identity in the SIP INVITE request for controlling MCVideo function of an MCVideo group is an MCVideo group ID: i) shall determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; ii) if necessary, shall start timer TNG1 (acknowledged call setup timer) according to the conditions stated in clause 6.3.3.3; iii) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": A) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; and C) if the in-progress emergency state of the group is set to a value of "false": I) shall set the value of the in-progress emergency state of the group to "true"; and II) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; iv) if the in-progress emergency state of the group is set to a value of "false" and if the received SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function shall: A) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and B) if the in-progress imminent peril state of the group is set to a value of "false", shall set the in- progress imminent peril state of the group to a value of "true"; v) shall invite each group member determined in step 13)g)i) above, to the group session, as specified in clause 9.2.1.4.1.1; and vi) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and 14) if the MCVideo group call is ongoing then: … c) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; … e) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined in step 14) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; f) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": i) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 158 ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; iii) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; and C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.6; iv) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and v) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; g) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function: i) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and ii) if the in-progress imminent peril state of the group is set to a value of "false": A) shall set the in-progress imminent peril state of the group to a value of "true"; B) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.15; and C) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and iii) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; h) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.4.2; i) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; j) shall include in the SIP 200 (OK) response with the warning text set to "123 MCVideo session already exists" as specified in clause 4.4; k) if the received SIP re-INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 159 l) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 4: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. m) shall interact with media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 5: Resulting media plane processing is completed before the next step is performed. n) shall send the SIP 200 (OK) response towards the inviting MCVideo client or inviting non-controlling MCVideo function according to 3GPP TS 24.229 [11]; o) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; NOTE 6: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. p) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]; q) Upon receiving a SIP ACK to the above SIP 200 (OK) response and the SIP 200 (OK) response contained a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall follow the procedures in clause 6.3.3.1.18; and r) shall not continue with the rest of the clause. Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 9.2.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [30], the timer TNG1 (acknowledged call setup timer) is not running, the controlling MCVideo function supports media buffering and the SIP final response is not yet sent to the inviting MCVideo client: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) shall include a P-Answer-State header field with the value "Unconfirmed"; 5) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 7: Resulting user plane processing is completed before the next step is performed. 8) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 160 9) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 8: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 10) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response for a SIP INVITE request as specified in clause 9.2.1.4.1.2 containing an indication of required group members, the timer TNG1 (acknowledged call setup timer) is running and all SIP 200 (OK) responses have been received to all SIP INVITE requests sent to MCVideo clients specified in clause 9.2.1.4.1.1, then the controlling MCVideo function shall wait until the SIP 200 (OK) response has been received to the SIP INVITE request specified in clause 9.2.1.4.1.2 before generating a SIP 200 (OK) response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group". Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1 that was sent to an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24]; and 1) if the MCVideo ID in the SIP 200 (OK) response matches to the MCVideo ID in the corresponding SIP INVITE request; 2) there are no outstanding SIP 200 (OK) responses to SIP INVITE requests which were sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24]; and 3) there is no outstanding SIP 200 (OK) response to a SIP INVITE request sent in clause 9.2.1.4.1.2 where the SIP 183 (Session Progress) response contained an indication of required group members; the controlling MCVideo function: 1) shall stop timer TNG1 (acknowledged call setup timer) as described in clause 6.3.3.3; 2) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 3) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has been exceeded the <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 4) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 5) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 9: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 7) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 10: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 8) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon: 1) receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1; 2) the timer TNG1 (acknowledged call setup timer) is not running; 3) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; 4) the controlling MCVideo function supports media buffering; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 161 5) the SIP final response has not yet been sent to the inviting MCVideo client; the controlling MCVideo function according to local policy: 1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has exceeded the <max- participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 5) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 11: Resulting media plane processing is completed before the next step is performed. 7) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 8) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 12: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 9) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon expiry of timer TNG1 (acknowledged call setup timer), if there are outstanding SIP 200 (OK) responses to SIP INVITE requests sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the procedures specified in clause 6.3.3.3. If timer TNG1 (acknowledged call setup timer) is running and a final SIP 4xx, 5xx or 6xx response is received from an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the relevant procedures specified in clause 6.3.3.3. If: 1) timer TNG1 (acknowledged call setup timer) is not running; 2) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; and 3) a final SIP 4xx, 5xx or 6xx response is received from an invited MCVideo client; then the controlling MCVideo function shall perform one of the following based on policy: 1) send the SIP final response towards the inviting MCVideo client, according to 3GPP TS 24.229 [11], if a SIP final response was received from all the other invited MCVideo clients and the SIP 200 (OK) response is not yet sent; or ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 162 2) remove the invited MCVideo client from the MCVideo Session as specified in clause 6.3.3.1.5, if a SIP final response other than 2xx or 3xx was received from all the invited MCVideo clients and the SIP 200 (OK) response is already sent. The controlling MCVideo function may invite an additional member of the prearranged MCVideo group as specified in clause 9.2.1.4.1 that has not already been invited, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24], and all members have not yet been invited. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.3] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.7] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a SIP re-INVITE request for an MCVideo session identity identifying an on-demand prearranged MCVideo group session, the controlling MCVideo function: … 2) if received SIP re-INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; … 4) if the received SIP re-INVITE request contains an imminent peril indication set to "true" for an MCVideo imminent peril group call and this is an unauthorised request for an MCVideo imminent peril group call as determined by clause 6.3.3.1.13.6, shall reject the SIP re-INVITE request … 5) if a Resource-Priority header field is included in the received SIP re-INVITE request: a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP re- INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP re-INVITE request … and skip the rest of the steps; and b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP re- INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request …and skip the rest of the steps; 6) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true" and is an authorised request to initiate an MCVideo emergency group call as determined by clause 6.3.3.1.13.2, the controlling MCVideo function shall: i) shall cache the MCVideo ID of the MCVideo user that has initiated an MCVideo emergency call; ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the MCVideo ID of the MCVideo user that has initiated an MCVideo emergency alert; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 163 iii) if the in-progress emergency state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's emergency indication as specified in clause 6.3.3.1.11, setting the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and C) if the in-progress imminent peril state of the group is set to a value of "true", shall set it to a value of "false"; and iv) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; NOTE 2: The interactions of TNG2 with the TNG3 (group call timer) are explained in clause 6.3.3.5.2. Editor's Note: timers need to be defined. C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other participants of the MCVideo group call as specified in clause 6.3.3.1.6; D) shall send the SIP re-INVITEs towards the other participants of the MCVideo group call; and E) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; 7) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is an unauthorised request for an MCVideo emergency group call cancellation as determined by clause 6.3.3.1.13.4: a) shall reject the SIP re-INVITE request. … c) if an <alert-ind> element of the mcvideoinfo MIME body is included in the SIP re-INVITE request set to "false", and there is an outstanding MCVideo emergency alert for this MCVideo user, shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <alert-ind> element set to a value of "true"; and d) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [11] and skip the rest of the steps; 8) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is determined to be an authorised request for an MCVideo emergency call cancellation as specified in clause 6.3.3.1.16 and the in-progress emergency state of the group to is set to a value of "true" the controlling MCVideo function: a) shall set the in-progress emergency group state of the group to a value of "false"; b) shall clear the cache of the MCVideo ID of the MCVideo user as having an outstanding MCVideo emergency group call; c) if an <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body is included and set to "false" and is determined to be an authorised request for an MCVideo emergency alert cancellation as specified in clause 6.3.3.1.13.3 and there is an outstanding MCVideo emergency alert for this MCVideo user shall: i) if the received SIP re-INVITE request contains an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, clear the cache of the MCVideo ID of the MCVideo user identified by the <originated-by> element as having an outstanding MCVideo emergency alert; or ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 164 ii) if the received SIP re-INVITE request does not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, clear the cache of the MCVideo ID of the sender of the SIP re-INVITE request as having an outstanding MCVideo emergency alert; d) shall generate SIP re-INVITE requests to the participants in the group call as specified in clause 6.3.3.1.6. The MCVideo controlling function: i) for each of the other participants in the group call shall send the SIP re-INVITE request towards the MCVideo client as specified in 3GPP TS 24.229 [11]; and ii) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; NOTE 3: Clause 6.3.3.1.5 will inform the group call participants of the cancellation of the MCVideo group's in- progress emergency state and the cancellation of the MCVideo emergency alert if applicable. e) shall stop timer TNG2 (in-progress emergency group call timer); and NOTE 4: The interactions of TNG2 with the TNG3 (group call timer) are explained in clause 6.3.3.5.2; f) for each of the affiliated members of the group that are not participating in the call: i) generate a SIP MESSAGE request notification of the cancellation of the MCVideo user's emergency call as specified in clause 6.3.3.1.11; ii) set the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "false"; iii) if indicated above in step 8) c), set the <alert-ind> element of the application/vnd.3gpp.mcvideo- info+xml MIME body to a value of "false"; and iv) send the SIP MESSAGE request according to 3GPP TS 24.229 [11]; 9) if the received SIP re-INVITE request contains an imminent peril indication and the in-progress emergency group state of the group is set to a value of "false", shall perform the procedures specified in clause 9.2.1.4.8 and skip the rest of the steps. Upon receiving a SIP 200 (OK) response to a SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; 1) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [11]; 2) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [11] with the clarifications specified in clause 6.3.3.2.1; 3) shall include the "norefersub" option tag in a Supported header field according to IETF RFC 4488 [31]; 4) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [32]; 5) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "true" and if this is an unauthorised request for an MCVideo emergency alert as determined by clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <alert-ind> element set to a value of "false" and if this is an unauthorised request for an MCVideo emergency alert cancellation as determined by clause 6.3.3.1.13.3, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true", this is an authorised request for an MCVideo imminent peril group call and the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 165 NOTE 5: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. 8) shall interact with media plane as specified in 3GPP TS 24.581 [5]; and 9) shall send the SIP 200 (OK) response towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18. Upon receipt of a SIP 2xx response for an outgoing SIP MESSAGE request, shall handle according to 3GPP TS 24.229 [11]." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.1.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.1.4.2 or as the result of receiving a SIP 403 (Forbidden) response as described in this clause. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited.; NOTE 1: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 2: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 3) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the MCVideo ID of the terminating user; and b) the <mcvideo-calling-group-id> element set to the group identity; NOTE 3: The <mcvideo-calling-user-id> is already included in the MIME body as a result of calling clause 6.3.3.1.2 in step 1). 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; 6) if the in-progress emergency state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.19; b) if the received SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true": i) shall include in the outgoing SIP INVITE request in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 166 ii) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcvideo-info+xml MIME body and the application/vnd.3gpp.location- info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false"; and c) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.19; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; and 9) shall send the SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response containing a Require header field with the option tag "100rel" and containing a P-Answer-State header field with the value "Unconfirmed" in response to the SIP INVITE request the controlling MCVideo function: 1) shall send a SIP PRACK request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; 2) shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 9.2.3.4; and 3) shall increment the local counter of the number of SIP 200 (OK) responses received from invited members, by 1. NOTE 4: The notifications above could be sent prior to the SIP 200 (OK) response being sent to the inviting MCVideo client. These notifications received by MCVideo clients that are group members do not mean that the group session will be successfully established. NOTE 5: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 167 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.1.2] "The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the non-controlling MCVideo function serving the group identity of the MCVideo group owned by the partner MCVideo system; 3) shall set the P-Asserted-Identity to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the group identity of the MCVideo group hosted by the non- controlling MCVideo function in the partner MCVideo system; and b) the <mcvideo-calling-group-id> element set to the group identity of the group served by the controlling MCVideo function; 5) shall include the Recv-Info header field set to g.3gpp.mcvideo-transmission-request; 6) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and 8) shall send the SIP INVITE request towards the partner MCVideo system in accordance with 3GPP TS 24.229 [11]. Upon receiving SIP 403 (Forbidden) response for the SIP INVITE request, if according to local policy and if: 1) the response contains a Warning header field with the MCVideo warning code "128"; and 2) the response contains a P-Refused-URI-List header field and an application/resource-lists+xml MIME body as specified in IETF RFC 5318 [28]; NOTE 1: The application/resource-lists+xml MIME body contains MCVideo IDs identifying MCVideo users in a partner MCVideo system that needs to be invited to the prearranged group call in case of group regrouping using interrogating method. Editor's Note: The above note currently isn't defined in the 23.280 and 23.281. then the controlling MCVideo function: 1) shall check if the number of members of the MCVideo group exceeds the value contained in the <on-network- max-participant-count> element of the group document as specified in 3GPP TS 24.481 [24]. If exceeded, the controlling MCVideo function shall invite only <on-network-max-participant-count> members from the application/resource-lists+xml MIME body; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 168 NOTE 2: The <on-network-max-participant-count> element indicates the maximum number of participants allowed in the prearranged group session It is operator policy that determines which participants in the application/resource-lists+xml MIME body are invited to the group call. 2) shall invite MCVideo users as specified in this clause using the list of MCVideo IDs in URI-List. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and NOTE 3: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2. 2) if at least one of the invited MCVideo clients has subscribed to the conference package, shall subscribe to the conference event package in the non-controlling MCVideo function as specified in clause 9.2.3.4.3." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.6] "This clause is referenced from other procedures. This clause describes the procedures for inviting an MCVideo user to an MCVideo session associated with an MCVideo emergency group call or MCVideo imminent peril group call. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.2.4.1.1. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the address of the terminating participating MCVideo function associated with the MCVideo ID of the targeted MCVideo user; 3) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element populated as follows: a) the <mcvideo-request-uri> element set to the value of the MCVideo ID of the targeted MCVideo user; b) the <mcvideo-calling-user-id> element set to the value of the MCVideo ID of the calling MCVideo user; and c) the <mcvideo-calling-group-id> element set to the value of the MCVideo group ID of the emergency group call. 4) shall include in the P-Asserted-Identity header field the public service identity of the controlling MCVideo function; 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and 6) if the in-progress emergency group state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.18; b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; c) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.12.1, shall populate the application/vnd.3gpp.mcvideo- info+xml MIME body and the application/vnd.3gpp.mcvideo-location-info+xml MIME body as specified in clause 6.3.3.1.11. Otherwise, shall set the <alert-ind> element to a value of "false" in the application/vnd.3gpp.mcvideo-info+xml MIME body; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 169 d) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; NOTE: If the imminent peril state of the group is true at this point, the controlling function will set it to false as part of the calling procedure. 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.18; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; and 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains an <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.12.2] "If the controlling MCVideo function has received a SIP request for an MCVideo group call with the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of "true" and: 1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true" and: a) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and: i) if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) contains the identity of the MCVideo group targeted by the calling MCVideo user; and ii) if the <allow-MCVideo-emergency-call> element of the <list-service> element of the group document identified by the targeted MCVideo group identity is set to a value of "true" as specified in 3GPP TS 24.481 [24]; then the controlling MCVideo function shall consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call and skip the remaining steps; or; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 170 b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup" and if the <allow-MCVideo-emergency-call> element of the <list- service> element of the group document identified by the targeted MCVideo group identity is set to a value of "true" as specified in 3GPP TS 24.481 [24]; then the controlling MCVideo function shall consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call and skip the remaining steps; or 2) if the controlling MCVideo function does not consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call by step 1) above, then the controlling MCVideo function shall consider the MCVideo emergency group call request to be an unauthorised request for an MCVideo emergency group call. If the controlling MCVideo function has received a SIP request for an MCVideo private call with the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of "true" and: 1) if the <allow-emergency-private-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true"; and a) if the "entry-info" attribute of the <entry> element of the <MCVideoPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UsePreConfigured" and if the MCVideo ID targeted for the call is contained in the <uri-entry> element of the <entry> element of the <MCVideoPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element (see the MCVideo user profile document in 3GPP TS 24.484 [25]); or b) if the "entry-info" attribute of the <entry> element of the <MCVideoPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "LocallyDetermined"; then the controlling MCVideo function shall consider the MCVideo emergency private call request to be an authorised request for an MCVideo emergency private call and skip step 2) below; or 2) if the controlling MCVideo function does not consider the MCVideo emergency private call request to be an authorised request for an MCVideo emergency private call by step 1) above, then the controlling MCVideo function shall consider the MCVideo emergency private call request to be an unauthorised request for an MCVideo emergency private call." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.12.4] "If the controlling MCVideo function has received a SIP request with the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to a value of "false" and: 1) if the <allow-cancel-emergency-alert> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true", then the MCVideo emergency alert cancellation request shall be considered to be an authorised request for an MCVideo emergency alert cancellation; and 2) if the <allow-cancel-emergency-alert> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "false", then the MCVideo emergency alert cancellation request shall be considered to be an unauthorised request for an MCVideo emergency alert cancellation." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 171 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.2.1] "When composing the SDP answer according to 3GPP TS 24.229 [11], the controlling MCVideo function: 1) for the accepted media stream in the received SDP offer: a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the controlling MCVideo function; and 2) for the accepted media-transmission control entity, if present in the received SDP offer: a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the controlling MCVideo function, for the accepted media-transmission control entity, if present in the received SDP offer; and b) shall include 'fmtp' attributes as specified in 3GPP TS 24.581 clause 14." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.2.2] "On receipt of an initial SIP INVITE request the controlling MCVideo function shall cache SIP feature tags, if received in the Contact header field and if the specific feature tags are supported." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.2.1] "The transmission control server arbitration logic in the transmission control server shall support the procedures in clauses 6.3.2 and 6.3.3 and shall behave according to the transmission control server state transition diagram for 'general transmission control operation' in clause 6.3.4. The transmission control interface towards the MCVideo client in the transmission control server shall behave according to the transmission control server state transition diagram for 'basic transmission control operation towards the transmission participant' as specified in clause 6.3.5. The reception control arbitration logic in the transmission control server shall support the procedures in clauses 6.3.2 and 6.3.3 and shall behave according to the reception control server state transition diagram for 'general reception control operation' in clause 6.3.6. The transmission control interface towards the MCVideo client in the transmission control server shall behave according to the transmission control server state transition diagram for 'basic reception control operation towards the transmission participant' as specified in clause 6.3.7." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.2.2] "When an MCVideo call is established a new instance of the transmission control server state machine for 'general transmission control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' is added. When an MCVideo call is established a new instance of the transmission control server state machine for 'general reception control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic reception control operation towards the transmission participant' is added. If the optional "mc_queueing" feature is supported and has been negotiated as specified in clause 14, the transmission control server could queue the implicit transmission control request for the media-transmission control entity. The original initial SIP INVITE request or SIP REFER request to establish an MCVideo chat group call or to rejoin an ongoing MCVideo call is not handled as an implicit transmission control request message by the transmission control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request. The permission to send media to the inviting MCVideo client due to implicit transmission control request is applicable to both confirmed indication and unconfirmed indication. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 172 When the first unconfirmed indication is received from the invited participating MCVideo function (see 3GPP TS 24.281 [2]) the transmission control server optionally can give an early indication to send RTP media packets, to the inviting MCVideo client. If an early indication to send RTP media packets is given to the inviting MCVideo client, the transmission participant is granted the permission to send media and the MCVideo server buffers RTP media packets received from the MCVideo client at least until the first invited MCVideo client accepts the invitation or until the RTP media packet buffer exceeds it maximum limit to store RTP media packets. If the MCVideo server does not support or does not allow media buffering then when an early indication to send RTP media packets is not given to the inviting MCVideo client, the transmission participant is granted the permission to send media when the first invited MCVideo client accepts the media. Before the transmission control server sends the first transmission control message in the MCVideo call, the transmission control server has to assign itself a SSRC identifier to be included in media transmission control messages and quality feedback messages if the MCVideo server is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3]. The transmission participant and the transmission control server can negotiate the maximum priority level that the transmission participant is permitted to request. The transmission control server can pre-empt the current sender based on the negotiated maximum priority level that the transmission participant is permitted to request and the priority level included in the Transmission Media Request message. NOTE: The maximum priority level that a transmission participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the controlling MCVideo function from the group management server as described in 3GPP TS 24.481 [12] and service configuration data retrieved by the controlling MCVideo function from the configuration management server as described in 3GPP TS 24.484 [13]. The transmission participant and the transmission control server can negotiate queueing of Transmission requests using the "mc_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the transmission control server queues the transmission control request if a Transmission Media Request message is received when another transmission participant has the transmission and the priority of the current speaker is the same or higher." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.1] "The transmission control messages are coded as described in clause 9.1.2 where the transmission control message is part of the application-dependent data. For the transmission control protocol the ASCII name string is: MCVx (Mission Critical Video x) with x=0, 1 or 2 as specified in clause 9.1.2. A list of transmission control messages can be found in clause 9.2.2.1. The transmission control specific fields are specified in clause 9.2.3." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 173 When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 174 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 175 d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine;and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and 2. shall set the general state to 'G: pending Transmission Revoke'." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 176 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 177 ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 178 b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.8.3 Test description | 5.1.1.8.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). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 179 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). - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are registered and authorized to use the MCVideo system. - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are affiliated to the pre-arranged group and are authorized to initiate group calls. - The IUT (MCVideo Server) is the controlling server of the pre-arranged group. 5.1.1.8.3.2 Test procedure sequence Table 5.1.1.8.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E group call establishment' as described in Annex A, Table A.4.1.4.3-1 to establish an imminent peril pre-arranged group call with implicit transmission control request according to option b.ii of note in Annex A, Table A.4.1.4.3-1, initiated by SS-UE1 (MCVideo Client)? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure ' MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1, to end SS-UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1, to request permission to transmit for 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 5.1.1.8.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.1.1.8.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.1.1.8.3.2-1; Step 1, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-1, with condition IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 180 Table 5.1.1.8.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.8.3.2-1; Step 2, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-2, with condition IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.8.3.3-3: SIP 200 (OK) from SS (MCVideo Server) (Step 1, Table 5.1.1.8.3.2-1; Step 8, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-6 Table 5.1.1.8.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.1.1.8.3.2-1; Step 9, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-7 Table 5.1.1.8.3.3-5: Transmission Idle from IUT (MCVideo Server) (Step 2, Table 5.1.1.8.3.2-1; Steps 4 and 5, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-6, with condition IMMPERIL-CALL. Table 5.1.1.8.3.3-6: Transmission Request from SS (MCVideo Server) (Step 3, Table 5.1.1.8.3.2-1; Step 1, Annex A, Table A.3.7.3-1) Derivation Path: Annex A, Table A.3.7.4-1, with condition IMMPERIL-CALL. Table 5.1.1.8.3.3-7: Transmission Granted from IUT (MCVideo Server) (Steps 1 and 3, Table 5.1.1.8.3.2-1; Step 3a1 or 3b1, Annex A, Table A.3.7.3-1; Step 9a1, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.3.7.4-2 or A.3.7.4-3 (note), with condition IMMPERIL-CALL. NOTE: Depends on server implementation. Table 5.1.1.8.3.3-8: Media Transmission Notification from IUT (MCVideo Server) (Steps 1 and 3, Table 5.1.1.8.3.2-1; Step 3a3 or 3b2, Annex A, Table A.3.7.3-1; Step 10a1, Annex A, Table 4.1.1.3-1) Derivation Path: Annex A, Table A.3.7.4-4 or A.3.7.4-5 (note), with condition IMMPERIL-CALL. NOTE: Depends on server implementation. 5.1.1.9 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Imminent Peril Group Call / Terminating Participating server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.9.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to SS (MCVideo Server) } ensure that { when { the SS (MCVideo Server) providing the controlling function initiates an imminent peril pre- arranged group call with automatic commencement } then { IUT (MCVideo Server) accepts the call and establishes the call with SS-UE2 (MCVideo Client) and forwards the media transmission notification received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 181 (2) with { IUT (MCVideo Server) having established an imminent peril pre-arranged group call } ensure that { when { the SS (MCVideo Server) ends the media transmission } then { IUT (MCVideo Server) forwards the transmission end notify received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) and forwards the transmission idle received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established an imminent peril pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the controlling function ends the pre-arranged group call } then { IUT (MCVideo Server) sends a SIP BYE message to SS-UE2 (MCVideo Client) and responds by sending a SIP 200 (OK) message to SS (MCVideo Server) } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.9.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 9.2.1.3.2, 9.2.1.3.4, 6.3.2.1.6.0, 6.3.2.1.6.1, 6.3.3.1.6, 6.3.2.2.5.1, 6.3.2.2.6.1, 6.3.2.2.8.1, 6.3.2.2.4.2, 6.3.2.2.2.1 and 6.3.2.1.2.1, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.2] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. NOTE 1: This clause covers on-demand session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: … 2) shall check the presence of the isfocus media feature tag in the URI of the Contact header field and if it is not present then the participating MCVideo function shall reject the request …, and shall not continue with the rest of the steps; 3) if the Answer-Mode Indication in the application/poc-settings+xml MIME body has not yet been received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4, shall reject the request …, and shall not continue with the rest of the steps; 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; 5) if the binding between the MCVideo ID and public user identity does not exist, then the participating MCVideo function shall reject the SIP INVITE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps; 6) if the SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC- GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 182 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.4] "Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.2.8.1." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.6.0] "This clause contains common procedures to be used for MCVideo emergency group calls and MCVideo imminent peril group calls." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.6.1] "When the participating MCVideo function receives a request from the MCVideo client to originate an MCVideo emergency group call and needs to determine if the request is an authorised request for an MCVideo emergency call, the participating MCVideo function shall check the following: 1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true" and: a) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element contains the identity of the MCVideo group targeted by the calling MCVideo user; or b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup"; then the participating MCVideo function shall consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call; In all other cases, the participating MCVideo function shall consider the request to originate an MCVideo emergency group call to be an unauthorised request to originate an MCVideo emergency group call. When the participating MCVideo function receives a request from the MCVideo client to originate an MCVideo imminent peril group call and needs to determine if the request is an authorised request for an MCVideo imminent peril group call the participating MCVideo function shall check the following: 1) if the <allow-imminent-peril-call> element of <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true"; and a) if the "entry-info" attribute of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element contains the identity of the MCVideo group targeted by the calling MCVideo user; or b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup"; then the participating MCVideo function shall consider the MCVideo imminent peril group call request to be an authorised request for an MCVideo emergency group call; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 183 In all other cases, the participating MCVideo function shall consider the request to originate an MCVideo imminent peril group call to be an unauthorised request to originate an MCVideo imminent peril call." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.6] "This clause is referenced from other procedures. This clause describes the procedures for inviting an MCVideo user to an MCVideo session associated with an MCVideo emergency group call or MCVideo imminent peril group call. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.2.4.1.1. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the address of the terminating participating MCVideo function associated with the MCVideo ID of the targeted MCVideo user; 3) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element populated as follows: a) the <mcvideo-request-uri> element set to the value of the MCVideo ID of the targeted MCVideo user; b) the <mcvideo-calling-user-id> element set to the value of the MCVideo ID of the calling MCVideo user; and c) the <mcvideo-calling-group-id> element set to the value of the MCVideo group ID of the emergency group call. 4) shall include in the P-Asserted-Identity header field the public service identity of the controlling MCVideo function; 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and 6) if the in-progress emergency group state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.18; b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; c) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.12.1, shall populate the application/vnd.3gpp.mcvideo- info+xml MIME body and the application/vnd.3gpp.mcvideo-location-info+xml MIME body as specified in clause 6.3.3.1.11. Otherwise, shall set the <alert-ind> element to a value of "false" in the application/vnd.3gpp.mcvideo-info+xml MIME body; and d) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; NOTE: If the imminent peril state of the group is true at this point, the controlling function will set it to false as part of the calling procedure. 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.18; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 184 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains an <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.5.1] "When receiving a "SIP INVITE request for terminating participating MCVideo function" that requires automatic commencement mode: 1) if: a) the invited MCVideo client has one or more pre-established sessions without an associated MCVideo session; b) the media-level sections for the offered MCVideo video media stream are the same as the media-level sections for MCVideo video media stream in an existing pre-established session; and c) the media-level section of the offered media-transmission control entity is the same as the media-level section for media-transmission control entity in an existing pre-established session; then the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.5.3; or 2) otherwise the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.5.2." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.6.1] "When receiving a "SIP INVITE request for terminating participating MCVideo function" that requires manual commencement mode: 1) if: a) the invited MCVideo client has one or more pre-established sessions without an associated MCVideo session; b) the media-level sections for the offered MCVideo video media stream are the same as the media-level section for MCVideo video media stream in the existing pre-established session; and c) the media-level section of the offered media-transmission control entity is the same as the media-level section for media-transmission control entity in the existing pre-established session; then the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.6.3; or 2) otherwise the participating MCVideo function shall perform the actions specified in clause 6.3.2.2.6.2." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.8.1] "Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function: 1) shall interact with the media plane as specified in clause 6.4 in 3GPP TS 24.581 [5] for releasing media plane resource associated with the SIP session with the controlling MCVideo function; 2) shall generate a SIP BYE request according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 185 3) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP BYE request to the P- Asserted-Identity header field of the outgoing SIP BYE request; 4) if the received SIP BYE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body into the outgoing SIP BYE request; and 5) shall send the SIP BYE request to the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response to the SIP BYE request the participating MCVideo function: 1) shall send a SIP 200 (OK) response to the SIP BYE request received from the controlling MCVideo function according to 3GPP TS 24.229 [11]; and 2) shall interact with the media plane as specified in 3GPP TS 24.581 [5] for releasing media plane resources associated with the SIP session with the MCVideo client." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.4.2] "This clause is referenced from other procedures. When sending SIP 200 (OK) responses, the participating MCVideo function shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [11] and: 1) shall include the option tag "timer" in a Require header field; 2) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [23], "UAS Behavior". If no "refresher" parameter was included in the SIP INVITE request, the "refresher" parameter in the Session-Expires header field shall be set to "uas"; 3) shall include the following in the Contact header field: a) the g.3gpp.mcvideo media feature tag; b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; and c) an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP INVITE request from the controlling MCVideo function; 4) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [32]; and 5) if the incoming SIP response contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body to the outgoing SIP 200 (OK) response." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.2.2.1] "The participating MCVideo function shall follow the procedures in clause 6.3.2.1.2.1." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.2.1] "When composing the SDP answer according to 3GPP TS 24.229 [11], the participating MCVideo function: 1) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCVideo function, for the accepted media stream in the received SDP offer, if required; and NOTE 1: Requirements can exist for the participating MCVideo function to be always included in the path of the offered media stream, for example: for the support of features such as MBMS, lawful interception and recording. Other examples can exist. 2) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCVideo function, for the accepted media-transmission control entity, if present in the received SDP offer. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 186 NOTE 2: If the participating MCVideo function and the controlling MCVideo function are in the same MCVideo server, and the participating MCVideo function does not have a dedicated IP address or a dedicated port number for media transmission control or media stream, the replacement of the IP address or the port number is omitted." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.1] "Once an on-demand MCVideo session is established or a pre-established session is in use when the participating MCVideo function receives transmission control messages from the transmission participant in the MCVideo client or from the transmission control server in the controlling MCVideo function, the behaviour of the participating MCVideo function is described in the following clauses." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 187 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 188 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 189 d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine;and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 190 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and 2. shall set the general state to 'G: pending Transmission Revoke'." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 191 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 192 NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 193 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.9.3 Test description | 5.1.1.9.3.1 Pre-test conditions System Simulator: - SS (MCVideo Server), providing the controlling MCVideo function. - SS-UE2 (MCVideo Client). IUT: - IUT (MCVideo Server), providing the terminating participating 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 some sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server and the HTTP Client. Preamble: - The IUT (MCVideo Server) is connected to SS (MCVideo Server) and SS-UE2 (MCVideo Client). - The SS-UE2 (MCVideo client) is registered and authorized to use the MCVideo system. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 194 - The SS-UE2 (MCVideo client) is affiliated to the pre-arranged group and is authorized to initiate group calls. 5.1.1.9.3.2 Test procedure sequence Table 5.1.1.9.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 CT group/private call establishment, automatic commencement' as described in Annex A, Table A.4.3.3.3-1 to establish an imminent peril pre-arranged group call with automatic commencement mode and notify a media transmission from SS-UE1 (MCVideo Client)? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Notification - Idle' as described in Annex A, Table A.4.3.8.3-1 to notify the end of SS-UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E call release' as described in Annex A, Table A.4.3.5.3-1, to release the call? - - 3 P 5.1.1.9.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.1.1.9.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.1.1.9.3.2-1; Step 1, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-1, with conditions GROUP-CALL and IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.9.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.9.3.2-1; Step 2, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-2, with conditions GROUP-CALL and IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.9.3.3-3: SIP 200 (OK) from SS-UE2 (MCVideo Client) (Step 1, Table 5.1.1.9.3.2-1; Step 6, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-7, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.9.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.1.1.9.3.2-1; Step 7, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-8, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 195 Table 5.1.1.9.3.3-5: Transmission Idle (Step 2, Table 5.1.1.9.3.2-1; Steps 13 and 14, Annex A, Table A.4.3.8.3-1) Derivation Path: Annex A, Table A.4.3.8.4-6, with condition IMMPERIL-CALL. Table 5.1.1.9.3.3-6: Media Transmission Notification (Step 1, Table 5.1.1.9.3.2-1; Steps 10a1 and 10a2, Annex A, Table 4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-11, with condition IMMPERIL-CALL. 5.1.1.10 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Imminent Peril Group Call / Originating Participating server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.10.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to SS (MCVideo Server) } ensure that { when { the SS-UE1 (MCVideo Client) initiates an imminent peril pre-arranged group call with implicit transmission control } then { IUT (MCVideo Server) accepts the call from initiator and establishes the call with the SS (MCVideo Server) providing the controlling function and forwards the transmission granted received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established an imminent peril pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) forwards the transmission end request to SS (MCVideo Server) and forwards the transmission end response to SS-UE1 (MCVideo Client) and forwards the transmission idle received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established an imminent peril pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control } then { IUT (MCVideo Server) forwards the transmission request to SS (MCVideo Server) and forwards the transmission granted received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (4) with { IUT (MCVideo Server) having established an imminent peril pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) ends the pre-arranged group call } then { IUT (MCVideo Server) sends a SIP BYE message to SS (MCVideo Server) providing the controlling function and responds by sending a SIP 200 (OK) message to SS-UE1 (MCVideo Client) } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.10.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 9.2.1.3.1.1, 9.2.1.3.3, 6.2.8.1.1, 6.3.1.1, 6.3.2.1.3, 6.3.2.1.1.1 and 6.3.2.1.6.1, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.1.1] "In the procedures in this clause: 1) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 196 2) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 3) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "prearranged", the participating MCVideo function: 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The participating MCVideo function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [15]. Otherwise, continue with the rest of the steps; NOTE 1: if the SIP INVITE request contains an emergency indication or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCVideo function can according to local policy choose to accept the request. 2) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and shall authorise the calling user; NOTE 2: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. 3) if through local policy in the participating MCVideo function, the user identified by the MCVideo ID is not authorised to initiate prearranged group calls, shall reject the "SIP INVITE request for originating participating MCVideo function" with a SIP 403 (Forbidden) response to the SIP INVITE request, with warning text set to "109 user not authorised to make prearranged group calls" in a Warning header field as specified in clause 4.4; 4) shall validate the media parameters and if the MCVideo codecs are not offered in the SIP INVITE request shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; 5) shall check if the number of maximum simultaneous MCVideo group calls supported for the MCVideo user as specified in the <MaxSimultaneousCallsN6> element of the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) has been exceeded. If exceeded, the participating MCVideo function shall respond with a SIP 486 (Busy Here) response with the warning text set to "103 maximum simultaneous MCVideo group calls reached" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps; NOTE 3: If the SIP INVITE request contains an emergency indication or an imminent peril indication, the participating MCVideo function can by means beyond the scope of this specification choose to allow for an exception to the limit for the maximum simultaneous MCVideo sessions supported for the MCVideo user. Alternatively, a lower priority session of the MCVideo user could be terminated to allow for the new session. 6) if the user identified by the MCVideo ID is not affiliated to the group identified in the "SIP INVITE request for originating participating MCVideo function" as determined by clause 8.2.2.2.11 and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, shall perform the actions specified in clause 8.2.2.2.12 for implicit affiliation; 7) if the actions for implicit affiliation specified in step 6) above were performed but not successful in affiliating the MCVideo user due to the MCVideo user already having N2 simultaneous affiliations, shall reject the "SIP INVITE request for originating participating MCVideo function" with a SIP 486 (Busy Here) response with the warning text set to "102 too many simultaneous affiliations" in a Warning header field as specified in clause 4.4. and skip the rest of the steps. NOTE 4: N2 is the total number of MCVideo groups that an MCVideo user can be affiliated to simultaneously as specified in 3GPP TS 23.281 [26]. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 197 NOTE 5: if the SIP INVITE request contains an emergency indication set to a value of "true" or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCVideo function can according to local policy choose to allow an exception to the N2 limit. Alternatively, a lower priority affiliation of the MCVideo user could be cancelled to allow for the new affiliation. 8) shall determine the public service identity of the controlling MCVideo function associated with the group identity in the SIP INVITE request; NOTE 6: The public service identity can identify the controlling MCVideo function in the primary MCVideo system or a partner MCVideo system. NOTE 7: How the participating MCVideo server discovers the public service identity of the controlling MCVideo function associated with the group identity is out of scope of the current release. 9) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3; 10) shall set the Request-URI to the public service identity of the controlling MCVideo function associated with the group identity which was present in the incoming SIP INVITE request; 11) shall not copy the following header fields from the incoming SIP INVITE request to the outgoing SIP INVITE request, if they were present in the incoming SIP INVITE request: a) Answer-Mode header field as specified in IETF RFC 5373 [27]; and b) Priv-Answer-Mode header field as specified in IETF RFC 5373 [27]; 12) shall set the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; 14) if the received SIP INVITE request contains an application/vnd.3gpp.location-info+xml MIME body and if not already copied, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body received in the SIP INVITE request into an application/vnd.3gpp.location-info+xml MIME body included in the outgoing SIP request; 15) if a Resource-Priority header field was included in the received SIP INVITE request, shall include a Resource- Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCVideo client; and NOTE 8: The participating MCVideo function will leave verification of the Resource-Priority header field to the controlling MCVideo function. 16) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. Upon receipt of a SIP 302 (Moved Temporarily) response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.2.1.10; 2) shall include an SDP offer based upon the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; and 3) shall forward the SIP INVITE request according to 3GPP TS 24.229 [11]. Upon receipt of a SIP 2xx response in response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) if the received SIP 2xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC-GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 2) shall generate a SIP 200 (OK) response as in clause 6.3.2.1.5.2; 3) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 198 4) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 5) shall include the public service identity received in the P-Asserted-Identity header field of the incoming SIP 200 (OK) response into the P-Asserted-Identity header field of the outgoing SIP 200 (OK) response; 6) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 7) if the procedures of clause 8.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 8.2.2.2.13; 8) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 9) shall interact with Media Plane as specified in 3GPP TS 24.581 [5]; and 10) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [23]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request in step 14) the participating MCVideo function: 1) shall generate a SIP response according to 3GPP TS 24.229 [11]; 2) shall include Warning header field(s) that were received in the incoming SIP response; 3) shall forward the SIP response to the MCVideo client according to 3GPP TS 24.229 [11]; and 4) if the implicit affiliation procedures of clause 8.2.2.2.12 were invoked in this procedure, shall perform the procedures of clause 8.2.2.2.14;" [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.3] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.1.6." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.2.8.1.1] "This clause is referenced from other procedures. When the MCVideo emergency state is set and this MCVideo user and MCVideo group are authorised to initiate MCVideo emergency group calls as determined by the procedures of clause 6.2.8.1.8, the MCVideo client: 1) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the SIP INVITE request, an <emergency-ind> element set to "true" and if the MCVideo emergency group call state is set to "MVEGC 1: emergency-gc-capable", shall set the MCVideo emergency group call state to "MVEGC 2: emergency-call- requested"; 2) if the MCVideo user has also requested an MCVideo emergency alert to be sent and this is an authorised request for MCVideo emergency alert as determined by the procedures of clause 6.2.8.1.6, and the MCVideo emergency alert state is set to "MVEA 1: no-alert", shall: a) set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to "true" and set the MCVideo emergency alert state to "MVEA 2: emergency-alert-confirm-pending"; and b) perform the procedures specified in clause 6.2.9.1 for the MCVideo emergency alert trigger; 3) if the MCVideo user has not requested an MCVideo emergency alert to be sent and the MCVideo emergency alert state is set to "MVEA 1: no-alert", shall set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to "false"; and 4) if the MCVideo client emergency group state of the group is set to a value other than "MVEG 2: in-progress" set the MCVideo client emergency group state of the MCVideo group to "MVEG 3: confirm-pending". NOTE 1: This is the case of an MCVideo user already being in the MCVideo emergency state it initiated previously while originating an MCVideo emergency group call or MCVideo emergency alert. All group calls the MCVideo user originates while in MCVideo emergency state will be MCVideo emergency group calls. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 199 When the MCVideo emergency state is clear and the MCVideo emergency group call state is set to "MVEGC 1: emergency-gc-capable" and the MCVideo user is authorised to initiate an MCVideo emergency group call on the targetted MCVideo group as determined by the procedures of clause 6.2.8.1.8, the MCVideo client shall set the MCVideo emergency state and perform the following actions: 1) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the SIP INVITE request an <emergency-ind> element set to "true" and set the MCVideo emergency group call state to "MVEGC 2: emergency-call-requested" state; 2) if the MCVideo user has also requested an MCVideo emergency alert to be sent and this is an authorised request for MCVideo emergency alert as determined by the procedures of clause 6.2.8.1.6, shall: a) include in the application/vnd.3gpp.mcvideo-info+xml MIME body the <alert-ind> element set to "true" and set the MCVideo emergency alert state to "MVEA 2: emergency-alert-confirm-pending"; and b) perform the procedures specified in clause 6.2.9.1 for the MCVideo emergency alert trigger; 3) if the MCVideo user has not requested an MCVideo emergency alert to be sent, shall set the <alert-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to "false"; and 4) if the MCVideo client emergency group state of the group is set to a value other than "MVEG 2: in-progress" shall set the MCVideo client emergency group state of the MCVideo group to "MVEG 3: confirm-pending". NOTE 2: This is the case of an initial MCVideo emergency group call and optionally an MCVideo emergency alert being sent. As the MCVideo emergency state is not sent, there is no MCVideo emergency alert outstanding. NOTE 3: An MCVideo group call originated by an affiliated member of an MCVideo group which is in an in- progress emergency state (as tracked on the MCVideo client by the MCVideo client emergency group state) but is not in an MCVideo emergency state of their own will also be an MCVideo emergency group call. The <emergency-ind> and <alert-ind> elements of the application/vnd.3gpp.mcvideo-info+xml MIME body do not need to be included in this case and hence no action needs to be taken in this clause." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.1.1] "The MCVideo server needs to distinguish between the following initial SIP INVITE requests for originations and terminations: - SIP INVITE requests routed to the participating MCVideo function as a result of processing initial filter criteria at the S-CSCF in accordance with the origination procedures as specified in 3GPP TS 24.229 [11] and the Request-URI is set to a public service identity of the participating MCVideo function that does not identify the pre-established session set-up. Such requests are known as "SIP INVITE request for originating participating MCVideo function" in the procedures in the present document; - SIP INVITE requests routed to the participating MCVideo function as a result of processing initial filter criteria at the S-CSCF in accordance with the termination procedures as specified in 3GPP TS 24.229 [11] and the Request-URI contains a PSI of the terminating participating MCVideo function. Such requests are known as "SIP INVITE request for terminating participating MCVideo function" in the procedures in the present document; - SIP INVITE requests routed to the controlling MCVideo function as a result of PSI routing on the originating side in accordance with the originating procedures as specified in 3GPP TS 24.229 [11], or as a result of direct PSI routing, in accordance with the termination procedures as specified in 3GPP TS 24.229 [11], the Request-URI is set to a public service identity for MCVideo private call and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [16]. Such requests are known as "SIP INVITE request for controlling MCVideo function of a private call" in the procedures in the present document; - SIP INVITE requests routed to the controlling MCVideo function as a result of PSI routing on the originating side in accordance with the originating procedures as specified in 3GPP TS 24.229 [11], or as a result of direct PSI routing, in accordance with the termination procedures as specified in 3GPP TS 24.229 [11], the Request-URI is set to a public service identity serving an MCVideo group and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [16]. Such requests are known as "SIP INVITE request for controlling MCVideo function of an MCVideo group" in the procedures in the present document; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 200 - SIP INVITE requests routed to the controlling MCVideo function as a result of PSI routing on the originating side in accordance with the originating procedures as specified in 3GPP TS 24.229 [11], or as a result of direct PSI routing, in accordance with the termination procedures as specified in 3GPP TS 24.229 [11], the Request-URI is set to a public service identity for MCVideo ambient viewing call and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [22]. Such requests are known as "SIP INVITE request for controlling MCVideo function of an ambient viewing call" in the procedures in the present document." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.3] "This clause is referenced from other procedures. When generating an initial SIP INVITE request according to 3GPP TS 24.229 [11], on receipt of an incoming SIP INVITE request, the participating MCVideo function: 1) shall include in the SIP INVITE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [20] if included in the incoming SIP INVITE request; 2) should include the Session-Expires header field according to IETF RFC 4028 [23]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 3) shall include the option tag "timer" in the Supported header field; 4) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP INVITE request to the P- Asserted-Identity header field of the outgoing SIP INVITE request; 5) shall include the g.3gpp.mcvideo media feature tag into the Contact header field of the outgoing SIP INVITE request; 6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; 7) if the incoming SIP INVITE request contained a MIME resource-lists body with the MCVideo ID of the invited MCVideo user, shall copy the MIME resource-lists body, according to rules and procedures of IETF RFC 5366 [37]; 8) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the contents of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request to the outgoing SIP INVITE request; and 9) if the incoming SIP INVITE request contained an application/vnd.3gpp.location-info+xml MIME body, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body of the incoming SIP INVITE request to the outgoing SIP INVITE request." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.1.1] "This clause is referenced from other clauses. The SDP offer is generated based on the received SDP offer. The SDP offer generated by the participating MCVideo function: 1) shall contain two SDP media-level sections for MCVideo video media as contained in the received SDP offer; and 2) shall contain an SDP media-level section for one media-transmission control entity, if present in the received SDP offer. When composing the SDP offer according to 3GPP TS 24.229 [11], the participating MCVideo function: 1) shall replace the IP address and port number for the offered media stream in the received SDP offer with the IP address and port number of the participating MCVideo function, if required; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 201 NOTE 1: Requirements can exist for the participating MCVideo function to be always included in the path of the offered media stream, for example: for the support of features such as MBMS, lawful interception and recording. Other examples can exist. 2) shall replace the IP address and port number for the offered media transmission control entity, if any, in the received SDP offer with the IP address and port number of the participating MCVideo function; and NOTE 2: If the participating MCVideo function and the controlling MCVideo function are in the same MCVideo server, and the participating MCVideo function does not have a dedicated IP address or a dedicated port number for media transmission control or media stream, the replacement of the IP address or the port number is omitted. 3) shall contain an "a=key-mgmt" attribute field with a "mikey" attribute value, if present in the received SDP offer." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.2.1.6.1] "When the participating MCVideo function receives a request from the MCVideo client to originate an MCVideo emergency group call and needs to determine if the request is an authorised request for an MCVideo emergency call, the participating MCVideo function shall check the following: 1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true" and: a) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> element contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element contains the identity of the MCVideo group targeted by the calling MCVideo user; or b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element of the <EmergencyCall> contained within the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup"; then the participating MCVideo function shall consider the MCVideo emergency group call request to be an authorised request for an MCVideo emergency group call; In all other cases, the participating MCVideo function shall consider the request to originate an MCVideo emergency group call to be an unauthorised request to originate an MCVideo emergency group call. When the participating MCVideo function receives a request from the MCVideo client to originate an MCVideo imminent peril group call and needs to determine if the request is an authorised request for an MCVideo imminent peril group call the participating MCVideo function shall check the following: 1) if the <allow-imminent-peril-call> element of <ruleset> element of the MCVideo user profile document identified by the MCVideo ID of the calling user (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "true"; and a) if the "entry-info" attribute of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCVideoGroupInitiation> element contains the identity of the MCVideo group targeted by the calling MCVideo user; or b) if the "entry-info" attribute of the <entry> element of the <MCVideoGroupInitiation> element contained within the <ImminentPerilCall> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) is set to a value of "UseCurrentlySelectedGroup"; then the participating MCVideo function shall consider the MCVideo imminent peril group call request to be an authorised request for an MCVideo emergency group call; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 202 In all other cases, the participating MCVideo function shall consider the request to originate an MCVideo imminent peril group call to be an unauthorised request to originate an MCVideo imminent peril call." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.1] "Once an on-demand MCVideo session is established or a pre-established session is in use when the participating MCVideo function receives transmission control messages from the transmission participant in the MCVideo client or from the transmission control server in the controlling MCVideo function, the behaviour of the participating MCVideo function is described in the following clauses." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 203 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 204 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 205 d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine;and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 206 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and 2. shall set the general state to 'G: pending Transmission Revoke'." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 207 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 208 NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 209 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.10.3 Test description | 5.1.1.10.3.1 Pre-test conditions System Simulator: - SS (MCVideo Server), providing the controlling MCVideo function. - SS-UE1 (MCVideo Client). IUT: - IUT (MCVideo Server), providing the originating participating 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 some sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server and the HTTP Client. Preamble: - The IUT (MCVideo Server) is connected to SS (MCVideo Server) and SS-UE1 (MCVideo Client). - The SS-UE1 (MCVideo client) is registered and authorized to use the MCVideo system. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 210 - The SS-UE1 (MCVideo client) is affiliated to the pre-arranged group and is authorized to initiate group calls. 5.1.1.10.3.2 Test procedure sequence Table 5.1.1.10.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 CO session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.4.2.1.3-1 to establish an imminent peril pre-arranged group call with implicit transmission control request according to option b.ii of note in Annex A, Table A.4.2.1.3-1, initiated by SS-UE1 (MCVideo Client? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO Transmission End Request - Transmission End Response' as described in Annex A, Table A.4.2.5.3-1 to end SS-UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Transmission Granted' as described in Annex A, Table A.4.2.4.3-1, to request permission to transmit for SS-UE1 (MCVideo Client)? - - 3 P 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO call release' as described in Annex A, Table A.4.2.3.3-1, to release the call? - - 4 P 5.1.1.10.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.1.1.10.3.3-1: SIP INVITE from SS-UE1 (MCVideo Client) (Step 1, Table 5.1.1.10.3.2-1; Step 1, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-1, with conditions GROUP-CALL and IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.10.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.10.3.2-1; Step 2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-2, with conditions GROUP-CALL and IMMPERIL-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.10.3.3-3: SIP 200 (OK) from SS (MCVideo Server) (Step 1, Table 5.1.1.10.3.2-1; Step 5, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-3, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.10.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.1.1.10.3.2-1; Step 6, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-4, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 211 Table 5.1.1.10.3.3-5: Transmission Idle (Steps 2, Table 5.1.1.10.3.2-1; Steps 9 and 10, Annex A, Table A.4.2.5.3-1) Derivation Path: Annex A, Table A.4.2.5.4-3, with condition IMMPERIL-CALL. Table 5.1.1.10.3.3-6: Transmission Request (Step 3, Table 5.1.1.10.3.2-1; Steps 1 and 2, Annex A, Table A.4.2.4.3-1) Derivation Path: Annex A, Table A.4.2.4.4-1, with condition IMMPERIL-CALL. Table 5.1.1.10.3.3-7: Transmission Granted (Steps 1 and 3, Table 5.1.1.10.3.2-1; Steps 5 and 6, Annex A, Table A.4.2.4.3-1; Steps 9a1 and 9a2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.4.4-2, with condition IMMPERIL-CALL. 5.1.1.11 MCVideo Server - MCVideo Server / Broadcast Group Call / Controlling server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.11.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 broadcast group call with implicit transmission control } then { IUT (MCVideo Server) accepts the call from initiator and establishes the call with all affiliated users by sending call establishment requests to 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 broadcast group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) sends transmission control idle to SS-UE1 (MCVideo Client) and sends transmission control idle to SS-UE2 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established a broadcast group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control } then { IUT (MCVideo Server) sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } (4) with { IUT (MCVideo Server) having established a broadcast group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function ends the broadcast group 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 } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 212 |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.11.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 9.2.1.2.1.1, 6.2.8.2, 9.2.1.4.2, 9.2.1.4.3 and 9.2.1.4.4.2, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.3.1, 6.3.2.2, 9.2.1, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.2.1.1] "Upon receiving a request from an MCVideo user to establish an MCVideo prearranged group session the MCVideo client shall generate an initial SIP INVITE request by following the UE originating session procedures specified in 3GPP TS 24.229 [11], with the clarifications given below. The MCVideo client: 1) if the MCVideo user has requested the origination of an MCVideo emergency group call or is originating an MCVideo prearranged group call and the MCVideo emergency state is already set, the MCVideo client shall comply with the procedures in clause 6.2.8.1.1; 2) if the MCVideo user has requested the origination of an MCVideo imminent peril group call, the MCVideo client shall comply with the procedures in clause 6.2.8.1.9; 3) if the MCVideo user has requested the origination of a broadcast group call, the MCVideo client shall comply with the procedures in clause 6.2.8.2; 4) shall include the g.3gpp.mcvideo media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" in the Contact header field of the SIP INVITE request according to IETF RFC 3840 [22]; 5) shall include an Accept-Contact header field containing the g.3gpp.mcvideo media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; 6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Preferred-Service header field according to IETF RFC 6050 [14] in the SIP INVITE request; 7) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; 8) should include the "timer" option tag in the Supported header field; 9) should include the Session-Expires header field according to IETF RFC 4028 [23]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 10) shall set the Request-URI of the SIP INVITE request to the public service identity identifying the participating MCVideo function serving the MCVideo user; NOTE 1: The MCVideo client is configured with public service identity identifying the participating MCVideo function serving the MCVideo user. 11) may include a P-Preferred-Identity header field in the SIP INVITE request containing a public user identity as specified in 3GPP TS 24.229 [11]; 12) if the MCVideo emergency state is already set or the MCVideo client emergency group state for this group is set to "MVEG 2: in-progress", the MCVideo client shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2; 13) if the MCVideo client imminent peril group state for this group is set to "MVIG 2: in-progress" or "MVIG 4: confirm-pending" shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.12; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 213 14) shall contain in an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with: a) the <session-type> element set to a value of "prearranged"; b) the <mcvideo-request-uri> element set to the group identity; c) the <mcvideo-client-id> element set to the MCVideo client ID of the originating MCVideo client; and NOTE 2: The MCVideo client does not include the MCVideo ID of the originating MCVideo user in the body, as this will be inserted into the body of the SIP INVITE request that is sent from the originating participating MCVideo function. d) if the group identity can be determined to be a TGI and if the MCVideo client can associate the TGI with a MCVideo group ID, the <associated-group-id> element set to the MCVideo group ID; NOTE 3: The text "can associate the TGI with a MCVideo group ID" means that the MCVideo client is able to determine that there is a constituent group of the temporary group that it is a member of. NOTE 4: The MCVideo client is informed about temporary groups and regouping of MCVideo groups that the user is a member of as specified in 3GPP TS 24.481 [24]. NOTE 5: If the MCVideo user selected a TGI where there are several MCVideo groups where the MCVideo user is a member, the MCVideo client selects one of those MCVideo groups. 15) shall include an SDP offer according to 3GPP TS 24.229 [11] with the clarifications given in clause 6.2.1; 16) if an implicit transmission request is required, shall indicate this as specified in clause 6.4; and 17) shall send the SIP INVITE request towards the MCVideo server according to 3GPP TS 24.229 [11]. On receiving a SIP 2xx response to the SIP INVITE request, the MCVideo client: 1) shall interact with the user plane as specified in 3GPP TS 24.581 [5]; 2) if the MCVideo emergency group call state is set to "MVEGC 2: emergency-call-requested" or "MVEGC 3: emergency-call-granted" or the MCVideo imminent peril group call state is set to "MVIGC 2: imminent-peril- call-requested" or "MVIGC 3: imminent-peril-call-granted", the MCVideo client shall perform the actions specified in clause 6.2.8.1.4; and 3) may subscribe to the conference event package as specified in clause 9.1.3.1. On receiving a SIP 4xx response, a SIP 5xx response or a SIP 6xx response to the SIP INVITE request: 1) if the MCVideo emergency group call state is set to "MVEGC 2: emergency-call-requested" or "MVEGC 3: emergency-call-granted"; or 2) if the MCVideo imminent peril group call state is set to "MVIGC 2: imminent-peril-call-requested" or "MVIGC 3: imminent-peril-call-granted"; the MCVideo client shall perform the actions specified in clause 6.2.8.1.5. On receiving a SIP INFO request where the Request-URI contains an MCVideo session ID identifying an ongoing group session, the MCVideo client shall follow the actions specified in clause 6.2.8.1.13." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.2.8.2] "NOTE: This clause is referenced from other procedures. When the MCVideo user initiates a broadcast group call, the MCVideo client: 1) in the case of the prearranged group call is initiated on-demand, shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body the <broadcast-ind> element set to "true" as defined in clause F.1; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 214 2) in the case the prearranged group call is initiated using a pre-established session, shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the hname "body" parameter in the headers portion of the SIP URI in the Refer-To header field the <broadcast-ind> element set to "true" as defined in clause F.1." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.2] "In the procedures in this clause: 1) MCVideo ID in an incoming SIP INVITE request refers to the MCVideo ID of the originating user from the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 3) MCVideo ID in an outgoing SIP INVITE request refers to the MCVideo ID of the called user in the <mcvideo- request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) indication of required group members in a SIP 183 (Session Progress) response refers to the <required> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to "true" in a SIP 183 (Session Progress) sent by the non-controlling MCVideo function of an MCVideo group; 5) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 6) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for controlling MCVideo function of an MCVideo group", the controlling MCVideo function: … 2) shall determine if the media parameters are acceptable and the MCVideo codecs are offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps; 3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if: a) an Accept-Contact header field does not include the g.3gpp.mcvideo media feature tag; or b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; 4) if received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; 5) shall retrieve the necessary group document(s) from the group management server for the group identity contained in the SIP INVITE request and carry out initial processing as specified in clause 6.3.5.2; 6) if the result of the initial processing in clause 6.3.5.2 was: a) that authorization of the MCVideo ID is required at a non-controlling MCVideo function of an MCVideo group is required, perform the actions in clause 6.3.3.1.13.7 and do not continue with the rest of the steps in this clause; and b) that a SIP 3xx, 4xx, 5xx or 6xx response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group" has been sent, do not continue with the rest of the steps in this clause; 7) shall perform the actions as described in clause 6.3.3.2.2; 8) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 215 9) shall determine if an MCVideo group call for the group identity is already ongoing by determining if an MCVideo session identity has already been allocated for the group call and the MCVideo session is active; … 12) if a Resource-Priority header field is included in the SIP INVITE request: a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; or b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; 13) if the MCVideo group call is not ongoing then: … c) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined as determined in step 13) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; d) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; e) shall create a prearranged group session and allocate an MCVideo session identity for the prearranged group call, and shall handle timer TNG3 (group call timer) as specified in clause 6.3.3.5; f) if the group identity in the "SIP INVITE request for controlling MCVideo function of an MCVideo group" is a TGI: i) shall for each of the constituent MCVideo groups homed on the primary MCVideo system: …; B) if the controlling MCVideo function owns the MCVideo group identified by the MCVideo group ID then: I) determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; II) invite each group member determined in step A) above, to the group session, as specified in clause 9.2.1.4.1.1; and III) interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and ii) shall for each of the constituent MCVideo groups homed on the partner MCVideo system generate a SIP INVITE request for the MCVideo group identity homed on the partner MCVideo system as specified in clause 9.2.1.4.1.2; and g) if the group identity in the SIP INVITE request for controlling MCVideo function of an MCVideo group is an MCVideo group ID: i) shall determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; ii) if necessary, shall start timer TNG1 (acknowledged call setup timer) according to the conditions stated in clause 6.3.3.3; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 216 iii) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": A) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; and C) if the in-progress emergency state of the group is set to a value of "false": I) shall set the value of the in-progress emergency state of the group to "true"; and II) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; iv) if the in-progress emergency state of the group is set to a value of "false" and if the received SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function shall: A) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and B) if the in-progress imminent peril state of the group is set to a value of "false", shall set the in- progress imminent peril state of the group to a value of "true"; v) shall invite each group member determined in step 13)g)i) above, to the group session, as specified in clause 9.2.1.4.1.1; and vi) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and 14) if the MCVideo group call is ongoing then: … c) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; … e) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined in step 14) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; f) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": i) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; iii) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 217 C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.6; iv) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and v) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; g) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function: i) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and ii) if the in-progress imminent peril state of the group is set to a value of "false": A) shall set the in-progress imminent peril state of the group to a value of "true"; B) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.15; and C) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and iii) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; h) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.4.2; i) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; j) shall include in the SIP 200 (OK) response with the warning text set to "123 MCVideo session already exists" as specified in clause 4.4; k) if the received SIP re-INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; l) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 4: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. m) shall interact with media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 5: Resulting media plane processing is completed before the next step is performed. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 218 n) shall send the SIP 200 (OK) response towards the inviting MCVideo client or inviting non-controlling MCVideo function according to 3GPP TS 24.229 [11]; o) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; NOTE 6: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. p) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]; q) Upon receiving a SIP ACK to the above SIP 200 (OK) response and the SIP 200 (OK) response contained a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall follow the procedures in clause 6.3.3.1.18; and r) shall not continue with the rest of the clause. Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 9.2.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [30], the timer TNG1 (acknowledged call setup timer) is not running, the controlling MCVideo function supports media buffering and the SIP final response is not yet sent to the inviting MCVideo client: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) shall include a P-Answer-State header field with the value "Unconfirmed"; 5) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 7: Resulting user plane processing is completed before the next step is performed. 8) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; 9) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 8: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 10) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response for a SIP INVITE request as specified in clause 9.2.1.4.1.2 containing an indication of required group members, the timer TNG1 (acknowledged call setup timer) is running and all SIP 200 (OK) responses have been received to all SIP INVITE requests sent to MCVideo clients specified in clause 9.2.1.4.1.1, then the controlling MCVideo function shall wait until the SIP 200 (OK) response has been received to the SIP INVITE request specified in clause 9.2.1.4.1.2 before generating a SIP 200 (OK) response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group". ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 219 Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1 that was sent to an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24]; and 1) if the MCVideo ID in the SIP 200 (OK) response matches to the MCVideo ID in the corresponding SIP INVITE request; 2) there are no outstanding SIP 200 (OK) responses to SIP INVITE requests which were sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24]; and 3) there is no outstanding SIP 200 (OK) response to a SIP INVITE request sent in clause 9.2.1.4.1.2 where the SIP 183 (Session Progress) response contained an indication of required group members; the controlling MCVideo function: 1) shall stop timer TNG1 (acknowledged call setup timer) as described in clause 6.3.3.3; 2) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 3) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has been exceeded the <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 4) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 5) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 9: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 7) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 10: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 8) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon: 1) receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1; 2) the timer TNG1 (acknowledged call setup timer) is not running; 3) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; 4) the controlling MCVideo function supports media buffering; and 5) the SIP final response has not yet been sent to the inviting MCVideo client; the controlling MCVideo function according to local policy: 1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has exceeded the <max- participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 220 4) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 5) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 11: Resulting media plane processing is completed before the next step is performed. 7) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 8) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 12: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 9) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon expiry of timer TNG1 (acknowledged call setup timer), if there are outstanding SIP 200 (OK) responses to SIP INVITE requests sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the procedures specified in clause 6.3.3.3. If timer TNG1 (acknowledged call setup timer) is running and a final SIP 4xx, 5xx or 6xx response is received from an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the relevant procedures specified in clause 6.3.3.3. If: 1) timer TNG1 (acknowledged call setup timer) is not running; 2) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; and 3) a final SIP 4xx, 5xx or 6xx response is received from an invited MCVideo client; then the controlling MCVideo function shall perform one of the following based on policy: 1) send the SIP final response towards the inviting MCVideo client, according to 3GPP TS 24.229 [11], if a SIP final response was received from all the other invited MCVideo clients and the SIP 200 (OK) response is not yet sent; or 2) remove the invited MCVideo client from the MCVideo Session as specified in clause 6.3.3.1.5, if a SIP final response other than 2xx or 3xx was received from all the invited MCVideo clients and the SIP 200 (OK) response is already sent. The controlling MCVideo function may invite an additional member of the prearranged MCVideo group as specified in clause 9.2.1.4.1 that has not already been invited, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24], and all members have not yet been invited. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.3] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 221 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.4.2] "When the MCVideo session for group call needs to be released as specified in clause 6.3.8.1, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.5." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.1] "The transmission control server arbitration logic in the transmission control server shall support the procedures in clauses 6.3.2 and 6.3.3 and shall behave according to the transmission control server state transition diagram for 'general transmission control operation' in clause 6.3.4. The transmission control interface towards the MCVideo client in the transmission control server shall behave according to the transmission control server state transition diagram for 'basic transmission control operation towards the transmission participant' as specified in clause 6.3.5. The reception control arbitration logic in the transmission control server shall support the procedures in clauses 6.3.2 and 6.3.3 and shall behave according to the reception control server state transition diagram for 'general reception control operation' in clause 6.3.6. The transmission control interface towards the MCVideo client in the transmission control server shall behave according to the transmission control server state transition diagram for 'basic reception control operation towards the transmission participant' as specified in clause 6.3.7." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.2.2] "When an MCVideo call is established a new instance of the transmission control server state machine for 'general transmission control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' is added. When an MCVideo call is established a new instance of the transmission control server state machine for 'general reception control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic reception control operation towards the transmission participant' is added. If the optional "mc_queueing" feature is supported and has been negotiated as specified in clause 14, the transmission control server could queue the implicit transmission control request for the media-transmission control entity. The original initial SIP INVITE request or SIP REFER request to establish an MCVideo chat group call or to rejoin an ongoing MCVideo call is not handled as an implicit transmission control request message by the transmission control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request. The permission to send media to the inviting MCVideo client due to implicit transmission control request is applicable to both confirmed indication and unconfirmed indication. When the first unconfirmed indication is received from the invited participating MCVideo function (see 3GPP TS 24.281 [2]) the transmission control server optionally can give an early indication to send RTP media packets, to the inviting MCVideo client. If an early indication to send RTP media packets is given to the inviting MCVideo client, the transmission participant is granted the permission to send media and the MCVideo server buffers RTP media packets received from the MCVideo client at least until the first invited MCVideo client accepts the invitation or until the RTP media packet buffer exceeds it maximum limit to store RTP media packets. If the MCVideo server does not support or does not allow media buffering then when an early indication to send RTP media packets is not given to the inviting MCVideo client, the transmission participant is granted the permission to send media when the first invited MCVideo client accepts the media. Before the transmission control server sends the first transmission control message in the MCVideo call, the transmission control server has to assign itself a SSRC identifier to be included in media transmission control messages and quality feedback messages if the MCVideo server is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3]. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 222 The transmission participant and the transmission control server can negotiate the maximum priority level that the transmission participant is permitted to request. The transmission control server can pre-empt the current sender based on the negotiated maximum priority level that the transmission participant is permitted to request and the priority level included in the Transmission Media Request message. NOTE: The maximum priority level that a transmission participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the controlling MCVideo function from the group management server as described in 3GPP TS 24.481 [12] and service configuration data retrieved by the controlling MCVideo function from the configuration management server as described in 3GPP TS 24.484 [13]. The transmission participant and the transmission control server can negotiate queueing of Transmission requests using the "mc_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the transmission control server queues the transmission control request if a Transmission Media Request message is received when another transmission participant has the transmission and the priority of the current speaker is the same or higher." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.1] "The transmission control messages are coded as described in clause 9.1.2 where the transmission control message is part of the application-dependent data. For the transmission control protocol the ASCII name string is: MCVx (Mission Critical Video x) with x=0, 1 or 2 as specified in clause 9.1.2. A list of transmission control messages can be found in clause 9.2.2.1. The transmission control specific fields are specified in clause 9.2.3." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 223 Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 224 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine;and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 225 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and 2. shall set the general state to 'G: pending Transmission Revoke'." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 226 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 227 NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 228 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.11.3 Test description | 5.1.1.11.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). 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) 229 - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are registered and authorized to use the MCVideo system. - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are affiliated to the pre-arranged group and are authorized to initiate broadcast group calls. - The IUT (MCVideo Server) is the controlling server of the pre-arranged group. 5.1.1.11.3.2 Test procedure sequence Table 5.1.1.11.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E group call establishment' as described in Annex A, Table A.4.1.4.3-1 to establish a broadcast group call with implicit transmission control request according to option b.ii of note in Annex A, Table A.4.1.4.3-1, initiated by SS-UE1 (MCVideo Client)? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure ' MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1, to end SS-UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1, to request permission to transmit for 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 5.1.1.11.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.1.1.11.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.1.1.11.3.2-1; Step 1, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-1, with condition BROADCAST-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.11.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.11.3.2-1; Step 2, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-2, with condition BROADCAST-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.11.3.3-3: SIP 200 (OK) from SS (MCVideo Server) (Step 1, Table 5.1.1.11.3.2-1; Step 8, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-6 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 230 Table 5.1.1.11.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.1.1.11.3.2-1; Step 9, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-7 Table 5.1.1.11.3.3-5: Transmission Idle from IUT (MCVideo Server) (Step 2, Table 5.1.1.11.3.2-1; Steps 4 and 5, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-6, with condition BROADCAST-CALL. Table 5.1.1.11.3.3-6: Transmission Request from SS (MCVideo Server) (Step 3, Table 5.1.1.11.3.2-1; Step 1, Annex A, Table A.3.7.3-1) Derivation Path: Annex A, Table A.3.7.4-1, with condition BROADCAST-CALL. Table 5.1.1.11.3.3-7: Transmission Granted from IUT (MCVideo Server) (Steps 1 and 3, Table 5.1.1.11.3.2-1; Step 3a1 or 3b1, Annex A, Table A.3.7.3-1; Step 9a1, Annex A, Table A.4.1.1.3-1) Derivation Path: Annex A, Table A.3.7.4-2 or A.3.7.4-3 (note), with condition BROADCAST-CALL. NOTE: Depends on server implementation. Table 5.1.1.11.3.3-8: Media Transmission Notification from IUT (MCVideo Server) (Steps 1 and 3, Table 5.1.1.11.3.2-1; Step 3a3 or 3b2, Annex A, Table A.3.7.3-1; Step 10a1, Annex A, Table 4.1.1.3-1) Derivation Path: Annex A, Table A.3.7.4-4 or A.3.7.4-5 (note), with condition BROADCAST-CALL. NOTE: Depends on server implementation. 5.1.1.12 MCVideo Server - MCVideo Server / Broadcast Group Call / Terminating Participating server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.12.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to SS (MCVideo Server) } ensure that { when { the SS (MCVideo Server) providing the controlling function initiates a broadcast group call with automatic commencement } then { IUT (MCVideo Server) accepts the call and establishes the call with SS-UE2 (MCVideo Client) and forwards the media transmission notification received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established a broadcast group call } ensure that { when { the SS (MCVideo Server) ends the media transmission } then { IUT (MCVideo Server) forwards the transmission end notify received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) and forwards the transmission idle received from SS (MCVideo Server) to SS-UE2 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 231 (3) with { IUT (MCVideo Server) having established a broadcast group call } ensure that { when { the SS (MCVideo Server) providing the controlling function ends the broadcast group call } then { IUT (MCVideo Server) sends a SIP BYE message to SS-UE2 (MCVideo Client) and responds by sending a SIP 200 (OK) message to SS (MCVideo Server) } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.12.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 9.2.1.2.1.1, 6.2.8.2, 9.2.1.3.2 and 9.2.1.3.4.1, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.2.1.1] "Upon receiving a request from an MCVideo user to establish an MCVideo prearranged group session the MCVideo client shall generate an initial SIP INVITE request by following the UE originating session procedures specified in 3GPP TS 24.229 [11], with the clarifications given below. The MCVideo client: 1) if the MCVideo user has requested the origination of an MCVideo emergency group call or is originating an MCVideo prearranged group call and the MCVideo emergency state is already set, the MCVideo client shall comply with the procedures in clause 6.2.8.1.1; 2) if the MCVideo user has requested the origination of an MCVideo imminent peril group call, the MCVideo client shall comply with the procedures in clause 6.2.8.1.9; 3) if the MCVideo user has requested the origination of a broadcast group call, the MCVideo client shall comply with the procedures in clause 6.2.8.2; 4) shall include the g.3gpp.mcvideo media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" in the Contact header field of the SIP INVITE request according to IETF RFC 3840 [22]; 5) shall include an Accept-Contact header field containing the g.3gpp.mcvideo media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; 6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Preferred-Service header field according to IETF RFC 6050 [14] in the SIP INVITE request; 7) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; 8) should include the "timer" option tag in the Supported header field; 9) should include the Session-Expires header field according to IETF RFC 4028 [23]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 10) shall set the Request-URI of the SIP INVITE request to the public service identity identifying the participating MCVideo function serving the MCVideo user; NOTE 1: The MCVideo client is configured with public service identity identifying the participating MCVideo function serving the MCVideo user. 11) may include a P-Preferred-Identity header field in the SIP INVITE request containing a public user identity as specified in 3GPP TS 24.229 [11]; 12) if the MCVideo emergency state is already set or the MCVideo client emergency group state for this group is set to "MVEG 2: in-progress", the MCVideo client shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 232 13) if the MCVideo client imminent peril group state for this group is set to "MVIG 2: in-progress" or "MVIG 4: confirm-pending" shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.12; 14) shall contain in an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with: a) the <session-type> element set to a value of "prearranged"; b) the <mcvideo-request-uri> element set to the group identity; c) the <mcvideo-client-id> element set to the MCVideo client ID of the originating MCVideo client; and NOTE 2: The MCVideo client does not include the MCVideo ID of the originating MCVideo user in the body, as this will be inserted into the body of the SIP INVITE request that is sent from the originating participating MCVideo function. d) if the group identity can be determined to be a TGI and if the MCVideo client can associate the TGI with a MCVideo group ID, the <associated-group-id> element set to the MCVideo group ID; NOTE 3: The text "can associate the TGI with a MCVideo group ID" means that the MCVideo client is able to determine that there is a constituent group of the temporary group that it is a member of. NOTE 4: The MCVideo client is informed about temporary groups and regouping of MCVideo groups that the user is a member of as specified in 3GPP TS 24.481 [24]. NOTE 5: If the MCVideo user selected a TGI where there are several MCVideo groups where the MCVideo user is a member, the MCVideo client selects one of those MCVideo groups. 15) shall include an SDP offer according to 3GPP TS 24.229 [11] with the clarifications given in clause 6.2.1; 16) if an implicit transmission request is required, shall indicate this as specified in clause 6.4; and 17) shall send the SIP INVITE request towards the MCVideo server according to 3GPP TS 24.229 [11]. On receiving a SIP 2xx response to the SIP INVITE request, the MCVideo client: 1) shall interact with the user plane as specified in 3GPP TS 24.581 [5] ; 2) if the MCVideo emergency group call state is set to "MVEGC 2: emergency-call-requested" or "MVEGC 3: emergency-call-granted" or the MCVideo imminent peril group call state is set to "MVIGC 2: imminent-peril- call-requested" or "MVIGC 3: imminent-peril-call-granted", the MCVideo client shall perform the actions specified in clause 6.2.8.1.4; and 3) may subscribe to the conference event package as specified in clause 9.1.3.1. On receiving a SIP 4xx response, a SIP 5xx response or a SIP 6xx response to the SIP INVITE request: 1) if the MCVideo emergency group call state is set to "MVEGC 2: emergency-call-requested" or "MVEGC 3: emergency-call-granted"; or 2) if the MCVideo imminent peril group call state is set to "MVIGC 2: imminent-peril-call-requested" or "MVIGC 3: imminent-peril-call-granted"; the MCVideo client shall perform the actions specified in clause 6.2.8.1.5. On receiving a SIP INFO request where the Request-URI contains an MCVideo session ID identifying an ongoing group session, the MCVideo client shall follow the actions specified in clause 6.2.8.1.13." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 233 [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.2.8.2] "NOTE: This clause is referenced from other procedures. When the MCVideo user initiates a broadcast group call, the MCVideo client: 1) in the case of the prearranged group call is initiated on-demand, shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body the <broadcast-ind> element set to "true" as defined in clause F.1; and 2) in the case the prearranged group call is initiated using a pre-established session, shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the hname "body" parameter in the headers portion of the SIP URI in the Refer-To header field the <broadcast-ind> element set to "true" as defined in clause F.1." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.2] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. NOTE 1: This clause covers on-demand session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The participating MCVideo function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [15], and shall not continue with the rest of the steps; NOTE 2: if the SIP INVITE request contains an emergency indication or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCVideo function can according to local policy choose to accept the request. 2) shall check the presence of the isfocus media feature tag in the URI of the Contact header field and if it is not present then the participating MCVideo function shall reject the request with a SIP 403 (Forbidden) response with the warning text set to "104 isfocus not assigned" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps; 3) if the Answer-Mode Indication in the application/poc-settings+xml MIME body has not yet been received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4, shall reject the request with a SIP 480 (Temporarily Unavailable) response with the warning text set to "146 T-PF unable to determine the service settings for the called user" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps; 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; 5) if the binding between the MCVideo ID and public user identity does not exist, then the participating MCVideo function shall reject the SIP INVITE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps; 6) if the SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC- GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 234 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.4.1] "In the procedures in this clause: 1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. NOTE 1: This clause covers on-demand session. Upon receipt of a "SIP INVITE request for terminating participating MCVideo function", the participating MCVideo function: 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The participating MCVideo function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [15], and shall not continue with the rest of the steps; NOTE 2: if the SIP INVITE request contains an emergency indication or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCVideo function can according to local policy choose to accept the request. 2) shall check the presence of the isfocus media feature tag in the URI of the Contact header field and if it is not present then the participating MCVideo function shall reject the request with a SIP 403 (Forbidden) response with the warning text set to "104 isfocus not assigned" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps; 3) if the Answer-Mode Indication in the application/poc-settings+xml MIME body has not yet been received from the invited MCVideo client as defined in clause 7.3.3 or clause 7.3.4, shall reject the request with a SIP 480 (Temporarily Unavailable) response with the warning text set to "146 T-PF unable to determine the service settings for the called user" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps; 4) shall use the MCVideo ID present in the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo- info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCVideo ID and public user identity; 5) if the binding between the MCVideo ID and public user identity does not exist, then the participating MCVideo function shall reject the SIP INVITE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps; 6) if the SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC- GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; and 8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [27] if the "SIP INVITE request for terminating participating MCVideo function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc- settings+xml MIME body received from the invited MCVideo client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer"." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 235 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.1] "Once an on-demand MCVideo session is established or a pre-established session is in use when the participating MCVideo function receives transmission control messages from the transmission participant in the MCVideo client or from the transmission control server in the controlling MCVideo function, the behaviour of the participating MCVideo function is described in the following clauses." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 236 ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 237 Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 238 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine; and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 239 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and 2. shall set the general state to 'G: pending Transmission Revoke'." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 240 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 241 NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 242 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.12.3 Test description | 5.1.1.12.3.1 Pre-test conditions System Simulator: - SS (MCVideo Server), providing the controlling MCVideo function. - SS-UE2 (MCVideo Client). IUT: - IUT (MCVideo Server), providing the terminating participating 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 some sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server and the HTTP Client. Preamble: - The IUT (MCVideo Server) is connected to SS (MCVideo Server) and SS-UE2 (MCVideo Client). - The SS-UE2 (MCVideo client) is registered and authorized to use the MCVideo system. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 243 - The SS-UE2 (MCVideo client) is affiliated to the pre-arranged group and is authorized to initiate broadcast group calls. 5.1.1.12.3.2 Test procedure sequence Table 5.1.1.12.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 CT group/private call establishment, automatic commencement' as described in Annex A, Table A.4.3.3.3-1 to establish a broadcast group call with automatic commencement mode and notify a media transmission from SS-UE1 (MCVideo Client)? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Notification - Idle' as described in Annex A, Table A.4.3.8.3-1 to notify the end of SS-UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E call release' as described in Annex A, Table A.4.3.5.3-1, to release the call? - - 3 P 5.1.1.12.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.1.1.12.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.1.1.12.3.2-1; Step 1, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-1, with conditions GROUP-CALL and BROADCAST-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.12.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.12.3.2-1; Step 2, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-2, with conditions GROUP-CALL and BROADCAST-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.12.3.3-3: SIP 200 (OK) from SS-UE2 (MCVideo Client) (Step 1, Table 5.1.1.12.3.2-1; Step 6, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-7, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.12.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.1.1.12.3.2-1; Step 7, Annex A, Table A.4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-8, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 244 Table 5.1.1.12.3.3-5: Transmission Idle (Step 2, Table 5.1.1.12.3.2-1; Steps 13 and 14, Annex A, Table A.4.3.8.3-1) Derivation Path: Annex A, Table A.4.3.8.4-6, with condition BROADCAST-CALL. Table 5.1.1.12.3.3-6: Media Transmission Notification (Step 1, Table 5.1.1.12.3.2-1; Steps 10a1 and 10a2, Annex A, Table 4.3.3.3-1) Derivation Path: Annex A, Table A.4.3.3.4-11, with condition BROADCAST-CALL. 5.1.1.13 MCVideo Server - MCVideo Server / Broadcast Group Call / Originating Participating server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.13.1 Test Purpose (TP) | (1) with { IUT (MCVideo Server) connected to SS (MCVideo Server) } ensure that { when { the SS-UE1 (MCVideo Client) initiates a broadcast group call with implicit transmission control } then { IUT (MCVideo Server) accepts the call from initiator and establishes the call with the SS (MCVideo Server) providing the controlling function and forwards the transmission granted received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established a broadcast group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) forwards the transmission end request to SS (MCVideo Server) and forwards the transmission end response to SS-UE1 (MCVideo Client) and forwards the transmission idle received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established a broadcast group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control } then { IUT (MCVideo Server) forwards the transmission request to SS (MCVideo Server) and forwards the transmission granted received from SS (MCVideo Server) to SS-UE1 (MCVideo Client) } } (4) with { IUT (MCVideo Server) having established a broadcast group call } ensure that { when { the SS-UE1 (MCVideo Client) ends the broadcast group call } then { IUT (MCVideo Server) sends a SIP BYE message to SS (MCVideo Server) providing the controlling function and responds by sending a SIP 200 (OK) message to SS-UE1 (MCVideo Client) } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.13.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 9.2.1.2.1.1, 6.2.8.2, 9.2.1.3.1.1 and 9.2.1.3.3.1, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.3.3, 9.2.3.11, 6.3.4.3.2, 6.3.4.4.2, 6.3.4.4.12, 6.3.4.5.2, 6.3.5.2.2 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.2.1.1] "Upon receiving a request from an MCVideo user to establish an MCVideo prearranged group session the MCVideo client shall generate an initial SIP INVITE request by following the UE originating session procedures specified in 3GPP TS 24.229 [11], with the clarifications given below. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 245 The MCVideo client: 1) if the MCVideo user has requested the origination of an MCVideo emergency group call or is originating an MCVideo prearranged group call and the MCVideo emergency state is already set, the MCVideo client shall comply with the procedures in clause 6.2.8.1.1; 2) if the MCVideo user has requested the origination of an MCVideo imminent peril group call, the MCVideo client shall comply with the procedures in clause 6.2.8.1.9; 3) if the MCVideo user has requested the origination of a broadcast group call, the MCVideo client shall comply with the procedures in clause 6.2.8.2; 4) shall include the g.3gpp.mcvideo media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" in the Contact header field of the SIP INVITE request according to IETF RFC 3840 [22]; 5) shall include an Accept-Contact header field containing the g.3gpp.mcvideo media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; 6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Preferred-Service header field according to IETF RFC 6050 [14] in the SIP INVITE request; 7) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; 8) should include the "timer" option tag in the Supported header field; 9) should include the Session-Expires header field according to IETF RFC 4028 [23]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac"; 10) shall set the Request-URI of the SIP INVITE request to the public service identity identifying the participating MCVideo function serving the MCVideo user; NOTE 1: The MCVideo client is configured with public service identity identifying the participating MCVideo function serving the MCVideo user. 11) may include a P-Preferred-Identity header field in the SIP INVITE request containing a public user identity as specified in 3GPP TS 24.229 [11]; 12) if the MCVideo emergency state is already set or the MCVideo client emergency group state for this group is set to "MVEG 2: in-progress", the MCVideo client shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2; 13) if the MCVideo client imminent peril group state for this group is set to "MVIG 2: in-progress" or "MVIG 4: confirm-pending" shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.12; 14) shall contain in an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with: a) the <session-type> element set to a value of "prearranged"; b) the <mcvideo-request-uri> element set to the group identity; c) the <mcvideo-client-id> element set to the MCVideo client ID of the originating MCVideo client; and NOTE 2: The MCVideo client does not include the MCVideo ID of the originating MCVideo user in the body, as this will be inserted into the body of the SIP INVITE request that is sent from the originating participating MCVideo function. d) if the group identity can be determined to be a TGI and if the MCVideo client can associate the TGI with a MCVideo group ID, the <associated-group-id> element set to the MCVideo group ID; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 246 NOTE 3: The text "can associate the TGI with a MCVideo group ID" means that the MCVideo client is able to determine that there is a constituent group of the temporary group that it is a member of. NOTE 4: The MCVideo client is informed about temporary groups and regouping of MCVideo groups that the user is a member of as specified in 3GPP TS 24.481 [24]. NOTE 5: If the MCVideo user selected a TGI where there are several MCVideo groups where the MCVideo user is a member, the MCVideo client selects one of those MCVideo groups. 15) shall include an SDP offer according to 3GPP TS 24.229 [11] with the clarifications given in clause 6.2.1; 16) if an implicit transmission request is required, shall indicate this as specified in clause 6.4; and 17) shall send the SIP INVITE request towards the MCVideo server according to 3GPP TS 24.229 [11]. On receiving a SIP 2xx response to the SIP INVITE request, the MCVideo client: 1) shall interact with the user plane as specified in 3GPP TS 24.581 [5] ; 2) if the MCVideo emergency group call state is set to "MVEGC 2: emergency-call-requested" or "MVEGC 3: emergency-call-granted" or the MCVideo imminent peril group call state is set to "MVIGC 2: imminent-peril- call-requested" or "MVIGC 3: imminent-peril-call-granted", the MCVideo client shall perform the actions specified in clause 6.2.8.1.4; and 3) may subscribe to the conference event package as specified in clause 9.1.3.1. On receiving a SIP 4xx response, a SIP 5xx response or a SIP 6xx response to the SIP INVITE request: 1) if the MCVideo emergency group call state is set to "MVEGC 2: emergency-call-requested" or "MVEGC 3: emergency-call-granted"; or 2) if the MCVideo imminent peril group call state is set to "MVIGC 2: imminent-peril-call-requested" or "MVIGC 3: imminent-peril-call-granted"; the MCVideo client shall perform the actions specified in clause 6.2.8.1.5. On receiving a SIP INFO request where the Request-URI contains an MCVideo session ID identifying an ongoing group session, the MCVideo client shall follow the actions specified in clause 6.2.8.1.13." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.2.8.2] "NOTE: This clause is referenced from other procedures. When the MCVideo user initiates a broadcast group call, the MCVideo client: 1) in the case of the prearranged group call is initiated on-demand, shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body the <broadcast-ind> element set to "true" as defined in clause F.1; and 2) in the case the prearranged group call is initiated using a pre-established session, shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the hname "body" parameter in the headers portion of the SIP URI in the Refer-To header field the <broadcast-ind> element set to "true" as defined in clause F.1." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.1.1] "In the procedures in this clause: 1) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 3) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 247 Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "prearranged", the participating MCVideo function: 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The participating MCVideo function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [15]. Otherwise, continue with the rest of the steps; NOTE 1: if the SIP INVITE request contains an emergency indication or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCVideo function can according to local policy choose to accept the request. 2) shall determine the MCVideo ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request, and shall authorise the calling user; NOTE 2: The MCVideo ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3. 3) if through local policy in the participating MCVideo function, the user identified by the MCVideo ID is not authorised to initiate prearranged group calls, shall reject the "SIP INVITE request for originating participating MCVideo function" with a SIP 403 (Forbidden) response to the SIP INVITE request, with warning text set to "109 user not authorised to make prearranged group calls" in a Warning header field as specified in clause 4.4; 4) shall validate the media parameters and if the MCVideo codecs are not offered in the SIP INVITE request shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; 5) shall check if the number of maximum simultaneous MCVideo group calls supported for the MCVideo user as specified in the <MaxSimultaneousCallsN6> element of the <MCVideo-group-call> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]) has been exceeded. If exceeded, the participating MCVideo function shall respond with a SIP 486 (Busy Here) response with the warning text set to "103 maximum simultaneous MCVideo group calls reached" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps; NOTE 3: If the SIP INVITE request contains an emergency indication or an imminent peril indication, the participating MCVideo function can by means beyond the scope of this specification choose to allow for an exception to the limit for the maximum simultaneous MCVideo sessions supported for the MCVideo user. Alternatively, a lower priority session of the MCVideo user could be terminated to allow for the new session. 6) if the user identified by the MCVideo ID is not affiliated to the group identified in the "SIP INVITE request for originating participating MCVideo function" as determined by clause 8.2.2.2.11 and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, shall perform the actions specified in clause 8.2.2.2.12 for implicit affiliation; 7) if the actions for implicit affiliation specified in step 6) above were performed but not successful in affiliating the MCVideo user due to the MCVideo user already having N2 simultaneous affiliations, shall reject the "SIP INVITE request for originating participating MCVideo function" with a SIP 486 (Busy Here) response with the warning text set to "102 too many simultaneous affiliations" in a Warning header field as specified in clause 4.4. and skip the rest of the steps. NOTE 4: N2 is the total number of MCVideo groups that an MCVideo user can be affiliated to simultaneously as specified in 3GPP TS 23.281 [26]. NOTE 5: if the SIP INVITE request contains an emergency indication set to a value of "true" or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCVideo function can according to local policy choose to allow an exception to the N2 limit. Alternatively, a lower priority affiliation of the MCVideo user could be cancelled to allow for the new affiliation. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 248 8) shall determine the public service identity of the controlling MCVideo function associated with the group identity in the SIP INVITE request; NOTE 6: The public service identity can identify the controlling MCVideo function in the primary MCVideo system or a partner MCVideo system. NOTE 7: How the participating MCVideo server discovers the public service identity of the controlling MCVideo function associated with the group identity is out of scope of the current release. 9) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3; 10) shall set the Request-URI to the public service identity of the controlling MCVideo function associated with the group identity which was present in the incoming SIP INVITE request; 11) shall not copy the following header fields from the incoming SIP INVITE request to the outgoing SIP INVITE request, if they were present in the incoming SIP INVITE request: a) Answer-Mode header field as specified in IETF RFC 5373 [27]; and b) Priv-Answer-Mode header field as specified in IETF RFC 5373 [27]; 12) shall set the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the SIP INVITE request to the MCVideo ID of the calling user; 13) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; 14) if the received SIP INVITE request contains an application/vnd.3gpp.location-info+xml MIME body and if not already copied, shall copy the contents of the application/vnd.3gpp.location-info+xml MIME body received in the SIP INVITE request into an application/vnd.3gpp.location-info+xml MIME body included in the outgoing SIP request; 15) if a Resource-Priority header field was included in the received SIP INVITE request, shall include a Resource- Priority header field according to rules and procedures of 3GPP TS 24.229 [11] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCVideo client; and NOTE 8: The participating MCVideo function will leave verification of the Resource-Priority header field to the controlling MCVideo function. 16) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [11]. Upon receipt of a SIP 302 (Moved Temporarily) response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.2.1.10; 2) shall include an SDP offer based upon the SDP offer in the received SIP INVITE request from the MCVideo client as specified in clause 6.3.2.1.1.1; and 3) shall forward the SIP INVITE request according to 3GPP TS 24.229 [11]. Upon receipt of a SIP 2xx response in response to the above SIP INVITE request in step 15), the participating MCVideo function: 1) if the received SIP 2xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <MKFC-GKTPs> element, shall perform the procedures in clause 6.3.2.3.2; 2) shall generate a SIP 200 (OK) response as in clause 6.3.2.1.5.2; 3) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1; 4) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; 5) shall include the public service identity received in the P-Asserted-Identity header field of the incoming SIP 200 (OK) response into the P-Asserted-Identity header field of the outgoing SIP 200 (OK) response; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 249 6) shall include an MCVideo session identity mapped to the MCVideo session identity provided in the Contact header field of the received SIP 200 (OK) response; 7) if the procedures of clause 8.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 8.2.2.2.13; 8) shall send the SIP 200 (OK) response to the MCVideo client according to 3GPP TS 24.229 [11]; 9) shall interact with Media Plane as specified in 3GPP TS 24.581 [5]; and 10) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [23]. Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request in step 14) the participating MCVideo function: 1) shall generate a SIP response according to 3GPP TS 24.229 [11]; 2) shall include Warning header field(s) that were received in the incoming SIP response; 3) shall forward the SIP response to the MCVideo client according to 3GPP TS 24.229 [11]; and 4) if the implicit affiliation procedures of clause 8.2.2.2.12 were invoked in this procedure, shall perform the procedures of clause 8.2.2.2.14;" [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.3.3.1] "Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 6.3.2.1.6." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.1] "Once an on-demand MCVideo session is established or a pre-established session is in use when the participating MCVideo function receives transmission control messages from the transmission participant in the MCVideo client or from the transmission control server in the controlling MCVideo function, the behaviour of the participating MCVideo function is described in the following clauses." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 250 ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 251 Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.3.11] "The Transmission Indicator contains additional information about a received transmission control message. Table 9.2.3.11-1 describes the coding of the Transmission Indicator field. Table 9.2.3.11-1: Transmission Indicator field coding 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Transmission |Transmission |Transmission Indicator value | |Indicator |Indicator | | |field ID value |Length value | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The <Transmission Indicator field ID> value is a binary value and is set according to table 9.2.3.1-1. The <Transmission Indicator Length> value is a binary value and has the value '2'. The <Transmission Indicator> value is a 16 bit bit-map named as shown in table 9.2.3.11-2: Table 9.2.3.11-2: Transmission Indicator bit marking +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When set to 1, the bit has the following meaning: A = Normal call B = Broadcast group call C = System call D = Emergency call E = Imminent peril call NOTE 1: The indicators C, D and E are only informative. There are no procedures specified for the C, D and E indicators in this release of the present document and the use of the indicators are implementation specific. Bits F to P are reserved for future use and are set to 0. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 252 There can be more than one bit set to 1 at the same time. The local policy in the transmission control server decides which combinations are possible and the priority of the indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.3.2] "When entering this state from any state except the 'Start-stop' state and if no MCVideo client negotiated support of queueing Transmission requests as described in clause 14, the transmission control arbitration logic in the transmission control server: 1. if the active Transmission request queue is empty the transmission control server: a. shall send Transmission Idle message to all transmission participants. The Transmission Idle message: i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; b. shall start timer T2 (Transmit Idle) and initialise counter C2 (Transmit Idle) to 1; c. shall start timer T1 (Inactivity); d. shall set the general state to the 'G: Transmit Idle' state; and e. shall initialise counter Cx (Simultaneous transmission video) to 0. 2. if the active Transmission request queue is not empty the transmission control server: a. shall select a queued Transmission request from the top of the active Transmission request queue; b. shall remove that queued Transmission request from the active Transmission request queue; and c. shall enter the 'G: Transmit Taken' state as specified in the clause 6.3.4.4.2 with respect to that transmission participant." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send a Transmission Grant message to the requesting transmission participant. The Transmission Grant message: a. shall include the granted priority in the Transmission priority field; b. shall increment counter Cx (Simultaneous transmission video) by 1 if counter Cx (Simultaneous transmission video) has not reached its upper limit; c. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and d. shall include the SSRC of the granted transmission participant to be used by the MCVideo user transmitting the media; 2. shall start timer T4 (Transmission Granted) if the Transmission request was queued and initialise the counter C4 (Transmission Grant) to 1; 3. shall send Media Transmission notify message to the reception control arbitration logic. The Media Transmission notification message: a. shall include the granted MCVideo user's MCVideo ID in the User ID field, if privacy is not requested; b. shall include the granted MCVideo user's SSRC in the SSRC of transmitter field; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 253 c. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; d. if the session is a broadcast group call, shall include the Permission to Request the Transmission field set to '0'; e. if the session is not a broadcast group call, may include the Permission to Request the Transmission field set to '1'; f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and g. shall initiate the 'general reception control operation' state machine;and 4. shall enter the 'G: Transmit Taken' state." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.4.12] "Upon receiving an implicit Transmission request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the transmission control arbitration logic in the transmission control server: 1. if counter Cx (Simultaneous transmission video) has not reached its upper limit: a. shall perform the actions specified in the clause 6.3.4.4.2; 2. if counter Cx (Simultaneous transmission video) has reached its upper limit: a. select one of the transmission participants with permission to send media without the pre-emptive priority or low effective priority; b. shall stop timer T4 (Transmission Grant), if running; c. shall set the Reject Cause field in the Transmission Revoke message to #4 (Media Transmission pre- empted); d. shall enter the 'G: pending Transmission Revoke' state as specified in the clause 6.3.4.5.2; e. shall insert the transmission participant into the active Transmission request queue to the position in front of all queued requests, if not inserted yet or update the position of the transmission participant in the active Transmission request queue to the position in front of all other queued requests, if already inserted; and f. shall send a Transmission Queue Position Info message to the requesting transmission participant, if negotiated support of queueing Transmission requests as specified in clause 14. The Queue Position Request message: i. shall include the queue position and transmission priority in the Queue Info field; and ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.4.5.2] "When entering this state the transmission control arbitration logic in the transmission control server: 1. shall send the Transmission Revoke or Transmission End Request message to the permitted transmission participant. The Transmission Revoke or Transmission End Request message: a. shall include the reason for sending the Transmission Revoke or Transmission End Request message in the <Reject Cause> value in the Reject Cause field; and b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 254 2. shall set the general state to 'G: pending Transmission Revoke'." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 255 ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 256 b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.13.3 Test description | 5.1.1.13.3.1 Pre-test conditions System Simulator: - SS (MCVideo Server), providing the controlling MCVideo function. - SS-UE1 (MCVideo Client). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 257 IUT: - IUT (MCVideo Server), providing the originating participating 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 some sub- systems of the MCVideo Server, including the Media Distribution Function, the MCVideo User Database, the SIP AS, the HTTP Server and the HTTP Client. Preamble: - The IUT (MCVideo Server) is connected to SS (MCVideo Server) and SS-UE1 (MCVideo Client). - The SS-UE1 (MCVideo client) is registered and authorized to use the MCVideo system. - The SS-UE1 (MCVideo client) is affiliated to the pre-arranged group and is authorized to initiate broadcast group calls. 5.1.1.13.3.2 Test procedure sequence Table 5.1.1.13.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 CO session establishment/modification without provisional responses other than 100 Trying' as described in Annex A, Table A.4.2.1.3-1 to establish a broadcast group call with implicit transmission control request according to option b.ii of note in Annex A, Table A.4.2.1.3-1, initiated by SS-UE1 (MCVideo Client? - - 1 P 2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO Transmission End Request - Transmission End Response' as described in Annex A, Table A.4.2.5.3-1 to end SS-UE1 (MCVideo Client) transmission? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Transmission Granted' as described in Annex A, Table A.4.2.4.3-1, to request permission to transmit for SS-UE1 (MCVideo Client)? - - 3 P 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo CO call release' as described in Annex A, Table A.4.2.3.3-1, to release the call? - - 4 P 5.1.1.13.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.1.1.13.3.3-1: SIP INVITE from SS-UE1 (MCVideo Client) (Step 1, Table 5.1.1.13.3.2-1; Step 1, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-1, with conditions GROUP-CALL and BROADCAST-CALL. NOTE: Conditions are also applied to all body parts. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 258 Table 5.1.1.13.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.13.3.2-1; Step 2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-2, with conditions GROUP-CALL and BROADCAST-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.13.3.3-3: SIP 200 (OK) from SS (MCVideo Server) (Step 1, Table 5.1.1.13.3.2-1; Step 5, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-3, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.13.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.1.1.13.3.2-1; Step 6, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.1.4-4, with condition GROUP-CALL. NOTE: Conditions are also applied to all body parts. Table 5.1.1.13.3.3-5: Transmission Idle (Steps 2, Table 5.1.1.13.3.2-1; Steps 9 and 10, Annex A, Table A.4.2.5.3-1) Derivation Path: Annex A, Table A.4.2.5.4-3, with condition BROADCAST-CALL. Table 5.1.1.13.3.3-6: Transmission Request (Step 3, Table 5.1.1.13.3.2-1; Steps 1 and 2, Annex A, Table A.4.2.4.3-1) Derivation Path: Annex A, Table A.4.2.4.4-1, with condition BROADCAST-CALL. Table 5.1.1.13.3.3-7: Transmission Granted (Steps 1 and 3, Table 5.1.1.13.3.2-1; Steps 5 and 6, Annex A, Table A.4.2.4.3-1; Steps 9a1 and 9a2, Annex A, Table A.4.2.1.3-1) Derivation Path: Annex A, Table A.4.2.4.4-2, with condition BROADCAST-CALL. 5.1.1.14 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Transmission Control State Transitions / Controlling server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.14.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 pre- arranged group call without implicit transmission control } then { IUT (MCVideo Server) accepts the call from initiator and establishes the call with all affiliated users by sending call establishment requests to SS (MCVideo Server) providing the terminating participating function and sends transmission idle to SS-UE1 (MCVideo Client) and SS-UE2 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control } then { IUT (MCVideo Server) sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 259 (3) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE2 (MCVideo Client) requests the transmission control with higher priority than SS- UE1 (MCVideo Client) while SS-UE1 is transmitting media } then { IUT (MCVideo Server) revokes SS-UE1 (MCVideo Client) media transmission permission and grants the transmission to SS-UE2 (MCVideo Client) by sending a transmission granted message and sends media transmission notification to SS-UE1 (MCVideo Client) } } (4) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) sends transmission control idle to SS-UE1 (MCVideo Client) and SS- UE2 (MCVideo Client) and stops forwarding media from SS-UE1 (MCVideo Client) } } (5) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE2 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) sends transmission control idle to SS-UE1 (MCVideo Client) and SS- UE2 (MCVideo Client) and stops forwarding media from SS-UE2 (MCVideo Client) } } (6) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE2 (MCVideo Client) requests the transmission control with high priority } then { IUT (MCVideo Server) sends transmission granted to SS-UE2 (MCVideo Client) and sends media transmission notification to SS-UE1 (MCVideo Client) } } (7) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control with lower priority than SS- UE2 (MCVideo Client), while SS-UE2 is transmitting media } then { IUT (MCVideo Server) queues SS-UE1 (MCVideo Client) media transmission request and responds with a queue position info message to SS-UE1 (MCVideo Client) } } (8) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests queue position information } then { IUT (MCVideo Server) responds with a queue position info message to SS-UE1 (MCVideo Client) } } (9) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to cancel queued transmission request } then { IUT (MCVideo Server) accepts SS-UE1 (MCVideo client) transmission request cancellation and removes the request from the queue } } (10) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE2 (MCVideo Client) requests to end the transmission control while SS-UE1 (MCVideo Client) transmission request is queued } then { IUT (MCVideo Server) accepts SS-UE2 (MCVideo Client) transmission end request and stops forwarding media from SS-UE2 (MCVideo Client) and sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 260 (11) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control with lower priority than SS- UE2 (MCVideo Client), while SS-UE2 is transmitting media } then { IUT (MCVideo Server) rejects SS-UE1 (MCVideo Client) media transmission request by sending a transmission rejected message } } (12) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) transmits for a longer period than allowed in the transmission granted } then { IUT (MCVideo Server) revokes SS-UE1 (MCVideo Client) media transmission permission and stops forwarding media } } (13) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function ends the pre- arranged group 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.1.1.14.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 9.2.1.4.1.1, 9.2.1.4.1.2, 9.2.1.4.2, 9.2.1.4.3, 6.3.3.1.2 and 6.3.3.1.1, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.3.2.2, 6.3.3, 6.4.2, 6.4.3, 6.4.4, 9.2.1, 6.2.1, 6.2.2, 6.2.4, 6.3.3 and 6.3.5.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.1.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.1.4.2 or as the result of receiving a SIP 403 (Forbidden) response as described in this clause. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited.; NOTE 1: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 2: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 3) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the MCVideo ID of the terminating user; and b) the <mcvideo-calling-group-id> element set to the group identity; NOTE 3: The <mcvideo-calling-user-id> is already included in the MIME body as a result of calling clause 6.3.3.1.2 in step 1). ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 261 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; 6) if the in-progress emergency state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.19; b) if the received SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true": i) shall include in the outgoing SIP INVITE request in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; and ii) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcvideo-info+xml MIME body and the application/vnd.3gpp.location- info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false"; and c) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.19; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; and 9) shall send the SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response containing a Require header field with the option tag "100rel" and containing a P-Answer-State header field with the value "Unconfirmed" in response to the SIP INVITE request the controlling MCVideo function: 1) shall send a SIP PRACK request towards the MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 262 2) shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 9.2.3.4; and 3) shall increment the local counter of the number of SIP 200 (OK) responses received from invited members, by 1. NOTE 4: The notifications above could be sent prior to the SIP 200 (OK) response being sent to the inviting MCVideo client. These notifications received by MCVideo clients that are group members do not mean that the group session will be successfully established. NOTE 5: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.1.2] "The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the non-controlling MCVideo function serving the group identity of the MCVideo group owned by the partner MCVideo system; 3) shall set the P-Asserted-Identity to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the group identity of the MCVideo group hosted by the non- controlling MCVideo function in the partner MCVideo system; and b) the <mcvideo-calling-group-id> element set to the group identity of the group served by the controlling MCVideo function; 5) shall include the Recv-Info header field set to g.3gpp.mcvideo-transmission-request; 6) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and 8) shall send the SIP INVITE request towards the partner MCVideo system in accordance with 3GPP TS 24.229 [11]. Upon receiving SIP 403 (Forbidden) response for the SIP INVITE request, if according to local policy and if: 1) the response contains a Warning header field with the MCVideo warning code "128"; and 2) the response contains a P-Refused-URI-List header field and an application/resource-lists+xml MIME body as specified in IETF RFC 5318 [28]; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 263 NOTE 1: The application/resource-lists+xml MIME body contains MCVideo IDs identifying MCVideo users in a partner MCVideo system that needs to be invited to the prearranged group call in case of group regrouping using interrogating method. Editor's Note: The above note currently isn't defined in the 23.280 and 23.281. then the controlling MCVideo function: 1) shall check if the number of members of the MCVideo group exceeds the value contained in the <on-network- max-participant-count> element of the group document as specified in 3GPP TS 24.481 [24]. If exceeded, the controlling MCVideo function shall invite only <on-network-max-participant-count> members from the application/resource-lists+xml MIME body; and NOTE 2: The <on-network-max-participant-count> element indicates the maximum number of participants allowed in the prearranged group session It is operator policy that determines which participants in the application/resource-lists+xml MIME body are invited to the group call. 2) shall invite MCVideo users as specified in this clause using the list of MCVideo IDs in URI-List. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and NOTE 3: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2. 2) if at least one of the invited MCVideo clients has subscribed to the conference package, shall subscribe to the conference event package in the non-controlling MCVideo function as specified in clause 9.2.3.4.3." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.2] "In the procedures in this clause: 1) MCVideo ID in an incoming SIP INVITE request refers to the MCVideo ID of the originating user from the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 3) MCVideo ID in an outgoing SIP INVITE request refers to the MCVideo ID of the called user in the <mcvideo- request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) indication of required group members in a SIP 183 (Session Progress) response refers to the <required> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to "true" in a SIP 183 (Session Progress) sent by the non-controlling MCVideo function of an MCVideo group; 5) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 6) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for controlling MCVideo function of an MCVideo group", the controlling MCVideo function: 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The controlling MCVideo function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [15] and skip the rest of the steps; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 264 NOTE 1: if the SIP INVITE request contains an emergency indication or an imminent peril indication set to a value of "true" and this is an authorised request for originating an MCVideo emergency group call as determined by clause 6.3.3.1.13.2, or for originating an MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5, the controlling MCVideo function can according to local policy choose to accept the request. 2) shall determine if the media parameters are acceptable and the MCVideo codecs are offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps; 3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if: a) an Accept-Contact header field does not include the g.3gpp.mcvideo media feature tag; or b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; 4) if received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; 5) shall retrieve the necessary group document(s) from the group management server for the group identity contained in the SIP INVITE request and carry out initial processing as specified in clause 6.3.5.2; 6) if the result of the initial processing in clause 6.3.5.2 was: a) that authorization of the MCVideo ID is required at a non-controlling MCVideo function of an MCVideo group is required, perform the actions in clause 6.3.3.1.13.7 and do not continue with the rest of the steps in this clause; and b) that a SIP 3xx, 4xx, 5xx or 6xx response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group" has been sent, do not continue with the rest of the steps in this clause; 7) shall perform the actions as described in clause 6.3.3.2.2; 8) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero; 9) shall determine if an MCVideo group call for the group identity is already ongoing by determining if an MCVideo session identity has already been allocated for the group call and the MCVideo session is active; 10) if the SIP INVITE request contains an unauthorised request for an MCVideo emergency group 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 [11] and skip the rest of the steps; 11) if the SIP INVITE request contains an unauthorised request for an MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5, shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the following clarifications: a) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in clause F.1 with the <mcvideoinfo> element containing the <mcvideo-Params> element with the <imminentperil-ind> element set to a value of "false"; and b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [11] and skip the rest of the steps; 12) if a Resource-Priority header field is included in the SIP INVITE request: a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; or ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 265 b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; 13) if the MCVideo group call is not ongoing then: a) if: i) the user identified by the MCVideo ID is not affiliated to the group identity contained in the SIP INVITE request as specified in clause 6.3.6; ii) the group identity contained in the SIP INVITE request is not a constituent MCVideo group ID; iii) the received SIP INVITE request does not contain an emergency indication or imminent peril indication; or iv) the received SIP INVITE request is an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by steps clause 6.3.3.1.13.5 and is determined to not be eligible for implicit affiliation as specified in clause 8.2.2.3.6; then shall return a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4, and skip the rest of the steps below; b) if the user identified by the MCVideo ID is not authorised to initiate the prearranged group session as specified in clause 6.3.5.4, shall send a SIP 403 (Forbidden) response with the warning text set to: "119 user is not authorised to initiate the group call" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below; c) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined as determined in step 13) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; d) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; e) shall create a prearranged group session and allocate an MCVideo session identity for the prearranged group call, and shall handle timer TNG3 (group call timer) as specified in clause 6.3.3.5; f) if the group identity in the "SIP INVITE request for controlling MCVideo function of an MCVideo group" is a TGI: i) shall for each of the constituent MCVideo groups homed on the primary MCVideo system: A) if the controlling MCVideo function does not own the MCVideo group identified by the MCVideo group ID, then generate a SIP INVITE request towards the MCVideo server that owns the MCVideo group identity by following the procedures in clause 9.2.1.4.1.2; and NOTE 2: The MCVideo server that the SIP INVITE request is sent to acts as a non-controlling MCVideo function; B) if the controlling MCVideo function owns the MCVideo group identified by the MCVideo group ID then: I) determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; II) invite each group member determined in step A) above, to the group session, as specified in clause 9.2.1.4.1.1; and III) interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 266 ii) shall for each of the constituent MCVideo groups homed on the partner MCVideo system generate a SIP INVITE request for the MCVideo group identity homed on the partner MCVideo system as specified in clause 9.2.1.4.1.2; and g) if the group identity in the SIP INVITE request for controlling MCVideo function of an MCVideo group is an MCVideo group ID: i) shall determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; ii) if necessary, shall start timer TNG1 (acknowledged call setup timer) according to the conditions stated in clause 6.3.3.3; iii) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": A) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; and C) if the in-progress emergency state of the group is set to a value of "false": I) shall set the value of the in-progress emergency state of the group to "true"; and II) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; iv) if the in-progress emergency state of the group is set to a value of "false" and if the received SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function shall: A) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and B) if the in-progress imminent peril state of the group is set to a value of "false", shall set the in- progress imminent peril state of the group to a value of "true"; v) shall invite each group member determined in step 13)g)i) above, to the group session, as specified in clause 9.2.1.4.1.1; and vi) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and 14) if the MCVideo group call is ongoing then: a) if: i) the user identified by the MCVideo ID in the SIP INVITE request is not affiliated to the group identity contained in the SIP INVITE request as specified in clause 6.3.6; ii) the group identity contained in the SIP INVITE request is not a constituent MCVideo group ID; iii) the received SIP INVITE request does not contain an emergency indication or imminent peril indication; or iv) the received SIP INVITE request is an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined clause 6.3.3.1.13.5 and is determined to not be eligible for implicit affiliation as specified in clause 8.2.2.3.6; then shall return a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4, and skip the rest of the steps below; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 267 b) if the user identified by the MCVideo ID in the SIP INVITE request is not authorised to join the prearranged group session as specified in clause 6.3.5.3, shall send a SIP 403 (Forbidden) response with the warning text set to "121 user is not allowed to join the group call" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below; c) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; d) if <on-network-max-participant-count> as specified in 3GPP TS 24.481 [24] is already reached: i) if, according to local policy, the user identified by the MCVideo ID in the SIP INVITE request is deemed to have a higher priority than an existing user in the group session, may remove a participant from the session by following clause 9.2.1.4.4.3, and skip the next step; and NOTE 3: The local policy for deciding whether to admit a user to a call that has reached its maximum amount of participants can include the <user-priority> and the <participant-type> of the user as well as other information of the user from the group document as specified in 3GPP TS 24.481 [24]. The local policy decisions can also include taking into account whether the imminent-peril indicator or emergency indicator was received in the SIP INVITE request. ii) shall return a SIP 486 (Busy Here) response with the warning text set to "122 too many participants" to the originating network as specified in clause 4.4 and skip the rest of the steps; e) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined in step 14) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; f) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": i) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; iii) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; and C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.6; iv) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and v) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; g) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function: i) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 268 ii) if the in-progress imminent peril state of the group is set to a value of "false": A) shall set the in-progress imminent peril state of the group to a value of "true"; B) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.15; and C) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and iii) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; h) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.4.2; i) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; j) shall include in the SIP 200 (OK) response with the warning text set to "123 MCVideo session already exists" as specified in clause 4.4; k) if the received SIP re-INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; l) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 4: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. m) shall interact with media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 5: Resulting media plane processing is completed before the next step is performed. n) shall send the SIP 200 (OK) response towards the inviting MCVideo client or inviting non-controlling MCVideo function according to 3GPP TS 24.229 [11]; o) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; NOTE 6: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. p) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]; q) Upon receiving a SIP ACK to the above SIP 200 (OK) response and the SIP 200 (OK) response contained a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall follow the procedures in clause 6.3.3.1.18; and r) shall not continue with the rest of the clause. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 269 Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 9.2.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [30], the timer TNG1 (acknowledged call setup timer) is not running, the controlling MCVideo function supports media buffering and the SIP final response is not yet sent to the inviting MCVideo client: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) shall include a P-Answer-State header field with the value "Unconfirmed"; 5) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 7: Resulting user plane processing is completed before the next step is performed. 8) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; 9) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 8: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 10) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response for a SIP INVITE request as specified in clause 9.2.1.4.1.2 containing an indication of required group members, the timer TNG1 (acknowledged call setup timer) is running and all SIP 200 (OK) responses have been received to all SIP INVITE requests sent to MCVideo clients specified in clause 9.2.1.4.1.1, then the controlling MCVideo function shall wait until the SIP 200 (OK) response has been received to the SIP INVITE request specified in clause 9.2.1.4.1.2 before generating a SIP 200 (OK) response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group". Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1 that was sent to an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24]; and 1) if the MCVideo ID in the SIP 200 (OK) response matches to the MCVideo ID in the corresponding SIP INVITE request; 2) there are no outstanding SIP 200 (OK) responses to SIP INVITE requests which were sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24]; and 3) there is no outstanding SIP 200 (OK) response to a SIP INVITE request sent in clause 9.2.1.4.1.2 where the SIP 183 (Session Progress) response contained an indication of required group members; the controlling MCVideo function: 1) shall stop timer TNG1 (acknowledged call setup timer) as described in clause 6.3.3.3; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 270 2) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 3) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has been exceeded the <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 4) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 5) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 9: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 7) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 10: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 8) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon: 1) receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1; 2) the timer TNG1 (acknowledged call setup timer) is not running; 3) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; 4) the controlling MCVideo function supports media buffering; and 5) the SIP final response has not yet been sent to the inviting MCVideo client; the controlling MCVideo function according to local policy: 1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has exceeded the <max- participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 5) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 11: Resulting media plane processing is completed before the next step is performed. 7) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 271 8) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 12: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 9) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon expiry of timer TNG1 (acknowledged call setup timer), if there are outstanding SIP 200 (OK) responses to SIP INVITE requests sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the procedures specified in clause 6.3.3.3. If timer TNG1 (acknowledged call setup timer) is running and a final SIP 4xx, 5xx or 6xx response is received from an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the relevant procedures specified in clause 6.3.3.3. If: 1) timer TNG1 (acknowledged call setup timer) is not running; 2) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; and 3) a final SIP 4xx, 5xx or 6xx response is received from an invited MCVideo client; then the controlling MCVideo function shall perform one of the following based on policy: 1) send the SIP final response towards the inviting MCVideo client, according to 3GPP TS 24.229 [11], if a SIP final response was received from all the other invited MCVideo clients and the SIP 200 (OK) response is not yet sent; or 2) remove the invited MCVideo client from the MCVideo Session as specified in clause 6.3.3.1.5, if a SIP final response other than 2xx or 3xx was received from all the invited MCVideo clients and the SIP 200 (OK) response is already sent. The controlling MCVideo function may invite an additional member of the prearranged MCVideo group as specified in clause 9.2.1.4.1 that has not already been invited, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24], and all members have not yet been invited. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.3] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.2] "This clause is referenced from other procedures. The controlling MCVideo function shall generate an initial SIP INVITE request according to 3GPP TS 24.229 [11]. The controlling MCVideo function: 1) shall include in the Contact header field an MCVideo session identity for the MCVideo session with the g.3gpp.mcvideo media feature tag, the isfocus media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" according to IETF RFC 3840 [22]; 2) shall include an Accept-Contact header field containing the g.3gpp.mcvideo media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; 3) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Asserted-Service-Id header field according to IETF RFC 6050 [14] in the SIP INVITE request; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 272 4) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with parameters "require" and "explicit" according to IETF RFC 3841 [20]; 5) shall include a Referred-By header field with the public user identity of the inviting MCVideo client; 6) should include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [7]. The refresher parameter shall be omitted; 7) shall include the Supported header field set to "timer"; 8) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body to the outgoing INVITE request; 9) if the received SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body containing an <ambient-viewing-type> element and: a) if the Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was included in the received SIP INVITE request with a value of "Auto" or if no Priv-Answer-Mode header field was received in the received SIP INVITE request; or b) a Priv-Answer-Mode header field was received containing a value other than "Auto"; shall include a Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request; and 10) if the received SIP INVITE request did not contain an application/vnd.3gpp.mcvideo-info+xml MIME body containing an <ambient-viewing-type> element, shall include an unmodified Answer-Mode header field if present in the incoming SIP INVITE request." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.1] "The SDP offer is generated based on the received SDP offer. The SDP offer generated by the controlling MCVideo function: 1) when initiating a new MCVideo session the SDP offer; a) shall contain only one SDP media-level section for MCVideo video media stream as contained in the received SDP offer; and b) shall contain an SDP media-level section for one media-transmission control entity, if present in the received SDP offer; and 2) when adding a new MCVideo user to an existing MCVideo Session, the SDP offer shall contain the media stream currently used in the MCVideo session. When composing the SDP offer according to 3GPP TS 24.229 [11], the controlling MCVideo function: 1) shall replace the IP address and port number for the offered media stream in the received SDP offer with the IP address and port number of the controlling MCVideo function; 2) for the MCVideo video media stream, shall include all media-level attributes from the received SDP offer; 3) shall replace the IP address and port number for the offered media transmission control entity, if any, in the received SDP offer with the IP address and port number of the controlling MCVideo function; and 4) for the offered media transmission control entity, shall include the offered media transmission control entity 'fmtp' attributes as specified in 3GPP TS 24.581 [5] clause 14." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.2.2] "When an MCVideo call is established a new instance of the transmission control server state machine for 'general transmission control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' is added. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 273 When an MCVideo call is established a new instance of the transmission control server state machine for 'general reception control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic reception control operation towards the transmission participant' is added. If the optional "mc_queueing" feature is supported and has been negotiated as specified in clause 14, the transmission control server could queue the implicit transmission control request for the media-transmission control entity. The original initial SIP INVITE request or SIP REFER request to establish an MCVideo chat group call or to rejoin an ongoing MCVideo call is not handled as an implicit transmission control request message by the transmission control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request. The permission to send media to the inviting MCVideo client due to implicit transmission control request is applicable to both confirmed indication and unconfirmed indication. When the first unconfirmed indication is received from the invited participating MCVideo function (see 3GPP TS 24.281 [2]) the transmission control server optionally can give an early indication to send RTP media packets, to the inviting MCVideo client. If an early indication to send RTP media packets is given to the inviting MCVideo client, the transmission participant is granted the permission to send media and the MCVideo server buffers RTP media packets received from the MCVideo client at least until the first invited MCVideo client accepts the invitation or until the RTP media packet buffer exceeds it maximum limit to store RTP media packets. If the MCVideo server does not support or does not allow media buffering then when an early indication to send RTP media packets is not given to the inviting MCVideo client, the transmission participant is granted the permission to send media when the first invited MCVideo client accepts the media. Before the transmission control server sends the first transmission control message in the MCVideo call, the transmission control server has to assign itself a SSRC identifier to be included in media transmission control messages and quality feedback messages if the MCVideo server is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3]. The transmission participant and the transmission control server can negotiate the maximum priority level that the transmission participant is permitted to request. The transmission control server can pre-empt the current sender based on the negotiated maximum priority level that the transmission participant is permitted to request and the priority level included in the Transmission Media Request message. NOTE: The maximum priority level that a transmission participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the controlling MCVideo function from the group management server as described in 3GPP TS 24.481 [12] and service configuration data retrieved by the controlling MCVideo function from the configuration management server as described in 3GPP TS 24.484 [13]. The transmission participant and the transmission control server can negotiate queueing of Transmission requests using the "mc_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the transmission control server queues the transmission control request if a Transmission Media Request message is received when another transmission participant has the transmission and the priority of the current speaker is the same or higher." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 274 When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 275 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.1] "The transmission control messages are coded as described in clause 9.1.2 where the transmission control message is part of the application-dependent data. For the transmission control protocol the ASCII name string is: MCVx (Mission Critical Video x) with x=0, 1 or 2 as specified in clause 9.1.2. A list of transmission control messages can be found in clause 9.2.2.1. The transmission control specific fields are specified in clause 9.2.3." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.2.1] "Based on the negotiations during the call establishment specified in 3GPP TS 24.281 [2], a new instance of the 'Transmission participant state transition diagram for basic transmission control operation', as specified in clause 6.2.4 and a new instance of the 'Transmission participant state transition diagram for basic reception control operation' as specified in clause 6.2.5, shall be created for this call. The SIP INVITE request sent by the application and signalling plane: 1. shall be regarded an implicit Transmission request when an implicit Transmission request is negotiated; and 2. shall not be regarded as an implicit Transmission request in case of a rejoin to an already on-going group call. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 276 NOTE: The transmission participant can negotiate the use of prioritization of the Transmission Media Request message. In that case, the transmission participant can request permission to send media at a priority level that is either the same as or lower than the highest priority that was permitted to the participant in the MCVideo call initialization. If a transmission participant is authorized for pre-emptive priority in the MCVideo call it is good practise to always request permission to send RTP media packets at a priority level that is lower than pre-emptive priority unless the user explicitly requests to pre-empt the current RTP media packets sender." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.2.2] "The MCVideo call release (whether it is initiated by the transmission participant or transmission control server) is a two-step procedure. Step 1 The transmission participant stops sending transmission control and reception control messages and the MCVideo client stops sending and receiving RTP media packets. Step 2 When the application and signalling plane has determined that the MCVideo call is released, the corresponding instance of the 'Transmission participant state transition diagram for basic transmission control operation' as specified in clause 6.2.4 and the corresponding instance of the 'Transmission participant state transition diagram for basic reception control operation' as specified in clause 6.2.5 are terminated and the transmission participant releases all the used resources. The user plane can initiate the release step 1, but the application and signalling plane always initiates the release step 2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.2.4] "The transmission participant shall behave according to the state diagram and the state transitions specified in this clause. Figure 6.2.4.1-1 shows the state diagram for 'Transmission participant state transition diagram for basic transmission control operation'. …" [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 277 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.5.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiates an MCVideo call with an implicit Transmission request, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 2: In the clause 6.3.4.2.2 the 'general transmission control operation' state machine will continue with the initialization of the 'general transmission control operation' state machine. b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; 2. if the associated MCVideo client rejoins an ongoing MCVideo call without an implicit Transmission request or initiates or joins a chat group call without an implicit Transmission request or attempts to initiate an already existing MCVideo call without an implicit Transmission request, and a. if an MCVideo call already exists but no MCVideo client has the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; b. if an MCVideo call is initiated, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted and Transmit Idle' as specified in the clause 6.3.5.5.2; and ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine. c. if other MCVideo clients have the permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; NOTE 3: For multiple MCVideo clients have the permission to send a media, the following Media Transmission notify messages will be handle as in 'U: not permitted and transmit taken' state as specified in the clause 6.3.5.4.2. 3. if the associated transmission participant attempts to initiate an already existing MCVideo call with an implicit Transmission request, and a. if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.3.3; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 278 ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;b. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has not reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall processes the implicit Transmission request as if a Transmission Media Request message was receive as specified in clause 6.3.4.4.12; and ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2; c. if the MCVideo client negotiated support of queueing Transmission requests as specified in clause 14 and if other MCVideo clients have the permission to send media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall set the priority level to the negotiated maximum priority level that the MCVideo client is permitted to request, except for pre-emptive priority, when high priority is used; NOTE 4: The maximum transmission priority the transmission participant is permitted to request is negotiated in the "mc_priority" fmtp attribute as specified in clause 14. NOTE 5: The initial implicit Transmission request will not result in pre-emption when an MCVideo client is joining an ongoing MCVideo call. If the MCVideo client wants to pre-empt the current MCVideo client that are sending media, an explicit Transmission request with pre-emptive transmission priority is required. ii. shall insert the MCVideo client into the active Transmission request queue to the position immediately following all queued Transmission requests with the same transmission priority; iii. shall send a Transmission Queue Position Info message to the MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; iv. should send a Transmission Queue Position Info message with the updated status to the MCVideo clients in the active Transmission request queue which negotiated queueing of Transmission requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Transmission Queue Position Info message and which is not the joining MCVideo client. The Transmission Queue Position Info message: A. shall include the queue position and transmission priority in the Queue Info field; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and v. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and d. if the MCVideo client did not negotiate queueing of Transmission requests and if other MCVideo clients have the permission to send a media and if Cx (Simultaneous Transmission video) has reached it upper limit, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and 4. if the MCVideo client is invited to the MCVideo call and a. if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the 'U: not permitted and Transmit Taken' state as specified in the clause 6.3.5.4.2; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 279 b. if no other MCVideo client has the permission to send a media; the transmission control interface towards the MCVideo client in the transmission control server: i. should send a Transmission Idle message to the MCVideo client. The Transmission Idle message: A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Transmission Indicator field with appropriate indications; and ii. shall enter the 'U: not permitted and Transmit Idle' state as specified in the clause 6.3.5.3.2." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.14.3 Test description | 5.1.1.14.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). 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). - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are registered and authorized to use the MCVideo system. - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are affiliated to the pre-arranged group and are authorized to initiate group calls. - The IUT (MCVideo Server) is the controlling server of the pre-arranged group. 5.1.1.14.3.2 Test procedure sequence Table 5.1.1.14.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E group call establishment' as described in Annex A, Table A.4.1.4.3-1 to establish a pre-arranged group call without implicit transmission control request according to option a of note in Annex A, Table A.4.1.4.3-1, initiated by SS-UE1 (MCVideo Client)? - - 1 P ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 280 St Procedure Message Sequence TP Verdict U - S Message 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-UE1 (MCVideo Client)? - - 2 P - EXCEPTION: Steps 3a - 3b describe behaviour that depends on pc_MCVideo_TransmissionRequestQueueing. - - - - - IF pc_MCVideo_TransmissionRequestQueueing THEN: - - - - 3a Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Queue Position Info' as described in Annex A, Table A.3.12.3-1 to request permission to transmit for SS-UE2 (MCVideo Client) with higher priority than SS-UE1 (MCVideo Client)? - - 3 P - ELSE: - - - - 3b Check: Does the IUT (MCVideo Server) correctly perform steps 1-2 of procedure 'MCVideo Transmission Request - Queue Position Info' as described in Annex A, Table A.3.12.3-1 to request permission to transmit for SS-UE2 (MCVideo Client) with higher priority than SS-UE1 (MCVideo Client)? - - 3 P 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Revoked - Transmission End Request' as described in Annex A, Table A.3.14.3-1, to revoke SS-UE1 (MCVideo Client) media transmission, with revoke reason #4 (Media Burst pre-empted)? - - 3 P 5 Check: Does the IUT (MCVideo Server) send a Transmission End Notify message to SS-UE2 (MCVideo Client) informing that SS-UE1 (MCVideo Client) has stopped to transmit? <-- Transmission End Notify 3 P 6 IF the IUT (MCVideo Server) requests acknowledgement, the SS-UE2 (MCVideo Client) sends a Transmission Control Ack message in response to the Transmission End Notify message. --> Transmission Control Ack - - 7 Check: Does the IUT (MCVideo Server) correctly perform steps 3a1-3b2 of procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1 to grant the transmission to SS-UE2 (MCVideo Client)? - - 3 P 8 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1 to end the transmission of SS-UE2 (MCVideo Client)? - - 5 P 9 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) with high priority? - - 6 P - EXCEPTION: Steps 10a1 - 10b2 describe behaviour that depends on pc_MCVideo_TransmissionRequestQueueing. - - - - - IF pc_MCVideo_TransmissionRequestQueueing THEN: - - - - ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 281 St Procedure Message Sequence TP Verdict U - S Message 10a1 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Queue Position Info' as described in Annex A, Table A.3.12.3-1 to request permission to transmit for SS-UE1 (MCVideo Client) with lower priority than SS-UE2 (MCVideo Client)? - - 7 P 10a2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Queue Position Request - Queue Position Info', as described in Annex A, Table A.3.13.3-1 to request queue position info for SS-UE1 (MCVideo Client)? - - 8 P 10a3 The SS-UE1 (MCVideo Client) sends a Transmission End Request message, with acknowledgement, to cancel queued transmission. --> Transmission End Request - - 10a4 Check: Does the IUT (MCVideo Server) send a Transmission Control Ack message? <-- Transmission Control Ack 9 P 10a5 Check: Does the IUT (MCVideo Server) send a Transmission End Response message to SS-UE1 (MCVideo Client)? <-- Transmission End Response 9 P 10a6 IF the IUT (MCVideo Server) requests acknowledgement, the SS-UE1 (MCVideo Client) sends a Transmission Control Ack message in response to the Transmission End Response message. --> Transmission Control Ack - - 10a7 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Queue Position Info' as described in Annex A, Table A.3.12.3-1 1 to request permission to transmit for SS-UE1 (MCVideo Client) with lower priority than SS-UE2 (MCVideo Client) - - 7 P 10a8 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify', except steps 4-5, as described in Annex A, Table A.3.8.3-1 to end the transmission of SS- UE2 (MCVideo Client)? - - 10 P 10a9 Check: Does the IUT (MCVideo Server) correctly perform steps 3a1-3b2 of procedure 'MCVideo Transmission Request - Granted and Media Transmission Notification' as described in Annex A, Table A.3.7.3-1 to grant transmission to SS-UE1 (MCVideo Client)? - - 10 P 10a1 1 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1 to end the transmission of SS-UE1 (MCVideo Client)?? - - 4 P - ELSE: - - - - 10b1 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Request - Rejected' as described in Annex A, Table A.3.11.3-1 to request permission to transmit for SS-UE1 (MCVideo Client) with lower priority than SS-UE2 (MCVideo Client)? - - 11 P 10b2 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify', as described in Annex A, Table A.3.8.3-1 to end the transmission of SS-UE2 (MCVideo Client)? 5 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 282 St Procedure Message Sequence TP Verdict U - S Message 11 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-UE1 (MCVideo Client)? - - 2 P 12 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission Revoked - Transmission End Request' as described in Annex A, Table A.3.14.3-1, to revoke SS-UE1 (MCVideo Client) media transmission, with revoke reason #2 (Media Burst too long)? - - 12 P 13 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1, except steps 1-3a2 and 3b1, to inform SS-UE2 (MCVideo Client) that SS-UE1 (MCVideo Client) transmission has ended? - - 12 P 14 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? - - 13 P 5.1.1.14.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.1.1.14.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.1.1.14.3.2-1; Step 1, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-1 Table 5.1.1.14.3.3-2: SIP INVITE from IUT (MCVideo Server) (Step 1, Table 5.1.1.14.3.2-1; Step 2, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-2 Table 5.1.1.14.3.3-3: SIP 200 (OK) from SS (MCVideo Server) (Step 1, Table 5.1.1.14.3.2-1; Step 8, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-6 Table 5.1.1.14.3.3-4: SIP 200 (OK) from IUT (MCVideo Server) (Step 1, Table 5.1.1.14.3.2-1; Step 9, Annex A, Table A.4.1.4.3-1) Derivation Path: Annex A, Table A.4.1.4.4-7 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 283 Table 5.1.1.14.3.3-5: Transmission Request from the SS-UE1 (MCVideo Client) (Steps 2, 10a1, 10a7 and 10b1, Table 5.1.1.14.3.2-1; Step 1, Annex A, Table A.3.7.3-1; Step 1, Annex A, Table A.3.11.3-1; Step 1, Annex A, Table A.3.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.1.1-1, with condition ACK Information Element Value/remark Comment Reference Condition Transmission Priority ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.2 Transmission Priority Value "5" Table 5.1.1.14.3.3-6: Transmission Granted from the IUT (MCVideo Server) (Steps 2 and 10a9, Table 5.1.1.14.3.2-1; Steps 3b1 and 3a1, Annex A, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.1-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Transmission Priority ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.2 Transmission Priority Value "5" Table 5.1.1.14.3.3-7: Transmission Request from the SS-UE2 (MCVideo Client) (Steps 3a, 3b and 9, Table 5.1.1.14.3.2-1; Step 1, Annex A, Table A.3.7.3-1; Step 1, Annex A, Table A.3.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.1.1-1, with condition ACK Information Element Value/remark Comment Reference Condition Transmission Priority ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.2 Transmission Priority Value "15" Table 5.1.1.14.3.3-8: Queue Position Info from the IUT (MCVideo Server) (Steps 3a and 3b, Table 5.1.1.14.3.2-1; Steps 3a1 and 3b1, Annex A, Table A.3.12.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.6-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Queue Info Defines the queue position and granted transmission control priority in the queue. ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.5 Queue Priority Level "15" ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.2 Table 5.1.1.14.3.3-9: Transmission Revoked from the IUT (MCVideo Server) (Step 4, Table 5.1.1.14.3.2-1; Steps 1aA and 1aB, Annex A, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.2-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Reject Cause ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.4 Reject Cause Value 4 ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.10.2 Reject Cause Phrase "Media Burst pre- empted" A text string encoded the text string in the SDES item CNAME. ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.10.2 ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 284 Table 5.1.1.14.3.3-10: Transmission End Request from the IUT (MCVideo Server) (Step 4, Table 5.1.1.14.3.2-1; Steps 1bA and 1bB, Annex A, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.1-1, with condition DOWNLINK. Condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Reject Cause ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.4 Reject Cause Value 4 ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.10.2 Reject Cause Phrase "Media Burst pre-empted" A text string encoded the text string in the SDES item CNAME. ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.10.2 Table 5.1.1.14.3.3-11: Transmission End Notify from the IUT (MCVideo Server) (Step 5, Table 5.1.1.14.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.15-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition User Id of the Transmitting User Carries the identity of the user whose media transmission has been released ETSI TS 124 581 [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 5.1.1.14.3.3-12: Transmission Control Ack from the SS-UE1 (MCVideo Client) (Step 6, Table 5.1.1.14.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, condition UPLINK Table 5.1.1.14.3.3-13: Transmission Granted from the IUT (MCVideo Server) (Steps 7 and 9, Table 5.1.1.14.3.2-1; Steps 3a1 and 3b1, Annex A, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.1-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Transmission Priority ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.2 Transmission Priority Value "15" Table 5.1.1.14.3.3-14: Media Transmission Notification from the IUT (MCVideo Server) (Steps 7 and 9, Table 5.1.1.14.3.2-1; Steps 3a3 and 3b2, Annex A, Table A.3.7.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.7-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 285 Table 5.1.1.14.3.3-15: Transmission End Request from the SS-UE2 (MCVideo Client) (Steps 8, 10a8 and 10b2, Table 5.1.1.14.3.2-1; Step 1, Annex A, Table A.3.8.3-1) Derivation Path: Annex A, Table A.3.8.4-1 Information Element Value/remark Comment Reference Condition User Id of the Transmitting User identity of the user whose media transmission is requested to be terminated. ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.6 User Id of the Transmitting User px_MCVideo_ID_User_ B Table 5.1.1.14.3.3-16: Transmission End Notify from the IUT (MCVideo Server) (Steps 8, 10a8 and 10b2, Table 5.1.1.14.3.2-1; Steps 3a3 and 3b2, Annex A, Table A.3.8.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.15-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Table 5.1.1.14.3.3-17: Queue Position Info from the IUT (MCVideo Server) (Steps 10a1, 10a2 and 10a7, Table 5.1.1.14.3.2-1; Steps 3a1 and 3b1, Annex A, Table A.3.12.3-1; Steps 3a1 and 3b1, Annex A, Table A.3.13.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.6-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Queue Info Defines the queue position and granted transmission control priority in the queue. ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.5 Queue Priority Level "5" ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.2 Table 5.1.1.14.3.3-18: Transmission End Request from the SS-UE1 (MCVideo Client) (Step 10a3, Table 5.1.1.14.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.1-1, with conditions ACK and UPLINK Table 5.1.1.14.3.3-19: Transmission Control Ack from the IUT (MCVideo Server) (Steps 10a4, Table 5.1.1.14.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, with condition DOWNLINK. Table 5.1.1.14.3.3-20: Transmission End Response from the IUT (MCVideo Server) (Step 10a5, Table 5.1.1.14.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.2-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Table 5.1.1.14.3.3-21: Transmission Control Ack from the SS-UE1 (MCVideo Client) (Steps 10a6, Table 5.1.1.14.3.2-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.5-1, with condition UPLINK. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 286 Table 5.1.1.14.3.3-22: Transmission Revoked from the IUT (MCVideo Server) (Step 12, Table 5.1.1.14.3.2-1; Steps 1aA and 1aB, Annex A, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.2.2-1, with condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Reject Cause ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.4 Reject Cause Value 2 ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.10.2 Reject Cause Phrase "Media burst too long" A text string encoded the text string in the SDES item CNAME. ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.10.2 Table 5.1.1.14.3.3-23: Transmission End Request from the IUT (MCVideo Server) (Step 12, Table 5.1.1.14.3.2-1; Steps 1bA and 1bB, Annex A, Table A.3.14.3-1) Derivation Path: ETSI TS 136 579-1 [1] (3GPP TS 36.579-1), Table 5.5.11.3.1-1, with condition DOWNLINK. Condition ACK IF the IUT (MCVideo Server) requests message acknowledgement. Information Element Value/remark Comment Reference Condition Reject Cause ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.3.4 Reject Cause Value 2 ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.10.2 Reject Cause Phrase "Media burst too long" A text string encoded the text string in the SDES item CNAME. ETSI TS 124 581 [6] (3GPP TS 24.581) clause 9.2.10.2 5.1.1.15 MCVideo Server - MCVideo Server / Pre-arranged Group Call / Reception Control State Transitions / Controlling server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.15.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 pre- arranged group call with implicit transmission control } then { IUT (MCVideo Server) accepts the call from initiator and establishes the call with all affiliated users by sending call establishment requests to the SS (MCVideo Server) providing the terminating participating function and sends transmission granted to the SS-UE1 (MCVideo Client) and sends media transmission notification to the SS-UE2 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE2 (MCVideo Client) requests to receive SS-UE1 (MCVideo client) media transmission } then { IUT (MCVideo Server) accepts SS-UE2 (MCVideo Client) media reception request and forwards SS-UE1 (MCVideo Client) media transmission to SS-UE2 (MCVideo Client) } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 287 (3) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE2 (MCVideo Client) requests to stop receiving SS-UE1 (MCVideo Client) media transmission } then { IUT (MCVideo Server) accepts SS-UE2 media reception end request and stops forwarding media } } (4) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) sends transmission control idle to the SS-UE1 (MCVideo Client) and stops forwarding media and sends transmission control idle to the SS-UE2 (MCVideo Client) } } (5) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control } then { IUT (MCVideo Server) sends transmission granted to the SS-UE1 (MCVideo Client) and sends media transmission notification to the SS-UE2 (MCVideo Client) } } (6) with { IUT (MCVideo Server) having established a pre-arranged group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function ends the pre- arranged group call } then { IUT (MCVideo Server) responds by sending a SIP 200 (OK) message to the SS (MCVideo Server) ending the call and sends a SIP BYE message to the SS (MCVideo Server) providing the terminating participating function } } |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.15.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 9.2.1.4.1.1, 9.2.1.4.1.2, 9.2.1.4.2, 9.2.1.4.3, 6.3.3.1.2 and 6.3.3.1.1, and ETSI TS 124 581 [6] (3GPP TS 24.581), clauses 6.3.2.2, 6.3.3, 6.4.2, 6.4.3, 6.4.4, 9.2.1, 6.2.1, 6.2.2, 6.2.4, 6.3.3 and 6.3.7.2.2. Unless otherwise stated, these are Rel-15 requirements. [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.1.1] "This clause describes the procedures for inviting an MCVideo user to an MCVideo session. The procedure is initiated by the controlling MCVideo function as the result of an action in clause 9.2.1.4.2 or as the result of receiving a SIP 403 (Forbidden) response as described in this clause. The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the terminating participating MCVideo function associated to the MCVideo user to be invited.; NOTE 1: How the controlling MCVideo function finds the address of the terminating MCVideo participating function is out of the scope of the current release. NOTE 2: If the terminating MCVideo user is part of a partner MCVideo system, then the public service identity can identify an entry point in the partner network that is able to identify the terminating participating MCVideo function. 3) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the MCVideo ID of the terminating user; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 288 b) the <mcvideo-calling-group-id> element set to the group identity; NOTE 3: The <mcvideo-calling-user-id> is already included in the MIME body as a result of calling clause 6.3.3.1.2 in step 1). 5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; 6) if the in-progress emergency state of the group is set to a value of "true" the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo emergency group call as specified in clause 6.3.3.1.19; b) if the received SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body with the <emergency-ind> element set to a value of "true": i) shall include in the outgoing SIP INVITE request in the application/vnd.3gpp.mcvideo-info+xml MIME body an <emergency-ind> element set to a value of "true"; and ii) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCVideo user and MCVideo group are authorised for the initiation of MCVideo emergency alerts as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcvideo-info+xml MIME body and the application/vnd.3gpp.location- info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false"; and c) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; 7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCVideo function: a) shall include a Resource-Priority header field populated with the values for an MCVideo imminent peril group call as specified in clause 6.3.3.1.19; and b) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true"; 8) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; and 9) shall send the SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response containing a Require header field with the option tag "100rel" and containing a P-Answer-State header field with the value "Unconfirmed" in response to the SIP INVITE request the controlling MCVideo function: 1) shall send a SIP PRACK request towards the MCVideo client according to 3GPP TS 24.229 [11]. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 289 Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; 2) shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 9.2.3.4; and 3) shall increment the local counter of the number of SIP 200 (OK) responses received from invited members, by 1. NOTE 4: The notifications above could be sent prior to the SIP 200 (OK) response being sent to the inviting MCVideo client. These notifications received by MCVideo clients that are group members do not mean that the group session will be successfully established. NOTE 5: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.1.2] "The controlling MCVideo function: 1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2; 2) shall set the Request-URI to the public service identity of the non-controlling MCVideo function serving the group identity of the MCVideo group owned by the partner MCVideo system; 3) shall set the P-Asserted-Identity to the public service identity of the controlling MCVideo function; 4) shall include in the application/vnd.3gpp.mcvideo-info+xml MIME body in the outgoing SIP INVITE request: a) the <mcvideo-request-uri> element set to the group identity of the MCVideo group hosted by the non- controlling MCVideo function in the partner MCVideo system; and b) the <mcvideo-calling-group-id> element set to the group identity of the group served by the controlling MCVideo function; 5) shall include the Recv-Info header field set to g.3gpp.mcvideo-transmission-request; 6) if: a) an MCVideo GKTP document exists for the group identity contained in the <mcvideo-request-uri> element in the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; and b) the MCVideo GKTP document contains a <MKFC-GKTPs> element; then: a) for each instance of <GKTP> element of the <MKFC-GKTPs> element of the MCVideo GKTP document: i) shall perform the procedure in clause 6.3.3.6.2 to re-generate an I_MESSAGE; and ii) if the procedure in clause 6.3.3.6.2 was successful, shall include the I_MESSAGE in a <GKTP> element of the <MKFC-GKTPs> element of an application/vnd.3gpp.mcvideo-info+xml MIME body included in the outgoing SIP INVITE request; 7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and 8) shall send the SIP INVITE request towards the partner MCVideo system in accordance with 3GPP TS 24.229 [11]. Upon receiving SIP 403 (Forbidden) response for the SIP INVITE request, if according to local policy and if: 1) the response contains a Warning header field with the MCVideo warning code "128"; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 290 2) the response contains a P-Refused-URI-List header field and an application/resource-lists+xml MIME body as specified in IETF RFC 5318 [28]; NOTE 1: The application/resource-lists+xml MIME body contains MCVideo IDs identifying MCVideo users in a partner MCVideo system that needs to be invited to the prearranged group call in case of group regrouping using interrogating method. Editor's Note: The above note currently isn't defined in the 23.280 and 23.281. then the controlling MCVideo function: 1) shall check if the number of members of the MCVideo group exceeds the value contained in the <on-network- max-participant-count> element of the group document as specified in 3GPP TS 24.481 [24]. If exceeded, the controlling MCVideo function shall invite only <on-network-max-participant-count> members from the application/resource-lists+xml MIME body; and NOTE 2: The <on-network-max-participant-count> element indicates the maximum number of participants allowed in the prearranged group session It is operator policy that determines which participants in the application/resource-lists+xml MIME body are invited to the group call. 2) shall invite MCVideo users as specified in this clause using the list of MCVideo IDs in URI-List. Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCVideo function: 1) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and NOTE 3: The procedures executed by the controlling MCVideo function prior to sending a response to the inviting MCVideo client are specified in clause 9.2.1.4.2. 2) if at least one of the invited MCVideo clients has subscribed to the conference package, shall subscribe to the conference event package in the non-controlling MCVideo function as specified in clause 9.2.3.4.3." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.2] "In the procedures in this clause: 1) MCVideo ID in an incoming SIP INVITE request refers to the MCVideo ID of the originating user from the <mcvideo-calling-user-id> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 2) group identity in an incoming SIP INVITE request refers to the group identity from the <mcvideo-request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the incoming SIP INVITE request; 3) MCVideo ID in an outgoing SIP INVITE request refers to the MCVideo ID of the called user in the <mcvideo- request-uri> element of the application/vnd.3gpp.mcvideo-info+xml MIME body of the outgoing SIP INVITE request; 4) indication of required group members in a SIP 183 (Session Progress) response refers to the <required> element of the application/vnd.3gpp.mcvideo-info+xml MIME body set to "true" in a SIP 183 (Session Progress) sent by the non-controlling MCVideo function of an MCVideo group; 5) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body; and 6) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body. Upon receipt of a "SIP INVITE request for controlling MCVideo function of an MCVideo group", the controlling MCVideo function: 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The controlling MCVideo function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [15] and skip the rest of the steps; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 291 NOTE 1: if the SIP INVITE request contains an emergency indication or an imminent peril indication set to a value of "true" and this is an authorised request for originating an MCVideo emergency group call as determined by clause 6.3.3.1.13.2, or for originating an MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5, the controlling MCVideo function can according to local policy choose to accept the request. 2) shall determine if the media parameters are acceptable and the MCVideo codecs are offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps; 3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if: a) an Accept-Contact header field does not include the g.3gpp.mcvideo media feature tag; or b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo"; 4) if received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17; 5) shall retrieve the necessary group document(s) from the group management server for the group identity contained in the SIP INVITE request and carry out initial processing as specified in clause 6.3.5.2; 6) if the result of the initial processing in clause 6.3.5.2 was: a) that authorization of the MCVideo ID is required at a non-controlling MCVideo function of an MCVideo group is required, perform the actions in clause 6.3.3.1.13.7 and do not continue with the rest of the steps in this clause; and b) that a SIP 3xx, 4xx, 5xx or 6xx response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group" has been sent, do not continue with the rest of the steps in this clause; 7) shall perform the actions as described in clause 6.3.3.2.2; 8) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero; 9) shall determine if an MCVideo group call for the group identity is already ongoing by determining if an MCVideo session identity has already been allocated for the group call and the MCVideo session is active; 10) if the SIP INVITE request contains an unauthorised request for an MCVideo emergency group 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 [11] and skip the rest of the steps; 11) if the SIP INVITE request contains an unauthorised request for an MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5, shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the following clarifications: a) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcvideo-info+xml MIME body as specified in clause F.1 with the <mcvideoinfo> element containing the <mcvideo-Params> element with the <imminentperil-ind> element set to a value of "false"; and b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [11] and skip the rest of the steps; 12) if a Resource-Priority header field is included in the SIP INVITE request: a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; or ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 292 b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; 13) if the MCVideo group call is not ongoing then: a) if: i) the user identified by the MCVideo ID is not affiliated to the group identity contained in the SIP INVITE request as specified in clause 6.3.6; ii) the group identity contained in the SIP INVITE request is not a constituent MCVideo group ID; iii) the received SIP INVITE request does not contain an emergency indication or imminent peril indication; or iv) the received SIP INVITE request is an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by steps clause 6.3.3.1.13.5 and is determined to not be eligible for implicit affiliation as specified in clause 8.2.2.3.6; then shall return a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4, and skip the rest of the steps below; b) if the user identified by the MCVideo ID is not authorised to initiate the prearranged group session as specified in clause 6.3.5.4, shall send a SIP 403 (Forbidden) response with the warning text set to: "119 user is not authorised to initiate the group call" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below; c) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined as determined in step 13) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; d) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; e) shall create a prearranged group session and allocate an MCVideo session identity for the prearranged group call, and shall handle timer TNG3 (group call timer) as specified in clause 6.3.3.5; f) if the group identity in the "SIP INVITE request for controlling MCVideo function of an MCVideo group" is a TGI: i) shall for each of the constituent MCVideo groups homed on the primary MCVideo system: A) if the controlling MCVideo function does not own the MCVideo group identified by the MCVideo group ID, then generate a SIP INVITE request towards the MCVideo server that owns the MCVideo group identity by following the procedures in clause 9.2.1.4.1.2; and NOTE 2: The MCVideo server that the SIP INVITE request is sent to acts as a non-controlling MCVideo function; B) if the controlling MCVideo function owns the MCVideo group identified by the MCVideo group ID then: I) determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; II) invite each group member determined in step A) above, to the group session, as specified in clause 9.2.1.4.1.1; and III) interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 293 ii) shall for each of the constituent MCVideo groups homed on the partner MCVideo system generate a SIP INVITE request for the MCVideo group identity homed on the partner MCVideo system as specified in clause 9.2.1.4.1.2; and g) if the group identity in the SIP INVITE request for controlling MCVideo function of an MCVideo group is an MCVideo group ID: i) shall determine the members to invite to the prearranged MCVideo group call as specified in clause 6.3.5.5; ii) if necessary, shall start timer TNG1 (acknowledged call setup timer) according to the conditions stated in clause 6.3.3.3; iii) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": A) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; and C) if the in-progress emergency state of the group is set to a value of "false": I) shall set the value of the in-progress emergency state of the group to "true"; and II) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; iv) if the in-progress emergency state of the group is set to a value of "false" and if the received SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function shall: A) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and B) if the in-progress imminent peril state of the group is set to a value of "false", shall set the in- progress imminent peril state of the group to a value of "true"; v) shall invite each group member determined in step 13)g)i) above, to the group session, as specified in clause 9.2.1.4.1.1; and vi) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; and 14) if the MCVideo group call is ongoing then: a) if: i) the user identified by the MCVideo ID in the SIP INVITE request is not affiliated to the group identity contained in the SIP INVITE request as specified in clause 6.3.6; ii) the group identity contained in the SIP INVITE request is not a constituent MCVideo group ID; iii) the received SIP INVITE request does not contain an emergency indication or imminent peril indication; or iv) the received SIP INVITE request is an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined clause 6.3.3.1.13.5 and is determined to not be eligible for implicit affiliation as specified in clause 8.2.2.3.6; then shall return a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4, and skip the rest of the steps below; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 294 b) if the user identified by the MCVideo ID in the SIP INVITE request is not authorised to join the prearranged group session as specified in clause 6.3.5.3, shall send a SIP 403 (Forbidden) response with the warning text set to "121 user is not allowed to join the group call" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below; c) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [11]; d) if <on-network-max-participant-count> as specified in 3GPP TS 24.481 [24] is already reached: i) if, according to local policy, the user identified by the MCVideo ID in the SIP INVITE request is deemed to have a higher priority than an existing user in the group session, may remove a participant from the session by following clause 9.2.1.4.4.3, and skip the next step; and NOTE 3: The local policy for deciding whether to admit a user to a call that has reached its maximum amount of participants can include the <user-priority> and the <participant-type> of the user as well as other information of the user from the group document as specified in 3GPP TS 24.481 [24]. The local policy decisions can also include taking into account whether the imminent-peril indicator or emergency indicator was received in the SIP INVITE request. ii) shall return a SIP 486 (Busy Here) response with the warning text set to "122 too many participants" to the originating network as specified in clause 4.4 and skip the rest of the steps; e) if the received SIP INVITE request contains an an authorised request for an MCVideo emergency group call as determined by clause 6.3.3.1.13.2 or MCVideo imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCVideo user is eligible to be implicitly affiliated with the MCVideo group as determined in step 14) a) iv) above, shall perform the implicit affiliation as specified in clause 8.2.2.3.7; f) if the received SIP INVITE request includes an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true": i) shall cache the information that this MCVideo user has initiated an MCVideo emergency call; ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCVideo emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that this MCVideo user has initiated an MCVideo emergency alert; iii) if the in-progress emergency state of the group is set to a value of "false": A) shall set the value of the in-progress emergency state of the group to "true"; B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16; and C) shall generate SIP re-INVITE requests for the MCVideo emergency group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.6; iv) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; and v) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; g) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCVideo function: i) shall cache the information that this MCVideo user has initiated an MCVideo imminent peril call; and ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 295 ii) if the in-progress imminent peril state of the group is set to a value of "false": A) shall set the in-progress imminent peril state of the group to a value of "true"; B) shall generate SIP re-INVITE requests for the MCVideo imminent peril group call to the other call participants of the MCVideo group as specified in clause 6.3.3.1.15; and C) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCVideo function shall interact with the media plane as specified in 3GPP TS 24.581 [5]; and iii) if the in-progress imminent peril state of the group is set to a value of "true": A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCVideo user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcvideo-info+xml MIME body to a value of "true"; and B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [11]; h) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.4.2; i) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; j) shall include in the SIP 200 (OK) response with the warning text set to "123 MCVideo session already exists" as specified in clause 4.4; k) if the received SIP re-INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; l) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; NOTE 4: In this case, the request was for an imminent peril call but a higher priority MCVideo emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority. m) shall interact with media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 5: Resulting media plane processing is completed before the next step is performed. n) shall send the SIP 200 (OK) response towards the inviting MCVideo client or inviting non-controlling MCVideo function according to 3GPP TS 24.229 [11]; o) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; NOTE 6: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. p) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]; q) Upon receiving a SIP ACK to the above SIP 200 (OK) response and the SIP 200 (OK) response contained a Warning header field as specified in clause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall follow the procedures in clause 6.3.3.1.18; and r) shall not continue with the rest of the clause. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 296 Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 9.2.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [30], the timer TNG1 (acknowledged call setup timer) is not running, the controlling MCVideo function supports media buffering and the SIP final response is not yet sent to the inviting MCVideo client: 1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) shall include a P-Answer-State header field with the value "Unconfirmed"; 5) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 7) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 7: Resulting user plane processing is completed before the next step is performed. 8) shall send the SIP 200 (OK) response towards the inviting MCVideo client according to 3GPP TS 24.229 [11]; 9) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo User has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 8: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 10) shall send a SIP NOTIFY request to each MCVideo client according to 3GPP TS 24.229 [11]. Upon receiving a SIP 183 (Session Progress) response for a SIP INVITE request as specified in clause 9.2.1.4.1.2 containing an indication of required group members, the timer TNG1 (acknowledged call setup timer) is running and all SIP 200 (OK) responses have been received to all SIP INVITE requests sent to MCVideo clients specified in clause 9.2.1.4.1.1, then the controlling MCVideo function shall wait until the SIP 200 (OK) response has been received to the SIP INVITE request specified in clause 9.2.1.4.1.2 before generating a SIP 200 (OK) response to the "SIP INVITE request for controlling MCVideo function of an MCVideo group". Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1 that was sent to an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24]; and 1) if the MCVideo ID in the SIP 200 (OK) response matches to the MCVideo ID in the corresponding SIP INVITE request; 2) there are no outstanding SIP 200 (OK) responses to SIP INVITE requests which were sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24]; and 3) there is no outstanding SIP 200 (OK) response to a SIP INVITE request sent in clause 9.2.1.4.1.2 where the SIP 183 (Session Progress) response contained an indication of required group members; the controlling MCVideo function: 1) shall stop timer TNG1 (acknowledged call setup timer) as described in clause 6.3.3.3; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 297 2) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps; 3) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has been exceeded the <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24]; 4) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 5) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 9: Resulting media plane processing is completed before the next step is performed. 6) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; 7) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 10: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 8) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon: 1) receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 9.2.1.4.1; 2) the timer TNG1 (acknowledged call setup timer) is not running; 3) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; 4) the controlling MCVideo function supports media buffering; and 5) the SIP final response has not yet been sent to the inviting MCVideo client; the controlling MCVideo function according to local policy: 1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2; 2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCVideo group has exceeded the <max- participant-count> members as specified in 3GPP TS 24.481 [24]; 3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; 4) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCVideo emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 5) if the received SIP INVITE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4; 6) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.3; NOTE 11: Resulting media plane processing is completed before the next step is performed. 7) shall send a SIP 200 (OK) response to the inviting MCVideo client according to 3GPP TS 24.229 [11]; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 298 8) shall generate a notification to the MCVideo clients, which have subscribed to the conference state event package that the inviting MCVideo user has joined in the MCVideo group session, as specified in clause 6.3.3.4; and NOTE 12: As a group document can potentially have a large content, the controlling MCVideo function can notify using content-indirection as defined in IETF RFC 4483 [29]. 9) shall send the SIP NOTIFY request to the MCVideo clients according to 3GPP TS 24.229 [11]. Upon expiry of timer TNG1 (acknowledged call setup timer), if there are outstanding SIP 200 (OK) responses to SIP INVITE requests sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the procedures specified in clause 6.3.3.3. If timer TNG1 (acknowledged call setup timer) is running and a final SIP 4xx, 5xx or 6xx response is received from an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [24], the controlling MCVideo function shall follow the relevant procedures specified in clause 6.3.3.3. If: 1) timer TNG1 (acknowledged call setup timer) is not running; 2) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; and 3) a final SIP 4xx, 5xx or 6xx response is received from an invited MCVideo client; then the controlling MCVideo function shall perform one of the following based on policy: 1) send the SIP final response towards the inviting MCVideo client, according to 3GPP TS 24.229 [11], if a SIP final response was received from all the other invited MCVideo clients and the SIP 200 (OK) response is not yet sent; or 2) remove the invited MCVideo client from the MCVideo Session as specified in clause 6.3.3.1.5, if a SIP final response other than 2xx or 3xx was received from all the invited MCVideo clients and the SIP 200 (OK) response is already sent. The controlling MCVideo function may invite an additional member of the prearranged MCVideo group as specified in clause 9.2.1.4.1 that has not already been invited, if the prearranged MCVideo group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [24], and all members have not yet been invited. Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCVideo client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCVideo function shall follow the procedures in clause 6.3.3.1.18." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 9.2.1.4.3] "Upon receiving a SIP BYE request the controlling MCVideo function shall follow the procedures as specified in clause 6.3.3.2.4." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.2] "This clause is referenced from other procedures. The controlling MCVideo function shall generate an initial SIP INVITE request according to 3GPP TS 24.229 [11]. The controlling MCVideo function: 1) shall include in the Contact header field an MCVideo session identity for the MCVideo session with the g.3gpp.mcvideo media feature tag, the isfocus media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" according to IETF RFC 3840 [22]; 2) shall include an Accept-Contact header field containing the g.3gpp.mcvideo media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20]; 3) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Asserted-Service-Id header field according to IETF RFC 6050 [14] in the SIP INVITE request; ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 299 4) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with parameters "require" and "explicit" according to IETF RFC 3841 [20]; 5) shall include a Referred-By header field with the public user identity of the inviting MCVideo client; 6) should include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [7]. The refresher parameter shall be omitted; 7) shall include the Supported header field set to "timer"; 8) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body, shall copy the application/vnd.3gpp.mcvideo-info+xml MIME body to the outgoing INVITE request; 9) if the received SIP INVITE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body containing an <ambient-viewing-type> element and: a) if the Priv-Answer-Mode header field specified in IETF RFC 5373 [27] was included in the received SIP INVITE request with a value of "Auto" or if no Priv-Answer-Mode header field was received in the received SIP INVITE request; or b) a Priv-Answer-Mode header field was received containing a value other than "Auto"; shall include a Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request; and 10) if the received SIP INVITE request did not contain an application/vnd.3gpp.mcvideo-info+xml MIME body containing an <ambient-viewing-type> element, shall include an unmodified Answer-Mode header field if present in the incoming SIP INVITE request." [ETSI TS 124 281 [5] (3GPP TS 24.281), clause 6.3.3.1.1] "The SDP offer is generated based on the received SDP offer. The SDP offer generated by the controlling MCVideo function: 1) when initiating a new MCVideo session the SDP offer; a) shall contain only one SDP media-level section for MCVideo video media stream as contained in the received SDP offer; and b) shall contain an SDP media-level section for one media-transmission control entity, if present in the received SDP offer; and 2) when adding a new MCVideo user to an existing MCVideo Session, the SDP offer shall contain the media stream currently used in the MCVideo session. When composing the SDP offer according to 3GPP TS 24.229 [11], the controlling MCVideo function: 1) shall replace the IP address and port number for the offered media stream in the received SDP offer with the IP address and port number of the controlling MCVideo function; 2) for the MCVideo video media stream, shall include all media-level attributes from the received SDP offer; 3) shall replace the IP address and port number for the offered media transmission control entity, if any, in the received SDP offer with the IP address and port number of the controlling MCVideo function; and 4) for the offered media transmission control entity, shall include the offered media transmission control entity 'fmtp' attributes as specified in 3GPP TS 24.581 [5] clause 14." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.2.2] "When an MCVideo call is established a new instance of the transmission control server state machine for 'general transmission control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' is added. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 300 When an MCVideo call is established a new instance of the transmission control server state machine for 'general reception control operation' is created. For each MCVideo client added to the MCVideo call, a new instance of the transmission control server state machine for 'basic reception control operation towards the transmission participant' is added. If the optional "mc_queueing" feature is supported and has been negotiated as specified in clause 14, the transmission control server could queue the implicit transmission control request for the media-transmission control entity. The original initial SIP INVITE request or SIP REFER request to establish an MCVideo chat group call or to rejoin an ongoing MCVideo call is not handled as an implicit transmission control request message by the transmission control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request. The permission to send media to the inviting MCVideo client due to implicit transmission control request is applicable to both confirmed indication and unconfirmed indication. When the first unconfirmed indication is received from the invited participating MCVideo function (see 3GPP TS 24.281 [2]) the transmission control server optionally can give an early indication to send RTP media packets, to the inviting MCVideo client. If an early indication to send RTP media packets is given to the inviting MCVideo client, the transmission participant is granted the permission to send media and the MCVideo server buffers RTP media packets received from the MCVideo client at least until the first invited MCVideo client accepts the invitation or until the RTP media packet buffer exceeds it maximum limit to store RTP media packets. If the MCVideo server does not support or does not allow media buffering then when an early indication to send RTP media packets is not given to the inviting MCVideo client, the transmission participant is granted the permission to send media when the first invited MCVideo client accepts the media. Before the transmission control server sends the first transmission control message in the MCVideo call, the transmission control server has to assign itself a SSRC identifier to be included in media transmission control messages and quality feedback messages if the MCVideo server is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3]. The transmission participant and the transmission control server can negotiate the maximum priority level that the transmission participant is permitted to request. The transmission control server can pre-empt the current sender based on the negotiated maximum priority level that the transmission participant is permitted to request and the priority level included in the Transmission Media Request message. NOTE: The maximum priority level that a transmission participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the controlling MCVideo function from the group management server as described in 3GPP TS 24.481 [12] and service configuration data retrieved by the controlling MCVideo function from the configuration management server as described in 3GPP TS 24.484 [13]. The transmission participant and the transmission control server can negotiate queueing of Transmission requests using the "mc_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the transmission control server queues the transmission control request if a Transmission Media Request message is received when another transmission participant has the transmission and the priority of the current speaker is the same or higher." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 301 When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.2] "Upon receiving a transmission control message the participating MCVideo function: 1. shall immediately forward the transmission control message to the transmission control server if the message is received from the transmission participant; 2. if an MBMS subchannel is not used for a transmission in the session the transmission control message is associated with, shall immediately forward the transmission control message to the transmission participant if the message is received from the transmission control server; and 3. if an MBMS subchannel is used for a transmission in the session the transmission control message is associated with: a. if i. the transmission control message is not a Transmission Idle message or a Media Transmission Notify message; ii. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or iii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; shall immediately forward the transmission control message to the transmission participant; and b. if i. the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report; and ii. if the transmission control message is the Transmission Idle message or the Media Transmission Notify message, shall perform actions as specified in clause 10.2. NOTE: When the Transmit Idle or Media Transmission Notify messages are discarded the messages are sent to the MCVideo clients over the MBMS subchannel allocated for the transmission as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.3] "Upon receiving RTP media packets the participating MCVideo function: 1. shall immediately forward the RTP media packet to the controlling MCVideo function if the RTP packet is from an MCVideo client; and 2. if an MBMS subchannel is not used for a transmission in the session the RTP media packets are associated with, shall immediately forward the RTP media packets to the MCVideo client if the RTP packet is from the controlling MCVideo function or the non-controlling MCVideo function. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 302 3. if an MBMS subchannel is used for a transmission in the session the RTP media packets are associated with and if RTP media packets are received from the controlling MCVideo function or the non-controlling MCVideo function: a. if i. the MCVideo client has not reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3; or ii. the MCVideo client has reported "not-listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall immediately forward the RTP media packets to the MCVideo client; and b. if the MCVideo client has reported "listening" status as specified in 3GPP TS 24.281 [2] clause 14.2.3 in the latest received MBMS bearer listening status report, shall perform actions as specified in clause 10.2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.4.4] "When the participating function receives an indication from the application and signalling plane that session release is initiated, the participating MCVideo function: 1. shall stop sending transmission control messages towards the transmission participant and the transmission control server; and 2. shall stop sending RTP media packets towards the MCVideo client and towards the controlling MCVideo function. When the participating MCVideo function receives an indication from the application and signalling plane that the session is released, the participating MCVideo function: 1. in case of a pre-established session, shall perform the actions in clause 9.3.2; and 2. in case of an on-demand session, shall release the media resources associated with the session." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 9.2.1] "The transmission control messages are coded as described in clause 9.1.2 where the transmission control message is part of the application-dependent data. For the transmission control protocol the ASCII name string is: MCVx (Mission Critical Video x) with x=0, 1 or 2 as specified in clause 9.1.2. A list of transmission control messages can be found in clause 9.2.2.1. The transmission control specific fields are specified in clause 9.2.3." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.2.1] "Based on the negotiations during the call establishment specified in 3GPP TS 24.281 [2], a new instance of the 'Transmission participant state transition diagram for basic transmission control operation', as specified in clause 6.2.4 and a new instance of the 'Transmission participant state transition diagram for basic reception control operation' as specified in clause 6.2.5, shall be created for this call. The SIP INVITE request sent by the application and signalling plane: 1. shall be regarded an implicit Transmission request when an implicit Transmission request is negotiated; and 2. shall not be regarded as an implicit Transmission request in case of a rejoin to an already on-going group call. ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 303 NOTE: The transmission participant can negotiate the use of prioritization of the Transmission Media Request message. In that case, the transmission participant can request permission to send media at a priority level that is either the same as or lower than the highest priority that was permitted to the participant in the MCVideo call initialization. If a transmission participant is authorized for pre-emptive priority in the MCVideo call it is good practise to always request permission to send RTP media packets at a priority level that is lower than pre-emptive priority unless the user explicitly requests to pre-empt the current RTP media packets sender." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.2.2] "The MCVideo call release (whether it is initiated by the transmission participant or transmission control server) is a two-step procedure. Step 1 The transmission participant stops sending transmission control and reception control messages and the MCVideo client stops sending and receiving RTP media packets. Step 2 When the application and signalling plane has determined that the MCVideo call is released, the corresponding instance of the 'Transmission participant state transition diagram for basic transmission control operation' as specified in clause 6.2.4 and the corresponding instance of the 'Transmission participant state transition diagram for basic reception control operation' as specified in clause 6.2.5 are terminated and the transmission participant releases all the used resources. The user plane can initiate the release step 1, but the application and signalling plane always initiates the release step 2." [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.2.5] "The transmission participant shall behave according to the state diagrams and the state transitions specified in this clause. Figure 6.2.5.1-1 shows the state diagram for 'Transmission participant state transition diagram for general reception control operation'. …" [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.3] "When an MCVideo client leaves an MCVideo call and the MCVideo call remains ongoing with the other MCVideo clients, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to the MCVideo client leaving the MCVideo call and .the MCVideo server discards transmission control messages and RTP media packets received from the MCVideo client leaving the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call with this transmission participant has been released, the corresponding instance of the transmission control server state machine for 'basic transmission control operation towards the transmission participant' and 'basic reception control operation towards the transmission participant' is released. When an MCVideo call is released, the transmission control server follows a two-step procedure. Step 1 The MCVideo server stops sending transmission control messages and RTP media packets to all transmission participants in the MCVideo call. Step 2 When the application and signalling plane has determined that the MCVideo call has been released, the corresponding instance of the transmission control server state machine for 'general transmission control operation' and 'general reception control operation' are also terminated, along with any 'basic transmission control operation towards the transmission participant' and any 'basic reception control operation towards the transmission participant' state machines for the transmission participants of this call. The transmission control server state machine for general transmission control operation initiates the MCVideo call release depending on the release policy specified in 3GPP TS 24.281 [2]." ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 304 [ETSI TS 124 581 [6] (3GPP TS 24.581), clause 6.3.7.2.2] "When a SIP Session is established and if the session is a normal group call session: NOTE 1: Temporary group call is not supported in this release. Normal group call contains pre-arranged group call, chat group call, broadcast group call. 1. if an MCVideo client initiate an MCVideo call, and the MCVideo call does not exist yet, the transmission control interface towards the MCVideo client in the transmission control server: a. shall initialize a general state machine as specified in clause 6.3.6.2.2; and NOTE 2: In the clause 6.3.6.2.2 the 'general reception control operation' state machine will continue with the initialization of the 'general reception control operation' state machine. b. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and 2. if the associated transmission participant attempts to initiate an already existing MCVideo call or MCVideo client rejoins an ongoing MCVideo call or if the MCVideo client is invited to the MCVideo call a if no MCVideo client has the permission to send media, the transmission control interface towards the MCVideo client in the transmission control server i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and b if other MCVideo clients have permission to send a media, the transmission control interface towards the MCVideo client in the transmission control server: i. shall enter the state 'U: not permitted to receive' as specified in the clause 6.3.7.3.2; and ii. shall send media transmission notification as specified in the clause 6.3.7.3.3. NOTE 3: The usecases, the MCVideo client initiating new call, joining ongoing call and re-joining ongoing call are applicable towards the originating MCVideo client and for other usecases it is applicable towards the terminating MCVideo client. The maximum reception priority of the transmission participant is permitted to request is negotiated in the "mc_reception_priority" fmtp attribute as specified in clause 14." |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.1.15.3 Test description | 5.1.1.15.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). 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) 305 - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are registered and authorized to use the MCVideo system. - The SS-UE1 (MCVideo client) and the SS-UE2 (MCVideo client) are affiliated to the pre-arranged group and are authorized to initiate group calls. - The IUT (MCVideo Server) is the controlling server of the pre-arranged group. 5.1.1.15.3.2 Test procedure sequence Table 5.1.1.15.3.2-1: Main Behaviour St Procedure Message Sequence TP Verdict U - S Message 1 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo E2E group call establishment' as described in Annex A, Table A.4.1.4.3-1 to establish a pre-arranged group call with implicit transmission control request according to option b.ii of note in Annex A, Table A.4.1.4.3-1, initiated by SS-UE1 (MCVideo Client)? - - 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 request SS-UE1 (MCVideo Client) media reception? - - 2 P 3 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Media Reception End Request and Response' as described in Annex A, Table A.3.10.3-1 to request end of media reception? - - 3 P 4 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1 to end the transmission of SS-UE1 (MCVideo Client)? - - 4 P 5 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-UE1 (MCVideo Client)? - - 5 P 6 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 request SS-UE1 (MCVideo Client) media reception? - - 2 P 7 Check: Does the IUT (MCVideo Server) correctly perform procedure 'MCVideo Transmission End Request - Idle and Transmission End Notify' as described in Annex A, Table A.3.8.3-1 to end the transmission of SS-UE1 (MCVideo Client), while SS-UE2 (MCVideo Client) is still permitted to receive media? - - 4 P 8 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? - - 6 P 5.1.1.15.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) 306 |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.2 Chat Group Call | 5.1.2.1 MCVideo Server - MCVideo Server / Chat Group Call / Upgrade to Emergency Group Call / Cancel Emergency State / Upgrade to Imminent Peril Group call / Cancel Imminent Peril State / Controlling server |
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.1.2.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 chat group call without implicit transmission control } then { IUT (MCVideo Server) accepts the call from initiator and sends transmission idle to SS- UE1 (MCVideo Client) } } (2) with { IUT (MCVideo Server) having established a chat group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function requests to join the ongoing chat group call without implicit transmission control, on behalf of SS-UE2 (MCVideo client) } then { IUT (MCVideo Server) accepts the call join request and sends transmission idle to SS-UE2 (MCVideo Client) } } (3) with { IUT (MCVideo Server) having established a chat group call } ensure that { when { the SS-UE1 (MCVideo Client) requests to end the transmission control } then { IUT (MCVideo Server) sends transmission control idle to SS-UE1 (MCVideo Client) and sends transmission control idle to SS-UE2 (MCVideo Client) } } (4) with { IUT (MCVideo Server) having established a chat group call } ensure that { when { the SS-UE1 (MCVideo Client) requests the transmission control } then { IUT (MCVideo Server) sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } (5) with { IUT (MCVideo Server) having established a chat group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function upgrades the call to emergency group call with implicit transmission control } then { IUT (MCVideo Server) accepts the upgrade from the initiator and updates the call for all participants and sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } (6) with { IUT (MCVideo Server) having upgraded to an emergency chat group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function requests to cancel the ongoing emergency state } then { IUT (MCVideo Server) accepts the emergency state cancellation and updates the call for all participants } } ETSI ETSI TS 104 152-1 V1.1.1 (2026-02) 307 (7) with { IUT (MCVideo Server) having established a chat group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function upgrades the call to imminent peril group call with implicit transmission control } then { IUT (MCVideo Server) accepts the upgrade from the initiator and updates the call for all participants and sends transmission granted to SS-UE1 (MCVideo Client) and sends media transmission notification to SS-UE2 (MCVideo Client) } } (8) with { IUT (MCVideo Server) having upgraded to an imminent peril chat group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function requests to cancel the ongoing imminent peril state } then { IUT (MCVideo Server) accepts the imminent peril state cancellation and updates the call for all participants } } (9) with { IUT (MCVideo Server) having established a chat group call } ensure that { when { the SS (MCVideo Server) providing the originating participating function ends the chat group 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 } } |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.