CN113328943B

CN113328943B - Route matching method, information sending method and device

Info

Publication number: CN113328943B
Application number: CN202010408957.5A
Authority: CN
Inventors: 谢经荣; 胡华威
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-02-28
Filing date: 2020-05-14
Publication date: 2022-04-12
Anticipated expiration: 2040-05-14
Also published as: CN114900462A; WO2021169254A1; CN113328943A

Abstract

The application discloses a route matching method and a route matching device, which can improve multicast adding efficiency and reduce resource overhead. The method comprises the following steps: the first operator edge PE node receives indication information from the second PE node, wherein the indication information is used for indicating to carry out inclusion matching, the inclusion matching comprises matching the acquired multicast source group information with the acquired N1 selective operator multicast service interface S-PMSI automatic discovery AD routes, the multicast source group information comprises a multicast source S1 and a multicast group G1, N1 is an integer greater than or equal to 2, N1S-PMSI AD routes comprise a first S-PMSI AD route and a second S-PMSI AD route, the first S-PMSI AD route comprises at least one wildcard, and the second S-PMSI AD route comprises S1 and G1; and the first PE node processes the N2S-PMSI AD routes matched with the multicast source group information according to the indication information so as to join N2 tunnels with the second PE node, wherein N2 is greater than or equal to 2 and less than or equal to N1, and one tunnel in the N2 tunnels corresponds to one S-PMSI AD route in the N2S-PMSI AD routes.

Description

Route matching method, information sending method and device

The present application claims priority of chinese patent application entitled "a route updating method, apparatus and system" filed by the national intellectual property office at 28/2/2020, application number 202010134746.7, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of communications, and in particular, to a route matching method, an information sending method, and an information sending apparatus.

Background

An Auto-discovery (AD) route is an important signaling of a Multicast Virtual Private Network (MVPN) in a selective provider Multicast service interface (S-PMSI) Auto-discovery (AD). "matching processing" S-PMSI AD routing on Provider Edge (PE) nodes is a key step of MVPN, and is suitable for multiple occasions such as ReSource reservation Protocol-Traffic engineering (RSVP-TE) in MVPN, multicast extension of Label distribution Protocol (mLDP), Bit Index Explicit Replication (BIER) tunnel, and the like.

RFC6625 proposes to determine the S-PMSI AD route matching the multicast source group information by a "longest-match" principle, i.e., a leaf node joins a tunnel corresponding to the S-PMSI AD route determined according to the longest-match principle corresponding to the multicast source group information and receives a multicast data stream from the tunnel. However, this method has the problems of low multicast joining efficiency and high resource overhead.

Disclosure of Invention

The application provides a route matching method, an information sending method and a device, which can improve multicast adding efficiency and reduce resource overhead.

In a first aspect, the present application provides a route matching method, which is applied to a first PE node, and specifically includes the following steps: the first PE node receives indication information from the second PE node, wherein the indication information is used for indicating to perform inclusion matching, and the inclusion matching comprises matching the acquired multicast source group information with the acquired N1 selective operator multicast service interface S-PMSI AD routes. The multicast source group information comprises a multicast source S1 and a multicast group G1, N1 is an integer greater than or equal to 2, N1S-PMSI AD routes comprise a first S-PMSI AD route and a second S-PMSI AD route, the first S-PMSI AD route comprises at least one wildcard, and the second S-PMSI AD route comprises S1 and G1. That is, one multicast source group information can be matched with at least two S-PMSI AD routes having a containment relationship. The multicast source group information may be matched with at least one S-PMSI AD route including a wildcard in addition to the S-PMSI AD route including the multicast source group information. And the first PE node processes the N2S-PMSI AD routes matched with the multicast source group information according to the indication information so as to join N2 tunnels with the second PE node, wherein N2 is greater than or equal to 2 and less than or equal to N1, and one tunnel in the N2 tunnels corresponds to one S-PMSI AD route in the N2S-PMSI AD routes. Because of the 'containing matching', the first PE node can not only make the multicast source group information match with the N2S-PMSI AD routes having the containing relationship, but also make the first PE node join the N2 tunnels with the second PE node. Compared with the traditional 'longest matching' principle, the second PE node can be established only once by establishing the tunnel corresponding to the first S-PMSI AD route according to the 'including matching' principle without repeated establishment when new multicast is added, so that the multicast adding efficiency is improved, and the resource overhead is reduced.

In one possible implementation, the method further includes: and the first PE node receives a first identifier and a second identifier which are sent by the second PE node and correspond to any one S-PMSI AD route in the N1S-PMSI AD routes. Specifically, the first PE node receives N1 messages from the second PE node, where the N1 messages may be Border Gateway Protocol (BGP) messages, for example. Each of the N1 messages includes a first TLV field and a second TLV field, respectively, where the first TLV field carries an S-PMSI AD route, the second TLV field includes a PMSI Tunnel Attribute field, and the PMSI Tunnel Attribute field carries a first identifier and a second identifier. The first identifier is used to identify a tunnel type, and the second identifier is used to identify a request Leaf Information (LIR). In this case, the tunnel type may be BIER or RSVP-TE.

In one possible implementation manner, when the tunnel type is BIER or RSVP-TE, the processing, by the first PE node, the N2S-PMSI AD routes matching the multicast source group information according to the indication information includes: the first PE node generates N2 leaf AD routes corresponding to the N2S-PMSI AD routes according to the indication information, one of the N2 leaf AD routes corresponds to one of the N2S-PMSI AD routes, the N2 leaf AD routes comprise a first leaf AD route and a second leaf AD route, the first leaf AD route comprises at least one wildcard, and the second leaf AD route comprises S1 and G1. The first PE node issues N2 leaf AD routes to the second PE node to join tunnels corresponding to the N2 leaf AD routes. Compared with the traditional 'longest matching' principle, the 'including matching' principle is adopted in the method, the first PE node can only issue the first leaf AD route to the second PE node once, repeated issuing is not needed when new multicast is added, the multicast adding efficiency is improved, and the cost of resources is reduced.

In one possible implementation manner, when the tunnel type is BIER or RSVP-TE, the processing, by the first PE node, the N2S-PMSI AD routes matching the multicast source group information according to the indication information includes: the first PE node generates N2 leaf AD routes corresponding to the N2S-PMSI AD routes according to the indication information, one of the N2 leaf AD routes corresponds to one of the N2S-PMSI AD routes, the N2 leaf AD routes comprise a first leaf AD route and a second leaf AD route, the first leaf AD route comprises at least one wildcard, and the second leaf AD route comprises S1 and G1; the first PE node issues a first leaf AD route to a second PE node; the first PE node issues a second leaf AD route to the second PE node and starts a timer; and after the timer finishes timing, the first PE node keeps the first leaf AD route valid. The purpose of keeping the first leaf AD route active is to keep the tunnel corresponding to the first leaf AD route from being withdrawn, so that it can be achieved (S1, G1) that "containment matching" can be achieved with two or more S-PMSI AD routes. In some embodiments, there may be additional implementations, such as the first PE node not starting a timer, and may also maintain the first leaf AD route.

In one possible implementation, the method further includes: and the first PE node receives a first identifier which is sent by the second PE node and corresponds to any one S-PMSI AD route in the N1S-PMSI AD routes. Specifically, the first PE node receives N1 messages from the second PE node, where the N1 messages may be BGP messages, for example. Each of the N1 messages respectively includes a first TLV field, where the first TLV field carries an S-PMSI AD route, and the second TLV field includes a PMSI Tunnel Attribute field, where the PMSI Tunnel Attribute field carries a first identifier. The first identifier is used for identifying the type of the tunnel. In this case, the tunnel type may be mLDP.

In one possible implementation manner, when the tunnel type is mLDP, the processing, by the first PE node, the N2S-PMSI AD routes matching the multicast source group information according to the indication information includes: a first PE node acquires tunnel identifiers of N2 tunnels corresponding to N2S-PMSI AD routes, wherein one S-PMSI AD route in the N2S-PMSI AD routes corresponds to the tunnel identifier of one tunnel in N2 tunnels; the first PE node sends N2 mapping messages of Label Distribution Protocol (LDP) to the second PE node, wherein one LDP mapping message of the N2 LDP mapping messages comprises one tunnel identifier of tunnel identifiers of N2 tunnels. Compared with the traditional 'longest matching' principle, the 'including matching' principle is adopted in the method, the first PE node can only send the inclusion to the second PE node once, and repeated release is not needed when new multicast is added, so that the multicast adding efficiency is improved, and the resource overhead is reduced.

In a possible implementation manner, the tunnel type is mLDP, and the processing, by the first PE node, the N2S-PMSI AD routes matched with the multicast source group information according to the indication information includes: a first PE node acquires tunnel identifiers of N2 tunnels corresponding to N2S-PMSI AD routes, wherein one S-PMSI AD route in the N2S-PMSI AD routes corresponds to the tunnel identifier of one tunnel in N2 tunnels; a first PE node sends a first LDP mapping message to a second PE node, wherein the first LDP mapping message comprises a tunnel identifier of a tunnel corresponding to a first S-PMSI AD route; the first PE node sends a second LDP mapping message to a second PE node, and a timer is started, wherein the second LDP mapping message comprises a tunnel identifier of a tunnel corresponding to a second S-PMSI AD route; and after the timer finishes timing, the first PE node keeps adding the tunnel corresponding to the first S-PMSI AD route so as to ensure that the tunnel corresponding to the S-PMSI AD route comprising at least one wildcard between the first PE node and the second PE node keeps being connected but not being withdrawn. In some embodiments, there may be additional implementations, such as the first PE node not starting a timer, and likewise may remain joined in the tunnel corresponding to the first S-PMSI AD route.

In one possible implementation, the receiving, by the first PE node, the indication information from the second PE node includes: the first PE node receives the message issued by the second PE node. The message may be, for example, a BGP message. The message includes an extended provider multicast service interface Tunnel Attribute flag (Additional PMSI Tunnel Attribute Flags) for carrying indication information. Optionally, the first PE node receives N1 messages from the second PE node, where the N1 messages may be BGP messages, and one of the N1 BGP messages includes a first TLV field and a third TLV field, where the first TLV field carries an S-PMSI AD route including at least one wildcard, the third TLV field includes an Additional PMSI Tunnel Attribute flag, and the Additional PMSI Tunnel Attribute flag carries indication information.

In a second aspect, the present application provides an information sending method, which is applied to a second PE node. The method specifically comprises the following steps: the second PE node obtains indication information and sends the indication information to the first PE node, the indication information is used for indicating that the content matching is carried out, the content matching comprises matching of multicast source group information obtained by the first PE node with N1S-PMSI automatic discovery AD routes, the multicast source group information comprises a multicast source S1 and a multicast group G1, N1 is an integer greater than or equal to 2, N1S-PMSI AD routes comprise a first S-PMSI AD route and a second S-PMSI AD route, the first S-PMSI route comprises at least one wildcard, and the second S-PMSI AD route comprises S1 and G1. And sending indication information to the PE node through the second PE node, wherein the indication information is used for indicating that the matching is contained, and compared with the traditional 'longest matching' principle, the indication information can realize that the second PE node only needs to establish a tunnel corresponding to the first S-PMSI AD route once according to the 'containing matching' principle, and does not need to be repeatedly established when new multicast is added, so that the multicast adding efficiency is improved, and the resource overhead is reduced.

In one possible implementation, the method further includes: and the second PE node sends a first identifier and a second identifier corresponding to any one S-PMSI AD route in the N1S-PMSI AD routes to the first PE node, wherein the first identifier is used for identifying the type of the tunnel, and the second identifier is used for identifying the request leaf information. In this case, the tunnel type may be BIER or RSVP-TE.

In one possible implementation, the method further includes: and the second PE node sends a first identifier corresponding to any one S-PMSI AD route in the N1S-PMSI AD routes to the first PE node, wherein the first identifier is used for identifying the type of the tunnel. In this case, the tunnel type may be mLDP.

Optionally, the sending, by the second PE node, the indication information to the first PE node includes: and the second PE node issues a message to the first PE node, wherein the message comprises an extended operator multicast service interface Tunnel Attribute flag bit Additional PMSI Tunnel Attribute Flags, and the extended operator multicast service interface Tunnel Attribute flag bit is used for carrying indication information.

In a third aspect, the present application provides a route matching apparatus, where the apparatus is applied to a first provider edge PE node, and the apparatus includes: a receiving unit, configured to receive indication information from the second PE node, where the indication information is used to indicate that a match is performed, where the match includes matching the obtained multicast source group information with the obtained N1 selective operator multicast service interface S-PMSI auto discovery AD routes, where the multicast source group information includes a multicast source S1 and a multicast group G1, N1 is an integer greater than or equal to 2, and N1S-PMSI AD routes include a first S-PMSI AD route and a second S-PMSI AD route, the first S-PMSI AD route includes at least one wildcard, and the second S-PMSI AD route includes S1 and G1; and the processing unit is used for processing the N2S-PMSI AD routes matched with the multicast source group information according to the indication information so as to join N2 tunnels between the second PE node, wherein N2 is greater than or equal to 2 and less than or equal to N1, and one tunnel in the N2 tunnels corresponds to one S-PMSI AD route in the N2S-PMSI AD routes.

Optionally, the receiving unit is further configured to receive a first identifier and a second identifier, which are from the second PE node and correspond to any one of the N1S-PMSI AD routes, where the first identifier is used to identify a tunnel type, and the second identifier is used to identify request leaf information.

Optionally, the tunnel type is BIER or RSVP-TE. The processing unit is used for generating N2 leaf AD routes corresponding to the N2S-PMSI AD routes according to the indication information and issuing N2 leaf AD routes to the second PE node; one leaf AD route of the N2 leaf AD routes corresponds to one S-PMSI AD route of the N2S-PMSI AD routes, the N2 leaf AD routes include a first leaf AD route including at least one wildcard and a second leaf AD route including S1 and G1.

Optionally, the receiving unit is further configured to receive a first identifier, which is used to identify a tunnel type, from the second PE node and corresponds to any S-PMSI AD route of the N1S-PMSI AD routes.

Optionally, the tunnel type is mLDP. And the processing unit is used for acquiring tunnel identifications of N2 tunnels corresponding to N2S-PMSI AD routes, and sending N2 label distribution protocol LDP mapping messages to the second PE node, wherein one S-PMSI AD route in the N2S-PMSI AD routes corresponds to the tunnel identification of one tunnel in the N2 tunnels, and one LDP mapping message in the N2 LDP mapping messages comprises one tunnel identification in the tunnel identifications of the N2 tunnels.

Optionally, the receiving unit is configured to receive a message issued by the second PE node, where the message includes an extended provider multicast service interface Tunnel Attribute flag bit Additional PMSI Tunnel Attribute Flags, and the extended provider multicast service interface Tunnel Attribute flag bit is used to carry indication information.

In a fourth aspect, the present application provides an information sending apparatus, where the apparatus is applied to a second provider edge PE node, and the apparatus includes: an obtaining unit, configured to obtain indication information, where the indication information is used to indicate that performing inclusion matching includes matching multicast source group information obtained by a first PE node with obtained N1 selective operator multicast service interface S-PMSI auto discovery AD routes, where the inclusion matching includes matching the multicast source group information with a multicast group G1 and a multicast source S1, N1 is an integer greater than or equal to 2, and N1S-PMSI AD routes include a first S-PMSI AD route and a second S-PMSI AD route, the first S-PMSI AD route includes at least one wildcard, and the second S-PMSI AD route includes S1 and G1; and the sending unit is used for sending the indication information to the first PE node.

Optionally, the sending unit is further configured to send, to the first PE node, a first identifier and a second identifier corresponding to any S-PMSI AD route of the N1S-PMSI AD routes, where the first identifier is used to identify a tunnel type, and the second identifier is used to identify request leaf information.

Optionally, the sending unit is further configured to send, to the first PE node, a first identifier corresponding to any S-PMSI AD route of the N1S-PMSI AD routes, where the first identifier is used to identify a tunnel type.

Optionally, the sending unit is configured to issue a message to the first PE node, where the message includes an extended provider multicast service interface Tunnel Attribute flag bit Additional PMSI Tunnel Attribute Flags, and the extended provider multicast service interface Tunnel Attribute flag bit is used to carry indication information.

Drawings

Fig. 1 is a schematic diagram of a network architecture in an MVPN scenario provided in an embodiment of the present application;

fig. 2 is a flowchart of a route matching method according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of a route matching apparatus 300 according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of an information sending apparatus 400 according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an apparatus 500 according to an embodiment of the present application.

Detailed Description

The MVPN is a service supporting a multicast service of a plurality of point-to-multipoint (P2 MP) in an operator network. Referring to fig. 1, the figure is a schematic diagram of a network architecture in an MVPN scenario. In fig. 1, the network architecture includes a multicast source (source), a Customer Edge (CE) 1 in communication with the multicast source, a PE1, an operator (P) node, a PE2, a PE3, a CE2, a CE3, one or more multicast receivers (receivers) in communication with a CE2, and one or more multicast receivers in communication with a CE 3. The CE1 is connected with PE1, the PE1 is connected with a P node, the P node is respectively connected with PE2 and PE3, the PE2 is connected with CE2, and the PE3 is connected with CE 3. CE1, CE2, CE3, PE1, P nodes, PE2, and PE3 may be routers (routers) or switches (switches), etc. PE1, the P node, PE2, and PE3 form an Internet Protocol (IP) backbone network. Since PE1 is connected to CE1 communicating with the multicast source, PE1 may also be referred to as an ingress node; since PE2 and PE3 are connected to CE2 and CE3, respectively, which are connected to multicast receivers, PE2 and PE3 may also be referred to as egress (egres) nodes. In the embodiment of the present application, the multicast source, CE1, CE2, CE3, and each multicast receiver belong to the same VPN, i.e., VPNA. PE1 establishes BGP MVPN neighbors with PE2 and PE3, respectively, to transmit BGP MVPN signaling, e.g., MVPN routes.

The multicast source in fig. 1 may be a server or the like, and the multicast receiver may be a terminal or the like. A terminal device, which may also be referred to as a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), a terminal, etc., is a device for providing voice and/or data connectivity to a user, or a chip disposed in the device, such as a handheld device with a wireless connection function, a vehicle-mounted device, etc. Currently, some examples of terminal devices are: a mobile phone, a desktop computer, a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety, a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), a home gateway device (5G-gateway, 5G-RG) supporting 5G access, and the like.

See table 1 for 7 route types for MVPN routes and their corresponding roles.

TABLE 1

In the above 7 types of MVPN routes, the release of S-PMSI AD routes is a very important signaling for multicast VPN. The matching process to implement S-PMSI AD routing according to the "longest match" principle is defined in RFC 6625. The longest match means that the multicast source group information in the multicast join message is matched with the parameters contained in the S-PMSI AD route, and the S-PMSI AD route containing the most same parameters compared with the parameters contained in the multicast source group information conforms to the principle of longest match. The PE node can add a tunnel corresponding to the S-PMSI AD route determined according to the longest match. The multicast source group information includes information of a multicast source and information of a multicast group. The information of the multicast source is a specific multicast source or a non-specific multicast source. The information of the multicast group is a specific multicast group or a non-specific multicast group. The S-PMSI AD route determined based on the longest match is a S-PMSI AD route determined based on the longest match principle from among S-PMSI AD routes including at least one wildcard and S-PMSI AD routes not including a wildcard. And the S-PMSI AD route which is determined according to the longest matching principle and does not contain the wildcard is the S-PMSI AD route corresponding to the specific multicast source and the specific multicast group. The S-PMSI AD route containing at least one wildcard includes the following three possible implementations: the multicast source group information comprises a non-specific multicast source and a non-specific multicast group. The multicast source group information indicated by (, G) includes a non-specific multicast source and a specific multicast group. The multicast source group information indicated by (S) includes a specific multicast source and a non-specific multicast group. The multicast source group information represented by (S1, G1) or (S1, G2) includes a specific multicast source and a specific multicast group.

Although the storage space of the PE2 can be reduced by performing matching processing based on the "longest match" principle, since the tunnel corresponding to the S-PMSI (x, x) AD route added by the PE2 is cancelled, the tunnel needs to be added again whenever the PE2 receives a new multicast addition packet, so that the multicast addition efficiency is reduced, and the resource overhead is large.

The "longest match" principle is described in detail below with reference to fig. 1, which takes RSVP-TE, MLDP and BIER scenarios as examples.

First, taking the MVPN scenario based on RSVP-TE P2MP tunnel as an example, the following description is made:

(1) PE1 issues S-PMSI (star) AD routes, tunnel identifiers (tunnel identifiers) and LIR identifiers to PE 2. The tunnel identifier is tunnel identifier 0. In the RSVP-TE scenario, the tunnel identifier is specifically a session identifier for establishing a session between PE1 and PE2, where the session is used for interaction between PE1 and PE 2. The AD route (including S-PMSI AD route and Leaf AD route), the tunnel identifier, and the LIR identifier published in this application may be carried in a message (e.g., BGP message) interacted between PE1 and PE2, and details of relevant parts are not described below.

(2) After the PE2 receives the S-PMSI (star) AD route, if the PE2 stores the multicast entry corresponding to (S1, G1) according to the multicast join message including (S1, G1), and S1 is the address of the multicast source communicating with the PE1, the PE2 may issue a Leaf (star) AD route carrying the IP address of the PE2 to the PE1 according to the LIR identifier.

(3) PE1 establishes an RSVP-TE P2MP tunnel with PE2 using the tunnel identified by tunnel identifier0, according to the Leaf (a,) AD route from PE 2.

(4) PE1 transmits the multicast data stream including (S1, G1) to PE2 along the tunnel corresponding to tunnel identifier 0.

(5) PE1 publishes the S-PMSI (S1, G1) AD route, tunnel identifier 1 and LIR identification after a certain time interval.

(6) After receiving the S-PMSI (S1, G1) AD route, PE2 determines from the S-PMSI (S1, G1) AD route and the S-PMSI (,) AD route according to the longest match rule: the route longest matching (S1, G1) is the S-PMSI (S1, G1) AD route. PE2 issues a Leaf (S1, G1) AD route to PE1 that carries the IP address of PE 2. When PE2 issues the Leaf (S1, G1) AD route, PE2 starts a timer T1.

(7) PE1 receives the Leaf (S1, G1) AD route from PE2 and establishes an RSVP-TE P2MP tunnel with PE2 using the tunnel identified by tunnel identifier 1.

(8) PE1 sends the multicast data stream including (S1, G1) to PE2 along the tunnel corresponding to tunnel identifier 1.

(9) PE2 issues a route withdraw request to withdraw a Leaf (a) AD route to PE1 after timer T1 expires, the route withdraw request including the IP address of PE 2.

(10) After receiving the route revocation request for revoking the Leaf (,) AD route sent by PE2, PE1 initiates a revocation response to PE2 through the tunnel corresponding to tunnel identifier0, where the revocation response is used to revoke the tunnel corresponding to tunnel identifier0, so as to delete PE2 from the Leaf list of the P2MP tree corresponding to tunnel identifier 0.

(11) The PE2 receives the multicast join message including (S1, G2), and according to the longest match rule, the processing is as follows:

a) since there are only S-PMSI (,) AD routes and S-PMSI (S1, G1) AD routes on PE2, the route that longest matches (S1, G2) is the S-PMSI (,) AD route, PE2 generates a Leaf (,) AD route and issues to PE 1;

b) PE1 establishes a branch to the tree of PE2 based on the tunnel corresponding to tunnel identifier0 according to the Leaf (a,) AD route sent by PE2, and sends the multicast data stream including (S1, G2) to PE2 through the tunnel corresponding to tunnel identifier 0.

c) PE1 publishes the S-PMSI (S1, G2) AD routings and tunnel identifier 2 after a certain time interval.

d) After PE2 receives the route, according to the longest match rule, among S-PMSI (x, x) AD route, S-PMSI (S1, G1) AD route, and S-PMSI (S1, G2) AD route, the route that matches (S1, G2) with its longest match becomes S-PMSI (S1, G2) AD route, PE2 generates Leaf (S1, G2) AD route and issues it to PE1, and starts timer T1 again.

e) PE1 receives the Leaf (S1, G2) AD route from PE2, and establishes a tunnel identified as tunnel identifier 2 to PE2, i.e., establishes a branch to the P2MP tree of PE2, based on the Leaf (S1, G2) AD route, and sends the multicast data stream including (S1, G2) to PE2 through this tunnel.

f) PE2 issues a route withdraw request to withdraw a Leaf (a) AD route to PE1 again after timer T1 times out. Thus, after the tunnel corresponding to the tunnel identifier 2 is established, the PE2 cancels the Leaf (a, a) AD route, and can ensure that the multicast data stream is not interrupted when the longest matching route changes.

g) After receiving the route revocation request for revoking the Leaf (,) AD route sent by PE2, PE1 initiates a revocation response to PE2 through the tunnel corresponding to tunnel identifier0, where the revocation response is used to revoke the tunnel corresponding to tunnel identifier0, so as to delete PE2 from the Leaf list of the P2MP tree corresponding to tunnel identifier 0.

The interaction between PE3 and PE1 in the RSVP-TE P2MP scenario is similar to the interaction between PE2 and PE1 mentioned above, and is not described herein again.

Second, taking MVPN based on mLDP P2MP tunnel as an example, the following description is made:

(1) PE1 issues S-PMSI (,) AD routes and corresponding tunnel identifications to PE2 according to the configuration. The tunnel identifier is tunnel identifier 0. In the mLDP scenario, the tunnel identifier is the FEC of one LDP. The FEC includes the root node IP address of the P2MP tunnel, which in the example shown in FIG. 1 is the IP address of PE 1. The S-PMSI (x) AD route may not carry the LIR identification.

(2) After the PE2 receives the S-PMSI (x, x) AD route, if the PE2 stores the multicast entry corresponding to (S1, G1) according to the multicast join message including (S1, G1), and S1 is the address of the multicast source communicating with the PE1, the PE2 sends a tunnel establishment request 1 to the PE1, where the tunnel establishment request 1 includes tunnel identifier0, so as to establish a tunnel corresponding to the tunnel identifier0, that is, to establish a branch of the P2MP tree of the tunnel identifier0 using the PE1 as a root node.

(3) PE1 transmits the multicast data stream including (S1, G1) to PE2 along the tunnel corresponding to tunnel identifier 0.

(4) The PE1 issues a S-PMSI (S1, G1) AD route and a corresponding tunnel identifier 1 after a certain time interval.

(5) After receiving the S-PMSI (S1, G1) AD route, PE2 determines from the S-PMSI (S1, G1) AD route and the S-PMSI (,) AD route according to the longest match rule: the route longest matching (S1, G1) is the S-PMSI (S1, G1) AD route. PE2 initiates a tunnel establishment request 2 to PE1, where the tunnel establishment request 2 includes tunnel identifier 1, so as to establish a tunnel corresponding to tunnel identifier 1, that is, to establish a branch of a P2MP tree corresponding to tunnel identifier 1. When PE2 initiates tunnel establishment request 2 to PE1, PE2 starts timer T1.

(6) PE1 sends the multicast data stream including (S1, G1) to PE2 along the tunnel corresponding to tunnel identifier 1.

(7) After the timer T1 expires, the PE2 initiates a tunnel cancellation request for canceling the tunnel corresponding to the tunnel identifier0 to the PE1, where the tunnel cancellation request includes the tunnel identifier0, so as to cancel the branch of the P2MP tree corresponding to the tunnel identifier 0.

(8) The PE2 receives the multicast join message including (S1, G2), and according to the longest match rule, the processing is as follows:

a) since there are only S-PMSI (,) AD route and S-PMSI (S1, G1) AD route on PE2, the route that matches (S1, G2) longest is S-PMSI (,) AD route, PE2 joins the tunnel identified as tunnel identifier0 that corresponds to S-PMSI (,) AD route;

b) the PE1 transmits a multicast data stream including (S1, G2) to the PE2 through a tunnel corresponding to the tunnel identifier 0.

c) The PE1 issues a S-PMSI (S1, G2) AD route and a corresponding tunnel identifier 2 after a certain time interval.

d) After the PE2 receives the S-PMSI (S1, G2) AD route, according to the longest matching rule, among the S-PMSI (x, x) AD route, S-PMSI (S1, G1) and S-PMSI (S1, G2) AD route, the route matching the longest route of (S1, G2) becomes the S-PMSI (S1, G2) AD route, PE2 adds a tunnel whose tunnel identifier is tunnel identifier 2 corresponding to the S-PMSI (S1, G2) route, and starts the timer T1 AD again.

e) The PE1 transmits the multicast data stream including (S1, G2) to the PE2 through the tunnel corresponding to the tunnel identifier 2.

f) When the timer T1 times out, the PE2 sends a tunnel cancel request to the PE1 again, where the tunnel cancel request includes a tunnel identifier0, so as to cancel a branch of the P2MP tree corresponding to the tunnel identifier 0.

The interaction between PE3 and PE1 in the mLDP P2MP scenario is similar to the interaction between PE2 and PE1 mentioned above, and is not described here.

Thirdly, taking MVPN based on BIER tunnel as an example, the following description is made:

(1) PE1 issues to PE2, according to the configuration, the S-PMSI (,) AD route, the LIR identification and the tunnel identification of the BIER type. The tunnel identifier of the BIER type includes an IP address and a bit forwarding router identifier (BFR-id). In this scenario, the BIER-type tunnel id issued by PE1 includes the IP address of PE1 and the BFR-id of PE1, e.g., the BFR-id value is 1. Different from the former two scenarios, in the BIER scenario, the tunnel identifier is carried in the packet to indicate that the tunnel is added, instead of executing the step of generating the tunnel in the former two scenarios.

(2) After the PE2 receives the S-PMSI (x, x) AD route, if the PE2 stores the multicast entry corresponding to (S1, G1) according to the multicast join message including (S1, G1), and S1 is the address of the multicast source communicating with the PE1, the PE2 may issue a Leaf (x, x) AD route to the PE1 according to the LIR identifier, and add the tunnel corresponding to the Leaf (x, x) AD route, carrying the IP address of the PE2 and the BFR-id value of the PE2, for example, the BFR-id value is 2.

(3) PE1 encapsulates BIER header information in a BIER message including (S1, G1), the encapsulated BIER header information including a value of BFR-id of 2, and transmits the BIER message to PE 2.

(4) The PE1 issues S-PMSI (S1, G1) AD routes, LIR identities and BIER type tunnel identities after a certain time interval.

(5) After receiving the S-PMSI (S1, G1) AD route, PE2 determines from the S-PMSI (S1, G1) AD route and the S-PMSI (,) AD route according to the longest match rule: the route longest matching (S1, G1) is the S-PMSI (S1, G1) AD route. Thus, PE2 issues a Leaf (S1, G1) AD route to PE1, carrying the IP address of PE2 and the BFR-id value of 2, to join the tunnel corresponding to the Leaf (S1, G1) AD route. When a Leaf (S1, G1) AD route is issued, PE2 starts a timer T1.

(6) PE1 encapsulates BIER header information in a BIER packet including (S1, G1) according to Leaf (S1, G1) AD routing, the encapsulated BIER header information including a value of BFR-id of 1, and then transmits the BIER packet to PE 2.

(7) After the timer T1 expires, the PE2 initiates a route withdrawal request to the PE1, where the route withdrawal request carries the IP address and the BFR-id value 2 of the PE2, so as to withdraw the tunnel corresponding to the Leaf AD route.

a) since there are only S-PMSI (,) AD routes and S-PMSI (S1, G1) AD routes on PE2, the route that is the longest match with (S1, G2) determined according to the longest match rule is the S-PMSI (,) AD route, and PE2 issues a Leaf (,) AD route corresponding to the S-PMSI (,) AD route to join the tunnel corresponding to the Leaf (,) AD route.

b) PE1 sends the multicast data stream including (S1, G2) to PE2 according to the tunnel corresponding to the Leaf (,) AD route.

c) The PE1 issues the S-PMSI (S1, G2) AD route, tunnel ID and LIR ID after a certain time interval.

d) After receiving the S-PMSI (S1, G2) AD route, the PE2 determines, according to the longest matching rule, a route that matches the longest of (S1, G2) from among the S-PMSI (,) AD route, S-PMSI (S1, G1) and S-PMSI (S1, G2) AD route as the S-PMSI (S1, G2) AD route, and the PE2 issues a Leaf (S1, G2) AD route to the PE1 to join a tunnel corresponding to the Leaf (S1, G2) AD route, and starts the timer T1 again.

e) The PE1 transmits a multicast data stream including (S1, G2) to the PE2 through a tunnel corresponding to the S-PMSI (S1, G2) AD route.

f) PE2 sends a route withdraw request for withdrawing a Leaf (x) AD route to PE1 after timer T1 expires, to withdraw the tunnel corresponding to the Leaf (x) AD route.

The interaction between PE3 and PE1 in the BIER scenario is similar to the interaction between PE2 and PE1 mentioned above, and is not described here in detail.

In the above three scenarios, the PE2 deletes the tunnel corresponding to the S-PMSI AD route that is not the longest match after adding the tunnel corresponding to the S-PMSI AD route that is the longest match, and finally, the PE2 matches the specific multicast source and the specific multicast group to only one S-PMSI AD route, and the PE2 adds only one tunnel corresponding to the S-PMSI AD route, and acquires traffic from the tunnel. And when the longest matching S-PMSI AD route changes, the multicast data flow is ensured not to be interrupted. Although the storage space of the PE2 can be reduced in this way, since the tunnel corresponding to the S-PMSI (star) AD route added by the PE2 is removed, the tunnel needs to be added again each time the PE2 receives a new multicast addition packet, so that the multicast addition efficiency is reduced, and the resource overhead is large. In order to solve the foregoing problems, embodiments of the present application provide a route matching method, which can reduce resource overhead and improve multicast join efficiency.

Referring to fig. 2, this figure is a flowchart of a route matching method provided in an embodiment of the present application. The route matching method comprises the following steps:

s101: the first PE node acquires a multicast adding message, and the multicast adding message carries multicast source group information.

For example, the first PE node may be an egress node, such as PE2 or PE3 in the embodiment shown in fig. 1. The acquiring of the multicast join message by the first PE node may be receiving the multicast join message from a CE in communication with a multicast recipient (e.g., as shown in fig. 1). For example, if the first PE node is PE2 shown in fig. 1, the first PE node may receive a multicast join packet from CE 2; if the first PE node is PE3 shown in fig. 1, the first PE node may receive the multicast join packet from CE 3. The multicast join message includes multicast source group information, and the multicast source group information includes information of a multicast source (source, S) and information of a multicast group (group, G). The multicast source group information represented by (S1, G1) in the embodiment shown in fig. 2 is only an example, and is not a limitation to the technical solution of the present application, for example, the route matching method provided in the embodiment of the present application may also be applied to the processing of the multicast source group information represented by (S1, G2).

S102: the first PE node sends the multicast source group information to the second PE node.

For example, the second PE node may be an ingress node, such as PE1 shown in fig. 1.

S103: and the second PE node sends indication information to the first PE node, wherein the indication information is used for indicating to carry out inclusion matching.

For example, the inclusion-matching (Inclusive-match) means that the acquired multicast source group information is matched with the acquired N1S-PMSI AD routes to N2S-PMSI AD routes. The S-PMSI AD route may be the S-PMSI AD route described above, for example, a S-PMSI (,) AD route and a S-PMSI (S1, G1) AD route. Wherein N1 is an integer of 2 or more, and N2 is an integer of 2 or more and N1 or less. The N1S-PMSI AD routes include a first S-PMSI AD route containing at least one wildcard and a second S-PMSI AD route including S1 and G1. Wildcards can be denoted as x.

For RSVP-TE and BIER scenarios, taking multicast source group information (S1, G1) as an example, N1S-PMSI AD routes and N2S-PMSI AD routes may be implemented as one of the following:

(1) the N1S-PMSI AD routes may include 1S-PMSI (x, x) AD route and N1-1S-PMSI (S, G) AD routes, wherein N1-1S-PMSI (S, G) AD routes include S-PMSI (S1, G1) AD route, S-PMSI (S2, G2) AD route … S-PMSI (S (N1-1), G (N1-1)) AD route. If N1 is 2, then N1-1S-PMSI (S, G) AD routes include S-PMSI (S1, G1) AD routes. If N1 is 3, then N1-1S-PMSI (S, G) AD routes include S-PMSI (S1, G1) AD routes and S-PMSI (S2, G2) AD routes. The N2S-PMSI AD routes may include S-PMSI (,) AD routes and S-PMSI (S1, G1) AD routes.

(2) The N1S-PMSI AD routes may include 1S-PMSI (G1) AD route and N1-1S-PMSI (S, G1) AD route, wherein the N1-1S-PMSI (S, G1) AD routes include S-PMSI (S1, G1) AD route, S-PMSI (S2, G1) AD route, S-PMSI (S3, G1) AD route … S-PMSI (S1-1), G1) AD route. If N1 is 2, then N1-1S-PMSI (S, G1) AD routes include S-PMSI (S1, G1) AD routes. If N1 is 3, then N1-1S-PMSI (S, G1) AD routes include S-PMSI (S1, G1) AD routes and S-PMSI (S2, G1) AD routes. The N2S-PMSI AD routes may include S-PMSI (, G1) AD routes and S-PMSI (S1, G1) AD routes.

(3) The N1S-PMSI AD routes may include 1S-PMSI (S1, one) AD route and N1-1S-PMSI (S1, G) AD route, wherein the N1-1S-PMSI (S1, G) AD routes include S-PMSI (S1, G1) AD route, S-PMSI (S1, G2) AD route, S-PMSI (S1, G3) AD route … S-PMSI (S1, G (N1-1)) AD route. If N1 is 2, then N1-1S-PMSI (S1, G) AD routes include S-PMSI (S1, G1) AD routes. If N1 is 3, then N1-1S-PMSI (S1, G) AD routes include S-PMSI (S1, G1) AD routes and S-PMSI (S1, G2) AD routes. The N2S-PMSI AD routes may include S-PMSI (S1, x) AD routes and S-PMSI (S1, G1) AD routes.

(4) The N1S-PMSI AD routes may include 1S-PMSI (, x) AD route, 1S-PMSI (, G1) AD route, and N1-2S-PMSI (S, G1) AD routes, wherein, when N1 is 2, N1-2S-PMSI (S, G1) AD routes do not exist. When N1 is greater than or equal to 3, N1-2S-PMSI (S, G1) AD routes include S-PMSI (S1, G1) AD route, S-PMSI (S2, G1) AD route, S-PMSI (S3, G1) AD route … S-PMSI (S (N1-2), G1) AD route. If N1 is 3, then N1-2S-PMSI (S, G1) AD routes include S-PMSI (S1, G1) AD routes. If N1 is 4, then N1-2S-PMSI (S, G1) AD routes include S-PMSI (S1, G1) AD routes and S-PMSI (S2, G1) AD routes. The N2S-PMSI AD routes may include S-PMSI (, G1) AD routes, S-PMSI (, G1) AD routes, and S-PMSI (S1, G1) AD routes.

The above four implementation manners do not limit the technical solution of the present application, and a person skilled in the art can design the implementation manners according to actual situations.

For the MLDP scenario, taking the multicast source group information as (S1, G1) as an example, the N1S-PMSI AD routes may be 1S-PMSI (x, x) AD route and N1-1S-PMSI (S, G) AD route; the N2S-PMSI AD routes may include 1S-PMSI (x,) AD route and 1S-PMSI (S1, G1) AD route. The implementation manner does not constitute a limitation to the technical solution of the present application, and a person skilled in the art can design the implementation manner according to actual situations.

For example, the second PE node sends the first PE node a first identity and a second identity corresponding to any one of the N1S-PMSI AD routes. Specifically, the second PE node may send N1 messages to the first PE node, where the N1 messages may be BGP messages, for example. Any one of the N1 messages includes a first TLV field and a second TLV field, where the first TLV field carries an S-PMSI AD route, the second TLV field includes a PMSI Tunnel Attribute field, and the PMSI Tunnel Attribute field carries a first identifier and a second identifier. The first identifier is used for identifying the type of the tunnel, and the second identifier is used for identifying the LIR. The tunnel type may be BIER or RSVP-TE. The first identity may be the tunnel identity described above. The second identity may be the LIR identity described above.

For example, the second PE node sends a first identification corresponding to any one of the N1S-PMSI AD routes to the first PE node. Specifically, the second PE node sends N1 messages to the first PE node, where the N1 messages may be BGP messages, for example. Any one of the N1 messages includes a first TLV field and a second TLV field, where the first TLV field carries an S-PMSI AD route, the second TLV field includes a PMSI Tunnel Attribute field, and the PMSI Tunnel Attribute field carries a first identifier. The first identifier is used for identifying the type of the tunnel. The tunnel type may be mLDP. The first identity may be the tunnel identity described above.

For example, the indication information may be carried in a message sent by the second PE node to the first PE node, where the message may be, for example, a BGP message. The message may be one or more of the N1 messages described above. The indication information may be carried in an extended operator multicast service interface Tunnel Attribute flag (Additional PMSI Tunnel Attribute Flags) of the BGP message, where the Additional PMSI Tunnel Attribute Flags bit is defined in RFC 7902. Specifically, the BGP message may further include a third TLV field, where the third TLV field includes the indication information. Optionally, the S-PMSI AD route carried by the BGP message carrying the indication information is a S-PMSI AD route including at least one wildcard.

S104: the first PE node receives the indication information and the N1S-PMSI AD routes from the second PE node.

S105: and the first PE node processes the N2S-PMSI AD routes matched with the multicast source group information in the N1S-PMSI AD routes according to the indication information so as to join N2 tunnels with the second PE node.

For example, after the first PE node acquires the indication information and the multicast source group information, the multicast source group information is subjected to inclusion matching with N1S-PMSI AD routes according to the indication information, and N2S-PMSI AD routes that are successfully matched are determined. One of the N2 tunnels corresponds to one of the N2S-PMSI AD routes. One multicast source group information can be matched with at least two S-PMSI AD routes having a containment relationship. The S-PMSI AD routes matching with each other in multiple multicast source group information may overlap, for example:

the S-PMSI AD routes matched with the multicast source group information (S1, G1) include S-PMSI (x, x) AD routes and S-PMSI (S1, G1) AD routes.

The S-PMSI AD routes matched with the multicast source group information (S2, G2) include S-PMSI (x, x) AD routes and S-PMSI (S2, G2) AD routes.

Therefore, when there are a plurality of multicast source group information, the proportion of the memory occupied by the matching method is not large, for example, there are 100 multicast source group information, and only 101S-PMSI a-D routes matched by the matching method. The multicast source group information may be matched with at least one S-PMSI AD route including a wildcard in addition to the S-PMSI AD route including the multicast source group information. For example, (S1, G1) may match S-PMSI (S1, G1) AD routes, in addition to S-PMSI (a, a) AD routes. As another example, (S1, G2) may be matched to S-PMSI (S1, G2) AD routes, as well as S-PMSI (S1) AD routes. In the embodiment of the present application, "include matching" means that not only N2S-PMSI AD routes having a inclusion relationship on multicast source group information can be matched, but also N2 tunnels between a first PE node and a second PE node can be joined by the first PE node.

For example, when the tunnel type is BIER or RSVP-TE, S106 can be implemented by the following steps: first, the first PE node generates N2 leaf AD routes corresponding to N2S-PMSI AD routes according to the indication information. Then, the first PE node issues to the second PE node N2 leaf AD routes, where the N2 leaf AD routes are used to enable the first PE node to join the corresponding tunnels, respectively. Wherein, one leaf AD route in N2 leaf AD routes corresponds to one S-PMSI AD route in N2S-PMSI AD routes, N2 leaf AD routes include first leaf AD route and second leaf AD route, and first leaf AD route includes at least one wildcard, and second leaf AD route includes S1 and G1.

For RSVP-TE and BIER scenarios, when the N1S-PMSI AD routes are one of the following implementations, the corresponding N2 leaf AD routes are as follows:

(1) when the N1S-PMSI AD routes are 1S-PMSI (, x) AD route and N1-1S-PMSI (S, G) AD routes, where N1-1S-PMSI (S, G) AD routes include S-PMSI (S1, G1) AD route, S-PMSI (S2, G2) AD route … S-PMSI (S (N1-1), G (N1-1)) AD route, the corresponding Leaf AD routes include 1 Leaf (, x) AD route and N2-1 Leaf (S, G) AD route. Wherein the N2-1 Leaf (S, G) AD routes are determined according to the multicast source group information. If N2 is 3 and the multicast source group information includes (S1, G1) and (S2, G2), then N2-1 Leaf (S, G) AD routes include Leaf (S1, G1) AD routes and Leaf (S2, G2) AD routes. If N2 is 2 and the multicast source group information is (S2, G2), then the N2-1 Leaf (S, G) AD routes include Leaf (S2, G2) AD routes.

(2) When N1S-PMSI AD routes are 1S-PMSI (G1) AD route and N1-1S-PMSI (S, G1) AD route, and N1-1S-PMSI (S, G1) AD routes include S-PMSI (S1, G1) AD route, S-PMSI (S2, G1) AD route, S-PMSI (S3, G1) AD route ….. S-PMSI (S (N1-1), G1) AD route, the corresponding N2 leaf AD routes include: 1 Leaf (, G1) AD route and N2-1 Leaf (S, G1) AD route. Wherein N2-1 Leaf (S, G1) AD routes are determined from multicast source group information. If N2 is 3 and the multicast source group information includes (S1, G1) and (S2, G1), then N2-1 Leaf (S, G1) AD routes include Leaf (S1, G1) AD routes and Leaf (S2, G1) AD routes. If N2 is 2 and the multicast source group information is (S2, G1), then the N2-1 Leaf (S, G1) AD routes include Leaf (S2, G1) AD routes.

(3) When N1S-PMSI AD routes are 1S-PMSI (S1,) AD route and N1-1S-PMSI (S1, G) AD route, N1-1S-PMSI (S1, G) AD routes include S-PMSI (S1, G1) AD route, S-PMSI (S1, G2) AD route, S-PMSI (S1, G3) AD route ….. S-PMSI (S1, G (N1-1)) AD route, the corresponding N2 leaf AD routes include: 1 Leaf (S1, x) AD route and N2-1 Leaf (S1, G) AD route. Wherein N2-1 Leaf (S1, G) AD routes are determined from the multicast source group information. If N2 is 3 and the multicast source group information includes (S1, G1) and (S1, G2), then N2-1 Leaf (S1, G) AD routes include Leaf (S1, G1) AD routes and Leaf (S1, G2) AD routes. If N2 is 2 and the multicast source group information is (S1, G2), then the N2-1 Leaf (S1, G) AD routes include Leaf (S1, G2) AD routes.

(4) When the N1S-PMSI AD routes are 1S-PMSI (x, x) AD route, 1S-PMSI (x, G1) AD route and N1-2S-PMSI (S, G1) AD routes, N1 is more than or equal to 3. N1-2S-PMSI (S, G1) AD routes include S-PMSI (S1, G1) AD route, S-PMSI (S2, G1) AD route, S-PMSI (S3, G1) AD route …. The corresponding N2 leaf AD routes include: 1 Leaf (x) AD route, 1 Leaf (G1) AD route, and N2-2 Leaf (S, G1) AD routes, N2 being an integer greater than or equal to 3 and less than or equal to N1. If N2 is 3 and the multicast source group information is (S2, G1), then the N2-2 Leaf (S, G1) AD routes include Leaf (S2, G1) AD routes. If N2 is 4 and the multicast source group information includes (S2, G1) and (S1, G1), then N2-2 Leaf (S, G1) AD routes include Leaf (S2, G1) AD routes and Leaf (S1, G1) AD routes.

When the tunnel type is mLDP, S106 can be implemented by: first, a first PE node obtains tunnel identifiers of N2 tunnels corresponding to N2S-PMSI AD routes, and one S-PMSI AD route in the N2S-PMSI AD routes corresponds to the tunnel identifier of one tunnel in the N2 tunnels. Then, the first PE node sends N2 LDP mapping messages to the second PE node, where any one of the N2 LDP mapping messages includes a tunnel identifier, so that the first PE node joins the tunnel identified by the tunnel identifier included in the N2 tunnels. When the first PE node is not directly connected to the second PE node, the first PE node may determine a next-hop node on the path to the second PE node, and send the N2 LDP mapping messages to the next-hop node, so that the next-hop node can send the N2 LDP mapping messages to the second PE node, and so on until the N2 LDP mapping messages reach the second PE node.

To implement N2 tunnels between the first PE node joining the second PE node, as one possible implementation, the first PE node does not start a timer (e.g., timer T1 above); as another possible implementation, the second PE node starts a timer, but does not withdraw a tunnel that has been joined with the S-PMSI AD route including at least one wildcard at the end of the timing, so as to ensure that the tunnel corresponding to the S-PMSI AD route including at least one wildcard between the first PE node and the second PE node remains connected, instead of being withdrawn.

For example, if the added tunnel is a BIER or RSVP-TE tunnel, the processing, by the first PE node, the N2S-PMSI AD routes matching the multicast source group information according to the indication information includes: the first PE node generates N2 leaf AD routes corresponding to the N2S-PMSI AD routes according to the indication information, one of the N2 leaf AD routes corresponds to one of the N2S-PMSI AD routes, the N2 leaf AD routes comprise a first leaf AD route and a second leaf AD route, the first leaf AD route comprises at least one wildcard, and the second leaf AD route comprises S1 and G1. The first PE node issues a first leaf AD route to the second PE node, and issues a second leaf AD route to the second PE node. When the first PE node issues the second leaf AD route to the second PE node, the first PE node may not start the timer, or start the timer, but after the timer finishes timing, the first PE node keeps the first leaf AD route valid. The timer may be, for example, the timer T1 described above. The purpose of keeping the first leaf AD route active is to keep the tunnel corresponding to the first leaf AD route from being withdrawn, so that it can be achieved (S1, G1) that "containment matching" can be achieved with two or more S-PMSI AD routes.

For another example, if the added tunnel is mLDP, the processing, by the first PE node, the N2S-PMSI AD routes matched with the multicast source group information according to the indication information includes: the first PE node obtains tunnel identifiers of N2 tunnels corresponding to N2S-PMSI AD routes, and one S-PMSI AD route in the N2S-PMSI AD routes corresponds to the tunnel identifier of one tunnel in the N2 tunnels. And the first PE node sends a first LDP mapping message to the second PE node, wherein the first LDP mapping message comprises a tunnel identifier of a tunnel corresponding to the first S-PMSI AD route. And the first PE node sends a second LDP mapping message to the second PE node, wherein the second LDP mapping message comprises the tunnel identifier of the tunnel corresponding to the second S-PMSI AD route. When sending the second LDP mapping message, the second PE node may not start the timer (e.g., the timer T1 described above), or start the timer, but after the timer expires, keep joining the tunnel corresponding to the first S-PMSI AD route, i.e., ensure that the tunnel corresponding to the first S-PMSI AD route is not withdrawn, so that it can be realized (S1, G1) to "include match" with two or more S-PMSI AD routes.

According to the route matching method, the principle of 'including matching' is adopted, the first PE node can establish a tunnel corresponding to the first S-PMSI AD route between the first PE node and the second PE node according to the indication information, and repeated establishment is not needed when new multicast is added, so that multicast adding efficiency is improved, and resource overhead is reduced.

The following describes in detail the route matching method provided in the embodiment of the present application, with reference to fig. 1, taking RSVP-TE, MLDP and BIER scenarios as examples, respectively.

In an RSVP-TE scenario, the method for route matching provided in the embodiment of the present application includes the following steps:

(1) the PE1 sends a BGP message to the PE2 according to the configuration trigger, where the BGP message includes an S-PMSI (star) AD route, a tunnel identifier0, and a LIR identifier, where the tunnel identifier0 is a first identifier and the LIR identifier is a second identifier. In the RSVP-TE scenario, the tunnel identifier is specifically a session identifier for establishing a session between PE1 and PE 2. The BGP message also carries indication information. The indication information may be represented as additive-Match indication information. Optionally, the indication information may be carried only in a BGP message including the S-PMSI (star, AD) route, and the BGP message including the S-PMSI (S1, G1) AD route or the S-PMSI (S1, G2) AD route may not carry the indication information, so as to save message overhead.

(6) After receiving the S-PMSI (S1, G1) AD route, the PE2 performs inclusion matching according to the indication information, that is, when the BGP message including the S-PMSI (x, x) AD route further includes the indication information, the PE2 performs inclusion matching between the (S1, G1) AD route and the S-PMSI (x, x) AD route stored in the PE2 (S1, G1) AD route. In the embodiment of the present application, (S1, G1) can match not only the S-PMSI AD route including the multicast source group information, i.e., the S-PMSI (S1, G1) AD route, but also the S-PMSI AD route including the wildcard to which it belongs, i.e., the S-PMSI (,) AD route, and the PE2 determines that the S-PMSI AD route matching (S1, G1) includes the S-PMSI (,) AD route and the S-PMSI (S1, G1) AD route. PE2 may publish Leaf AD routes corresponding to the matched S-PMSI AD routes to PE1, i.e., PE2 may publish Leaf (S1, G1) AD routes and Leaf (,) AD routes to PE 1. However, the Leaf (x) AD route is already issued in step (2), so the PE2 only needs to issue the Leaf (S1, G1) AD route, and carries the IP address of the PE2 in the Leaf (S1, G1) AD route, thereby saving network resources.

In the method provided in this embodiment, in order to enable both the specific multicast source and the multicast group included in the multicast join packet to perform inclusion matching, PE2 does not send a route withdraw request for withdrawing a Leaf (x) AD route to PE1, that is, does not withdraw the tunnel whose tunnel identifier is tunnel identifier0 and which PE2 joins. In order to achieve this objective, the embodiments of the present application provide two possible implementation manners:

a) in one implementation, PE2 does not start timer T1 according to the "include-match" indication.

b) In another implementation, PE2 still starts timer T1, but does not send a route withdraw request for withdrawing a Leaf (x) AD route to PE1 according to the "inclusive-match" indication message at the end of timer T1 to keep the Leaf (x) AD route valid.

(9) If, according to implementation a of step (6), PE2 does not start timer T1, the Leaf (a) AD route is not withdrawn and does not need to be reissued. Then, after PE2 receives the multicast join message including (S1, G2), the interaction between PE2 and PE1 may include the following steps:

a) the PE2 transmits the multicast source group information including (S1, G2) to the PE 1.

b) The PE1 sends the multicast data stream including (S1, G2) to the PE2 through the tunnel corresponding to the tunnel identifier 0.

d) After receiving the S-PMSI (S1, G2) AD route, the PE2 performs inclusion matching according to the indication information, that is, when the BGP message including the S-PMSI (x, x) AD route also includes the indication information, the PE2 performs inclusion matching between the (S1, G2) and the S-PMSI (x, x) AD route, the S-PMSI (S1, G1) AD route, and the S-PMSI (S1, G2) AD route stored in the PE 2. In the embodiment of the present application, (S1, G2) can be matched not only to S-PMSI AD routes including itself, i.e., S-PMSI (S1, G2) AD routes, but also to S-PMSI AD routes including wildcards to which it belongs, i.e., S-PMSI (,) AD routes, and PE2 determines that S-PMSI AD routes matched with (S1, G2) include S-PMSI (,) AD routes and S-PMSI (S1, G2) AD routes. After matching, PE2 may publish to PE1 the Leaf AD route corresponding to the S-PMSI AD route that was matched, i.e., PE2 may publish to PE1 a Leaf (S1, G2) AD route and a Leaf (,) AD route. Since the Leaf (x) AD route is already issued in step (2), PE2 only needs to issue the Leaf (S1, G2) AD route, and carries the IP address of PE2 in the Leaf (S1, G2) AD route, saving network resources.

In this embodiment of the present application, in order to enable both a specific multicast source and a multicast group included in the multicast join message to perform inclusion matching, PE2 does not send a route withdraw request for withdrawing a Leaf (a, x) AD route to PE1, that is, does not withdraw a tunnel whose tunnel identifier is tunnel identifier0 added by PE 2. For specific implementation, please refer to two implementation manners of step (6), which are not described herein again.

e) PE1 receives the Leaf (S1, G2) AD route from PE2, establishes a tunnel with tunnel identifier 2 according to the Leaf (S1, G2) AD route, and sends the multicast data stream including (S1, G2) to PE2 through the tunnel corresponding to tunnel identifier 2.

(10) If, according to implementation b of step (6), PE2 starts timer T1, but does not send a route withdrawal request to withdraw a Leaf (x) AD route after timer T1 ends, there is no need to reissue a Leaf (x) AD route. Then, after PE2 receives the multicast join message including (S1, G2), the interaction between PE2 and PE1 may include the following steps:

a) the PE2 transmits multicast source group information including (S1, G2) to the PE1, and starts a timer T1.

c) The PE1 issues an S-PMSI (S1, G2) AD route and a tunnel identifier 2, and transmits a multicast data stream including (S1, G2) to the PE2 based on a tunnel corresponding to the tunnel identifier 0.

d) After receiving the S-PMSI (S1, G2) AD route, the PE2 performs inclusion matching according to the indication information, that is, in the case that the BGP message including the S-PMSI (x, x) AD route also includes the inclusive-match indication information, the PE2 performs inclusion matching between the (S1, G2) and the S-PMSI (x, x) AD route, the S-PMSI (S1, G1) AD route, and the S-PMSI (S1, G2) AD route stored in the PE 2. In the embodiment of the present application, (S1, G2) can be matched not only to S-PMSI AD routes including itself, i.e., S-PMSI (S1, G2) AD routes, but also to S-PMSI AD routes including wildcards to which it belongs, i.e., S-PMSI (,) AD routes, and PE2 determines that S-PMSI AD routes matched with (S1, G2) include S-PMSI (,) AD routes and S-PMSI (S1, G2) AD routes. After matching, PE2 may publish to PE1 the Leaf AD route corresponding to the S-PMSI AD route that was matched, i.e., PE2 may publish to PE1 a Leaf (S1, G2) AD route and a Leaf (,) AD route. Since the Leaf (x) AD route has already been issued in step (2), PE2 only needs to issue the Leaf (S1, G2) AD route and carry the IP address of PE2 in the Leaf (S1, G2) AD route.

e) When the timer T1 expires, PE2 does not send a route withdraw request for withdrawing a Leaf (a,) AD route to PE1 according to the "include-match" indication message.

f) PE1 receives the Leaf (S1, G2) AD route from PE2, establishes a tunnel with tunnel identifier 2 according to the Leaf (S1, G2) AD route, and sends the multicast data stream including (S1, G2) to PE2 through the tunnel corresponding to tunnel identifier 2.

The step (9) and the step (10) are two parallel implementation modes.

Secondly, in an MLDP scenario, the route matching method provided in the embodiment of the present application includes the following steps:

(1) the PE1 sends, according to the configuration, a BGP message to the PE2, where the BGP message includes an S-PMSI (,) AD route, indication information, and a tunnel identifier0, where the tunnel identifier0 is the first identifier in the foregoing, and the indication information may be the above indication information for indicating that the inclusion matching is performed. In this scenario, the tunnel identifier is an FEC for LDP when using the mLDP protocol. The FEC includes the root node IP address of the P2MP tunnel, which in the example of FIG. 1 is the IP address of PE 1. The S-PMSI (x) AD route does not carry the LIR identity.

(2) After the PE2 receives the S-PMSI (x, x) AD route, if the PE2 stores the multicast entry corresponding to (S1, G1) according to the multicast join message including (S1, G1), and S1 is the address of the multicast source communicating with the PE1, the PE2 sends a tunnel establishment request 1 to the PE1, where the tunnel establishment request 1 includes tunnel identifier0, so as to establish a tunnel corresponding to the tunnel identifier0, that is, to establish a branch of the P2MP tree corresponding to the tunnel identifier0 using the PE1 as a root node.

(4) PE1 publishes the S-PMSI (S1, G1) AD routings and tunnel identifier 1 after a certain time interval.

(5) After receiving the S-PMSI (S1, G1) AD route, the PE2 performs inclusion matching according to the indication information, that is, when the BGP message including the S-PMSI (x, x) AD route further includes the indication information, both the S-PMSI (x, x) AD route and the S-PMSI (S1, G1) AD route stored in the PE2 are subjected to inclusion matching (S1, G1). In the embodiment of the present application, (S1, G1) can be matched not only to S-PMSI AD routes including itself, i.e., S-PMSI (S1, G1) AD routes, but also to S-PMSI AD routes including wildcards to which it belongs, i.e., S-PMSI (,) AD routes, and PE2 determines that S-PMSI AD routes matched with (S1, G1) include S-PMSI (,) AD routes and S-PMSI (S1, G1) AD routes. After matching, PE2 may send a tunnel establishment request to PE 1. Since the tunnel identified by tunnel identifier0 corresponding to the S-PMSI (a, x) AD route is already established, PE2 may only send tunnel establishment request 2 for establishing the tunnel corresponding to tunnel identifier 1 to PE1, where tunnel establishment request 2 carries tunnel identifier 1.

According to the above description, in the conventional manner, when PE2 sends tunnel establishment request 2 to PE1, timer T1 is started, and after the timer T1 times out, PE2 cancels the tunnel identified by tunnel identifier 0. In this embodiment of the present application, in order to enable both a specific multicast source and a multicast group included in the multicast join message to perform inclusion matching, PE2 needs not to send a tunnel cancellation request for cancelling a tunnel identified by tunnel identifier0 to PE 1.

In order to achieve this objective, the embodiments of the present application provide two possible implementation manners:

a) in one implementation, PE2 does not start timer T1 according to the indication information.

b) In another implementation, PE2 still starts timer T1, but does not send a tunnel cancellation request for canceling the tunnel identified by tunnel identifier0 to PE1 according to the indication information when timer T1 times out, that is, keeps joining the tunnel corresponding to tunnel identifier 0.

(7) If according to the implementation mode a) of step (5), PE2 does not start timer T1, and the tunnel corresponding to tunnel identifier0 is not revoked, and does not need to be re-established. Then, when PE2 receives the multicast join message including (S1, G2), the interaction between PE2 and PE1 may include the following steps:

c) PE1 publishes the S-PMSI (S1, G2) AD route and tunnel identifier 2 to PE 2.

d) After receiving the S-PMSI (S1, G2) AD route, the PE2 performs inclusion matching according to the indication information, that is, when the BGP message including the S-PMSI (x, x) AD route also includes the indication information, the PE2 performs inclusion matching on (S1, G2) and the S-PMSI (x, x) AD route, the S-PMSI (S1, G1) AD route, and the S-PMSI (S1, G2) AD route stored in the PE 2. In the embodiment of the present application, (S1, G2) can be matched not only to S-PMSI AD routes including itself, i.e., S-PMSI (S1, G2) AD routes, but also to S-PMSI AD routes including wildcards to which it belongs, i.e., S-PMSI (,) AD routes, and PE2 determines that S-PMSI AD routes matched with (S1, G2) include S-PMSI (,) AD routes and S-PMSI (S1, G2) AD routes. After matching, PE2 may send a tunnel setup request corresponding to the matched S-PMSI AD route to PE 1. Since, in the present embodiment, tunnel identifier0 corresponding to the S-PMSI (, AD route is not revoked, PE2 may send only a tunnel establishment request including tunnel identifier 2 to PE 1.

e) PE1 receives a tunnel establishment request including tunnel identifier 2, and establishes tunnel identifier 2 according to the tunnel establishment request.

f) The PE1 transmits the multicast data stream including (S1, G2) to the PE2 through the tunnel identifier 2.

(8) If, according to implementation b) in step (5), PE2 starts timer T1, but does not send a tunnel cancellation request for cancelling the tunnel identified by tunnel identifier0 after timer T1 ends, so when PE2 receives the multicast join packet including (S1, G2), the interaction between PE2 and PE1 may include the following steps:

c) PE1 publishes the S-PMSI (S1, G2) AD route and corresponding tunnel identifier 2 to PE 2.

d) After receiving the S-PMSI (S1, G2) AD route, the PE2 performs inclusion matching according to the indication information, that is, the (S1, G2) AD route performs inclusion matching with the S-PMSI (,) AD route, the S-PMSI (S1, G1) AD route, and the S-PMSI (S1, G2) AD route stored in the PE 2. In the embodiment of the present application, (S1, G2) can be matched not only to S-PMSI AD routes including itself, i.e., S-PMSI (S1, G2) AD routes, but also to S-PMSI AD routes including wildcards to which it belongs, i.e., S-PMSI (,) AD routes, and PE2 determines that S-PMSI AD routes matched with (S1, G2) include S-PMSI (,) AD routes and S-PMSI (S1, G2) AD routes. After matching, PE2 may send a tunnel setup request corresponding to the matched S-PMSI AD route to PE 1. Since, in the present embodiment, the tunnel corresponding to tunnel identifier0 corresponding to the S-PMSI (, AD route is not revoked, PE2 may send only a tunnel establishment request including tunnel identifier 2 to PE 1.

e) When the timer T1 expires, PE2 does not send a tunnel cancellation request for canceling the tunnel corresponding to tunnel identifier0 to PE1 according to the indication information, so as to keep joining tunnel identifier 0.

It is understood that the above steps (7) and (8) are two parallel implementations.

The interaction between PE3 and PE1 in the MLDP scenario is similar to the interaction between PE2 and PE1 mentioned above, and is not described here.

Thirdly, in a BIER scenario, the route matching method provided by the embodiment of the present application includes the following steps:

(1) PE1 sends a BGP message to PE2, including an S-PMSI (star) AD route, indication information, a LIR identification, and a tunnel identification of BIER type, according to the configuration. The tunnel identifier is the first identifier above and the LIR identifier is the second identifier above. The indication information may be exclusive-match indication information. The tunnel information of the BIER type includes an IP address and a BFR-id, and the tunnel information of the BIER type in the scene includes an IP address of PE1 and a BFR-id of PE1, for example, the BFR-id value is 1.

(2) After the PE2 receives the S-PMSI (star) AD route, if the PE2 stores the multicast entry corresponding to (S1, G1) according to the multicast join message including (S1, G1), and S1 is the address of the multicast source communicating with the PE1, the PE2 may issue a Leaf (star) AD route to the PE1 according to the LIR identifier, and carry the IP address of the PE2 and its BFR-id value, for example, the BFR-id value is 2, so as to join the tunnel corresponding to the Leaf (star) AD route.

(5) After receiving the S-PMSI (S1, G1) AD route, the PE2 performs inclusion matching according to the indication information, that is, when the BGP message including the S-PMSI (x, x) AD route also includes the indication information, the PE2 performs inclusion matching on (S1, G2) and the S-PMSI (x, x) AD route, the S-PMSI (S1, G1) AD route, and the S-PMSI (S1, G2) AD route stored in the PE 2. In the embodiment of the present application, (S1, G2) can be matched not only to S-PMSI AD routes including itself, i.e., S-PMSI (S1, G2) AD routes, but also to S-PMSI AD routes including wildcards to which it belongs, i.e., S-PMSI (,) AD routes, and PE2 determines that S-PMSI AD routes matched with (S1, G2) include S-PMSI (,) AD routes and S-PMSI (S1, G2) AD routes. After matching, PE2 may send a Leaf AD route to PE1 that corresponds to the matching S-PMSI AD route. Since the Leaf (x) AD route has already been issued in the present embodiment, PE2 may issue only the Leaf (S1, G1) AD route to PE 1.

In this embodiment, in order to enable both the specific multicast source and the specific multicast group included in the multicast join message to perform inclusion matching, the PE2 does not send a route withdraw request for withdrawing a Leaf (,) AD route to the PE1, that is, does not withdraw a tunnel corresponding to the Leaf (,) AD route that the PE2 joins. In order to achieve this objective, the embodiments of the present application provide two possible implementation manners:

b) In another implementation, PE2 still starts timer T1, but does not send a route withdrawal request for withdrawing a Leaf (x) AD route to PE1 according to the indication information at the end of timer T1, so as to keep the Leaf (x) AD route valid.

(7) If, according to implementation a of step (5), PE2 does not start timer T1, the Leaf (a) AD route is not withdrawn and does not need to be reissued. Then, after PE2 receives the multicast join message including (S1, G2), the interaction between PE2 and PE1 may include the following steps:

b) The PE1 sends the multicast data stream including (S1, G2) to the PE2 according to S-PMSI (,) AD routing.

c) The PE1 issues to the PE2, at certain time intervals, a S-PMSI (S1, G2) AD route and corresponding tunnel identification and LIR identification.

d) After receiving the S-PMSI (S1, G2) AD route, the PE2 performs inclusion matching according to the inclusive-match indication information, that is, the (S1, G2) and the S-PMSI (,) AD route, S-PMSI (S1, G1) AD route, and S-PMSI (S1, G2) AD route stored in the PE2 perform inclusion matching. In the embodiment of the present application, (S1, G2) can be matched not only to S-PMSI AD routes including itself, i.e., S-PMSI (S1, G2) AD routes, but also to S-PMSI AD routes including wildcards to which it belongs, i.e., S-PMSI (,) AD routes, and PE2 determines that S-PMSI AD routes matched with (S1, G2) include S-PMSI (,) AD routes and S-PMSI (S1, G2) AD routes.

After matching, PE2 may publish to PE1 the Leaf AD route corresponding to the S-PMSI AD route that was matched, i.e., PE2 may publish to PE1 a Leaf (S1, G2) AD route and a Leaf (,) AD route. Since the Leaf (x) AD route has already been issued in step (2), PE2 only needs to issue the Leaf (S1, G2) AD route and carry the IP address of PE2 in the Leaf (S1, G2) AD route to join the tunnel corresponding to the Leaf (S1, G2) AD route.

In this embodiment, in order to enable both the specific multicast source and the multicast group included in the multicast join packet to perform inclusion matching, PE2 does not send a route withdraw request for withdrawing a Leaf (,) AD route to PE1, that is, does not withdraw a tunnel corresponding to the Leaf (,) AD route that PE2 joins. For specific implementation, please refer to two implementation manners of step (6), which are not described herein again.

(8) If, according to implementation b of step (6), PE2 starts timer T1, but does not send a route withdrawal request to withdraw a Leaf (x) AD route after timer T1 ends, there is no need to reissue a Leaf (x) AD route. Then, after PE2 receives the multicast join message including (S1, G2), the interaction between PE2 and PE1 may include the following steps:

b) The PE1 transmits a multicast data stream including (S1, G2) to the PE2 according to a tunnel corresponding to the S-PMSI (,) AD route.

c) PE1 publishes S-PMSI (S1, G2) AD routes and corresponding tunnel identifications.

d) After receiving the S-PMSI (S1, G2) AD route, the PE2 performs inclusion matching according to the inclusive-match indication information, that is, the (S1, G2) and the S-PMSI (,) AD route, S-PMSI (S1, G1) AD route, and S-PMSI (S1, G2) AD route stored in the PE2 perform inclusion matching. In the embodiment of the present application, (S1, G2) can match not only the S-PMSI AD route including itself, i.e., the S-PMSI (S1, G2) AD route, but also the S-PMSI AD route including wildcards to which it belongs, i.e., the S-PMSI (,) AD route, so the S-PMSI AD routes matching (S1, G2) include the S-PMSI (,) AD route and the S-PMSI (S1, G2) AD route.

After matching, PE2 may publish to PE1 the Leaf AD route corresponding to the S-PMSI AD route that was matched, i.e., PE2 may publish to PE1 a Leaf (S1, G2) AD route and a Leaf (,) AD route. Since the Leaf (x) AD route has already been issued in step (2), PE2 only needs to issue the Leaf (S1, G2) AD route and carry the IP address of PE2 in the Leaf (S1, G2) AD route.

e) When the T1 timer expires, PE2 does not send a route withdraw request for withdrawing a Leaf (a) AD route to PE1 according to the indication information.

e) The PE1 receives the Leaf (S1, G1) AD route from the PE2, establishes a corresponding tunnel according to the Leaf (S1, G2) AD route, and transmits the multicast data stream including (S1, G2) to the PE2 through the tunnel.

It is understood that the above step (7) and step (8) are two parallel implementations.

Referring to fig. 3, the present application further provides a route matching apparatus 300, where the apparatus 300 may be applied to a first PE node, and the first PE node may implement the function of the first PE node in the embodiment shown in fig. 2.

The apparatus 300 comprises: a receiving unit 301 and a processing unit 302. Wherein, the receiving unit 301 may implement the function of S104 in the embodiment shown in fig. 2, and the processing unit 302 may implement the function of S105 in the embodiment shown in fig. 2.

Specifically, the receiving unit 301 is configured to receive indication information from the second PE node, where the indication information is used to indicate that a match is performed, where the match includes matching the obtained multicast source group information with the obtained N1 selective operator multicast service interface S-PMSI auto discovery AD routes, where the multicast source group information includes a multicast source S1 and a multicast group G1, N1 is an integer greater than or equal to 2, and N1S-PMSI AD routes include a first S-PMSI AD route and a second S-PMSI AD route, the first S-PMSI AD route includes at least one wildcard, and the second S-PMSI AD route includes S1 and G1;

a processing unit 302, configured to process, according to the indication information, the N2S-PMSI AD routes matching the multicast source group information to join N2 tunnels with the second PE node, where N2 is greater than or equal to 2 and less than or equal to N1, and one tunnel of the N2 tunnels corresponds to one S-PMSI AD route of the N2S-PMSI AD routes.

Optionally, the receiving unit 301 is further configured to receive a first identifier and a second identifier, which are from the second PE node and correspond to any S-PMSI AD route in the N1S-PMSI AD routes, where the first identifier is used to identify a tunnel type, and the second identifier is used to identify request leaf information.

Optionally, the tunnel type is BIER or RSVP-TE,. A processing unit 302, configured to generate N2 leaf AD routes corresponding to the N2S-PMSI AD routes according to the indication information, and issue N2 leaf AD routes to the second PE node; one leaf AD route of the N2 leaf AD routes corresponds to one S-PMSI AD route of the N2S-PMSI AD routes, the N2 leaf AD routes include a first leaf AD route including at least one wildcard and a second leaf AD route including S1 and G1.

Optionally, the receiving unit 301 is further configured to receive a first identifier, which is used to identify a tunnel type, from the second PE node and corresponds to any S-PMSI AD route in the N1S-PMSI AD routes.

Optionally, the tunnel type is mLDP, and the processing unit 302 is configured to obtain tunnel identifiers of N2 tunnels corresponding to N2S-PMSI AD routes, and send N2 label distribution protocol LDP mapping messages to the second PE node, where one S-PMSI AD route in the N2S-PMSI AD routes corresponds to a tunnel identifier of one tunnel in the N2 tunnels, and one LDP mapping message in the N2 LDP mapping messages includes one tunnel identifier in the tunnel identifiers of the N2 tunnels.

Optionally, the receiving unit 301 is configured to receive a message issued by the second PE node, where the message includes an extended provider multicast service interface Tunnel Attribute flag bit Additional PMSI Tunnel Attribute Flags, and the extended provider multicast service interface Tunnel Attribute flag bit is used to carry indication information.

For details of the route matching device 300, reference is made to the foregoing method embodiments, and details are not repeated here.

Referring to fig. 4, the present application further provides an information sending apparatus 400, where the apparatus 400 is applied to a second PE node, and can implement the function of the second PE node in the embodiment shown in fig. 2.

The apparatus 400 comprises: an acquisition unit 401 and a transmission unit 402. The obtaining unit 401 and the sending unit 402 may implement the function of S103 in the embodiment shown in fig. 2.

The acquiring unit 401 is configured to acquire indication information, where the indication information is used to indicate that performing inclusion matching includes matching multicast source group information acquired by a first PE node with acquired N1 selective operator multicast service interface S-PMSI auto discovery AD routes, where the inclusion matching includes matching the multicast source group information with a multicast group G1 and a multicast group G1, N1 is an integer greater than or equal to 2, and N1S-PMSI AD routes include a first S-PMSI AD route and a second S-PMSI AD route, the first S-PMSI AD route includes at least one wildcard, and the second S-PMSI AD route includes S1 and G1;

a sending unit 402, configured to send indication information to the first PE node.

Optionally, the sending unit 402 is further configured to send, to the first PE node, a first identifier and a second identifier corresponding to any S-PMSI AD route in the N1S-PMSI AD routes, where the first identifier is used to identify a tunnel type, and the second identifier is used to identify request leaf information.

Optionally, the sending unit 402 is further configured to send, to the first PE node, a first identifier corresponding to any S-PMSI AD route of the N1S-PMSI AD routes, where the first identifier is used to identify a tunnel type.

Optionally, the sending unit 402 is configured to issue a message to the first PE node, where the message includes an extended provider multicast service interface Tunnel Attribute flag (Additional PMSI Tunnel Attribute Flags), and the extended provider multicast service interface Tunnel Attribute flag is used to carry indication information.

For details of the information sending apparatus 400, please refer to the foregoing method embodiments, which are not described herein again.

Correspondingly, the embodiment of the present application further provides a route matching device corresponding to the route matching apparatus 300, including a processor and a memory; the memory to store instructions; the processor is configured to execute the instructions in the memory and execute the method for route matching performed by the first PE node in the embodiment shown in fig. 2.

Correspondingly, the embodiment of the present application further provides an information sending device corresponding to the information sending apparatus 400, including a processor and a memory; the memory to store instructions; the processor is configured to execute the instructions in the memory, and execute the information sending method executed by the second PE node in the embodiment shown in fig. 2.

The hardware configuration of the route matching device corresponding to the route matching apparatus 300 and the hardware configuration of the information transmitting device corresponding to the information transmitting apparatus 400 may be as shown in fig. 5. Fig. 5 is a schematic structural diagram of an apparatus according to an embodiment of the present application.

Referring to fig. 5, the apparatus 500 includes: a processor 510, a communication interface 520, and a memory 530. Wherein the number of the processors 510 in the device 500 may be one or more, and one processor is taken as an example in fig. 5. In the embodiment of the present application, the processor 510, the communication interface 520, and the memory 530 may be connected by a bus system or other means, wherein fig. 5 is exemplified by the connection via the bus system 540.

Processor 510 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP. The processor 510 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof.

Memory 530 may include volatile memory (RAM), such as random-access memory (RAM); the memory 530 may also include a non-volatile memory (english: non-volatile memory), such as a flash memory (english: flash memory), a hard disk (HDD) or a solid-state drive (SSD); memory 530 may also comprise a combination of memories of the sort described above.

Optionally, memory 530 stores an operating system and programs, executable modules or data structures, or subsets thereof, or extensions thereof, wherein the programs may include various operating instructions for performing various operations. The operating system may include various system programs for implementing various basic services and for handling hardware-based tasks. The processor 510 can read the program in the memory 530 to implement the method for adjusting the transmission rate provided by the embodiment of the present application.

The bus system 540 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus system 540 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.

The embodiment of the application also provides a route matching system, which comprises a first PE node and a second PE node. The first PE node in the system may execute the processing steps of the first PE node in the embodiment of fig. 2, or correspondingly, the first PE node in the system is the route matching apparatus 300 in the embodiment shown in fig. 3. The second PE node in the system may execute the processing steps of the second PE node in the embodiment of fig. 2, or correspondingly, the second PE node in the system is the information sending apparatus 400 in the embodiment shown in fig. 4.

The present application further provides a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the route matching method performed by the first PE node according to the foregoing method embodiment.

The embodiment of the present application further provides a computer-readable storage medium, which includes instructions, when the computer runs on a computer, to cause the computer to execute the information sending method performed by the second PE node according to the above method embodiment.

Embodiments of the present application further provide a computer program product containing instructions, which when run on a computer, cause the computer to perform the route matching method performed by the first PE node provided in the above method embodiments.

The present application further provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the information sending method executed by the second PE node provided in the above method embodiment.

The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical module division, and other division manners may be available in actual implementation, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be obtained according to actual needs to achieve the purpose of the solution of the present embodiment.

In addition, each module unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a hardware form, and can also be realized in a software module unit form.

The integrated unit, if implemented as a software module unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above-described embodiments are intended to explain the objects, aspects and advantages of the present invention in further detail, and it should be understood that the above-described embodiments are merely exemplary embodiments of the present invention.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method of route matching, the method comprising:

the first operator edge PE node receives indication information from the second PE node, wherein the indication information is used for indicating that inclusion matching is performed, the inclusion matching comprises matching of acquired multicast source group information and acquired N1 selective operator multicast service interface S-PMSI automatic discovery AD routes, the multicast source group information comprises a multicast source S1 and a multicast group G1, the N1 is an integer greater than or equal to 2, the N1S-PMSI AD routes comprise a first S-PMSI AD route and a second S-PMSI AD route, the first S-PMSI AD route comprises at least one wildcard, and the second S-PMSI AD route comprises the S1 and G1;

the first PE node processes N2S-PMSI AD routes matched with the multicast source group information according to the indication information so as to join N2 tunnels with the second PE node, wherein N2 is greater than or equal to 2 and less than or equal to N1, and one tunnel of the N2 tunnels corresponds to one S-PMSI AD route of the N2S-PMSI AD routes.

2. The method of claim 1, further comprising:

the first PE node receives a first identification and a second identification from a second PE node, wherein the first identification corresponds to any one of the N1S-PMSI AD routes, the first identification is used for identifying a tunnel type, and the second identification is used for identifying request leaf information.

3. The method of claim 2, wherein the tunnel type is BIER or RSVP-TE, and wherein the processing, by the first PE node, the N2S-PMSI AD routes matching the multicast source group information according to the indication information comprises:

the first PE node generating N2 leaf AD routes corresponding to N2S-PMSI AD routes according to the indication information, one of the N2 leaf AD routes corresponding to one of the N2S-PMSI AD routes, the N2 leaf AD routes including a first leaf AD route and a second leaf AD route, the first leaf AD route including the at least one wildcard, the second leaf AD route including the S1 and the G1;

the first PE node issues the N2 leaf AD routes to the second PE node.

4. The method of claim 1, further comprising:

the first PE node receives a first identification corresponding to any one of the N1S-PMSI AD routes from a second PE node, the first identification being used to identify a tunnel type.

5. The method of claim 4, wherein the tunnel type is mLDP, and wherein the processing, by the first PE node, the N2S-PMSI AD routes that match the multicast source group information according to the indication information comprises:

the first PE node acquires tunnel identifiers of N2 tunnels corresponding to the N2S-PMSI AD routes, wherein one S-PMSI AD route in the N2S-PMSI AD routes corresponds to the tunnel identifier of one tunnel in the N2 tunnels;

the first PE node sends N2 Label Distribution Protocol (LDP) mapping messages to the second PE node, wherein one of the N2 LDP mapping messages comprises one of the tunnel identifications of the N2 tunnels.

6. The method of any of claims 1-5, wherein the first operator edge (PE) node receiving the indication information from the second PE node comprises:

and the first PE node receives a message issued by the second PE node, wherein the message comprises an extended operator multicast service interface tunnel attribute flag bit Additional PMSI Tunnel attribute Flags, and the extended operator multicast service interface tunnel attribute flag bit is used for carrying the indication information.

7. An information sending method, characterized in that the method comprises:

the second provider edge PE node obtains indication information, the indication information is used for indicating that inclusion matching is performed, the inclusion matching includes matching of multicast source group information obtained by the first PE node with obtained N1 selective provider multicast service interface S-PMSI automatic discovery AD routes, the multicast source group information includes a multicast source S1 and a multicast group G1, the N1 is an integer greater than or equal to 2, the N1S-PMSI AD routes include a first S-PMSI AD route and a second S-PMSI AD route, the first S-PMSI AD route includes at least one wildcard, and the second S-PMSI AD route includes the S1 and G1;

and the second PE node sends the indication information to the first PE node.

8. The method of claim 7, further comprising:

and the second PE node sends a first identifier and a second identifier corresponding to any one S-PMSI AD route in the N1S-PMSI AD routes to the first PE node, wherein the first identifier is used for identifying the type of the tunnel, and the second identifier is used for identifying the request leaf information.

9. The method of claim 7, further comprising:

and the second PE node sends a first identifier corresponding to any one S-PMSI AD route in the N1S-PMSI AD routes to the first PE node, wherein the first identifier is used for identifying the type of the tunnel.

10. The method of any of claims 7-9, wherein sending the indication information to the first PE node by the second PE node comprises:

and the second PE node issues a message to the first PE node, wherein the message comprises an extended operator multicast service interface Tunnel Attribute flag bit Additional PMSI Tunnel Attribute Flags, and the extended operator multicast service interface Tunnel Attribute flag bit is used for carrying the indication information.

11. A route matching apparatus applied to a first operator edge PE node, the apparatus comprising:

a receiving unit, configured to receive indication information from the second PE node, where the indication information is used to indicate that an inclusion matching is performed, where the inclusion matching includes matching the obtained multicast source group information with the obtained N1 selective operator multicast service interface S-PMSI auto discovery AD routes, where the multicast source group information includes a multicast source S1 and a multicast group G1, where N1 is an integer greater than or equal to 2, the N1S-PMSI AD routes include a first S-PMSI AD route and a second S-PMSI AD route, the first S-PMSI AD route includes at least one wildcard, and the second S-PMSI AD route includes the S1 and the G1;

a processing unit, configured to process, according to the indication information, N2S-PMSI AD routes matched with the multicast source group information to join N2 tunnels with the second PE node, where N2 is greater than or equal to 2 and less than or equal to N1, and one of the N2 tunnels corresponds to one of the N2S-PMSI AD routes.

12. The apparatus of claim 11,

the receiving unit is further configured to receive a first identifier and a second identifier, which are from a second PE node and correspond to any one of the N1S-PMSI AD routes, where the first identifier is used to identify a tunnel type, and the second identifier is used to identify request leaf information.

13. The apparatus of claim 12, wherein the tunnel type is BIER or RSVP-TE;

the processing unit is configured to generate N2 leaf AD routes corresponding to N2S-PMSI AD routes according to the indication information, and issue the N2 leaf AD routes to the second PE node; one of the N2 leaf AD routes corresponds to one of the N2S-PMSI AD routes, the N2 leaf AD routes include a first leaf AD route including the at least one wildcard and a second leaf AD route including the S1 and the G1.

14. The apparatus of claim 11,

the receiving unit is further configured to receive a first identifier, which is used for identifying a tunnel type, from a second PE node and corresponds to any one of the N1S-PMSI AD routes.

15. The apparatus of claim 14, wherein the tunnel type is mLDP;

the processing unit is configured to obtain tunnel identifiers of N2 tunnels corresponding to the N2S-PMSI AD routes, and send N2 label distribution protocol LDP mapping messages to the second PE node, where one S-PMSI AD route of the N2S-PMSI AD routes corresponds to a tunnel identifier of one tunnel of the N2 tunnels, and one LDP mapping message of the N2 LDP mapping messages includes one tunnel identifier of the tunnel identifiers of the N2 tunnels.

16. The apparatus according to any one of claims 11-15,

the receiving unit is configured to receive a message issued by the second PE node, where the message includes an extended operator multicast service interface tunnel attribute flag bit Additional PMSI tunnel attribute Flags, and the extended operator multicast service interface tunnel attribute flag bit is used to carry the indication information.

17. An information sending apparatus, applied to a second operator edge (PE) node, the apparatus comprising:

an obtaining unit, configured to obtain indication information, where the indication information is used to indicate that a content matching is performed, where the content matching includes matching multicast source group information obtained by a first PE node with obtained N1 selective operator multicast service interface S-PMSI auto discovery AD routes, where the multicast source group information includes a multicast source S1 and a multicast group G1, where N1 is an integer greater than or equal to 2, the N1S-PMSI AD routes include a first S-PMSI AD route and a second S-PMSI AD route, the first S-PMSI AD route includes at least one wildcard, and the second S-PMSI AD route includes S1 and G1;

a sending unit, configured to send the indication information to the first PE node.

18. The apparatus of claim 17,

the sending unit is further configured to send, to the first PE node, a first identifier and a second identifier corresponding to any S-PMSI AD route of the N1S-PMSI AD routes, where the first identifier is used to identify a tunnel type, and the second identifier is used to identify request leaf information.

19. The apparatus of claim 17,

the sending unit is further configured to send, to the first PE node, a first identifier corresponding to any S-PMSI AD route of the N1S-PMSI AD routes, where the first identifier is used to identify a tunnel type.

20. The apparatus of any one of claims 17-19,

the sending unit is configured to issue a message to the first PE node, where the message includes an extended operator multicast service interface tunnel attribute flag bit Additional PMSI tunnel attribute Flags, and the extended operator multicast service interface tunnel attribute flag bit is used to carry the indication information.