An interconnect network for operation within a communication node

<u>Technical Field</u>

0001The invention relates generally to communication nodes, and more particularly to an interconnect network for operation within a communication node.

<u>Background of the Invention</u>

0002Communication nodes, which act as junction points for communication signals transferred between a plurality of sources, are required to handle a variety of popular communication protocols, such as Integrated Services Digital Network (ISDN) protocol, Asynchronous Transfer Mode (ATM), and Internet Protocol (IP). ISDN, an early attempt at a multi-service architecture (i.e., an architecture capable of handling a variety of communication encapsulations), which is based on the telephone hierarchy, apportions bandwidth in 64 kilobits per second (Kbps) circuits. With local area networks (LANs) operating at 10 megabits per second (Mbps), ISDN has proved too slow. ATM is a packet switching protocol that was conceived as a transport mechanism for broadband ISDN. ATM transfers information in fixed-length packets called cells. The cells travel over virtual connections (VCs) between communication nodes that are established prior to each communication session. The combination of fixed cell formats and VCs renders ATM a faster alternative to ISDN. Additionally, ATM handles bursts of data traffic more efficiently than time division multiplexing (TDM) and provides high-quality voice and video support.

0003The popularity of the World Wide Web (WWW) has encouraged the use of IP. As a result, low-cost, distance-insensitive IP-based transport has become an attractive alternative to leased lines and frame relay (FR). Additionally, Internet Service Providers (ISPs) have become serious contenders for enterprise traffic.

0004Unfortunately, all of the information transfer protocols have drawbacks. Specifically, ISDN provides a relatively low-speed access solution. ATM supports frame relay, virtual private networks (VPNs), circuit emulation, private branch exchange (PBX) interconnects and quality of service (QoS), but does not mesh easily with existing data protocols. IP supports applications such as Internet Access and VPNs, for which cost connectivity is important. However, IP has yet to demonstrate industrial-strength reliability. As a result, full service providers find it necessary to maintain parallel switching networks. Because such parallel networks require maintenance and service of a variety of devices such as, voice switches, frame relay switches, ATM switches, routers, add/drop multiplexers, and digital cross-connects, they have a high associated capital equipment cost.

0005Conventional communication nodes also have a variety of drawbacks. For example, conventional communication nodes fail to provide sufficient ease of scalability. Typically, conventional switching nodes provide a switching/routing network having a fixed bandwidth. However, as enterprises grow, their needs also grow.

0006But, the fixed bandwidth switching routing network of conventional technology requires enterprises to predict such growth and purchase systems having sufficiently large bandwidth up front; thereby compounding the challenge of maintaining parallel networks. Another drawback of conventional systems is reliability. Because conventional systems fail to provide a single switch/routing network that can operate on a variety of protocols, today's Giga Points-of-Presence (GigaPoPs) and Access PoPs are a complex and expensive aggregation of core routers conducting smaller Access PoPs to the core transport capacity. These structures are fragile, with frequent service outages due to performance limitations and equipment failures. Enterprises cannot afford to be exposed to significant down time due to failures or updates associated with conventional technology.

0007Because the switching/routing networks of conventional systems are typically designed to operate under the constraints of a particular protocol, they lack the flexibility to adapt to emerging technologies, employing new communication protocols. As discussed above, different protocols provide different QoS features. Thus, another drawback of a network operating under the constraints of a single protocol is that a service provider cannot offer varying grades of service to users having differing priority requirements; thus causing service providers to forego a potentially significant source of revenue.

0008<patcit id="pcit0001" dnum="US5740156A"><text>US5,740,156</text></patcit> discloses an interconnect network suitable for operation within a communication node with a number of interconnect modules, each having transfer elements suitable for transferring information between a plurality of I/O channels and a second module located proximate to the first interconnect modules and having coupling means for electrically coupling to said I/O channels.

0009Accordingly, it is an object of the invention to provide an interconnect network that enables a multi-service communication node to handle a variety of communication protocols, without requiring the maintenance of costly parallel networks.

0010It is a further object of the invention to provide an interconnect network that enables a communication node to adapt to communication protocols employed by emerging technologies.

0011Another object of the invention is to provide a scalable interconnect network enabling bandwidth scaling of a communication node to fit the needs of providers having varying bandwidth requirements.

0012An additional object of the invention is to provide a fault-tolerant interconnect network capable of repair and update, without causing down-time or compromising operation of the communication node.

0013These and other objects of the invention will be apparent with respect to the following description of the invention.

<u>Summary of the Invention</u>

0014The invention is directed to communication nodes. More particularly, it is directed to interconnect networks in communication nodes. According to one embodiment of the invention, a communication node includes interconnect networks that enable the node to transfer a variety of communication protocols. According to a further embodiment, an interconnect network according to the invention enables a communication node to handle ATM and IP Packet-over-SONET protocols with the same hardware. An interconnect network according to an additional embodiment of the invention also enables a communication node to provide Frame Relay Data Terminal Equipment (DTE) and Multiprotocol Label Switching(MPLS) functionality. An interconnect network according to another embodiment of the invention enables a communication node to act as both a native ATM switch and a native IP router, operating at line speeds up to at least as high as 2.488 Gps (OC48c/STM16c).

0015According to additional features, the invention can provide improved reliability. By way of example, according to one embodiment, the invention provides Automatic Protection Switching (APS), wherein Open Systems Interconnection (OSI) Layer 2 and Layer 3 information is mirrored to provide rapid APS switchover. Additionally, system modules can be hot-swappable, and designed so that single component failures do not lead to total node failure.

0016According to another embodiment, the communication node is packaged in a scalable set of modules. OC48 line cards and Gigabit Ethernet modules populate a local communication interface module including a local interconnect network. An optional front end access module provides fan out to OC12/STM4, OC3/STM1, DS3, or E3 interfaces, and an optional expanded interconnect module, sometimes referred to as a hyperconnect fabric, allows dynamic bandwidth expansion of the communication node to include up to eight interconnected local interconnect modules, thereby providing 160 Gbs of essentially non-blocking bandwidth.

0017Yet another embodiment of the invention enables service providers to offer enterprises differing grades or quality of service (QoS).

0018Briefly described, an interconnect network according to one embodiment of the invention is incorporated in a communication node having a local communication interface, an associated local interconnect network, and scaling elements. The local communication interface includes a plurality of external communication channels for coupling information into and out of the node and a plurality of internal communication channels for transferring information within the node. Each external communication channel couples to an internal communication channel. The local interconnect network has local transfer elements for directing information between the internal communication channels, and consequently between the external communication channels. The scaling elements enable dynamically scaling the node to include additional local communication interfaces having additional associated local interconnect networks, such that information can be transferred between the local communication interfaces. According to a further feature, as the node expands to include additional local communication interfaces and local interconnect networks, the communication node, optionally, can transfer information between any of the internal communication channels, and thus any of the external communication channels, of the local communication interfaces.

0019Since an enhanced feature of the invention is dynamic bandwidth scalability, according to further embodiment, the communication node provides an additional local communication interface and an additional local interconnect network; and the scaling elements include an expanded interconnect network. The additional local communication interface has an additional plurality of external communication channels for coupling information in and out of the node, and an additional plurality of internal communication channels for transferring information within the node. The internal and external communication channels of the additional local communication interface couple to each other. The additional local interconnect network includes additional local transfer elements for directing information between the additional plurality of internal communication channels. The local interconnect network and the additional local interconnect network both include non-local transfer elements for directing information between the internal communication channels and the expanded interconnect network. The expanded interconnect network includes expanded transfer elements for directing information between the local interconnect networks, such that information, optionally, can be transferred between any of the internal communication channels of the local communication interfaces.

0020In another embodiment, the invention includes up to eight local communication interfaces, with associated local interconnect networks. According to the dynamic bandwidth scalability feature of the invention, the expanded interconnect network remains unchanged, regardless of the number of local communication interfaces, and provides the ability to transfer information between the internal communication channels. Such an embodiment provides an ease of bandwidth scalability absent from prior art technology. In a further embodiment, the communication node can be scaled to change the number of local communication interfaces, while the node is operating transferring information. In this way, a communication node, incorporating an interconnect network according to one embodiment of the invention, can more easily meet a service provider's varying bandwidth needs.

0021As mentioned above, the invention may provide enhanced QoS features. To provide such features, an interconnect network according to one embodiment of the invention can monitor the availability of communication channels. More particularly, the local interconnect network can include a plurality of transceivers for transferring information between the local transfer elements and the internal communication channels. Each transceiver couples to an associated internal communication channel, and has a corresponding availability status indicative of an availability of that communication channel for transferring information. The local interconnect network may also include a plurality of memory storage queues, having associated ones of the transceivers, and including memory for storing information to be transferred by an associated transceiver. The interconnect networks may further include control elements for setting the status corresponding to a particular internal communication channel to indicate unavailability for transferring information, in response to an associated memory queue reaching a selectable content level. In this way, the communication node lowers the likelihood of losing information or blocking transfer due to overloading a particular channel. Additionally, according to a further embodiment, the information coupled into the communication node is assigned a particular priority, and the interconnect networks optionally includes control elements for setting the status corresponding to a particular channel to indicate availability for receiving information having a particular priority, such as high, medium or low, in response to an associated memory queue reaching a selectable content level.

0022According to a related embodiment, the interconnect networks provides a back pressure signal to the internal communication channels, wherein the back pressure signal contains the availability status for each of the internal communication channels. A further enhancement of this feature utilizes communication bits, initially reserved for a destination address or handle, associated with a particular internal communication channel, to transfer the back pressure / availability status from a local interconnect network to an associated local communication interface.

0023According to another embodiment, the invention provides enhanced error correction. As a result the local interconnect network includes elements for generating a redundant version of information transferred from the local interconnect network to the local communication interface. If error detection elements detect an anomaly in transferred information, error correction elements can recover an error-free version of information from the redundant version. According to a further embodiment, the communication node includes control elements for deactivating those elements, be they line cards or interconnect elements, causing the detected anomalies. According to a related embodiment, the communication node provides improved fault-tolerance by deactivating failed line cards or interconnect elements, without compromising the speed with which information is transferred through the node. Additionally, to provide reduced down-time, the communication node generally, and the interconnects specifically, may also include circuit protection elements for enabling the hot replacement of failed components, while the communication node continues to transfer information.

0024In a related embodiment, the interconnect networks transfer information internally as information cells, wherein each cell includes groups of information words, and each group of information words is transferred by way of a different internal communication channel. The local interconnect network generates the redundant version by performing a bit-by-bit "exclusive or" operation on pairs of groups of information words, prior to the pair being transferred to the local communication interface. The local interconnect network also transfers the "exclusive or" version of the pair to the local communication interface. In response to a detected anomaly in either member of the pair, the local communication interface can reconstruct an error-free version of the anomalous member by performing an "exclusive or" operation between the non-anomalous member and the "exclusive or" version of the transferred pair.

0025One way to enhance the non-blocking feature of the invention and thus, the speed with which information can be transferred through the interconnect networks, is to avoid the need for re-ordering groups of information words into a complete cell, subsequent to transfer through an interconnect network. According to one embodiment, the invention employs "clumping" to avoid re-ordering and thus, enhance transfer speed. More specifically, the interconnect networks can include elements for "clumping" or combining a plurality of information cells, and for transferring those clumped cells substantially simultaneously. In a further enhancement, the interconnect networks also include elements for appending "dummy" cells to fill in a partial clump prior to the clump being transferred.

0026In a related embodiment, an interconnect network according to the invention implements the clumping feature by employing storage queues associated with the transceivers. The storage queues intermediately store groups of information words to be transferred. The interconnect networks can further include detection elements for detecting when groups of words of a plurality of information cells to be included in a clump are stored in a queue, and transfer elements for substantially simultaneously transferring the clumped information cells by coupling the groups of words to transceivers.

0027As the communication node expands to include additional local communication interfaces and associated local interconnect networks, it becomes increasingly important for the expanded interconnect network to select an efficient path through which information passes, thereby avoiding unnecessary delays. Accordingly, in a further embodiment, the invention provides a substantially non-blocking feature. According to the non-blocking feature, the expanded interconnect network can include a forwarding array for storing data indicative of an unblocked local path through the expanded interconnect network. The expanded interconnect network can use at least a portion of the destination address of a group of words of an information cell as a pointer into the forwarding array to select an unblocked path. In a further embodiment, the expanded interconnect network employs a plurality of forwarding arrays, each storing data indicative of a segment of an unblocked path through the expanded interconnect network. Further, the expanded interconnect network can use successive portions of the destination address as pointers into each of the forwarding arrays to select each segment of an unblocked path.

0028According to a further embodiment, the transfer elements of the local interconnect network and the transfer elements of the expanded interconnect network are essentially identical, and therefore, interchangeable. In such an embodiment, the transfer elements can include a mode selection feature for selecting whether the element is to be used in a local mode or in an expanded mode. Such a feature provides substantial cost savings over prior art systems.

0029In further aspects, the invention includes methods corresponding to the above described apparatus.

<u>Brief Description of the Drawings</u>

0030The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. However, the invention, both as to organization and method of practice, together with further objects and advantages thereof, may best be understood by reference to the following illustrative description taken in conjunction with the accompanying drawings in which like numerals refer to like elements, and <ul id="ul0001" list-style="none"><li><figref idref="f0001">FIGURE 1</figref> depicts a plurality of communication networks interfacing through a communication node employing interconnection networks according to the invention;</li><li><figref idref="f0002">FIGURE 2</figref> is block diagram of a communication node of the type depicted in <figref idref="f0001">FIGURE 1</figref> and incorporating interconnect networks according to the invention;</li><li><figref idref="f0003">FIGURE 3</figref> is a more detailed interconnection diagram of an exemplary local line card module and local interconnect module of the type depicted in <figref idref="f0002">FIGURE 2</figref>;</li><li><figref idref="f0004">FIGURE 4</figref> is a table illustrative of the interconnections between a typical line card module and an interconnect module of the types depicted in <figref idref="f0002">FIGURES 2</figref> and <figref idref="f0003">3</figref>;</li><li><figref idref="f0005">FIGURE 5</figref> is a more detailed block diagram showing interconnections between an exemplary local interconnect module and an expanded interconnect module of the types depicted in <figref idref="f0002">FIGURE 2</figref>;</li><li><figref idref="f0006">FIGURE 6</figref> is a table detailing the communication channel connections between an exemplary local interconnect module and the expanded interconnect module;</li><li><figref idref="f0007">FIGURE 7</figref> is a table further specifying the connection of communication channels between potential local interconnect modules and the expanded interconnect module;</li><li><figref idref="f0008">FIGURE 8</figref> is a functional block diagram of a local interconnect logical plane of the type depicted in <figref idref="f0003">FIGURE 3</figref>;</li><li><figref idref="f0009">FIGURES 9A and 9B</figref> are conceptual illustrations of high- and low-priority queues;</li><li><figref idref="f0010">FIGURES 10A</figref> and <figref idref="f0011">10B</figref> are flow-charts depicting the operation of the queues of <figref idref="f0009">FIGURES 9A and 9B</figref>; and</li><li><figref idref="f0012">FIGURE 11</figref> is functional block diagram of an expanded interconnect logical plane of the type depicted in <figref idref="f0005">FIGURE 5</figref>.</li></ul>

<u>Description of Illustrated Embodiments</u>

0031As briefly described above, the invention is directed to an interconnection network in a communication node. Communication nodes are junctions for transferring communication signals between a plurality of sources. As such, communication nodes may be required to interface with systems employing a variety of communication protocols and operating at differing information transfer speeds. Prior art systems typically require maintenance of a plurality of networks, each being capable of interfacing with a particular type of source. In contrast, a communication node, embodying features of an illustrative embodiment of the invention, can process information entering the node at a variety of speeds and formatted pursuant to a plurality of protocols. By way of example, information can enter and leave the communication node at OC48, OC12/STM4, OC3/STM1, DS3 and E3 speeds. Additionally, information can enter and leave the node in IP- or ATM-based formats.

0032Another important feature of the invention is dynamic bandwidth scalability. A communication node employing interconnection networks according to an illustrative embodiment of the invention, employs a modular design. The modular design enables a service provider to change the number of communication channels by adding or subtracting physical proximately located modules to or from the communication node. According to a preferred embodiment, the modules include a plurality of I/O interfaces coupled to an associated interconnection network. In a further embodiment of the invention, the communication node employs a two-level interconnection network modularity; a local level and an expanded level. More particularly, a plurality of local interconnection network modules, preferably proximately located with respect to each other, couple to an expanded interconnection network, also preferably located proximate to the local interconnection modules. By changing the number of local interconnection network modules that are "plugged-in" to the expanded interconnection module, a service provider can change the bandwidth of the communication node. Moreover, according to a further embodiment, a service provider can connect and unconnect local interconnect modules while the communication node is operating transferring information, thus, providing dynamic bandwidth scalability.

0033<figref idref="f0001">FIGURE 1</figref> illustrates a typical deployment of a communication node 100 employing interconnection networks according to the invention. As shown, the communication node 100 can support, among other systems, SONET rings 10, WWW server farms 20, dial up IP systems 30, IP over CATV/xDSL systems 40, IP over FR networks 50, multi-service ATM networks 60, ATM transports 70, and internet WDM systems 80. Multi-service ATM access 60 can include CBR circuits 61, voice over ATM circuits 62, internet access 63, FR over ATM data 64, and LANs 65.

0034<figref idref="f0002">FIGURE 2</figref> shows a block diagram of a communication node 100 incorporating interconnect networks according to an illustrative embodiment of the invention. The communication node 100 employs a two-level interconnect architecture. Accordingly, the node 100 includes one or more local line card modules 102-116, each having first-level associated local interconnect modules 118-132. In the case where the node 100 includes more than one local line card modules, the communication node 100 further includes a second-level expanded interconnect module 134, sometimes referred to as a hyperconnect fabric. The illustrated expanded interconnect module 134 includes three expanded interconnect boards 136-140. The boards are printed circuit boards holding integrated circuits and other components. According to one embodiment, the local line card modules 102-116 are essentially identical to each other. Similarly, the local interconnect modules 118-132 are also essentially identical to each other. Accordingly, for the most part, the following description focuses on an exemplary local line card module 102 and an exemplary local interconnect module 118; that description being equally applicable to the remaining local line card modules 104-116, and the remaining local interconnect modules 120-132.

0035The local line card module 102 transfers information into and out of the communication node 100, by way of a plurality of I/O interfaces. Those I/O interfaces can be, for example, IP or SONET/SDH ports that accept an OC48 data stream. For grooming to lower-speed interfaces, optional access modules 162-180 can be employed to provide OC12/STM4, OC3/STM1, DS3 and E3 ports. Access module 162 multiplexes input data streams into an OC48/STM16 uplink to local line card module 102. Line card module 102 couples information to an associated local interconnect module 118 by way of a plurality of Gigabit Ethernet connections 142. The local interconnect module 118 transfers information between the I/O channels of local line card module 102.

0036A feature of the local line card module 102 is that it supports a number of datalink layer encapsulations, implemented by a flexible encapsulation/decapsulation mechanism. The decapsulation mechanism is adaptable to accommodate emerging encapsulations. According to one embodiment, local line card module 102 supports IP over ATM over SONET/SDH; IP over PPP over SONET/SDH; IP over FR over SONET/SDH; IP over PPP over FR over SONET/SDH; IP over PPP over ATM over SONET/SDH; IP over MPLS over SONET/SDH; IP over SNAP 802.2; and IP over Ethernet 2.0. Line card module 102 also supports FRAME Relay DTE.

0037Those skilled in the art of communication nodes will appreciate that other encapsulations may be accommodated by the invention. The above list is intended to be illustrative, rather than limiting in nature.

0038A further feature of the illustrated communication node 100 is that it is dynamically bandwidth scalable. More particularly, according to one embodiment, the communication node 100 can include up to seven additional local line card modules 104-116, coupled to associated local interconnect modules 120-132 by way of Gigabit Ethernet connections 144-160. The expanded interconnect module 134 transfers information between local interconnect modules 118-132 by way of a plurality of Gigabit Ethernet connections 170. Each local interconnect module 118-132 is coupled to all three expanded interconnect boards 136-140. Another feature of the invention is that the same expanded interconnect module 134 can be employed for two local line card modules as is employed for additional local line card modules.

0039<figref idref="f0003">FIGURE 3</figref> is a more detailed schematic block diagram of an illustrative embodiment 200 of the communication node 100, but having only a single local line card module 102 coupled to a single local interconnect module 118. Since there is only a single local line card module 102, there is no need for the communication node 200 to include the second-level expanded interconnect module 134 of the type shown in <figref idref="f0001">FIGURE 1</figref>.

0040The local line card module 102 includes eight local line cards 202-216. Local line cards 202-216 are printed circuit boards holding integrated circuits and other components. Each line card 202-216 has six internal (I/O) ports 202a-202f, and an external SONET I/O port 202g. Line card 202 couples information between external I/O port 202g and internal I/O ports 202a-202f. External I/O port 202g couples information into and out of the node 200, and the internal I/O ports 202a-202f connect with up to forty-eight internal communication lines 217 and couple information between the local line card module 102 and the local interconnect module 118. Typically, each internal I/O port a-f includes a Gigabit Ethernet transceiver, providing a Gigabit Ethernet input channel and a Gigabit Ethernet output channel. Preferably, the input and output channels provide 10-bits of information. However, it should be noted that the term transceiver, as used throughout this description, is also intended to encompass structures including separate receivers and transmitters. The external I/O port 202g is preferably software configurable for either SONET or SDH operation. Thus, physical interfaces are software configurable for OC48 or STM16. SONET and SDH PAMS may be freely intermixed within access module 142. A fully loaded local line card module 102 can have up to eight external SONET/SDH I/O ports and forty-eight corresponding internal I/O ports.

0041The local interconnect module 118 includes three identical interconnect boards 218-222. The interconnect boards 218-222 are printed circuit boards holding integrated circuits and other components. Each board 218-222 is logically subdivided into two essentially identical planes. By way of example, interconnect board 218 includes logical planes 218a and 218b; interconnect board 220 includes logical planes 220a and 220b; and interconnect board 222 includes logical planes 222a and 222b. The communication node 200 transfers information through the interconnect boards 218-222 by way of Application Specific Integrated Circuits (ASICs) 224-228. Each ASIC 224-228 logically includes an a-half and a b-half. The logical a-half services the logical a-plane of a particular interconnect board 218-222, while the logical b-half services the logical b-plane of the particular interconnect board 218-222. By way of example, ASIC 224a services logical plane 218a and ASIC 224b services logical plane 218b.

0042The illustrated embodiment of <figref idref="f0002">FIGURES 2</figref> and <figref idref="f0003">3</figref> is described with respect to particular physical groupings of line cards 202-216 and local interconnect boards 218-222, and particular logical divisions of local interconnect planes 218a, 218b, 220a, 220b, 222a and 222c. However, as one skilled in the art will appreciate, the number of line card modules 102-116 and associated local interconnect modules 118-132 can be varied. Moreover, the number of local line cards included in a local line card module 102-116 can also be varied. Further, the number of local interconnect boards included in a local interconnect module 118 and the number of extended interconnect boards included in an extended interconnect module 134 can be varied. All logical divisions can also be varied.

0043With that caveat, according to the illustrated embodiment, each local interconnect board 218-222 includes sixteen internal communication ports (eight associated with each logical plane), and sixteen expanded communication ports (eight associated with each logical plane). As each interconnect board is essentially identical, board 218 will be discussed in detail. Boards 220 and 222 have a similar construction and operation. Specifically, local interconnect board 218 has eight internal communication ports 0a-7a, associated with ASIC 224a, and eight internal communication ports 0b-7b, associated with ASIC 224b. Local interconnect board 218 also includes eight expanded communication ports 8a-15a, associated with ASIC 224a, and eight expanded communication ports 8b-15b, associated with ASIC 224b. Each internal and expanded communication port includes an Ethernet transceiver providing a Gigabit Ethernet input channel and a Gigabit Ethernet output channel. Each internal communication port 0a-7a and 0b-7b couples to an internal communication port a-f of a line card 202-216, and transfers information between the local line card module 102 and the local interconnect module 118. Similarly, each internal communication port a-f of line cards 202-216 couples to an internal communication port 0a-7a and 0b-7b of one of the interconnect boards 218-222.

0044<figref idref="f0004">FIGURE 4</figref> shows a table 300 illustrative of the interconnections between the internal communication ports of line cards 202-216 and the internal communication ports of interconnect boards 218-222. Column 302 shows the line card designation numbers 202-216. Column 304 lists sets of ordered pairs in the form (interconnect plane #, port #), wherein those ordered pairs identify which internal port 0a-7a and 0b-7b of interconnect module 118 couples to each internal port a-f of line cards 202-216. By way of example, the first line of table 300 indicates that line card 202, internal port a, couples to internal port 0a of interconnect plane 218a. Similarly, internal ports b, c, d, e, and f of line card 202, couple to internal ports 0b of plane 218b, 0a of plane 220a, 0a of plane 220b, 0a of plane 222a, and 0b of plane 222b, respectively. In other words, the internal communication ports of line card 202 couple to the "zero numbered" ports of the interconnect planes 224a, 224b, 226a, 226b, 228a and 228b. In a similar fashion, the internal communication ports of line card 204 couple to the "one numbered" ports (e.g. 1a). Those of line card 206 couple to the "two numbered" ports (e.g. 2a). Those of line card 208 couple to the "three numbered" ports (e.g. 3a), and so on.

0045According to an illustrative embodiment, and as shown below in TABLE 1, the communication node 200 transfers information from the local interconnect module 118 to associated local line card module 102 in 64-byte cells.

0046As shown in TABLE 1, the 64-byte cell is subdivided into 16-byte groups. Logical plane 218a transfers 8-words of 2-bytes each. Logical planes 218b, 220a and 220b do the same. The two least significant bytes (LSBs) of the first and third 16-byte groups (i.e.. the groups transferred by logical planes 218a and 220a) are used for the address/handle of a destination line card. The two LSBs of the second and fourth 16-byte groups (i.e., the groups transferred by logical planes 218b and 220b) are used for interconnect addressing and flow control information. Board 222 provides error correction and redundancy information. More particularly, logical plane 222a provides a bit-by-bit "exclusive or" (⊕) between the information transferred on logical plane 218a and logical plane 220a. Logical plane 222b provides a bit-by-bit "exclusive or" between the information transferred on logical plane 218b and logical plane 220b. In the illustrated embodiment of TABLE 1, a byte contains 8-bits and a word contains 2-bytes. However, those skilled in the art will appreciate that alternative byte and word conventions may be employed. <tables id="tabl0001" num="0001"><table frame="all"><title><b>TABLE 1</b></title><tgroup cols="9"><colspec colnum="1" colname="col1" colwidth="14mm" /><colspec colnum="2" colname="col2" colwidth="21mm" /><colspec colnum="3" colname="col3" colwidth="21mm" /><colspec colnum="4" colname="col4" colwidth="21mm" /><colspec colnum="5" colname="col5" colwidth="21mm" /><colspec colnum="6" colname="col6" colwidth="21mm" /><colspec colnum="7" colname="col7" colwidth="21mm" /><colspec colnum="8" colname="col8" colwidth="21mm" /><colspec colnum="9" colname="col9" colwidth="23mm" /><thead><row><entry valign="top">Plane</entry><entry align="center" valign="top">Word 7</entry><entry align="center" valign="top">Word 6</entry><entry align="center" valign="top">Word 5</entry><entry align="center" valign="top">Word 4</entry><entry align="center" valign="top">Word 3</entry><entry align="center" valign="top">Word 2</entry><entry align="center" valign="top">Word 1</entry><entry align="center" valign="top">Word 0</entry></row></thead><tbody><row><entry>218a</entry><entry align="center">Data 7-0</entry><entry align="center">Data 6-0</entry><entry align="center">Data 5-0</entry><entry align="center">Data 4-0</entry><entry align="center">Data 3-0</entry><entry align="center">Data 2-0</entry><entry align="center">Data 1-0</entry><entry align="center">Dest. Adrs</entry></row><row><entry>218b</entry><entry align="center">Data 7-0a</entry><entry align="center">Data 6-0a</entry><entry align="center">Data 5-0a</entry><entry align="center">Data 4-0a</entry><entry align="center">Data 3-0a</entry><entry align="center">Data 2-0a</entry><entry align="center">Data 1-0a</entry><entry align="center">Flow Control</entry></row><row><entry>220a</entry><entry align="center">Data 7-1</entry><entry align="center">Data 6-1</entry><entry align="center">Data 5-1</entry><entry align="center">Data 4-1</entry><entry align="center">Data 3-1</entry><entry align="center">Data 2-1</entry><entry align="center">Data 1-1</entry><entry align="center">Dest. Adrs</entry></row><row><entry>220b</entry><entry align="center">Data 7-1a</entry><entry align="center">Data 6-1a</entry><entry align="center">Date 5-1 a</entry><entry align="center">Data 4-1 a</entry><entry align="center">Data 3-1 a</entry><entry align="center">Data 2-1 a</entry><entry align="center">Data 1-1a</entry><entry align="center">Flow Control</entry></row><row><entry>222a</entry><entry align="center">Data 7-0 ⊕ Data 7-1</entry><entry align="center">Data 6-0 ⊕ Data 6-1</entry><entry align="center">Data 5-0 ⊕ Data 5-1</entry><entry align="center">Data 4-0 ⊕ Data 4-1</entry><entry align="center">Data 3-0 ⊕ Data 3-1</entry><entry align="center">Data 2-0 ⊕ Data 2-1</entry><entry align="center">Data 1-0 ⊕ Data 1-0</entry><entry align="center">Dest Adrs</entry></row><row><entry>222b</entry><entry align="center">Data 7-0a ⊕ Data 7-1a</entry><entry align="center">Data 6-0a ⊕ Data 6-1a</entry><entry align="center">Data 5-0a ⊕ Date 5-1a</entry><entry align="center">Data 4-0a ⊕ Data 4-1a</entry><entry align="center">Data 3-0a ⊕ Data 3-1a</entry><entry align="center">Data 2-0a ⊕ Data 2-1a</entry><entry align="center">Data 1-0a ⊕ Data 1-0a</entry><entry align="center">Flow Control</entry></row></tbody></tgroup></table></tables>

0047With each line card 202-216 having six Gigabit internal Ethernet ports a-f, spread across three interconnect boards 218-222, and according to the format of TABLE 1, the six Gigabit internal Ethernet ports a-f provide 3-Gbs of usable bandwidth. More specifically, board 222 is not used for payload bandwidth, instead providing redundancy and error correction information, thus leaving 4-Gbs of bandwidth. 4-bytes out of sixty-four contained in a transferred cell (the LSBs of logical planes 218b and 220b) are used for interconnect addressing and flow control information, leaving 3.5 Gbs of bandwidth. And, 4-bytes out of the remaining fifty-six (the LSBs of logical planes 218a and 220a) are used by the line cards 202-216 as a destination handle/address, leaving 3 Gbs of bandwidth. This ensures that the communication node 200 can provide a sustained OC-48 (2.4 Gbs) transfer rate

0048TABLE 2 below depicts a typical information cell format for information transferred from a line card 202-216 to local interconnect planes 218a, 218b, 220a, 220b, 222a and 222b.

0049As shown in the first column of TABLE 2 and as previously described with respect to TABLE 1, information is transferred in 8-word/16-byte groups. Each logical plane 218a, 218b, 220a and 220b receives a 16-byte group. Logical plane 222a receives the "exclusive or" of planes 218a and 220a, and logical plane 222b receives the "exclusive or" of logical planes 218b and 220b. Bytes 2-16 of logical planes 218a, 218b, 220a and 220b provide the transferred data. <tables id="tabl0002" num="0002"><table frame="all"><title><b>TABLE 2</b></title><tgroup cols="13"><colspec colnum="1" colname="col1" colwidth="12mm" /><colspec colnum="2" colname="col2" colwidth="19mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="11mm" /><colspec colnum="5" colname="col5" colwidth="11mm" /><colspec colnum="6" colname="col6" colwidth="19mm" /><colspec colnum="7" colname="col7" colwidth="10mm" /><colspec colnum="8" colname="col8" colwidth="11mm" /><colspec colnum="9" colname="col9" colwidth="11mm" /><colspec colnum="10" colname="col10" colwidth="22mm" /><colspec colnum="11" colname="col11" colwidth="11mm" /><colspec colnum="12" colname="col12" colwidth="11mm" /><colspec colnum="13" colname="col13" colwidth="11mm" /><thead><row><entry valign="top">Byte</entry><entry valign="top">Plane 218a</entry><entry namest="col3" nameend="col5" align="left" valign="top">Plane 218b</entry><entry valign="top">Plane 220a</entry><entry namest="col7" nameend="col9" align="left" valign="top">Plane 220b</entry><entry valign="top">Plane 222a</entry><entry namest="col11" nameend="col13" align="left" valign="top">Plane 222b</entry></row></thead><tbody><row><entry>0</entry><entry><u>DestLo</u></entry><entry namest="col3" nameend="col4" align="left">0</entry><entry><u>X</u></entry><entry><u>DestLo</u></entry><entry namest="col7" nameend="col8" align="left"><i>0</i></entry><entry><u>X</u></entry><entry><u>DestLo</u></entry><entry namest="col11" nameend="col12" align="left">0</entry><entry><u>X</u></entry></row><row><entry>1</entry><entry><u>DestHi</u></entry><entry><u>P</u></entry><entry namest="col4" nameend="col5" align="left"><u>Payload</u></entry><entry><u>DestHi</u></entry><entry>P</entry><entry namest="col8" nameend="col9" align="left"><u>Payload</u></entry><entry><u>DestHi</u></entry><entry><u>P</u></entry><entry namest="col12" nameend="col13" align="left"><u>Payload</u></entry></row><row><entry>2</entry><entry>Data0</entry><entry namest="col3" nameend="col5" align="left">Data 1</entry><entry>Data2</entry><entry namest="col7" nameend="col9" align="left">Data 3</entry><entry>218a⊕220a</entry><entry namest="col11" nameend="col13" align="left">218b⊕220b</entry></row><row><entry>3</entry><entry>Data4</entry><entry namest="col3" nameend="col5" align="left">Data5</entry><entry>Data6</entry><entry namest="col7" nameend="col9" align="left">Data7</entry><entry>218a⊕220a</entry><entry namest="col11" nameend="col13" align="left">218b⊕220b</entry></row><row><entry>•</entry><entry>•</entry><entry namest="col3" nameend="col5" align="left">•</entry><entry>•</entry><entry namest="col7" nameend="col9" align="left">•</entry><entry>•</entry><entry namest="col11" nameend="col13" align="left">•</entry></row><row><entry>15</entry><entry>Data52</entry><entry namest="col3" nameend="col5" align="left">Data53</entry><entry>Data54</entry><entry namest="col7" nameend="col9" align="left">Data55</entry><entry>218a⊕220a</entry><entry namest="col11" nameend="col13" align="left">218b⊕220b</entry></row></tbody></tgroup></table></tables>

0050"X" above represents an XOFF from the line card to the local interconnect 118. Information cells pass through the local interconnect 118 on separate planes 218a-222b, but with some discrepancies. By way of example, the a-planes contain the line card destination addresses. The b-planes allow for 14-bits of extra "payload" data carried through untouched. The payload byte above typically has its most significant bit (bit "P") set as parity for words 0 and 1 together. Even on plane 222a, the "P" bit covers the 15-bits which precede it, rather than the parity across planes 218a and 220a.

0051The line card destination address is an address or handle (global to the node 100 system wide) which specifies the destination line card (for unicast information) or line card set (for multicast information) to which the information cell is to be transferred.

0052TABLE 3 below depicts a preferred destination address format for locally transferred unicast information, while TABLE 4 depicts a preferred destination address format for locally transferred multicast information. <tables id="tabl0003" num="0003"><table frame="all"><title><b>TABLE 3</b></title><tgroup cols="9"><colspec colnum="1" colname="col1" colwidth="14mm" /><colspec colnum="2" colname="col2" colwidth="12mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><colspec colnum="7" colname="col7" colwidth="12mm" /><colspec colnum="8" colname="col8" colwidth="12mm" /><colspec colnum="9" colname="col9" colwidth="12mm" /><thead><row><entry align="center" valign="top"><i>BYTE</i></entry><entry align="center" valign="top">7</entry><entry align="center" valign="top">6</entry><entry align="center" valign="top">5</entry><entry align="center" valign="top">4</entry><entry align="center" valign="top">3</entry><entry align="center" valign="top">2</entry><entry align="center" valign="top">1</entry><entry align="center" valign="top">0</entry></row></thead><tbody><row><entry align="center">0</entry><entry align="center"><i>APS</i></entry><entry align="center">0</entry><entry namest="col4" nameend="col6" align="center"><i>Line Card Module</i></entry><entry namest="col7" nameend="col9" align="center"><i>Line Card Designation</i></entry></row><row><entry align="center">1</entry><entry align="center"><i>P</i></entry><entry align="center">0</entry><entry align="center">0</entry><entry align="center">0</entry><entry align="center">0</entry><entry align="center">0</entry><entry align="center">1</entry><entry align="center">Pri</entry></row><row><entry align="center">2-15</entry><entry namest="col2" nameend="col9" align="center"><i>Cell Data</i></entry></row></tbody></tgroup></table></tables><tables id="tabl0004" num="0004"><table frame="all"><title><b>TABLE 4</b></title><tgroup cols="9"><colspec colnum="1" colname="col1" colwidth="14mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><colspec colnum="7" colname="col7" colwidth="10mm" /><colspec colnum="8" colname="col8" colwidth="10mm" /><colspec colnum="9" colname="col9" colwidth="10mm" /><thead><row><entry align="center" valign="top"><i>BYTE</i></entry><entry align="center" valign="top">7</entry><entry align="center" valign="top">6</entry><entry align="center" valign="top">5</entry><entry align="center" valign="top">4</entry><entry align="center" valign="top">3</entry><entry align="center" valign="top">2</entry><entry align="center" valign="top">1</entry><entry align="center" valign="top">0</entry></row></thead><tbody><row><entry align="center">0</entry><entry namest="col2" nameend="col9" align="center"><i>Least-Significant 8 bits of MulticastID</i></entry></row><row><entry align="center">1</entry><entry align="center"><i>P</i></entry><entry align="center">1</entry><entry namest="col4" nameend="col9" align="center"><i>Most-Significant 6 bits of Mcast ID</i></entry></row><row><entry align="center">2-15</entry><entry namest="col2" nameend="col9" align="center"><i>Cell Data</i></entry></row></tbody></tgroup></table></tables>

0053Byte-0 of TABLE 3 provides an "APS" bit, a Line Card Module designation field and a Line Card designation field. As shown in <figref idref="f0003">FIGURE 3</figref>, according to the illustrated embodiment, there are eight potential destination line cards 202-216. Each one is assigned a 3-bit code 000-111. Bits 3, 4 and 5 of byte-0 of TABLE 3 provide this code. As shown in <figref idref="f0002">FIGURE 2</figref>, a communication node 100, according to the illustrated embodiment, has eight potential line card modules 102-116. Each line card module 102-116 is assigned a 3-bit code 000-111. Bits 0, 1 and 2 of byte-0 of TABLE 3 provide this code. Bytes 2-15 provide the transferred data. The "P" bit provides parity across byte 1.

0054According to a preferred embodiment, unicast information cells travelling to a single destination line card have the "Pri" bit of TABLE 3 set to one for high-priority traffic. If the "APS" bit of TABLE 1 is set, the cell is sent to both the designated line card (n) and the (n+1) line card.

0055With reference to TABLE 4, the multicastID is an address into a 16 k x 9-bit RAM 748 of <figref idref="f0008">FIGURE 8</figref>. This 14-bit address retrieves a 9-bit value. The least significant 8-bits are a mask with each bit representing a line card 202-216. The most significant bit represents priority; set to a logical one for high priority or a logical zero for low priority. If the node includes more than one local line card chassis 102, then each bit of the 8-bit mask represents a particular local line card chassis.

0056In operation, and as illustrated in TABLE 1 above, the communication node 200 transfers each 16-byte group over a different internal communication channel. By way of example and referring again to <figref idref="f0003">FIGURE 3</figref>, assume each line card 202-216 has an associated address, and information enters line card 202 by way of external port 202g. Assume further that the entering information has a destination address of line card 208. As shown in <figref idref="f0002">FIGURE 2</figref>, internal port 202a couples a first 16-byte group to internal port 0a of interconnect board 218. Internal port 202b couples a second 16-byte group to internal port 0b of board 218. Internal port 202c couples a third 16-byte group to internal port 0a of board 220, and internal 202d couples a fourth 16-byte group to internal port 0b of board 220. Internal port 0a of board 218 couples the first 16-byte group to ASIC 224a. Internal port 0b of board 218 couples the second 16-byte group to ASIC 224b. Internal port 0a of board 220 couples the third 16-byte group to ASIC 226a, and internal port 0b of board 220 couples the fourth 16-byte group to ASIC 226b.

0057ASIC 224a processes the line card destination address and directs the first 16-byte group to internal port 3a of board 218. ASIC 224b processes the line card destination address and directs the second 16-byte group to internal port 3b of board 218. ASIC 226a processes the line card destination address and directs third 16-byte group to internal port 3a of board 220. ASIC 226b processes the line card destination address and directs the fourth 16-byte group to internal port 3b of board 220. Board 222 generates a bit-by-bit "exclusive or" between the first and third groups, and between the second and fourth groups. ASIC 228a processes the line card destination address and directs the "exclusive or" combination of the first and third groups to internal communication port 3a of board 222, and ASIC 228b processes the line card destination address and directs the "exclusive or" combination of the second and fourth groups to the internal communication port 3b of board 222. Board 222 in turn couples the first, second, third and fourth groups to destination line card 208, internal ports 208a-208d, respectively. Similarly, board 222 couples the "exclusive or" version of the groups of bytes to internal ports 208e and 208f. Destination line card 208 then performs various types of error checking, such as plain parity, 8B10B disparity and CRC across multiple cells. If line card 208 detects a bad character error, software can alert the line card to use the "exclusive or" version to retrieve an error-free version of the transferred information.

0058According to a further embodiment, the line card module 102 can determine whether a detected error is due to a failed line card 202-216 or a failed interconnect board 218-222. In the case where the error is due to a failed line card, the interconnect module removes that card from operation. In the case where the detected error is due to a failed interconnect card 218-222, the line card detecting the error can signal the error prone interconnect board 218-222 to take itself off line. So as not to compromise bandwidth, interconnect board 222 can automatically take the place of either interconnect board 218 or 220, until the failed board is replaced. According to a further feature, the failed board can be hot-swapped.

0059As discussed above, a feature of the invention is that according to a preferred embodiment, the communication node 100 is dynamically bandwidth scalable to include additional line card modules 104-116, having additional associated local interconnect chassis 120-160. According to a preferred embodiment, the modular construction of the line card modules 102-116, along with the modular construction of the local interconnect modules 118-132, in combination with the expanded interconnect module 134 provides the scalable feature. More specifically, as indicated in <figref idref="f0002">FIGURE 2</figref>, according to the illustrated embodiment 100, a first mechanical chassis 101 houses up to eight local line card modules 102-116. Similarly, a second mechanical chassis 103 houses up to eight local interconnect modules 118-132. Further, a third mechanical chassis 105 houses the extended interconnect network 134. The first mechanical chassis 101 electrically couples to the second mechanical chassis 103 by way of communication channels 142-160. The second mechanical chassis 103 electrically couples to the third mechanical module 105 by way of communication channels 170. The communication node 100 employs connectors designed for "hot-swapping" at module interfaces. Those connectors enable the local line card modules 102-116. the local interconnect modules 118-132, and the expanded interconnect boards 136-140 to be connected and unconnected (i.e., "hot-swapped") from their respective mechanical chassis 101, 103 and 105, while the communication node 100 is powered and operating transferring information. Thus, as a service provider requires additional bandwidth, additional local line card modules 102-116, with associate additional local interconnect modules 118-132 can be "plugged in" to chassis 101 and 103, respectively.

0060<figref idref="f0005">FIGURE 5</figref> is a more detailed schematic block diagram 400 showing interconnections between an exemplary local interconnect module 118 and an expanded interconnect module 134. The embodiment of <figref idref="f0004">FIGURE 4</figref> is illustrative of the dynamic bandwidth scalability of the communication node 100. As mentioned above, the local interconnect module 118 is essentially identical to optional local interconnect modules 120-132. Accordingly, the following illustrative description focuses on the interconnections between local interconnect module 118 and expanded interconnect module 134. However, each additional local interconnect module 120-132 interfaces to expanded interconnect module 134 in a like manner.

0061As shown in <figref idref="f0005">FIGURE 5</figref>, and as discussed in more detail with regard to <figref idref="f0003">FIGURE 3</figref>, the local interconnect module 118 includes three interconnect boards 218-222. Each board 218-222 logically subdivides into an a-plane and a b-plane. The a-plane and the b-plane are essentially identical and share an ASIC, which is also logically subdivided into an a-half and a b-half. Each ASIC 224-222 provides, among other functions, routing and switching between the internal communication channels associated with the particular interconnect board 218-222. According to the illustrated embodiment, each ASIC 224-226 may also provides storage queues, a control processor, control registers and status registers. It also controls Gigabit Ethernet I/O interfaces included on each interconnect board 218-222. The ASICs 224-228 further provide one or more pointer queues for storing information indicative of a substantially non-blocked path through its switching/routing circuitry.

0062Each local interconnect board 218-222 includes sixteen internal I/O ports 0a-7a and 0b-7b. The internal I/O ports 0a-7a and 0b-7b provide Gigabit Ethernet interfaces. As shown in <figref idref="f0003">FIGURE 3</figref>, those Gigabit interfaces couple to the internal communication channels of an associated local line card module 102. Each local interconnect board 218-222 also provides sixteen expanded I/O ports 8a-15a and 8b-15b. Each expanded I/O port 8a-15a and 8b-15b provides a Gigabit input channel and a Gigabit output channel. The expanded I/O ports 8a-15a and 8b-15b couple information between the local interconnect module 118 and the expanded interconnect module 134.

0063The expanded interconnect module 134 includes three essentially identical expanded interconnect boards 136-140. Each board 136-140 includes, among other components, one hundred and twenty-eight Gigabit Ethernet transceivers. Each board 136-140 also includes four ASICs 402-408, 410-416 and 418-424, respectively. ASICs 402-424 are essentially identical to ASICs 224-228. However, ASICs 404-424 are mode selected to operate in an expanded interconnect mode, rather than the local interconnect mode of ASICs 224-228. As in the case of ASICs 224-228, ASICS 404-424 each logically subdivides into an a-half and a b-half. Each half includes sixteen Gigabit Ethernet I/O ports, wherein each port includes a Gigabit input channel and a Gigabit output channel. Each of the sixteen Gigabit Ethernet ports couple to a Gigabit transceiver on the extended interconnect board.

0064By way of a specific example, board 136 of <figref idref="f0005">FIGURE 5</figref> includes ASICs 402-408. ASIC 402 is subdivided into to logical halves 402a and 402b. Similarly, ASIC 404 is subdivided into logical halves 404a and 404b; ASIC 406 is subdivided into logical halves 406a and 406b; and ASIC 408 is subdivided into logical halves 408a and 408b. ASIC 402 includes Gigabit Ethernet ports 0a-15a, on half 402a, and 0b-15b on half 402b. Ports 0a-15a couple to transceivers 0-15 on board 136, and ports 0b-15b couple to transceivers 16-31. Gigabit ports 0a-15a and 0b-15b of ASICS 404-408 successively couple to remaining transceivers 32-127. Gigabit I/O ports of ASICs 410-416 and 418-424 couple to one hundred and twenty-eight transceivers of boards 138 and 140, respectively, in an identical fashion to that described with respect to ASICS 402-404 on board 136.

0065<figref idref="f0006">FIGURE 6</figref> is a table 500 illustrating the communication paths between local interconnect module 118 and expanded interconnect module 134. Column 502 specifies the local interconnect port designation. Column 504 specifies the communication paths between local interconnect board 218 and expanded interconnect 134. Similarly, column 506 specifies the communication paths between local interconnect board 220 and expanded interconnect 134; and column 508 specifies the communication paths between local interconnect board 222 and expanded interconnect 134. As can be seen from <figref idref="f0004">FIGURES 4</figref> and <figref idref="f0005">5</figref>, the communication channels of board 218 couple to board 136. Those of board 220 couple to board 138, and those of board 222 couple to board 140. As also can be seen from <figref idref="f0005">FIGURE 5</figref>, the I/O interfaces from local interconnect module 118 couple to the zero and eight ports of ASICs 402-424.

0066<figref idref="f0007">FIGURE 7</figref> is a table 600 depicting the expanded interconnect port assignments for each of the potential local interconnect modules 118-132 of <figref idref="f0001">FIGURE 1</figref>. Column 602 identifies the particular local interconnect modules 118-132. Column 604 identifies the port assignments for the extended interconnect module 134. As shown, local interconnect module 120 couples to the one and nine ports; module 122 couples to the two and ten ports; module 124 couples to the three and eleven ports; module 126 couples to the four and twelve ports; module 128 couples to the five and thirteen ports; module 130 couples to the six and fourteen ports; and module 132 couples to the seven and fifteen ports.

0067TABLE 5 below specifies a preferred format for the destination address for unicast information transferred from a local interconnect modules 118-132 to the expanded interconnect module 134. Similarly, TABLE 6 specifies a preferred format for the destination address for multicast information transferred from a local interconnect modules 118-132 to the expanded interconnect module 134. <tables id="tabl0005" num="0005"><table frame="all"><title><b>TABLE 5</b></title><tgroup cols="16"><colspec colnum="1" colname="col1" colwidth="9mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="13mm" /><colspec colnum="4" colname="col4" colwidth="15mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><colspec colnum="7" colname="col7" colwidth="10mm" /><colspec colnum="8" colname="col8" colwidth="10mm" /><colspec colnum="9" colname="col9" colwidth="12mm" /><colspec colnum="10" colname="col10" colwidth="10mm" /><colspec colnum="11" colname="col11" colwidth="10mm" /><colspec colnum="12" colname="col12" colwidth="10mm" /><colspec colnum="13" colname="col13" colwidth="10mm" /><colspec colnum="14" colname="col14" colwidth="10mm" /><colspec colnum="15" colname="col15" colwidth="10mm" /><colspec colnum="16" colname="col16" colwidth="10mm" /><thead><row><entry namest="col1" nameend="col8" align="center" valign="top">DestHi</entry><entry namest="col9" nameend="col16" align="center" valign="top">DestLo</entry></row></thead><tbody><row><entry align="center">7</entry><entry align="center">6</entry><entry align="center">5</entry><entry align="center">4</entry><entry align="center">3</entry><entry align="center">2</entry><entry align="center">1</entry><entry align="center">0</entry><entry align="center">7</entry><entry align="center">6</entry><entry align="center">5</entry><entry align="center">4</entry><entry align="center">3</entry><entry align="center">2</entry><entry align="center">1</entry><entry align="center">0</entry></row><row><entry align="center">P</entry><entry align="center">0</entry><entry align="center"><u>Valid</u></entry><entry align="center"><u>Clump</u></entry><entry align="center">0</entry><entry align="center">0</entry><entry align="center">1</entry><entry align="center"><u>Pri</u></entry><entry align="center"><u>APS</u></entry><entry align="center">0</entry><entry namest="col11" nameend="col13" align="center"><u>Module</u></entry><entry namest="col14" nameend="col16" align="center"><u>Card</u></entry></row></tbody></tgroup></table></tables>

0068Referring to TABLE 5, bit 7 of the most significant byte (MSB) is the parity bit, which represents parity across the previous 15-bits of the destination address. Bit 5 is the "Valid" bit. The "Valid" bit is set if the destination address is valid. Bit 4 is the "Clump" bit. The "Clump" bit is set if there is a valid combination or clump of cells. Clumping is a feature of the invention employed for eliminating the need for reordering transferred information subsequent to transfer. As discussed in further detail below, with reference to <figref idref="f0007">FIGURE 7</figref>. Bit 7 is the "Pri" bit. The "Pri" bit is set to one for high-priority traffic. Bit 7 of the LSB is the "APS" bit. The "APS" bit is simply passed through the expanded interconnect 134 to local interconnects 118-132. Bits 3-5 of the LSB provide the 3-bit designation 000-111 for the destination line card module. Bits 0-3 of the LSB provide the 3-bit designation 000-111 for the particular line card. <tables id="tabl0006" num="0006"><table frame="all"><title><b>TABLE 6</b></title><tgroup cols="16"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><colspec colnum="7" colname="col7" colwidth="10mm" /><colspec colnum="8" colname="col8" colwidth="10mm" /><colspec colnum="9" colname="col9" colwidth="10mm" /><colspec colnum="10" colname="col10" colwidth="10mm" /><colspec colnum="11" colname="col11" colwidth="10mm" /><colspec colnum="12" colname="col12" colwidth="10mm" /><colspec colnum="13" colname="col13" colwidth="10mm" /><colspec colnum="14" colname="col14" colwidth="10mm" /><colspec colnum="15" colname="col15" colwidth="10mm" /><colspec colnum="16" colname="col16" colwidth="10mm" /><thead><row><entry namest="col1" nameend="col8" align="center" valign="top">DestHi</entry><entry namest="col9" nameend="col16" align="center" valign="top">DestLo</entry></row></thead><tbody><row><entry align="center">7</entry><entry align="center">6</entry><entry align="center">5</entry><entry align="center">4</entry><entry align="center">3</entry><entry align="center">2</entry><entry align="center">1</entry><entry align="center">0</entry><entry align="center">7</entry><entry align="center">6</entry><entry align="center">5</entry><entry align="center">4</entry><entry align="center">3</entry><entry align="center">2</entry><entry align="center">1</entry><entry align="center">0</entry></row><row><entry align="center">P</entry><entry align="center">1</entry><entry namest="col3" nameend="col16" align="center"><u>MulticastID (not 0 × 3FFF)</u></entry></row></tbody></tgroup></table></tables>

0069Preferably, the "Multicast ID" of TABLE 6 is passed on to the expanded interconnect module 134 to be translated. If the payload data portion of the cell is 0x3FFF, the information cell is considered to be invalid.

0070TABLES 7 and 8 depict a preferred format for unicast and multicast destination addresses, respectively, for information cells transferred from the expanded interconnect module 134 to a local interconnect modules 118-132. As described above, the "P" bit provides parity across the destination address. The "Valid" bit is set if the destination address is valid. The "Pri" bit is set for high-priority traffic. The "APS" bit is set if the cell is to be sent to both the designated line card (n), and the (n+1) line card. Bits 0-3 provide the designation code for the line card to which the cell is sent. <tables id="tabl0007" num="0007"><table frame="all"><title><b>TABLE 7</b></title><tgroup cols="16"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="13mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><colspec colnum="7" colname="col7" colwidth="10mm" /><colspec colnum="8" colname="col8" colwidth="10mm" /><colspec colnum="9" colname="col9" colwidth="12mm" /><colspec colnum="10" colname="col10" colwidth="10mm" /><colspec colnum="11" colname="col11" colwidth="10mm" /><colspec colnum="12" colname="col12" colwidth="10mm" /><colspec colnum="13" colname="col13" colwidth="10mm" /><colspec colnum="14" colname="col14" colwidth="10mm" /><colspec colnum="15" colname="col15" colwidth="10mm" /><colspec colnum="16" colname="col16" colwidth="10mm" /><thead><row><entry namest="col1" nameend="col8" align="center" valign="top">DestHi</entry><entry namest="col9" nameend="col16" align="center" valign="top">DestLo</entry></row></thead><tbody><row><entry>7</entry><entry>6</entry><entry>5</entry><entry>4</entry><entry>3</entry><entry>2</entry><entry>1</entry><entry>0</entry><entry>7</entry><entry>6</entry><entry>5</entry><entry>4</entry><entry>3</entry><entry>2</entry><entry>1</entry><entry>0</entry></row><row><entry>P</entry><entry>0</entry><entry><u>Valid</u></entry><entry /><entry /><entry /><entry /><entry><u>Pri</u></entry><entry><u>APS</u></entry><entry /><entry /><entry /><entry /><entry namest="col14" nameend="col16" align="center"><i>Card</i></entry></row></tbody></tgroup></table></tables><tables id="tabl0008" num="0008"><table frame="all"><title><b>TABLE 8</b></title><tgroup cols="16"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><colspec colnum="7" colname="col7" colwidth="10mm" /><colspec colnum="8" colname="col8" colwidth="10mm" /><colspec colnum="9" colname="col9" colwidth="10mm" /><colspec colnum="10" colname="col10" colwidth="10mm" /><colspec colnum="11" colname="col11" colwidth="10mm" /><colspec colnum="12" colname="col12" colwidth="10mm" /><colspec colnum="13" colname="col13" colwidth="10mm" /><colspec colnum="14" colname="col14" colwidth="10mm" /><colspec colnum="15" colname="col15" colwidth="10mm" /><colspec colnum="16" colname="col16" colwidth="10mm" /><thead><row><entry namest="col1" nameend="col8" align="center" valign="top">DestHi</entry><entry namest="col9" nameend="col16" align="center" valign="top">DestLo</entry></row></thead><tbody><row><entry>7</entry><entry>6</entry><entry>5</entry><entry>4</entry><entry>3</entry><entry>2</entry><entry>1</entry><entry>0</entry><entry>7</entry><entry>6</entry><entry>5</entry><entry>4</entry><entry>3</entry><entry>2</entry><entry>1</entry><entry>0</entry></row><row><entry>P</entry><entry>1</entry><entry namest="col3" nameend="col16" align="center"><u>MulticastID (not 0 × 3FFF)</u></entry></row></tbody></tgroup></table></tables>

0071<figref idref="f0008">FIGURE 8</figref> is a functional block diagram of an illustrative local interconnect board of <figref idref="f0005">FIGURE 5</figref>. The board 218 includes an ASIC 224 of the type employed in the local interconnect module 118. Preferably, ASIC 224 is identical to ASICs 402-424 employed in the expanded interconnect module 134. As all of the local interconnect boards are preferably identical, for the purpose of the following discussion it is assumed that board 218 is an exemplary local interconnect board of local interconnect module 118, and interfaces with local line card module 102 of <figref idref="f0002">FIGURE 2</figref>. However, those of ordinary skill in the art will appreciate that the ASIC 224 need not be identical to ASICs 404-424.

0072As shown in <figref idref="f0008">FIGURE 8</figref>, the interconnect board 218 includes Gigabit transceiver sets 704 and 708, memory elements 710, controller 712 and status and control registers 714. Gigabit transceiver set 708 provides Gigabit I/O ports 0a-7a and 0b-7b, which couple to the internal communication channels of a local line card module 102 of <figref idref="f0003">FIGURE 3</figref>. Gigabit transceiver set 704 provides Gigabit I/O ports 8a-15a and 8b-15b, which couple to the expanded communication channels of the expanded interconnect module 134, shown in <figref idref="f0005">FIGURE 5</figref>.

0073Each transceiver of sets 704 and 708 couples to the ASIC 224 by way of associated input and output shift and hold registers. More specifically, transceivers of set 704 couple to input shift and hold registers 714 by way of lines 716 and output shift and hold registers 718 by way of lines 720. Transceivers of set 704 couple to input shift and hold registers 722 by way of lines 724, and output shift and hold registers 726 by way of lines 728.

0074The ASIC 224 also includes a dual-port RAM 730 for storing various stacks and queues 731 associated with flow control information. Flow status 733 stores an availability status, regarding the availability of a particular line card to receive information. RAM 730 intermediately stores information being transferred through the board 218. Shift and hold registers 714 and 716 couple to the dual-port RAM 730 by way of lines 732 and 734, respectively. Shift and hold registers 722 and 726 couple to the dual-port RAM 730 by way of lines 736 and 738. The dual-port RAM 730 also couples to destination stack 740 by way of lines 742. The ninety-six destination queues 740 intermediately store addresses representative of where particular data is stored in RAM 730. The queues 740, preferably employ a plurality of stacks for ease of addressing. However, other storage structures can be employed.

0075As discussed above in the Summary of the Invention, and as discussed in further detail below, according to a preferred embodiment, the invention employs a plurality of memory storage queues / buffers to aid in the efficient transfer of information. It should be noted that the terms queue and buffer are used interchangeably. The dual-port RAM 730 provides an output queue for each transceiver of sets 704 and 706. More specifically, information cells coupled into board 218 to be transferred to a line card 202-204 of local interconnect 102, are first written into buffer memory at an address which is written into an output queue. Free list memory 742 provides a list of available buffer memory addresses. There is a reference counter 744 for each of the 1536 buffers in the dual port RAM 730. Reference counter 744 contains the number of output queues to which the contents of the respective buffers are to be sent. A reference counter 744 decrements in response to information being read from an associated buffer. When the reference counter reaches zero, the address of the buffer is returned to free list 743. In this way, the ASIC 224 can track the available buffer locations associated with each transceiver. Information written to buffer memory is subsequently transferred to one of the output shift and hold registers 720 or 728, and held there until an internal time slot arrives in which the destination address lookup can be performed, the read from the free list memory 742 can be performed, the write to the buffer memory can be performed, and the write to the output queue can be performed.

0076According to a preferred embodiment, the invention provides enhanced QoS features. To that end, queues 731 can include QoS queues. The QoS queues, such as those conceptually illustrated in <figref idref="f0009">FIGURES 9A and 9B</figref>, can have multiple watermark levels; those levels corresponding to differing priorities. By way of example, high-priority queue 900 of <figref idref="f0009">FIGURE 9A</figref> can have two watermarks 906 and 908. In range 902, queue 900 reports its status as "stop-none," indicating the I/O channel associated with queue 900 is ready to receive information of any priority. As depicted in the flow-chart of <figref idref="f0010">FIGURE 10A</figref>, during operation, in range 904, queue 900 reports its status as "stop-low" 1002, indicating the I/O channel associated with queue 900 is ready to receive information having a "medium" priority or higher, as indicated at 1004. When the queue 900 is filled up to level 906, it reports its status as "stop-all," as shown at 1006. As shown at 1008, this indicates that its associated I/O channel is unavailable. If the "Stop-Low" watermark 908 of queue 900 has not been reached, as indicated at 1006, it is available to receive information of any priority.

0077Low-priority queues, such as queue 910 depicted in <figref idref="f0009">FIGURE 9B</figref>, the operation of which is illustrated in flow-chart 1010 of <figref idref="f0010">FIGURE 10A</figref>, can include three watermarks 918, 920 and 922. As shown at 1012, queue 910 reports a status of "Stop-None" in range 912. As shown at 1014 and 101B, it reports a status of "Stop-Low" in range 914. As shown at 1018 and 1020, it reports a status of "Stop-Medium" in range 916, and as shown at 1022 and 1024, queue 910 reports a status of "Stop-All" subsequent to reaching watermark 918.

0078High-priority queues, such as queue 900, enable associated line cards to pass low- and medium-priority traffic, while not allowing low-priority traffic of one line card to strangle medium-priority traffic of a different line card.

0079Low-priority queues, such as queue 910, enable associated line cards to pass low-, medium- and high-priority traffic, while not allowing low-priority and medium-priority traffic of one line card to strangle high-priority traffic of a different line card. It also prevents low-priority traffic of one line card from strangling medium- and high-priority traffic of a different line card.

0080To efficiently manage information of differing priorities, the dual-port RAM 730 preferably provides storage for sixty-four low-priority unicast queues; one for each possible local line card in the communication node 100. The RAM 730 also provides storage for sixteen high-priority unicast queues; one for each line card of its local interconnect module, one for each potential additional local interconnect module, and one extra queue. Multicast traffic, preferably employs four low-priority and four high-priority queues.

0081Additionally, each plane of the expanded interconnect 134 employs eight high-priority unicast queues; one for each potential local interconnect module 118-132. Each expanded interconnect logical plane also employs eight high-priority and eight low-priority multicast queues; again, one for each potential local interconnect destination module 118-132.

0082A related component, the queue depth logic circuitry 746, maintains a status of all of the line cards 202-216 of local module 102. The status provides information regarding the availability of each line card 202-216 to receive information of varying priority levels.

0083Another feature of the illustrated embodiment of the invention is the way in which the node 100 passes the flow control status (sometimes referred to as back pressure status) between the expanded interconnect module 134 and each of the line cards of the local interconnect modules 118-132. According to one preferred embodiment, the invention utilizes bits of the information cell, previously reserved for the destination address. These bits are indicated in TABLE 1 as the "Flow Control" words on the b-channels.

0084Flow control information is passed between the local interconnect modules 118-132 and the expanded interconnect module 134 using the least significant word of the b-channel. These bits are included in the parity calculation of the parity bit in the primary channel's destination address word. This format is generally illustrated above in TABLE 1, with respect to local interconnect plane 218a word 0, and local interconnect plane 218b word 0. This flow information is preferably not repeated on all links. As illustrated in TABLE 9 below, also with reference to local interconnect planes 218a and 218b and expanded interconnect board 136, flow control information is sent in a two-cell sequence.

0085More particularly, column 1 of TABLE 9 lists the expanded interconnect port in (ASIC reference designation, ASIC port designation) format. Column 2 lists the port reference designations for local interconnect plane 218b. Type 0 and Type 1 identifies the information contained in the byte (e.g. if local interconnect port 8b receives a Type 0 byte, that byte contains Low6, Low5, Low4, Low3, Low2, Low1 and Low 0 flow control information). Each of the Low0-Low63 bits are set if the corresponding low-priority queue is not full and thus, can receive data. Similarly, the High0-High7, MCHigh, and MCLow bids are set if the corresponding high-priority, multicast high-priority and multicast low-priority queues have space available for receiving information. <tables id="tabl0009" num="0009"><table frame="all"><title><b>TABLE 9</b></title><tgroup cols="10"><colspec colnum="1" colname="col1" colwidth="23mm" /><colspec colnum="2" colname="col2" colwidth="23mm" /><colspec colnum="3" colname="col3" colwidth="14mm" /><colspec colnum="4" colname="col4" colwidth="15mm" /><colspec colnum="5" colname="col5" colwidth="15mm" /><colspec colnum="6" colname="col6" colwidth="15mm" /><colspec colnum="7" colname="col7" colwidth="15mm" /><colspec colnum="8" colname="col8" colwidth="15mm" /><colspec colnum="9" colname="col9" colwidth="17mm" /><colspec colnum="10" colname="col10" colwidth="16mm" /><thead><row rowsep="0"><entry align="center" valign="top">Exp.</entry><entry align="center" valign="top">Local</entry><entry align="center" valign="top">D7</entry><entry align="center" valign="top">D6</entry><entry align="center" valign="top">D5</entry><entry align="center" valign="top">D4</entry><entry align="center" valign="top">D3</entry><entry align="center" valign="top">D2</entry><entry align="center" valign="top">D 1</entry><entry align="center" valign="top">D0</entry></row><row rowsep="0"><entry align="center" valign="top">Interconnect</entry><entry align="center" valign="top">Interconnect</entry><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /></row><row><entry align="center" valign="top">Port</entry><entry align="center" valign="top">Port</entry><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /><entry align="center" valign="top" /></row></thead><tbody><row><entry align="center">402b.0</entry><entry align="center">8b</entry><entry align="center">Type0</entry><entry align="center">Low6</entry><entry align="center">Low5</entry><entry align="center">Low4</entry><entry align="center">Low3</entry><entry align="center">Low2</entry><entry align="center">Low1</entry><entry align="center">Low0</entry></row><row><entry align="center">404b,0</entry><entry align="center">9b</entry><entry align="center">Type0</entry><entry align="center">Low13</entry><entry align="center">Low12</entry><entry align="center">Low11</entry><entry align="center">Low10</entry><entry align="center">Low9</entry><entry align="center">Low8</entry><entry align="center">Low7</entry></row><row><entry align="center">406b.0</entry><entry align="center">10b</entry><entry align="center">Type0</entry><entry align="center">Low20</entry><entry align="center">Low19</entry><entry align="center">Low18</entry><entry align="center">Low17</entry><entry align="center">Low16</entry><entry align="center">Low15</entry><entry align="center">Low14</entry></row><row><entry align="center">408b.0</entry><entry align="center">11b</entry><entry align="center">Type0</entry><entry align="center">Low27</entry><entry align="center">Low26</entry><entry align="center">Low25</entry><entry align="center">Low24</entry><entry align="center">Low23</entry><entry align="center">Low22</entry><entry align="center">Low21</entry></row><row><entry align="center">402b.8</entry><entry align="center">12b</entry><entry align="center">Type0</entry><entry align="center">Low34</entry><entry align="center">Low33</entry><entry align="center">Low32</entry><entry align="center">Low31</entry><entry align="center">Low30</entry><entry align="center">Low29</entry><entry align="center">Low28</entry></row><row><entry align="center">404b.8</entry><entry align="center">13b</entry><entry align="center">Type0</entry><entry align="center">Low41</entry><entry align="center">Low40</entry><entry align="center">Low39</entry><entry align="center">Low38</entry><entry align="center">Low37</entry><entry align="center">Low36</entry><entry align="center">Low35</entry></row><row><entry align="center">406b.8</entry><entry align="center">14b</entry><entry align="center">Type0</entry><entry align="center">High0</entry><entry align="center">Low47</entry><entry align="center">Low46</entry><entry align="center">Low45</entry><entry align="center">Low44</entry><entry align="center">Low43</entry><entry align="center">Low42</entry></row><row><entry align="center">408b.8</entry><entry align="center">15b</entry><entry align="center">Type0</entry><entry align="center">High7</entry><entry align="center">High6</entry><entry align="center">High5</entry><entry align="center">High4</entry><entry align="center">High3</entry><entry align="center">High2</entry><entry align="center">High 1</entry></row><row><entry namest="col1" nameend="col10" align="center" /></row><row><entry align="center">402b.0</entry><entry align="center">8b</entry><entry align="center">Type 1</entry><entry align="center">Low52</entry><entry align="center">Low51</entry><entry align="center">Low50</entry><entry align="center">Low49</entry><entry align="center">Low48</entry><entry align="center">MCHigh</entry><entry align="center">MCLow</entry></row><row><entry align="center">404b.0</entry><entry align="center">9b</entry><entry align="center">Type1</entry><entry align="center">Low57</entry><entry align="center">Low56</entry><entry align="center">Low55</entry><entry align="center">Low54</entry><entry align="center">Low53</entry><entry align="center">MCHigh</entry><entry align="center">MCLow</entry></row><row><entry align="center">406b.0</entry><entry align="center">10b</entry><entry align="center">Type 1</entry><entry align="center">Low62</entry><entry align="center">Low61</entry><entry align="center">Low60</entry><entry align="center">Low59</entry><entry align="center">Low58</entry><entry align="center">MCHigh</entry><entry align="center">MCLow</entry></row><row><entry align="center">408b.0</entry><entry align="center">11b</entry><entry align="center">Type1</entry><entry align="center">Low3</entry><entry align="center">Low2</entry><entry align="center">Low1</entry><entry align="center">Low0</entry><entry align="center">Low63</entry><entry align="center">MCHigh</entry><entry align="center">MCLow</entry></row><row><entry align="center">402b.8</entry><entry align="center">12b</entry><entry align="center">Type1</entry><entry align="center">Low10</entry><entry align="center">Low9</entry><entry align="center">Low8</entry><entry align="center">Low7</entry><entry align="center">Low6</entry><entry align="center">Low5</entry><entry align="center">Low4</entry></row><row><entry align="center">404b.8</entry><entry align="center">13b</entry><entry align="center">Type1</entry><entry align="center">Low17</entry><entry align="center">Low16</entry><entry align="center">Low15</entry><entry align="center">Low14</entry><entry align="center">Low13</entry><entry align="center">Low12</entry><entry align="center">Low11</entry></row><row><entry align="center">406b,8</entry><entry align="center">14b</entry><entry align="center">Type1</entry><entry align="center">High0</entry><entry align="center">Low23</entry><entry align="center">Low22</entry><entry align="center">Low21</entry><entry align="center">Low20</entry><entry align="center">Low19</entry><entry align="center">Low18</entry></row><row><entry align="center">408b.8</entry><entry align="center">15</entry><entry align="center">Type1</entry><entry align="center">High7</entry><entry align="center">High6</entry><entry align="center">High5</entry><entry align="center">High4</entry><entry align="center">High3</entry><entry align="center">High2</entry><entry align="center">High1</entry></row></tbody></tgroup></table></tables>

0086Even though the high-priority, and some of the low-priority flow-control information is repeated on both cycles, there may nevertheless be some associated latency. Thus, to avoid queue overflow, the watermark levels are programmed at a level that takes into account potential latency. By way of example, if flow control latency takes four cells to stop incoming information, (4* 16)-4 locations should be reserved above the watermark to avoid overflow. This results from each of sixteen local input ports potentially aiming at the queue for four cell times. Thus, it would be draining out four information cells in that interval. In contrast, the space below the watermark level need only be (1*flow control latency) to avoid underflow. As a result, a preferred embodiment sets the watermark threshold levels between twelve and eighteen bytes out of one hundred and ninety-two bytes.

0087According to the above-discussed structures and protocols, the interconnect networks support Constant Bit Rate (CBR), Variable Bit Rate-Real-Time (VBR-rt), Variable Bit Rate-Non-Real-Time (VBR-nrt), and Unspecified Bit Rate (UBR) QoS categories. The interconnect networks can operate as a class-based ATM switch. Thus, traffic is queued for transfer based on the service category of the virtual circuit. However, shaping and policing are performed on a per-virtual-circuit basis. The interconnect networks also support QoS features for IP networks, such as the Differentiated Services Model.

0088As also mentioned above, a preferred embodiment of the invention employs "clumping" to increase the rate with which information can be transferred through the interconnect networks. Typically, in prior art systems, portions of communications can pass through an interconnect network at varying speeds, thus arriving at a common destination in a misordered fashion. Reordering information subsequent to transfer can waste valuable time, and has the potential for receiving out of order cells.

0089Therefore, according to a preferred embodiment of the invention, the expanded interconnect network 134 includes elements for "clumping" or combining a plurality of information cells and for transferring the clumped cells substantially simultaneously.

0090More particularly, the queue depth logic 746 detects when a group of four unicast information cells are available in a single queue. In response to detecting four unicast cells in a single queue, the queue depth logic 746 signals the dual-port RAM 731 working in conjunction with the destination stack 740 to transfer the detected four cell clump to shift and hold registers 726 for substantially simultaneous transfer via Ethernet transceivers 708. With the clump of cells being transferred together, they arrive at a destination within a close enough time proximity to avoid reordering.

0091According to a further embodiment, a programmable wait timer begins decrementing upon the arrival of a first information cell to be included in the clump. If the timer expires prior to the complete formation of a clump, it triggers the cell(s) ready to be sent to be combined with 4-N invalid cells, where N is the number of cells which the clump is lacking.

0092Multicast cells are clumped together across paths. When multicast traffic is available to be sent on at least four different paths, it is considered available for transmission. As in the case of unicast traffic, a programmable wait timer on any given multicast queue can artificially render multicast traffic eligible. A programmable watermark threshold on multicast queues can also artificially render multicast traffic eligible. Whenever multicast traffic is eligible to be sent, "QInfo" cells are sent on the remaining links to or from the expanded interconnect 134.

0093The ASIC 224 also includes a translation memory 748. The translation memory 748 provides storage for path segments through the expanded interconnect module 118, if such a module is included in the system. In the case of a node configured as shown in <figref idref="f0002">FIGURE 2</figref>, translation memory 748 preferably contains nine logical storage areas; one for each local interconnect modules 102-116, and one for the expanded interconnect module 118. The expanded interconnect storage area is configured as a bitmap of destination line cards and priority. Destination address circuitry 750 accesses the translation memory 748, and the multicast bitmap register 752 receives the accessed information.

0094A feature of the invention is synchronization of the local interconnect boards of a particular local interconnect module with each other, and the synchronization of the expanded interconnect boards 138-140 with each other. Since each board is independent, although they derive their clock frequencies from the same source, some signals are employed to establish and maintain synchronization between boards. Slot synchronization forces essentially identical "time zero" references between boards, and thus planes, in a module. Cell synchronization enables a local interconnect module to set its slot zero reference such that its transmitted information cells can arrive at the expanded interconnect 134 at a safe time. CPU synchronization enables certain CPU write operations to take place at the same time on all planes in a module.

0095Plane synchronization logic 752 provide signals 754 necessary to synchronize certain read and write operations between each plane of local interconnect module 118. Control registers 758 provide flow control information by way of lines 760 to the other planes of local interconnect 118, if operating in local mode, or the additional expanded interconnect planes of module 134 if operating in expanded mode.

0096Plane to plane cell synchronization is attained by cellok inter-plane connections 761. An asserted cellok signal 761 indicates that the corresponding plane has received a valid and error free cell header containing the 2-byte destination address. According to the illustrated embodiment, each plane outputs 16 cellok signals 761 and inputs 32 cellok signals 761. Each cellok output, N, represents that both the a-ports and the b-ports have valid cell headers.

0097For a cell to be forwarded, all operating planes assert their respective cellok signals 761. If one plane asserts cellok signals 761 and other planes do not, errors are recorded in CPU addressable registers 758. If a plane fails, the system has the capability of instructing the operating planes to ignore the failed plane. In this way, a single failed plain does not reduce the rate with which the effected local or expanded interconnect can transfer information.

0098Substantially identical ASICs are employed in the local interconnect modules 118-132 and the expanded interconnect module 134. To that end, ASIC 224 includes mode select 756 for selecting whether ASIC 224 is to operate as a local interconnection circuit or as an expanded interconnection circuit. As shown in <figref idref="f0003">FIGURES 3</figref> and <figref idref="f0005">5</figref>, in local mode, ports 0a-7a and 0b-7b connect to local line cards and ports 8a-15a and 8b-15b connect to expanded interconnect 134. Alternatively, in expanded mode all ports 0a-15a and 0b-15b connect to local interconnect planes, such as 218-222 shown in <figref idref="f0005">FIGURE 5</figref>.

0099Referring again to <figref idref="f0008">FIGURE 8</figref>, an important feature of the illustrated ASIC 224 is a "slot counter" contained in timers, counters, control registers 758. The slot counter repeatedly counts from 0-15. Each port 01-15a and 0b-15b is assigned a slot count. Each time the slot count 0-15 matches a port number, a check is performed to determine if there is a cell to be transmitted out that port. If there is, the cell is copied from RAM 730 to shift and hold register 718 or 726 for transmission. If there is no cell to be transmitted, then a flow control cell is transmitted. According to the illustrated embodiment, a common slot counter is employed for the a-ports and the b-ports.

0100As mentioned above, board 218 also includes controller 712 and memory 710. Memory 710 stores the control code for board 218. As such, it provides start up initialization of statuses, pointers and communication interfaces. Controller 712 provides a variety of conventional processor functions.

0101As in the case of the local interconnect boards, expanded interconnect boards divide logically into essentially identical a- and p-planes. Thus, for illustrative purposes, <figref idref="f0012">FIGURE 11</figref> is described in terms of the a-plane 136a of expanded interconnect board 136 of <figref idref="f0005">FIGURE 5</figref>.

0102Plane 136a includes four ASICs 402a, 404a, 406a and 408a. ASICs 402a-408a are essentially identical to ASIC 224 of <figref idref="f0008">FIGURE 8</figref>. Each ASIC 402a-408a controls sixteen Gigabit Ethernet ports 1102-1108. Ports 1102-1108 couple to ASICs 402a-408a by way of shift and hold registers, such as registers 714 and 718 of <figref idref="f0008">FIGURE 8</figref>. Bus 110 couples interplane control signals, such as those generated by counters, timers and registers 758 and plane synchronization logic 753, to each ASIC 402a-408a. Processor 1114 controls ASICS 402a-408a by way of bus 1112. Processor 1114 includes a CPU module, DRAM, FPGA control and Ethernet control, much in the same way that memory 710, controller 712 and control and status registers 753 provide these functions for local interconnect board 218.

0103It should be noted that connections and circuit divisions referred to in the above description may be representative of both actual and logical connections or divisions.

0104<figref idref="f0012">FIGURE 11</figref> shows a functional block diagram of a typical expanded interconnect logical plane illustrative of any of interconnect planes of <figref idref="f0004">FIGURE 4</figref>.

0105It will thus be seen that the invention efficiently attains the objects set forth above, including providing dynamically bandwidth scalable interconnect network. Since certain changes may be made in the above constructions and the described methods without departing from the scope of the invention, it is intended that all matter contained in the above description or shown in the accompanying drawings be interpreted as illustrative and not in a limiting sense.

0106Having described the invention, what is claimed as new and protected by Letters Patent is: