{'fraction_non_alphanumeric': 0.03571428571428571, 'fraction_numerical': 0.0, 'mean_word_length': 4.783068783068783, '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}}
Analysis of two-phase path management scheme for MPLS traffic engineering

Multi-Protocol Label Switching (MPLS) is suitable for implementing Traffic Engineering (TE) to achieve two goals: Quality of Service (QoS) provisioning and the efficient use of network resources. In fact, MPLS allows several detour paths to be (pre-)established for some source-destination pair as well as its primary path of minimum hops. Thus, we focus on a two-phase path management scheme using these two kinds of paths. In the first phase, each primary path is allocated to a flow on a specific source-destination pair if the path is not congested, i.e., if its utilization is less than some predetermined threshold; otherwise, as the second phase, one of the detour paths is allocated randomly if it is available. Therefore, in this paper, we analytically evaluate this path management scheme by extending the M/M/c/c queueing system and we investigate the impact of a threshold on the flow-blocking probability. Through some numerical results, we discuss the adequacy of the path management scheme for MPLS-TE.