Content for TS 23.280 Word version: 18.6.0
1…
5…
5.2.8…
6
7…
7.3.2
7.4…
7.4.3…
7.5…
8…
9…
9.2.2…
9.2.2.2…
9.3…
10…
10.1.2…
10.1.3…
10.1.4.3…
10.1.4.5…
10.1.5…
10.1.6…
10.2…
10.2.3…
10.2.4.2…
10.2.4.3…
10.2.5…
10.2.7…
10.3…
10.6…
10.7…
10.7.3…
10.7.3.4…
10.7.3.7…
10.7.3.7.3
10.7.3.8…
10.7.3.10…
10.8…
10.8.4…
10.8.5…
10.9…
10.9.3…
10.9.3.5…
10.9.3.8…
10.9.3.9…
10.9.3.9.3…
10.9.3.9.4…
10.9.3.10…
10.9.3.10.4…
10.9.3.10.6…
10.10…
10.10.1.2.3…
10.10.2…
10.10.3…
10.10.3.3…
10.10.3.4…
10.11…
10.11.5…
10.12…
10.13…
10.13.3…
10.13.7…
10.13.10…
10.14…
10.15…
10.15.3…
10.15.3.3…
10.15.3.4…
10.16…
10.16.3…
11…
11.3…
11.5…
11.5.2…
11.5.3…
11.5.3.3.2A…
11.5.4…
A…
B…
C…
11.3 Using identities behind the MC gateway UE
11.3.1 General
11.3.2 When using separate IMS subscriptions
11.3.3 When sharing MC gateway UE's IMS subscription
11.4 MC gateway UE routing capabilities
11.4.1 General
11.4.2 MC client IP address association
11.4.3 IP address association using the MC gateway UE
...
...
11.3 Using identities behind the MC gateway UE p. 309
11.3.1 General p. 309
The MC gateway UE enables access to the MC system for MC service clients either hosted on the MC gateway UE or hosted on non-3GPP devices using non-3GPP connectivity with the MC gateway UE. Simultaneous sharing of an MC gateway UE by multiple MC service clients requires a unique relationship between the MC service identities used by the MC service clients with corresponding media streams passing the MC gateway UE towards the MC system sharing 3GPP connectivity of the MC gateway UE.
An MC service user behind the MC gateway UE has no 3GPP transport access credentials (i.e., no UICC), whereas the MC system relies on private user identity associated with public user identities (i.e., IMPU/IMPI) needed for authentication purposes. Moreover, the one-to-one correspondence between MC service ID and IMPUs enables routing of signalling traffic between the MC service server and the MC service client.
The use of the various mission critical user identities is determined by clause 8 of the present document.
11.3.2 When using separate IMS subscriptions p. 309
If the MC service clients are hosted by non-3GPP devices or the MC service clients are hosted by the MC gateway UE, an MC service user corresponding to an MC client uses a dedicated IMS/SIP subscription without any relation to the MC gateway UE subscription.
Figure 11.3.2-1 depicts the use of the IMS Credential (IMC) application in accordance with TS 23.228.
The MC service user profiles are independent of the MC gateway MC service user profile.
11.3.3 When sharing MC gateway UE's IMS subscription p. 309
For the case of non-3GPP devices which are unable to host an MC service client, the MC gateway UE forwards the media from/ to the non-3GPP devices behind the MC gateway UE. As there are no MC service clients hosted by the non-3GPP devices, they rely on credentials at the MC gateway UE to access MC services.
The MC service clients, instantiated at the MC gateway UE on behalf of the non-3GPP devices which cannot host an MC service client, rely on MC service IDs provided by the MC gateway UE. In this case, the MC service clients instantiated at the MC gateway UE share the credentials from the IMS subscription of the MC gateway UE, as shown in Figure 11.3.3-1. The number of MC service clients at the MC gateway UE, which are instantiated on behalf on the non-3GPP devices which cannot host an MC service client, is determined by the number of subscribed MC service IDs that are associated with the IMS subscription of the MC gateway UE.
11.4 MC gateway UE routing capabilities p. 310
11.4.1 General p. 310
The use of the MC gateway UE requires the support of an IP network behind the MC gateway UE, that a range of IP addresses are reachable over a single MC gateway UE. That enables the forwarding of signalling information and media plane between non-3GPP devices and MC server by the MC gateway UE.
11.4.2 MC client IP address association p. 310
The use of a unique IP address by the MC clients shall be ensured for the period of association of the MC clients via the MC gateway UE with the IMS/SIP core and the MC server. Each MC gateway UE requires a unique IP address range for their MC client association which is known by the MC service environment and a correlation between the MC client's IP address and the MC gateway UE's IP address exists.
Framed routing in accordance with RFC 2865, RFC 3162, TS 23.501 shall be used to enable the support of an IP network behind the MC gateway UE, such that a range of IP addresses is reachable over a single 3GPP transport session. It allows the routing of packets to IP addresses that do not belong to the PDN/PDU session of the MC gateway UE.
11.4.3 IP address association using the MC gateway UE p. 310
If the MC client relies on IP address provided by the MC gateway UE, the MC gateway UE shall store the correlation between the GW MC service ID and the IP address (MC gateway UE IP and the local IP) used by the MC client once it performs the connection authorisation to the MC service server (see clause 11.5.1 and clause 11.5.2). Subsequent procedures initiated by the MC client, i.e. SIP registration, user authentication and service authorisation uses the MC gateway UE's IP address.
The MC gateway UE assigns the local IPs from address pool which it maintains to the individual MC clients. Managing the local IP addresses, re-using the local IP address, and how the traffic is routed between the MC clients and the network is left for implementation.
