# An Efficient 5G Data Plan Approach Based on Partially Distributed Mobility Architecture
###### Abstract
One of these algorithms is placed at the user equipment and the second algorithm in the core network. This approach aims to satisfy the users regarding security, quality of service, cost, and energy consumption. This paper [36] introduces a new core architecture based on eliminating the SGW and different interfaces such as S5/S8. Then suggest communicating the S1- and S11 to the PGW directly. In this paper [37], a new 4G architecture is proposed based on combining the PGW and SGW to functions as one network node. The proposed node is distributed in the backbone mobile network to manage mobility. Further, the MME node assigns the user equipment's IP address and acts as a mobility anchor. In [38], the IP-in-IP protocol is proposed for data transmission and mobility management in the mobile core network instead of implementing the GTP protocol. The 3 gpp technical reports and standards described four main solutions for separating the user plane (UP) and control plane (C.P.) for the EPC nodes. These solutions have their drawbacks on other entities in the core network, such as MME. Therefore, in our proposal, we are distributing the functionality of UP while keeping the C.P. intact. The UP functionality is distributed during the PDN establishment, changing the UP session identity and relocating UP functionality based on the U.E. mobility. Our proposed architecture shall eliminate the additional signaling requirements as described in [39; 40; 41]  
In terms of handover, different approaches were proposed for Ultra-dense networks (UDNs) based on the trigger time and eNB cooperation set to reduce the handover procedure time. [PERSON], [PERSON], et al. propose to use the making coordinated multipoint (CoMP) protocol to transmission approach. The solution aims to track the user movement intelligently to assigned small or microcell by gauging the dwell time. Further, the authors suggest an improved movement-aware CoMP handover called iMACH to improve the reliability. The numerical and simulation results show an out-performance regarding the handover probability, coverage, and throughput [42]. This paper [43] presents a multi-attribute mobility handover approach based on the throughput necessity and link reliability to enhance the quality of experience (QoE) and quality of service (QoS). Furthermore, to guarantee the QoS requirement, the lowest throughput is considered. The UE connects to the target cell with the highest priority, which is computed according to related weights, QoS index, and link index. The experimental results show the superiority in terms of handover delay and throughput. Therefore, we proposed an SDN-based DMM architecture for the 5G mobile core network in this research. The proposed architecture comprises a centralizing control function with SDN technology support and distributing the user data plane. This proposal aims to simplify signaling messages and eliminate the number of entities in the data path, thus, reducing the total latency. We focus on analyzing necessary data plane procedures, including initial attachment, data delivery, handover in intra-gateway and inter-gateway situations. Experiments are conducted on several scenarios using NS-3 simulation to validate the performance of the proposed architecture. Firstly, we build new network entities representing the mobile core, such as Mobile Control Entity, which combines the MME, S-GW, and P-GW, and consists of several control entities to avoid a single point of failure. A new Mobility Gateway acts also as anchor mobility inside the network and routing IP packets to the Internet. Secondly, implement control and data plane into the corresponding interface. The proposed SDN-based DMM architecture obtained better results in terms of total transmission delay, inter and intra handover delay, queuing delay, and total attachment time. The Numerical analysis and simulation results showed that the proposed SDN-based DMM architecture performance-enhanced end-to-end latency over the legacy architecture.