Virtual burst-switching networks

• US 7,397,792 B1
• Filed: 10/09/2003
• Issued: 07/08/2008
• Est. Priority Date: 10/09/2003
• Status: Expired due to Fees

• Current Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Jamoussi, Bilel N., Beshai, Maged E.
• Primary Examiner(s): Kizou, Hassan
• Assistant Examiner(s): O CONNOR, BRIAN T
• Application Number:
  US10/682,467
• Time in Patent Office: 1,734 Days
• Field of Search: 370/352, 370/355, 370/360, 370/389, 370/390, 370/400, 370/401, 370/403, 370/404, 370/391, 370/477, 398/45, 398/47, 398/48, 398/51, 398/52, 398/54, 398/50, 398/59
• US Class Current: 370/355
• CPC Class Codes: H04L 12/56 Packet switching systems
• CPC Class Codes: H04L 45/122 by minimising distances, e.g. by selecting a route with minimum of number of hops
• CPC Class Codes: H04L 45/124 using a combination of metrics
• CPC Class Codes: H04L 45/20 Hop count for routing purposes, e.g. TTL
• CPC Class Codes: H04L 45/302 Route determination based on requested QoS
• CPC Class Codes: H04L 45/40 Wormhole routing
• CPC Class Codes: H04L 45/62 Wavelength based optical switching H04Q11/0062
• CPC Class Codes: H04Q 11/0066 Provisions for optical burst or packet networks
• CPC Class Codes: H04Q 2011/0045 Synchronisation
• CPC Class Codes: H04Q 2011/0064 Arbitration, scheduling or medium access control aspects

Abstract

A time-shared network comprising edge nodes and optical core nodes may be dynamically divided into several embedded networks, each of which covering selected edge nodes. At least one of the edge nodes may host an embedded-network controller operable to form multiple-source flow-rate allocation requests each of the requests specifying flow-rate allocations to a plurality of paths from several source nodes to several sink nodes. A core node may also host an embedded-network controller or several embedded-network controllers. The time-shared network may use both time-division multiplexing and burst switching.

Claims

1. An edge node comprising:

a plurality of input ports including ingress ports for receiving data packets from subtending data sources, and inbound ports for receiving data bursts from external nodes;

a plurality of output ports including egress ports for transmitting data packets to subtending data sinks and outbound ports for transmitting data bursts, each data burst comprising at least one data packet, to external nodes;

an edge controller in communication with said input ports and output ports;

an input control port for transmitting control signals from said ingress ports and inbound ports to said edge controller; and

an output control port for transmitting control signals from said edge controller to said outbound ports and egress ports;

wherein at least one outbound port has a bimodal burst-formation device operable to compute burst-descriptors and flow-rate-allocation requirements for data bursts;

wherein said at least one outbound port transmits said burst descriptors and said flow-rate-allocation requirements to an external node;

wherein at least one inbound port receives from said external node burst-transfer schedules for waiting bursts and burst-transfer permits for forthcoming bursts;

and wherein said edge node forms multiple-source flow-rate-allocation requests each request specifying directed pairs of edge nodes, and a flow-rate for each of said pairs.

2. The edge node of claim 1 wherein at least one of said outbound ports transmits to an external controller at least one of a burst transfer request, a single-source flow-rate-allocation request, and multiple-source flow-rate-allocation requests.

3. The edge node of claim 1 wherein at least one of said outbound ports includes a timing circuit operable to time-lock to an external timing circuit.

4. The edge node of claim 1 wherein said burst-formation device interleaving interleaves variable-size data bursts and regular time slots in a time frame.

5. A core node interconnecting a plurality of source edge nodes and sink edge nodes, said core node comprising:

input ports for receiving optical signals;

output ports for transmitting optical signals;

a core controller including a burst-descriptor generator, and

a burst scheduler;

wherein said core controller

receives multiple-source connection requests each specifying at least two source edge nodes, and for each of the at least two source edge nodes specifying;

at least one sink edge node; and

a corresponding capacity allocation

receives burst-admission requests and single-source flow-rate-allocation requests from at least one of said input ports;

parses each of said multiple-source flow-rate-allocation requests to produce multiple single-source flow-rate-allocation requests;

directs single-source flow-rate-allocation requests to said burst-descriptor generator to produce a nominal burst size and a nominal inter-burst time-interval corresponding to each flow-rate allocation; and

directs said burst-admission requests and said burst descriptors to said burst scheduler;

wherein each of said burst-admission requests includes;

a request identifier;

an identifier of a requesting edge node;

a number χ

>

0 of destinations for which burst-scheduling is requested;

multiple-destination burst-description records, one for each of said χ

destinations, each record including;

a cyclic burst number relevant to said requesting edge node;

an identifier of a sink edge-node to which a corresponding burst is destined; and

a size of said corresponding burst.

6. A core node interconnecting a plurality of source edge nodes and sink edge nodes, said core node comprising:

input ports for receiving optical signals;

output ports for transmitting optical signals;

a core controller including a burst-descriptor generator, and

a burst scheduler;

wherein said core controller;

receives multiple-source connection requests each specifying at least two source edge nodes, and for each of the at least two source edge nodes specifying;

at least one sink edge node; and

a corresponding capacity allocation;

receives burst-admission requests and single-source flow-rate-allocation requests from at least one of said input ports;

parses each of said multiple-source flow-rate-allocation requests to produce multiple single-source flow-rate-allocation requests;

directs single-source flow-rate-allocation requests to said burst-descriptor generator to produce a nominal burst size and a nominal inter-burst time-interval corresponding to each flow-rate allocation; and

directs said burst-admission requests and said burst descriptors to said burst scheduler;

and

wherein said burst-descriptor generator determines burst-sizes and inter-burst intervals so that, for each specified flow-rate, the specified flow-rate multiplied by the time interval between any two successive burst transmission instants equals the size of a burst eligible for transmission at the second of said two successive burst transmission instants.

8. The core node of claim 6 wherein each of said multiple-source flow-rate-allocation requests includes:

a request identifier;

an identifier of a reporting edge node;

a number ψ

of source nodes for which flow-rate allocations are requested;

ψ

super-records, each super record including;

an identifier of a corresponding source node to said super record;

a number κ

of destination sink nodes for which flow-rate allocations from said corresponding source node are requested;

κ

records each record including an identifier of a sink edge-node to which burst-transfer permits are requested from said corresponding source node and a required flow-rate expressed in a prescribed unit.

9. The core node of claim 8 wherein said burst scheduler further includes means for performing temporal matching among said input ports and said output ports.

10. The core node of claim 9 wherein said burst scheduler further interleaves contiguous intervals in a time frame so that successive intervals contain variable-size data bursts and regular time slots.

7. The core node of 6 wherein each of said single-source flow-rate-allocation requests includes:

a request identifier;

an identifier of a requesting edge node;

a number κ

>

0 of destinations for which burst-transfer permits are requested;

multiple-destination burst-description records, one for each of said K destination, each record including;

an identifier of a sink edge-node to which a burst is destined; and

a required flow-rate.

11. A network comprising:

core nodes, each core node having a core controller;

edge nodes having links to said core nodes, each edge node having an edge controller, wherein at least one edge controller;

forms multiple-source flow-rate allocation requests, each specifying flow-rate allocations from at least one edge node to at least one other edge node and

directs said multiple-source flow-rate allocation requests to at least one core node;

a burst-transfer regulator in said at least one core node, the burst transfer regulator generates burst-transfer permits to comply with a flow-rate constraint;

wherein a subset of said edge nodes forms an embedded network and each edge node in said subset communicates with a controller of said embedded-network.

12. The network of claim 11 wherein said embedded-network controller modifies said flow-rate allocation requests according to traffic data it receives from at least one of said edge nodes.