US 6,182,147 B2Grant
Multicast group routing using unidirectional links
Issue Date:2001-01-30
•12 Claims
•2 Drawing Sheets
Abstract
The invention provides a method and system for multicast group routing using unidirectional links. A set of uplink routers and a set of downlink routers provide a primary unidirectional distribution path from a set of sources to a set of destinations. A relatively smaller reverse communication channel is provided between the destinations and the sources. When a destination desires to add itself to, or take itself off, a multicast distribution group, one of the downlink routers acts as a proxy for that destination and so informs the relevant source. The selection of the proxy reporter for downlink routers or the querier for uplink routers does not require bi-directional communication between either of them, respectively.
Metadata
Assignee
- Cisco Technology, Inc.
Inventor
- Dino Farinacci
Application Information
Application Number:US 09/126,907
Filing Date:1998-07-31
Priority Date:1998-07-31
Art Unit:7
Classifications
IPC:
G06F 1342
Field of Search:
709217709221709228709238709250370 941370404370392365 49379 67
Patent Drawings (2 sheets)
Description
BACKGROUND OF THE INVENTION
[0002] 1. Field of the Invention
[0003] This invention relates to multicast packet routing.
[0004] 2. Related Art
[0005] In a computer network, it is often desirable to transmit messages from a single source to a selected plurality of destinations. This activity is often referred to as “multicast routing.” It is further desirable for the plurality of destinations to be capable of self-selection, so as to add themselves to, or to take themselves off, multicast distribution groups.
[0006] One method in the known art is the IGMP (Internet Group Management Protocol), in which messages are transmitted from a single source to a plurality of destinations, and in which destination devices can add themselves to, or take themselves off, multicast distribution groups. One problem with IGMP is that it uses bi-directional communication between routing devices (that receive messages from the source device) and the destination devices, so that routing devices intermediate between the source and destinations can determine how to route multicast messages. IGMP is not well suited when a primary communication path between the source and the destinations is unidirectional, such as in distribution systems using satellite communication.
[0007] Accordingly, it would be desirable to provide a method and system for multicast group routing using unidirectional links. This advantage is achieved in an embodiment of the invention in which a set of uplink routers and a set of downlink routers provide a unidirectional distribution path from a set of sources to a set of destinations, and in which some (but not all) downlink routers act as proxies for others to inform uplink routers whether distribution should occur over that unidirectional distribution path.
SUMMARY OF THE INVENTION
[0008] The invention provides a method and system for multicast group routing using unidirectional links. A set of uplink routers and a set of downlink routers provide a primary unidirectional distribution path from a set of sources to a set of destinations. A relatively smaller reverse communication channel is provided between the destinations and the sources. When a destination desires to add itself to, or take itself off, a multicast distribution group, one of the downlink routers acts as a proxy for that destination and so informs the relevant source. The selection of the proxy does not require bi-directional communication between either uplink routers or downlink routers.
BRIEF DESCRIPTION OF THE DRAWINGS
[0009] FIG. 1 shows a block diagram of a system for multicast group routing using unidirectional links.
[0010] FIG. 2 shows a process flow diagram for a method of operating a system for multicast group routing using unidirectional links.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] In the following description, a preferred embodiment of the invention is described with regard to preferred process steps and data structures. Those skilled in the art would recognize after perusal of this application that embodiments of the invention can be implemented using circuits adapted to particular process steps and data structures described herein, and that implementation of the process steps and data structures described herein would not require undue experimentation or further invention.
System Elements
[0012] FIG. 1 shows a block diagram of a system for multicast group routing using unidirectional links.
[0013] A system 100 includes a set of source devices 110, a set of uplink routers 120, a unidirectional communication pathway 130, a set of downlink routers 140, a set of destination devices 150, and a reverse communication channel 160.
[0014] As used herein, a “source device” includes any device taking on the role of a source in a multicast environment. There is no particular requirement that the source devices 110 must be individual devices; they can each be a single device, a set of cooperating devices, a portion of a device, or some combination thereof.
[0015] Similarly, as used herein, a “destination device” includes any device taking on the role of a destination in a multicast environment, such as using IGMP or a similar protocol. There is no particular requirement that the destination devices 150 must be individual devices; they can each be a single device, a set of cooperating devices, a portion of a device, or some combination thereof.
[0016] Each source device 110 is coupled to an uplink router 120 using a communication pathway 111, such as a direct communication link, a LAN (local area network), a WAN (wide area network), a network using IP (such as the internet), or some combination thereof. Each source device 110 is associated with an uplink router 120, and is disposed for bi-directional communication with its associated uplink router 120.
[0017] Each uplink router 120 is coupled to the unidirectional communication pathway 130 and is disposed for transmitting messages using the unidirectional communication pathway 130. Each uplink router 120 is also disposed for receiving messages using the reverse communication channel 160 or using a (relatively limited) reverse communication capability of the unidirectional communication pathway 130.
[0018] An uplink router 120 can be coupled to more than one unidirectional communication pathway 130 if the system 100 includes more than one unidirectional communication pathway 130. In this case, the uplink router 120 identifies multicast messages sent using one of the unidirectional communication pathways 130 to indicate which uplink router 120 and which unidirectional communication pathway 130 is being used.
[0019] An uplink router 120 can also perform a unicast communication protocol that doe s not require bi-directional communication, using the unidirectional communication pathway 130.
[0020] The unidirectional communication pathway 130 is disposed for communicating messages from uplink routers 120 to downlink routers 140.
[0021] In a preferred embodiment, the unidirectional communication pathway 130 comprises a satellite communication system, the uplink routers 120 comprise uplink transmitters in the satellite communication system, and the downlink routers 140 comprise downlink transmitters in the satellite communication system. Thus, each uplink transmitter is disposed for transmitting, but not necessarily for receiving; similarly, each downlink transmitter is disposed for receiving, but not necessarily for transmitting.
[0022] Each downlink router 140 is coupled to the unidirectional communication pathway 130 and is disposed for receiving messages using the unidirectional communication pathway 130.
[0023] The unidirectional communication pathway 130 is described herein as being disposed for communicating messages from uplink routers 120 to downlink routers 140, and the invention does not rely on any other capability of the unidirectional communication pathway 130. However, there is no particular requirement that the unidirectional communication pathway 130 is limited to that capability. For example, the unidirectional communication pathway 130 can have a relatively limited capability for communication in a reverse direction, and thus serve as part of or in cooperation with the reverse communication channel 160.
[0024] For example, in an embodiment where the unidirectional communication pathway 130 comprises a satellite communication system, it is possible for uplink routers 120 and downlink routers 140 to be co-located or logically coupled, so that a single device can have both capabilities and possibly perform both functions. Similarly, it is possible for some of the source devices 110 and some of the destination devices 150 to be co-located or logically coupled, so that 3 single device can have both capabilities and possibly perform both functions.
[0025] Each destination device 150 is coupled to a downlink router 140 using a communication pathway 151 similar to the communication pathway 111. Each destination device 150 is similarly associated with a downlink router 140, and is disposed for bi-directional communication with its associated downlink router 140.
[0026] A reverse communication channel 160 couples each downlink router 140 to each uplink router 120, so that the downlink routers 140 can send messages to the uplink routers 120. In a preferred embodiment, the reverse communication channel 160 is similar to the communication pathway 111.
[0027] The reverse communication channel 160 can also be unidirectional (in the reverse of the unidirectional communication pathway 130), but there is no particular requirement that the reverse communication channel 160 be either bi-directional or unidirectional.
[0028] The reverse communication channel 160 need not have a particularly wide bandwidth, as the number, frequency, and size of messages to be transmitted using the reverse communication channel 160 is expected to be relatively minor. However, there is no particular requirement that the reverse communication channel 160 be either fast or slow, or wide bandwidth or narrow bandwidth.
Method of Operation
[0029] FIG. 2 shows a process flow diagram for a method of operating a system for multicast group routing using unidirectional links.
[0030] A method 200 is performed by the system 100, including the source devices 110, the uplink routers 120, the unidirectional communication pathway 130, the downlink routers 140, the destination devices 150, and the reverse communication channel 160.
Transmitting Multicast Messages
[0031] At a flow point 210, one of the source devices 110 is ready to send multicast messages to selected destination devices 150.
[0032] At a step 211, one of the source devices 110 sends a message to its associated uplink router 120 for multicast distribution.
[0033] At a step 212, the associated uplink router 120 determines if there are any destination devices 150 that are group members associated with the group that is the target for the message and coupled to associated downlink routers 140. If so, the associated uplink router 120 transmits the message using the unidirectional communication pathway 130.
[0034] At a step 213, the downlink routers 140 receive the multicast message using the unidirectional communication pathway 130. Each particular downlink router 140 determines if there are any destination devices 150 that are group members associated with the group that is the target for the message, and associated with that particular downlink router 140. Each particular downlink router 140 discards the message if it does not have any such associated destination devices 150.
[0035] At a step 214, each downlink router 140 determines if it has one or more associated destination devices 150 that are selected for receipt of the multicast message.
[0036] At a step 215, each downlink router 140, forwards the multicast message to those associated destination devices 150 selected for receipt, if any.
[0037] At a flow point 220, the multicast messages have been delivered to selected destination devices 150.
Adding Destinations to Multicast Groups
[0038] At a flow point 230, one particular destination device 150 is ready to add itself to a multicast group.
[0039] At a step 231, the destination device 150 sends an IGMP Report message (that is, a request to be added to a multicast group), to its associated downlink router 140.
[0040] At a step 232, the associated downlink router 140 adds the particular destination device 150 to its distribution list for that group.
[0041] At a step 233, the associated downlink router 140 determines if there is any reason for it to report the addition to the multicast group. There is no reason for the associated downlink router 140 to make any report for either of the following conditions:
[0042] The uplink router 120 is already transmitting multicast message for the indicated group. or
[0043] The downlink router 140 is already receiving and distributing multicast messages for the indicated group.
[0044] These two conditions are functionally the same. There is also no reason for the associated downlink router 140 to report the addition if another downlink router 140 is already a proxy reporter for the indicated multicast group.
[0045] In any of these cases where no action is required, the associated downlink router 140 takes no further action, and the method 200 proceeds with the flow point 240. If not, the method 200 proceeds with the next step.
[0046] At a step 234, the associated downlink router 140 sends an IGMP Report message to the uplink router 120 associated with that multicast group, using the reverse communication channel 160.
[0047] In a preferred embodiment, the downlink router 140 sending the IGMP Report message uses an IP address for the uplink router 120 as the destination IP address for the uplink router 120. The destination IP address is not equal to the IP address for the interface the uplink router 120 has to the unidirectional communication pathway 130. Thus, the IGMP Report message is transmitted using the reverse communication channel 160. In the IGMP Report message, the downlink router 140 includes its own IP address for the unidirectional communication pathway 130 as the source IP address for the IGMP Report message.
[0048] In a preferred embodiment, the uplink router 120 should be configured so that all downlink routers 140 coupled thereto using the unidirectional communication pathway 130 are on the same subnet.
[0049] At a step 235, the associated uplink router 120 receives the IGMP Report message and adds the interface the uplink router 120 has to the unidirectional communication pathway 130 to its distribution list for the multicast group. The uplink router 120 can determine which such interface to a unidirectional communication pathway 130 to use in response to the source IP address in the IGMP Report message. Thereafter, the uplink router 120 receives and distributes messages for that multicast group using the unidirectional communication pathway 130.
[0050] At a step 236, the associated uplink router 120 transmits the IGMP Report message using the unidirectional communication pathway 130. All downlink routers 140 thus receive a copy of the IGMP Report message.
[0051] At a step 237, each downlink router 140 note that the downlink router 140 that initiated the IGMP Report message is the proxy reporter for all IGMP Report messages for that multicast group.
[0052] At a flow point 240, the particular destination device 150 has been added to the multicast group.
Removing Destinations from Multicast Groups
[0053] At a flow point 250, one particular destination device 150 is ready to leave a multicast group.
[0054] At a step 251, the destination device 150 sends an IGMP Leave message (that is, a request to leave a multicast group), to its associated downlink router 140.
[0055] At a step 252, the associated downlink router 140 removes the output interface associated with the particular destination device 150 from its distribution list for that group if there are no more group members associated with that output interface. If not, the associated downlink router 140 takes no further action, and the method 200 proceeds with the flow point 260. If so, the method 200 proceeds with the next step.
[0056] At a step 253, the associated downlink router 140 determines if another downlink router 140 is already a proxy reporter for the indicated multicast group. If so, the downlink router 140 takes no further action, and the method 200 proceeds with the flow point 260. If not, the method 200 proceeds with the next step.
[0057] At a step 254, the associated downlink router 140 sends an IGMP Leave message to the uplink router 120 associated with that multicast group, using the reverse communication channel 160.
[0058] At a step 255, the uplink router 120 associated with that multicast group, after a (relatively small) period of time, removes the unidirectional interface if no other downlink router 140 sends an IGMP Report message (thus becoming a new proxy reporter).
[0059] At a step 256, the uplink router 120 transmits the IGMP Leave message using the unidirectional communication pathway 130. All downlink routers 140 thus receive a copy of the IGMP Leave message.
[0060] At a step 257, each downlink router 140 determines that the proxy reporter for that multicast group is no longer performing that function. As a consequence, another one of the downlink routers 140 is selected as a proxy reporter. This occurs when the next downlink router 140 sends an IGMP Report message. It is expected that the next downlink router 140 to be selected as the proxy reporter will be randomly distributed among the downlink routers 140.
[0061] At a flow point 260, the particular destination device 150 has left the indicated multicast group.
IGMP Query Messages
[0062] At a flow point 270, the uplink routers 120 are ready to send IGMP Query messages.
[0063] At a step 271, each uplink router 120 sends an IGMP Query message, using the unidirectional communication pathway 130. Each uplink router 120 does not receive the IGMP Query messages sent by each other uplink router 120.
[0064] At a step 272, each downlink router 140 receives the IGMP Query message, and notes the status of a single elected uplink querier.
[0065] At a step 273, each downlink router 140 sets its RPF interface, for all sources, in response to the IGMP Query message sent by the elected uplink querier. However, the unicast interface is not Necessarily the same interface as the multicast interface between each particular downlink router 140 and each particular uplink router 120.
[0066] At a step 274, each downlink router 140 selects one of the uplink routers 120 as the destination for IGMP helpered reports.
[0067] In a preferred embodiment, each downlink router 140 selects the uplink routers 120 with the lowest IP address as the elected uplink querier. However, in alternative embodiments, other techniques could be used that each downlink router 140 can determine individually and that result in consensus among the downlink routers 140 as to which uplink router 120 should be the elected uplink querier.
[0068] At a step 275, when the downlink routers 140 each determine that any uplink router 120 is no longer sending IGMP Query messages (such as due to a service interruption or configuration charge), each such downlink router 140 selects a new elected uplink querier for each multicast group.
[0069] At a flow point 280, the IGMP Query messages have been processed.
Alternative Embodiments
[0070] Although preferred embodiments are disclosed herein, many variations are possible which remain within the concept, scope, and spirit of the invention, and these variations would become clear to those skilled in the art after perusal of this application.
Claims
What is claimed is:
1. A method, comprising the following steps:
transmitting multicast messages from a set of sending devices to a set of uplink routers;
transmitting said multicast messages from said set of uplink routers to a set of downlink routers, using a substantially unidirectional communication path;
transmitting said multicast messages from said set of downlink routers to a set of destination devices; and
altering distribution of said multicast messages from said set of sending devices to said set of destination devices using a multicast group management protocol, said steps for altering including communicating protocol messages from said set of downlink routers to said set of uplink routers using a reverse communication path, said reverse communication path having substantially less bandwidth than said substantially unidirectional communication path, wherein one of said downlink routers acts as a proxy for said set of downlink routers, the altering of the distribution of the multicast messages also involving changing a membership status of at least one destination device in the set of destination devices, the membership status being with regard to membership in at least one of a plurality of multicast message destination groups, the changing of the membership status being initiated by transmission by the one destination device to one downlink router associated with the one destination device of a request to change the membership status, the one downlink router reporting the request to one uplink router associated with the group, unless at least one predetermined condition exists, via the reverse communication path.
2. A method according to claim 1, wherein the condition comprises the one uplink router already transmitting multicast messages associated with the group.
3. A method according to claim 1, wherein the condition comprises the one downlink router already receiving and distributing multicast messages associated with the group.
4. A method according to claim 1, wherein the condition comprises another downlink router being a proxy reporter for the group.
5. A method, comprising the following steps:
transmitting multicast messages from a set of sending devices to a set of uplink routers;
transmitting said multicast messages from said set of uplink routers to a set of downlink routers, using a substantially unidirectional communication path;
transmitting said multicast messages from said set of downlink routers to a set of destination devices; and
altering distribution of said multicast messages from said set of sending devices to said set of destination devices using a multicast group management protocol, said steps for altering including communicating protocol messages from said set of downlink routers to said set of uplink routers using a reverse communication path, said reverse communication path having substantially less bandwidth than said substantially unidirectional communication path, wherein one of said uplink routers acts as an elected querier for said set of uplink routers, the altering of the distribution of the multicast messages also involving changing a membership status of at least one destination device in the set of destination devices, the membership status being with regard to membership in at least one of a plurality of multicast message destination groups, the changing of the membership status being initiated by transmission by the one destination device to one downlink router associated with the one destination device of a request to change the membership status, the one downlink router reporting the request to one uplink router associated with the group, unless at least one predetermined condition exists, via the reverse communication path.
6. A method according to claim 5, wherein the condition comprises the one uplink router already transmitting multicast messages associated with the group.
7. A method according to claim 5, wherein the condition comprises the one downlink router already receiving and distributing multicast messages associated with the group.
8. A method according to claim 5, wherein the condition comprises another downlink router being a proxy reporter for the group.
9. A system comprising:
a receiver that receives multicast messages transmitted from uplink routers via a substantially unidirection communication path;
a transmitter that transmits the messages received from the uplink routers to destination devices; and
the system being able to effect an alteration in distribution of the messages to the destination devices using a multicast group protocol, the system effecting the alteration by communicating protocol messages to the uplink routers using a reverse communication path having substantially less bandwidth than said substantially unidirectional communication path, the alteration involving changing a membership status of at least one destination device, the membership status being with regard to membership in at least one of a plurality of multicast message destination groups, the changing of the membership status being initiated by transmission by the one destination device to the system of a request to change the membership status, the system reporting the request to one uplink router associated with the group, unless at least one predetermined condition exists, via the reverse communication path.
10. A system according to claim 9, wherein the condition comprises the one uplink router already transmitting multicast messages associated with the group.
11. Apparatus comprising:
means for receiving multicast messages transmitted from uplink routers via a substantially unidirection communication path;
means for transmitting the messages received from the uplink routers to destination devices; and
means for effecting an alteration in distribution of the messages to the destination devices using a multicast group protocol, the system effecting the alteration by communicating protocol messages to the uplink routers using a reverse communication path having substantially less bandwidth than said substantially unidirectional communication path, the alteration involving changing a membership status of at least one destination device, the membership status being with regard to membership in at least one of a plurality of multicast message destination groups, the changing of the membership status being initiated by transmission by the one destination device to the system of a request to change the membership status, the system reporting the request to one uplink router associated with the group, unless at least one predetermined condition exists, via the reverse communication path.
12. Apparatus according to claim 11, wherein the condition comprises the one uplink router already transmitting multicast messages associated with the group.
Patent Citations (197)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| USRe.33900 | 1992-04-01 | Howson | Applicant |
| US4131767 | 1978-12-01 | Weinstein | Applicant |
| US4161719 | 1979-07-01 | Parikh et al. | Applicant |
| US4316284 | 1982-02-01 | Howson | Applicant |
| US4397020 | 1983-08-01 | Howson | Applicant |
| US4419728 | 1983-12-01 | Larson | Applicant |
| US4424565 | 1984-01-01 | Larson | Applicant |
| US4437087 | 1984-03-01 | Petr | Applicant |
| US4438511 | 1984-03-01 | Baran | Applicant |
| US4439763 | 1984-03-01 | Limb | Applicant |
| US4445213 | 1984-04-01 | Baugh et al. | Applicant |
| US4446555 | 1984-05-01 | Devault et al. | Applicant |
| US4456957 | 1984-06-01 | Schieltz | Applicant |
| US4464658 | 1984-08-01 | Thelen | Applicant |
| US4499576 | 1985-02-01 | Fraser | Applicant |
| US4506358 | 1985-03-01 | Montgomery | Applicant |
| US4507760 | 1985-03-01 | Fraser | Applicant |
| US4532626 | 1985-07-01 | Flores et al. | Applicant |
| US4644532 | 1987-02-01 | George et al. | Applicant |
| US4646287 | 1987-02-01 | Larson et al. | Applicant |
| US4677423 | 1987-06-01 | Benvenuto et al. | Applicant |
| US4679189 | 1987-07-01 | Olson et al. | Applicant |
| US4679227 | 1987-07-01 | Hughes-Hartogs | Applicant |
| US4723267 | 1988-02-01 | Jones et al. | Applicant |
| US4731816 | 1988-03-01 | Hughes-Hartogs | Applicant |
| US4750136 | 1988-06-01 | Arpin et al. | Applicant |
| US4757495 | 1988-07-01 | Decker et al. | Applicant |
| US4763191 | 1988-08-01 | Gordon et al. | Applicant |
| US4769810 | 1988-09-01 | Eckberg, Jr. et al. | Applicant |
| US4769811 | 1988-09-01 | Eckberg, Jr. et al. | Applicant |
| US4771425 | 1988-09-01 | Baran et al. | Applicant |
| US4819228 | 1989-04-01 | Baran et al. | Applicant |
| US4827411 | 1989-05-01 | Arrowood et al | Applicant |
| US4833706 | 1989-05-01 | Hughes-Hartogs | Applicant |
| US4835737 | 1989-05-01 | Herrig et al. | Applicant |
| US4879551 | 1989-11-01 | Georgiou et al. | Applicant |
| US4893306 | 1990-01-01 | Chao et al. | Applicant |
| US4903261 | 1990-02-01 | Baran et al. | Applicant |
| US4922486 | 1990-05-01 | Lidinsky et al. | Applicant |
| US4933937 | 1990-06-01 | Konishi | Applicant |
| US4960310 | 1990-10-01 | Cushing | Applicant |
| US4962497 | 1990-10-01 | Ferenc et al. | Applicant |
| US4962532 | 1990-10-01 | Kasirai et al. | Applicant |
| US4965767 | 1990-10-01 | Kinoshita et al. | Examiner |
| US4965772 | 1990-10-01 | Daniel et al. | Applicant |
| US4970678 | 1990-11-01 | Sladowski et al. | Applicant |
| US4979118 | 1990-12-01 | Kheradpir | Applicant |
| US4980897 | 1990-12-01 | Decker et al. | Applicant |
| US4991169 | 1991-02-01 | Davis et al. | Applicant |
| US5003595 | 1991-03-01 | Collins et al. | Applicant |
| US5014265 | 1991-05-01 | Hahne et al. | Applicant |
| US5020058 | 1991-05-01 | Holden et al. | Applicant |
| US5033076 | 1991-07-01 | Jones et al. | Applicant |
| US5034919 | 1991-07-01 | Sasai et al. | Examiner |
| US5054034 | 1991-10-01 | Hughes-Hartogs | Applicant |
| US5059925 | 1991-10-01 | Weisbloom | Applicant |
| US5072449 | 1991-12-01 | Enns et al. | Applicant |
| US5088032 | 1992-02-01 | Bosack | Applicant |
| US5095480 | 1992-03-01 | Fenner | Applicant |
| US5115431 | 1992-05-01 | Williams et al. | Applicant |
| US5128945 | 1992-07-01 | Enns et al. | Applicant |
| US5136580 | 1992-08-01 | Videlock et al. | Applicant |
| US5166930 | 1992-11-01 | Braff et al. | Applicant |
| US5199049 | 1993-03-01 | Wilson | Applicant |
| US5206886 | 1993-04-01 | Bingham | Applicant |
| US5208811 | 1993-05-01 | Kashio et al. | Applicant |
| US5212686 | 1993-05-01 | Joy et al. | Applicant |
| US5224099 | 1993-06-01 | Corbalis et al. | Applicant |
| US5226120 | 1993-07-01 | Brown et al. | Applicant |
| US5228062 | 1993-07-01 | Bingham | Applicant |
| US5229994 | 1993-07-01 | Balzano et al. | Applicant |
| US5237564 | 1993-08-01 | Lespagnol et al. | Applicant |
| US5241682 | 1993-08-01 | Bryant et al. | Applicant |
| US5243342 | 1993-09-01 | Kattemalalavadi et al. | Applicant |
| US5243596 | 1993-09-01 | Port et al. | Applicant |
| US5247516 | 1993-09-01 | Bernstein et al. | Applicant |
| US5249178 | 1993-09-01 | Kurano et al. | Applicant |
| US5253251 | 1993-10-01 | Aramaki | Applicant |
| US5255291 | 1993-10-01 | Holden et al. | Applicant |
| US5260933 | 1993-11-01 | Rouse | Applicant |
| US5260978 | 1993-11-01 | Fleischer et al. | Applicant |
| US5268592 | 1993-12-01 | Bellamy et al. | Applicant |
| US5268900 | 1993-12-01 | Hluchyj et al. | Applicant |
| US5271004 | 1993-12-01 | Proctor et al | Applicant |
| US5274631 | 1993-12-01 | Bhardwaj | Applicant |
| US5274635 | 1993-12-01 | Rahman et al. | Applicant |
| US5274643 | 1993-12-01 | Fisk | Applicant |
| US5280470 | 1994-01-01 | Buhrke et al. | Applicant |
| US5280480 | 1994-01-01 | Pitt et al. | Applicant |
| US5280500 | 1994-01-01 | Mazzola et al. | Applicant |
| US5283783 | 1994-02-01 | Nguyen et al. | Applicant |
| US5287103 | 1994-02-01 | Kasprzyk et al. | Applicant |
| US5287453 | 1994-02-01 | Roberts | Applicant |
| US5291482 | 1994-03-01 | McHarg et al. | Applicant |
| US5305311 | 1994-04-01 | Lyles | Applicant |
| US5307343 | 1994-04-01 | Bostica et al. | Applicant |
| US5309437 | 1994-05-01 | Perlman et al. | Applicant |
| US5311509 | 1994-05-01 | Heddes et al. | Applicant |
| US5313454 | 1994-05-01 | Bustini et al. | Applicant |
| US5313582 | 1994-05-01 | Hendel et al. | Applicant |
| US5317562 | 1994-05-01 | Nardin et al. | Applicant |
| US5319644 | 1994-06-01 | Liang | Applicant |
| US5327421 | 1994-07-01 | Hiller et al. | Applicant |
| US5331637 | 1994-07-01 | Francis et al. | Applicant |
| US5345445 | 1994-09-01 | Hiller et al. | Applicant |
| US5345446 | 1994-09-01 | Hiller et al. | Applicant |
| US5359592 | 1994-10-01 | Corbalis et al. | Applicant |
| US5361250 | 1994-11-01 | Nguyen et al. | Applicant |
| US5361256 | 1994-11-01 | Doeringer et al. | Applicant |
| US5361259 | 1994-11-01 | Hunt et al. | Applicant |
| US5365524 | 1994-11-01 | Hiller et al. | Applicant |
| US5367517 | 1994-11-01 | Cidon et al. | Applicant |
| US5371852 | 1994-12-01 | Attanasio et al. | Applicant |
| US5386567 | 1995-01-01 | Lien et al. | Applicant |
| US5390170 | 1995-02-01 | Sawant et al. | Applicant |
| US5390175 | 1995-02-01 | Hiller et al. | Applicant |
| US5394394 | 1995-02-01 | Crowther et al. | Applicant |
| US5394402 | 1995-02-01 | Ross | Applicant |
| US5400325 | 1995-03-01 | Chatwani et al. | Applicant |
| US5408469 | 1995-04-01 | Opher et al. | Applicant |
| US5416842 | 1995-05-01 | Aziz | Applicant |
| US5422880 | 1995-06-01 | Heitkamp et al. | Applicant |
| US5422882 | 1995-06-01 | Hiller et al. | Applicant |
| US5423002 | 1995-06-01 | Hart | Applicant |
| US5426636 | 1995-06-01 | Hiller et al. | Applicant |
| US5428607 | 1995-06-01 | Hiller et al. | Applicant |
| US5430715 | 1995-07-01 | Corabalis et al. | Applicant |
| US5430729 | 1995-07-01 | Rahnema | Applicant |
| US5442457 | 1995-08-01 | Najafi | Applicant |
| US5442630 | 1995-08-01 | Gagliardi et al. | Applicant |
| US5452297 | 1995-09-01 | Hiller et al. | Applicant |
| US5473599 | 1995-12-01 | Li et al. | Applicant |
| US5473607 | 1995-12-01 | Hausman et al. | Applicant |
| US5477541 | 1995-12-01 | White et al. | Examiner |
| US5485455 | 1996-01-01 | Dobbins et al. | Applicant |
| US5490140 | 1996-02-01 | Abensour et al. | Applicant |
| US5490258 | 1996-02-01 | Fenner | Applicant |
| US5491687 | 1996-02-01 | Christensen et al. | Applicant |
| US5491804 | 1996-02-01 | Heath et al. | Applicant |
| US5497368 | 1996-03-01 | Reijnierse et al. | Applicant |
| US5504747 | 1996-04-01 | Sweasey | Applicant |
| US5509006 | 1996-04-01 | Wilford et al. | Applicant |
| US5517494 | 1996-05-01 | Green | Applicant |
| US5519704 | 1996-05-01 | Farinacci et al. | Applicant |
| US5519858 | 1996-05-01 | Walton et al. | Applicant |
| US5526489 | 1996-06-01 | Nilakantan et al. | Applicant |
| US5530963 | 1996-06-01 | Moore et al. | Applicant |
| US5535195 | 1996-07-01 | Lee | Applicant |
| US5539734 | 1996-07-01 | Burwell et al. | Applicant |
| US5541911 | 1996-07-01 | Nilakantan et al. | Applicant |
| US5546370 | 1996-08-01 | Ishikawa | Applicant |
| US5555244 | 1996-09-01 | Gupta et al. | Applicant |
| US5561669 | 1996-10-01 | Lenney et al. | Applicant |
| US5583862 | 1996-12-01 | Callon | Applicant |
| US5586121 | 1996-12-01 | Moura et al. | Examiner |
| US5592470 | 1997-01-01 | Rudrapatna et al. | Applicant |
| US5598581 | 1997-01-01 | Daines et al. | Applicant |
| US5600798 | 1997-02-01 | Cherukuri et al. | Applicant |
| US5602770 | 1997-02-01 | Ohira | Examiner |
| US5604868 | 1997-02-01 | Komine et al. | Applicant |
| US5608726 | 1997-03-01 | Virgile | Applicant |
| US5617417 | 1997-04-01 | Sathe et al. | Applicant |
| US5617421 | 1997-04-01 | Chin et al. | Applicant |
| US5630125 | 1997-05-01 | Zellweger | Applicant |
| US5631908 | 1997-05-01 | Saxe | Applicant |
| US5632021 | 1997-05-01 | Jennings et al. | Applicant |
| US5634010 | 1997-05-01 | Ciscon et al. | Applicant |
| US5638359 | 1997-06-01 | Peltola et al. | Applicant |
| US5644718 | 1997-07-01 | Belove et al. | Applicant |
| US5647002 | 1997-07-01 | Brunson | Examiner |
| US5659684 | 1997-08-01 | Giovannoni et al. | Applicant |
| US5666353 | 1997-09-01 | Klausmeier et al. | Applicant |
| US5673265 | 1997-09-01 | Gupta et al. | Applicant |
| US5678006 | 1997-10-01 | Valizadeh et al. | Applicant |
| US5680116 | 1997-10-01 | Hashimoto et al. | Applicant |
| US5684797 | 1997-11-01 | Aznar et al. | Applicant |
| US5687324 | 1997-11-01 | Green et al. | Applicant |
| US5689506 | 1997-11-01 | Chiussi et al. | Applicant |
| US5694390 | 1997-12-01 | Yamato et al. | Applicant |
| US5724351 | 1998-03-01 | Chao et al. | Applicant |
| US5740097 | 1998-04-01 | Satoh | Examiner |
| US5742905 | 1998-04-01 | Pepe et al. | Examiner |
| US5748186 | 1998-05-01 | Raman | Applicant |
| US5748617 | 1998-05-01 | McLain, Jr. | Applicant |
| US5754547 | 1998-05-01 | Nakazawa | Applicant |
| US5790809 | 1998-08-01 | Holmes | Examiner |
| US5802054 | 1998-09-01 | Bellenger | Applicant |
| US5809415 | 1998-09-01 | Ayanoglu et al. | Examiner |
| US5835710 | 1998-10-01 | Nagami et al. | Examiner |
| US5841874 | 1998-11-01 | Kempke et al. | Examiner |
| US5854903 | 1998-12-01 | Morrison et al. | Applicant |
| US5856981 | 1999-01-01 | Voelker | Applicant |
| US5892924 | 1999-04-01 | Lyon et al. | Applicant |
| US5898686 | 1999-04-01 | Virgile | Applicant |
| US5903559 | 1999-05-01 | Acharya et al. | Applicant |
| US6006264 | 1999-12-01 | Colby et al. | Examiner |
| US6038594 | 2000-03-01 | Puente et al. | Examiner |
Non-Patent Literature (11)
- Allen, M., “Novell IPX Over Various WAN Media (IPXW AN),” Network Working Group, RFC 1551, Dec. 1993, pp. 1-22.Applicant
- Becker, D., “3c589.c: A 3c589 EtherLink3 ethernet driver for linux,” becker @CESDIS.gsfc.nasa.gov, May 3, 1994, pp. 1-13.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
- Zhang, et al., “Rate-Controlled Static-Priority Queueing,” INFOCOM 1993, pp. 227-236.Applicant
- William Stallings, Data and Computer Communications, pp: 329-333, Prentice Hall, Upper Saddle River, New Jersey 07458, 1997.Applicant