{'fraction_non_alphanumeric': 0.0155195681511471, 'fraction_numerical': 0.002699055330634278, 'mean_word_length': 5.475982532751091, '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}}
Network Mobility in satellite networks: architecture and the protocol

Mobility management is required to ensure the session continuity for multiple Internet Protocol‐enabled devices onboard a satellite that hands off between ground stations. Network Mobility (NEMO) can efficiently manage the mobility of multiple Internet Protocol‐enabled devices that are connected as a mobile network. However, existing mobility management solutions for satellite networks are unable to route through intermediate satellites links when a direct connection with a ground station is lost. We proposed an architecture of NEMO in satellite networks with routing through multiple satellite links using nesting, where a mobile network connects to another mobile network. However, NEMO Basic Support Protocol can be inefficient in satellite networks because of poor nesting formation leading to the routing loop, inefficient routes, and overloaded links. We extended NEMO Basic Support Protocol for the efficient use in satellite networks by augmenting it with a decision criteria for the nesting. Results verify that the extended protocol ensures loop‐free and continuous connection despite the loss of direct connection to the ground and provides an insight on how to form the nested NEMO to avoid overloading. The architecture and the extended NEMO protocol can be used for the efficient and continuous transfer of data from satellite networks to the ground. Copyright © 2011 John Wiley & Sons, Ltd.