Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.280  Word version:  19.3.1

Top   Top   Up   Prev   None
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.17…   10.17.3…   10.17.5…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   A…   B…   C…   E… 
E MC gateway UE routing capabilities  E.1 General  E.2 MC client IP address association  E.3 IP address association using the MC gateway UE  $ Change history 

 

E  MC gateway UE routing capabilities |R18|  p. 369

E.1  General  p. 369

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.

E.2  MC client IP address association  p. 369

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.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. E.2-1: MC client IP address relationship
Figure E.2-1: MC client IP address relationship
(⇒ copy of original 3GPP image)
Up
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.
Up

E.3  IP address association using the MC gateway UE  p. 370

If the MC client relies on IP address provided by the MC gateway UE, the MC gateway UE shall store the correlation between the non-3GPP device and the IP address (MC gateway UE IP and the local IP) used by the MC client . The procedures initiated by the MC client, i.e., SIP registration, user authentication and service authorisation use 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.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. E.3-1: non-3GPP device uses MC gateway UE's IP address
Figure E.3-1: non-3GPP device uses MC gateway UE's IP address
(⇒ copy of original 3GPP image)
Up

$  Change history  p. 371

Up   Top