# An Efficient 5G Data Plan Approach Based on Partially Distributed Mobility Architecture
## 2 Proposed 5G Network Architecture  
The proposed 5G Architecture is illustrated in Figure 2; to satisfy the demand of the partially distributed concept, the control protocols running on S-GW (SGW-C) and P-GW (PGW-C) to MME will be removed [44]. The SGW-C, PGW-C, and MME combined in one entity, called Mobile Control Entity (MCE). MCE focuses on both management and control EPC core. The functionalities of the centralized control plane and distributed data plane are detailed below.  
MCE is the central control unit that triggers a control signaling message and responds to the corresponding functions accordingly. It is responsible for U.E. authentication and authorization, tracking U.E. location, Gateway selection, and bearer control. Additionally, MCE is establishing a data-plane session by assigning the tunnel parameters such as Tunnel Endpoint Identifier (TEID), Quality Class Identifier (QCI), or Guaranteed Bit Rate (GBR) for a dedicated bearer. Besides, U.E. IP allocation function and data forwarding rules are also implemented.  
The Software-Defined Networking technology [45] is realized to reach the separating control and data plane. In order to avoid a single point of failure, MCE should be divided into several Control Entity (C.E.); each C.E. manages an area covered by a group of E-UTRAN and Gateway. Thus, the U.E. IP address is unchanged during mobility in the same C.E. domain. However, when U.E. moves to a new C.E. domain, the new C.E. will assign a new IP address, the management of IP addresses for the DMM concept is presented in [21].  
In a centralized LTE architecture, the Mobility Management Entity (MME) is responsible for tracking area updates TAU and paging procedures. With the massive increase in U.E. equipment and the envisioned IoT deployment, the signaling generated from TAU and paging procedure leads to a high volume of signaling traffic which hinders the performance of MME. Therefore, we propose a distributed data plane based on a non-anchor concept that relies on a more significant number of the gateway. Thus, the packet can be routed flexibly to the closest node, which results in reduced latency. Our proposal includes only One M-GW in charge of anchor mobility inside the core network and routing IP packets to the Internet. C.E. will allocate the M-GW depending on the distance from M-GW to U.E.'s current attached location. M-GW's role is to receive data plan routing rules from C.E. and then connect to the corresponding nodes. Furthermore, the gateway should be handled the data plane filtering and classification responsible for distinguishing traffic based on user profile and policy for uplink and downlink. The GTP tunneling protocol is kept the same as described in LTE Core networks. In this work, we keep the C.P centralized to mimic the SDN architecture without changing the whole network structure or adding new hardware devices to satisfy the SDN architecture. Further, the number of the C.P will be increased and distributed to keep function as mobility anchor to support the data routing and distributed data plane.  
The proposed architecture comprises a separated control plane and user data; this architecture will provide the operators with an efficient and intelligent network to solve the 5G problems. Decoupling the control plane and user plane will affect the hardware infrastructure by combining the S-GW and P-GW, which will significantly reduce the cost of deployment and development.  
Figure 2: Proposed partially distributed packet core for 5G network.