WO2021228090A1 - 用于发送组播报文的方法和装置 - Google Patents

用于发送组播报文的方法和装置 Download PDF

Info

Publication number
WO2021228090A1
WO2021228090A1 PCT/CN2021/093063 CN2021093063W WO2021228090A1 WO 2021228090 A1 WO2021228090 A1 WO 2021228090A1 CN 2021093063 W CN2021093063 W CN 2021093063W WO 2021228090 A1 WO2021228090 A1 WO 2021228090A1
Authority
WO
WIPO (PCT)
Prior art keywords
identifier
area
intermediate device
address
next hop
Prior art date
Application number
PCT/CN2021/093063
Other languages
English (en)
French (fr)
Inventor
谢经荣
闫刚
耿雪松
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21804760.3A priority Critical patent/EP4142227A4/en
Publication of WO2021228090A1 publication Critical patent/WO2021228090A1/zh
Priority to US17/984,506 priority patent/US20230081052A1/en

Links

Images

Classifications

    • 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/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • This application relates to the field of communication technology, and more specifically, to a method and device for sending multicast messages.
  • Bit Index Explicit Replication (BIER for short) is a commonly used multicast architecture.
  • the BIER header encapsulation format and encapsulation method are defined in the Internet Engineering Task Force (IETF) standard.
  • the BIER encapsulation may be based on, for example, Multi-Protocol Label Switching (MPLS for short), Ethernet and Internet protocol version 6 (IPv6 for short), etc.
  • MPLS Multi-Protocol Label Switching
  • IPv6 Internet protocol version 6
  • AS autonomous System
  • the multicast source can communicate with the Provider Edge (PE) devices of the backbone network, and multiple multicast receivers can communicate with multiple PE devices in the metropolitan area network. .
  • the PE device communicating with the multicast source can send multicast packets to the PE device communicating with the multicast receiver through the Autonomous System Boundary Router (ASBR for short) of the backbone network.
  • ASBR Autonomous System Boundary Router
  • any PE device can be assigned a Bit Forwarding Router (BFR) identifier (BFR-id).
  • the PE device communicating with the multicast receiver When the PE device communicating with the multicast receiver is in a different AS domain and needs to receive multicast packets from a certain multicast source, the PE device communicating with the multicast source needs to copy multiple multicast packets and send them to When the AS domain where the PE device communicating with the multicast receiver is located sends multicast packets, there will be a problem of wasting network resources.
  • This application provides a method and device for sending multicast messages, which can save network resources.
  • a method for sending multicast messages includes: the intermediate device obtains the identifier of the area corresponding to the multicast packet based on the multicast packet from the entrance device; the intermediate device obtains the address of the next hop device based on the area identifier and forwarding entry, and the forwarding entry includes The identification of the area and the address of the next hop device; the intermediate device sends multicast packets based on the address of the next hop device.
  • the intermediate device acts as a transit node between one or more egress devices and the ingress device, and can forward the multicast message according to the determined area identifier after receiving the multicast message of the ingress device.
  • This method will no longer copy and forward multicast packets from the PE device communicating with the multicast source as in the usual cross-domain multicast scenario, but locate the intermediate device as a transit node based on the area identifier and send it by the intermediate device
  • the next-hop device implements multicast packet replication and forwarding operations, which saves traffic between the ingress device and the intermediate device (less network resources are taken up to send replicated multicast packets).
  • the traffic between the intermediate device and the next-hop device can be further saved (less network resources are taken up to send duplicate multicast packets).
  • the area includes one or more AS domains.
  • the next hop device can be the egress device or the ASBR of the AS domain where the egress device is located.
  • the egress device is an edge device that can communicate with the multicast receiver, and can also be called a bit forwarding egress router (BFER).
  • BFER bit forwarding egress router
  • the ingress device can be an edge device that communicates with the multicast source, and can also be referred to as a bit forwarding ingress router (BFIR).
  • BFIR bit forwarding ingress router
  • the intermediate device and the entrance device are devices in the BIER cross-domain network scenario.
  • the multicast packet includes the identifier of the area
  • the intermediate device obtains the identifier of the area corresponding to the multicast packet based on the multicast packet from the ingress device, including: the intermediate device obtains the area from the multicast packet Of the logo.
  • the multicast message includes the identifier of the intermediate device, and the intermediate device is based on the multicast message from the ingress device, and obtaining the identifier of the area corresponding to the multicast message includes: the intermediate device is based on the identifier in the multicast message The identifier of the intermediate device obtains the identifier of the area corresponding to the identifier of the intermediate device.
  • a corresponding relationship may be pre-configured on the intermediate device, and the corresponding relationship includes the identifier of the intermediate device and the identifier of the area. This method has better compatibility, and there is no need to make too many improvements or processing on multicast packets.
  • the method further includes: the intermediate device receives the address of the next hop device and the identifier of the area to which the next hop device belongs from the next hop device; the intermediate device is based on the area identifier and the next hop The address of the device to obtain the forwarding entry.
  • the method further includes: the intermediate device receives the identity of the next hop device and the identity of the area to which the next hop device belongs from the next hop device; the intermediate device is based on the identity of the next hop device, Obtain the address of the next hop device; the intermediate device obtains the forwarding entry based on the area identifier and the address of the next hop device.
  • the method further includes: the intermediate device receives the range of the BFR identifier of the forwarding router in the destination AS domain sent by the next hop device, and the destination AS domain is the AS domain to which the next hop device contained in the area belongs.
  • the forwarding table entry also includes the range of the BFR identifier in the destination AS domain.
  • the multicast message further includes the range of the BFR identifier
  • the method further includes: the intermediate device determines the forwarding entry based on the area identifier and the range of the BFR identifier.
  • the method further includes: the intermediate device sending the address of the intermediate device and the identifier of the area to which the intermediate device belongs to the entrance device.
  • the method further includes: the intermediate device sends to the entrance device the range of the BFR identifier in the AS domain to which the intermediate device belongs, and the AS domain to which the intermediate device belongs is included in the area to which the intermediate device belongs.
  • a method for sending multicast messages includes: the entrance device obtains the identifier of the region corresponding to the received multicast message; the entrance device obtains the address of the intermediate device used to forward the multicast message to the region based on the region identifier and forwarding table entry, and the forwarding table
  • the items include the identification of the area and the address of the intermediate device; the ingress device sends a multicast message based on the address of the intermediate device.
  • the entrance device can send the multicast message to the intermediate device according to the area identification, instead of copying and forwarding the multicast message as in the usual cross-domain multicast scenario, saving it and the intermediate device
  • the traffic between (less network resources are used to send replicated multicast packets).
  • the intermediate device and the entrance device are devices in the BIER cross-domain network scenario.
  • the method further includes: the entrance device receives the address of the intermediate device and the region identifier sent by the intermediate device; the entrance device obtains the forwarding entry based on the address of the intermediate device and the region identifier.
  • the method further includes: the entrance device receives the identifier of the intermediate device and the region identifier sent by the intermediate device; the entrance device determines the address of the intermediate device based on the identifier of the intermediate device; the entrance device is based on the intermediate device The address and area identification, obtain the forwarding entry.
  • the method further includes: the ingress device receives the range of the BFR identifier in the destination autonomous system AS domain sent by the intermediate device, the destination AS domain is the AS domain to which the multicast packets contained in the area need to be sent, and forwarding
  • the published item also includes the scope of the BFR mark in the destination AS domain.
  • the method further includes: the ingress device determines the forwarding entry based on the range of the BFR identifier in the destination AS domain and the identifier of the area.
  • the multicast message contains the identifier of the area
  • the ingress device obtaining the identifier of the area corresponding to the received multicast message includes: the ingress device obtains the identifier of the area from the multicast message; or in the multicast message Contains the identifier of the intermediate device, the multicast packet contains the identifier of the area, and the ingress device obtains the identifier of the area corresponding to the received multicast packet.
  • the ingress device obtains the identifier corresponding to the intermediate device based on the identifier of the intermediate device in the multicast packet. The ID of the area.
  • a method for generating forwarding entries includes: an intermediate device obtains from a next hop device the identifier of the area to which the next hop device belongs and the address of the next hop device; the intermediate device obtains a forwarding entry based on the area identifier and the address of the next hop device .
  • the intermediate device can obtain the forwarding entry for forwarding the multicast message according to the parameters obtained from the next-hop device, which reduces the complexity of manual configuration after the network structure changes, and can refresh more flexibly and quickly The entry used to forward multicast packets.
  • the obtaining, by the intermediate device, the identifier of the area to which the next hop device belongs and the address of the next hop device from the next hop device includes: the intermediate device receiving the next hop device The address of the next hop device and the identifier of the area sent by the hop device.
  • the obtaining, by the intermediate device, the identifier of the area to which the next hop device belongs and the address of the next hop device from the next hop device includes: the intermediate device receiving the next hop device The identifier of the next hop device and the identifier of the area sent by the hop device; the intermediate device obtains the address of the next hop device based on the identifier of the next hop device.
  • the identifier of the next hop device may be other information or parameters used to identify the next hop device except the address.
  • the intermediate device may convert the identifier of the next hop device into the address of the next hop device according to a preset algorithm, or the intermediate device may obtain the next hop device according to a corresponding relationship and the identifier of the next hop device.
  • the address of the hop device, and the corresponding relationship includes the identifier of the next hop device and the address of the next hop device.
  • the method further includes: the intermediate device receives the range of the BFR identifier of the forwarding router in the destination AS domain sent by the next hop device, and the destination AS domain is the AS domain to which the next hop device contained in the area belongs.
  • the forwarding table entry also includes the range of the BFR identifier in the destination AS domain.
  • the intermediate device after the intermediate device generates the forwarding entry, it can use the forwarding entry to send the multicast message from the ingress device, which saves the traffic between the ingress device and the intermediate device (less network resources are taken up to send replication Multicast packets).
  • the next-hop device when the next-hop device is not an egress device, the traffic between the intermediate device and the next-hop device can be further saved (less network resources are taken up to send duplicate multicast packets).
  • a method for generating forwarding entries includes: the entrance device obtains the address of the intermediate device and the identifier of the area from the intermediate device; the entrance device obtains the forwarding entry based on the address of the intermediate device and the identifier of the area.
  • the ingress device can obtain the forwarding entry for forwarding the multicast message according to the parameters obtained from the intermediate device, which reduces the complexity of manual configuration after the network structure changes, and can refresh more flexibly and quickly. Entries for forwarding multicast packets.
  • the ingress device acquiring the address of the intermediate device and the identifier of the area from the intermediate device includes: the ingress device receives the address of the intermediate device and the address of the area sent by the intermediate device. Mentioned identification.
  • the ingress device acquiring the address of the intermediate device and the identifier of the area from the intermediate device includes: the ingress device receives the identifier of the intermediate device and the identifier of the area sent by the intermediate device.
  • the identifier; the entrance device determines the address of the intermediate device according to the identifier of the intermediate device.
  • the identifier of the intermediate device may be other information or parameters used to identify the intermediate device except the address.
  • the entry device may convert the identifier of the intermediate device into the address of the intermediate device according to a preset algorithm, or the entry device may obtain the address of the intermediate device according to a correspondence relationship and the identity of the intermediate device. Including the identification of the intermediate hop device and the address of the intermediate hop device.
  • the method further includes: the ingress device receives the range of the BFR identifier in the destination autonomous system AS domain sent by the intermediate device, the destination AS domain is the AS domain to which the multicast packets contained in the area need to be sent, and forwarding
  • the published item also includes the scope of the BFR mark in the destination AS domain.
  • the entry device after the entry device generates the forwarding entry, it can use the forwarding entry to send multicast messages to the intermediate device, which saves the traffic between the entry device and the intermediate device (less network resources are taken up to send duplicated packets). Multicast packets).
  • a device for sending a multicast message is provided, and the device is installed in an intermediate device.
  • the device includes a module for implementing the function corresponding to the method provided by the foregoing first aspect or any one of the possible implementation manners of the first aspect; or the device includes a module for implementing the foregoing third aspect or any one of the possible implementation manners of the third aspect.
  • the method corresponds to the functional module.
  • a device for sending multicast messages is provided, and the device is installed in an entrance device.
  • the device includes a module for implementing the function corresponding to the method provided in the foregoing second aspect or any one of the possible implementation manners of the second aspect; or the device includes the module for implementing the foregoing fourth aspect or any one of the possible implementation manners of the fourth aspect.
  • the method corresponds to the function module. .
  • a device in the seventh aspect, includes a processor and a memory storing instructions.
  • the device executes the method provided by the first aspect or any one of the possible implementation manners of the first aspect; or when the instruction is executed by the processor Make the device execute the method provided in the second aspect or any one of the possible implementation manners of the second aspect; or when the instruction is executed by the processor, make the device execute the third aspect or any one of the possible implementation manners of the third aspect.
  • the device executes the method provided in the fourth aspect or any one of the possible implementation manners of the fourth aspect.
  • a computer-readable storage medium on which instructions are stored, which when executed by a processor in a device, cause the device to execute the first aspect or any one of the possible implementation manners of the first aspect.
  • the device executes the method provided in the second aspect or any one of the possible implementations of the second aspect; or, when the instruction is executed by the processor, the device executes the third Or the method provided in any possible implementation manner of the fourth aspect or the third aspect; or when the instruction is executed by a processor, the device executes the method provided in the fourth aspect or any one of the possible implementation manners of the fourth aspect.
  • a system in a ninth aspect, includes the device described in the fifth aspect and the device described in the sixth aspect.
  • FIG. 1 shows a schematic diagram of a network scenario provided by an embodiment of the present application
  • FIG. 2 shows a schematic diagram of the interaction process of a multicast message provided by an embodiment of the present application
  • Figure 3 shows a multicast scenario provided by an embodiment of the present application
  • Figure 4 shows another multicast scenario provided by an embodiment of the present application
  • Figure 5 shows another multicast scenario provided by an embodiment of the present application
  • FIG. 6 shows a schematic structural diagram of an apparatus for sending multicast packets provided by an embodiment of the present application
  • FIG. 7 shows a schematic structural diagram of an apparatus for sending multicast packets provided by an embodiment of the present application.
  • Fig. 8 shows a schematic structural diagram of a device provided by an embodiment of the present application.
  • the term "entry device” in the embodiments of the present application refers to a device that is close to the multicast source and can communicate with the multicast source in the cross-domain multicast process.
  • the ingress device may include a PE device in the AS domain where the multicast source is located.
  • the entrance device can be located in the backbone network or in the metropolitan area network.
  • the ingress device may perform BIER encapsulation on the multicast message from the multicast source.
  • the term "egress device” in the embodiments of the present application refers to a device that is located close to the multicast receiver and can communicate with the multicast receiver during the cross-domain multicast process.
  • the egress device may include a PE device in the AS domain to which the multicast receiver communicates or belongs.
  • the egress device can be located in a metropolitan area network.
  • the egress device may perform BIER decapsulation on the received multicast message.
  • the term "intermediate device" in the embodiments of the present application refers to a device used to implement multicast forwarding between an ingress device and an egress device in a cross-domain multicast process.
  • the intermediate device may include the ASBR in the backbone network. The intermediate device can also be located in the metropolitan area network.
  • each PE device can be distinguished by BFR-id.
  • the BFR-id of the PE device is uniformly allocated, so the number of supported PE devices is limited by the number of bits of the BFR-id value. For example, if the BFR-id value is 16 bits, it cannot support more than 65535 PE devices.
  • the BFR-id of the PE device can be allocated independently, so it can support more PE devices.
  • the ingress device needs to forward multicast packets to all AS domains. Especially as the network expands, more and more AS domains will be added. Even if the number of PE devices in a certain AS domain is small, the ingress device needs to forward to the AS domain, which will cause huge traffic duplication waste.
  • an area includes one or more AS domains.
  • the intermediate device obtains one or more forwarding entries corresponding to the area, and any forwarding entry includes an identifier (ID) of the area and an associated address of each AS domain in the area.
  • ID can be the address of any suitable device associated with the AS domain. For example, it can be the address of an intermediate device or an egress device in the AS domain, or it can be the address of a device downstream of the intermediate device on the path to the AS domain.
  • the intermediate device determines the ID of the area to which the multicast packet will be sent, and uses the area ID to obtain the first forwarding entry.
  • the first forwarding entry includes the area’s ID and the address of the next hop device corresponding to the destination AS domain. Based on the address of the next hop device in the first forwarding entry.
  • the destination AS domain is the AS domain where the egress device corresponding to the multicast packet is located.
  • the intermediate device sends the multicast packet to the next hop device according to the first forwarding entry.
  • the entry device can obtain one or more forwarding entries corresponding to the area, and any forwarding entry includes the ID of the area and the address of the intermediate device.
  • the ingress device obtains the multicast packet, it determines the ID of the area to which the multicast packet is to be sent, and uses the area ID to obtain a second forwarding entry.
  • the second forwarding entry includes the area ID and the address of the intermediate device.
  • the ingress device sends the multicast message to the intermediate device based on the second forwarding entry.
  • generating forwarding entries for forwarding multicast packets to areas including one or more AS domains can increase the number of supported egress devices in each area on the one hand, and on the other hand On the one hand, the ingress device sends packets to the area where the egress device is located, without sending packets to all AS domains, which reduces the waste of traffic replication.
  • Fig. 1 shows a schematic diagram of a network scenario provided by an embodiment of the present application.
  • the environment 100 is, for example, a part of a communication network, and may include a backbone network and a metropolitan area network.
  • the environment 100 includes an ingress device 105 for sending multicast messages from a multicast source to an egress device (not shown in the figure) that the multicast receiver communicates with.
  • the entrance device 105 may be directly connected or connected to a multicast source (not shown) through a user-side edge device.
  • the entrance device 105 may be a PE device in an AS domain in a backbone network, or a PE device in an AS domain in a metropolitan area network.
  • the environment 100 also includes an intermediate device 110.
  • the intermediate device 110 In the direction from the ingress device 105 to the egress device, the intermediate device 110 is located downstream of the ingress device 105 in a backbone network or a metropolitan area network.
  • the intermediate device 110 is used to forward the multicast message from the ingress device 105 to the egress device.
  • the intermediate device 110 and the ingress device 105 are located in the same AS domain.
  • the entrance device 105 is a PE device in an AS domain in a backbone network or a metropolitan area network
  • the intermediate device 110 may be an ASBR in the AS domain.
  • the intermediate device 110 and the entrance device 105 may be located in different AS domains.
  • the AS domain to which the intermediate device 110 belongs is located downstream of the AS domain to which the ingress device 105 belongs.
  • multiple AS domains can communicate with multicast receivers, where N is greater than or equal to 1.
  • the AS domain 115-1...115-N may be located in a metropolitan area network.
  • the N AS domains 115-1...115-N are divided into M areas 120-1...120-M, where M is an integer greater than or equal to 1 and less than or equal to N.
  • the area 120-1 includes the AS domain 115-1.
  • Area 120-2 includes AS domains 115-2 and 115-3.
  • the area 120-M includes the AS domain 115-N.
  • the area 120-1 includes N AS domains 115-1, 115-2,...
  • AS domain 115-N one or more AS domains included in the area can be configured and/or updated as required.
  • the AS domain 115-1, 115-2, 115-3... or 115-N is also referred to as the AS domain 115, and the area 120-1...120-M is also referred to as the area 120.
  • the intermediate device 110 stores a forwarding table 125, in which each row is a forwarding table entry.
  • the forwarding table 125 includes forwarding entries 130-1, 130-2, 130-3....
  • the individual forwarding entries 130-1, 130-2, and 130-3 in the forwarding table 125 are also referred to as forwarding entries 130 (also referred to as first forwarding entries 130).
  • the column 135 of the forwarding table 125 records the ID of the area (also referred to as "area ID").
  • the column 138 of the forwarding table 125 records the addresses of the next hop devices 140-1, 140-2...140-N belonging to the area identified by the area ID.
  • the address of the next hop device can be an IP address.
  • the next hop devices 140-1, 140-2...140-N are edge devices of the AS domain to which they belong, and can be called ASBRs.
  • the area ID of the area 120-1 recorded in the column 135 of the forwarding table 125 is represented as "2”
  • the edge device of the AS domain 115-1 included in the area 120-1 is the next hop device 140-1.
  • the address of the next hop device 140-1 is represented as "IP address 2a".
  • the area ID of area 120-2 is represented as "3"
  • the edge device of AS domain 115-2 included in area 120-2 is the next hop device 140-2
  • the edge device of AS domain 115-3 included in area 120-2 It is the next hop device 140-3
  • the address of the next hop device 140-2 is represented as "IP address 3a”
  • the address of the next hop device 140-3 is represented as "IP address 4a”.
  • the next hop devices 140-1, 140-2... 140-N are also referred to as devices 140 below.
  • the device 140 may be the ASBR of the AS domain to which it belongs.
  • the device 140 may forward the multicast packet to one or more egress devices (not shown) included in the AS domain to which it belongs.
  • the egress device may be a PE device included in the AS domain to which it belongs.
  • the device 140 may be an egress device of the AS domain to which it belongs.
  • the intermediate device 110 may directly forward the multicast packet to the egress device of the AS domain.
  • the next hop device 140 may be an ASBR in the AS domain of the backbone network.
  • the forwarding table 125 further includes a column 145, which stores the range of the BFR identifier (also referred to as "BFR-id") corresponding to the AS domain to which the device identified by the parameter in the column 138 belongs.
  • BFR-id the BFR-id range of the AS domain 115-1 to which the next hop device 140-1 identified by "IP address 2a" belongs.
  • the BFR-id range that can be allocated to the Bit Forwarding Exit Router (BFER) (also known as the egress device) is 1 to 256.
  • the BFR-id range of the AS domain 115-2 to which the next hop device 140-2 identified by "IP address 3a" belongs is 1 to 44, that is, the BFER in the AS domain 115-2 can be allocated
  • the range of BFR-id is 1 ⁇ 44.
  • the BFR-id range of the AS domain 115-3 to which the next hop device 140-3 identified by "IP address 4a" belongs is 45 ⁇ 144, that is, the BFER in the AS domain 115-3 can be allocated
  • the range of BFR-id is 45 ⁇ 144.
  • the AS domain 115-2 and the AS domain 115-3 in the same area 120-2 can be distinguished.
  • the column 145 for recording the BFR-id range is optional. For the area 120-1 that only includes one AS domain 115-1, the forwarding entry 130-1 corresponding to the area 120-1 may not include the BFR-id column 145.
  • the intermediate device 110 may receive information indicating its address and the area ID to which it belongs from the next hop device 140, and establish a forwarding table 125 based on the received information.
  • the next hop device 140 may directly send the address of the next hop device 140 and the area ID to which it belongs to the intermediate device 110 through a BGP message.
  • the next hop device 140 may publish a BGP message to the intermediate device 110 via a route reflector (Route Reflector, RR for short).
  • the BGP message includes the address of the next hop device 140 and its belonging. The ID of the area.
  • the next hop device 140 may also advertise the BFR-id range corresponding to the AS domain to which it belongs to the intermediate device 110, for example, directly advertise to the intermediate device 110 through a BGP message, or advertise a BGP message to the intermediate device 110 through an RR
  • the BGP message also includes the BFR-id range corresponding to the AS domain to which the next hop device 140 belongs.
  • the range of the BFR-id corresponding to the AS domain 115-2 to which the next hop device 140-2 in the AS domain 115-2 included in the area 120-2 to the intermediate device 110 belongs is 1 to 44.
  • the range of the BFR-id corresponding to the AS domain 115-3 to which the next hop device 140-3 in the AS domain 115-3 included in the area 120-2 to the intermediate device 110 belongs is 45-144.
  • a default area ID can be set.
  • the area ID to which it belongs may not be sent to the intermediate device 110.
  • the intermediate device 110 may record the area to which the next hop device belongs in the forwarding table 125 according to the setting and use the default area ID.
  • the portal device 105 stores a forwarding table 150.
  • the forwarding table 150 includes a plurality of forwarding entries, and specifically may be forwarding entries 155-1, 155-2, 155-3....
  • the forwarding entries 155-1, 155-2, and 155-3 included in the forwarding table 150 are also referred to as forwarding entries 155 (also referred to as second forwarding entries 155).
  • the ingress device 105 and the intermediate device 110 are located in the same AS domain.
  • the column 160 of the forwarding table 150 records the area ID
  • the column 162 records the address of the intermediate device 110 corresponding to the area ID, such as an IP address or other forms of address.
  • the intermediate device 110 may have multiple addresses, and each address corresponds to an area ID.
  • the intermediate device address corresponding to area ID "2" (identifying area 120-1) is IP address 2b
  • the intermediate device address corresponding to area ID "3" identifying area 120-2)
  • the device address is IP address 3b.
  • the forwarding table 150 further includes a column 165 storing the BFR-id range, which records the BFR-id range in the area 120 identified by the area ID.
  • a column 165 storing the BFR-id range, which records the BFR-id range in the area 120 identified by the area ID.
  • the forwarding entry 155-2 records the AS domain 115- 2
  • the corresponding BFR-id ranges from 1 to 44.
  • the forwarding entry 155-3 records the range of BFR-id in the AS domain 115-3 from 45 to 144.
  • the portal device 105 may obtain the area ID, the intermediate device address, and the range of BFR-id from the intermediate device 110, and generate a forwarding table 150 based on the obtained information.
  • the intermediate device 110 may publish the area ID, the address of the intermediate device 110, and the BFR-id range corresponding to the AS domain included in the area identified by the area ID to the entrance device 105 through a BGP message.
  • the intermediary device 110 may publish multiple BGP messages, and each message includes the area ID, the address of the intermediary device 110, and the BFR-id range of a certain AS domain included in the area.
  • the intermediate device 110 may advertise BGP messages through the RR, or may directly advertise BGP messages. In the embodiment where the default area ID is set, the issued BGP message may not carry the area ID.
  • the portal device 105 can learn that the corresponding area uses the default area ID according to the setting.
  • the area ID is used to obtain the second forwarding entry 155 including the area ID and the address of the intermediate device 110.
  • the entrance device 105 sends the multicast message to the intermediate device 110 based on the address of the intermediate device 110.
  • the intermediate device 110 determines the ID of the area to which the multicast message is to be sent.
  • the intermediate device 110 uses the area ID to obtain the first forwarding entry 130 that records the area ID and the address of the next hop device 140.
  • the intermediate device 110 sends the multicast packet to the next hop device 140 based on the address of the next hop device 140 in the first forwarding entry 130.
  • the intermediate device 110 and the ingress device 105 can obtain forwarding tables 125 and 150 that reach one or more regions.
  • Each area 120 may include one or more AS domains 115.
  • BFR-id planning can be independently performed in the area 120, thereby supporting multicast packets to more export devices.
  • the forwarding table 125 on the intermediate device 110 includes the next hop device addresses of the multiple AS domains 115 in the area 120 identified by the area ID obtained according to the location of the multicast message, and the ingress device 105 does not need to send a group to each AS area. Broadcast messages, thereby significantly improving multicast efficiency.
  • the entry device 105 and the intermediate device 110 are located in different AS domains, and the address recorded in the column 162 in the forwarding table 150 of the entry device 105 may be forwarded between the entry device 105 and the intermediate device 110 The address of the device.
  • the ID of the area to which the ingress device 105 is located is different from the ID of the area to which the egress device is located.
  • the ingress device and the intermediate device 110 that communicate with the multicast source can implement the transmission of multicast packets based on the area ID of the ingress device 105 as the egress device. Specific embodiments in this regard will be described in detail below with reference to FIGS. 4 and 5.
  • FIG. 2 shows a schematic diagram of the interaction process of a multicast message provided by an embodiment of the present application.
  • the process 200 shown in FIG. 2 may be performed in the example scenario described in FIG. 1. For the convenience of discussion, the following will be described in conjunction with FIG. 1.
  • the portal device 105 determines the identifier of the area 120 to which the multicast packet will be sent.
  • the multicast message from the multicast source may include the ID of the area to which the egress device of the multicast receiver communicates belongs.
  • the portal device 105 may determine the area ID based on the received multicast message.
  • the destination address contained in the multicast message may have a corresponding relationship with the area ID.
  • the portal device 105 may determine the area ID according to the destination address and the corresponding relationship in the received multicast message.
  • the portal device 105 obtains the second forwarding entry 155 by using the area ID.
  • the second forwarding entry 155 includes the area ID and the address of the intermediate device 110.
  • the forwarding table 150 stores the corresponding relationship between the area ID and the address of the intermediate device.
  • the portal device 105 uses the area ID to look up the forwarding table 150, and can obtain a second forwarding table entry 155 containing the area ID and the address of the intermediate device 110.
  • the forwarding table 150 may be statically configured. For example, it can be manually configured.
  • the forwarding table 150 may also be dynamically configured to further improve the configuration and update efficiency of the forwarding table. For details, please refer to the related content of FIG. 1 above.
  • the ingress device 105 sends the multicast packet to the intermediate device 110 based on the determined address.
  • the ingress device 105 may encapsulate the determined address of the intermediate device 110 in the destination address of the multicast packet.
  • the multicast message may include the ID of the area 120 to be sent to, so as to clearly indicate the area ID to the intermediate device 110.
  • the multicast message may also include the range of the BFR-id corresponding to the AS domain where the egress device to be sent is located.
  • there may be a mapping or corresponding relationship between the area ID and the identification of the intermediate device 110.
  • the identification of the intermediate device 110 may be any suitable information that can be used to identify the intermediate device 110, for example, including the address of the intermediate device 110.
  • the entrance device 105 may include the identifier of the intermediate device 110 in the multicast message, so as to implicitly indicate the area ID to the intermediate device 110.
  • the identification of the intermediate device 110 may be included in any appropriate part of the multicast message.
  • the portal device 105 may include the identifier of the intermediate device 110 in the destination address field of the multicast message. In this way, the structure of the multicast message can be simplified, and backward compatibility can be better realized.
  • the intermediate device 110 may obtain the area ID according to the identifier and the corresponding relationship of the intermediate device 110 included in the multicast message.
  • the ingress device 105 only needs to send a message to one area 120 instead of sending it to all the AS domains 115, which improves the multicast efficiency.
  • the intermediate device 110 After receiving the multicast packet whose destination address is its own address, the intermediate device 110 determines the ID of the area 120 to which the multicast packet will be sent.
  • the intermediate device 110 may obtain the area ID from the multicast message.
  • the multicast message includes the identifier of the intermediate device 110 (for example, the address of the intermediate device 110)
  • the intermediate device 110 may correspond to the intermediate device 110 according to the identifier and the area ID of the intermediate device 110 contained in the multicast message To determine the area ID.
  • the intermediate device 110 may be assigned multiple identifiers (or addresses), and each identifier of the intermediate device 110 corresponds to a different area ID.
  • the intermediate device 110 may obtain the identifier of the intermediate device 110 from the multicast message (for example, from the destination address field or part of the multicast message), and then determine the corresponding area ID.
  • the intermediate device 110 obtains the first forwarding entry 130 by using the area ID.
  • the intermediate device 110 may use the determined area ID to look up the forwarding table 125 to obtain the first forwarding entry 130.
  • the intermediate device 110 may find multiple forwarding entries 130 corresponding to the area ID of a certain area 120 in the forwarding table 125. For example, for the area 120-2 including the AS domains 115-2 and 115-3, the forwarding entries 130-2 and 130-3 and the area identifier 2 of the area 120-2 can be found.
  • the intermediate device 110 may Based on the range of the BFR-id contained in the multicast message, the corresponding forwarding entry 130-2 or 130-3 is determined.
  • the forwarding table 125 at the intermediate device 110 may be configured statically or dynamically.
  • the static configuration method can be manual configuration. Refer to the corresponding content in Figure 1 for the method of dynamic configuration.
  • the intermediate device 110 can receive information from the newly added AS domain and update the forwarding table 125 accordingly, thereby significantly improving the configuration and update efficiency of the forwarding table.
  • the intermediate device 110 sends the multicast packet to the next hop device 140 based on the address of the next hop device 140 included in the first forwarding entry 130.
  • the intermediate device 110 can directly send the multicast packet to the area 120 -1 AS domain 115-1, without duplicating the received multicast packets.
  • the intermediate device 140 may perform replication processing on the multicast message, so as to send the multicast message and the replicated multicast message to the area 120 -2 in the AS domains 115-2 and 115-3.
  • FIG. 3 shows a multicast scenario provided by an embodiment of the present application.
  • scenario 300 shown in FIG. 3 will be described below in conjunction with FIG. 1.
  • the difference between scenario 300 and scenario 1 is that AS domains 115-4 and 115-5 are AS domains added after network expansion.
  • the area 120-2 includes the AS domain 115-4.
  • the area 120-3 includes the AS domain 115-5.
  • the entrance device 105 and the intermediate device 110 are located in the same AS domain 115-6 of the backbone network.
  • the entrance device 105 can be implemented by a PE device in the AS domain 115-6.
  • the intermediate device 110 may be implemented by the ASBR of the AS domain 115-6.
  • the next hop device 140-4 belongs to the AS domain 115-4.
  • the next hop device 140-5 belongs to the AS domain 115-5.
  • the description of the same structure can refer to the corresponding content of the scene shown in FIG. 1.
  • next hop devices 140-1, 140-2, and 140-3 may directly publish the following information to the intermediate device 110, or may publish the following information to the intermediate device 110 through the RR 310.
  • the information released by the next hop devices 140-1, 140-2, and 140-3 is as follows:
  • ASBR2 indicates device 140-1
  • IPv6 address ⁇ ASBR2> indicates the IPv6 address of device 140-1
  • ASBR3 indicates device 140-2
  • IPv6 address ⁇ ASBR3> indicates the IPv6 address of device 140-2
  • ASBR4 indicates device 140-3
  • IPv6 address ⁇ ASBR4> indicates the IPv6 address of device 140-3
  • the intermediate device 110 establishes a forwarding table 125 according to the received information.
  • the forwarding table 125 includes the following multiple forwarding entries 130:
  • the intermediate device 110 After the multicast message from the entrance device 105 reaches the intermediate device 110, the intermediate device 110 first determines the area ID of the area 120.
  • a multicast message (for example, a BIERv6 multicast message) may carry a Color value, which is used to represent the area ID.
  • the intermediate device 110 may obtain the corresponding relationship between the Color value and the identifier of the intermediate device 110. The intermediate device 110 determines the Color value used to represent the area ID according to the correspondence and the identifier of the intermediate device 110 included in the multicast packet.
  • the intermediate device 110 determines the next hop address according to the range of BFR-id contained in the multicast packet. For example, in an embodiment where the multicast message is a BIERv6 multicast message, the intermediate device 110 may determine the range of the BFR-id according to the bit string included in the BIERv6 message.
  • the intermediate device 110 may instruct to publish the information of the area ID, the corresponding own address, and the optional BFR-id range to the portal device 105.
  • the intermediate device 110 may publish the information to the portal device 105 through the RR 310, or may directly publish it.
  • the intermediate device 110 may publish the following information to the portal device 105:
  • the above information includes the corresponding relationship of (Color, IPv6 address), where the IPv6 address represents the IPv6 address of the intermediate device 110, which corresponds to the area ID.
  • the information also includes information about the BFR-id range in each AS domain in the area identified by the Color value, that is, (Color, BFR-id) information.
  • the portal device 105 After the portal device 105 receives the information issued by the intermediate device 110, it can obtain the following forwarding entry 155:
  • forwarding entries 155 can be combined as follows:
  • the network is expanded, for example, the AS domain 115-4 is added.
  • the AS domain 115-4 corresponds to 112 BFR-ids, and the total number of BFR-ids corresponding to AS 115-2 and 115-3 is 256.
  • the next hop device 140-4 of the AS domain 115-4 publishes the area ID, the address of the next hop device 140-4, and the range of BFR-id corresponding to the AS domain 115-4 to the intermediate device 110.
  • the portal device 105 After receiving the above information, the portal device 105 creates the following forwarding table entry 155 to update the forwarding table 150:
  • the network continues to expand, for example, an AS domain 115-5 is added, and its BFR-id has 65,500.
  • the AS domain 115-5 device 140-5 can publish the area ID, the address of the device 140-5, and the BFR-id range in the AS domain 115-5 to the intermediate device 110 through the RR 310.
  • the portal device 105 creates the following forwarding table entry 155 to update the forwarding table 150:
  • the address can be dynamically applied for by the intermediate device 110 according to the received Color value, so that no additional configuration is necessary, which improves efficiency.
  • the BGP routing can adopt the BGP IPv6 unicast (BGP IPv6-Unicast) address family, or can adopt other address families, such as the BGP link state (BGP-LS) address family. Alternatively, it can be a newly created address family, such as the BIER address family. As an example, you can use the IPv6-Unicast address family and publish it through RR 310.
  • the device 140-1 is represented as ASBR2
  • the device 140-2 is represented as ASBR3
  • the device 140-3 is represented as ASBR4
  • the intermediate device 110 is represented as ASBR1b
  • the ingress device 105 is represented as PE1.
  • Figure 4 shows another multicast scenario provided by an embodiment of the present application.
  • the entrance device 105 and the intermediate device 110 are located in different AS domains.
  • the entrance device 105 is located in the AS domain 115-6 of the metropolitan area network, for example, is implemented as a PE device in the AS domain 115-6.
  • the intermediate device 110 is located in the AS domain 115-7 of the backbone network, for example, is implemented as an ASBR of the AS domain 115-7.
  • another ASBR 405-7 in the AS domain 115-7 acts as a next hop device associated with the AS domain 115-1...115-5.
  • Multicast packets sent to each AS domain 115-1...115-5 are forwarded to the ASBR 405-1...405-5 of these AS domains 115-1...115-5 via the ASBR 405-7.
  • the intermediate device 110 and the ASBR 405-7 may both establish BGP neighbors with the RR 310, so that the ASBR 405-7 advertises related routing information to the intermediate device 110 via the RR 310.
  • the AS domain 115-6 belongs to the area 120-4, which has a different area ID from the areas 120-1, 120-2, and 120-3.
  • the establishment of the forwarding table 125 at the intermediate device 110 may include a forwarding entry with the portal device 105 as the multicast destination, in which the area ID of the area 120-4 is recorded.
  • the ASBR 405-6 of the AS domain 115-6 serves as the next hop device associated with the area 120-4.
  • the area ID of the entrance device 105, the address of the associated next hop device, and the BFR-id range of the area 120-4 may be issued by the ASBR 405-6 to the intermediate device 110 via the RR 310. Since the area ID of the area 120-4 where the entry device 105 is located is different from the areas 120-1, 120-2, and 120-3, when the RR 310 advertises routing information, the RR 310 can use the area ID to identify the destination device of the routing information. Make a distinction.
  • Figure 5 shows another multicast scenario provided by an embodiment of the present application.
  • ASBR 405-1...405-7 are ASBRs in AS domain 115-1...115-7
  • ASBR 405-8 is another ASBR in AS domain 115-7 ASBR. Both 405-7 and 405-8 can act as intermediate devices.
  • the routing information is not advertised via the RR, but is directly advertised by each device to upstream and downstream devices.
  • the ASBR 405-1...405-5 of each AS domain 115-1...115-5 serves as the original route publisher and publishes the following routing information:
  • the prefix (prefix) field is used to carry the IP address prefix
  • the NextHop (next hop) field is used to carry the IP address
  • BIER-info represents BIER information
  • BFR-id-range represents the range of BFR-id.
  • ASBR2, ASBR3, ASBR4, ASBR5, and ASBR6 represent ASBR 405-1, 405-2, 405-3, 405-4, and 405-5, respectively.
  • ASBR 405-6 which is the next hop device associated with AS domain 115-6, is also the original route publisher, and it advertises the following routing information about AS domain 115-6:
  • ASBR0 represents ASBR 405-6
  • ASBR 405-8 and ASBR 405-7 are not the original route distributors, but will re-advertise the routing information advertised by other devices to other internal BGP (iBGP) peers or external BGP (eBGP) peers.
  • ASBR 405-7 can receive the corresponding routing information from ASBR 405-1...405-5 which is the eBGP peer, and then advertise it to ASBR 405-8 which is the iBGP peer. The next hop of the route is changed to itself. This can be achieved through routing strategies.
  • ASBR 405-8 can receive routing information from ASBR 405-6, which is the eBGP peer, and then advertise it to ASBR 405-7, which is iBGP peer, and when advertised, the next hop of the route is also set through routing policies. Change to yourself.
  • ASBR 405-8 and ASBR 405-7 can also advertise routing information to PE 505 as an iBGP peer in the same AS domain 115-7.
  • PE 505 can act as the entrance device of AS domain 115-7.
  • ASBR 405-7 can be used as an intermediate device associated with it.
  • PE 505 can obtain the following routing information, where ASBR1b represents ASBR 405-7, and ASBR1a represents ASBR 405-8:
  • PE 505 can create the following BIER forwarding entries that reach the AS domain 115-1...115-6:
  • ASBR 405-7 when ASBR 405-7 advertises routing information received from ASBR 405-1...405-5, which is the eBGP peer, to PE 505 and ASBR 405-8, which are iBGP peers, it can be Set the next hop address as one or more identifiers of oneself to indicate the corresponding area ID. In this way, after the ASBR 405-7 receives the multicast packet, the ASBR 405-7 can determine the corresponding area ID according to the identifier contained in the multicast packet. In this way, PE 505 can obtain the following routing information:
  • PE 505 can create the following BIER forwarding entries that reach the AS domain 115-1...115-6:
  • ASBR 405-8 can obtain the following routing information:
  • ASBR 405-8 can create BIER forwarding entries that reach AS domain 115-1...115-6 accordingly.
  • the next hop of the BIER forwarding entry created by ASBR 405-8 to reach AS domain 115-6 is ASBR 405-6.
  • ASBR 405-7 can obtain the following routing information:
  • ASBR 405-7 can create BIER forwarding entries that reach AS domain 115-1...115-6 accordingly.
  • the next hop of the BIER forwarding table established by ASBR 405-7 to reach AS domain 115-1...115-5 is ASBR 405-1...405-5.
  • ASBR 405-8 will not re-advertise the routing information advertised from ASBR 405-6 to ASBR 405-6, but will send the routing information advertised from ASBR 405-7 to ASBR 405-6 Publish and do not modify the next hop, which can be achieved through routing strategies.
  • ASBR 405-6 can obtain the following routing information:
  • ASBR 405-6 can create BIER forwarding entries that reach AS domain 115-1...115-5 accordingly.
  • the BIER forwarding entry of each BFR-id of the ASBR 405-6 to the AS domain 115-6 belongs to the AS domain and may not be established through BGP messages.
  • the ASBR 405-6 advertises the routing information advertised from the ASBR 405-8 to the ingress device 105 without modifying the next hop. This can be achieved through a routing policy.
  • the entrance device 105 can obtain the following routing information:
  • the portal device 105 can create a BIER forwarding entry to the AS domain 115-1...115-5 accordingly.
  • the BIER forwarding entry of each BFR-id of the ingress device 105 to the AS domain 115-6 belongs to the AS domain and may not be established through BGP messages.
  • ASBR 405-7 can further advertise the received routing information to ASBRs 405-1...405-5.
  • ASBR 405-7 can advertise the routing information advertised by ASBR 405-8 to ASBR 405-1...405-5 without changing the next hop of the route.
  • ASBR 405-7 can also advertise the routes advertised by ASBR 405-2...405-6 to ASBR 405-1, and change the next hop of the route to itself.
  • the ASBR 405-1 can re-advertise the route advertised from the ASBR 405-7 to the PE 510-1 in the AS domain 115-1 (which can act as the ingress device of the AS domain 115-1), and does not change the next hop of the route.
  • both ASBR 405-1 and PE 510-1 can obtain the following routing information, and can create corresponding BIER forwarding entries based on this:
  • ASBR 405-7 can also advertise the routes advertised by ASBR 405-1, 405-3, 405-4, 405-5, and 405-6 to ASBR 405-2, and change the next hop to itself.
  • the ASBR 405-2 can also advertise the route advertised from the ASBR 405-7 to the PE 510-2 (which can act as the ingress device of the AS domain 115-2), and does not change the next hop of the route.
  • both ASBR 405-2 and PE 510-2 can obtain the following routing information, and can create corresponding BIER forwarding entries based on this:
  • ASBR 405-7 can also advertise the routes advertised by ASBR 405-1, 405-2, 405-4, 405-5, and 405-6 to ASBR 405-3, and change the next hop to itself.
  • the ASBR 405-3 can also advertise the route advertised from the ASBR 405-7 to the PE 510-3 (which can act as the ingress device of the AS domain 115-3), and does not change the next hop of the route.
  • Both ASBR 405-3 and PE 510-3 can obtain the following routing information, and can establish corresponding BIER forwarding entries based on this:
  • ASBR 405-4 can obtain the following routing information, and can create corresponding BIER forwarding entries based on this:
  • ASBR 405-5 can obtain the following routing information, and can create corresponding BIER forwarding entries based on this:
  • the next hop of ASBR 405-1...405-5 recorded by the ingress device 105 and ASBR 405-6 is ASBR 405-7, if IPv6 unicast routing (i.e. IPv6 Unicast address family) is used .
  • IPv6 unicast routing i.e. IPv6 Unicast address family
  • IPv6 multicast routing i.e. IPv6 Multicast address family
  • the IPv6 multicast routing itself does not generate a unicast forwarding table. It only needs to be based on these IPv6 multicast routes and the information they carry.
  • Area ID information such as Color value
  • BIER information such as BFR-id range
  • Fig. 6 shows a schematic structural diagram of an apparatus for sending a multicast packet provided by an embodiment of the present application.
  • the device 600 shown in FIG. 6 may be installed in the intermediate device in any embodiment corresponding to FIG. 1 to FIG. 5.
  • the device 600 will be described below in conjunction with FIG. 1 and FIG. 6.
  • the apparatus 600 includes a first obtaining module 605, a second obtaining module 610, and a first sending module 615.
  • the first obtaining module 605 is configured to obtain the identifier of the area corresponding to the multicast packet based on the multicast packet from the entrance device.
  • the second obtaining module 610 is used to obtain the address of the next hop device based on the area identification and forwarding entry.
  • the forwarding entry includes the area identification and the address of the next hop device.
  • the first sending module 615 is configured to send the multicast message based on the address of the next hop device.
  • the multicast packet includes the identifier of the area
  • the first obtaining module 605 is configured to obtain the identifier of the area from the multicast packet.
  • the first obtaining module 605 is configured to obtain the identifier of the area corresponding to the identifier of the intermediate device based on the identifier of the intermediate device in the multicast packet.
  • the apparatus 600 may store a corresponding relationship, and the corresponding relationship includes the identifier of the intermediate device and the identifier of the area.
  • the first obtaining module 605 is configured to obtain the identifier of the area corresponding to the address of the intermediate device based on the address of the intermediate device in the multicast packet.
  • the apparatus 600 may store a corresponding relationship, and the corresponding relationship includes the address of the intermediate device and the identifier of the area.
  • the apparatus 600 may further include: a first receiving module, configured to receive the address of the next hop device and the identifier of the area to which the next hop device belongs; and the third obtaining module The module is used to obtain forwarding entries based on the identification of the area and the address of the next hop device.
  • the apparatus 600 may further include: a first receiving module, configured to receive the identifier of the next hop device and the identifier of the area to which the next hop device belongs, sent by the next hop device.
  • the third obtaining module is used to obtain the address of the next hop device based on the identifier of the next hop device; the third obtaining module is used to obtain the forwarding entry based on the identifier of the area and the address of the next hop device.
  • the apparatus 600 may store a corresponding relationship, and the corresponding relationship includes the identifier of the next hop device and the address of the next hop device.
  • the first receiving module is further configured to receive the range of the BFR identifier of the forwarding router in the destination AS domain sent by the next hop device, and the destination AS domain is the AS domain to which the next hop device contained in the area belongs.
  • the forwarding table entry also includes the range of the BFR identifier in the destination AS domain.
  • the multicast message also includes the range of the BFR identifier, and the third obtaining module is used to determine the forwarding entry based on the area identifier and the range of the BFR identifier.
  • the apparatus 600 may further include: a second sending module, configured to send the address of the intermediate device and the identifier of the area to which the intermediate device belongs to the entrance device.
  • the second sending module is further configured to send to the entrance device the range of the BFR identifier in the AS domain to which the intermediate device belongs, and the AS domain to which the intermediate device belongs is included in the area to which the intermediate device belongs.
  • FIG. 7 shows a schematic structural diagram of an apparatus for sending a multicast packet provided by an embodiment of the present application.
  • the apparatus 700 shown in FIG. 7 may be installed in the inlet device in any embodiment corresponding to FIG. 1 to FIG. 5.
  • the device 700 will be described with reference to FIG. 1 and FIG. 7.
  • the apparatus 700 includes a first obtaining module 705, a second obtaining module 710, and a first sending module 715.
  • the first obtaining module 705 is configured to obtain the identifier of the area corresponding to the received multicast packet.
  • the second obtaining module 710 is configured to obtain the address of an intermediate device used to forward the multicast packet to the area based on the area-based identification and forwarding entry, and the forwarding entry includes the area identification and the address of the intermediate device.
  • the first sending module 715 is configured to send the multicast message based on the address of the intermediate device.
  • the apparatus 700 may further include: a second receiving module, configured to receive the address and region identifier of the intermediate device sent by the intermediate device; and a third obtaining module, configured to receive the address and region identification of the intermediate device based on the The identification of the area, the forwarding entry is obtained.
  • the apparatus 700 may further include: a second receiving module, configured to receive the identification of the intermediate device and the identification of the area sent by the intermediate device; and a third obtaining module, configured to be based on the identification of the intermediate device, The address of the intermediate device is determined; the third obtaining module is used to obtain the forwarding entry based on the address of the intermediate device and the identifier of the area.
  • the second receiving module is also used to receive the range of the BFR identifier in the AS domain of the target autonomous system sent by the intermediate device.
  • the target AS domain is the AS domain to which the multicast packets contained in the area need to be sent, and forward
  • the published item also includes the scope of the BFR mark in the destination AS domain.
  • the second obtaining module 710 is configured to determine the forwarding entry based on the range of the BFR identifier in the target AS domain and the identifier of the area.
  • the multicast packet contains the identifier of the area
  • the first obtaining module 705 is configured to obtain the identifier of the area from the multicast packet.
  • the multicast packet includes the identifier of the intermediate device
  • the first obtaining module 705 is configured to obtain the identifier of the area corresponding to the identifier of the intermediate device based on the identifier of the intermediate device in the multicast packet.
  • the modules included in the apparatuses 600 and 700 can be implemented in various ways, including software, hardware, firmware, or any combination thereof.
  • one or more modules may be implemented using software and/or firmware, such as machine-executable instructions stored on a storage medium.
  • some or all of the modules in the apparatuses 600 and 700 may be at least partially implemented by one or more hardware logic components.
  • the exemplary types of hardware logic components include field programmable gate arrays (FPGA), application specific integrated circuits (ASIC), application specific standards (ASSP), system on chip (SOC), complex programmable logic devices (CPLD), etc.
  • Figure 8 shows a block diagram of a device 800 in which certain embodiments of the present application can be implemented.
  • the device 800 can be used to implement the intermediate device or the entrance device provided in any embodiment corresponding to FIG. 1 to FIG. 7.
  • the device 800 includes a processor 810, a memory 820, a communication interface 830, and a communication bus 840.
  • the processor 810, the memory 820, and the communication interface 830 perform internal interaction through the communication bus 840.
  • the communication bus 840 can interact with external devices or devices. in.
  • the memory 820 is used to store instructions; the processor 810 is used to execute the instructions in the memory, and execute the instructions provided in any of the above-mentioned embodiments corresponding to FIGS.
  • the method executed by the intermediate device When the device 800 is installed in the portal device, the memory 820 is used to store instructions; the processor 810 is used to execute the instructions in the memory, and execute the instructions provided by any one of the embodiments corresponding to FIGS. 2 to 5 above. The method performed by the portal device.
  • the memory 820 can be of any suitable type suitable for the local technical environment, and can be implemented by any suitable data storage technology, including but not limited to semiconductor-based storage devices, magnetic storage devices and systems, and optical storage devices and systems. Although only one memory unit is shown in FIG. 8, there may be multiple physically different memory units in the device 800.
  • the processor 810 may be of any suitable type suitable for the local technical environment, and may include, but is not limited to, general-purpose computers, special-purpose computers, microcontrollers, digital signal controllers (DSP), and controller-based multi-core controller architectures. one or more.
  • the device 800 may also include multiple processors 810.
  • the processor 810 is coupled with the communication unit 840.
  • the communication unit 840 may realize the reception and transmission of information through radio signals or by means of optical fibers, cables, and/or other components.
  • various example embodiments of the present application may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device.
  • firmware or software that can be executed by a controller, microprocessor, or other computing device.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, etc., which perform specific tasks or implement specific abstract data structures.
  • functions of the program modules may be combined or divided among the described program modules.
  • the machine-executable instructions for the program modules can be executed in local or distributed devices. In distributed equipment, program modules can be located in both local and remote storage media.
  • the computer program codes used to implement the methods of the embodiments of the present application can be written in one or more programming languages. These computer program codes can be provided to the processors of general-purpose computers, special-purpose computers, or other programmable data processing devices, so that when the program codes are executed by the computer or other programmable data processing devices, they will cause changes in the flowcharts and/or block diagrams. The functions/operations specified in are implemented.
  • the program code can be executed entirely on a computer, partly on a computer, as a stand-alone software package, partly on a computer and partly on a remote computer, or entirely on a remote computer or server.
  • a machine-readable medium or a computer-readable medium may be any tangible medium that contains or stores a program used in or related to an instruction execution system, apparatus, or device.
  • the machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium.
  • the machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination thereof. More detailed examples of machine-readable storage media include electrical connections with one or more wires, portable computer disks, hard disks, random memory access (RAM), read-only memory (ROM), erasable programmable read-only Memory (EPROM or flash memory), optical storage device, magnetic storage device, or any suitable combination thereof.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供用于发送组播报文的方法和装置。该方法中，入口设备获取接收到的组播报文对应的区域的标识；所述入口设备基于所述区域的标识和转发表项，获得用于将所述组播报文转发至所述区域的中间设备的地址，所述转发表项包括所述区域的所述标识以及所述中间设备的所述地址；所述入口设备基于所述中间设备的所述地址发送所述组播报文。中间设备基于来自入口设备的组播报文，获取组播报文对应的区域的标识；中间设备基于区域的标识和转发表项，获得下一跳设备的地址，转发表项包含区域的标识以及下一跳设备的地址；中间设备基于下一跳设备的地址发送组播报文。该方法可以节省网络资源。

Description

用于发送组播报文的方法和装置
本申请要求于2020年5月11日提交中国国家知识产权局、申请号为202010393103.4、发明名称为“一种组播转发方法及装置”的中国专利申请的优先权，并要求于2020年7月3日递交中国国家知识产权局、申请号为202010632551.5，发明名称为“用于发送组播报文的方法和装置”的中国专利申请的优先权。上述中国专利申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，更具体地，涉及用于发送组播报文的方法和装置。
背景技术
位索引显式复制(Bit Index Explicit Replication，简称为BIER)是一种常用的组播架构。互联网工程任务组(Internet Engineering Task Force，简称为IETF)标准中定义了BIER头封装格式以及封装方法。BIER封装可以例如基于多协议标签交换(Multi-Protocol Label Switching，简称为MPLS)、基于以太网和基于因特网协议第6版(Internet protocol version 6，简称为IPv6)等。基于IPv6的BIER(或BIERv6)在跨自治系统(Autonomous System，简称为AS)域的部署方面具有较好的灵活性。
在基于BIERv6的跨域组播场景中，组播源可以与骨干网络的运营商边缘(Provider Edge，简称为PE)设备通信，多个组播接收者可以与城域网络的多个PE设备通信。与组播源通信的PE设备可以通过骨干网络的自治系统边界路由器(Autonomous System Boundary Router，简称为ASBR)向与组播接收者通信的PE设备发送组播报文。基于BIERv6的组播场景中，任一PE设备可以被分配位转发路由器(Bit Forwarding Router，简称为BFR)标识(BFR-id)。当与组播接收者通信的PE设备处于不同的AS域内，且需要从某个组播源接收组播报文时，与组播源通信的PE设备需要复制多份组播报文，并向与组播接收者通信的PE设备所在的AS域发送组播报文，会存在浪费网络资源的问题。
发明内容
本申请提供了一种用于发送组播报文的方法和装置，能够节省网络资源。
第一方面，提供了一种用于发送组播报文的方法。该方法包括：中间设备基于来自入口设备的组播报文，获取组播报文对应的区域的标识；中间设备基于区域的标识和转发表项，获得下一跳设备的地址，转发表项包含区域的标识以及下一跳设备的地址；中间设备基于下一跳设备的地址发送组播报文。
上述方法中，中间设备作为一个或多个出口设备与入口设备之间的中转节点，可在接收到了入口设备组播报文后，根据确定的区域的标识来转发组播报文。该方法不会再如通常的跨域组播场景中从与组播源通信的PE设备开始进行组播报文复制和转发，而是根据区域标识定位作为中转节点的中间设备，由中间设备发送给下一跳设备，再由下一跳设备实现组播报文复制和转发操作，节省了入口设备与中间设备之间的流量(较少地占用网络资源来发送复制的组播报文)。可选地，当下一跳设备不是出口设备时，还可进一步节省中间设备与下一跳设备之间的流量(较少地占用网络资源来发送复制的组播报文)。
在一种可能的实现方式中，所述区域包含一个或多个AS域。下一跳设备可以是出口设备，或者是出口设备所在的AS域的ASBR。出口设备是能够与组播接收者通信的边缘设备，也可称为位转发出口路由器(bit forwarding egress router，BFER)。入口设备可以是与组播源通信的边缘设别，也可称为位转发入口路由器(bit forwarding ingress router，BFIR)。中间设备和入口设备为BIER跨域网络场景中的设备。
在一种可能的实现方式中，组播报文包括区域的标识，中间设备基于来自入口设备的组播报文，获取组播报文对应的区域的标识包括：中间设备从组播报文中获取区域的标识。
在一种可能的实现方式中，组播报文包括中间设备的标识，中间设备基于来自入口设备的组播报文，获取组播报文对应的区域的标识包括：中间设备基于组播报文中的中间设备的标识，获取与中间设备的标识对应的区域的标识。该实现方式中，中间设备上可预先配置一对应关系，该对应关系包括中间设备的标识和区域的标识。这种方式具有更佳的兼容性，对组播报文无需进行过多的改进或处理。
在一种可能的实现方式中，该方法还包括：中间设备接收下一跳设备发送的下一跳设备的地址和下一跳设备所属的区域的标识；中间设备基于区域的标识和下一跳设备的地址，获得转发表项。
在一种可能的实现方式中，该方法还包括：中间设备接收下一跳设备发送的下一跳设备的标识和下一跳设备所属的区域的标识；中间设备基于下一跳设备的标识，获得下一跳设备的地址；中间设备基于区域的标识和下一跳设备的地址，获得转发表项。
在一种可能的实现方式中，该方法还包括：中间设备接收下一跳设备发送的目的AS域内位转发路由器BFR标识的范围，目的AS域为区域包含的下一跳设备所属的AS域，转发表项还包括目的AS域内BFR标识的范围。
在一种可能的实现方式中，组播报文还包括BFR标识的范围，该方法还包括：中间设备基于区域的标识和BFR标识的范围，确定转发表项。
在一种可能的实现方式中，该方法还包括：中间设备向入口设备发送中间设备的地址和中间设备所属的区域的标识。
在一种可能的实现方式中，该方法还包括：中间设备向入口设备发送中间设备所属AS域内BFR标识的范围，中间设备所属AS域包含于中间设备所属的区域。
第二方面，提供了一种用于发送组播报文的方法。该方法包括：入口设备获取接收到的组播报文对应的区域的标识；入口设备基于区域的标识和转发表项，获得用于将组播报文转发至区域的中间设备的地址，转发表项包括区域的标识以及中间设备的地址；入口设备基于中间设备的地址发送组播报文。
上述方法中，入口设备可根据区域的标识，将组播报文发送给中间设备，而不会再如通常的跨域组播场景中进行组播报文复制和转发，节省了其与中间设备之间的流量(较少地占用网络资源来发送复制的组播报文)。中间设备和入口设备为BIER跨域网络场景中的设备。
在一种可能的实现方式中，该方法还包括：入口设备接收中间设备发送的中间设备的地址和区域的标识；入口设备基于中间设备的地址和区域的标识，获得转发表项。
在一种可能的实现方式中，该方法还包括：入口设备接收中间设备发送的中间设备的标识和区域的标识；入口设备基于中间设备的标识，确定中间设备的地址；入口设备基于中间设备的地址和区域的标识，获得转发表项。
在一种可能的实现方式中，该方法还包括：入口设备接收中间设备发送的目的自治系统AS域内BFR标识的范围，目的AS域为区域包含的组播报文需要发送到的AS域，转发表项还包括目的AS域内BFR标识的范围。
在一种可能的实现方式中，该方法还包括：入口设备基于目的AS域内BFR标识的范围和区域的标识，确定转发表项。
在一种可能的实现方式中，组播报文中包含区域的标识，入口设备获取接收到的组播报文对应的区域的标识包括：入口设备从组播报文获取区域的标识；或者组播报文中包含中间设备的标识，组播报文中包含区域的标识，入口设备获取接收到的组播报文对应的区域的标识包括：入口设备基于组播报文中的中间设备的标识，获取与中间设备的标识对应的区域的标识。
在第三方面，提供了一种用于生成转发表项的方法。该方法包括：中间设备从下一跳设备获取所述下一跳设备所属的区域的标识和所述下一跳设备的地址；中间设备基于区域的标识和下一跳设备的地址获得转发表项。
上述方法中，中间设备可根据从下一跳设备获取的参数来获得用于转发组播报文的转发表项，降低了网络结构发生变动后进行手动配置的复杂性，可以更灵活快捷地刷新用于转发组播报文的表项。
在一种可能的实现方式中，所述中间设备从下一跳设备获取所述下一跳设备所属的区域的标识和所述下一跳设备的地址包括：所述中间设备接收所述下一跳设备发送的所述下一跳设备的地址和所述区域的所述标识。
在一种可能的实现方式中，所述中间设备从下一跳设备获取所述下一跳设备所属的区域的标识和所述下一跳设备的地址包括：所述中间设备接收所述下一跳设备发送的所述下一跳设备的标识和所述区域的所述标识；所述中间设备基于下一跳设备的标识，获得所述下一跳设备的地址。其中，所述下一跳设备的标识可以是除地址之外的其它用于标识所述下一跳设备的信息或参数。中间设备可根据预设算法将所述下一跳设备的标识转换为所述下一跳设备的地址，或者中间设备可根据一对应关系和所述下一跳设备的标识，获得所述下一跳设备的地址，该对应关系包括下一跳设备的标识和下一跳设备的地址。
在一种可能的实现方式中，该方法还包括：中间设备接收下一跳设备发送的目的AS域内位转发路由器BFR标识的范围，目的AS域为区域包含的下一跳设备所属的AS域，转发表项还包括目的AS域内BFR标识的范围。
上述方法中，中间设备在生成了转发表项后，可利用转发表项发送来自入口设备的组播报文，节省了入口设备与中间设备之间的流量(较少地占用网络资源来发送复制的组播报文)。可选地，当下一跳设备不是出口设备时，还可进一步节省中间设备与下一跳设备之间的流量(较少地占用网络资源来发送复制的组播报文)。
在第四方面，提供了一种用于生成转发表项的方法。该方法包括：入口设备从中间设备获取所述中间设备的地址和区域的标识；入口设备基于中间设备的地址和区域的标识，获得转发表项。
上述方法中，入口设备可根据从中间设备获取的参数来获得用于转发组播报文的转发表项，降低了网络结构发生变动后进行手动配置的复杂性，可以更灵活快捷地刷新用于转发组播报文的表项。
在一种可能的实现方式中，入口设备从中间设备获取所述中间设备的地址和区域的标 识包括：所述入口设备接收所述中间设备发送的所述中间设备的地址和所述区域的所述标识。
在一种可能的实现方式中，入口设备从中间设备获取所述中间设备的地址和区域的标识包括：所述入口设备接收所述中间设备发送的所述中间设备的标识和所述区域的所述标识；所述入口设备根据所述中间设备的标识，确定所述中间设备的地址。其中，所述中间设备的标识可以是除地址之外的其它用于标识所述中间设备的信息或参数。入口设备可根据预设算法将所述中间设备的标识转换为所述中间设备的地址，或者入口设备可根据一对应关系和所述中间设备的标识，获得所述中间设备的地址，该对应关系包括中间跳设备的标识和中间跳设备的地址。
在一种可能的实现方式中，该方法还包括：入口设备接收中间设备发送的目的自治系统AS域内BFR标识的范围，目的AS域为区域包含的组播报文需要发送到的AS域，转发表项还包括目的AS域内BFR标识的范围。
上述方法中，入口设备在生成了转发表项后，可利用转发表项向中间设备发送组播报文，节省了入口设备与中间设备之间的流量(较少地占用网络资源来发送复制的组播报文)。
第五方面，提供了一种用于发送组播报文的装置，该装置设置于中间设备。该装置包括用于实现上述第一方面或第一方面任一种可能实现方式提供的方法对应功能的模块；或者该装置包括用于实现上述第三方面或第三方面任一种可能实现方式提供的方法对应功能的模块。
第六方面，提供了一种用于发送组播报文的装置，该装置设置于入口设备。装置包括用于实现上述第二方面或第二方面任一种可能实现方式提供的方法对应功能的模块；或者该装置包括用于实现上述第四方面或第四方面任一种可能实现方式提供的方法对应功能的模块。。
第七方面，提供了一种设备。该设备包括处理器和存储指令的存储器，该指令在被处理器执行时使该设备执行上述第一方面或第一方面任一种可能实现方式提供的方法；或者该指令在被处理器执行时使该设备执行上述第二方面或第二方面任一种可能实现方式提供的方法；或者该指令在被处理器执行时使该设备执行上述第三方面或第三方面任一种可能实现方式提供的方法；或者该指令在被处理器执行时使该设备执行上述第四方面或第四方面任一种可能实现方式提供的方法。
第八方面，提供了一种计算机可读存储介质，其上存储有指令，该指令在由设备中的处理器执行时，使设备执行上述第一方面或第一方面任一种可能实现方式提供的方法；或者该指令在被处理器执行时使该设备执行上述第二方面或第二方面任一种可能实现方式提供的方法；或者该指令在被处理器执行时使该设备执行上述第三方面或第三方面任一种可能实现方式提供的方法；或者该指令在被处理器执行时使该设备执行上述第四方面或第四方面任一种可能实现方式提供的方法。
第九方面，提供了一种系统，所述系统包括第五方面所述的装置和第六方面所述的装置。
附图说明
图1示出了本申请实施例提供的一种网络场景示意图；
图2示出了本申请实施例提供的组播报文的交互流程示意图；
图3示出了本申请实施例提供的一种组播场景；
图4示出了本申请实施例提供的另一种组播场景；
图5示出了本申请实施例提供的另一种组播场景；
图6示出了本申请实施例提供的用于发送组播报文的装置的结构示意图；
图7示出了本申请实施例提供的用于发送组播报文的装置的结构示意图；以及
图8示出了本申请实施例提供的设备的结构示意图。
具体实施方式
本申请实施例中的术语“入口设备”是指跨域组播过程中靠近组播源且能够与组播源通信的设备。作为示例，入口设备可以包括组播源所在的AS域中的PE设备。入口设备可以位于骨干网络中，也可以位于城域网络中。在基于BIER进行跨域组播的实施例中，入口设备可以对来自组播源的组播报文进行BIER封装。本申请实施例中的术语“出口设备”是指跨域组播过程中位于靠近组播接收者侧能够与组播接收者通信的设备。作为示例，出口设备可以包括组播接收者通信的或者所属的AS域中的PE设备。出口设备可以位于城域网络中。在基于BIER进行跨域组播的实施例中，出口设备可以对接收到的组播报文进行BIER解封装。本申请实施例中的术语“中间设备”是指跨域组播过程中在入口设备和出口设备之间用于实现组播转发的设备。作为示例，中间设备可以包括骨干网络中的ASBR。中间设备也可以位于城域网络中。本申请实施例中的术语“包括”及其变形是开放性包括，即“包括但不限于”。术语“基于”是“至少部分地基于”。术语“一个实施例”表示“至少一个实施例”；术语“另一实施例”表示“至少一个另外的实施例”。其他术语的相关定义将在下文描述中给出。尽管本文可以使用术语“第一”和“第二”等来描述各种元件，但这些元件不应受到这些术语的限制。这些术语仅用于区分一个元件和另一个元件。如本文所用，术语“和/或”包括一个或多个所列术语的任何和所有组合。
在通常的层次化组播中，从骨干网络向城域网络进行BIERv6跨域转发时，各PE设备可以通过BFR-id来区分。PE设备的BFR-id是统一分配的，因此所支持的PE设备的数目受限于BFR-id值的位数。例如，如果BFR-id值为16位，则无法支持多于65535个PE设备。在通常的对等组播中，PE设备的BFR-id可以独立分配，因此可以支持较多PE设备。然而，入口设备需要向所有AS域转发组播报文。特别是随着网络扩容，会增加越来越多的AS域，即使某个AS域的PE设备数目较少，入口设备也需要向该AS域进行转发，这会造成巨大的流量复制浪费。
本申请实施例提出了一种用于发送组播报文的方法。该方法中，一个区域包括一个或多个AS域。中间设备获得与区域对应的一个或多个转发表项，任一转发表项包括区域的标识(identifier，ID)和该区域中的各AS域的关联地址。该地址可以是与AS域相关联的任意适当设备的地址。例如，可以是AS域的中间设备或出口设备的地址，或者可以是在去往AS域的路径上位于中间设备下游的某个设备的地址。中间设备从入口设备接收到组播报文之后，中间设备确定组播报文将被发送到的区域的ID，并且利用区域的ID获得第一转发表项，第一转发表项包括该区域的ID和与目的AS域对应的下一跳设备的地址。基于第一转发表项中的下一跳设备的地址。目的AS域为组播报文所对应的出口设备所在的AS域。中间设备根据第一转发表项，将组播报文发送到下一跳设备。入口设备可获得与区域对应的一 个或多个转发表项，任一转发表项包括区域的ID和中间设备的地址。入口设备获得组播报文后，确定组播报文要发送到的区域的ID，并且利用区域ID获得第二转发表项，第二转发表项包括区域ID和中间设备的地址。入口设备基于第二转发表项，将组播报文发送给中间设备。本申请实施例提供的方法中，生成用于将组播报文转发至包括一个或多个AS域的区域的转发表项，一方面能够在每个区域增加所支持的出口设备的数目，另一方面，入口设备向出口设备所在的区域发送报文，无需向所有AS域发送报文，减少了流量复制的浪费。
图1示出了本申请实施例提供的一种网络场景示意图。如图1所示，环境100例如为通信网络的一部分，可以包括骨干网络和城域网络。环境100包括入口设备105，用于将来自组播源的组播报文发送到组播接收者所通信的出口设备(图中未示出)。入口设备105可以直接连接或通过用户侧边缘设备连接到组播源(未示出)。作为示例，入口设备105可以为骨干网络中AS域的PE设备，或者城域网络中的AS域中的PE设备。
环境100还包括中间设备110。在从入口设备105到出口设备的方向，中间设备110在骨干网络或城域网络中位于入口设备105的下游。中间设备110用于将来自入口设备105的组播报文转发到出口设备。在一种可能的实现方式中，中间设备110与入口设备105位于同一AS域中。例如，入口设备105为骨干网络或城域网络中AS域的PE设备，中间设备110可以为该AS域的ASBR。在另一种可能的实现方式中，中间设备110可以与入口设备105位于不同的AS域中。例如，在入口设备105为骨干网络中AS域的实施例中，从入口设备105至出口设备的方向上，中间设备110所属的AS域位于入口设备105所属的AS域的下游。
在环境100中，多个AS域，比如图2中通过115-1、115-2、115-3……115-N标识的AS域能够与组播接收者通信，其中N为大于或等于1的整数。AS域115-1……115-N可以位于城域网络中。N个AS域115-1……115-N被划分到了M个区域120-1……120-M中，M为大于等于1且小于等于N的整数。如图1所示，区域120-1包括AS域115-1。区域120-2包括AS域115-2和115-3。区域120-M包括AS域115-N。在一种可能的实现方式中，当M为1时，区域120-1包括N个AS域115-1、115-2……115-N。其中，区域所包括的一个或多个AS域可根据需要进行配置和/或更新。AS域115-1、115-2、115-3……或115-N还被称为AS域115，区域120-1……120-M还被称为区域120。
如图1所示，中间设备110在存储有转发表125，其中每一行是一条转发表项。转发表125包括转发表项130-1、130-2、130-3……。转发表125中的个体转发表项130-1、130-2和130-3还被称为转发表项130(也被称为第一转发表项130)。
转发表125的列135记录了区域的ID(也称为“区域ID”)。转发表125的列138记录了属于区域ID所标识的区域的下一跳设备140-1、140-2……140-N的地址。下一跳设备的地址可以为IP地址。下一跳设备140-1、140-2……140-N为其所属的AS域的边缘设备，可以称为ASBR。如图1所示，转发表125的列135记录的区域120-1的区域ID表示为“2”，区域120-1包括的AS域115-1的边缘设备为下一跳设备140-1，下一跳设备140-1的地址表示为“IP地址2a”。区域120-2的区域ID表示为“3”，区域120-2包括的AS域115-2的边缘设备为下一跳设备140-2，区域120-2包括的AS域115-3的边缘设备为下一跳设备140-3，下一跳设备140-2的地址表示为“IP地址3a”，下一跳设备140-3的地址表示为“IP地址4a”。
下一跳设备140-1、140-2……140-N在以下还被称为设备140。在一种可能的实现方式中，设备140可以为其所属的AS域的ASBR。设备140可以将组播报文转发至其所属的在AS域包括的一个或多个出口设备(未示出)。出口设备可以是其所属的AS域内包括的PE设备。 在另一种可能的实现方式中，设备140可以为其所属的AS域的出口设备。中间设备110可以将组播报文直接转发给AS域的出口设备。在又一种可能的实现方式中，当入口设备105和中间设备110位于城域网的同一AS域中时，下一跳设备140可以为骨干网的AS域中的ASBR。
在图1所示的示例中，转发表125还包括列145，其存储的是138列的参数所标识的设备所属的AS域对应的BFR标识(也称为“BFR-id”)的范围。如图1所示，在列145中，“IP地址2a”所标识的下一跳设备140-1所属的AS域115-1对应的BFR-id范围为1～256，即AS域115-1中的位转发出口路由器(BFER)(也称为出口设备)可被分配的BFR-id范围为1～256。在列145中，“IP地址3a”所标识的下一跳设备140-2所属的AS域115-2对应的BFR-id范围为1～44，即AS域115-2中的BFER可被分配的BFR-id范围为1～44。在列145中，“IP地址4a”所标识的下一跳设备140-3所属的AS域115-3对应的BFR-id范围为45～144，即AS域115-3中的BFER可被分配的BFR-id范围为45～144。通过BFR-id的范围，同一区域120-2中的AS域115-2和AS域115-3可以被区分开来。其中，记录BFR-id范围的列145是可选的。对于只包括一个AS域115-1的区域120-1，与该区域120-1对应的转发表项130-1可以不包括BFR-id列145。
中间设备110可以从下一跳设备140接收指示其地址的信息以及其所属的区域ID，并且基于接收到的信息建立转发表125。在一种可能的实现方式中，下一跳设备140可直接通过BGP消息，将下一跳设备140的地址和其所属的区域ID发送给中间设备110。在另一种可能的实现方式中，下一跳设备140可以经由路由反射器(Route Reflector，简称为RR)向中间设备110发布BGP消息，该BGP消息包括下一跳设备140的地址和其所属的区域ID。可选地，下一跳设备140还可将其所属AS域对应的BFR-id的范围发布给中间设备110，比如通过BGP消息直接发布给中间设备110，或者通过RR向中间设备110发布BGP消息，相应地，BGP消息还包括下一跳设备140所属AS域对应的BFR-id的范围。例如，区域120-2包括的AS域115-2中的下一跳设备140-2向中间设备110发布的其所属的AS域115-2对应的BFR-id的范围为1～44。区域120-2包括的AS域115-3中的下一跳设备140-3向中间设备110发布的其所属的AS域115-3对应的BFR-id的范围为45～144。
为了进一步简化信令，可以设置默认区域ID。针对使用默认区域ID的区域内的AS域所包括的下一跳设备，可以不向中间设备110发送其所属的区域ID。中间设备110可以根据设置在转发表125中记录该下一跳设备所属的区域使用默认区域ID。
如图1所示，入口设备105存储有转发表150。转发表150包括多个转发表项，具体可以为转发表项155-1、155-2、155-3……。转发表150包括的转发表项155-1、155-2和155-3还被称为转发表项155(也称为第二转发表项155)。
在一种可能的实现方式中，入口设备105与中间设备110位于同一AS域中。相应地，转发表150的列160记录了区域ID，列162记录了与区域ID相对应的中间设备110的地址，例如IP地址或其他形式的地址。中间设备110可以具有多个地址，每个地址与一个区域ID相对应。在图1所示的转发表150中，与区域ID“2”(标识区域120-1)对应的中间设备地址为IP地址2b，与区域ID“3”(标识区域120-2)对应的中间设备地址为IP地址3b。可选地，转发表150还包括存储BFR-id范围的列165，其记录区域ID所标识的区域120中的BFR-id的范围。针对包括多个AS域115-2和115-3的区域120-2，可以在转发表150中创建多个转发表项155-2和155-3，转发表项155-2记录AS域115-2对应的BFR-id的范围1～44。转发表项155-3记录AS 域115-3内的BFR-id的范围45～144。
入口设备105可以从中间设备110获得区域ID、中间设备地址和BFR-id的范围，并基于所获得的上述信息生成转发表150。例如，中间设备110可以通过BGP消息将区域ID、中间设备110的地址以及区域ID所标识的区域包括的AS域对应的BFR-id的范围发布给入口设备105。中间设备110可以发布多个BGP消息，每个消息包含区域ID、中间设备110的地址以及区域包括的某个AS域的BFR-id范围。中间设备110可以通过RR发布BGP消息，也可以直接发布BGP消息。在设置了默认区域ID的实施例中，所发布的BGP消息中可以不携带区域ID。相应地，入口设备105可以根据设定获知相应的区域使用默认区域ID。
根据本申请的实施例，在入口设备105确定组播报文将被发送到的区域的ID后，利用区域ID获得包括该区域ID以及中间设备110的地址的第二转发表项155。入口设备105基于中间设备110的地址，将组播报文发送给中间设备110。中间设备110接收到该组播报文后，确定组播报文要被发送到的区域的ID。中间设备110利用区域ID获得记录该区域ID和下一跳设备140的地址的第一转发表项130。中间设备110基于第一转发表项130中下一跳设备140的地址，将组播报文发送给下一跳设备140。中间设备110和入口设备105可以获得到达一个或多个区域的转发表125和150。每个区域120可以包括一个或多个AS域115。区域120内可独立进行BFR-id规划，由此可以支持到较多出口设备的组播报文。中间设备110上的转发表125包括根据组播报文定位获得的区域ID所标识的区域120中的多个AS域115的下一跳设备地址，入口设备105无需向每个AS区域分别发送组播报文，从而显著提高了组播效率。
在另一种可能的实现方式中，入口设备105与中间设备110位于不同的AS域中，入口设备105的转发表150中列162所记录的地址可以是入口设备105与中间设备110之间转发设备的地址。
举例说明，入口设备105所位于的AS域所属的区域的ID不同于出口设备所位于的AS域所属的区域的ID。这样，入口设备105在作为出口设备的场景下，与组播源通信的入口设备和中间设备110可以基于作为出口设备的入口设备105区域ID来实现组播报文的传输。这方面的具体实施例将在下文参考图4和图5详细描述。
图2示出了本申请实施例提供的组播报文的交互流程示意图。图2所示的过程200可以在图1所述的示例场景中进行。为讨论方便，以下将结合图1来进行描述。
205，入口设备105确定组播报文将被发送到的区域120的标识。
在一种是实现方式中，来自组播源的组播报文可以包含组播接收者通信的出口设备所属的区域的ID。入口设备105可以基于接收到的组播报文确定区域ID。在另一种可能的实现方式中，组播报文中的某个字段或部分可以与区域ID之间存在映射或对应关系。组播报文中包含的目的地址可以与区域ID具有对应关系。入口设备105可以根据接收到的组播报文中的目的地址和对应关系，来确定区域ID。
210，入口设备105利用区域ID获得第二转发表项155。
举例说明，第二转发表项155包括区域ID和中间设备110的地址。如图1所示，转发表150存储了区域ID与中间设备地址的对应关系。入口设备105利用区域ID查找转发表150，可以获得包含该区域ID以及中间设备110的地址的第二转发表项155。其中，转发表150可以是静态配置的。例如，可以由人工配置。转发表150还可以是动态配置，以便进一步提高转发表的配置和更新效率，具体可参见上述图1的相关内容。
215，入口设备105基于所确定的地址将组播报文发送给中间设备110。
举例说明，入口设备105可以将所确定的中间设备110的地址封装在组播报文的目的地址中。在一种可能的实现方式中，组播报文可以包含要发送到的区域120的ID，以向中间设备110明确指示区域ID。可选地，组播报文还可包括需要发送到的出口设备所位于的AS域对应的BFR-id的范围。在另一种可能的实现方式中，区域ID与中间设备110的标识可存在映射或对应关系。中间设备110的标识可以为能够用于标识中间设备110的任意适当信息，例如包括中间设备110的地址。入口设备105可以将中间设备110的标识包含在组播报文中，以便向中间设备110隐式地指示区域ID。中间设备110的标识可以包含在组播报文的任意适当部分中。例如，入口设备105可以将中间设备110的标识包含在组播报文的目的地址字段中。以此方式，可以简化组播报文的结构，更好地实现后向兼容。中间设备110可根据组播报文中包括的中间设备110的标识和对应关系，来获得区域ID。
以此方式，入口设备105只需向一个区域120发送一份报文，而无需向所有AS域115发送，提高了组播效率。
220，中间设备110在接收到目的地址为其自身地址的组播报文后，确定组播报文将被发送到的区域120的ID。
在组播报文包含要发送到的区域120的ID的实施例中，中间设备110可以从组播报文获得区域ID。在组播报文中包含中间设备110的标识(例如，中间设备110的地址)的实施例中，中间设备110可以根据组播报文中包含的中间设备110的标识和区域ID与中间设备110间的对应关系，来确定区域ID。其中，中间设备110可以被分配多个标识(或地址)，中间设备110的各个标识与不同的区域ID相对应。在接收到组播报文后，中间设备110可以从组播报文中(例如，从组播报文的目的地址字段或部分中)获取中间设备110的标识，继而确定相应的区域ID。
225，中间设备110利用区域ID，获得第一转发表项130。
举例说明，中间设备110可以利用所确定的区域ID查找转发表125，来获得第一转发表项130。在区域120包括多个AS域115的实施例中，中间设备110可以在转发表125中查找到与某一个区域120的区域ID对应的多个转发表项130。例如，针对包括AS域115-2和115-3的区域120-2，可以查找到转发表项130-2和130-3与区域120-2的区域标识2。如果转发表项130-2和130-3中还包括AS域115-2和115-3所分别对应的的BFR-id的范围，组播报文中还包括BFR-id的范围，则中间设备110可以基于组播报文中包含的BFR-id的范围，确定对应的转发表项130-2或130-3。其中，中间设备110处的转发表125可以静态或者动态地配置。静态配置的方法可以是人工配置。动态配置的方法可参见图1的相应内容。在网络扩容时，中间设备110可以接收到来自新增加的AS域的信息，并且相应地更新转发表125，从而显著提高了转发表的配置和更新的效率。
230，中间设备110基于第一转发表项130中所包含的下一跳设备140的地址，将组播报文发送给下一跳设备140。
举例说明，对于只包括一个AS域115-1的区域120-1，中间设备110在获得了包含区域120-1的ID的转发表项130后，可以将组播报文直接发送到该区域120-1的AS域115-1，而无需对所接收组播报文进行复制处理。对于包括多个AS域115-2和115-3的区域120-2，中间设备140可以对组播报文进行复制处理，以便将组播报文和复制后的组播报文发送到区域120-2中的AS域115-2和115-3。
下面结合图3、图4和图5讨论使用根据本申请的实施例提供的方法来发送组播报文的示例过程。
图3示出了本申请实施例提供的一种组播场景。为讨论方便，以下将结合图1来描述如图3所示的场景300。
场景300与场景1不同之处在于，AS域115-4和115-5是网络扩容后增加的AS域。区域120-2包括AS域115-4。区域120-3包括AS域115-5。入口设备105和中间设备110位于骨干网络的同一AS域115-6中。入口设备105可由AS域115-6的PE设备实现。中间设备110可由由AS域115-6的ASBR实现。下一跳设备140-4属于AS域115-4。下一跳设备140-5属于AS域115-5。相同的结构的说明可参见图1所示场景的相应内容。
下一跳设备140-1、140-2和140-3可以直接将下述信息发布给中间设备110，或者可以通过RR 310发布给中间设备110。下一跳设备140-1、140-2和140-3发布的信息例如如下：
下一跳设备140-1发布的信息为：(Color＝2，IPv6地址<ASBR2>,BFR-id＝1～256)
下一跳设备140-2发布的信息为：(Color＝3，IPv6地址<ASBR3>,BFR-id＝1～44)
下一跳设备140-3发布的信息为：(Color＝3，IPv6地址<ASBR4>,BFR-id＝45～144)
其中，Color＝2表示区域120-1的区域ID，ASBR2表示设备140-1，IPv6地址<ASBR2>表示设备140-1的IPv6地址，BFR-id＝1～256表示AS域115-1对应的BFR-id的范围。Color＝3表示区域120-2的ID，ASBR3表示设备140-2，IPv6地址<ASBR3>表示设备140-2的IPv6地址，BFR-id＝1～44表示AS域115-2对应的BFR-id的范围。Color＝3表示区域120-2的ID，ASBR4表示设备140-3，IPv6地址<ASBR4>表示设备140-3的IPv6地址，BFR-id＝45～144表示AS域115-3内的BFR-id的范围。
中间设备110根据收到的信息建立转发表125。在此示例中，转发表125包括下列多条转发表项130：
-(Color＝2,BFR-id＝1～256,下一跳＝IPv6地址<ASBR2>)
-(Color＝3,BFR-id＝1～44,下一跳＝IPv6地址<ASBR3>)
-(Color＝3,BFR-id＝45～144,下一跳＝IPv6地址<ASBR4>)
在来自入口设备105的组播报文到达中间设备110后，中间设备110首先确定区域120的区域ID。在一种可能的实现方式中，组播报文(例如，BIERv6组播报文)中可以携带一个Color值，用于表示区域ID。在另一种可能的实现方式中，中间设备110可以获得Color值与中间设备110的标识的对应关系。中间设备110根据该对应关系以及组播报文包括的中间设备110的标识，确定用于表示区域ID的Color值。其中，Color值与中间设备110的地址的对应关系，例如Color＝2与地址2001:db1::2对应、Color＝3与地址2001:db1::3对应。该对应关系可以静态或动态配置。如果中间设备110接收到的组播报文的目的地址是2001:db1::2，则可以确定组播报文要发送给Color＝2标识的区域120-1。中间设备110再根据组播报文中包含的BFR-id的范围来确定下一跳地址。例如，在组播报文为BIERv6组播报文的实施例中，中间设备110可以根据BIERv6报文包括比特串确定BFR-id的范围。中间设备110根据该BFR-id的范围和转发表125，确定下一跳地址为IPv6地址<ASBR2>。对于包括AS域115-2和115-3的区域120-2，中间设备110在根据组播报文的目的地址2001:db1::3确定Color＝3标识的区域120-2后，进一步根据组播报文中包含的BFR-id的范围来确定下一跳地址为IPv6地址<ASBR3>和IPv6地址<ASBR4>中的一个或多个。如果需要发送给多个下一跳设备，则中间设备110可以对组播报文里的比特串进行复制处理，以便将组播报文发送到AS域115-2和 115-3。
在场景300中，中间设备110可以指示将区域ID、相应的自身地址以及可选的BFR-id范围的信息发布给入口设备105。中间设备110可以通过RR 310将该信息发布给入口设备105，也可以直接发布。在此示例中，中间设备110可以将如下信息发布给入口设备105：
-(Color＝2,IPv6地址＝2001:db1::2)
-(Color＝2,BFR-id＝1～256)
-(Color＝3,IPv6地址＝2001:db1::3)
-(Color＝3,BFR-id＝1～44)
-(Color＝3,BFR-id＝45～144)
上述信息包含(Color,IPv6地址)的对应关系，其中IPv6地址表示中间设备110的IPv6地址，其与区域ID相对应。可选地，该信息还包含Color值所标识的区域中的各AS域内的BFR-id范围的信息，即(Color,BFR-id)信息。
入口设备105在接收到中间设备110发布的信息后，可以获得如下转发表项155：
-(Color＝2,BFR-id＝1～256,下一跳＝2001:db1::2)
-(Color＝3,BFR-id＝1～44,下一跳＝2001:db1::3)
-(Color＝3,BFR-id＝45～144,下一跳＝2001:db1::3)
可选地，后面的2条转发表项155可以合并如下：
-(Color＝2,BFR-id＝1～256,下一跳＝2001:db1::2)
-(Color＝3,BFR-id＝1～144,下一跳＝2001:db1::3)
其中，下一跳＝2001:db1::2和下一跳＝2001:db1::3都是中间设备110的地址，不同的地址对应于由不同Color值所标识的区域。BFR-id＝1～256和BFR-id＝1～144是可选的参数。
在场景300中，网络进行了扩容，例如增加了AS域115-4。AS域115-4对应112个BFR-id，与AS 115-2和115-3对应的BFR-id合计为256个。AS域115-4的下一跳设备140-4将区域ID、下一跳设备140-4的地址及AS域115-4对应的BFR-id的范围发布给中间设备110。例如，设备140-4可以通过RR 310向中间设备110发布如下信息：(Color＝3，IPv6地址<ASBR5>，BFR-id＝145～256)，其中，Color＝3表示区域120-2的区域ID，ASBR5表示设备140-4，IPv6地址<ASBR5>表示设备140-4的IPv6地址。
中间设备110在接收到上述信息后在转发表125中增加一条表项：(Color＝3,BFR-id＝145～256,下一跳＝IPv6地址<ASBR5>)。中间设备110可以通过RR 310向入口设备105发布增加的信息(Color＝3,BFR-id＝145～256,下一跳＝2001:db1::3)。其中，下一跳＝2001:db1::3是中间设备110与区域120-2对应的地址。
入口设备105接收到上述信息后，创建如下转发表项155，以更新转发表150：
-(Color＝2,BFR-id＝1 to 256,下一跳＝2001:db1::2)
-(Color＝3,BFR-id＝1 to 256,下一跳＝2001:db1::3)
在网络扩容增加了一个AS域115-4时，只需要对扩容的设备140-4进行配置，其他设备或节点都不需要额外配置，入口设备和中间设备可以自动更新各自的转发表，提高了转发表的更新效率。
举例说明，网络继续扩容，例如又增加了一个AS域115-5，其BFR-id有65500个。可以将AS域115-5设置为一个新的区域120-3，可以配置Color＝6来表示区域120-3的ID。AS域115-5设备140-5可以将区域ID、设备140-5的地址以及AS域115-5内的BFR-id范围通过RR  310发布给中间设备110。所发布的信息例如为(Color＝6，IPv6地址<ASBR6>，BFR-id＝1～65500)，其中，Color＝6表示区域120-3的区域ID，ASBR6表示设备140-5，并且IPv6地址<ASBR6>表示设备140-5的IPv6地址。
中间设备110接收到上述信息后在转发表125中增加一条表项(Color＝6,BFR-id＝1～65500,下一跳＝IPv6地址<ASBR6>)。中间设备110通过RR 310向入口设备105发布增加的信息(Color＝6,BFR-id＝1～65500,下一跳＝2001:db1::6)。入口设备105接收到上述信息后，创建如下转发表项155，以更新转发表150：
-(Color＝2,BFR-id＝1～256,下一跳＝2001:db1::2)
-(Color＝3,BFR-id＝1～256,下一跳＝2001:db1::3)
-(Color＝6,BFR-id＝1～65500,下一跳＝2001:db1::6)
其中，2001:db1::6是中间设备110的另外一个IPv6地址，与Color＝6表示的区域ID相对应。该地址可以由中间设备110根据接收到的Color值动态申请，从而不必额外配置，提高了效率。此外，中间设备110也可配置Color＝6对应的地址。这两种方式都不需要入口设备105增加额外的配置。
下面讨论使用本申请的实施例的组播机制的示例组播配置。BGP路由可以采用BGP IPv6单播(BGP IPv6-Unicast)地址族，或者可以采用其它地址族，例如BGP链路状态(BGP-LS)地址族。备选地，可以是一个新建的地址族，如BIER地址族。作为示例，可以使用IPv6-Unicast地址族并且通过RR 310进行发布。在此示例中，设备140-1表示为ASBR2，设备140-2表示为ASBR3，设备140-3表示为ASBR4，中间设备110表示为ASBR1b，入口设备105表示为PE1。这些设备可配置如下：
Figure PCTCN2021093063-appb-000001
Figure PCTCN2021093063-appb-000002
Figure PCTCN2021093063-appb-000003
图4示出了本申请实施例提供的另一种组播场景。
与图1中的场景100和图3中的场景300不同，在图4所示的场景400中，入口设备105和中间设备110位于不同的AS域中。如图4所示，入口设备105位于城域网络的AS域115-6中，例如实现为AS域115-6的PE设备。中间设备110位于骨干网络的AS域115-7中，例如实现为AS域115-7的ASBR。而且，不同于场景300，AS域115-7中的另一ASBR 405-7充当与AS域115-1……115-5相关联的下一跳设备。发往各个AS域115-1……115-5的组播报文，经由ASBR 405-7转发到这些AS域115-1……115-5的ASBR 405-1……405-5。中间设备110与ASBR 405-7可以都与RR 310建立BGP邻居，以便ASBR 405-7经由RR 310向中间设备110发布相关的路由信息。在场景400中，AS域115-6属于区域120-4，其具有与区域120-1、120-2和120-3不同的区域ID。相应地，在中间设备110处建立转发表125可以包括以入口设备105作为组播目的地的转发表项，其中记录区域120-4的区域ID。在此示例中，AS域115-6的ASBR 405-6充当与区域120-4相关联的下一跳设备。入口设备105的区域ID、相关联的下一跳设备的地址以及区域120-4的BFR-id范围可以由ASBR 405-6经由RR 310发布给中间设备110。由于入口设备105所在的区域120-4与区域120-1、120-2和120-3的区域ID不同，在经由RR 310发布路由信息时，RR 310可以利用区域ID对路由信息的目的地设备进行区分。
图5示出了本申请实施例提供的另一种组播场景。在图5所示的场景500中，ASBR 405-1……405-7分别是AS域115-1……115-7中的ASBR，而ASBR 405-8是AS域115-7中的另一ASBR。405-7和405-8都可以充当中间设备。在此示例中，路由信息不经由RR发布，而由各设备直接发布给上下游设备。
在场景500中，各AS域115-1……115-5的ASBR 405-1……405-5作为原始的路由发布方，发布如下的路由信息：
ASBR 405-1发布的路由信息为：(prefix＝ASBR2,NextHop＝ASBR2,Color＝2,BIER-info＝<BFR-id-range 1 to 256>)
ASBR 405-2发布的路由信息为：(prefix＝ASBR3,NextHop＝ASBR3,Color＝3,BIER-info＝<BFR-id-range 1 to 44>)
ASBR 405-3发布的路由信息为：(prefix＝ASBR4,NextHop＝ASBR4,Color＝3,BIER-info＝<BFR-id-range 45 to 144>)
ASBR 405-4发布的路由信息为：(prefix＝ASBR5,NextHop＝ASBR5,Color＝3,BIER-info＝<BFR-id-range 145 to 256>)
ASBR 405-5发布的路由信息为：(prefix＝ASBR6,NextHop＝ASBR6,Color＝6,BIER-info＝<BFR-id-range 1 to 65500>)
其中，prefix(前缀)这个字段用来携带IP地址前缀，NextHop(下一跳)这个字段用来携带IP地址，BIER-info表示BIER信息，BFR-id-range表示BFR-id的范围。ASBR2、ASBR3、ASBR4、ASBR5和ASBR6分别表示ASBR 405-1、405-2、405-3、405-4和405-5。
作为与AS域115-6相关联的下一跳设备的ASBR 405-6也是原始的路由发布方，其发布关于AS域115-6的如下路由信息：
-(prefix＝ASBR0,NextHop＝ASBR0,Color＝7,BIER-info＝<BFR-id-range 1 to 256>)
其中，ASBR0表示ASBR 405-6，并且Color＝7表示AS域115-6所属的区域120-4的区域ID。
ASBR 405-8和ASBR 405-7不是原始的路由发布方，但会将其他设备发布的路由信息向其他的内部BGP(iBGP)对等体或外部BGP(eBGP)对等体重新发布。例如，ASBR 405-7可以从作为eBGP对等体的ASBR 405-1……405-5收到相应的路由信息，然后向作为iBGP对等体的ASBR 405-8发布，并且发布的时候会将路由的下一跳更改为自己。这可以通过路由策略实现。ASBR 405-8可以从作为eBGP对等体的ASBR 405-6收到路由信息，然后向作为iBGP对等体的ASBR 405-7发布，并且发布的时候也会通过路由策略将路由的下一跳更改为自己。ASBR 405-8和ASBR 405-7还可以将路由信息发布给同一个AS域115-7内作为iBGP对等体的PE 505。PE 505可以充当AS域115-7的入口设备。此时，ASBR 405-7可以作为与其相关联的中间设备。这样，PE 505可以获得如下的路由信息，其中ASBR1b表示ASBR 405-7，ASBR1a表示ASBR 405-8：
-(prefix＝ASBR2,NextHop＝ASBR1b,Color＝2,BIER-info＝<BFR-id-range 1 to 256>)
-(prefix＝ASBR3,NextHop＝ASBR1b,Color＝3,BIER-info＝<BFR-id-range 1 to 44>)
-(prefix＝ASBR4,NextHop＝ASBR1b,Color＝3,BIER-info＝<BFR-id-range 45 to 144>)
-(prefix＝ASBR5,NextHop＝ASBR1b,Color＝3,BIER-info＝<BFR-id-range 145 to 256>)
-(prefix＝ASBR6,NextHop＝ASBR1b,Color＝6,BIER-info＝<BFR-id-range 1 to 65500>)
-(prefix＝ASBR0,NextHop＝ASBR1a,Color＝7,BIER-info＝<BFR-id-range 1 to 256>)
PE 505可以据此建立到达AS域115-1……115-6的如下BIER转发表项：
-(Color＝2,BFR-id＝1～256,下一跳＝ASBR1b)
-(Color＝3,BFR-id＝1～256,下一跳＝ASBR1b)
-(Color＝4,BFR-id＝1～65550,下一跳＝ASBR1b)
-(Color＝7,BFR-id＝1～256,下一跳＝ASBR1a)
在场景500中，ASBR 405-7将从作为eBGP对等体的ASBR 405-1……405-5接收到的路由信息向作为iBGP的对等体的PE 505和ASBR 405-8发布时，可以将下一跳地址设置为自己的一个或多个标识，以用于指示相应的区域ID。这样，在ASBR 405-7接收到组播报文后，ASBR 405-7可以根据组播报文中包含的标识来确定相应的区域ID。如此，PE 505可以获得如下路由信息：
-(prefix＝ASBR2,NextHop＝ASBR1b2,Color＝2,BIER-info＝<BFR-id-range 1 to 256>)
-(prefix＝ASBR3,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 1 to 44>)
-(prefix＝ASBR4,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 45 to 144>)
-(prefix＝ASBR5,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 145 to 256>)
-(prefix＝ASBR6,NextHop＝ASBR1b6,Color＝6,BIER-info＝<BFR-id-range 1 to  65500>)
-(prefix＝ASBR0,NextHop＝ASBR1a,Color＝7,BIER-info＝<BFR-id-range 1 to 256>)
其中，ASBR1b2、ASBR1b3、ASBR1b6和ASBR1a表示分别对应于区域ID Color＝2、Color＝3、Color＝6和Color＝7的ASBR 405-7的标识。
PE 505可以据此建立到达AS域115-1……115-6的如下BIER转发表项：
-(Color＝2,BFR-id＝1～256,下一跳＝ASBR1b2)
-(Color＝3,BFR-id＝1～256,下一跳＝ASBR1b3)
-(Color＝4,BFR-id＝1～65550,下一跳＝ASBR1b6)
-(Color＝7,BFR-id＝1～256,下一跳＝ASBR1a)
而且，ASBR 405-8可以获得如下路由信息：
-(prefix＝ASBR2,NextHop＝ASBR1b2,Color＝2,BIER-info＝<BFR-id-range 1 to 256>)
-(prefix＝ASBR3,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 1 to 44>)
-(prefix＝ASBR4,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 45 to 144>)
-(prefix＝ASBR5,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 145 to 256>)
-(prefix＝ASBR6,NextHop＝ASBR1b6,Color＝6,BIER-info＝<BFR-id-range 1 to 65500>)
-(prefix＝ASBR0,NextHop＝ASBR0,Color＝7,BIER-info＝<BFR-id-range 1 to 256>)
ASBR 405-8可以据此建立到达AS域115-1……115-6的BIER转发表项。ASBR 405-8建立的到达AS域115-6的BIER转发表项的下一跳是ASBR 405-6。
类似地，ASBR 405-7可以获得如下的路由信息：
-(prefix＝ASBR2,NextHop＝ASBR2,Color＝2,BIER-info＝<BFR-id-range 1 to 256>)
-(prefix＝ASBR3,NextHop＝ASBR3,Color＝3,BIER-info＝<BFR-id-range 1 to 44>)
-(prefix＝ASBR4,NextHop＝ASBR4,Color＝3,BIER-info＝<BFR-id-range 45 to 144>)
-(prefix＝ASBR5,NextHop＝ASBR5,Color＝3,BIER-info＝<BFR-id-range 145 to 256>)
-(prefix＝ASBR6,NextHop＝ASBR6,Color＝6,BIER-info＝<BFR-id-range 1 to 65500>)
-(prefix＝ASBR0,NextHop＝ASBR1a,Color＝7,BIER-info＝<BFR-id-range 1 to 256>)
ASBR 405-7可以据此建立到达AS域115-1……115-6的BIER转发表项。ASBR 405-7建立的到达AS域115-1……115-5的BIER转发表的下一跳是ASBR 405-1……405-5。
在一种可能的实现方式中，ASBR 405-8不会将从ASBR 405-6发布的路由信息再发布给ASBR 405-6，但会将从ASBR 405-7发布的路由信息向ASBR 405-6发布并且不修改下一跳，这可以通过路由策略实现。相应的，ASBR 405-6可以获得如下的路由信息：
-(prefix＝ASBR2,NextHop＝ASBR1b2,Color＝2,BIER-info＝<BFR-id-range 1 to 256>)
-(prefix＝ASBR3,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 1 to 44>)
-(prefix＝ASBR4,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 45 to 144>)
-(prefix＝ASBR5,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 145 to 256>)
-(prefix＝ASBR6,NextHop＝ASBR1b6,Color＝6,BIER-info＝<BFR-id-range 1 to  65500>)
ASBR 405-6可以据此建立到达AS域115-1……115-5的BIER转发表项。ASBR 405-6到达AS域115-6的各BFR-id的BIER转发表项属于AS域内，可以不通过BGP消息建立。
在一种可能的实现方式中，ASBR 405-6将从ASBR 405-8发布的路由信息再向入口设备105发布且不修改下一跳，这可以通过路由策略实现。相应的，入口设备105可以获得如下的路由信息：
-(prefix＝ASBR2,NextHop＝ASBR1b2,Color＝2,BIER-info＝<BFR-id-range 1 to 256>)
-(prefix＝ASBR3,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 1 to 44>)
-(prefix＝ASBR4,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 45 to 144>)
-(prefix＝ASBR5,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 145 to 256>)
-(prefix＝ASBR6,NextHop＝ASBR1b6,Color＝6,BIER-info＝<BFR-id-range 1 to 65500>)
入口设备105可以据此建立到达AS域115-1……115-5的BIER转发表项。入口设备105到达AS域115-6的各BFR-id的BIER转发表项属于AS域内，可以不通过BGP消息建立。
此外，ASBR 405-7可以将接收到的路由信息进一步发布给ASBR 405-1……405-5。例如，ASBR 405-7可以将ASBR 405-8发布的路由信息再发布给ASBR 405-1……405-5并且不更改路由下一跳。
ASBR 405-7还可以将ASBR 405-2……405-6发布的路由再发布给ASBR 405-1，并且将路由下一跳更改为自己。ASBR 405-1可以将从ASBR 405-7发布的路由再发布给AS域115-1中的PE 510-1(可以充当AS域115-1的入口设备)，并且不更改路由下一跳。
相应的，ASBR 405-1和PE 510-1都可以获得如下路由信息，并可据此建立相应的BIER转发表项：
-(prefix＝ASBR3,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 1 to 44>)
-(prefix＝ASBR4,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 45 to 144>)
-(prefix＝ASBR5,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 145 to 256>)
-(prefix＝ASBR6,NextHop＝ASBR1b6,Color＝6,BIER-info＝<BFR-id-range 1 to 65500>)
-(prefix＝ASBR0,NextHop＝ASBR1a,Color＝7,BIER-info＝<BFR-id-range 1 to 256>)
ASBR 405-7还可以将ASBR 405-1、405-3、405-4、405-5和405-6发布的路由再发布给ASBR 405-2，并且将下一跳更改为自己。ASBR 405-2还可以将从ASBR 405-7发布的路由再发布给PE 510-2(可以充当AS域115-2的入口设备)，并且不更改路由下一跳。
相应的，ASBR 405-2和PE 510-2都可以获得如下路由信息，并可据此建立相应的BIER转发表项：
-(prefix＝ASBR2,NextHop＝ASBR1b2,Color＝2,BIER-info＝<BFR-id-range 1 to 256>)
-(prefix＝ASBR4,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 45 to 144>)
-(prefix＝ASBR5,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 145 to 256>)
-(prefix＝ASBR6,NextHop＝ASBR1b6,Color＝6,BIER-info＝<BFR-id-range 1 to 65500>)
-(prefix＝ASBR0,NextHop＝ASBR1a,Color＝7,BIER-info＝<BFR-id-range 1 to 256>)
ASBR 405-7还可以将ASBR 405-1、405-2、405-4、405-5和405-6发布的路由再发布给ASBR 405-3，并且将下一跳更改为自己。ASBR 405-3还可以将从ASBR 405-7发布的路由再发布给PE 510-3(可以充当AS域115-3的入口设备)，并且不更改路由下一跳。
ASBR 405-3和PE 510-3都会可以获得如下路由信息，并可据此建立相应的BIER转发表项：
-(prefix＝ASBR2,NextHop＝ASBR1b2,Color＝2,BIER-info＝<BFR-id-range 1 to 256>)
-(prefix＝ASBR3,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 1 to 44>)
-(prefix＝ASBR5,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 145 to 256>)
-(prefix＝ASBR6,NextHop＝ASBR1b6,Color＝6,BIER-info＝<BFR-id-range 1 to 65500>)
-(prefix＝ASBR0,NextHop＝ASBR1a,Color＝7,BIER-info＝<BFR-id-range 1 to 256>)
类似地，ASBR 405-4可以获得如下路由信息，并可据此建立相应的BIER转发表项：
-(prefix＝ASBR2,NextHop＝ASBR1b2,Color＝2,BIER-info＝<BFR-id-range 1 to 256>)
-(prefix＝ASBR3,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 1 to 44>)
-(prefix＝ASBR4,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 45 to 144>)
-(prefix＝ASBR6,NextHop＝ASBR1b6,Color＝6,BIER-info＝<BFR-id-range 1 to 65500>)
-(prefix＝ASBR0,NextHop＝ASBR1a,Color＝7,BIER-info＝<BFR-id-range 1 to 256>)
ASBR 405-5可以获得如下路由信息，并可据此建立相应的BIER转发表项：
-(prefix＝ASBR2,NextHop＝ASBR1b2,Color＝2,BIER-info＝<BFR-id-range 1 to 256>)
-(prefix＝ASBR3,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 1 to 44>)
-(prefix＝ASBR4,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 45 to 144>)
-(prefix＝ASBR5,NextHop＝ASBR1b3,Color＝3,BIER-info＝<BFR-id-range 145 to 256>)
-(prefix＝ASBR0,NextHop＝ASBR1a,Color＝7,BIER-info＝<BFR-id-range 1 to 256>)
在此示例中，入口设备105和ASBR 405-6记录的ASBR 405-1……405-5的下一跳都是ASBR 405-7，如果采用IPv6单播路由(即IPv6 Unicast地址族)的方式，可以要求IPv6单播路由不生成相应的单播转发表，而生成BIER的转发表，这可以通过对IPv6单播路由使用路由策略实现。如果采用其它的地址族，比如可以采用IPv6组播路由(即IPv6 Multicast地址族)的方式，则IPv6组播路由本身就不生成单播转发表，只需要根据这些IPv6组播路由及其携带的区域ID信息(如Color值)、BIER信息(如BFR-id范围)生成BIER转发表。
图6示出了本申请实施例提供的用于发送组播报文的装置的结构示意图。图6所示的装 置600可以设置于图1至图5对应的的任一实施例中的中间设备。下文将结合图1和图6，对装置600进行说明。
如图6所示，装置600包括第一获得模块605、第二获得模块610和第一发送模块615。第一获得模块605用于基于来自入口设备的组播报文，获取组播报文对应的区域的标识。第二获得模块610用于基于区域的标识和转发表项，获得下一跳设备的地址，转发表项包含区域的标识以及下一跳设备的地址。第一发送模块615用于基于下一跳设备的地址发送组播报文。
在一种可能的实现方式中，组播报文包括区域的标识，第一获得模块605用于从组播报文中获取区域的标识。
在一种可能的实现方式中，第一获得模块605用于基于组播报文中的中间设备的标识，获取与中间设备的标识对应的区域的标识。其中，装置600可保存一对应关系，该对应关系包括中间设备的标识和区域的标识。
在一种可能的实现方式中，第一获得模块605用于基于组播报文中的中间设备的地址，获取与中间设备的地址对应的区域的标识。其中，装置600可保存一对应关系，该对应关系包括中间设备的地址和区域的标识。
在一种可能的实现方式中，装置600还可以包括：第一接收模块，用于接收下一跳设备发送的下一跳设备的地址和下一跳设备所属的区域的标识；以及第三获得模块，用于基于区域的标识和下一跳设备的地址，获得转发表项。
在一种可能的实现方式中，装置600还可以包括：第一接收模块，用于接收下一跳设备发送的下一跳设备的标识和下一跳设备所属的区域的标识。第三获得模块，用于基于下一跳设备的标识，获得下一跳设备的地址；所述第三获得模块用于基于区域的标识和下一跳设备的地址，获得转发表项。其中，装置600可保存一对应关系，该对应关系包括下一跳设备的标识和下一跳设备的地址。
在一种可能的实现方式中，第一接收模块还用于接收下一跳设备发送的目的AS域内位转发路由器BFR标识的范围，目的AS域为区域包含的下一跳设备所属的AS域，转发表项还包括目的AS域内BFR标识的范围。相应地，组播报文还包括BFR标识的范围，第三获得模块用于基于区域的标识和BFR标识的范围，确定转发表项。
在一种可能的实现方式中，装置600还可以包括：第二发送模块，用于向入口设备发送中间设备的地址和中间设备所属的区域的标识。
在一种可能的实现方式中，第二发送模块还用于向入口设备发送中间设备所属AS域内BFR标识的范围，中间设备所属AS域包含于中间设备所属的区域。
图7示出了本申请实施例提供的用于发送组播报文的装置的结构示意图。图7所示的装置700可以设置于图1至图5对应的的任一实施例中的入口设备。下文将结合图1和图7，对装置700进行说明。
如图7所示，装置700包括第一获得模块705、第二获得模块710和第一发送模块715。第一获得模块705用于获取接收到的组播报文对应的区域的标识。第二获得模块710用于基于区域的标识和转发表项，获得用于将组播报文转发至区域的中间设备的地址，转发表项包括区域的标识以及中间设备的地址。第一发送模块715用于基于中间设备的地址发送组播报文。
在一种可能的实现方式中，装置700还可以包括：第二接收模块，用于接收中间设备发 送的中间设备的地址和区域的标识；以及第三获得模块，用于基于中间设备的地址和区域的标识，获得转发表项。
在一种可能的实现方式中，装置700还可以包括：第二接收模块，用于接收中间设备发送的中间设备的标识和区域的标识；以及第三获得模块，用于基于中间设备的标识，确定中间设备的地址；所述第三获得模块用于基于中间设备的地址和区域的标识，获得转发表项。
在一种可能的实现方式中，第二接收模块还用于接收中间设备发送的目的自治系统AS域内BFR标识的范围，目的AS域为区域包含的组播报文需要发送到的AS域，转发表项还包括目的AS域内BFR标识的范围。
在一种可能的实现方式中，第二获得模块710用于基于目的AS域内BFR标识的范围和区域的标识，确定转发表项。
在一种可能的实现方式中，组播报文中包含区域的标识，并且第一获得模块705用于从组播报文获取区域的标识。
在一种可能的实现方式中，组播报文中包含中间设备的标识，第一获得模块705用于基于组播报文中的中间设备的标识，获取与中间设备的标识对应的区域的标识。
装置600和700中所包括的模块可以利用各种方式来实现，包括软件、硬件、固件或其任意组合。在一些实施例中，一个或多个模块可以使用软件和/或固件来实现，例如存储在存储介质上的机器可执行指令。除了机器可执行指令之外或者作为替代，装置600和700中的部分或者全部模块可以至少部分地由一个或多个硬件逻辑组件来实现。作为示例而非限制，可以使用的示范类型的硬件逻辑组件包括现场可编程门阵列(FPGA)、专用集成电路(ASIC)、专用标准品(ASSP)、片上系统(SOC)、复杂可编程逻辑器件(CPLD)，等等。
图8示出了其中可以实施本申请的某些实施例的设备800的框图。设备800能够用来实现例图1至图7对应的任一实施例提供的中间设备或入口设备。如图8所示，设备800包括处理器810、存储器820、通信接口830和通信总线840。处理器810、存储器820和通信接口830通过通信总线840进行内部交互。通信总线840可与外部设备或装置进行交互。其中。当设备800设置于中间设备时，所述存储器820用于存储指令；所述处理器810用于执行所述存储器中的所述指令，执行上述图2至图5对应的任一实施例提供的由中间设备执行的方法。当设备800设置于入口设备时，所述存储器820用于存储指令；所述处理器810用于执行所述存储器中的所述指令，执行上述图2至图5对应的任一实施例提供的由入口设备执行的方法。，存储器820可以是适用于本地技术环境的任何合适的类型，并且可以利用任何合适的数据存储技术来实现，包括但不限于基于半导体的存储器件、磁存储器件和系统、光存储器件和系统。尽管图8中仅仅示出了一个存储器单元，但是在设备800中可以有多个物理不同的存储器单元。处理器810可以是适用于本地技术环境的任何合适的类型，并且可以包括但不限于通用计算机、专用计算机、微控制器、数字信号控制器(DSP)以及基于控制器的多核控制器架构中的一个或多个。设备800也可以包括多个处理器810。处理器810与通信单元840耦合。通信单元840可以通过无线电信号或者借助于光纤、电缆和/或其他部件来实现信息的接收和发送。
一般而言，本申请的各种示例实施例可以在硬件或专用电路、软件、逻辑，或其任何组合中实施。某些方面可以在硬件中实施，而其他方面可以在可以由控制器、微处理器或 其他计算设备执行的固件或软件中实施。当本申请的示例实施例的各方面被图示或描述为框图、流程图或使用某些其他图形表示时，将理解此处描述的方框、装置、系统、技术或方法可以作为非限制性的示例在硬件、软件、固件、专用电路或逻辑、通用硬件或控制器或其他计算设备，或其某些组合中实施。
作为示例，本申请的示例实施例可以在机器或计算机可执行指令的上下文中被描述，机器可执行指令诸如包括在目标的真实或者虚拟处理器上的器件中执行的程序模块中。一般而言，程序模块包括例程、程序、库、对象、类、组件、数据结构等，其执行特定的任务或者实现特定的抽象数据结构。在各示例实施例中，程序模块的功能可以在所描述的程序模块之间合并或者分割。用于程序模块的机器可执行指令可以在本地或者分布式设备内执行。在分布式设备中，程序模块可以位于本地和远程存储介质二者中。
用于实现本申请实施例的方法的计算机程序代码可以用一种或多种编程语言编写。这些计算机程序代码可以提供给通用计算机、专用计算机或其他可编程的数据处理装置的处理器，使得程序代码在被计算机或其他可编程的数据处理装置执行的时候，引起在流程图和/或框图中规定的功能/操作被实施。程序代码可以完全在计算机上、部分在计算机上、作为独立的软件包、部分在计算机上且部分在远程计算机上或完全在远程计算机或服务器上执行。
在本申请实施例的上下文中，机器可读介质或计算机可读介质可以是包含或存储用于或有关于指令执行系统、装置或设备的程序的任何有形介质。机器可读介质可以是机器可读信号介质或机器可读存储介质。机器可读介质可以包括但不限于电子的、磁的、光学的、电磁的、红外的或半导体系统、装置或设备，或其任意合适的组合。机器可读存储介质的更详细示例包括带有一根或多根导线的电气连接、便携式计算机磁盘、硬盘、随机存储存取器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM或闪存)、光存储设备、磁存储设备，或其任意合适的组合。
另外，尽管操作以特定顺序被描绘，但这并不应该理解为要求此类操作以示出的特定顺序或以相继顺序完成，或者执行所有图示的操作以获取期望结果。在某些情况下，多任务或并行处理会是有益的。同样地，尽管上述讨论包含了某些特定的实施细节，但这并不应解释为限制任何发明或权利要求的范围，而应解释为对可以针对特定发明的特定示例实施例的描述。本说明书中在分开的示例实施例的上下文中描述的某些特征也可以整合实施在单个示例实施例中。反之，在单个示例实施例的上下文中描述的各种特征也可以分离地在多个示例实施例或在任意合适的子组合中实施。
尽管已经以特定于结构特征和/或方法动作的语言描述了主题，但是应当理解，所附权利要求中限定的主题并不限于上文描述的特定特征或动作。相反，上文描述的特定特征和动作是作为实现权利要求的示例形式而被公开的。

Claims (29)

  1. 一种用于发送组播报文的方法，其特征在于，所述方法包括：
    中间设备基于来自入口设备的组播报文，获取所述组播报文对应的区域的标识；
    所述中间设备基于所述区域的所述标识和转发表项，获得下一跳设备的地址，所述转发表项包含所述区域的所述标识以及所述下一跳设备的所述地址；
    所述中间设备基于所述下一跳设备的所述地址发送所述组播报文。
  2. 根据权利要求1所述的方法，其特征在于，所述组播报文包括所述区域的所述标识，所述中间设备基于来自入口设备的组播报文，获取所述组播报文对应的区域的标识包括：所述中间设备从所述组播报文中获取所述区域的所述标识；或者
    所述组播报文包括所述中间设备的标识，所述中间设备基于来自入口设备的组播报文，获取所述组播报文对应的区域的标识包括：所述中间设备基于所述组播报文中的所述中间设备的标识，获取与所述中间设备的标识对应的所述区域的所述标识。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述中间设备接收所述下一跳设备发送的所述下一跳设备的所述地址和所述下一跳设备所属的所述区域的所述标识；
    所述中间设备基于所述区域的所述标识和所述下一跳设备的所述地址，获得所述转发表项。
  4. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述中间设备接收所述下一跳设备发送的所述下一跳设备的标识和所述下一跳设备所属的所述区域的所述标识；
    所述中间设备基于所述下一跳设备的标识，获得所述下一跳设备的所述地址；
    所述中间设备基于所述区域的所述标识和所述下一跳设备的所述地址，获得所述转发表项。
  5. 根据权利要求3或4所述的方法，其特征在于，所述方法还包括：
    所述中间设备接收所述下一跳设备发送的目的AS域内位转发路由器BFR标识的范围，所述目的AS域为所述区域包含的所述下一跳设备所属的AS域，所述转发表项还包括所述目的AS域内BFR标识的范围。
  6. 根据权利要求5所述的方法，其特征在于，所述组播报文还包括所述BFR标识的范围，所述方法还包括：
    所述中间设备基于所述区域的所述标识和所述BFR标识的范围，确定所述转发表项。
  7. 根据权利要求1至6任一所述的方法，其特征在于，所述方法还包括：
    所述中间设备向所述入口设备发送所述中间设备的地址和所述中间设备所属的区域的标识。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述中间设备向所述入口设备发送所述中间设备所属AS域内BFR标识的范围，所述中间设备所属AS域包含于所述中间设备所属的区域。
  9. 一种用于发送组播报文的方法，其特征在于，所述方法包括：
    入口设备获取接收到的组播报文对应的区域的标识；
    所述入口设备基于所述区域的标识和转发表项，获得用于将所述组播报文转发至所述区域的中间设备的地址，所述转发表项包括所述区域的所述标识以及所述中间设备的所述 地址；
    所述入口设备基于所述中间设备的所述地址发送所述组播报文。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述入口设备接收所述中间设备发送的所述中间设备的所述地址和所述区域的所述标识；
    所述入口设备基于所述中间设备的所述地址和所述区域的所述标识，获得所述转发表项。
  11. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述入口设备接收所述中间设备发送的所述中间设备的标识和所述区域的所述标识；
    所述入口设备基于所述中间设备的所述标识，确定所述中间设备的所述地址；
    所述入口设备基于所述中间设备的所述地址和所述区域的所述标识，获得所述转发表项。
  12. 根据权利要求10或11所述的方法，其特征在于，所述方法还包括：
    所述入口设备接收所述中间设备发送的目的自治系统AS域内BFR标识的范围，所述目的AS域为所述区域包含的所述组播报文需要发送到的AS域，所述转发表项还包括所述目的AS域内BFR标识的范围。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述入口设备基于所述目的AS域内BFR标识的范围和所述区域的所述标识，确定所述转发表项。
  14. 根据权利要求9至13任一所述的方法，其特征在于，所述组播报文中包含所述区域的所述标识，所述入口设备获取接收到的组播报文对应的区域的标识包括：所述入口设备从所述组播报文获取所述区域的所述标识；或者
    所述组播报文中包含所述中间设备的标识，所述入口设备获取接收到的组播报文对应的区域的标识包括：所述入口设备基于所述组播报文中的所述中间设备的标识，获取与所述中间设备的标识对应的所述区域的所述标识。
  15. 一种用于发送组播报文的装置，其特征在于，所述装置设置于中间设备，所述装置包括：
    第一获得模块，用于基于来自入口设备的组播报文，获取所述组播报文对应的区域的标识；
    第二获得模块，用于基于所述区域的所述标识和转发表项，获得下一跳设备的地址，所述转发表项包含所述区域的所述标识以及所述下一跳设备的所述地址；
    第一发送模块，用于基于所述下一跳设备的所述地址发送所述组播报文。
  16. 根据权利要求15所述的装置，其特征在于，所述组播报文包括所述区域的所述标识，所述第一获得模块用于从所述组播报文中获取所述区域的所述标识；或者
    所述组播报文包括所述中间设备的标识，所述第一获得模块用于基于所述组播报文中的所述中间设备的标识，获取与所述中间设备的标识对应的所述区域的所述标识。
  17. 根据权利要求15或16所述的装置，其特征在于，所述装置还包括：
    第一接收模块，用于接收所述下一跳设备发送的所述下一跳设备的所述地址和所述下一跳设备所属的所述区域的所述标识；以及
    第三获得模块，用于基于所述区域的所述标识和所述下一跳设备的所述地址，获得所 述转发表项。
  18. 根据权利要求15或16所述的装置，其特征在于，所述装置还包括：
    第一接收模块，用于接收所述下一跳设备发送的所述下一跳设备的标识和所述下一跳设备所属的所述区域的所述标识；以及
    第三获得模块，用于基于所述下一跳设备的标识，获得所述下一跳设备的所述地址；
    所述第三获得模块用于基于所述区域的所述标识和所述下一跳设备的所述地址，获得所述转发表项。
  19. 根据权利要求17或18所述的装置，其特征在于，
    所述第一接收模块用于接收所述下一跳设备发送的目的AS域内位转发路由器BFR标识的范围，所述目的AS域为所述区域包含的所述下一跳设备所属的AS域，所述转发表项还包括所述目的AS域内BFR标识的范围。
  20. 根据权利要求19所述的装置，其特征在于，所述组播报文还包括所述BFR标识的范围，所述第二获得模块用于基于所述区域的所述标识和所述BFR标识的范围，确定所述转发表项。
  21. 根据权利要求15至20任一所述的装置，其特征在于，所述装置还包括：
    第二发送模块，用于向所述入口设备发送所述中间设备的地址和所述中间设备所属的区域的标识。
  22. 根据权利要求21所述的装置，其特征在于，
    所述第二发送模块还用于向所述入口设备发送所述中间设备所属AS域内BFR标识的范围，所述中间设备所属AS域包含于所述中间设备所属的区域。
  23. 一种用于发送组播报文的装置，其特征在于，所述装置设于入口设备，所述装置包括：
    第一获得模块，用于获取接收到的组播报文对应的区域的标识；
    第二获得模块，用于基于所述区域的标识和转发表项，获得用于将所述组播报文转发至所述区域的中间设备的地址，所述转发表项包括所述区域的所述标识以及所述中间设备的所述地址；
    第一发送模块，用于基于所述中间设备的所述地址发送所述组播报文。
  24. 根据权利要求23所述的装置，其特征在于，所述装置还包括：
    第一接收模块，用于接收所述中间设备发送的所述中间设备的所述地址和所述区域的所述标识；以及
    第三获得模块，用于基于所述中间设备的所述地址和所述区域的所述标识，获得所述转发表项。
  25. 根据权利要求23所述的装置，其特征在于，所述装置还包括：
    第一接收模块，用于接收所述中间设备发送的所述中间设备的标识和所述区域的所述标识；以及
    第三获得模块，用于基于所述中间设备的所述标识，确定所述中间设备的所述地址；
    所述第三获得模块用于基于所述中间设备的所述地址和所述区域的所述标识，获得所述转发表项。
  26. 根据权利要求24或25所述的装置，其特征在于，所述第二接收模块还用于：
    接收所述中间设备发送的目的自治系统AS域内BFR标识的范围，所述目的AS域为 所述区域包含的所述组播报文需要发送到的AS域，所述转发表项还包括所述目的AS域内BFR标识的范围。
  27. 根据权利要求26所述的装置，其特征在于，
    所述第二获得模块用于基于所述目的AS域内BFR标识的范围和所述区域的所述标识，确定所述转发表项。
  28. 根据权利要求23至27任一所述的装置，其特征在于，所述组播报文中包含所述区域的所述标识，所述第第一获得模块用于从所述组播报文获取所述区域的所述标识；或者
    所述组播报文中包含所述中间设备的标识，所述第一获得模块用于基于所述组播报文中的所述中间设备的标识，获取与所述中间设备的标识对应的所述区域的所述标识。
  29. 一种系统，其特征在于，所述系统包括权利要求15至22任一所述的装置和权利要求23至28任一所述的装置。
PCT/CN2021/093063 2020-05-11 2021-05-11 用于发送组播报文的方法和装置 WO2021228090A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21804760.3A EP4142227A4 (en) 2020-05-11 2021-05-11 METHOD AND APPARATUS FOR SENDING MULTICAST MESSAGE
US17/984,506 US20230081052A1 (en) 2020-05-11 2022-11-10 Method and apparatus for sending multicast packet

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202010393103.4 2020-05-11
CN202010393103 2020-05-11
CN202010632551.5A CN113645134A (zh) 2020-05-11 2020-07-03 用于发送组播报文的方法和装置
CN202010632551.5 2020-07-03

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/984,506 Continuation US20230081052A1 (en) 2020-05-11 2022-11-10 Method and apparatus for sending multicast packet

Publications (1)

Publication Number Publication Date
WO2021228090A1 true WO2021228090A1 (zh) 2021-11-18

Family

ID=78415640

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/093063 WO2021228090A1 (zh) 2020-05-11 2021-05-11 用于发送组播报文的方法和装置

Country Status (4)

Country Link
US (1) US20230081052A1 (zh)
EP (1) EP4142227A4 (zh)
CN (1) CN113645134A (zh)
WO (1) WO2021228090A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114793226A (zh) * 2022-06-23 2022-07-26 北京安盟信息技术股份有限公司 一种基于中间设备实现组播代理与组播溯源的方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020150094A1 (en) * 2000-10-27 2002-10-17 Matthew Cheng Hierarchical level-based internet protocol multicasting
CN102916893A (zh) * 2012-11-14 2013-02-06 迈普通信技术股份有限公司 三层交换机中设置ip组播转发端口的装置和方法
WO2019214589A1 (zh) * 2018-05-08 2019-11-14 华为技术有限公司 组播数据传输方法、相关装置及系统
CN110535768A (zh) * 2018-05-25 2019-12-03 北京华为数字技术有限公司 组播数据传输方法及相关设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109150730A (zh) * 2017-06-15 2019-01-04 中兴通讯股份有限公司 组播跨域方法、装置、系统及计算机可读存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020150094A1 (en) * 2000-10-27 2002-10-17 Matthew Cheng Hierarchical level-based internet protocol multicasting
CN102916893A (zh) * 2012-11-14 2013-02-06 迈普通信技术股份有限公司 三层交换机中设置ip组播转发端口的装置和方法
WO2019214589A1 (zh) * 2018-05-08 2019-11-14 华为技术有限公司 组播数据传输方法、相关装置及系统
CN110535768A (zh) * 2018-05-25 2019-12-03 北京华为数字技术有限公司 组播数据传输方法及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
IJ. WIJNANDS: "Multicast VPN Using Bit Index Explicit Replication (BIER)", INTERNET ENGINEERING TASK FORCE (IETF), 30 April 2018 (2018-04-30), pages 1 - 43, XP055753750 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114793226A (zh) * 2022-06-23 2022-07-26 北京安盟信息技术股份有限公司 一种基于中间设备实现组播代理与组播溯源的方法及系统

Also Published As

Publication number Publication date
CN113645134A (zh) 2021-11-12
EP4142227A4 (en) 2023-10-25
US20230081052A1 (en) 2023-03-16
EP4142227A1 (en) 2023-03-01

Similar Documents

Publication Publication Date Title
US11153108B2 (en) Bit indexed explicit replication using multiprotocol label switching
WO2021063232A1 (zh) 建立bier转发表项的方法、装置和系统
US10097446B2 (en) Dynamic area filtering for link-state routing protocols
US9485141B1 (en) Constrained route distribution for multiple virtual private network services
US11689452B2 (en) Method for forwarding service data, network device, and network system
EP4073986B1 (en) Efficient arp bindings distribution in vpn networks
US7940763B1 (en) Aggregated topological routing
US7590115B1 (en) Exchange of control information for virtual private local area network (LAN) service multicast
Aggarwal et al. BGP encodings and procedures for multicast in MPLS/BGP IP VPNs
US11881963B2 (en) Service-based transport classes for mapping services to tunnels
CN102137024B (zh) 报文处理方法、出口路由设备及边界路由设备
WO2016032584A1 (en) Methods, systems, and computer readable media for virtual fabric routing
US9832121B1 (en) Next hop instruction associations for forwarding unit programming within a network device
JP7077367B2 (ja) Ｓｆｃネットワークにおけるトポロジー情報を同期させるための方法、およびルーティングネットワーク要素
EP3965368B1 (en) Replication mode selection for multicast in evpn
US7362752B1 (en) Aggregated topological routing
EP3166263B1 (en) Routing calculation method and device for trill isis
WO2016150093A1 (zh) 报文转发方法、装置及服务提供商网络边缘pe设备
WO2021228090A1 (zh) 用于发送组播报文的方法和装置
CN113364692B (zh) 双平面模式下的路由内存优化方法和路由内存优化装置
CN113992564B (zh) 报文处理方法及装置
WO2021103744A1 (zh) 一种异构网络通信方法、系统和控制器
WO2024061184A1 (zh) 对应关系的获取方法、参数通告方法、装置、设备及介质
WO2023051179A1 (zh) 边界网关协议路由的接收、发送方法及装置和存储介质
WO2024007762A1 (zh) 一种路由发布方法、通信方法及装置

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: 21804760

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021804760

Country of ref document: EP

Effective date: 20221121

NENP Non-entry into the national phase

Ref country code: DE