Architecture for transport of multiple services in connectionless packet-based communication networks

• US 6,647,428 B1
• Filed: 05/05/2000
• Issued: 11/11/2003
• Est. Priority Date: 05/05/2000
• Status: Expired due to Term

• Current Assignee: ADTRAN Incorporated (ADTRAN Holdings, Inc.)
• Original Assignee: Luminous Networks, Inc (ADTRAN Holdings, Inc.)
• Inventors: Srinivasan, Seshadri, Choi, Inwhan, Shinde, Atul, Stillman, Robert, Lindquist, Richard, Mallick, Sohail, Watts, Warren, Fan, Jason C., Bannai, Vinay K., Barry, Charles F., Kalman, Robert F.
• Primary Examiner(s): Lim, Krisna
• Application Number:
  US09/567,555
• Time in Patent Office: 1,285 Days
• Field of Search: 709/251, 709/245, 709/236, 709/238, 370/403-406, 370/424, 370/452, 370/909, 370/253, 370/355, 370/389, 370/390
• US Class Current: 709/245
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 69/324 in the data link layer [OSI layer 2], e.g. HDLC
• CPC Class Codes: H04Q 11/0066 Provisions for optical burst or packet networks
• CPC Class Codes: H04Q 11/0071 Provisions for the electrical-optical layer interface
• CPC Class Codes: H04Q 2011/0073 Provisions for forwarding or routing, e.g. lookup tables
• CPC Class Codes: H04Q 2011/0077 Labelling aspects, e.g. multiprotocol label switching [MPLS], G-MPLS, MPAS

Abstract

An architecture for transport of multiple services in connectionless packet-based networks is described herein, along with the packet format used for data transport in this architecture. The architecture supports transport of both connectionless packetized data and framed data from synchronous leased lines. The architecture supports transparent packetization of incoming DS1 data. The architecture works for mesh architectures but is optimized for OSI Layer 1 (crossconnect) and Layer 2 (Virtual LAN, or VLAN) services and for ring topologies, since for these services in a ring no path setup is required using a label distribution protocol. In addition, it simultaneously supports OSI Layer 1, Layer 2, and Layer 3 services.

Claims

1. A method performed by a communications network, said network comprising nodes interconnected by communication links, said method comprising:

attachment of a header to an incoming message identifying information required to deliver the message to a destination;

routing of the message through the network to a destination based on information contained in the header, wherein the information comprises an address mode field, the address mode field identifying a type of addressing associated with a source and a destination address fields, wherein a first type of addressing comprises an M-bit address, wherein a second type of addressing comprises an N-bit address, N being significantly less than M.

2. The method of claim 1, wherein the header further comprises the source address field, the destination address field, and the address mode field.

3. The method of claim 2, wherein the header further comprises a version field to indicate a version of the header.

4. The method of claim 1, wherein the network comprises a ring topology, the header further comprising a tag field.

5. The method of claim 1, wherein the header further comprising:

determining whether the incoming message is protected with a cyclic redundancy check (CRC);

adding a payload frame check sequence to the incoming message if the incoming message is not protected with a CRC.

6. The method of claim 1, the header further comprising:

the source address field, the destination address field, and the address mode field;

a version field to indicate a version of the header; and

a checksum field.

7. The method of claim 6, further comprising:

determining whether the incoming message is protected with a cyclic redundancy check (CRC);

adding a payload frame check sequence to the incoming message if the incoming message is not protected with a CRC.

8. The method of claim 1, wherein the incoming message comprises synchronous framed data, plesiochronous framed data, synchronous packet-based data, asynchronous packet-based data, asynchronous connection-oriented cell-based data, or frame-based data.

9. A method performed by a communications network, said network comprising nodes interconnected by communication links, said method comprising:

receiving an incoming message at an ingress port;

attaching a header to the incoming message, the header comprising;

a field indicating which of a predetermined set of protection types is associated with the message, and

an address mode field identifying a type of addressing associated with a source and a destination address fields, wherein a first type of addressing comprises an M-bit address, wherein a second type of addressing comprises an N-bit address, N being significantly less than M; and

routing the incoming message according to the associated protection type.

10. The method of claim 9, wherein the communications network has a ring topology having first and second routing directions and wherein the protection type indicates whether the message is to be routed in the first routing direction or in the first and second routing directions.

11. The method of claim 9, wherein the protection type indicates whether the message will be re-routed in case of a device failure or a break in the network.

12. The method of claim 9, wherein the header further comprises at least one stream ID field to identify a stream associated with the message.

13. The method of claim 9, wherein the header further comprises a field representing an identity of the ingress port.

14. A method performed by a communications network, said network comprising nodes interconnected by communication links, said method comprising:

receiving a payload to be transmitted from a node via an egress port of the node;

attaching a header to the payload, the header comprising;

a field identifying the egress port through which the payload is to be transmitted, and

an address mode field identifying a type of addressing associated with a source and a destination address fields, wherein a first type of addressing comprises an M-bit address, wherein a second type of addressing comprises an N-bit address, N being significantly less than M; and

transmitting the payload through the egress port identified in the header.

15. The method of claim 14, wherein the header further comprise a field containing a stream identifier associated with the payload.