Content for TS 23.289 Word version: 19.4.0

0… 4… 4.7… 4.7.4… 4.8… 5… 5.4… 6… 6.3… 6.3.2… 7… 7.2.4… 7.3… 7.3.3… 7.3.3.2… 7.3.3.4… 7.3.3.5… 7.3.3.7… 7.3.3.8… 7.3.3.9… 7.3.3.10… 7.3.3.11… 7.3.3.12… 7.3.3.13… 7.4… 7.5… 7.6… A…

6.3.2 Resource management of MC service sessions by SIP core and MC service server 6.3.2.1 General 6.3.2.2 Resource Management of MC service sessions by SIP core 6.3.2.3 Management of MC service sessions by MC service server 6.4 Involved business relationships 6.4.1 General 6.4.2 Public network and non-public network utilization 6.4.3 NTN utilization 6.5 Off-network architectural model 6.5.1 Off-network architectural model diagram 6.5.2 UE 3 6.5.3 UE 4 6.5.4 Offline common services server
...

6.3.2 Resource management of MC service sessions by SIP core and MC service server p. 39

6.3.2.1 General p. 39

This clause describes two different scenarios in which resource management of MC service sessions is performed via the Rx reference point, or N5 reference point, or N33 reference point as defined in TS 23.501, TS 23.502 and TS 23.503, by either the SIP core or the MC service server with the 5GS (PCF).

These may provide suitable models for each of the scenarios listed in clause 6.3.1. However, there is no direct correlation of any of the scenarios described in this clause to each of the scenarios described in clause 6.3.1.

6.3.2.2 Resource Management of MC service sessions by SIP core p. 39

In the scenario shown in Figure 6.3.2.2-1, resource management of MC service sessions is performed by the SIP core.

Reproduction of 3GPP TS 23.289, Fig. 6.3.2.2-1: Resource management of MC service sessions by SIP core

Figure 6.3.2.2-1: Resource management of MC service sessions by SIP core

6.3.2.3 Management of MC service sessions by MC service server p. 39

In the scenario shown in Figure 6.3.2.3-1, resource management of MC service sessions is performed by the MC service server.

Reproduction of 3GPP TS 23.289, Fig. 6.3.2.3-1: Resource management of MC service sessions by MC service server

Figure 6.3.2.3-1: Resource management of MC service sessions by MC service server

6.4 Involved business relationships p. 40

6.4.1 General p. 40

For the relationship between the MC service provider, the MC service organization and the MC service user clause 6 of TS 23.280 applies.

6.4.2 Public network and non-public network utilization p. 40

For the relationship between MC service provider and the utilization of public networks and/or non-public networks the following service arrangements apply:

A home public network operator or a home non-public network operator can have service arrangements with multiple MC service providers.
A MC service provider can have service arrangements with multiple home public network operators and/or home non-public network operators.
As part of the service arrangement between the MC service provider and the home public network operator/home non-public network operator, the corresponding 5GS user profile can be provided which allows the MC service UEs to register to the home public network operator/home non-public network operator.
The home PLMN operator can have PLMN roaming agreements with multiple visited PLMN operators and the visited PLMN operator can have PLMN roaming agreements with multiple home PLMN operators.

Reproduction of 3GPP TS 23.289, Fig. 6.4.2-1: Business relationships for MC services

Figure 6.4.2-1: Business relationships for MC services

6.4.3 NTN utilization |R19| p. 41

Figure 6.4.3-1 shows required additional relationship related to MC services over NTN.

Reproduction of 3GPP TS 23.289, Fig. 6.4.3-1: Business relationships for MC services for NTN operator

Figure 6.4.3-1: Business relationships for MC services for NTN operator

The home PLMN operator and the MC service provider can have satellite service agreement with multiple satellite service providers to offer MC services over NTN, e.g., for areas with no terrestrial network coverage. The satellite providers guarantee a certain level of transmission performance via considering the type of satellite constellation and their characteristics (e.g., altitude).

For the relationship between the MC service provider, the home PLMN operator and satellite service provider, the following service agreements apply:

The home PLMN operator and MC service provider can have satellite service agreements with multiple satellite service provider.
The home PLMN operator and visited PLMN operator can have satellite service agreements with multiple satellite service provider as part of their roaming agreements.

6.5 Off-network architectural model |R18| p. 41

6.5.1 Off-network architectural model diagram p. 41

Figure 6.5.1-1 shows the off-network architectural model for the MC system solution for 5G inter-UE communication, where no relay function is used.

Reproduction of 3GPP TS 23.289, Fig. 6.5.1-1: Off-network architectural model for 5G inter-UE communication where no relay function is used

Figure 6.5.1-1: Off-network architectural model for 5G inter-UE communication where no relay function is used

Figure 6.5.1-2 shows the off-network architectural model for the MC system solution for configuration management and group management. The description in clause 9.3.1 of TS 23.280 applies.

Reproduction of 3GPP TS 23.289, Fig. 6.5.1-2: Off-network architectural model for configuration management and group management

Figure 6.5.1-2: Off-network architectural model for configuration management and group management

6.5.2 UE 3 p. 42

The UE 3 is a UE using 5G ProSe and supporting application(s) related to off-network MC service, and it is composed of the corresponding MC service functional entities described in clause 5.

6.5.3 UE 4 p. 42

The UE 4 represents one or more UEs with the same functionality as UE 3.

6.5.4 Offline common services server p. 42

The offline common services server supports configuration applications related to MC service, and it is composed of the corresponding MC service functional entities described in clause 5.