# US 2009/0245253 A1 · Computing Point-to-Multipoint Paths

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2009/0245253 A1
- Document ID: US20090245253A1
- Status: Published application
- Kind: A1
- Application number: 12/404,100
- Filed: 2009-03-13
- Published: 2009-10-01
- Earliest claimed: 2008-03-27
- Assignees: Futurewei Technologies, Inc.
- Inventors: Huaimo Chen; Qianglin Quintin Zhao; Hua Autumn Liu
- Web page: https://patentgrep.com/patent/US20090245253A1

## CPC

- H04L 45/42: Centralised routing
- H04L 12/18: for broadcast or conference {, e.g. multicast}
- H04L 45/02: Topology update or discovery
- H04L 45/22: {Alternate routing}
- H04L 45/28: using route fault recovery
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

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.

## Claims

### Claim 1

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.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the PCE and the PCC communicate using a request message and a reply message, a plurality of session establishment messages, or both.

### Claim 3 (depends on 2)

The apparatus of claim 2, wherein the request message comprises a source and a plurality of destinations for a new P2MP path, wherein the source is a root of the new P2MP path and the destinations are a plurality of leaves of the new P2MP path, and wherein the reply message comprises the new P2MP path.

### Claim 4 (depends on 2)

The apparatus of claim 2, wherein the request message comprises an existing P2MP path and a plurality of destination addresses as a plurality of new leaves to be added to the existing P2MP path, and wherein the reply message comprises a plurality of new branches to the leaves.

### Claim 5 (depends on 2)

The apparatus of claim 2, wherein the request message comprises a P2MP path identifier (ID) of an existing P2MP path and a plurality of destination addresses as a plurality of new leaves to be added to the existing P2MP path, and wherein the reply message comprises a plurality of new branches to the leaves and the P2MP path ID.

### Claim 6 (depends on 2)

The apparatus of claim 2, wherein the session establishment message from the PCE to the PCC comprises a plurality of capability flags, wherein one of the capability flags indicates that the PCE is configured to store a P2MP path for the PCC, wherein the session establishment message from the PCC to the PCE comprises a plurality of request flags, and wherein one of the request flags indicates that the PCC requests that the PCE store the P2MP path for the PCC.

### Claim 7 (depends on 6)

The apparatus of claim 6, wherein another session establishment message from the PCE to the PCC comprises a plurality of confirmation flags, wherein one of the confirmation flags indicates that the PCE accepts the request to store the P2MP path, and wherein the PCC records the confirmation from the PCE.

### Claim 8 (depends on 2)

The apparatus of claim 2, wherein the PCE is coupled to or comprises a P2MP path database (PDB) that stores and maintains information associated with P2MP path, a point-to-point (P2P) path or both.

### Claim 9

A network component comprising:
at least one processor configured to implement a method comprising:
obtaining a computation request for a point-to-multipoint (P2MP) path across a plurality of autonomous system (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.

### Claim 10 (depends on 9)

The network component of claim 9, wherein attempting to calculate the P2MP path comprises creating a new P2MP path, adding a path to the P2MP path, or re-optimizing the P2MP path.

### Claim 11 (depends on 9)

The network component of claim 9, wherein the computation request comprises a plurality of request messages each comprising a common request identifier (ID) and a different sub request identifier (S-ID), wherein the S-IDs distinguish the request messages from each other.

### Claim 12 (depends on 9)

The network component of claim 9, wherein the method further comprises:
obtaining a request to store or delete the P2MP path; and
transmitting a confirmation that indicates whether the P2MP path was stored, deleted, or the request was rejected.

### Claim 13 (depends on 9)

The network component of claim 9, wherein the method further comprises:
obtaining a request to delete all the P2MP paths from a path computation client (PCC); and
transmitting a confirmation that indicates whether the P2MP paths were deleted, or the request was rejected.

### Claim 14 (depends on 9)

The network component of claim 9, wherein the method further comprises exchanging information about a P2MP path computation capability during a session establishment.

### Claim 15

A method comprising: exchanging a request message and a reply message about a point-to-multipoint (P2MP) path across an autonomous system (AS) domain between a path computation client (PCC) and a path computation element (PCE).

### Claim 16 (depends on 15)

The method of claim 15, wherein the request message, the reply message, or both comprise a request/reply (RP) object that indicates a path request, a end-points object that indicates a source node and a destination node for the point-to-multipoint (P2MP) path, or both.

### Claim 17 (depends on 15)

The method of claim 15, wherein the RP object comprises a reserved field, a plurality of flags, a request identification-(ID)-number, and an optional type length value (TLV) field, wherein the flags comprise an explicit route object (ERO)-compression bit flag, a P2MP bit flag, a strict/loose bit flag, a bi-directional bit flag, a re-optimization bit flag, a plurality of priority bit flags, and remaining unused bits, and wherein the end-points object comprises a leaf type, a source address, and at least one destination address.
