 all the impacted elements and what is required as the entry level for the end user IPv6 service. User Equipment IPv6 has a significant impact on the UE on multiple layers. At a high level the following has to be verified for IPv6 support: Deploying IPv6 in 3GPP Networks Rf/Ga/Bp/Gy O(F)CS NodeB ((q)) Operator services eNodeB Internet ((q)) S1-MME Corporate services SAE Gateway Transport Legend: O(F)CS Online/offline Charging System NMS Network Management System PCRF Policy and Charging Rules Function MSC Mobile Switching Center SAE System Architecture Evolution Figure 4.7 3G-GPRS and EPS networking elements affected by the IPv6 user plane service. 1. The radio modem and its firmware has to support IPv6. It is common practice not to implement every feature, even those mandatory for a specific 3GPP release, if the customer has not specifically requested for it. IPv6 and IPv4v6 PDN Type has been such for a long time. 2. The UE TCP/IP stack has to support the required IPv6 standards [33]. 3. If the UE implements any kind of connection manager, it has to be IPv6 aware, for instance, to be able to request PDN Type IPv6 for IPv6 connectivity. 4. The Application Programming Interfaces (APIs) and possible middleware have to support the new IP version, IPv6. 5. The applications have to support IPv6, or in the best case the application should not need to care about IP version at all. Assuming that the APIs and middleware already provide applications interfaces that are IP version agnostic, then there is no need to port the application over to IPv6 (except when the application has to be IP-aware). 3GPP has traditionally divided UEs into two main categories depending on the integration level of the IP stack and the radio modem functions. A UE typically means a mobile phone that is a tightly integrated device, where the separation of the modem and the rest of the host, including the IP stack, is in practice undefined. In a standards space, the interface between the modem and the host is an ATtention (AT)-command [34] and a PP