{'fraction_non_alphanumeric': 0.032716927453769556, 'fraction_numerical': 0.0021337126600284497, 'mean_word_length': 5.090909090909091, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Programmable Mobile Core Network

Mobile operators are recently forced to provide higher bandwidth connections to mobile users in order to manage fierce competition. As a result, operators started deployment of Long Term Evolution (LTE)/ Evolved Packet core (EPC) network. However, current LTE/EPC architecture, functions and protocols are not optimized. For example, tunneling protocol in data plane induces protocol overhead. In general, this network is not programmable, therefore, it hinders the innovation around the mobile network. This paper presents an initial architecture for mobile core network, called Programmable Mobile Core Network. The programmable data plane for the LTE/EPC network, starting from eNode B (eNB) to the external network gateway. This data plane consists of OpenFlow-enabled switches and routers, with a centralized OpenFlow Controller that cooperates with the MME. Each eNB is connected to OpenFlow-enabled switch. When a flow is started from/to User Equipment (UE), OpenFlow controller assigns necessary routes in the programmable data plane. The feasibility of programmable data plane of the LTE/EPC is verified by exploring three different procedures: 1) initially UE is attached to the network, 2) UE is moving across eNBs while data connection is active, and 3) UE is in an idle mode, when there is downink data. Finally, we present our test bed and an initial result.