Multicast distribution tree switching

• US 10,454,696 B2
• Filed: 08/27/2015
• Issued: 10/22/2019
• Est. Priority Date: 08/28/2014
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Chai, Jialin
• Primary Examiner(s): Thier, Michael
• Assistant Examiner(s): Sandhu, Nevena Zecevic
• Application Number:
  US15/507,439
• Publication Number:
  US 20170288890A1
• Time in Patent Office: 1,517 Days
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 12/1854 with non-centralised forwarding system, e.g. chaincast
• CPC Class Codes: H04L 12/46 Interconnection of networks
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 12/56 Packet switching systems
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]

Abstract

A mapping relationship between a private network multicast group address, which may be preset to support switching from a default Multicast Distribution Tree (MDT) to a data MDT, and a data group address may be stored in a first Provider Edge (“PE”) device. If a private network multi cast data flow corresponding to the mapping relationship satisfies a condition of switching from the default MDT to the data MDT, the first PE device may send a data MDT switch initiation packet including the private network multicast group address and the data group address to a second PE device on the default MDI, so that the second PE device joins the data MDT, a root of which is the first PE device, using the data group address. The first PE device may switch the private network multicast data flow to the data MDT, so that the private network multicast data flow is transmitted on the data MDT.

Claims

1. A method, comprising:

receiving, by a first Provider Edge (PE) device from a second PE device, a Multicast Distribution Tree (MDT) switch notice packet comprising a mapping relationship between a private network multicast group address, which is preset to support switching from a default MDT bidirectional [*, G] tree to a data MDT [*, G] tree, and a data group address, the data group address included in the MDT switch notice packet by the second PE device based on a search of a bidirectional Protocol Independent Multicast (PIM) forwarding table by the second PE device;

storing, by the first PE device, the mapping relationship;

in response to a private network multicast data flow corresponding to the mapping relationship satisfying a condition of switching from the default MDT bidirectional [*, G]-tree to the data MDT [*, G] tree, sending, by the first PE device, a data MDT switch initiation packet including the private network multicast group address and the data group address to a third PE device on the default MDT bidirectional [*, G] tree, to cause joining by the third PE device of the data MDT [*, G] tree, a root of which is the first PE device, using the data group address; and

switching, by the first PE device, the private network multicast data flow to the data MDT [*, G] tree, so that the private network multicast data flow is transmitted on the data MDT [*, G]-tree.

2. The method according to claim 1, wherein the second PE device is a Rendezvous Port (RP) PE device, which is closest to a bidirectional PIM RP of a private network,

wherein the mapping relationship between the private network multicast group address and the data group address is created by the second PE device, and

wherein the mapping relationship is sent by the second PE device to a plurality of PE devices on the default MDT bidirectional [*, G] tree using type-length-value fields of a MDT join packet, to cause the plurality of PE devices on the default MDT bidirectional [*, G] tree to store the mapping relationship, the MDT switch notice packet comprising the MDT join packet.

3. The method according to claim 2, wherein the data group address is least cited in a group of data group addresses corresponding to an instance to which the private network multicast group address belongs.

4. The method according to claim 1, further comprising:

receiving, by the first PE device, a first data MDT switch initiation packet from another PE device, the first data MDT switch initiation packet including a first private network multicast group address, which is preset to support switching from a first default MDT bidirectional [*, G] tree to a first data MDT [*, G] tree, and a first data group address corresponding to the first private network multicast group address;

checking, by the first PE device, whether the first PE device connects with a receiver that receives a private network multicast data flow corresponding to the first private network multicast group address;

if the first PE device connects with the receiver, joining in, by the first PE device, a first data group corresponding to the first data group address to create the first data MDT [*, G] tree;

if the first PE device does not connect with the receiver, storing, by the first PE device, the first private network multicast group address and the first data group address and joining in, by the first PE device, the first data group after the first PE device connects with the receiver.

5. The method according to claim 1, further comprising:

in response to a condition of switching from the data MDT [*, G] tree to the default MDT bidirectional [*, G] tree being satisfied, stopping, by the first PE device, using the data group address; and

encapsulating, by the first PE device, the private network multicast data flow using the private network multicast group address.

6. The method according to claim 1, further comprising:

for a virtual private network (VPN), searching, by the second PE device, the bidirectional PIM forwarding table to find an entry in the bidirectional PIM forwarding table for the VPN; and

in response to determining that the entry in the bidirectional PIM forwarding table comprises the private network multicast group address that supports switching from the default MDT bidirectional [*, G] tree to the data MDT [*, G] tree, select the data group address from a plurality of data group addresses to include in the MDT switch notice packet.

7. The method according to claim 6, wherein the MDT switch notice packet comprises an identifier specifying that the MDT switch notice packet is a bidirectional PIM-specific data MDT switch notice packet.

8. The method according to claim 6, further comprising:

sending, by the second PE device, the MDT switch notice packet to a plurality of PE devices.

9. A first Provider Edge (PE) device, comprising:

a non-transitory storage medium and a processor, wherein the processor is to execute machine readable instructions stored in the non-transitory storage medium to;

receive, from a second PE device, a Multicast Distribution Tree (MDT) switch notice packet comprising a mapping relationship between a private network multicast group address, which is preset to support switching from a default multicast distribution tree (MDT) bidirectional [*, G] tree to a data MDT [*, G] tree, and a data group address the data group address included in the MDT switch notice packet by the second PE device based on a search of a bidirectional Protocol Independent Multicast (PIM) forwarding table by the second PE device;

store the mapping relationship;

in response to a private network multicast data flow corresponding to the mapping relationship satisfying a condition of switching from the default MDT bidirectional [*, G] tree to the data MDT [*, G] tree, send a data MDT switch initiation packet including the private network multicast group address and the data group address to a third PE device on the default MDT bidirectional [*, G] tree, to cause joining by the third PE device of the data MDT [*, G] tree, a root of which is the first PE device, using the data group address; and

switch the private network multicast data flow to the data MDT [*, G] tree, so that the private network multicast data flow is transmitted on the data MDT [*, G] tree.

10. The first PE device according to claim 9, wherein the processor is further to execute the machine readable instructions in the non-transitory storage medium, to:

receive a first data MDT switch initiation packet from a another PE device, the first data MDT switch initiation packet including a first private network multicast group address, which is preset to support switching from a first default MDT bidirectional [*, G] tree to a first data MDT [*, G] tree, and a first data group address corresponding to the first private network multicast group address;

check whether the PE device connects with a receiver that receives a private network multicast data flow corresponding to the first private network multicast group address;

if the PE device connects with the receiver, join in a first data group corresponding to the first data group address using the first data group address to create the first data MDT [*, G] tree;

if the PE device does not connect with the receiver, store the first private network multicast group address and the first data group address and join in the first data group after the PE device connects with the receiver.

11. The first PE device according to claim 9, wherein the processor is further to execute the machine readable instructions in the non-transitory storage medium, to:

in response to a condition of switching from the data MDT [*, G] tree to the default MDT bidirectional [*, G] tree being satisfied, stop using the data group address;

encapsulate the private network multicast data flow using the private network multicast group address.

12. The first PE device according to claim 9, wherein the MDT switch notice packet comprises an identifier specifying that the MDT switch notice packet is a bidirectional PIM-specific data MDT switch notice packet.

13. A non-transitory machine-readable storage medium comprising instructions that upon execution cause a first Provider Edge (PE) device to:

create a mapping relationship between a private network multicast group address that supports switching from a default MDT bidirectional [*, G] tree to a data MDT [*, G] tree and a data group address;

send a Multicast Distribution Tree (MDT) switch notice packet comprising the mapping relationship from the first PE device on the default MDT bidirectional [*, G] tree to a plurality of PE devices on the default MDT bidirectional [*, G] tree;

include the data group address in the MDT switch notice packet based on a search of a bidirectional Protocol Independent Multicast (PIM) forwarding table by the first PE device; and

switch a private network multicast data flow from the default MDT bidirectional [*, G] tree to the data MDT [*, G] tree, so that the private network multicast data flow is transmitted on the data MDT [*, G] tree upon the private network multicast data flow satisfying a switching condition, the switching being performed by the first PE device by sending a data MDT switch initiation packet including the private network multicast group address and the data group address to a second PE device on the default MDT bidirectional [*, G] tree.

14. The non-transitory machine-readable storage medium according to claim 13, wherein the instructions upon execution cause the first PE device to:

join the second PE device on the default MDT bidirectional [*, G] tree to the data MDT [*, G] tree, a root of which is the first PE device, using the data group address upon satisfying the switching condition and prior to the switching.

15. The non-transitory machine-readable storage medium according to claim 14, wherein the data MDT [*, G] tree is a subset of the default MDT bidirectional [*, G] tree.

16. The non-transitory machine-readable storage medium according to claim 13, wherein the MDT switch notice packet comprises a MDT join packet that includes type-length-value fields comprising a bidirectional PIM-specific data MDT switch notice packet identifier.

17. The non-transitory machine-readable storage medium according to claim 13, wherein the instructions upon execution cause the first PE device to:

stop use of the data group address in response to a switching condition of switching from the data MDT [*, G] tree to the default MDT bidirectional [*, G] tree being satisfied; and

encapsulate the private network multicast data flow using the private network multicast group address.

18. The non-transitory machine-readable storage medium according to claim 13, wherein the switching condition is that a flow forwarding rate of the private network multicast data flow exceeds a threshold in a first time period.

19. The non-transitory machine-readable storage medium according to claim 13, wherein the instructions upon execution cause the first PE device to:

receive a first data MDT switch initiation packet from another PE device, the first data MDT switch initiation packet including a first private network multicast group address, which is preset to support switching from a first default MDT bidirectional [*, G] tree to a first data MDT [*, G] tree, and a first data group address corresponding to the first private network multicast group address;

check whether the first PE device connects with a receiver that receives a private network multicast data flow corresponding to the first private network multicast group address;

if the first PE device connects with the receiver, join in, by the first PE device, a first data group corresponding to the first data group address to create the first data MDT [*, G] tree;

if the first PE device does not connect with the receiver, store, by the first PE device, the first private network multicast group address and the first data group address and joining in, by the first PE device, the first data group after the first PE device connects with the receiver.

20. The non-transitory machine-readable storage medium of claim 13, wherein the instructions upon execution cause the first PE device to:

for a virtual private network (VPN), search the bidirectional PIM forwarding table to find an entry in the bidirectional PIM forwarding table for the VPN; and

in response to determining that the entry in the bidirectional PIM forwarding table comprises the private network multicast group address that supports switching from the default MDT bidirectional [*, G] tree to the data MDT [*, G] tree, select the data group address from a plurality of data group addresses to include in the MDT switch notice packet.