A PCE-based Connectivity Provisioning Management Framework

Abstract

Many carriers and Service Providers (SPs) use different network domains. The Path Computation Element MPLS to achieve Traffic Engineering (TE) objectives, such as (PCE) architecture has been proposed by the IETF [2], based network resources optimization, support for end-to-end QoS on the idea of decoupling Path Computation from Path guarantees services, aggregated traffic measurement and fast Establishment processes, taking the former out of the routing recovery against link/node/Shared Risk Link Group (SRLG) X ,failures. The three main Traffic Engineering components of hardware, while keeping the latter under Control Plane MPLS are the routing component, responsible for the discovery responsibility. The PCE functionality is orthogonal to the of the network topology, the path computation component, forwarding capacity of the node in which it is implemented. responsible for the assignment of resources to traffic demands, Centralized, off-line route computation has been practised and the signaling component, responsible for the establishment of in transport networks since long ago. Given the network the Label Switched Paths (LSPs) along the computed path. Path Computation under QoS and administrative constraints is atopology and a staic traffic matrix a route server can compute usually performed sub-optimally in network nodes, which are manaotmal dribut resources.antheetyp ao mnewrs mainly dedicated to traffic forwarding. Off-load of this task to management procedures (either automatic and/or manual)

A Survey on the Path Computation Element (PCE) Architecture

“…Besides the aforementioned solutions, a number of works propose mixed or intermediate approaches. A combined approach is proposed in the implementation work [31], in which a strict cooperation between control plane and management plane is enforced. In particular the PCE TED entries are updated by both OSPF-TE session peering and SNMP extra monitoring information.…”