Route control method, device, system and border gateway protocol peer

The BGP peer-based route control method manages VPN routes by limiting their numbers using ORF filters in route refresh messages, addressing the resource overutilization issue in MPLS VPN cross-domain networks.

JP7583064B2Active Publication Date: 2024-11-13CHINA TELECOM CORP LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2022566011
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-04-30
Filing Date
2021-04-28
Publication Date
2024-11-13
Estimated Expiration
2041-04-28

AI Technical Summary

Technical Problem

In MPLS VPN cross-domain networks, the number of VPN routes can exceed limits, occupying administrative and storage resources and impacting the sending and receiving of VPN routes for other instances, particularly in Option A, B, and C scenarios where ASBR and RR functionalities are limited in controlling VPN route numbers.

Method used

A route control method is implemented using Border Gateway Protocol (BGP) peers to manage VPN routes by determining if the number of routes exceeds a limit, sending instruction information to stop or allow route additions, and utilizing out-of-band route filters (ORF) to manage VPN routes through route refresh messages.

Benefits of technology

The method effectively limits VPN routes, preventing resource overutilization and ensuring smooth operation of VPN instances by controlling route additions and withdrawals, maintaining compatibility with existing technologies.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007583064000003
    Figure 0007583064000003
  • Figure 0007583064000004
    Figure 0007583064000004
  • Figure 0007583064000005
    Figure 0007583064000005
Patent Text Reader

Abstract

The present application relates to the field of communications technology, and more particularly to a route control method, an apparatus, a system, and a Border Gateway Protocol (BGP) peer. The present application relates to a method, a device, a system, and a Border Gateway Protocol (BGP) peer, which can be performed by a first BGP peer, and includes receiving new Virtual Private Network (VPN) route information from a second BGP peer, where the new VPN route information includes the new VPN route and a first VPN instance identifier thereof; after adding the new VPN route, determining, according to the first VPN instance identifier, whether the number of VPN routes corresponding to the first VPN instance identifier reaches or exceeds a limit; and, if the number of VPN routes corresponding to the first VPN instance identifier reaches or exceeds the limit, sending first instruction information to the second BGP peer to instruct the second BGP peer to stop adding the VPN route corresponding to the first VPN instance identifier, where the BGP peer is an internal Border Gateway Protocol (iBGP) peer in a first autonomous system (AS).
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] This application claims priority from Chinese Patent Application No. 202010360605.7, filed on April 30, 2020, the disclosure of which is incorporated herein in its entirety.

[0002] The present disclosure relates to the field of communication technologies, and in particular to a route control method, device, system, and BGP peer. [Background technology]

[0003] MPLS (Multiprotocol Label Switching) VPN (Virtual Private Network) cross-domain network includes implementing as modes Option A, Option B and Option C. In VPN cross-domain network scenario, BGP (Border Gateway Protocol) peers can advertise VPN routes. Summary of the Invention [Problem to be solved by the invention]

[0004] Currently, in the scenario of Option A, when an ASBR (Autonomous System Boundary Router) acts as a BGP peer and receives routes sent by BGP peers (other ASBRs) in other ASes (Autonomous Systems), the corresponding VRF (Virtual Route Forwarding) route table can be searched based on the access link interface, and the number of VPN routes of the VPN instance on the BGP peers of other ASes is limited according to the VRF route table. This prevents a VPN instance from having too many VPN routes, occupying excessive management and storage resources and affecting the sending and receiving of VPN routes of other VPN instances. [Means for solving the problem]

[0005] According to some embodiments of the disclosure of the present application, there is provided a route control method, the route control method being performed by a first Border Gateway Protocol (BGP) peer, the method comprising: receiving additional information of a new Virtual Private Network (VPN) route sent from a second BGP peer, the additional information of the new VPN route comprising the new VPN route and an identifier of a first VPN instance corresponding to the new VPN route; determining whether a number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds a limit value after adding the new VPN route according to the identifier of the first VPN instance; and sending first instruction information to the second BGP peer to instruct the second BGP peer to stop adding VPN routes corresponding to the identifier of the first VPN instance when the number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds the limit value, the first BGP peer being an Interior Border Gateway Protocol (IBGP) peer in a first Autonomous System (AS).

[0006] In some embodiments The second BGP peer is a BGP peer that functions as an external border gateway protocol peer (eBGP) between the first AS and the second AS at the border of the first AS.

[0007] In some embodiments, the identifier of the first VPN instance is a first route identifier (RD), and determining whether the number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds a limit value after adding the new VPN route in response to the identifier of the first VPN instance includes identifying the first RD in the new VPN route; The route target (RT) of the new VPN route In response to the first RD, a first virtual route forwarding (VRF) route table corresponding to the new VPN route is determined, the first RD is removed from the new VPN route, and the new VPN route having the removed first RD is added to the first VPN route table of the new VPN route. RTand determining whether the number of routes entered in the first VRF route table reaches or exceeds the limit value in response to the first VRF route table.

[0008] In some embodiments, the identifier of the first VPN instance is a first route identifier (RD), the first indication information is a first route refresh message, and sending the first indication information to the second BGP peer includes configuring a first out-of-band route filter (ORF) entry in the first route refresh message, setting a value of an action field of the first ORF entry to a first value indicating that a filter state corresponding to the first ORF entry should be added to an out-of-bounds route filter of the second BGP peer, and setting a value of a match field of the first ORF entry to a first value indicating that a filter state corresponding to the first ORF entry should be added to an out-of-bounds route filter of the second BGP peer. addition to a second value indicating that the ORF entry is rejected, and adds the first RD to the type specific portion field of the first ORF entry.

[0009] In some embodiments, the method further comprises: Should be revoked receiving information regarding the withdrawal of a VPN route, Should be revoked The information withdrawing the VPN route is withdrawn. Should The VPN route will be withdrawn Should and an identifier of a second VPN instance corresponding to the VPR route, delete the VPN route to be withdrawn according to the identifier of the second VPN instance, and if the number of VPN routes corresponding to the identifier of the second VPN instance reaches or exceeds the limit value, determine whether the number of VPN routes corresponding to the identifier of the second VPN instance is less than the limit value after deleting the VPN route to be withdrawn, and if the number of VPN routes corresponding to the identifier of the second VPN instance is less than the limit value, send second instruction information to the second BGP peer instructing the second BGP peer to allow the second BGP peer to add a VPN route corresponding to the identifier of the second VPN instance.

[0010] In some embodiments, the identifier of the second VPN instance is a second RD, the second indication information is a second route refresh message, and sending the second indication information to the second BGP peer includes configuring a second ORF entry in the second route refresh message, setting a value of an action field of the second ORF entry to a third value indicating that a configured filter condition corresponding to the second ORF entry should be removed from the out-of-boundary route filter of the second BGP peer, and adding the second RD to a type-specific subfield of the second ORF entry.

[0011] In some embodiments, an Address Family Identifier (AFI) and a Subsequent Address Family Identifier (SAFI) in the first route refresh message are set to the AFI and SAFI values, respectively, of a first Virtual Route Forward (VRF) route table corresponding to the first RD, and a Refresh Time Required field of the first route refresh message is set to a value indicating "immediate." or an ORF type field corresponding to the first ORF entry of the first route refresh message is set to a preset value representing a new ORF type. .

[0012] In some embodiments, the AFI and SAFI fields in the second route refresh message are set to the AFI and SAFI values, respectively, of a second VRF route table corresponding to the second RD, and a refresh time required field of the second route refresh message is set to a value indicating "immediate." or an ORF type field corresponding to the second ORF entry in the second route refresh message is set to a preset value representing a new ORF type. .

[0013] According to yet another embodiment of the present disclosure, there is provided a route control method, the route control method being executed by a second Border Gateway Protocol (BGP) peer, comprising: sending additional information of a new Virtual Private Network (VPN) route to a first BGP peer, the additional information of the new VPN route comprising the new VPN route and an identifier of a first VPN instance corresponding to the new VPN route; receiving first indication information sent from the first BGP peer when the first BGP peer determines that a number of VPN routes corresponding to the identifier of the first VPN instance has reached or exceeded a limit value, the first indication information instructing the second BGP peer to stop adding a VPN route corresponding to the identifier of the first VPN instance; and in response to the first indication information, causing the first BGP peer to stop adding the VPN route corresponding to the identifier of the first VPN instance, the first BGP peer being an Internal Border Gateway Protocol (iBGP) peer.

[0014] In some embodiments, The second BGP peer is a BGP peer that functions as an external border gateway protocol peer (eBGP) between the first AS and the second AS at the border of the first AS.

[0015] In some embodiments, the method further comprises sending the first instruction information to the third BGP peer to instruct the third BGP peer to stop adding the VPN route corresponding to the identifier of the first VPN instance, and sending the first instruction information from the third BGP peer to the fourth BGP peer to instruct the fourth BGP peer to stop adding the VPN route corresponding to the identifier of the first VPN instance, wherein the fourth BGP peer is an iBGP peer in a second AS.

[0016] In some embodiments, the identifier of the first VPN instance is a first RD, and the first indication information is a first route refresh message, and stopping adding the VPN route corresponding to the identifier of the first VPN instance to the first BGP peer in response to the first indication information comprises: adding, in the first route refresh message, a filter condition to remove the VPN route corresponding to the identifier of the first VPN instance to an out-of-boundary route filter in response to a first out-of-band route filter (ORF) entry, the first ORF entry comprising the first RD; and removing a BGP update message comprising the VPN route corresponding to the identifier of the first VPN instance in response to the filter condition.

[0017] In some embodiments, adding a filter condition to the out-of-boundary route filter in the first route refresh message in response to the first ORF entry to remove the VPN route corresponding to the identifier of the first VPN instance includes: parsing a first ORF entry having an ORF type set to a preset value in the first route refresh message, the preset value representing a new ORF type; parsing an action field in the first ORF entry to obtain a first value, the first value being The filter condition is This indicates that the route should be added to the second BGP peer's out-of-bounds route filter. In the Action field The analysis is performed to find the VPN route that matches the first ORF entry. Add analyze a value of a match field of the first ORF entry to obtain a second value indicating that the VPN route corresponding to the first RD is rejected, analyze a type-specific subfield of the first ORF entry to obtain the first RD, and add a filter condition to the out-of-boundary route filter according to the first value, the second value, and the first RD to remove the BGP update message comprising the VPN route corresponding to the first RD.

[0018] In some embodiments, the first BGP peer Should be revoked VPN Route Withdrawal The transmission of information Should be revoked VPN Route Withdrawal The said information is Withdrawal The VPN route to be Withdrawal receiving second indication information sent from the first BGP peer, the second indication information comprising an identifier of a second VPN instance corresponding to the VPN route to be forwarded; Withdrawal the first BGP peer determines that the number of VPN routes corresponding to the identifier of the second VPN instance is less than the limit value after the VPN route to be added is deleted, and the second instruction information is received instructing the second BGP peer to stop adding a VPN route corresponding to the identifier of the second VPN instance, and in response to the second instruction information, stops removing messages to add the VPN route corresponding to the identifier of the second VPN instance.

[0019] In some embodiments, the identifier of the second VPN instance is a second RD, the second indication information is a second route refresh message, and removing the message for adding the VPN route corresponding to the identifier of the second VPN instance in response to the second indication information comprises removing a configured filter condition corresponding to the second ORF entry in an out-of-boundary route filter in response to a second ORF entry in the second route refresh message to pass a BGP update message comprising the VPN route corresponding to the identifier of the second VPN instance, the second ORF entry comprising the second RD.

[0020] In some embodiments, in the second route refresh message, removing the configured filter condition corresponding to the second ORF entry from the out-of-boundary route filter in response to the second ORF entry includes parsing a second ORF entry having an ORF type set to a preset value in the second route refresh message, the preset value representing a new ORF, parsing an action field in the second ORF entry to obtain a third value, the first value being the configured filter condition corresponding to the second ORF entry to be removed from the out-of-boundary route filter of the second BGP peer, and removing the configured filter condition corresponding to the second ORF entry from the out-of-boundary route filter in response to the third value.

[0021] According to yet another embodiment of the present disclosure, there is provided a Border Gateway Protocol (BGP) peer, the BGP peer comprising: a processor; and a memory, coupled to the processor, for storing instructions that, when executed by the processor, cause the processor to perform a route control method in accordance with the route control method performed by the first BGP peer of any of the previous embodiments. .

[0022] According to yet another embodiment of the present disclosure, there is provided a Border Gateway Protocol (BGP) peer, the BGP peer comprising: a processor; and a memory, coupled to the processor, for storing instructions that, when executed by the processor, cause the processor to perform a route control method in response to the route control method performed by the second BGP peer of any of the previous embodiments. .

[0023] According to yet another embodiment of the present disclosure, there is provided a route control system including a first BGP peer and a second BGP peer that transmits information of an addition of a new Virtual Private Network (VPN) route to the first BGP peer, the information of the addition of the new VPN route including the new VPN route and a VPN route corresponding to an identifier of a first VPN instance corresponding to the new VPN route, the route control system receiving first instruction information from the first BGP peer when the first BGP peer determines whether a number of VPN routes corresponding to the identifier of the first VPN instance has reached or exceeded a limit value, the first instruction information being used to instruct the second BGP peer to stop adding the VPN route corresponding to the identifier of the first VPN instance, and in response to the first instruction information, causing the first BGP peer to stop adding the VPN route corresponding to the identifier of the first VPN instance, the first BGP peer being an internal border gateway protocol (iBGP) peer. .

[0024] In accordance with still other embodiments of the present disclosure, in accordance with some embodiments, the route control system further includes a third BGP peer and a fourth BGP peer, the second BGP peer is further configured to send first instruction information to the third BGP peer instructing the third BGP peer to stop adding a VPN route corresponding to the identifier of the first VPN instance, the third BGP peer is an eBGP peer in a first AS, the third BGP peer is configured to receive the first instruction information sent from the second BGP peer and in response to the first instruction information to the second BGP peer, stop adding a VPN route corresponding to the identifier of the first VPN instance, and send the first instruction information to the fourth BGP peer to instruct the fourth BGP peer to stop adding a VPN route corresponding to the identifier of the first VPN instance, the fourth BGP peer is an iBGP peer in a second AS, the fourth BGP peer is configured to receive the first instruction information sent from the third BGP peer and in response to the first instruction information to the third BGP peer, stop adding a VPN route corresponding to the identifier of the first VPN instance.

[0025] Other features and advantages of the present invention will become apparent from the following detailed description of illustrative embodiments of the present disclosure, when read in conjunction with the accompanying drawings.

[0026] The accompanying drawings are included to provide a further understanding of the present disclosure, are incorporated in and constitute a part of this specification, illustrate embodiments of the present invention, and are not intended to be limiting of the disclosure herein, together with the exemplary embodiments of the present application. [Brief description of the drawings]

[0027] [Figure 1] FIG. 1 illustrates a schematic flow chart of a route control method according to some embodiments of the present disclosure. [Diagram 2]FIG. 2 shows a schematic flowchart of a route control method according to another embodiment of the present disclosure. [Diagram 3] FIG. 3 is a schematic structural diagram of a BGP peer according to some embodiments of the present disclosure. [Figure 4] FIG. 4 is a schematic structural diagram of a BGP peer according to another embodiment of the present disclosure. [Diagram 5] FIG. 5 illustrates a schematic flow chart of a route control device according to some embodiments of the present disclosure. [Figure 6] FIG. 6 shows a schematic flow chart of a route control device according to another embodiment of the present disclosure. [Figure 7] FIG. 7 shows a schematic structural diagram of a route control system according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0028] Hereinafter, a clear and complete description of the technical solutions of the embodiments of the present disclosure will be given with reference to the figures of the embodiments. Obviously, not all embodiments of the present disclosure are given, but only some embodiments are given in this specification. The following description of at least one exemplary embodiment is merely exemplary in nature, and is not intended to limit the present invention, its application or use. All other embodiments obtained by those skilled in the art without creative efforts based on the embodiments of the present disclosure fall within the protection scope of the present disclosure.

[0029] The inventors noticed that in the scenario of option B, it is on the VRF table configured on the ASBR, and in the scenario of option C, the RR (router reflector) does not process VPN information. Therefore, in the scenarios of options B and C, it is currently impossible to limit the number of VPN routes. This may lead to an excessive number of VPN routes for a VPN instance, which may affect the sending and receiving of VPN routes for other VPN instances.

[0030] The technical problem to be solved by this disclosure is how to limit the number of VPN routes of a VPN instance in the Option B and Option C scenarios.

[0031] The present disclosure provides a route control method, which is described below with reference to FIG.

[0032] FIG. 1 is a flow chart of some embodiments of the route control method of the present disclosure. As shown in FIG. 1, the method of these embodiments includes steps S102 to S108. In this embodiment, the first BGP peer can be an iBGP peer (internal Border Gateway Protocol peer) in the first AS, such as a PE. The second BGP peer can be a BGP peer that, together with the first BGP peer, functions as an eBGP peer (external Border Gateway Protocol peer) and an iBGP peer in the first AS at the border of the first AS between the first AS and the second AS.

[0033] In step S102, the second BGP peer sends additional information of the new VPN route to the first BGP peer, and in response, the first BGP peer receives the additional information of the new VPN route sent from the second BGP peer.

[0034] The additional information of the new VPN route can be configured to include the new VPN route and an identifier of the first VPN instance corresponding to the new VPN route. The identifier of the first VPN instance can be a first RD (route identification element) that is included in the new VPN route and can be used as an extended prefix of the destination address of the new VPN route. In the scenario of option A, the route exchanged between ASBRs does not carry the RD. In the scenarios of options B and C, the VPN route carries the RD. The RD can limit the number of VPN routes in a simple and convenient manner that is compatible with existing technologies. Of course, the VPN instance can be uniquely set by setting a new identifier of the VPN instance other than the RD, but is not limited to the example presented in this specification. In the following embodiments, the RD is described as an identifier of the VPN instance as an example.

[0035] The additional information of the new VPN route may be in a BGP update message, which may include a NLRI (Network Layer Reachability Information) field, in which the new VPN route may be carried.

[0036] In some embodiments, In the Option B scenario, the second BGP peer is an ASBR, and in the Option C scenario, the second BGP peer is a RR, i.e., the second BGP peer is a BGP peer at the border of the first AS and acts as an eBGP peer between the first AS and the second AS.

[0037] In step S104, the first BGP peer determines whether the number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds a limit value after adding the new VPN route corresponding to the identifier of the first VPN instance.

[0038] The limit can be set according to the actual processing capabilities of the first BGP peer. The first BGP peer is Identifying the 1st RD in the new VPN route, RT (route target) of the new VPN routeThe first VRF route table corresponding to the new VPN route is determined according to the RT add a new VPN route having the removed first RD to the first VRF route table in response to the first RD, and determine whether the number of route entries in the first VRF route table has reached or exceeded a limit value.

[0039] The first RD can be used as an extended prefix for the destination address in the new VPN route. The first BGP peer can identify the first RD, RT for new VPN route Depending on Support for new VPN routes The first VRF route table can be determined. The RT is also used to determine whether to add a new VPN route to the first VRF route table. The first BGP peer adds a VPN route with the deleted first RD to the first VRF route table, and determines whether the route entry in the first VRF route table reaches or exceeds the limit value. For the process of adding a new VPN route to the first VRF route table, it can be implemented with reference to the prior art.

[0040] In step S106, the first BGP peer sends a first instruction to the second BGP peer, instructing the second BGP peer to stop adding a VPN route corresponding to the identifier of the first VPN instance. When the route corresponding to the identifier of the first VPN instance reaches or exceeds a limit value, the second BGP peer receives the first instruction sent from the first BGP peer accordingly.

[0041] In the scenario of option A, the ASBR can indicate to its peers via a BGP notification message that the number of routes has reached or exceeded a limit value. In this disclosure, the inventors recognized that in the scenarios of options B and C, the ASBR or RR cannot implement a subsequent process of removing (e.g., stopping addition of) VPN routes of a VPN instance in response to the BGP notification message. Therefore, the existing standard route refresh message is improved to control the number of VPN routes of a VPN instance. The structure of the route refresh message is defined in related standards such as RFC5291.

[0042] The first indication information may be a route refresh message. The present disclosure improves this message to realize the control of the number of VPN routes of a VPN instance in the scenarios of option B and option C. The route refresh message comprises one or more ORF (out-of-band route filter) entries. A BGP peer, as a BGP speaker, sends one or more ORF entries to other BGP peers, so that the other BGP peers can use filters corresponding to the ORF entries to pass or filter out BGP update messages sent to the BGP speaker. A first BGP peer can set a first ORF entry that transports a first RD in a first route refresh message and send it to a second BGP peer, so that the second BGP peer can stop adding a VPN corresponding to the first RD according to the first ORF entry. Table 1 shows the structure of a route refresh message in which an ORF entry is transported.

[0043] [Table 1]

[0044] As shown in Table 1, AFI (Address Family Identifier), SAFI (Subsequent Address Family Identifier), Reserved, and Refresh Time belong to the intersection. The route refresh message can be configured to include one or more ORF types, and each of the one or more ORF types can be configured to correspond to one or more ORF entries. The following describes how to configure various fields to control the number of VPN routes corresponding to the first VPN instance depending on the order of the fields in Table 1.

[0045] In the AFI field and the SAFI field, for example, the AFI value and the SAFI value of the first VRF route table corresponding to the first RD are set, respectively.

[0046] The required refresh time field is set to a value representing, for example, “immediate”. Since the required refresh time field can be configured with two values ​​corresponding to “immediate” and “delayed”, the required refresh time field can be set to a value corresponding to “immediate” when the number of VPN routes of the first VPN instance needs to be controlled.

[0047] Regarding the ORF type field, the ORF type used in the present disclosure to control the number of VPN routes of the first VPN instance is a new type compared to the ORF type in an existing standard (e.g., CP-ORF ("hidden prefix ORF"). Therefore, the ORF type field corresponding to the first ORF entry of the first route refresh message can be set to a preset value representing the new ORF type.

[0048] The length field of the ORF entry indicates the total length (in octets) of all ORF entries corresponding to the ORF type. The length of the ORF entry can be configured according to the actual situation.

[0049] For each ORF entry field, the structure of the ORF entry is defined by existing standards. Specifically, as shown in Table 2, an ORF entry is structured to have four fields: action, match, reserved, and type-specific part.

[0050] [Table 2]

[0051] The following describes how the various fields of the first ORF entry can be configured to control the number of VPN routes for the first VPN instance, depending on the order of the fields in Table 2.

[0052] For the action field, for example, the value of the action field of the first ORF entry is set to a first value to indicate that the filter condition corresponding to the first ORF entry should be added to the out-of-boundary route filter of the second BGP peer. In the existing standard, the value of the action field is set to 0 for "add", 1 for "remove", and 2 for "remove all". Thus, VPN routes If you need to control it, you can set the action field to 0.

[0053] For example, the match field of the first ORF entry is the match field of the VPN route whose value matches the first ORF entry. addition In the current standard, the match field is set to a second value indicating that the number of VPN routes in the first VPN instance should be allowed through. In the existing standard, the match field is set to a value of 0 for "allow" and 1 for "deny". Thus, if you need to control the number of VPN routes in the first VPN instance, you can set the match field to 1. If you need to let the number of VPN routes in the first VPN instance through, you can set the match field to 0.

[0054] For the type-specific partial field, the first RD can be added to the type-specific partial field in the first ORF entry, for example, the first RD occupies 8 bytes. For the specific structure of the type-specific partial field, existing standards can be referenced, including fields such as sequence and reserved, and these existing fields are omitted here.

[0055] Through a specific configuration of the first route refresh message, the first BGP peer can instruct the second BGP peer to configure a filter condition corresponding to the first ORF entry in the first route refresh message to remove a BGP update message corresponding to the first RD carried in the first route refresh message.

[0056] In step S108, the second BGP peer stops adding the VPN route corresponding to the identifier of the first VPN instance to the first BGP peer according to the first indication information.

[0057] In some embodiments, the second BGP peer adds a filter condition to remove a VPN route corresponding to the identifier of the first VPN instance in the out-of-boundary route filter in response to the first ORF entry in the first route refresh message. The second BGP peer removes a BGP update message comprising a VPN route corresponding to the identifier of the first VPN instance in the NLRI field in response to the filter condition. The VPN route can be transported in the NLRI field of the BGP update message.

[0058] Further, based on the configuration method of the first route refresh message in the above embodiment, the second BGP peer can analyze the first route refresh message to obtain values ​​of various fields to configure a filter condition for removing a VPN route corresponding to an identifier of the first VPN instance. In some embodiments, the second BGP peer analyzes the AFI and SAFI fields to obtain an AFI value and a SAFI value belonging to the first VRF route table corresponding to the first RD, and sets the corresponding AFI and SAFI fields to the filter condition according to the AFI and SAFI values. According to the corresponding AFI and SAFI fields of the filter condition, the second BGP peer can effectively remove the BGP update message carrying the VPN route that matches the values ​​of the AFI and SAFI fields. The second BGP peer can analyze the required refresh time field to obtain a value representing "immediately" and perform the removal immediately after setting the filter condition. The second BGP peer can analyze the ORF type field to obtain a preset value to determine the type of the subsequent ORF entry. The second BGP peer can parse the transmitted length of the ORF entry to obtain the corresponding length value that facilitates accurate parsing of subsequent ORF entries.

[0059] In addition, the second BGP peer parses the first ORF entry having an ORF type field set to a preset value in the first route refresh message, parses an action field of the first ORF entry to obtain a first value indicating that a filter condition corresponding to the first ORF entry should be added to the second BGP peer's out-of-boundary route filter, and parses a match field of the first ORF entry to obtain an out-of-boundary route filter of the VPN route that matches the first ORF entry. additionis rejected, analyze the type-specific subfield of the first ORF entry to obtain a first RD, and add a filter condition according to the first value, the second value, and the first RD, for removing a BGP update message having a VPN route corresponding to the first RD of the out-of-boundary route filter. When the second BGP peer has a BGP update message that needs to be sent to the first BGP peer, and the RD carried in the VPN route in the NLRI field of the BGP update message is the same as the first RD of the filter condition, the second BGP peer removes the BGP update, i.e., stops sending the VPN route corresponding to the first RD to the first BGP peer.

[0060] In the method of the above embodiment, the first BGP peer receives the information of adding a new VPN route sent from the second BGP peer, and determines that the number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds a limit value after adding a new VPN route according to the identifier of the first VPN instance. When the number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds a limit value, the first BGP peer instructs the second BGP peer to stop adding a VPN route corresponding to the identifier of the first VPN instance. In the disclosure herein, the first BGP peer is an iBGP peer in the first AS, such as a PE. That is, in the present disclosure, instead of using an ASBR or RR at the border of the first AS in option B and option C, the number of VPN routes can be counted and determined through a router in the AS, and the function of the ASBR or RR in option B and option C is not changed, and compatibility with existing technologies is ensured.

[0061] In addition, the identifier of the first VPN instance is transferred in the additional information of the VPN route. According to the identifier of the first VPN instance, the first BGP peer can achieve real-time statistics and determination on the number of VPN routes corresponding to the first VPN instance. , to the first VPN instanceInstruct the second BGP peer to stop adding VPN routes corresponding to the identifier of the first VPN instance so as to limit the number of corresponding routes, thereby reducing the resources of the first BGP peer occupied by the routes of the first VPN instance, not to mention the impact on sending and receiving VPN routes corresponding to other VPN instances, leading to a flexible and controllable VPN network solution.

[0062] The method of the above embodiment is applicable to the scenarios of option B and option C. The ASBR of option B or the RR of option C can be used as the second BGP peer, and the out-of-bounds route filter is configured according to the first route refresh message of the first BGP peer to control the number of VPN routes corresponding to the first VPN instance based on the first RD (the identifier of the first VPN instance).

[0063] Another embodiment of the route control method of the present disclosure will be described below with reference to FIG.

[0064] 2 shows a flowchart of another embodiment of the route control method of the present disclosure. As shown in FIG. 2, referring to FIG. 2, after step S108, the method further includes steps S202 to S218. The second BGP peer may be configured to be a BGP peer at the boundary of the first AS that functions as an eBGP peer between the first AS and the second AS.

[0065] In step S202, the second BGP peer sends a first instruction to the third BGP peer to instruct the third BGP peer to stop adding a VPN route corresponding to the identifier of the first VPN instance. The third BGP peer is, for example, an eBGP peer of the second AS. That is, the third BGP peer may be an ASBR of option B or an RR of option C.

[0066] For the first indication information, the above embodiment can be referred to. According to the first indication information, the third BGP peer stops adding the VPN route corresponding to the identifier of the first VPN instance to the second BGP peer.

[0067] In step S204, the third BGP peer sends a first instruction information to the fourth BGP peer to instruct the fourth BGP peer to stop adding a VPN route corresponding to the identifier of the first VPN instance. The fourth BGP peer is, for example, an iBGP peer in a second AS such as a PE. In response to the first instruction information, the fourth BGP peer stops adding a VPN route corresponding to the identifier of the first VPN instance to the third BGP peer.

[0068] The fourth BGP peer may be a source node that sends additional information (e.g., BGP update message) for the VPN route. After the fourth BGP peer sends the additional information for the VPN route, it is sent to the first BGP peer in the first AS via the third BGP peer and the second BGP peer. The first BGP peer sends the first indication information to the second BGP peer, the third BGP peer and the fourth BGP peer, and each BGP peer in the entire transmission route limits the number of VPN routes of the first VPN instance and reduces the possibility of the occurrence of unknown routes.

[0069] In step S206, the second BGP peer: Should be revoked Sends the withdrawal information of the VPN route to the first BGP peer, and in response, the first BGP peer Should be revoked Receives VPN route withdrawal information.

[0070] Should be revoked The VPN route withdrawal information is withdrawn. Should VPN routes and retracted Should and an identifier of a second VPN instance corresponding to the VPN route. The identifier of the second VPN instance may be a second RD. Should be revokedThe information of the withdrawal of a VPN route may be a BGP update message, and the BGP update message may comprise a withdraw route field that comprises the VPN route to be withdrawn.

[0071] In step S208, the first BGP peer is withdrawn according to the identifier of the second VPN instance. Should Delete a VPN route.

[0072] The first BGP peer identifies the second RD, determines a corresponding second VRF route table according to the second RD, removes the second RD from the VPN route to be withdrawn, searches for the VPN route to be deleted and with the second RD in the second VRF route table, and deletes the VPN route to be withdrawn with the found and deleted second RD.

[0073] In step S210, if the number of routes corresponding to the identifier of the second VPN instance reaches or exceeds the limit value, the first BGP peer deletes the VPN route to be withdrawn and then determines whether the number of VPN routes corresponding to the identifier of the second VPN instance is less than the limit value.

[0074] After deleting the VPN route to be withdrawn, the first BGP peer compares the number of route entries in the second VRF route table with a limit value to determine whether the number is less than the limit value.

[0075] In step S212, if the number of VPN routes corresponding to the identifier of the second VPN instance is less than the limit value, the first BGP peer sends second instruction information to the second BGP peer, instructing the second BGP peer to be allowed to add a VPN route corresponding to the identifier of the second VPN instance, and the second BGP peer receives the second instruction information sent from the first BGP peer in response.

[0076] For example, if the first BGP peer determines that oscillation will not occur, it sends the second indication to the second BGP peer. An indication indicating the determination that oscillation will not occur may also be manually sent to the first BGP peer, and the first BGP peer sends the second indication to the second BGP peer. This prevents the first BGP peer from repeatedly sending the first and second indications to the second BGP peer, which would waste resources and cause the number of VPN routes sent from the second BGP peer to repeatedly fluctuate around the limit.

[0077] The second indication information may be a second route refresh message, in which the first BGP peer sets a second ORF entry carrying an identifier of a second VPN instance (e.g., a second RD) in the second route refresh message and sends it to the second BGP peer, so that the second BGP peer can pass additional information of the VPN route corresponding to the identifier of the second VPN instance according to the second ORF entry.

[0078] With reference to Tables 1 and 2, for implementation of the second indication message, various fields may be set as follows:

[0079] The AFI and SAFI fields are, for example, set to the AFI and SAFI values ​​of the second VRF route table corresponding to the second RD, respectively.

[0080] The refresh time required field may be set to a value that represents, for example, "immediately." The refresh time required field may be set to a value that corresponds to "immediately."

[0081] For the ORF type field, for example, the ORF type field corresponding to the second ORF entry can be set to a preset value representing the new ORF type.

[0082] The length of the ORF entry can be set according to the actual situation.

[0083] The various fields in the second ORF entry can be set as follows:

[0084] For the action field, for example, the value of the action field of the second ORF entry is set to a third value indicating that the configured filter condition corresponding to the second ORF entry should be deleted from the second BGP peer's out-of-boundary route filter. For example, the action field can be set to 1 (representing "delete"). If the second BGP peer is requested to resend all VPN routes, the action field can be set to 2 (representing "all delete"). For the type-specific partial field, a second RD can be added to the type-specific partial field of the second ORF entry, for example, the second RD occupies 8 bytes, and the specific structure of the type-specific partial field can refer to existing standards, including fields such as sequence, reserved, and the description of these existing fields is omitted here.

[0085] In step S214, the second BGP peer stops removing the message for adding the VPN route corresponding to the identifier of the second VPN instance according to the second indication information.

[0086] In some embodiments, the second BGP peer, in response to a second ORF entry in the second route refresh message, removes a configured filter condition corresponding to the second ORF entry in the out-of-band route filter to pass a BGP update message corresponding to an identifier of the second VPN instance and including a VPN route, where the second ORF entry comprises a second RD.

[0087] Further, the second BGP peer parses the second ORF entry having an ORF type field set to a preset value in the second route refresh message, parses the action field of the second ORF entry to obtain a third value representing that the configured filter condition corresponding to the second ORF entry should be deleted from the out-of-boundary route filter of the second BGP peer, and deletes the configured filter condition corresponding to the second ORF entry from the out-of-boundary route filter according to the third value. For the analysis of other fields, reference can be made to the above-mentioned embodiment, and the value obtained after parsing other fields can be used to search for the corresponding filter condition in the out-of-boundary route filter.

[0088] In step S216, the second BGP peer sends to the third BGP peer a second instruction to instruct the third BGP peer to allow addition of a VPN route corresponding to the identifier of the second VPN instance. The third BGP peer is an eBGP peer of the second AS. The third BGP peer may be an ASBR of option B or an RR of option C.

[0089] In step S218, the third BGP peer sends second instruction information to the fourth BGP peer, instructing the fourth BGP peer to allow the addition of a VPN route corresponding to the identifier of the second VPN instance. The fourth BGP peer is an iBGP peer in the second AS. The fourth BGP peer stops removing messages for adding a VPN route corresponding to the identifier of the second VPN instance in response to the second instruction information. The first BGP peer sends the second instruction information to the second BGP peer, the third BGP peer and the fourth BGP peer, so that each BGP peer in the entire transmission path can restore the update of the VPN route corresponding to the identifier of the second VPN instance.

[0090] In the method of the above embodiment, under the condition that the number of routes corresponding to the identifier of the second VPN instance does not exceed a limit value, each BGP peer can restore the update and addition of VPN routes corresponding to the identifier of the second VPN instance. Flexible VPN route control is realized based on the identifier of the second VPN instance (such as RD) and the second route refresh message. It can be applied to the scenarios of Option B and Option C, is compatible with existing technologies, and is flexible and extensible.

[0091] The present disclosure further provides a BGP peer as described below with reference to FIG.

[0092] Figure 3 is a structural diagram of some embodiments of the BGP peer of the present disclosure. As shown in Figure 3, the BGP peer 30 of this embodiment can function as a first BGP peer 30, and includes a receiving module 310, a determining module 320, and a sending module 330. The first BGP peer is an iBGP peer in a first AS. The second BGP peer is a BGP peer at the border of the first AS and serves as an eBGP peer of the first AS and the second AS.

[0093] The receiving module 310 is configured to receive additional information of a new virtual private network (VPN) route sent from a second BGP peer, where the additional information of the new VPN route comprises an identifier of the new VPN route and a first VPN instance corresponding to the new VPN route.

[0094] The determination module 320 is configured to determine whether the number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds a limit value after adding the new VPN route according to the identifier of the first VPN instance.

[0095] In some embodiments, the identifier of the first VPN instance is a first RD. The determination module 320 is configured to identify the first RD included in the new VPN route, Route Target (RT) of the new VPN routeDetermine a first virtual route forwarding (VRF) route table corresponding to the new VPN route according to the first RD, and remove the first RD from the new VPN route. RT Depending on the , add new VPN routes with the 1st RD deleted to the 1st VRF route table, and determine whether the number of route entries in the 1st VRF route table has reached or exceeded the limit.

[0096] The sending module 330 is configured to send first instruction information to the second BGP peer to instruct the second BGP peer to stop adding VPN routes corresponding to the identifier of the first VPN instance when the number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds a limit value.

[0097] In some embodiments, the first indication is a first route refresh message in which a first ORF entry is set. A value of an action field of the first ORF entry is set to a first value indicating that a filter condition corresponding to the first ORF entry should be added to the out-of-boundary route filter of the second BGP peer. A value of a match field of the first ORF entry is set to a first value indicating that a filter condition corresponding to the first ORF entry should be added to the out-of-boundary route filter of the second BGP peer. addition is set to a second value indicating that it is rejected, and the first RD is added to the type-specific portion field of the first ORF entry.

[0098] In some embodiments, the receiving module 310 receives the BGP request from the second BGP peer. Should be revoked configured to receive VPN route withdrawal information, Should be revokedThe information on the withdrawal of the VPN route includes the VPN route to be withdrawn and an identifier of a second VPN instance corresponding to the VPN route to be withdrawn, deletes the VPN route to be withdrawn according to the identifier of the second VPN instance, and if the number of VPN routes corresponding to the identifier of the second VPN instance has reached or exceeded a limit value, after deleting the VPN route to be withdrawn, determines whether the number of VPN routes corresponding to the identifier of the second VPN instance is less than the limit value, and if the number of VPN routes corresponding to the identifier of the second VPN instance is less than the limit value, sends second instruction information to the second BGP peer instructing it to allow the addition of the VPN route corresponding to the identifier of the second VPN instance.

[0099] In some embodiments, the identifier of the second VPN instance is a second RD, the second indication information is a second route refresh message, and the sending module 330 is configured to set a second ORF entry in the second route refresh message, set a value of an action field of the second ORF entry to a third value indicating that a configured filter condition corresponding to the second ORF entry should be removed from the out-of-boundary route filter of the second BGP peer, and add the second RD to a type-specific part field of the second ORF entry.

[0100] In some embodiments, the AFI (Address Family Identifier) ​​field and the SAFI (Subsequent Address Family Identifier) ​​field in the first route refresh message are set to the AFI and SAFI values ​​of the first VRF route table corresponding to the first RD, and the refresh time needed field of the first route refresh message is set to a value representing “immediate”.

[0101] In some embodiments, the ORF type field corresponding to the first ORF entry in the first route refresh message is set to a preset value representing a new ORF type.

[0102] 4 is a structural diagram of another embodiment of the BGP peer of the present disclosure. As shown in FIG. 4, the BGP peer 40 of this embodiment can function as a second BGP peer 40, and includes a sending module 410, a receiving module 420 and a filter module 430. The first BGP peer is an iBGP peer in the first AS. The second BGP peer is a BGP peer at the border of the first AS, functioning as an eBGP peer between the first AS and the second AS.

[0103] The sending module 410 is configured to send a new virtual private network (VPN) route with additional information to a first BGP peer, comprising the new VPN route and an identifier of a first VPN instance corresponding to the new VPN route.

[0104] The receiving module 420 is configured to receive first instruction information sent from the first BGP peer when the first BGP peer determines that the number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds a limit value, and the first instruction information is used to instruct the second BGP peer to stop adding VPN routes corresponding to the identifier of the first VPN instance.

[0105] The filter module 430 is configured to stop adding a VPN route corresponding to the identifier of the first VPN instance to the first BGP peer in response to the first indication information.

[0106] In some embodiments, the identifier of the first VPN instance is a first RD, the first indication information is a first route refresh message, and the filter module 430 is configured to add a filter condition to remove a VPN route corresponding to the identifier of the first VPN instance in an out-of-boundary route filter in response to a first out-of-band router filter (ORF) entry in the first route refresh message, where the first ORF entry includes the first RD, and in response to the filter condition, remove the BGP update message with the VPN route corresponding to the identifier of the first VPN instance.

[0107] In some embodiments, the filter module 430 is configured to parse a first ORF entry having an ORF type field set to a preset value in the first route refresh message, the preset value representing a new ORF type, and parse an action field of the first ORF entry to , filter criteria Retrieve the first value that indicates what should be added to the out-of-boundary route filter of the second BGP peer, analyze the match field of the first ORF entry, and find the VPN routes that match the first ORF entry. addition is rejected; analyze the type-specific subfield of the first ORF entry to obtain the first RD; and add a filter condition for removing BGP update messages having a VPN route corresponding to the first RD of the out-of-boundary route filter according to the first value, the second value, and the first RD.

[0108] In some embodiments, the transmission module 410 includes: Should be revoked configured to send information to the first BGP peer to withdraw the VPN route; Should be revoked The information for withdrawing a VPN route includes a VPN route to be withdrawn and an identifier of a second VPN instance corresponding to the VPN route instance to be withdrawn, and receives second instruction information sent from the first BGP peer, where the second instruction information represents that the first BGP peer determines that after deleting the VPN route to be withdrawn, the number of VPN routes corresponding to the identifier of the second VPN instance is less than a limit value, and is used to indicate that the second BGP peer is allowed to add a VPN route corresponding to the identifier of the second VPN instance, and the filter module 430 is further configured to stop removing messages for adding a VPN route corresponding to the identifier of the second VPN instance in response to the second instruction information.

[0109] In some embodiments, the identifier of the second VPN instance is a second RD, the second indication information is a second route refresh message, and the filter module 430 is configured to, in response to the second ORF entry in the second route refresh message, remove the configured filter condition corresponding to the second ORF entry in the out-of-band route filter to pass the BGP update message comprising the VPN route corresponding to the identifier of the second VPN instance, where the second ORF entry includes the second RD.

[0110] In some embodiments, the filter module 430 is configured to parse a second ORF entry having an ORF type field set to a preset value in the second route refresh message, where the preset value represents a new ORF, parse an action field of the second ORF entry to obtain a third value indicating that a configured filter condition corresponding to the second ORF entry should be removed from the out-of-boundary route filter of the second BGP peer, and remove the configured filter condition corresponding to the second ORF entry from the out-of-boundary route filter in response to the third value.

[0111] In some embodiments, the sending module 410 is further configured to send the first instruction information to a third BGP peer to instruct the third BGP peer to stop adding a VPN route corresponding to the identifier of the first VPN instance, the third BGP peer being an eBGP peer of the second AS, and the third BGP peer is configured to send the first instruction information to a fourth BGP peer to instruct the fourth BGP peer to stop adding a VPN route corresponding to the identifier of the first VPN instance, the fourth BGP peer being an iBGP peer within the second AS.

[0112] The present disclosure further provides a route control device that can be provided in a first BGP peer to execute the method performed by the first BGP peer in the aforementioned embodiment. The route control device can also be provided in a second BGP peer to execute the method performed by the second BGP peer in the aforementioned embodiment. The route control device of this embodiment of the present disclosure can be implemented by various computing devices or computer systems, which will be described below with reference to Figures 5 and 6.

[0113] 5 is a structural diagram of some embodiments of the route control device of the present disclosure. As shown in FIG. 5, the device 50 of this embodiment includes a memory 510 and a processor 520 coupled to the memory 510, and the processor 520 is configured to execute the route control method according to any one of the embodiments according to the instructions stored in the memory 510.

[0114] Here, the memory 510 may be configured to include, for example, a system memory, a fixed non-volatile storage medium, etc. The system memory stores, for example, an operating system, applications, a boot loader, databases, and other programs.

[0115] FIG. 6 is a structural diagram of another embodiment of the route control device of the present disclosure. As shown in FIG. 6, the device 60 of this embodiment includes a memory 610 and a processor 620 similar to the memory 510 and the processor 520, respectively. In addition, the device 60 may include an input / output interface 630, a network interface 640, a storage interface 650, and the like. These interfaces 630, 640, and 650 may be connected to the memory 610 and the processor 620 via a bus 660, for example. Here, the input / output interface 630 provides a connection interface for input / output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 640 provides a connection interface to various networked devices, and can be connected to, for example, a database server or a cloud storage server. The storage interface 650 provides a connection interface to an external storage device such as an SD card or a USB flash disk.

[0116] The present disclosure further provides a route control system, which is described below with reference to FIG.

[0117] 7 is a structural diagram of some embodiments of the route control system of the present disclosure. As shown in FIG. 7, the system 7 of this embodiment includes a first BGP peer 40 and a second BGP peer 50 according to any of the previous embodiments.

[0118] In some embodiments, the system further comprises a third BGP peer 72 and a fourth BGP peer 74 .

[0119] The second BGP peer 50 is further used to send a first instruction information to a third BGP peer 72 to instruct the third BGP peer 72 to stop adding new VPN routes corresponding to the identifier of the first VPN instance, where the third BGP peer 72 is an eBGP peer of the second AS.

[0120] The third BGP peer 72 receives the first instruction information sent from the second BGP peer, and is used to stop adding a new VPN route corresponding to the identifier of the first VPN instance, and sends the first instruction information to the fourth BGP peer 74 for instructing the fourth BGP peer 74 to stop adding a new VPN route corresponding to the identifier of the first VPN instance, where the fourth BGP peer 74 is an iBGP in the second AS.

[0121] The fourth BGP peer 74 receives first instruction information sent from the third BGP peer 72, which is used to stop the third BGP peer 72 from adding a new VPN route corresponding to the identifier of the first VPN instance, where the second BGP peer 50 is a BGP peer at the border of the first AS and functions as an eBGP peer of the first AS and the second AS.

[0122] The present disclosure further provides a non-volatile computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the route control method of any one of the preceding embodiments.

[0123] Those skilled in the art should understand that the embodiments of the present disclosure may be provided as a method, a system, or a computer program product. Thus, the embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment including both hardware and software elements. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer usable non-volatile storage media (including, but not limited to, disk storage devices, CD-ROMs, optical storage devices, etc.) having program code embodied therein that is usable by a computer.

[0124] The present disclosure will be described with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present disclosure. It should be understood that each process and / or block in the flowcharts and / or block diagrams, and combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. The computer program instructions may be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or a processor of other programmable data processing apparatus to generate a machine that, when executed by a processor of the computer or other programmable data processing apparatus, generates means for implementing the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0125] Also, computer program instructions may be stored in a computer-readable storage device that can instruct a computer or other programmable data processing apparatus to operate in a particular manner, where the instructions stored in the computer-readable storage device produce a product comprising instructions for implementing the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0126] These computer program instructions can also be loaded into a computer or other programmable device and cause the computer or other programmable device to execute a series of operational steps to generate a computer-implemented process such that the instructions executing on the computer or other programmable device provide steps for implementing the functions specified in one or more flows of the flowcharts and / or one or more blocks of the block diagrams.

[0127] The above are merely preferred embodiments of the present disclosure, and are not intended to be limiting of the present disclosure. Any modifications, replacements, improvements, etc. within the spirit and principle of the present disclosure are included in the scope of protection of the present disclosure.

Claims

1. 1. A method of route control performed by a first Border Gateway Protocol (BGP) peer, the method comprising: receiving additional information of a new virtual private network (VPN) route sent from a second BGP peer, the additional information of the new VPN route comprising an identifier of the new VPN route and a first VPN instance corresponding to the new VPN route; determining whether a number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds a limit value after adding the new VPN route according to the identifier of the first VPN instance; sending a first instruction to the second BGP peer to instruct the second BGP peer to stop adding VPN routes corresponding to the identifier of the first VPN instance when the number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds the limit; The method of claim 1, wherein the first BGP peer is an internal Border Gateway Protocol (iBGP) peer in a first autonomous system (AS).

2. 2. A route control method according to claim 1, comprising: The second BGP peer is a BGP peer that functions as an external Border Gateway Protocol peer (eBGP) between the first AS and the second AS at the boundary of the first AS.

3. 3. A route control method according to claim 1, wherein the identifier of the first VPN instance is a first route identifier (RD), and determining whether the number of VPN routes corresponding to the identifier of the first VPN instance reaches or exceeds a limit value after adding the new VPN route according to the identifier of the first VPN instance includes identifying the first RD in the new VPN route; Determine a first virtual route forward (VRF) route table corresponding to the new VPN route according to a route target (RT) of the new VPN route, and remove the first RD from the new VPN route; Add the new VPN route with the first RD removed to the first VRF route table according to the RT of the new VPN route; determining when a number of routes entered in the first VRF route table reaches or exceeds the limit value.

4. 3. A method for route control according to claim 1 or 2, wherein the identifier of the first VPN instance is a first route distinguisher (RD); The first indication information is a first route refresh message, and sending the first indication information to the second BGP peer includes: Configuring a first out-of-band route filter (ORF) entry in the first route refresh message; setting a value of an action field of the first ORF entry to a first value indicating that a filter state corresponding to the first ORF entry should be added to the out-of-bounds route filter of the second BGP peer; setting a value of a match field of the first ORF entry to a second value indicating that addition of the VPN route matching the first ORF entry is denied; The method of route control further comprising adding a first RD to a type specific portion field of the first ORF entry.

5. The route control method according to claim 1 or 2, further comprising: receiving information regarding the withdrawal of a VPN route to be withdrawn sent from the second BGP peer, the information regarding the withdrawal of the VPN route to be withdrawn comprising the VPN route to be withdrawn and an identifier of a second VPN instance corresponding to the VPN route to be withdrawn; Deleting the VPN route to be revoked according to the identifier of the second VPN instance; When the number of VPN routes corresponding to the identifier of the second VPN instance reaches or exceeds the limit value, determining whether the number of VPN routes corresponding to the identifier of the second VPN instance is less than the limit value after deleting the VPN route to be withdrawn; A route control method, comprising: sending second instruction information to a second BGP peer instructing the second BGP peer to allow the second BGP peer to add a VPN route corresponding to the identifier of the second VPN instance when the number of VPN routes corresponding to the identifier of the second VPN instance is smaller than the limit value.

6. 6. A route control method according to claim 5, comprising: the identifier of the second VPN instance is a second RD, the second indication information is a second route refresh message, and sending the second indication information to the second BGP peer includes: populating the second route refresh message with a second ORF entry; setting a value of an action field of the second ORF entry to a third value indicating that a configured filter term corresponding to the second ORF entry should be deleted from the out-of-boundary route filter of the second BGP peer; The method of route control further comprising adding the second RD to a type specific portion field of the second ORF entry.

7. 5. A route control method according to claim 4, comprising: Setting an Address Family Identifier (AFI) and a Subsequent Address Family Identifier (SAFI) in the first route refresh message to an AFI value and a SAFI value, respectively, of a first Virtual Route Forward (VRF) route table corresponding to the first RD; a refresh-required-time field of the first route refresh message is set to a value indicating "immediate", or The method of route control, wherein an ORF type field corresponding to the first ORF entry of the first route refresh message is set to a preset value representing a new ORF type.

8. 7. A route control method according to claim 6, comprising: The AFI field and the SAFI field in the second route refresh message are set to the AFI value and the SAFI value of a second VRF route table corresponding to the second RD, respectively; a refresh-required-time field of the second route refresh message is set to a value indicating "immediate", or The method of claim 1, wherein an ORF type field corresponding to the second ORF entry in the second route refresh message is set to a preset value representing a new ORF type.

9. 1. A route control method performed by a second Border Gateway Protocol (BGP) peer, the route control method comprising: transmitting additional information of a new virtual private network (VPN) route to the first BGP peer, the additional information of the new VPN route comprising an identifier of the new VPN route and a first VPN instance corresponding to the new VPN route; receiving first instruction information transmitted from the first BGP peer when the first BGP peer determines that a number of VPN routes corresponding to the identifier of the first VPN instance has reached or exceeded a limit value, the first instruction information instructing the second BGP peer to stop adding VPN routes corresponding to the identifier of the first VPN instance; Stop adding the VPN route corresponding to the identifier of the first VPN instance to the first BGP peer in response to the first indication information; The method of route control, wherein the first BGP peer is an internal Border Gateway Protocol (iBGP) peer.

10. 10. A route control method according to claim 9, comprising: The second BGP peer is a BGP peer that functions as an external Border Gateway Protocol peer (eBGP) between the first AS and the second AS at the boundary of the first AS.

11. The route control method according to claim 9 or 10, further comprising: sending the first instruction information to a third BGP peer to instruct the third BGP peer to stop adding the VPN route corresponding to the identifier of the first VPN instance; sending the first instruction information from the third BGP peer to a fourth BGP peer to instruct the fourth BGP peer to stop adding the VPN route corresponding to the identifier of the first VPN instance; The fourth BGP peer is an iBGP peer in a second AS.

12. The route control method according to claim 9 or 10, further comprising: the identifier of the first VPN instance is a first RD, and the first indication information is a first route refresh message; Stopping adding the VPN route corresponding to the identifier of the first VPN instance to the first BGP peer in response to the first indication information includes: adding, in the first route refresh message, a filter condition to remove the VPN route corresponding to the identifier of the first VPN instance to an out-of-bounds route filter in response to a first out-of-band route filter (ORF) entry, the first ORF entry comprising the first RD; removing BGP update messages comprising the VPN route corresponding to the identifier of the first VPN instance according to the filter condition.

13. 13. A route control method according to claim 12, comprising: In the first route refresh message, adding a filter condition to the out-of-boundary route filter in response to the first ORF entry to remove the VPN route corresponding to the identifier of the first VPN instance includes: parsing a first ORF entry having an ORF type set to a preset value in the first route refresh message, the preset value representing a new ORF type; parsing an action field in the first ORF entry to obtain a first value, the first value indicating that the filter term should be added to an out-of-bounds route filter of the second BGP peer; parsing a value of a match field of the first ORF entry to obtain a second value indicating that addition of a VPN route matching the first ORF entry is denied; parsing a type-specific portion field of the first ORF entry to obtain the first RD; A route control method that adds a filter condition to the out-of-boundary route filter according to the first value, the second value, and the first RD, for removing the BGP update message having the VPN route corresponding to the first RD.

14. The route control method according to claim 9 or 10, further comprising: transmitting to a first BGP peer information of a withdrawal of a VPN route to be withdrawn, the information of the withdrawal of the VPN route to be withdrawn comprising an identifier of the VPN route to be withdrawn and a second VPN instance corresponding to the VPN route to be withdrawn; receiving second indication information transmitted from the first BGP peer, the second indication information indicating that the first BGP peer has determined that the number of VPN routes corresponding to the identifier of the second VPN instance is less than the limit value after the VPN route to be withdrawn is deleted, the second indication information instructing the second BGP peer to stop adding VPN routes corresponding to the identifier of the second VPN instance; and stopping, in response to the second instruction information, removing a message for adding the VPN route corresponding to the identifier of the second VPN instance.

15. The route control method according to claim 14, further comprising: the identifier of the second VPN instance is a second RD, and the second indication information is a second route refresh message; The removal of the message for adding the VPN route corresponding to the identifier of the second VPN instance in response to the second indication information includes: A route control method comprising: deleting a configured filter condition corresponding to the second ORF entry in an out-of-boundary route filter in response to a second ORF entry in the second route refresh message to pass a BGP update message comprising the VPN route corresponding to the identifier of the second VPN instance, the second ORF entry comprising the second RD.

16. 16. A route control method according to claim 15, comprising: In the second route refresh message, deleting the configured filter condition corresponding to the second ORF entry from the out-of-boundary route filter in response to the second ORF entry includes: analyzing a second ORF entry having an ORF type set to a preset value in the second route refresh message, the preset value representing a new ORF; parsing an action field in the second ORF entry to obtain a third value indicating that the configured filter term corresponding to the second ORF entry should be deleted from the second BGP peer's out-of-bounds route filter; and deleting the configured filter condition corresponding to the second ORF entry from the out-of-boundary route filter in response to the third value.

17. 1. A Border Gateway Protocol (BGP) peer, comprising: A processor; A Border Gateway Protocol (BGP) peer comprising: a memory coupled to the processor storing instructions that, when executed by the processor, cause the processor to perform the route control method of claim 1.

18. 1. A Border Gateway Protocol (BGP) peer, comprising: A processor; A Border Gateway Protocol (BGP) peer comprising: a memory coupled to the processor storing instructions that, when executed by the processor, cause the processor to perform the route control method of claim 11.

19. A BGP peer according to claim 17 acting as a first BGP peer; The BGP peer of claim 18 acting as a second BGP peer.

20. 20. The route control system of claim 19, Further, a third BGP peer and a fourth BGP peer are provided; a route control system for receiving the first indication information from the third BGP peer and instructing the third BGP peer to stop adding the VPN route corresponding to the identifier of the first VPN instance in response to the first indication information to the second BGP peer, and for transmitting the first indication information to the fourth BGP peer to instruct the fourth BGP peer to stop adding the VPN route corresponding to the identifier of the first VPN instance, and the fourth BGP peer is an iBGP peer in the second AS, and the fourth BGP peer is configured to receive the first indication information from the third BGP peer and instruct the third BGP peer to stop adding the VPN route corresponding to the identifier of the first VPN instance in response to the first indication information to the third BGP peer.

Citation Information

Patent Citations

  • Device and method for transferring packet, and its processing program

    JP2003258876A

  • Device for monitoring number of paths, method for monitoring number of paths, and program for monitoring number of paths

    JP2008054026A

  • System and program transferring user route advertisement to virtual closed-area network

    JP2008219530A

  • Method and system for implementing a virtual private network based on a traffic engineering tunnel

    JP2014532368A

  • Method and apparatus for limiting VPNv4 prefixes per VPN in an inter-autonomous system environment

    US20060193329A1