{'fraction_non_alphanumeric': 0.01588785046728972, 'fraction_numerical': 0.0009345794392523365, 'mean_word_length': 5.226744186046512, '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}}
A comparison of rerouting methods in Network Centric Environments based on Swarm topology

Due to vast use of network centric environments in critical applications, reliability and availability are the essential characteristics of these networks. A fundamental requirement is the ability to keep the relation between the network elements even in any malfunctions in network topology. Rerouting is a suitable response to this issue. In this paper, we consider several retrieval and rerouting methods based on MPLS and normal IP in Swarm topology. Besides, the method is simulated in NS2 in order to evaluate the performance of these methods and calculate and compare their quality of service (QoS) parameters. Results depicts that in the beginning of simulation, when the network traffic load is low, the methods which reroute after a fault occurrence represent much better QoS. However, it decreases in the situation in which the traffic load increases. In addition, the methods which provide the alternate route before misconduct represent static and constant behavior.