US 6,798,776 B1Grant
Method for traffic management, traffic prioritization, access control, and packet forwarding in a datagram computer network
Issue Date:2004-09-28
•30 Claims
Abstract
A method and apparatus for an enhanced datagram packet switched computer network is disclosed. The invention processes network datagram packets in network devices as separate flows, based on the source-destination address pair contained in the datagram packet itself. As a result, the network can control and manage each flow of datagrams in a segregated fashion. The processing steps that can be specified for each flow include traffic management, flow control, packet forwarding, access control, and other network management functions. The ability to control network traffic on a per flow basis allows for the efficient handling of a wide range and a large variety of network traffic, as is typical in large-scale computer networks, including video and multimedia type traffic. The amount of buffer resources and bandwidth resources assigned to each flow can be individually controlled by network management. In the dynamic operation of the network, these resources can be varied based on actual network traffic loading and congestion encountered.
Metadata
Assignee
- Cisco Technology, Inc.
Inventors
- David R. Cheriton
- Andreas V. Bechtolsheim
Application Information
Application Number:US 09/482,940
Filing Date:2000-01-14
Priority Date:1995-12-29
Art Unit:7
Classifications
IPC:
H04L 1256
Field of Search:
3703923703953137039532370396370397370398370399370465709238709242
Patent Drawings
This patent does not have any drawings.
Description
[0002] This application is a Continuation of application Ser. No. 08/581,134 Filed on Dec. 29, 1995, now U.S. Pat No. 6,091,725.
Cross-Reference to the Appendix Containing Software
[0003] Appendix A, which is a part of the present disclosure, lists the computer programs and related data in one embodiment of this invention. This listing of computer programs contains material which is subject to copyright protection The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the present disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
Background of the Invention
[0004] 1. Field of Invention
[0005] The present invention relates to the field of computer networks. More particularly, the present invention relates to the field of computer networks which are based on datagram packet switching.
[0006] 2. Background of the Invention
[0007] Computer Networks are used to interconnect computers and peripherals to allow them to exchange and share data such as files, electronic mail, databases, multimedia/video, and other data.
[0008] Packet Switching
[0009] Nearly all computer networks use packet switching, which divides longer units of data transfer into smaller packets which are sent separately over the network. This allows each packet to be processed independently from another packet without having to wait for the entire data transfer to be completed. It also enables communications between a plurality of computer systems to be intermixed on one network. Host interfaces connect the computer systems to a network allowing each, computer system to act as the source and destination of packets on the network.
[0010] A first key issue in packet switched networks is addressing. The addressing in packet switched networks is conventionally performed by one of two approaches, known as virtual circuit packet switching or datagram packet switching.
[0011] Virtual Circuit Packet Switching
[0012] In the virtual circuit approach, before any data can be transmitted, a virtual circuit must be first established along the path from the source to the destination in advance of any communication. After the virtual circuit is setup, the source can then send packets to the destination. Each packet in the virtual circuit approach has a virtual circuit identifier, which is used to switch the packet along the path from source to the destination.
[0013] The virtual circuit approach reduces the size of the identification required in each packet header. It also allows additional information about the packet handling to be established as part of the virtual circuit setup operation. Another claimed benefit is that forwarding and switching of virtual circuit packets can be made more efficient because of the virtual setup process. However, the virtual circuit approach incurs the cost of delay to setup the virtual circuit before sending any data, and it incurs the cost of maintaining the virtual circuit state in each network device along the virtual circuit path, even if a virtual circuit is idle. Also, in practice the memory space for virtual circuit state in network devices has limited the number of circuits that are available, which complicates the behavior of network nodes that need to create virtual circuits to communicate.
[0014] Datagram Packet Switching
[0015] In the datagram approach, each datagram packet is a self-contained unit of data delivery. A typical datagram packet includes a globally unique source address, a globally unique destination address, a protocol type field, a data field, and a cyclic redundancy checksum (“CRC”) to insure data integrity.
[0016] Datagrams can be sent without prior arrangement with the network, i.e. without setting up a virtual circuit or connection. Each network device receiving a datagram packet examines the destination address included in the datagram packet and makes a local decision whether to accept, ignore, or forward this packet.
[0017] Various conventional network devices learn information from observing datagram packet traffic in data networks. For example, a conventional network switch device that interconnects multiple network segments can “learn” the location of network stations connected to its ports by monitoring the source address of packets received on its ports. After it has associated a station address with a certain port, the network switch can then forward datagram packets addressed to that station to that port. In this type of device, the datagram source address is used to learn the location of a station on the network, whereas the forwarding decision is made on basis of the datagram destination address alone.
[0018] Datagram packet switching has the advantage that it avoids the overhead and cost of setting up virtual circuit connection in network devices. However, it incurs the expense of transmitting a larger packet header than required for virtual circuit switching, and it incurs the cost for processing this larger packet header in every network device to which it is delivered. Also, there is no virtual circuit setup process to establish additional information for datagram packet processing. Another disadvantage of datagram packet switching is that it is difficult to control packet flow to the same degree as with virtual circuits because there is, in the conventional case, no state in the network devices associated with the traffic flow.
[0019] The datagram packet switching approach has been extensively used in shared media local area networks. Shared media networks provide for a multiplicity of stations directly connected to the network, with the shared media providing direct access from any transmitter to any receiver. Since the receivers need to be able to distinguish packets addressed specifically to them, each receiver needs to have a unique address. In addition, since the unit of access to the shared medium is one packet, each packet needs to contain the unique address capable to identify the receiver. As a result, all commonly used local area networks are based on datagram packet switching and have no provisions for virtual circuit setup.
[0020] Media Access Control Protocol
[0021] The network access mechanism in shared media local area network will now be further described. This function, commonly known as the media access control or MAC protocol, defines how to arbitrate access among multiple stations that desire to use the network. Individual stations connected to the network have to adhere to the MAC protocol in order to allow proper network operation.
[0022] A number of different media access control protocols exist. The MAC protocol, in conjunction with the exact packet format, is the essence of what defines a local area network standard. The following is a brief overview of local area network standards that are in wide use today.
[0023] The most widely used local area network is commonly known as Ethernet and employs an access protocol referred to as Carrier Sense Multiple Access with Collision Detection (CSMA/CD). [see U.S. Pat. No. 4,063,220, issued Dec. 13, 1977, for a Multipoint Data Communication System with Collision Detection, Inventors Metcalfe, Boggs, Thacker, and Lampson]. The current definition of the Ethernet CSMA/CD protocol is defined in IEEE Standard 802.3, published by the Institute of Electrical and Electronics Engineers, 345 East 45th Street, New York, N.Y. 10017. The Ethernet standard specifies a data transmission rate of 10 or 100 Megabits/second.
[0024] Another widely used local area network standard is Tokenring, also known as IEEE Std 802.5, transmitting at a speed of 4 or 16 Mbits/sec and FDDI or Fiber-Distributed-Data-Interface which sends data at a speed of 100 Mbits/sec. Both Tokenring and FDDI are based on a circulating token granting access to the network, although their respective datagram packet formats and other operating aspects are unique to each standard.
[0025] What is common to all these media access control mechanisms is that they do not include provisions for virtual circuit setup and have no provisions to specify attributes that relate to virtual circuits, such as traffic management or flow control for specific connections. This limits the ability of conventional local area networks to accommodate higher level network functions or to support virtual connection oriented traffic mechanisms.
[0026] Devices for Interconnecting Local Area Networks
[0027] Another key issue with datagram packet switched networks is how to interconnect individual network segments into larger networks. The size and usage of datagram packet switched networks has grown much beyond what was envisioned when these networks were designed. Devices such as bridges, switches, and routers, have been used to interconnect individual LAN segments into larger networks, but each have their own set of problems in scaling to higher performance.
[0028] Bridges forward datagram packets between network segments by learning the location of the devices on the network by observing the source address contained in datagram packets passing by. Once the bridge has learned which network device ia located on which network segment, it can then forward datagram packets addressed to that network device to the appropriate network segment. One of the limitations of bridges is that they do not filter traffic beyond the data link level.
[0029] Switches are basically multi-port network bridges that can forward datagram packets among a multiplicity of network ports. Frequently, switches provide additional capabilities for assisting with network management, including traffic filtering and segmenting networks into virtual LANs. As in the case of bridges, switches have to forward broadcasts to all ports configured into one virtual LAN. In addition, conventional switches cannot provide fair service or priority service to individual traffic flows, and they require significant amount of memory to avoid dropping packets in the case of network congestion.
[0030] Routers also interconnect several network segments, but they operate primarily at the network protocol layer, rather than at the datagram packet layer. Routers participate in all network protocol functions, which traditionally requires general purpose processing. As a result, traditional routers are more expensive and have less throughput than switches. In addition they are more difficult to administer.
[0031] Finally, virtual circuit packet switched networks, in particular ATM, have-been proposed to interconnect local area network segments. However, it has turned out to be very difficult to map existing network protocols that are based on datagram packets to the ATM network architecture.
[0032] In summary, bridges and switches transparently extend the domain of networks, and allow for cost-effective and high-performance implementations. However, they cannot segment a network effectively in terms of traffic management and broadcast traffic. Routers, on the other hand, can segment networks very effectively, but are much more expensive and are performance bottleneck in high-speed networks. ATM has been very difficult to map to current network protocols.
[0033] The ideal network device for interconnecting network segments would have the high-speed and cost-effectiveness of a switch, with the ability of segment and manage network traffic similar to a router.
[0034] Traffic Management
[0035] Another key issue in packet switched networks is traffic control or traffic management.
[0036] In a packet switched network, each link at every switching node in the network represents a queue. As the traffic arrival rate at a link approaches its transmission rate, the queue length grows dramatically and the data in the queue needs to be stored in the attached network nodes. Eventually, a network node will run out of packet buffer capacity which will cause further packets arriving to be discarded or dropped. Dropped packets are eventually retransmitted by the source, causing the traffic load to increase further. Eventually, the network can reach a state where most of the packets in the network are retransmissions.
[0037] Conventionally, two types of traffic control mechanism are used in packet switched networks: flow control and congestion control. Flow control is concerned with matching the transmission rate of a source station to the reception rate of a destination station. A typical networks flow control mechanism uses a window techniques to limit the number of packets a source can transmit which are not yet confirmed as having been received by the destination. Conventional flow control is an end-to-end mechanism that exists in certain network protocols, in particular connection oriented network protocols such as TCP/IP. However, conventional flow control between source and destination does not solve the network congestion problem, since it does not take the utilization of buffer resources within the network into account. In addition, non-connection oriented network protocols do not use window based flow control. Also, continuous rate traffic sources such as real-time video don't match the nature of destination controlled behavior since the transmission rate is determined by the source.
[0038] Problem Statement
[0039] What is needed is an improved method and apparatus for high-speed datagram packet switched networks that can support a large number of network stations, a wide range of network transmission speeds, a wide variety of source traffic behavior including video and multimedia, while maintaining compatibility with existing network protocols and applications.
Summary of the Invention
[0040] Methods and apparatus for an enhanced datagram packet switched computer network are disclosed.
[0041] The invention processes network datagram packets in network devices as separate flows, based on the source-destination address pair contained in the datagram packet itself. As a result, the network can control and manage each flow of datagrams in a segregated fashion. The processing steps that can be specified for each flow include traffic management, flow control, packet forwarding, access control, and other network management functions.
[0042] The ability to control network traffic on a per flow basis allows for the efficient handling of a wide range and a large variety of network traffic, as is typical in large-scale computer networks, including video and multimedia type traffic.
[0043] The amount of buffer resources and bandwidth resources assigned to each flow can be individually controlled by network management. In the dynamic operation of the network, these resources can be varied based on actual network traffic loading and congestion encountered.
[0044] The invention also includes an enhanced network access control method which can selectively control flows of datagram packets entering the network and traveling between network nodes. This new network access control method interoperates with existing media access control protocols, such as used in the Ethernet or 802.3 local area network.
[0045] An important aspect of the invention is that it can be implemented in network switching devices at very high performance and at low cost. High performance is required to match the transmission speed of datagram packets on the network. Low cost is essential such that it is economical to use the invention widely.
[0046] In the preferred implementation, both high-performance and low cost is achieved by partitioning the task of datagram flow processing between dedicated network switch hardware and dedicated network switch software that executes on a high-speed controller CPU.
[0047] The network switch hardware provides a multiplicity of network ports, a shared memory buffer for storing datagram packets, a virtual path cache that stores the state and processing instructions specific to the active datagram packet flows.
[0048] Datagram packets received on an input port are buffered in the shared memory buffer. The source-destination address pair in the datagram packet header is used to index the virtual path cache to find a matching entry. If a matching entry is found in the virtual path cache, then the switch hardware performs all the packet processing steps indicated in the virtual path record, including traffic management and packet routing.
[0049] If no matching entry is found in the virtual path cache, then the datagram packet is forwarded to the controller CPU for general purpose processing. The controller CPU determines, through network management data structures and software, how to process further datagram packets with this source-destination address in the switch hardware. The controller CPU then loads an appropriate entry into the virtual path cache. If all entries in the virtual path cache are in use, then the CPU removes the least recently used entry before loading the new entry.
Brief Description of the Drawings
[0050] Other features and advantages of the present invention will become more apparent to those skilled in the art from the following detailed description in conjunction with the appended drawings in which:
[0051] FIG. 1 is a block diagram of a computer communication system;
[0052] FIG. 2 is a block diagram of the Ethernet datagram packet format;
[0053] FIG. 3 illustrates the Virtual Path Record data structure;
[0054] FIG. 4 is a block diagram of the network switching device;
[0055] FIG. 5 is a flow diagram of the network switching device operation;
[0056] FIG. 6 is a block diagram of the virtual path cache;
[0057] FIG. 7 is a block diagram of the virtual path hash function; and
[0058] FIG. 8 is a block diagram of the transmit data structure.
Detailed Description of the Invention
[0059] An enhanced computer network communication system is disclosed.
[0060] To help understand the invention, the following definitions are used:
[0061] A “datagram packet” is a self-contained unit of packet delivery on a packet switched network, which includes a destination address field, a source address field, an optional type field, and a data field.
[0062] The “destination address” and the “source address” refer to the physical network device addresses contained in a datagram packet, both of which are unique within a network.
[0063] A “flow” is a plurality of datagram packets each packet containing an identical source-destination address pair.
[0064] A “virtual path” is the communication path from a source to a destination in a datagram packet switched network.
[0065] In the following description, for purposes of explanation, specific numbers, times, signals, and other parameters are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to anyone skilled in the art that the present invention may be practiced without these specific details. In other instances, well known circuits and devices are shown in block diagram in order not to obscure the present invention unnecessarily.
[0066] The datagram packet switched communication system is illustrated in FIG. 1 by way of four network switching devices 101, 102, 103, and 104 interconnected with each other via backbone links 105, 106, 107, and 108. In addition, switch 103 is interconnected via links 110 through 112 to client computers 120 through 122, switch 104 is interconnected via links 113 through 115 to client computers 123 to 125 and switch 102 is interconnected via links 116 and 117 to server computers 126 and 127.
[0067] The network shown in FIG. 1 is small for purposes of illustration. In practice most networks would include a much larger number of host computers and network switching devices.
[0068] The basic unit of transmission and processing in this network is a datagram. For purposes of illustration, we will be using the Ethernet datagram packet format in this description. It will be apparent to anyone skilled in the art that other datagram packet formats can also be used to practice this invention, including the different datagrams described in the IEEE 802 family of network standards.
[0069] As illustrated in FIG. 2, the Ethernet datagram 200 contains a 48-bit destination address field 201, a 48-bit source address field 202, a 16-bit type field 203, a variable size data field 204 ranging from 46 bytes to 1500 bytes, and a 32-bit CRC field 205.
[0070] A key aspect of the present invention is the virtual path method. A virtual path is specified by the source-destination address pair contained in a datagram packet. In the Ethernet packet datagram, the source-destination address pair can be thought of as a 96-bit circuit identifier, which specifies a unidirectional circuit from the source to the destination. This 96-bit circuit identifier will subsequently be referred to as a virtual path in order to avoid confusion with virtual circuit networks. While this 96-bit virtual path identifier may appear large as compared to the much smaller circuit identifiers in virtual circuit networks, it has the significant advantage that it is globally unique and thus does not require to be mapped to different identifiers as a datagram packet travels along the path from source to destination.
[0071] Virtual Path Record
[0072] Each datagram packet arriving at a network switching device is recognized as traveling on a particular virtual path by the source-destination address pair contained in this header. The network switch maps this source-destination pair to a virtual path record in the switch. The virtual path record specifies how the datagram packet is to be processed, including its routing, priority, scheduling ,and buffer resource allocation.
[0073] FIG. 3 illustrates the data structure of the virtual path record.
[0074] It will be apparent to those skilled in the art that other data structures from the one shown can be successfully used, including but not limited to fields of different size, arranging the fields,in different order, and additional fields not present in FIG. 3.
[0075] Turning now to the specific virtual path record illustrated in FIG. 3, there are four groups of fields: the tag field 310, the forwarding field 320, the state field 330, and the statistics field 340. The function and meaning of these fields will now be described.
[0076] Tag Field
[0077] The purpose of the tag field is to match an incoming datagram packet against a virtual path record. The tag field 310 has four subfields: the destination address field 311, the source address field 312, the optional type field 313, and the input port field 314.
[0078] Since the virtual path index is quite large, 96 bits in the case of Ethernet datagrams, it is not practical to provide a full array indexed by the virtual path number. Instead, each virtual path record is keyed with the virtual path number to allow lookup by search or partial index. One method for organizing the virtual path records and looking them up will be further described below.
[0079] For the lookup method to locate the correct virtual path record, the destination address field 311 and the source address field 312 in the virtual path record must match the destination address field 201 and the source address field 202 in the datagram header.
[0080] Type field 313 allows for optional type filtering. If the type field is set to 0, any type field 203 in the datagram header will match this virtual path record. However, if the type field is not 0, then the type field has to match the type field 203 in the datagram header exactly for the match to be successful.
[0081] The input port field 314 allows input port filtering. The input port field has to match the actual input port number at which the datagram packet has been received.
[0082] Forwarding Field
[0083] The forwarding field 320 determines how the datagram packet should be forwarded. Output port field 321 specifies the output port on which this datagram will be transmitted. Priority field 322 specifies the traffic management priority of this virtual path compared to other virtual paths. Real time field 323 forces the switch to process this packet in real time mode, which includes the act of dropping the packet if it cannot be sent within a certain time.
[0084] Store Forward field 324 selects the store-forward mode of operation. Normally the switch operates in cut-through mode where an incoming datagram is sent on to the output port as soon as feasible, even before it is completely received. In store-forward mode, an incoming packet must be completely received before it is sent on. This is a requirement in case of speed conversion from a slower input port to a faster output port. Store-forward mode is also used to insure the correctness of the complete packet received before sending it on.
[0085] Multicast field 325 selects the multicast mode of operation. Multicast mode involves scheduling of a single datagram packet on multiple outputs, which are determined by a bit vector in the output port field, with “1” bits indicating output ports to which the Multicast should be sent.
[0086] Field 326 is the Snoop Mode. Snoop mode when selected sends a copy of the datagram packet to the CPU for general purpose processing.
[0087] Field 327 is the Buffer Size field, which specifies the maximum number of packet buffers allocated to this path for buffering purposes.
[0088] The state field 330, includes the following fields: Head Pointer Field 331, which points to the beginning of the buffer area associated with this virtual path; Tail Pointer 332 points to the end of the buffer area of this virtual path; Uplink Pointer 333 points to the next virtual path record to transmit to the source, downlink pointer 334 points to the next virtual path record to transmit to the destination.
[0089] The statistics field 340 maintains traffic statistics regarding the traffic received on this virtual path. Field 341 counts the number of packets received and field 342 counts the number of bytes received on this virtual path.
[0090] FIG. 4 Preferred Implementation
[0091] Referring to FIG. 4, a virtual path network switching device 400 is illustrated with Network Input Ports 401 through 404, network output ports 405 through 408, switch hardware 409, where shared buffer memory 410, controller CPU 411, CPU interface 412, CPU read-and-write memory 413, Flash PROM 414, and virtual path cache 415. Using FIG. 4 and the flow chart in FIG. 5, a cycle of operation will be described.
[0092] Datagram packets arriving through network ports 401 through 404 are temporarily stored in shared buffer memory 410. As soon as the datagram packet header has arrived, which in the case of Ethernet datagrams is after the first 14 bytes of the datagram packet, the virtual path cache is looked up to check whether a virtual path cache entry exists for this path. If a matching entry is found in the virtual path cache 415, then switch hardware 409 starts processing the datagram packet as specified in the virtual path cache entry which in the typical case will forward the datagram packet on one of the output ports 405 through 408.
[0093] If no entry matching the datagram was found in the virtual path cache 415, then the datagram packet is forwarded to controller CPU 411 via CPU interface 412 for general purpose processing. Controller CPU 411 processes datagram packet according to instructions and data stored in main memory 413 and optionally in Flash PROM 414. Said instructions and data structures used for datagram processing have been created previously by network management, network configuration, network statistics, and network behavior.
[0094] The result of the datagram general purpose processing is that the CPU determines how future datagram packets on this virtual path should be processed by the switch hardware 409 and loads an appropriate entry into the virtual path cache 415. If all entries in the virtual path cache 415 are in use, then controller CPU 409 removes the least recently used entry in virtual path cache 415 before loading the new entry. CPU 411 then forwards the datagram packet to the switch hardware 409 via CPU interface 412 for transmission.
[0095] When the controller CPU loads a new virtual path cache entry, it sets the tag field 310 to the desired virtual path index, the forwarding field 320 to the desired forwarding function, and it initializes the state field 330 and the statistics field 340. The switch hardware will then automatically update the state and the statistics fields as the path is used. The switch hardware does not modify the information in the tag field and the forwarding field.
[0096] FIG. 5 Flow Diagram
[0097] A method in accordance with this invention is shown in the flow diagram of FIG. 5.
[0098] 1. Packet Arrives at the invented system.
[0099] 2. Check Datagram Virtual Path Index against Virtual Path Cache.
[0100] 3. If valid virtual path entry is found, process packet in Switch Hardware which includes the steps of forwarding the datagram packet to output port and updating the statistics field 340.
[0101] 4. If No Entry is found, forward packet to Controller CPU to process datagram packet in software. Controller CPU sends datagram packet back to switch hardware for transmission on the appropriate output port.
[0102] 5. If Controller CPU determines that future datagram packets of this virtual path should be processed by switch hardware, Controller CPU then creates new virtual path record and writes it into virtual path cache, replacing the least recently used entry if necessary.
[0103] Virtual Path Cache Organization
[0104] FIG. 6 illustrates an example of virtual path cache organization.
[0105] It will be apparent to anyone skilled in the art that other cache sizes and organizations from the one shown can be successfully used, including but not limited to caches of different size, associativity, alternative hash-function, and content-addressability.
[0106] The virtual path cache illustrated in FIG. 6 is organized as a 4-set associative cache built with four banks of high-speed static memory 601 through 604, each equipped with a set of comparators 611 . . . 614 that control a set of tri-state buffers 621 through 624.
[0107] The virtual path index 630, which is the source-destination address pair of the incoming datagram, enters hash function 631 which in turn produces a virtual patch cache index 632 which in turn looks up the four parallel sets of the virtual path cache SRAMs 601 through 604. The tag field 310 from each set of SRAMs will be compared against the virtual path index 630 and only that virtual path record that matches will be output on the virtual path record databus 633 via tri-state drivers 621 through 624. Combinatorial logic 634 will generate a high signal 635 to indicate a hit.
[0108] If no tag field matches, then combinatorial logic 634 will generate a low signal 635 to indicate a miss, i.e. that no valid virtual path record was found in the virtual path cache.
[0109] Hash Function
[0110] FIG. 7 illustrates a specific hash function embodied in hash function logic 631. Again, this hash function is used for illustration only. It will be apparent to anyone skilled in the art that other hash functions from the one shown can be used.
[0111] Referring now to FIG. 7, the specific hash function logic is the bitwise Exclusive-OR 703 between the low-order 15 bits of the destination address 701 and the source address 702 of the Virtual Path Index 630, producing the 15 bit virtual path cache index 632. A bit-wise Exclusive-OR function is used because it is simple and fast to implement. The low-order address bits are used from both source and destination address since they change with the highest frequency.
[0112] Packet Transmission
[0113] FIG. 8 shows a data structure that illustrates how an output port transmits datagram packets buffered in the switch shared memory. This particular structure design is for purposes of illustration only; it will be apparent to anyone skilled in the art that other data structures from the one shown can be used successfully.
[0114] The data structure in FIG. 8 is for one output port only. Referring briefly to FIG. 4, each output port 405 through 408 in the switch hardware 409 has a similar data structure to that shown in FIG. 8.
[0115] Output port 801 is to transmit datagrams buffered and waiting for transmission on virtual paths 810-1, 810-2 through 810-n, where n is a selected integer.
[0116] The output port 801 has a head pointer 802 and current pointer 803. Head pointer 802 points to the first entry 810-1 in the transmit list 804, which links to the next entry 810-2. Current pointer 803 points to the entry from which datagrams are to be transmitted next, which is virtual path 810-2 in this example. The transmit list 804 is formed by the link fields 811-1 through 811-n. Each link field points to the next path in the transmit list. The last link entry 811-n in the transmit list 804 has a link field value of 0. The actual length of the transmit list 804 will vary as a function of the number of paths that have datagrams pending for transmission on output port 801. If no path is waiting to transmit on output port 801 then the value of both head pointer 802 and current pointer 803 is 0.
[0117] The next datagram,to be sent on output port 801 is determined by current pointer 803 which points to the next entry in the transmit list 804 of linked virtual path entries. This method of organizing the output list 804 as a chain of all virtual paths waiting to transmit on output port 801 has the effect of giving round robin priority to datagram packets waiting to be transmitted from different virtual paths.
[0118] A mechanism is also provided to send datagram packets from selected virtual paths at a higher priority than other virtual paths. If the priority field 322 in the virtual path record 300 is set, then the value in the priority field 322 indicates the number of packets to be transmitted from a virtual path before transmitting a packet from the next path in the transmit list 804.
[0119] Overall Switch and Network Operation
[0120] Referring to FIGS. 1 through 8, the overall operation of the system shall now be described.
[0121] For purposes of illustration, assume that client station 120 (FIG. 1) wants to send a datagram packet 200 (FIG. 2) to server station 126. Datagram 200 will be received on switch input port 401 (FIG. 4). Switch hardware generates virtual path index 630 from the datagram destination and source address fields and sends virtual path index signals on bus 421 to virtual path cache 415 for lookup.
[0122] The virtual path index in cache 415 will be converted by hash logic 631 to a virtual path cache index 632 (FIGS. 6 and 7) that indexes the four set associative virtual path cache 601 through 604 (FIG. 6). The virtual path index is further compared in parallel against the outputs from the four set associate cache 601 through 604 via the four comparators 611 through 614. Assuming a valid virtual path tag was found in SRAM cache 601 then comparator 611 will indicate a “hit” signal on hit/miss wire 635 and enable tri-state buffer 621 to output the virtual path record stored in SRAM cache 601 on virtual path record bus 633.
[0123] Switch hardware 409 then forwards and processes the datagram packet according to the fields of the virtual path record on bus 633 (FIGS. 6 and 4).
[0124] If the virtual path cache had not contained a valid virtual path cache entry then it would indicate “miss” on the hit/miss wire 635 (FIGS. 6 and 4). This causes the switch hardware to forward the packet to the CPU 411 via CPU interface 412 for processing. The controller CPU 411 then processes the packet in software and sends it back to the switch hardware 409 to output on the appropriate output port. If controller CPU 411 determines that future datagram packets of this virtual path should be processed by switch hardware, controller CPU 411 then creates a new virtual path record for said virtual path and writes it into virtual path cache 415 replacing the least recently used entry if necessary.
[0125] Several advantages flow from this invention. For example, the invented method and structure:
[0126] 1. supports reliable and efficient data communication in datagram networks without dropping datagram packets due to lack of network resources;
[0127] 2. allows the specification of the attributes of datagram packet flows similar to the capabilities available in a virtual circuit packet switched network, but without the disadvantages of having to set up, maintain, and tear down virtual circuits; and
[0128] 3. is compatible with existing network protocols and applications, and interoperates with the installed base of datagram network interfaces.
[0129] The other embodiments of this invention may be obvious to those skilled in the art. The above description is illustrative only and not limiting.
Claims
We claim:
1. In a network device, a method for processing a plurality of datagram packets each including a source-destination address pair, comprising:
(a) comparing said source-destination address pair contained in each respective datagram packet to a stored listing of source-destination pairs, each source-destination pair in the listing being associated with a virtual path;
(b) if no match is found in the comparing for a currently compared respective datagram packet, creating and storing a virtual path for the source-destination pair of that currently compared respective datagram packet; and
(c) if a match is found in the comparing for the currently compared respective datagram packet, processing the currently compared respective datagram packet based on the stored virtual path.
2. The method of claim 1, wherein each datagram packet further includes a type field and the processing is determined by the source-destination address pair and the type field contained in each datagram packet.
3. The method of claim 1, wherein each datagram packet is one of datagrams defined in the IEEE 802 family of network standards.
4. The method of claim 1, wherein each datagram packet is an Ethernet datagram packet and wherein the source address is the Ethernet packet source address field and the destination address is the Ethernet packet destination address field.
5. The method of claim 1, wherein the processing comprises an action chosen from the group consisting of: dropping the packet, buffering the packet, forwarding the packet to an output port, forwarding the packet to a multiplicity of output ports, forwarding a copy of the packet to another network device, and generating a response back to the sender of the packet.
6. The method of claim 1, wherein the processing includes forwarding respective of the datagram packets to an output port.
7. The method of claim 1, wherein the processing includes forwarding respective of the datagram packets to a multiplicity of output ports.
8. The method of claim 1, wherein the processing includes sending respective of the datagram packets to a controller CPU for further processing.
9. The method of claim 1, wherein the processing includes forwarding a copy of respective of the datagram packets to another network device for processing.
10. The method of claim 1, wherein the processing includes discarding respective of the datagram packets.
11. The method of claim 1, wherein the processing includes notifying the sender of respective of the datagram packets that the respective datagram packets that were sent have not been accepted.
12. The method of claim 1, wherein the processing includes notifying the sender of respective of the datagram packets that the respective datagram packets that were sent have not been accepted, wherein said datagram is an Ethernet datagram, and wherein the response back to the source comprises an Ethernet collision signal.
13. The method of claim 1, wherein the processing includes determining whether respective of the datagram packets are sent from an authorized source to an authorized destination.
14. The method of claim 1, wherein the processing includes storing respective of the datagram packets in packet buffer memory, with separate buffer resources provided for each separate virtual path.
15. The method of claim 1, wherein the processing includes determining availability of buffer space on a particular virtual path and not accepting additional datagram packets that would exceed an amount of buffer space allowed for the particular virtual path.
16. The method of claim 1, wherein the processing includes communicating availability of packet buffer resources available to an upstream sender of datagram packets.
17. The method of claim 1, further comprising (c) allowing the network device to specify a maximum rate of transmission of a flow of datagrams.
18. The method of claim 1, further comprising (c) providing for specifying a rate of transmission of one flow of datagrams packets relative to a rate of transmission of other flows of datagram packets.
19. In a network device, a method for processing datagram packets each having a source and a destination address, comprising:
(a) receiving respective of the datagram packets;
(b) determining from the source-destination address pair contained in each of the datagram packets a virtual path record comprising specifications for processing the respective datagram packets by comparing source-destination address pairs in each of the respective datagram packets with a stored list of source-destination address pairs, each source-destination address pair associated with a respective datagram packet, wherein in the comparing (b1) if no match is found in the comparing for a currently compared respective datagram packet, a virtual path for the source-destination pair of that currently compared respective datagram packet is created and stored and (b2) if a match is found in the comparing for the currently compared respective datagram packet, the respective datagram packets is processed according to the processing steps associated with said virtual path record.
20. A network device, comprising:
(a) at least one port configured to receive and transmit datagram packets, each including a source-destination address pair;
(b) a memory configured to store said datagram packets; and
(c) a processor configured to compare said source-destination address pair contained in each of the datagram packets to a listing of source-destination pairs, each source-destination pair in the listing being associated with a virtual path, and
(c1) if no match is found in the comparing for a currently compared respective datagram packet, a virtual path for the source-destination pair of that currently compared respective datagram packet is created and stored in the memory; and
(c2) if a match is found in the comparing for the currently compared respective datagram packet, the currently compared respective datagram packet is processed based on the stored virtual path.
21. A network device as in claim 20, wherein said at least one port comprises a plurality of ports.
22. A network device as in claim 20, wherein said processing defines an action to be taken with respect to each datagram packet, said action being chosen from the group consisting of: dropping the packet, buffering the packet, forwarding the packet to an output port, forwarding the packet to a multiplicity of output ports, forwarding a copy of the packet to another network device, and generating a response back to the sender of the packet.
23. The network device of claim 20, wherein each datagram packet is one of datagrams defined in the IEEE 802 family of network standards.
24. The network device of claim 20, wherein each datagram packet is an Ethernet datagram packet and wherein the source address is the Ethernet packet source address field and the destination address is the Ethernet packet destination address field.
25. The network device of claim 20, wherein the processor processes each datagram packet comprises a routing action chosen from the group consisting of: dropping the packet, buffering the packet, forwarding the packet to an output port, forwarding the packet to a multiplicity of output ports, forwarding a copy of the packet to another network device, and generating a response back to the sender of the packet.
26. The network device of claim 20, further comprising means for storing information specifying an amount of buffer resources provided for each separate flow of datagram packets.
27. The network device of claim 20, further comprising flow control means for communicating to an upstream sender of datagram packets availability of packet buffer resources available.
28. The network device of claim 20, further comprising means for allowing the network system to control relative rate of transmissions among multiple flows of datagram packets.
29. The network device of claim 20, further comprising:
a virtual path cache memory for providing storage for most recently used virtual path records;
virtual path cache lookup means for allowing switch hardware to determine if a certain virtual path entry is located in the virtual path cache;
means for performing processing actions specified in the virtual path record if a valid virtual path record is found in the virtual path cache memory; and
means for processing datagram packets for which no valid entry is found in the virtual path cache memory.
30. The network device of claim 29, further comprising a controller CPU and controller memory for processing datagram packets that have no valid virtual path record in the virtual path cache, said controller CPU also being able to read and write virtual path cache entries.
Patent Citations (217)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4131767(A) | 1978-12-01 | Weinstein | Applicant |
| US4161719(A) | 1979-07-01 | Parikh et al. | Applicant |
| US4316284(A) | 1982-02-01 | Howson | Applicant |
| US4397020(A) | 1983-08-01 | Howson | Applicant |
| US4419728(A) | 1983-12-01 | Larson | Applicant |
| US4424565(A) | 1984-01-01 | Larson | Applicant |
| US4437087(A) | 1984-03-01 | Petr | Applicant |
| US4438511(A) | 1984-03-01 | Baran | Applicant |
| US4439763(A) | 1984-03-01 | Limb | Applicant |
| US4445213(A) | 1984-04-01 | Baugh et al. | Applicant |
| US4446555(A) | 1984-05-01 | Devault et al. | Applicant |
| US4456957(A) | 1984-06-01 | Schicltz | Applicant |
| US4464658(A) | 1984-08-01 | Thelen | Applicant |
| US4499576(A) | 1985-02-01 | Fraser | Applicant |
| US4506358(A) | 1985-03-01 | Montgomery | Applicant |
| US4507760(A) | 1985-03-01 | Fraser | Applicant |
| US4532626(A) | 1985-07-01 | Flores et al. | Applicant |
| US4644532(A) | 1987-02-01 | George et al. | Applicant |
| US4646287(A) | 1987-02-01 | Larson et al. | Applicant |
| US4677423(A) | 1987-06-01 | Benvenuto et al. | Applicant |
| US4679189(A) | 1987-07-01 | Olson et al. | Applicant |
| US4679227(A) | 1987-07-01 | Hughes-Hartogs | Applicant |
| US4723267(A) | 1988-02-01 | Jones et al. | Applicant |
| US4731816(A) | 1988-03-01 | Hughes-Hartogs | Applicant |
| US4750136(A) | 1988-06-01 | Arpin et al. | Applicant |
| US4757495(A) | 1988-07-01 | Decker et al. | Applicant |
| US4763191(A) | 1988-08-01 | Gordon et al. | Applicant |
| US4769810(A) | 1988-09-01 | Eckberg, Jr. et al. | Applicant |
| US4769811(A) | 1988-09-01 | Eckberg, Jr. et al. | Applicant |
| US4771425(A) | 1988-09-01 | Baran et al. | Applicant |
| US4819228(A) | 1989-04-01 | Baran et al. | Applicant |
| US4827411(A) | 1989-05-01 | Arrowood et al. | Applicant |
| US4833706(A) | 1989-05-01 | Hughes-Hartogs | Applicant |
| US4835737(A) | 1989-05-01 | Herrig et al. | Applicant |
| US4879551(A) | 1989-11-01 | Georgiou et al. | Applicant |
| US4893306(A) | 1990-01-01 | Chao et al. | Applicant |
| US4903261(A) | 1990-02-01 | Baran et al. | Applicant |
| US4922486(A) | 1990-05-01 | Lidinsky et al. | Applicant |
| US4933937(A) | 1990-06-01 | Konishi | Applicant |
| US4933938(A) | 1990-06-01 | Sheehy | Examiner |
| US4960310(A) | 1990-10-01 | Cushing | Applicant |
| US4962497(A) | 1990-10-01 | Ferenc et al. | Applicant |
| US4962532(A) | 1990-10-01 | Kasiraj et al. | Applicant |
| US4965772(A) | 1990-10-01 | Daniel et al. | Applicant |
| US4970678(A) | 1990-11-01 | Sladowski et al. | Applicant |
| US4979118(A) | 1990-12-01 | Kheradpir | Applicant |
| US4980897(A) | 1990-12-01 | Decker et al. | Applicant |
| US4991169(A) | 1991-02-01 | Davis et al. | Applicant |
| US5003595(A) | 1991-03-01 | Collins et al. | Applicant |
| US5014265(A) | 1991-05-01 | Hahne et al. | Applicant |
| US5020058(A) | 1991-05-01 | Holden et al. | Applicant |
| US5033076(A) | 1991-07-01 | Jones et al. | Applicant |
| US5054034(A) | 1991-10-01 | Hughes-Hartogs | Applicant |
| US5059925(A) | 1991-10-01 | Weisbloom | Applicant |
| US5072449(A) | 1991-12-01 | Enns et al. | Applicant |
| US5088032(A) | 1992-02-01 | Bosack | Applicant |
| US5095480(A) | 1992-03-01 | Fenner | Applicant |
| US5115431(A) | 1992-05-01 | Williams et al. | Applicant |
| US5128945(A) | 1992-07-01 | Enns et al. | Applicant |
| US5136580(A) | 1992-08-01 | Videlock et al. | Applicant |
| US5166930(A) | 1992-11-01 | Braff et al. | Applicant |
| US5199049(A) | 1993-03-01 | Wilson | Applicant |
| US5206886(A) | 1993-04-01 | Bingham | Applicant |
| US5208811(A) | 1993-05-01 | Kashio et al. | Applicant |
| US5212686(A) | 1993-05-01 | Joy et al. | Applicant |
| US5224099(A) | 1993-06-01 | Corbalis et al. | Applicant |
| US5226120(A) | 1993-07-01 | Brown et al. | Applicant |
| US5228062(A) | 1993-07-01 | Bingham | Applicant |
| US5229994(A) | 1993-07-01 | Balzano et al. | Applicant |
| US5237564(A) | 1993-08-01 | Lespagnol et al. | Applicant |
| US5241682(A) | 1993-08-01 | Bryant et al. | Applicant |
| US5243342(A) | 1993-09-01 | Kattemalalavadi et al. | Applicant |
| US5243596(A) | 1993-09-01 | Port et al. | Applicant |
| US5245614(A) | 1993-09-01 | Gutman et al. | Applicant |
| US5247516(A) | 1993-09-01 | Bernstein et al. | Applicant |
| US5249178(A) | 1993-09-01 | Kurano et al. | Applicant |
| US5253251(A) | 1993-10-01 | Aramaki | Applicant |
| US5255291(A) | 1993-10-01 | Holden et al. | Applicant |
| US5260933(A) | 1993-11-01 | Rouse | Applicant |
| US5260978(A) | 1993-11-01 | Fleischor et al. | Applicant |
| US5268592(A) | 1993-12-01 | Bellamy et al. | Applicant |
| US5268900(A) | 1993-12-01 | Hluchyj et al. | Applicant |
| US5271004(A) | 1993-12-01 | Proctor et al. | Applicant |
| US5274631(A) | 1993-12-01 | Bhardwaj | Applicant |
| US5274635(A) | 1993-12-01 | Rahman et al. | Applicant |
| US5274643(A) | 1993-12-01 | Fisk | Applicant |
| US5280470(A) | 1994-01-01 | Buhrke et al. | Applicant |
| US5280480(A) | 1994-01-01 | Pitt et al. | Examiner |
| US5280500(A) | 1994-01-01 | Mazzola et al. | Applicant |
| US5283783(A) | 1994-02-01 | Nguyen et al. | Applicant |
| US5287103(A) | 1994-02-01 | Kasprzyk et al. | Applicant |
| US5287453(A) | 1994-02-01 | Roberts | Applicant |
| US5287535(A) | 1994-02-01 | Sakagawa et al. | Examiner |
| US5291442(A) | 1994-03-01 | Emma et al. | Examiner |
| US5291482(A) | 1994-03-01 | McHarg et al. | Applicant |
| US5305311(A) | 1994-04-01 | Lyles | Applicant |
| US5307343(A) | 1994-04-01 | Bostica et al. | Applicant |
| US5309437(A) | 1994-05-01 | Perlman et al. | Applicant |
| US5311509(A) | 1994-05-01 | Heddes et al. | Applicant |
| US5313454(A) | 1994-05-01 | Bustini et al. | Applicant |
| US5313582(A) | 1994-05-01 | Hendel et al. | Applicant |
| US5317562(A) | 1994-05-01 | Nardin et al. | Applicant |
| US5319644(A) | 1994-06-01 | Liang | Applicant |
| US5325504(A) | 1994-06-01 | Tipley et al. | Examiner |
| US5327421(A) | 1994-07-01 | Hiller et al. | Applicant |
| US5331637(A) | 1994-07-01 | Francis et al. | Applicant |
| US5335224(A) | 1994-08-01 | Cole et al. | Applicant |
| US5345445(A) | 1994-09-01 | Hiller et al. | Applicant |
| US5345446(A) | 1994-09-01 | Hiller et al. | Applicant |
| US5347642(A) | 1994-09-01 | Barratt | Examiner |
| US5359592(A) | 1994-10-01 | Corbalis et al. | Applicant |
| US5361250(A) | 1994-11-01 | Nguyen et al. | Applicant |
| US5361256(A) | 1994-11-01 | Doeringer et al. | Applicant |
| US5361259(A) | 1994-11-01 | Hunt et al. | Applicant |
| US5365524(A) | 1994-11-01 | Hiller et al. | Applicant |
| US5367517(A) | 1994-11-01 | Cidon et al. | Applicant |
| US5371852(A) | 1994-12-01 | Attanasio et al. | Applicant |
| US5386567(A) | 1995-01-01 | Lien et al. | Applicant |
| US5390170(A) | 1995-02-01 | Sawant et al. | Applicant |
| US5390175(A) | 1995-02-01 | Hiller et al. | Applicant |
| US5394394(A) | 1995-02-01 | Crowther et al. | Applicant |
| US5394402(A) | 1995-02-01 | Ross | Applicant |
| US5394408(A) | 1995-02-01 | Nishihara et al. | Examiner |
| US5400325(A) | 1995-03-01 | Chatwani et al. | Applicant |
| US5408469(A) | 1995-04-01 | Opher et al. | Applicant |
| US5416842(A) | 1995-05-01 | Aziz | Applicant |
| US5418922(A) | 1995-05-01 | Liu | Examiner |
| US5422880(A) | 1995-06-01 | Heitkamp et al. | Applicant |
| US5422882(A) | 1995-06-01 | Hiller et al. | Applicant |
| US5423002(A) | 1995-06-01 | Hart | Applicant |
| US5426636(A) | 1995-06-01 | Hiller et al. | Applicant |
| US5426637(A) | 1995-06-01 | Derby et al. | Applicant |
| US5428607(A) | 1995-06-01 | Hiller et al. | Applicant |
| US5430715(A) | 1995-07-01 | Corbalis et al. | Applicant |
| US5430729(A) | 1995-07-01 | Rahnema | Applicant |
| US5432784(A) | 1995-07-01 | Ozveren | Applicant |
| US5442457(A) | 1995-08-01 | Najafi | Applicant |
| US5442624(A) | 1995-08-01 | Bonomi et al. | Examiner |
| US5442630(A) | 1995-08-01 | Gagliardi et al. | Applicant |
| US5444491(A) | 1995-08-01 | Lim | Examiner |
| US5450406(A) | 1995-09-01 | Esaki et al. | Examiner |
| US5452297(A) | 1995-09-01 | Hiller et al. | Applicant |
| US5473599(A) | 1995-12-01 | Li et al. | Applicant |
| US5473607(A) | 1995-12-01 | Hausman et al. | Applicant |
| US5477541(A) | 1995-12-01 | White et al. | Applicant |
| US5485455(A) | 1996-01-01 | Dobbins et al. | Applicant |
| US5490140(A) | 1996-02-01 | Abensour et al. | Applicant |
| US5490258(A) | 1996-02-01 | Fenner | Applicant |
| US5491687(A) | 1996-02-01 | Christensen et al. | Applicant |
| US5491804(A) | 1996-02-01 | Heath et al. | Applicant |
| US5497368(A) | 1996-03-01 | Reijnierse et al. | Applicant |
| US5499238(A) | 1996-03-01 | Shon | Applicant |
| US5504747(A) | 1996-04-01 | Sweasey | Applicant |
| US5509006(A) | 1996-04-01 | Wilford et al. | Applicant |
| US5517494(A) | 1996-05-01 | Green | Applicant |
| US5519704(A) | 1996-05-01 | Farinacci et al. | Applicant |
| US5519858(A) | 1996-05-01 | Walton et al. | Applicant |
| US5523999(A) | 1996-06-01 | Takano et al. | Examiner |
| US5526489(A) | 1996-06-01 | Nilakantan et al. | Applicant |
| US5528592(A) | 1996-06-01 | Schibler et al. | Examiner |
| US5530963(A) | 1996-06-01 | Moore et al. | Applicant |
| US5533033(A) | 1996-07-01 | Ratner | Examiner |
| US5535195(A) | 1996-07-01 | Lee | Applicant |
| US5539734(A) | 1996-07-01 | Burwell et al. | Applicant |
| US5541911(A) | 1996-07-01 | Nilakantan et al. | Applicant |
| US5546370(A) | 1996-08-01 | Ishikawa | Applicant |
| US5555244(A) | 1996-09-01 | Gupta et al. | Applicant |
| US5557747(A) | 1996-09-01 | Rogers et al. | Examiner |
| US5561669(A) | 1996-10-01 | Lenney et al. | Applicant |
| US5566170(A) | 1996-10-01 | Bakke et al. | Examiner |
| US5583862(A) | 1996-12-01 | Callon | Applicant |
| US5583865(A) | 1996-12-01 | Esaki et al. | Examiner |
| US5592470(A) | 1997-01-01 | Rudrapatna et al. | Applicant |
| US5598581(A) | 1997-01-01 | Daines et al. | Applicant |
| US5600798(A) | 1997-02-01 | Chenrukuri et al. | Applicant |
| US5604868(A) | 1997-02-01 | Komine et al. | Applicant |
| US5608726(A) | 1997-03-01 | Virgile | Applicant |
| US5608908(A) | 1997-03-01 | Barghouti et al. | Examiner |
| US5610904(A) | 1997-03-01 | Eng et al. | Examiner |
| US5614891(A) | 1997-03-01 | Zeinstra et al. | Examiner |
| US5617417(A) | 1997-04-01 | Sathe et al. | Applicant |
| US5617421(A) | 1997-04-01 | Chin et al. | Applicant |
| US5625622(A) | 1997-04-01 | Johri | Examiner |
| US5630125(A) | 1997-05-01 | Zellweger | Applicant |
| US5632021(A) | 1997-05-01 | Jennings et al. | Applicant |
| US5634010(A) | 1997-05-01 | Ciscon et al. | Applicant |
| US5638359(A) | 1997-06-01 | Peltola et al. | Applicant |
| US5644718(A) | 1997-07-01 | Belove et al. | Applicant |
| US5644751(A) | 1997-07-01 | Burnett | Examiner |
| US5659684(A) | 1997-08-01 | Giovannoni et al. | Applicant |
| US5666353(A) | 1997-09-01 | Klausmeier et al. | Applicant |
| US5673265(A) | 1997-09-01 | Gupta et al. | Applicant |
| US5678006(A) | 1997-10-01 | Valizadeh et al. | Applicant |
| US5680116(A) | 1997-10-01 | Hashimoto et al. | Applicant |
| US5684797(A) | 1997-11-01 | Aznar et al. | Applicant |
| US5689506(A) | 1997-11-01 | Chiussi et al. | Applicant |
| US5694390(A) | 1997-12-01 | Yamato et al. | Applicant |
| US5699532(A) | 1997-12-01 | Barrett et al. | Examiner |
| US5748186(A) | 1998-05-01 | Raman | Applicant |
| US5748617(A) | 1998-05-01 | McLain, Jr. | Applicant |
| US5754768(A) | 1998-05-01 | Brech et al. | Examiner |
| US5802054(A) | 1998-09-01 | Bellenger | Applicant |
| US5835710(A) | 1998-11-01 | Nagami et al. | Applicant |
| US5842040(A) | 1998-11-01 | Hughes et al. | Examiner |
| US5856981(A) | 1999-01-01 | Voelker | Applicant |
| US5892924(A) | 1999-04-01 | Lyon et al. | Applicant |
| US5903559(A) | 1999-05-01 | Acharya et al. | Applicant |
| US6091725(A) | 2000-07-01 | Cheriton et al. | Examiner |
| US6343322(B2) | 2002-01-01 | Nagami et al. | Examiner |
| EP384758 | 1990-02-01 | Applicant | |
| EP384758(A2) | 1990-08-01 | Applicant | |
| EP431751(A1) | 1990-11-01 | Applicant | |
| EP567217(A2) | 1993-10-01 | Applicant | |
| WO93/07569 | 1993-04-01 | Applicant | |
| WO93/07692 | 1993-04-01 | Applicant | |
| WO94/01828 | 1994-01-01 | Applicant | |
| WO95/20850 | 1995-08-01 | Applicant |
Non-Patent Literature (16)
- William Stallings, Data and Computer Communications, PP:329-333, Prentice Hall, Upper Saddle River, New Jersey 07458.Applicant
- Allen, M., “Novell IPX Over Various WAN Media (IPXWAN),” Network Working Group, RFC 1551, Dec. 1993, pp. 1-22.Applicant
- Chowdhury, et al., “Alternative Bandwidth Allocation Algorithms for Packet Video in ATM Networks, ” INFOCOM 1992, pp. 1061-1068.Applicant
- Doeringer, W., “Routing on Longest-Matching Prefixes,” IEEE/ACM Transactions in Networking, vol. 4, No. 1, Feb. 1996, pp. 86-97.Applicant
- Esaki, et al., “Datagram Delivery in an ATM-Internet,” 2334b IEICE Transactions on Communications, Mar. 1994, No. 3, Tokyo, Japan.Applicant
- IBM Corporation, “Method and Apparatus for the Statistical Multiplexing of Voice, Data and Image Signals,” IBM Technical Disclosure Bulletin, No. 6, Nov. 1992, pp. 409-411.Applicant
- Pei, et al., “Putting Routing Tables in Silicon,” IEEE Network Magazine, Jan. 1992, pp. 42-50.Applicant
- Perkins, D., “Requirements for an Internet Standard Point-to-Point Protocol,” Network Working Group, RFC 1547, Dec. 1993, pp. 1-19.Applicant
- Simpson, W., “The Point-to-Point Protocol (PPP),” Network Working Group, RFC 1548, Dec. 1993, pp. 1-53.Applicant
- Tsuchiya, P.F., “A Search Algorithm for Table Entries with Non-Contiguous Wildcarding,” Abstract, Bellcore.Applicant
- Zhang, et al., “Rate-Controlled Static-Priority Queueing,” INFOCOM 1993, pp. 227-236.Applicant
- Chowdhury, et al. “Alternative Bandwith Allocation,” 1992, IEEE Infocom '92, pp. 1061-1068.Applicant
- Zhang, et al. “Rate-Controlled Static-Priority Queueing,” 1993, IEEE, pp. 227-236.Applicant
- IBM, “Method and Apparatus for the Statistical Multiplexing of Voice, Data, and Image Signals”, Nov. 1992, IBM Technical Data Bulletin n6 Nov. 1992, pp. 409-411.Applicant
- Esaki, et al., “Datagram Delivery in an ATM-Internet, ” IEICE Transactions on Communications vol. E77-B, No. 3, (1994) Mar., Tokyo, Japan.Applicant
- Doeringer, et al., “Routing on Longest-Matching Prefixes,” IEEE Transactions on Networking, vol. 4, No. 1, Feb. 1996, pp. 86-97.Applicant