CN108521377B

CN108521377B - Route publishing method and device

Info

Publication number: CN108521377B
Application number: CN201810673020.3A
Authority: CN
Inventors: 陈岩; 王伟
Original assignee: New H3C Technologies Co Ltd Hefei Branch
Current assignee: New H3C Technologies Co Ltd Hefei Branch
Priority date: 2018-06-26
Filing date: 2018-06-26
Publication date: 2020-11-03
Anticipated expiration: 2038-06-26
Also published as: CN108521377A

Abstract

The present disclosure relates to a method and a device for issuing a route, wherein the method comprises the following steps: obtaining the extended community attribute RT information of each PE device from each service provider network edge PE device connected with RR, wherein the RT information comprises an incoming direction extended community attribute IRT and an outgoing direction extended community attribute ERT; and sending a target IRT matched with the ERT to the PE device corresponding to the ERT so that the PE device corresponding to the ERT determines a route to be issued according to the target IRT. Therefore, the PE device corresponding to the ERT may determine the route to be issued according to the target IRT, that is, the PE device corresponding to the ERT automatically uses the target IRT as the RT filtering policy, and thus, compared with the prior art in which the RT filtering policy needs to be manually configured on the source-end PE device, the present disclosure automatically sets the RT filtering policy without manually configuring the RT filtering policy, and is flexible in operation and good in user experience.

Description

Route publishing method and device

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for routing advertisement.

Background

MPLS (Multi-Protocol Label Switching) L3VPN (Layer3Virtual Private Network) is an L3VPN technology of PE (Provider Edge) devices, which uses BGP (Border Gateway Protocol) RT (Route Target) to control the distribution of VPN routes.

VPN instances on PE devices have two types of RT attributes: ERT (Export Route Target, outbound direction extended community attribute) and IRT (Import Route Target, inbound direction extended community attribute). After learning an IPv4 route from a Site connected with the local PE device, the local PE device converts the IPv4 route into a VPN-IPv4 route, sets ERT for the VPN-IPv4 route and issues the VPN-IPv4 route carrying the ERT to other PE devices. When receiving the VPN-IPv4 routes issued by other PE devices, the PE devices check ERT carried by the VPN-IPv4 routes, and when the ERT is matched with the IRT attribute of the VPN instance on the PE devices, the PE devices add the VPN-IPv4 routes into the routing table of the VPN instance.

In order to reduce IBGP (Internal BGP) full connectivity, an RR (Route Reflector) is introduced into a BGP L3VPN networking, and thus, a BGP L3VPN networking includes three components: CE (customer edge) device, PE device, and RR, where the RR establishes BGP with the PE device. However, the introduction of RRs to BGP L3VPN networking results in a large number of routes on the RRs.

In order to reduce the routes on the RR, an RT filtering policy needs to be manually configured on the source PE device, and route filtering is completed when the source PE device sends a route to the RR, so that the number of routes sent by the source PE device to the RR can be reduced.

For example, fig. 1 is a schematic diagram of a BGP L3VPN networking. As shown in fig. 1, the networking includes CE1, CE2, CE3, CE4, PE1, PE2, PE3, and RR. The PE1 is provided with VPN1 and VPN2, and the ERT of the VPN1 is 200:1, ERT of VPN2 is 300: 1, a VPN3 is configured on PE2, and the IRT of VPN3 is 200:1, a VPN4 is configured on PE3, and the IRT of VPN4 is 100: 1.

to reduce routing on the RR, an IRT of 100 needs to be manually configured on PE 1: 1 and 200: 1. With this RT filtering strategy, PE1 only sends RR with ERT of 100: 1 or ERT of 200: route 1, since the ERT of VPN1 is 200:1 and ERT of VPN2 is 300: 1, therefore, PE1 only sends routing information carrying the routing information issued by CE1 to RR with ERT 200: VPN1 route of 1, but not sending route information with the issuance of CE2 to RR and ERT 300: VPN2 route of 1.

However, since the RT filtering policy needs to be manually configured on the source PE device, the operation is not flexible and the user experience is poor.

Disclosure of Invention

In view of this, the present disclosure provides a route distribution method and apparatus.

According to a first aspect of the present disclosure, there is provided a route publishing method applied to a route reflector RR, the method including:

obtaining the extended community attribute RT information of each PE device from each service provider network edge PE device connected with RR, wherein the RT information comprises an incoming direction extended community attribute IRT and an outgoing direction extended community attribute ERT;

and sending a target IRT matched with the ERT to the PE device corresponding to the ERT so that the PE device corresponding to the ERT determines a route to be issued according to the target IRT.

According to a second aspect of the present disclosure, there is provided a route distribution method applied to a source service provider network edge PE device, the method including:

receiving a target entering direction extended community attribute IRT sent by a route reflector RR;

and when the route is to be issued, determining the route to be issued in the route according to the target IRT and the ERT carried by the route.

According to a third aspect of the present disclosure, there is provided a route issuing device applied to a route reflector RR, the device including:

an obtaining module, configured to obtain, from each service provider network edge PE device connected to the RR, extended community attribute RT information of each PE device, where the RT information includes an ingress extended community attribute IRT and an egress extended community attribute ERT;

a first sending module, configured to send a target IRT matched with the ERT to the PE device corresponding to the ERT, so that the PE device corresponding to the ERT determines a route to be issued according to the target IRT.

According to a fourth aspect of the present disclosure, there is provided a route distribution apparatus applied to a source service provider network edge PE device, the apparatus including:

a receiving module, configured to receive a target entry direction extended community attribute IRT sent by a route reflector RR;

and the determining module is used for determining the to-be-issued route in the routes according to the target IRT and the ERT carried by the routes when the routes are to be issued.

The technical scheme provided by the disclosure can comprise the following beneficial effects: the PE device corresponding to the ERT may determine the route to be issued according to the target IRT received from the RR, that is, the PE device corresponding to the ERT automatically uses the target IRT as the RT filtering policy, and thus, compared with the prior art in which the RT filtering policy needs to be manually configured on the source-side PE device, the present disclosure automatically sets the RT filtering policy without manually configuring the RT filtering policy, and is flexible in operation and good in user experience.

And the RR determines the device to which the route is to be sent according to the ERT carried by the route received from the PE device corresponding to the ERT and the recorded correspondence between the IRT and the PE device, and sends the route to the determined device, so that compared with the prior art in which the RR issues routes to all the PE devices connected to the RR except the PE device that sends the route, the RR can accurately control the issuance of the route, and reduce the route issuance pressure of the RR.

In addition, compared with the prior art that the RR issues the route to all the PE devices connected to the RR except the PE device sending the route, the RR directly forwards the route according to the address carried by the received route, so that the RR issues the route only to the PE device whose address is the address carried by the received route, the RR can accurately control the issue of the route and relieve the route issue pressure of the RR, and the RR does not need to perform processing for determining the device to which the route to be issued is to be sent, thereby relieving the processing pressure of the RR.

In addition, the RR performs deduplication processing on the determined target IRT, and sends the deduplicated target IRT to the PE device, so that link bandwidth resources can be saved.

Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

Fig. 1 is a schematic diagram of a BGP L3VPN networking.

Fig. 2 is a schematic diagram of a BGP L3VPN networking.

Fig. 3 is a flow diagram illustrating a method of route publication in accordance with an exemplary embodiment.

Fig. 4 is a flow diagram illustrating a method of route publication in accordance with an exemplary embodiment.

Fig. 5 is a flow diagram illustrating a method of route publication in accordance with an exemplary embodiment.

Fig. 6 is a flow diagram illustrating a method of route publication in accordance with an example embodiment.

Fig. 7 is a block diagram illustrating a route distribution apparatus according to an example embodiment.

Fig. 8 is a block diagram illustrating a route distribution apparatus according to an example embodiment.

Fig. 9 is a block diagram illustrating a route distribution apparatus according to an example embodiment.

Fig. 10 is a block diagram illustrating a route distribution apparatus according to an example embodiment.

Fig. 11 is a block diagram illustrating a hardware configuration of a route distribution apparatus according to an exemplary embodiment.

Detailed Description

Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers can indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.

Fig. 2 is a schematic diagram of a BGP L3VPN networking. As shown in fig. 2, the networking includes CE1, CE2, CE3, CE4, CE5, PE1, PE2, PE3, PE4, and RR. CE1 and CE2 are respectively connected with PE1, CE3 is connected with PE2, CE4 is connected with PE3, CE5 is connected with PE4, CE1 issues a route of 1.1.1.1/32, and CE2 issues a route of 2.2.2.2/32. The PE1 is provided with VPN1 and VPN2, and the ERT of the VPN1 is 200:1, ERT of VPN2 is 300: 1. the PE2 is provided with a VPN3, and the IRT of the VPN3 is 200: 1. the PE3 is provided with a VPN4, and the IRT of the VPN4 is 100: 1. the PE4 is provided with a VPN5, and the IRT of the VPN5 is 200: 1. the routes that the PE1 can publish include routes with route information of 1.1.1.1/32 and ERT of 200: route 1 for 1, and 2.2.2.2/32 for route information and 300 for ERT: route 2 of 1.

Fig. 3 shows a flow chart of a route distribution method according to an embodiment of the present disclosure. The route distribution method may be applied to the route reflector RR. For convenience of explanation, the following description will be given by taking the networking shown in fig. 2 as an example. As shown in fig. 3, the route distribution method may include the following steps.

In step S320, extended community attribute RT information of each PE device is obtained from each service provider network edge PE device connected to the RR, where the RT information includes an ingress extended community attribute IRT and an egress extended community attribute ERT.

In this embodiment, the RR may obtain RT information of each PE device connected to the RR in the following manner: the RR obtains the RT information of each PE device by sending a message for obtaining the RT information of the PE device to each PE device connected thereto. Specifically, the RR sends a message for acquiring the RT information of the PE device to each PE device connected to the RR, and each PE device sends its own RT information to the RR when receiving the message. In another implementation, each PE device may send its own RT information to the RR within a predetermined period. Specifically, when RT information of each PE device is changed, each PE device transmits the changed RT information to the RR.

In an implementation manner, the PE device may send its own RT information to the RR by sending a route-refresh (route-refresh) message to the RR, where the route-refresh message carries the RT information of the PE device. Therefore, compared with the route refresh packet in the prior art, the route refresh packet of this embodiment carries the RT information of the PE device. Certainly, the route refresh packet also carries an identifier of the PE device, and thus, the RR determines, according to the identifier carried by the route refresh packet, which PE device the route refresh packet is sent by. One or more VPNs may be configured on the PE device and an IRT or ERT may be configured for each VPN. The IRT or ERT configured for each VPN may be the same or different.

For example, for the networking shown in fig. 2, PE1 sends a packet carrying id PE1 and ERT 200 to RR: 1 and ERT 300: 1, PE2 sends a route refresh message carrying a flag as PE2 and an IRT of 200 to RR: 1, PE3 sends a route refresh message carrying a flag as PE3 and an IRT of 100 to RR: 1, PE4 sends a route refresh message carrying a flag as PE2 and an IRT of 200 to RR: 1, and refreshing the message by the route.

In step S340, a target IRT matched with the ERT is sent to the PE device corresponding to the ERT, so that the PE device corresponding to the ERT determines a route to be issued according to the target IRT.

In this embodiment, after the RR acquires the RT information of each PE device, the RR matches an ERT in the RT information with an IRT in the RT information, determines the IRT matched with the ERT as a target IRT, and sends the determined target IRT to a PE device corresponding to the ERT (the PE device corresponding to the ERT may be referred to as a source-end PE device). For example, the RR may send a route refresh packet carrying the target IRT to the PE device corresponding to the ERT, so as to send the target IRT to the PE device corresponding to the ERT.

For example, for the networking shown in fig. 2, RRs are respectively acquired from PE1 to PE4 to ERT 200: 1. ERT 300: 1. IRT 200: 1. IRT 200:1 and IRT 100: 1, therefore RR compares ERT 200:1 and IRT 200: 1. IRT 200:1 and IRT 100: 1, and ERT 300: 1 and IRT 200: 1. IRT 200:1 and IRT 100: 1, found to match ERT 200: the IRT for 1 match is 200:1, therefore RR determines that IRT 200:1 is the target IRT. Thus, RR to ERT 200: the PE device corresponding to 1, that is, PE1, sends a packet carrying target IRT 200:1, and refreshing the message by the route.

In a first implementation manner, the PE device corresponding to the ERT may determine the route to be issued according to the following manner: and the PE device corresponding to the ERT matches the ERT in the routes which can be issued with the target IRT, and determines the route of which the ERT is matched with the target IRT as the route to be issued. Illustratively, for the networking shown in fig. 2, a target IRT200 is received at PE1 from an RR: after 1, PE1 compares target IRT 200:1 and ERT 200:1 and ERT 300: 1, since the target IRT 200:1 with ERT 200:1 match, so PE1 only determines route 1 as the route to be issued.

In a second implementation manner, the PE device corresponding to the ERT may determine the route to be issued according to the following manner: and the PE device corresponding to the ERT directly determines the routes corresponding to the RT information and the target IRT in the routes which can be issued as the routes to be issued without matching the target IRT with the ERT. Illustratively, for the networking shown in fig. 2, a target IRT200 is received at PE1 from an RR: after 1, PE1 determines its RT information to include 200:1 and 300: 1, PE1 will directly include RT information as 200: route 1 of 1 is determined as the route to be issued.

Therefore, in this embodiment, the RR collects RT information of each PE device connected to the RR, and sends a target IRT matched with the ERT to the PE device corresponding to the ERT, so that the PE device corresponding to the ERT may determine a route to be issued according to the received target IRT, that is, the PE device corresponding to the ERT automatically uses the target IRT as an RT filtering policy.

In an implementation manner, the route publishing method may further include the following steps:

performing a deduplication process on the target IRT, wherein the deduplication process is used to remove duplicate target IRTs,

correspondingly, step S340 may specifically include:

and sending the target IRT subjected to the deduplication processing to the PE equipment corresponding to the ERT.

In this embodiment, after the RR determines the target IRT, the RR may remove the repeated target IRT, and send the target IRT after removing the repeated target IRT to the PE device corresponding to the ERT. Therefore, the RR can be prevented from sending the same target IRT to the PE device corresponding to the ERT, the information sent by the RR to the PE device corresponding to the ERT can be reduced, and therefore link bandwidth resources can be saved.

For example, for the networking shown in fig. 2, the RR acquires the target IRT 200:1 and IRT 200:1, RR performs deduplication processing on the two target IRTs, where the target IRT after deduplication processing is 200:1, RR sends PE1 that the carrying identifier is RR and IRT is 200:1 and 100: 1, thereby sending to PE1 a packet carrying the identifier RR and having an IRT of 200, compared to the RR: 1 and 200:1, link bandwidth resources can be saved.

Fig. 4 shows a flow chart of a route publishing method according to an embodiment of the present disclosure. The route distribution method may be applied to the route reflector RR. For convenience of explanation, the following description will be given by taking the networking shown in fig. 2 as an example. As shown in fig. 4, the route distribution method may include the following steps.

In step S410, extended community attribute RT information of each PE device is obtained from each service provider network edge PE device connected to the RR, where the RT information includes an ingress extended community attribute IRT and an egress extended community attribute ERT.

In step S420, a target IRT matched with the ERT is sent to the PE device corresponding to the ERT, so that the PE device corresponding to the ERT determines a route to be issued according to the target IRT.

For the description of steps S410 and S420, reference may be specifically made to the foregoing detailed description of steps S320 and S340, which is not described herein again.

In step S430, the route to be issued is received from the PE device corresponding to the ERT, and the route to be issued carries the ERT.

In this embodiment, after the RR sends the target IRT to the PE device corresponding to the ERT, the PE device corresponding to the ERT determines the route to be issued according to the target IRT and sends the determined route to the RR, so that the RR may receive the route to be issued from the PE device corresponding to the ERT.

In step S440, the device to which the to-be-issued route is to be sent is determined according to the recorded correspondence between the IRT and the PE device and the ERT carried by the to-be-issued route.

In one implementation, step S440 may specifically include: and matching the ERT carried by the route to be issued with the IRT in the recorded corresponding relation, and determining the PE device corresponding to the IRT matched with the ERT carried by the route to be issued in the corresponding relation as the device to be sent by the route to be issued.

In one implementation, before step S440, the route publishing method may further include the following steps: and generating and recording a mapping table of the PE equipment and the IRT according to the obtained IRT, wherein each table item of the mapping table represents the corresponding relation between the IRT of each PE equipment and each PE equipment.

In this embodiment, after the RR acquires the RT information of each PE device, the RR further acquires an identifier of each PE device. That is, the RR can acquire the IRT and the identifier of each PE device. Thus, the RR generates a mapping table according to the acquired IRT and the identifier, and records the mapping table. And the RR takes the determined identifier and the corresponding IRT as an item of the mapping table.

For example, for the networking shown in fig. 2, the RR may generate a mapping table shown in table 1 below.

TABLE 1 mapping table

IRT 200：1	PE2
		IRT100：1	PE3
IRT 200：1	PE4

For the networking shown in fig. 2, the RR receives a route 1 carrying ERT 200:1 sent by PE1, and the RR respectively matches ERT 200:1 with IRT200 in table 1: 1. IRT 100: 1 and IRT 200:1, and RR finds that ERT 200:1 matches IRT 200:1 match, so the RR determines PE2 and PE4 as the devices to which route 1 is to be sent.

In step S450, the route to be issued is sent to the determined device.

Therefore, in this embodiment, the RR determines, according to the ERT carried by the route received from the PE device corresponding to the ERT and the recorded correspondence between the IRT and the PE device, the device to which the route is to be sent, and sends the route to the determined device, so that, compared with the prior art in which the RR issues routes to all PE devices connected to the RR except the PE device that sends the route, the present disclosure issues routes only to the PE device determined according to the ERT carried by the route, the RR can accurately control the issuance of the route, and reduce the route issuance pressure of the RR.

Fig. 5 shows a flow chart of a route publishing method according to an embodiment of the present disclosure. The route distribution method may be applied to the route reflector RR. For convenience of explanation, the following description will be given by taking the networking shown in fig. 2 as an example. As shown in fig. 5, the route distribution method may include the following steps.

In step S510, extended community attribute RT information of each PE device is obtained from each service provider network edge PE device connected to the RR, where the RT information includes an ingress extended community attribute IRT and an egress extended community attribute ERT.

For the description of step S510, reference may be specifically made to the foregoing detailed description of step S320, which is not repeated herein.

In step S520, a target IRT matched with the ERT and an address of the PE device corresponding to the target IRT are sent to the PE device corresponding to the ERT.

In this embodiment, the RR may send the target IRT and the address of the PE device corresponding to the target IRT to the PE device corresponding to the ERT.

In step S530, the route to be issued is received from the PE device corresponding to the ERT, and the route to be issued carries the address.

In this embodiment, after the RR sends the target IRT and the address of the PE device corresponding to the target IRT to the PE device corresponding to the ERT, the PE device corresponding to the ERT determines the route to be issued according to the target IRT, determines the address of the device to which the route to be issued is sent according to the address of the PE device corresponding to the target IRT, and sends the determined route to the RR with the address of the PE device corresponding to the target IRT in the route.

In step S540, the route to be issued is forwarded according to the address.

In this embodiment, the RR may send the route to be issued to the PE device whose address is carried by the route.

Therefore, in this embodiment, compared with the prior art in which the RR issues a route to all PE devices connected to the RR, except for the PE device that sends the route, the RR forwards the route directly according to the address carried by the received route, so that the RR issues a route only to the PE device whose address is the address carried by the received route, the RR can accurately control the issuance of the route, and the route issuance pressure of the RR is reduced, and the RR does not need to perform processing for determining a device to which the route to be issued is to be sent, thereby reducing the processing pressure of the RR.

Fig. 6 is a flowchart illustrating a route distribution method that may be applied to an edge PE device of a source service provider network according to an example embodiment. For convenience of explanation, the following description will be given by taking the networking shown in fig. 2 as an example. As shown in fig. 6, the route distribution method may include the following steps.

In step S620, the target entry direction extended community attribute IRT sent by the route reflector RR is received.

In step S640, when a route is to be issued, the route to be issued in the routes is determined according to the target IRT and the ERT carried by the route.

For the description of step S620 and step S640, reference may be specifically made to the foregoing detailed description of step S320 and step S340, which is not described herein again.

Therefore, in this embodiment, the source PE device receives the target IRT sent by the RR, and determines the route to be issued according to the received target IRT, that is, the source PE device automatically uses the received target IRT as the RT filtering policy, so compared with the prior art that the RT filtering policy needs to be manually configured on the source PE device, the present disclosure automatically sets the RT filtering policy without manually configuring the RT filtering policy, and is flexible in operation and good in user experience.

In one implementation, the address of the PE device corresponding to the target IRT sent by the RR is also received,

the method further comprises the following steps:

and sending the route to be issued to RR, wherein the route to be issued carries the address of the PE device corresponding to the target IRT.

For a specific description, reference may be made to the detailed description of steps S520 to S530, which is not described herein again.

Therefore, in this embodiment, the source PE device sends the first route to be issued and the address of the PE device corresponding to the target IRT to the RR, so that, compared with the prior art where the RR issues routes to all PE devices connected to the source PE device except the PE device that sends the route, the RR forwards the route directly according to the address carried by the received route, and thus, the RR issues routes only to the PE devices whose addresses are the addresses carried by the received route, the RR can accurately control the issuance of the route, and the RR relieves the routing pressure of the RR, and the RR does not need to perform processing for determining the device to which the route to be issued is to be sent, and relieves the processing pressure of the RR.

Fig. 7 is a block diagram illustrating a route distribution apparatus according to an example embodiment. The route distribution device may be applied to the route reflector RR. As shown in fig. 7, the route distribution apparatus 700 may include an obtaining module 710 and a first sending module 730.

The obtaining module 710 is configured to obtain, from each service provider network edge PE device connected to the RR, extended community attribute RT information of each PE device, where the RT information includes an ingress extended community attribute IRT and an egress extended community attribute ERT. The first sending module 730 is connected to the obtaining module 710, and configured to send a target IRT matched with the ERT to the PE device corresponding to the ERT, so that the PE device corresponding to the ERT determines a route to be issued according to the target IRT.

In one implementation, the route issuing apparatus 700 may further include:

a deduplication processing module (not shown) configured to perform deduplication processing on the target IRT, wherein the deduplication processing is configured to remove duplicate target IRTs,

the first sending module 730 is configured to: and sending the target IRT subjected to the deduplication processing to the PE equipment corresponding to the ERT.

Fig. 8 is a block diagram illustrating a route distribution apparatus according to an example embodiment. The route distribution device may be applied to the route reflector RR. As shown in fig. 8, the route distribution apparatus 800 may include an obtaining module 810, a first sending module 830, a receiving module 850, a determining module 870, and a second sending module 890.

The obtaining module 810 is configured to obtain, from each service provider network edge PE device connected to the RR, extended community attribute RT information of each PE device, where the RT information includes an ingress extended community attribute IRT and an egress extended community attribute ERT. The first sending module 830 is connected to the obtaining module 810, and is configured to send a target IRT matched with the ERT to the PE device corresponding to the ERT, so that the PE device corresponding to the ERT determines a route to be issued according to the target IRT. The receiving module 850 is configured to receive the route to be issued from the PE device corresponding to the ERT, where the route to be issued carries the ERT. The determining module 870 is connected to the receiving module 850, and configured to determine, according to the recorded correspondence between the IRT and the PE device and the ERT carried by the route to be issued, a device to which the route to be issued is to be sent. The second sending module 890 is connected to the determining module 870, and is configured to send the to-be-issued route to the determined device.

In one implementation, the determination module 870 is configured to:

matching the ERT carried by the route to be issued with the IRT in the corresponding relation, and determining the PE device corresponding to the IRT matched with the ERT carried by the route to be issued in the corresponding relation as the device to be sent by the route to be issued.

In one implementation, the route distribution apparatus 800 may further include:

a generating and recording module (not shown) configured to generate and record a mapping table between the PE devices and the IRT according to the obtained IRT, where each entry of the mapping table represents a corresponding relationship between the IRT of each PE device and each PE device itself.

Fig. 9 is a block diagram illustrating a route distribution apparatus according to an example embodiment. The route distribution device may be applied to the route reflector RR. As shown in fig. 9, the route distribution apparatus 900 may include an obtaining module 910, a first sending module 930, a receiving module 950, and a forwarding module 970.

The obtaining module 910 is configured to obtain, from each service provider network edge PE device connected to the RR, extended community attribute RT information of each PE device, where the RT information includes an ingress extended community attribute IRT and an egress extended community attribute ERT. The first sending module 930 is connected to the obtaining module 910, and configured to send the target IRT and the address of the PE device corresponding to the target IRT to the PE device corresponding to the ERT. The receiving module 950 is configured to receive the route to be issued from the PE device corresponding to the ERT, where the route to be issued carries the address. The forwarding module 970 is connected to the receiving module 950, and is configured to forward the route to be issued according to the address.

Fig. 10 is a block diagram illustrating a route distribution apparatus according to an example embodiment. The route issuing device can be applied to the source service provider network edge PE equipment. As shown in fig. 10, the route distribution apparatus 1000 may include a receiving module 1010 and a determining module 1030. The receiving module 1010 is configured to receive a message sent by the route reflector RR and carrying the target entry direction extended community attribute IRT. The determining module 1030 is connected to the receiving module 1010, and configured to determine, when a route is to be issued, the route to be issued in the route according to the target IRT and the ERT carried by the route.

In a possible implementation manner, the receiving module 1010 further receives an address of a PE device corresponding to the target IRT,

accordingly, the route distribution apparatus 1000 may further include:

a sending module (not shown) configured to send the route to be issued to the RR, where the route to be issued carries an address of the PE device corresponding to the target IRT.

With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Fig. 11 is a block diagram illustrating a hardware configuration for a route issuing apparatus 1100 according to an exemplary embodiment. Referring to fig. 11, the apparatus 1100 may include a processor 901, a machine-readable storage medium 902 having stored thereon machine-executable instructions. The processor 901 and the machine-readable storage medium 902 may communicate via a system bus 903. Also, the processor 901 performs the route distribution method described above by reading machine executable instructions in the machine readable storage medium 902 corresponding to the route distribution logic.

The machine-readable storage medium 902 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.

Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein were chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the techniques in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A route publishing method applied to a route reflector RR is characterized by comprising the following steps:

obtaining the extended community attribute RT information of each PE device from each service provider network edge PE device connected with RR, wherein the RT information comprises an incoming direction extended community attribute IRT and an outgoing direction extended community attribute ERT; and

respectively matching ERT in the RT information with IRT in the RT information, and determining the IRT matched with the ERT as a target IRT;

2. The route distribution method according to claim 1, further comprising:

receiving the to-be-issued route from the PE device corresponding to the ERT, wherein the to-be-issued route carries the ERT;

determining the device to which the to-be-issued route is to be sent according to the recorded corresponding relation between the IRT and the PE device and the ERT carried by the to-be-issued route;

and sending the route to be issued to the determined equipment.

3. The route publishing method according to claim 2, wherein determining, according to the recorded correspondence between the IRT and the PE device and the ERT carried by the route to be published, a device to which the route to be published is to be sent, comprises:

4. The route distribution method according to claim 2, further comprising:

and generating and recording a mapping table of the PE equipment and the IRT according to the obtained IRT, wherein each table entry of the mapping table represents the corresponding relation between the IRT of each PE equipment and each PE equipment.

5. The route distribution method according to claim 1,

sending a target IRT matched with the ERT to the PE device corresponding to the ERT, wherein the target IRT comprises: sending the target IRT and the address of the PE device corresponding to the target IRT to the PE device corresponding to the ERT,

the method further comprises the following steps:

receiving the to-be-issued route from the PE device corresponding to the ERT, wherein the to-be-issued route carries the address;

and forwarding the route to be issued according to the address.

6. The route distribution method according to any one of claims 1 to 5, further comprising:

sending a target IRT matched with the ERT to the PE device corresponding to the ERT, wherein the target IRT comprises:

7. A route distribution method is applied to a source service provider network edge (PE) device, and is characterized by comprising the following steps:

the target IRT is determined by the RR by: obtaining the extended community attribute RT information of each PE device from each service provider network edge PE device connected with RR, wherein the RT information comprises an incoming direction extended community attribute IRT and an outgoing direction extended community attribute ERT; respectively matching ERT in the RT information with IRT in the RT information, and determining the IRT matched with the ERT as a target IRT; the PE receiving the target IRT is a PE device corresponding to an ERT matched with the target IRT;

8. The route distribution method according to claim 7,

also receives the address of the PE device corresponding to the target IRT sent by the RR,

the method further comprises the following steps:

9. A route issuing device applied to a route reflector RR is characterized by comprising:

an obtaining module, configured to obtain, from each service provider network edge PE device connected to the RR, extended community attribute RT information of each PE device, where the RT information includes an ingress extended community attribute IRT and an egress extended community attribute ERT; and

the matching module is used for respectively matching the ERT in the RT information with the IRT in the RT information and determining the IRT matched with the ERT as a target IRT;

10. The route distribution apparatus according to claim 9, further comprising:

a receiving module, configured to receive the to-be-issued route from the PE device corresponding to the ERT, where the to-be-issued route carries the ERT;

a determining module, configured to determine, according to a recorded correspondence between the IRT and the PE device and an ERT carried by the route to be issued, a device to which the route to be issued is to be sent;

and the second sending module is used for sending the route to be issued to the determined equipment.

11. The route distribution apparatus of claim 10, wherein the determination module is configured to:

12. The route distribution device according to claim 10, further comprising:

and the generating and recording module is used for generating and recording a mapping table of the PE equipment and the IRT according to the obtained IRT, wherein each table entry of the mapping table represents the corresponding relation between the IRT of each PE equipment and each PE equipment.

13. The route distribution apparatus according to claim 9,

the first transmitting module is configured to: sending the target IRT and the address of the PE device corresponding to the target IRT to the PE device corresponding to the ERT,

the device further comprises:

a receiving module, configured to receive the to-be-issued route from the PE device corresponding to the ERT, where the to-be-issued route carries the address;

and the forwarding module is used for forwarding the to-be-issued route according to the address.

14. The route distribution apparatus according to any one of claims 9 to 13, further comprising:

a deduplication processing module, configured to perform deduplication processing on the target IRT, where the deduplication processing is used to remove duplicate target IRTs,

the first transmitting module is configured to: and sending the target IRT subjected to the deduplication processing to the PE equipment corresponding to the ERT.

15. A routing distribution device applied to a source service Provider (PE) network edge device, the device comprising:

the target IRT is determined by the RR by: obtaining the extended community attribute RT information of each PE device from each service provider network edge PE device connected with RR, wherein the RT information comprises an incoming direction extended community attribute IRT and an outgoing direction extended community attribute ERT; respectively matching ERT in the RT information with IRT in the RT information, and determining the IRT matched with the ERT as a target IRT;

the PE receiving the target IRT is a PE device corresponding to an ERT matched with the target IRT; and the determining module is used for determining the to-be-issued route in the routes according to the target IRT and the ERT carried by the routes when the routes are to be issued.

16. The route distribution apparatus according to claim 15,

the receiving module further receives an address of the PE device corresponding to the target IRT,

the device further comprises:

a sending module, configured to send the route to be issued to the RR, where the route to be issued carries an address of the PE device corresponding to the target IRT.