 of the func- tions of the existing 4G mobile core (e.g., authentication, charging, QoS, policy, mobility, handover, etc.), and will support emerging 5G use cases, while achieving synergies with wireline access core functions. These functions, however, will be performed in the NGxC environment and may not necessarily follow the 4G architectural concepts. In addition, NGxC is envisioned to perform newer functions to meet the requirements of the use cases outlined in the 4G America's 5G White Paper [6]. Some of these new functions are as follows: Access agnostic Mobility as a service (MaaS) Separation of control and user plane The architectural concepts for the NGxC are influenced by the NGMN white paper [7]. The table below gives a summary of key evolutionary changes from today's (4G LTE) architecture to NGxC. Nodal boundaries Composition and decomposition of VNFs Hierarchical network deployment Flexible network deployment Nodes with combined control and user plane Complete separation of control and user planes for functions independent scaling and distribution. Standard interface between control and user plane. Decomposition of bundled user plane functions Multiple control and user plane nodes A unified control plane VNF and a unified user plane VNF. Software based on cloud architecture with scale-out characteristics One mobile packet core (MPC) to suit all use Instantiation of an NGxC optimized for various cases use cases Mobility for every mobility subscriber Designed specifically for 3GPP defined RAN. Designed for a multiaccess environment from the Interworking with non-3GPP access (e.g., beginning. Plug and play for non-3GPP access types Wi-Fi) as an afterthought Manual service creation Automatic service creation in concert with ONAP In the area of cloud solutions, an area of research is use of container technologies and cloud native solutions for VNFs that are part of a service. The Cloud Native Computing Foundation (CNCF) views container technology as a key enabler for making network functions more applicat