IP Library Granted Patent US 10,862,795
Granted Patent B2
US 10,862,795 · App. 16/242,707 · Granted Dec 8, 2020

Provisioning recovery paths in a mesh network

Inventors: Sanjay Gera (Plano, TX); Fredrick Gruman (Plano, TX); David Traylor (Allen, TX); Cong Deng (Plano, TX); Abinder Dhillon (Allen, TX); Catherine Yuan (Plano, TX); Jun Chen (Plano, TX)
Assignee: Fujitsu Limited
H04L45/28H04L41/0806H04L45/22H04L45/245H04Q11/0062H04Q2011/0081H04W84/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,862,795
App. No.
16/242,707
Granted
Dec 8, 2020
Kind
B2
Abstract

A system and method for of pre-provisioning recovery paths in a mesh network including creating i) a working path between a head end NE and a tail end NE of the mesh network and ii) a recovery path between the head end NE and the tail end NE, wherein the working path and the recovery path include one or more intermediate NEs; provisioning the working path in an activated state, including establishing cross connects of each of the NEs of the working path; provisioning the recovery path in a pending state, including establishing cross connects of each of the NEs of the recovery path; after provisioning the recovery path, detecting a failure along the working path, and in response, allocating and reserving link resources along the recovery path; and activating, by the NEs along the recovery path, cross connects of the recovery path into respective hardware associated with the NEs.

Claims (42)

1. A computer-implemented method of pre-provisioning recovery paths in a mesh network, the method comprising:

creating, by a controller computing module, i) a working path between a head end network element (NE) and a tail end NE of the mesh network and ii) a recovery path between the head end NE and the tail end NE, wherein the working path and the recovery path include one or more intermediate NEs;

provisioning, by the controller computing module, the working path in an activated state, including establishing cross connects of each of the NEs of the working path;

provisioning, by the controller computing module, the recovery path in a pending state, including establishing cross connects of each of the NEs of the recovery path;

configuring, by the controller computing module, a pool of link resources for each link between the NEs;

after provisioning the recovery path, detecting, by the head end NE, a failure along the working path;

in response to detecting the failure along the working path, allocating and reserving, by the head end NE, link resources along the recovery path based on the pool of link resources for each link between the NEs of the recovery path, wherein allocating and reserving the link resources along the recovery path further includes:

transmitting, by the head end NE, an activation message on an outgoing link of the cross connect to a particular intermediate NE along the recovery path, the activation message including proposed link resources;

receiving, by the particular intermediate NE, the activation message, and in response, determining an availability of the proposed link resources;

transmitting, by the particular intermediate node, the activation message to the tail end NE;

receiving, by the tail end NE, the activation message, and in response, providing, to the particular intermediate node, an activation success message;

receiving, by the particular intermediate node, the activation success message, and in response, providing the activation success message to the head end NE; and

receiving, by the head end NE, the activation success message; and

activating, by the NEs along the recovery path, cross connects of the recovery path into respective hardware associated with the NEs, wherein the activating is independent of the controller computing module interaction.

2. The computer-implemented method of claim 1 , further comprising:

creating, by the controller computing module and using the pool of link resources, multiple recovery paths between the head end NE and the tail end NE.

3. The computer-implemented method of claim 2 , wherein assigning the pool of link resources further comprises oversubscribing the pool of link resources based on a network failure analysis.

4. The computer-implemented method of claim 1 , in response to establishing the cross connects of each of the NEs of the working path, activating, by each of the NEs along the working path, cross connects of the working path into respective hardware associated with the NEs.

5. The computer-implemented method of claim 1 , in response to establishing the cross connects of each of the NEs of the recovery path, storing, by each of the NEs along the recovery path, data indicating the cross connects into memory associated with the NEs.

6. The computer-implemented of claim 1 , further comprising, activating, by the NEs along the recovery path, the cross connects of the recovery path into respective hardware associated with the NEs.

7. A system for pre-provisioning recovery paths in a mesh network, the system comprising:

a controller computing module configured to:

create i) a working path between a head end network element (NE) and a tail end network element of the mesh network and ii) a recovery path between the head end NE and the tail end NE, wherein the working path and the recovery path include one or more intermediate NEs;

provision the working path in an activated state, including establishing cross connects of each of the NEs of the working path;

provision the recovery path in a pending state, including establishing cross connects of each of the NEs of the recovery path;

configure a pool of link resources for each link between the NEs;

the head end NE configured to:

after provisioning the recovery path, detect a failure along the working path;

in response to detecting the failure along the working path, allocating and reserving link resources along the recovery path based on the pool of link resources for each link between the NEs of the recovery path, wherein allocating and reserving the link resources along the recovery path further includes:

transmitting, by the head end NE, an activation message on an outgoing link of the cross connect to a particular intermediate NE along the recovery path, the activation message including proposed link resources;

receiving, by the particular intermediate NE, the activation message, and in response, determining an availability of the proposed link resources;

transmitting, by the particular intermediate node, the activation message to the tail end NE;

receiving, by the tail end NE, the activation message, and in response, providing, to the particular intermediate node, an activation success message;

receiving, by the particular intermediate node, the activation success message, and in response, providing the activation success message to the head end NE; and

receiving, by the head end NE, the activation success message; and

wherein each of the NEs along the recovery path activate the cross connects of the recovery path into respective hardware associated with the NEs, wherein the activating is independent of the controller computing module interaction.

8. The system of claim 7 , wherein the controller computing module is further configured to:

create, using the pool of link resources, multiple recovery paths between the head end NE and the tail end NE.

9. The system of claim 8 , wherein assigning the pool of link resources further comprises oversubscribing the pool of link resources based on a network failure analysis.

10. The system of claim 7 , in response to establishing the cross connects of each of the NEs of the working path, activating, by each of the NEs along the working path, cross connects of the working path into respective hardware associated with the NEs.

11. The system of claim 7 , in response to establishing the cross connects of each of the NEs of the recovery path, storing, by each of the NEs along the recovery path, data indicating the cross connects into memory associated with the NEs.

12. The system of claim 7 , further comprising, activating, by the NEs along the recovery path, the cross connects of the recovery path into respective hardware associated with the NEs.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 13, 2025
From: FUJITSU LIMITED
To: 1FINITY INC.
Reel/Frame 072436/0269 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 22, 2019
From: FUJITSU NETWORK COMMUNICATIONS, INC.
To: FUJITSU LIMITED
Reel/Frame 050129/0757 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 6, 2019
From: GERA, SANJAY; GRUMAN, FREDRICK; TRAYLOR, DAVID; DENG, CONG; DHILLON, ABINDER; YUAN, CATHERINE; CHEN, JUN
To: FUJITSU NETWORK COMMUNICATIONS, INC.
Reel/Frame 048265/0269 →
Continuity (1)
Related Publication 20200220806A1 · Jul 9, 2020