[go: up one dir, main page]

WO2019174552A1 - Procédé de traitement de route de multidiffusion, dispositif de réseau, et réflecteur de voie - Google Patents

Procédé de traitement de route de multidiffusion, dispositif de réseau, et réflecteur de voie Download PDF

Info

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
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/077703
Other languages
English (en)
Chinese (zh)
Inventor
孙春霞
张耀坤
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2019174552A1 publication Critical patent/WO2019174552A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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

La présente invention concerne un procédé de traitement de route de multidiffusion. Le procédé proposé par des modes de réalisation de la présente invention comprend les étapes suivantes : un premier dispositif racine reçoit un premier message de rattachement de multidiffusion envoyé par un dispositif feuille cible, ou reçoit un second message de rattachement de multidiffusion envoyé par un réflecteur de route, le premier message de rattachement de multidiffusion contenant des informations de route de multidiffusion, les informations de route de multidiffusion comprenant un identificateur de route de dispositif, et des informations de route de multidiffusion dans le second message de rattachement de multidiffusion étant identiques aux informations de route de multidiffusion du premier message de rattachement de multidiffusion ; le premier dispositif racine détermine, d'après l'identificateur de route de dispositif, que les informations de route de multidiffusion satisfont une condition préférentielle ; le premier dispositif racine détermine si des secondes informations de dispositif racine comprises dans les informations de route de multidiffusion sont identiques aux premières informations de dispositif racine ; dans l'affirmative, le premier dispositif racine ajoute les informations de route de multidiffusion du dispositif feuille cible à une table de routage VPN du premier dispositif racine ; le premier dispositif racine envoie des données de multidiffusion au dispositif feuille cible, d'après la table de routage VPN. La solution de la présente invention peut garantir que chaque dispositif feuille cible reçoive des données de multidiffusion.
PCT/CN2019/077703 2018-03-14 2019-03-11 Procédé de traitement de route de multidiffusion, dispositif de réseau, et réflecteur de voie Ceased WO2019174552A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810210276.0A CN110278156B (zh) 2018-03-14 2018-03-14 组播路由处理方法、网络设备以及路由反射器
CN201810210276.0 2018-03-14

Publications (1)

Publication Number Publication Date
WO2019174552A1 true WO2019174552A1 (fr) 2019-09-19

Family

ID=67908555

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/077703 Ceased WO2019174552A1 (fr) 2018-03-14 2019-03-11 Procédé de traitement de route de multidiffusion, dispositif de réseau, et réflecteur de voie

Country Status (2)

Country Link
CN (1) CN110278156B (fr)
WO (1) WO2019174552A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822097A (zh) * 2019-11-15 2021-05-18 华为技术有限公司 报文转发的方法、第一网络设备以及第一设备组

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112887115B (zh) * 2019-11-29 2022-11-18 华为技术有限公司 一种用于配置静态组播组的方法及装置
CN113132230A (zh) * 2019-12-31 2021-07-16 北京华为数字技术有限公司 发送报文的方法、设备及计算机存储介质
CN115733796B (zh) * 2021-08-24 2025-07-11 华为技术有限公司 通信方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
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 (zh) * 2013-03-12 2013-06-12 福建星网锐捷网络有限公司 组播流的传输方法、装置和入口边缘设备
CN104092554A (zh) * 2014-07-31 2014-10-08 杭州华三通信技术有限公司 组播分发树建立方法及装置
CN104378217A (zh) * 2014-11-26 2015-02-25 中国联合网络通信集团有限公司 确定组播组数据的方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729274B (zh) * 2009-06-18 2012-05-23 中兴通讯股份有限公司 Pbb_vpls网络中实现组播的方法
CN105743780B (zh) * 2014-12-09 2019-05-28 华为技术有限公司 报文传输方法及装置
US9385953B1 (en) * 2015-02-03 2016-07-05 Google Inc. Mesh network addressing
CN104717143B (zh) * 2015-03-12 2018-03-02 华为技术有限公司 用于多归场景组播数据传输的方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
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 (zh) * 2013-03-12 2013-06-12 福建星网锐捷网络有限公司 组播流的传输方法、装置和入口边缘设备
CN104092554A (zh) * 2014-07-31 2014-10-08 杭州华三通信技术有限公司 组播分发树建立方法及装置
CN104378217A (zh) * 2014-11-26 2015-02-25 中国联合网络通信集团有限公司 确定组播组数据的方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822097A (zh) * 2019-11-15 2021-05-18 华为技术有限公司 报文转发的方法、第一网络设备以及第一设备组

Also Published As

Publication number Publication date
CN110278156B (zh) 2020-12-22
CN110278156A (zh) 2019-09-24

Similar Documents

Publication Publication Date Title
US8339973B1 (en) Multicast traceroute over MPLS/BGP IP multicast VPN
EP3226491B1 (fr) Support d'attente segment racine chaud pour multidiffusion
CN103685022B (zh) 报文转发方法及服务提供商网络边缘设备
US10033539B1 (en) Replicating multicast state information between multi-homed EVPN routing devices
WO2019174552A1 (fr) Procédé de traitement de route de multidiffusion, dispositif de réseau, et réflecteur de voie
WO2016062106A1 (fr) Procédé, dispositif et système de traitement de paquets
US10050867B2 (en) Methods and systems for transmitting broadcast data
WO2019165900A1 (fr) Procédé et dispositif de traitement d'un paquet de données de multidiffusion
WO2020168854A1 (fr) Procédé, appareil, et système de multidiffusion evpn
US10374826B2 (en) Methods and systems for transmitting broadcast data
WO2018068588A1 (fr) Procédé et contrôleur de réseautage défini par logiciel (sdn) destinés à fournir un service de multidiffusion
US20250350556A1 (en) Traffic Handling for EVPN E-Tree
US8675658B2 (en) Using multiple IGMP queriers in a layer 2 network
CN105743780A (zh) 报文传输方法及装置
WO2021093463A1 (fr) Procédé de transfert de paquets, premier dispositif de réseau et premier groupe de dispositifs
CN109756412B (zh) 一种数据报文转发方法以及设备
WO2021147377A1 (fr) Procédé de détection de paquet de multidiffusion, dispositif de réseau, et système
US11805049B2 (en) Communication method and communications device
WO2019128612A1 (fr) Procédé et dispositif permettant de traiter un paquet de protocole de routage
WO2022033449A1 (fr) Procédé d'envoi d'un message à multidiffusion, et procédé et appareil pour acquérir une entrée de table de transfert
WO2014169856A1 (fr) Procédé de communication en multidiffusion et commutateur d'agrégation
WO2009076839A1 (fr) Procédé, système et dispositif de transmission par paquets entre dispositifs pe
CN103825794B (zh) 多链路透明互联数据帧发送方法及装置
CN113328943B (zh) 一种路由匹配方法、信息发送方法及装置
US20240364615A1 (en) BUM Traffic Handling for EVPN E-Tree via Network Convergence

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