cludes proprietary hardware that is running proprietary software provided by the router vendor. The hardware and the software are tightly integrated together; you cannot use one without the other. Routers have evolved to support higher-level services such as firewall and security functions but typically these functions are limited compared to purpose-built appliances, and typically the best of breed choice for each network function does not come from the same vendor. Therefore, if the site needs additional functions such as an advanced firewall, that is provided as a separate box. The firewall will also have its own proprietary hardware and operating system, just like the router. There are many other network functions that follow the same "middle box" model including WANx, network analyzers, caching, or wireless LAN controllers to name a few. If the customer wants the best of breed for each function, they likely will be left with multiple hardware vendors with multiple proprietary network management interfaces. Also, if a customer wants to add a network function to a site, a new piece of hardware has to be purchased, configured, shipped to the site, and a truck roll to install and bring up that service. The uCPE model will fundamentally change how premise-based services are delivered. The hardware will be the open hardware platform discussed above for all customer sites. There will be different size platforms for different site types, but the architecture will be consistent. The VNF functions that run on the uCPE will be typically available in a VNF library, where the customer can decide what network functions they would like to download and run on the uCPE. Think of this like an App Store model for enterprises. All the major network hardware providers now offer their proprietary software as a software-only option that will run on x86. A good example is the Cisco Cloud Server Router (CSR), which is their traditional IOS software that can be purchased and run on an x86 platform. Vendors in the routing, security, a