CN106357541B

CN106357541B - Information transmission method and device

Info

Publication number: CN106357541B
Application number: CN201610813210.1A
Authority: CN
Inventors: 黄李伟; 吴慧英; 王伟
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Information Technologies Co Ltd
Priority date: 2016-09-09
Filing date: 2016-09-09
Publication date: 2019-12-17
Anticipated expiration: 2036-09-09
Also published as: CN106357541A

Abstract

The embodiment of the invention provides an information transmission method and a device, wherein the method comprises the following steps: determining a rendezvous point corresponding to the multicast group; generating protocol updating information according to the address of the convergent point; and sending the protocol updating information to each PE (provider edge) of the backbone network so that each PE in the multicast group generates a rendezvous point information table according to the protocol updating information, wherein the rendezvous point information table is used for creating a backbone network core equipment tunnel in the multicast group. By the embodiment of the invention, the address of the convergent point can be synchronized to all PEs in the MVPN by adopting the MVPN BGP protocol message, thereby solving the problem of dependence of BSR information transmission in the existing MVPN on the Inclusive P-Tunnel.

Description

Information transmission method and device

Technical Field

The present invention relates to the field of computer network technology, and in particular, to an information delivery method and an information delivery apparatus.

Background

virtual Private Network (VPN) refers to a technology for establishing a Private Network on a public Network. A VPN network consists of the public network of the operator and the sites (sites) of the users, which are isolated from each other and can only be intercommunicated with the help of a public network. The Multicast VPN (MVPN) is a technology for implementing Multicast transmission in a VPN Network.

Currently, in MVPN networking, two types of Point-To-multipoint master station (P2 MP) tunnels are generally established, which are: a dynamically compatible backbone network core device Tunnel (Inclusive P-Tunnel) and a dynamically Selective backbone network core device Tunnel (Selective provider Tunnel). The first dynamic Inclusive P-Tunnel is a Tunnel which is mainly established after an MVPN Border Gateway Protocol (BGP) session is established and enables an MVPN capability, and the Tunnel mainly functions to transmit Buffer Status Report (BSR) information and forward any multicast source data; the second dynamic Selective P-Tunnel mainly has a function of not forwarding the multicast packet to a backbone Edge Router (PE) node that does not require the multicast source flow when a special multicast source joins in registration of the packet.

specifically, after the MVPN BGP neighbor relation is established between the PEs, a corresponding dynamic Inclusive P-Tunnel is established. For example, PE1, PE2, and PE3 establish MVPN BGP neighbors two by two and dynamic Inclusive P-tunnels two by two, as shown in fig. 1, both Tunnel1 and Tunnel2 are Inclusive P-tunnels. Among them, the most important role of tunnel1 is to notify PE1 device, and the most important role of tunnel2 is to notify PE2 device, and the Rendezvous Point (RP) is above the Customer Edge Router (CE) hung under PE 3. After receiving the BSR information sent by tunnel1, PE1 forwards the multicast traffic sent by the multicast Source (Source, S) to the PE1 device to the PE3 device; if Receiver (Receiver, R) wants to receive multicast data of multicast source S, it sends multicast join request message to RP. After forming a multicast forwarding table on PE3, the multicast data is forwarded to PE 2.

however, no Inclusive P-Tunnel protection mechanism exists in MVPN networking at present. If the Inclusive P-Tunnel fails (Down), the BSR information cannot be sent to the PE that establishes the MVPN BGP neighbor, so that the subsequent multicast service cannot be used normally.

Disclosure of Invention

In view of the foregoing problems, embodiments of the present invention are provided to provide an information delivery method and an information delivery apparatus, which overcome the foregoing problems or at least partially solve the foregoing problems, so as to solve the problem of dependence of BSR information delivery on an Inclusive P-Tunnel in the existing MVPN, thereby ensuring normal use of multicast services.

In order to solve the above problem, an embodiment of the present invention discloses an information transfer method, including:

Determining a rendezvous point corresponding to the multicast group;

Generating protocol updating information according to the address of the convergent point;

And sending the protocol updating information to each PE (provider edge) of the backbone network so that each PE in the multicast group generates a rendezvous point information table according to the protocol updating information, wherein the rendezvous point information table is used for creating a backbone network core equipment tunnel in the multicast group.

correspondingly, the embodiment of the invention also discloses another information transmission method, which comprises the following steps:

when protocol updating information is received, analyzing the protocol updating information to obtain an address of a convergent point;

And generating a convergent point information table by adopting the address of the convergent point, wherein the convergent point information table is used for creating a backbone network core equipment tunnel in a multicast group corresponding to the convergent point.

The embodiment of the invention also discloses an information transmission device, which comprises:

a rendezvous point determining module, configured to determine a rendezvous point corresponding to the multicast group;

The information generation module is used for generating protocol updating information according to the address of the convergent point;

And the information sending module is used for sending the protocol updating information to each PE (provider edge) of the backbone network so that each PE in the multicast group generates a rendezvous point information table according to the protocol updating information, wherein the rendezvous point information table is used for creating a backbone network core equipment tunnel in the multicast group.

the embodiment of the invention also discloses another information transmission device, which comprises:

The information analysis module is used for analyzing the protocol updating information to obtain the address of the convergent point when the protocol updating information is received;

And the information table generating module is used for generating a convergent point information table by adopting the address of the convergent point, wherein the convergent point information table is used for creating a backbone network core equipment tunnel in a multicast group corresponding to the convergent point.

The embodiment of the invention has the following advantages:

First, the embodiment of the present invention may generate protocol update information according to the address of the rendezvous point, for example, the protocol update information is generated by adding the address of the rendezvous point to a border gateway protocol packet, and the protocol update information may be sent to each PE in the network, so that each PE in the multicast group may generate a rendezvous point information table according to the protocol update information, that is, the address of the rendezvous point carried by BSR information is synchronized to all PEs in MVPN through an MVPN BGP protocol packet, thereby solving the problem of dependence of BSR information transfer on Inclusive P-Tunnel in the existing MVPN.

secondly, the PE of the embodiment of the present invention may obtain the address of the rendezvous point by analyzing the received protocol update information, and may generate a corresponding rendezvous point information table by using the address information of the rendezvous point, where the rendezvous point information table may be used to create a backbone network core device tunnel for transmitting service data, that is, the backbone network core device tunnel may be used to forward multicast data, thereby ensuring normal use of multicast service.

Drawings

fig. 1 is a schematic diagram of establishing an Inclusive P-Tunnel in the existing MVPN networking;

FIG. 2 is a schematic diagram of a multicast VPN;

Fig. 3 is a schematic diagram of a P2MP tunnel established by an existing MVPN;

FIG. 4 is a flow chart of the steps of one information delivery method embodiment of the present invention;

FIG. 5 is a flow chart of steps in another information delivery method embodiment of the present invention;

FIG. 6 is a flow chart of steps of a method of information delivery in one particular example of the invention;

FIG. 7A is a diagram illustrating the transmission of protocol update information in an exemplary embodiment of the invention;

Fig. 7B is a diagram illustrating synchronization of RP information to a newly added PE in an embodiment of the present invention.

FIG. 8A is a block diagram of an embodiment of an information delivery device of the present invention;

FIG. 8B is a block diagram of an alternate embodiment of an information delivery device of the present invention;

FIG. 9A is a block diagram of another information delivery device embodiment of the present invention;

Fig. 9B is a block diagram of an alternative embodiment of an information delivery apparatus according to the present invention.

Detailed Description

in order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below.

Fig. 2 shows a schematic diagram of a multicast VPN. Both the multicast source and the user (i.e., recipient) are within the VPN. The private network side adopts a Protocol Independent Multicast (PIM) Protocol. The public network is a Multi-Protocol Label Switching (MPLS) backbone network, and P2MP Label forwarding between PEs is constructed by using Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE). The multicast flow encapsulates the MPLS label on the PE connected with the CE, and forwards the MPLS label to other PE with a receiver through a resource reservation Protocol (RSVP) P2MP tunnel, the PE with the receiver removes the MPLS encapsulation, and sends the MPLS encapsulation to the lower-hanging CE by common three-layer multicast.

At present, MVPN performs PE automatic discovery through BGP, a BGP peer is established between PE routers within the same MBGP-MVPN, and MBGP-MVPN control information is exchanged with each other through a Multiprotocol Border Gateway Protocol (MBGP). BGP enables PE auto-discovery through a new address family, such as the Multicast Virtual Private Network (MCAST-VPN) address family. Any PE connected to an MBGP-MVPN must publish a Route through BGP, where the Route includes a Route Target (RT) extended community attribute, and the peer PE receiving the Route determines, through the RT attribute, whether the sender is the same MBGP-MVPN as itself, and then notifies RSVP-TE to establish a P2MP tunnel.

in MVPN networking, if the service data and the protocol packet are transmitted through the same tunnel, the protocol packet is easily flushed by the service data due to the large service data. Therefore, to avoid the problem of packet loss of protocol packets, two types of P2MP tunnels are usually established in MVPN networking, which are: the dynamic Inclusive P-Tunnel and the dynamic Selective P-Tunnel adopt the Inclusive P-Tunnel to transmit a protocol message and adopt the Selective P-Tunnel to transmit service data. Any PE that has multicast message requirements (e.g., needs to send control messages or traffic) will first initiate dynamic P-Tunnel creation of the compatibility tree that will connect all the receiver PEs. The PE of the initiator issues an inter-autonomous system (Intra-AS) dynamic compatible PMSI interface (Inclusive-PMSI, I-PMSI) Auto Discovery Route (Auto-Discovery Route, a-D Route) to each PE through MBGP, where the Type (Type) of Network Layer Reachable Information (NLRI) carrying a Tunnel Attribute (Tunnel Attribute) providing a Multicast service interface (Provider multimedia service interface, PMSI) is 1. Wherein the PMSI Tunnel attribute carries the type of the P-Tunnel to be created. Unlike the Inclusive P-Tunnel creation flow, the creation of Selective P-tunnels does not know which PEs are in the recipient set. The head node PE issues a Selective-PMSI interface (S-PMSI) a-D route carrying NLRI Type 3 of the PMSI tunnel attribute by using MBGP, and the PE that needs to receive the traffic responds to Leaf (Leaf) a-D route having NLRI Type 4. I.e., Label Switched Path (LSP) head node, needs to know which PEs need to receive data for a particular C-flow.

Fig. 3 shows a schematic diagram of a P2MP tunnel established by an existing MVPN. AS shown in fig. 3, PE1 may publish intra-AS I-PMSI a-D route carrying NLRI Type of PMSI tunnel attribute of 1 to PE2 and PE 3; when the PE2 and PE3 receive the a-D route, an Inclusive P-Tunnel corresponding to the multicast group may be created according to the type of the PMSI Tunnel that carries the P-Tunnel to be created, for example, an Inclusive P-Tunnel belonging to VPN a is created. In addition, PE1 may also issue S-PMSI a-D route carrying NLRI Type of PMSI tunnel attribute of 3 to PE2 and PE 3; when receiving the S-PMSI a-D route, PE2 and PE3 respond to PE1 with a Leaf a-D route whose NLRI Type is 4, so that PE1 knows that PE2 and PE3 need to receive the multicast message of VPN a. The Leaf a-D route responded by the PE2 carries the MPLS label 1151, so that the PE1 can send the service data to the PE2 according to the MPLS label 1151; leaf A-D route responded by PE3 carries MPLS label 1150, so that PE1 can send service data to PE3 according to MPLS label 1150.

obviously, the delivery of BSR information in the existing MVPN depends on the Inclusive P-Tunnel. If the Inclusive P-Tunnel Down falls, the BSR information cannot be sent to the PE that establishes the MVPN BGP neighbor, and the subsequent multicast service cannot be used normally.

one of the core concepts of the embodiments of the present invention is that, while the MVPN BGP neighbor is established, the address of the rendezvous point in the BSR information is synchronized to all peer PEs in the MVPN through the MVPN BGP protocol packet, so that the transmission of the BSR information does not depend on the Inclusive P-Tunnel any more, that is, the problem of the dependency of BSR information transmission on the Inclusive P-Tunnel in the existing MVPN is solved, thereby ensuring the normal use of the multicast service.

referring to fig. 4, a flowchart illustrating steps of an embodiment of an information delivery method according to the present invention is shown, which may specifically include the following steps:

step 402, determine the rendezvous point corresponding to the multicast group.

Generally, MVPN may perform automatic discovery of PEs through BGP protocol, and establish MVPN BGP neighbor relationship between PEs to form a multicast group. In MVPN networking, a corresponding Rendezvous Point (RP) may be configured for a multicast group based on MVPN BGP neighbor relations between PEs, so that all senders and receivers in the multicast group may converge at the Rendezvous Point. Embodiments of the present invention may refer to a CE configured as an RP device, and may refer to a PE connected to the RP device as a specific PE. The specific PE may determine the RP device as the rendezvous point corresponding to the multicast group to which the RP device belongs.

Step 404, generating protocol update information according to the address of the rendezvous point.

After determining the rendezvous point of the multicast group, the embodiment of the invention can add the address of the rendezvous point into a Border Gateway Protocol (BGP) message to generate Protocol update information corresponding to the multicast group. The protocol Update (Update) information may include: NLRI carrying RP information, such as BSR information.

As a specific example of the present invention, when MVPN BGP neighbors are established between PE1, PE2, and PE3, a CE under PE3 may be configured as an RP corresponding to a multicast group formed by PE1, PE2, and PE3, that is, a CE under PE3 may be used as an RP device, so that an Internet Protocol (IP) address of the CE may be used as a node address of the RP, and the node address of the RP may be added to a BGP message to generate BGP Update information. The NLRI carried by the BGP Update information may specifically include parameter information such AS a Route Type (Route Type), a Route identifier (RD), a Source Autonomous System (Source AS) number of a Multicast Source, an RP Address (Address), and a Multicast Group (Multicast Group). The value of the routing type can be used for determining whether the NLRI carries RP synchronization information; RD may be used to distinguish between individual customers who apparently connect to a provider VPN route; the RP address may be used to represent an RP address carried in BSR information; the Multicast Group may be used to indicate a network segment of a Multicast Group corresponding to the RP, such as a range of Multicast groups that the RP may serve.

Step 406, sending the protocol update information to each PE, so that each PE in the multicast group generates a rendezvous point information table according to the protocol update information.

After the neighbor relation between the PEs is successfully established, the specific PE connected with the RP device in the embodiment of the present invention may transmit the protocol update information to each PE in the MVPN networking in a BGP notification manner based on the established neighbor relation, so that each PE in the multicast group corresponding to the RP may generate the rendezvous point information table according to the protocol update information.

the PE in the embodiment of the invention can analyze the received protocol updating information to obtain the address of the convergent point in the protocol updating information, thereby generating the convergent point information table corresponding to the multicast group based on the address of the convergent point. Specifically, after receiving the protocol update information, the PE may extract the address of the rendezvous point and the network segment of the multicast group corresponding to the rendezvous point from the protocol update information, so as to determine whether to generate the rendezvous point information table corresponding to the multicast group by verifying whether the local IP address is in the network segment. If the local IP address is in the network segment of the multicast group, the PE can determine that the protocol updating information accords with the local configuration introduction condition, and further adopts the parameter information carried in the protocol updating information to generate the convergent point information table corresponding to the multicast group. If the local IP address is not in the network segment of the multicast group, the PE can determine that the protocol updating information does not conform to the local configuration introduction condition, and further ignore the protocol updating information, if the protocol updating information is not processed. The data recorded in the rendezvous point information table may include: and parameter information such as VPN Routing and Forwarding (VRF), an address of a rendezvous point and a next hop (nexthop), and the like, and can be used for creating a backbone core device tunnel in the multicast group. The backbone core device tunnel may be used to transport traffic data.

for example, with reference to the above example, after the MVPN BGP neighbor relationship between PE3 and PE1 and PE2 is successfully established, PE3 may send protocol update information to PE1 and PE2 in a BGP notification manner, so that PE1 and PE2 may locally generate a corresponding RP information table based on the node address of the RP carried in the protocol update information. PE1 and PE2 may create a backbone core device tunnel with PE3 according to the data recorded in the RP information table, so as to transmit the service data using the created backbone core device tunnel.

Obviously, the embodiment of the present invention may generate the protocol update information according to the address of the rendezvous point, for example, the protocol update information is generated by adding the address of the rendezvous point to the border gateway protocol message, and the protocol update information may be sent to each PE in the multicast group, so that each PE in the multicast group corresponding to the rendezvous point may generate the rendezvous point information table according to the protocol update information, that is, the address of the rendezvous point carried by the BSR information is synchronized to all PEs in the MVPN through the MVPN BGP protocol message, thereby solving the problem of dependence of BSR information transfer on the Inclusive P-Tunnel in the existing MVPN.

Of course, the embodiment of the present invention may also determine, according to the pre-established neighbor relationship between the PEs, each PE in the multicast group corresponding to the rendezvous point, and further may send the protocol update information corresponding to the multicast group to the determined PE, that is, may avoid sending the protocol update information to the PE not belonging to the multicast group corresponding to the rendezvous point, and save network resources.

Referring to fig. 5, a flowchart illustrating steps of another embodiment of an information delivery method of the present invention is shown, which may specifically include the following steps:

Step 502, when protocol update information is received, the protocol update information is analyzed to obtain an address of an aggregation point.

In the embodiment of the present invention, when receiving the protocol update information sent by a specific PE, the PE may locally introduce a route according to the protocol update information. Specifically, the PE may analyze the received protocol update information to obtain information carried in the protocol update information, such as NLRI including RP information; and, the obtained information may be employed to determine whether the protocol update information complies with the local configuration lead-in condition. The NLRI may specifically include parameter information such as a routing type, a routing identifier, a home-made system number of a multicast source, an RP address, and a multicast group, which is not specifically limited in this embodiment of the present invention.

if the local configuration introduction condition is met, step 504 may be executed to locally introduce the route carried by the protocol update information, for example, introduce a type 8 route including an RP address using the resolved address of the rendezvous point.

And step 504, generating a convergent point information table by adopting the address of the convergent point.

in the embodiment of the present invention, after determining that the protocol update information conforms to the local configuration introduction condition, the PE may locally generate the rendezvous point information table corresponding to the multicast group by using the address of the rendezvous point carried in the protocol update information. The rendezvous point information table may be used to create a backbone core device tunnel in the multicast group corresponding to the rendezvous point, and specifically may include an address of the rendezvous point and BGP remote neighbor information, such as next-hop device information.

as a specific example of the present invention, in combination with the above example, after receiving the RP synchronization information sent by PE3, PE1 and PE2 may locally perform BGP route introduction. If the BGP route carried by the RP synchronization information meets the locally configured introduction condition of PE1, PE1 may analyze the BGP route to locally maintain an address table entry of an RP by analyzing RP information and BGP remote neighbor information, as shown in table 1, that is, generate a corresponding RP information table. Similarly, if the RP synchronization information also meets the locally configured import condition of PE2, PE2 may also generate an RP information table as shown in table 1. Wherein, the VRF is VPN1, which may indicate that VPN1 is a VPN corresponding to the VRF of the multicast group; the RP is 4.4.4.4, which can be used to indicate that the RP with the address of 4.4.4.4 is the rendezvous point corresponding to the multicast group; nexthop is PE3 and the next hop in the multicast group that can be used to represent traffic data is PE 3.

VRF	RP	nexthop
			VPN1	4.4.4.4	PE3

TABLE 1

After the RP information table is generated, PE1 and PE2 may use the RP information table to create a backbone core device Tunnel connected to PE3, such as actively establishing a Selective P-Tunnel, which may be identified as Tunnel1 and Tunnel2, respectively. Wherein, the backbone network core device tunnel connected with PE1 and PE3 is tunnel1, the source address of tunnel1 is 1.1.1.1, and the destination address is 3.3.3.3; the backbone network core device tunnel connected to PE2 and PE3 is tunnel2, and the source address of tunnel2 is 2.2.2.2 and the destination address is 3.3.3.3.

To sum up, the PE of the embodiment of the present invention may obtain the address of the rendezvous point by analyzing the protocol update information, and may generate a corresponding rendezvous point information table by using the address of the rendezvous point, that is, the address of the rendezvous point carried by the BSR information may be received through the MVPN BGP protocol packet, thereby solving the problem of dependence of BSR information transfer on the Inclusive P-Tunnel in the existing MVPN; and, the convergent point information table can be used to create a backbone network core device tunnel for transmitting service data, that is, the backbone network core device tunnel can be used to forward multicast data, thereby ensuring normal use of multicast service.

in a preferred embodiment of the present invention, generating the protocol update information according to the address of the aggregation point may specifically include: acquiring the address configured by the convergent point, and generating corresponding network layer reachable information; and adding the network layer reachable information into a border gateway protocol message to generate the protocol updating information. The network layer reachable information may include a network segment of the multicast group corresponding to the rendezvous point, that is, the protocol update information may carry the network segment of the multicast group corresponding to the rendezvous point.

In the MVPN networking, a multicast group can be formed by establishing the neighbor relation between PEs in the multicast virtual private network, for example, the identifier is VPN 1; and a PE connected to the customer network edge router as the rendezvous point RP may be determined as a specific PE of the multicast group corresponding to the multicast virtual private network. Specifically, a specific PE in the multicast group may obtain a loopback interface address from the suspended CE, and use the obtained loopback interface address as an address of the rendezvous point, so that the address may be added to network layer reachable information carried in the BGP message to update the network layer reachable information carried in the BGP message, and generate protocol update information corresponding to the multicast group, such as BGP update information. Optionally, when the protocol update information is sent, the specific PE may determine, according to the network segment carried by the protocol update information, whether the peer PE that establishes the neighbor relationship with the specific PE belongs to a PE in the multicast group corresponding to the rendezvous point. If the opposite end PE belongs to the PE in the multicast group corresponding to the rendezvous point, the specific PE can send protocol updating information to the opposite end PE so as to trigger the opposite end PE to generate a corresponding rendezvous point information table according to the protocol updating information, and therefore a backbone network core equipment tunnel can be established with the opposite end PE so as to transmit service data in the multicast group. Of course, if the peer PE does not belong to the PE in the multicast group corresponding to the rendezvous point, the specific PE may ignore the peer PE, and if the protocol update information is not sent to the peer PE, network resources may be saved.

in a preferred embodiment of the present invention, determining, according to the neighbor relation, each PE belonging to the multicast group may specifically include: and determining each PE belonging to the network segment carried by the protocol updating information as each PE in the multicast group corresponding to the aggregation point based on the neighbor relation.

Specifically, after the neighbor relationship between the PEs is successfully established, the specific PE of the multicast group may determine, based on the neighbor relationship with the PE of the opposite end, the PE in the network segment specified in the network layer reachable information as the PE in the rendezvous point multicast group, and may further send rendezvous point update information by the determined PE, so as to trigger the PE receiving the protocol information to generate the rendezvous point information table corresponding to the multicast group. When receiving the protocol updating information, the PE can detect whether the protocol updating information meets the local configuration introduction condition; if the information accords with the preset local configuration introduction condition, analyzing the protocol updating information which accords with the local configuration introduction condition to obtain the address and the neighbor information of the convergent point, and generating a convergent point information table by adopting the address and the neighbor information; if not, the corresponding convergent point information table does not need to be generated according to the protocol updating information, and if the protocol updating information can be ignored or deleted.

of course, the specific PE may also determine the PE belonging to the multicast group corresponding to the rendezvous point in other manners, which is not limited in this embodiment of the present invention. For example, a specific PE may determine whether a peer PE belongs to a multicast group corresponding to the rendezvous point by verifying whether the peer PE establishes a neighbor relation for the rendezvous point. If the opposite end PE establishes a neighbor relation with the specific PE aiming at the rendezvous point, the specific PE can determine that the opposite end PE belongs to the multicast group corresponding to the rendezvous point. If the opposite-end PE does not establish a neighbor relationship with the specific PE for the rendezvous point, the specific PE may determine that the opposite-end PE does not belong to the multicast group corresponding to the rendezvous point.

In a preferred embodiment of the present invention, the information transfer method further includes: after the convergent point information table is generated, feeding back route confirmation information to the specific PE of the multicast group, wherein the route confirmation information is used for responding the protocol updating information; and creating a backbone network core device tunnel connected with the specific PE based on the convergent point information table. The backbone network core equipment tunnel is used for transmitting the service data in the multicast group; the particular PE is the PE that connects the rendezvous points, such as PE3 in the example above.

In the embodiment of the present invention, after the peer PE generates the rendezvous point information table, route confirmation information may be fed back to the specific PE, so as to respond that the peer PE has received the route information carried in the protocol update information. When receiving the route confirmation information fed back by the opposite-end PE, the specific PE may not send the route information to the opposite-end PE any more. The route confirmation information may include: routing type, routing identifier, homemade system number and acknowledgement (Confirm) of multicast source, etc. For example, when receiving the route confirmation information sent by the PE1, the PE3 may determine, through the parameter information carried in the route confirmation information, that the PE1 has generated the rendezvous point information table corresponding to the multicast group VPN1 according to the protocol update information, so that the protocol update information carrying the RP synchronization information may not be sent to the PE1 any more. In addition, the PE1 may also actively create a Selective P-Tunnel using the data recorded in the rendezvous point information table, so as to transmit the multicast data, such as the service data, in the multicast group VPN1 using the created Selective P-Tunnel.

On the basis of the above embodiments, the present embodiment discusses the present invention in detail with reference to specific application scenarios.

referring to fig. 6, a flowchart illustrating steps of an information delivery method in a specific example of the present invention is shown, which may specifically include the following steps:

step 602, MVPN BGP neighbor relations are established between PE1, PE2, and PE 3.

a corresponding multicast group VPN1 may thus be formed and PE3 may be determined to be a particular PE of the multicast group VPN 1.

At step 604, PE3 determines the address of the RP.

Specifically, PE3 may use the suspended CE device as an RP device. If the loopback interface address of the RP device is configured to be 4.4.4.4, PE3 may obtain that the loopback interface address configured by the rendezvous point is 4.4.4.4, and may use the loopback interface address as the address of the RP.

in step 606, PE3 may generate protocol update information according to the address of the RP

After obtaining the address of the RP, the PE3 may add the address of the RP to the NLRI carried by the BGP, and generate BGP update information.

At step 608, PE3 may send the generated protocol update information to PE1 and PE2 based on the neighbor relations.

After MVPN BGP neighbors of PE3, PE1, and PE2 are successfully established, PE3 may prompt PE1 and PE2 to send BGP Update information to other PEs, so as to trigger each PE in the multicast group VPN1 to generate a rendezvous point information table according to the protocol Update information. As shown in fig. 7A, PE3 may send the NLRI carried by BGP Update information to PE1 and PE2 in a BGP advertisement manner.

In step 610, PE1 and PE2 generate a rendezvous point information table corresponding to the multicast group VPN1 according to the received BGP Update information.

The aggregation point information tables generated by PE1 and PE2 may be as shown in table 1 above.

In the embodiment of the present invention, when receiving BGP Update information sent by PE3, PE1 and PE2 may extract NLRI from the BGP Update information, determine, according to the value of the route type carried by the NLRI being 8, that the NLRI is a synchronous route of RP, and introduce, locally, a BGP route of class 8. Specifically, if the BGP route of class 8 meets the locally configured introduction condition, the BGP route of class 8 is introduced, that is, the BGP route is analyzed to analyze the RP information and the BGP remote neighbor information, so as to generate the rendezvous point information table shown in table 1.

For example, PE1 and PE2 may determine whether the class 8 BGP route carried by the NLRI matches the locally configured RD by detecting whether the RD detection carried by the NLRI matches the locally configured RD, so that when the RD carried by the NLRI matches the locally configured RD, it may be determined that the class 8 BGP route carried by the NLRI matches the locally configured RD, and the BGP route is analyzed to analyze the RP information and BGP far-end neighbor information, thereby locally maintaining an address entry of an RP, that is, generating the rendezvous point information table shown in table 1. After the PE1 and PE2 devices generate the rendezvous point information table, the PE3 may also respond to a route confirmation message to acknowledge that the PE1 and PE2 devices have introduced the synchronous route carried by the protocol update message. After PE3 receives the route determination information, it may no longer send the protocol update information carrying the synchronous route to PE1 and PE 2.

Optionally, when receiving the routing determination information sent by PE1 but not receiving the routing determination information sent by PE2, PE3 may send protocol update information to PE2 at a preset time interval, so as to avoid a situation that PE2 cannot receive the protocol update information due to loss of the protocol update information. It can be seen that the specific PE of the embodiment of the present invention can determine whether each peer PE receives the protocol update information through the route determination information, thereby ensuring that each peer PE in the multicast group can receive the protocol update information, and generating a corresponding rendezvous point information table according to the protocol update information.

After the RP information table is generated, PE1 and PE2 may actively establish a P-Tunnel, step 612.

The P-Tunnel established by PE1 is Tunnel1 in fig. 7A, and Tunnel1 has a source address of 1.1.1.1 and a destination address of 3.3.3.3; the P-Tunnel established by PE2 is the sum Tunnel2 in fig. 7A, and Tunnel2 has a source address of 2.2.2.2 and a destination address of 3.3.3.3. After multicast source multicast data hung under PE1 enters PE1, PE1 may query the RP information table and forward the multicast data to PE3 through tunnel 1; when a multicast receiver hung under PE2 has a multicast join request to enter, multicast data can also be sent to PE3 through tunnel 2.

The embodiment of the invention can adopt the newly added 8-type route to synchronize the RP information between MVPN neighbors by adding the 8-type route of the MVPN, so that the message transmission of the BSR does not depend on the Inclusive P-Tunnel, and meanwhile, the transmission of the BSR information in the MVPN and the forwarding of any multicast source data can be protected by utilizing the BGP protocol, thereby ensuring the normal use of the multicast service.

In the embodiment of the present invention, a PE in an MVPN may generate an RP information entry by using a newly added type 8 route, that is, a P-Tunnel may be created by using an RP information entry synchronized at a remote end, for example, a Selective P-Tunnel is created, multicast data may be forwarded by using the P-Tunnel, and an Inclusive P-Tunnel does not need to be created, so that a problem of service data transmission interruption caused by switching the PE from the Selective P-Tunnel to the Inclusive P-Tunnel can be avoided.

of course, if a new PE joins the multicast domain of the MVPN, the PE3 may establish a neighbor with the new PE and may also directly synchronize RP information with the new PE. For example, when PE4 joins multicast group VPN1 in the above example, as shown in fig. 7B, PE3 may send protocol update information to PE4, so that PE4 may generate an RP information table corresponding to the multicast group VPN1 using the protocol update information to create a corresponding P-Tunnel using the RP information table, such as Tunnel3 in fig. 7B. The source address of Tunnel3 is 5.5.5.5 and the destination address is 3.3.3.3.

optionally, if a PE exits from the multicast domain of the MVPN, the PE exiting may delete the address table entry corresponding to the RP corresponding to the particular PE in the local rendezvous point information while deleting the neighbor relationship between the PE exiting and the particular PE of the MVPN, so as to delete the Selective P-Tunnel between the PE exiting and the particular PE.

In a preferred embodiment of the present invention, the information delivery method may further include: and when the rendezvous point changes, updating the rendezvous point information table of each PE in the multicast group by adopting the changed address of the rendezvous point.

In the embodiment of the present invention, if the RP node changes, the MVPN full topology performs RP information update, that is, the changed address of the rendezvous point is used to update the rendezvous point information table of each PE in the multicast group, so as to ensure that one RP information can reach in the MVPN domain, thereby realizing optimal path convergence from each PE in the multicast group to the rendezvous point corresponding to the multicast group.

In summary, the embodiments of the present invention may update the RP information corresponding to the MVPN synchronously by a synchronization mechanism of newly adding the RP information, that is, when adding and/or deleting the PE in the MVPN, thereby implementing forwarding of any multicast source data and further ensuring normal use of multicast services.

it should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.

the embodiment discloses an information delivery apparatus, which can be specifically applied to a specific PE of a multicast group.

Referring to fig. 8A, a block diagram of an embodiment of an information delivery apparatus according to the present invention is shown, and specifically, the block diagram may include the following modules:

the rendezvous point determining module 802 is configured to determine a rendezvous point corresponding to the multicast group.

An information generating module 804, configured to generate protocol update information according to the address of the rendezvous point.

An information sending module 806, configured to send the protocol update information to each PE of the backbone network edge router, so that each PE in the multicast group generates a rendezvous point information table according to the protocol update information. And the convergent point information table is used for creating a backbone network core equipment tunnel in the multicast group.

Referring to FIG. 8B, a block diagram illustrating an alternate embodiment of an information delivery apparatus of the present invention is shown

Optionally, the information delivery apparatus may further include a neighbor relation establishing module 808.

in this embodiment of the present invention, the neighbor relation establishing module 808 may be configured to establish a neighbor relation between PEs. The information sending module 806 may specifically include: a determination sub-module 8062 and a transmission sub-module 8064. The determining submodule 8062 is configured to determine, according to the neighbor relation, each PE belonging to the multicast group; a sending submodule 8064, configured to generate the protocol update information for each determined PE.

in a preferred embodiment of the present invention, the protocol update information may carry a network segment of the multicast group corresponding to the rendezvous point. The determining submodule 8062 may be specifically configured to determine, based on the neighbor relation, each PE belonging to the network segment as each PE in the multicast group.

In a preferred embodiment of the present invention, the information transfer apparatus may further include: an information table update module 810. The information table updating module 810 may be configured to update the rendezvous point information table of each PE in the multicast group by using the changed address of the rendezvous point when the rendezvous point changes.

The present embodiment discloses another information delivery apparatus, which may be specifically applied to an opposite-end PE having a neighbor relationship with a specific PE of a multicast group.

Referring to fig. 9A, a block diagram of another information delivery apparatus according to another embodiment of the present invention is shown, and may specifically include the following modules:

The information analyzing module 902 is configured to, when receiving the protocol update information, analyze the protocol update information to obtain an address of the rendezvous point.

An information table generating module 904, configured to generate a rendezvous point information table by using the address of the rendezvous point, where the rendezvous point information table is used to create a backbone core device tunnel in a multicast group corresponding to the rendezvous point.

Referring to fig. 9B, a block diagram of an alternate embodiment of an information delivery apparatus of the present invention is shown.

In a preferred embodiment of the present invention, the information transfer apparatus may further include the following modules:

A confirmation information feedback module 906, configured to feed back, after the rendezvous point information table is generated, route confirmation information to a specific PE of the multicast group, where the route confirmation information is used to respond to the protocol update information, and the specific PE is a PE connected to the rendezvous point.

A tunnel creating module 908, configured to create a backbone core device tunnel connected to the specific PE based on the rendezvous point information table, where the backbone core device tunnel is used to transmit service data in the multicast group.

For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.

The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

as will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.

Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.

The above detailed description is provided for an information delivery method and an information delivery apparatus, and the principle and the implementation of the present invention are explained in detail by applying specific examples, and the description of the above embodiments is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. An information delivery method, comprising:

Determining a rendezvous point corresponding to the multicast group;

generating protocol updating information according to the address of the convergent point, wherein the protocol updating information is generated by adding the address of the convergent point into a border gateway protocol message;

and sending the protocol updating information to each PE (provider edge) of the backbone network so that each PE in the multicast group generates a rendezvous point information table according to the address of the rendezvous point in the protocol updating information, wherein the rendezvous point information table is used for creating a backbone network core equipment tunnel in the multicast group.

2. The method of claim 1, further comprising:

Establishing a neighbor relation between PEs;

Wherein, sending the protocol update information to each backbone network edge router PE includes:

determining each PE belonging to the multicast group according to the neighbor relation;

And sending the protocol updating information to each determined PE.

3. The method of claim 2, wherein the protocol update information carries a network segment of the multicast group corresponding to the rendezvous point;

wherein, according to the neighbor relation, determining each PE belonging to the multicast group includes: and determining each PE belonging to the network segment as each PE in the multicast group based on the neighbor relation.

4. the method of any of claims 1 to 3, further comprising:

And when the convergent point changes, updating the convergent point information table of each PE in the multicast group by adopting the changed convergent point address.

5. An information delivery method, comprising:

When protocol updating information is received, analyzing the protocol updating information to obtain an address of a convergent point, wherein the specific generation mode of the protocol updating information is as follows: adding the address of the rendezvous point into the border gateway protocol message to generate protocol updating information;

6. the method of claim 5, further comprising:

After the rendezvous point information table is generated, feeding back route confirmation information to a specific PE of the multicast group, wherein the route confirmation information is used for responding the protocol updating information, and the specific PE is a PE connected with the rendezvous point;

And creating a backbone network core device tunnel connected with the specific PE based on the rendezvous point information table, wherein the backbone network core device tunnel is used for transmitting the service data in the multicast group.

7. An information delivery apparatus, comprising:

The information generating module is used for generating protocol updating information according to the address of the convergent point, and is specifically used for adding the address of the convergent point into a border gateway protocol message to generate protocol updating information;

And the information sending module is used for sending the protocol updating information to each PE (provider edge) of the backbone network so that each PE in the multicast group generates a rendezvous point information table according to the address of the rendezvous point in the protocol updating information, wherein the rendezvous point information table is used for creating a backbone network core equipment tunnel in the multicast group.

8. the apparatus of claim 7, further comprising:

the neighbor relation establishing module is used for establishing the neighbor relation between the PEs;

wherein, the information sending module comprises:

A determining submodule, configured to determine, according to the neighbor relation, each PE belonging to the multicast group;

And the sending submodule is used for sending the protocol updating information to each determined PE.

9. The apparatus of claim 8, wherein the protocol update information carries a network segment of a multicast group corresponding to the rendezvous point;

The determining submodule is specifically configured to determine, based on the neighbor relation, each PE belonging to the network segment as each PE in the multicast group.

10. The apparatus of any of claims 7 to 9, further comprising:

And the information table updating module is used for updating the convergent point information table of each PE in the multicast group by adopting the changed address of the convergent point when the convergent point is changed.

11. an information delivery apparatus, comprising:

the information analysis module is used for analyzing the protocol updating information to obtain the address of the convergent point when the protocol updating information is received, wherein the specific generation mode of the protocol updating information is as follows: adding the address of the rendezvous point into the border gateway protocol message to generate protocol updating information;

12. The apparatus of claim 11, further comprising:

a confirmation information feedback module, configured to feed back, after the rendezvous point information table is generated, route confirmation information to a specific PE of the multicast group, where the route confirmation information is used to respond to the protocol update information, and the specific PE is a PE connected to the rendezvous point;

a tunnel creating module, configured to create a backbone network core device tunnel connected to the specific PE based on the rendezvous point information table, where the backbone network core device tunnel is used to transmit service data in the multicast group.