5.1 IP version issues

23.2213GPPArchitectural requirementsRelease 17TS

The EPS/UMTS/GSM architecture shall support IPv4 / IPv6 based on the statements below.

– IP transport between network elements of the IP Connectivity services (between RNC, SGSN, GGSN, eNodeB, MME, S-GW, and P-GW) and IP transport for the CS Domain: both IPv4 and IPv6 are options for IP Connectivity.

– For UEs used for Machine-Type Communications (MTC) IPv6 addressing as described in TS 23.401 [27] and TS 23.060 [2] should be the primary mechanism for IP addressing. IPv4 based addressing is considered a transition solution and is deprecated for MTC used over 3GPP accesses.

For implementation guidelines related to transition and other aspects of IPv4 address usage see Annex B.

– IM CN subsystem elements (UE to CSCF and the other elements e.g. MRF):

– The architecture should make optimum use of IPv6.

– 3GPP specifications design the IM CN subsystem elements and interfaces to support both IPv4 and IPv6. In the case the UE supports IPv4, the guidelines and recommendations in TR 23.981 [26] should be followed.

– The UE may support IPv4 only, IPv6 only or both for the connection to the IM CN subsystem. In the case the UE supports IPv4, the guidelines and recommendations in TR 23.981 [26] should be followed.

– According to the procedures defined in TS 23.060 [2] and/or TS 23.401 [27], when a UE is assigned an IPv6 prefix, it can change the global IPv6 address it is currently using via the mechanism defined in RFC 4941 [17a], or similar means.

– Access to existing data services (Intranet, Internet,…):

– The UE can access IPv4 and IPv6 based services.