US20070110082A1 - Systems and Methods for Implementing Second-Link Routing in Packet Switched Networks - Google Patents
Systems and Methods for Implementing Second-Link Routing in Packet Switched Networks Download PDFInfo
- Publication number
- US20070110082A1 US20070110082A1 US11/530,811 US53081106A US2007110082A1 US 20070110082 A1 US20070110082 A1 US 20070110082A1 US 53081106 A US53081106 A US 53081106A US 2007110082 A1 US2007110082 A1 US 2007110082A1
- Authority
- US
- United States
- Prior art keywords
- gateway
- router
- packet
- switch
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
- H04L45/10—Routing in connection-oriented networks, e.g. X.25 or ATM
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
- This application is a Continuation of U.S. patent application Ser. No. 09/726,056, filed Nov. 30, 2000, entitled “Systems and Methods for Implementing Second-Link Routing in Packet Switched Networks,” Attorney Docket No. 74120-315065 (formerly 99-463C), by Robert J. Donaghey, incorporated herein by reference for all purposes.
- The present invention relates generally to packet switching systems and methods and, more particularly, to systems and methods for routing Internet Protocol (IP) traffic between local-area networks (LANs) connected via connection-oriented packet switches in mobile ad-hoc networks using virtual circuits.
- Connection-oriented protocols have conventionally been used for switching packets from a source node to a destination node in packet switching networks. Such protocols have found acceptance in the mobile arena with network hardware installed in trucks and other vehicles or hand-carried. Connections between switches in such environments are often short-lived as equipment is moved together or apart, and are of widely fluctuating throughput quality. The challenge of routing data packets in this environment is substantially greater than that of stationary systems. Connection-oriented designs for such systems have been favored because of the need to support telephony as well as machine-to-machine communications. However, IP has become the protocol of choice for end users of such systems, so the need to route IP packets across mobile, ad hoc switching networks has been met by adding IP routers on top of the connection-oriented switches, and developing protocols for establishing the optimal path from one router to another.
- The algorithms used by routers to convey connectivity in a mobile network have evolved to keep up with the constantly changing topology, and, as the IP addresses themselves will not convey any topological information when a router can move about freely, they typically use flooding techniques (sometimes called ‘Shortest Path First’ algorithms) to pass local connectivity information on to more distantly-connected routers. A router then uses this information when sending or forwarding packets to another router to decide which way to send the packet. Typically a router will determine which of its nearest neighbors is ‘closest’ to the destination, and then forwards the packet one hop to the chosen neighbor. To do so when the router is attached to a connection-oriented switch, as is the case here, the router must select a virtual circuit on which to place the packet. To facilitate this, it is the current practice for each switch to automatically set up a permanent one-hop circuit to each of its immediate neighbors, with the neighbor forwarding all packets arriving on this circuit to its connected IP router.
- When workstations on LANs are attached to a network switch, it is the current practice for whatever device is used to bridge between the LAN and the switch (technically a gateway) to employ the same technique of forwarding all packets addressed ‘off LAN’ to the same one-hop circuit to be forwarded to the IP-router, where the knowledge of the current network topology resides.
- The use of multi-hop circuits for faster IP packet transport has faced a number of substantial obstacles: Portable equipment lags the stationary world in terms of size and speed, and mobile switch equipment usually has sufficient memory only for small Virtual Circuit (VC) tables. Hence, circuits have to be used selectively. The paths between switches are in constant flux in a fast moving mobile environment (as, for example, in military or fire-fighting environments), so connections are constantly being broken and re-established. IP is not connection-oriented, so setting up connections as packets arrive for some new destination has proved infeasible since the standard protocols for negotiating a virtual circuit across multiple hops take substantially longer than TCP timeouts tolerate. Knowledge of breaks in connectivity is known first to the switches closest to the break, so packets forwarded by more distant routers will often arrive with the expectation of a (now-broken) path to the destination, and the receiving router must be able to acquire control of the packet, rather than have its connected switch forward the packet further down a no-longer-complete virtual circuit.
- For traffic between workstations on different LANs attached by gateways to different switches (in trucks, etc.), the problem is even more difficult since the gateway device bridging between the LAN and a router/switch has no knowledge of the network topology. Nevertheless, fast communications is a must between workstations in ad hoc networks, and there is a real need for better use of the capabilities of the underlying connection-oriented switching network for these communications.
- Therefore, there exists a need for a system and method that can implement multi-hop virtual circuit paths in a mobile, ad hoc, connection-oriented packet switching network to support fast and reliable connectivity of connected LANs.
- Systems and methods, consistent with the present invention, address this and other needs by assigning virtual circuit identifiers (VCIs) to LAN gateways and distributing the VCIs to other LAN gateways throughout a network. Distribution of these VCIs permits each receiving LAN gateway to implement virtual circuit paths with other LAN gateways in the network.
- In accordance with the purpose of the invention as embodied and broadly described herein, a method of distributing virtual circuit identifiers associated with gateways in a network includes receiving, at a first node, packets comprising a plurality of first virtual circuit identifiers associated with gateways in the network; determining if any of the gateways are connected to the first node; assigning second virtual circuit identifiers to the connected gateways; and initiating the transmission of a message to the connected gateways informing the connected gateways of the plurality of first virtual circuit identifiers.
- In another implementation consistent with the present invention, a method of forwarding packets received at a first gateway in a network includes receiving a message at the first gateway, the message comprising a plurality of virtual circuit identifiers associated with other gateways in the network; receiving packets for transmission from the first gateway to a destination address associated with a second gateway; and sending the received packets towards the second gateway using one of the received plurality of virtual circuit identifiers.
- The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate an embodiment of the invention and, together with the description, explain the invention. In the drawings,
-
FIG. 1 illustrates an exemplary network in which systems and methods, consistent with the present invention, may be implemented; -
FIG. 2 illustrates exemplary components of a Router/Switch consistent with the present invention; -
FIG. 3 illustrates exemplary components of a gateway consistent with the present invention; -
FIG. 4 is an exemplary Switch Virtual Circuit (VC) table for a switch-gateway interface 250 consistent with the present invention; - FIGS. 5 is an exemplary gateway VC table for the switch port consistent with the present invention;
-
FIG. 6 is an exemplary gateway forwarding table consistent with the present invention; -
FIG. 7 is an exemplary router-to-adjacent-router update packet consistent with the present invention; -
FIG. 8 is an exemplary router-to-router gateway-flood-update packet consistent with the present invention; -
FIG. 9 is an exemplary router-to-gateway update packet consistent with the present invention; -
FIG. 10 is a flowchart that illustrates exemplary router gateway-flood-update processing consistent with the present invention; -
FIG. 11 is a flowchart that illustrates exemplary gateway processing of packets from LAN consistent with the present invention; -
FIG. 12 is a flowchart that illustrates exemplary gateway processing of packets from switch consistent with the present invention; and -
FIG. 13 is a flowchart that illustrates exemplary switch processing of packets from gateway consistent with the present invention. - The following detailed description of the invention refers to the accompanying drawings. The same reference numbers in different drawings identify the same or similar elements. Also, the following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims.
- Systems and methods consistent with the present invention provide mechanisms that assign VCIs to LAN gateways and distribute the VCIs to other LAN gateways throughout a network. Distribution of these VCIs permits each receiving LAN gateway to implement virtual circuit paths with other LAN gateways in the network.
-
FIG. 1 illustrates anexemplary network 100 in which systems and methods, consistent with the present invention, may be implemented. Network 100 may include multiple routers, each router interconnected with another router by conventional links. For purposes of illustration,FIG. 1 shows router/switches R1 105, R2 110, R3 115, R4 120, R5 125 and R6 130 interconnected bylinks 155. One skilled in the art will recognize that a typical network may include fewer or greater numbers of routers than those shown inFIG. 1 . - Network 100 may further include gateways interconnected with one or more of the routers of the network. For purposes of illustration,
FIG. 1 showsgateways routers R1 105 andR6 130, respectively. Each gateway may further connect with a local-area network (LAN). For example,gateways LANs LANs -
FIG. 2 illustrates an exemplary router/switch R1 105 that may route packets in a manner consistent with the present invention. Router/switches 110-130 may be similarly configured. Router/switch R1 105 may include an IP-router processor 205, arouter memory 210, aswitch memory 215, aswitch processor 220, a switch-router interface 225, port interfaces 230, 235, 240 and 245, and switch-gateway interface 250. - IP-
router processor 205 may execute instructions for performing IP routing algorithms and can include a conventional processing device.Switch processor 220 may execute instructions for performing, among other functions, virtual circuit path switching and can include a conventional processing device.Router memory 210 may provide permanent, semi-permanent, or temporary working storage of data and instructions for use by IP-router processor 205.Switch memory 215 may provide permanent, semi-permanent, or temporary working storage of data and instructions for use byswitch processor 220.Router memory 210 and switchmemory 215 may include conventional data storage devices, such as, for example, Random Access Memory (RAM) or Dynamic RAM (DRAM). - Switch-
router interface 225 may include conventional mechanisms for interfacing IP-router processor 205 withswitch processor 220.Port 0interface 230,port 1interface 235,port 2interface 240 andport 3interface 245 may each include conventional mechanisms for interfacingrouter 105 withnetwork 100 vialinks 155. Switch-gateway interface 250 may include conventional mechanisms for interfacingrouter 105 with one or more gateways, such asgateway 135. -
FIG. 3 illustrates anexemplary gateway 135 that may receive and forward IP packets to and fromLAN 145 consistent with the present invention.Gateway 140 may be similarly configured.Gateway 135 may include aswitch interface 305, amemory 310, aLAN interface 315 and aprocessor 320. -
Switch interface 305 may include conventional mechanisms for interfacinggateway 135 with a packet-switch, such as router/switch 105.Memory 310 may provide permanent, semi-permanent, or temporary working storage of data and instructions for use byprocessor 320.Memory 310 may include conventional data storage devices, such as, for example, RAM or DRAM.LAN interface 315 may include conventional mechanisms for interfacinggateway 135 with a LAN, such asLAN 145.Processor 320 may execute instructions for forwarding packets to and from a connected switch or a connected LAN in a manner consistent with the present invention.Processor 320 may include a conventional processing device. -
FIG. 4 illustrates an exemplary switch Virtual Circuit (VC) table 400, consistent with the present invention, that may be stored inswitch memory 215 for the switch-gateway interface 250 of router/switch 105. Switch VC table 400 may includeVC entries 405 containing a switch output port (PNout) 410 and an outgoing virtual circuit identifier (VCIout) 415.Switch VC entries 405 may correspond to incoming VCIs contained in received packet headers. ASwitch VC entry 405 may include a switch output port (PNout) 410 through which to forward a packet, and it may also include an outgoing virtual circuit identifier (VCIout) 415 that is to be placed in an outgoing packet header in place of an incoming VCI (VCIin). -
FIG. 5 illustrates an exemplary gateway VC table 500, consistent with the present invention, that may be stored inmemory 310 of each gateway innetwork 100. VC table 500 may includeVC entries 505 containing adestination 510.VC destinations 510 may include the gateway processor and the LAN.VC entries 505 may exist for ‘Hello’ protocol messages, ‘Route’ protocol messages, and packets intended for the LAN. For example, entry one might be designated as the ‘Hello’ protocol entry number, entry two might be designated as the ‘Route’ protocol number, and three might be designated as the entry number for all packets intended for a workstation connected to a gateway LAN, such asLAN 145. -
FIG. 6 illustrates an exemplary gateway forwarding table 600, consistent with the present invention, that may be stored inmemory 210 of each router innetwork 100, such asrouter RI 105, and inmemory 310 of each gateway innetwork 100. Forwarding table 600 may includedestination gateway entries 605 and outgoing virtual circuit identifier entries (VCIout) 610.Destination gateway entries 605 may include entries indicating destination gateways innetwork 100 that the gateway storing forwarding table 600 may be able to reach. VCIout entries 610 may include outgoing virtual circuit identifiers that correspond to eachdestination gateway 605. VCIout entries 610 for different destination gateways may or may not be distinct, depending on the connected router's decision logic and its understanding of the network topology. -
FIG. 7 illustrates anexemplary packet 700, consistent with the present invention, that may be used by a router innetwork 100, such asrouter R1 105, to inform neighboring routers of gateways connected torouter RI 105.Packet 700 may include arouter number 705, asequence number 710,gateway state data 715, andgateway VCI data 720. -
Router number 705 may include a number that identifies the router sending the update packet.Sequence number 710 may provide an indication of the version ofpacket 700 sent from the router identified byrouter number 705. For example, older versions of a packet sent fromrouter 105 may have lower sequence numbers than newer versions of the tag update packet.Gateway state data 715 may include data indicating whether gateways connected torouter 105 are operational or non-operational.Gateway VCI data 720 may include data identifying the VCI(s) assigned byrouter 105 to gateways connected torouter 105.Gateway VCI data 720 may be used by another router in the network to fashion a virtual circuit whose last two links are into some port of the router's switch, and then out of the switch toward the gateway. To this end, the router may set the VC Table entry assigned for the gateway to have Pnout=SWITCH-GATEWAY INTERFACE 250 and VCIout=IP #, the entry number for all packets intended for a workstation connected to the gateway LAN. This allows the other router to form a virtual circuit terminating at this router's gateway for use in fast switching the other router's gateway's packets to this gateway. -
FIG. 8 illustrates anexemplary packet 800, consistent with the present invention, that may be used by a router innetwork 100, such asrouter R1 105, to inform other routers in the network of gateways innetwork 100.Packet 600 may include arouter number 805, asequence number 810,gateway identifiers 815, andgateway data 820. -
Router number 805 may include a number identifying the router sending the packet.Sequence number 810 may provide an indication of the version ofpacket 800 sent from the router identified byrouter number 805. For example, older versions of a packet sent fromrouter 105 may have lower sequence numbers than newer versions of the tag update packet.Gateway identifiers 815 may identify addresses associated with gateways innetwork 100.Gateway data 820 may indicate up/down state, characteristics, IP address ranges, or any other information that the routers find useful. -
FIG. 9 illustrates anexemplary packet 900, consistent with the present invention, that may be used by a router innetwork 100, such asrouter R1 105, to inform a connected gateway of VCIs assigned to other gateways innetwork 100, so that the gateway may keep its gateway forwarding table 600 consistent with the router's.Packet 900 may include asequence number 905,gateway identifiers 910, gateway VCIs 915 and add/drop flags 920. -
Sequence number 905 may provide an indication of the version ofpacket 900 sent from the router connected to a gateway.Gateway identifiers 910 may include addresses associated with gateways innetwork 100. For example, older versions of a packet sent fromrouter 105 may have lower sequence numbers than newer versions of the update packet. Gateway VCIs 915 may include VCIs for each connected gateway to use to reach gateways identified bygateway identifiers 910. Add/drop flag 920 may include status indicators that indicate whether gateways identified bygateway identifiers 910 should be added to or removed from gateway forwarding table 600. -
FIG. 10 is a flowchart that illustrates exemplary processing, consistent with the present invention, for updating the entries in VC table 400. As one skilled in the art will appreciate, the method exemplified byFIG. 10 can be implemented as a sequence of instructions and stored inswitch memory 215 of router/switches innetwork 100, such as router/switch 105. - To begin processing,
router 105 receivesupdate packets 700 and/or 800 from neighboring routers (e.g.,R2 110, R3 115) [step 1005]. From the received packets,router 105 determines if there are any new gateways in network 100 [step 1010]. If so,router 105 assigns and setsVC entry 405 in switch's gateway-node VC table 400 for each new gateway connected to network 100 [step 1015] and updates its gateway forwarding table 600. If there are no new gateways innetwork 100,router 105 determines if any previously existing gateways have been disconnected or are down [step 1020]. If not, processing proceeds to step 1030. If any previously existing gateways are down, or if their routers have been disconnected,router 105 adjusts theVC entry 405 in VC table 400 for each gateway down or disconnected, setting the routeroutput port entry 410 to “IP-router” and setting theVCI out 415 to IP # so that packets arriving from the gateway with this VCI are sent to the IP Router by its switch for processing [step 1025].Router 105 may then send apacket 900 to any connected gateway informing the connected gateway of changes to VCIs that the connected gateways may use to reach other gateways connected to other routers in network 100 [step 1030]. Each connected gateway, such asgateway 135, updates <Destination Gateway, VCIout>entries 610 in its gateway forwarding table 600 with theGateway 910 and gateway VCI 915 values received in packet 900 [step 1035] in order to keep its gateway forwarding table 600 in sync with that of its router. -
FIG. 11 is a flowchart that illustrates exemplary processing, consistent with the present invention, for forwarding packets received at a gateway innetwork 100, such asgateway 135, from a connected router/switch, such as router/switch 105. As one skilled in the art will appreciate, the method exemplified byFIG. 11 can be implemented as a sequence of instructions and stored inmemory 310 ofgateways 135. - To begin processing,
gateway 135 may receive a packet from router/switch 105 [step 1105].Gateway 135 may then read the incoming VCI (VCIIN) from the packet header [step 1110].Gateway 135 may determine if VCIIN is equal to the ‘Hello’ protocol entry number [step 1115]. If so,gateway 135 processes the received packet in the conventional fashion for ‘hello’ or ‘keep-alive’ protocols (which are used to determine the up/down state of an attached device)[step 1120]. If not,gateway 135 may determine if VCIIN is equal to the ‘route number’ [step 1125]. If so,gateway 135 processes the received router-to-gateway-update packet 900 and updates its gateway forwarding table 600 from data in packet 900 [step 1130]. If not,gateway 135 may determine if VCIIN is equal to the IP number [step 1135]. If so,gateway 135 removes the switch-packet header containing the VCIIN from the packet [step 1140] and forwards the packet to LAN 145 [step 1145]. If VCIIN is not equal to any of these numbers (typically 1,2, and 3 respectively), thengateway 135 may discard the packet as being of an unknown type [step 1150]. -
FIG. 12 is a flowchart that illustrates exemplary processing, consistent with the present invention, for forwarding packets received at a gateway innetwork 100, such asgateway 135, from a workstation connected to a LAN, such asLAN 145. As one skilled in the art will appreciate, the method exemplified byFIG. 12 can be implemented as a sequence of instructions and stored inmemory 310 ofgateway 135. - To begin processing,
gateway 135 may receive a packet sent from a workstation, such asworkstation 160 a, acrossLAN 145, the packet containing a destination IP address that resides outside of LAN 145 [step 1205].Gateway 135 may determine if the destination IP address is associated with a gateway in its gateway forwarding table 600 [step 1210]. If not,gateway 135 can insert the customary default IP # VCI [typically the number “1”] in the packet header [step 1225] so that the switch, on receiving the packet, will forward it to its router for customary processing. Ifgateway 135 determines that the destination IP address is associated with a gateway in its gateway forwarding table 600,gateway 135 can retrieve aVCI out 610, associated with the gateway, from the gateway VCI table 600 [step 1215].Gateway 135 may then insertVCI out 610 in the packet header [step 1220]. - At
step 1230,gateway 135 can forward the received packet to switch 105. -
FIG. 13 is a flowchart that illustrates exemplary processing, consistent with the present invention, for forwarding packets received at a switch innetwork 100, such asswitch 105, from a gateway, such asgateway 135, connected to its a switch-gateway interface 250. As one skilled in the art will appreciate, the method exemplified byFIG. 13 can be implemented as a sequence of instructions and stored inswitch memory 215 ofrouter RI 105. - To begin processing, router/
switch R1 105 may receive a packet from switch-gateway interface 250 [step 1305] and then may inspect the packet's incoming VCI (VCIin) in the packet header [step 1310].Router R1 105 may further determine an output port number (PNout) 410 fromVC entry 405, corresponding to VCIin, of switch-gateway interface 250 VC table 400 [step 1315].Router RI 105 may then determine an outgoing VCI (VCIout) 415 fromVC entry 405, corresponding to VCIin, of VC table 400 [step 1320].Router R1 105 can replace VCIin in the packet header with the determined VCIout 415 [step 1325].Router R1 105 may then forward the packet to PNout 410 (either an output port or IP-router 205 [step 1330]. - Systems and methods consistent with the present invention provide mechanisms that assign virtual circuit identifiers to LAN gateways and distribute the VCIs to other LAN gateways throughout a network. Distribution of these VCIs permits each receiving LAN gateway to implement virtual circuit paths with other LAN gateways in the network.
- The foregoing description of exemplary embodiments of the present invention provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. For example, while certain components of the invention have been described as implemented in hardware and others in software, other configurations may be possible. Also, while series of steps have been described with regard to
FIGS. 10-13 , the order of the steps may be altered in other implementations consistent with the present invention. No element, step, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly described as such. The scope of the invention is defined by the following claims and their equivalents.
Claims (1)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/530,811 US20070110082A1 (en) | 1999-11-30 | 2006-09-11 | Systems and Methods for Implementing Second-Link Routing in Packet Switched Networks |
US15/385,397 US20170104667A1 (en) | 1999-11-30 | 2016-12-20 | Systems and methods for implementing second-link routing in packet switched networks |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16791899P | 1999-11-30 | 1999-11-30 | |
US09/726,056 US7106747B2 (en) | 1999-11-30 | 2000-11-30 | Systems and methods for implementing second-link routing in packet switched networks |
US11/530,811 US20070110082A1 (en) | 1999-11-30 | 2006-09-11 | Systems and Methods for Implementing Second-Link Routing in Packet Switched Networks |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/726,056 Continuation US7106747B2 (en) | 1999-11-30 | 2000-11-30 | Systems and methods for implementing second-link routing in packet switched networks |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/385,397 Continuation US20170104667A1 (en) | 1999-11-30 | 2016-12-20 | Systems and methods for implementing second-link routing in packet switched networks |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070110082A1 true US20070110082A1 (en) | 2007-05-17 |
Family
ID=26863599
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/726,056 Expired - Lifetime US7106747B2 (en) | 1999-11-30 | 2000-11-30 | Systems and methods for implementing second-link routing in packet switched networks |
US11/530,811 Abandoned US20070110082A1 (en) | 1999-11-30 | 2006-09-11 | Systems and Methods for Implementing Second-Link Routing in Packet Switched Networks |
US15/385,397 Abandoned US20170104667A1 (en) | 1999-11-30 | 2016-12-20 | Systems and methods for implementing second-link routing in packet switched networks |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/726,056 Expired - Lifetime US7106747B2 (en) | 1999-11-30 | 2000-11-30 | Systems and methods for implementing second-link routing in packet switched networks |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/385,397 Abandoned US20170104667A1 (en) | 1999-11-30 | 2016-12-20 | Systems and methods for implementing second-link routing in packet switched networks |
Country Status (1)
Country | Link |
---|---|
US (3) | US7106747B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110996269A (en) * | 2019-12-24 | 2020-04-10 | 湖北凯乐科技股份有限公司 | Wireless ad hoc network QoS enhancement application method based on token ring |
Families Citing this family (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7535826B1 (en) * | 2000-12-11 | 2009-05-19 | Juniper Networks, Inc | Routing protocols for accommodating nodes with redundant routing facilities |
US8713185B2 (en) * | 2001-12-07 | 2014-04-29 | Rockstar Bidco, LP | Methods of establishing virtual circuits and of providing a virtual private network service through a shared network, and provider edge device for such network |
US7797444B2 (en) * | 2003-02-03 | 2010-09-14 | Nippon Telegraph And Telephone Corporation | Data transfer apparatus and data transfer system |
US7532640B2 (en) * | 2003-07-02 | 2009-05-12 | Caterpillar Inc. | Systems and methods for performing protocol conversions in a machine |
US7983820B2 (en) * | 2003-07-02 | 2011-07-19 | Caterpillar Inc. | Systems and methods for providing proxy control functions in a work machine |
US7646752B1 (en) * | 2003-12-31 | 2010-01-12 | Nortel Networks Limited | Multi-hop wireless backhaul network and method |
US7869436B1 (en) * | 2005-10-13 | 2011-01-11 | Cisco Technology, Inc. | Methods and apparatus for connecting to virtual networks using non supplicant authentication |
US20070115959A1 (en) * | 2005-10-13 | 2007-05-24 | Parker Jason M | Method and system for quiet time |
US20080043759A1 (en) * | 2006-08-17 | 2008-02-21 | Northrop Grumman Systems Corporation | System, Apparatus, Method and Computer Program Product for an Intercom System |
TW200820732A (en) * | 2006-10-27 | 2008-05-01 | Hon Hai Prec Ind Co Ltd | Gateway and signal intensity adjusting method thereof |
US9019967B2 (en) * | 2012-07-30 | 2015-04-28 | Dell Products L.P. | VLAN advertisement and automated configuration |
US9451381B2 (en) * | 2013-08-06 | 2016-09-20 | Time Warner Cable Enterprises Llc | Automated provisioning of managed services in a Wi-Fi capable client device |
US20200084109A1 (en) * | 2018-09-12 | 2020-03-12 | Nokia Solutions And Networks Oy | Sparse link-state flooding |
US11258221B2 (en) | 2019-07-12 | 2022-02-22 | Oliden Technology, Llc | Rotatable and wet-mateable connector |
Citations (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5463621A (en) * | 1993-05-27 | 1995-10-31 | Nec Corporation | Fast connection setup interfaces using pre-assigned virtual channel identifiers |
US5467349A (en) * | 1993-12-21 | 1995-11-14 | Trw Inc. | Address handler for an asynchronous transfer mode switch |
US5822309A (en) * | 1995-06-15 | 1998-10-13 | Lucent Technologies Inc. | Signaling and control architecture for an ad-hoc ATM LAN |
US5822304A (en) * | 1996-03-22 | 1998-10-13 | Hewlett-Packard Company | Scanning for active ATM virtual channel/virtual path identifiers |
US5933425A (en) * | 1995-12-04 | 1999-08-03 | Nec Corporation | Source routing for connection-oriented network with repeated call attempts for satisfying user-specified QOS parameters |
US6055561A (en) * | 1996-10-02 | 2000-04-25 | International Business Machines Corporation | Mapping of routing traffic to switching networks |
US6108708A (en) * | 1993-12-27 | 2000-08-22 | Nec Corporation | Connection-oriented network using distributed network resources and predetermined VPIs for fast VC establishment |
US6122282A (en) * | 1995-08-07 | 2000-09-19 | British Telecommunications | Route finding in communication networks |
US6147994A (en) * | 1996-05-28 | 2000-11-14 | Sprint Communications Company, L.P. | Telecommunications system with a connection processing system |
US6151365A (en) * | 1997-02-25 | 2000-11-21 | Sony Corporation | Information detecting apparatus and method |
US6178169B1 (en) * | 1996-03-28 | 2001-01-23 | British Telecommunications Public Limited Company | Method of transmitting an ATM cell over an ATM network |
US6188671B1 (en) * | 1997-07-03 | 2001-02-13 | At&T Corp | Traffic management for frame relay switched data service |
US6201962B1 (en) * | 1997-05-14 | 2001-03-13 | Telxon Corporation | Seamless roaming among multiple networks including seamless transitioning between multiple devices |
US6222845B1 (en) * | 1997-02-25 | 2001-04-24 | Cascade Communications Corp. | System and method for providing unitary virtual circuit in digital network having communication links of diverse service types |
US6275494B1 (en) * | 1997-05-19 | 2001-08-14 | Hitachi, Ltd. | Packet switching system, packet switching network and packet switching method |
US6301257B1 (en) * | 1997-03-19 | 2001-10-09 | Nortel Networks Limited | Method and apparatus for transmitting data frames between switches in a meshed data network |
US6304556B1 (en) * | 1998-08-24 | 2001-10-16 | Cornell Research Foundation, Inc. | Routing and mobility management protocols for ad-hoc networks |
US6347078B1 (en) * | 1997-09-02 | 2002-02-12 | Lucent Technologies Inc. | Multiple path routing |
US6505255B1 (en) * | 1999-04-29 | 2003-01-07 | Mitsubishi Electric Information Technology Center America, Inc. (Ita) | Method for formatting and routing data between an external network and an internal network |
US6563833B1 (en) * | 1999-01-05 | 2003-05-13 | Lucent Technologies Inc. | Combinatorial design method and apparatus for multi-ring networks with combined routing and flow control |
US6587467B1 (en) * | 1999-11-03 | 2003-07-01 | 3Com Corporation | Virtual channel multicast utilizing virtual path tunneling in asynchronous mode transfer networks |
US20030133406A1 (en) * | 1998-11-10 | 2003-07-17 | Ayman Fawaz | Method and apparatus to minimize congestion in a packet switched network |
US20030165117A1 (en) * | 1999-10-15 | 2003-09-04 | J. Joaquin Garcia-Luna-Aceves | System for communicating labeled routing trees to establish preferred paths and source routes with local identifiers in wireless computer networks |
US6633543B1 (en) * | 1998-08-27 | 2003-10-14 | Intel Corporation | Multicast flow control |
US6680946B1 (en) * | 1998-04-30 | 2004-01-20 | Nec Corporation | Layer 3 flow-switching method and system |
US6683865B1 (en) * | 1999-10-15 | 2004-01-27 | Nokia Wireless Routers, Inc. | System for routing and switching in computer networks |
US6791985B1 (en) * | 2000-07-12 | 2004-09-14 | Nortel Networks Limited | ATM transport over multi-protocol label switching |
-
2000
- 2000-11-30 US US09/726,056 patent/US7106747B2/en not_active Expired - Lifetime
-
2006
- 2006-09-11 US US11/530,811 patent/US20070110082A1/en not_active Abandoned
-
2016
- 2016-12-20 US US15/385,397 patent/US20170104667A1/en not_active Abandoned
Patent Citations (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5463621A (en) * | 1993-05-27 | 1995-10-31 | Nec Corporation | Fast connection setup interfaces using pre-assigned virtual channel identifiers |
US5467349A (en) * | 1993-12-21 | 1995-11-14 | Trw Inc. | Address handler for an asynchronous transfer mode switch |
US6108708A (en) * | 1993-12-27 | 2000-08-22 | Nec Corporation | Connection-oriented network using distributed network resources and predetermined VPIs for fast VC establishment |
US5822309A (en) * | 1995-06-15 | 1998-10-13 | Lucent Technologies Inc. | Signaling and control architecture for an ad-hoc ATM LAN |
US6122282A (en) * | 1995-08-07 | 2000-09-19 | British Telecommunications | Route finding in communication networks |
US5933425A (en) * | 1995-12-04 | 1999-08-03 | Nec Corporation | Source routing for connection-oriented network with repeated call attempts for satisfying user-specified QOS parameters |
US5822304A (en) * | 1996-03-22 | 1998-10-13 | Hewlett-Packard Company | Scanning for active ATM virtual channel/virtual path identifiers |
US6178169B1 (en) * | 1996-03-28 | 2001-01-23 | British Telecommunications Public Limited Company | Method of transmitting an ATM cell over an ATM network |
US6147994A (en) * | 1996-05-28 | 2000-11-14 | Sprint Communications Company, L.P. | Telecommunications system with a connection processing system |
US6055561A (en) * | 1996-10-02 | 2000-04-25 | International Business Machines Corporation | Mapping of routing traffic to switching networks |
US6069889A (en) * | 1996-10-02 | 2000-05-30 | International Business Machines Corporation | Aggregation of data flows on switched network paths |
US6222845B1 (en) * | 1997-02-25 | 2001-04-24 | Cascade Communications Corp. | System and method for providing unitary virtual circuit in digital network having communication links of diverse service types |
US6151365A (en) * | 1997-02-25 | 2000-11-21 | Sony Corporation | Information detecting apparatus and method |
US6301257B1 (en) * | 1997-03-19 | 2001-10-09 | Nortel Networks Limited | Method and apparatus for transmitting data frames between switches in a meshed data network |
US6201962B1 (en) * | 1997-05-14 | 2001-03-13 | Telxon Corporation | Seamless roaming among multiple networks including seamless transitioning between multiple devices |
US6275494B1 (en) * | 1997-05-19 | 2001-08-14 | Hitachi, Ltd. | Packet switching system, packet switching network and packet switching method |
US6188671B1 (en) * | 1997-07-03 | 2001-02-13 | At&T Corp | Traffic management for frame relay switched data service |
US6347078B1 (en) * | 1997-09-02 | 2002-02-12 | Lucent Technologies Inc. | Multiple path routing |
US6680946B1 (en) * | 1998-04-30 | 2004-01-20 | Nec Corporation | Layer 3 flow-switching method and system |
US6304556B1 (en) * | 1998-08-24 | 2001-10-16 | Cornell Research Foundation, Inc. | Routing and mobility management protocols for ad-hoc networks |
US6633543B1 (en) * | 1998-08-27 | 2003-10-14 | Intel Corporation | Multicast flow control |
US20030133406A1 (en) * | 1998-11-10 | 2003-07-17 | Ayman Fawaz | Method and apparatus to minimize congestion in a packet switched network |
US6563833B1 (en) * | 1999-01-05 | 2003-05-13 | Lucent Technologies Inc. | Combinatorial design method and apparatus for multi-ring networks with combined routing and flow control |
US6505255B1 (en) * | 1999-04-29 | 2003-01-07 | Mitsubishi Electric Information Technology Center America, Inc. (Ita) | Method for formatting and routing data between an external network and an internal network |
US20030165117A1 (en) * | 1999-10-15 | 2003-09-04 | J. Joaquin Garcia-Luna-Aceves | System for communicating labeled routing trees to establish preferred paths and source routes with local identifiers in wireless computer networks |
US6683865B1 (en) * | 1999-10-15 | 2004-01-27 | Nokia Wireless Routers, Inc. | System for routing and switching in computer networks |
US6587467B1 (en) * | 1999-11-03 | 2003-07-01 | 3Com Corporation | Virtual channel multicast utilizing virtual path tunneling in asynchronous mode transfer networks |
US6791985B1 (en) * | 2000-07-12 | 2004-09-14 | Nortel Networks Limited | ATM transport over multi-protocol label switching |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110996269A (en) * | 2019-12-24 | 2020-04-10 | 湖北凯乐科技股份有限公司 | Wireless ad hoc network QoS enhancement application method based on token ring |
Also Published As
Publication number | Publication date |
---|---|
US20170104667A1 (en) | 2017-04-13 |
US7106747B2 (en) | 2006-09-12 |
US20010030972A1 (en) | 2001-10-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20170104667A1 (en) | Systems and methods for implementing second-link routing in packet switched networks | |
US7586894B2 (en) | Communication system capable of selecting optimum gateway for terminals | |
US8599685B2 (en) | Snooping of on-path IP reservation protocols for layer 2 nodes | |
US7894456B2 (en) | Routing data packets from a multihomed host | |
US8416712B2 (en) | Method and device for installing and distributing routes | |
EP2372951B1 (en) | Network layer topology management for mobile ad-hoc networks and associated methods | |
US9276898B2 (en) | Method and device for link fault detecting and recovering based on ARP interaction | |
US8279881B2 (en) | Method and system for route updating | |
EP3841837B1 (en) | Multi-path access network | |
US20110013509A1 (en) | Network node and method for establishing network path and sending data | |
US20020009088A1 (en) | Systems and methods for negotiating virtual circuit paths in packet switched networks | |
US20010030969A1 (en) | Systems and methods for implementing global virtual circuits in packet-switched networks | |
US10999183B2 (en) | Link state routing protocol adjacency state machine | |
US6820120B1 (en) | Routing of data packets in heterogeneous networks | |
CA2496345C (en) | Efficient intra-domain routing in packet-switched networks | |
EP1964330B1 (en) | Method for reducing fault detection time in a telecommunication network | |
CN104412548A (en) | Method and device for keeping user device IP address fixed | |
Kaur et al. | Comparative study of OSPFv3, IS-IS and OSPFv3 IS-IS protocols using OPNET | |
US9742670B2 (en) | Non-eligible distance vector protocol paths as backup paths | |
Fujieda et al. | The design of OSPF extension for handling unidirectional-links | |
CN116827861A (en) | Message forwarding method and device | |
JP2001189750A (en) | Path controlling method, method for preparing path control table, path control table and router |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: LEVEL 3 COMMUNICATIONS, LLC,COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LEVEL 3 COMMUNICATIONS, INC.;REEL/FRAME:018989/0678 Effective date: 20070312 Owner name: LEVEL 3 COMMUNICATIONS, LLC, COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LEVEL 3 COMMUNICATIONS, INC.;REEL/FRAME:018989/0678 Effective date: 20070312 |
|
AS | Assignment |
Owner name: LEVEL 3 COMMUNICATIONS, LLC, COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VERIZON CORPORATE SERVICES GROUP INC.;REEL/FRAME:024804/0080 Effective date: 20100712 |
|
AS | Assignment |
Owner name: GENUITY INC., MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DONAGHEY, ROBERT;REEL/FRAME:027366/0372 Effective date: 20010118 Owner name: GTE SERVICE CORPORATION, TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DONAGHEY, ROBERT;REEL/FRAME:027366/0372 Effective date: 20010118 |
|
AS | Assignment |
Owner name: LEVEL 3 COMMUNICATIONS, LLC, COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GENUITY INC.;REEL/FRAME:027446/0268 Effective date: 20030204 |
|
AS | Assignment |
Owner name: LEVEL 3 COMMUNICATIONS, LLC, COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VERIZON CORPORATE SERVICES GROUP INC.;REEL/FRAME:027535/0308 Effective date: 20100712 Owner name: BBN TECHNOLOGIES CORP. (AS SUCCESSOR BY MERGER TO Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:BANK OF AMERICA, N.A. (SUCCESSOR BY MERGER TO FLEET NATIONAL BANK);REEL/FRAME:027535/0559 Effective date: 20091026 Owner name: BBNT SOLUTIONS LLC, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VERIZON CORPORATE SERVICES GROUP INC.;REEL/FRAME:027535/0281 Effective date: 20040421 Owner name: BBN TECHNOLOGIES CORP., MASSACHUSETTS Free format text: MERGER;ASSIGNOR:BBNT SOLUTIONS LLC;REEL/FRAME:027535/0298 Effective date: 20060103 Owner name: FLEET NATIONAL BANK, AS AGENT, MASSACHUSETTS Free format text: SECURITY AGREEMENT;ASSIGNOR:BBNT SOLUTIONS LLC;REEL/FRAME:027535/0460 Effective date: 20040326 Owner name: VERIZON CORPORATE SERVICES GROUP INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BBN TECHNOLOGIES CORP.;REEL/FRAME:027535/0304 Effective date: 20071011 |
|
AS | Assignment |
Owner name: MERRILL LYNCH CAPITAL CORPORATION, AS COLLATERAL A Free format text: SECURITY AGREEMENT;ASSIGNORS:LEVEL 3 COMMUNICATIONS, INC.;ICG COMMUNICATION, INC.;REEL/FRAME:027585/0842 Effective date: 20060627 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |