“…7 Ericsson evolved packet gateway. http://goo.gl/tEjcWP • Use of proprietary black boxes [3] • Use of inflexible hard-state signalling protocols [49] • Use of monolithic functionalities [3] • Reconfiguration/updates available only with heavy integration within network operators [50] • Updates require replacements of existing equipment even if it is still sufficient for most purposes [50] • High CAPEX to extend the network (i.e., increasing coverage) [50], [59], [60], [61] • High CAPEX to introduce novel services [50], [59], [60], [61] • High OPEX for network management [50], [59], [60], [61] Complexity • Network entities involved in both U/C-planes [51], [52] • Use of GTP tunnels [54], [17] • Offering a converged service view [4] • Centralized U-plane (issues at the SGW and PGW) [53], [49] • Centralized C-plane (issues at the MME) [55] • High number of information related to UEs (charging, QoS, etc.) [47] • Delay susceptible of the overload at the MME, SGW and PGW [53], [49], [55] • Reduction of the overall capacity (in terms of resources to be used for data traffic) of the network [62] • High CAPEX/OPEX to scale the network [17] Centralised U/C-planes • U-plane unaware of session profiles and characteristics [47] • C-plane signalling is growing 50% faster than data traffic [55] • U-plane connectivity may involve a waste of network resources even if UEs do not have data to send [62] • Reduction of the overall capacity (in terms of resources to be used for data traffic) of the network...…”