Dynamic routing of restorable QoS connections in MPLS networks

On OR-based routing approaches for the Internet

“…Four major routing principles that use mutipath routing may be identified: traffic splitting in which the traffic demand offered from origin to destination is divided by several paths, satisfying the total bandwidth requirements of the corresponding service class with obvious advantages in terms of allowing better network load distribution and improved reliability/survivability under failures; alternative routing in which one or more alternative path(s) are attempted to be used when a first choice path is unavailable for the considered node‐to‐node traffic flow due to current bandwidth occupations in the links; protection routing when a number of paths (usually node‐disjoint) have to be calculated in order to guarantee total protection of the origin‐destination traffic in certain failure scenario(s) (or at least protection of the traffic for some sub‐paths of the active path in which the traffic is originally carried) (see e.g. Kodialam and Lakshman, 2003; Agrawal et al, 2005; Rosenbaum et al, 2005); multicast routing involving the calculation of a set of paths from an originating node to multiple destination nodes (e.g. for distributive services in the Internet) which involves in OR terms, the computation of Steiner trees (see examples in Cerulli et al, 2006; Donoso et al, 2004), seeking to optimize some metric(s) such as load cost or average delay; broadcast routing involving the calculation of a set of paths from an originating node to all remaining nodes of the specified network (e.g.…”

An Adaptive Segment Repair in MPLS Protection

“…Recently, much effort has been concentrated on the designing of Multi-Protocol Label Switching (MPLS) [1] protection method [2][3][4][5][6][7][8][9][10][11]. Three main approaches exist [2]: Global Repair, Local Repair and Segment Repair.…”

“…Previous MPLS protection researches only consider one or two QoS parameters, such as resource utilization [4][5][6][7][8], packet loss [4,[6][7], recovery time [5][6]9] and request rejection ratio [10][11]. However, all QoS requirements and other aspect, like failure probability [8] are not considered at the same time.…”