IP Library Granted Patent US 7,145,867
Granted Patent B2
US 7,145,867 · App. 10/114,564 · Granted Dec 5, 2006

System and method for slot deflection routing

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 7,145,867
App. No.
10/114,564
Granted
Dec 5, 2006
Kind
B2
Abstract

The present invention provides a system and method for slot deflection routing of optical data packets. The method of the present invention includes the steps of establishing a schedule pattern that includes a plurality of time slots. The schedule pattern includes at least one time slot in which an ingress edge unit can communicate with a destination egress edge unit, at least one time slot in which the ingress edge unit can communicate with a intermediate edge unit, and at least one time slot in which the intermediate edge unit can communicate with the destination egress edge unit. The present invention also includes receiving a data packet at the ingress edge unit and determining if the schedule pattern allocates sufficient bandwidth to send the data packet from the ingress edge unit to the destination egress edge unit without deflecting the data packet through an intermediate edge unit. If enough bandwidth has been allocated, the data packet can be sent to the destination edge unit from the ingress edge unit without deflection. Alternatively, if enough bandwidth has not been allocated, the data packet can be deflected to an intermediate edge unit prior to being communicated to the destination egress edge unit.

Claims (94)

1. A method for routing optical data packets comprising:

establishing a schedule pattern comprising a plurality of time slots, wherein the schedule pattern includes at least one time slot in which an ingress edge unit can communicate with a destination egress edge unit, at least one time slot in which an ingress edge unit can communicate with an intermediate edge unit, and at least one time slot in which the intermediate edge unit can communicate with the destination egress edge unit:

receiving a data packet at the ingress edge unit;

determining if the schedule pattern allocates sufficient bandwidth to communicate the data packet to the destination egress edge unit without deflection;

if sufficient bandwidth has been allocated, communicating the data packet to the destination egress edge unit; and

if sufficient bandwidth has not been allocated:

deflecting the data packet to the intermediate edge unit; and

communicating the data packet from the intermediate edge unit to the destination egress edge unit

determining the current traffic demand; and

if sufficient bandwidth has not been allocated to communicate the data packet to the destination egress edge unit without deflection under the current traffic demand, updating the schedule pattern to increase the allocated bandwidth between the ingress edge unit and the destination egress edge unit.

2. The method of claim 1 , further comprising:

predetermining a deflection route for incoming data packets arriving at the ingress edge unit based on the schedule pattern; and

deflecting the data packet based on the predetermined deflection route.

3. The method of claim 1 , wherein the step of deflecting the data packet to the intermediate edge unit further comprises deflecting the data packet to a plurality of intermediate edge units in parallel.

4. The method of claim 1 , wherein the step of deflecting the data packet to the intermediate edge unit further comprises deflecting the data packet to a plurality of intermediate edge units in series.

5. The method of claim 1 , further comprising

determining if there is a fault between the ingress edge unit and the destination egress edge unit; and

if there is a fault, deflecting the data packet to the intermediate edge unit.

6. The method of claim 5 , further comprising deriving a new schedule pattern to compensate for the fault.

7. A method for routing optical data comprising:

establishing a schedule pattern comprising a plurality of time slots, wherein the schedule pattern includes at least one time slot in which an ingress edge unit can communicate with a destination egress edge unit, at least one time slot in which the ingress edge unit can communicate with an intermediate edge unit, and at least one time slot in which the intermediate edge unit can communicate with the destination egress edge unit;

receiving a plurality of data packets bound for the same destination edge unit;

determining if the schedule pattern allocates sufficient bandwidth to communicate the plurality of data packets to the destination egress edge unit without deflection;

if sufficient bandwidth has been allocated, communicating the plurality of data packets to the destination egress edge unit; and

if sufficient bandwidth has not been allocated:

deflecting at least a portion of the plurality of data packets to the intermediate edge unit; and

communicating the at least a portion of the plurality of data packets from the intermediate edge unit to the destination egress edge unit

determining the current traffic demand, wherein the schedule pattern is based on expected traffic; and

if sufficient bandwidth has not been allocated to communicate the plurality of data packets to the destination egress edge unit without deflection under the current traffic demand, updating the schedule pattern to increase the allocated bandwidth between the ingress edge unit and the destination egress edge unit.

8. The method of claim 7 , further comprising:

predetermining a best deflection route for incoming data packets arriving at the ingress edge unit based on the schedule pattern; and

deflecting the at least a portion of the plurality of data packets based on the predetermined deflection route.

9. The method of claim 7 , wherein the step of deflecting at least a portion of the plurality of data packets further comprises deflecting the at least a portion of the plurality of data packets to a plurality of intermediate edge units in parallel.

10. The method of claim 7 , wherein the step of deflecting at least a portion of the plurality of data packets further comprises deflecting the at least a portion of the plurality of data packets to a plurality of intermediate edge units in series.

11. The method of claim 7 , further comprising:

determining if a fault exists between the ingress edge unit and the destination egress edge unit; and

if the fault exists:

deflecting the plurality of data packets to at least one intermediate edge unit; and

communicating the plurality of data packets from the at least one intermediate edge unit to the destination egress edge unit.

12. A system for routing optical data packets comprising:

a destination egress edge unit;

an intermediate edge unit;

an ingress edge unit, wherein the ingress edge unit receives an optical data packet;

a scheduler which establishes a schedule pattern, wherein the schedule pattern comprises a series of time slots and wherein the schedule pattern includes at least one time slot in which the ingress edge unit can communicate with the destination egress edge unit, at least one time slot in which the ingress edge unit can communicate with the intermediate edge unit, and at least one time slot in which the intermediate edge unit can communicate with the destination egress edge unit;

a core controller operable to:

determine if the schedule pattern allocates sufficient bandwidth for the ingress edge unit to communicate the destination egress edge unit without deflection;

if sufficient bandwidth has not been allocated, route the data packet from the ingress edge unit to the intermediate edge unit; and

route the data packet from the intermediate edge unit to the destination egress edge unit; and

an optical switch core, and wherein the core controller is further operable to:

configure the switch core so that the ingress edge unit communicates with the destination egress edge unit according to the schedule pattern;

configure the switch core so that the ingress edge unit communicates with the intermediate edge unit according to the schedule pattern; and

configure the switch core so that the intermediate edge unit communicates with the destination egress edge unit according to the switch core.

13. The system of claim 12 , wherein the core controller is further operable to:

if sufficient bandwidth has been allocated for the ingress edge unit to communicate with the destination egress edge unit without deflection, prompt the ingress edge unit to communicate the data packet to the destination egress edge unit in the at least one time slot in which the ingress edge unit can communicate with the destination egress edge unit; and

if sufficient bandwidth has not been allocated:

prompt the ingress edge unit to communicate the data packet to the intermediate edge unit in the at least one time slot in which the ingress edge unit can communicate with the intermediate edge unit; and

prompt the intermediate edge unit to communicate the data packet to the destination egress edge unit in the at least one time slot in which the intermediate edge unit can communicate with the destination egress edge unit.

14. The system of claim 12 , wherein the core controller is further operable to:

predetermine the best deflection route based on the schedule pattern; and

route the data packet to the intermediate edge unit based on the schedule pattern.

15. The system of claim 12 , further comprising a plurality of intermediate edge units and wherein the core controller is further operable to route the data packet to the plurality of intermediate edge units in parallel.

16. The system of claim 12 , further comprising a plurality of intermediate edge units and wherein the core controller is further operable to route the data packet to the plurality of intermediate edge units in series.

17. The system of claim 12 , wherein the scheduler is operable to establish the schedule pattern based on expected traffic.

18. The system of claim 16 , wherein the core controller is further operable to determine the current traffic and wherein the scheduler is further operable to update the schedule pattern based on the current traffic.

19. A system for routing optical data packets, comprising:

a destination egress edge unit;

an intermediate edge unit;

an ingress edge unit, wherein the ingress edge unit receives an optical data packet;

a scheduler which establishes a schedule pattern, wherein the schedule pattern comprises a series of time slots and wherein the schedule pattern includes at least one time slot in which the ingress edge unit can communicate with the destination egress edge unit, at least one time slot in which the ingress edge unit can communicate with the intermediate edge unit, and at least one time slot in which the intermediate edge unit can communicate with the destination egress edge unit;

a core controller operable to:

determine if the schedule pattern allocates sufficient bandwidth for the ingress edge unit to communicate the destination egress edge unit without deflection;

if sufficient bandwidth has not been allocated, route the data packet from the ingress edge unit to the intermediate edge unit; and

route the data packet from the intermediate edge unit to the destination egress edge unit; and

a plurality of intermediate edge units, wherein the core controller is further operable to route the data packet to the plurality of intermediate edge units in series and determine the current traffic, and wherein the scheduler is further operable to update the schedule pattern based on the current traffic.

20. A system for routing optical data packets comprising:

a destination egress edge unit;

an intermediate edge unit;

an ingress edge unit, wherein the ingress edge unit receives an optical data packet;

a scheduler which establishes a schedule pattern, wherein the schedule pattern comprises a series of time slots and wherein the schedule pattern includes at least one time slot in which the ingress edge unit can communicate with the destination egress edge unit, at least one time slot in which the ingress edge unit can communicate with the intermediate edge unit, and at least one time slot in which the intermediate edge unit can communicate with the destination egress edge unit;

a core controller operable to:

determine if the schedule pattern allocates sufficient bandwidth for the ingress edge unit to communicate the destination egress edge unit without deflection;

if sufficient bandwidth has not been allocated for the ingress edge unit to communicate the destination egress edge unit without deflection,

route the data packet from the ingress edge unit to the intermediate edge unit; and

route the data packet from the intermediate edge unit to the destination egress edge unit;

if sufficient bandwidth has been allocated for the ingress edge unit to communicate with the destination egress edge unit without deflection,

prompt the ingress edge unit to communicate the data packet to the destination egress edge unit in the at least one time slot in which the ingress edge unit can communicate with the destination egress edge unit; and

an optical switch core, and wherein the core controller is further operable to:

configure the switch core so that the ingress edge unit communicates with the destination egress edge unit according to the schedule pattern;

configure the switch core so that the ingress edge unit communicates with the intermediate edge unit according to the schedule pattern; and

configure the switch core so that the intermediate edge unit communicates with the destination egress edge unit according to the switch core;

wherein the core controller is further operable to:

if sufficient bandwidth has not been allocated:

prompt the ingress edge unit to communicate the data packet to the intermediate edge unit in the at least one time slot in which the ingress edge unit can communicate with the intermediate edge unit; and

prompt the intermediate edge unit to communicate the data packet to the destination egress edge unit in the at least one time slot in which the intermediate edge unit can communicate with the destination egress edge unit.

Assignments (8)
CORRECTIVE ASSIGNMENT TO CORRECT THE THE NATURE OF CONVEYANCE PREVIOUSLY RECORDED AT REEL: 056981 FRAME: 0631. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Feb 16, 2022
From: COMMWORKS SOLUTIONS, LLC
To: UNWIRED BROADBAND, INC.
Reel/Frame 059907/0563 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED AT REEL: 054443 FRAME: 0958. ASSIGNOR(S) HEREBY CONFIRMS THE LICENSE. Recorded Feb 4, 2021
From: COMMWORKS SOLUTIONS, LLC
To: UNWIRED BROADBAND, INC.
Reel/Frame 056981/0631 →
LICENSE Recorded Nov 5, 2020
From: COMMWORKS SOLUTIONS, LLC
To: UNWIRED SOLUTIONS, INC.
Reel/Frame 054443/0958 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 3, 2020
From: INTELLECTUAL VENTURES ASSETS 135 LLC
To: COMMWORKS SOLUTIONS, LLC
Reel/Frame 051463/0138 →
CONFIRMATORY ASSIGNMENT Recorded Nov 30, 2019
From: YOTTA NETWORKS, INC.
To: LIGHTHOUSE CAPITAL PARTNERS IV, L.P.
Reel/Frame 051146/0932 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 1, 2019
From: S. AQUA SEMICONDUCTOR, LLC
To: INTELLECTUAL VENTURES ASSETS 135 LLC
Reel/Frame 050886/0724 →
AFFIDAVIT OF FORECLOSURE Recorded Oct 29, 2019
From: YOTTA NETWORKS, INC
To: LIGHTHOUSE CAPITAL PARTNERS IV L.P.
Reel/Frame 050849/0829 →
MERGER Recorded Oct 23, 2015
From: YT NETWORKS CAPITAL, LLC
To: S. AQUA SEMICONDUCTOR, LLC
Reel/Frame 036872/0774 →