le flexibility for specialized treatment of user flows. Although the architecture does provide support for QoS, other sorts of treatment involving mid- dleboxes, for example, specialized deep packet inspection or data 5 SDN and NFV in 5G caching for transcoding or augmented reality applications, is difficult to support with the current PC architecture. Almost all such applica- tions require the packet flows to exit through the GGSN, thereby being detunneled from GTP, and be processed within the wired network. 5.3.2 Virtualization and Cloud-Assisted PC The basic concept of bringing virtualization and cloud to PC is to split the control plane and the data plane for the PC network entities and to implement the control plane by deploying the EPC control plane entities in a cloud computing facility, while the data plane is implemented by a distributed collection of OpenFlow switches. The OpenFlow protocol is used to connect the two, with enhancements to support GTP routing, while the PC already has a split between the data and control plane, in the sense that the HLR, HSS, AuC are pure control plane. The EPC architecture assumes a standard routed IP network for transport on top of which the mobile network entities and protocols are implemented. The split proposed in this document is instead at the level of IP rout- ing and MAC switching. Instead of using L2 routing and L3 internal gateway protocols to distribute IP routing and managing Ethernet and IP routing as a collection of distributed control entities, this docu- ment proposes centralizing L2 and L3 routing management in a cloud facility and controlling the routing from the cloud using OpenFlow. The standard 3G PC control plane entities, SGSN, GGSN, HSS, HLR, AuC, VLR, EIR, SMS-IWMSC, SMS-GMSC, and SLF are deployed in the cloud. The data plane consists of standard OpenFlow switches with enhancements as needed for routing GTP packets, rather than IP routers and Ethernet switches. At a minimum, the data plane travers- ing through the SGSN and GGSN and the packet ro