Routing Control at Internet Exchange Points
By processing control information and routing information in the server of the IXP network, generating and sending routing information, the accuracy of routing information management and exchange in the IXP network is solved, the accurate exchange and filtering of routing information is realized, and the network traffic is improved Management efficiency and consistency.
Patent Information
- Application Number
- CN202010456053.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2015-12-16
- Filing Date
- 2015-12-17
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2035-12-17
AI Technical Summary
In Internet Switching Point (IXP) networks, it is difficult for the prior art to effectively manage and exchange routing information, which makes it difficult to ensure the accuracy and consistency of routing information, affecting the normal exchange of network traffic.
By receiving and processing control information and routing information in the server of the IXP network, generating and sending corresponding routing information, ensuring the accurate transmission and filtering of routing information, using outbound routing filtering (ORF) entries and border gateway protocol (BGP) messages Exchange and filter routing information.
It realizes accurate exchange and filtering of routing information in the IXP network, improves network traffic management efficiency and consistency, ensures that data packets can be correctly routed to the destination, and improves network reliability and performance.
Smart Images

Figure CN111786889B_ABST
Abstract
Description
[0001] Related Applications Cross-Application
[0002] This application claims the benefit of priority to U.S. non-provisional patent application No. 14 / 971,974, filed by Lin Han on December 16, 2015, entitled “Route Control for Internet Exchange Point,” and U.S. provisional patent application No. 62 / 093,150, filed by Lin Han on December 17, 2014, entitled “Outbound Route Filtering for Internet Exchange Point,” the entire contents of which are incorporated herein by reference. Background Art
[0003] An Internet exchange point (IXP) is a physical infrastructure used by network providers to connect their networks and exchange traffic. Network providers that exchange traffic at an IXP are called IXP members. Some examples of network providers may include Internet service providers (ISPs) and enterprises. Each provider network may be referred to as an autonomous system (AS), which operates under a single management entity with a well-defined routing policy. AS may have the meaning given in RFC4271. An IXP may be referred to as an IXP network, which may connect the routers of multiple IXP members together for routing information exchange. An IXP network may operate in layer 2 (L2) or layer 3 (L3) of the open system interconnection (OSI) model. The border gateway protocol (BGP) described in Request for Comment (RFC) 4271 is incorporated into this text by introduction and may be used to enable IXP members to exchange routing and reachability information. When IXP members agree to exchange traffic in the IXP network, IXP members are also referred to as peer members. Summary of the invention
[0004] In one embodiment, the present invention includes a method implemented in a server of an IXP network, the method comprising: receiving first control information in a first message from a first IXP member via the IXP network, wherein the first control information includes an identifier of a second IXP member; obtaining first routing information from the first IXP member via the IXP network; generating second routing information based on the first control information and the first routing information; and sending the second routing information to the second IXP member.
[0005] In one aspect of the embodiment, the second routing information is the same as the first routing information.
[0006] In one aspect of the embodiment, the control information includes an IP prefix associated with the first IXP member.
[0007] In one aspect of the implementation, the server generating the second routing information based on the first control information and the first routing information includes: determining a part of the first routing information as the second routing information.
[0008] In one aspect of the embodiment, the method further includes: receiving second control information in a second message from a third IXP member; obtaining third routing information from the third IXP member; determining an IP prefix associated with the first IXP member and the third IXP member; calculating a first route to the IP prefix and a second route to the IP prefix based on the first routing information and the third routing information, the first route including a next hop associated with the first IXP member, and the second route including a next hop associated with the third IXP member; determining whether to send the first route to the second IXP member based on the first control information; when it is determined not to send the first route to the second IXP member, determining whether to send the second route to the second IXP member based on the second control information; and when it is determined to send the second route to the second IXP member, sending the second route to the second IXP member.
[0009] In one aspect of the embodiment, the first control information includes an identifier of a fourth IXP member.
[0010] In one aspect of the implementation manner, the server generating the second routing information based on the first control information and the first routing information includes: generating fourth routing information for the fourth IXP member.
[0011] In one aspect of the embodiment, the method includes sending the fourth routing information to the fourth IXP member.
[0012] In one aspect of the embodiment, the first control information is stored in an outbound route filtering (ORF) entry.
[0013] In one aspect of the implementation, the first routing information includes: destination address information, next hop and autonomous system (Autonomous System, AS) path information.
[0014] In another embodiment, the present invention includes a network element (NE), the network element including: a memory storage including computer executable instructions and a processor coupled to the memory storage. The processor is configured to execute the instructions to: receive first control information in a first message from a first IXP member through an IXP network, wherein the first control information includes an identifier of a second IXP member; obtain first routing information from the first IXP member through the IXP network; generate second routing information based on the first control information and the first routing information; and send the second routing information to the second IXP member.
[0015] In the implementation manner, the second routing information is the same as the first routing information.
[0016] In the embodiment, the control information includes an IP prefix associated with the first IXP member.
[0017] In the embodiment, the second routing information is a part of the first routing information.
[0018] In the embodiment, the processor is configured to execute the instructions to: receive second control information in a second message from a third IXP member; obtain third routing information from the third IXP member; determine an IP prefix associated with the first IXP member and the third IXP member; calculate a first route to the IP prefix and a second route to the IP prefix based on the first routing information and the third routing information, wherein the first route has a next hop associated with the first IXP member and the second route has a next hop associated with the third IXP member; determine whether to send the first route to the second IXP member based on the first control information; when it is determined not to send the first route to the second IXP member, determine whether to send the second route to the second IXP member based on the second control information; and when it is determined to send the second route to the second IXP member, send the second route to the second IXP member.
[0019] In the implementation manner, the first control information includes an identifier of a fourth IXP member.
[0020] In the embodiment, the processor is configured to execute the instructions to: generate fourth routing information for the fourth IXP member.
[0021] In the implementation manner, the processor is further configured to execute the instruction to: send the fourth routing information to the fourth IXP member.
[0022] In the embodiment, the first control information is stored in an outbound route filtering (ORF) entry.
[0023] In another embodiment, the present invention includes a non-transitory computer-readable medium storing computer-readable instructions for causing a processor to: receive first control information in a first message from a first IXP member via an IXP network, wherein the first control information includes an identification of a second IXP member; obtain first routing information from the first IXP member via the IXP network; generate second routing information based on the first control information and the first routing information; and send the second routing information to the second IXP member.
[0024] These and other features will become more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] For a more thorough understanding of the present invention, reference is now made to the following brief description taken in conjunction with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.
[0026] Figure 1 FIG. 1 is a schematic diagram of a network according to an embodiment of the present invention.
[0027] Figure 2 The figure is a flow chart of a method for sending routing information according to an embodiment of the present invention.
[0028] Figure 3 FIG. 4 is a schematic diagram of an AS-based IXP ORF entry according to an embodiment of the present invention.
[0029] Figure 4 FIG. 4 is a schematic diagram of an IXP ORF entry based on an AS prefix according to an embodiment of the present invention.
[0030] Figure 5 The figure is a flow chart of a method for sending routing information according to an embodiment of the present invention.
[0031] Figure 6 is a schematic diagram of a NE according to an embodiment of the present invention. DETAILED DESCRIPTION
[0032] First, it should be understood that although illustrative implementations of one or more embodiments are provided below, the disclosed systems and / or methods may be implemented using any number of techniques, whether currently known or in existence. The present invention should in no way be limited to the illustrative implementations, drawings, and techniques described below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.
[0033] Figure 1 FIG. 1 is a schematic diagram illustrating a network 100 according to an embodiment of the present invention. The network 100 includes an IXP network 110, an AS 120, and two servers 130 and 140, wherein the AS 120 and the two servers 130 and 140 are outside the IXP network 110. The IXP network 110 includes an AS 111, an AS 112, an AS 113, an AS 114, an AS 115, and an AS 116. The AS 111 includes the server 101. Figure 1 As shown, AS 112, AS 113, AS 114, AS 115, and AS 116 of IXP network 110 can be coupled together through server 101 in AS 111 to exchange routing information. These ASs do not need to be fully meshed to exchange routing information. AS 112, AS 113, AS 114, AS 115, and AS 116 can be respectively referred to as IXP member 112, IXP member 113, IXP member 114, IXP member 115, and IXP member 116. Server 101 and AS 111 are not IXP members. Since server 101 is used to couple to IXP members in IXP network 110 for traffic exchange, it is also referred to as IXP server 101. Servers 130 and 140 are each assigned one or more prefixes (e.g., prefixes 1310 and 1410). Each prefix can cover one or more IP addresses associated with Internet services such as websites. For example, the one or more IP addresses may include IP addresses of websites such as Google, Netflix, or other similar service and / or content providers. Servers 130 and 140 may be deployed by service and / or content providers or by some Internet operators such as AT&T and Verizon. Since a prefix includes at least one IP address, it may also be referred to as an IP prefix.
[0034] The IXP network 110 may be used to provide a backbone hub for different IXP members to exchange L2 or L3 data traffic. The exchange of data traffic between IXP members may be referred to as peering. Each IXP member in the IXP network 110 may be coupled to any other IXP member in the IXP network 110. In one embodiment, the IXP network 110 may be an Ethernet local area network (LAN) having a plurality of Ethernet switches. In another embodiment, the IXP network 110 may be an IP LAN having a plurality of L3 switches and routers. Each IXP member in the IXP network 110 may have a plurality of edge devices, such as edge switches or routers. The IXP members in the IXP network 110 may be coupled to other IXP members in the IXP network 110 and / or other ASs or servers outside the IXP network 110 through their associated edge devices.
[0035] In one embodiment, the IXP member 115 may send one or more messages 154 and one message 151 to the server 101. The one or more messages 154 include routing information 153, and the routing information 153 includes destination address information 153A, next hop 153B, and may also include AS path information 153C. The destination address information 153A may include one or more prefixes (e.g., prefix 131 and / or prefix 141), and the next hop 153B may include an IP address of a network node in the IXP member 115. In this case, the destination address information 153A and the next hop 153B indicate that if a data packet needs to be routed to an IP address covered by the destination address information 153A (e.g., prefix 131 and / or prefix 141), the data packet may be routed to the network node determined by the next hop 153B. Then, the network node determined by the next hop 153B routes the data packet to its destination. When a network node receives the destination address information 153A and the next hop 153B and needs a data packet whose destination is covered by the destination address information 153A, the network node will send the data packet to the network node determined by the next hop 153B. The AS path information 153C includes one or more AS paths, each of which corresponds to a prefix in the destination address information 153A. For example, when the destination address information 153A includes prefixes 131 and 141, the AS path information 153C includes an AS path 161 from AS 115 to the server 130 and an AS path 162 from AS 115 to the server 140. The AS path 161 corresponds to the prefix 131, and the AS path 162 corresponds to the prefix 141. The message 151 may include an IXP ORF entry 152, and the IXP ORF entry 152 includes control information 155. The control information 155 instructs the server 101 to generate routing information 156.
[0036] The routing information 156 may have the same structure as the routing information 153 or a part of the structure of the routing information 153. In the routing information 156, the next hop 156B may be the same as the destination address information 153A and the next hop 153B. According to the control information 155, the destination address information 156A may be the same as the destination address information 153A (e.g., prefixes 131 and 141) or a part of the destination address information 153A (e.g., prefixes 131 and prefix 141). When the routing information 153 includes the AS path information 153C, the routing information 156 may or may not include the AS path information 156C. The AS path information 156C may include the AS path corresponding to the destination address information 156A. For example, when the destination address information 156A includes the prefix 131, the AS path information 156C includes the AS path 161, and when the destination address information 156A includes the prefixes 131 and 141, the AS path information 156C includes the AS path 161 and the AS path 162.
[0037] The control information 155 may instruct the server 101 to generate the same routing information 156 for multiple IXP members (e.g., AS 112 and AS 113). The control information 155 may also generate different routing information for different IXP members. For example, the server 101 generates routing information 156 for IXP member 112 and generates routing information different from routing information 156 for IXP member 113. The routing information of IXP member 113 may have the same or similar structure as routing information 156. After generating routing information corresponding to one or more IXP members, the server 101 sends the corresponding routing information to each of the one or more IXP members. In one example, the destination address information in the routing information 156 may include prefix 131, and the destination address information in the routing information generated for IXP member 113 may include prefix 141. The next hop in the routing information generated for IXP member 113 is the same as the next hop 156B in the routing information 156.
[0038] Figure 2 The present invention is a flowchart illustrating a method for sending routing information according to an embodiment of the present invention.
[0039] In operation 202, the server receives control information from a first IXP member in the IXP network, the control information including an identifier of a second IXP member in the IXP network. Figure 1As shown, control information 155 in message 151 may be received from IXP member 115 via IXP network 110, wherein control information 155 includes an identification of IXP member 112. Message 151 may be a BGP ROUTE-REFRESH message defined in RFC 5291. Control information 155 may be carried in a new or extended IXP ORF entry 152 in message 151.
[0040] In operation 204, the server receives first routing information from an IXP member in the IXP network. In one example, the server 101 obtains routing information 153 from the IXP member 115 through the IXP network 110. The first routing information is associated with the IXP member. For example, the routing information 153 includes a prefix, and the routing information 153 is used to indicate that the IXP member 115 can route the data packet to the destination determined by the prefix carried in the routing information 153.
[0041] In some embodiments, the server 101 may receive the routing information 153 before or at the same time as receiving the control information 155. The IXP member 115 may send one or more BGP UPDATE messages 154 defined in RFC 4271 to the server 101. Based on the BGP UPDATE message 154, the server 101 may obtain the routing information 153, which includes the destination address information 153A, the next hop 153B, and the AS path information 153C. The destination address information 153A may be one or more IP prefixes associated with the IXP member 115, for example Figure 1 131 and 132 are shown. When an IP prefix (e.g., prefix 131) is associated with an IXP member (e.g., IXP member 115), the IXP member can send a data packet to its destination (e.g., server 130), where the destination address of the data packet is covered by the prefix (e.g., prefix 131). Next hop 153B may be an IP address assigned to IXP member 115, such as an IP address assigned to a router in IXP member 115. AS path information 153C may include one or more AS paths that couple IXP member 115 with one or more external network nodes (e.g., server 130 and server 140) assigned with destination address information (e.g., prefix 131 or prefix 132). For example, AS path 161 may start from AS 115, pass through AS 120, and end at server 130; AS path 162 may start from AS 115, pass through AS 120, and end at server 140.
[0042] In operation 206, the server in the IXP network generates second routing information based on the received control information and the first routing information. For example, the server 101 may generate the second routing information 156 based on the received control information 155 and the first routing information 153. When the control information 155 is AS-based control information, the second routing information 156 may be the same as the first routing information 153. When the control information 155 is AS-based control information, the IXP ORF entry 152 may be as follows: Figure 3 When the control information 155 is control information based on an AS prefix, the routing information 156 may be part of the first routing information 153. In one embodiment, in the first routing information 153, the destination address information 153A includes prefixes 131 and 141, wherein prefix 131 is a prefix assigned to the server 130, and prefix 141 is a prefix assigned to the server 140. The next hop 153B includes the IP address of the IXP member 115, and the AS path information 153C includes two paths: path 161 and path 162, wherein path 161 starts from the IXP member 115, passes through the AS 120, and ends at the server 130, and path 162 starts from the IXP member 115, passes through the AS 120, and ends at the server 140. In one example, the control information 155 includes one of the two prefixes 131 and 141, and the identifier of the IXP member 112. Thus, the second routing information 156 may include the prefix 131 in the control information 155 as the destination address information 156A, include the next hop 153B of the first routing information 153 as the next hop 156B, and include the AS path 161 associated with the prefix 131 (e.g., IXP member 115 to AS 120 to server 130) as the AS path information 156C. In some embodiments, the second routing information 156 may not include the AS path information 156C. When the control information 155 is the control information based on the AS prefix, the control information 155 may be shown in the form of the IXP ORF entry 152, such as Figure 4 shown.
[0043] In operation 208, the server sends the second routing information to the second IXP member. In one embodiment, the server 101 sends the second routing information 156 to the IXP member 112. Through the second routing information 156, the IXP member 112 can send a data packet with a destination address determined by the destination address information 156A (e.g., prefix 131) to the IXP member 115, and the IXP member 115 will further route the data packet to the server 130. A method for sending routing information can publish the routing information.
[0044] As described above, the IXP member 115 may send part or all of the first routing information to IXP members designated by the IXP member 115 instead of publishing the routing information of the IXP member 115 to all IXP members in the IXP network 110.
[0045] Figure 3 FIG. 1 is a schematic diagram of an AS-based IXP ORF entry 300 according to an embodiment of the present invention. In one embodiment, the AS-based control information 155 may be used in the form of an ORF entry 300. Figure 3 As shown, ORF entry 300 includes a subtype field 310, a length field 320, an action field 330, an AS type field 340, a reserved field 350, and a peer AS list field 360. Subtype field 310 may be one octet long and may be set to a value of zero. Length field 320 may be two octets long and may be used to store the length of ORF entry 300. Action field 330 may be one bit long and is used to instruct IXP server 101 to perform an appropriate action. The appropriate action may include sending second routing information 156 to each IXP member determined by peer AS list field 360. Since ORF entry 300 is used to send routing information at the AS level, ORF entry 300 does not include a filtering condition for determining second routing information 156 based on first routing information 153. Therefore, when AS-based control information is applied to generate the second routing information, the second routing information 156 may be the same as the first routing information 153. AS type field 340 may be about one bit long. For example, the AS type field 340 is set to a value of zero to indicate a two-octet AS number format and a value of one to indicate a four-octet AS number format. The reserved field 350 may be approximately 6 bits long and is reserved for future use. The peer AS list field 360 is a variable length field used to store one or more AS numbers to which the server 101 can send routing information (e.g., the second routing information 156).
[0046] When a server (e.g., server 101) receives a message, such as a ROUTE-REFRESH message, carrying an ORF entry 300, wherein the ORF entry 300 has an action field 330 from an IXP member 115, the action field 330 in the ORF entry 300 is set to a value that instructs the server 101 to send the second routing information 156 that is the same as the first routing information 153 to each IXP member identified by the peer AS list field 360, such as the IXP members 112, 113, and 114. In one example, the server 101 receives a message, such as a ROUTE-REFRESH message, carrying an ORF entry 300 from the IXP member 115, wherein the action field 330 is set to zero, and the peer AS list field 360 includes the identities of the IXP members 112 and 113. Based on the message, the server 101 sends the first routing information 153 obtained from the IXP member 115 to the IXP members 112 and 113. Since the peer AS list field 360 does not include the IXP members 114 and 116 , the server 101 does not send the first routing information 153 to the IXP members 114 and 116 .
[0047] Figure 4 FIG. 4 is a schematic diagram of an IXP ORF entry 400 based on an AS prefix according to an embodiment of the present invention. In one embodiment, the ORF entry 400 is used to carry control information based on the AS prefix. Figure 3 As discussed, entry 300 may be used to carry messages such as a ROUTE-REFRESH message as described in RFC 2918. An IXP member (eg, IXP member 115) may employ ORF entry 400 to send routing information at a finer granularity level than the AS level.
[0048] ORF entry 400 includes a subtype field 410, a length field 420, an action field 430, an AS type field 440, a reserved field 450, and one or more address groups 460. The subtype field 410, the length field 420, the AS type field 440, and the reserved field 450 of ORF entry 400 are respectively Figure 3 The subtype field 310, length field 320, AS type field 340, and reserved field 350 of the entry 300 are similar or identical. The action field 430 of the ORF entry 400 may be used to instruct the IXP server (e.g., server 101) to filter routing information (e.g., first routing information 153) for one or more IXP members in the IXP network, respectively, and then send each filtered routing information to its corresponding IXP member.
[0049] Each address group 460 (e.g., 460A) includes an AS number field 461 (e.g., 461A), a length field 462 (e.g., 462A), and one or more ORF address fields 463 (e.g., 463A1 and 463A2). The number field 461 (e.g., 461A) includes a variable length depending on the AS type field 440. The AS number field 461 (e.g., 461A) determines the AS that can be used by the server peer to send routing information. The length field 462 (e.g., 462A) can be two octets long and can be used to indicate the length of the ORF address field 463 (e.g., 463A1 and 463A2). Each ORF address field 463 (e.g., 463A1 or 463A2) is a variable length field and can be encoded according to RFC 5292. Since the variable length field can be called an entry, each ORF address field can be called an ORF address entry. Each ORF address field 463 (eg, 463A1 or 463A2) may include an IP prefix indicating a group of IP addresses or only one IP address.
[0050] In one embodiment, ORF entry 400 has two address groups: address group 460A and address group 460B. Address group 460A includes peer AS number 461A, length field 462A, and two ORF address fields 463A1 and 463A2. Peer AS number 461A includes the AS number of IXP member 112. Length field 462A indicates the length of ORF address field 463A, wherein ORF address field 463A includes ORF address fields 463A1 and 463A2. ORF address field 463A1 includes prefix 131, and ORF address field 463A2 includes prefix 141. Address group 460B includes peer AS number 461B, length field 462B, and one ORF address field 463B1. Peer AS number 461B includes the AS number of IXP member 113. Length field 462B indicates the length of ORF address field 463B1. The ORF address field 463B1 includes the prefix 131.
[0051] In one embodiment, after receiving the ORF entry 400 with the address group 460A and the address group 460B, the server 101 may send first filtering routing information to the IXP member 112 based on the AS number of the IXP 112 included in the peer AS number 461A. The first filtering routing information may be the same as the first routing information 153. The server 101 may send second filtering routing information to the IXP member 113 based on the AS number of the IXP member 113 included in the peer AS number 461B. The destination address information in the second filtering routing information includes the prefix 131, but does not include the prefix 141. The next hop in the second filtering routing information is the same as the next hop in the routing information 153. The AS path information in the filtering routing information may be used to indicate a path starting from the IXP member 115, passing through the AS 120, and ending at the server 130.
[0052] Figure 5 FIG. 5 is a flowchart of a method 500 for sending routing information based on received control information according to an embodiment of the present invention. In one embodiment, the method 500 is performed at a server (e.g., Figure 1 The server may be implemented in a server 101 in the IXP network 101. The server may receive routing information associated with each IXP member (e.g., IXP members 112 to 116 of the IXP network 101). In one example, routing information associated with one IXP member may be received via a BGP UPDATE message as described in RFC 4271. The routing information has destination address information, which includes one or more IP prefixes.
[0053] When a prefix is associated with an IXP member, the IXP member may route a data packet whose destination address is covered by the prefix to a destination determined by the destination address. The server may also receive messages from the IXP members, such as a ROUTE-REFRESH message. Each message carries an ORF entry (e.g., ORF entry 300 or ORF entry 400) including control information. In one embodiment, method 500 begins after a server (e.g., server 101) receives control information and obtains routing information from two or more IXP members (e.g., IXP members 114, 115, and 116).
[0054] In operation 501, a server (e.g., server 101) in an IXP network (e.g., IXP network 110) selects a prefix (e.g., prefix 131). The prefix is associated with two or more IXP members in the IXP network. When a prefix is associated with an IXP member, the IXP member can route a data packet to the prefix instead of routing the data packet to the default gateway of the IXP member. For example, when prefix 131 is associated with IXP members 114, 115, and 116, each of IXP members 114, 115, and 116 can route a data packet to prefix 131 to server 130. In operation 502, the server (e.g., server 101) calculates a plurality of preferred BGP paths to the selected prefix (e.g., prefix 131). The path to the prefix may refer to a path to a network node to which the prefix is assigned. For example, as in Figure 1 As shown, the path to prefix 131 is the path to server 130. The multiple preferred BGP paths may be referred to as multiple best BGP paths or multiple best paths. The multiple preferred BGP paths may be paths with high priority among multiple potential BGP paths.
[0055] In one embodiment, IXP member 114 notifies server 101 that IXP member 114 can route the data packet to prefix 131 by sending routing information to server 101. In addition, IXP members 115 and 116 also respectively notify server 101 that they can route the data packet to prefix 131. Then, server 101 calculates three potential paths to prefix 131. The first potential path may be from server 101 to IXP member 115, the second potential path may be from server 101 to IXP member 114, and the third potential path may be from server 101 to IXP 116. Server 101 may determine that the first path has the highest priority among the three potential BGP paths. Therefore, the first path is determined to be the preferred BGP path. Server 101 may take the first path from the three potential BGP paths to obtain two potential paths. In addition, server 101 may determine that the second path has the highest priority among the two potential BGP paths, wherein the second path includes the second and third paths. Therefore, the second path is determined to be another preferred BGP path. Although the first path and the second path are both preferred BGP paths, the first path has a higher priority than the second path. In one embodiment, the preferred BGP path may also be randomly selected from a plurality of potential BGP paths. In another embodiment, all potential paths may be determined as preferred BGP paths.
[0056] In operation 503, a preferred BGP path (eg, a first path) having the highest priority is selected from a pool including all preferred BGP paths.
[0057] In operation 504, a first IXP member (e.g., IXM member 112) is selected. The selected IXP member is not on the preferred BGP path selected in operation 503. For example, when the first path is selected in operation 503, the first IXP member selected in operation 504 may be IXM member 112 or 113, but may not be IXM member 115.
[0058] In operation 505, the server (e.g., server 101) determines whether there is first control information, the first control information being used to control sending routing information obtained from a source IXP member to a first IXP member (e.g., IXP member 112). The source IXP member (e.g., IXP member 115) is on the path selected in operation 503. In one embodiment, when the first IXP member is IXP member 112 and the source IXP member is IXP member 115, the first control information may include a source IXP number and a destination IXP number, wherein the source IXP number is the source IXP member number and the destination IXP number is the first IXP member number.
[0059] When the server has the first control information, the method proceeds to 506 ; when the IXP server does not have the first control information, the method proceeds to 508 .
[0060] In operation 506, the first control information is applied to control the transmission of routing information of the prefix selected in operation 501 to the first IXP member. Although the first control information may be obtained by a server (e.g., server 101) before operation 501, the IXP server may not apply the first control information to control the transmission of routing information of the prefix selected in operation 501 to the first IXP member.
[0061] In operation 507, based on the applied first control information, the IXP server determines whether first routing information of the prefix (e.g., prefix 131) selected in operation 501 can be sent to the selected IXP member. The prefix (e.g., prefix 131) selected as the destination address in operation 501 may include the first routing information of the prefix (e.g., prefix 131) selected in operation 501, and further include a next hop, wherein the next hop is an IP address assigned to a router in the IXP member, wherein the IXP member is on the preferred BGP path selected in operation 503. When the applied first control information allows the first routing information to be sent to the IXP member selected in operation 504, the method proceeds to operation 508; otherwise, the method proceeds to operation 507.
[0062] In operation 508, the first routing information is sent to the IXP member (e.g., IXP member 112) selected in operation 504. In this way, the IXP member (e.g., IXP member 112) selected in operation 504 obtains the first routing information. Therefore, the IXP member (e.g., IXP member 112) selected in operation 504 can route the data packet with the IP address determined by the prefix (e.g., prefix 131) selected in operation 501 to the IXP member (e.g., IXP member 115) on the preferred BGP path selected in operation 503. Then, the IXP member (e.g., IXP member 115) on the preferred BGP path selected in operation 503 can further route the data packet to its destination.
[0063] In operation 509, the server (eg, server 101) determines whether the first routing information needs to be sent to the next IXP member. When the next IXP member exists in the IXP network, method 500 returns to operation 504; when the next IXP member does not exist in the IXP network, method 500 ends.
[0064] In operation 571, the server (eg, server 101) determines whether it is necessary to find the next preferred BGP path to the prefix. When it is necessary to find the next preferred BGP path to the prefix, method 500 returns to operation 503; otherwise, method 500 proceeds to operation 572.
[0065] In operation 572, the server (eg, server 101) determines whether it is necessary to select a next prefix. When it is necessary to select a next prefix, method 500 proceeds to operation 501; otherwise, method 500 ends.
[0066] Figure 6 is a schematic diagram of NE 600 according to an embodiment of the present invention. NE 600 may act as a network switch or border router, such as switches and routers in IXP members 112 to 116, or act as a server in IXP network 110, such as server 101. NE 600 may be used to implement and / or support the routing information control scheme and IXP ORF scheme described herein. NE 600 may be implemented in a single node, or the functions of NE 600 may be implemented in multiple nodes. Those skilled in the art will recognize that the term NE encompasses a wide range of devices, and NE 600 is merely an example. NE 600 is for reasons of clarity of description, and is by no means intended to limit the application of the present invention to a particular NE embodiment or a class of NE embodiments. At least some of the features and / or methods described in the present invention may be implemented in a network device or module such as NE 600. For example, the features and / or methods in the present invention may be implemented using hardware, firmware, and / or software installed and running on hardware. As Figure 6As shown, NE 600 may include a transceiver (Tx / Rx) 610, which may be a transmitter, a receiver, or a combination thereof. Respectively, Tx / Rx 610 may be coupled to multiple downstream ports 620 for transmitting and / or receiving frames from other nodes, and Tx / Rx 610 may be coupled to multiple upstream ports 650 for transmitting and / or receiving frames from other nodes. A processor 630 may be coupled to Tx / Rx 610 to process frames and / or determine which nodes to send frames to. Processor 630 may include one or more multi-core processors and / or memory devices 640, which may be used as data storage, buffers, etc. Processor 630 may be implemented as a general-purpose processor or may be part of one or more application specific integrated circuits (ASICs) and / or digital signal processors (DSPs). Processor 630 may include a routing information control module 633, which may execute methods 100 and 500, and / or any other methods discussed herein. In an alternative embodiment, the routing information control module 633 may be implemented as instructions stored in the storage device 640 and executed by the processor 630. The storage device 640 may include a cache for temporarily storing content, such as a random-access memory (RAM). In addition, the storage device 640 may include a long-term memory for storing content for a relatively long time, such as a read-only memory (ROM). For example, the cache and the long-term memory may include dynamic RAM (DRAM), a solid-state drive (SSD), a hard disk, or a combination thereof.
[0067] It is understood that by programming and / or loading executable instructions to the network element 600, at least one of the processor 630 and / or the memory device 640 will be changed, transforming the network element 600 into a machine or device having the novel functions described in the present invention, such as a multi-core forwarding architecture. It is basic to the power engineering and software engineering techniques that the functionality that can be implemented by loading executable software into a computer can be converted into a hardware implementation through well-known design rules. The decision between implementing a concept in software or hardware usually depends on considerations related to the stability of the design and the number of units to be produced, and has nothing to do with any issues involved in translating from the software domain to the hardware domain. Generally, designs that are still subject to frequent changes are preferably implemented in software because it is more expensive to re-modify the hardware implementation than to re-modify the software design. Generally, stable and mass-produced designs are more suitable for implementation in hardware such as ASICs because it is cheaper to run mass production of hardware implementations than software implementations. Generally, a design can be developed and tested in software form, and then transformed into an equivalent hardware implementation in an ASIC (application specific integrated circuit) that hardwires the instructions of the software through well-known design rules. A machine controlled by the new ASIC is a specific machine or device, similarly, a computer programmed and / or loaded with executable instructions can be considered a specific machine or device.
[0068] Although several embodiments have been provided in the present invention, it should be understood that the systems and methods disclosed herein may be embodied in many other specific forms without departing from the spirit or scope of the present invention. The examples of the present invention should be considered illustrative rather than restrictive, and the present invention is not limited to the details given in this text. For example, various elements or components may be combined or merged in another system, or certain features may be omitted or not implemented.
[0069] Although the above describes processes or methods according to some sequential operations, it should be understood that some of the operations described may be performed in different orders. In addition, some operations may be performed in parallel rather than in sequence.
[0070] In addition, without departing from the scope of the present invention, the techniques, systems, subsystems and methods described and illustrated as discrete or separate in the various embodiments may be combined or merged with other systems, modules, techniques or methods. Other items shown or discussed as coupled or directly coupled or communicating with each other may also be coupled or communicated indirectly through an interface, device or intermediate component, either electrically, mechanically or otherwise. Other variations, substitutions and altered examples may be determined by those skilled in the art without departing from the spirit and scope of the present invention.
Claims
1. A method for sending routing information in an Internet exchange point IXP network, characterized in that: include: The server receives first control information and first routing information from a first IXP member through the IXP network, wherein the first control information includes an identifier of a second IXP member, and the IXP network includes: an autonomous system AS; The server generates second routing information based on the first control information and the first routing information; and The server sends the second routing information to the second IXP member based on the identifier of the second IXP member.
2. The method according to claim 1, characterized in that The second routing information is the same as the first routing information.
3. The method according to claim 1, characterized in that: The first control information includes an IP prefix associated with the first IXP member.
4. The method according to claim 3, characterized in that The server generating the second routing information based on the first control information and the first routing information includes: A portion of the first routing information is determined as the second routing information.
5. The method according to claim 1, characterized in that Also includes: receiving second control information from a third IXP member; obtaining third routing information from the third IXP member; determining IP prefixes associated with the first IXP member and the third IXP member; Calculate a first route to the IP prefix and a second route to the IP prefix based on the first routing information and the third routing information, wherein the first route includes a next hop associated with the first IXP member, and the second route includes a next hop associated with the third IXP member; determining whether to send the first route to the second IXP member based on the first control information; When it is determined not to send the first route to the second IXP member, determining whether to send the second route to the second IXP member based on the second control information; as well as When it is determined to send the second route to the second IXP member, the second route is sent to the second IXP member.
6. The method according to claim 1, characterized in that The first control information includes an identifier of a fourth IXP member.
7. The method according to claim 6, characterized in that The server generating the second routing information based on the first control information and the first routing information includes: Generate fourth routing information for a fourth IXP member.
8. The method according to claim 7, characterized in that The method further comprises: The fourth routing information is sent to the fourth IXP member.
9. The method according to claim 1, characterized in that: The first control information is stored in an outbound routing filter (ORF) entry.
10. The method according to claim 1, characterized in that The first routing information includes: destination address information, next hop and autonomous system AS path information.
11. A network node, characterized in that: include: a memory storage device including computer executable instructions; as well as A processor coupled to the memory storage, wherein the processor is configured to execute the instructions to perform the following operations: receiving first control information and first routing information from a first IXP member via an Internet Exchange Point IXP network, wherein the first control information includes an identifier of a second IXP member, the IXP network including: an Autonomous System AS; generating second routing information based on the first control information and the first routing information; and The second routing information is sent to the second IXP member based on the identifier of the second IXP member.
12. The network node according to claim 11, characterized in that: The second routing information is the same as the first routing information.
13. The network node according to claim 11, characterized in that: The first control information includes an IP prefix associated with the first IXP member.
14. The network node according to claim 13, characterized in that: The second routing information is a part of the first routing information.
15. The network node according to claim 11, characterized in that: The processor is configured to execute the instructions to perform the following operations: receiving second control information from a third IXP member; obtaining third routing information from the third IXP member; determining IP prefixes associated with the first IXP member and the third IXP member; Calculating a first route to the IP prefix and a second route to the IP prefix based on the first routing information and the third routing information, wherein the first route has a next hop associated with the first IXP member and the second route has a next hop associated with the third IXP member; determining whether to send the first route to the second IXP member based on the first control information; When it is determined not to send the first route to the second IXP member, determining whether to send the second route to the second IXP member based on the second control information; as well as When it is determined to send the second route to the second IXP member, the second route is sent to the second IXP member.
16. The network node according to claim 11, characterized in that: The first control information includes an identifier of a fourth IXP member.
17. The network node according to claim 16, characterized in that: The processor is configured to execute the instructions to perform the following operations: Generate fourth routing information for the fourth IXP member.
18. The network node according to claim 17, characterized in that: The processor is further configured to execute the instructions to perform the following operations: The fourth routing information is sent to the fourth IXP member.
19. The network node according to claim 11, characterized in that: The first control information is stored in an outbound routing filter (ORF) entry.
20. A non-transitory computer readable medium, characterized in that The computer-readable medium stores instructions, which, when executed on a computer, enable the computer to execute the method according to any one of claims 1 to 10.
Citation Information
Patent Citations
Route Control For Internet Exchange Point
US20160182371A1
Method for determining anticipation peer-to-peer collaborator of Internet service supplier
CN101473605A
Border gateway protocol extended community attribute for layer-2 and layer-3 virtual private networks using 802.1ah-based tunnels
CN103840998A
Internet exchange point routing control methods
CN106576076B
System and method for packet network configuration debugging and database
US20020021675A1
