CN106230730B

CN106230730B - Multicast transmission method and device

Info

Publication number: CN106230730B
Application number: CN201610617480.5A
Authority: CN
Inventors: 黄李伟; 陈岩; 王伟
Original assignee: Hangzhou H3C Technologies Co Ltd
Current assignee: New H3C Information Technologies Co Ltd
Priority date: 2016-07-28
Filing date: 2016-07-28
Publication date: 2020-02-18
Anticipated expiration: 2036-07-28
Also published as: CN106230730A

Abstract

The embodiment of the application provides a multicast transmission method and device. The method comprises the following steps: determining MVPN corresponding to the multicast data; searching and obtaining a P2MP tunnel outgoing interface corresponding to the MVPN in the established forwarding table; forwarding the multicast data through the P2MP tunnel egress interface; wherein, one P2MP tunnel corresponds to multiple MVNPs. The embodiment of the application can improve the utilization rate of P2MP tunnel resources of the PE equipment and reduce network bandwidth resources occupied by a plurality of P2MP tunnels.

Description

Multicast transmission method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a multicast transmission method and apparatus.

Background

MVPN (Multicast virtual private network, Multicast VPN) is a technology for realizing Multicast transmission in a VPN network. A VPN network usually consists of a public network of the operator and individual sites of the subscriber, which are isolated from each other and can only be intercommunicated by means of a public network.

Referring to fig. 1, a schematic diagram of an existing MVPN network structure is shown. Wherein, CE (customer edge) device CE1 in site1 is connected to multicast source, and is in the same MVPN, such as MVPN a, and CE2 and CE3 are also in MVPN a. In the network structure shown in fig. 1, a public network adopts an MPLS (Multi-Protocol label switching) backbone network, and in a specific application, a P2MP (Point 2Multiple Point, Point to multipoint) Tunnel may be established between PEs (Provider Edge devices) to transmit private network data in an MVPN a, so that a CE2 in a site2 and a CE3 in a site3 may receive multicast data sent by a multicast source through the P2MP Tunnel.

Specifically, when PE1 receives multicast data from a multicast source, the multicast data is encapsulated with an MPLS label, and then forwarded to other PE devices connected to a receiver through a P2MP tunnel, such as PE2 and PE3, and PE2 and PE3 remove an outer label from the received multicast data, and then forwarded through three layers of multicast to be sent to connected CE2 and CE3, respectively.

Disclosure of Invention

The embodiment of the application provides a multicast transmission method and a multicast transmission device, so that multiple MVPNs share the same P2MP tunnel, the utilization rate of P2MP tunnel resources of PE equipment can be improved, and network bandwidth resources occupied by multiple P2MP tunnels are reduced.

In order to solve the above problem, an embodiment of the present application discloses a multicast transmission method, including:

determining MVPN corresponding to the multicast data;

searching and obtaining a P2MP tunnel outgoing interface corresponding to the MVPN in the established forwarding table;

forwarding the multicast data through the P2MP tunnel egress interface; wherein, one P2MP tunnel corresponds to multiple MVNPs.

According to another aspect of the present application, an embodiment of the present application discloses a multicast transmission apparatus, including:

the first determining module is used for determining the MVPN corresponding to the multicast data;

the query module is used for searching and obtaining a P2MP tunnel outgoing interface corresponding to the MVPN in the established forwarding table;

a data forwarding module, configured to forward the multicast data through the P2MP tunnel egress interface; wherein, one P2MP tunnel corresponds to multiple MVNPs.

The embodiment of the application has the following advantages:

the embodiment of the application can establish the corresponding relation between each MVPN and the P2MP tunnel outlet interface, and in the process of transmitting the multicast data, firstly, the MVPN corresponding to the multicast data is determined; then searching and obtaining a P2MP tunnel outgoing interface corresponding to the MVPN in the established forwarding table; finally, the multicast data is forwarded through the P2MP tunnel out interface. Because one P2MP tunnel may correspond to multiple MVNPs, and each MVNP may correspond to a different P2MP tunnel outgoing interface, a public network P2MP tunnel may be shared by multiple MVPNs, so as to improve the utilization rate of P2MP tunnel resources of the PE device, and reduce network bandwidth resources occupied by multiple P2MP tunnels.

Drawings

Fig. 1 shows a schematic diagram of a conventional MVPN network structure;

fig. 2 is a flow chart illustrating steps of a multicast transmission method according to an embodiment of the present application;

fig. 3 shows a schematic structural diagram of an MVPN network according to the present application;

fig. 4 shows a block diagram of a multicast transmission apparatus according to an embodiment of the present application.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.

In the MVPN technology, MVPN and P2MP tunnels are in a one-to-one correspondence relationship, such as the P2MP tunnel established in fig. 1, which can only be used for transmitting private network data in MVPN a, and when private network data in multiple MVPNs, such as MVPN b and MVPN c, needs to be transmitted, a P2MP tunnel corresponding to MVPN b, a P2MP tunnel corresponding to MVPN c, and the like need to be established respectively. Therefore, with the increasing number of MVPNs, the requirement on the P2MP tunnel resources of the PE device is high, even the P2MP tunnel resources are not enough, and multiple P2MP tunnels also cause waste of network bandwidth resources.

Referring to fig. 2, a flowchart of steps of a multicast transmission method according to an embodiment of the present application is shown, where the method is applicable to a PE device, and the PE device may specifically be a PE device connected to a multicast source, that is, the PE device may be a head node of a P2MP tunnel; or, the PE device may be a PE device connected to the receiver, that is, the PE device may be a tail node of a P2MP tunnel; alternatively, the PE device may also be an intermediate forwarding device. It is to be understood that the present application is not limited to the specific form of the PE device, and the method may specifically include the following steps:

step 201, determining an MVPN corresponding to multicast data;

step 202, finding out a P2MP tunnel outgoing interface corresponding to the MVPN from an established forwarding table;

step 203, forwarding the multicast data through the tunnel egress interface of P2 MP; wherein, one P2MP tunnel corresponds to multiple MVNPs.

The embodiment of the application is applicable to an application scenario of the MVPN, and compared with the existing MVPN, one MVPN can only correspond to one unique public network P2MP tunnel, and the embodiment of the application can realize that a plurality of MVPNs share one public network P2MP tunnel, thereby improving the utilization rate of P2MP tunnel resources of PE equipment and reducing network bandwidth resources occupied by a plurality of P2MP tunnels.

In order to realize that a plurality of MVPNs share one public network P2MP tunnel, the embodiment of the application can establish the corresponding relationship between each MVPN and the P2MP tunnel output interface, and in the process of transmitting multicast data, firstly, the MVPN corresponding to the multicast data is determined; then searching and obtaining a P2MP tunnel outgoing interface corresponding to the MVPN in the established forwarding table; finally, the multicast data is forwarded through the P2MP tunnel out interface. Since one P2MP tunnel may correspond to multiple MVNPs, and each MVNP may correspond to a different P2MP tunnel egress interface, it may be implemented that multiple MVPNs share one public network P2MP tunnel.

In an alternative embodiment of the present application, a custom tag may be used to identify different MVNPs, and the method may further include the following steps:

applying for each MVPN corresponding to the PE equipment for an MVPN label corresponding to the MVPN;

and sending the MVPN label corresponding to the MVPN to the neighbor equipment of the PE equipment.

In a specific application, when the PE device is the head node, a corresponding MVPN tag may be applied to each MVPN on the PE device to identify each MVPN. For example, the PE device PE1 is a head node, and the PE1 is configured with MVPN a and MVPN b, then the PE1 may apply for corresponding MVPN tags for the MVPN a and the MVPN b, respectively, for example, the MVPN tag corresponding to MVPN a is 300; the MVPN tag corresponding to MVPN b is 301. Therefore, the corresponding MVPN can be uniquely identified through the MVPN label.

After PE1 applies for MVPN a and MVPN b respectively corresponding MVPN tags, it may send MVPN tags corresponding to MVPN a and MVPN b to neighbor devices of PE1, for example, PE1 may send neighbor update messages carrying MVPN tags to BGP (Border Gateway Protocol) neighbor devices, so that each PE device in a forwarding path may obtain an MVPN tag corresponding to an MVPN, and further, a mapping relationship between the MVPN tag and a P2MP tunnel exit interface may be established in its own forwarding table.

In an application example of the present application, referring to fig. 3, a schematic diagram of an MVPN network structure of the present application is shown. The PE equipment PE1 is connected with a multicast source, the PE equipment PE3, PE4 and PE5 are respectively connected with multicast receivers, and the PE1 is provided with MVPN a and MVPN b; the PE3 is provided with an MVPN a and an MVPN b; the PE4 is provided with MVPN b; PE5 has MVPN a allocated thereon. Referring to table 1, a specific illustration of a forwarding table of the present application is shown, and the forwarding table is pre-established in a PE1 device. Assuming that a P2MP tunnel has been established on PE1 as tunnel1, the egress interface of tunnel1 on PE1 includes egress interface 1 and egress interface 2.

TABLE 1

MVPN name	MVPN label	P2MP tunnel exit interface
			a	300	1
b	301	1
			a	300	2
b	301	2

In this embodiment of the present application, after the PE1 device receives multicast data from a multicast source, it may forward multiple copies of multicast data from the same established P2MP tunnel, in order to distinguish multicast data corresponding to different MVPNs in the same tunnel, the PE1 device needs to add an MVPN tag when forwarding the multicast data, in the forwarding process, the intermediate forwarding device queries its own forwarding table through the MVPN tag after receiving the multicast data forwarded by the PE1, so as to obtain a P2MP tunnel exit interface corresponding to the MVPN tag, and the multicast data may be forwarded through the exit interface.

In an optional embodiment of the present application, the step of forwarding the multicast data through the P2MP tunnel egress interface may specifically include:

packaging the multicast data according to the MVPN label;

and forwarding the encapsulated multicast data through the P2MP tunnel outlet interface.

Assuming that the PE1 device receives multicast data corresponding to MVPN b, and the egress interface corresponding to MVPN b obtained by searching in table 1 includes egress interface 1 and egress interface 2, one copy of the multicast data may be copied on the PE1 device, two copies of the multicast data are encapsulated according to the MVPN tag 301 corresponding to the multicast data, and the encapsulated multicast data are forwarded to PE3 through the P2MP tunnel egress interface 1 and forwarded to PE2 through the P2MP tunnel egress interface 2, respectively.

After PE2 receives the multicast data from PE1, first determining an MVPN corresponding to the multicast data, specifically, the step of determining the MVPN corresponding to the multicast data may include: and analyzing the multicast data to obtain an MVPN label of the MVPN corresponding to the multicast data. For example, PE2 parses the multicast data received from PE1, and obtains that the MVPN tag of the multicast data is 301.

Then, PE2 finds the P2MP tunnel egress interface corresponding to the MVPN tag in its forwarding table. Specifically, the step of finding the P2MP tunnel egress interface corresponding to the MVPN in the established forwarding table may include: inquiring in the established forwarding table to obtain a P2MP tunnel outgoing interface corresponding to the MVPN label; wherein, the forwarding table stores the mapping relationship between the MVPN label and the P2MP tunnel outgoing interface.

Referring to table 2, a specific illustration of another forwarding table of the present application is shown, and the forwarding table is pre-established in a PE2 device. Assuming that a P2MP tunnel has been established on PE2 as tunnel1, the egress interface of tunnel1 on PE2 includes egress interface 3 and egress interface 4.

TABLE 2

MVPN label	P2MP tunnel exit interface
		300	3
301	4

PE2 may obtain that the P2MP tunnel egress interface corresponding to MVPN tag 301 is egress interface 4 by querying the forwarding table shown in table 2, and may forward the multicast data through egress interface 4.

When the PE1 receives the multicast data of MVPN a, the MVPN tag 300 may be encapsulated in the multicast data, and the multicast data may be forwarded through the P2MP tunnel egress interface corresponding to the MVPN tag 300, where the forwarding process is similar to the forwarding process of the multicast data of MVPN b, and is not described here again. Therefore, the multicast data of the MVPN a and the MVPN b can share the same P2MP tunnel 1. Therefore, the utilization rate of P2MP tunnel resources of the PE equipment can be improved, and network bandwidth resources occupied by a plurality of P2MP tunnels can be reduced.

It is understood that the multicast data of the two MVPNs, MVPN a and MVPN b, share the same P2MP tunnel, which is only an application example of the present application, and in a specific application, the present application does not limit the number of MVPNs that can be shared by one P2MP tunnel.

In an optional embodiment of the present application, to further ensure the utilization rate of the network bandwidth resource, the method may further include the following steps:

determining the number of MVPNs corresponding to the PE equipment;

and when the number of the MVPNs corresponding to the PE equipment exceeds a preset sharing threshold value of the current P2MP tunnel, newly establishing a P2MP tunnel.

In an application example of the present application, assuming that a preset sharing threshold of a P2MP tunnel is preset to be k, that is, k MVPNs may share the same P2MP tunnel, if the number of MVPNs on PE1 exceeds a preset sharing threshold k of a current P2MP tunnel1, PE1 may newly create a P2MP tunnel2, and transmit multicast data corresponding to the exceeded MVPN through tunnel2 to share the transmission burden of tunnel 1.

In summary, in the embodiment of the present application, a corresponding relationship between each MVPN and the P2MP tunnel egress interface may be established, and in the process of transmitting multicast data, the MVPN corresponding to the multicast data is first determined; then searching and obtaining a P2MP tunnel outgoing interface corresponding to the MVPN in the established forwarding table; finally, the multicast data is forwarded through the P2MP tunnel out interface. Because one P2MP tunnel may correspond to multiple MVNPs, and each MVNP may correspond to a different P2MP tunnel outgoing interface, a public network P2MP tunnel may be shared by multiple MVPNs, so as to improve the utilization rate of P2MP tunnel resources of the PE device, and reduce network bandwidth resources occupied by multiple P2MP tunnels.

In another embodiment of the present application, the forwarding table may include a correspondence between an inner label, an outer label, and a P2MP tunnel egress interface. According to the embodiment of the application, the query depth when the multicast data is forwarded is increased by adding the inner layer label and the outer layer label to the multicast data, the inner layer label is applied for each MVPN at the head node of the P2MP tunnel, so that in the forwarding table, the same outer layer label can correspond to a plurality of different inner layer labels, and the multicast data corresponding to different MVPNs can be forwarded through the same P2MP tunnel. It should be noted that the inner layer label in the embodiment of the present application may be a custom label, such as an MVPN label, and the outer layer label may be an existing MPLS label, and when encapsulating multicast data, the inner layer label (MVPN label) may be encapsulated first, and then the outer layer label (MPLS label) may be encapsulated. Thus, when the PE device in the public network receives the multicast data, it needs to perform two-layer deep label query on the multicast data, and then determines the forwarding-out interface of the multicast data, so as to implement that multiple MVPNs share the same P2MP tunnel.

In an application example of the present application, the schematic view of the MVPN network structure shown in fig. 3 is still taken as an example. Referring to table 3, a specific illustration of another forwarding table of the present application is shown, where the forwarding table is pre-established in a PE1 device, and includes a corresponding relationship between an inner label, an outer label, and a P2MP tunnel egress interface.

TABLE 3

MVPN name	Inner label	Outer label	P2MP tunnel exit interface
				a	300	1150	1
b	301	1150	1
				a	300	1151	2
b	301	1151	2

Since the PE1 is configured with MVPN a and MVPN b, the PE1 applies for corresponding inner layer labels for MVPN a and MVPN b, respectively, for example, the inner layer label corresponding to MVPN a is 300; the inner label corresponding to MVPN b is 301. Assuming that a P2MP tunnel has been established on PE1 as tunnel1, the egress interface of tunnel1 on PE1 includes egress interface 1 and egress interface 2.

After the PE1 device receives multicast data from a multicast source, it may forward multiple copies of multicast data from the same established P2MP tunnel, in order to distinguish multicast data corresponding to different MVPNs in the same tunnel, the PE1 device needs to add two layers of labels, which are an inner layer label and an outer layer label, when forwarding the multicast data, in the forwarding process, the intermediate forwarding device may obtain the inner layer label by stripping the outer layer label after receiving the multicast data forwarded by the PE1, and may obtain an egress interface corresponding to the outer layer label and the inner layer label of the multicast data by querying a forwarding table stored in itself, and may forward the multicast data through the egress interface.

Assuming that the PE1 device receives multicast data corresponding to MVPN b, and a forwarding table entry corresponding to MVPN b is found in table 3 and is shown in table 4, copying a copy of the multicast data on the PE1 device, adding an inner label 301 to an inner layer of one copy of the multicast data, adding an outer label 1150 to an outer layer of the multicast data, and forwarding the multicast data to the PE3 through the output interface 1; another piece of multicast data is added with an inner label 301 at the inner layer and an outer label 1151 at the outer layer, and is forwarded to PE2 through an egress interface 2.

TABLE 4

MVPN name	Inner label	Outer label	P2MP tunnel exit interface
				b	301	1150	1
b	301	1151	2

It can be seen that the PE1 device may add corresponding inner layer label and outer layer label to the multicast data corresponding to MVPN a and MVPN b, and forward the multicast data to the intermediate forwarding device or the end node through the same P2MP tunnel, and finally forward the multicast data to the corresponding receiver. Similarly, the intermediate forwarding device (e.g., PE2, PE3, and PE4) may also store a corresponding forwarding table, and after receiving the multicast data forwarded by the PE1 device, the intermediate forwarding device extracts the outer label and the inner label of the multicast data and queries the local forwarding table twice, so as to finally obtain a corresponding forwarding output interface. In order to enable each intermediate forwarding device in the multicast data forwarding path to obtain the inner label applied by the PE1 device, in this embodiment of the present application, the PE1 device may further send the inner label to a BGP neighbor device.

In a specific application, as shown in fig. 3, after configuring corresponding MVPNs for PE1, PE2, PE3, PE4, and PE5, PE1, PE2, PE3, PE4, and PE5 respectively establish BGP MVPN address family neighbors, and perform discovery operation of the BGP MVPN neighbors. PE1 may establish BGP multicast address family neighbors with PE3, PE4, PE5, and after establishing BGP neighbors, may establish P2MP tunnels, such as establishing P2MP tunnel as tunnel1, tunnel1 with destination addresses PE3, PE4, PE5, and P2MP tunnels having been distributed according to MPLS labels as shown in fig. 3, forming forwarding paths. At this point, PE1 may build a forwarding table based on the MVPN name, the inner label, the outer label, and the P2MP tunnel egress interface.

After PE1 establishes BGP multicast address family neighbors with PE3, PE4, and PE5, PE1 may send the inner layer label corresponding to the MVPN to the intermediate forwarding device through a neighbor update message. The neighbor update message may carry a Network Layer Reachability Information (NLRI) of a PMSI tunnel Attribute, the Network Layer Reachability Information may carry an inner Layer label in the Attribute, and PE1 may send the neighbor update message to all MBGP peer devices, including PE3, PE4, and PE5, so that PE3, PE4, and PE5 may establish their corresponding forwarding tables according to the received inner Layer label, and after receiving multicast data, may perform query matching of two layers of labels on the multicast data according to the established forwarding table, and if matching, forward the multicast data according to the forwarding table through the established P2MP tunnel.

When the intermediate forwarding device receives the multicast data, the multicast data is analyzed to obtain outer layer labels and inner layer labels, and the forwarding can be performed only when the labels of the two layers are matched with the forwarding table.

Taking the PE3 device in fig. 3 as an example, referring to table 5, a specific illustration of a forwarding table of a PE3 device of the present application is shown. After receiving the multicast data corresponding to MVPN b, PE3 analyzes the multicast data, extracts the multicast data to obtain an outer label 1150, then queries the forwarding table shown in table 5 to obtain a matching entry matching MVPN b and outer label 1150, as shown in the third row in table 3, further analyzes the multicast data to obtain an inner label 301 of the multicast data, which matches with the inner label in the matching entry, so that PE3 can send the multicast data to receiver 1 connected to it through a private network.

TABLE 5

Outer label	Inner label	MVPN name
			1150	300	a
1150	301	b

In this embodiment of the present application, when the intermediate forwarding device is a BGP multicast address family neighbor of the first node PE device, the inner label corresponding to the MVPN may be obtained by receiving a neighbor update packet from the first node PE device, and for an intermediate forwarding device that is not a BGP multicast address family neighbor of the first node PE device, such as the PE2 device in fig. 3, the inner label may not be obtained. To solve the above problem, in an alternative embodiment of the present application, the method may further include the steps of:

and transmitting the inner layer label corresponding to the MVPN to upstream intermediate forwarding equipment.

Specifically, the PE2 device may send the inner label corresponding to the MVPN to an upstream intermediate forwarding device according to the forwarding path of the tunnel1 created in fig. 3, so that all PE devices in the entire forwarding path of the tunnel1 may obtain the inner label corresponding to the MVPN, and thus may establish respective corresponding forwarding tables.

In this embodiment of the present application, after the intermediate forwarding device (e.g., PE2) receives multicast data, because tunnel1 has two outgoing interfaces corresponding to PE2, including outgoing interface 3 and outgoing interface 4, it is necessary to continue to perform two label queries and one label replacement operation according to a forwarding table on PE2, and then multicast data can be forwarded from the corresponding outgoing interface. Referring to table 6, a specific illustration of a forwarding table of a PE2 device of the present application is shown.

TABLE 6

As shown in table 6, the incoming outer label corresponds to an outer label encapsulated in the received multicast data, and the outgoing outer label is an outer label that needs to be encapsulated in the multicast data when the PE2 device forwards the multicast data, that is, the PE2 device strips the original outer label 1151 of the received multicast data, replaces the original outer label 1151 with the original outer label 1140 or 1141, and forwards the multicast data through the corresponding outgoing interface.

Specifically, after receiving the multicast data, PE2 first obtains an outer label of the multicast data by parsing the multicast data to be 1151, and matches the outer label with an ingress label 1151 in a forwarding table shown in table 6, and if the inner label of the multicast data is 301, queries the table 6 according to the inner label 301, and obtains that the corresponding egress interface is an egress interface 4 of a P2MP tunnel 1; then, two-layer label packaging is carried out on the multicast data, the inner layer label is kept 301 unchanged, and the outer layer label is replaced by 1141 from the original 1151; and finally, sending the encapsulated multicast data to the PE4 device corresponding to the egress interface 4 through the egress interface 4. Thus, the intermediate forwarding device PE2 completes the forwarding process of the multicast data.

Referring to table 7, a specific illustration of a forwarding table of a PE4 device of the present application is shown. PE4 may receive multicast data corresponding to MVPN b forwarded by PE2 from the outgoing interface 4 of P2MP tunnel1, PE4 analyzes the multicast data to obtain an outer label 1141, and by looking up a forwarding table shown in table 7, if there is a matching entry matching MVPN b and outer label 1141, further analyzes the multicast data, obtains an inner label 301 of the multicast data, and matches the inner label in the matching entry, so that the multicast data may be sent to receiver 3 through a private network.

TABLE 7

Outer label	Inner label	MVPN name
			1141	301	b

Similarly, the PE5 device may receive, from the outgoing interface 3 of the P2MP tunnel1, multicast data corresponding to the MVPN a forwarded by the PE2, the PE5 analyzes the multicast data to obtain an outer label 1140, and finally, by querying its own forwarding table, may send the multicast data to the receiver 2 through the private network. Therefore, the PE device in this embodiment of the present application may receive and forward multicast data corresponding to different MVPNs through the same P2MP tunnel, so that multiple MVPNs may share the same P2MP tunnel, and the utilization rate of the P2MP tunnel resource of the PE device is improved.

In addition, when the multicast traffic of the embodiment of the application is forwarded on the P2MP tunnel, two queries of the inner and outer layer labels need to be performed, so that an output interface corresponding to one P2MP tunnel can be correctly positioned through the query of the inner layer label on the intermediate forwarding device, thereby realizing that a plurality of MVPNs can share the same P2MP tunnel, and further reducing bandwidth resources occupied by establishing a plurality of P2MP tunnels.

Therefore, the sharing of the public network P2MP tunnel can be realized by the embodiment of the present application, the number of MVPNs that one P2MP tunnel can be shared is preset, an inner label corresponding to each MVPN is applied on the PE device of the first node connected to the multicast source, and the inner label corresponding to the MVPN is notified to the PE devices of all tail nodes corresponding to the P2MP tunnel through the BGP neighbor update message, such as the PE3, the PE4, and the PE5 devices in fig. 3, and the tail node can send the inner label corresponding to the MVPN to the upstream intermediate forwarding device, so that all PE devices in the whole forwarding path of the P2MP tunnel can obtain the inner label corresponding to the MVPN, and thus respective corresponding forwarding tables can be established. In the process of forwarding multicast data through a P2MP tunnel, in addition to matching a public network outer label, such as 1150 or 1151, in a forwarding table, a private network inner label, such as 300 or 301, needs to be further matched, so that multiple MVPNs can share the same P2MP tunnel, thereby realizing resource sharing and saving network bandwidth resources.

To sum up, the embodiment of the present application increases the identification depth of multicast data by encapsulating an inner layer tag and an outer layer tag for the multicast data, where each inner layer tag corresponds to one MVPN, so that the same outer layer tag may correspond to a plurality of different inner layer tags, and when forwarding the encapsulated multicast data through an outgoing interface of an established P2MP tunnel, one P2MP tunnel may correspond to a plurality of MVNPs. Thus, when receiving multicast data, the PE device in the public network needs to perform two-layer deep tag identification on the multicast data, and then determines the forwarding path of the multicast data, thereby realizing that multiple MVPNs share the same P2MP tunnel, further improving the utilization rate of P2MP tunnel resources of the PE device, and reducing network bandwidth resources occupied by multiple P2MP tunnels.

Referring to fig. 4, a block diagram of a multicast transmission apparatus according to an embodiment of the present application is shown, where the apparatus is applicable to a PE device, and in the embodiment of the present application, the apparatus may specifically include:

a first determining module 401, configured to determine an MVPN corresponding to multicast data;

a query module 402, configured to search for a P2MP tunnel egress interface corresponding to the MVPN in an established forwarding table;

a data forwarding module 403, configured to forward the multicast data through the P2MP tunnel egress interface; wherein, one P2MP tunnel corresponds to multiple MVNPs.

In an optional embodiment of the present application, the first determining module 401 is further configured to analyze the multicast data to obtain an MVPN tag of an MVPN corresponding to the multicast data;

the query module 402 is further configured to query the established forwarding table to obtain a P2MP tunnel egress interface corresponding to the MVPN tag; wherein, the forwarding table stores the mapping relationship between the MVPN label and the P2MP tunnel outgoing interface.

In another optional embodiment of the present application, the apparatus may further include:

a label application module, configured to apply for an MVPN label corresponding to each MVPN corresponding to the PE device;

and the label sending module is used for sending the MVPN label corresponding to the MVPN to the neighbor equipment of the PE equipment.

In another optional embodiment of the present application, the data forwarding module 403 may specifically include:

the encapsulation submodule is used for encapsulating the multicast data according to the MVPN label;

and the forwarding submodule is used for forwarding the encapsulated multicast data through the P2MP tunnel exit interface.

In yet another optional embodiment of the present application, the apparatus may further include:

a second determining module, configured to determine the number of MVPNs corresponding to the PE device;

and a new establishing module, configured to establish a P2MP tunnel when the number of MVPNs corresponding to the PE device exceeds a preset sharing threshold of the current P2MP tunnel.

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 of skill in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present application 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 application 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 application 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 application. 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 application 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 the preferred embodiment and all such alterations and modifications as fall within the true scope of the embodiments of the application.

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 foregoing detailed description is directed to a multicast transmission method and apparatus provided in the present application, and a specific example is applied in the present application to explain the principle and the implementation of the present application, and the description of the foregoing embodiment is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, 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 application.

Claims

1. A multicast transmission method is applied to PE equipment, and the method comprises the following steps:

determining MVPN corresponding to the multicast data;

forwarding the multicast data through the P2MP tunnel egress interface; wherein, one P2MP tunnel corresponds to a plurality of MVNPs;

when there are a plurality of P2MP tunnel egress interfaces corresponding to the MVPN, the step of forwarding the multicast data through the P2MP tunnel egress interface includes:

copying the multicast data according to the number of the P2MP tunnel outgoing interfaces corresponding to the MVPN;

and respectively forwarding the multicast data through the P2MP tunnel outlet interface.

2. The method of claim 1, wherein the step of determining the MVPN corresponding to the multicast data comprises:

analyzing the multicast data to obtain an MVPN label of the MVPN corresponding to the multicast data;

the step of finding the P2MP tunnel outgoing interface corresponding to the MVPN in the established forwarding table includes:

inquiring in the established forwarding table to obtain a P2MP tunnel outgoing interface corresponding to the MVPN label; wherein, the forwarding table stores the mapping relationship between the MVPN label and the P2MP tunnel outgoing interface.

3. The method of claim 1, further comprising:

4. The method of claim 3, wherein the step of forwarding the multicast data through the P2MP tunnel egress interface comprises:

packaging the multicast data according to the MVPN label;

5. The method of claim 1, further comprising:

determining the number of MVPNs corresponding to the PE equipment;

6. A multicast transmission apparatus, applied to a PE device, the apparatus comprising:

a data forwarding module, configured to forward the multicast data through the P2MP tunnel egress interface; wherein, one P2MP tunnel corresponds to a plurality of MVNPs;

when the number of the P2MP tunnel egress interfaces corresponding to the MVPN is multiple, the data forwarding module is further configured to:

7. The apparatus of claim 6, wherein the first determining module is further configured to parse the multicast data to obtain an MVPN tag of an MVPN corresponding to the multicast data;

the query module is further configured to query the established forwarding table to obtain a P2MP tunnel egress interface corresponding to the MVPN tag; wherein, the forwarding table stores the mapping relationship between the MVPN label and the P2MP tunnel outgoing interface.

8. The apparatus of claim 6, further comprising:

9. The apparatus of claim 8, wherein the data forwarding module comprises:

10. The apparatus of claim 6, further comprising: