{'fraction_non_alphanumeric': 0.020713463751438434, 'fraction_numerical': 0.0011507479861910242, 'mean_word_length': 5.492537313432836, '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}}
On the implementation of End-to-End Mobility Management Framework (EMF)

Traditionally the mobility problem has been solved mostly at network layer. However the End-to-End Mobility Management Framework (EMF) [1] provides the solution to this problem above the transport layer. EMF overcomes some limitations of current mobility management solutions by effectively providing mobility services such as soft handover, willful handover, location updates etc. EMF neither requires any support of additional entities in the network nor requires the changes in the current implementation of TCP. This paper describes a portable implementation design of the EMF framework along with the tradeoffs involved in implementing the framework. The results of some experiments to measure the performance of EMF are also presented that quantify the protocol and computational overheads.