This Annex provides information about the static data needed for configuration of MC services encompassing the following category:

• Initial MC service UE configuration data (see subclause A.2).

Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MC service UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism.

The configuration data defined in TS 23.280 in Annex A.6 apply, with the following exceptions:

• DNN and the corresponding DN credentials instead of the PDN credentials shall be used, along with the S-NSSAI to be used for each MC service;
• The Default Configured slice(s) information may be pre-configured at the MC service UE and be utilized as defined in TS 23.501;
• Additional MC network slice identification information may be provided for each S-NSSAI, e.g., the corresponding network slice credentials.

The configuration data defined in TS 23.379 in Annex A.3, apply, with the following exceptions:

• "MCPTT group ID" instead of the "ProSe discovery group ID" shall be used;

The configuration data defined in TS 23.281 in Annex A.3, apply, with the following exceptions:

• "MCVideo group ID" instead of the "ProSe discovery group ID" shall be used;

The configuration data defined in TS 23.282 in Annex A.3, apply, with the following exceptions:

• "MCData group ID" instead of the "Discovery group ID" shall be used;

The configuration data defined in TS 23.379 in Annex A.4, TS 23.281 in Annex A.4, TS 23.282 in Annex A.4, apply, with the following exceptions:

• "Default PQI values" (as specified in TS 23.304) instead of "Default ProSe Per-Packet priority values" (as specified in TS 23.303) shall be used;

The configuration data defined in TS 23.379 in Annex A.5, TS 23.281 in Annex A.5, TS 23.282 in Annex A.5, apply, with the following exceptions:

• "Default PQI values" (as specified in TS 23.304) instead of "Default ProSe Per-Packet priority values" (as specified in TS 23.303) shall be used;

This Annex describes how TS 23.237 mechanisms for IMS service continuity can be used to provide service continuity between on-network MC service and UE-to-network relay MC service.

The details of MBS interfaces are specified in clause 4.7. The interaction between SIP core and 5GC is specified in TS 23.228. The procedure for service continuity from on-network MCPTT service to UE-to-network relay MCPTT service is described in Annex B of TS 23.280. As illustrated in Figure B.1-1:

• Initially UE-1 has a direct connection to the network via 5GS (on-network MCPTT service). It is registered with the SIP core and is engaged in a SIP session with the MCPTT Application Server (solid lines SIP-1 and MC[service]-1 in Figure B.1-1).
• When UE-1 realises that it is losing connection to the network, or after the connection to the network has been lost, UE-1 discovers a UE-to-network relay (UE-R) and establishes a PC5 connection with UE-R. UE-1 registers with the SIP core over the target access leg and enters UE-to-network relay MC service by transferring the media streams over the target leg (dashed lines SIP-1 and MC[service]-1 in Figure B.1-1).
• The SIP session is anchored at a Service Centralisation and Continuity Application Server (SCC AS) before and after the handover, as described in TS 23.237.