{'fraction_non_alphanumeric': 0.026411657559198543, 'fraction_numerical': 0.00546448087431694, 'mean_word_length': 5.038461538461538, '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}}
Simultaneous mobility management in the HIP-based M2M overlay network

The HIP-Based M2M Overlay Network (HBMON) is a virtual, self-organized and secure M2M network built on the top of Internet, composed of scattered mobile devices. A fundamental requirements of this overlay network is to ensure session survivability upon end-host movement. The Host Identity Protocol (HIP) provides a regular mobility support in our M2M Overlay network. However, HIP is not able to handle the simultaneous mobility case, where both communicating end-points simultaneously acquires a new topologically correct IP address. We propose in this paper a novel solution to manage the simultaneous mobility (also known as double jump) of M2M devices within our overlay. For this purpose we enhance the HIP rendez-vous server in order to fully manage the double jump case. We analytically evaluate the signaling cost of our solution. Then, we implement our double jump solution within the OMNeT++ network simulator. Finally, we evaluate the application recovery time of an M2M device experiencing a double jump situation.