unction. The decomposition of network functions should address the following guidelines: Decompose if the functions have significantly different scaling characteristics (e.g., signal- ing VS. media functions, control VS. data plane functions, etc.) Decomposition should enable customizing a specific aspect of the network function on instantiations (e.g., the interworking function may need to be customized specific to each carrier interconnect instantiation) Decomposition should enable instantiating only the functionality that is needed for the service (e.g., if transcoding is not needed, it should not be instantiated) Deploying NFV in a cloud service platform has provided operators new opportunities to mini- mize their costs and deploy new advanced value-added services. The NFV implementation ought to be cloud-native, and not just an adaptation of software from dedicated vendor hardware to a x86- based COTS platform. A native cloud implementation ensures efficient sharing of storage and com- puting resource. To fully utilize the resource, NFV needs to be both dynamic and flexible, as well as Scalable Interoperable Reusable Distributed Maintain state in the event of a VF failure Enabled by SDN and virtualization, NFV function decomposition (disaggregation) is a key pil- lar of the new network design. One of the benefits of NFV disaggregation (i.e., decompose a NFV into small components) is to enable operators to achieve efficient capacity scaling and reusability. Especially, it allows operators to scale different components based on different load profiles. Another key defining characteristic and benefit of decomposed NFV systems is that it allows function sharing across different VNFs. The idea of breaking large applications into small components can be traced back to service- oriented architecture (SOA). We have also seen it help scale big data applications across thousands of servers with technologies such as Hadoop and Storm. The key benefit is to optimally utilize resources such as individual central processin