es steer GTP flows to particular locations. The operator, in this case, peers its PC with two other fixed operators. Routing through each peering point is handled by the respective GGSN1-D and GGSN2-D. The bottom two lines with arrow shows traffic from a UE that needs to be routed to either one or another peering operator. The flow rules and actions to distinguish which peering point the traffic should traverse are installed in the OpenFlow switches and gateways by the OpenFlow controller. The OpenFlow controller calculates these flow rules and actions based on the routing tables it maintains for outside traffic, and the source and destination of the packets, as well as by any specialized forwarding treatment required for DSCP marked packets. The top line with arrow shows an example of a UE that is obtaining content from an external source. The content is originally not formu- lated for the UE's screen, SO the OpenFlow controller has installed flow controller Cloud manager Transcoding (((C))) appliance (((c))) (((c)))) (((C))) Figure 5.15 Virtualized PC and SDN routing. 5.4 Virtualized Customer Premises Equipment rules and actions on the GGSN1, SGSN-D, and the OpenFlow switches to route the flow through a transcoding application in the cloud. The transcoding application reformats the content SO that it will fit on the UE's screen. MSC requests the specialized treatment at the time the UE sets up its session with the external content source via the IP mul- timedia subsystem (IMS) or another signaling protocol. Virtualized Customer Premises Equipment Virtualizing and cloudifying the customer premises equipment (CPE) of enterprises and SMBs is an important NFV use-case. In practice, most existing vCPE PoCs and deployments are overlaid on a distributed physical network topology with relatively static and inefficient resource placement. The current focus has been on connectivity and functionality, rather than performance and agility. The static resource placement and cumbersome deployment are a result of the need to p