CN106713098A - Routing target processing method and device - Google Patents

Abstract

The invention provides a routing target processing method and device. The method includes the following steps that: a routing target value that is not used by a virtual private network (VPN) is generated; and the routing target value not used by the VPN is applied to the import and export routing targets of all PE (Provider Edge) nodes of provider edge devices under a network. With the routing target processing method and device of the invention adopted, a problem that a routing target can only be manually generated in the prior art can be solved, and therefore, the high efficiency of routing target distribution can be realized.

Description

Routing target processing method and device

technical field

The present invention relates to the communication field, in particular to a method and device for processing routing objects.

Background technique

At present, due to the consideration of L3VPN service security and network efficiency, users do not want their own routing information to be published on the entire network. The introduced control method is to use the Route Target (RT for short). At the same time, RT is divided into Import RT and Export RT, which are used for import and export strategies of routing information respectively. The RT enables the PE router to include only the routes of the virtual private network (Virtual Private Network, VPN for short) directly connected to it, thereby saving resources of the PE router and improving network scalability. Because RT is unique, it can only be used by one VPN. By importing and exporting RT through reasonable configuration, operators can build L3VPNs with different topologies.

Aiming at the problem that routing targets can only be manually generated in related technologies, no effective solution has been proposed yet.

Contents of the invention

The present invention provides a routing target processing method and device to at least solve the problem in the related art that routing targets can only be generated manually.

According to one aspect of the present invention, a routing target processing method is provided, including: generating a virtual private network VPN unused routing target value; applying the VPN unused routing target value to all operator edge devices under the network Import and export routing targets of PE nodes.

Optionally, before generating the unused routing target value of the virtual private network VPN, the method includes: acquiring information of all PE nodes; and determining that all PE nodes are connected nodes according to the information.

Optionally, when the networking is a FullMesh fast rerouting FRR networking, the method includes: counting the PE nodes with FRR master-backup relationship as A pair; generating 2A VPN unused routing target values; The above 2A VPN unused routing target values are applied to the import and export routing targets of PE nodes that do not form a FRR active-standby relationship; and/or, the routing target values excluding the routing target values corresponding to the first PE node The import and export routing target of the second PE node; wherein, the first PE node and the second PE node have an FRR master-backup relationship, and A is a natural number.

Optionally, when the network is an H-L3VPN network, PE nodes at the user-side PE device (User facing-Provider Edge, referred to as UPE) level are connected to the network core PE device (Network Provider Edge, referred to as UPE for short). When there are PE nodes at the NPE level, and the PE nodes at the NPE level do not have a PE node with a FRR master-backup relationship, the method includes: counting the number of PE nodes at the UPE level as B, where B is a natural number; Generate B VPN unused routing target values; apply a VPN unused routing target value to the import and export routing targets of PE nodes at the UPE level; and/or, apply the B VPN unused routing targets The value is applied to the import and export routing targets of the PE nodes at the NPE level.

Optionally, when the network is an H-L3VPN network, the PE nodes at the UPE level are connected to the PE nodes at the NPE level, and the PE nodes at the NPE level have PE nodes with an FRR master-backup relationship, the The method includes: counting the number of PE nodes at the UPE level as C, where C is a natural number; counting PE nodes with FRR active/standby relationships as D pairs, where D is a natural number; generating C+D unused VPN Routing target value; apply a VPN unused routing target value to the import and export routing target of the PE node of the UPE layer that does not form a FRR active/standby relationship; and/or, apply the C+D VPN unused The routing target value is applied to the import and export routing target of the PE node of the NPE layer that does not form the FRR active-standby relationship; and/or, the routing target value that is not used by the two VPNs is applied to the UPE that forms the FRR active-standby relationship and/or, applying C+D-1 VPN unused routing target values to the import and export routing targets of the PE nodes of the NPE layer forming the FRR master-backup relationship.

According to another aspect of the present invention, there is also provided a routing target processing device, including: a first generation module, used to generate a routing target value not used by a virtual private network VPN; a first application module, used to convert the VPN Unused route target values are applied to the import and export route targets of all carrier edge device PE nodes in the network.

Optionally, the device further includes: an acquiring module, configured to acquire information of all the PE nodes; a determining module, configured to determine, according to the information, that all the PE nodes are connected nodes.

Optionally, when the networking is a FullMesh FRR networking, the device includes: a first statistics module, used to count PE nodes with an FRR master-backup relationship as A pairs; a second generation module, used to generate 2A A VPN unused routing target value; the second application module is used to apply the 2A VPN unused routing target values to the import and export routing targets of PE nodes that do not form a FRR active-standby relationship; and/or, the first Three application modules, configured to apply routing target values other than the routing target value corresponding to the first PE node to the import and export routing targets of the second PE node; wherein, the first PE node and the second PE node There is an FRR active/standby relationship between nodes, and A is a natural number.

Optionally, when the network is an H-L3VPN network, and the PE nodes at the UPE level are connected to the PE nodes at the NPE level, and the PE nodes at the NPE level do not have a PE node with an FRR master-backup relationship, the The device includes: a second statistical module, used to count the number of PE nodes at the UPE level as B, where B is a natural number; a third generation module, used to generate B unused routing target values for VPN; fourth An application module, configured to apply a VPN unused route target value to the import-export route target of the PE node at the UPE level; and/or, a fifth application module, configured to apply the B VPN unused routes The target value is applied to the import and export route targets of the PE nodes at the NPE level.

Optionally, when the network is an H-L3VPN network, the PE nodes at the UPE level are connected to the PE nodes at the NPE level, and the PE nodes at the NPE level have PE nodes with an FRR master-backup relationship, the The device includes: a third statistical module, which is used to count the number of PE nodes at the UPE level as C, wherein C is a natural number; a fourth statistical module, which is used to count PE nodes with FRR master-backup relationships as D pairs, where , D is a natural number; the fourth generation module is used to generate C+D unused routing target values of VPN; the sixth application module is used to apply a VPN unused routing target value to the FRR master/backup relationship The import and export routing target of the PE node of the UPE layer; and/or, the seventh application module, configured to apply the routing target values unused by the C+D VPNs to the NPE that has not formed an FRR active/standby relationship The import and export routing target of the PE node of the layer; and/or, the eighth application module, used to apply the routing target value of the two VPNs unused to the import and export route of the PE node of the UPE layer forming the FRR active/standby relationship Target; and/or, a ninth application module, configured to apply C+D-1 unused routing target values of the VPN to the import and export routing targets of the PE nodes of the NPE layer that form the FRR master-backup relationship.

Through the present invention, the unused routing target value of the generated virtual private network VPN is used; the VPN unused routing target value is applied to the import and export routing targets of all operator edge equipment PE nodes under the network. The problem that the routing target can only be manually generated in the related art is solved, thereby realizing the high efficiency of routing target publishing.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

Fig. 1 is a flowchart of a routing target processing method according to an embodiment of the present invention;

FIG. 2 is a structural block diagram of a routing object processing device according to an embodiment of the present invention;

FIG. 3 is a structural block diagram (1) of a routing object processing device according to an embodiment of the present invention;

4 is a structural block diagram (2) of a routing object processing device according to an embodiment of the present invention;

FIG. 5 is a structural block diagram (3) of a routing object processing device according to an embodiment of the present invention;

FIG. 6 is a structural block diagram (4) of a routing object processing device according to an embodiment of the present invention;

Fig. 7 is a FullMesh scene routing target release diagram according to an embodiment of the present invention;

Fig. 8 is a FullMesh FRR scenario routing target release diagram according to an embodiment of the present invention;

Fig. 9 is an H-L3VPN scenario routing target publishing diagram according to an embodiment of the present invention;

Fig. 10 is a FullMesh scene networking diagram according to an embodiment of the present invention;

FIG. 11 is a networking diagram of a FullMesh FRR scenario according to an embodiment of the present invention;

Fig. 12 is a networking diagram of an H-L3VPN scenario according to an embodiment of the present invention.

detailed description

Hereinafter, the present invention will be described in detail with reference to the drawings and examples. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

It should be noted that the terms "first" and "second" in the description and claims of the present invention and the above drawings are used to distinguish similar objects, but not necessarily used to describe a specific sequence or sequence.

In this embodiment, a routing target processing method is provided. FIG. 1 is a flowchart of a routing target processing method according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:

Step S102, generating an unused routing target value of the virtual private network VPN;

Step S104, applying the unused route target value of the VPN to the import and export route targets of all PE nodes of the operator's edge equipment in the network.

Through the above steps, the unused routing target value of the VPN can be automatically generated, and the unused routing target value of the VPN can be applied to the import and export routing targets of all PE nodes in the network, which solves the problem of manually generating routing targets in related technologies problem, and then realize the efficiency of routing target publishing.

In an optional embodiment, before generating the unused routing target value of the virtual private network VPN, the information of all the PE nodes is obtained, and all the PE nodes are determined to be connected nodes according to the information. That is, there are no isolated PE nodes in the networking.

When the above-mentioned networking is a FullMesh fast rerouting FRR networking, in an optional embodiment, the PE nodes with the FRR master-backup relationship are counted as A pairs, and 2A VPN unused routing target values are generated. Unused route target values are applied to the import and export route targets of PE nodes that do not form an active/standby FRR relationship. In another optional embodiment, the routing target value except the routing target value corresponding to the first PE node is applied to the import and export routing target of the second PE node; wherein, the first PE node and the second PE node There is an FRR active/standby relationship, and A is a natural number.

When the above-mentioned networking is an H-L3VPN networking, and the PE nodes at the UPE level are connected to the PE nodes at the NPE level, and the PE nodes at the NPE level do not have a PE node with an FRR master-backup relationship, in an optional embodiment , the number of PE nodes at the UPE level is counted as B, where B is a natural number, and B unused routing target values for the VPN are generated, and an unused routing target value for the VPN is applied to the import and export of the PE nodes at the UPE level routing target. In another optional embodiment, the B route target values not used by the VPN are applied to the import and export route targets of the PE nodes at the NPE level.

When the above-mentioned networking is an H-L3VPN networking, and the PE nodes at the UPE level are connected to the PE nodes at the NPE level, and the PE nodes at the NPE level have PE nodes with an FRR master-backup relationship, in an optional embodiment, The number of PE nodes at the UPE level is counted as C, where C is a natural number, and the number of PE nodes with FRR active/standby relationship is counted as D pairs, where D is a natural number, and C+D unused routing target values are generated by the VPN. A VPN unused route target value is applied to the import and export route targets of the PE nodes of the UPE layer that do not form the FRR active/standby relationship. In another optional embodiment, the C+D unused route target values of the VPN are applied to the import and export route targets of the PE nodes of the NPE layer that do not form the FRR master-backup relationship. In yet another optional embodiment, two routing target values not used by the VPN are applied to the import and export routing targets of the PE nodes of the UPE layer forming the FRR master-backup relationship. In yet another optional embodiment, C+D-1 unused routing target values of the VPN are applied to the import and export routing targets of the PE nodes at the NPE layer forming the FRR master-backup relationship.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products are stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to enable a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present invention.

In this embodiment, a routing target processing device is also provided, which is used to implement the above embodiments and preferred implementation modes, and what has already been described will not be repeated. As used below, the term "module" may be a combination of software and/or hardware that realizes a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.

Fig. 2 is a structural block diagram of a routing target processing device according to an embodiment of the present invention. As shown in Fig. 2 , the device includes: a first generation module 22 for generating unused routing target values of a virtual private network VPN; a first application Module 24, configured to apply the routing target value not used by the VPN to the importing and exporting routing targets of all PE nodes of the operator's edge equipment under the network.

Fig. 3 is a structural block diagram (1) of a routing object processing device according to an embodiment of the present invention. As shown in Fig. 3 , the device includes, in addition to all modules shown in Fig. 2 , an obtaining module 32 for obtaining the Information of all PE nodes; a determining module 34, configured to determine that all PE nodes are connected nodes according to the information.

Fig. 4 is a structural block diagram (two) of a routing target processing device according to an embodiment of the present invention. As shown in Fig. 4, when the networking is a FullMesh FRR networking, the device includes: a first statistics module 42 for statistics There is the PE node of FRR master/backup relationship as A pair; The second generating module 44 is used to generate 2A VPN unused routing target values; the second application module 46 is used to use the 2A VPN unused routing target values Applied to the import and export routing target of the PE node that has not formed the FRR active-standby relationship; and/or, the third application module 48 is used to apply the routing target value except the routing target value corresponding to the first PE node to the An import and export routing target of two PE nodes; wherein, the first PE node and the second PE node have an FRR master-backup relationship, and A is a natural number.

Fig. 5 is a structural block diagram (3) of a routing target processing device according to an embodiment of the present invention. As shown in Fig. 5, the networking is an H-L3VPN networking, and the PE nodes at the UPE level are connected to the PE nodes at the NPE level , and when the PE nodes at the NPE level do not have a PE node with an FRR master-backup relationship, the device includes: a second statistics module 52, which is used to count the number of PE nodes at the UPE level as B, where B is a natural number; Three generating modules 54, for generating B VPN unused routing target values; a fourth application module 56, for applying a VPN unused routing target value to import and export routing targets of PE nodes at the UPE level; and /or, the fifth application module 58 is configured to apply the B VPN unused route target values to the import and export route targets of the PE nodes at the NPE level.

Fig. 6 is a structural block diagram (four) of a routing object processing device according to an embodiment of the present invention. As shown in Fig. 6, the networking is an H-L3VPN networking, and the PE nodes at the UPE level are connected to the PE nodes at the NPE level , and when the PE nodes at the NPE level have PE nodes with an FRR master-backup relationship, the device includes: a third statistics module 62, which is used to count the number of PE nodes at the UPE level as C, where C is a natural number; the fourth Statistical module 64, used to count PE nodes with FRR active/standby relationship as D pairs, wherein D is a natural number; the fourth generation module 66 is used to generate C+D unused routing target values of VPN; the sixth application module 68. It is used to apply a routing target value not used by VPN to the import and export routing target of the PE node of the UPE layer that has not formed the FRR master-backup relationship; and/or, the seventh application module 70 is used to use the C+ D VPN unused routing target values are applied to the import and export routing targets of the PE nodes of the NPE layer that do not form the FRR active-standby relationship; and/or, the eighth application module 72 is used to apply the two VPN unused routes The target value is applied to the import and export routing target of the PE node of the UPE layer forming the FRR active-standby relationship; and/or, the ninth application module 74 is used to apply the unused routing target value of C+D-1 VPN to The import and export routing targets of the PE nodes at the NPE layer that form the FRR active/standby relationship.

It should be noted that each of the above-mentioned modules can be implemented by software or hardware. For the latter, it can be implemented in the following manner, but not limited to this: the above-mentioned modules are all located in the same processor; or, the above-mentioned modules are respectively located in multiple in the processor.

The embodiment of the invention also provides a storage medium. Optionally, in this embodiment, the above-mentioned storage medium may be configured to store program codes for performing the following steps:

S1, generating an unused routing target value of the virtual private network VPN;

S2. Apply the unused route target value of the VPN to the import and export route targets of all PE nodes of the operator's edge equipment under the network.

Optionally, in this embodiment, the above-mentioned storage medium may include but not limited to: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk Various media that can store program codes such as discs or optical discs.

Optionally, in this embodiment, the processor executes the above S1 and S2 according to the program code stored in the storage medium.

Optionally, for specific examples in this embodiment, reference may be made to the examples described in the foregoing embodiments and optional implementation manners, and details are not repeated in this embodiment.

The method for automatically publishing routing targets of L3vpn services described in the optional embodiments of the present invention refers to that the network management system automatically generates required import and export routing target values according to different networking and FRR protection relationships between PE nodes. The technical solution of this optional embodiment is divided into three scenarios:

1. FullMesh networking scenario

FullMesh networking is a fully connected networking scenario. In this scenario, all nodes are connected. Therefore, there is only one import and export routing target for all PE nodes in this scenario, and it is guaranteed to be unique on the entire network.

Invention points:

1) Obtain the information of all PE nodes in the FullMesh network.

2) Verify the connectivity of the PE nodes, and prompt the user to handle if there are isolated PE nodes.

3) Generate an unused route target value.

4) Apply this route target value to the import and export route targets of all PE nodes.

Fig. 7 is a FullMesh scene routing target release diagram according to an embodiment of the present invention, as shown in Fig. 7, including the following steps:

Step S702, traversing the PEs, starting from PE1;

Step S704, judging whether it is an isolated node, if the judgment result is yes, execute step S716, and if the judgment result is no, execute step S706;

Step S706, obtaining available routing target values;

Step S708, judging whether there is an available target value, if the judgment result is yes, execute step S708, and if the judgment result is no, execute step S716,

Step S710, setting import and export routing targets;

Step S712, traversing the next PE node;

Step S714, judging whether there are unconfigured nodes, if the judging result is yes, go to step S702, and if the judging result is no, go to step S716;

Step S716, end.

2. FullMesh FRR networking scenario

In the FullMesh Fast Reroute (FullMesh FRR for short) networking scenario, the active and standby FRR nodes are isolated from each other, that is, the routing target of the active node PE does not need to be advertised to the standby node PE. Similarly, the routing target of the PE of the standby node does not need to be the PE of the active node at the release level, so each pair of active and standby FRR nodes needs two routing target values. In the networking, if there are N pairs of active and standby FRR relationships, 2N routing target values are required.

Invention points:

1) Retrieve N pairs of active and standby FRR relationships in the networking scenario.

2) The application generates 2N unused routing target values.

3) Advertise 2N routing target values on the imported and exported routes on the PE nodes that do not form the FRR active/standby relationship.

4) For the PE nodes forming the FRR master/standby relationship, the import and export routes publish all values except the values corresponding to the paired PEs.

Fig. 8 is a FullMesh FRR scenario routing target publishing diagram according to an embodiment of the present invention, as shown in Fig. 8, including the following steps:

Step S802, obtaining N FRR relationship pairs;

Step S804, obtaining 2N available routing target values;

Step S806, traversing the PEs, starting from PE1;

Step S808, judging whether it is an isolated node, if the judging result is no, go to step S810, and if the judging result is yes, go to step S818;

Step S810, judging whether it is a FRR relationship node;

Step S812, setting import and export routing targets;

Step S814, traversing the next PE node;

Step S816, judging whether there are unconfigured nodes, if the judging result is yes, go to step S806, and if the judging result is no, go to step S818;

Step S818, end.

3. H-L3VPN networking scenario

In a hierarchical L3VPN (Hierarchy of Lay 3VPN, H-L3VPN for short) scenario, the node types are divided into two levels, that is, PE nodes at the NPE level and nodes at the UPE level. If the UPE is connected to the NPE without FRR active/standby access, each UPE is assigned a routing target value, and the UPE is only configured with the RT value in the import/export direction, and all NPEs are configured with all route target values in the import/export direction ; If the UPE is connected to the NPE and the active/standby connection is performed, the UPE is assigned two routing target values, the connected NPE is only configured with one of the values, and the UPE is configured with both. The values assigned by other UPEs are configured on non-access NPEs.

Invention points:

1) Retrieve that in the networking scenario, there are N UPE nodes.

2) Retrieve whether there is an FRR active-standby relationship between UPE and NPE nodes in the networking scenario.

3) If there is no FRR master-backup relationship between UPE nodes and NPE nodes, there are N UPE nodes.

4) The application generates N unused routing target values.

5) Each UPE node publishes a route target value in the route import and export direction, and the NPE node publishes N route target values in the route import and export direction.

6) If there is an FRR master-backup relationship between the UPE node and the NPE node, there are N UPE nodes. There are M active and standby FRR relationships.

7) The application generates N+M unused routing target values.

8) The UPE node that has not formed the FRR master/standby relationship publishes a route target value in the route import and export direction.

9) The NPE nodes that have not formed the FRR master-standby relationship publish N+M routing target values in the direction of drop import and export.

9) The UPE nodes forming the FRR active/standby relationship publish two routing target values in the route import/export direction.

10) The NPE nodes forming the FRR active/standby relationship publish N+M-1 routing target values in the route import/export direction.

Fig. 9 is an H-L3VPN scenario routing target release diagram according to an embodiment of the present invention, as shown in Fig. 9, including the following steps:

Step S902, obtaining N UPE nodes;

Step S904, acquiring M FRR relationship pairs;

Step S906, obtaining N+M available routing target values;

Step S908, traverse all PEs, starting from PE1;

Step S910, judging whether it is an isolated node, if the judging result is no, go to step S912, and if the judging result is yes, go to step S922;

Step S912, judging whether it is a FRR relationship node;

Step S914, judging whether it is a UPE node;

Step S916, setting import and export routing targets;

Step S918, traversing the next PE node;

Step S920, judging whether there are unconfigured nodes, if the judging result is yes, go to step S908, and if the judging result is no, go to step S922;

Step S922, end.

A. FullMesh scene networking

Figure 10 is a network diagram of a FullMesh scenario according to an embodiment of the present invention. As shown in Figure 10, there are four PE nodes in the network, and each node is interconnected in pairs to form a fully connected network. The routing in this network Target value configuration requires only a unique route target value.

According to the FullMesh scene networking publishing algorithm, the configuration results after completion are as follows:

NE PE1:

Import export route target value: 1:1

Network element PE2:

Import export route target value: 1:1

Network element PE3:

Import export route target value: 1:1

Network element PE4:

Import export route target value: 1:1

B. Networking in FullMesh FRR scenarios

Figure 11 is a network diagram of a FullMesh FRR scenario according to an embodiment of the present invention. As shown in Figure 11, the network has 5 PE nodes in total, and the two upper PE (PE1 and PE2) nodes form an FRR master-backup relationship, that is, PE1 , PE3, PE4, and PE5 form a FullMesh network; PE2, PE3, PE4, and PE5 form a FullMesh network. Two routing target values are generated in the FullMeshFRR scenario. The final generated configuration routing target values are as follows:

Node PE1:

Import export route target value: 1:1

Node PE2:

import export route target value: 2:2

Node PE3:

Import and export routing target values: 1:1, 2:2

Node PE4:

Import and export routing target values: 1:1, 2:2

Node PE5:

Import and export routing target values: 1:1, 2:2

C. Networking in H-L3VPN scenarios

Figure 12 is a network diagram of an H-L3VPN scenario according to an embodiment of the present invention. As shown in Figure 12, the network has seven nodes in total, including four NPE nodes and three UPE nodes. NPE1 and NPE2 form the FRR master NPE3 and NPE4 form an active-standby FRR relationship. UPE1 connects to NPE1 and NPE2, UPE2 connects to NPE2 and NPE3, and UPE3 connects to NPE3 and NPE4. NPE1 and NPE2 are respectively connected to NPE3 and NPE4. According to the H-L3VPN scenario networking, N+M or 5 routing target values are generated. The final generated configuration routing target values are as follows:

Node UPE1:

Import and export routing target values: 1:1, 2:2

Node UPE2:

import export route target value: 3:3

Node UPE3:

Import export route target value: 4:4, 5:5

Node NPE1:

Import and export routing target values: 1:1, 3:3, 4:4, 5:5

Node NPE2:

Import and export routing target values: 2:2, 3:3, 4:4, 5:5

Node NPE3:

Import and export routing target values: 1:1, 2:2, 3:3, 4:4

Node NPE4:

Import and export routing target values: 1:1, 2:2, 3:3, 5:5

To sum up, the present invention provides users with a solution for efficiently publishing routing targets in various L3VPN networking scenarios. It is more convenient for service provisioning, and automatically releases the routing targets required by the service according to the current networking scenario.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices Alternatively, they may be implemented in program code executable by a computing device so that they may be stored in a storage device to be executed by a computing device, and in some cases in an order different from that shown here The steps shown or described are carried out, or they are separately fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present invention is not limited to any specific combination of hardware and software.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. a kind of route target processing method, it is characterised in that including：

The generation VPN untapped route target values of VPN；

The untapped route target values of the VPN are applied to all provider edge equipment PE nodes under networking Import and export route target.

2. method according to claim 1, it is characterised in that the generation VPN untapped route mesh of VPN Include before scale value：

Obtain the information of all PE nodes；

The node that all PE nodes are connection is determined according to described information.

3. method according to claim 1, it is characterised in that in the networking be the quick heavy-route FRR of FullMesh During networking, methods described includes：

The PE nodes that statistics has FRR main and standby relations are A pairs；

The 2A untapped route target value of VPN of generation；

The untapped route target values of 2A VPN are applied to not formed the PE nodes of FRR main and standby relations Import and export route target；And/or,

The route target value removed outside route target value corresponding with a PE nodes is applied to the 2nd PE nodes Import and export route target；Wherein, with the 2nd PE nodes there is the active and standby passes of FRR in a PE nodes System, A is natural number.

4. method according to claim 1, it is characterised in that in the networking be H-L3VPN networkings, user side The PE nodes of PE equipment UPE levels are linked into the PE nodes of network core PE equipment NPE levels, and described When the PE nodes of NPE levels do not exist the PE nodes of FRR main and standby relations, methods described includes：

The quantity for counting the PE nodes of the UPE levels is B, wherein, B is natural number；

The B untapped route target value of VPN of generation；

The PE nodes that one untapped route target value of VPN is applied to the UPE levels import and export road By target；And/or,

The importing of the PE nodes that the untapped route target values of B VPN are applied into the NPE levels is led Go out route target.

5. method according to claim 1, it is characterised in that in the networking be H-L3VPN networkings, UPE levels PE nodes be linked into the PE nodes of NPE levels, and the PE nodes of the NPE levels to there is FRR active and standby During the PE nodes of relation, methods described includes：

The quantity for counting the PE nodes of the UPE levels is C, wherein, C is natural number；

The PE nodes that statistics has FRR main and standby relations are D pairs, wherein, D is natural number；

The C+D untapped route target value of VPN of generation；

One untapped route target value of VPN is applied to not formed the UPE layers of FRR main and standby relations PE nodes import and export route target；And/or,

The untapped route target values of C+D VPN are applied to not formed the NPE of FRR main and standby relations The PE nodes of layer import and export route target；And/or,

Two untapped route target values of VPN are applied to be formed the UPE layers of FRR main and standby relations of PE Node imports and exports route target；And/or,

The C+D-1 untapped route target value of VPN is applied to be formed the NPE layers of FRR main and standby relations PE nodes import and export route target.

6. a kind of route target processing unit, it is characterised in that including：

First generation module, for generating the untapped route target values of VPN VPN；

First application module, for the untapped route target values of the VPN to be applied into all operations under networking Business edge device PE nodes import and export route target.

7. device according to claim 6, it is characterised in that described device also includes：

Acquisition module, the information for obtaining all PE nodes；

Determining module, for according to described information determine all PE nodes be connection node.

8. device according to claim 6, it is characterised in that when the networking is FullMesh FRR networkings, institute Stating device includes：

First statistical module, the PE nodes that there is FRR main and standby relations for counting are A pairs；

Second generation module, for generating the 2A untapped route target value of VPN；

Second application module, for the untapped route target values of 2A VPN to be applied to not form FRR The PE nodes of main and standby relation import and export route target；And/or,

3rd application module, for the route target outside route target value corresponding with a PE nodes will to be removed What value was applied to the 2nd PE nodes imports and exports route target；Wherein, a PE nodes and described second There is FRR main and standby relations in PE nodes, A is natural number.

9. device according to claim 6, it is characterised in that in the networking be H-L3VPN networkings, UPE levels PE nodes be linked into the PE nodes of NPE levels, and the PE nodes of the NPE levels do not exist FRR master During the PE nodes of standby relation, described device includes：

Second statistical module, the quantity of the PE nodes for counting the UPE levels is B, wherein, B is certainly So count；

3rd generation module, for generating the B untapped route target value of VPN；

4th application module, for a untapped route target value of VPN to be applied into the UPE levels PE nodes import and export route target；And/or,

5th application module, it is described NPE layers for the untapped route target values of B VPN to be applied to Secondary PE nodes import and export route target.

10. device according to claim 6, it is characterised in that in the networking be H-L3VPN networkings, UPE levels PE nodes be linked into the PE nodes of NPE levels, and the PE nodes of the NPE levels to there is FRR active and standby During the PE nodes of relation, described device includes：

3rd statistical module, the quantity of the PE nodes for counting the UPE levels is C, wherein, C is certainly So count；

, there is the PE nodes of FRR main and standby relations for counting for D pairs in the 4th statistical module, wherein, D is certainly So count；

4th generation module, for generating the C+D untapped route target value of VPN；

6th application module, for being applied to not form FRR active and standby by a untapped route target value of VPN The PE nodes of the UPE layers of relation import and export route target；And/or,

7th application module, for the untapped route target values of C+D VPN to be applied to not form FRR The PE nodes of the NPE layers of main and standby relation import and export route target；And/or,

8th application module, for being applied to form the active and standby passes of FRR by two untapped route target values of VPN The PE nodes of the UPE layers of system import and export route target；And/or,

9th application module, for the C+D-1 untapped route target value of VPN to be applied to form FRR master Route target is imported and exported for the NPE layers of relation of PE nodes.