US 5,978,359 AGrant
Allocated and Dynamic Switch Flow Control
Issue Date:1999-11-02
•60 Claims
•3 Drawing Sheets
Abstract
A system is disclosed for eliminating cell loss through the use of flow control of both allocated and dynamic bandwidth. When output buffers in the switch become filled to a predetermined threshold level a feedback message is provided to input buffers to prevent transmission of cells from the input buffers to the output buffers. In order to provide connection and traffic type isolation the buffers are grouped into queues and flow control may be implemented on a per queue basis. The feedback message is a digital signal including an ACCEPT/REJECT message and a NO-OP/XOFF message. An XOFF message can be received while transmitting via allocated bandwidth or dynamic bandwidth. In particular, an XOFF (allocated) message may be received with regard to allocated bandwidth and an XOFF (dynamic) message may be received with regard to dynamic bandwidth. When ACCEPT is received by the requesting input queue the cell is transferred to the output queue. When REJECT is received by the requesting queue the cell is not transferred. When XOFF (dynamic) is received by the requesting input queue further requests to transfer to that output queue by the requesting input queue using dynamic bandwidth are halted until receipt of an XON message from that output queue. When XOFF (allocated) is received by the requesting input queue further requests to transfer to that output queue by the requesting input queue using allocated bandwidth are halted until receipt of an XON message from that output queue.
Metadata
Assignees
- Fujitsu Network Communications, Inc.
- Fujitsu Limited
Inventors
- Stephen A. Caldara
- Stephen A. Hauser
- Thomas A. Manning
Application Information
Application Number:US 6833489
Filing Date:1996-07-18
Priority Date:1996-07-18
Art Unit:272
Classifications
IPC:
H04L 1256
Field of Search:
370413;414;230;231;235;249;236;412;417;389;391;392;395;398;399;428;429;465;468
Patent Drawings (3 sheets)
Description
Field of the Invention
The present invention is generally related to telecommunications networks, and more particularly to reduction of cell loss in network switches.
Background of the Invention
Networks such as asynchronous transfer mode ("ATM") networks are used for transfer of audio, video and other data. ATM networks deliver data by routing data units such as ATM cells from source to destination through switches. Switches include input/output ("I/O") ports through which ATM cells are received and transmitted. The appropriate output port for transmission of the cell is determined based on the cell header.
One problem associated with ATM networks is loss of cells. Cells are buffered within each switch before being routed and transmitted from the switch. More particularly, switches typically have buffers at either the inputs or outputs of the switch for temporarily storing cells prior to transmission. As network traffic increases, there is an increasing possibility that buffer space may be inadequate and data lost. If the buffer size is insufficient, cells are lost. Cell loss causes undesirable interruptions in audio and video data transmissions, and may cause more serious damage to other types of data transmissions. Avoidance of cell loss is therefore desirable.
Summary of the Invention
A method and apparatus are disclosed for eliminating cell loss within a network switch through the use of flow control. The switch includes at least one input port, at least one output port, and input and output buffers associated with the respective input and output ports. Cells enter the switch through the input port and are buffered in the input buffers. The cells are then transmitted from the input buffers to the output buffers, and then transmitted to the output port. When the output buffers become filled to a predetermined threshold level, a feedback message is provided to the input buffers to prevent transmission of cells from the input buffers to the output buffers. Hence, cell loss between the input buffer and the output buffer is prevented by flow control.
In order to provide both connection and traffic type isolation, the buffers are grouped into queues and flow control is implemented on a per queue basis. Each queue includes multiple buffers, and each switch includes multiple input queues and multiple output queues. Upon entering the switch, each cell is loaded into a particular input queue for eventual transmission to a particular output queue. Individual queues are then assigned to traffic type groups in order to provide traffic type flow control if shared resources are being utilized. In an alternate implementation, each queue could be dedicated to a particular traffic type (sometimes referred to as a service class) such as the variable bit rate ("VBR") service class and the available bit rate ("ABR") service class. Flow control can then be implemented on a per traffic type basis. Further, flow control can be implemented on traffic sub-types and queues where each queue may be assigned to a particular connection, thereby providing flow control on a per connection as well as traffic subtype basis. Table 1 below shows possible flow control configurations.
Each connection is assigned bandwidth types based on the traffic type associated with the connection. There are two types of bandwidth to grant within the switch: allocated and dynamic. Allocated bandwidth is bandwidth which is "reserved" for use by the connection to which the bandwidth is allocated. Generally, a connection with allocated bandwidth is guaranteed access to the full amount of bandwidth allocated to that connection. As such, traffic types that need deterministic control of delay are assigned allocated bandwidth. Dynamic bandwidth is bandwidth which is "shared" by any of various competing connections. Because dynamic bandwidth is a shared resource, there is generally no guarantee that any particular connection will have access to a particular amount of bandwidth. For this reason dynamic bandwidth is typically assigned to connections with larger delay bounds. Other connections may be assigned a combination of dynamic and allocated bandwidth.
A digital feedback message with first and second bits is provided to facilitate flow control. The feedback message may include an ACCEPT message which can be sent from the output queue to the input queue. More particularly, using the first bit of the feedback message, first bit=0 indicates an ACCEPT of an input queue request to transfer a cell to the output queue. When ACCEPT is received by the requesting input queue, the cell is transferred to the output queue.
The feedback message may also include a REJECT message. When REJECT is received by the requesting input queue, the cell is not transferred. However, further requests to transfer may be sent by the input queue.
The feedback message may also include a NO-OP/XOFF message. An XOFF message can be received while transmitting via allocated bandwidth or dynamic bandwidth. In particular, an XOFF (allocated) message may be received with regard to allocated bandwidth and an XOFF (dynamic) message may be received with regard to dynamic bandwidth. An optional tagging technique may be employed to distinguish between requests for dynamic and allocated bandwidth.
The XOFF (dynamic) message temporarily halts transmission of requests to transfer via dynamic bandwidth. Each input queue receiving XOFF (dynamic) from a particular output queue temporarily ceases submitting requests to transmit to that particular output queue via dynamic bandwidth until a specified event occurs. The specified event could be passage of a predetermined amount of time or receipt of an XON signal which enables further requests to transfer to be sent. The input queues could also be enabled with an XON signal on a regular basis, i.e., without regard to when each particular input queue was placed in the XOFF (dynamic) state. Such a regular basis could be, for example, every 100 msec. When the second bit of the two bit message equals 0, such indicates an NO-OP (no operation) signal. Each input queue receiving a NO-OP signal is not disabled.
The XOFF (allocated) feedback message temporarily halts transmission of requests to transfer via allocated bandwidth. Each input queue receiving XOFF (allocated) from a particular output queue temporarily ceases submitting requests to transmit to that particular output queue via allocated bandwidth until a specified event occurs. The specified event is typically receipt of an XON signal which enables further requests to transfer to be sent. The input queues could also be enabled with an XON signal on a regular basis, i.e., without regard to when each particular input queue was placed in the XOFF (allocated) state. Such a regular basis could be, for example, every 100 msec. When the second bit of the two bit message equals 0, such indicates an NO-OP signal. Each input queue receiving a NO-OP (no operation) signal is not disabled.
In the preferred embodiment an XON signal is used to enable input queues which have been placed in either XOFF state. Each input queue receiving XON from a particular output queue is enabled to submit requests to transmit to that output queue. More particularly, the XON resets both the XOFF (dynamic) and XOFF (allocated) states. The XON signal can be used in conjunction with enabling on a regular basis to both reduce unnecessary switch traffic and prevent flow blockage due to errors.
It will be apparent that various combinational responses to a request to transmit may be received by the requesting input queue. Receipt of NO-OP and either ACCEPT or REJECT operates as described above. Receipt of either XOFF (dynamic) and ACCEPT or XOFF (allocated) and ACCEPT indicates that further requests to transfer via the designated bandwidth type should cease following transfer of one cell. Receipt of XOFF (dynamic) and REJECT or XOFF (allocated) and REJECT indicates that further requests to transfer via the designated bandwidth type should cease immediately and no cells may be transmitted. Thus, the XOFF commands effect future requests while the REJECT command provides for denial of the current request.
The NO-OP/XOFF (dynamic) message is employed to reduce unnecessary feedback signaling within the switch. Switch bandwidth is inefficiently used when REJECT is repeatedly asserted when a cell can not be transmitted through the switch. XOFF (dynamic) is thus used to modify To Switch Port Processor ("TSPP") behavior to reduce the number of requests made to a full From Switch Port Processor ("FSPP") queue.
Flow control with the feedback messages described above provides reliable point-to-multipoint transmission within the switch, i.e., transmission from a single input queue to multiple output queues. In point-to-multipoint operation the feedback messages from the multiple output queues to the single input queue are logically OR'd such that a single XOFF (dynamic) or REJECT message from any one of the plurality of output queues prevents transmission. Thus, point-to-multipoint cells are transmitted at the rate of the slowest destination queue.
Flow control with the two bit feedback messages described above also provides reliable multipoint-to-point transmission within the switch, i.e., transmission from multiple input queues to a single output queue. Each output queue has a threshold, and sends the XON message when the output queue drains to that threshold. In multipoint-to-point operation, the XON threshold of the output queue is dynamically set to reserve sufficient space for each input queue to transmit to the output queue. For example, if there are eight input queues then the threshold is set to eight so that the output queue will free sufficient space to receive all of the cells contemporaneously in serial fashion.
Brief Description of the Drawing
These and other features of the present invention will be more apparent from the following detailed description in conjunction with the drawing of which:
FIG. 1 is a switch interconnect block diagram;
FIG. 2 is a block diagram illustrating point-to-point operation, switch flow control and link flow control;
FIG. 3 is a block diagram illustrating point-to-multipoint operation; and
FIG. 4 is a block diagram illustrating multipoint-to-point operation.
Detailed Description of the Drawing
Referring now to FIG. 1, the switch includes an N.times.N switch fabric 10, a bandwidth arbiter 12, a plurality of To Switch Port Processor subsystems ("TSPP") 14, a plurality of To Switch Port Processor ASICs 15, a plurality of From Switch Port Processor subsystems ("FSPP") 16, a plurality of From Switch Port Processor ASICs 17 and a plurality of multipoint topology controllers 18. The N.times.N switch fabric, such as an ECL cross point switch fabric, is used for cell data transport, and yields N times 670 Mbps throughput. The bandwidth arbiter controls switch fabric interconnection, dynamically schedules unassigned bandwidth and resolves multipoint-to-point bandwidth contention. Each TSPP schedules transmission of cells to the switch fabric from multiple connections. Not shown are the physical line interfaces between the input link and the TSPP subsystem. The FSPP receives cells from the switch fabric and organizes those cells onto output links. Not shown are the physical line interfaces between the output link and the FSPP subsystem.
Referring now to FIG. 2, the switch includes a plurality of input ports 20, a plurality of output ports 22, and input buffers 26 and output buffers 28 associated with the input ports and output ports, respectively. To traverse the switch, a cell 24 enters the switch through an input port and is buffered in the input buffers. The cell is then transmitted from the input buffers to output buffers in an output port. From the output port the cell is transmitted outside of the switch, for example, to another switch 29. In response to a transfer request, if the output buffers become filled to a predetermined threshold level a feedback message 30 is provided to the input ports to prevent transmission of cells from the input ports to the output buffers.
The feedback message 30 prevents cell loss within the switch. If the number of cells 24 transmitted to the output buffers is greater than the number of available output buffers 28 then cells are lost. However, in response to a transfer request, when the output buffers 28 become filled to the threshold level the feedback message is transmitted to the input ports 20 to prevent transmission of cells from the input buffers. The threshold level is set to a value which prevents transmission of more cells than can be handled by the available output buffers. Hence, cell loss between the input buffers and the output buffers is prevented by the flow control feedback message.
In order to provide both connection and traffic type isolation the buffers 26, 28 are organized into queues 32, 34 respectively and flow control is implemented on a per queue basis. Each queue includes multiple buffers, and each input port and output port includes multiple input queues 32 and multiple output queues 34. Upon entering the switch, each cell 24 is loaded into a particular input queue 32 for eventual transmission to a particular output queue 34. The queues are also assigned to traffic type groups in order to provide traffic type flow control if shared resources are being utilized. By assigning a unique queue per connection, flow control can then be implemented on a per connection basis. In addition, nested queues of queues may be employed to provide per traffic type, per connection flow control.
For multipoint topologies multiple queues may be required per connection, and indirection utilized to implement per connection flow control. At the TSPP when there are multiple sources for a multipoint connection the multiple queues are nested into a scheduling list 48. At the TSPP when there is a single source a scheduling list is still employed, but having a single queue. A scheduling list is effectively a queue of queues where the queues have cells to be transmitted for that connection, and there is a scheduling list for each connection at the TSPP and the TSPP supports multiple connections. Hence, a scheduling list may be considered an input queue, and the terms are hereafter used synonymously.
Each connection is assigned bandwidth types based on the traffic type associated with the connection. There are two types of bandwidth to grant within the switch: allocated and dynamic. Allocated bandwidth is bandwidth which is "reserved" for use by the connection to which the bandwidth is allocated. Generally, a connection with allocated bandwidth is guaranteed access to the full amount of bandwidth allocated to that connection. As such, traffic types that need deterministic control of delay are assigned allocated bandwidth. Dynamic bandwidth is bandwidth which is "shared" by any of various competing connections. Because dynamic bandwidth is a shared resource, there is generally no guarantee that any particular connection will have access to a particular amount of bandwidth. For this reason dynamic bandwidth is typically assigned to connections with larger delay bounds. Other connections may be assigned a combination of dynamic and allocated bandwidth.
In order to distinguish between cells associated with connections utilizing dynamic bandwidth, allocated bandwidth, or both, each transfer request is tagged. More particularly, transfer requests of a connection utilizing dynamic bandwidth are tagged with a bit in a first state and transfer requests of a connection utilizing allocated bandwidth are tagged with the bit in a second state. If the connection is above the allocated cell rate then the transfer request is tagged as dynamic. If the connection is operating at or below the allocated cell rate then the transfer request is tagged as allocated.
Referring now to FIG. 1, FIG. 2 and Table 2, the feedback message 30 is provided in response to a request message 36. Prior to transmitting a cell from an input port 20 to an output port 22 the request message including the allocated/dynamic tag is sent from the input port to the output port to determine whether sufficient buffers 28 are available in the output port. The feedback message 30 provides an indication of buffer status at the output port, and transmission proceeds accordingly. The request message 36 always precedes cell transfer within the switch so that cells are only transferred under selected conditions.
In order to provide efficient flow control the feedback message 30 from the output port to the input port includes several sub-type messages. For example, the feedback message includes an ACCEPT message which may be sent in response to the request message. Using a one bit digital signal, a first bit=0 indicates an ACCEPT of an input queue request to transfer a cell to a particular output queue. When ACCEPT is received by the requesting input queue, the cell is transferred to the output queue.
The feedback message 30 also includes a REJECT message. More particularly, the response to the request message includes either an ACCEPT or REJECT message. Using the one bit digital signal, a first bit=1 indicates a REJECT of the request to transfer a cell to the output queue. When REJECT is received by the requesting input queue, the cell is not transferred to the output queue. However, further request messages 36 may be sent from the input queue to the output queue.
In order to reduce unnecessary message traffic the feedback message 30 may also include an XOFF (dynamic) message which temporarily halts transmission of request messages 36 via dynamic bandwidth. Using a second bit of a two bit digital feedback signal, a second bit=1 indicates XOFF (dynamic). Each input queue 32 receiving XOFF (dynamic) from a particular output queue 34 temporarily ceases transmission of request messages for dynamic bandwidth to that particular output queue until a specified event occurs. The specified event could be passage of a predetermined interval of time or receipt of another signal. A second bit=0 indicates a NO-OP, i.e., a no operation message meaning that XOFF (dynamic) has not been asserted.
The feedback message may also include an XOFF (allocated) feedback message. Each input queue receiving XOFF (allocated) from a particular output queue temporarily ceases submitting requests to transmit to that particular output queue via allocated bandwidth until a specified event occurs. The specified event is typically receipt of an XON signal which enables further requests to transfer to be sent. The input queues could also be enabled with an XON signal on a regular basis, i.e., without regard to when each particular input queue was placed in the XOFF (allocated) state. Such a regular basis could be, for example, every 100 msec.
In practice the request tagging technique allows use of a single XOFF message to designate either XOFF (dynamic) or XOFF (allocated). The request tagging technique tags requests for bandwidth with a tag bit based upon whether the request is for dynamic or allocated bandwidth. The tag bit thus distinguishes allocated and dynamic requests and feedback, i.e., the XOFF transmitted in response to a request for dynamic bandwidth is XOFF (dynamic).
Utilizing the two bit feedback message, various responses to each request message may be received by the requesting input queue. Such responses are interpreted as follows. Receipt of NO-OP and either ACCEPT or REJECT operates as described above. Receipt of XOFF (dynamic) and ACCEPT indicates that further requests to transfer should cease following transfer of one cell. Receipt of XOFF (dynamic) and REJECT indicates that further requests to transfer should cease immediately and no cells may be transmitted. Thus, the XOFF (dynamic) command effects future requests while the REJECT command provides for denial of the current request.
The feedback message 30 may also include an XON message which enables further transmission of request messages. The XON message occurs asynchronously to the request to transfer messages, and is not provided in response thereto. The XON message is effective to remove both XOFF conditions. Each input queue receiving XON from a particular output queue is enabled to submit requests to transmit to that output queue.
In order to reduce the likelihood of lockup in switch flow control it may be desirable to employ timeout type functions which will allow continued operation despite the removal or failure of internal elements such as ports. For example, an input queue 32 which has ceased transmission of request messages to a particular output queue 34 following receipt of an XOFF (dynamic or allocated) message may transmit a further request message to that output queue if an XON message is not received from that output queue within a predetermined interval of time. Alternatively, input queues may periodically transmit request messages regardless of XOFF (dynamic or allocated) state.
Referring again to FIG. 1, the invention will now be described in greater detail. In the preferred architecture each input port includes a TSPP 14, and each output port includes an FSPP 16. The TSPPs and FSPPs each include cell buffer RAM which is organized into queues 32, 34, respectively. All cells in a connection 40 pass through a single queue at each port, one at the TSPP and one at the FSPP, for the life of the connection. The queues thus preserve cell ordering. This strategy also allows quality of service ("QoS") guarantees on a per connection basis.
The request message 36 is a probe which is sent to the FSPP 16 from the TSPP 14 to determine whether sufficient buffers 34 are available for cell transmission. In order to guarantee no cell loss within the switch a TSPP cannot transmit a cell to an FSPP unless there is buffer space available for that cell. To determine buffer status, the probe communicates destination multiqueue numbers which indicate the FSPP queue or queues to which the cell is to be transmitted. For example, a destination multiqueue number could identify output queue 34a as the destination queue. When buffer space is not available in that queue, the FSPP responds to the probe with either or both of the "REJECT" and "XOFF (dynamic or allocated)" messages, as will be described below.
Three communication paths are used to implement the probe and feedback messages of switch flow control: a Probe Crossbar 42, an XOFF Crossbar 44 and an XON Crossbar 46. The Probe Crossbar 42 is an N.times.N crosspoint switch fabric which is used to transmit an FSPP multiqueue Number to each FSPP. The multiqueue number identifies a plurality of destination queues for the cell for use in point-to-multipoint connections. The FSPP uses the multiqueue number to direct the probe 36 to the appropriate output queue or queues 34 and thereby determine if there are enough output buffers available in the destination queues for receipt of the cell or cells. There is a unique multiqueue number per connection per FSPP with multiple multiqueue numbers in the case of point-to-multipoint.
The XOFF Crossbar 44 is an N.times.N serial crosspoint switch fabric which is used to communicate "Don't Send" type messages from the FSPP 16 to the TSPP 14. Each TSPP includes multiple scheduling lists 48 which have queues of cells to be transmitted for each connection. The first bit of the feedback message 30, namely XOFF, is asserted to halt transmission of request message probes 36 from a particular TSPP's scheduling list, and is thus a state control bit which puts the receiving TSPP's scheduling list in an XOFF state, meaning that this TSPP's scheduling list 48 will not use dynamic bandwidth. This TSPP's Scheduling List then remains in the XOFF state until receiving an XON message. The second bit, namely REJECT, is asserted when insufficient buffer space is available to receive the cell in the FSPP. This situation may result from the FSPP destination queue being full or from the entire pool of output buffers being exhausted. The TSPP responds to an asserted REJECT feedback message by not dequeueing the cell 24 through the data crossbar 47. An idle cell denoted by a complemented CRC, is transmitted instead. The TSPP responds to an asserted XOFF (dynamic) feedback message by modifying the TSPP's scheduling list XOFF state bits. The XOFF state bits prevent the TSPP from attempting to send a request message from that queue on that Scheduling List until notified by the FSPPs that cell buffers are available.
The XON Crossbar 46 is an N.times.N serial contention-based switch which is used to communicate "Enable Send" type messages. More particularly, the XON Crossbar is employed to communicate the XON message from the FSPP to the TSPP. When the number of buffered cells in the FSPP queue drops below an XON threshold, the XON message is sent from the FSPP to the TSPP. The XON message enables the TSPP Scheduling List to resume sending request messages.
FIG. 3 illustrates point-to-multipoint switch flow control, i.e., transmission from a single input queue 32 to multiple output queues 34. In point-to-multipoint operation the XOFF crossbar performs a logical OR function. More particularly, the XOFF crossbar performs a logical OR of the feedback messages 30 asserted by the FSPPs to provided a single feedback message. As a result, receipt of REJECT or XOFF from any FSPP will cause the single resultant feedback message to be interpreted as asserting REJECT and/or XOFF respectively. This technique limits the TSPP to transmission at the rate of the slowest destination queue. However, the technique also provides desirable contemporaneous serial transmission of cells.
In the case of point-to-multipoint transmission it will be noted that a TSPP may receive multiple XON messages. Such is true because multiple XOFFs could be set by the FSPPs, i.e., more than one FSPP can assert XOFF on a transfer request. In such a case, XON messages received when the TSPP scheduling list XOFF state is clear are ignored. For example, when multiple XON messages are sent, the TSPP ignores the XONs received after the first received XON message. In the case of multipoint-to-point transmission the XON message is sent simultaneously to all TSPPs with scheduling lists transferring to an FSPP queue.
FIG. 4 illustrates multipoint-to-point switch flow control, i.e., transmission from multiple input queues 32 to a single output queue 34. Each output queue has a threshold, and the XON message is sent when the output queue drains below that threshold. In multipoint-to-point operation, the XON threshold of the output queue is dynamically set to reserve enough buffers for each input queue to transmit to the output queue. For example, if eight queues are transmitting, the threshold is set to eight so that the output queue will free sufficient buffers to receive all eight of the cells contemporaneously in serial fashion, and thereby insuring that each queue has an opportunity to transmit.
Referring now to FIGS. 1 and 4, in the case of multipoint-to-point connections, the XON crossbar 46 is used to broadcast to all TSPPs in the switch, regardless of whether or not any of the TSPPs were transmitting to the asserting FSPP queue. For the broadcast, the multipoint topology controller 18 transmits a reverse broadcast channel number on behalf of the FSPP. The receiving multipoint topology controller then performs a reverse broadcast channel to scheduling list number lookup to determine which scheduling list 48 to enable. Any TSPPs without queues transmitting to that particular FSPP queue are unaffected by the broadcast XON message since the reverse broadcast channel number look-up entry will be marked invalid.
Referring again to FIG. 2, an additional flow control enhancement provides for the queues to be organized on an hierarchical basis with multiple individual flows 52 at each hierarchical level and the feedback message 30 from the output queues to the input queues is made on the basis of the combined flow at each of the hierarchical levels. Still another enhancement provides for the queues to be organized on an hierarchical basis with multiple individual flows at each of the hierarchical levels and the feedback message from the output queues to the input queues is made on the basis of each of the individual flows.
The Probe & XOFF communication paths operate in a pipeline fashion. First, the TSPP 14 selects an input queue 34, and information associated with that queue is used to determine output ports for transmission, i.e., a destination output queue. The bandwidth arbitrator reduces this information to a TSPP to FSPP connectivity map which is employed to control the Probe, XOFF, and data cross-points in sequence. More particularly, the FSPP multiqueue number is transmitted to the FSPP using the Probe crossbar 42. The FSPP then tests for buffer availability, and asserts REJECT and/or XOFF on the XOFF crossbar 44 if sufficient buffers are not available. The TSPP then transmits an idle cell if REJECT was asserted. If XOFF was asserted, the TSPP puts the Scheduling List into the XOFF state. If sufficient buffers are available, the TSPP transmits the cell to the FSPP output queue through the data crossbar 47.
Table 3 summarizes the policies used by the FSPP to assert REJECT and XOFF in response to requests tagged as utilizing dynamic bandwidth. The policies are based upon two relationships: the traffic type cell count in relation to the cell count limit and the queue's dynamic buffer count in relation to the buffer count limit. The traffic type cell count is a count of all cells shared by connections within a traffic type, e.g., "VBR." When the limits are not exceeded, neither REJECT nor XOFF (dynamic) is asserted. More particularly, when the traffic type cell count not greater than or equal to the limit, and the queue's dynamic buffer count is not greater than or equal to the limit, neither REJECT nor XOFF (dynamic) is asserted. When the traffic type cell count is not greater than or equal to the limit but the queue's dynamic buffer count is greater than or equal to the limit, both REJECT and XOFF (dynamic) are asserted. When the traffic type cell count is greater than or equal to the limit and the queue's dynamic buffer count is not greater than or equal to buffer limit XOFF is not asserted but REJECT is asserted. When the traffic type cell count is greater than or equal to the limit and the queue's dynamic buffer count greater than or equal to the limit both REJECT and XOFF are asserted.
Table 4 summarizes the policies used by the FSPP to assert REJECT and XOFF in response to requests tagged to use allocated bandwidth. The policies are based upon three relationships: the queue's allocated buffer-state count in relation to the buffer-state count limit, the traffic type cell count in relation to the cell count limit, and the queue's allocated buffer count in relation to the buffer count limit. Link flow control uses a buffer-state counter to indicate cells in flight. The allocated buffer-state counter is used to track cells in flight for the allocated component of a connection using link flow control. Neither XOFF nor REJECT are asserted if the queue's allocated buffer-state count is greater than or equal to the count limit, the traffic type cell count is greater than or equal to the cell count limit, and the queue's allocated buffer count is greater than or equal to the count limit. Both XOFF and REJECT are asserted if the queue's allocated buffer count is greater than or equal to the buffer count limit. If the queue's allocated buffer count is not greater than or equal to the count limit, but either the queue's allocated buffer-state count is greater than or equal to the count limit or the traffic type cell count is greater than or equal to the cell count limit then REJECT is asserted and XOFF is not asserted. In all cases, if an FSPP queue has already sent an XOFF, that queue will reassert XOFF on the next probe.
It will be understood that various changes and modifications to the above described method and apparatus may be made without departing from the inventive concepts disclosed herein. Accordingly, the present invention is not to be viewed as limited to the embodiments described herein.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed:
1. A method for controlling flow of a data unit within a network switch, comprising the steps of: receiving the data unit in the switch, the data unit being received at an input port associated with an input queue, the input queue associated with at least one input buffer; storing the data unit in the at least one input buffer associated with the input queue; forwarding a request to transmit the data unit to at least one output buffer associated with an output queue, the output queue associated with an output port; providing, by the output port in response to the request to transmit, a feedback message to the input port indicating to cease forwarding requests to transmit data units from the at least one input buffer associated with the input queue to the at least one output buffer associated with the output queue in the event that a total number of the output buffers associated with the output queue and available for data unit storage is less than a predetermined threshold; and ceasing forwarding requests to transmit data units from the at least one input buffer associated with the input queue to the at least one output buffer associated with the output queue, responsive to receiving the feedback message by the input port.
2. The method of claim 1 wherein a plurality of data units are received in a plurality of input queues and said forwarding a request step includes the further step of forwarding a request from each respective one of said plurality of input queues in receipt of at least one of said plurality of data units to respective ones of a plurality of output queues for which each respective one of said plurality of data units is destined, each request to transmit being specific to the respective input and output queues on a per transmission basis.
3. The method of claim 1 further comprising assigning the input queue and the output queue to a selected connection, whereby flow control is executed on a per connection basis.
4. The method of claim 1 wherein the feedback message includes a first signal indicating acceptance or rejection of the submitted request, the data unit being transmitted to the output queue if the first signal indicates acceptance, and not being transmitted to the output queue if the first signal indicates rejection.
5. The method of claim 4, wherein said transmitting includes transmitting the data unit to a plurality of output queues, wherein each such output queue is associated with a different output port.
6. The method of claim 4 further comprising assigning the input queue and the output queue to a selected service class, wherein each service class is associated with a transmission priority level and requests to transmit are accepted and rejected based at least in part on such priority level.
7. The method of claim 4 wherein at least one connection is established through the switch and including the further step of assigning the input queue and the output queue to a selected connection and a selected service class, wherein each service class is associated with a transmission priority level, whereby flow control is executed on a per connection, per service class basis, and requests to transmit are accepted and rejected based at least in part on such priority level.
8. The method of claim 4 wherein a subsequent request to transmit is forwarded after a delay if the first signal indicates rejection.
9. The method of claim 4 further comprising providing a second signal in the feedback message indicating either an instruction to cease forwarding requests to transmit or no operation as part of the feedback message, wherein each input queue receiving an instruction to cease forwarding requests to transmit ceases submitting requests to tranmit to such output queue having provided such instruction to cease forwarding requests to transmit.
10. The method of claim 9 wherein at least one inputted data unit is received in at least one input queue and said forwarding a request step includes the further step of forwarding a request from each respective input queue of the at least one input queue in receipt of the at least one inputted data unit to respective output queues of at least one output queue for which each respective inputted data unit of the at least one inputted data unit is destined, each request to transmit being specific to the respective input and output queues on a per transmission basis, and including, in the case of transmission from a single input queue to a plurality of output queues, the further step of performing a logical OR operation on the respective first and second signals of the feedback messages from the at least one output queue such that transmission from a single input queue to a plurality of output queues is contemporaneous.
11. The method of claim 10 including, in the case of transmission from a plurality of input queues to a particular output queue, the further step of setting the threshold to provide sufficient buffers for contemporaneous receipt of data units from the plurality of input queues.
12. The method of claim 9 including the further step of providing a third signal in a subsequent feedback message to countermand the instruction to cease forwarding requests to transmit by re-enabling the input queue to forward requests to transmit to the output queue when sufficient buffers become available for receipt of a predetermined number of data units by said output queue.
13. The method of claim 12 including the further step of providing the third signal upon dequeueing a data unit from the one of the at least one output queue.
14. The method of claim 12 including providing the third signal when the total number of output buffers available for data unit storage and associated with the output queue is greater than the predetermined threshold.
15. The method of claim 12 including the further step of providing the third signal to the input queue after passage of a predetermined period of time following transmission of the second signal.
16. The method of claim 12 including the further step of providing the third signal to the input queue on a periodic basis.
17. The method of claim 12 including the further step of providing the third signal from the output queue to a plurality of input queues.
18. The method of claim 1 including the further step of organizing the input buffers and output buffers into a hierarchy of levels with multiple individual flows of data units at each hierarchical level, wherein feedback messages are provided for each level based on combined flow at the respective level.
19. The method of claim 1 including the further step of organizing the input buffers and output buffers into a hierarchy of levels with multiple individual flows of data units at each hierarchical level, wherein feedback messages are provided for each individual flow.
20. The method of claim 1 wherein the request to transmit is a request to transmit utilizing dynamic bandwidth.
21. The method of claim 20, wherein the feedback message indicates to cease forwarding requests to transmit utilizing dynamic bandwidth to the output queue, and wherein the input queue, responsive to receiving the feedback message, ceases forwarding requests to transmit utilizing dynamic bandwidth to the output queue.
22. The method of claim 1 wherein the request to transmit is a request to transmit utilizing allocated bandwidth.
23. The method of claim 22, wherein the feedback message indicates to cease forwarding requests to transmit utilizing allocated bandwidth to the output queue, and wherein the input queue, responsive to receiving the feedback message, ceases forwarding requests to transmit utilizing allocated bandwidth to the output queue.
24. A network switch for controlling flow of at least one data unit within a telecommunications network, comprising: at least one input port for receiving the at least one data unit into the switch; at least one output port for transmitting the at least one data unit out of said switch; at least one input buffer queue associated with said at least one input port for enqueuing the at least one data unit received at the at least one input port; at least one output buffer queue associated with said at least one input buffer queue for receiving and temporarily storing the at least one data unit from said at least one input buffer queue; at least one transmission request generator operative to generate one or more requests for permission to transmit the at least one data unit from said at least one input buffer queue to said at least one output buffer queue; at least one feedback message generator operative to provide at least one feedback message to said at least one input buffer queue, said at least one feedback message including a signal having first and second states, said first and second states respectively indicating no operation and an instruction to cease sending requests for permission to transmit, and wherein each of said at least one input buffer queue receiving the signal in the second state from one or more of said at least one output buffer queue ceases submitting requests to transmit to said one or more of said at least one output buffer queue.
25. The switch of claim 24 wherein each one of said at least one output port includes one of said at least one feedback message generator.
26. The switch of claim 24 wherein a plurality of connections are established within the switch and each such connection utilizes one of said at least one input buffer queue and one of said at least one output buffer queue, whereby flow control is executed on a per connection basis.
27. The switch of claim 24 wherein one or more of said at least one input buffer queue and one or more of said at least one output buffer queue are assigned to a selected service class, whereby flow control is executed on a per service class basis.
28. The switch of claim 24 wherein a plurality of connections are established within the switch and each of said at least one input buffer queue and each of said at least one output buffer queue are assigned to a respective one of said plurality of connections and a selected service class, whereby flow control is executed on a per connection, per service class basis.
29. The switch of claim 24 including a logic circuit which, in the case of transmission from a single one of said at least one input buffer queue to a plurality of said at least one output buffer queue, performs a logical OR operation on the respective first and second signals of the feedback messages from said plurality of said at least one output buffer queue such that transmission from the single one of said at least one input buffer queue to the plurality of said at least one output buffer queue is serially contemporaneous.
30. The switch of claim 25 wherein, in the case of transmission from a plurality of said at least one input buffer queue to a particular one of said at least one output buffer queue, a dynamically adjustable threshold at which the first signal in the second state is provided in connection with the particular one of said at least one output buffer queue is increased in order to provide sufficient buffers for contemporaneous receipt of the at least one data unit from the plurality of said at least one input buffer queue.
31. The switch of claim 20 wherein said at least one input buffer queue and said at least one output buffer queue are each arranged in a hierarchy of levels with multiple individual flows of data units at each hierarchical level, said at least one feedback message being provided for each level based on combined flow at the respective level.
32. The switch of claim 24 wherein said at least one input buffer queue and said at least one output buffer queue are each arranged into a hierarchy of levels with multiple individual flows of data units at each hierarchical level, an individual one of said at least one feedback message being provided for each individual flow.
33. The network switch of claim 24, said at least one feedback message further comprising a second signal having a first state and a second state, wherein said first state indicates a grant of permission to transmit the at least one data unit from one or more of the at least one input buffer queue where the data unit is enqueued to one or more of said at least one output buffer queue and said second state indicates a denial of permission to transmit the enqueued data unit from the one or more of the at least one input buffer queue to said one or more of said at least one output buffer queue.
34. The switch of claim 32 wherein said at least one feedback message generator provides said at least one feedback message in response to said one or more requests for permission to transmit.
35. The switch of claim 32 wherein the at least one data unit is transmitted if the second signal indicates that permission to transmit is granted and the at least one data unit is not immediately transmitted if the second signal indicates that permission to transmit is denied.
36. The switch of claim 33 wherein a third signal is provided in said at least one feedback message to countermand the first signal in the second state by re-enabling one or more of said at least one input buffer queue to forward permission requesting signals to said one or more of said at least one output buffer queue.
37. The switch of claim 36 wherein said third signal is provided upon dequeueing a data unit from said one or more of said at least one output buffer queue.
38. The switch of claim 36 wherein a threshold is set in said one or more of said at least one output buffer queue, said third signal being provided when a total number of output buffers available to store said at least one data unit in said one or more of said at least one output buffer queue is greater than said threshold.
39. The switch of claim 31 wherein said third signal is provided to said one or more of said at least one input buffer queue after passage of a predetermined period of time following receipt of said second signal in the second state.
40. The switch of claim 31 wherein said third signal is provided to said one or more of said at least one input buffer queue on a regular time basis.
41. The switch of claim 31 wherein said third signal is provided from said one or more of said at least one output buffer queue to a plurality of said at least one input buffer queue.
42. A method for controlling flow of at least one inputted cell within a network switch having a plurality of input buffers associated with at least one input queue and a plurality of output buffers associated with at least one output queue, the method comprising the steps of: receiving the at least one inputted cell in the switch, the cell being received in the input queue of the input memory; forwarding a request to transmit the at least one inputted cell to one of said at least one output queue; and asserting, when a traffic type cell count of all cells shared by all existing connections is not greater than or equal to a first limit and a dynamic buffer count associated with one of said at least one output queue is greater than or equal to a second limit, both a first signal denying said request and a second signal causing cessation of forwarding requests to transmit to the one output queue.
43. The method of claim 42 including the further step of, when the traffic type cell count is not greater than or equal to the first limit and the dynamic buffer count associated with the one output queue is not greater than or equal to the second limit, asserting neither the first signal nor the second signal.
44. The method of claim 43 including the further step of, when the traffic type cell count is greater than or equal to the first limit and the dynamic buffer count associated with the one output queue is not greater than or equal to the second limit, not asserting the second signal and asserting the first signal.
45. The method of claim 44 including the further step of, when the traffic type cell count is greater than or equal to the first limit and the dynamic buffer count associated with the one output queue is greater than or equal to the second limit, asserting both the first signal and the second signal.
46. The method of claim 45 including the further step of, asserting neither the first signal nor the second signal when an allocated buffer-state count associated with the one output queue is greater than or equal to a second imit, the traffic type cell count is greater than or equal to the first limit, and an allocated buffer count is greater than or equal to a third limit.
47. The method of claim 46 including the further step of asserting both the first signal and the second signal when the allocated buffer count is greater than or equal to the third limit.
48. The method of claim 47 including the further step of, when the allocated buffer count is not greater than or equal to the third limit, but either the allocated buffer-state count is greater than or equal to the second limit or the traffic type cell count is greater than or equal to the first limit, asserting the second signal and not asserting the first signal.
49. The method of claim 48 including the further step of, when an output queue has already asserted the first signal, reasserting the first signal on a subsequent probe.
50. A system for controlling flow of a received data unit in a network switch, comprising: an input queue associated with a receive buffer for storing the received data unit, the input queue associated with an input port, a first traffic type, and a first connection; a plurality of traffic type output queues associated with an output port, each one of the plurality of traffic type output queues further associated with a respective traffic type, each one of the traffic type output queues including a plurality of connection specific output queues; and a feedback message generator operative to determine whether there is insufficient buffer space in one of the connection specific output queues associated with the first connection included in one of the traffic type output queues associated with the first traffic type and the first output port, the feedback message generator further operative to provide a first feedback message to the input queue responsive to determining there is insufficient buffer space in the one of the connection specific output queues associated with the first connection included in the one of the traffic type output queues associated with the first traffic type and the first output port.
51. The system of claim 50, wherein the first feedback message denies a request to transmit the received data unit.
52. The system of claim 50 wherein the input queue is one of a plurality of input queues associated with the input port.
53. The system of claim 50 wherein the first traffic type is variable bit rate.
54. The system of claim 50 wherein the first traffic type is constant bit rate.
55. The system of claim 50 wherein the first traffic type is available bit rate.
56. The system of claim 50 wherein said feedback message generator is further operative to provide a second feedback message to the input queue responsive to determining there is sufficient buffer space in the one of the connection specific output queues associated with the first connection.
57. The system of claim 56, wherein the second feedback message enables transmission of the received data unit to the one of the connection specific output queues associated with the first connection.
58. A method for controlling flow of a data unit within a network switch, comprising: receiving the data unit in the switch, the data unit being received at an input port associated with an input queue, the input queue associated with at least one input buffer; storing the data unit in the at least one input buffer associated with the input queue; at least at some times, forwarding a plurality of requests to transmit the data unit from the input port to a plurality of output queues, the plurality of output queues associated with a respective plurality of output ports; providing, by at least one of the respective plurality of output ports in response to the plurality of requests to transmit, a feedback message to the input port denying the request to transmit the data unit in the event that a total number of the output buffers associated with the respective output queue and available for data unit storage is less than are needed to store the data unit; and delaying transmission of the data unit from the input queue to the respective plurality of output ports in the event that the at least one of the output ports provides the feedback message denying the request to transmit the data unit.
59. The method of claim 58 further comprising forwarding the data unit to each of the plurality of output queues in the event that none of the to plurality of output ports provide the feedback message denying the request to transmit.
60. The method of claim 58 wherein the feedback message includes a bit indicating whether the request to transmit is granted or denied, and further comprising logically ORing the bit from a plurality of feedback messages to determine whether transmission of the data unit should be delayed.
Patent Citations (249)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3804991 | 1974-04-01 | Hammond et al. | |
| US3974343 | 1976-08-01 | Cheney et al. | |
| US4069399 | 1978-01-01 | Barrett et al. | |
| US4603382 | 1986-07-01 | Cole et al. | |
| US4715030 | 1987-12-01 | Koch et al. | |
| US4727537 | 1988-02-01 | Nichols | |
| US4737953 | 1988-04-01 | Koch et al. | |
| US4797881 | 1989-01-01 | Ben-Artzi | |
| US4821034 | 1989-04-01 | Anderson et al. | |
| US4837761 | 1989-06-01 | Isono et al. | |
| US4849968 | 1989-07-01 | Turner | |
| US4870641 | 1989-09-01 | Pattavina | |
| US4872159 | 1989-10-01 | Hemmady et al. | |
| US4872160 | 1989-10-01 | Hemmady et al. | |
| US4878216 | 1989-10-01 | Yunoki | |
| US4893302 | 1990-01-01 | Hemmady et al. | |
| US4893307 | 1990-01-01 | McKay et al. | |
| US4894824 | 1990-01-01 | Hemmady et al. | |
| US4897841 | 1990-01-01 | Gang, Jr. | |
| US4899333 | 1990-02-01 | Roediger | |
| US4920531 | 1990-04-01 | Isono et al. | |
| US4922503 | 1990-05-01 | Leone | |
| US4933938 | 1990-06-01 | Sheehy | |
| US4947390 | 1990-08-01 | Sheehy | |
| US4953157 | 1990-08-01 | Franklin et al. | |
| US4956839 | 1990-09-01 | Torii et al. | |
| US4958341 | 1990-09-01 | Hemmady et al. | |
| US4979100 | 1990-12-01 | Makris et al. | |
| US4993018 | 1991-02-01 | Hajikano et al. | |
| US5021949 | 1991-06-01 | Morten et al. | |
| US5029164 | 1991-07-01 | Goldstein et al. | |
| US5060228 | 1991-10-01 | Tsutsui et al. | |
| US5067123 | 1991-11-01 | Hyodo et al. | |
| US5070498 | 1991-12-01 | Kakuma et al. | |
| US5083269 | 1992-01-01 | Syobatake et al. | |
| US5084867 | 1992-01-01 | Tachibana et al. | |
| US5084871 | 1992-01-01 | Carn et al. | |
| US5090011 | 1992-02-01 | Fukuta et al. | |
| US5090024 | 1992-02-01 | Vander Mey et al. | |
| US5093912 | 1992-03-01 | Dong et al. | |
| US5115429 | 1992-05-01 | Hluchyj et al. | |
| US5119369 | 1992-06-01 | Tanabe et al. | |
| US5119372 | 1992-06-01 | Verbeek | |
| US5128932 | 1992-07-01 | Li | |
| US5130975 | 1992-07-01 | Akata | |
| US5130982 | 1992-07-01 | Ash et al. | |
| US5132966 | 1992-07-01 | Hayano et al. | |
| US5146474 | 1992-09-01 | Nagler et al. | |
| US5146560 | 1992-09-01 | Goldberg et al. | |
| US5150358 | 1992-09-01 | Punj et al. | |
| US5151897 | 1992-09-01 | Suzuki | |
| US5157657 | 1992-10-01 | Potter et al. | |
| US5163045 | 1992-11-01 | Caram et al. | |
| US5163046 | 1992-11-01 | Hahne et al. | |
| US5179556 | 1993-01-01 | Turner | |
| US5179558 | 1993-01-01 | Thacker et al. | |
| US5185743 | 1993-02-01 | Murayama et al. | |
| US5191582 | 1993-03-01 | Upp | |
| US5191652 | 1993-03-01 | Dias et al. | |
| US5193151 | 1993-03-01 | Jain | |
| US5197067 | 1993-03-01 | Fujimoto et al. | |
| US5198808 | 1993-03-01 | Kudo | |
| US5199027 | 1993-03-01 | Barri | |
| US5239539 | 1993-08-01 | Uchida et al. | |
| US5253247 | 1993-10-01 | Hirose et al. | |
| US5253248 | 1993-10-01 | Dravida et al. | |
| US5255264 | 1993-10-01 | Cotton et al. | |
| US5255266 | 1993-10-01 | Watanabe et al. | |
| US5257311 | 1993-10-01 | Naito et al. | |
| US5258979 | 1993-11-01 | Oamuro et al. | |
| US5265088 | 1993-11-01 | Takigawa et al. | |
| US5267232 | 1993-11-01 | Katsube et al. | |
| US5268897 | 1993-12-01 | Komine et al. | |
| US5271010 | 1993-12-01 | Miyake et al. | |
| US5272697 | 1993-12-01 | Fraser et al. | |
| US5274641 | 1993-12-01 | Shobatake et al. | |
| US5274768 | 1993-12-01 | Traw et al. | |
| US5280469 | 1994-01-01 | Taniguchi et al. | |
| US5280470 | 1994-01-01 | Buhrke et al. | |
| US5282201 | 1994-01-01 | Frank et al. | |
| US5283788 | 1994-02-01 | Morita et al. | |
| US5285445 | 1994-02-01 | Lehnert et al. | |
| US5285446 | 1994-02-01 | Yonehara | |
| US5287349 | 1994-02-01 | Hyodo et al. | |
| US5287535 | 1994-02-01 | Sakagawa et al. | |
| US5289462 | 1994-02-01 | Ahmadi et al. | |
| US5289463 | 1994-02-01 | Mobasser | |
| US5289470 | 1994-02-01 | Chang et al. | |
| US5291481 | 1994-03-01 | Doshi et al. | |
| US5291482 | 1994-03-01 | McHarg et al. | |
| US5295134 | 1994-03-01 | Yoshimura et al. | |
| US5301055 | 1994-04-01 | Bagchi et al. | |
| US5301184 | 1994-04-01 | Uriu et al. | |
| US5301190 | 1994-04-01 | Tsukuda et al. | |
| US5301193 | 1994-04-01 | Toyofuku et al. | |
| US5303232 | 1994-04-01 | Faulk, Jr. | |
| US5305311 | 1994-04-01 | Lyles | |
| US5309431 | 1994-05-01 | Tominaga et al. | |
| US5309438 | 1994-05-01 | Nakajima | |
| US5311586 | 1994-05-01 | Bogart et al. | |
| US5313454 | 1994-05-01 | Bustini et al. | |
| US5313458 | 1994-05-01 | Suzuki | |
| US5315586 | 1994-05-01 | Charvillat | |
| US5319638 | 1994-06-01 | Lin | |
| US5321695 | 1994-06-01 | Proctor et al. | |
| US5323389 | 1994-06-01 | Bitz et al. | |
| US5333131 | 1994-07-01 | Tanabe et al. | |
| US5333134 | 1994-07-01 | Ishibashi et al. | |
| US5335222 | 1994-08-01 | Kamoi et al. | |
| US5335325 | 1994-08-01 | Frank et al. | |
| US5339310 | 1994-08-01 | Taniguchi | |
| US5339317 | 1994-08-01 | Tanaka et al. | |
| US5339318 | 1994-08-01 | Tanaka et al. | |
| US5341366 | 1994-08-01 | Soumiya et al. | |
| US5341373 | 1994-08-01 | Ishibashi et al. | |
| US5341376 | 1994-08-01 | Yamashita | |
| US5345229 | 1994-09-01 | Olnowich et al. | |
| US5350906 | 1994-09-01 | Brody et al. | |
| US5355372 | 1994-10-01 | Sehgupta et al. | |
| US5357506 | 1994-10-01 | Sugawara | |
| US5357507 | 1994-10-01 | Hughes et al. | |
| US5357508 | 1994-10-01 | Le Boudec et al. | |
| US5357510 | 1994-10-01 | Norizuki et al. | |
| US5359600 | 1994-10-01 | Ueda et al. | |
| US5361251 | 1994-11-01 | Aihara et al. | |
| US5361372 | 1994-11-01 | Rege et al. | |
| US5363433 | 1994-11-01 | Isono | |
| US5365514 | 1994-11-01 | Hershey et al. | |
| US5371893 | 1994-12-01 | Price et al. | |
| US5373504 | 1994-12-01 | Tanaka et al. | |
| US5375117 | 1994-12-01 | Morita et al. | |
| US5377262 | 1994-12-01 | Bales et al. | |
| US5377327 | 1994-12-01 | Jain et al. | |
| US5379297 | 1995-01-01 | Glover et al. | |
| US5379418 | 1995-01-01 | Shimazaki et al. | |
| US5390170 | 1995-02-01 | Sawant et al. | |
| US5390175 | 1995-02-01 | Hiller et al. | |
| US5392280 | 1995-02-01 | Zheng | |
| US5392402 | 1995-02-01 | Robrock, II | |
| US5394396 | 1995-02-01 | Yoshimura et al. | |
| US5394397 | 1995-02-01 | Yanagi et al. | |
| US5398235 | 1995-03-01 | Tsuzuki et al. | |
| US5400337 | 1995-03-01 | Munter | |
| US5402415 | 1995-03-01 | Turner | |
| US5412648 | 1995-05-01 | Fan | |
| US5414703 | 1995-05-01 | Sakaue et al. | |
| US5420858 | 1995-05-01 | Marshall et al. | |
| US5420988 | 1995-05-01 | Elliott | |
| US5422879 | 1995-06-01 | Parsons et al. | |
| US5425021 | 1995-06-01 | Derby et al. | |
| US5425026 | 1995-06-01 | Mori | |
| US5432713 | 1995-07-01 | Takeo et al. | |
| US5432784 | 1995-07-01 | Ozveren | |
| US5432785 | 1995-07-01 | Ahmad et al. | |
| US5432908 | 1995-07-01 | Heddes et al. | |
| US5436886 | 1995-07-01 | McGill | |
| US5436893 | 1995-07-01 | Barnett | |
| US5440547 | 1995-08-01 | Easki et al. | |
| US5444702 | 1995-08-01 | Burnett et al. | |
| US5446733 | 1995-08-01 | Tsuruoka | |
| US5446737 | 1995-08-01 | Cidon et al. | |
| US5446738 | 1995-08-01 | Kim et al. | |
| US5448559 | 1995-09-01 | Hayter et al. | |
| US5450406 | 1995-09-01 | Esaki et al. | |
| US5452296 | 1995-09-01 | Shimizu | |
| US5455820 | 1995-10-01 | Yamada | |
| US5455825 | 1995-10-01 | Lauer et al. | |
| US5457687 | 1995-10-01 | Newman | |
| US5459743 | 1995-10-01 | Fukuda et al. | |
| US5461611 | 1995-10-01 | Drake, Jr. et al. | |
| US5463620 | 1995-10-01 | Sriram | |
| US5465331 | 1995-11-01 | Yang et al. | |
| US5475679 | 1995-12-01 | Munter | |
| US5479401 | 1995-12-01 | Bitz et al. | |
| US5479402 | 1995-12-01 | Hata et al. | |
| US5483526 | 1996-01-01 | Ben-Nun et al. | |
| US5485453 | 1996-01-01 | Wahlman et al. | |
| US5485455 | 1996-01-01 | Dobbins et al. | |
| US5487063 | 1996-01-01 | Kakuma et al. | |
| US5488606 | 1996-01-01 | Kakuma et al. | |
| US5491691 | 1996-02-01 | Shtayer et al. | |
| US5491694 | 1996-02-01 | Oliver et al. | |
| US5493566 | 1996-02-01 | Ljungberg et al. | |
| US5497369 | 1996-03-01 | Wainwright | |
| US5499238 | 1996-03-01 | Shon | |
| US5504741 | 1996-04-01 | Yamanaka et al. | |
| US5504742 | 1996-04-01 | Kakuma et al. | |
| US5506834 | 1996-04-01 | Sekihata et al. | |
| US5506839 | 1996-04-01 | Hatta | |
| US5506956 | 1996-04-01 | Cohen | |
| US5509001 | 1996-04-01 | Tachibana et al. | |
| US5509007 | 1996-04-01 | Takashima et al. | |
| US5513134 | 1996-04-01 | Cooperman et al. | |
| US5513178 | 1996-04-01 | Tanaka | |
| US5513180 | 1996-04-01 | Miyake et al. | |
| US5515359 | 1996-05-01 | Zheng | |
| US5517495 | 1996-05-01 | Lund et al. | |
| US5519690 | 1996-05-01 | Suzuka et al. | |
| US5521905 | 1996-05-01 | Oda et al. | |
| US5521915 | 1996-05-01 | Dieudonne et al. | |
| US5521916 | 1996-05-01 | Choudhury et al. | |
| US5521917 | 1996-05-01 | Watanabe et al. | |
| US5521923 | 1996-05-01 | Willman et al. | |
| US5523999 | 1996-06-01 | Takano et al. | |
| US5524113 | 1996-06-01 | Gaddis | |
| US5526344 | 1996-06-01 | Diaz et al. | |
| US5528588 | 1996-06-01 | Bennett et al. | |
| US5528590 | 1996-06-01 | Iidaka et al. | |
| US5528591 | 1996-06-01 | Lauer | |
| US5530695 | 1996-06-01 | Dighe et al. | |
| US5533009 | 1996-07-01 | Chen | |
| US5533020 | 1996-07-01 | Byrn et al. | |
| US5535196 | 1996-07-01 | Aihara et al. | |
| US5535197 | 1996-07-01 | Cotton | |
| US5537394 | 1996-07-01 | Abe et al. | |
| US5541912 | 1996-07-01 | Choudhury et al. | |
| US5544168 | 1996-08-01 | Jeffrey et al. | |
| US5544169 | 1996-08-01 | Norizuki et al. | |
| US5544170 | 1996-08-01 | Kasahara | |
| US5546389 | 1996-08-01 | Wippenback et al. | |
| US5546391 | 1996-08-01 | Hochschild et al. | |
| US5546392 | 1996-08-01 | Boal et al. | |
| US5550815 | 1996-08-01 | Lloonan et al. | |
| US5550821 | 1996-08-01 | Akiyoshi | |
| US5550823 | 1996-08-01 | Irie et al. | |
| US5553057 | 1996-09-01 | Nakayama | |
| US5553068 | 1996-09-01 | Aso et al. | |
| US5555243 | 1996-09-01 | Kakuma et al. | |
| US5555265 | 1996-09-01 | Kakuma et al. | |
| US5557607 | 1996-09-01 | Holden | |
| US5568479 | 1996-10-01 | Watanabe et al. | |
| US5570361 | 1996-10-01 | Norizuki et al. | |
| US5570362 | 1996-10-01 | Nishimura | |
| US5572522 | 1996-11-01 | Calamvokis et al. | |
| US5577032 | 1996-11-01 | Sone et al. | |
| US5577035 | 1996-11-01 | Hayter et al. | |
| US5583857 | 1996-12-01 | Soumiya et al. | |
| US5583858 | 1996-12-01 | Hanaoka | |
| US5583861 | 1996-12-01 | Holden | |
| US5590132 | 1996-12-01 | Ishibashi et al. | |
| US5602829 | 1997-02-01 | Nie et al. | |
| US5610913 | 1997-03-01 | Tomonaga et al. | |
| US5623405 | 1997-04-01 | Isono | |
| US5625846 | 1997-04-01 | Kobayakawa et al. | |
| US5633861 | 1997-05-01 | Hanson et al. | |
| US5636365 | 1997-06-01 | Tanioka | |
| US5666360 | 1997-09-01 | Chen et al. | |
| US5724351 | 1998-03-01 | Chao et al. | |
| JPX484943 | 1992-03-01 |
Non-Patent Literature (17)
- Head of Line Arbitration in ATM Switches with Input-Output Buffering and Backpressure Control. By Hosein F. Badran and H. T. Mouftah, GLOBECOM '91, pp. 0347-0351.
- H.T. Kung and K. Chang, Receiver-Oriented Adaptive Buffer Allocation in Credit-Based Flow Control for ATM Networks, Proceedings of INFOCOM '95, Apr. 2-6, 1995, pp. 1-14.
- H.T. Kung, et al., Credit-Based Flow Control for ATM Networks: Credit Update Protocol, Adaptive Credit Allocation and Statistical Multiplexing, Proceedings of ACM SIGCOMM '94 Symposium on Communications Architectures Protocols and Applications, Aug. 31-Sep. 2, 1994, pp. 1-14.
- An Ascom Timeplex White Paper, Meeting Critical Requirements with Scalable Enterprise Networking Solutions Based on a Unified ATM Foundation, pp. 1-12, Apr. 1994 -Apr. 1995?.
- Douglas H. Hunt, ATM Traffic Management -- Another Perspective, Business Communications Review, Jul. 1994.
- Richard Bubenik et al., Leaf Initiated Join Extensions, Technical Committee, Signalling Subworking Group, ATM Forum/94-0325R1, Jul. 1, 1994.
- Douglas H. Hunt et al., Flow Controlled Virtual Connections Proposal for ATM Traffic Management (Revision R2) Traffic Management Subworking Group, ATM Forum/94-0632R2, Aug. 1994.
- Flavio Bonomi et al., The Rate-Based Flow Control Framework for the Available Bit Rate ATM Service, IEEE Network, Mar./Apr. 1995, pp. 25-39.
- R. Jain, Myths About Congestion Management in High Speed Networks, Internetworking Research and Experience, vol. 3, 101-113 (1992).
- Douglas H. Hunt et al., Credit-Based FCVC Proposal for ATM Traffic Management (Revision R1), ATM Forum Technical Committee Traffic Management Subworking Group, ATM Forum/94-0168R1, Apr. 28, 1994.
- Douglas H. Hunt et al., Action Item Status for Credit-Based FCVC Proposal, ATM Forum Technical Committee Traffic Management Subworking Group, ATM Forum/94-0439, Apr. 28, 1994.
- Timothy P. Donahue et al., Arguments in Favor of Continuing Phase 1 as the Initial ATM Forum P-NNI Routing Protocol Implementation, ATM Forum Technical Committee, ATM Forum/94-0460, Apr. 28, 1994.
- Richard Bubenick et al., Leaf Initiated Join Extensions, Technical Committee, Signalling Subworking Group, ATM Forum/94-0325, Apr. 28, 1994.
- Rob Coltun et al., PRP: A P-NNI Routing Protocol Proposal, ATM Forum Technical Committee ATM Forum/94-0492, Apr. 28, 1994.
- Richard Bubenik et al., Leaf Initiated Join Extensions, ATM Forum Technical Committee, Signalling Subworking Group, ATM Forum 94-0325, Apr. 28, 1994.
- Richard Bubenik et al., Requirements For Phase 2 Signaling Protocol, ATM Forum Technical Committee, Signalling Subworking Group, ATM Forum 94-1078, Jan. 1, 1994.
- SITA, ATM RFP: C-Overall Technical Requirements, Sep. 1994.