WO2019174552A1 - Multicast route processing method, network device, and route reflector - Google Patents
Multicast route processing method, network device, and route reflector Download PDFInfo
- Publication number
- WO2019174552A1 WO2019174552A1 PCT/CN2019/077703 CN2019077703W WO2019174552A1 WO 2019174552 A1 WO2019174552 A1 WO 2019174552A1 CN 2019077703 W CN2019077703 W CN 2019077703W WO 2019174552 A1 WO2019174552 A1 WO 2019174552A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- multicast
- root
- routing
- leaf
- information
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1886—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/16—Multipoint routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/54—Organization of routing tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
Definitions
- the embodiments of the present disclosure relate to the field of communications, and in particular, to a multicast routing processing method, a network device, and a route reflector.
- Multicast virtual private network is a transport network based on border gateway protocol (BGP) and multiprotocol label switch (MPLS). MVPN is established on the public network. The technology of the private network realizes the transmission of multicast data in MVPN.
- BGP border gateway protocol
- MPLS multiprotocol label switch
- the MVPN when the MVPN includes a provider edge (PE) device of the M sender service provider networks, and N receiver PE devices, M is an integer greater than 1, and N is an integer greater than or equal to 2, N
- the receiving PEs send the multicast packets to the M transmitting PEs. After the M transmitting PEs receive the multicast routes sent by the N receiving PEs, the M transmitting PEs use the single.
- the rules of the virtual private network (VPN) are used to process the multicast routes sent by the N receivers.
- the route identifiers (RDs) of the PEs in the same MVPN are the same. Therefore, each of the M-side PE devices can only forward and cross a multicast route in the multicast route sent by the N-side PE devices.
- the different PE devices at the receiving end preferably have different transmitting PEs.
- the sending PE device processes the multicast route sent by the receiving PE.
- the PE device on the sending end only prefers one multicast route for pre-issue and cross-processing.
- the discarded multicast route must exist.
- the PE device cannot receive multicast data, so the user edge (CE) device connected to the PE device that does not receive the multicast data cannot receive multicast data.
- CE user edge
- the embodiment of the present application provides a multicast routing processing method, a network device, and a route reflector (RR) for increasing device routing in network layer reachability information (NLRI) in a multicast route.
- the identifier is such that the multicast route with the device routing identifier added is preferred and forwarded.
- the first aspect of the present application provides a multicast routing processing method, where the method is applied to an MVPN, where the MVPN includes M root devices and N leaf devices, where the M is an integer greater than 1, and the N is An integer of greater than or equal to 2, the N-th leaf device preferably different root devices of the M root devices when sending a multicast join message, and the first root device includes: the first The root device receives the first multicast join message sent by the target leaf device, where the first multicast join message includes multicast routing information, where the multicast routing information includes a device routing identifier, and the target leaf device is Determining one or more of the N leaf devices, the first root device being any one of the M root devices; the first root device determining, according to the device routing identifier, that the multicast routing information is satisfied Preferably, the first root device determines whether the second root device information included in the multicast routing information is the same as the first root device information, and the second root device information is a preferred receiving group of the target leaf device.
- the first root device adds the multicast routing information of the target leaf device to the virtual private network VPN routing table of the first root device;
- the first root device sends the multicast data to the target leaf device according to the VPN routing table. If not, the first root device discards the multicast routing information. It can be seen that the first device can ensure that the multicast routing information is optimized in the first root device according to the root device information in the multicast routing information, and then add the multicast routing information to the device.
- the first device can send multicast data to the target leaf device according to the VPN routing table, so that each leaf device receives the multicast data.
- determining, by the first root device, that the multicast routing information meets a preferred condition according to the device routing identifier includes: When the device routing identifier is the routing ID corresponding to the target leaf device, the first root device determines that the multicast routing information meets a preferred condition according to the routing ID corresponding to the target leaf device. It can be seen that the first device in the first embodiment can ensure that the multicast routing information sent by each target leaf device is obtained in the first device according to the routing ID corresponding to each leaf device. Preferably, in practical applications, the achievability of the solution is improved.
- the first root device determines the group according to the device routing identifier.
- the preferred condition for the broadcast routing information to be satisfied includes: when the device routing identifier is a routing ID of the second root device that the target leaf device preferably receives the multicast data, the first root device is according to the second root The routing ID of the device determines that the multicast routing information satisfies a preferred condition.
- the embodiment of the present application provides another routing ID (a routing ID of the second root device that the target leaf device preferably receives the multicast data) to ensure that each target leaf device sends the
- the multicast routing information satisfies the preferred conditions, and in practical applications, the diversity of the scheme is improved.
- the first root device determines the VPN instance of the multicast routing information And determining whether the MVPN ID is the same as the MVPN ID of the first root device, where the MVPN ID is an ID address corresponding to the MVPN of the first root device; if the same, the first root device adds the multicast routing information to the target
- the target routing table is one of the VPN routing tables of the first root device, and the target routing table is used to instruct the first root device to send the multicast to the target leaf device.
- the first device can determine whether the VPN instance identifier of the multicast routing information is the same as the MVPN ID of the first root device, to determine whether the multicast routing information is The routing information processed by the first root device provides a specific way to add multicast routing information to the VPN routing table.
- the sending, by the first root device, the multicast data to the target leaf device includes: the first root device sending a multicast data receiving message to the target leaf device, where the multicast data receiving message is used to indicate the The target leaf device receives the multicast data; the first root device receives a multicast data receiving response message sent by the target leaf device, where the multicast data receiving response message is used to indicate that the target leaf device needs to receive the The multicast data is sent by the first root device to the target leaf device corresponding to the multicast data receiving response message.
- the first device before the first device sends the multicast data to the target leaf device, the first device sends a multicast data receiving message to the target leaf device, and then receives the response to the sending multicast data.
- the target leaf device sends multicast data, which improves the efficiency of the target leaf device to receive multicast data.
- a second aspect of the present application provides a multicast routing processing method, where the method is applied to an MVPN, where the MVPN includes M root devices, N leaf devices, and a route reflector, where the M is an integer greater than 1.
- the N is an integer greater than or equal to 2, and the N leaf devices respectively select different root devices of the M root devices when sending the multicast join message
- the first root device includes: Receiving, by the first root device, a second multicast join message sent by the route reflector, where the second multicast join message includes multicast routing information, where the multicast routing information includes a device routing identifier, the target
- the leaf device is one or more of the N leaf devices, the first root device is any one of the M root devices; the first root device determines the group according to the device routing identifier
- the broadcast routing information meets a preferred condition; the first root device determines whether the second root device information included in the multicast routing information is the same as the first root device information, and the second root device information is the target leaf device.
- the first root device adds the multicast routing information of the target leaf device to the virtual private network VPN routing table of the first root device.
- the first root device sends the multicast data to the target leaf device according to the VPN routing table. If not, the first root device discards the multicast routing information.
- the first device can ensure that the multicast routing information is preferred in the first root device according to the root device information in the multicast routing information, and then add the multicast routing information to the device.
- the first device can send multicast data to the target leaf device according to the VPN routing table, so that each leaf device receives the multicast data.
- determining, by the first root device, that the multicast routing information meets a preferred condition according to the device routing identifier includes: When the device routing identifier is the routing ID corresponding to the target leaf device, the first root device determines that the multicast routing information meets a preferred condition according to the routing ID corresponding to the target leaf device.
- the first device in the embodiment of the present application can ensure that the multicast routing information sent by each target leaf device is obtained in the first device according to the routing ID corresponding to each leaf device. Preferably, in practical applications, the achievability of the solution is improved.
- the first root device determines the group according to the device routing identifier.
- the preferred condition for the broadcast routing information to be satisfied includes: when the device routing identifier is a routing ID of the second root device that the target leaf device preferably receives the multicast data, the first root device is according to the second root.
- the routing ID of the device determines that the multicast routing information satisfies a preferred condition.
- the embodiment of the present application provides another route ID to ensure that each target leaf device sends the multicast routing information to meet a preferred condition, and in practical applications, the scheme is improved. Sex.
- the second implementation manner of the second aspect of the second embodiment of the present application Adding the multicast routing information of the target leaf device to the virtual private network VPN routing table of the first root device, where the first root device determines the VPN instance of the multicast routing information And determining whether the MVPN ID is the same as the MVPN ID of the first root device, where the MVPN ID is an ID address corresponding to the MVPN of the first root device; if the same, the first root device adds the multicast routing information to the target In the routing table, the target routing table is one of the VPN routing tables of the first root device, and the target routing table is used to instruct the first root device to send the multicast to the target leaf device. data.
- the first device can determine whether the VPN instance identifier of the multicast routing information is the same as the MVPN ID of the first root device, to determine whether the multicast routing information is The routing information processed by the first root device provides a specific way to add multicast routing information to the VPN routing table.
- the sending, by the first root device, the multicast data to the target leaf device includes: the first root device sending a multicast data receiving message to the target leaf device, where the multicast data receiving message is used to indicate the The target leaf device receives the multicast data; the first root device receives a multicast data receiving response message sent by the target leaf device, where the multicast data receiving response message is used to indicate that the target leaf device needs to receive the The multicast data is sent by the first root device to the target leaf device corresponding to the multicast data receiving response message.
- the first device before the first device sends the multicast data to the target leaf device, the first device sends a multicast data receiving message to the target leaf device, and then receives the response to the sending multicast data.
- the target leaf device sends multicast data, which improves the efficiency of the target leaf device to receive multicast data.
- a third aspect of the present application provides a multicast routing processing method, where the method is applied to an MVPN, where the MVPN includes a route reflector, M root devices, and N leaf devices, where the M is an integer greater than 1.
- the N is an integer greater than or equal to 2, and the N leaf devices respectively select different root devices of the M root devices when sending the multicast join message, including: the route reflector receiving a first multicast join message sent by the target leaf device, where the first multicast join message includes multicast routing information, where the multicast routing information includes a device routing identifier, and the target leaf device is the N One or more of the leaf devices; the route reflector determines that the first multicast join message meets the pre-condition according to the device route identifier; the route reflector sends the second group to the first root device Broadcasting the message, the first root device is any one of the M root devices, and the second multicast join message is the same as the multicast routing information included in the first multicast join message.
- the second multicast join report Determining, by the first root device, that the multicast routing information meets a preferred condition according to the device routing identifier, and determining whether the second root device information included in the multicast routing information is the same as the first root device information
- the second root device information is information corresponding to the second root device that the target leaf device preferably receives the multicast data. If the information is the same, the first root device uses the multicast routing information of the target leaf device. Adding to the virtual private network VPN routing table of the first root device, when the multicast data is delivered, the first root device sends the multicast data to the target leaf device according to the VPN routing table. .
- the route reflector can ensure that each first multicast join message is forwarded in the route reflector according to the device route identifier in the multicast routing information, so that the multicast routing information is in the first root device.
- the preferred conditions can all be met.
- the route reflector determines, according to the device routing identifier, that the first multicast join message meets a pre-condition The routing reflector determines that the first multicast join message satisfies the pre-conditions according to the route ID corresponding to the target leaf device, when the device route identifier is the route ID corresponding to the target leaf device. .
- the route reflector of the embodiment of the present application can ensure that the multicast routing information sent by each target leaf device is forwarded in the route reflector according to the routing ID corresponding to each leaf device. In practical applications, the achievability of the solution is improved.
- the route reflector is determined according to the device routing identifier.
- the first multicast join message satisfies the pre-condition: when the device route identifier is the route ID of the second root device that the target leaf device preferably receives the multicast data, the route reflector Determining, according to the routing ID of the second root device, that the first multicast join message meets the pre-condition.
- the embodiment of the present application provides another routing ID (the routing ID of the second root device that the target leaf device preferably receives the multicast data) to ensure that each target leaf device sends the
- the multicast routing information satisfies the preferred conditions, and in practical applications, the diversity of the scheme is improved.
- the sending, by the route reflector, the second multicast join message to the first root device includes: when the device route identifier is a route ID corresponding to the target leaf device, the second multicast join message is The first multicast join message sent by the target leaf device, and the route reflector sends the first multicast join message sent by each target leaf device to the first root device. It can be seen from the third implementation manner of the third aspect that, in the embodiment of the present application, the routing ID corresponding to each target leaf device is different, so that each target leaf device sends a multicast join message in the route reflector. Can get the front.
- the second multicast join message is the first multicast join that meets the pre-condition
- the route reflector sends one of the first multicast join messages that meet the pre-conditions to the first root device.
- the fourth implementation manner of the third device is as follows: One of the multicast join messages saves the network resources dedicated to the multicast virtual.
- a fourth aspect of the present application provides a network device, where the network device is a first root device, where the first root device includes: a receiving unit, a processing unit, and a sending unit, where the receiving unit is configured to perform the foregoing first aspect,
- the second aspect and any possible implementations relate to the step of receiving a operation; the processing unit is configured to perform the steps of the processing operations described above in the first aspect, the second aspect, and any possible implementation; the transmitting unit The steps for performing the transmitting operation in performing the above, the second aspect, and any of the possible implementations.
- a fifth aspect of the embodiments of the present application provides a route reflector, where the route reflector includes: a receiving unit, a processing unit, and a sending unit, where the receiving unit is configured to perform the foregoing second aspect, and any possible implementation relates to receiving a step of operating; the processing unit is configured to perform the steps of the second aspect and any of the possible implementations related to the processing operation; the sending unit is configured to perform the foregoing second aspect and any possible implementation relates to sending The steps of the operation.
- a sixth aspect of the embodiments of the present application provides a network device, where the network device is a first device, and includes: a memory, a transceiver, and at least one processor, where the memory stores an instruction; the memory The transceiver and the at least one processor are interconnected by a line;
- the at least one processor invokes the instructions to perform the message processing or control operations performed on the first root device side in the first aspect and the second aspect.
- a seventh aspect of the embodiments of the present application provides a network device, where the network device is a route reflector, and includes: a memory, a transceiver, and at least one processor, where the memory stores instructions; the memory, The transceiver and the at least one processor are interconnected by a line;
- the at least one processor invokes the instruction to perform a message processing or control operation performed on the route reflector side in the third aspect.
- An eighth aspect of the present application provides a computer program product comprising instructions for use in a first root device, when the program is run on a computing device, performing the operations of the first device in the first aspect and the second aspect.
- a ninth aspect of the present application provides a computer program product comprising instructions for use in a route reflector, the operation of the route reflector of the third aspect described above being performed when the program is run on a computing device.
- a tenth aspect of the present application provides a computer storage medium for storing computer software instructions for use in the first aspect and the first device in the second aspect, including And the program designed by the first device in the second aspect.
- An eleventh aspect of the present application provides a computer storage medium for storing computer software instructions for use in the route reflector of the above third aspect, including for performing route reflection for the third aspect The program designed by the device.
- a twelfth aspect of the present application provides a network system, including: a first root device, a target leaf device, and a route reflector; wherein the first device is the first aspect, the second aspect, or the third aspect, and any The first device in the possible implementation manner; the target leaf device is the foregoing first aspect, the second aspect, or the third aspect, and the target leaf device in any possible implementation manner, the route reflector is the second aspect Or the leaf device of the third aspect and any possible implementation.
- the thirteenth aspect of the present application provides a network system, including: a first root device and a target leaf device; wherein the first root device is the first aspect or the second aspect, and the first of any possible implementation manners Root device; the target leaf device is the first aspect or the second aspect described above, and the target leaf device in any of the possible implementations.
- the fourteenth aspect of the present application provides a chip system, including: applied to a network device, where the network device is a first device, the chip system includes at least one processor and a communication interface, and the chip system may further include a memory.
- the memory, the communication interface, and the at least one processor are interconnected by a line, the at least one memory storing instructions; the instructions being executed by the processor to perform the first aspect or the second aspect, and The operation of the first root device in any of the possible implementations.
- a fifteenth aspect of the present application provides a chip system, including: being applied to a network device, where the network device is a route reflector, the chip system includes at least one processor and a communication interface, and the chip system may further include a memory.
- the memory, the communication interface, and the at least one processor are interconnected by a line, the at least one memory storing instructions; the instructions being executed by the processor to perform a third side, and any possible implementation The operation of the route reflector in the manner.
- the embodiments of the present application have the following advantages:
- the first root device receives the first multicast join message sent by the target leaf device or the second multicast join message sent by the route reflector, and the first multicast join message or the first group
- the multicast join information includes multicast routing information.
- the NLRI information of the multicast routing information includes the device routing identifier.
- the first device can determine that the multicast routing information meets the preferred condition according to the device routing identifier, and then the first device will satisfy the The multicast routing information of the preferred condition is added to the corresponding VPN routing table.
- the first device sends the multicast data to the target leaf device according to the VPN routing table.
- the device routing identifier is added to the NLRI information of the multicast routing information, so that the first root device can ensure that each target leaf device sends multicast routing information according to the device routing identifier, and each target leaf device is sent when the multicast data is sent. Will receive multicast data.
- FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present application
- FIG. 2 is a schematic diagram of another application scenario in the embodiment of the present application.
- FIG. 3 is a schematic diagram of an embodiment of a multicast routing processing method in an embodiment of the present application.
- FIG. 4 is a schematic diagram of another application scenario in the embodiment of the present application.
- FIG. 5 is a schematic diagram of another application scenario in the embodiment of the present application.
- FIG. 6 is a schematic diagram of another embodiment of a multicast routing processing method according to an embodiment of the present application.
- FIG. 7 is a schematic diagram of another application scenario in the embodiment of the present application.
- FIG. 8 is a schematic diagram of another application scenario in the embodiment of the present application.
- FIG. 9 is a schematic diagram of an embodiment of a network device according to an embodiment of the present application.
- FIG. 10 is a schematic diagram of another embodiment of a network device according to an embodiment of the present application.
- FIG. 11 is a schematic diagram of another embodiment of a network device according to an embodiment of the present application.
- FIG. 12 is a schematic diagram of an embodiment of a chip system in an embodiment of the present application.
- the embodiment of the present application provides a multicast routing processing method, a network device, and a route reflector (RR) for increasing device routing in network layer reachability information (NLRI) in a multicast route.
- the identifier is such that the multicast route with the device routing identifier added is preferred and forwarded.
- the embodiment of the present application can be applied to the MVPN as shown in FIG. 1 and FIG. 2.
- the MVPN shown in FIG. 1 includes M root devices and N leaf devices, where M is an integer greater than 1, and N is an integer greater than or equal to 2.
- M is an integer greater than 1
- N is an integer greater than or equal to 2.
- M is preferred.
- Different root devices in the root device is preferred.
- the MVPN shown in Figure 2 includes an RR, M root devices, and N leaf devices.
- M is an integer greater than 1.
- N is an integer greater than or equal to 2.
- the N leaf devices prefer to send multicast join messages. Different root devices in M root devices.
- the M root devices shown in FIG. 1 and FIG. 2 are the transmitting end PE devices, and are directly connected to the transmitting end CE device.
- the N leaf devices shown in FIG. 1 and FIG. 2 are the receiving end PE devices, and are directly connected to the receiving end CE device.
- the transmitting end PE device in FIG. 1 is directly connected to the receiving end PE device, and the transmitting end PE device in FIG.
- the PE device at the receiving end is connected through the RR.
- the M root devices are connected to the N leaf devices.
- the BGP connection is established between the root device and the leaf device.
- the root device and the leaf device independently send routing information.
- the MVPN shown in Figure 2 includes the RR, the M root devices, and the N leaf devices as clients.
- the client establishes an internal border gateway protocol (IBGP) connection with the RR.
- IBGP internal border gateway protocol
- the RR and the client form a cluster.
- the RR reflects routing information between clients, and there is no need to establish a BGP connection between clients.
- the M root devices and the N leaf devices shown in FIG. 1 and FIG. 2 may be routers or switches, and are not limited herein. In the embodiment of the present application, the M root devices and the N leaf devices are described by using only a router as an example.
- the first device may receive the first multicast join message sent by the leaf device, and may also receive the second multicast join message sent by the RR, and the application scenario diagram shown in FIG.
- the device receives the first multicast join message sent by the leaf device, and the first device is any one of the M root devices in the MVPN shown in FIG.
- a device receives the second multicast join message sent by the RR.
- the first device is any one of the M root devices in the MVPN shown in FIG. 2, and is respectively shown in FIG. 1 and FIG. 2 respectively.
- the illustrated scenario describes the multicast routing processing method in this embodiment of the present application:
- the first device receives the first multicast join message sent by the target leaf device.
- an embodiment of a multicast routing processing method in this embodiment of the present application includes:
- the 301 target leaf device sends a first multicast join message to the first root device.
- the target leaf device When the target leaf device needs to receive the multicast data, the target leaf device sends a first multicast join message to the first root device, where the first multicast join message is used to indicate that the target leaf device needs to join the MVPN and receive the multicast data.
- the first multicast join message includes multicast routing information, and the multicast routing information includes NLRI information, where the NLRI information includes a device routing identifier, where the device routing identifier is used to identify the first multicast join sent by the target leaf device. Message.
- the device routing identifier may be a target leaf device corresponding route ID (ROUTER ID), or may be a target leaf device preferred second device ROUTER ID, and the second root device is a target leaf device preferably received.
- the root device of the multicast data may be a target leaf device corresponding route ID (ROUTER ID), or may be a target leaf device preferred second device ROUTER ID, and the second root device is a target leaf device preferably received.
- Table 3-1 lists the NLRI information contained in the multicast routing information in the first multicast join message when the device routing identifier is the ROUTER ID of the target leaf device.
- the NLRI information in Table 3-1 adds the Originating route's IP address of the target leaf device, where the Originating route's IP address fills in the ROUTER ID corresponding to the leaf device.
- the NLRI information contained in the multicast routing information in the first multicast join message is as shown in Table 3-2, when the device routing identifier is the preferred second device of the target leaf device.
- the NLRI information in Table 3-2 adds the Originating route's IP address of the preferred second root device of the target leaf device.
- the Originating route's IP address of the second device fills in the ROUTER ID of the second device.
- the second device can be any one of the M root devices in the multicast route.
- the first root device determines, according to the device routing identifier, that the multicast routing information meets a preferred condition.
- the first multicast join message After the first device receives the first multicast join message, the first multicast join message includes the multicast routing information, and the NLRI information in the multicast routing information includes the device routing identifier, and the device routing identifier may be the target leaf device corresponding to the target device.
- the ROUTER ID can also be the ROUTER ID of the second device preferred by the target leaf device.
- the device route identifier is the ROUTER ID corresponding to the target leaf device
- the ROUTER ID corresponding to each target leaf device is different, that is, the different target leaf devices correspond to different ROUTER IDs. Therefore, the first root device corresponds to the target leaf device.
- the ROUTER ID can determine that the multicast routing information of the first multicast join message satisfies a preferred condition.
- the first root device may determine, according to the ROUTER ID of the second root device, the first multicast join that is sent by the target leaf device that is preferred to the second root device.
- the multicast routing information of the packet satisfies the preferred condition.
- the first device determines that the multicast routing information meets the preferred condition according to the ROUTER ID corresponding to the target leaf device, and determines the multicast according to the ROUTER ID of the second device that is preferred by the first root device according to the target leaf device.
- the routing information satisfies the preferred conditions and is illustrated separately:
- the first device is only illustrated by the root device 1 and the root device 2 shown in FIG. 4 and FIG. 5, and the target leaf device only uses the leaf device 1, the leaf device 2, and the leaf device. 3 for an example.
- the preferred second device of the target leaf device is either the root device 1 or the root device 2.
- the leaf device 1 and the leaf device 2 receive the multicast data from the root device 1, and the leaf device 3 preferably receives the multicast data from the root device 2 as an example.
- the leaf device 1 and the leaf device 2 can also receive multicast data from the root device 2 preferentially.
- the leaf device 3 can also preferentially receive multicast data from the root device 1 as long as the different leaf devices are different.
- the root device can receive multicast data, which is not specifically limited here.
- the device routing identifier included in the multicast routing information in the first multicast join message in FIG. 4 is the ROUTER ID corresponding to the target leaf device.
- each first The NLRI information in the multicast routing confidence in the multicast join message contains the ROUTER ID corresponding to the leaf device. Because the ROUTER ID corresponding to the leaf device 1, the leaf device 2, and the leaf device 3 are different, the root device 1 can be based on the leaf device. 1.
- the ROUTER ID corresponding to the leaf device 2 and the leaf device 3 respectively determines that the multicast routing information in the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively satisfies a preferred condition, that is, as shown in FIG.
- the three multicast routes of the root device 1 are all in the preferred condition.
- the leaf device 1, the leaf device 2, and the leaf device 3 respectively send the multicast routing information of the first multicast join message
- the root device 1 satisfies the preferred condition
- the root device 1 enters the cross-flow process of the multicast routing information of the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3, that is, the leaf device 1 and the leaf device 2
- the root device information corresponding to the preferred root device of the leaf device 3 is compared with the root device information of the root device 1 itself.
- the first multicast join message is displayed.
- the NLRI information in the multicast routing information includes the ROUTER ID corresponding to the leaf device. Because the ROUTER ID corresponding to the leaf device 1, the leaf device 2, and the leaf device 3 are different, the root device 2 can be based on the leaf device 1 and the leaf device 2 And the ROUTER ID corresponding to the leaf device 3 respectively determines that the multicast routing information in the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively meets a preferred condition, that is, the root device 2 is as shown in FIG.
- the three multicast routes satisfy the preferred condition.
- the leaf device 1, the leaf device 2, and the leaf device 3 send the multicast route of the first multicast join message
- the root device 2 satisfies the preferred condition
- the root device 2 respectively leaves the leaf.
- the multicast routing information of the first multicast join message sent by the device 1, the leaf device 2, and the leaf device 3 enters a cross-flow process, that is, the leaf device 1, the leaf device 2, and the leaf device 3 respectively Selected root root device corresponding to the device information of the device 2 itself and a root root device information is compared.
- the device routing identifier included in the multicast routing information in the first multicast join message in FIG. 5 is the ROUTER ID of the second root device preferred by the target leaf device.
- the first multicast The NLRI information in the multicast routing information in the join message includes the ROUTER ID corresponding to the preferred root device of the leaf device 1, the leaf device 2, and the leaf device 3 respectively. Since the leaf device 1 and the leaf device 2 preferably have the root device 1, The multicast routing information sent by the leaf device 1 and the leaf device 2 respectively carries the same ROUTER ID. Therefore, the root device 1 receives the two multicast routing information sent by the leaf device 1 and the leaf device 2, and only one of the multicast routing information is sent.
- the root device information of the preferred root device of the leaf device corresponding to a multicast routing information of the cross-flow process is compared with the root device information corresponding to the root device 1. Since the ROUTER ID of the root device 1 is different from the ROUTER ID of the root device 2, it is preferable that the multicast routing information sent by the leaf device 3 of the root device 2 enters the cross flow in the root device 1. Therefore, as shown in FIG. 5, the root device 1 obtains two pre-sentences of the multicast routing information, which are respectively one of the two multicast routing information sent by the leaf device 1 and the leaf device 2 of the root device 1, and Preferably, the leaf device 3 of the root device 2 transmits multicast routing information.
- the root device 2 shown in FIG. 5 receives the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3, as shown in Table 3-2
- the first multicast join message is displayed.
- the NLRI information in the multicast routing information includes the ROUTER ID corresponding to the preferred root device of the leaf device 1, the leaf device 2, and the leaf device 3 respectively. Since the leaf device 1 and the leaf device 2 prefer the root device 1, the leaf device 1
- the multicast routing information sent by the leaf device 2 is the same as the ROUTER ID. Therefore, the root device 2 receives the two multicast routing information sent by the leaf device 1 and the leaf device 2, and only one of the multicast routing information enters the cross process.
- the root device information of the preferred root device of the leaf device corresponding to a multicast routing information that is about to enter the cross-flow process is compared with the root device information corresponding to the root device 2. Further, since the ROUTER ID of the root device 1 is different from the ROUTER ID of the root device 2, it is preferable that the multicast routing information transmitted by the leaf device 3 of the root device 2 enters the cross flow in the root device 2. Therefore, as shown in FIG. 5, the root device 2 obtains two pre-sentences of the multicast routing information, which are respectively one of the two multicast routing information sent by the leaf device 1 and the leaf device 2 of the root device 1, and Preferably, the leaf device 3 of the root device 2 transmits multicast routing information.
- the first device determines whether the second device information included in the multicast routing information is the same as the first device information. If the information is the same, step 304 is performed.
- the first root device matches the second root device information in the multicast routing information that meets the preferred condition with the first root device.
- the first device information is compared.
- the second device information may be, for example, a management field (administrator) included in an import attribute of a routing target (RT) in the multicast routing information.
- the first device information may be the MVPN ID of the first root device, and the MVPN ID is the ID corresponding to the MVPN maintained by the first root device, for example, Table 3-3, and Table 3-3 is the first root.
- the plurality of VPN routing tables maintained by the device that is, the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3, the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3 have the same MVPN ID, for example, in the table.
- the MVPN IDs of VPN routing table 1, VPN routing table 2, and VPN routing table 3 are both (192.168.110.2).
- VPN routing table VPN routing table 1:192.168.110.2:13 VPN routing table 2: 192.168.110.2:10 VPN routing table 3: 192.168.110.2:05
- the first device compares the RT-import attribute of the multicast routing information in the first multicast join message with the administrator field and the MVPN ID of the first root device, for example, when the multicast routing information is included.
- the administrator field is ⁇ 192.168.110.2:13>
- the first device compares (192.168.110.2) in ⁇ 192.168.110.2:13> with the MVPN ID of the first device in Table 3-3, that is, the table. 3-3 shows the VPN routing table 1, VPN routing table 2, and VPN routing table 3 corresponding to (192.168.110.2) for comparison. If they are the same, it means the MVPN ID of the first root device and the administrator in the multicast routing information.
- the field is the same, and then the first device adds the multicast routing information in the first multicast join message to the VPN routing table.
- the VPN routing table 1, VPN routing table 2, and VPN shown in Table 3-3 If the MVPN ID of the routing table 3 is not (192.168.110.2), the multicast routing information corresponding to the first multicast join message is not the multicast routing information processed by the first root device. The first device does not use the first group. Add multicast routing information in the broadcast join message to the routing table. Or discard multicast join a first multicast routing information packets.
- the administrator field included in the multicast routing information is ⁇ 192.168.110.2:13>, which is only an example. In the actual application, the administrator field may be other, which is not limited herein.
- the root device 1 determines that the multicast routing information sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively satisfies the preferred condition
- the root device 1 respectively sends the leaf device 1, the leaf device 2, and the leaf device 3 respectively.
- the administrator field of the RT-import attribute of the multicast routing information in the first multicast join message is compared with the MVPN ID of the root device 1. If the two are the same, the root device 1 adds the first multicast to the packet.
- the multicast routing information is added to the VPN routing table of the root device 1.
- the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute of the multicast routing information in the first multicast join message sent by the leaf device 1 and the leaf device 2 respectively
- the administrator field is the same as the MVPN ID of the root device 1.
- the root device 1 adds the multicast routing information of the first multicast join message sent by the leaf device 1 and the leaf device 2 to the VPN routing table of the root device 1.
- the leaf device 3 is preferably the root device 2, so the leaf device 3 sends the multicast field included in the RT-import attribute of the multicast routing information in the first multicast join message to the root device 1 and the MVPN ID of the root device 1 is not If the same, the root device 1 discards the multicast routing information in the first multicast join message.
- the root device 2 shown in FIG. 4 determines that the multicast routing information sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively satisfies the preferred condition
- the root device 2 respectively sets the leaf device 1, the leaf device 2, and the leaf device 3.
- the administrator field of the RT-import attribute of the multicast routing information in the first multicast join message is compared with the MVPN ID of the root device 2. If the two are the same, the root device 2 joins the first multicast join message.
- the multicast routing information in the multicast routing information is added to the VPN routing table of the root device 2.
- the leaf device 3 Since the leaf device 3 is preferably the root device 2, the leaf device 3 sends the multicast routing information in the first multicast join message to the root device 2, and the Administrator field contained in the RT-import attribute is the same as the MVPN ID of the root device 2. Therefore, the root device 2 adds the multicast routing information in the first multicast join message sent by the leaf device 3 to the VPN routing table of the root device 2. However, the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, so the RT-import attribute of the multicast routing information in the first multicast join message sent by the leaf device 1 and the leaf device 2 respectively is included. The administrator field is different from the MVPN ID of the root device 2. Therefore, the root device 2 discards the multicast routing information in the first multicast join message sent by the leaf device 1 and the leaf device 2 respectively.
- the root device 1 shown in FIG. 5 determines one of the multicast routing information sent by the leaf device 1 and the leaf device 2, and the multicast routing information sent by the leaf device 3 enters a crossover process, and the root device 1 respectively Comparing one multicast routing information corresponding to the leaf device 1 and the leaf device 2, and the Administrator field included in the RT-import attribute in the multicast routing information corresponding to the leaf device 3 to the MVPN ID of the root device 1, if the two are the same
- the root device 1 adds the multicast routing information in the first multicast join message to the VPN routing table of the root device 1.
- the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the root device 1
- the MVPN ID is the same, so the root device 1 adds a multicast routing information corresponding to the leaf device 1 and the leaf device 2 to the VPN routing table of the root device 1.
- the leaf device 3 preferably has the root device 2, so the leaf device 3
- the multicast field information sent to the root device 1 is different from the MVPN ID of the root device 1 in the RT-import attribute.
- the root device 1 discards the multicast in the first multicast join message sent by the leaf device 3. Routing information.
- the root device 2 shown in FIG. 5 determines one of the multicast routing information sent by the leaf device 1 and the leaf device 2, and the multicast routing information sent by the leaf device 3 enters the cross process, and the root device 2 respectively sets the leaf device.
- a multicast routing information corresponding to the leaf device 2, and an LDAP field included in the RT-import attribute in the multicast routing information corresponding to the leaf device 3 is compared with the MVPN ID of the root device 2, if the two are the same, the root The device 2 adds the multicast routing information in the first multicast join message to the VPN routing table of the root device 2.
- the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the root device 2
- the MVPN IDs are different, so the root device 2 discards one multicast routing information corresponding to the leaf device 1 and the leaf device 2.
- the leaf device 3 is preferably the root device 2, so the RR-import attribute of the multicast routing information sent by the leaf device 3 to the root device 2 is the same as the MVPN ID of the root device 2, and the root device 2 sends the leaf device 3
- the multicast routing information in the first multicast join message is added to the VPN routing table of the root device 2.
- the first device adds the multicast routing information of the target leaf device to the target routing table according to the VPN instance identifier of the multicast routing information.
- the corresponding multicast routing information in the first multicast join message includes a VPN instance identifier, where the VPN instance identifier is used to represent a routing table corresponding to the multicast routing information.
- the first root device Since the first device maintains one or more VPN routing tables, when the multicast routing information needs to be added to the VPN routing table, the first root device needs to use the VPN instance identifier in the multicast routing information and the local VPN routing table.
- the index of the VPN routing table is matched. It should be noted that each VPN routing table in the first root device includes its corresponding index. Different indexes are used to distinguish different VPN routing tables. Specifically, The first device determines that the VPN instance ID of the multicast routing information is 13 according to the ⁇ 192.168.110.2:13> included in the administrator field, and the first root device identifies the VPN instance identifier 13 and Table 3-3. The index corresponding to the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3 are matched.
- the first device determines the VPN routing table with index 13 as the target routing table. For example, if the index corresponding to the VPN routing table 1 in Table 3-3 is 13, the first device determines the VPN routing table 1 as the target routing table, and adds the multicast routing information to the VPN routing table 1, for example, The multicast routing information is included The originating route's IP address and the multicast source in the NLRI information are added to the entry corresponding to the VPN routing table 1. It should be noted that the first device in this embodiment may also be used. The other information in the multicast routing information is added to the VPN routing table 1. The information such as the inbound and outbound interfaces of the device is added to the VPN routing table 1. If the routing table with index 13 is not in the multicast routing table, the first device discards the multicast routing information.
- the first root device sends multicast data to the target leaf device.
- the first device sends the multicast data to the target leaf device according to the information in the target routing table.
- the first device may send the first multicast data receiving message to the target leaf device, and the target leaf receives the first multicast. After receiving the message, the first multicast data receiving response message is sent to the first root device, and then the first root device sends the multicast data to the target leaf device that sends the first multicast data receiving response message; It is not necessary to send the first multicast data receiving message to the target leaf device, and directly send the multicast data to the target leaf device according to the information in the target routing table, which is not specifically limited herein.
- the leaf device 1 and the leaf device 2 preferably receive the multicast data by the root device 1, so the root device 1 transmits the multicast data to the leaf device 1 and the leaf device 2, respectively, according to the information in the target routing table.
- the leaf device 3 preferably receives the multicast data by the root device 2, so the root device 2 transmits the multicast data to the leaf device 3 according to the information in the target routing table.
- the leaf device 1 and the leaf device 2 preferably receive the multicast data by the root device 1.
- the first multicast join message sent by the leaf device 1 and the leaf device 2 is only one of the root device 1 in the root device 1.
- a multicast join message enters the cross-flow process. Before the root device 1 sends the multicast data to the leaf device 1 and the leaf device 2, the root device 1 sends a multicast data reception message to the leaf device 1 and the leaf device 2, and when the leaf device 1 After the leaf device 2 transmits the multicast data reception response message to the root device 1, the root device 1 transmits the multicast data to the leaf device 1 and the leaf device 2. Since the leaf device 3 preferably receives the multicast data, the root device 2 transmits the multicast data to the leaf device 3 according to the target routing table.
- the target leaf device sends a first multicast join message to the first root device, where the first multicast join message includes multicast routing information, and the NLRI information of the multicast routing information includes the device route identifier.
- the first device may determine that the multicast routing information meets the preferred condition according to the device routing identifier included in the NLRI information of the multicast routing information, when the first multicast routing information is used.
- the RT-import attribute contains the same MVPN ID of the first device.
- the first device adds the multicast routing information to the corresponding VPN routing table. When multicast data is delivered, the first one is generated. The device sends the multicast data to the target leaf device according to the VPN routing table.
- the first root device when the different target leaf devices prefer different root devices, the first root device sends the multicast route according to the target leaf device.
- the device routing identifier of the information ensures that each target leaf device sends multicast routing information to be optimized.
- the different root settings are preferred. Target leaves the device will receive the multicast data.
- the first device receives the second multicast join message sent by the RR.
- FIG. 6 another embodiment of a multicast routing processing method in this embodiment of the present application includes:
- the target leaf device sends a first multicast join message to the RR.
- the target leaf device When the target leaf device in the MVPN needs to receive the multicast data, the target leaf device adds the first multicast join message to the RR, and the first multicast join message is used to indicate that the target leaf device needs to join the MVPN and receive the multicast data.
- the first multicast join message includes multicast routing information, and the multicast routing information includes NLRI information, where the NLRI information includes a device routing identifier, where the device routing identifier is used to identify the first multicast join sent by the target leaf device. Message.
- the device routing identifier may be a ROUTER ID corresponding to the target leaf device, or a ROUTER ID of the second device preferred by the target leaf device.
- the device routing identifier may be a ROUTER ID corresponding to the target leaf device, or a ROUTER ID of the second device preferred by the target leaf device.
- ROUTER ID corresponding to the target leaf device
- ROUTER ID of the second device preferred by the target leaf device For details, refer to Table 3-1 and Table 3-2. .
- the RR determines, according to the device routing identifier, that the first multicast join message meets the pre-condition.
- the first multicast join message After receiving the first multicast join message, the first multicast join message includes the multicast routing information.
- the NLRI information in the multicast routing information includes the device route identifier.
- the device route identifier can be the ROUTER ID corresponding to the target leaf device. It can also be the ROUTER ID of the second device preferred by the target leaf device.
- the device route identifier is the ROUTER ID corresponding to the target leaf device
- the ROUTER ID corresponding to each target leaf device is different, that is, the different target leaf devices correspond to different ROUTER IDs. Therefore, the RR is based on the ROUTER ID corresponding to the target leaf device.
- the multicast routing information of the first multicast join message can be determined to meet the pre-condition.
- the RR determines, according to the ROUTER ID of the second device, the group of the first multicast join message that is sent by the target leaf device of the second device.
- the broadcast routing information satisfies the pre-conditions.
- the leaf device 1 and the leaf device 2 in FIG. 8 preferably have a root device 1
- the leaf device 3 preferably has a root device 2
- the RR transmits the first according to the leaf device 1 and the leaf device 2, respectively.
- the ROUTER ID of the root device 1 included in the multicast join message determines that the first multicast join message sent by the leaf device 1 and the leaf device 2 respectively meets the pre-conditions, and the RR is based on the preferred root device 2 of the leaf device 3.
- the ROUTER ID determines that the first multicast join message sent by the leaf device 3 satisfies the pre-condition.
- the RR sends a second multicast join message to the first root device.
- the first multicast join message sent by the target leaf device meets the pre-condition, so the RR sends the second multicast join message to the first device in the MVPN, and the first multicast join message joins the first multicast join message.
- the multicast routing information contained in the packet is the same.
- the multicast routing information in the first multicast join message sent by each target leaf device in this implementation is different because the different target leaf devices correspond to different ROUTER IDs.
- the corresponding ROUTER IDs are different. Therefore, the first multicast join message sent by each target leaf device is sent in the RR.
- the second multicast join message sent by the RR to the first root device is used for each target.
- the device route identifier is the ROUTER ID of the second device of the target leaf device
- the multicast route sent by the target leaf device of the same second root device is preferred.
- the information is forwarded in the RR.
- the device route identifier is the ROUTER ID of the second device that is preferred by the target leaf device
- the RR sends the information to the first device according to the information in the border gateway protocol (BGP).
- BGP border gateway protocol
- the second multicast join message is one of the first multicast join messages that meet the pre-conditions.
- the BGP is an autonomous system running on a transmission control protocol (TCP). Routing protocol.
- the target leaf device is only exemplified by the leaf device 1, the leaf device 2, and the leaf device 3.
- the preferred second device of the target leaf device is either the root device 1 or the root device 2.
- the leaf device 1 and the leaf device 2 receive the multicast data from the root device 1, and the leaf device 3 preferably receives the multicast data from the root device 2 as an example.
- the leaf device 1 and the leaf device 2 can also receive multicast data from the root device 2 preferentially.
- the leaf device 3 can also preferentially receive multicast data from the root device 1 as long as the different leaf devices are different.
- the root device can receive multicast data, which is not specifically limited here.
- the device routing identifier corresponding to the application scenario diagram shown in FIG. 7 is the ROUTER ID corresponding to the target leaf device.
- the NLRI information of the multicast routing information includes the ROUTER ID corresponding to the target leaf device.
- the corresponding ROUTER IDs of the leaf device 1, the leaf device 2, and the leaf device 3 are different, and the RR corresponds to the leaf device 1, the leaf device 2, and the leaf device 3 respectively.
- the ROUTER ID determines that the multicast routing information in the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively meets the pre-condition.
- the second multicast join message sent by the RR to the root device 1 and the root device 2 is the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively.
- the device routing identifier corresponding to the application scenario diagram shown in FIG. 8 is the ROUTER ID of the second root device preferred by the target leaf device.
- the first multicast join message is included.
- the NLRI information of the multicast routing information includes the ROUTER ID corresponding to the second root device preferred by the leaf device. Since both the leaf device 1 and the leaf device 2 are preferably the root device 1, the leaf device 1 and the leaf device 2 respectively correspond to the multicast.
- the routing information carries the same ROUTER ID. Therefore, the RR receives the two first multicast join messages sent by the leaf device 1 and the leaf device 2, and only one of the first multicast join messages is sent.
- the ROUTER ID of the root device 1 is different from the ROUTER ID of the root device 2.
- the first multicast join message sent by the leaf device 3 of the root device 2 is also forwarded in the RR.
- two first multicast join messages are sent in the RR, and two first multicast join messages respectively sent by the leaf device 1 and the leaf device 2 of the root device 1 are respectively selected.
- One, and preferably the leaf device 3 of the root device 2 sends a first multicast join message. Therefore, the second multicast join message sent by the RR to the root device 1 and the root device 2 is one of the first multicast join messages respectively sent by the leaf device 1 and the leaf device 2, and The first multicast join message sent by the leaf device 3.
- the first root device determines, according to the device routing identifier, that the multicast routing information meets a preferred condition.
- the second multicast join message After the first device receives the second multicast join message sent by the RR, the second multicast join message includes the multicast routing information, and the NLRI information of the multicast routing information includes the device route identifier, and the device route identifier may be the target leaf.
- the ROUTER ID corresponding to the device may also be the ROUTER ID of the second device preferred by the target leaf device.
- the device route identifier is the ROUTER ID corresponding to the target leaf device
- the ROUTER ID corresponding to each target leaf device is different, that is, the different target leaf devices correspond to different ROUTER IDs. Therefore, the first root device corresponds to the target leaf device.
- the ROUTER ID can determine that the multicast routing information of the second multicast join message satisfies a preferred condition.
- the second device corresponds to a different ROUTER ID. Therefore, the first device determines the second device according to the ROUTER ID of the second device.
- the multicast route of the second multicast join message sent by the target leaf device of the root device satisfies the preferred condition.
- the routing information satisfies the preferred conditions and is illustrated separately:
- the device routing identifier corresponding to the application scenario diagram shown in FIG. 7 is the ROUTER ID corresponding to the target leaf device.
- the NLRI information in the multicast routing information of the packet includes the ROUTER ID corresponding to the leaf device.
- the ROUTER ID corresponding to the leaf device 1, the leaf device 2, and the leaf device 3 are different, so the root device 1 is based on the leaf device 1 and the leaf device 2 And the ROUTER ID corresponding to the leaf device 3 respectively determines that the multicast routing information corresponding to the first multicast join message of the leaf device 1, the leaf device 2, and the leaf device 3 sent by the RR meets a preferred condition, and the root device 1 sets the leaf device 1 and the leaf.
- the multicast routing information of the first multicast join message corresponding to the device 2 and the leaf device 3 respectively enters a cross-flow process, that is, the root device information and the root device corresponding to the preferred root device of the leaf device 1, the leaf device 2, and the leaf device 3 respectively 1 Compare their own root device information.
- the process performed by the root device 2 is similar to the process performed by the root device 1 of FIG. 7, and details are not described herein again.
- the device routing identifier corresponding to the application scenario diagram shown in FIG. 8 is the ROUTER ID of the second root device preferred by the target leaf device.
- the root device 1 receives one of the first multicast join messages corresponding to the leaf device 1 and the leaf device 2, and the first multicast join message corresponding to the leaf device 3, as shown in Table 3.
- the NLRI information of the multicast routing information includes the ROUTER ID corresponding to the root device. Since the root device 1 and the root device 2 have different ROUTER IDs, the leaf device 1 and the leaf device 2 of the root device 1 are preferred.
- One of the multicast routing information meets the preferred conditions in the root device 1.
- the multicast routing information corresponding to the leaf device 3 of the root device 2 also satisfies the preferred condition in the root device 1.
- the process performed by the root device 2 is similar to the process performed by the root device 1 of FIG. 8 and will not be described herein.
- the first device determines whether the second device information included in the multicast routing information is the same as the first device information. If yes, step 606 is performed.
- the first root device matches the second root device information in the multicast routing information that meets the preferred condition with the first root device.
- the first device information is compared.
- the second device information may be, for example, a management field (administrator) included in an import attribute of a routing target (RT) in the multicast routing information.
- the first device information may be the MVPN ID of the first root device, and the MVPN ID is the ID corresponding to the MVPN maintained by the first root device, for example, Table 3-3, and Table 3-3 is the first root.
- the plurality of VPN routing tables maintained by the device that is, the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3, the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3 have the same MVPN ID, for example, in the table.
- the MVPN IDs of VPN routing table 1, VPN routing table 2, and VPN routing table 3 are both (192.168.110.2).
- the first device compares the RT-import attribute of the multicast routing information in the second multicast join message with the administrator field and the MVPN ID of the first root device, for example, when the multicast routing information is included.
- the administrator field is ⁇ 192.168.110.2:13>
- the first device compares (192.168.110.2) in ⁇ 192.168.110.2:13> with the MVPN ID of the first device in Table 3-3, that is, the table. 3-3 shows the VPN routing table 1, VPN routing table 2, and VPN routing table 3 corresponding to (192.168.110.2) for comparison. If they are the same, it means the MVPN ID of the first root device and the administrator in the multicast routing information.
- the field is the same, and then the first device adds the multicast routing information in the second multicast join message to the VPN routing table.
- the VPN routing table 1, VPN routing table 2, and VPN shown in Table 3-3 If the MVPN ID of the routing table 3 is not (192.168.110.2), the multicast routing information corresponding to the second multicast join message is not the multicast routing information processed by the first root device. The first device does not use the second group. Add multicast routing information in the broadcast join message to the routing table. The multicast routing information in the second multicast join message is discarded.
- the administrator field included in the multicast routing information is ⁇ 192.168.110.2:13>, which is only an example. In the actual application, the administrator field may be other, which is not limited herein.
- the root device 1 shown in FIG. 7 determines that the multicast routing information corresponding to the leaf device 1, the leaf device 2, and the leaf device 3 respectively meets the preferred conditions
- the root device 1 respectively sets the leaf device 1, the leaf device 2, and
- the administrator field of the RT-import attribute in the multicast routing information corresponding to the leaf device 3 is compared with the MVPN ID of the root device 1. If the two are the same, the root device 1 adds the multicast routing information to the VPN of the root device 1. In the routing table.
- the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the root device 1
- the MVPN ID is the same, so the root device 1 adds the multicast routing information corresponding to the leaf device 1 and the leaf device 2 to the VPN routing table of the root device 1.
- the leaf device 3 preferably has the root device 2, so the leaf device 3 is rooted.
- the multicast field information in the RT-import attribute of the device 1 is different from the MVPN ID of the root device 1.
- the root device 1 discards the multicast routing information corresponding to the leaf device 3.
- the root device 1 respectively sets the leaf device 1, the leaf device 2, and the leaf device 3.
- the administrator field of the RT-import attribute in the corresponding multicast routing information is compared with the MVPN ID of the root device 2. If the two are the same, the root device 2 adds the multicast routing information to the VPN routing table of the root device 2. in. Since the leaf device 3 is preferably the root device 2, the LDAP field included in the RT-import attribute of the leaf device 3 corresponding to the root device 2 is the same as the MVPN ID of the root device 2, so the root device 2 will be the leaf device 3.
- the corresponding multicast routing information is added to the VPN routing table of the root device 2.
- the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, so the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the MVPN ID of the root device 2.
- the root device 2 discards the multicast routing information corresponding to the leaf device 1 and the leaf device 2.
- the two multicast routing information corresponding to the RR received by the root device 1 in FIG. 8 is one of the multicast routing information corresponding to the leaf device 1 and the leaf device 2, and the multicast corresponding to the leaf device 3. Routing information.
- the root device 1 performs one of the multicast routing information corresponding to the leaf device 1 and the leaf device 2, and the administrator field of the RT-import attribute in the multicast routing information corresponding to the leaf device 3 and the MVPN ID of the root device 1 respectively. For comparison, if the two are the same, the root device 1 adds the multicast routing information to the VPN routing table of the root device 1.
- the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the root device 1
- the MVPN ID is the same, so the root device 1 adds a multicast routing information corresponding to the leaf device 1 and the leaf device 2 to the VPN routing table of the root device 1.
- the leaf device 3 preferably has the root device 2, so the leaf device 3 The root device 1 discards the multicast routing information corresponding to the leaf device 3, and the host device 1 has the same MVPN ID as the root device 1 in the corresponding multicast routing information.
- the two multicast routing information corresponding to the RR received by the root device 2 in FIG. 8 is one of the multicast routing information corresponding to the leaf device 1 and the leaf device 2, and the multicast routing information corresponding to the leaf device 3.
- the root device 2 compares the multicast routing information corresponding to the leaf device 1 and the leaf device 2, and the administrator field included in the RT-import attribute in the multicast routing information corresponding to the leaf device 3 with the MVPN ID of the root device 2, respectively. If the two are the same, the root device 2 adds the multicast routing information to the VPN routing table of the root device 1.
- the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the root device 2
- the MVPN IDs are different, so the root device 2 discards one multicast routing information corresponding to the leaf device 1 and the leaf device 2.
- the leaf device 3 is preferably the root device 2, so the router field corresponding to the RT-import attribute of the leaf device 3 has the same MVPN ID as the root device 2, and the root device 2 uses the multicast route corresponding to the leaf device 3.
- Information is added to the VPN routing table of root device 2.
- the first device adds the multicast routing information of the target leaf device to the target routing table according to the VPN instance identifier of the multicast routing information.
- the corresponding multicast routing information in the second multicast join message includes a VPN instance identifier, where the VPN instance identifier is used to represent a routing table corresponding to the multicast routing information.
- the first root device Since the first device maintains one or more VPN routing tables, when the multicast routing information needs to be added to the VPN routing table, the first root device needs to use the VPN instance identifier in the multicast routing information and the local VPN routing table.
- the index of the VPN routing table is matched. It should be noted that each VPN routing table in the first root device includes its corresponding index. Different indexes are used to distinguish different VPN routing tables. Specifically, The first device determines that the VPN instance ID of the multicast routing information is 13 according to the ⁇ 192.168.110.2:13> included in the administrator field, and the first root device identifies the VPN instance identifier 13 and Table 3-3. The index corresponding to the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3 are matched.
- the first device determines the VPN routing table with index 13 as the target routing table. For example, if the index corresponding to the VPN routing table 1 in Table 3-3 is 13, the first device determines the VPN routing table 1 as the target routing table, and adds the multicast routing information to the VPN routing table 1. For example, the originating route's IP address and the multicast source in the NLRI information included in the multicast routing information are added to the entry corresponding to the VPN routing table 1. In this embodiment, the first device may also add other information in the multicast routing information to the VPN routing table 1. The information such as the inbound and outbound interfaces of the device is added to the VPN routing table 1. If the routing table with index 13 is not in the multicast routing table, the first device discards the multicast routing information.
- the first root device sends multicast data to the target leaf device.
- the first device sends the multicast data to the target leaf device according to the information in the target routing table.
- the first root device when the first root device sends multicast data to the target leaf device, the first root device may directly send the multicast data to the target leaf device, and may also send the multicast data to the core device (Provider, P). The multicast data is sent, and then the P device sends the multicast data to the target leaf device, which is not limited herein.
- the first device directly sends the multicast data to the target leaf device, which is similar to the foregoing step 305 in FIG. 3, and details are not described herein again.
- the RR when the RR serves as the root device, the RR performs the foregoing steps 301 to 305 in FIG. 3, and the RR serves as the root device, and the RR acts as both a route reflector and a PE device. The role of this, will not repeat them here.
- the first multicast join message sent by the target leaf device to the RR includes the device route identifier, and the RR may determine each first according to the device route identifier.
- the multicast join message meets the pre-conditions.
- the device route identifier is the ROUTER ID of the leaf device
- the second multicast join message sent by the RR to the first device is the first multicast join message.
- the RR sends one of the first multicast join messages sent by the leaf device that is preferably the same second device to the first device.
- the first multicast join message includes the device routing identifier, and ensures that the first multicast join message satisfies the pre-conditions in the RR.
- the first device sends the packet to the first multicast device.
- the target leaf device of the first root device sends multicast data, so that the leaf devices that prefer different root devices can receive the multicast data.
- the method for processing the multicast routing in the embodiment of the present application has been described above.
- the description of the network device in the embodiment of the present application is described below with reference to the accompanying drawings.
- the network device in the embodiment of the present application may include a network device, a route reflector, and a chip system, and the functions are different in different roles.
- the edge device is only the first in the embodiment of the present application and the subsequent embodiments.
- the root device is explained as an example.
- the network device provided by the embodiment of the present application may be a first device or a chip system, where the network device is applied to a multicast virtual private network (MVPN), where the MVPN includes M root devices and N leaf devices.
- the M is an integer greater than 1
- the N is an integer greater than or equal to 2.
- the N leaf devices respectively select different root devices of the M root devices when sending the multicast join message.
- the network device 90 includes a receiving unit 901, a processing unit 902, and a transmitting unit 903.
- the receiving unit 901 can be used to execute the content described in step 301 in the embodiment corresponding to FIG. 3.
- the processing unit 902 can be used to perform the operations described in step 302, step 303, and step 304 in the corresponding embodiment of FIG.
- the sending unit 903 can be used to perform the content described in step 305 in the embodiment corresponding to FIG. 3, and can also perform the content described in step 607 in the corresponding embodiment of FIG. 6.
- the network device provided by the embodiment of the present application may be a route reflector or a chip system, where the network device is applied to an MVPN, where the MVPN includes a route reflector, M root devices, and N leaf devices, M is an integer greater than 1, and the N is an integer greater than or equal to 2.
- the N leaf devices respectively select different root devices of the M root devices when sending the multicast join message.
- the network device 100 includes a receiving unit 1001, a processing unit 1002, and a sending unit 1003.
- the receiving unit 1001 can be configured to receive the step 601 in the embodiment corresponding to FIG. 6 to send the first multicast joining message.
- the processing unit 1002 can be used to perform the content described in step 602 in the embodiment corresponding to FIG. 6.
- the transmitting unit 1003 can be used to execute the content described in step 604 in the embodiment corresponding to FIG. 6.
- FIG. 11 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.
- the network device is a first device.
- the first root device 110 includes at least one processor 1110, a memory 1150, and a transceiver 1130.
- the transceiver can include a receiver and a transmitter, and the memory 1150 can include read only memory and/or random access memory and provide operational instructions and data to the processor 1110.
- a portion of the memory 1150 can also include non-volatile random access memory (NVRAM).
- NVRAM non-volatile random access memory
- the memory 1150 stores the following elements, executable modules or data structures, or a subset thereof, or their extended set:
- the corresponding operation is performed by calling an operation instruction stored in the memory 1150 (which can be stored in the operating system).
- the processor 1110 controls the operation of the first root device 110, and the processor 1110 may also be referred to as a CPU (Central Processing Unit).
- Memory 1150 can include read only memory and random access memory and provides instructions and data to processor 1110.
- a portion of the memory 1150 can also include non-volatile random access memory (NVRAM).
- NVRAM non-volatile random access memory
- the components of the first device 110 are coupled together by a bus system 1120.
- the bus system 1120 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 1120 in the figure.
- the method disclosed in the foregoing embodiment of the present application may be applied to the processor 1110 or implemented by the processor 1110.
- the processor 1110 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1110 or an instruction in a form of software.
- the processor 1110 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or discrete hardware. Component.
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA off-the-shelf programmable gate array
- the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
- the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
- the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
- the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
- the storage medium is located in the memory 1150.
- the memory 1150 can be a physically separate unit or integrated with the processor 1110.
- the processor 1110 reads the information in the memory 1150 and completes the steps of the above method in combination with hardware.
- the transceiver 1130 may be used to perform the content described in step 301 in the embodiment corresponding to FIG. 3 and the content described in step 305 in the embodiment corresponding to FIG. 3, and may also be executed in the corresponding embodiment in FIG. The content described in step 607. Or the step of message transmission and reception of the first root device in other alternative embodiments.
- the processor 1110 can be used to perform the operations described in step 302, step 303, and step 304 in the corresponding embodiment of FIG. 3, and can also be used to perform step 604, step 605, and step 606 in the corresponding embodiment in FIG. 6, respectively.
- the structure of the route reflector can also be understood by referring to FIG. 11.
- the corresponding transceiver in the route reflector can be used to receive the first multicast join message in step 601 in the embodiment corresponding to FIG. 6.
- the content described in step 603 in the embodiment corresponding to FIG. 6 is performed.
- the processor can also be used to perform the description described in step 602 of the embodiment corresponding to FIG. Or the corresponding steps of receiving and processing the route reflector in other alternative embodiments.
- FIG. 12 is a schematic structural diagram of another embodiment of a chip system 120 according to an embodiment of the present application.
- the chip system 120 includes at least one processor 1210, a memory 1250, and a communication interface 1230.
- the memory 1250 can include read only memory and random access memory, and provides operational instructions and data to the processor 1210.
- a portion of memory 1250 may also include non-volatile random access memory (NVRAM).
- NVRAM non-volatile random access memory
- the memory 1250 stores the following elements, executable modules or data structures, or a subset thereof, or their extended set:
- the corresponding operation is performed by calling an operation instruction stored in the memory 1250 (which can be stored in the operating system).
- chip system used in the chip system and the network device are similar in structure, but different devices use different chip systems to achieve their respective functions.
- the processor 1210 controls the operation of the chip system, and the processor 1210 may also be referred to as a CPU (Central Processing Unit).
- Memory 1250 can include read only memory and random access memory and provides instructions and data to processor 1210.
- a portion of memory 1250 may also include non-volatile random access memory (NVRAM).
- the components of the chip system 110 are coupled together by a bus system 1220 in a specific application.
- the bus system 1220 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 1220 in the figure.
- Processor 1210 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1210 or an instruction in a form of software.
- the processor 1210 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or discrete hardware. Component.
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA off-the-shelf programmable gate array
- the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
- the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
- the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
- the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
- the storage medium is located in a memory 1250, which may be a physically separate unit, or may be integrated with the processor 1210.
- the processor 1210 reads the information in the memory 1250 and performs the steps of the above method in combination with its hardware.
- the communication interface 1230 can be used to perform the content described in step 301 in the embodiment corresponding to FIG. 3 and the content described in step 305 in the embodiment corresponding to FIG. 3, and can also be executed in the corresponding embodiment in FIG.
- the content described in step 604 can also be used to perform the content described in step 607 in the corresponding embodiment in FIG. Or the step of receiving and transmitting data in the first device or route reflector in other alternative embodiments.
- the processor 1210 may be configured to perform the operations described in step 302, step 303, step 304, and step 305 in the corresponding embodiment of FIG. 3, and may also be used to perform step 604, step 605 in the corresponding embodiment in FIG. Step 606 describes the content described separately. It can also be used to perform the description described in step 602 in the embodiment corresponding to FIG. 6. Or the step of data processing in the first root device or route reflector in other alternative embodiments.
- the computer program product includes one or more computer instructions.
- the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
- the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
- wire eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
- the computer readable storage medium can be any available media that can be stored by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
- the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
- the program may be stored in a computer readable storage medium, and the storage medium may include: ROM, RAM, disk or CD.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Disclosed in the present application is a multicast route processing method. The method provided by embodiments of the present application comprises: a first root device receives a first multicast joining message sent by a target leaf device or receives a second multicast joining message sent by a route reflector, the first multicast joining message comprising multicast route information, the multicast route information comprising a device route distinguisher, and multicast route information in the second multicast joining message is the same as the multicast route information in the first multicast joining message; the first root device determines according to the device route distinguisher that the multicast route information meets a preferring condition; the first root device determines whether second root device information comprised in the multicast route information is the same as the first root device information; if yes, the first root device adds the multicast route information of the target leaf device to a VPN route table of the first root device; the first root device sends multicast data to the target leaf device according to the VPN route table. The solution of the present application can ensure that each target leaf device can receive multicast data.
Description
本申请要求了2018年3月14日提交的,申请号为CN 201810210276.0,发明名称为“组播路由处理方法、网络设备以及路由反射器”的中国申请的优先权,其全部内容通过引用结合在本申请中。This application claims the priority of the Chinese application filed on March 14, 2018, the application number is CN 201810210276.0, the invention is entitled "multicast routing processing method, network device and route reflector", the entire contents of which are incorporated by reference. In this application.
本申请实施例涉及通讯领域,尤其涉及一种组播路由处理方法、网络设备以及路由反射器。The embodiments of the present disclosure relate to the field of communications, and in particular, to a multicast routing processing method, a network device, and a route reflector.
组播虚拟专用网(multicast virtual private network,MVPN)是一种基于边界网关协议(border gateway protocol,BGP)和多协议标签交(multiprotocol label switch,MPLS)的传输网络,MVPN是在公用网络上建立专用网络的技术,在MVPN中实现组播数据的传输。Multicast virtual private network (MVPN) is a transport network based on border gateway protocol (BGP) and multiprotocol label switch (MPLS). MVPN is established on the public network. The technology of the private network realizes the transmission of multicast data in MVPN.
现有技术中,当MVPN包括M个发送端服务提供商网络的边缘(provider edge,PE)设备,N个接收端PE设备,M为大于1的整数,N为大于或等于2的整数,N个接收端PE设备分别向M个发送端PE设备发送加入组播报文,M个发送端PE设备接收到N个接收端PE设备发送的组播路由后,M个发送端PE设备沿用了单播虚拟专用网(virtual private network,VPN)的规则对N个接收端PE设备发送的组播路由进行处理,现有技术中同一MVPN中的PE设备对应的路由标识(route distinguisher,RD)相同。所以M个发送端PE设备中的每个发送端PE设备只会优选N个接收端PE设备发送的组播路由中的一个组播路由进行前发和交叉。In the prior art, when the MVPN includes a provider edge (PE) device of the M sender service provider networks, and N receiver PE devices, M is an integer greater than 1, and N is an integer greater than or equal to 2, N The receiving PEs send the multicast packets to the M transmitting PEs. After the M transmitting PEs receive the multicast routes sent by the N receiving PEs, the M transmitting PEs use the single. The rules of the virtual private network (VPN) are used to process the multicast routes sent by the N receivers. In the prior art, the route identifiers (RDs) of the PEs in the same MVPN are the same. Therefore, each of the M-side PE devices can only forward and cross a multicast route in the multicast route sent by the N-side PE devices.
但是,当N个接收端PE设备中存在一个PE设备优选的发送端的PE设备与其他接收端PE设备优选的发送端的PE设备不同时,则存在不同的接收端PE设备优选了不同的发送端PE设备,发送端PE设备处理接收端PE发送的组播路由时,发送端PE设备只会优选一个组播路由进行前发和交叉处理,则一定会存在被丢弃的组播路由,导致存在接收端PE设备收不到组播数据,这样与收不到组播数据的PE设备相连的用户网络边缘(customer edge,CE)设备就无法接收组播数据。However, when there are one PE device at the receiving end of the PE device, and the PE device at the transmitting end of the PE device is different from the PE device at the transmitting end of the other receiving PE device, the different PE devices at the receiving end preferably have different transmitting PEs. On the device, the sending PE device processes the multicast route sent by the receiving PE. The PE device on the sending end only prefers one multicast route for pre-issue and cross-processing. The discarded multicast route must exist. The PE device cannot receive multicast data, so the user edge (CE) device connected to the PE device that does not receive the multicast data cannot receive multicast data.
发明内容Summary of the invention
本申请实施例提供了一种组播路由处理方法、网络设备以及路由反射器(route reflector,RR)用于在组播路由中的网络层可达信息(network layer reachability information,NLRI)增加设备路由标识,以使得增加了设备路由标识的组播路由得到优选和前发。The embodiment of the present application provides a multicast routing processing method, a network device, and a route reflector (RR) for increasing device routing in network layer reachability information (NLRI) in a multicast route. The identifier is such that the multicast route with the device routing identifier added is preferred and forwarded.
本申请实施例第一方面提供一种组播路由处理方法,所述方法应用于MVPN,所述MVPN包括M个根设备和N个叶子设备,所述M为大于1的整数,所述N为大于或等于2的整数,所述N个叶子设备在发送组播加入报文时,分别优选了所述M个根设备中的不同的根设备,针对第一根设备,包括:所述第一根设备接收目标叶子设备发送的第一组播加入报文,所述第一组播加入报文包括组播路由信息,所述组播路由信息中包括设备路由标识,所述目标叶子设备为所述N个叶子设备中的一个或多个,所述第一根设备为所述M个根设备中的任意一个;所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件;所述第一 根设备确定所述组播路由信息中包含的第二根设备信息与第一根设备信息是否相同,所述第二根设备信息为所述目标叶子设备所优选接收组播数据的第二根设备对应的信息;若相同,则所述第一根设备将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中;在有组播数据下发时,所述第一根设备根据所述VPN路由表向所述目标叶子设备发送所述组播数据。若不相同,则所述第一根设备将所述组播路由信息丢弃。由该第一方面可见,第一根设备可以根据组播路由信息中的根设备信息,确保所述组播路由信息在第一根设备中得到优选,然后将所述组播路由信息添加到所述第一根设备的VPN路由表中,在有组播数据下发时,第一根设备可以根据VPN路由表向目标叶子设备发送组播数据使得每个叶子设备都接收到组播数据。The first aspect of the present application provides a multicast routing processing method, where the method is applied to an MVPN, where the MVPN includes M root devices and N leaf devices, where the M is an integer greater than 1, and the N is An integer of greater than or equal to 2, the N-th leaf device preferably different root devices of the M root devices when sending a multicast join message, and the first root device includes: the first The root device receives the first multicast join message sent by the target leaf device, where the first multicast join message includes multicast routing information, where the multicast routing information includes a device routing identifier, and the target leaf device is Determining one or more of the N leaf devices, the first root device being any one of the M root devices; the first root device determining, according to the device routing identifier, that the multicast routing information is satisfied Preferably, the first root device determines whether the second root device information included in the multicast routing information is the same as the first root device information, and the second root device information is a preferred receiving group of the target leaf device. Broadcast data Corresponding information of the second root device; if the same, the first root device adds the multicast routing information of the target leaf device to the virtual private network VPN routing table of the first root device; When the broadcast data is delivered, the first root device sends the multicast data to the target leaf device according to the VPN routing table. If not, the first root device discards the multicast routing information. It can be seen that the first device can ensure that the multicast routing information is optimized in the first root device according to the root device information in the multicast routing information, and then add the multicast routing information to the device. In the VPN routing table of the first device, when the multicast data is delivered, the first device can send multicast data to the target leaf device according to the VPN routing table, so that each leaf device receives the multicast data.
基于本申请实施例第一方面,本申请实施例第一方面的第一种实现方式中,所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件包括:当所述设备路由标识为所述目标叶子设备对应的路由ID时,所述第一根设备根据所述目标叶子设备对应的路由ID确定所述组播路由信息满足优选条件。由第一方面的第一种实现方式可见,本申请实施例第一根设备可以根据每个叶子设备对应的路由ID确保每个目标叶子设备发送的组播路由信息在第一根设备中都得到优选,在实际应用中,提升了方案的可实现性。Based on the first aspect of the embodiment of the present application, in a first implementation manner of the first aspect of the embodiments of the present application, determining, by the first root device, that the multicast routing information meets a preferred condition according to the device routing identifier includes: When the device routing identifier is the routing ID corresponding to the target leaf device, the first root device determines that the multicast routing information meets a preferred condition according to the routing ID corresponding to the target leaf device. It can be seen that the first device in the first embodiment can ensure that the multicast routing information sent by each target leaf device is obtained in the first device according to the routing ID corresponding to each leaf device. Preferably, in practical applications, the achievability of the solution is improved.
基于本申请实施例第一方面以及第一方面的第一种实现方式,本申请实施例第一方面的第二种实现方式中,所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件包括:当所述设备路由标识为所述目标叶子设备所优选接收组播数据的所述第二根设备的路由ID时,所述第一根设备根据所述第二根设备的路由ID确定所述组播路由信息满足优选条件。由第一方面的第二种实现方式可见,本申请实施例提供了另外一种路由ID(目标叶子设备优选接收组播数据的第二根设备的路由ID)确保每个目标叶子设备发送所述组播路由信息满足优选条件,在实际应用中,提升了方案的多样性。According to the first aspect of the embodiment of the present application, and the first implementation manner of the first aspect, in a second implementation manner of the first aspect of the embodiment, the first root device determines the group according to the device routing identifier. The preferred condition for the broadcast routing information to be satisfied includes: when the device routing identifier is a routing ID of the second root device that the target leaf device preferably receives the multicast data, the first root device is according to the second root The routing ID of the device determines that the multicast routing information satisfies a preferred condition. It can be seen from the second implementation manner of the first aspect that the embodiment of the present application provides another routing ID (a routing ID of the second root device that the target leaf device preferably receives the multicast data) to ensure that each target leaf device sends the The multicast routing information satisfies the preferred conditions, and in practical applications, the diversity of the scheme is improved.
基于本申请实施例第一方面以及第一方面的第一种实现方式至第一方面的第二种实现方式中的任一项,本申请实施例第一方面的第三种实现方式中,所述第一根设备将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中包括:所述第一根设备确定所述组播路由信息的VPN实例标识与所述第一根设备的MVPN ID是否相同,所述MVPN ID为第一根设备的MVPN对应的ID地址;若相同,则所述第一根设备将所述组播路由信息添加到目标路由表中,所述目标路由表为所述第一根设备的VPN路由表中的其中一个,所述目标路由表用于指示所述第一根设备向所述目标叶子设备发送所述组播数据。由第一方面的第三种实现方式中可见,本申请实施例中第一根设备可以判断组播路由信息的VPN实例标识与第一根设备的MVPN ID是否相同来确定该组播路由信息是否为第一根设备处理的路由信息,提供了一种将组播路由信息添加到VPN路由表的具体方式。Based on the first aspect of the first embodiment of the present application and the second implementation manner of the first aspect to the second implementation manner of the first aspect, Adding the multicast routing information of the target leaf device to the virtual private network VPN routing table of the first root device, where the first root device determines the VPN instance of the multicast routing information And determining whether the MVPN ID is the same as the MVPN ID of the first root device, where the MVPN ID is an ID address corresponding to the MVPN of the first root device; if the same, the first root device adds the multicast routing information to the target In the routing table, the target routing table is one of the VPN routing tables of the first root device, and the target routing table is used to instruct the first root device to send the multicast to the target leaf device. data. As can be seen from the third implementation manner of the first aspect, in the embodiment of the present application, the first device can determine whether the VPN instance identifier of the multicast routing information is the same as the MVPN ID of the first root device, to determine whether the multicast routing information is The routing information processed by the first root device provides a specific way to add multicast routing information to the VPN routing table.
基于本申请实施例第一方面以及第一方面的第一种实现方式至第一方面的第三种实现方式中的任一项,本申请实施例第一方面的第四种实现方式中,所述第一根设备向所述目标叶子设备发送所述组播数据包括:所述第一根设备向所述目标叶子设备发送组播数据接收消息,所述组播数据接收消息用于指示所述目标叶子设备接收所述组播数据;所述第一根设备接收所述目标叶子设备发送的组播数据接收响应消息,所述组播数据接收响应消息用于指示所述目标叶子设备需要接收所述组播数据;所述第一根设备向发送所述组播数据接收响应消息对应的所述目标叶子设备发送所述组播数据。由第一方面的第四种实现方式可见,本申请实施例中第一根设备向目标叶子设备发送组播数据之前,向目标叶子设备发送组播数据接收 消息,然后向发送组播数据接收响应的目标叶子设备发送组播数据,提高了目标叶子设备接收组播数据的效率。According to the first aspect of the first embodiment of the present application, and the third implementation manner of the first aspect, the fourth implementation manner of the first aspect of the present application, The sending, by the first root device, the multicast data to the target leaf device includes: the first root device sending a multicast data receiving message to the target leaf device, where the multicast data receiving message is used to indicate the The target leaf device receives the multicast data; the first root device receives a multicast data receiving response message sent by the target leaf device, where the multicast data receiving response message is used to indicate that the target leaf device needs to receive the The multicast data is sent by the first root device to the target leaf device corresponding to the multicast data receiving response message. According to the fourth implementation manner of the first aspect, before the first device sends the multicast data to the target leaf device, the first device sends a multicast data receiving message to the target leaf device, and then receives the response to the sending multicast data. The target leaf device sends multicast data, which improves the efficiency of the target leaf device to receive multicast data.
本申请实施例第二方面提供一种组播路由处理方法,所述方法应用于MVPN,所述MVPN包括M个根设备和N个叶子设备以及路由反射器,所述M为大于1的整数,所述N为大于或等于2的整数,所述N个叶子设备在发送组播加入报文时,分别优选了所述M个根设备中的不同的根设备,针对第一根设备,包括:所述第一根设备接收路由反射器发送的第二组播加入报文,所述第二组播加入报文包括组播路由信息,所述组播路由信息中包括设备路由标识,所述目标叶子设备为所述N个叶子设备中的一个或多个,所述第一根设备为所述M个根设备中的任意一个;所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件;所述第一根设备确定所述组播路由信息中包含的第二根设备信息与第一根设备信息是否相同,所述第二根设备信息为所述目标叶子设备所优选接收组播数据的第二根设备对应的信息;若相同,则所述第一根设备将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中;在有组播数据下发时,所述第一根设备根据所述VPN路由表向所述目标叶子设备发送所述组播数据。若不相同,则所述第一根设备将所述组播路由信息丢弃。由该第二方面可见,第一根设备可以根据组播路由信息中的根设备信息,确保所述组播路由信息在第一根设备中得到优选,然后将所述组播路由信息添加到所述第一根设备的VPN路由表中,在有组播数据下发时,第一根设备可以根据VPN路由表向目标叶子设备发送组播数据使得每个叶子设备都接收到组播数据。A second aspect of the present application provides a multicast routing processing method, where the method is applied to an MVPN, where the MVPN includes M root devices, N leaf devices, and a route reflector, where the M is an integer greater than 1. The N is an integer greater than or equal to 2, and the N leaf devices respectively select different root devices of the M root devices when sending the multicast join message, and the first root device includes: Receiving, by the first root device, a second multicast join message sent by the route reflector, where the second multicast join message includes multicast routing information, where the multicast routing information includes a device routing identifier, the target The leaf device is one or more of the N leaf devices, the first root device is any one of the M root devices; the first root device determines the group according to the device routing identifier The broadcast routing information meets a preferred condition; the first root device determines whether the second root device information included in the multicast routing information is the same as the first root device information, and the second root device information is the target leaf device. Preferred The information corresponding to the second device that receives the multicast data; if the same, the first root device adds the multicast routing information of the target leaf device to the virtual private network VPN routing table of the first root device. When the multicast data is delivered, the first root device sends the multicast data to the target leaf device according to the VPN routing table. If not, the first root device discards the multicast routing information. It can be seen from the second aspect that the first device can ensure that the multicast routing information is preferred in the first root device according to the root device information in the multicast routing information, and then add the multicast routing information to the device. In the VPN routing table of the first device, when the multicast data is delivered, the first device can send multicast data to the target leaf device according to the VPN routing table, so that each leaf device receives the multicast data.
基于本申请实施例第二方面,本申请实施例第二方面的第一种实现方式中,所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件包括:当所述设备路由标识为所述目标叶子设备对应的路由ID时,所述第一根设备根据所述目标叶子设备对应的路由ID确定所述组播路由信息满足优选条件。由第二方面的第一种实现方式可见,本申请实施例第一根设备可以根据每个叶子设备对应的路由ID确保每个目标叶子设备发送的组播路由信息在第一根设备中都得到优选,在实际应用中,提升了方案的可实现性。Based on the second aspect of the embodiment of the present application, in a first implementation manner of the second aspect of the embodiments of the present application, determining, by the first root device, that the multicast routing information meets a preferred condition according to the device routing identifier includes: When the device routing identifier is the routing ID corresponding to the target leaf device, the first root device determines that the multicast routing information meets a preferred condition according to the routing ID corresponding to the target leaf device. According to the first implementation of the second aspect, the first device in the embodiment of the present application can ensure that the multicast routing information sent by each target leaf device is obtained in the first device according to the routing ID corresponding to each leaf device. Preferably, in practical applications, the achievability of the solution is improved.
基于本申请实施例第二方面以及第二方面的第一种实现方式,本申请实施例第二方面的第二种实现方式中,所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件包括:当所述设备路由标识为所述目标叶子设备所优选接收组播数据的所述第二根设备的路由ID时,所述第一根设备根据所述第二根设备的路由ID确定所述组播路由信息满足优选条件。由第二方面的第二种实现方式可见,本申请实施例提供了另外一种路由ID确保每个目标叶子设备发送所述组播路由信息满足优选条件,在实际应用中,提升了方案的多样性。According to the second aspect of the embodiments of the present application, and the first implementation manner of the second aspect, in the second implementation manner of the second aspect of the embodiments, the first root device determines the group according to the device routing identifier. The preferred condition for the broadcast routing information to be satisfied includes: when the device routing identifier is a routing ID of the second root device that the target leaf device preferably receives the multicast data, the first root device is according to the second root The routing ID of the device determines that the multicast routing information satisfies a preferred condition. As shown in the second implementation manner of the second aspect, the embodiment of the present application provides another route ID to ensure that each target leaf device sends the multicast routing information to meet a preferred condition, and in practical applications, the scheme is improved. Sex.
基于本申请实施例第二方面以及第二方面的第一种实现方式至第二方面的第二种实现方式中的任一项,本申请实施例第二方面的第三种实现方式中,所述第一根设备将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中包括:所述第一根设备确定所述组播路由信息的VPN实例标识与所述第一根设备的MVPN ID是否相同,所述MVPN ID为第一根设备的MVPN对应的ID地址;若相同,则所述第一根设备将所述组播路由信息添加到目标路由表中,所述目标路由表为所述第一根设备的VPN路由表中的其中一个,所述目标路由表用于指示所述第一根设备向所述目标叶子设备发送所述组播数据。由第二方面的第三种实现方式中可见,本申请实施例中第一根设备可以判断组播路由信息的VPN实例标识与第一根设备的MVPN ID是否相同来确定该组播路由信息是否为第一根设备处理的路由信息,提供了一种将组播路由信息添加到VPN路由表的具体方式。Based on the second aspect of the embodiment of the present application and the second implementation manner of the second aspect, the second implementation manner of the second aspect of the second embodiment of the present application, Adding the multicast routing information of the target leaf device to the virtual private network VPN routing table of the first root device, where the first root device determines the VPN instance of the multicast routing information And determining whether the MVPN ID is the same as the MVPN ID of the first root device, where the MVPN ID is an ID address corresponding to the MVPN of the first root device; if the same, the first root device adds the multicast routing information to the target In the routing table, the target routing table is one of the VPN routing tables of the first root device, and the target routing table is used to instruct the first root device to send the multicast to the target leaf device. data. It can be seen from the third implementation manner of the second aspect that, in the embodiment of the present application, the first device can determine whether the VPN instance identifier of the multicast routing information is the same as the MVPN ID of the first root device, to determine whether the multicast routing information is The routing information processed by the first root device provides a specific way to add multicast routing information to the VPN routing table.
基于本申请实施例第二方面以及第二方面的第一种实现方式至第二方面的第三种实现方式中的任一项,本申请实施例第二方面的第四种实现方式中,所述第一根设备向所述目标叶子设备发送所述组播数据包括:所述第一根设备向所述目标叶子设备发送组播数据接收消息,所述组播数据接收消息用于指示所述目标叶子设备接收所述组播数据;所述第一根设备接收所述目标叶子设备发送的组播数据接收响应消息,所述组播数据接收响应消息用于指示所述目标叶子设备需要接收所述组播数据;所述第一根设备向发送所述组播数据接收响应消息对应的所述目标叶子设备发送所述组播数据。由第一方面的第四种实现方式可见,本申请实施例中第一根设备向目标叶子设备发送组播数据之前,向目标叶子设备发送组播数据接收消息,然后向发送组播数据接收响应的目标叶子设备发送组播数据,提高了目标叶子设备接收组播数据的效率。According to the second aspect of the embodiment of the present application, and the third implementation manner of the second aspect, the fourth implementation manner of the second aspect of the embodiment of the present application, The sending, by the first root device, the multicast data to the target leaf device includes: the first root device sending a multicast data receiving message to the target leaf device, where the multicast data receiving message is used to indicate the The target leaf device receives the multicast data; the first root device receives a multicast data receiving response message sent by the target leaf device, where the multicast data receiving response message is used to indicate that the target leaf device needs to receive the The multicast data is sent by the first root device to the target leaf device corresponding to the multicast data receiving response message. According to the fourth implementation manner of the first aspect, before the first device sends the multicast data to the target leaf device, the first device sends a multicast data receiving message to the target leaf device, and then receives the response to the sending multicast data. The target leaf device sends multicast data, which improves the efficiency of the target leaf device to receive multicast data.
本申请实施例第三方面提供一种组播路由处理方法,所述方法应用于MVPN,所述MVPN包括路由反射器、M个根设备和N个叶子设备,所述M为大于1的整数,所述N为大于或等于2的整数,所述N个叶子设备在发送组播加入报文时,分别优选了所述M个根设备中的不同的根设备,包括:所述路由反射器接收目标叶子设备发送的第一组播加入报文,所述第一组播加入报文包括组播路由信息,所述组播路由信息中包括设备路由标识,所述目标叶子设备为所述N个叶子设备中的一个或多个;所述路由反射器根据所述设备路由标识确定所述第一组播加入报文都满足前发条件;所述路由反射器向第一根设备发送第二组播加入报文,所述第一根设备为所述M个根设备中的任意一个,所述第二组播加入报文与所述第一组播加入报文所包含的组播路由信息相同,所述第二组播加入报文用于指示所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件,并确定所述组播路由信息中包含的第二根设备信息与第一根设备信息是否相同,所述第二根设备信息为所述目标叶子设备所优选接收组播数据的第二根设备对应的信息,若相同,则所述第一根设备将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中,在有组播数据下发时,所述第一根设备根据所述VPN路由表向所述目标叶子设备发送所述组播数据。由第三方面可见,路由反射器根据组播路由信息中的设备路由标识可以确保每个第一组播加入报文在路由反射器中都得到前发,使得组播路由信息在第一根设备中可以都满足优选条件。A third aspect of the present application provides a multicast routing processing method, where the method is applied to an MVPN, where the MVPN includes a route reflector, M root devices, and N leaf devices, where the M is an integer greater than 1. The N is an integer greater than or equal to 2, and the N leaf devices respectively select different root devices of the M root devices when sending the multicast join message, including: the route reflector receiving a first multicast join message sent by the target leaf device, where the first multicast join message includes multicast routing information, where the multicast routing information includes a device routing identifier, and the target leaf device is the N One or more of the leaf devices; the route reflector determines that the first multicast join message meets the pre-condition according to the device route identifier; the route reflector sends the second group to the first root device Broadcasting the message, the first root device is any one of the M root devices, and the second multicast join message is the same as the multicast routing information included in the first multicast join message. The second multicast join report Determining, by the first root device, that the multicast routing information meets a preferred condition according to the device routing identifier, and determining whether the second root device information included in the multicast routing information is the same as the first root device information The second root device information is information corresponding to the second root device that the target leaf device preferably receives the multicast data. If the information is the same, the first root device uses the multicast routing information of the target leaf device. Adding to the virtual private network VPN routing table of the first root device, when the multicast data is delivered, the first root device sends the multicast data to the target leaf device according to the VPN routing table. . It can be seen from the third aspect that the route reflector can ensure that each first multicast join message is forwarded in the route reflector according to the device route identifier in the multicast routing information, so that the multicast routing information is in the first root device. The preferred conditions can all be met.
基于本申请实施例第三方面,本申请实施例第三方面的第一种实现方式中,所述路由反射器根据所述设备路由标识确定所述第一组播加入报文都满足前发条件包括:当所述设备路由标识为所述目标叶子设备对应的路由ID时,所述路由反射器根据所述目标叶子设备对应的路由ID确定所述第一组播加入报文都满足前发条件。由第三方面的第一种实现方式可见,本申请实施例路由反射器可以根据每个叶子设备对应的路由ID确保每个目标叶子设备发送的组播路由信息在路由反射器中都得到前发,在实际应用中,提升了方案的可实现性。According to the third aspect of the embodiments of the present application, in a first implementation manner of the third aspect of the embodiments of the present application, the route reflector determines, according to the device routing identifier, that the first multicast join message meets a pre-condition The routing reflector determines that the first multicast join message satisfies the pre-conditions according to the route ID corresponding to the target leaf device, when the device route identifier is the route ID corresponding to the target leaf device. . According to the first implementation manner of the third aspect, the route reflector of the embodiment of the present application can ensure that the multicast routing information sent by each target leaf device is forwarded in the route reflector according to the routing ID corresponding to each leaf device. In practical applications, the achievability of the solution is improved.
基于本申请实施例第三方面以及本申请实施例第三方面的第一种实现方式,本申请实施例第三方面的第二种实现方式中,所述路由反射器根据所述设备路由标识确定所述第一组播加入报文都满足前发条件包括:当所述设备路由标识为所述目标叶子设备优选接收组播数据的所述第二根设备的路由ID时,所述路由反射器根据所述第二根设备的路由ID确定所述第一组播加入报文都满足前发条件。由第三方面的第二种实现方式可见,本申请实施例提供了另外一种路由ID(目标叶子设备优选接收组播数据的第二根设备的路由ID)确保每个目标叶子设备发送所述组播路由信息满足优选条件,在实际应用中,提升了方案的多样性。Based on the third aspect of the embodiments of the present application and the first implementation manner of the third aspect of the application, in the second implementation manner of the third aspect of the application, the route reflector is determined according to the device routing identifier. The first multicast join message satisfies the pre-condition: when the device route identifier is the route ID of the second root device that the target leaf device preferably receives the multicast data, the route reflector Determining, according to the routing ID of the second root device, that the first multicast join message meets the pre-condition. It can be seen from the second implementation manner of the third aspect that the embodiment of the present application provides another routing ID (the routing ID of the second root device that the target leaf device preferably receives the multicast data) to ensure that each target leaf device sends the The multicast routing information satisfies the preferred conditions, and in practical applications, the diversity of the scheme is improved.
基于本申请实施例第三方面以及本申请实施例第三方面的第一种实现方式至第二种实 现方式中的任一项,本申请实施例第三方面的第三种实现方式中,所述路由反射器向所述第一根设备发送第二组播加入报文包括:当所述设备路由标识为所述目标叶子设备对应的路由ID时,所述第二组播加入报文为每个所述目标叶子设备分别发送的所述第一组播加入报文;所述路由反射器向第一根设备发送所述每个目标叶子设备分别发送的第一组播加入报文。由第三方面的第三种实现方式可见,本申请实施例中,由于每个目标叶子设备对应的路由ID都不同,因此,确保每个目标叶子设备发送组播加入报文在路由反射器中都能得到前发。According to the third aspect of the embodiments of the present application, and the third implementation manner of the third implementation manner of the third aspect of the present application, The sending, by the route reflector, the second multicast join message to the first root device includes: when the device route identifier is a route ID corresponding to the target leaf device, the second multicast join message is The first multicast join message sent by the target leaf device, and the route reflector sends the first multicast join message sent by each target leaf device to the first root device. It can be seen from the third implementation manner of the third aspect that, in the embodiment of the present application, the routing ID corresponding to each target leaf device is different, so that each target leaf device sends a multicast join message in the route reflector. Can get the front.
基于本申请实施例第三方面以及本申请实施例第三方面的第一种实现方式至第三种实现方式中的任一项,本申请实施例第三方面的第四种实现方式中,当所述设备路由标识为所述目标叶子设备优选接收组播数据的所述第二根设备的路由ID时,所述第二组播加入报文为满足前发条件的所述第一组播加入报文中的一个;所述路由反射器向所述第一根设备发送满足前发条件的所述第一组播加入报文中的一个。由第三方面的第四种实现方式可见,本申请实施例中,路由反射器向第一根设备发送的第二组播加入报文为优选了第二根设备的目标叶子设备所发送的第一组播加入报文中的一个,节省了该组播虚拟专用的的网络资源。Based on the third aspect of the embodiments of the present application, and the first implementation manner to the third implementation manner of the third aspect of the present application, in a fourth implementation manner of the third aspect of the embodiments of the present application, When the device routing identifier is the routing ID of the second root device that the target leaf device preferably receives the multicast data, the second multicast join message is the first multicast join that meets the pre-condition One of the packets: the route reflector sends one of the first multicast join messages that meet the pre-conditions to the first root device. The fourth implementation manner of the third device is as follows: One of the multicast join messages saves the network resources dedicated to the multicast virtual.
本申请实施例第四方面提供一种网络设备,所述网络设备为第一根设备,该第一根设备包括:接收单元、处理单元和发送单元,该接收单元用于执行上述第一方面、第二方面以及任一可能的实现方式中涉及到接收操作的步骤;该处理单元用于执行上述第一方面、第二方面以及任一可能的实现方式中涉及到处理操作的步骤;该发送单元用于执行上述、第二方面以及任一可能的实现方式中涉及到发送操作的步骤。A fourth aspect of the present application provides a network device, where the network device is a first root device, where the first root device includes: a receiving unit, a processing unit, and a sending unit, where the receiving unit is configured to perform the foregoing first aspect, The second aspect and any possible implementations relate to the step of receiving a operation; the processing unit is configured to perform the steps of the processing operations described above in the first aspect, the second aspect, and any possible implementation; the transmitting unit The steps for performing the transmitting operation in performing the above, the second aspect, and any of the possible implementations.
本申请实施例第五方面提供一种路由反射器,该路由反射器包括:接收单元、处理单元和发送单元,该接收单元用于执行上述第二方面以及任一可能的实现方式中涉及到接收操作的步骤;该处理单元用于执行上述第二方面以及任一可能的实现方式中涉及到处理操作的步骤;该发送单元用于执行上述第二方面以及任一可能的实现方式中涉及到发送操作的步骤。A fifth aspect of the embodiments of the present application provides a route reflector, where the route reflector includes: a receiving unit, a processing unit, and a sending unit, where the receiving unit is configured to perform the foregoing second aspect, and any possible implementation relates to receiving a step of operating; the processing unit is configured to perform the steps of the second aspect and any of the possible implementations related to the processing operation; the sending unit is configured to perform the foregoing second aspect and any possible implementation relates to sending The steps of the operation.
本申请实施例第六方面提供一种网络设备,所述网络设备为第一根设备,其特征在于,包括:存储器、收发器和至少一个处理器,所述存储器中存储有指令;所述存储器、所述收发器和所述至少一个处理器通过线路互联;A sixth aspect of the embodiments of the present application provides a network device, where the network device is a first device, and includes: a memory, a transceiver, and at least one processor, where the memory stores an instruction; the memory The transceiver and the at least one processor are interconnected by a line;
所述至少一个处理器调用所述指令,执行第一方面以及第二方面中在所述第一根设备侧进行的消息处理或控制操作。The at least one processor invokes the instructions to perform the message processing or control operations performed on the first root device side in the first aspect and the second aspect.
本申请实施例第七方面提供一种网络设备,所述网络设备为路由反射器,其特征在于,包括:存储器、收发器和至少一个处理器,所述存储器中存储有指令;所述存储器、所述收发器和所述至少一个处理器通过线路互联;A seventh aspect of the embodiments of the present application provides a network device, where the network device is a route reflector, and includes: a memory, a transceiver, and at least one processor, where the memory stores instructions; the memory, The transceiver and the at least one processor are interconnected by a line;
所述至少一个处理器调用所述指令,执行第三方面中在所述路由反射器侧进行的消息处理或控制操作。The at least one processor invokes the instruction to perform a message processing or control operation performed on the route reflector side in the third aspect.
本申请第八方面提供一种包含指令的计算机程序产品,应用于第一根设备,当该程序在计算设备上运行时,执行上述第一方面以及第二方面中第一根设备的操作。An eighth aspect of the present application provides a computer program product comprising instructions for use in a first root device, when the program is run on a computing device, performing the operations of the first device in the first aspect and the second aspect.
本申请第九方面提供一种包含指令的计算机程序产品,应用于路由反射器,当该程序在计算设备上运行时,执行上述第三方面中路由反射器的操作。A ninth aspect of the present application provides a computer program product comprising instructions for use in a route reflector, the operation of the route reflector of the third aspect described above being performed when the program is run on a computing device.
本申请实施例第十方面提供了一种计算机存储介质,该计算机存储介质用于储存为上述第一方面以及第二方面中第一根设备所用的计算机软件指令,其包括用于执行为第一方面以及第二方面中第一根设备所设计的程序。A tenth aspect of the present application provides a computer storage medium for storing computer software instructions for use in the first aspect and the first device in the second aspect, including And the program designed by the first device in the second aspect.
本申请实施例第十一方面提供了一种计算机存储介质,该计算机存储介质用于储存为上 述第三方面的路由反射器所用的计算机软件指令,其包括用于执行为第三方面的路由反射器所设计的程序。An eleventh aspect of the present application provides a computer storage medium for storing computer software instructions for use in the route reflector of the above third aspect, including for performing route reflection for the third aspect The program designed by the device.
本申请十二方面提供一种网络系统,包括:第一根设备、目标叶子设备和路由反射器;其中,该第一根设备为上述第一方面、第二方面或第三方面,以及任一可能的实现方式中的第一根设备;该目标叶子设备为上述第一方面、第二方面或第三方面,以及任一可能的实现方式中的目标叶子设备,该路由反射器为第二方面或第三方面以及任一可能的实现方式中的叶子设备。A twelfth aspect of the present application provides a network system, including: a first root device, a target leaf device, and a route reflector; wherein the first device is the first aspect, the second aspect, or the third aspect, and any The first device in the possible implementation manner; the target leaf device is the foregoing first aspect, the second aspect, or the third aspect, and the target leaf device in any possible implementation manner, the route reflector is the second aspect Or the leaf device of the third aspect and any possible implementation.
本申请十三方面提供一种网络系统,包括:第一根设备和目标叶子设备;其中,该第一根设备为上述第一方面或第二方面,以及任一可能的实现方式中的第一根设备;该目标叶子设备为上述第一方面或第二方面,以及任一可能的实现方式中的目标叶子设备。The thirteenth aspect of the present application provides a network system, including: a first root device and a target leaf device; wherein the first root device is the first aspect or the second aspect, and the first of any possible implementation manners Root device; the target leaf device is the first aspect or the second aspect described above, and the target leaf device in any of the possible implementations.
本申请第十四方面提供一种芯片系统,包括:应用于网络设备中,该网络设备为第一根设备,所述芯片系统包括至少一个处理器和通信接口,该芯片系统中还可以包括存储器,所述存储器、所通信接口和所述至少一个处理器通过线路互联,所述至少一个存储器中存储有指令;所述指令被所述处理器执行,以执行第一方面或第二方面,以及任一可能的实现方式中所述第一根设备的操作。The fourteenth aspect of the present application provides a chip system, including: applied to a network device, where the network device is a first device, the chip system includes at least one processor and a communication interface, and the chip system may further include a memory. The memory, the communication interface, and the at least one processor are interconnected by a line, the at least one memory storing instructions; the instructions being executed by the processor to perform the first aspect or the second aspect, and The operation of the first root device in any of the possible implementations.
本申请第十五方面提供一种芯片系统,包括:应用于网络设备中,该网络设备为路由反射器,所述芯片系统包括至少一个处理器和通信接口,该芯片系统中还可以包括存储器,所述存储器、所通信接口和所述至少一个处理器通过线路互联,所述至少一个存储器中存储有指令;所述指令被所述处理器执行,以执行第三面,以及任一可能的实现方式中所述路由反射器的操作。A fifteenth aspect of the present application provides a chip system, including: being applied to a network device, where the network device is a route reflector, the chip system includes at least one processor and a communication interface, and the chip system may further include a memory. The memory, the communication interface, and the at least one processor are interconnected by a line, the at least one memory storing instructions; the instructions being executed by the processor to perform a third side, and any possible implementation The operation of the route reflector in the manner.
从以上技术方案可以看出,本申请实施例具有以下优点:As can be seen from the above technical solutions, the embodiments of the present application have the following advantages:
本实施例中,所述第一根设备接收目标叶子设备发送的第一组播加入报文或接收路由反射器发送的第二组播加入报文,第一组播加入报文或第一组播加入报文中包含组播路由信息,该组播路由信息的NLRI信息包含设备路由标识,第一根设备可以根据设备路由标识确定该组播路由信息满足优选条件,然后第一根设备将满足优选条件的组播路由信息添加到对应的VPN路由表中,在有组播数据下发时,第一根设备根据VPN路由表向目标叶子设备发送组播数据,因此,本实施例中,在组播路由信息的NLRI信息中添加设备路由标识,使得第一根设备可以根据设备路由标识确保每个目标叶子设备发送组播路由信息得到优选,在组播数据下发时,每个目标叶子设备都会收到组播数据。In this embodiment, the first root device receives the first multicast join message sent by the target leaf device or the second multicast join message sent by the route reflector, and the first multicast join message or the first group The multicast join information includes multicast routing information. The NLRI information of the multicast routing information includes the device routing identifier. The first device can determine that the multicast routing information meets the preferred condition according to the device routing identifier, and then the first device will satisfy the The multicast routing information of the preferred condition is added to the corresponding VPN routing table. When the multicast data is delivered, the first device sends the multicast data to the target leaf device according to the VPN routing table. Therefore, in this embodiment, The device routing identifier is added to the NLRI information of the multicast routing information, so that the first root device can ensure that each target leaf device sends multicast routing information according to the device routing identifier, and each target leaf device is sent when the multicast data is sent. Will receive multicast data.
图1为本申请实施例中一个应用场景示意图;FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present application;
图2为本申请实施例中另一个应用场景示意图;2 is a schematic diagram of another application scenario in the embodiment of the present application;
图3为本申请实施例中组播路由处理方法的一个实施例示意图;3 is a schematic diagram of an embodiment of a multicast routing processing method in an embodiment of the present application;
图4为本申请实施例中另一个应用场景示意图;4 is a schematic diagram of another application scenario in the embodiment of the present application;
图5为本申请实施例中另一个应用场景示意图;FIG. 5 is a schematic diagram of another application scenario in the embodiment of the present application;
图6为本申请实施例中组播路由处理方法的另一个实施例示意图;FIG. 6 is a schematic diagram of another embodiment of a multicast routing processing method according to an embodiment of the present application;
图7为本申请实施例中另一个应用场景示意图;FIG. 7 is a schematic diagram of another application scenario in the embodiment of the present application;
图8为本申请实施例中另一个应用场景示意图;FIG. 8 is a schematic diagram of another application scenario in the embodiment of the present application;
图9为本申请实施例中网络设备的一个实施例示意图;FIG. 9 is a schematic diagram of an embodiment of a network device according to an embodiment of the present application;
图10为本申请实施例中网络设备的另一个实施例示意图;FIG. 10 is a schematic diagram of another embodiment of a network device according to an embodiment of the present application;
图11为本申请实施例中网络设备的另一个实施例示意图;FIG. 11 is a schematic diagram of another embodiment of a network device according to an embodiment of the present application;
图12为本申请实施例中芯片系统的一个实施例示意图。FIG. 12 is a schematic diagram of an embodiment of a chip system in an embodiment of the present application.
本申请实施例提供了一种组播路由处理方法、网络设备以及路由反射器(route reflector,RR)用于在组播路由中的网络层可达信息(network layer reachability information,NLRI)增加设备路由标识,以使得增加了设备路由标识的组播路由得到优选和前发。The embodiment of the present application provides a multicast routing processing method, a network device, and a route reflector (RR) for increasing device routing in network layer reachability information (NLRI) in a multicast route. The identifier is such that the multicast route with the device routing identifier added is preferred and forwarded.
本申请实施例可应用于如图1以及图2所示的MVPN中。The embodiment of the present application can be applied to the MVPN as shown in FIG. 1 and FIG. 2.
图1所示的MVPN包括M个根设备以及N个叶子设备,M为大于1的整数,N为大于或等于2的整数,N个叶子设备在发送组播加入报文时,优选了M个根设备中的不同的根设备。The MVPN shown in FIG. 1 includes M root devices and N leaf devices, where M is an integer greater than 1, and N is an integer greater than or equal to 2. When the N leaf devices send multicast join messages, M is preferred. Different root devices in the root device.
图2所示的MVPN包括RR、M个根设备以及N个叶子设备,M为大于1的整数,N为大于或等于2的整数,N个叶子设备在发送组播加入报文时,优选了M个根设备中的不同的根设备。The MVPN shown in Figure 2 includes an RR, M root devices, and N leaf devices. M is an integer greater than 1. N is an integer greater than or equal to 2. The N leaf devices prefer to send multicast join messages. Different root devices in M root devices.
需要说明的是,图1以及图2所示的M个根设备为发送端PE设备,与发送端CE设备直接相连。图1以及图2所示的N个叶子设备为接收端PE设备,与接收端CE设备直接相连,图1中的发送端PE设备与接收端的PE设备直接相连,图2中发送端PE设备与接收端的PE设备通过RR连接。It should be noted that the M root devices shown in FIG. 1 and FIG. 2 are the transmitting end PE devices, and are directly connected to the transmitting end CE device. The N leaf devices shown in FIG. 1 and FIG. 2 are the receiving end PE devices, and are directly connected to the receiving end CE device. The transmitting end PE device in FIG. 1 is directly connected to the receiving end PE device, and the transmitting end PE device in FIG. The PE device at the receiving end is connected through the RR.
图1所示的MVPN,M个根设备分别与N个叶子设备相连接,根设备与叶子设备之间建立BGP连接,根设备与叶子设备之间独立发送路由信息。In the MVPN shown in Figure 1, the M root devices are connected to the N leaf devices. The BGP connection is established between the root device and the leaf device. The root device and the leaf device independently send routing information.
图2所示的MVPN,包括RR,M个根设备以及N个叶子设备分别作为客户机(Client),客户机与RR之间建立内部边界网关协议(internal border gateway protocol,IBGP)连接。RR和客户机组成一个集群(Cluster)。RR在客户机之间反射路由信息,客户机之间不需要建立BGP连接。The MVPN shown in Figure 2 includes the RR, the M root devices, and the N leaf devices as clients. The client establishes an internal border gateway protocol (IBGP) connection with the RR. The RR and the client form a cluster. The RR reflects routing information between clients, and there is no need to establish a BGP connection between clients.
需要说明的是,图1以及图2所示M个根设备以及N个叶子设备可以是路由器,也可以是交换机,此处不做限定。本申请实施例M个根设备以及N个叶子设备仅以路由器作为例子进行说明。It should be noted that the M root devices and the N leaf devices shown in FIG. 1 and FIG. 2 may be routers or switches, and are not limited herein. In the embodiment of the present application, the M root devices and the N leaf devices are described by using only a router as an example.
本申请实施例中,第一根设备可以接收叶子设备发送的第一组播加入报文,也可以接收RR发送的第二组播加入报文,图1所示的应用场景示意图对应第一根设备接收叶子设备发送的第一组播加入报文,需要说明的是,第一根设备为图1所示的MVPN中的M个根设备的任意一个,图2所示的应用场景示意图对应第一根设备接收RR发送的第二组播加入报文,需要说明的是,第一根设备为图2所示的MVPN中的M个根设备的任意一个,下面分别对图1以及图2所示的场景对本申请实施例的组播路由处理方法进行描述:In the embodiment of the present application, the first device may receive the first multicast join message sent by the leaf device, and may also receive the second multicast join message sent by the RR, and the application scenario diagram shown in FIG. The device receives the first multicast join message sent by the leaf device, and the first device is any one of the M root devices in the MVPN shown in FIG. A device receives the second multicast join message sent by the RR. It should be noted that the first device is any one of the M root devices in the MVPN shown in FIG. 2, and is respectively shown in FIG. 1 and FIG. 2 respectively. The illustrated scenario describes the multicast routing processing method in this embodiment of the present application:
一、第一根设备接收目标叶子设备发送的第一组播加入报文。The first device receives the first multicast join message sent by the target leaf device.
请参考图3,本申请实施例中组播路由处理方法的一个实施例包括:Referring to FIG. 3, an embodiment of a multicast routing processing method in this embodiment of the present application includes:
301目标叶子设备向第一根设备发送第一组播加入报文。The 301 target leaf device sends a first multicast join message to the first root device.
当目标叶子设备需要接收组播数据时,目标叶子设备向第一根设备发送的第一组播加入报文,第一组播加入报文用于指示目标叶子设备需要加入MVPN,接收组播数据。其中, 第一组播加入报文包括组播路由信息,组播路由信息包含NLRI信息,该NLRI信息中包含设备路由标识,该设备路由标识用于标识该目标叶子设备发送的第一组播加入报文。When the target leaf device needs to receive the multicast data, the target leaf device sends a first multicast join message to the first root device, where the first multicast join message is used to indicate that the target leaf device needs to join the MVPN and receive the multicast data. . The first multicast join message includes multicast routing information, and the multicast routing information includes NLRI information, where the NLRI information includes a device routing identifier, where the device routing identifier is used to identify the first multicast join sent by the target leaf device. Message.
具体地,本实施例中设备路由标识可以是目标叶子设备对应路由ID(ROUTER ID),也可以是目标叶子设备优选的第二根设备的ROUTER ID,第二根设备为目标叶子设备所优选接收组播数据的根设备。Specifically, in this embodiment, the device routing identifier may be a target leaf device corresponding route ID (ROUTER ID), or may be a target leaf device preferred second device ROUTER ID, and the second root device is a target leaf device preferably received. The root device of the multicast data.
当设备路由标识为目标叶子设备对应ROUTER ID时,第一组播加入报文中的组播路由信息包含的NLRI信息如表3-1所示。表3-1中的NLRI信息增加了目标叶子设备的始发路由器IP地址(Originating route’s IP address),其中Originating route’s IP address填写了叶子设备对应的ROUTER ID。Table 3-1 lists the NLRI information contained in the multicast routing information in the first multicast join message when the device routing identifier is the ROUTER ID of the target leaf device. The NLRI information in Table 3-1 adds the Originating route's IP address of the target leaf device, where the Originating route's IP address fills in the ROUTER ID corresponding to the leaf device.
表3-1.组播路由信息的NLRI信息Table 3-1. NLRI information of multicast routing information
当设备路由标识为目标叶子设备优选的第二根设备对应ROUTER ID时,第一组播加入报文中的组播路由信息包含的NLRI信息如表3-2所示。表3-2中的NLRI信息增加了目标叶子设备的优选的第二根设备的Originating route’s IP address,其中第二根设备的Originating route’s IP address填写了第二根设备对应ROUTER ID,此处需要说明的是,第二根设备可以是组播路由中M个根设备的任意一个。The NLRI information contained in the multicast routing information in the first multicast join message is as shown in Table 3-2, when the device routing identifier is the preferred second device of the target leaf device. The NLRI information in Table 3-2 adds the Originating route's IP address of the preferred second root device of the target leaf device. The Originating route's IP address of the second device fills in the ROUTER ID of the second device. The second device can be any one of the M root devices in the multicast route.
表3-2.组播路由信息的NLRI信息Table 3-2. NLRI Information of Multicast Routing Information
302、第一根设备根据设备路由标识确定组播路由信息满足优选条件。302. The first root device determines, according to the device routing identifier, that the multicast routing information meets a preferred condition.
第一根设备接收到第一组播加入报文之后,第一组播加入报文包含组播路由信息,组播路由信息中的NLRI信息包含设备路由标识,设备路由标识可以是目标叶子设备对应的ROUTER ID,也可以是目标叶子设备优选的第二根设备的ROUTER ID。After the first device receives the first multicast join message, the first multicast join message includes the multicast routing information, and the NLRI information in the multicast routing information includes the device routing identifier, and the device routing identifier may be the target leaf device corresponding to the target device. The ROUTER ID can also be the ROUTER ID of the second device preferred by the target leaf device.
当设备路由标识为目标叶子设备对应的ROUTER ID,由于每个目标叶子设备对应的ROUTER ID是不同的,即不同的目标叶子设备对应不同的ROUTER ID,因此,第一根设备根据目标叶子设备对应的ROUTER ID可以确定第一组播加入报文的组播路由信息满足优选条件。When the device route identifier is the ROUTER ID corresponding to the target leaf device, the ROUTER ID corresponding to each target leaf device is different, that is, the different target leaf devices correspond to different ROUTER IDs. Therefore, the first root device corresponds to the target leaf device. The ROUTER ID can determine that the multicast routing information of the first multicast join message satisfies a preferred condition.
当设备路由标识为目标叶子设备优选的第二根设备的ROUTER ID时,第一根设备可以根据第二根设备的ROUTER ID确定优选了第二根设备的目标叶子设备发送的第一组播加入报文的组播路由信息满足优选条件。When the device routing identifier is the ROUTER ID of the second root device of the target leaf device, the first root device may determine, according to the ROUTER ID of the second root device, the first multicast join that is sent by the target leaf device that is preferred to the second root device. The multicast routing information of the packet satisfies the preferred condition.
下面以图4对第一根设备根据目标叶子设备对应的ROUTER ID确定组播路由信息满足优选条件以及以图5对第一根设备根据目标叶子设备优选的第二根设备的ROUTER ID确定组播路由信息满足优选条件,分别进行举例说明:4, the first device determines that the multicast routing information meets the preferred condition according to the ROUTER ID corresponding to the target leaf device, and determines the multicast according to the ROUTER ID of the second device that is preferred by the first root device according to the target leaf device. The routing information satisfies the preferred conditions and is illustrated separately:
需要说明的是,本实施例中,第一根设备仅以图4和图5所示的根设备1以及根设备2进行举例说明,目标叶子设备仅以叶子设备1、叶子设备2以及叶子设备3进行举例说明。It should be noted that, in this embodiment, the first device is only illustrated by the root device 1 and the root device 2 shown in FIG. 4 and FIG. 5, and the target leaf device only uses the leaf device 1, the leaf device 2, and the leaf device. 3 for an example.
目标叶子设备优选的第二根设备为根设备1或根设备2中的任意一个。The preferred second device of the target leaf device is either the root device 1 or the root device 2.
另外,本实施例中,仅以叶子设备1以及叶子设备2优选从根设备1接收组播数据,叶子设备3优选从根设备2接收组播数据为例进行说明。在实际应用中,叶子设备1以及叶子设备2还可以优先从根设备2接收组播数据,叶子设备3还可以优先从根设备1接收组播数据,只要满足存在有不同的叶子设备优选不同的根设备接收组播数据即可,此处不做具体限定。Further, in the present embodiment, it is preferable that only the leaf device 1 and the leaf device 2 receive the multicast data from the root device 1, and the leaf device 3 preferably receives the multicast data from the root device 2 as an example. In actual applications, the leaf device 1 and the leaf device 2 can also receive multicast data from the root device 2 preferentially. The leaf device 3 can also preferentially receive multicast data from the root device 1 as long as the different leaf devices are different. The root device can receive multicast data, which is not specifically limited here.
请参考图4,图4中第一组播加入报文中的组播路由信息包含的设备路由标识为目标叶子设备对应的ROUTER ID。Referring to FIG. 4, the device routing identifier included in the multicast routing information in the first multicast join message in FIG. 4 is the ROUTER ID corresponding to the target leaf device.
具体地,如图4所示,当根设备1接收到叶子设备1、叶子设备2以及叶子设备3分别发送的第一组播加入报文之后,如表3-1所示,每个第一组播加入报文中的组播路由信心中的NLRI信息包含叶子设备对应的ROUTER ID,因为叶子设备1、叶子设备2以及叶子设备3分别对应的ROUTER ID不同,所以根设备1可以根据叶子设备1、叶子设备2以及叶子设备3分别对应的ROUTER ID确定叶子设备1、叶子设备2以及叶子设备3分别发送的第一组播加入报文中的组播路由信息满足优选条件,即如图4所示根设备1的三条组播路由均满足优选条件,当叶子设备1、叶子设备2以及叶子设备3分别发送第一组播加入报文的组播路由信息在根设备1都满足优选条件之后,根设备1分别将叶子设备1、叶子设备2以及叶子设备3所发送第一组播加入报文的组播路由信息进入交叉流程,即将叶子设备1、叶子设备2以及叶子设备3分别优选的根设备对应的根设备信息与根设备1自身的根设备信息进行比较。Specifically, as shown in FIG. 4, after the root device 1 receives the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3, as shown in Table 3-1, each first The NLRI information in the multicast routing confidence in the multicast join message contains the ROUTER ID corresponding to the leaf device. Because the ROUTER ID corresponding to the leaf device 1, the leaf device 2, and the leaf device 3 are different, the root device 1 can be based on the leaf device. 1. The ROUTER ID corresponding to the leaf device 2 and the leaf device 3 respectively determines that the multicast routing information in the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively satisfies a preferred condition, that is, as shown in FIG. 4 The three multicast routes of the root device 1 are all in the preferred condition. After the leaf device 1, the leaf device 2, and the leaf device 3 respectively send the multicast routing information of the first multicast join message, after the root device 1 satisfies the preferred condition, The root device 1 enters the cross-flow process of the multicast routing information of the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3, that is, the leaf device 1 and the leaf device 2 And the root device information corresponding to the preferred root device of the leaf device 3 is compared with the root device information of the root device 1 itself.
同样,图4所示的根设备2接收到叶子设备1、叶子设备2以及叶子设备3分别发送的第一组播加入报文之后,如表3-1所示,第一组播加入报文中的组播路由信息中的NLRI信息包含叶子设备对应的ROUTER ID,因为叶子设备1、叶子设备2以及叶子设备3分别对应的ROUTER ID不同,所以根设备2可以根据叶子设备1、叶子设备2以及叶子设备3分别对应的ROUTER ID确定叶子设备1、叶子设备2以及叶子设备3分别发送的第一组播加入报文中的组播路由信息满足优选条件,即如图4所示根设备2的三条组播路由均满足优选条件, 当叶子设备1、叶子设备2以及叶子设备3发送第一组播加入报文的组播路由在根设备2都满足优选条件之后,根设备2分别将叶子设备1、叶子设备2以及叶子设备3所发送第一组播加入报文的组播路由信息进入交叉流程,即将叶子设备1、叶子设备2以及叶子设备3分别优选的根设备对应的根设备信息与根设备2自身的根设备信息进行比较。Similarly, after the root device 2 shown in FIG. 4 receives the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3, as shown in Table 3-1, the first multicast join message is displayed. The NLRI information in the multicast routing information includes the ROUTER ID corresponding to the leaf device. Because the ROUTER ID corresponding to the leaf device 1, the leaf device 2, and the leaf device 3 are different, the root device 2 can be based on the leaf device 1 and the leaf device 2 And the ROUTER ID corresponding to the leaf device 3 respectively determines that the multicast routing information in the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively meets a preferred condition, that is, the root device 2 is as shown in FIG. The three multicast routes satisfy the preferred condition. After the leaf device 1, the leaf device 2, and the leaf device 3 send the multicast route of the first multicast join message, after the root device 2 satisfies the preferred condition, the root device 2 respectively leaves the leaf. The multicast routing information of the first multicast join message sent by the device 1, the leaf device 2, and the leaf device 3 enters a cross-flow process, that is, the leaf device 1, the leaf device 2, and the leaf device 3 respectively Selected root root device corresponding to the device information of the device 2 itself and a root root device information is compared.
请参考图5,图5中第一组播加入报文中的组播路由信息包含的设备路由标识为目标叶子设备优选的第二根设备的ROUTER ID。Referring to FIG. 5, the device routing identifier included in the multicast routing information in the first multicast join message in FIG. 5 is the ROUTER ID of the second root device preferred by the target leaf device.
具体地,如图5所示,当根设备1接收到叶子设备1、叶子设备2以及叶子设备3分别发送的第一组播加入报文之后,如表3-2所示,第一组播加入报文中的组播路由信息中的NLRI信息包含叶子设备1、叶子设备2和叶子设备3分别优选的根设备对应的ROUTER ID,由于叶子设备1和叶子设备2优选了根设备1,所以叶子设备1和叶子设备2分别发送的组播路由信息携带的ROUTER ID相同,因此根设备1接收叶子设备1和叶子设备2发送的两条组播路由信息,只会将其中一个组播路由信息进入交叉流程,即将进入交叉流程的一个组播路由信息对应的叶子设备所优选的根设备的根设备信息与根设备1对应的根设备信息进行比较。又因为根设备1的ROUTER ID与根设备2的ROUTER ID不同,所以优选了根设备2的叶子设备3发送的组播路由信息在根设备1中会进入交叉流程。因此,如图5所示,根设备1中得到前发两条组播路由信息,分别是优选了根设备1的叶子设备1和叶子设备2发送的两条组播路由信息中的一个,以及优选了根设备2的叶子设备3发送组播路由信息。Specifically, as shown in FIG. 5, after the root device 1 receives the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3, as shown in Table 3-2, the first multicast The NLRI information in the multicast routing information in the join message includes the ROUTER ID corresponding to the preferred root device of the leaf device 1, the leaf device 2, and the leaf device 3 respectively. Since the leaf device 1 and the leaf device 2 preferably have the root device 1, The multicast routing information sent by the leaf device 1 and the leaf device 2 respectively carries the same ROUTER ID. Therefore, the root device 1 receives the two multicast routing information sent by the leaf device 1 and the leaf device 2, and only one of the multicast routing information is sent. The root device information of the preferred root device of the leaf device corresponding to a multicast routing information of the cross-flow process is compared with the root device information corresponding to the root device 1. Since the ROUTER ID of the root device 1 is different from the ROUTER ID of the root device 2, it is preferable that the multicast routing information sent by the leaf device 3 of the root device 2 enters the cross flow in the root device 1. Therefore, as shown in FIG. 5, the root device 1 obtains two pre-sentences of the multicast routing information, which are respectively one of the two multicast routing information sent by the leaf device 1 and the leaf device 2 of the root device 1, and Preferably, the leaf device 3 of the root device 2 transmits multicast routing information.
同样,图5所示的根设备2接收到叶子设备1、叶子设备2以及叶子设备3分别发送的第一组播加入报文之后,如表3-2所示,第一组播加入报文中的组播路由信息中的NLRI信息包含叶子设备1、叶子设备2和叶子设备3分别优选的根设备对应的ROUTER ID,由于叶子设备1和叶子设备2优选了根设备1,所以叶子设备1和叶子设备2分别发送的组播路由信息携带的ROUTER ID相同,因此根设备2接收叶子设备1和叶子设备2发送的两条组播路由信息,只会优选其中一个组播路由信息进入交叉流程,即将进入交叉流程的一个组播路由信息对应的叶子设备所优选的根设备的根设备信息与根设备2对应的根设备信息进行比较。又因为根设备1的ROUTER ID与根设备2的ROUTER ID不同,所以优选了根设备2的叶子设备3发送的组播路由信息在根设备2中进入交叉流程。因此,如图5所示,根设备2中得到前发两条组播路由信息,分别是优选了根设备1的叶子设备1和叶子设备2发送的两条组播路由信息中的一个,以及优选了根设备2的叶子设备3发送组播路由信息。Similarly, after the root device 2 shown in FIG. 5 receives the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3, as shown in Table 3-2, the first multicast join message is displayed. The NLRI information in the multicast routing information includes the ROUTER ID corresponding to the preferred root device of the leaf device 1, the leaf device 2, and the leaf device 3 respectively. Since the leaf device 1 and the leaf device 2 prefer the root device 1, the leaf device 1 The multicast routing information sent by the leaf device 2 is the same as the ROUTER ID. Therefore, the root device 2 receives the two multicast routing information sent by the leaf device 1 and the leaf device 2, and only one of the multicast routing information enters the cross process. The root device information of the preferred root device of the leaf device corresponding to a multicast routing information that is about to enter the cross-flow process is compared with the root device information corresponding to the root device 2. Further, since the ROUTER ID of the root device 1 is different from the ROUTER ID of the root device 2, it is preferable that the multicast routing information transmitted by the leaf device 3 of the root device 2 enters the cross flow in the root device 2. Therefore, as shown in FIG. 5, the root device 2 obtains two pre-sentences of the multicast routing information, which are respectively one of the two multicast routing information sent by the leaf device 1 and the leaf device 2 of the root device 1, and Preferably, the leaf device 3 of the root device 2 transmits multicast routing information.
303、第一根设备确定组播路由信息中包含的第二根设备信息与第一根设备信息是否相同,若相同,则执行步骤304。303. The first device determines whether the second device information included in the multicast routing information is the same as the first device information. If the information is the same, step 304 is performed.
当第一根设备确定第一组播加入报文对应的组播路由信息满足优选条件之后,第一根设备将满足优选条件的组播路由信息中的第二根设备信息与第一根设备对应的第一根设备信息进行比较,需要说明的是,第二根设备信息,例如可以为该组播路由信息中的路由目标(routing target,RT)的输入(import)属性包含的管理字段(administrator field);第一根设备信息,例如可以为第一根设备的MVPN ID,该MVPN ID为第一根设备所维护的MVPN对应的ID,例如表3-3,表3-3为第一根设备所述维护的多个VPN路由表,即VPN路由表1、VPN路由表2以及VPN路由表3,VPN路由表1、VPN路由表2以及VPN路由表3对应的MVPN ID相同,例如在表3-3中,VPN路由表1、VPN路由表2以及VPN路由表3的MVPN ID都为(192.168.110.2)。After the first device determines that the multicast routing information corresponding to the first multicast join message meets the preferred condition, the first root device matches the second root device information in the multicast routing information that meets the preferred condition with the first root device. The first device information is compared. It should be noted that the second device information may be, for example, a management field (administrator) included in an import attribute of a routing target (RT) in the multicast routing information. The first device information, for example, may be the MVPN ID of the first root device, and the MVPN ID is the ID corresponding to the MVPN maintained by the first root device, for example, Table 3-3, and Table 3-3 is the first root. The plurality of VPN routing tables maintained by the device, that is, the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3, the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3 have the same MVPN ID, for example, in the table. In 3-3, the MVPN IDs of VPN routing table 1, VPN routing table 2, and VPN routing table 3 are both (192.168.110.2).
表3-3.VPN路由表Table 3-3. VPN Routing Table
VPN路由表VPN routing table |
VPN路由表1:192.168.110.2:13VPN routing table 1:192.168.110.2:13 |
VPN路由表2:192.168.110.2:10VPN routing table 2: 192.168.110.2:10 |
VPN路由表3:192.168.110.2:05VPN routing table 3: 192.168.110.2:05 |
具体地,第一根设备将第一组播加入报文中的组播路由信息的RT-import属性包含administrator field与第一根设备的MVPN ID进行比较,例如,当组播路由信息中包含的administrator field为<192.168.110.2:13>时,第一根设备将<192.168.110.2:13>中的(192.168.110.2)与表3-3中第一根设备的MVPN ID进行比较,即与表3-3所示的VPN路由表1、VPN路由表2以及VPN路由表3对应的(192.168.110.2)进行比较,如果相同,则表示第一根设备的MVPN ID与组播路由信息中的administrator field相同,然后第一根设备将第一组播加入报文中的组播路由信息添加到VPN路由表中,另外,如果表3-3所示的VPN路由表1、VPN路由表2以及VPN路由表3对应MVPN ID的不是(192.168.110.2),则表示第一组播加入报文对应的组播路由信息不是第一根设备处理的组播路由信息,第一根设备不将第一组播加入报文中的组播路由信息添加到路由表中或者丢弃第一组播加入报文中的组播路由信息等。Specifically, the first device compares the RT-import attribute of the multicast routing information in the first multicast join message with the administrator field and the MVPN ID of the first root device, for example, when the multicast routing information is included. When the administrator field is <192.168.110.2:13>, the first device compares (192.168.110.2) in <192.168.110.2:13> with the MVPN ID of the first device in Table 3-3, that is, the table. 3-3 shows the VPN routing table 1, VPN routing table 2, and VPN routing table 3 corresponding to (192.168.110.2) for comparison. If they are the same, it means the MVPN ID of the first root device and the administrator in the multicast routing information. The field is the same, and then the first device adds the multicast routing information in the first multicast join message to the VPN routing table. In addition, if the VPN routing table 1, VPN routing table 2, and VPN shown in Table 3-3 If the MVPN ID of the routing table 3 is not (192.168.110.2), the multicast routing information corresponding to the first multicast join message is not the multicast routing information processed by the first root device. The first device does not use the first group. Add multicast routing information in the broadcast join message to the routing table. Or discard multicast join a first multicast routing information packets.
需要说明的是,本实施例中,组播路由信息中包含的administrator field为<192.168.110.2:13>仅仅为一个例子,在实际应用中administrator field还可以是其他,此处不做限定。It should be noted that, in this embodiment, the administrator field included in the multicast routing information is <192.168.110.2:13>, which is only an example. In the actual application, the administrator field may be other, which is not limited herein.
下面分别参以图4和图5中的根设备1和根设备2的处理流程进行详细描述:The following is a detailed description of the processing flow of the root device 1 and the root device 2 in FIG. 4 and FIG. 5 respectively:
请参考图4,根设备1确定叶子设备1、叶子设备2以及叶子设备3分别发送的组播路由信息满足优选条件之后,根设备1分别将叶子设备1、叶子设备2以及叶子设备3分别发送第一组播加入报文中的组播路由信息的RT-import属性包含的Administrator field与根设备1的MVPN ID进行比较,如果两者相同,则根设备1将第一组播加入报文中的组播路由信息添加到根设备1的VPN路由表中。具体地,由于叶子设备1以及叶子设备2优选从根设备1接收组播数据,所以叶子设备1和叶子设备2分别发送的第一组播加入报文中的组播路由信息的RT-import属性包含的Administrator field与根设备1的MVPN ID相同,所以根设备1将叶子设备1和叶子设备2分别发送的第一组播加入报文组播路由信息添加到根设备1的VPN路由表中,但是,叶子设备3优选了根设备2,所以叶子设备3向根设备1发送第一组播加入报文中的组播路由信息的RT-import属性包含的Administrator field与根设备1的MVPN ID不相同,则根设备1丢弃叶子设备3发送第一组播加入报文中的组播路由信息。Referring to FIG. 4, after the root device 1 determines that the multicast routing information sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively satisfies the preferred condition, the root device 1 respectively sends the leaf device 1, the leaf device 2, and the leaf device 3 respectively. The administrator field of the RT-import attribute of the multicast routing information in the first multicast join message is compared with the MVPN ID of the root device 1. If the two are the same, the root device 1 adds the first multicast to the packet. The multicast routing information is added to the VPN routing table of the root device 1. Specifically, since the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute of the multicast routing information in the first multicast join message sent by the leaf device 1 and the leaf device 2 respectively The administrator field is the same as the MVPN ID of the root device 1. The root device 1 adds the multicast routing information of the first multicast join message sent by the leaf device 1 and the leaf device 2 to the VPN routing table of the root device 1. However, the leaf device 3 is preferably the root device 2, so the leaf device 3 sends the multicast field included in the RT-import attribute of the multicast routing information in the first multicast join message to the root device 1 and the MVPN ID of the root device 1 is not If the same, the root device 1 discards the multicast routing information in the first multicast join message.
同样,图4所示的根设备2确定叶子设备1、叶子设备2以及叶子设备3分别发送的组播路由信息满足优选条件之后,根设备2分别将叶子设备1、叶子设备2以及叶子设备3分别发送第一组播加入报文中的组播路由信息的RT-import属性包含的Administrator field与根设备2的MVPN ID进行比较,如果两者相同,则根设备2第一组播加入报文中的该组播路由信息添加到根设备2的VPN路由表中。由于叶子设备3优选了根设备2,所以叶子设备3向根设备2发送第一组播加入报文中的组播路由信息的RT-import属性包含的Administrator field与根设备2的MVPN ID相同,所以根设备2将叶子设备3发送的第一组播加入报文中的组播路由信息添加到根设备2的VPN路由表中。但是,叶子设备1以及叶子设备2优选从根设备1接收组播数据,所以叶子设备1和叶子设备2分别发送的第一组播 加入报文中的组播路由信息的RT-import属性包含的Administrator field与根设备2的MVPN ID不相同,因此,根设备2将叶子设备1和叶子设备2分别发送的第一组播加入报文中的组播路由信息丢弃。Similarly, after the root device 2 shown in FIG. 4 determines that the multicast routing information sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively satisfies the preferred condition, the root device 2 respectively sets the leaf device 1, the leaf device 2, and the leaf device 3. The administrator field of the RT-import attribute of the multicast routing information in the first multicast join message is compared with the MVPN ID of the root device 2. If the two are the same, the root device 2 joins the first multicast join message. The multicast routing information in the multicast routing information is added to the VPN routing table of the root device 2. Since the leaf device 3 is preferably the root device 2, the leaf device 3 sends the multicast routing information in the first multicast join message to the root device 2, and the Administrator field contained in the RT-import attribute is the same as the MVPN ID of the root device 2. Therefore, the root device 2 adds the multicast routing information in the first multicast join message sent by the leaf device 3 to the VPN routing table of the root device 2. However, the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, so the RT-import attribute of the multicast routing information in the first multicast join message sent by the leaf device 1 and the leaf device 2 respectively is included. The administrator field is different from the MVPN ID of the root device 2. Therefore, the root device 2 discards the multicast routing information in the first multicast join message sent by the leaf device 1 and the leaf device 2 respectively.
请参考图5,图5所示的根设备1确定叶子设备1和叶子设备2分别发送的组播路由信息其中的一个,以及叶子设备3发送的组播路由信息进入交叉流程,根设备1分别将叶子设备1和叶子设备2对应的一个组播路由信息,以及叶子设备3对应的组播路由信息中的RT-import属性包含的Administrator field与根设备1的MVPN ID进行比较,如果两者相同,则根设备1将第一组播加入报文中的组播路由信息添加到根设备1的VPN路由表中。具体地,由于叶子设备1以及叶子设备2优选从根设备1接收组播数据,所以叶子设备1和叶子设备2对应的一个组播路由信息中的RT-import属性包含的Administrator field与根设备1的MVPN ID相同,所以根设备1将叶子设备1和叶子设备2对应的一个组播路由信息添加到根设备1的VPN路由表中,但是,叶子设备3优选了根设备2,所以叶子设备3向根设备1发送的组播路由信息中RT-import属性包含的Administrator field与根设备1的MVPN ID不相同,则根设备1丢弃叶子设备3发送的第一组播加入报文中的组播路由信息。Referring to FIG. 5, the root device 1 shown in FIG. 5 determines one of the multicast routing information sent by the leaf device 1 and the leaf device 2, and the multicast routing information sent by the leaf device 3 enters a crossover process, and the root device 1 respectively Comparing one multicast routing information corresponding to the leaf device 1 and the leaf device 2, and the Administrator field included in the RT-import attribute in the multicast routing information corresponding to the leaf device 3 to the MVPN ID of the root device 1, if the two are the same The root device 1 adds the multicast routing information in the first multicast join message to the VPN routing table of the root device 1. Specifically, since the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the root device 1 The MVPN ID is the same, so the root device 1 adds a multicast routing information corresponding to the leaf device 1 and the leaf device 2 to the VPN routing table of the root device 1. However, the leaf device 3 preferably has the root device 2, so the leaf device 3 The multicast field information sent to the root device 1 is different from the MVPN ID of the root device 1 in the RT-import attribute. The root device 1 discards the multicast in the first multicast join message sent by the leaf device 3. Routing information.
同样,图5所示的根设备2确定叶子设备1和叶子设备2分别发送的组播路由信息其中的一个,以及叶子设备3发送的组播路由信息进入交叉流程,根设备2分别将叶子设备1和叶子设备2对应的一个组播路由信息,以及叶子设备3对应的组播路由信息中的RT-import属性包含的Administrator field与根设备2的MVPN ID进行比较,如果两者相同,则根设备2将第一组播加入报文中的组播路由信息添加到根设备2的VPN路由表中。具体地,由于叶子设备1以及叶子设备2优选从根设备1接收组播数据,所以叶子设备1和叶子设备2对应的一个组播路由信息中的RT-import属性包含的Administrator field与根设备2的MVPN ID不相同,所以根设备2丢弃叶子设备1和叶子设备2对应的一个组播路由信息。叶子设备3优选了根设备2,所以叶子设备3向根设备2发送的组播路由信息中RT-import属性包含的Administrator field与根设备2的MVPN ID相同,则根设备2将叶子设备3发送的第一组播加入报文中的组播路由信息添加到根设备2的VPN路由表中。Similarly, the root device 2 shown in FIG. 5 determines one of the multicast routing information sent by the leaf device 1 and the leaf device 2, and the multicast routing information sent by the leaf device 3 enters the cross process, and the root device 2 respectively sets the leaf device. 1: A multicast routing information corresponding to the leaf device 2, and an LDAP field included in the RT-import attribute in the multicast routing information corresponding to the leaf device 3 is compared with the MVPN ID of the root device 2, if the two are the same, the root The device 2 adds the multicast routing information in the first multicast join message to the VPN routing table of the root device 2. Specifically, since the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the root device 2 The MVPN IDs are different, so the root device 2 discards one multicast routing information corresponding to the leaf device 1 and the leaf device 2. The leaf device 3 is preferably the root device 2, so the RR-import attribute of the multicast routing information sent by the leaf device 3 to the root device 2 is the same as the MVPN ID of the root device 2, and the root device 2 sends the leaf device 3 The multicast routing information in the first multicast join message is added to the VPN routing table of the root device 2.
304、第一根设备根据组播路由信息的VPN实例标识将目标叶子设备的组播路由信息添加到目标路由表中。304. The first device adds the multicast routing information of the target leaf device to the target routing table according to the VPN instance identifier of the multicast routing information.
每个第一组播加入报文中对应的组播路由信息中包含VPN实例标识,该VPN实例标识用于表征该组播路由信息对应的路由表。The corresponding multicast routing information in the first multicast join message includes a VPN instance identifier, where the VPN instance identifier is used to represent a routing table corresponding to the multicast routing information.
由于第一根设备维护一个或多个VPN路由表,当有组播路由信息需要加入VPN路由表时,第一根设备需要根据组播路由信息中的VPN实例标识与本地的VPN路由表中每个VPN路由表的标志(index)进行匹配,需要说明的是第一根设备中的每个VPN路由表都包含其相对应的index,不同的index用于区分表征不同VPN路由表,具体地,第一根设备根据administrator field包含的<192.168.110.2:13>中的确定该组播路由信息包含的VPN实例标识为13,则第一根设备将该VPN实例标识13与表3-3中的VPN路由表1、VPN路由表2以及VPN路由表3分别对应的index进行匹配,如果存在index为13的VPN路由表,则第一根设备将index为13的VPN路由表确定为目标路由表,例如表3-3中VPN路由表1对应的index为13,则第一根设备将VPN路由表1确定为目标路由表,并将该组播路由信息添加到VPN路由表1中,例如,将该组播路由信息包含的NLRI信息中的始发路由器IP地址(Originating route’s IP address)和组播源(Multicast source)添加到VPN路由表1对 应的表项中,需要说明的是,本实施例中第一根设备还可以将组播路由信息中其他的信息添加到VPN路由表1,如设备的出入接口等信息添加到VPN路由表1中。若组播路由表中不存在index为13的路由表,则第一根设备将该组播路由信息丢弃。Since the first device maintains one or more VPN routing tables, when the multicast routing information needs to be added to the VPN routing table, the first root device needs to use the VPN instance identifier in the multicast routing information and the local VPN routing table. The index of the VPN routing table is matched. It should be noted that each VPN routing table in the first root device includes its corresponding index. Different indexes are used to distinguish different VPN routing tables. Specifically, The first device determines that the VPN instance ID of the multicast routing information is 13 according to the <192.168.110.2:13> included in the administrator field, and the first root device identifies the VPN instance identifier 13 and Table 3-3. The index corresponding to the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3 are matched. If there is a VPN routing table with an index of 13, the first device determines the VPN routing table with index 13 as the target routing table. For example, if the index corresponding to the VPN routing table 1 in Table 3-3 is 13, the first device determines the VPN routing table 1 as the target routing table, and adds the multicast routing information to the VPN routing table 1, for example, The multicast routing information is included The originating route's IP address and the multicast source in the NLRI information are added to the entry corresponding to the VPN routing table 1. It should be noted that the first device in this embodiment may also be used. The other information in the multicast routing information is added to the VPN routing table 1. The information such as the inbound and outbound interfaces of the device is added to the VPN routing table 1. If the routing table with index 13 is not in the multicast routing table, the first device discards the multicast routing information.
305、第一根设备向目标叶子设备发送组播数据。305. The first root device sends multicast data to the target leaf device.
在组播源向第一根设备下发组播数据时,第一根设备则根据目标路由表中的信息向目标叶子设备发送该组播数据。When the multicast source sends multicast data to the first root device, the first device sends the multicast data to the target leaf device according to the information in the target routing table.
需要说明的是,本实施例中,第一根设备向目标叶子设备发送组播数据之前,第一根设备可以向目标叶子设备发送第一组播数据接收消息,目标叶子接收到第一组播数据接收消息之后,向第一根设备发送第一组播数据接收响应消息,然后第一根设备向发送了第一组播数据接收响应消息的目标叶子设备发送组播数据;此外,第一根设也可以不向目标叶子设备发送第一组播数据接收消息,直接根据目标路由表中的信息向目标叶子设备发送该组播数据,此处不做具体限定。It should be noted that, in this embodiment, before the first device sends the multicast data to the target leaf device, the first device may send the first multicast data receiving message to the target leaf device, and the target leaf receives the first multicast. After receiving the message, the first multicast data receiving response message is sent to the first root device, and then the first root device sends the multicast data to the target leaf device that sends the first multicast data receiving response message; It is not necessary to send the first multicast data receiving message to the target leaf device, and directly send the multicast data to the target leaf device according to the information in the target routing table, which is not specifically limited herein.
下面分别以图4和图5中所示的应用场景进行举例说明:The following is an example of the application scenarios shown in FIG. 4 and FIG. 5:
如图4所示,叶子设备1以及叶子设备2优选了是根设备1接收组播数据,所以根设备1根据目标路由表中的信息分别向叶子设备1以及叶子设备2发送组播数据。叶子设备3优选根设备2接收组播数据,所以根设备2根据目标路由表中的信息向叶子设备3发送组播数据。As shown in FIG. 4, the leaf device 1 and the leaf device 2 preferably receive the multicast data by the root device 1, so the root device 1 transmits the multicast data to the leaf device 1 and the leaf device 2, respectively, according to the information in the target routing table. The leaf device 3 preferably receives the multicast data by the root device 2, so the root device 2 transmits the multicast data to the leaf device 3 according to the information in the target routing table.
如图5所示,叶子设备1以及叶子设备2优选了根设备1接收组播数据,由于叶子设备1以及叶子设备2分别发送的第一组播加入报文在根设备1中只有其中一个第一组播加入报文进入交叉流程,所以根设备1向叶子设备1以及叶子设备2发送组播数据之前,根设备1向叶子设备1以及叶子设备2发送组播数据接收消息,当叶子设备1以及叶子设备2向根设备1发送组播数据接收响应消息之后,根设备1向叶子设备1以及叶子设备2发送组播数据。由于叶子设备3优选根设备2接收组播数据,所以根设备2根据目标路由表向叶子设备3发送组播数据。As shown in FIG. 5, the leaf device 1 and the leaf device 2 preferably receive the multicast data by the root device 1. The first multicast join message sent by the leaf device 1 and the leaf device 2 is only one of the root device 1 in the root device 1. A multicast join message enters the cross-flow process. Before the root device 1 sends the multicast data to the leaf device 1 and the leaf device 2, the root device 1 sends a multicast data reception message to the leaf device 1 and the leaf device 2, and when the leaf device 1 After the leaf device 2 transmits the multicast data reception response message to the root device 1, the root device 1 transmits the multicast data to the leaf device 1 and the leaf device 2. Since the leaf device 3 preferably receives the multicast data, the root device 2 transmits the multicast data to the leaf device 3 according to the target routing table.
本实施例中,目标叶子设备向第一根设备发送第一组播加入报文,第一组播加入报文中包含组播路由信息,组播路由信息的NLRI信息包含设备路由标识,当第一根设备接收到第一组播加入报文之后,第一根设备可以根据组播路由信息的NLRI信息包含的设备路由标识确定组播路由信息满足优选条件,当第一该组播路由信息的RT-import属性包含Administrator field与第一根设备本身的MVPN ID相同,则第一根设备将该组播路由信息添加到对应的VPN路由表中,在有组播数据下发时,第一根设备根据VPN路由表向目标叶子设备发送组播数据,因此,本实施例中,不同的目标叶子设备在优选了不同的根设备的情况下,第一根设备根据目标叶子设备发送的组播路由信息的设备路由标识确保每个目标叶子设备发送组播路由信息得到优选,在组播数据下发时,使得优选了不同根设备的目标叶子设备都会收到组播数据。In this embodiment, the target leaf device sends a first multicast join message to the first root device, where the first multicast join message includes multicast routing information, and the NLRI information of the multicast routing information includes the device route identifier. After receiving the first multicast join message, the first device may determine that the multicast routing information meets the preferred condition according to the device routing identifier included in the NLRI information of the multicast routing information, when the first multicast routing information is used. The RT-import attribute contains the same MVPN ID of the first device. The first device adds the multicast routing information to the corresponding VPN routing table. When multicast data is delivered, the first one is generated. The device sends the multicast data to the target leaf device according to the VPN routing table. Therefore, in this embodiment, when the different target leaf devices prefer different root devices, the first root device sends the multicast route according to the target leaf device. The device routing identifier of the information ensures that each target leaf device sends multicast routing information to be optimized. When the multicast data is sent, the different root settings are preferred. Target leaves the device will receive the multicast data.
二、第一根设备接收RR发送的第二组播加入报文。The first device receives the second multicast join message sent by the RR.
请参考图6,本申请实施例中组播路由处理方法的另一个实施例,包括:Referring to FIG. 6, another embodiment of a multicast routing processing method in this embodiment of the present application includes:
601、目标叶子设备向RR发送第一组播加入报文。601. The target leaf device sends a first multicast join message to the RR.
当MVPN中的目标叶子设备需要接收组播数据时,目标叶子设备向RR发送的第一组播加入报文,第一组播加入报文用于指示目标叶子设备需要加入MVPN,接收组播数据。其中, 第一组播加入报文包括组播路由信息,组播路由信息包含NLRI信息,该NLRI信息中包含设备路由标识,该设备路由标识用于标识该目标叶子设备发送的第一组播加入报文。When the target leaf device in the MVPN needs to receive the multicast data, the target leaf device adds the first multicast join message to the RR, and the first multicast join message is used to indicate that the target leaf device needs to join the MVPN and receive the multicast data. . The first multicast join message includes multicast routing information, and the multicast routing information includes NLRI information, where the NLRI information includes a device routing identifier, where the device routing identifier is used to identify the first multicast join sent by the target leaf device. Message.
需要说明的是,本实施例中设备路由标识可以是目标叶子设备对应ROUTER ID,也可以是目标叶子设备优选的第二根设备的ROUTER ID,具体请参考表3-1,以及表3-2。It should be noted that, in this embodiment, the device routing identifier may be a ROUTER ID corresponding to the target leaf device, or a ROUTER ID of the second device preferred by the target leaf device. For details, refer to Table 3-1 and Table 3-2. .
602、RR根据设备路由标识确定第一组播加入报文满足前发条件。602. The RR determines, according to the device routing identifier, that the first multicast join message meets the pre-condition.
RR接收到第一组播加入报文之后,第一组播加入报文包含组播路由信息,组播路由信息中的NLRI信息包含设备路由标识,设备路由标识可以是目标叶子设备对应的ROUTER ID,也可以是目标叶子设备优选的第二根设备的ROUTER ID。After receiving the first multicast join message, the first multicast join message includes the multicast routing information. The NLRI information in the multicast routing information includes the device route identifier. The device route identifier can be the ROUTER ID corresponding to the target leaf device. It can also be the ROUTER ID of the second device preferred by the target leaf device.
当设备路由标识为目标叶子设备对应的ROUTER ID,由于每个目标叶子设备对应的ROUTER ID是不同的,即不同的目标叶子设备对应不同的ROUTER ID,因此,RR根据目标叶子设备对应的ROUTER ID可以确定第一组播加入报文的组播路由信息满足前发条件。When the device route identifier is the ROUTER ID corresponding to the target leaf device, the ROUTER ID corresponding to each target leaf device is different, that is, the different target leaf devices correspond to different ROUTER IDs. Therefore, the RR is based on the ROUTER ID corresponding to the target leaf device. The multicast routing information of the first multicast join message can be determined to meet the pre-condition.
当设备路由标识为目标叶子设备优选的第二根设备的ROUTER ID时,RR根据第二根设备的ROUTER ID确定优选了第二根设备的目标叶子设备发送的第一组播加入报文的组播路由信息满足前发条件。具体地,如图8所示的场景,图8中叶子设备1和叶子设备2优选了根设备1,叶子设备3优选了根设备2,RR根据叶子设备1和叶子设备2分别发送的第一组播加入报文中包含的根设备1的ROUTER ID确定叶子设备1和叶子设备2分别发送的第一组播加入报文满足前发条件,另外,RR根据叶子设备3优选的根设备2的ROUTER ID确定叶子设备3发送的第一组播加入报文满足前发条件。When the device route identifier is the ROUTER ID of the second device that is the preferred one of the target device, the RR determines, according to the ROUTER ID of the second device, the group of the first multicast join message that is sent by the target leaf device of the second device. The broadcast routing information satisfies the pre-conditions. Specifically, as shown in FIG. 8, the leaf device 1 and the leaf device 2 in FIG. 8 preferably have a root device 1, the leaf device 3 preferably has a root device 2, and the RR transmits the first according to the leaf device 1 and the leaf device 2, respectively. The ROUTER ID of the root device 1 included in the multicast join message determines that the first multicast join message sent by the leaf device 1 and the leaf device 2 respectively meets the pre-conditions, and the RR is based on the preferred root device 2 of the leaf device 3. The ROUTER ID determines that the first multicast join message sent by the leaf device 3 satisfies the pre-condition.
603、RR向第一根设备发送第二组播加入报文。603. The RR sends a second multicast join message to the first root device.
由于目标叶子设备发送的第一组播加入报文满足前发条件,所以RR向MVPN中的第一根设备发送第二组播加入报文,第一组播加入报文与第一组播加入报文所包含的组播路由信息相同。The first multicast join message sent by the target leaf device meets the pre-condition, so the RR sends the second multicast join message to the first device in the MVPN, and the first multicast join message joins the first multicast join message. The multicast routing information contained in the packet is the same.
当设备路由标识为目标叶子设备对应的ROUTER ID,由于不同的目标叶子设备对应不同的ROUTER ID,因此本实施中,每个目标叶子设备发送的第一组播加入报文中的组播路由信息对应的ROUTER ID都不同,所以每个目标叶子设备分别发送的第一组播加入报文在RR中都会前发,则RR向第一根设备发送的第二组播加入报文为每个目标叶子设备分别发送的第一组播加入报文。When the device route identifier is the ROUTER ID corresponding to the target leaf device, the multicast routing information in the first multicast join message sent by each target leaf device in this implementation is different because the different target leaf devices correspond to different ROUTER IDs. The corresponding ROUTER IDs are different. Therefore, the first multicast join message sent by each target leaf device is sent in the RR. The second multicast join message sent by the RR to the first root device is used for each target. The first multicast join message sent by the leaf device.
当设备路由标识为目标叶子设备优选的第二根设备的ROUTER ID时,当存在多个目标叶子设备优选同一第二根设备时,优选了同一第二根设备的目标叶子设备发送的组播路由信息在RR中前发其中一个,即当设备路由标识为目标叶子设备优选的第二根设备的ROUTER ID时,RR根据边界网关协议(border gateway protocol,BGP)中的信息向第一根设备发送的第二组播加入报文为满足前发条件的第一组播加入报文中的一个,需要说明的是该BGP为运行于传输控制协议(transmission control protocol,TCP)上的一种自治系统的路由协议。When the device route identifier is the ROUTER ID of the second device of the target leaf device, when there are multiple target leaf devices, preferably the same second root device, the multicast route sent by the target leaf device of the same second root device is preferred. The information is forwarded in the RR. When the device route identifier is the ROUTER ID of the second device that is preferred by the target leaf device, the RR sends the information to the first device according to the information in the border gateway protocol (BGP). The second multicast join message is one of the first multicast join messages that meet the pre-conditions. It should be noted that the BGP is an autonomous system running on a transmission control protocol (TCP). Routing protocol.
下面分别以图7和图8对RR向第一根设备发送第二组播加入报文进行举例说明:The following is an example of sending a second multicast join message to the first device by using the RR in FIG. 7 and FIG. 8 respectively:
需要说明的是,本实施例中,对于RR,仅以图7和图8所示的RR进行举例说明,目标叶子设备仅以叶子设备1、叶子设备2以及叶子设备3进行举例说明。It should be noted that, in the embodiment, only the RRs shown in FIG. 7 and FIG. 8 are used for the RR, and the target leaf device is only exemplified by the leaf device 1, the leaf device 2, and the leaf device 3.
目标叶子设备优选的第二根设备为根设备1或根设备2中的任意一个。The preferred second device of the target leaf device is either the root device 1 or the root device 2.
另外,本实施例中,仅以叶子设备1以及叶子设备2优选从根设备1接收组播数据,叶子设备3优选从根设备2接收组播数据为例进行说明。在实际应用中,叶子设备1以及叶子 设备2还可以优先从根设备2接收组播数据,叶子设备3还可以优先从根设备1接收组播数据,只要满足存在有不同的叶子设备优选不同的根设备接收组播数据即可,此处不做具体限定。Further, in the present embodiment, it is preferable that only the leaf device 1 and the leaf device 2 receive the multicast data from the root device 1, and the leaf device 3 preferably receives the multicast data from the root device 2 as an example. In actual applications, the leaf device 1 and the leaf device 2 can also receive multicast data from the root device 2 preferentially. The leaf device 3 can also preferentially receive multicast data from the root device 1 as long as the different leaf devices are different. The root device can receive multicast data, which is not specifically limited here.
请参考图7,图7所示的应用场景示意图对应的设备路由标识为目标叶子设备对应的ROUTER ID。Referring to FIG. 7, the device routing identifier corresponding to the application scenario diagram shown in FIG. 7 is the ROUTER ID corresponding to the target leaf device.
如图7所示,当RR接收到叶子设备1、叶子设备2以及叶子设备3分别发送的第一组播加入报文之后,如表3-1所示,第一组播加入报文中的组播路由信息的NLRI信息包含目标叶子设备对应的ROUTER ID,叶子设备1、叶子设备2以及叶子设备3分别对应的ROUTER ID不同,则RR根据叶子设备1、叶子设备2以及叶子设备3分别对应的ROUTER ID确定叶子设备1、叶子设备2以及叶子设备3分别发送的第一组播加入报文中的组播路由信息满足前发条件。RR分别向根设备1以及根设备2发送的第二组播加入报文为叶子设备1、叶子设备2以及叶子设备3分别发送的第一组播加入报文。As shown in FIG. 7, after the RR receives the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3, as shown in Table 3-1, the first multicast join message is included. The NLRI information of the multicast routing information includes the ROUTER ID corresponding to the target leaf device. The corresponding ROUTER IDs of the leaf device 1, the leaf device 2, and the leaf device 3 are different, and the RR corresponds to the leaf device 1, the leaf device 2, and the leaf device 3 respectively. The ROUTER ID determines that the multicast routing information in the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively meets the pre-condition. The second multicast join message sent by the RR to the root device 1 and the root device 2 is the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3 respectively.
请参考图8,图8所示的应用场景示意图对应的设备路由标识为目标叶子设备优选的第二根设备的ROUTER ID。Referring to FIG. 8, the device routing identifier corresponding to the application scenario diagram shown in FIG. 8 is the ROUTER ID of the second root device preferred by the target leaf device.
如图8所示,当RR接收到叶子设备1、叶子设备2以及叶子设备3分别发送的第一组播加入报文之后,如表3-2所示,第一组播加入报文中的组播路由信息的NLRI信息包含叶子设备优选的第二根设备对应的ROUTER ID,由于叶子设备1和叶子设备2都是优选了根设备1,所以叶子设备1和叶子设备2分别对应的组播路由信息携带的ROUTER ID相同,因此RR接收叶子设备1和叶子设备2发送的两条第一组播加入报文,只有其中一个第一组播加入报文得到前发。另外,根设备1的ROUTER ID与根设备2的ROUTER ID不同,所以优选了根设备2的叶子设备3发送的第一组播加入报文在RR中同样得到前发。如图8所示,RR中有两条第一组播加入报文得到前发,分别是优选了根设备1的叶子设备1和叶子设备2分别发送的两条第一组播加入报文其中的一个,以及优选了根设备2的叶子设备3发送第一组播加入报文。因此,图8所示的RR向根设备1以及根设备2分别发送的第二组播加入报文分别是叶子设备1和叶子设备2分别发送的第一组播加入报文其中的一个,以及叶子设备3发送的第一组播加入报文。As shown in Figure 8, after the RR receives the first multicast join message sent by the leaf device 1, the leaf device 2, and the leaf device 3, as shown in Table 3-2, the first multicast join message is included. The NLRI information of the multicast routing information includes the ROUTER ID corresponding to the second root device preferred by the leaf device. Since both the leaf device 1 and the leaf device 2 are preferably the root device 1, the leaf device 1 and the leaf device 2 respectively correspond to the multicast. The routing information carries the same ROUTER ID. Therefore, the RR receives the two first multicast join messages sent by the leaf device 1 and the leaf device 2, and only one of the first multicast join messages is sent. In addition, the ROUTER ID of the root device 1 is different from the ROUTER ID of the root device 2. Therefore, it is preferred that the first multicast join message sent by the leaf device 3 of the root device 2 is also forwarded in the RR. As shown in FIG. 8, two first multicast join messages are sent in the RR, and two first multicast join messages respectively sent by the leaf device 1 and the leaf device 2 of the root device 1 are respectively selected. One, and preferably the leaf device 3 of the root device 2 sends a first multicast join message. Therefore, the second multicast join message sent by the RR to the root device 1 and the root device 2 is one of the first multicast join messages respectively sent by the leaf device 1 and the leaf device 2, and The first multicast join message sent by the leaf device 3.
604、第一根设备根据设备路由标识确定组播路由信息满足优选条件。604. The first root device determines, according to the device routing identifier, that the multicast routing information meets a preferred condition.
第一根设备接收到RR发送的第二组播加入报文之后,第二组播加入报文包含组播路由信息,组播路由信息的NLRI信息包含设备路由标识,设备路由标识可以是目标叶子设备对应的ROUTER ID,也可以是目标叶子设备优选的第二根设备的ROUTER ID。After the first device receives the second multicast join message sent by the RR, the second multicast join message includes the multicast routing information, and the NLRI information of the multicast routing information includes the device route identifier, and the device route identifier may be the target leaf. The ROUTER ID corresponding to the device may also be the ROUTER ID of the second device preferred by the target leaf device.
当设备路由标识为目标叶子设备对应的ROUTER ID,由于每个目标叶子设备对应的ROUTER ID是不同的,即不同的目标叶子设备对应不同的ROUTER ID,因此,第一根设备根据目标叶子设备对应的ROUTER ID可以确定第二组播加入报文的组播路由信息满足优选条件。When the device route identifier is the ROUTER ID corresponding to the target leaf device, the ROUTER ID corresponding to each target leaf device is different, that is, the different target leaf devices correspond to different ROUTER IDs. Therefore, the first root device corresponds to the target leaf device. The ROUTER ID can determine that the multicast routing information of the second multicast join message satisfies a preferred condition.
当设备路由标识为目标叶子设备优选的第二根设备的ROUTER ID时,不同的第二根设备对应不同的ROUTER ID,因此,第一根设备根据第二根设备的ROUTER ID确定优选了第二根设备的目标叶子设备发送的第二组播加入报文的组播路由满足优选条件。When the device routing identifier is the ROUTER ID of the second root device of the target leaf device, the second device corresponds to a different ROUTER ID. Therefore, the first device determines the second device according to the ROUTER ID of the second device. The multicast route of the second multicast join message sent by the target leaf device of the root device satisfies the preferred condition.
下面以图7对第一根设备根据目标叶子设备对应的ROUTER ID确定组播路由信息满足优选条件以及以图8对第一根设备根据目标叶子设备优选的第二根设备的ROUTER ID确定组播路由信息满足优选条件,分别进行举例说明:7 is used to determine that the first root device determines the multicast routing information according to the ROUTER ID corresponding to the target leaf device, and determines the multicast condition according to the ROUTER ID of the second device that is preferred by the first root device according to the target leaf device. The routing information satisfies the preferred conditions and is illustrated separately:
请参考图7,图7所示的应用场景示意图对应的设备路由标识为目标叶子设备对应的ROUTER ID。Referring to FIG. 7, the device routing identifier corresponding to the application scenario diagram shown in FIG. 7 is the ROUTER ID corresponding to the target leaf device.
如图7所示,当根设备1接收到RR发送的叶子设备1、叶子设备2以及叶子设备3分别对应第一组播加入报文之后,如表3-1所示,第一组播加入报文中的组播路由信息中的NLRI信息包含叶子设备对应的ROUTER ID,叶子设备1、叶子设备2以及叶子设备3分别对应的ROUTER ID不同,所以根设备1根据叶子设备1、叶子设备2以及叶子设备3分别对应的ROUTER ID确定RR发送的叶子设备1、叶子设备2以及叶子设备3对应第一组播加入报文的组播路由信息满足优选条件,根设备1将叶子设备1、叶子设备2以及叶子设备3分别对应的第一组播加入报文的组播路由信息进入交叉流程,即将叶子设备1、叶子设备2以及叶子设备3分别优选的根设备对应的根设备信息与根设备1自身的根设备信息进行比较。As shown in FIG. 7, after the root device 1 receives the leaf device 1, the leaf device 2, and the leaf device 3 that are sent by the RR, respectively, corresponding to the first multicast join message, as shown in Table 3-1, the first multicast joins. The NLRI information in the multicast routing information of the packet includes the ROUTER ID corresponding to the leaf device. The ROUTER ID corresponding to the leaf device 1, the leaf device 2, and the leaf device 3 are different, so the root device 1 is based on the leaf device 1 and the leaf device 2 And the ROUTER ID corresponding to the leaf device 3 respectively determines that the multicast routing information corresponding to the first multicast join message of the leaf device 1, the leaf device 2, and the leaf device 3 sent by the RR meets a preferred condition, and the root device 1 sets the leaf device 1 and the leaf. The multicast routing information of the first multicast join message corresponding to the device 2 and the leaf device 3 respectively enters a cross-flow process, that is, the root device information and the root device corresponding to the preferred root device of the leaf device 1, the leaf device 2, and the leaf device 3 respectively 1 Compare their own root device information.
同样,如图7所示,根设备2执行的流程与前述图7根设备1所执行的流程类似,此处不再赘述。Similarly, as shown in FIG. 7, the process performed by the root device 2 is similar to the process performed by the root device 1 of FIG. 7, and details are not described herein again.
请参考图8,图8所示的应用场景示意图对应的设备路由标识为目标叶子设备优选的第二根设备的ROUTER ID。Referring to FIG. 8, the device routing identifier corresponding to the application scenario diagram shown in FIG. 8 is the ROUTER ID of the second root device preferred by the target leaf device.
如图8所示,根设备1接收到RR发送叶子设备1和叶子设备2分别对应的第一组播加入报文其中的一个以及叶子设备3对应的第一组播加入报文,如表3-2所示,组播路由信息的NLRI信息包含根设备对应的ROUTER ID,由于根设备1与根设备2对应的ROUTER ID不同,所以优选了根设备1的叶子设备1以及叶子设备2对应的其中一个组播路由信息在根设备1中满足优选条件,优选了根设备2的叶子设备3对应的组播路由信息在根设备1中同样满足优选条件。As shown in FIG. 8, the root device 1 receives one of the first multicast join messages corresponding to the leaf device 1 and the leaf device 2, and the first multicast join message corresponding to the leaf device 3, as shown in Table 3. As shown in FIG. 2, the NLRI information of the multicast routing information includes the ROUTER ID corresponding to the root device. Since the root device 1 and the root device 2 have different ROUTER IDs, the leaf device 1 and the leaf device 2 of the root device 1 are preferred. One of the multicast routing information meets the preferred conditions in the root device 1. Preferably, the multicast routing information corresponding to the leaf device 3 of the root device 2 also satisfies the preferred condition in the root device 1.
同样,如图8所示,根设备2执行的流程与前述图8根设备1所执行的流程类似,此处不再赘述。Similarly, as shown in FIG. 8, the process performed by the root device 2 is similar to the process performed by the root device 1 of FIG. 8 and will not be described herein.
605、第一根设备确定组播路由信息包含的第二根设备信息与第一根设备信息是否相同,若是,则执行步骤606。605. The first device determines whether the second device information included in the multicast routing information is the same as the first device information. If yes, step 606 is performed.
当第一根设备确定第二组播加入报文对应的组播路由信息满足优选条件之后,第一根设备将满足优选条件的组播路由信息中的第二根设备信息与第一根设备对应的第一根设备信息进行比较,需要说明的是,第二根设备信息,例如可以为该组播路由信息中的路由目标(routing target,RT)的输入(import)属性包含的管理字段(administrator field);第一根设备信息,例如可以为第一根设备的MVPN ID,该MVPN ID为第一根设备所维护的MVPN对应的ID,例如表3-3,表3-3为第一根设备所述维护的多个VPN路由表,即VPN路由表1、VPN路由表2以及VPN路由表3,VPN路由表1、VPN路由表2以及VPN路由表3对应的MVPN ID相同,例如在表3-3中,VPN路由表1、VPN路由表2以及VPN路由表3的MVPN ID都为(192.168.110.2)。After the first device determines that the multicast routing information corresponding to the second multicast join message meets the preferred condition, the first root device matches the second root device information in the multicast routing information that meets the preferred condition with the first root device. The first device information is compared. It should be noted that the second device information may be, for example, a management field (administrator) included in an import attribute of a routing target (RT) in the multicast routing information. The first device information, for example, may be the MVPN ID of the first root device, and the MVPN ID is the ID corresponding to the MVPN maintained by the first root device, for example, Table 3-3, and Table 3-3 is the first root. The plurality of VPN routing tables maintained by the device, that is, the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3, the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3 have the same MVPN ID, for example, in the table. In 3-3, the MVPN IDs of VPN routing table 1, VPN routing table 2, and VPN routing table 3 are both (192.168.110.2).
具体地,第一根设备将第二组播加入报文中的组播路由信息的RT-import属性包含administrator field与第一根设备的MVPN ID进行比较,例如,当组播路由信息中包含的administrator field为<192.168.110.2:13>时,第一根设备将<192.168.110.2:13>中的(192.168.110.2)与表3-3中第一根设备的MVPN ID进行比较,即与表3-3所示的VPN路由表1、VPN路由表2以及VPN路由表3对应的(192.168.110.2)进行比较,如果相同,则表示第一根设备的MVPN ID与组播路由信息中的administrator field相同,然后第一根设备将第二组播加入报文中的组播路由信息添加到VPN路由表中,另外,如果表3-3所示的 VPN路由表1、VPN路由表2以及VPN路由表3对应MVPN ID的不是(192.168.110.2),则表示第二组播加入报文对应的组播路由信息不是第一根设备处理的组播路由信息,第一根设备不将第二组播加入报文中的组播路由信息添加到路由表中或者丢弃第二组播加入报文中的组播路由信息等。Specifically, the first device compares the RT-import attribute of the multicast routing information in the second multicast join message with the administrator field and the MVPN ID of the first root device, for example, when the multicast routing information is included. When the administrator field is <192.168.110.2:13>, the first device compares (192.168.110.2) in <192.168.110.2:13> with the MVPN ID of the first device in Table 3-3, that is, the table. 3-3 shows the VPN routing table 1, VPN routing table 2, and VPN routing table 3 corresponding to (192.168.110.2) for comparison. If they are the same, it means the MVPN ID of the first root device and the administrator in the multicast routing information. The field is the same, and then the first device adds the multicast routing information in the second multicast join message to the VPN routing table. In addition, if the VPN routing table 1, VPN routing table 2, and VPN shown in Table 3-3 If the MVPN ID of the routing table 3 is not (192.168.110.2), the multicast routing information corresponding to the second multicast join message is not the multicast routing information processed by the first root device. The first device does not use the second group. Add multicast routing information in the broadcast join message to the routing table. The multicast routing information in the second multicast join message is discarded.
需要说明的是,本实施例中,组播路由信息中包含的administrator field为<192.168.110.2:13>仅仅为一个例子,在实际应用中administrator field还可以是其他,此处不做限定。It should be noted that, in this embodiment, the administrator field included in the multicast routing information is <192.168.110.2:13>, which is only an example. In the actual application, the administrator field may be other, which is not limited herein.
具体请参考图7和图8的根设备1和根设备2的处理流程进行描述:For details, please refer to the processing flow of the root device 1 and the root device 2 of FIG. 7 and FIG. 8 for description:
请参考图7,图7所示的根设备1确定叶子设备1、叶子设备2以及叶子设备3分别对应的组播路由信息满足优选条件之后,根设备1分别将叶子设备1、叶子设备2以及叶子设备3对应的组播路由信息中的RT-import属性包含的Administrator field与根设备1的MVPN ID进行比较,如果两者相同,则根设备1将组播路由信息添加到根设备1的VPN路由表中。具体地,由于叶子设备1以及叶子设备2优选从根设备1接收组播数据,所以叶子设备1和叶子设备2对应的组播路由信息中的RT-import属性包含的Administrator field与根设备1的MVPN ID相同,所以根设备1将叶子设备1和叶子设备2对应的组播路由信息添加到根设备1的VPN路由表中,但是,叶子设备3优选了根设备2,所以叶子设备3向根设备1对应的组播路由信息中RT-import属性包含的Administrator field与根设备1的MVPN ID不相同,则根设备1丢弃叶子设备3对应的组播路由信息。Referring to FIG. 7, after the root device 1 shown in FIG. 7 determines that the multicast routing information corresponding to the leaf device 1, the leaf device 2, and the leaf device 3 respectively meets the preferred conditions, the root device 1 respectively sets the leaf device 1, the leaf device 2, and The administrator field of the RT-import attribute in the multicast routing information corresponding to the leaf device 3 is compared with the MVPN ID of the root device 1. If the two are the same, the root device 1 adds the multicast routing information to the VPN of the root device 1. In the routing table. Specifically, since the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the root device 1 The MVPN ID is the same, so the root device 1 adds the multicast routing information corresponding to the leaf device 1 and the leaf device 2 to the VPN routing table of the root device 1. However, the leaf device 3 preferably has the root device 2, so the leaf device 3 is rooted. The multicast field information in the RT-import attribute of the device 1 is different from the MVPN ID of the root device 1. The root device 1 discards the multicast routing information corresponding to the leaf device 3.
同样,图7所示的根设备2确定叶子设备1、叶子设备2以及叶子设备3分别对应的组播路由信息满足优选条件之后,根设备1分别将叶子设备1、叶子设备2以及叶子设备3对应的组播路由信息中的RT-import属性包含的Administrator field与根设备2的MVPN ID进行比较,如果两者相同,则根设备2将该组播路由信息添加到根设备2的VPN路由表中。由于叶子设备3优选了根设备2,所以叶子设备3向根设备2对应的组播路由信息中RT-import属性包含的Administrator field与根设备2的MVPN ID相同,所以根设备2将叶子设备3对应的组播路由信息添加到根设备2的VPN路由表中。但是,叶子设备1以及叶子设备2优选从根设备1接收组播数据,所以叶子设备1和叶子设备2对应的组播路由信息中的RT-import属性包含的Administrator field与根设备2的MVPN ID不相同,因此,根设备2将叶子设备1和叶子设备2对应的组播路由信息丢弃。Similarly, after the root device 2 shown in FIG. 7 determines that the multicast routing information corresponding to the leaf device 1, the leaf device 2, and the leaf device 3 respectively meets the preferred condition, the root device 1 respectively sets the leaf device 1, the leaf device 2, and the leaf device 3. The administrator field of the RT-import attribute in the corresponding multicast routing information is compared with the MVPN ID of the root device 2. If the two are the same, the root device 2 adds the multicast routing information to the VPN routing table of the root device 2. in. Since the leaf device 3 is preferably the root device 2, the LDAP field included in the RT-import attribute of the leaf device 3 corresponding to the root device 2 is the same as the MVPN ID of the root device 2, so the root device 2 will be the leaf device 3. The corresponding multicast routing information is added to the VPN routing table of the root device 2. However, the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, so the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the MVPN ID of the root device 2. The root device 2 discards the multicast routing information corresponding to the leaf device 1 and the leaf device 2.
请参考图8,图8所示的根设备1接收RR对应的两条组播路由信息分别是叶子设备1和叶子设备2对应的组播路由信息其中的一个,以及叶子设备3对应的组播路由信息。根设备1分别将叶子设备1和叶子设备2对应的组播路由信息其中的一个,以及叶子设备3对应的组播路由信息中的RT-import属性包含的Administrator field与根设备1的MVPN ID进行比较,如果两者相同,则根设备1将组播路由信息添加到根设备1的VPN路由表中。具体地,由于叶子设备1以及叶子设备2优选从根设备1接收组播数据,所以叶子设备1和叶子设备2对应的一个组播路由信息中的RT-import属性包含的Administrator field与根设备1的MVPN ID相同,所以根设备1将叶子设备1和叶子设备2对应的一个组播路由信息添加到根设备1的VPN路由表中,但是,叶子设备3优选了根设备2,所以叶子设备3对应的组播路由信息中RT-import属性包含的Administrator field与根设备1的MVPN ID不相同,则根设备1丢弃叶子设备3对应的组播路由信息。Referring to FIG. 8, the two multicast routing information corresponding to the RR received by the root device 1 in FIG. 8 is one of the multicast routing information corresponding to the leaf device 1 and the leaf device 2, and the multicast corresponding to the leaf device 3. Routing information. The root device 1 performs one of the multicast routing information corresponding to the leaf device 1 and the leaf device 2, and the administrator field of the RT-import attribute in the multicast routing information corresponding to the leaf device 3 and the MVPN ID of the root device 1 respectively. For comparison, if the two are the same, the root device 1 adds the multicast routing information to the VPN routing table of the root device 1. Specifically, since the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the root device 1 The MVPN ID is the same, so the root device 1 adds a multicast routing information corresponding to the leaf device 1 and the leaf device 2 to the VPN routing table of the root device 1. However, the leaf device 3 preferably has the root device 2, so the leaf device 3 The root device 1 discards the multicast routing information corresponding to the leaf device 3, and the host device 1 has the same MVPN ID as the root device 1 in the corresponding multicast routing information.
同样,图8中根设备2接收RR对应的两条组播路由信息分别是叶子设备1和叶子设备2对应的组播路由信息其中的一个,以及叶子设备3对应的组播路由信息。根设备2分别将叶子设备1和叶子设备2对应的组播路由信息,以及叶子设备3对应的组播路由信息中的RT-import属性包含的Administrator field与根设备2的MVPN ID进行比较,如果两者相同,则根设备2将组播路由信息添加到根设备1的VPN路由表中。具体地,由于叶子设备1以及叶子设备2优选从根设备1接收组播数据,所以叶子设备1和叶子设备2对应的一个组播路由信息中的RT-import属性包含的Administrator field与根设备2的MVPN ID不相同,所以根设备2丢弃叶子设备1和叶子设备2对应的一个组播路由信息。叶子设备3优选了根设备2,所以叶子设备3对应的组播路由信息中RT-import属性包含的Administrator field与根设备2的MVPN ID相同,则根设备2将叶子设备3对应的组播路由信息添加到根设备2的VPN路由表中。Similarly, the two multicast routing information corresponding to the RR received by the root device 2 in FIG. 8 is one of the multicast routing information corresponding to the leaf device 1 and the leaf device 2, and the multicast routing information corresponding to the leaf device 3. The root device 2 compares the multicast routing information corresponding to the leaf device 1 and the leaf device 2, and the administrator field included in the RT-import attribute in the multicast routing information corresponding to the leaf device 3 with the MVPN ID of the root device 2, respectively. If the two are the same, the root device 2 adds the multicast routing information to the VPN routing table of the root device 1. Specifically, since the leaf device 1 and the leaf device 2 preferably receive the multicast data from the root device 1, the RT-import attribute in the multicast routing information corresponding to the leaf device 1 and the leaf device 2 includes the Administrator field and the root device 2 The MVPN IDs are different, so the root device 2 discards one multicast routing information corresponding to the leaf device 1 and the leaf device 2. The leaf device 3 is preferably the root device 2, so the router field corresponding to the RT-import attribute of the leaf device 3 has the same MVPN ID as the root device 2, and the root device 2 uses the multicast route corresponding to the leaf device 3. Information is added to the VPN routing table of root device 2.
606、第一根设备根据组播路由信息的VPN实例标识将目标叶子设备的组播路由信息添加到目标路由表中。606. The first device adds the multicast routing information of the target leaf device to the target routing table according to the VPN instance identifier of the multicast routing information.
每个第二组播加入报文中对应的组播路由信息中包含VPN实例标识,该VPN实例标识用于表征该组播路由信息对应的路由表。The corresponding multicast routing information in the second multicast join message includes a VPN instance identifier, where the VPN instance identifier is used to represent a routing table corresponding to the multicast routing information.
由于第一根设备维护一个或多个VPN路由表,当有组播路由信息需要加入VPN路由表时,第一根设备需要根据组播路由信息中的VPN实例标识与本地的VPN路由表中每个VPN路由表的标志(index)进行匹配,需要说明的是第一根设备中的每个VPN路由表都包含其相对应的index,不同的index用于区分表征不同VPN路由表,具体地,第一根设备根据administrator field包含的<192.168.110.2:13>中的确定该组播路由信息包含的VPN实例标识为13,则第一根设备将该VPN实例标识13与表3-3中的VPN路由表1、VPN路由表2以及VPN路由表3分别对应的index进行匹配,如果存在index为13的VPN路由表,则第一根设备将index为13的VPN路由表确定为目标路由表,例如表3-3中VPN路由表1对应的index为13,则第一根设备将VPN路由表1确定为目标路由表,并将该组播路由信息添加到VPN路由表1中。例如,将该组播路由信息包含的NLRI信息中的始发路由器IP地址(Originating route’s IP address)和组播源(Multicast source)添加到VPN路由表1对应的表项中,需要说明的是,本实施例中第一根设备还可以将组播路由信息中其他的信息添加到VPN路由表1,如设备的出入接口等信息添加到VPN路由表1中。若组播路由表中不存在index为13的路由表,则第一根设备将该组播路由信息丢弃。Since the first device maintains one or more VPN routing tables, when the multicast routing information needs to be added to the VPN routing table, the first root device needs to use the VPN instance identifier in the multicast routing information and the local VPN routing table. The index of the VPN routing table is matched. It should be noted that each VPN routing table in the first root device includes its corresponding index. Different indexes are used to distinguish different VPN routing tables. Specifically, The first device determines that the VPN instance ID of the multicast routing information is 13 according to the <192.168.110.2:13> included in the administrator field, and the first root device identifies the VPN instance identifier 13 and Table 3-3. The index corresponding to the VPN routing table 1, the VPN routing table 2, and the VPN routing table 3 are matched. If there is a VPN routing table with an index of 13, the first device determines the VPN routing table with index 13 as the target routing table. For example, if the index corresponding to the VPN routing table 1 in Table 3-3 is 13, the first device determines the VPN routing table 1 as the target routing table, and adds the multicast routing information to the VPN routing table 1. For example, the originating route's IP address and the multicast source in the NLRI information included in the multicast routing information are added to the entry corresponding to the VPN routing table 1. In this embodiment, the first device may also add other information in the multicast routing information to the VPN routing table 1. The information such as the inbound and outbound interfaces of the device is added to the VPN routing table 1. If the routing table with index 13 is not in the multicast routing table, the first device discards the multicast routing information.
607、第一根设备向目标叶子设备发送组播数据。607. The first root device sends multicast data to the target leaf device.
在组播源向第一根设备下发组播数据时,第一根设备则根据目标路由表中的信息向目标叶子设备发送该组播数据。When the multicast source sends multicast data to the first root device, the first device sends the multicast data to the target leaf device according to the information in the target routing table.
需要说明的是,本实施例中,当第一根设备向目标叶子设备发送组播数据时,第一根设备可以直接向目标叶子设备发送组播数据,还可以向核心设备(Provider,P)发送组播数据,然后由P设备向目标叶子设备发送组播数据,此处不做限定。It should be noted that, in this embodiment, when the first root device sends multicast data to the target leaf device, the first root device may directly send the multicast data to the target leaf device, and may also send the multicast data to the core device (Provider, P). The multicast data is sent, and then the P device sends the multicast data to the target leaf device, which is not limited herein.
需要说明的是,本实施例中,第一根设备直接向目标叶子设备发送组播数据与前述图3中步骤305类似,此处不再赘述。It should be noted that, in this embodiment, the first device directly sends the multicast data to the target leaf device, which is similar to the foregoing step 305 in FIG. 3, and details are not described herein again.
需要说明的是,本实施例中,当RR兼做根设备时,RR执行前述图3中步骤301至步骤305的流程,RR兼做根设备为RR既充当路由反射器的作用又充当PE设备的作用,此处不再赘述。It should be noted that, in this embodiment, when the RR serves as the root device, the RR performs the foregoing steps 301 to 305 in FIG. 3, and the RR serves as the root device, and the RR acts as both a route reflector and a PE device. The role of this, will not repeat them here.
本实施中,目标叶子设备向RR发送的第一组播加入报文,第一组播加入报文中组播路由信息的NLRI信息包含设备路由标识,RR可以根据设备路由标识确定每个第一组播加入报文满足前发条件,当设备路由标识为叶子设备对应的ROUTER ID时,RR向第一根设备发送的第二组播加入报文为第一组播加入报文,当设备路由标识为目标叶子设备优选的二根设备的ROUTER ID时,RR向第一根设备发送优选了同一第二根设备的叶子设备发送的第一组播加入报文中的一个。因此,本实施中,第一组播加入报文中包含设备路由标识,确保第一组播加入报文在RR中都满足前发条件,当有组播数据下发时,第一根设备向优选了第一根设备的目标叶子设备发送组播数据,使得优选了不同根设备的叶子设备都可以接收到组播数据。In this implementation, the first multicast join message sent by the target leaf device to the RR, the NLRI information of the multicast routing information in the first multicast join message includes the device route identifier, and the RR may determine each first according to the device route identifier. The multicast join message meets the pre-conditions. When the device route identifier is the ROUTER ID of the leaf device, the second multicast join message sent by the RR to the first device is the first multicast join message. When the ROUTER ID of the two devices of the target leaf device is identified, the RR sends one of the first multicast join messages sent by the leaf device that is preferably the same second device to the first device. Therefore, in this implementation, the first multicast join message includes the device routing identifier, and ensures that the first multicast join message satisfies the pre-conditions in the RR. When the multicast data is delivered, the first device sends the packet to the first multicast device. Preferably, the target leaf device of the first root device sends multicast data, so that the leaf devices that prefer different root devices can receive the multicast data.
以上对本申请实施例中组播路由处理的方法进行了描述,下面结合附图描述本申请实施例中的网络设备进行描述。本申请实施例中的网络设备可以包括网络设备、路由反射器和芯片系统,在不同角色下其功能不同,需要说明的是,该边缘设备在本申请实施例以及后续实施例中仅以第一根设备作为例子进行说明。The method for processing the multicast routing in the embodiment of the present application has been described above. The description of the network device in the embodiment of the present application is described below with reference to the accompanying drawings. The network device in the embodiment of the present application may include a network device, a route reflector, and a chip system, and the functions are different in different roles. It is to be noted that the edge device is only the first in the embodiment of the present application and the subsequent embodiments. The root device is explained as an example.
请参考图9,本申请实施例提供的网络设备可以为第一根设备或芯片系统,该网络设备应用于组播虚拟专用网MVPN,所述MVPN包括M个根设备和N个叶子设备,所述M为大于1的整数,所述N为大于或等于2的整数,所述N个叶子设备在发送组播加入报文时,分别优选了所述M个根设备中的不同的根设备,该网络设备90包括接收单元901、处理单元902以及发送单元903。其中,接收单元901可以用于执行图3对应的实施例中的步骤301所描述的内容。处理单元902,可以用于执行图3对应实施例中的步骤302、步骤303、以及步骤304分别所描述的内容,也可以用于执行图6中对应的实施例中步骤604、步骤605以及步骤606分别所述描述的内容。发送单元903,可以用于执行图3对应的实施例中步骤305所描述的内容,也可以执行图6对应实施例中步骤607所述描述的内容。Referring to FIG. 9, the network device provided by the embodiment of the present application may be a first device or a chip system, where the network device is applied to a multicast virtual private network (MVPN), where the MVPN includes M root devices and N leaf devices. The M is an integer greater than 1, and the N is an integer greater than or equal to 2. The N leaf devices respectively select different root devices of the M root devices when sending the multicast join message. The network device 90 includes a receiving unit 901, a processing unit 902, and a transmitting unit 903. The receiving unit 901 can be used to execute the content described in step 301 in the embodiment corresponding to FIG. 3. The processing unit 902 can be used to perform the operations described in step 302, step 303, and step 304 in the corresponding embodiment of FIG. 3, and can also be used to perform step 604, step 605, and steps in the corresponding embodiment in FIG. 606 describes the content described separately. The sending unit 903 can be used to perform the content described in step 305 in the embodiment corresponding to FIG. 3, and can also perform the content described in step 607 in the corresponding embodiment of FIG. 6.
请参考图10,本申请实施例提供的网络设备可以为路由反射器或芯片系统,所述网络设备应用于MVPN,所述MVPN包括路由反射器、M个根设备和N个叶子设备,所述M为大于1的整数,所述N为大于或等于2的整数,所述N个叶子设备在发送组播加入报文时,分别优选了所述M个根设备中的不同的根设备,该网络设备100包括,接收单元1001,处理单元1002,发送单元1003,其中,接收单元1001可以用于接收图6对应的实施例中的步骤601目标叶子设备发送第一组播加入报文。处理单元1002可以用于执行图6对应的实施例中的步骤602所述描述的内容。发送单元1003可以用于执行图6对应的实施例中的步骤604所述描述的内容。Referring to FIG. 10, the network device provided by the embodiment of the present application may be a route reflector or a chip system, where the network device is applied to an MVPN, where the MVPN includes a route reflector, M root devices, and N leaf devices, M is an integer greater than 1, and the N is an integer greater than or equal to 2. The N leaf devices respectively select different root devices of the M root devices when sending the multicast join message. The network device 100 includes a receiving unit 1001, a processing unit 1002, and a sending unit 1003. The receiving unit 1001 can be configured to receive the step 601 in the embodiment corresponding to FIG. 6 to send the first multicast joining message. The processing unit 1002 can be used to perform the content described in step 602 in the embodiment corresponding to FIG. 6. The transmitting unit 1003 can be used to execute the content described in step 604 in the embodiment corresponding to FIG. 6.
请参考图11,图11是本申请实施例提供的网络设备的结构示意图,该网络设备为第一根设备。所述第一根设备110包括至少一个处理器1110、存储器1150和收发器1130。该收发器可包括接收机和发射机,该存储器1150可以包括只读存储器和/或随机存取存储器,并向处理器1110提供操作指令和数据。存储器1150的一部分还可以包括非易失性随机存取存储器(NVRAM)。Please refer to FIG. 11. FIG. 11 is a schematic structural diagram of a network device according to an embodiment of the present disclosure. The network device is a first device. The first root device 110 includes at least one processor 1110, a memory 1150, and a transceiver 1130. The transceiver can include a receiver and a transmitter, and the memory 1150 can include read only memory and/or random access memory and provide operational instructions and data to the processor 1110. A portion of the memory 1150 can also include non-volatile random access memory (NVRAM).
在一些实施方式中,存储器1150存储了如下的元素,可执行模块或者数据结构,或者他们的子集,或者他们的扩展集:In some implementations, the memory 1150 stores the following elements, executable modules or data structures, or a subset thereof, or their extended set:
在本申请实施例中,通过调用存储器1150存储的操作指令(该操作指令可存储在操作系统中),执行相应的操作。处理器1110控制第一根设备110的操作,处理器1110还可以称为CPU(Central Processing Unit,中央处理单元)。存储器1150可以包括只读存储器和随机存取 存储器,并向处理器1110提供指令和数据。存储器1150的一部分还可以包括非易失性随机存取存储器(NVRAM)。具体的应用中第一根设备110的各个组件通过总线系统1120耦合在一起,其中总线系统1120除包括数据总线之外,还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见,在图中将各种总线都标为总线系统1120。In the embodiment of the present application, the corresponding operation is performed by calling an operation instruction stored in the memory 1150 (which can be stored in the operating system). The processor 1110 controls the operation of the first root device 110, and the processor 1110 may also be referred to as a CPU (Central Processing Unit). Memory 1150 can include read only memory and random access memory and provides instructions and data to processor 1110. A portion of the memory 1150 can also include non-volatile random access memory (NVRAM). In a specific application, the components of the first device 110 are coupled together by a bus system 1120. The bus system 1120 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 1120 in the figure.
上述本申请实施例揭示的方法可以应用于处理器1110中,或者由处理器1110实现。处理器1110可能是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法的各步骤可以通过处理器1110中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1110可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1150,该存储器1150可以是物理上独立的单元,也可以是与处理器1110集成在一起的,处理器1110读取存储器1150中的信息,结合其硬件完成上述方法的步骤。The method disclosed in the foregoing embodiment of the present application may be applied to the processor 1110 or implemented by the processor 1110. The processor 1110 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1110 or an instruction in a form of software. The processor 1110 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or discrete hardware. Component. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1150. The memory 1150 can be a physically separate unit or integrated with the processor 1110. The processor 1110 reads the information in the memory 1150 and completes the steps of the above method in combination with hardware.
可选地,收发器1130可以用于执行图3对应的实施例中的步骤301所描述的内容和图3对应的实施例中步骤305所描述的内容,也可以执行图6中对应实施例中步骤607所述描述的内容。或其他可选实施例中的第一根设备的消息发送以及接收的步骤。Optionally, the transceiver 1130 may be used to perform the content described in step 301 in the embodiment corresponding to FIG. 3 and the content described in step 305 in the embodiment corresponding to FIG. 3, and may also be executed in the corresponding embodiment in FIG. The content described in step 607. Or the step of message transmission and reception of the first root device in other alternative embodiments.
处理器1110可以用于执行图3对应实施例中的步骤302、步骤303以及步骤304分别所描述的内容,也可以用于执行图6中对应的实施例中步骤604、步骤605以及步骤606分别所述描述的内容。或其他可选实施例中的第一根设备的数据处理的步骤。The processor 1110 can be used to perform the operations described in step 302, step 303, and step 304 in the corresponding embodiment of FIG. 3, and can also be used to perform step 604, step 605, and step 606 in the corresponding embodiment in FIG. 6, respectively. The content of the description. Or the step of data processing of the first device in the alternative embodiment.
路由反射器的结构也可以参阅图11进行理解,路由反射器中相应的收发器可以用于接收图6对应的实施例中的步骤601目标叶子设备发送第一组播加入报文,也可以用于执行图6对应的实施例中的步骤603所述描述的内容。处理器也可以用于执行图6对应的实施例中的步骤602所述描述的内容。或其他可选实施例中路由反射器相应的接收和处理的步骤。The structure of the route reflector can also be understood by referring to FIG. 11. The corresponding transceiver in the route reflector can be used to receive the first multicast join message in step 601 in the embodiment corresponding to FIG. 6. The content described in step 603 in the embodiment corresponding to FIG. 6 is performed. The processor can also be used to perform the description described in step 602 of the embodiment corresponding to FIG. Or the corresponding steps of receiving and processing the route reflector in other alternative embodiments.
图12是本申请实施例提供的芯片系统120的另一种实施方式的结构示意图。芯片系统120包括至少一个处理器1210、存储器1250和通信接口1230,存储器1250可以包括只读存储器和随机存取存储器,并向处理器1210提供操作指令和数据。存储器1250的一部分还可以包括非易失性随机存取存储器(NVRAM)。FIG. 12 is a schematic structural diagram of another embodiment of a chip system 120 according to an embodiment of the present application. The chip system 120 includes at least one processor 1210, a memory 1250, and a communication interface 1230. The memory 1250 can include read only memory and random access memory, and provides operational instructions and data to the processor 1210. A portion of memory 1250 may also include non-volatile random access memory (NVRAM).
在一些实施方式中,存储器1250存储了如下的元素,可执行模块或者数据结构,或者他们的子集,或者他们的扩展集:In some implementations, the memory 1250 stores the following elements, executable modules or data structures, or a subset thereof, or their extended set:
在本申请实施例中,通过调用存储器1250存储的操作指令(该操作指令可存储在操作系统中),执行相应的操作。In the embodiment of the present application, the corresponding operation is performed by calling an operation instruction stored in the memory 1250 (which can be stored in the operating system).
一种可能的实现方式为:芯片系统和网络设备所用的芯片系统的结构类似,但不同的装置使用不同的芯片系统以实现各自的功能。One possible implementation is that the chip system used in the chip system and the network device are similar in structure, but different devices use different chip systems to achieve their respective functions.
处理器1210控制芯片系统的操作,处理器1210还可以称为CPU(Central Processing Unit,中央处理单元)。存储器1250可以包括只读存储器和随机存取存储器,并向处理器1210提供指令和数据。存储器1250的一部分还可以包括非易失性随机存取存储器(NVRAM)。具体的应用中芯片系统110的各个组件通过总线系统1220耦合在一起,其中总线系统1220除包括 数据总线之外,还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见,在图中将各种总线都标为总线系统1220。The processor 1210 controls the operation of the chip system, and the processor 1210 may also be referred to as a CPU (Central Processing Unit). Memory 1250 can include read only memory and random access memory and provides instructions and data to processor 1210. A portion of memory 1250 may also include non-volatile random access memory (NVRAM). The components of the chip system 110 are coupled together by a bus system 1220 in a specific application. The bus system 1220 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 1220 in the figure.
上述本申请实施例揭示的方法可以应用于处理器1210中,或者由处理器1210实现。处理器1210可能是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法的各步骤可以通过处理器1210中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1210可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1250,该存储器1250可以是物理上独立的单元,也可以是与处理器1210集成在一起的,处理器1210读取存储器1250中的信息,结合其硬件完成上述方法的步骤。The method disclosed in the foregoing embodiment of the present application may be applied to the processor 1210 or implemented by the processor 1210. Processor 1210 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1210 or an instruction in a form of software. The processor 1210 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or discrete hardware. Component. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in a memory 1250, which may be a physically separate unit, or may be integrated with the processor 1210. The processor 1210 reads the information in the memory 1250 and performs the steps of the above method in combination with its hardware.
可选地,通信接口1230可以用于执行图3对应的实施例中的步骤301所描述的内容和图3对应的实施例中步骤305所描述的内容,也可以执行图6中对应实施例中步骤604所述描述的内容,还可以用于执行图6中对应实施例中步骤607所述描述的内容。或其他可选实施例中的第一根设备或路由反射器中数据的接收和发送的步骤。Optionally, the communication interface 1230 can be used to perform the content described in step 301 in the embodiment corresponding to FIG. 3 and the content described in step 305 in the embodiment corresponding to FIG. 3, and can also be executed in the corresponding embodiment in FIG. The content described in step 604 can also be used to perform the content described in step 607 in the corresponding embodiment in FIG. Or the step of receiving and transmitting data in the first device or route reflector in other alternative embodiments.
处理器1210可以用于执行图3对应实施例中的步骤302、步骤303、步骤304以及步骤305分别所描述的内容,也可以用于执行图6中对应的实施例中步骤604、步骤605以及步骤606分别所述描述的内容。还可以用于执行图6对应的实施例中的步骤602所述描述的内容。或其他可选实施例中的第一根设备或路由反射器中数据处理的步骤。The processor 1210 may be configured to perform the operations described in step 302, step 303, step 304, and step 305 in the corresponding embodiment of FIG. 3, and may also be used to perform step 604, step 605 in the corresponding embodiment in FIG. Step 606 describes the content described separately. It can also be used to perform the description described in step 602 in the embodiment corresponding to FIG. 6. Or the step of data processing in the first root device or route reflector in other alternative embodiments.
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product.
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质,(例如,软盘、硬盘、磁带)、光介质(例如,DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be stored by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成,该程序可以存储于一计算机可读存储介质中,存储介质可以包括:ROM、RAM、磁盘或光盘等。A person skilled in the art may understand that all or part of the various steps of the foregoing embodiments may be performed by a program to instruct related hardware. The program may be stored in a computer readable storage medium, and the storage medium may include: ROM, RAM, disk or CD.
以上对本申请实施例所提供的数据传输的方法、设备、计算机可读存储介质以及芯片系统进行了详细介绍,本文中应用了具体个例对本申请的原理及实施方式进行了阐述,以上实施例的说明只是用于帮助理解本申请的方法及其核心思想;同时,对于本领域的一般 技术人员,依据本申请的思想,在具体实施方式及应用范围上均会有改变之处,综上所述,本说明书内容不应理解为对本申请的限制。The method, device, computer readable storage medium and chip system for data transmission provided by the embodiments of the present application are described in detail. The principles and implementation manners of the present application are described in the following examples. The description is only used to help understand the method of the present application and its core ideas; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in specific embodiments and application scopes. The contents of this specification are not to be construed as limiting the application.
Claims (22)
- 一种组播路由处理方法,其特征在于,所述方法应用于组播虚拟专用网MVPN,所述MVPN包括M个根设备和N个叶子设备,所述M为大于1的整数,所述N为大于或等于2的整数,所述N个叶子设备在发送组播加入报文时,分别优选了所述M个根设备中的不同的根设备,针对第一根设备,所述方法包括:A multicast routing processing method is characterized in that the method is applied to a multicast virtual private network MVPN, where the MVPN includes M root devices and N leaf devices, and the M is an integer greater than 1, the N For the first root device, the N-th leaf device preferably uses a different root device of the M root devices when sending the multicast join message. For the first root device, the method includes:所述第一根设备接收目标叶子设备发送的第一组播加入报文或接收路由反射器发送的第二组播加入报文,所述第一组播加入报文包括组播路由信息,所述组播路由信息中包括设备路由标识,所述第二组播加入报文由路由反射器在接收到所述目标叶子设备发送的所述第一组播加入报文后发出,所述第二组播加入报文与所述第一组播加入报文所包含的组播路由信息相同,所述目标叶子设备为所述N个叶子设备中的一个或多个,所述第一根设备为所述M个根设备中的任意一个;The first root device receives the first multicast join message sent by the target leaf device or the second multicast join message sent by the route reflector, where the first multicast join message includes multicast routing information. The multicast routing information includes a device routing identifier, where the second multicast join message is sent by the route reflector after receiving the first multicast join message sent by the target leaf device, where the second The multicast join message is the same as the multicast routing information included in the first multicast join message, and the target leaf device is one or more of the N leaf devices, where the first root device is Any one of the M root devices;所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件;Determining, by the first root device, that the multicast routing information meets a preferred condition according to the device routing identifier;所述第一根设备确定所述组播路由信息中包含的第二根设备信息与第一根设备信息是否相同,所述第二根设备信息为所述目标叶子设备所优选接收组播数据的第二根设备对应的信息;Determining, by the first root device, whether the second root device information included in the multicast routing information is the same as the first root device information, where the second root device information is that the target leaf device preferentially receives the multicast data. Information corresponding to the second device;若相同,则所述第一根设备将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中;If the same, the first root device adds the multicast routing information of the target leaf device to the virtual private network VPN routing table of the first root device;在有组播数据下发时,所述第一根设备根据所述VPN路由表向所述目标叶子设备发送所述组播数据。When the multicast data is delivered, the first root device sends the multicast data to the target leaf device according to the VPN routing table.
- 根据权利要求1所述的方法,其特征在于,所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件包括:The method according to claim 1, wherein the determining, by the first root device, that the multicast routing information meets a preferred condition according to the device routing identifier comprises:当所述设备路由标识为所述目标叶子设备对应的路由ID时,所述第一根设备根据所述目标叶子设备对应的路由ID确定所述组播路由信息满足优选条件。When the device routing identifier is a routing ID corresponding to the target leaf device, the first root device determines that the multicast routing information satisfies a preferred condition according to a routing ID corresponding to the target leaf device.
- 根据权利要求1所述的方法,其特征在于,所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件包括:The method according to claim 1, wherein the determining, by the first root device, that the multicast routing information meets a preferred condition according to the device routing identifier comprises:当所述设备路由标识为所述目标叶子设备所优选接收组播数据的所述第二根设备的路由ID时,所述第一根设备根据所述第二根设备的路由ID确定所述组播路由信息满足优选条件。When the device routing identifier is a routing ID of the second root device that the target leaf device preferably receives the multicast data, the first root device determines the group according to the routing ID of the second root device. The broadcast routing information satisfies the preferred conditions.
- 根据权利要求1至3中任一项所述的方法,其特征在于,所述第一根设备将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中包括:The method according to any one of claims 1 to 3, wherein the first root device adds multicast routing information of the target leaf device to a virtual private network VPN route of the first root device The table includes:所述第一根设备确定所述组播路由信息的VPN实例标识与所述第一根设备的MVPN ID是否相同,所述MVPN ID为第一根设备的MVPN对应的ID地址;Determining, by the first root device, that the VPN instance identifier of the multicast routing information is the same as the MVPN ID of the first root device, where the MVPN ID is an ID address corresponding to the MVPN of the first root device;若相同,则所述第一根设备将所述组播路由信息添加到目标路由表中,所述目标路由表为所述第一根设备的VPN路由表中的其中一个,所述目标路由表用于指示所述第一根设备向所述目标叶子设备发送所述组播数据。If the same, the first root device adds the multicast routing information to the target routing table, where the target routing table is one of the VPN routing tables of the first root device, and the target routing table And configured to instruct the first root device to send the multicast data to the target leaf device.
- 根据权利要求4所述的方法,其特征在于,所述第一根设备向所述目标叶子设备发送所述组播数据包括:The method according to claim 4, wherein the transmitting, by the first root device, the multicast data to the target leaf device comprises:所述第一根设备向所述目标叶子设备发送组播数据接收消息,所述组播数据接收消息用于指示所述目标叶子设备接收所述组播数据;The first root device sends a multicast data receiving message to the target leaf device, where the multicast data receiving message is used to indicate that the target leaf device receives the multicast data;所述第一根设备接收所述目标叶子设备发送的组播数据接收响应消息,所述组播数据接 收响应消息用于指示所述目标叶子设备需要接收所述组播数据;Receiving, by the first root device, a multicast data receiving response message sent by the target leaf device, where the multicast data receiving response message is used to indicate that the target leaf device needs to receive the multicast data;所述第一根设备向发送所述组播数据接收响应消息对应的所述目标叶子设备发送所述组播数据。The first root device sends the multicast data to the target leaf device corresponding to the multicast data receiving response message.
- 一种组播路由处理方法,其特征在于,所述方法应用于MVPN,所述MVPN包括路由反射器、M个根设备和N个叶子设备,所述M为大于1的整数,所述N为大于或等于2的整数,所述N个叶子设备在发送组播加入报文时,分别优选了所述M个根设备中的不同的根设备,所述方法包括:A multicast routing processing method, the method is applied to an MVPN, where the MVPN includes a route reflector, M root devices, and N leaf devices, where the M is an integer greater than 1, and the N is An integer greater than or equal to 2, wherein the N leaf devices respectively select different root devices of the M root devices when sending the multicast join message, where the method includes:所述路由反射器接收目标叶子设备发送的第一组播加入报文,所述第一组播加入报文包括组播路由信息,所述组播路由信息中包括设备路由标识,所述目标叶子设备为所述N个叶子设备中的一个或多个;The route reflector receives the first multicast join message sent by the target leaf device, where the first multicast join message includes multicast routing information, where the multicast routing information includes a device routing identifier, and the target leaf The device is one or more of the N leaf devices;所述路由反射器根据所述设备路由标识确定所述第一组播加入报文满足前发条件;Determining, by the route reflector, that the first multicast join message meets a pre-condition according to the device routing identifier;所述路由反射器向第一根设备发送第二组播加入报文,所述第一根设备为所述M个根设备中的任意一个,所述第二组播加入报文与所述第一组播加入报文所包含的组播路由信息相同,所述第二组播加入报文用于指示所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件,并在确定所述组播路由信息中包含的第二根设备信息与第一根设备信息相同的情况下将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中,所述第二根设备信息为所述目标叶子设备所优选接收组播数据的第二根设备对应的信息;所述VPN路由表用于指示所述第一根设备根据所述VPN路由表向所述目标叶子设备发送所述组播数据。The route reflector sends a second multicast join message to the first root device, where the first root device is any one of the M root devices, and the second multicast join message and the first The multicast routing information included in a multicast join message is the same, and the second multicast join message is used to indicate that the first root device determines that the multicast routing information meets a preferred condition according to the device routing identifier. And adding the multicast routing information of the target leaf device to the virtual private network of the first root device, if it is determined that the second root device information included in the multicast routing information is the same as the first root device information In the VPN routing table, the second root device information is information corresponding to the second root device that the target leaf device preferably receives the multicast data, and the VPN routing table is used to indicate that the first root device is configured according to the The VPN routing table sends the multicast data to the target leaf device.
- 根据权利要求6所述的方法,其特征在于,所述路由反射器根据所述设备路由标识确定所述第一组播加入报文都满足前发条件包括:The method according to claim 6, wherein the routing reflector determines that the first multicast join message satisfies the pre-conditions according to the device routing identifier:当所述设备路由标识为所述目标叶子设备对应的路由ID时,所述路由反射器根据所述目标叶子设备对应的路由ID确定所述第一组播加入报文满足前发条件。When the device routing identifier is the routing ID corresponding to the target leaf device, the route reflector determines that the first multicast joining message meets the pre-condition according to the routing ID corresponding to the target leaf device.
- 根据权利要求6所述的方法,其特征在于,所述路由反射器根据所述设备路由标识确定所述第一组播加入报文都满足前发条件包括:The method according to claim 6, wherein the routing reflector determines that the first multicast join message satisfies the pre-conditions according to the device routing identifier:当所述设备路由标识为所述目标叶子设备优选接收组播数据的所述第二根设备的路由ID时,所述路由反射器根据所述第二根设备的路由ID确定所述第一组播加入报文满足前发条件。When the device route identifier is a route ID of the second root device that the target leaf device preferably receives the multicast data, the route reflector determines the first group according to the route ID of the second root device. The broadcast join message satisfies the pre-condition.
- 根据权利要求7所述的方法,其特征在于,所述路由反射器向所述第一根设备发送第二组播加入报文包括:The method according to claim 7, wherein the routing reflector sends the second multicast join message to the first root device, including:当所述设备路由标识为所述目标叶子设备对应的路由ID时,所述第二组播加入报文为每个所述目标叶子设备分别发送的所述第一组播加入报文;When the device routing identifier is a routing ID corresponding to the target leaf device, the second multicast joining message is the first multicast joining message sent by each of the target leaf devices.所述路由反射器向第一根设备发送每个所述目标叶子设备分别发送的第一组播加入报文。The route reflector sends a first multicast join message sent by each of the target leaf devices to the first root device.
- 根据权利要求8所述的方法,其特征在于,所述路由反射器向所述第一根设备发送第二组播加入报文包括:The method according to claim 8, wherein the routing reflector sends the second multicast join message to the first root device, including:当所述设备路由标识为所述目标叶子设备优选接收组播数据的所述第二根设备的路由ID时,所述第二组播加入报文为满足前发条件的所述第一组播加入报文中的一个;When the device routing identifier is the routing ID of the second root device that the target leaf device preferably receives the multicast data, the second multicast join message is the first multicast that meets the pre-condition Join one of the messages;所述路由反射器向所述第一根设备发送满足前发条件的所述第一组播加入报文中的一 个。The route reflector sends one of the first multicast join messages that meet the pre-conditions to the first root device.
- 一种网络设备,其特征在于,所述网络设备应用于MVPN,所述MVPN包括M个根设备和N个叶子设备,所述M为大于1的整数,所述N为大于或等于2的整数,所述N个叶子设备在发送组播加入报文时,分别优选了所述M个根设备中的不同的根设备,所述网络设备为第一根设备,所述网络设备包括:A network device, wherein the network device is applied to an MVPN, where the MVPN includes M root devices and N leaf devices, the M is an integer greater than 1, and the N is an integer greater than or equal to 2. When the N-th leaf device sends a multicast join message, each of the M root devices is selected as the first root device, and the network device includes:接收单元,用于接收目标叶子设备发送的第一组播加入报文或接收路由反射器发送的第二组播加入报文,所述第一组播加入报文包括组播路由信息,所述组播路由信息中包括设备路由标识,所述第二组播加入报文由路由反射器在接收到所述目标叶子设备发送的所述第一组播加入报文后发出,所述第二组播加入报文与所述第一组播加入报文所包含的组播路由信息相同,所述目标叶子设备为所述N个叶子设备中的一个或多个,所述第一根设备为所述M个根设备中的任意一个;a receiving unit, configured to receive a first multicast join message sent by the target leaf device, or receive a second multicast join message sent by the route reflector, where the first multicast join message includes multicast routing information, The multicast routing information includes a device routing identifier, where the second multicast join message is sent by the route reflector after receiving the first multicast join message sent by the target leaf device, where the second group The broadcast join message is the same as the multicast routing information included in the first multicast join message, and the target leaf device is one or more of the N leaf devices, where the first root device is Describe any of the M root devices;处理单元用于:The processing unit is used to:根据所述设备路由标识确定所述组播路由信息满足优选条件;Determining, according to the device routing identifier, that the multicast routing information meets a preferred condition;确定所述组播路由信息中包含的第二根设备信息与第一根设备信息是否相同,所述第二根设备信息为所述目标叶子设备所优选接收组播数据的第二根设备对应的信息;Determining whether the second root device information included in the multicast routing information is the same as the first root device information, where the second root device information is corresponding to the second root device that the target leaf device preferably receives the multicast data. information;当所述第二根设备信息与所述第一根设备信息相同时,将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中;Adding the multicast routing information of the target leaf device to the virtual private network VPN routing table of the first root device, when the second root device information is the same as the first root device information;发送单元,用于在有组播数据下发时,根据所述VPN路由表向所述目标叶子设备发送所述组播数据。And a sending unit, configured to send the multicast data to the target leaf device according to the VPN routing table when the multicast data is delivered.
- 根据权利要求11所述的网络设备,其特征在于,所述处理单元具体用于:The network device according to claim 11, wherein the processing unit is specifically configured to:当所述设备路由标识为所述目标叶子设备对应的路由ID时,根据所述目标叶子设备对应的路由ID确定所述组播路由信息满足优选条件。When the device routing identifier is the routing ID corresponding to the target leaf device, determining that the multicast routing information meets a preferred condition according to the routing ID corresponding to the target leaf device.
- 根据权利要求11所述的网络设备,其特征在于,所述处理单元具体用于:The network device according to claim 11, wherein the processing unit is specifically configured to:当所述设备路由标识为所述目标叶子设备所优选接收组播数据的所述第二根设备的路由ID时,根据所述第二根设备的路由ID确定所述组播路由信息满足优选条件。When the device routing identifier is a routing ID of the second root device that the target leaf device preferably receives the multicast data, determining, according to the routing ID of the second root device, that the multicast routing information meets a preferred condition .
- 根据权利要求11至13中任一项所述的网络设备,其特征在于,所述处理单元具体用于:The network device according to any one of claims 11 to 13, wherein the processing unit is specifically configured to:确定所述组播路由信息的VPN实例标识与所述第一根设备的MVPN ID是否相同,所述MVPN ID为第一根设备的MVPN对应的ID地址;Determining whether the VPN instance identifier of the multicast routing information is the same as the MVPN ID of the first root device, where the MVPN ID is an ID address corresponding to the MVPN of the first root device;若相同,则将所述组播路由信息添加到目标路由表中,所述目标路由表为所述第一根设备的VPN路由表中的其中一个,所述目标路由表用于指示所述第一根设备向所述目标叶子设备发送所述组播数据。If the same, the multicast routing information is added to the target routing table, where the target routing table is one of the VPN routing tables of the first root device, and the target routing table is used to indicate the first A device transmits the multicast data to the target leaf device.
- 根据权利要求14所述的网络设备,其特征在于,所述发送单元具体用于:The network device according to claim 14, wherein the sending unit is specifically configured to:向所述目标叶子设备发送组播数据接收消息,所述组播数据接收消息用于指示所述目标叶子设备接收所述组播数据;Sending a multicast data receiving message to the target leaf device, where the multicast data receiving message is used to indicate that the target leaf device receives the multicast data;接收所述目标叶子设备发送的组播数据接收响应消息,所述组播数据接收响应消息用于指示所述目标叶子设备需要接收所述组播数据;Receiving, by the target leaf device, a multicast data receiving response message, where the multicast data receiving response message is used to indicate that the target leaf device needs to receive the multicast data;向发送所述组播数据接收响应消息对应的所述目标叶子设备发送所述组播数据。And transmitting the multicast data to the target leaf device corresponding to the sending the multicast data receiving response message.
- 一种网络设备,其特征在于,所述网络设备应用于MVPN,所述MVPN包括路由反射器、M个根设备和N个叶子设备,所述M为大于1的整数,所述N为大于或等于2的整数, 所述N个叶子设备在发送组播加入报文时,分别优选了所述M个根设备中的不同的根设备,所述网络设备为所述路由反射器,所述网络设备包括:A network device, wherein the network device is applied to an MVPN, where the MVPN includes a route reflector, M root devices, and N leaf devices, where the M is an integer greater than 1, and the N is greater than or An integer equal to 2, wherein the N leaf devices respectively select different root devices of the M root devices when the multicast join message is sent, where the network device is the route reflector, the network Equipment includes:接收单元,用于接收目标叶子设备发送的第一组播加入报文,所述第一组播加入报文包括组播路由信息,所述组播路由信息中包括设备路由标识,所述目标叶子设备为所述N个叶子设备中的一个或多个;a receiving unit, configured to receive a first multicast join message sent by the target leaf device, where the first multicast join message includes multicast routing information, where the multicast routing information includes a device routing identifier, and the target leaf The device is one or more of the N leaf devices;处理单元,用于根据所述设备路由标识确定所述第一组播加入报文都满足前发条件;a processing unit, configured to determine, according to the device routing identifier, that the first multicast join message meets a pre-condition;发送单元,用于向第一根设备发送第二组播加入报文,所述第一根设备为所述M个根设备中的任意一个,所述第二组播加入报文与所述第一组播加入报文所包含的组播路由信息相同,所述第二组播加入报文用于指示所述第一根设备根据所述设备路由标识确定所述组播路由信息满足优选条件,并确定所述组播路由信息中包含的第二根设备信息与第一根设备信息是否相同,所述第二根设备信息为所述目标叶子设备所优选接收组播数据的第二根设备对应的信息,若相同,则所述第一根设备将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中,在有组播数据下发时,所述第一根设备根据所述VPN路由表向所述目标叶子设备发送所述组播数据。a sending unit, configured to send a second multicast join message to the first root device, where the first root device is any one of the M root devices, and the second multicast join message and the first The multicast routing information included in a multicast join message is the same, and the second multicast join message is used to indicate that the first root device determines that the multicast routing information meets a preferred condition according to the device routing identifier. And determining whether the second root device information included in the multicast routing information is the same as the first root device information, where the second root device information is the second root device that the target leaf device preferably receives the multicast data. If the information is the same, the first root device adds the multicast routing information of the target leaf device to the virtual private network VPN routing table of the first root device, and when the multicast data is delivered, The first root device sends the multicast data to the target leaf device according to the VPN routing table.
- 根据权利要求16所述的网络设备,其特征在于,所述处理单元具体用于:The network device according to claim 16, wherein the processing unit is specifically configured to:当所述设备路由标识为所述目标叶子设备对应的路由ID时,根据所述目标叶子设备对应的路由ID确定所述第一组播加入报文都满足前发条件。When the device routing identifier is the routing ID corresponding to the target leaf device, the first multicast joining message is determined to meet the pre-condition according to the routing ID corresponding to the target leaf device.
- 根据权利要求16所述的网络设备,其特征在于,所述处理单元具体用于:The network device according to claim 16, wherein the processing unit is specifically configured to:当所述设备路由标识为所述目标叶子设备优选接收组播数据的所述第二根设备的路由ID时,根据所述第二根设备的路由ID确定所述第一组播加入报文都满足前发条件。Determining, according to the routing ID of the second root device, the first multicast join message, when the device routing identifier is a routing ID of the second root device that the target leaf device preferably receives the multicast data. Meet the pre-conditions.
- 根据权利要求17中任一项所述的网络设备,其特征在于,所述发送单元具体用于:The network device according to any one of claims 17 to 17, wherein the sending unit is specifically configured to:当所述设备路由标识为所述目标叶子设备对应的路由ID时,所述第二组播加入报文为每个所述目标叶子设备分别发送的所述第一组播加入报文;When the device routing identifier is a routing ID corresponding to the target leaf device, the second multicast joining message is the first multicast joining message sent by each of the target leaf devices.向第一根设备发送所述每个目标叶子设备分别发送的第一组播加入报文。And sending, by the first root device, the first multicast join message sent by each target leaf device.
- 根据权利要求18所述的网络设备,其特征在于,所述发送单元具体用于:The network device according to claim 18, wherein the sending unit is specifically configured to:当所述设备路由标识为所述目标叶子设备优选接收组播数据的所述第二根设备的路由ID时,所述第二组播加入报文为满足前发条件的所述第一组播加入报文中的一个;When the device routing identifier is the routing ID of the second root device that the target leaf device preferably receives the multicast data, the second multicast join message is the first multicast that meets the pre-condition Join one of the messages;向所述第一根设备发送满足前发条件的所述第一组播加入报文中的一个。Sending, to the first root device, one of the first multicast join messages that meet the pre-conditions.
- 一种组播路由系统,所述组播路由系统应用于MVPN,所述MVPN包括M个根设备和N个叶子设备,所述M为大于1的整数,所述N为大于或等于2的整数,所述N个叶子设备在发送组播加入报文时,分别优选了所述M个根设备中的不同的根设备目标叶子设备和第一根设备,包括:A multicast routing system, the multicast routing system is applied to an MVPN, the MVPN includes M root devices and N leaf devices, the M is an integer greater than 1, and the N is an integer greater than or equal to 2. And the N-th leaf device, when sending the multicast join message, respectively, the different root device target leaf device and the first root device of the M root devices, including:所述目标叶子设备用于向所述第一根设备发送第一组播加入报文,所述第一组播加入报文包括组播路由信息,所述组播路由信息中包括设备路由标识,所述目标叶子设备为所述N个叶子设备中的一个或多个,所述第一根设备为所述M个根设备中的任意一个;The target leaf device is configured to send a first multicast join message to the first root device, where the first multicast join message includes multicast routing information, where the multicast routing information includes a device routing identifier. The target leaf device is one or more of the N leaf devices, and the first root device is any one of the M root devices;所述第一根设备用于:The first root device is used to:接收所述目标叶子设备发送的所述第一组播加入报文;Receiving the first multicast join message sent by the target leaf device;根据所述设备路由标识确定所述组播路由信息满足优选条件;Determining, according to the device routing identifier, that the multicast routing information meets a preferred condition;确定所述组播路由信息中包含的第二根设备信息与第一根设备信息是否相同,所述第二根设备信息为所述目标叶子设备所优选接收组播数据的第二根设备对应的信息;Determining whether the second root device information included in the multicast routing information is the same as the first root device information, where the second root device information is corresponding to the second root device that the target leaf device preferably receives the multicast data. information;若相同,则将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中;If the same, the multicast routing information of the target leaf device is added to the virtual private network VPN routing table of the first root device;在有组播数据下发时,根据所述VPN路由表向所述目标叶子设备发送所述组播数据。When the multicast data is delivered, the multicast data is sent to the target leaf device according to the VPN routing table.
- 根据权利要求21所述的组播路由系统,所述MVPN还包括路由反射器,所述组播路由系统还包括:The multicast routing system of claim 21, the MVPN further comprising a route reflector, the multicast routing system further comprising:所述路由反射器用于:The route reflector is used to:接收目标叶子设备发送的第一组播加入报文,所述第一组播加入报文包括组播路由信息,所述组播路由信息中包括设备路由标识,所述目标叶子设备为所述N个叶子设备中的一个或多个;Receiving a first multicast join message sent by the target leaf device, where the first multicast join message includes multicast routing information, where the multicast routing information includes a device routing identifier, and the target leaf device is the N One or more of the leaf devices;根据所述设备路由标识确定所述第一组播加入报文都满足前发条件;Determining, according to the device routing identifier, that the first multicast join message meets a pre-condition;向第一根设备发送第二组播加入报文,所述第一根设备为所述M个根设备中的任意一个,所述第二组播加入报文与所述第一组播加入报文所包含的组播路由信息相同;Sending a second multicast join message to the first root device, where the first root device is any one of the M root devices, the second multicast join message and the first multicast join report The multicast routing information contained in the text is the same;所述第一根设备还用于:The first root device is further configured to:接收所述第二组播加入报文;Receiving the second multicast join message;根据所述设备路由标识确定所述组播路由信息满足优选条件;Determining, according to the device routing identifier, that the multicast routing information meets a preferred condition;确定所述组播路由信息中包含的第二根设备信息与第一根设备信息是否相同,所述第二根设备信息为所述目标叶子设备所优选接收组播数据的第二根设备对应的信息;Determining whether the second root device information included in the multicast routing information is the same as the first root device information, where the second root device information is corresponding to the second root device that the target leaf device preferably receives the multicast data. information;若相同,则将所述目标叶子设备的组播路由信息添加到所述第一根设备的虚拟专用网VPN路由表中;If the same, the multicast routing information of the target leaf device is added to the virtual private network VPN routing table of the first root device;在有组播数据下发时,根据所述VPN路由表向所述目标叶子设备发送所述组播数据。When the multicast data is delivered, the multicast data is sent to the target leaf device according to the VPN routing table.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810210276.0A CN110278156B (en) | 2018-03-14 | 2018-03-14 | Multicast routing processing method, network equipment and route reflector |
CN201810210276.0 | 2018-03-14 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019174552A1 true WO2019174552A1 (en) | 2019-09-19 |
Family
ID=67908555
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/077703 WO2019174552A1 (en) | 2018-03-14 | 2019-03-11 | Multicast route processing method, network device, and route reflector |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110278156B (en) |
WO (1) | WO2019174552A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112822097A (en) * | 2019-11-15 | 2021-05-18 | 华为技术有限公司 | Message forwarding method, first network device and first device group |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112887115B (en) * | 2019-11-29 | 2022-11-18 | 华为技术有限公司 | Method and device for configuring static multicast group |
CN113132230A (en) * | 2019-12-31 | 2021-07-16 | 北京华为数字技术有限公司 | Method, device and computer storage medium for sending message |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7519010B1 (en) * | 2004-08-30 | 2009-04-14 | Juniper Networks, Inc. | Inter-autonomous system (AS) multicast virtual private networks |
CN103152280A (en) * | 2013-03-12 | 2013-06-12 | 福建星网锐捷网络有限公司 | Multicast stream transmission method, device and inlet edge equipment |
CN104092554A (en) * | 2014-07-31 | 2014-10-08 | 杭州华三通信技术有限公司 | Multicast distribution tree establishment method and device |
CN104378217A (en) * | 2014-11-26 | 2015-02-25 | 中国联合网络通信集团有限公司 | Method and device for determining multicast group data |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101729274B (en) * | 2009-06-18 | 2012-05-23 | 中兴通讯股份有限公司 | Method for realizing multicast in PBB_VPLS network |
CN105743780B (en) * | 2014-12-09 | 2019-05-28 | 华为技术有限公司 | Message transmitting method and device |
US9300581B1 (en) * | 2015-02-03 | 2016-03-29 | Google Inc. | Mesh network addressing |
CN104717143B (en) * | 2015-03-12 | 2018-03-02 | 华为技术有限公司 | For returning the method and apparatus of scene muticast data transmission more |
-
2018
- 2018-03-14 CN CN201810210276.0A patent/CN110278156B/en active Active
-
2019
- 2019-03-11 WO PCT/CN2019/077703 patent/WO2019174552A1/en active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7519010B1 (en) * | 2004-08-30 | 2009-04-14 | Juniper Networks, Inc. | Inter-autonomous system (AS) multicast virtual private networks |
CN103152280A (en) * | 2013-03-12 | 2013-06-12 | 福建星网锐捷网络有限公司 | Multicast stream transmission method, device and inlet edge equipment |
CN104092554A (en) * | 2014-07-31 | 2014-10-08 | 杭州华三通信技术有限公司 | Multicast distribution tree establishment method and device |
CN104378217A (en) * | 2014-11-26 | 2015-02-25 | 中国联合网络通信集团有限公司 | Method and device for determining multicast group data |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112822097A (en) * | 2019-11-15 | 2021-05-18 | 华为技术有限公司 | Message forwarding method, first network device and first device group |
Also Published As
Publication number | Publication date |
---|---|
CN110278156A (en) | 2019-09-24 |
CN110278156B (en) | 2020-12-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10536324B2 (en) | Per-prefix LFA FRR with bit indexed explicit replication | |
US8339973B1 (en) | Multicast traceroute over MPLS/BGP IP multicast VPN | |
EP3226491B1 (en) | Hot root standby support for multicast | |
US9860169B1 (en) | Neighbor resolution for remote EVPN hosts in IPV6 EVPN environment | |
US10033539B1 (en) | Replicating multicast state information between multi-homed EVPN routing devices | |
WO2019165900A1 (en) | Method and device for processing multicast data packet | |
WO2016062106A1 (en) | Packet processing method, device and system | |
US9584331B2 (en) | Methods and systems for transmitting broadcast data | |
CN110661701B (en) | Communication method, equipment and system for avoiding loop | |
WO2020168854A1 (en) | Evpn multicast method, apparatus and system | |
US10050867B2 (en) | Methods and systems for transmitting broadcast data | |
WO2019174552A1 (en) | Multicast route processing method, network device, and route reflector | |
WO2018068588A1 (en) | Method and software-defined networking (sdn) controller for providing multicast service | |
WO2013107245A1 (en) | Method, device and system for implementing multicast in transparent interconnection of lots of links (trill) campus | |
US8675658B2 (en) | Using multiple IGMP queriers in a layer 2 network | |
US10374826B2 (en) | Methods and systems for transmitting broadcast data | |
US20240235890A1 (en) | EVPN Tenant Domain Transit Network for Multicast Traffic | |
US11805049B2 (en) | Communication method and communications device | |
WO2021093463A1 (en) | Packet forwarding method, first network device, and first device group | |
WO2019128612A1 (en) | Method and device for processing routing protocol packet | |
WO2014169856A1 (en) | Multicast communication method and aggregation switch | |
WO2009076839A1 (en) | A packet transmission method, system and device between pe devices | |
WO2021147377A1 (en) | Multicast packet detection method, network device, and system | |
US9654304B2 (en) | Method and apparatus for sending transparent interconnection of lots of links data frame | |
CN109756412A (en) | A kind of data message forwarding method and equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19767403 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19767403 Country of ref document: EP Kind code of ref document: A1 |