PCE P2MP Path Computation Across AS Domains

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mechanisms for computing Point-to-Multipoint (P2MP) paths across multiple Autonomous System (AS) domains in MPLS and GMPLS networks are under development, lacking effective methods for path computation and communication between Path Computation Clients (PCC) and Path Computation Elements (PCE).

Innovation Solution

The implementation of a PCE configured to communicate with a PCC to compute and manage P2MP paths across AS domains, exchanging request and reply messages to generate and transmit computed paths or failure reasons, utilizing session establishment messages to declare path computation capabilities and manage path operations such as adding, deleting, or re-optimizing paths.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If P2MP path computation is implemented across multiple AS domains using PCC and PCE, then network flexibility and reliability are improved, but the complexity of path computation and communication protocols increases

Engineering Contradiction:
Improvenetwork reliabilityVSAvoidpath computation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The path computation function is segmented and distributed across multiple AS domains, with each domain having its own PCE that computes paths independently. This segmentation allows complex multi-domain path computation to be broken down into simpler single-domain computations, improving overall reliability while managing complexity through distributed processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A centralized PCE acts as an intermediary between PCCs in different AS domains, coordinating path computation requests and responses. This intermediary mechanism simplifies the communication protocol by centralizing the coordination function, allowing individual PCCs to focus on local path computation without managing complex multi-domain interactions directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If path computation requests and replies are exchanged between PCC and PCE, then path establishment is facilitated, but communication overhead and processing time increase

Engineering Contradiction:
Improvepath establishmentVSAvoidcomputation time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

Path computation capabilities and negotiation are performed in advance during session establishment between PCC and PCE. By pre-establishing the computational framework and capabilities, the actual path computation requests can be processed more quickly, reducing the time overhead during operational path establishment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The PCE provides feedback responses to PCC path computation requests, enabling iterative optimization. This feedback mechanism allows the PCC to adjust path requirements based on computation results, facilitating easier path establishment through coordinated iteration while managing total computation time through efficient feedback loops.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8953597B2Computing point-to-multipoint paths
Publication Date: 2015.02.10 FUTUREWEI TECHNOLOGIES INC
  • US8953597B2 patent drawing
  • US8953597B2 patent drawing
  • US8953597B2 patent drawing

AI summary

An apparatus comprising a path computation element (PCE) configured to communicate with a path computation client (PCC) and compute a point-to-multipoint (P2MP) path across an autonomous system (AS) domain. Also included is a network component comprising at least one processor configured to implement a method comprising obtaining a computation request for a P2MP path across a plurality of AS domains, attempting to calculate the P2MP path across the AS domains, thereby generating a computed path or a failure reason, and transmitting a reply comprising the computed path or an indication of the failure reason. Included is a method comprising exchanging a request message and a reply message about a P2MP path across an AS domain between a PCC and a PCE.