 in the LINP architecture (going from physical resources toward services, Figure 3.13): Physical resources. These are all physical hardware, including physical resources man- agement and logical separation of the physical resources [26], where logical resources have the same characteristics as physical resources. Virtual resources. They abstract the given physical resources. LINPs. They are built on multiple virtual network resources. Services. In virtualized (i.e. softwarized) networks, the services can be composed of large numbers of software components, which include appropriate combinations of application programs and virtual resources on different LINPs. The service man- agement is targeted to enable the network operator, which has network virtualized resources (LINPs), to support service provisioning with the required QoS. Achieving efficient usage of LINPs or network slicing in future networks requires stan- dardized functional architecture [26]. The following four user roles are defined in the LINP functional architecture: Service developer. It designs, develops, then tests and finally carries out operation and maintenance of services based on service developer functions. Such services are developed on one or more LINPs (when more LINPs are used for a given service it is referred to as a LINP federation). LINP operator. This is a network operator which aims to design and program net- work services over different LINPs. A further LINP operator configures, manages, and terminates such network services. Network operator. It designs, deploys, and manages physical resources in the network as well as their abstracted sets within the operator's administrative domain. End-user. When an authorized user has access to a LINP which carries a given service, that user can utilize the service. The QoS in virtualized networks is becoming decoupled from the physical network infrastructure. So, one may not talk about QoS in the network but QoS on a given network slice (in a given LINP) because services are provided via dif