US 6,182,224 B2Grant
Enhanced network services using a subnetwork of communicating processors
Issue Date:2001-01-30
•67 Claims
•8 Drawing Sheets
Abstract
A method and system for providing enhanced services for a network. The enhanced services use information about the network which is available to a subnet of communicating processors (such as a set of routers), collectively executing a common distributed technique for disseminating that network information. The router subnet collects network topology information and provides a service using that network topology information, responsive to requests from non-routers coupled to the network (such as a set of host processors). The router subnet also collects information advertised by hosts coupled to the network, and disseminates that host information to substantially all routers, using the common distributed technique for disseminating network topology information. The host information may comprise information about server processes available at the originating host (such as what services are available and to which users those services are available), or may comprise information about client processes operating at the originating host (such as which users are operating those client processes and which services they desire).
Metadata
Assignee
- Cisco Systems, Inc.
Inventors
- Stuart G. Phillips
- Anthony J. Li
- David M. Katz
Application Information
Application Number:US 08/582,073
Filing Date:1996-01-02
Priority Date:1995-09-29
Art Unit:7
Classifications
IPC:
G06F 1214
Field of Search:
3951870139520033952006839520072709229709239709240709242709238713200713201
Patent Drawings (8 sheets)
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority of Provisional Application Serial No. 60/004,568, having the same title, filed Sep. 29, 1995 in the name of the same inventors, Express Mail No. EM302068128US, D'Alessandro+Ritchie Docket No. CIS-008, hereby incorporated by reference as if fully set forth herein.
BACKGROUND OF THE INVENTION
[0003] 1. Field of the Invention
[0004] This invention relates to enhanced network services using a subnetwork of communicating processors.
[0005] 2. Description of Related Art
[0006] A computer network having more than one possible message delivery path, such as for example a network of computer networks (an “internetwork”), generally comprises a set of processors which have the task of routing each message from its source to its destination. These processors (herein called “routers”, but sometimes called “bridges”, “brouters”, or other terms) generally interoperate using a common distributed routing technique. For example, (1) routers generally exchange information about routing conditions in the network, so as to globally inform all routers of conditions which are detected locally, (2) routers generally each route messages according to the same techniques using the same routing technique.
[0007] The collection of routers (herein called the “subnet” of routers) thus has access to a rich collection of distributed information about the status of the network needed for routing messages therein, including detailed and up-to-date information about the network topology, relative distance measures in the network, administrative policies in force in the network (such as, for example, network “firewalls” or routers which will route only a subset of messages), and other information. It would be advantageous to provide at least some of this distributed information to applications which might use it to provide enhanced services. Examples of such enhanced services, and how they would be provided, are described herein.
[0008] The router subnet also provides a powerful and available resource for distributing other information, not strictly required for the task of routing messages in the network, such as, for example, relative load at each host in the network. It would be advantageous to disseminate this information and provide at least some of it to applications which might use it to provide enhanced services. Examples of such enhanced services, and how they would be provided, are described herein.
[0009] Accordingly, it would be advantageous to provide a method and system for enhanced network services using a subnetwork of communicating processors.
[0010] The following U.S. Patent(s) or other documents may be pertinent:
[0011] R. Srinivasan, “RPC: Remote Procedure Call Protocol Specification Version 2”, Network Working Group RFC 1831 (August 1995).
[0012] The pertinence of the related art will also be apparent to those skilled in the art after perusal of this application.
SUMMARY OF THE INVENTION
[0013] The invention provides a method and system for providing enhanced services for a network, using a subnetwork of communicating processors. The enhanced services use information about the network which is available to the subnet of communicating processors (such as a set of routers), interoperating using a common distributed technique for disseminating that network information. In a first aspect of the invention, the router subnet collects network topology information and provides a service using that network topology information, responsive to requests from non-routers (such as host processors) coupled to the network. The network topology information comprises information about paths and routes, including bandwidth, connectivity, delay, traffic reservations, and administrative policies applicable to those paths and routes. Routers providing the enhanced service have the option of requiring authentication for service requests.
[0014] For a first example, the router subnet provides an enhanced distributed naming service which, in addition to translating server names into host addresses, also orders those host addresses by relative distance in the network, or by another criterion designated by the client. For a second example, the router subnet provides an enhanced message delivery service which, in addition to delivering a message to a plurality of destinations, assures that all destinations receive the message at substantially the same time.
[0015] In a second aspect of the invention, the router subnet collects information advertised by hosts coupled to the network, and disseminates that host information to substantially all routers, using the common distributed technique for disseminating network topology information. In a first preferred embodiment, the host information comprises information about server processes available at the originating host (such as what services are available and to which users those services are available). In a second preferred embodiment, the host information comprises information about client processes operating at the originating host (such as which users are operating those client processes and which services they desire).
[0016] For a first example, hosts advertise their relative load for dissemination by the router subnet, and the router subnet provides an enhanced distributed naming service which, in addition to translating server names into host addresses, also orders those host addresses by relative load (or by both relative distance and relative load). Similarly, hosts may also advertise other server information, such as cost for performing the service, delay in performing the service, or other administrative policies which would affect the choice of server.
[0017] For a second example, hosts advertise their logged-in users for dissemination by the router subnet, and the router subnet provides an enhanced message-delivery service which, in addition to receiving messages for delivery, also delivers those messages to the host where the destination user is logged-in. Similarly, hosts may also advertise other client information, such as willingness to pay for performing a designated service, which the router subnet may disseminate for responses by servers or by other clients.
BRIEF DESCRIPTION OF THE DRAWINGS
[0018] FIG. 1A shows a block diagram of a system for providing enhanced services, and also shows a block diagram of a system for providing enhanced services using server advertisements, in a computer network.
[0019] FIG. 1B shows a flow diagram of a method for providing enhanced services, and also shows a flow diagram of a method for providing enhanced services using server advertisements in a computer network as shown in FIG. 1A.
[0020] FIG. 2A shows a block diagram of a system for providing synchronized message receipt in a computer network.
[0021] FIG. 2B shows a flow diagram of a method for providing synchronized message receipt in a computer network as shown in FIG. 2A.
[0022] FIG. 3A shows a block diagram of a system for providing enhanced services using both client and server advertisements, in a computer network.
[0023] FIG. 3B shows a flow diagram of a method for providing enhanced services using both client and server advertisements, in a computer network as shown in FIG. 3A.
[0024] FIG. 4A shows formats for a set of packets for use with an authenticated remote procedure call transport (“ART”) protocol.
[0025] FIG. 4B shows a flow diagram for an authenticated remote procedure call transport protocol.
DESCRIPTION OF THE PREFERRED EMBODIMENT
[0026] In the following description, a preferred embodiment of the invention is described with regard to preferred process steps and data structures. However, those skilled in the art would recognize, after perusal of this application, that embodiments of the invention may be implemented using a set of general purpose computers operating under program control, and that modification of a set of general purpose computers to implement the process steps and data structures described herein would not require undue invention.
Providing Enhanced Network Services
[0027] FIG. 1A shows a block diagram of a system for providing enhanced services, in a computer network. FIG. 1B shows a flow diagram of a method for providing enhanced services, in a computer network as shown in FIG. 1A.
[0028] In an internetwork 100 to which a network 101 is coupled, a client process 102 on a client node 103 contacts a server process 104 on a server node 105, to obtain data or a service. For example, the data may comprise a file located at the server node 105; the service may comprise conducting a computation, providing data in response to search parameters, or even just providing the current time.
[0029] The verb “contacts” refers to communication between the client process 102 and the server process 104 using messages comprising message packets which are transmitted using the internetwork 100 between the client process 102 and the server process 104. Messages and message packets are transmitted using the internetwork 100 using a subnet 110 of routers 111. Each router 111 executes a routing technique which causes the routers 111 to collectively interoperate using a common distributed technique for routing messages and distributing information about the internetwork 100. This network information is stored at each router 111 in one or more network tables 112, and generally comprises information about paths and routes, such as bandwidth, connectivity, delay, traffic reservations, and administrative policies applicable to those paths and routes.
[0030] Particular routing techniques, such as IGRP, AppleTalk, and IPX, are known in the art of networking.
[0031] A method 150 is conducted in cooperation by various nodes and processes coupled to the internetwork 100. At a flow point 160 for the method 150, the client process 102 desires to contact a server process 104, the latter of which is coupled to the internetwork 100.
[0032] At a step 161, the client process 102 first contacts a name server 105, which preferably comprises a server process 104 executing on a server node 103 for which the client process 102 already has a network address, using a name-request message 121. In this example, the name server 105 is shown executing on a different node and coupled to the same network 101 as the client node 103, but there is no particular requirement that the name server 105 is in fact so disposed. For example, the name server 105 may be located at the same node as the client process 102, or may be coupled to a different network 101 on the internetwork 100, so long as the client process 102 has available to it a sufficient network address to transmit the name-request message 121 to the name server 105.
[0033] In a preferred embodiment, the name server 105 comprises a DNS name server operating according to the DNS protocol.
[0034] The name-request message 121 asks the name server 105 to translate an identifier for the service provided into a network address for a server process 104 providing that service. For example, the identifier may comprise a host name for a node coupled to the internetwork 100, such as “sanjose.cisco.com”, and the name server 105 may translate that host name into an IP address for that node, such as “3.141.59.26”.
[0035] At a step 162, the name server 105 receives the name-request message 121, parses the name-request message 121 to determine the name to be translated, looks up the name in a table it maintains for translating names into network addresses, and transmits a name-response message 122 comprising one or more network addresses to the client process 102 at the client node 103.
[0036] In general, the name to be translated may specify a service which is provided by more than one server process 104 or by more than one server node 105, so that the name server 105 has more than one network address to provide in the name-response message 122. In a preferred embodiment, the name server 105 provides all such network addresses in the name-response message 122. Order is not critical at this flow point of the method 150.
[0037] At a step 163, the client process 102 receives the name-response message 122 and parses the name-response message 122 to determine the network addresses provided by the name server 105. The client process 102 then contacts a router 111 using an order-request message 123.
[0038] The order-request message 123 asks the router 111 to order a set of addresses by their relative distance on the internet-work 100. Preferably, the client process 102 packages the addresses from the name-response message 122 into the order-request message 123.
[0039] At a step 164, the router 111 receives the order-request message 123, parses the order-request message 123 to determine the set of addresses, looks up each address in its network tables 112 to determine a relative distance for that network address, orders the network addresses by relative distance, and transmits an order-response message 124 comprising the network addresses ordered relative distance.
[0040] The relative distance for each network address may differ at different times, so the order provided by the router 111 in the order-response message 124 may also differ in response to order-request messages 123 transmitted at different times.
[0041] In a preferred embodiment, the relative distance for each network address is computed in response to the expected time delay in delivering a message from the client node 103 to the server node 105. It is expected that this expected time delay will be nearly the same as the expected time delay from the name server 105. In alternative embodiments described below in which the name server 105 orders the addresses in response to relative distance information from the router 111, the ordering may turn out to differ from an ordering for the client node 103, but this is not expected to be important unless the name server 105 is at a substantial relative distance from the client node 103.
[0042] In alternative embodiments, the relative distance for each network address may also be computed in response to other information available to the router 111 in its network tables 112, including for example (1) an expected bandwidth of a path from the client node 103 to the server node 105, (2) any traffic reservations on paths between the client node 103 to the server node 105, or (3) any administrative policies applicable to those paths between the client node 103 to the server node 105. For example, if a required path to one of the server nodes 105 is known to the router 111 to be heavily trafficked between the hours of 9:00 a.m. and 5:00 p.m., that server node 105 may be assigned a substantially higher relative distance responsive to that information.
[0043] Although in a preferred embodiment, the name-request message 121 and the order-request message 123 are both preferably transmitted by the client process 102, in alternative embodiments, alternative arrangements are possible which would obtain the same information for the client process 102. Such alternative arrangements would be clear to those skilled in the art after perusing this application, and are within the scope and spirit of the invention. In a first alternative embodiment, the name server 105 may obtain an ordering of network addresses from the router 111, and may order the network addresses in the name-response message 122. To do so, the name server 105 may transmit an order-request message 123 to the router 111 and use the results it receives in the order-response message 124. In a second alternative embodiment, the name server 105 may be located at the router 111, and may order the network addresses in the name-response message 122 in response to direct access to the network tables 112.
[0044] In a preferred embodiment, the network address for one or more particular server nodes 105 may be restricted to those client processes 102 with sufficient authorization. In such a case, the name server 105 would require that the client process 102 is authenticated, to determine that the name-request message 121 really comes from the client process 102 and not someone else, and that the client process 102 has sufficient permissions, in particular, that the name server 105 has been informed that the client process 102 is authorized to receive that information. A preferred authentication process is described below with reference to FIG. 4.
[0045] In a preferred embodiment, the relative distance or other ordering information may also be restricted to those client processes 102 with sufficient authorization. In such a case, the router 111 would require that the client process 102 is authenticated, to determine that the name-request message 121 really comes from the client process 102 and not someone else, and that the client process 102 has sufficient permissions, in particular, that the router 111 has been informed that the client process 102 is authorized to receive that information.
[0046] In some cases, the router 111 may have insufficient information to respond to the order-request message 123 on its own. In such a case, the router 111 may forward the order-request message 123 (or another message with similar information) to a second router 111. The second router 111 may also find that it must forward the order-request message 123 or other message, until one or more routers are reached which, individually or collectively, do have sufficient information to respond to the original order-request message 123.
[0047] At a step 165, the client process 102 selects a first one of the network addresses, preferably the network address with the smallest relative distance, and contacts the server process 104 on the server node 105 with that network address. In the case that the client process 102 is unable to contact the server process 104 at the first network address, the client process 102 selects another, preferably the network address with the next smallest relative distance, and contacts the server process 104 on the server node 105 with that network address. The client process 102 repeats this step until one of the server processes 104 is contacted or the set of network addresses is exhausted.
Automated Resource Distribution
[0048] A first example enhanced network service is automated distribution of resources such as services. Some services are readily distributed by providing more than one service provider, each of which can fully provide substantially the same service. For example, a service providing a collection of data may be duplicated by copying the data to multiple sites; a service providing a program to be executed may be duplicated by copying the program to multiple sites, and providing resources for executing the program at each of those sites.
[0049] In this example enhanced service, a resource to be automatically distributed is embodied in server processes 104 at a plurality of server nodes 105. For example, the resource may comprise one of the following:
[0050] an FTP directory, such as a directory of files which may be copied from the server node 105 to the client node 103 using the “FTP” protocol;
[0051] a network news server, such as a server for providing messages posted to “network news” or to a bulletin board system, and distributed substantially throughout a portion of the internetwork 100;
[0052] a World Wide Web page, such as a file comprising a set of data to be displayed, possibly including text, graphics, display commands, or motion picture data, and comprising one or more hypertext links to other such files;
[0053] a database and search engine, such as a program for receiving search requests, executing those search requests against a database, and providing the results of such search requests; or
[0054] a time server, such as a program for providing a time of day or similar globally available information, such as a dictionary server, spell-checker or thesaurus.
[0055] Other and further possibilities will readily occur to those skilled in the art after perusal of this application; such other and further possibilities would not require invention or undue experiment, and are within the scope and spirit of the invention.
[0056] The name servers 105 which translate the service name into network addresses are given the network addresses for the plurality of server nodes 105 at which the server processes 104 may be found. This information is distributed to the name servers 105 using a name server protocol such as the DNS protocol. Name server protocols are known in the art of networking, and so are not discussed in detail herein.
[0057] Duplicating the server process 104 and distributing multiple network addresses for the service to the name servers 105 has the following effects: When the name-request message 121 is transmitted at the step 161 from the client process 102 to the name server 105, the name server 105 obtains a plurality of network addresses for server processes 104 at a plurality of server nodes 105. When the order-request message 123 is transmitted at the step 163 from the client process 102 to the router 111, the router 111 orders the plurality of network addresses for server processes 104 at a plurality of server nodes 105 by their relative distance from the client node 103. When the client process 102 contacts a server process 104 using a network address from the order-response message 124, the server process 104 which is chosen is the one at the server node 105 with the smallest relative distance from the client node 103.
[0058] Thus, when the client process 102 initiates the method 150 to contact one of the server processes 104, it will automatically be assigned to the relatively nearest server process 104; when multiple client process 102 attempt to contact one of the server processes 104, they will automatically be distributed among the set of server processes 104 which may be chosen.
Synchronized Message Receipt
[0059] FIG. 2A shows a block diagram of a system for providing synchronized message receipt in a computer network. FIG. 2B shows a flow diagram of a method for providing synchronized message receipt in a computer network as shown in FIG. 2A.
[0060] A second example enhanced network service is synchronized distribution of messages to recipients, such as (1) assuring that a designated message is delivered to a recipient node on the internetwork 100 at a designated time, or (2) assuring that a designated message is delivered to multiple recipients at the same time.
[0061] In this example enhanced service, a message is labeled with a set of designated destination nodes and a designated time for delivery to those destination nodes. For example, the message may comprise one of the following:
[0062] a financial news report, such as a ticker-tape entry which is intended for delivery to customers fifteen minutes after its occurrence in real time; or
[0063] a wake-up call or other reminder, such as a greeting message which is intended for delivery at a time specified by the recipient.
[0064] In a preferred embodiment, each one of the routers 111 maintains an indicator of the current time, synchronized across all routers 111 so that any pair of routers 111 will have the same value for the “current time”, preferably within an error margin of less than about 0.5 milliseconds. This indicator may be recorded in the network tables 112 or in another register within each router 111. The routers 111 may maintain this indicator by means of a network time protocol, or by some other technique. Network time protocols, which are preferred, are known in the art of networking.
[0065] A method 250 is conducted in cooperation by the client process 102 and various routers 111 on the internetwork 100. At a flow point 260 for the method 250, the client process 102 desires to send a message 200 for receipt at a destination node 201 at a designated time.
[0066] At a step 261, the client process 102 contacts one of the routers 111 using a timed message 210. Since all messages on the internetwork 100, other than those limited to the local network 101, are transmitted using one or more routers 111, the client process 102 need only transmit the timed message 210 to the destination node 201 as if it were to transmit any other message to the destination node 201, and the timed message 210 will be received by one of the routers 111 along a path to the destination node 201. The timed message 210 comprises an ordinary message for delivery to, plus a header designating the desired time for receipt at, the destination node 201.
[0067] At a step 262, one of the routers 111 along a path to the destination node 201 receives the timed message 210 and parses it to determine the destination node 201, and determines if it would be one of the routers 111 to effect final delivery of the message to the destination node 201. If there is a single destination node 201, there will be only one such router 111; if there are multiple destination nodes 201, there may be more than one such router 111. If this router 111 would not effect final delivery, the method 250 continues with the step 263; if this router 111 would effect final delivery, the method 250 continues with the step 264.
[0068] At a step 263 (the router 111 would not effect final delivery), the router 111 forwards the timed message 210 to the next router 111 in the path to the destination node 201, just like any other message. In a preferred embodiment, if the desired time for receipt is very soon, the router 111 may reply to the client process 102 with an error message, indicating that delivery at the designated time is impossible, unlikely, or merely not guaranteed. In alternative embodiments, if the desired time for receipt is very soon, the router 111 may give priority to the timed message 210 over other messages.
[0069] At a step 264 (the router 111 would effect final delivery), the router 111 holds the timed message 210 until the designated time for delivery to the destination node 201, and at that time, delivers the message just like any other message. In a preferred embodiment, if the current time is past the desired time for receipt, the router 111 may reply to the client process 102 with an error message, indicating that delivery at the designated time did not occur, and may either discard the message or deliver it late. In alternative embodiments, if the desired time for receipt is very soon, the router 111 may give priority to the timed message 210 over other messages.
[0070] In a preferred embodiment, the capability to send a timed message 210 may be restricted to those client processes 102 with sufficient authorization. In such a case, the first router 111 to receive and parse a timed message 210 would require that the client process 102 is authenticated, to determine that the timed message 210 really comes from the client process 102 and not someone else, and that the client process 102 has sufficient permissions, i.e., that the router 111 has been informed that the client process 102 is authorized to send timed messages 210.
Enhanced Services Using Server Advertisements
[0071] FIG. 1A also shows a block diagram of a system for providing enhanced services using server advertisements, in a computer network. FIG. 1B also shows a flow diagram of a method for providing enhanced services using server advertisements, in a computer network as shown in FIG. 1A.
[0072] In a preferred embodiment, the method 150 is supplemented by using information “advertised” by the server processes 104. At a flow point 170 for the supplemented method 150, one of the server processes 104 desires to disseminate server advertising information to the subnet 110 of routers 111 for use with an enhanced network service.
[0073] The server advertising information comprises any information provided by one of the server processes 104 for dissemination to the subnet 110 of routers 111. For example, server advertising information may comprise the following:
[0074] relative load at the server node;
[0075] resources available at the server node, such as what services are available and to which classes of client process 102 those services are available, amount of free mass storage space or free processor time;
[0076] services available at the server node, to which classes of users those services are available, cost for performing those services, expected delay in performing those services, or other administrative policies which could affect the choice of server process 104 by a client process 102; or
[0077] which persons are logged in at the server node 105.
[0078] At a step 171, one of the server processes 104 sends a server-info message 131 to one of the routers 111.
[0079] The routing technique is supplemented by providing that each one of the routers 111 disseminates information from the server-info message 131 to all routers 111 in the subnet 110. Each router 111 which receives the server-info message 131 performs the steps 172, 173, and 174. As a result, each router 111 eventually receives the information to be disseminated in the server-info message 131 and stores that information in its network tables 112.
[0080] At a step 172, the router 111 receives the server-info message 131 and parses the server-info message 131 to determine the information to be disseminated.
[0081] At a step 173, the router 111 stores the information to be disseminated in its network tables 112.
[0082] At a step 174, the router 111 forwards the information to be disseminated to a set of neighboring routers 111 in the subnet 110.
[0083] In the supplemented method 150, the step 164 is supplemented to determine the order for the network addresses responsive to the server advertising information. Thus for example, at the step 164 the router 111 orders the network addresses responsive to relative load on the server node 105, or responsive to both relative distance to the server node 105 and relative load on the server node 105.
[0084] In other enhanced network services, the routers 111 may route messages to server processes 104 responsive to the server advertising information. For a first example, the server advertising information may comprise a list of persons who are currently logged in at the server node 105, and the routers 111 may receive and route a person-to-person message naming a designated person to the server node 105 at which that designated person is logged in. For a second example, the server advertising information may comprise a set of administrative policies regarding traffic the server node 105 desires not to retransmit, and the routers 111 may receive and route such messages away from such server nodes 105.
Enhanced Services Using Both Client and Server Advertisements
[0085] FIG. 3A shows a block diagram of a system for providing enhanced services using both client and server advertisements, in a computer network. FIG. 3B shows a flow diagram of a method for providing enhanced services using both client and server advertisements, in a computer network as shown in FIG. 3A.
[0086] A method 350 is conducted in cooperation by various client processes 102, client nodes 103, server processes 104, and server nodes 105 and coupled to the internetwork 100. At a flow point 360 for the method 350, the client process 102 desires to disseminate client advertising information to the subnet 110 of routers 111 for use with an enhanced network service.
[0087] The client advertising information comprises any information provided by one of the client processes 102 for dissemination to the subnet 110 of routers 111. For example, client advertising information may comprise the following:
[0088] relative urgency of requests from the client process 102; or
[0089] willingness to pay for services from the server node 105.
[0090] At a step 361, one of the client processes 102 sends a client-info message 301 to one of the routers 111, similar to the step 171.
[0091] The routing technique is supplemented by providing that each one of the routers 111 disseminates information from the client-info message 301 to all routers 111 in the subnet 110. Each router 111 which receives the client-info message 301 performs the steps 362, 363, and 364. As a result, each router 111 eventually receives the information to be disseminated in the client-info message 301 and stores that information in its network tables 112.
[0092] At a step 362, the router 111 receives the client-info message 301 and parses the client-info message 301 to determine the information to be disseminated, similar to the step 172.
[0093] At a step 363, the router 111 stores the information to be disseminated in its network tables 112, similar to the step 173.
[0094] At a step 364, the router 111 forwards the information to be disseminated to a set of neighboring routers 111 in the subnet 110, similar to the step 174.
[0095] At a flow point 370 for the method 350, the server process 102 desires to disseminate server advertising information to the subnet 110 of routers 111 for use with an enhanced network service.
[0096] The routing technique is also supplemented by providing that each one of the routers 111 disseminates information from the server-info message 131 to all routers 111 in the subnet 110, similar to the supplemented method 150. Each router 111 which receives the server-info message 131 performs the steps 372, 373, and 374. As a result, each router 111 eventually receives the information to be disseminated in the server-info message 131 and stores that information in its network tables 112.
[0097] At a step 372, the router 111 receives the server-info message 131 and parses the server-info message 131 to determine the information to be disseminated, similar to the step 172.
[0098] At a step 373, the router 111 stores the information to be disseminated in its network tables 112, similar to the step 173.
[0099] At a step 374, the router 111 forwards the information to be disseminated to a set of neighboring routers 111 in the subnet 110, similar to the step 174.
[0100] At a flow point 380, one of the routers 111 receives both client advertising information and server advertising information.
[0101] At a step 381, the router 111 matches the client advertising information against the server advertising information.
[0102] The nature of this step 381 depends on the nature of the client advertising information and the server advertising information. For example, if the client advertising information indicates the desire to obtain a named service X for a price Y or less, and the server advertising information indicates the ability to provide the named service X for a price Y or more, the router 111 obtains a match. Other situations in which the router 111 might obtain a match include the following:
[0103] the client process 102 has an indicated degree of urgency and the server process 104 has an indicated degree of expected delay to perform the named service;
[0104] the client process 102 has an indicated priority and the server process 104 has an indicated degree of free capacity to perform the named service;
[0105] the client process 102 has an indicated set of server requirements and the server process 104 has an indicated set of server capabilities to perform the named service;
[0106] the client process 102 has an indicated set of subtasks of the named service to be performed and the server process 104 has an indicated set of subtasks of the named service it is capable of performing; or
[0107] the client process 102 has an indicated set of products or services a first associated user desires to obtain and the server process 104 has an indicated set of products or services a second associated user desires to provide, such as for example airline tickets, computer equipment, office supplies, stocks or other securities, or other products or services.
[0108] At a step 382, the router 111 transmits a client-match message 302 to the client process 102, and a server-match message 303 to the server process 104, indicating the nature of the match.
[0109] At a step 383, the client process 102 and the server process 104 communicate about the matched information.
Authenticated Remote Procedure Call Transport
[0110] FIG. 4A shows formats for a set of packets for use with an authenticated remote procedure call transport (“ART”) protocol. FIG. 4B shows a flow diagram for an authenticated remote procedure call transport protocol.
[0111] The ART protocol described herein comprises four types of packets: (1) an ART-request packet, indicating a request for a service to be performed at the remote site, (2) an ART-reply packet, indicating a response to the ART-request packet, (3) an ART-auth-challenge packet, indicating a challenge to the recipient to show that the recipient is authorized to make the request, and (4) an ART-auth-response packet, indicating a response to the authorization challenge.
[0112] A single transaction comprises the sequence (1) ART-request, (2) ART-reply. If authentication is performed, a single transaction comprises the sequence (1) ART-request, (2) ART-auth-challenge, (3) ART-auth-response, (4) ART-reply.
[0113] All four types of packet comprise a fixed length packet header 400 and variable length packet data 410. The packet header 400 comprises a version number 401, a packet type value 402, a reply port value 403, and a transaction identifier 404.
[0114] The version number 401 comprises one octet (eight-bit byte) specifying the version of the remote procedure call protocol.
[0115] The packet type value 402 comprises one octet specifying the type of operation the packet is for. In a preferred embodiment, a request packet has the value 1; a reply packet has the value 2; an authentication challenge packet has the value 3; an authentication response packet has the value 4.
[0116] The reply port value 403 comprises two octets specifying a 16-bit value of the port at which the client process 102 expects to receive further ART protocol packets. The client sets this value with its first ART-request packet; thereafter the client and server copy this value to all packets for a single ART transaction.
[0117] The transaction identifier 404 comprises four octets specifying a 32-bit unsigned integer identifier for a single transaction. The client sets this value with its first ART-request packet for each transaction; thereafter the client and server copy this value to all packets for a single ART transaction. In a preferred embodiment, the client chooses a random nonzero value for its first ART transaction and increments this value by one for each subsequent ART transaction; zero is a valid value which may occur by overflow.
[0118] For the ART-request packet, the variable length packet data 410 comprises one or more requests. Each request comprises a mode/type field 411, a length value 412, and a data field 413.
[0119] The mode/type field 411 comprises two octets specifying a one-bit authentication bit and a 15-bit request type.
[0120] The length value 412 comprises two octets specifying a 16-bit count of the number of octets in the data field 413.
[0121] The data field 413 comprises the actual data for the request. Its interpretation may vary depending on the type of request.
[0122] For the ART-auth-challenge packet, the variable length packet data 410 comprises one or more challenges, one for each request in the ART-request packet requiring authorization. Each challenge comprises the mode/type field 411, the length value 412, and the data field 413, formatted like those for requests in the ART-request packet.
[0123] The server copies the mode/type field 411 from the mode/type field 411 for the ART-request packet.
[0124] The data field 413 comprises a randomly chosen challenge value.
[0125] For the ART-auth-response packet, the variable length packet data 410 comprises one response for each challenge in the ART-auth-challenge packet. Each response comprises the mode/type field 411, the length value 412, and the data field 413, formatted like those in the ART-request packet.
[0126] The client copies the mode/type field 411 from the mode/type field 411 for the ART-auth-challenge packet.
[0127] The data field 413 comprises the response value appropriate to the corresponding challenge value.
[0128] For the ART-reply packet, the variable length packet data 410 comprises one reply for each request in the ART-request packet. Each reply comprises the mode/type field 411, the length value 412, and the data field 413, formatted like those in the ART-request packet, and a result field 414.
[0129] The server copies the mode/type field 411 from the mode/type field 411 for the ART-request packet.
[0130] The result field 414 comprises two octets specifying a 16-bit value indicating the success or failure of the corresponding request. If the request is successful, the value will be zero. If the request is not successful, the value will be nonzero, and particular nonzero values may (at the server's option) indicate the type of failure.
[0131] The ART protocol 450 is conducted in cooperation by the client process 102 and the server process 104. At a flow point 460 for the method 450, the client process 102 desires to initiate one or more ART requests.
[0132] At a step 461, the client process 102 constructs an ART-request packet 470 for transmission to the server process 104, and transmits the ART-request packet 470 to the server process 104. The ART-request packet 470 comprises one or more requests, as described above. The client process 102 sets a timer to protect against the possibility that the packet will be lost. A preferred timer value is 30 seconds. If no reply is received, the client process 102 retries the request, up to five times. ART requests are therefore preferably idempotent.
[0133] At a step 462, the server process 104 receives the ART-request packet 470 and parses the ART-request packet 470 to determine each of the requests. If authentication is required for one or more of the requests, the protocol 450 continues with the step 463. If authentication is not required for any of the requests, the protocol 450 continues with the step 465. It is possible that authentication will be required for some but not all of the requests in a single ART-request packet 470.
[0134] At a step 463, the server process 104 constructs an ART-auth-challenge packet 471 for transmission to the client process 102, and transmits the ART-auth-challenge packet 471 to the client process 102. The server process 104 sets a timer to protect against the possibility that the packet will be lost. A preferred timer value is 30 seconds. If no response to the challenge is received, the server process 104 need not retry the challenge.
[0135] At a step 464, the client process 102 receives the ART-auth-challenge packet 471 from the server process 104, parses the ART-auth-challenge packet 471 to determine the challenge data, determines the appropriate authorization response, constructs an ART-auth-response packet 472 for transmission to the server process 104, and transmits the ART-auth-response packet 472 to the server process 104. The client process 104 sets a timer to protect against the possibility that the packet will be lost. A preferred timer value is 30 seconds. If no reply to the original request is received, the client process 104 retries the original request, up to file times.
[0136] A preferred embodiment uses the shared secret model of authentication, as described in RFC-1344, hereby incorporated by reference as if fully set forth herein. The server process 104 generates a random challenge value for each request requiring authentication; the client process 102 and server process 104 each compute a hash function applied to the concatenation of the challenge value and the shared secret. A preferred embodiment uses the MD5 hash function, as described in RFC-1321, hereby incorporated by reference as if fully set forth herein. The client process 102 transmits the computed value as the response value to the server process 104, which matches the response value against its own computed value. Authentication succeeds if the response value matches the server's own computed value.
[0137] Those skilled in the art will recognize, after perusal of this application, that other and further types of authentication may be used instead or in addition.
[0138] At a step 465, the server process 104 receives the ART-auth-response packet 472 from the client process 102, parses the ART-auth-response packet 472 to determine the response data, and determines whether the authorization challenge was passed by the response. If the client process 102 passed the authorization challenge, the server process 104 performs the request, and the protocol continues with the step 466. If the client process 102 failed to pass the authorization challenge, the server process 104 generates an failed-authorization error, and the protocol continues with the step 466.
[0139] At a step 466, the server process 104 constructs an ART-reply packet 473 for transmission to the client process 102, and transmits the ART-reply packet 473 to the client process 102.
[0140] At a step 467, the client process 102 receives the ART-reply packet 473 from the server process 104 and parses the ART-reply packet 473 to determine the reply for each request. The client process 102 matches the transaction identifier for the ART-reply packet 473 to a list of outstanding requests; if there is no match, the client process 102 discards the ART-reply packet 473.
ALTERNATIVE EMBODIMENTS
[0141] 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
We claim:
1. A method for providing enhanced services in a network, said method comprising the steps of
collecting network topological information and disseminating said network topological information to a subnet of communicating processors, whereby substantially all of said communicating processors have access to said network topological information;
receiving a request for service at a one of said communicating processors, other than a request to route a message on said network, from a processor not in said subnet; and
providing a response to said request for service from said one of said communicating processors, responsive to said network topological information.
2. A method as in claim 1, wherein said network topological information comprises information about paths and routes, including bandwidth, connectivity, delay, traffic reservations, and administrative policies applicable to those paths and routes.
3. A method as in claim 1, comprising the step of authenticating said request for service.
4. A method as in claim 1, comprising the steps of
transmitting an authentication challenge to said processor not in said subnet;
receiving an authentication response to said authentication challenge; and
determining whether to provide said service responsive to said authentication response.
5. A method as in claim 1, wherein
said request for service comprises a server name for translation into a network address; and
said step of providing a response comprises the step of selecting a network address responsive to said network topological information.
6. A method as in claim 1, wherein
said request for service comprises a server name for translation into a network address; and
said step of providing a response comprises the step of ordering a set of network addresses responsive to said network topological information.
7. A method as in claim 6, wherein said step of ordering is responsive to a relative distance in the network from said one of said communicating processors.
8. A method as in claim 1, wherein
said request for service comprises a message and a plurality of destination addresses; and
said step of providing a response comprises the step of delivering said message to said plurality of destination addresses substantially all at a common time for delivery.
9. A method as in claim 1, wherein
said request for service comprises a message, a plurality of destination addresses, and a desired common time for delivery; and
said step of providing a response comprises the step of delivering said message to said plurality of destination addresses substantially all at said common time for delivery.
10. A method for providing enhanced services in a network, said method comprising the steps of
receiving dynamic host information from at least one host processor coupled to said network;
disseminating said dynamic host information to a subnet of communicating processors, whereby substantially all of said communicating processors have access to said dynamic host information;
receiving a request for service at a one of said communicating processors, other than a request to route a message on said network, from a processor not in said subnet; and
utilizing network topological information in providing a response to said request for service from said one of said communicating processors, responsive to said dynamic host information.
11. A method as in claim 10, wherein said dynamic host information is responsive to a service available at said at least one host processor, a load on said at least one host processor, or an administrative policy in force at said at least one host processor.
12. A method as in claim 11, wherein
said request for service comprises a server name for translation to a network address; and
said step of providing a response comprises the step of selecting a set of network addresses responsive to said dynamic host information.
13. A method as in claim 11, wherein
said request for service comprises a server name for translation to a network address; and
said step of providing a response comprises the step of ordering a set of network addresses responsive to said dynamic host information.
14. A method as in claim 13, wherein said step of ordering is responsive to a load on said at least one host processor, or an administrative policy in force at said at least one host processor.
15. A method as in claim 10, wherein said dynamic host information is responsive to said processor not in said subnet.
16. A method for providing enhanced services in a network, said method comprising the steps of
utilizing network topological information to provide a service at a plurality of devices coupled to said network;
receiving a request for said service; and
routing said request to one of said plurality of devices, said one being selected in response to network topological information about said network, said network topological information being dynamically collected and disseminated among a plurality of processors in said network.
17. A method as in claim 16, wherein said plurality of processors comprise a subnet of communicating processors, whereby substantially all of said communicating processors have access to said information.
18. A method as in claim 16, wherein said information comprises dynamically-updated information about paths and routes, including bandwidth, connectivity, delay, traffic reservations, and administrative policies applicable to those paths and routes.
19. A method as in claim 16, comprising the step of authenticating said request for service.
20. A method as in claim 16, comprising the steps of
transmitting an authentication challenge to said processor not in said subnet;
receiving an authentication response to said authentication challenge; and
determining whether to provide said service responsive to said authentication response.
21. A method as in claim 16, wherein said one is selected responsive to a relative distance in the network from a communicating processor responding to said request.
22. A method for providing enhanced services in a computer network, said method comprising the steps of:
receiving a message from a source on said network, said message to be delivered via said computer network to a plurality of destinations on said network at a specified time T;
routing said message on said network for delivery so as to be received at said destination devices;
delaying delivery of the message to at least one destination device before said specified time T has occurred; and
delivering said message via said computer network to each of said destination devices at substantially said specified time T.
23. A method for providing enhanced services in a computer network, said method comprising the steps of:
receiving a first message from a source on said network, said message to be delivered via said computer network to a destination on said network upon an occurrence of an event;
routing said first message to said destination;
delaying delivery of the first message to the destination while the event has not occurred; and
delivering said first message via said computer network to said destination upon the occurrence of the event.
24. A method as in claim 23, wherein said event is a delivery of a second message on said network; and
wherein the delivery of the first and second messages occur substantially simultaneously.
25. A method as in claim 23, wherein said event is a delivery of said first message to a second destination on said network; and
wherein said delivery of said first message to said first and second destinations occurrs at substantially a same time.
26. A method as in claim 23, wherein said event is an occurrence of a clock time.
27. Apparatus for providing enhanced services in a network, said apparatus comprising
a subnet of communicating processors disposed for collecting and disseminating network topological information, whereby substantially all of said communicating processors have access to said network topological information;
means, available to at least one said communicating processor, for receiving a request for service, other than a request to route a message on said network, from a processor not in said subnet; and
means, available to at least one said communicating processor, for providing a response to said request for service, responsive to said network topological information.
28. Apparatus as in claim 27, wherein said network topological information comprises information about paths and routes, including bandwidth, connectivity, delay, traffic reservations, and administrative policies applicable to those paths and routes.
29. Apparatus as in claim 27, comprising means for authenticating said request for service.
30. Apparatus as in claim 27, comprising
means for transmitting an authentication challenge to said processor not in said subnet;
means for receiving an authentication response to said authentication challenge; and
means for determining whether to provide said service responsive to said authentication response.
31. Apparatus as in claim 27, wherein
said request for service comprises a server name for translation into a network address; and
said means for providing a response comprises means for selecting a network address responsive to said network topological information.
32. Apparatus as in claim 27, wherein
said request for service comprises a server name for translation into a network address; and
said means for providing a response comprises means for ordering a set of network addresses responsive to said network topological information.
33. Apparatus as in claim 32, wherein said means for ordering is responsive to a relative distance in the network from said one of said communicating processors.
34. Apparatus as in claim 27, wherein
said request for service comprises a message and a plurality of destination addresses; and
said means for providing a response comprises means for delivering said message to said plurality of destination addresses substantially all at a common time for delivery.
35. Apparatus as in claim 27, wherein
said request for service comprises a message, a plurality of destination addresses, and a desired common time for delivery; and
said means for providing a response comprises means for delivering said message to said plurality of destination addresses substantially all at said common time for delivery.
36. Apparatus for providing enhanced services in a network, said apparatus comprising
means for receiving dynamic host information from at least one host processor coupled to said network;
means for disseminating said dynamic host information to a subnet of communicating processors, whereby substantially all of said communicating processors have access to said dynamic host information;
means for receiving a request for service at a one of said communicating processors, other than a request to route a message on said network, from a processor not in said subnet; and
means for utilizing network topological information in providing a response to said request for service from said one of said communicating processors, responsive to said dynamic host information.
37. Apparatus as in claim 36, wherein said dynamic host information is responsive to a service available at said at least one host processor, a load on said at least one host processor, or an administrative policy in force at said at least one host processor.
38. Apparatus as in claim 37, wherein
said request for service comprises a server name for translation to a network address; and
said means for providing a response comprises means for selecting a set of network addresses responsive to said dynamic host information.
39. Apparatus as in claim 37, wherein
said request for service comprises a server name for translation to a network address; and
said means for providing a response comprises means for ordering a set of network addresses responsive to said dynamic host information.
40. Apparatus as in claim 39, wherein said means for ordering is responsive to a load on said at least one host processor, or an administrative policy in force at said at least one host processor.
41. Apparatus as in claim 36, wherein said dynamic host information is responsive to said processor not in said subnet.
42. Apparatus for providing enhanced services in a network, said apparatus comprising
means for utilizing network topological information to provide a service at a plurality of devices coupled to said network;
means for receiving a request for said service; and
means for routing said request to one of said plurality of devices, said one being selected in response to network topological information, said network topological information being dynamically collected and disseminated among a plurality of processors in said network.
43. Apparatus as in claim 42, wherein said plurality of processors comprise a subnet of communicating processors, whereby substantially all of said communicating processors have access to said information.
44. Apparatus as in claim 42, wherein said information comprises dynamically-updated information about paths and routes, including bandwidth, connectivity, delay, traffic reservations, and administrative policies applicable to those paths and routes.
45. Apparatus as in claim 42, comprising means for authenticating said request for service.
46. Apparatus as in claim 42, comprising
means for transmitting an authentication challenge to said processor not in said subnet;
means for receiving an authentication response to said authentication challenge; and
means for determining whether to provide said service responsive to said authentication response.
47. Apparatus as in claim 42, wherein said one is selected responsive to a relative distance in the network from a communicating processor responding to said request.
48. Apparatus for providing enhanced services in a computer network, said method comprising the steps of:
receiving a message from a source on said network, said message to be delivered via said computer network to a plurality of destinations on said network at a specified time T;
routing said message on said network for delivery so as to be received at said destination devices;
means for delaying delivery of the message to at least one destination device before said specified time T has occurred; and
delivering said message via said computer network to each of said destination devices at substantially and specified time T.
49. Apparatus for providing enhanced services in a computer network, said method comprising the steps of:
means for receiving a message from a source on said network, said message to be delivered via said computer network to a destination on said network upon an occurrence of an event;
means for routing said message to said destination;
means for delaying delivery of the first message to the destination while the event has not occurred; and
means for delivering said message via said computer network to said destination upon the occurrence of the event.
50. Apparatus as in claim 49, wherein said event is a delivery of a second message on said network; and
wherein the delivery of the first and second messages occur substantially simultaneously.
51. Apparatus as in claim 49, wherein said event is a delivery of said first message to a second destination on said network; and
wherein said delivery of said first message to said first and second destinations occurrs at substantially a same time.
52. Apparatus as in claim 49, wherein said event is an occurrence of a clock time.
53. Apparatus for providing enhanced services in a network, comprising
means for collecting network topological information from and disseminating network topological information to at least one router in said network, whereby said apparatus and said at least one router have access to said network topological information;
means for receiving a request for service, other than a request to route a message on said network, from a processor other than said at least one router; and
means for providing a response to said request for service, responsive to said network topological information.
54. Apparatus as in claim 53, wherein said network topological information comprises information about paths and routes, including bandwidth, connectivity, delay, traffic reservations, and administrative policies applicable to those paths and routes.
55. Apparatus as in claim 53, comprising means for authenticating said request for service.
56. Apparatus as in claim 53, comprising
means for transmitting an authentication challenge to said processor not in said subnet;
means for receiving an authentication response to said authentication challenge, and
means for determining whether to provide said service responsive to said authentication response.
57. Apparatus as in claim 53, wherein
said request for service comprises a server name for translation into a network address; and
said means for providing a response comprises means for selecting a network address responsive to said network topological information.
58. Apparatus as in claim 53, wherein
said request for service comprises a server name for translation into a network address; and
said means for providing a response comprises means for ordering a set of network addresses responsive to said network topological information.
59. Apparatus as in claim 58, wherein said means for ordering is responsive to a relative distance in the network from said apparatus or said at least one router.
60. Apparatus as in claim 53, wherein
said request for service comprises a message and a plurality of destination addresses; and
said means for providing a response comprises means for delivering said message to said plurality of destination addresses substantially all at a common time for delivery.
61. Apparatus as in claim 53, wherein
said request for service comprises a message, a plurality of destination addresses, and a desired common time for delivery; and
said means for providing a response comprises means for delivering said message to said plurality of destination addresses substantially all at said common time for delivery.
62. Apparatus for providing enhanced services in a network, said apparatus comprising
means for receiving dynamic host information from at least one host processor coupled to said network;
means for collecting network topological information from and disseminating said network topological information to at least one router in said network, whereby said apparatus and said at least one router have access to said network topological information;
means for receiving a request for service, other than a request to route a message on said network, from a processor other than said at least one router; and
means for providing a response to said request for service, responsive to said dynamic host information.
63. Apparatus as in claim 62, wherein said dynamic host information is responsive to a service available at said at least one host processor, a load on said at least one host processor, or an administrative policy in force at said at least one host processor.
64. Apparatus as in claim 63, wherein
said request for service comprises a server name for translation to a network address; and
said means for providing a response comprises means for selecting a set of network addresses responsive to said dynamic host information.
65. Apparatus as in claim 63, wherein
said request for service comprises a server name for translation to a network address; and
said means for providing a response comprises means for ordering a set of network addresses responsive to said dynamic host information.
66. Apparatus as in claim 65, wherein said means for ordering is responsive to a load on said at least one host processor, or an administrative policy in force at said at least one host processor.
67. Apparatus as in claim 62, wherein said dynamic host information is responsive to said processor other than said at least one router.
Patent Citations (188)
| 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 |
| 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 | Kasiraj et al. | Applicant |
| US4965767 | 1990-10-01 | Kinoshita et al. | Applicant |
| US4965772 | 1990-10-01 | Daniel et al. | Applicant |
| US4970678 | 1990-11-01 | Sladowski et al. | 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 | Sassai et al. | Applicant |
| 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 |
| 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 |
| 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 | Fleisher et al. | Applicant |
| US5268592 | 1993-12-01 | Bellamy et al. | Applicant |
| US5268900 | 1993-12-01 | Hluchj 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 |
| 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 | Corbalis et al. | 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 |
| US5473604 | 1995-12-01 | Hausman et al. | Applicant |
| US5473607 | 1995-12-01 | Hausman et al. | Applicant |
| US5477541 | 1995-12-01 | White et al. | Applicant |
| 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 |
| US5513314 | 1996-04-01 | Kandasamy et al. | Examiner |
| US5517494 | 1996-05-01 | Green | Applicant |
| US5519704 | 1996-05-01 | Farinacci 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 |
| US5555244 | 1996-09-01 | Gupta et al. | Applicant |
| US5561669 | 1996-10-01 | Lenney et al. | Applicant |
| US5583862 | 1996-12-01 | Callon | Applicant |
| US5592470 | 1997-01-01 | Rudrapatna et al. | Applicant |
| US5598532 | 1997-01-01 | Liron | Examiner |
| US5598581 | 1997-01-01 | Daines et al. | Applicant |
| US5600798 | 1997-02-01 | Cherukuri et al. | Applicant |
| US5602770 | 1997-02-01 | Ohira | Applicant |
| US5604868 | 1997-02-01 | Komine et al. | Examiner |
| 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. | Examiner |
| US5638359 | 1997-06-01 | Peltola et al. | Applicant |
| US5644718 | 1997-07-01 | Belove et al. | 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 |
| 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 | Satch | Applicant |
| US5748186 | 1998-05-01 | Raman | Applicant |
| US5748617 | 1998-05-01 | McLain, Jr. | Applicant |
| US5754547 | 1998-05-01 | Nakazawa | Applicant |
| US5835710 | 1998-11-01 | Nagami et al. | Applicant |
| US5838912 | 1998-11-01 | Poon et al. | Examiner |
| US5841874 | 1998-11-01 | Kempke et al. | Applicant |
| US5854903 | 1998-12-01 | Morrison et al. | Applicant |
| US5898686 | 1999-04-01 | Virgile | Applicant |
| US5937162 | 1999-08-01 | Funk et al. | Examiner |
| EP384758 | 1990-02-01 | Applicant | |
| EP431751A1 | 1990-11-01 | Applicant | |
| EP567217A2 | 1993-10-01 | Applicant | |
| WO93/07692 | 1993-04-01 | Applicant | |
| WO93/07569 | 1993-04-01 | Applicant | |
| WO94/01828 | 1994-01-01 | Applicant | |
| WO95/20850 | 1995-08-01 | Applicant |
Non-Patent Literature (12)
- Allen, M., “Novell IPX Over Various WAN Media (IPXWAN)”, Network Working Group, RFC 1551, Dec. 1993, pp. 1-22.Applicant
- Becker, D., 3c589.c: A 3c589 EtherLink3 ethernet driver for linux, [email protected], May 3, 1994, pp. 1-13.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
- Tusuchiya, P.F., “A Search Algorithm for Table Entries with NonContinguous Wildcarding”, Abstract, Bellcore.Applicant
- Esaki, et al., “Datagram Delivery in an ATM-Internet,” IEICE Transactions on Communications vol. E77-B, No. 3, (1994) Mar., Tokyo, Japan.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
- Zhang, et al., “Rate-Controlled Static-Priority Queueing,” INFOCOM 1993, pp. 227-236.Applicant