CN101485161B - Systems and methods for network routing in a multiple backbone network architecture - Google Patents
Systems and methods for network routing in a multiple backbone network architecture Download PDFInfo
- Publication number
- CN101485161B CN101485161B CN2007800251934A CN200780025193A CN101485161B CN 101485161 B CN101485161 B CN 101485161B CN 2007800251934 A CN2007800251934 A CN 2007800251934A CN 200780025193 A CN200780025193 A CN 200780025193A CN 101485161 B CN101485161 B CN 101485161B
- Authority
- CN
- China
- Prior art keywords
- network
- address
- backbone network
- backbone
- down hop
- 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.)
- Expired - Fee Related
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/24—Multipath
-
- 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/04—Interdomain routing, e.g. hierarchical routing
-
- 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/60—Router architectures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/15—Interconnection of switching modules
- H04L49/1515—Non-blocking multistage, e.g. Clos
- H04L49/1523—Parallel switch fabric planes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/15—Interconnection of switching modules
- H04L49/1553—Interconnection of ATM switching modules, e.g. ATM switching fabrics
- H04L49/1569—Clos switching fabrics
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Embodiments of a network architecture include a backbone node having a plurality of independent routers or switches connected in a matrix, wherein the matrix includes a plurality of stages of routers or switches, to form a node having a node switching capacity that is greater than the node switching capacity of the individual routers or switches A method includes assigning one of a plurality of backbone networks to a destination network address, associating a next hop loopback address with the destination network address, and advertising the destination network address in combination with the next hop loopback address through the selected backbone network address.
Description
The reference of related application
The application is that the sequence number of submitting on November 30th, 2006 is 11/565, the continuity of 563 U.S. Patent application, it is that the sequence number of submitting on February 3rd, 2006 is 11/347, the part continuity of 810 U.S. Patent application, its sequence number that requires that on February 4th, 2005 submitted to is the rights and interests of 60/650,312 U.S. Provisional Application.All these applications all are incorporated into this.
Technical field
The present invention relates generally to network path selection, more specifically, relate to for carrying out the system and method for network path selection in multiple backbone network (multiple backbone network) structure.
Background technology
The price continuous decrease of high speed internet, but the basic cost of maintenance and operational network is still relatively high.Keeping a higher principal element of unit cost is the expensive of terabit multi protocol label exchange (MPLS) backbone network router.Therefore, along with the growth of bandwidth requirement, cost also will probably increase.
Summary of the invention
The embodiment of network comprises the backbone network node, this backbone network node comprises a plurality of separate routers or the switch that connects into matrix, wherein, matrix comprises multistage router or switch, to form the node switching node capacious of node switching Capacity Ratio separate router or switch.Router or switch can connect into the CLOS matrix based on N * M Internet protocol (IP), wherein, and N＞1st, the progression in matrix, and M＞1st, the number of router or switch in every grade.Use IP or Ethernet routing protocol, can guide (direct) flow between router or switch.Use is selected from and comprises equivalent cost load balance, traffic engineering or based on one or more load balancing techniques in the group of the load balance of flow, can carry out load balance to business.Can provide (provision) multilink on router or switch in the mode of the flow equilibrium technology supporting to be carried out by node.
A plurality of embodiment of network comprise: a plurality of backbone networks, support communicating by letter between sources traffic website and purpose communication site; Source provider's edge device, itself and a plurality of backbone network and the source provider's network at sources traffic website place communicate; And purpose provider edge device, itself and a plurality of backbone network and the purpose provider's network at place, purpose communication site communicate, wherein, purpose provider's edge device is configured to select one of backbone networks from a plurality of backbone networks, to process the communication that is associated with destination address in purpose provider network.
In a plurality of embodiment, purpose provider's edge device is selected backbone network with outside minimum cost routing protocol.This purpose provider edge device can be associated down hop loopback address and/or backbone network identifier with destination address, wherein, and the selected backbone network of backbone network identifier sign.This purpose provider edge device also can be via the one or more transmission bulletins in a plurality of backbone networks, and wherein, this bulletin comprises destination address and down hop loopback address at least.This source provider's edge device can be configured to receive bulletin and destination address and down hop loopback address are write to route map, thereby the packet that sends to subsequently destination address from source network is routed to the down hop loopback address via selected backbone network.This purpose provider edge device can transmit bulletin during Open Shortest Path First (OSPF) protocol processes.This bulletin can also comprise the backbone network identifier.
This purpose provider edge device can be associated backbone network identifier and down hop loopback address with destination address in route map.This purpose provider network can comprise the first purpose provider network, and destination address can comprise the first destination address.This purpose provider edge device can also with the second purpose provider network service of the second destination address that is included in the second place, purpose communication site, wherein, purpose provider's edge device also is configured to select the second backbone network from a plurality of backbone networks with outside minimum cost routing protocol, to process the communication that is associated with the second destination address.This purpose provider edge device can also be configured to the second down hop loopback address is associated with the second destination address.This source provider's edge network can be configured to than the lower Route Selection absorption of costs of the Route Selection cost of distributing to the down hop loopback address that is associated with the first destination address to the second down hop loopback address, thereby the packet that is addressed to the second destination address is routed through the second backbone network.
The embodiment that is used for packet is routed to the method for the first purpose network address comprises the following steps: first of a plurality of backbone networks distributed to the first purpose network address; The first down hop loopback address is associated with the first purpose network address; And via the first backbone network address, the first purpose network address is announced together with the first down hop loopback address, thereby the packet that is addressed to the first purpose network address is routed through the first backbone network.The method can also comprise: first common identifier that will represent the first backbone network is associated with the first purpose network address.The method can also comprise the establishment route map, and this route map comprises related between related and the first purpose network address and the first common identifier between the first purpose network address and the first down hop loopback address.
Some embodiment of the method also comprise: second backbone network in a plurality of backbone networks distributed to the second purpose network address; The second down hop loopback address is associated with the second purpose network address; And via the second backbone network address, the second purpose network address is announced together with the second down hop loopback address, thereby the packet that is addressed to the second purpose network address is routed through the second backbone network.This first backbone network and the second backbone network can be different backbone networks.
According to a plurality of embodiment of method, use Interior Gateway Protocol, the packet that is addressed to the first purpose network address can be routed through the first backbone network to the first down hop loopback address.The method can also comprise is arranged to provider's edge site identifier with inner minimum cost routing metric.In addition, the method can comprise: the inside minimum cost routing metric that will be associated with the second down hop loopback address in the second backbone network is arranged to equal the value less than another the inner minimum cost tolerance that is associated with the first down hop loopback address in the second backbone network.The first purpose network address and the second purpose network address can be associated from the different routes via one or more customer edge network.
In a plurality of embodiment of system and method, the edge router that is associated with backbone network or core router can be supported two inner minimum cost routing protocols.This router can be processed by carry out the first inner minimum cost Route Selection at the port on the router of backbone network, and carries out another minimum cost Route Selection by the another port on the router of edge network and process.This first backbone network can be as the backup network of the second backbone network.
The embodiment of computer-readable medium comprises computer executable instructions, and this computer executable instructions is used for making computer to carry out the processing that packet is routed to the purpose terminal point.The embodiment of this processing comprises: for each in a plurality of ISPs (ISP) network, Internet service provider network allocation is given one of a plurality of backbone networks that operate in parallel backbone network structure; Reception is addressed to the packet of the destination that is associated with one of ISP network; The backbone network of the ISP network that is associated with the purpose terminal point is distributed in selection; And via selected backbone network route data packets.
According to some embodiment of computer-readable medium, select backbone network to comprise access minimum cost route map, be provided to the minimum cost Route Selection of the ISP network that is associated with the purpose terminal point to determine which backbone network.Select backbone network can also comprise the address of definite fringe node that is associated with selected backbone network.The embodiment of this processing can also comprise: the node from each ISP network receives bulletin; And from each bulletin of route a plurality of backbone networks of process determine the minimum cost backbone network.
In addition, the embodiment of this processing can also comprise the down hop loopback address that further is provided for each backbone network, makes the packet of going to the ISP network of distributing to backbone network be routed to the down hop loopback address so that the inside minimum cost Route Selection in each backbone network is processed.For each backbone network, this processing can also comprise the next hop address of association is embedded bulletin via the backbone network route.In addition, this processing can also relate to based on the route that is associated with the down hop loopback address cost metric is distributed to each down hop loopback address.Absorption of costs can be comprised to the down hop loopback address: cost metric is distributed to loopback address, and this cost metric ratio is used for via the cost metric of the every other down hop loopback address of the route of the backbone network that is associated with the down hop loopback address low.
According to an embodiment of network configuration, this network configuration comprises: a plurality of backbone networks, and wherein, each backbone network is configured to packet is routed to the purpose network via it from source network; And provider's edge device, be configured to select route data packets one of the backbone network of process, wherein, this provider's edge device selects to distribute to the minimum cost backbone network of purpose network, wherein, the minimum cost backbone network is selected from a plurality of backbone networks.This provider's edge device can also be configured to based on the minimum cost routing protocol, one of a plurality of backbone networks are assigned to the purpose network.
In addition, this provider's edge device can be configured to receive announcement message from the purpose network, and this announcement message route is passed through the backbone network that distributes, thereby other provider's edge devices will be gone to the packet route of purpose network and pass through the backbone network that distributes.This provider's edge device can also be configured to the down hop loopback address is embedded in announcement message.This provider's edge device can also be configured to cost metric is distributed to the down hop loopback address.Can based on the route that is associated with the down hop loopback address, with respect to other cost metrics that are associated with other down hop loopback address, select this cost metric.
In addition, this provider's edge device can be configured to receive the announcement message that is associated with another network, and the down hop loopback address that will be included in announcement message is distributed to the backbone network that receives this announcement message from it.This provider's edge device can be distributed to the down hop loopback address backbone network in route map.This feed end edge device can also be configured to set up the minimum cost routing table, and this minimum cost routing table is associated each in a plurality of down hop loopback address with cost metric based on the backbone network that is associated with the down hop loopback address.
In some embodiment of the network configuration that comprises a plurality of backbone networks, at least one in backbone network can be as at least one the backup network in other backbone networks.At least one in backbone network can comprise the backbone network node, and this backbone network node comprises the CLOS matrix that the N of Ethernet switch * M IP realizes, wherein, and N＞1st, the progression in matrix, and M＞1st, the number of router or switch in every grade.
For via each in many communicating routes of one or more provider's networks, be used for providing the embodiment of the method for communication to comprise between provider's network: receive the bulletin with the network address that is associated with communicating route; Use outside minimum cost routing protocol, select backbone network from a plurality of backbone networks; The first down hop loopback address is associated with destination address, and wherein, this first down hop loopback address can arrive via selected backbone network; With the first absorption of costs to the down hop loopback address, wherein, the first cost less than with the second cost that is associated by accessibility the second down hop loopback address of another backbone network; Via a plurality of backbone networks announcement the first down hop loopback address, wherein, announce and comprise that indication is via the first cost of selected backbone network access the first down hop loopback address.
Another embodiment of the method comprises: use outside minimum cost routing protocol, the backbone network that is selected from a plurality of backbone networks is distributed in the purpose network address; The down hop loopback address is associated with the purpose network address, wherein, this down hop loopback address corresponding to purpose provider's edge device that selected backbone network is communicated by letter on port; Notification source provider's edge device down hop loopback address can utilize the minimum cost Route Selection to arrive via selected backbone network.Notification source provider's edge device can comprise: carry out inner minimum cost routing protocol between the source core router equipment in source provider's edge device and selected backbone network.The method can also be included in carries out inner minimum cost routing protocol processing between source core router equipment and purpose core router equipment, with the cost of determining to be associated with next road loopback address.
Description of drawings
Fig. 1 is the schematic diagram of framework more than three grades according to an embodiment of the invention (multichassis) ethernet router (MER).
Fig. 2 be according to another embodiment of the present invention be connected to equity and a plurality of parallel backbone network of the edge network (schematic diagram of N * BB).
Fig. 3 is the many frameworks ethernet router shown according to another embodiment of the present invention Fig. 1 and the schematic diagram of the combination of a plurality of parallel backbone networks shown in the Fig. 2 that is connected between website.
Fig. 4 is the parallel schematic diagrames based on the core net of many frameworks ethernet router of one or more multi protocol labels exchange (MPLS) core networks according to another embodiment of the present invention and that packet Route Selection between website is provided, wherein, the second user/provider's edge network is recommended or moved to the subset of user/provider's data packet flow again.
Fig. 5 is according to an embodiment of the invention and provides the MPLS backbone network of packet Route Selection the parallel schematic diagram based on the backbone network of MER between unique user/provider's edge network and reciprocity edge network.
Fig. 6 is the schematic diagram that can be connected to communicatedly a plurality of core local area network (LAN)s (LAN) between one or more core routers and one or more edge router according to another embodiment of the present invention.
Fig. 7 is the schematic diagram at the optional LAN of centre (LIM).
Fig. 8 shows the exemplary network structure that comprises a plurality of parallel backbone networks, and wherein, station address is advertised and is associated with the down hop loopback address, thereby each the packet of going in those addresses is routed through selected backbone network.
Fig. 9 shows the exemplary network structure shown in Fig. 8, wherein, bulletin has been labeled the backbone network identifier, with indication based on the Backbone network of destination by, and cost is assigned to the down hop loopback address, to strengthen packet via the Route Selection of the backbone network that is associated.
Figure 10 shows dual inside and processes based on the linking status generation of cost, wherein, two inside of the edge router operation wide area network on the backbone network edge in multiple parallel backbone network (multiple parallel backbone network) structure towards side and local wire side to side produce based on the Link State of cost and process.
Figure 11 is the flow chart that illustrates according to the algorithm of carrying out Route Selection in multiple backbone network structure of an embodiment.
Figure 12 shows the universal computing device that can realize embodiments of the invention.
Embodiment
Embodiment comprises and is provided for a plurality of backbone networks with the system and method for the communication between network enabled.The first routing protocol is used by provider's edge device, to select backbone network from a plurality of backbone networks for the treatment of the communication that is associated with one or more network addresss that are associated.This provider's edge network equipment will have the port assignment of down hop loopback address to the one or more network addresss that are associated.The secondary route selection protocol is used for notifying the selected backbone network of other provider's edge network equipment should be used for transporting the packet that (carry) is addressed to the one or more network addresss that are associated.
The representative network of using the service of backbone network is that ISP (ISP) or Internet Service Provider (NSP) network of end user's network service are provided to family and commercial Internet user.ISP has the network in a plurality of geographic sites usually, and wherein, backbone network also has provider's edge network equipment to be connected with the ISP network.More specifically, embodiment is provided for distributing one of a plurality of backbone networks to process the communication that is associated with the ISP network address.Process can be used in such as the outside minimum cost routing protocol of Border Gateway Protocol (BGP) backbone network is distributed to the ISP network address.Inner minimum cost routing protocol is processed and be can be used in the packet of guaranteeing to be addressed to the ISP network address and be routed backbone network through distributing.
According to an embodiment, provider's fringe node is carried out the minimum cost backbone network of outside minimum cost routing protocol to select to be associated with the given ISP network address.This provider's fringe node is distributed to the given ISP network address with the down hop loopback address.This down hop loopback address can arrive via selected backbone network.The down hop loopback address is advertised via one or more backbone networks together with the given ISP network address.Carry out inner minimum cost routing protocol and process, but to notify this down hop loopback address minimum cost of one or more other provider's edge devices to arrive via selected backbone network.In certain embodiments, together with the down hop loopback address that is associated, the backbone network identifier is associated with the given ISP network address.One or more provider's fringe nodes can upgrade or create route map, to comprise the association between the given ISP network address, backbone network identifier and down hop loopback address.
According to each embodiment, can align by the outside minimum cost routing protocol of a plurality of ISP network address execution to backbone network service provider network notifications and process.Because have a plurality of backbone networks in backbone network service provider network, can be to the backbone network different from the backbone network of distributing to one or more other ISP network address of the one or more distribution in the ISP network address.One or more ISP network address can be associated with single ISP network or a plurality of ISP network.Similarly, can be to the different backbone network of different I SP network address distribution in an ISP network.
In each embodiment, be routed to specific down hop loopback address for guaranteeing packet via the backbone network that distributes, the down hop loopback address is labeled the identifier that is useful on the backbone network that distributes.Bulletin can comprise label and/or the down hop loopback address that is associated with the backbone network that distributes, so that sign is via the route of the backbone network that distributes, to process the communication that is used for associated network address.
According to some embodiment, backbone network select to be processed and the existence of a plurality of backbone networks is sightless for ISP network and the terminal point that is associated with the ISP network address.Similarly, utilize the backbone network service of a plurality of backbone networks to need not to show to such an extent that have any different from the backbone network that utilizes single backbone network.Although in a plurality of embodiment, specific backbone network is assigned to each ISP network address, in certain embodiments, the backup network of the backbone network that one or more other backbone networks can be used as distributing.
Typically, the backbone network service provider has a backbone network at first.This backbone network service provider can increase one or more backbone networks to backbone network service provider network.When having increased one or more backbone network, the ISP network address and route can shift (migrate) to one or more new backbone networks from initial backbone network.Transfer relates to redistributes one or more ISP network address to new backbone network.Can carry out and redistribute processing, so that provider's edge device routes to the purpose ISP network address with packet via the backbone network of distributing to the purpose ISP network address.The embodiment that redistributes processing comprises that the core node on new backbone network is carried out about the inside minimum cost routing protocol of provider's fringe node to be processed and processes about another inner minimum cost routing protocol of the core node that spreads all over new backbone network.By the down hop loopback address that the announcement of new backbone network and new backbone network and the related transfer ISP network address are associated, this new backbone network has the cost metric lower than the corresponding cost metric of initial backbone network.
Some embodiment relate to network configuration, and it comprises having the separate router that connects into matrix structure or the backbone network node of switch, thereby produces the node switching capacity larger than the node switching capacity of independent router.Router or switch can be connected to the CLOS matrix that N * M Internet protocol (IP) realizes, wherein, and N＞1st, the progression in matrix, and M＞1st, the number of router or switch in every grade.Use this network configuration and matrix, Application standard IP or Ethernet routing protocol and load balancing techniques direct traffic between router or switch, load balancing techniques can include but not limited to equivalent cost load balance, traffic engineering or based on the load balance of flow.Provide link in the mode with the best interoperability of the flow equilibrium of node on router.
Definition
" module " is the autonomous type function element.Module can hardware, the form of software, firmware or its combination in any realizes.
Term " connection " or " coupling " and relational language are used on function definition, and are not necessarily limited to directly connect or coupling.
Phrase " in one embodiment ", " according to an embodiment " etc. mean that usually special characteristic, structure or characteristic after phrase comprise at least one embodiment of the present invention, and can be included in more than one embodiment of the present invention.Importantly, this phrase might not refer to same embodiment.
If specification has been explained element or feature " can ", " can ", " meeting " or " perhaps " comprises or have characteristic, this particular element or feature do not need to be included or to have this characteristic so.
Term " response " and " in response to " comprise wholly or in part response.
Term " computer-readable medium " is can be by the medium of computer access, and can include but not limited to computer-readable storage medium and communication media.Computer-readable storage medium is often referred to the computer-readable memory of any type, such as but be not limited to volatibility, non-volatile, removable or irremovable storage device.Communication media refers to the signaling bearer mechanized data after modulation, such as but be not limited to program module, instruction or data structure.
The network that term " backbone network " or " backbone network " refer to connect communicatedly two or more networks or subnet and the communication flows Route Selection is provided between it.Backbone network usually by geographical distribution to provide Route Selection between a plurality of geographical position.Therefore, in some cases, backbone network is wide area network (WAN).Backbone network comprises core router and is conducive to other nodes of packet Route Selection.
" user network " or " provider's network " is the example of third party's network, its can with provider's edge network or equipment connection (interface), thereby communicate by one or more backbone networks.
" customer edge " or " provider's edge device " be with such as third party's network of user network with are connected the equipment that backbone network is connected, with routing traffic between third party's network and one or more backbone network.Usually, customer edge is connected with one or more core nodes (such as core router) in backbone network, with the routing to communicate flow to backbone network and from backbone network routing to communicate flow.
" customer edge network ", " provider's edge network " or " reciprocity edge network " are the networks that can communicate by letter between third party's network and one or more backbone networks, and comprise one or more customer edge.In certain embodiments, local area network (LAN) (LAN) can be communicatedly between backbone network core node and customer edge network node.
Developed multiple systems and processed so that the backbone network Route Selection to be provided between network.These systems can be independently or use together to form and save cost, extendible core backbone network and edge network.This system comprises many frameworks ethernet router (" MER "), multiple parallel backbone network structure (" N * BB ") and is positioned at middle LAN (" LIM ") structure.
Many frameworks ethernet router (MER)
A kind of is to use the matrix of network or Ethernet switch with the more low-cost method of expanding backbone network largelyr, to carry out the current function of being carried out by the router of costliness.Can use these Ethernet switch matrixes to replace terabit multi protocol label exchange (MPLS) backbone network router, and replace the gigabit access router at network backbone network edge place.By using the Ethernet switch matrix, can reduce unit cost.
Although cost is focus, when the new system of Design and implementation, extensibility (ability that namely increases along with bandwidth demand) is also focus.In fact, some prognosticators estimate to have obvious demand growth.Therefore, in some cases, may expect the ability with rational cost extended network.
In one embodiment, MER will comprise multistage CLOS matrix (for example, the 3 grades) router that is based upon outside Ethernet switch.MER will use the IP agreement with dispense flow rate load on a plurality of switch-level.This design utilization (leverage) prior art, but by increase additional Ethernet switch, extra level, both combination or new, cheap MER realizes extensibility
Fig. 1 is the schematic diagram of the embodiment of 3 grades of MER 100 according to an embodiment of the invention.In this specific embodiment, 4 Ethernet switches 102 in every one-level of three grades of 104a-104c of MER use.In addition, can increase extra switch 102 or level.In this instantiation, as by as shown in the arrow in Fig. 1, arrive L11 from L34 flow out.Use one or more load balances or distribution method, L11 dispense flow rate equally on L21-L24.L21-L24 is forwarded to L34 with business, and its mix flow also transfers necessary link with them.This design has realized the remarkable increase on the scale.For example, in the embodiment shown, 4 * MER 100 has realized 4 times of increases of node size.The maximum increase of 3 level structures is (n^2)/2, and wherein, n is the number of the switch of use in every grade.Pyatyi and seven grades of matrixes will further increase extensibility.
This many frameworks ether router one 00 can be regarded as packet level CLOS matrix.Use although known CLOS matrix is used for bit-level, realize in the network of the Ethernet switch that the CLOS matrix does not operate on the packet level, it is that this specific implementation provides.In addition, use proprietary software to realize the CLOS matrix of usually realizing in extremely expensive MPLS router, and the CLOS matrix is enclosed in single logical block (box).In this specific implementation, the Ethernet switch of a plurality of cheapnesss forms matrix, and uses the IP agreement to realize that CLOS distributes, rather than uses proprietary software.In addition, in this specific implementation, the CLOS matrix is in each jumping rather than individual equipment place's realization of switch.Other agreements can be used for other embodiment.
After Ethernet switch 102 is joined together, use the load balance based on stream, packet and packet unit can be assigned to not at the same level 104 of matrix.Interior Gateway Protocol (" IGP ") can be used in and realizes load balancing techniques.In certain embodiments, MER100 can use the equivalent cost load balance, makes each the three grades of logical block (that is, L31, L32, L33 and L34) that are associated with the destination receive the flow of equal number.For example, if logical block L1, L2 and L3 all with provider's edge site or router communication based on New York, each logical block will receive the flow of equal number.When realizing new MER, this technology relatively easily realizes better and expands.
In another embodiment, can utilized bandwidth perception (aware) load balancing techniques distribute the flow on MER 100, such as Packet Generation being given the Technology of Traffic Engineering (for example, MPLS traffic engineering) of least busy switch.In one embodiment, intermediate layer 104b can operating flux engineering function, determines thereby make intelligent Route Selection.
In another embodiment, flow perception (awareness) technology in intermediate layer 104b (that is, L21, L22, L23 and L24) can be used for determining it may be what that downstream traffic requires.That is to say, this intermediate layer 104b can determine to be positioned at the 3rd or the demand of final layer 104c, then determines Route Selection based on capacity requirement.In this embodiment, via traffic engineering tunnel (for example, MPLS tunnel) or via the 2nd layer of VLANS, this intermediate layer 104b can receive order or capacity information from last (for example, the 3rd) layer 104c.Alternatively, can be utilized bandwidth information to be sent to intermediate layer 104b to the change of IGP.For example, switch L31 can be connected to the intermediate layer 104b (for example, via IGP or other agreements) based on the website in New York with 30Gb flow and communicate.This intermediate layer 104b can use this protocol information and from the information of other switches, so that MER 100 load balances.
In another embodiment, the realization of MER 100 can use control logic unit or route reflector with management MER 100.In certain embodiments, this Router Reflector or control logic unit can participate in or control routing protocol, keep the Route Selection statistics, utilize MER to solve bursting problem, expansion (scale) routing protocol etc.In one embodiment, this Router Reflector can be realized routing protocol.Therefore, replace with MER that the third level in another MER is communicated by letter in the third level, the Router Reflector that the Router Reflector that is associated with MER can be associated with other MER is communicated by letter, to determine Route Selection needs and agreement.This Router Reflector can use Border Gateway Protocol (" BGP ") or can use IGP route reflection protocols (for example, the route reflector can be used as Area Border Router).
A plurality of parallel backbone networks (N * BB)
Another execution mode that can be used for the extended core backbone network is to create a plurality of parallel backbone networks.Fig. 2 shows an embodiment of multiple parallel backbone network structure 200.Utilize N * BB structure 200, can cut apart flow with the increase scale on a plurality of backbone networks.More specifically, each backbone network all can optionally be assigned to one or more network addresss, so that the backbone network that distributes is processed the communication flows (for example, packet) that is associated with one or more network addresss of distributing.
In the embodiment shown in Fig. 2, this multiple parallel backbone network structure 200 has configured a series of parallel backbone network 202a-202e between core site therein.This backbone network can use large-scale MPLS router, Ethernet switch, above-mentioned MER or any other suitable Route Selection technology.In addition, in the embodiment shown, peer-to-peer 204a-204n can be connected to backbone network 202 by public reciprocity foundation structure or the edge 206 that is connected to each backbone network, and user 208a-208n can be connected to specific backbone network edge 210a-210e.That is to say, peer-to-peer (peer) 204 is connected to parallel backbone network 202 (BB, BB1, BB2, BB3 and BB4) by single reciprocity edge 206, and user 208 is connected to backbone network 202 by the edge network 210 that separates.In Fig. 2, each backbone network 202 has the customer edge network 210 of himself.Yet, in optional embodiment, can only use one or a pair of edge network 210 (being similar to a reciprocity edge) just.This edge network 210 can also use different Route Selection technology, comprises above-mentioned MER.The use of MER can help the expansion at reciprocity edge 206.
Arrow in Fig. 2 shows the example of the Business Stream 212 in parallel backbone network structure 200.In this example, the flow 214 of going to user A-Z 208a-208n arrives from peer-to-peer #2204b.Based on the final destination of flow, cut apart flow (for example, reciprocity edge 206 can based on IP purpose prefix assignment flow) at the equipment on reciprocity edge network 206 (for example, provider's edge device) on a plurality of backbone networks 202.Then, each backbone network 202 forwards the traffic to end user 208 destinations via its related customer edge 210.
This multiple parallel backbone network 200 can have many advantages.For example, parallel backbone network 202 makes in each backbone network switching requirement less, so can use Ethernet switch and/or MER.In addition, this parallel backbone network structure 200 can utilize existing route to select and control protocol, such as the BGP instrument of similar traffic engineering, associating (confederation), MBGP etc.The use traffic engineering agreement can help flow is caused suitable (a plurality of) backbone network 202.In addition, utilize the existence of a plurality of backbone networks 202, can create the redundancy with failover capabilities system and be used for mission critical applications.That is, one or more backbone networks 202 can be used for disaster recovery and/or backup purpose.
In addition, in other other embodiment, this parallel backbone network 202 can be organized based on different factors and use.For example, peer-to-peer 204 can have the one or more backbone networks 202 that are exclusively used in it.Similarly, user network 208 (for example, ISP network) can have the one or more backbone networks 202 that are exclusively used in it.In other other embodiment, can and/or serve distributing user 208 on backbone network 202 based on flow.For example, ip voice (VoIP) can use one or more backbone networks 202, and other IP service simultaneously can be used other backbone networks 202.Therefore, backbone network 202 can be provided by peer-to-peer 204, user 208, service, volume of business or any other suitable regulation parameter.
In addition, as shown in Figure 3, (N * BB) 304 combination can be used in even larger scale for many frameworks ethernet router (MER) 302 and parallel backbone network.For example, as shown in the example in Fig. 3, use the combination of MER 302 and parallel backbone network 304, the capacity of 300G Ethernet switch 306 can increase 64x to 19200G.In this example, 8 * MER 310 and 8 * parallel backbone network structure 312 is combined to obtain the network configuration 314 based on MER of 64 * extensibility multiple parallel.If use larger MER 302 (for example, 16 * or 32 *) and/or multiple parallel backbone network 304 more, extensibility even can be larger.Therefore, these technology of using separately and/or together can greatly help the expansion capacity.
In addition, as shown in Figure 4, based on the core network 402 of Ethernet (for example, core network based on MER 404) can be used as parallel core network 402 and be added to existing MPLS core network 406, thereby easily improve extensibility with reasonable price, and needn't replace existing core network 402.The reciprocity website place's interconnection in reciprocity edge network 408 of new parallel core network 402 and MPLS core network 406.In this embodiment, some existing users and new user can be transferred 410 to New Consumers edge network 414 from existing customer edge network 412.The flow that is transferred to the user of new customer edge network 414 can be routed to new Ethernet core backbone network 402.Alternatively, can be placed on new backbone network 402 such as the specific service of VoIP, simultaneously other services be stayed on MPLS network 406.It is contemplated that and use many different schemes of utilizing two cores.
Fig. 5 is another example based on the parallel core 502 of Ethernet parallel with having MPLS core 504 now.Outside minimum cost routing protocol technology such as the BGP technology can be used to based on which backbone network of each destination choice use.For the embodiment of key diagram 5, via customer edge network 506 announcement destination addresses A.1 and A.2.Alternative route has been labeled the BGP common identifier, such as public character string 508 or 510 (with IP down hop loopback address), illustrates as utilizing respectively bulletin 512 and 514.Under the particular case shown in Fig. 5, public character string is used for the minimum cost Route Selection and processes, going to the packet of address " A.1 " via backbone network 0 (BB0) route, and go to the packet of " A.2 " via backbone network 2 (BB2) route.
Similarly, based on destination address, public character string can force packet through backbone network effectively.This selection can be carried out as the basis take route, and can change based on the source.In one embodiment, the provider's edge device in provider's edge network 516 is based on the route selection backbone network.Alternatively, can use the global strategy based on the user, make all flows that exist in the User Part of particular group use same backbone network.Route selection and route map can be generated automatically by the capacity planning instrument.
Middle LAN (LlM)
Another network implementation mode that can be used for expanding the backbone network core is LIM.The embodiment of LIM 602 has been shown in Fig. 6.In the embodiment shown, core router 604a-604n is connected to edge router 606a-606n via Ethernet switch 608a-608n.This is similarly to configure with above-mentioned MER, is used for level 1 and level 3 except having core router and edge router now, rather than all levels of use Ethernet switch.The advantage of this configuration is that the existing route device can expand greatlyr, and needn't replace them with Ethernet switch.As above discuss, use the Ethernet switch in the intermediate layer and use the CLOS matrix, will increase the capacity of existing core router 604 and edge router 606.In one embodiment, core 604 and edge router 606 will be responsible for for providing flow via matrix 608.
Fig. 7 is the schematic diagram of the optional embodiment of LIM 700.For example can have 4 * 10G to LIM towards the user at provider edge (PE) 702.For 1+1 protection, this will allow 20G user in the face of working flow.At WAN towards side, 4 * 10G that each provider or core router (P) 704 has to LIM.For 1+1 protection, this will allow the WAN traffic of 20G at least.
Route Selection by multiple backbone network structure
Fig. 8 shows the example networks 800 that comprises a plurality of parallel backbone network 802a-802b and provider's edge device 804.This network 800 is that the first and second user networks (for example, user network A 806a and user network B 806b) provide the backbone network service.For easy explanation, user network A 806a has the related IP address that is expressed as A.1 here, and user network B 806b has related IP address B.1.Accessibility IP address more generally is expressed as A.X on user network A 806a, and accessibility IP address more generally is expressed as B.X on user network B 806b.
Node (such as router) on user network A 806a and user network B 806b is announced respectively A.X address and B.X address, makes the node of this provider's edge device PE1804 and other networks 800 can determine how packet to be routed to A.X address and B.X address.Bulletin from user network A 806a and user network B 806b is illustrated by arrow 808a and 808b respectively.
PE1804 has been labeled site identifier " WDC ", and it represents Washington DC.Therefore, in the situation that shown in, PE1804 processes the communication that is associated with user network in DC zone, Washington.Use WDC or any other specific site identifier only to be convenient to explanation, and it will be apparent to one skilled in the art that the processing about PE1804 described here can be carried out by any provider's edge device, and do not consider customer rs site.The description here relates to when using a plurality of backbone network, is used for packet is routed to the processing of station address.Therefore, although can be the source and destination of data at the node at address A.X and B.X place, for convenience of explanation, address A.X and B.X all be called " destination address " here.
Can carry out Route Selection via network 800 according to any in multiple criterion or strategy.Example comprises that the special-purpose multiple exit discriminator (MED) of Route Selection (for example, minimum cost Route Selection), user and the local first level based on cost arranges.For illustrative purposes, suppose preferentially to adopt the special-purpose strategy of (honor) user and local preferred the setting, and be according to the minimum cost routing strategy via the mode of the Route Selection of network 800.
The node of PE1804 from user network A 806a and user network B 806b receives one or more bulletins.PE1804 determines which backbone network is distributed to the A.X address and which backbone network is distributed to the B.X address.In one embodiment, PE1 selects backbone network based on outside minimum cost routing strategy (for example, Border Gateway Protocol (BGP)).In this embodiment, keep the shortest export, and do not consider to select the backbone network for each A.X address and B.X address.Under the particular case shown in Fig. 8, the communication of selecting backbone network 802a to be associated with user network A 806a with processing, and select backbone network 802b to process the communication that is associated with user network B 806b.
Strategy for the backbone network 802b of the backbone network 802a that strengthens using the A.X address and B.X address uses down hop minimum cost routing protocol tolerance.In one embodiment, down hop IGP tolerance is used for strengthening Route Selection.The first down hop loopback address L0 that PE1804 announcement is associated with the A.X address and the second down hop loopback address L1 that is associated with the B.X address.Address L0 and address L2 all are associated with port on PE1804.In one embodiment, PE1 uses the OSPF mark with by each label that is associated in backbone network 802a and backbone network 802b propagation and L0 and L2.Following being shown in further detail is routed through backbone network 802a and the packet of going to the B.X address with the packet of going to the A.X address and is routed this mode through backbone network 802b, and cost metric can be associated with the down hop loopback address.
According to an embodiment, PE1804 produces the route map that comprises the routing information relevant with the B.X address to the A.X address.Under the particular case shown in Fig. 8, it is related that route map can have another between related and A.X and backbone network 802a (BB0) between A.X and L0.Similarly, it is related that route map can have another between related and B.X and backbone network 802b (BB2) between B.X and L2.Identifier BB0 and BB2 are known as common identifier, and can be propagated the backbone network that is associated through the station address with their distribution.The simplified example that the below shows route map is used for explanation:
The PE1.WDC route map
Coupling A.X
Down hop L0.PE1.WDC.CUST.NET is set
Public BB0 is set
Coupling B.X
Down hop L2.PE1.WDC.CUST.NET is set
Public BB2 is set
At first, the provider of backbone network service can have a backbone network as wide area network.For a variety of reasons, this backbone network service provider can be increased to its network configuration with one or more additional backbone area networks.Additional backbone network can provide better Route Selection efficient or extensibility.As the result that merges with another backbone network service provider, this backbone network service provider can increase the number of backbone network.Do not consider to increase the reason of one or more backbone networks, the backbone network service provider can be carried out the processing of some network service provider routes being transferred to one or more backbone networks that increase.Fig. 9-Figure 10 shows the processing of transfer that can carry out to support the ISP route according to an embodiment.
Fig. 9 shows the exemplary network structure shown in Fig. 8, wherein, public character string is used for being convenient to the selectivity backbone network Route Selection based on the destination, and wherein, in the mode of forcing the packet route is passed through the backbone network that is distributed with absorption of costs to the down hop loopback address.For convenience of explanation, only show two backbone networks: BB0 902a and BB2 902b.Should be appreciated that, a plurality of backbone networks can be provided.First provider's edge device PE1.WDC 904a is connected with the user network of Washington DC, and second provider's edge device PE1.LAX 904b is connected with the user network in Los Angeles simultaneously.
In the situation that shown in, down hop loopback address L0 has been assigned to station address A.X, and down hop loopback address L2 has been assigned to station address B.X.Embodiment is to guarantee that address L0 arrives via BB0 902a and L2 announces L0 and L2 via the mode that BB2 902b arrives.Under a particular case, use the processing of redistributing based on cost, the B.X flow is transferred to BB2 902b.
In order to illustrate, PE1.WDC 904a can announce L0 and announce L2 to the first based on core node 906a and the second core node 906b based on WDC of WDC with initial cost with initial cost.Initial cost can be identical.Have the L2 of WDC label by announcement only, the second core node 906b based on WDC redistributes L0 and L2 address.This second core node 906b is increased to cost the initial cost owing to L2 usually.This second core node 908b based on LAX receives and announces and form another bulletin.
In forming the process of this bulletin, the second core node 908b based on LAX reduces the cost that is associated with address L2, to be slightly less than the cost that is associated with L0.This second core node 908b based on LAX is included in " redistributing " label in bulletin, and bulletin is sent to PE1.LAX 904b.PE1.LAX 904b has created and has comprised B.X, the related route map between L2 and BB2 902b.Therefore, when PE1.LAX 904b reception is addressed to the packet of B.X, at first PE1.LAX 904b is designated L2 the minimum cost route that arrives B.X, and will determine that then the second core node 908b based on LAX is the minimum cost node that Packet Generation is gone out.
Figure 10 shows dual inside and processes based on the Link State generation of cost, wherein, the operation of the edge router on the edge of the backbone network in multiple parallel backbone network structure is processed based on the Link State generation of cost to two inside of side towards side and local wire side for wide area network.
In the situation that shown in Figure 10, this second backbone network 1012 is added in network configuration 1000, wherein, there is and processes all providers between first provider's fringe node 1006 and second provider's fringe node 1008/telex network flow at first in this first network backbone network 1010.After having increased by the second backbone network 1012, selected provider/telex network flow can be processed by the second backbone network 1012.The first backbone network 1010 can maybe can be not used as backup network, to process the communication flows of being processed by the second backbone network 1012.
Execution is redistributed and is processed so that selected communication flows is processed by the second backbone network 1012.Selected with after being processed by new backbone network 1012 at communication flows, redistribute processing and be usually directed to process at a LAN 1002 and the inner minimum cost routing protocol of the 2nd interior execution of LAN 1004, and carry out another inner minimum cost routing protocol between the core node in the second backbone network 1012 and process.At first, selected provider/station address and/or route are assigned to backbone network 1012, and local port address (for example, L2,2.2.2.2) is assigned to selected user/provider address and/or route.Then, carry out inner minimum cost routing protocol and process so that local port address propagation is spreaded all over network configuration 1000, be routed through correct backbone network to guarantee communication flows.
In order to illustrate, to carry out local between PE1 1006 and core node N1P1 1014, N1P2 1016, N2P1 1022 and N2P2 1024 or process based on the OSPF of LAN.This OSPF based on LAN processes 1030 and relates to the OSPF label is propagated into core node.Under the particular case shown in Figure 10, PE1 1006 sends to the first label (for example, label 1) corresponding to the N1P1 1014 of the route that is associated with down hop loopback address L0 (1.1.1.1) and the core node of N1P2 1016.PE1 1006 sends to core node N2P1 1022 and N2P2 1024 corresponding to the route that is associated with down hop loopback address L2 (2.2.2.2) with another label (for example, label 2).
In the second backbone network 1012, the core router on the second backbone network 1012 is carried out another OSPF and is processed 1032.Under specific exemplary cases, the down hop loopback label 2 that core router N2P11022 and N2P2 1024 will be associated with address L2 (2.2.2.2) propagates into core router N2P3 1026 and N2P4 1028.
Figure 11 illustrates for carry out the flow chart of the algorithm 1100 of minimum cost Route Selection in multiple backbone network structure.In this embodiment, suppose that provider's fringe node is understood or the other purpose network address of determining about just serviced network (for example, ISP network).In selecting operation 1102, provider's fringe node selects backbone network for the treatment of the communication that is associated with one or more purposes network addresss.In an embodiment who selects operation, for each purpose network address, provider's fringe node is carried out outside minimum cost routing protocol and is processed, such as Border Gateway Protocol (BGP), to select backbone network from a plurality of backbone networks, this will produce packet to the minimum cost Route Selection of the purpose network address.
In batch operation 1104, the down hop loopback address is assigned to each purpose network address.This down hop loopback address is corresponding to the port on provider's edge network that can arrive via selected backbone network.In announcement operation 1106, announce each down hop loopback address and the related purpose network address via one or more backbone networks.An embodiment of announcement operation 1106 relates to the inner minimum cost routing protocol of execution to be processed, and processes such as OSPF/ISIS or other Interior Gateway Protocols (IGP).Use OSPF, propagated through one or more backbone networks with the label that down hop loopback address and/or the backbone network that distributes are associated, will be used for the backbone network route of the purpose network address of association with identification.
In setting operation 1108, such as another provider's fringe node setting and the cost that will be associated through each down hop loopback address that one or more backbone networks arrive of source provider's fringe node.In one embodiment, carry out between the core routing nodes on source provider's fringe node and the backbone network that distributes that Open Shortest Path First (OSPF) and/or the ISIS protocol processes, so that the cost that arrives the down hop loopback address when using the backbone network that distributes is lower than the cost of arrival down hop loopback address when any other network of use.In this was processed, the down hop loopback address can be labeled the backbone network that is associated with the down hop loopback address.
Exemplary computing equipment
Figure 12 is the schematic diagram that can realize and carry out the computing equipment 1200 of the embodiment of the present invention.The element of computing equipment 1200 is shown as the element that SIP registrar server can comprise or carries out above-mentioned reorientation and determine the server computer processed.
As discussed here, embodiments of the invention comprise a plurality of steps.Multiple these steps can be carried out or can be realized by machine-executable instruction by hardware element, and this machine-executable instruction can be used for making the universal or special processor execution in step of utilizing instruction programming.Alternatively, these steps can be passed through the combination execution of hardware, software and/or firmware.
According to current example, computing equipment 1200 comprises: bus 1201, at least one processor 1202, at least one communication port 1203, main storage 1204, movable storage medium 1205, read-only memory 1206 and mass storage 1207.(a plurality of) processor 1202 can be any known processor, such as but be not limited to Intel
Itanium
Or Itanium 2
Processor or (a plurality of) AMD
Opteron
Or Athlon MP
Processor or Motorola
Series processors.(a plurality of) communication port 1203 can be with the RS-232 port that uses together with the dial-up connection of modulator-demodulator, 10/100 ethernet port, the gigabit port that uses copper or optical fiber or USB port in any.(a plurality of) communication port 1203 can be selected according to any network that connects such as local area network (LAN) (LAN), wide area network (WAN) or computing equipment 1200.This computing equipment 1200 can be communicated by letter with the ancillary equipment (not shown), this ancillary equipment such as but be not limited to printer, loud speaker, video camera, microphone or scanner.
In the situation that do not deviate from scope of the present invention, can carry out various modifications and increase to exemplary embodiment discussed here.For example, although above-described embodiment is mentioned special characteristic, scope of the present invention also comprises the embodiment of the characteristic various combination of tool and does not comprise the embodiment of all above-mentioned features.Therefore, scope of the present invention be intended to comprise all such replacements, modification, variation with and all equivalents.
Although the present invention is described with reference to preferred embodiment, one skilled in the art will understand that to change in form and details in the situation that do not deviate from the spirit and scope of the present invention.
Claims (15)
1. method that is used for packet is routed to the first purpose network address, described method comprises:
Use outside minimum cost routing protocol to select the first backbone network from a plurality of backbone networks, and described the first backbone network is distributed to the described first purpose network address;
The first down hop loopback address is associated with the described first purpose network address, and wherein, described the first down hop loopback address is corresponding to the port on the purpose provider's edge device between described the first backbone network and purpose network;
Via described the first backbone network, the described first purpose network address is announced together with accessibility described the first down hop loopback address,
Thereby the packet that is addressed to the described first purpose network address is routed to the described first purpose network address, and described route is passed through described the first backbone network that distributes and arrived described the first down hop loopback address.
2. method according to claim 1 also comprises: first common identifier that will represent described the first backbone network is associated with the described first purpose network address.
3. method according to claim 2, also comprise: create route map, described route map comprises related between related and the described first purpose network address and described the first common identifier between the described first purpose network address and described the first down hop loopback address.
4. method according to claim 1 also comprises:
The second backbone network in described a plurality of backbone networks is distributed to the second purpose network address;
The second down hop loopback address is associated with the described second purpose network address, and wherein, described the second down hop loopback address is corresponding to the port on the purpose provider's edge device between described the second backbone network and purpose network;
With the described second purpose network address with announce together with accessibility described the second down hop loopback address of described the second backbone network,
Thereby the packet that is addressed to the described second purpose network address is routed through described the second backbone network.
5. method according to claim 1 wherein, is used Interior Gateway Protocol, and the packet that is addressed to the described first purpose network address is routed through described the first backbone network to described the first down hop loopback address.
6. method according to claim 1, also comprise: inner minimum cost routing metric is set to provider's edge site identifier.
7. method according to claim 4 also comprises: the inside minimum cost routing metric that will be associated with described the second down hop loopback address in described the second backbone network is arranged to the value less than another the inner minimum cost tolerance that is associated with described the first down hop loopback address in described the first backbone network.
8. method according to claim 4, wherein, the described first purpose network address and the described second purpose network address are associated from different routes via one or more customer edge network.
9. method according to claim 4, wherein, the edge router that is associated with described the second backbone network is supported two kinds of inner minimum cost routing protocols.
10. method according to claim 9, wherein, described edge router is carried out the first inner minimum cost Route Selection via the port on the edge router of described the second backbone network and is processed, and wherein, described edge router is carried out the second minimum cost Route Selection processing via the another port on the edge router of edge network.
11. method according to claim 4, wherein, described the first backbone network is as the backup network of described the second backbone network.
12. one kind is used for providing the method for communication between provider's network, described method comprises:
For via each in many communicating routes of one or more provider's networks:
Reception has the bulletin of the first network destination address that is associated with described communicating route;
Use outside minimum cost routing protocol to select the first backbone network from a plurality of backbone networks;
The first down hop loopback address is associated with described first network destination address, wherein, described the first down hop loopback address can arrive via selected the first backbone network, wherein, described the first down hop loopback address is corresponding to the port on the purpose provider's edge device between described the first backbone network and purpose network;
Give described the first down hop loopback address with the first absorption of costs, wherein, described the first cost less than with the second cost that is associated by accessibility the second down hop loopback address of the second backbone network, wherein, described the second down hop loopback address is corresponding to the port on the purpose provider's edge device between described the second backbone network and purpose network; And
Via described the first down hop loopback address of described a plurality of backbone network announcement, wherein, announcement comprises that indication is via described first cost of selected the first described the first down hop loopback address of backbone network access.
13. one kind is used for providing the method for communication between provider's network, comprises:
Use outside minimum cost routing protocol to select backbone networks from a plurality of backbone networks, and selected backbone network is distributed in the purpose network address;
The down hop loopback address is associated with the described purpose network address, wherein, described down hop loopback address corresponding to purpose provider's edge device that selected backbone network is communicated by letter on port; And
The described down hop loopback address of notification source provider's edge device utilizes the minimum cost Route Selection to arrive via selected backbone network.
14. method according to claim 13 wherein, notifies described source provider's edge device to comprise: carry out inner minimum cost routing protocol between the source core router equipment in described source provider's edge device and selected backbone network.
15. method according to claim 14, also comprise: carry out described inner minimum cost routing protocol between the purpose core router equipment in described source core router equipment and selected backbone network and process, with the cost of determining to be associated with described down hop loopback address.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US11/565,563 US8064467B2 (en) | 2005-02-04 | 2006-11-30 | Systems and methods for network routing in a multiple backbone network architecture |
| US11/565,563 | 2006-11-30 | ||
| PCT/US2007/061629 WO2008066936A1 (en) | 2006-11-30 | 2007-02-05 | Systems and methods for network routing in a multiple backbone network architecture |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101485161A CN101485161A (en) | 2009-07-15 |
| CN101485161B true CN101485161B (en) | 2013-06-12 |
Family
ID=39468241
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007800251934A Expired - Fee Related CN101485161B (en) | 2006-11-30 | 2007-02-05 | Systems and methods for network routing in a multiple backbone network architecture |
| CN2007800250931A Expired - Fee Related CN101485156B (en) | 2006-11-30 | 2007-11-29 | System and method for switching traffic through a network |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007800250931A Expired - Fee Related CN101485156B (en) | 2006-11-30 | 2007-11-29 | System and method for switching traffic through a network |
Country Status (6)
| Country | Link |
|---|---|
| US (3) | US8064467B2 (en) |
| EP (2) | EP2515490A3 (en) |
| CN (2) | CN101485161B (en) |
| CA (1) | CA2657111A1 (en) |
| HK (1) | HK1134973A1 (en) |
| WO (1) | WO2008066936A1 (en) |
Families Citing this family (137)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2595788C (en) * | 2005-02-04 | 2013-06-25 | Level 3 Communications, Inc. | Ethernet-based systems and methods for improved network routing |
| US8064467B2 (en) * | 2005-02-04 | 2011-11-22 | Level 3 Communications, Llc | Systems and methods for network routing in a multiple backbone network architecture |
| US8532095B2 (en) * | 2005-11-18 | 2013-09-10 | Cisco Technology, Inc. | Techniques configuring customer equipment for network operations from provider edge |
| US9426092B2 (en) * | 2006-02-03 | 2016-08-23 | Level 3 Communications Llc | System and method for switching traffic through a network |
| JP4630225B2 (en) * | 2006-05-15 | 2011-02-09 | 富士通株式会社 | Communication control system |
| US8000327B1 (en) | 2006-09-29 | 2011-08-16 | Juniper Networks, Inc. | Quality of service (QoS)-aware forwarding in an MPLS network with tactical traffic engineering |
| US7826482B1 (en) * | 2006-11-17 | 2010-11-02 | Juniper Networks, Inc. | Service-specific forwarding in an LDP-RSVP hybrid network |
| US8184786B2 (en) | 2007-02-26 | 2012-05-22 | Service Bureau Intetel S.A. | Updating routing patterns in an enterprise network |
| US8028090B2 (en) | 2008-11-17 | 2011-09-27 | Amazon Technologies, Inc. | Request routing utilizing client location information |
| US7991910B2 (en) | 2008-11-17 | 2011-08-02 | Amazon Technologies, Inc. | Updating routing information based on client location |
| JP2009147735A (en) * | 2007-12-14 | 2009-07-02 | Nec Corp | Network, node device, network redundancy method, and network redundancy program |
| US8396988B2 (en) * | 2007-12-19 | 2013-03-12 | At&T Intellectual Property I, L.P. | Method and system for survival of data plane through a total control plane failure |
| TW200937939A (en) * | 2008-02-26 | 2009-09-01 | Asustek Comp Inc | Method for establishing a communications link |
| US7970820B1 (en) | 2008-03-31 | 2011-06-28 | Amazon Technologies, Inc. | Locality based content distribution |
| US8156243B2 (en) | 2008-03-31 | 2012-04-10 | Amazon Technologies, Inc. | Request routing |
| US8321568B2 (en) | 2008-03-31 | 2012-11-27 | Amazon Technologies, Inc. | Content management |
| US8447831B1 (en) | 2008-03-31 | 2013-05-21 | Amazon Technologies, Inc. | Incentive driven content delivery |
| US8606996B2 (en) | 2008-03-31 | 2013-12-10 | Amazon Technologies, Inc. | Cache optimization |
| US8601090B1 (en) | 2008-03-31 | 2013-12-03 | Amazon Technologies, Inc. | Network resource identification |
| US8533293B1 (en) | 2008-03-31 | 2013-09-10 | Amazon Technologies, Inc. | Client side cache management |
| US7962597B2 (en) | 2008-03-31 | 2011-06-14 | Amazon Technologies, Inc. | Request routing based on class |
| US9912740B2 (en) | 2008-06-30 | 2018-03-06 | Amazon Technologies, Inc. | Latency measurement in resource requests |
| US7925782B2 (en) | 2008-06-30 | 2011-04-12 | Amazon Technologies, Inc. | Request routing using network computing components |
| US9407681B1 (en) | 2010-09-28 | 2016-08-02 | Amazon Technologies, Inc. | Latency measurement in resource requests |
| US8316124B1 (en) | 2008-09-29 | 2012-11-20 | Amazon Technologies, Inc. | Managing network data display |
| US8122124B1 (en) | 2008-09-29 | 2012-02-21 | Amazon Technologies, Inc. | Monitoring performance and operation of data exchanges |
| US7930393B1 (en) | 2008-09-29 | 2011-04-19 | Amazon Technologies, Inc. | Monitoring domain allocation performance |
| US8117306B1 (en) | 2008-09-29 | 2012-02-14 | Amazon Technologies, Inc. | Optimizing content management |
| US8286176B1 (en) | 2008-09-29 | 2012-10-09 | Amazon Technologies, Inc. | Optimizing resource configurations |
| US7865594B1 (en) | 2008-09-29 | 2011-01-04 | Amazon Technologies, Inc. | Managing resources consolidation configurations |
| US8051166B1 (en) | 2008-09-29 | 2011-11-01 | Amazon Technologies, Inc. | Service provider optimization of content management |
| US8521880B1 (en) | 2008-11-17 | 2013-08-27 | Amazon Technologies, Inc. | Managing content delivery network service providers |
| US8060616B1 (en) | 2008-11-17 | 2011-11-15 | Amazon Technologies, Inc. | Managing CDN registration by a storage provider |
| US8073940B1 (en) | 2008-11-17 | 2011-12-06 | Amazon Technologies, Inc. | Managing content delivery network service providers |
| US8122098B1 (en) | 2008-11-17 | 2012-02-21 | Amazon Technologies, Inc. | Managing content delivery network service providers by a content broker |
| US8732309B1 (en) | 2008-11-17 | 2014-05-20 | Amazon Technologies, Inc. | Request routing utilizing cost information |
| US8065417B1 (en) | 2008-11-17 | 2011-11-22 | Amazon Technologies, Inc. | Service provider registration by a content broker |
| US8693372B2 (en) * | 2009-01-29 | 2014-04-08 | Qualcomm Incorporated | Methods and apparatus for forming, maintaining and/or using overlapping networks |
| US7917618B1 (en) | 2009-03-24 | 2011-03-29 | Amazon Technologies, Inc. | Monitoring web site content |
| US8521851B1 (en) | 2009-03-27 | 2013-08-27 | Amazon Technologies, Inc. | DNS query processing using resource identifiers specifying an application broker |
| US8756341B1 (en) | 2009-03-27 | 2014-06-17 | Amazon Technologies, Inc. | Request routing utilizing popularity information |
| US8412823B1 (en) | 2009-03-27 | 2013-04-02 | Amazon Technologies, Inc. | Managing tracking information entries in resource cache components |
| US8688837B1 (en) | 2009-03-27 | 2014-04-01 | Amazon Technologies, Inc. | Dynamically translating resource identifiers for request routing using popularity information |
| US8782236B1 (en) | 2009-06-16 | 2014-07-15 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
| US8397073B1 (en) | 2009-09-04 | 2013-03-12 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
| US8433771B1 (en) | 2009-10-02 | 2013-04-30 | Amazon Technologies, Inc. | Distribution network with forward resource propagation |
| US8331371B2 (en) | 2009-12-17 | 2012-12-11 | Amazon Technologies, Inc. | Distributed routing architecture |
| US8331370B2 (en) * | 2009-12-17 | 2012-12-11 | Amazon Technologies, Inc. | Distributed routing architecture |
| US8325730B2 (en) * | 2009-12-17 | 2012-12-04 | Amazon Technologies, Inc. | Distributed routing architecture |
| US9495338B1 (en) | 2010-01-28 | 2016-11-15 | Amazon Technologies, Inc. | Content distribution network |
| US8472324B1 (en) * | 2010-06-29 | 2013-06-25 | Amazon Technologies, Inc. | Managing route selection in a communication network |
| US8576848B2 (en) | 2010-09-17 | 2013-11-05 | At&T Intellectual Property I, L.P. | Scalable multiprotocol label switching (MPLS) based networks |
| US8577992B1 (en) | 2010-09-28 | 2013-11-05 | Amazon Technologies, Inc. | Request routing management based on network components |
| US8819283B2 (en) | 2010-09-28 | 2014-08-26 | Amazon Technologies, Inc. | Request routing in a networked environment |
| US9003035B1 (en) | 2010-09-28 | 2015-04-07 | Amazon Technologies, Inc. | Point of presence management in request routing |
| US9712484B1 (en) | 2010-09-28 | 2017-07-18 | Amazon Technologies, Inc. | Managing request routing information utilizing client identifiers |
| US10958501B1 (en) | 2010-09-28 | 2021-03-23 | Amazon Technologies, Inc. | Request routing information based on client IP groupings |
| US8938526B1 (en) | 2010-09-28 | 2015-01-20 | Amazon Technologies, Inc. | Request routing management based on network components |
| US8930513B1 (en) | 2010-09-28 | 2015-01-06 | Amazon Technologies, Inc. | Latency measurement in resource requests |
| US8468247B1 (en) | 2010-09-28 | 2013-06-18 | Amazon Technologies, Inc. | Point of presence management in request routing |
| US8924528B1 (en) | 2010-09-28 | 2014-12-30 | Amazon Technologies, Inc. | Latency measurement in resource requests |
| US10097398B1 (en) | 2010-09-28 | 2018-10-09 | Amazon Technologies, Inc. | Point of presence management in request routing |
| US8452874B2 (en) | 2010-11-22 | 2013-05-28 | Amazon Technologies, Inc. | Request routing processing |
| US9391949B1 (en) | 2010-12-03 | 2016-07-12 | Amazon Technologies, Inc. | Request routing processing |
| US8626950B1 (en) | 2010-12-03 | 2014-01-07 | Amazon Technologies, Inc. | Request routing processing |
| US9282060B2 (en) * | 2010-12-15 | 2016-03-08 | Juniper Networks, Inc. | Methods and apparatus for dynamic resource management within a distributed control plane of a switch |
| US10467042B1 (en) | 2011-04-27 | 2019-11-05 | Amazon Technologies, Inc. | Optimized deployment based upon customer locality |
| CN102185772B (en) * | 2011-05-05 | 2013-10-23 | 北京交通大学 | Method for routing data centre network system |
| CN102164088B (en) * | 2011-05-05 | 2013-10-23 | 北京交通大学 | Data centre network system |
| EP2675118B1 (en) * | 2012-01-11 | 2016-01-06 | Huawei Technologies Co., Ltd. | Method and device for adjusting ip network load |
| US8904009B1 (en) | 2012-02-10 | 2014-12-02 | Amazon Technologies, Inc. | Dynamic content delivery |
| US10021179B1 (en) | 2012-02-21 | 2018-07-10 | Amazon Technologies, Inc. | Local resource delivery network |
| US9083743B1 (en) | 2012-03-21 | 2015-07-14 | Amazon Technologies, Inc. | Managing request routing information utilizing performance information |
| US10623408B1 (en) | 2012-04-02 | 2020-04-14 | Amazon Technologies, Inc. | Context sensitive object management |
| US9154551B1 (en) | 2012-06-11 | 2015-10-06 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
| US9288140B2 (en) | 2012-07-09 | 2016-03-15 | Coriant Operations, Inc. | Multichassis failover and recovery for MLPPP wireless backhaul |
| US9525659B1 (en) | 2012-09-04 | 2016-12-20 | Amazon Technologies, Inc. | Request routing utilizing point of presence load information |
| US9323577B2 (en) | 2012-09-20 | 2016-04-26 | Amazon Technologies, Inc. | Automated profiling of resource usage |
| US9135048B2 (en) | 2012-09-20 | 2015-09-15 | Amazon Technologies, Inc. | Automated profiling of resource usage |
| US9197541B2 (en) * | 2012-11-15 | 2015-11-24 | Compass Electro Optical Systems Ltd. | Router with passive interconnect and distributed switchless switching |
| US9444712B2 (en) | 2012-11-21 | 2016-09-13 | Cisco Technology, Inc. | Bandwidth on-demand services in multiple layer networks |
| US10205698B1 (en) | 2012-12-19 | 2019-02-12 | Amazon Technologies, Inc. | Source-dependent address resolution |
| CN103269316B (en) * | 2013-05-28 | 2016-06-29 | 北京星网锐捷网络技术有限公司 | The processing method of routing and device and the network equipment |
| US9294391B1 (en) | 2013-06-04 | 2016-03-22 | Amazon Technologies, Inc. | Managing network computing components utilizing request routing |
| US9825857B2 (en) * | 2013-11-05 | 2017-11-21 | Cisco Technology, Inc. | Method for increasing Layer-3 longest prefix match scale |
| JP6204168B2 (en) | 2013-11-27 | 2017-09-27 | 株式会社日立製作所 | Transfer device, server, and route change method |
| US9553993B2 (en) * | 2014-01-31 | 2017-01-24 | Tracfone Wireless, Inc. | Device and process for selecting one of a plurality of direct inward dialing numbers |
| US9608913B1 (en) * | 2014-02-24 | 2017-03-28 | Google Inc. | Weighted load balancing in a multistage network |
| US10097448B1 (en) | 2014-12-18 | 2018-10-09 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
| US10091096B1 (en) | 2014-12-18 | 2018-10-02 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
| US10033627B1 (en) | 2014-12-18 | 2018-07-24 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
| CN104601495B (en) * | 2015-01-30 | 2018-11-30 | 杭州晨晓科技股份有限公司 | A kind of system extending physical port |
| US10225326B1 (en) | 2015-03-23 | 2019-03-05 | Amazon Technologies, Inc. | Point of presence based data uploading |
| US9887931B1 (en) | 2015-03-30 | 2018-02-06 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
| US9887932B1 (en) | 2015-03-30 | 2018-02-06 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
| US9819567B1 (en) | 2015-03-30 | 2017-11-14 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
| US9832141B1 (en) | 2015-05-13 | 2017-11-28 | Amazon Technologies, Inc. | Routing based request correlation |
| US10616179B1 (en) | 2015-06-25 | 2020-04-07 | Amazon Technologies, Inc. | Selective routing of domain name system (DNS) requests |
| US10063428B1 (en) * | 2015-06-30 | 2018-08-28 | Apstra, Inc. | Selectable declarative requirement levels |
| US10097566B1 (en) | 2015-07-31 | 2018-10-09 | Amazon Technologies, Inc. | Identifying targets of network attacks |
| US9794281B1 (en) | 2015-09-24 | 2017-10-17 | Amazon Technologies, Inc. | Identifying sources of network attacks |
| US9742795B1 (en) | 2015-09-24 | 2017-08-22 | Amazon Technologies, Inc. | Mitigating network attacks |
| US9774619B1 (en) | 2015-09-24 | 2017-09-26 | Amazon Technologies, Inc. | Mitigating network attacks |
| US9794174B2 (en) | 2015-09-30 | 2017-10-17 | Juniper Networks, Inc. | Fast path content delivery over metro access networks |
| US9917774B2 (en) | 2015-09-30 | 2018-03-13 | Juniper Networks, Inc. | Content caching in metro access networks |
| WO2017071729A1 (en) * | 2015-10-26 | 2017-05-04 | Abb Schweiz Ag | Methods, nodes and system for establishing independent network paths |
| US10270878B1 (en) | 2015-11-10 | 2019-04-23 | Amazon Technologies, Inc. | Routing for origin-facing points of presence |
| US10904142B2 (en) * | 2015-11-19 | 2021-01-26 | Adaptiv Networks Inc. | System, apparatus and method for providing a virtual network edge and overlay with virtual control plane |
| US10257307B1 (en) | 2015-12-11 | 2019-04-09 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
| US10049051B1 (en) | 2015-12-11 | 2018-08-14 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
| US10348639B2 (en) | 2015-12-18 | 2019-07-09 | Amazon Technologies, Inc. | Use of virtual endpoints to improve data transmission rates |
| US10187289B1 (en) | 2015-12-28 | 2019-01-22 | Amazon Technologies, Inc. | Route advertisement management using tags in directly connected networks |
| US10129134B2 (en) | 2016-02-29 | 2018-11-13 | Level 3 Communications, Llc | System and method for adding routing paths in a network |
| US10075551B1 (en) | 2016-06-06 | 2018-09-11 | Amazon Technologies, Inc. | Request management for hierarchical cache |
| US10110694B1 (en) | 2016-06-29 | 2018-10-23 | Amazon Technologies, Inc. | Adaptive transfer rate for retrieving content from a server |
| US9992086B1 (en) | 2016-08-23 | 2018-06-05 | Amazon Technologies, Inc. | External health checking of virtual private cloud network environments |
| US10033691B1 (en) | 2016-08-24 | 2018-07-24 | Amazon Technologies, Inc. | Adaptive resolution of domain name requests in virtual private cloud network environments |
| US10650621B1 (en) | 2016-09-13 | 2020-05-12 | Iocurrents, Inc. | Interfacing with a vehicular controller area network |
| US10469513B2 (en) | 2016-10-05 | 2019-11-05 | Amazon Technologies, Inc. | Encrypted network addresses |
| US10372499B1 (en) | 2016-12-27 | 2019-08-06 | Amazon Technologies, Inc. | Efficient region selection system for executing request-driven code |
| US10831549B1 (en) | 2016-12-27 | 2020-11-10 | Amazon Technologies, Inc. | Multi-region request-driven code execution system |
| US10938884B1 (en) | 2017-01-30 | 2021-03-02 | Amazon Technologies, Inc. | Origin server cloaking using virtual private cloud network environments |
| US10362631B2 (en) * | 2017-04-03 | 2019-07-23 | Level 3 Communications, Llc | Last resource disaster routing in a telecommunications network |
| US10503613B1 (en) | 2017-04-21 | 2019-12-10 | Amazon Technologies, Inc. | Efficient serving of resources during server unavailability |
| US11075987B1 (en) | 2017-06-12 | 2021-07-27 | Amazon Technologies, Inc. | Load estimating content delivery network |
| US10447648B2 (en) | 2017-06-19 | 2019-10-15 | Amazon Technologies, Inc. | Assignment of a POP to a DNS resolver based on volume of communications over a link between client devices and the POP |
| US10742593B1 (en) | 2017-09-25 | 2020-08-11 | Amazon Technologies, Inc. | Hybrid content request routing system |
| US10873513B2 (en) * | 2018-02-20 | 2020-12-22 | Vmware, Inc. | Workload identification for network flows in hybrid environments with non-unique IP addresses |
| US10592578B1 (en) | 2018-03-07 | 2020-03-17 | Amazon Technologies, Inc. | Predictive content push-enabled content delivery network |
| TWI819072B (en) * | 2018-08-23 | 2023-10-21 | 美商阿爾克斯股份有限公司 | System, non-transitory computer readable storage media and computer-implemented method for loop conflict avoidance in a network computing environment |
| US10862852B1 (en) | 2018-11-16 | 2020-12-08 | Amazon Technologies, Inc. | Resolution of domain name requests in heterogeneous network environments |
| US11025747B1 (en) | 2018-12-12 | 2021-06-01 | Amazon Technologies, Inc. | Content request pattern-based routing system |
| CN109981428B (en) * | 2019-04-08 | 2021-10-22 | 苏州浪潮智能科技有限公司 | Virtual trunk-based rapid wide area network trunk access method, equipment and storage medium |
| US11050679B1 (en) * | 2019-06-28 | 2021-06-29 | Juniper Networks, Inc. | Defining non-forwarding adjacencies in bipartite networks, such as Clos newtorks, having a level 2 backbone and level 1 nodes |
| CN110311851A (en) * | 2019-07-23 | 2019-10-08 | 上海地面通信息网络股份有限公司 | Network communicating system between a kind of local area network |
| CN111277501B (en) * | 2020-01-19 | 2021-09-14 | 联想(北京)有限公司 | Method, equipment and system for controlling downlink data network selection |
| CN114422752A (en) * | 2021-12-27 | 2022-04-29 | 北京空间机电研究所 | High-reliability test field real-time control monitoring network transmission system |
Family Cites Families (66)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE3220622A1 (en) * | 1982-06-01 | 1983-12-15 | M.A.N.- Roland Druckmaschinen AG, 6050 Offenbach | DATA INPUT DEVICE ON PRINTING MACHINES |
| US4998242A (en) * | 1988-12-09 | 1991-03-05 | Transwitch Corp. | Virtual tributary cross connect switch and switch network utilizing the same |
| US5119370A (en) * | 1989-09-28 | 1992-06-02 | Northern Telecom Limited | Switching node for a communications switching network |
| US5068916A (en) * | 1990-10-29 | 1991-11-26 | International Business Machines Corporation | Coordination of wireless medium among a plurality of base stations |
| US5276445A (en) * | 1990-11-30 | 1994-01-04 | Sony Corporation | Polling control system for switching units in a plural stage switching matrix |
| MX9308193A (en) * | 1993-01-29 | 1995-01-31 | Ericsson Telefon Ab L M | CONTROLLED ACCESS ATM SWITCH. |
| US5541914A (en) * | 1994-01-19 | 1996-07-30 | Krishnamoorthy; Ashok V. | Packet-switched self-routing multistage interconnection network having contention-free fanout, low-loss routing, and fanin buffering to efficiently realize arbitrarily low packet loss |
| US5845215A (en) * | 1995-10-18 | 1998-12-01 | Telefonaktiebolaget Lm Ericsson | Operating mobile stations of wireless communication systems in multiple modes by external control |
| US6151324A (en) * | 1996-06-03 | 2000-11-21 | Cabletron Systems, Inc. | Aggregation of mac data flows through pre-established path between ingress and egress switch to reduce number of number connections |
| US6016307A (en) * | 1996-10-31 | 2000-01-18 | Connect One, Inc. | Multi-protocol telecommunications routing optimization |
| US6574335B1 (en) * | 1999-12-22 | 2003-06-03 | At&T Corp. | Method for simulating a ring back for a call between parties in different communication networks |
| US5999103A (en) * | 1997-06-30 | 1999-12-07 | Mci Communications Corporation | Method and system for assigning spare transmission links to restoral routes |
| US6633569B2 (en) | 1998-04-16 | 2003-10-14 | Samsung Electronics Co., Ltd. | System and method for routing data cells through an ATM architecture using quality of service data in a service control point |
| JP3319442B2 (en) | 1998-08-21 | 2002-09-03 | 日本電信電話株式会社 | ATM switch |
| US6600741B1 (en) * | 1999-03-25 | 2003-07-29 | Lucent Technologies Inc. | Large combined broadband and narrowband switch |
| US6982974B1 (en) * | 1999-01-15 | 2006-01-03 | Cisco Technology, Inc. | Method and apparatus for a rearrangeably non-blocking switching matrix |
| US6665273B1 (en) * | 2000-01-11 | 2003-12-16 | Cisco Technology, Inc. | Dynamically adjusting multiprotocol label switching (MPLS) traffic engineering tunnel bandwidth |
| US6335992B1 (en) * | 2000-02-15 | 2002-01-01 | Tellium, Inc. | Scalable optical cross-connect system and method transmitter/receiver protection |
| WO2001099344A2 (en) * | 2000-06-14 | 2001-12-27 | Williams Communications, Llc | Route selection within a network with peering connections |
| US6804731B1 (en) | 2000-08-11 | 2004-10-12 | Paion Company, Limited | System, method and article of manufacture for storing an incoming datagram in switch matrix in a switch fabric chipset system |
| US6981055B1 (en) | 2000-08-22 | 2005-12-27 | Internap Network Services Corporation | Method and system for optimizing routing through multiple available internet route providers |
| US6781984B1 (en) * | 2000-08-30 | 2004-08-24 | Ciena Corporation | Techniques and architectures for implementing a data skew equalizer for data alignment in a distributed system |
| US7080161B2 (en) | 2000-10-17 | 2006-07-18 | Avaya Technology Corp. | Routing information exchange |
| GB0031839D0 (en) * | 2000-12-29 | 2001-02-14 | Marconi Comm Ltd | A multi-service digital cross-connect |
| US20020186433A1 (en) | 2001-06-12 | 2002-12-12 | Manav Mishra | Routing and switching in a hybrid network |
| US7342922B1 (en) * | 2001-06-18 | 2008-03-11 | Cisco Technology, Inc. | Multi-stage switching for networks |
| JP2003009194A (en) | 2001-06-25 | 2003-01-10 | Kddi Corp | Optical crossconnect system and its controller and controlling method |
| US7151744B2 (en) * | 2001-09-21 | 2006-12-19 | Slt Logic Llc | Multi-service queuing method and apparatus that provides exhaustive arbitration, load balancing, and support for rapid port failover |
| US7106729B1 (en) * | 2001-10-29 | 2006-09-12 | Ciena Corporation | Switching control mechanism based upon the logical partitioning of a switch element |
| US7027396B1 (en) * | 2002-02-13 | 2006-04-11 | At&T Corp. | Traffic matrix computation for a backbone network supporting virtual private networks |
| US7586909B1 (en) * | 2002-03-06 | 2009-09-08 | Agere Systems Inc. | Striping algorithm for switching fabric |
| JP3898535B2 (en) * | 2002-03-14 | 2007-03-28 | 株式会社日立製作所 | Data transfer device |
| US7142555B2 (en) * | 2002-03-22 | 2006-11-28 | Mindspeed Technologies, Inc. | Method and apparatus for switching data using parallel switching elements |
| GB0215505D0 (en) * | 2002-07-04 | 2002-08-14 | Univ Cambridge Tech | Packet routing |
| US20040008674A1 (en) * | 2002-07-08 | 2004-01-15 | Michel Dubois | Digital cross connect switch matrix mapping method and system |
| US7307948B2 (en) * | 2002-10-21 | 2007-12-11 | Emulex Design & Manufacturing Corporation | System with multiple path fail over, fail back and load balancing |
| US20050152305A1 (en) * | 2002-11-25 | 2005-07-14 | Fujitsu Limited | Apparatus, method, and medium for self-organizing multi-hop wireless access networks |
| US7020087B2 (en) * | 2003-01-13 | 2006-03-28 | Motorola, Inc. | Segmented and distributed path optimization in a communication network |
| US6940863B2 (en) * | 2003-01-13 | 2005-09-06 | The Regents Of The University Of California | Edge router for optical label switched network |
| US7596135B1 (en) * | 2003-05-23 | 2009-09-29 | Cisco Technology, Inc. | Method and apparatus for mixed-cast routing through a Clos-like network |
| JP2004350078A (en) | 2003-05-23 | 2004-12-09 | Fujitsu Ltd | Line distribution transmission system |
| US7894343B2 (en) * | 2003-06-19 | 2011-02-22 | Polytechnic University | Packet sequence maintenance with load balancing, and head-of-line blocking avoidance in a switch |
| ITMI20031309A1 (en) * | 2003-06-26 | 2004-12-27 | Marconi Comm Spa | SWITCHING NETWORK. |
| US20040264448A1 (en) * | 2003-06-30 | 2004-12-30 | Wise Jeffrey L | Cross-coupled bi-delta network |
| US20050050243A1 (en) * | 2003-08-29 | 2005-03-03 | Clark Stacey A. | Modified core-edge topology for a fibre channel network |
| US7424010B2 (en) * | 2003-09-06 | 2008-09-09 | Teak Technologies, Inc. | Strictly nonblocking multicast multi-split linear-time multi-stage networks |
| US7751416B2 (en) | 2003-09-18 | 2010-07-06 | Cisco Technology, Inc. | Virtual network device |
| US7801122B2 (en) * | 2003-09-25 | 2010-09-21 | Fujitsu Limited | Method and apparatus for extending synchronous optical networks |
| CN100452886C (en) * | 2003-09-27 | 2009-01-14 | 华为技术有限公司 | Method and device of realizing synchronous switchover of CLDS crosslink matrix |
| US20050111465A1 (en) * | 2003-11-25 | 2005-05-26 | Stewart Mark Andrew W. | Infiniband switch operating in a clos network |
| ATE363796T1 (en) * | 2003-12-19 | 2007-06-15 | Alcatel Lucent | METHOD FOR TRANSMITTING A TIME MULTIPLEX FRAME OVER AN MPLS NETWORK |
| US20050220096A1 (en) * | 2004-04-06 | 2005-10-06 | Robert Friskney | Traffic engineering in frame-based carrier networks |
| EP1596612B1 (en) * | 2004-05-14 | 2006-07-05 | Alcatel | Network element with multistage lower order switching matrix |
| US8139475B2 (en) * | 2004-07-29 | 2012-03-20 | Telecom Italia S.P.A. | Method and system for fault and performance recovery in communication networks, related network and computer program product therefor |
| US20060090136A1 (en) | 2004-10-01 | 2006-04-27 | Microsoft Corporation | Methods and apparatus for implementing a virtualized computer system |
| US7715429B2 (en) * | 2004-12-06 | 2010-05-11 | Hewlett-Packard Development Company, L.P. | Interconnect system for supply chain management of virtual private network services |
| US7512063B2 (en) * | 2004-12-14 | 2009-03-31 | Cisco Technology, Inc. | Border router protection with backup tunnel stitching in a computer network |
| WO2006063459A1 (en) * | 2004-12-17 | 2006-06-22 | Onechip Photonics Inc. | Compact load balanced switching structures for packet based communication networks |
| US7978708B2 (en) * | 2004-12-29 | 2011-07-12 | Cisco Technology, Inc. | Automatic route tagging of BGP next-hop routes in IGP |
| US7436838B2 (en) * | 2004-12-29 | 2008-10-14 | Cisco Technology, Inc. | Automatic prioritization of BGP next-hop in IGP |
| CA2595788C (en) | 2005-02-04 | 2013-06-25 | Level 3 Communications, Inc. | Ethernet-based systems and methods for improved network routing |
| US8064467B2 (en) * | 2005-02-04 | 2011-11-22 | Level 3 Communications, Llc | Systems and methods for network routing in a multiple backbone network architecture |
| US7814227B2 (en) * | 2005-03-04 | 2010-10-12 | Cisco Technology, Inc. | Computation of a shortest inter-domain TE-LSP across a set of autonomous systems |
| JP2006262417A (en) * | 2005-03-18 | 2006-09-28 | Fujitsu Ltd | Communication speed control method and apparatus therefor |
| US7630392B2 (en) * | 2005-05-31 | 2009-12-08 | Cisco Technology, Inc. | Multi-homing using controlled route leakage at a backup service provider |
| US9426092B2 (en) * | 2006-02-03 | 2016-08-23 | Level 3 Communications Llc | System and method for switching traffic through a network |
-
2006
- 2006-11-30 US US11/565,563 patent/US8064467B2/en active Active
-
2007
- 2007-02-05 EP EP12177337.8A patent/EP2515490A3/en not_active Withdrawn
- 2007-02-05 EP EP07710455.2A patent/EP2087664B1/en active Active
- 2007-02-05 CN CN2007800251934A patent/CN101485161B/en not_active Expired - Fee Related
- 2007-02-05 WO PCT/US2007/061629 patent/WO2008066936A1/en active Application Filing
- 2007-02-05 CA CA002657111A patent/CA2657111A1/en not_active Abandoned
- 2007-11-29 CN CN2007800250931A patent/CN101485156B/en not_active Expired - Fee Related
-
2009
- 2009-02-06 US US12/367,147 patent/US8259713B2/en active Active
-
2010
- 2010-01-29 HK HK10101007.7A patent/HK1134973A1/en not_active IP Right Cessation
-
2012
- 2012-08-31 US US13/601,806 patent/US8995451B2/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| WO2008066936A1 (en) | 2008-06-05 |
| US20090141632A1 (en) | 2009-06-04 |
| CN101485156B (en) | 2013-09-11 |
| EP2087664B1 (en) | 2013-05-15 |
| US20120327946A1 (en) | 2012-12-27 |
| EP2515490A2 (en) | 2012-10-24 |
| CN101485156A (en) | 2009-07-15 |
| EP2087664A4 (en) | 2010-04-28 |
| CA2657111A1 (en) | 2008-06-05 |
| US8259713B2 (en) | 2012-09-04 |
| CN101485161A (en) | 2009-07-15 |
| EP2087664A1 (en) | 2009-08-12 |
| US8064467B2 (en) | 2011-11-22 |
| HK1134973A1 (en) | 2010-05-20 |
| US8995451B2 (en) | 2015-03-31 |
| US20070086429A1 (en) | 2007-04-19 |
| EP2515490A3 (en) | 2013-07-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101485161B (en) | Systems and methods for network routing in a multiple backbone network architecture | |
| JP4966206B2 (en) | Ethernet-based system and method for improving network routing | |
| JP4357537B2 (en) | Distribution route control device | |
| TW202034737A (en) | Routing optimizations in a network computing environment | |
| US9025615B2 (en) | Apparatus and methods for establishing virtual private networks in a broadband network | |
| US7969890B2 (en) | Methods, systems, and computer program products for load balanced and symmetric path computations for VoIP traffic engineering | |
| US20100124225A1 (en) | Service Instance Applied to MPLS Networks | |
| CN106063195A (en) | Control device discovery in networks having separate control and forwarding devices | |
| CN101155137A (en) | Method for confirming routing path and its confirming unit | |
| CN102185772B (en) | Method for routing data centre network system | |
| CN101350773A (en) | Mobile packet network architecture as well as access method for equalizing load of a plurality of firewalls | |
| US8611357B2 (en) | MPLS virtual private network using multiple network cores | |
| CN102439919B (en) | Method, device and system for building lable switching path | |
| CN105009602A (en) | Passive connectivity optical module | |
| WO2012051888A1 (en) | Method and system for realizing cross-node aggregated links in a packet switching network | |
| JP4580353B2 (en) | MPLS transfer method, MPLS router, and area border router |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C53 | Correction of patent for invention or patent application | ||
| CB02 | Change of applicant information |
Address after: American Colorado Applicant after: Level 3 Communications LLC Address before: American Colorado Applicant before: Level 3 Communications Inc. |
|
| COR | Change of bibliographic data |
Free format text: CORRECT: APPLICANT; FROM: LEVEL 3 COMMUNICATIONS LLC TO: LEVEL 3 COMMUNICATIONS LLC |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130612 Termination date: 20200205 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |