WO2018006671A1

WO2018006671A1 - Message sending method and apparatus, network architecture, and computer storage medium

Info

Publication number: WO2018006671A1
Application number: PCT/CN2017/086982
Authority: WO
Inventors: 胡方伟
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-07-07
Filing date: 2017-06-02
Publication date: 2018-01-11
Also published as: CN107592262A

Abstract

Provided are a message sending method and apparatus, a network architecture, and a computer storage medium. The message sending method comprises: a bit indexed explicit replication - rendezvous point (BIER-RP) device of a first domain announcing an address of a cross-domain multicast group to a controller; and after a bit-index forwarding ingress router (BFIR) of the first domain receives a multicast data message requesting to be transmitted across a domain to a second domain, the BFIR transmitting the multicast data message to a bit-index forwarding egress router (BFER) of the first domain, and the BFER forwarding the multicast data message to the second domain.

Description

Message sending method and device, network architecture, computer storage medium

Cross-reference to related applications

The present application is filed on the basis of the Chinese Patent Application No. PCT Application No.

Technical field

The present invention relates to the field of communications, and in particular to a message sending method and apparatus, a network architecture, and a computer storage medium.

Background technique

IP multicast technology realizes efficient point-to-multipoint data transmission in IP networks, which can effectively save network bandwidth and reduce network load. Therefore, IP multicast technology is used for real-time data transmission, multimedia conference, data copy, and network television (Internet). Protocol Television (abbreviated as IPTV), games and simulations have a wide range of applications. At present, the multicast technology is generally implemented by protocol independent multicast (PIM, including PIM-SM, PIM-DM) and Multicast Source Discovery Protocol (MSDP). A common feature is the need to construct a control plane multicast tree, which uses the multicast tree to process the network plane logic into a tree to implement point-to-multipoint data forwarding and loop avoidance for multicast forwarding. The intermediate node of the multicast routing protocol with the distribution tree as the core needs to maintain the state of complex multicast forwarding information. As the network size increases, the multicast data traffic increases with each other. Broadcast technology faces increasing costs and operational challenges.

To this end, the industry has proposed a new technology for building multicast forwarding paths, called Bit Indexed Explicit Replication (BIER), which proposes a new multicast technology architecture that does not require building a multicast distribution tree. As shown in Figure 1, the router supporting BIER technology is called A bit-forwarding router (BFR), a multicast forwarding domain consisting of BFRs is called a BFIR domain (that is, a BFIR domain). BFIR encapsulation of user multicast data is performed at the edge of the BIER domain. The device is called BFIR (referred to as the BTIR1 and BFIR2, as shown in Figure 1). The edge BFR device that decapsulates the BIER data packet is called BFER (called the Bit-Forwarding egress Router). BFER1 and BFER2) shown in Figure 1, the multicast data is encapsulated by the BFIR into the BIER domain, and is forwarded in the BIER domain depending on the header of the BIER, and leaves the BIER domain via one or more BFER devices. In the BIER domain, The device that receives and forwards the BIER message is called the transmission bit index forwarding router (ie, transit BFR) of the BIER message. A BFR can be either a BFIR role or a BFER role, depending on the encapsulation and decapsulation messages.

In the BIER field, each edge of the BFER is assigned a globally unique bit (ie bit position) in the entire bit index display copy copy subfield (ie BIER sub-domain), each BFER will use its own bit position The Interior Gateway Protocol (IGP) floods the BIER domain. All bit positions form a binary string (bitstring). The transmission and routing of data packets in the BIER domain depends on the bitstring. When other BFRs receive the header containing the BIER, they are forwarded based on the bit string carried in the BIER header and based on the Bin Forwarding Table. This principle of forwarding based on the BIER bit will change the forwarding based on the construction of the multicast distribution tree to the unicast lookup and forwarding using the bit identifier, which greatly reduces the forwarding cost of the network.

Figure 2 depicts the BIER forwarding process. BFR1 is the ingress-bit index forwarding router (ie, ingress BFR), BFR5, BFR6, and BFR7 are both egress BFR. The BFRs of BFR5, BFR6, and BFR7 are 0001, 0010, respectively. 0100. Egress BFR passed in advance The IGP protocol (such as IS-IS protocol, or OSPF protocol) advertises its own bit position in the BIER domain. After receiving the BFR5, BFR6, and BFR7 bit position notifications, BFR1 saves the information in the local bit index forwarding table. . After receiving the multicast packet, BFR1 assumes that the multicast packet needs to be transmitted to BFR5 and BFR6. Based on the mapping relationship saved in advance, BFR1 calculates the value of the Bitstring of the packet as 0101. The packet is encapsulated into a BIER packet. The Bitstring in the BIER Header is padded with 0101 and forwarded to BFR2. After receiving the packet, BFR2 searches for the entry in the previously stored bit index forwarding table. According to the entry, the packet needs to be forwarded to BFR3. Bitstring is paired with the F-BM of the matching entry to obtain 0101. BFR2 refills the BIER packet with 0101 as the Bitstring in the BIER Header, and forwards the packet to BFR3. After receiving the packet, BFR3 receives the packet. Find its own bit index forwarding table. BFR3 has two matching records, which represent the next hop of the packet forwarded to BFR4 and BFR6. For the first entry, BFR3 compares the value of Bitstring with the F-BM in the entry. Operation, the result is 0001. In the second entry, the value of Bitstring and the result of the F-BM operation are 0100. Then BFR3 forwards the BIER message from the two interfaces to BFR4 and BFR6, BIER of BFR4. Header's Bitstring value is 00 01, and the value of the Bitstring of the BIER Header forwarded to BFR6 is 0100. For the BFR6 packet, the value of the bitstring is the same as the bit position that it advertises. It indicates that it is the destination of the packet and decapsulates the BIER packet. When the arrival packet arrives at the BFR4, the packet forwarding is forwarded to the BFR5, and the BIER packet is decapsulated by the BFR5. The multicast packet is transmitted in the BIER domain, and the multicast packet is The BFR1 node of the ingress is forwarded to the receiving nodes BFR4 and BFR6 of the multicast.

For the advertisement of user multicast group addresses, the industry proposes to use the Internet Group Management Protocol/Multicast Listening Discovery Protocol (IGMP/MLD protocol) to superimpose on the BIER layer. BFIR is used as the IGMP/MLD querier, and BFER is used as the querier for IGMP/MLD. The listener, the user multicast group's packets are transmitted through the IGMP/MLD message overlay (that is, superimposed) to the BIER network. After receiving the IGMP/MLD message sent by the BFER, the BFIR can learn the user corresponding to the BFER. Group Broadcast group.

The above BIER forwarding and multicast group address advertisement method can be used to meet the requirements when applied to a single domain. However, for cross-domain multicast data forwarding, some problems are encountered: the existing bitstring advertisement is used. The IGP protocol advertises that the distributed bitstring advertisement cannot be unified and managed. The cross-domain forwarding needs to decapsulate the BIER packet of the first domain and re-encapsulate the BIER at the boundary of the second domain. The forwarding efficiency is relatively low. The IGMP/MLD packet is superimposed on the bit index to display the replication layer (that is, the overlay bier) to advertise the multicast group address of the inter-domain. When the network is large, the multicast user joins and leaves the multicast group. When the behavior is frequent, the flood of IGMP/MLD packets is flooded and the BIER forwarding resources are occupied in large quantities.

In view of the technical problem that the network needs to occupy more resources when transmitting multicast data packets in the related art, an effective solution has not been proposed yet.

Summary of the invention

The embodiments of the present invention provide a packet sending method and device, a network architecture, and a computer storage medium, to at least solve the technical problem that the network needs to occupy more resources when transmitting multicast data packets in the related art.

According to an aspect of the embodiments of the present invention, a packet sending method is provided, the method includes: displaying, by a bit index of a first domain, a copy-convergence point device BIER-RP advertising a cross-domain multicast group address to a controller; After the bit index forwarding ingress router BFIR of the domain receives the multicast data message requesting to transmit to the second domain across the domain, the BFIR transmits the multicast data packet to the bit index forwarding egress router BFER of the first domain, which will be The multicast data packet is forwarded to the second domain.

In the embodiment of the present invention, the bit index of the first domain shows that the replication-convergence point device BIER-RP advertises the cross-domain multicast group address to the controller, including: the BIER-RP advertises the cross-domain to the controller through the extended BGP-LS protocol. Multicast group address.

In the embodiment of the present invention, a sub-TLV is added to the Node Descriptor TLVs of the BGP-LS protocol, and the newly added sub-TLVs are used to carry the inter-domain multicast group address.

In the embodiment of the present invention, the BFIR transmits the multicast data packet to the bit index forwarding egress router BFER of the first domain, where the BFIR determines the BFER that is connected to the second domain in the first domain, and the BFIR transmits the multicast data packet to the BFER. A BFER that is in communication with the second domain.

In the embodiment of the present invention, forwarding the multicast data packet to the second domain by the BFER includes: determining, by the BFER, whether the second domain is adjacent to the first domain; and determining that the second domain is adjacent to the first domain, The BFER transmits the multicast data packet to the BFIR of the second domain. When it is determined that the second domain is not adjacent to the first domain, the BFER transmits the multicast data packet to the BFIR of the second domain through the third domain. The third domain is in communication with the first domain and the second domain, respectively.

According to another aspect of the present invention, a packet sending method is further provided, the method comprising: a bit index forwarding egress router BFER of a first domain, and an inter-domain capability for advertising a BFER in a first domain by using an extended routing protocol Attribute information; the bit index forwarding ingress router BFIR in the first domain determines the BFER connected to the second domain when receiving the multicast data message sent to the second domain, wherein the BFIR passes the cross-domain capability attribute of the BFER The information determines whether the BFER is connected to the second domain. The BFIR transmits the multicast data packet to the BFER connected to the second domain, and sends the multicast data packet to the second domain through the BFER connected to the second domain.

In the embodiment of the present invention, the bit index forwarding egress router BFER of the first domain advertises the cross-domain capability attribute information of the BFER in the first domain by using the extended routing protocol, and the BFER of the first domain is first to the extended routing protocol. The BFIR in the domain advertises the cross-domain capability attribute information of the BFER.

In the embodiment of the present invention, when the routing protocol is OSPF, a sub-sub-TLV is added to the OSPF BIER Sub-TLV of the OSPF protocol, and the newly added sub-sub-TLV is used to carry the cross-domain capability attribute information of the BFER.

In the embodiment of the present invention, when the routing protocol is the ISIS protocol, a sub-sub-TLV is added to the ISIS BIER info Sub-TLV of the ISIS protocol, and the newly added sub-sub-TLV is used to carry the cross-domain capability attribute information of the BFER. .

In the embodiment of the present invention, when the routing protocol is BGP, the sub-TLV is added to the BGP BIER info TLV of the BGP protocol, and the newly added sub-TLV is used to carry the cross-domain capability attribute information of the BFER.

In the embodiment of the present invention, the cross-domain capability attribute information includes a first flag field for indicating a cross-domain capability attribute, a second flag field for indicating whether to support forwarding equal-cost multipath ECMP, and a second flag field for indicating the second domain The third field of the system information of the autonomous system connected to the BFIR.

According to another aspect of the present invention, a message sending apparatus is provided, the apparatus comprising: a first advertising unit configured to control a bit index of a first domain to display a copy-convergence point device BIER-RP to notify a controller The cross-domain multicast group address; the transmission unit, configured as the bit index forwarding ingress router BFIR of the first domain, after receiving the multicast data packet requesting to be transmitted to the second domain across the domain, controlling the BFIR to transmit the multicast data packet The bit index to the first domain forwards the egress router BFER, and the BFER forwards the multicast data message to the second domain.

In the embodiment of the present invention, the first advertising unit includes: a first advertising module, configured to control the BIER-RP to notify the controller of the cross-domain multicast group address by using the extended BGP-LS protocol.

In the embodiment of the present invention, the transmission unit includes: a determining module configured to determine, by using the BFIR, a BFER that is connected to the second domain in the first domain; the first transmission module is configured to transmit the multicast data packet to the second through the BFIR Domain connected BFER.

In the embodiment of the present invention, the transmission unit includes: a determining module configured to determine, by using a BFER, whether the second domain is adjacent to the first domain; and the second transmitting module is configured to determine that the second domain is adjacent to the first domain The BFER transmits the multicast data packet to the BFIR of the second domain, and the third transmission module is configured to control the BFER to send the multicast data packet when it is determined that the second domain is not adjacent to the first domain. The BFIR is transmitted to the second domain through the third domain, wherein the third domain is in communication with the first domain and the second domain, respectively.

According to another aspect of the present invention, a message sending apparatus is further provided, the apparatus comprising: a second advertising unit configured to control a bit index forwarding egress router BFER of the first domain by using an extended routing protocol The cross-domain capability attribute information of the BFER is advertised in a domain; the determining unit is configured to control the bit index forwarding ingress router BFIR in the first domain to determine the second domain when receiving the multicast data packet sent to the second domain The connected BFER, wherein the BFIR determines whether the BFER is connected to the second domain by using the BFER cross-domain capability attribute information; the sending unit is configured to control the BFIR to transmit the multicast data packet to the BFER connected to the second domain, and The BFER connected to the second domain sends the multicast data packet to the second domain.

In the embodiment of the present invention, the second advertising unit includes: a second advertising module, configured to control the BFER of the first domain to notify the BFIR in the first domain of the cross-domain capability attribute information of the BFER by using the extended routing protocol.

According to another aspect of the embodiments of the present invention, a network architecture is provided, where the network architecture includes a hierarchical controller in a first domain, a bit index display copy-convergence point device BIER-RP, The bit index forwarding ingress router BFIR and the bit index forwarding egress router BFER, wherein the hierarchical controller is used to manage cross-domain routing information, network topology information, and multicast group information; the BIER-RP is respectively connected to the hierarchical controller and the BFIR, and configured To advertise the inter-domain multicast group address to the hierarchical controller, send the cross-domain routing information to the second domain, and advertise the received cross-domain routing information in the first domain; the BFIR is connected to the hierarchical controller and configured to receive When requesting the transmission of the multicast data packet to the second domain, the multicast data packet is forwarded to the corresponding BFER according to the cross-domain multicast group address and the autonomous system information corresponding to the multicast data packet; the BFER is used for receiving The received multicast data packet is forwarded to the second domain.

In the embodiment of the present invention, the hierarchical controller includes an SDN controller and a super network controller, and the super network controller is configured to generate an indication group according to the cross-domain multicast group address of the multicast data packet and the system information of the second domain. The control information of the transmission route of the data packet is broadcasted, and the multicast data packet and the control information are sent to the BFIR through the SDN controller.

In the embodiment of the present invention, the BIER-RP advertises the inter-domain multicast group address and the system information of the second domain to the SDN controller through the extended BGP-LS protocol.

In the embodiment of the present invention, a sub-TLV is added to the Node Descriptor TLVs of the BGP-LS protocol, and the newly added sub-TLV is used to carry the inter-domain multicast group address and the system information of the second domain.

In the embodiment of the present invention, the BFER is further used to notify the BFIR of the second domain of the cross-domain capability attribute information of the BFER by using the extended routing protocol.

In the embodiment of the present invention, when the routing protocol is BGP, BGP is BGP. A new sub-TLV is added to the BIER info TLV. The newly added sub-TLV is used to carry the cross-domain capability attribute information of the BFER.

According to another aspect of the present invention, a computer storage medium is provided, wherein a computer program is stored, the computer program being configured to perform a message transmission method of an embodiment of the present invention.

In the technical solution of the embodiment of the present invention, the bit index of the first domain shows that the copy-convergence point device BIER-RP advertises the cross-domain multicast group address to the controller; the bit index forwarding ingress router BFIR of the first domain receives the request. After the multicast data packet is transmitted to the second domain, the BFIR transmits the multicast data packet to the bit index forwarding egress router BFER of the first domain, and the BFER forwards the multicast data packet to the second domain. The technical problem of consuming network resources in the transmission of multicast data packets in the related art is solved, and the technical effect of reducing network resources for transmitting multicast data packets is achieved.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a schematic diagram of a message forwarding architecture in the related art;

2 is a schematic diagram of packet forwarding in the related art;

3 is a schematic diagram of a network architecture of packet cross-domain forwarding according to an embodiment of the present invention;

4 is a schematic diagram of an optional network architecture for packet cross-domain forwarding according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of an optional network architecture for cross-domain forwarding of packets according to an embodiment of the present invention; FIG.

6 is a schematic diagram of an optional network architecture for cross-domain forwarding of packets according to an embodiment of the present invention;

7 is a schematic diagram of an optional network architecture for cross-domain forwarding of packets according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of an optional network architecture for cross-domain forwarding of packets according to an embodiment of the present invention; FIG.

9 is a schematic diagram of a format of an optional TLV according to an embodiment of the present invention;

10 is a schematic diagram of a format of an optional TLV according to an embodiment of the present invention;

11 is a schematic diagram of a format of an optional TLV according to an embodiment of the present invention;

12 is a schematic diagram of a format of an optional TLV according to an embodiment of the present invention;

13 is a schematic diagram of a format of an optional TLV according to an embodiment of the present invention;

14 is a schematic diagram of a format of an optional TLV according to an embodiment of the present invention;

15 is a schematic diagram of an advertisement by a BGP protocol according to an embodiment of the present invention;

16 is a schematic diagram of cross-domain multicast data forwarding according to an embodiment of the present invention;

FIG. 17 is a flowchart of a method for sending a message according to an embodiment of the present invention; FIG.

FIG. 18 is a schematic diagram of a message sending apparatus according to an embodiment of the present invention; FIG.

FIG. 19 is a flowchart of another method for sending a message according to an embodiment of the present invention; FIG.

FIG. 20 is a schematic diagram of another message transmitting apparatus according to an embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It is to be understood that the terms "first", "second" and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

Example 1

According to the embodiment of the present invention, an embodiment of a network architecture for packet cross-domain forwarding is provided for the problem of cross-domain forwarding. As shown in FIG. 3, the network architecture includes: a hierarchical controller located in the first domain AS100. The Controller and the bit index display the copy-convergence point device BIER-RP, the bit index forwarding ingress router BFIR, and the bit index forwarding egress router BFER.

The hierarchical controller is used to manage cross-domain routing information, network topology information, and multicast group information.

The BIER-RP is connected to the hierarchical controller and the BFIR, and is configured to advertise the inter-domain multicast group address to the hierarchical controller, send the cross-domain routing information to the second domain AS200, and advertise the received cross-domain in the first domain. Routing information.

The BFIR is connected to the layered controller, and is configured to forward the multicast data according to the cross-domain multicast group address and the autonomous system information corresponding to the multicast data packet when receiving the multicast data packet that is requested to be transmitted to the second domain. The message is sent to the corresponding BFER.

The BFER is configured to forward the received multicast data packet to the second domain.

Through the foregoing embodiment, the hierarchical controller manages the cross-domain routing information, the network topology information, and the multicast group information; the BIER-RP advertises the inter-domain multicast group address to the hierarchical controller, and sends the cross-domain routing information to the second domain. Notifying the received cross-domain routing information in the first domain; when receiving the multicast data message requested to be transmitted to the second domain, the BFIR is based on the inter-domain multicast group address and the autonomous system corresponding to the multicast data packet. The information forwards the multicast data packet to the corresponding BFER; the BFER forwards the received multicast data packet to the second domain, thereby solving the technology in the related art that needs to occupy more resources of the network when transmitting the multicast data packet. The problem is that the technical effect of reducing network resources for transmitting multicast data messages is achieved.

It should be noted that the foregoing hierarchical controller includes an SDN controller and a super network controller, and the super network controller is configured to generate an indication according to the cross-domain multicast group address of the multicast data packet and the system information of the second domain. Control information about the transmission route of the multicast data packet, and send the multicast data packet and control information to the BFIR through the SDN controller.

In the foregoing embodiment, the connection with the first domain AS100 may be one domain or multiple. As shown in FIG. 4, the network architecture includes a bit index forwarding ingress router device BFIR, and a bit index display replication-convergence point device. BIER-RP, bit index forwarding egress router device BFER, network controller device controller and super controller device Super Controller, bit index forwarding entry path receives multicast data and then BIER packet encapsulation, bit index forwarding egress router device is located The autonomous domain boundary (that is, the AS boundary, the full name of the AS) is used to forward multicast data packets to other autonomous system domains. The BIER-RP device needs to advertise the inter-domain multicast group address information to the network controller. The super controller performs hierarchical control of the BIER network. For the BIER-RP to advertise the multicast group address information to the controller, there is no related technology. The application can implement the function by extending the BGP-LS protocol. The structure of the BIER cross-domain network proposed in this application is described in detail below with reference to FIG. 4:

The network architecture may include four AS autonomous system domains, namely AS100, AS200, AS300 and AS400. For the convenience of description, in the schematic diagram of the present application, an AS domain is also considered as a BIER domain (in practical applications, An AS domain may include multiple BIER domains, that is, BIER domain, that is, there are four BIER domains in FIG. 4, which are BIER domain 1, BIER domain 2, BIER domain 3, and BIER domain 4. BIER domain 1 includes six devices: BFIR11, BFR11, BFR12, BFER11, BFER12 and BIER-RP11; BIER domain2 includes five devices: BFIR21, BFR21, BFR22, BFER21 and BIER-RP21; BIER domain 3 includes BFIR31, BFR31, BFR32, BFER31, BFER32 and BIER-RP31 six devices; BIER domain 4 includes six devices BFIR41, BFR41, BFR42, BFER41, BFER42 and BIER-RP41. Controller1, Controller1, and Controller3 are network SDN controllers, and Super Controller is a super controller. The functions of the various components of the network architecture of the present application are detailed below.

(1) Bit index display copy-convergence point device BIER-RP

As shown in FIG. 4, the BIER-RP (including BIER-RP11, BIER-RP21, etc.) is a bit index display copy-convergence point device, and is a new device for implementing the cross-domain BIER forwarding network structure based on the SDN controller of the present application. The bit index shows that the replication-convergence point device is responsible for the advertisement of the inter-domain multicast address of the domain, and establishes a logical connection with the bit index display replication-aggregation point device of other domains, transmits the cross-domain routing information, and sends other domain information. Cross-domain routing information is advertised in this domain.

In Figure 5, the bit index shows the copy-convergence point device with the bit index entry router BFIR11 (The bit index export router BFER11) is connected to the network controller Controller1. In addition, the bit index display copy-convergence point device can also be associated with other BIER domains (that is, the autonomous system domain. In this application, for the convenience of description, the BIER domain and The bit index of the autonomous system domain shows that the replication-aggregation point devices are connected, such as BIER-RP11 and BIER-RP22. These connections can be either physical direct connections or logical connections.

The interface between the network SDN controller Controll1 and the BIER-RP11 can be defined as an I1 interface, so that the BIER-RP node can notify the network SDN controller of the network topology information and multicast group information of the BIER domain, and the I1 interface can pass. The extension of the Netconf protocol or the BGP-LS protocol implementation can also be implemented using other southbound interface protocols.

The interface between BIER-RP11 and BFIR11 can be defined as an I2 interface, and the I2 interface completes the advertisement of cross-domain routing information between BIER-RP and BFIR. The I2 interface can be implemented by extending the IGP protocol (ISIS protocol or OSPF protocol).

The interface between the BIER-RP11 and the BFER11 can be defined as an I3 interface. The I3 interface implements the advertisement of the cross-domain routing information between the BIER-RP11 and the BFER11, and also implements the BFER11 cross-domain border node capability attribute to the BIER-RP11 node. The I3 interface can be implemented by extending the IGP protocol (ISIS protocol or OSPF protocol).

The interface between the BIER-RP11 and the BIER-RP22 can be defined as an I4 interface. The I4 interface can implement cross-domain routing and parameter information advertisement between two domains. The I4 interface can be implemented by extending the BGP protocol, or other domains can be used. Inter-agreement implementation.

(2) Bit index forwarding entry router BFIR

As shown in Figure 4, BFIR (including BFIR11, BFIR21, etc.) is a bit-indexing ingress router device. In this application, BFIR11 is used to encapsulate BIER packets, and is also used to enhance cross-domain groups delivered by the receiving controller. Broadcast group address information. The implementation of the network interface and function of the enhanced bit indexing ingress router for cross-domain forwarding proposed by the present application is described below with reference to FIG. 6:

Figure 6 shows the interface diagram of the bit index ingress router, and BFIR11 is the bit index ingress route. BFIR11 is connected to BFR11 in the BIER domain (a bit index forwarding router, an autonomous domain may include multiple bit index forwarding routers, such as BFR11 and BFR12), and is logically associated with BIER-RP11. At the same time, BFIR11 and network SDN controller The controllers are logically connected. The interface between BFIR11 and other BIER forwarding devices in the BIER domain is defined as an I6 interface. The interface between the BFIR11 and the BIER-RP is an I2 interface. The interface between BFIR11 and Controller1 is an I5 interface. The I2 interface is connected to the BFIR11. And the BIER-RP device, the connection may be a physical direct connection or a logical connection. The I2 interface is a newly implemented interface function of the BIER cross-domain network structure proposed by the application on the BIER, and the interface completes the BFIR. Announcement of information and parameters such as cross-domain network link status and cross-domain routing between BIER-RP. The I5 interface is logically connected to the BFIR11 and the Controller1 device. The I5 interface implements the network SDN controller Controller1 to deliver related forwarding routes and cross-domain parameters to the BFIR11 device. The I5 interface is implemented through the southbound interface protocol, such as Netconf and PCEP. The specific implementation of the protocol is not specifically limited in the present invention. The I6 interface is an interface that is required to be implemented by the existing BIER device. The I6 interface performs the function of discovering and maintaining the neighbor status of the IGP protocol (ISIS or OSPF), flooding the link state parameters, and advertising information.

(3) Bit index forwarding exit router BFER

As shown in FIG. 4, BFER (BFER11, BFER12, BFER21, etc.) is a bit index egress router device. In this application, the BER11 and BFER12 devices not only need to decapsulate the BIER packets of the local domain, but also forward the multicast packets. To other ASs or to receivers of multicast packets, you need to advertise your own domain boundary capability attribute information. The location index ingress router device selects the appropriate egress router for cross-domain multicast data forwarding. The network structure and interface function definition implementation of the enhanced bit index forwarding egress router of the present application is explained below with reference to FIG.

Figure 7 shows the interface function diagram of the bit index forwarding egress router, BFER11 is the bit index forwarding egress router, BFR11, BFR12 is the intermediate bit index forwarding router, BIER-RP11 is the bit index display copy-convergence point device, the present application Enhanced bit index forwarding egress router with BFER12 is connected to BIER-RP11 (can be physically connected or logically connected). The interface between BFER11 and BER12 is defined as I7 interface. The interface between BFER11 and BIER-RP11 is defined as I3 interface. I7 interface is present. On the basis of the function of the link state and maintenance and link bandwidth of the IGP protocol, the BFER11 also advertises the BFER cross-domain boundary node capability attribute to the BFER12. The functional interface definition of I3 has been described in detail in the above embodiments, and the description thereof will not be repeated here.

(4) Bit index forwarding router BFR

BFR (including BFR11, BFR12, BFR21, etc.) is a bit index transmission router that transmits BIER messages according to the bit index forwarding table.

(5) Hierarchical SDN Controller Controller

The network structure and interface definition of the hierarchical SDN controller in the network architecture of the present application are described below with reference to FIG. 4 and FIG. 8.

The controller (including Controller1, Controller2, and so on) is a network SDN controller that configures and manages the forwarding device in the BIER domain. The network SDN controller receives the topology information and multicast group address information sent by the BIER domain forwarding device through the southbound interface protocol. Then, the controller sends control information to the relevant BIER device through protocols such as Netconf or PCEP according to its own calculation and decision. The controller Controller is managed by the super controller. When it is necessary to advertise information across domains, the super controller needs to perform calculations and decisions.

The super controller receives the information advertised by the controllers Controller1, Controller2, and Controller3, and sends related control information to the controllers Controller1, Controller2, and Controller3.

The SDN controller of the cross-domain network proposed in the present application adopts a hierarchical manner, and each BIER domain has its own SDN network controller, and the SDN network controller controls the autonomous system domain (BIER domain, default autonomous system domain and BIER domain). The BIER device under the same scope, including the bit index entry router, the bit index shows the copy-aggregation device, the interface of the bit index entry router is I5, the interface with BIER-RP is I1, and for the I5 interface, the SDN network controller Issue related forwarding Information in-place index ingress router, the interface is implemented by the southbound interface protocol, and can be a southbound interface protocol such as Netconf or PCEP. For the I1 interface, the interface between the replication-aggregation device is displayed for the SDN network controller and the bit index, and the user SDN network controller uses the interface to collect cross-domain information, network topology information, multicast group information, and the like.

The SDN network controller is connected to the super controller by using an I8 interface to advertise and deliver cross-domain information. The interface can use the northbound interface protocol, the Restfull interface protocol, and the Netconf protocol.

Through the above embodiment, by expanding the existing BIER system, resource consumption in the packet forwarding process can be saved.

Optionally, the BIER-RP advertises the cross-domain multicast group address and the system information of the second domain to the SDN controller by using the extended BGP-LS protocol.

Specifically, the sub-TLVs are added to the Node Descriptor TLVs of the BGP-LS protocol, and the newly added sub-TLVs are used to carry the inter-domain multicast group address and the system information of the second domain.

Figure 9 shows the format of the Node Descriptor TLV in the existing BGP-LS protocol. The value of the Type field is 256 or 257, which indicates the node description TLV and the remote node description TLV of the current segment. The Length field is the total length value of the Sub-TLV. The Node Descriptor Sub-TLVs (variable indicates variable length) field is the content of the Sub-TLV carried by the Node Descriptor TLV. The Sub-TLV types that have been defined so far are as shown in Table 1.

There are four Sub-TLVs in the current Node Descriptor TLV extension. The value of the Sub-TLV Code Point is 512 to 515, which indicates the autonomous system number (the Autonomous System corresponding to the Description) and the BGP-LS identifier. (BGP-LS Identifier), OSPF area ID (OSPF area-ID), IGP router ID (IGP Router-ID), length (ie Length) except IGP router ID is variable length, other The length is 4.

Table 1

Sub-TLV Code Point

Description

Length

512512	Autonomous System Autonomous System	44
513513	BGP-LS IdentifierBGP-LS Identifier	44
514514	OSPF Area-IDOSPF Area-ID	44
515515	IGP Router-IDIGP Router-ID	VariableVariable

The information such as the cross-domain multicast group address and the autonomous system number proposed in this application needs to be extended by the new Sub-TLV (BIER inter-domain Multicast sub-TLV). The BIER inter-domain Multicast sub-TLV indicates BIER-RP support. Multicast address information and autonomous system information. The Sub-TLV that the extended Node Descriptor TLV can support is shown in Table 2:

Table 2

The BIER inter-domain Multicast sub-TLV format is shown in Figure 10. The fields are described as follows:

The value of the Type field is recommended to be 516.

The Length field is the total length of the BIER inter-domain Multicast Sub-TLV.

The AS number is the AS number where the BIER-RP that advertises the BGP-LS information is located.

Res is a reserved field.

The multicast address type field indicates the type of the multicast address. If the value is 1, the multicast address carried by the BIER inter-domain multicast sub-TLV is an IPv4 address. If the value is 2, the BIER inter-domain Multicast Sub is displayed. - The multicast address carried by the TLV is an IPv6 address.

Number of multicast address indicates BIER inter-domain Multicast Sub-TLV Number of multicast addresses carried.

Multicast address: BIER inter-domain Multicast The multicast address carried by the Sub-TLV.

The BIER inter-domain Multicast Sub-TLV is advertised to the controller by the BIER-RP in the BIER domain, so this Sub-TLV is carried by the Local Node Descriptors TLV. BIER inter-domain Multicast Sub-TLV can be filled multiple times.

In the above embodiment, the BFER is further used to notify the BFIR of the second domain of the cross-domain capability attribute information of the BFER through the extended routing protocol.

Optionally, in the case that the routing protocol is the ISIS protocol, a sub-sub-TLV is added to the ISIS BIER info Sub-TLV of the ISIS protocol, and the newly added sub-sub-TLV is used to carry the cross-domain capability attribute information of the BFER.

Figure 11 shows the format of the ISIS BIER info Sub-TLV. The ISIS BIER info Sub-TLV carries the basic parameters of the BIER, including sub-domain id and BFR-id. The Sub-TLV can also carry MPLS Encapsulation. Sub-Sub-TLV, such as Sub-Sub-TLV and BIER sub-domain Tree Type, are used to carry the parameter information of the MPLS encapsulation of the BIER and the information of the tree used by the BIER to calculate the path. The present application extends the ISIS BIER info Sub-TLV. The newly added Sub-TLV is an AS Border BFER Sub-Sub-TLV, and carries the cross-domain capability attribute information of the bit index egress router.

When the bit index egress router encapsulates a Link State Packet Data Unit (LSPDU), the ISIS BIER info-Sub-TLV information is encapsulated, and the BIER info Sub-TLV carries the AS Border BFER Sub-Sub- The TLV, the bit index egress router uses the ISIS flooding mechanism to flood the BIER domain after the LSPDU is encapsulated. When the bit index ingress router and the BIER-RP router in the BIER domain receive the LSPDU, they can be carried according to the The content indicated by the AS Border BFER Sub-Sub-TLV determines whether the index export egress router supports cross-domain forwarding and information such as the AS number of other connected AS domains.

Optionally, in the case that the routing protocol is OSPF, a sub-sub-TLV is added to the OSPF BIER Sub-TLV of the OSPF protocol, and the newly added sub-sub-TLV is used to carry the cross-domain capability attribute information of the BFER.

Figure 12 shows the format of the OSPF BIER Sub-TLV. The OSPF BIER sub-TLV also carries the basic parameters of the BIER, including Sub-domain-ID and BFR-id. The sub-TLV can also carry MPLS Encapsulation. Sub-Sub-TLV, which is used to advertise the parameter information of the BIER MPLS encapsulation. The OSPF BIER Sub-TLV is extended in this application. The newly added sub-sub-TLV is the AS Border BFER Sub-Sub-TLV, which carries the cross-domain capability forwarding information of the bit index egress router (that is, the cross-domain capability attribute information).

When the bit index egress router encapsulates the LSA (Link State Advertise), the OSPF BIER Sub-TLV information is encapsulated. The BIER Sub-TLV carries the AS Border BFER Sub-Sub-TLV. The bit index egress router encapsulates the LSA. Then, the flooding is performed in the BIER domain by using the OSPF flooding mechanism. When the bit index ingress router and the BIER-RP router in the BIER domain receive the LSA, they can be instructed according to the carried AS Border BFER Sub-Sub-TLV. The content determines whether the index export router supports cross-domain forwarding, and knows the AS number of other connected autonomous system domains.

Optionally, in the case that the routing protocol is BGP, the sub-TLV is added to the BGP BIER info TLV of the BGP protocol, and the newly added sub-TLV is used to carry the cross-domain capability attribute information of the BFER.

Figure 13 shows the BGP BIER TLV format. The BGP BIER TLV carries the BIER basic parameters, including the Sub-domain ID and BFR-id. The TLV can carry the MPLS encapsulation sub-TLV to advertise the BIER MPLS encapsulation. Parameter information. This application extends the BGP BIER TLV. The newly added sub-TLV is the AS Border BFER Sub-TLV, which carries the cross-domain capability forwarding information of the bit index egress router.

It should be noted that the cross-domain capability attribute information includes a first flag field for indicating a cross-domain capability attribute, a second flag field for indicating whether to support forwarding equal-cost multipath ECMP, and A third field for indicating system information of an autonomous system connected to the BFIR of the second domain.

The AS Border BFER Sub-Sub-TLV format diagram of this application is shown in Figure 14. The description of each field is as follows:

Type field: expressed as AS Border BFER Sub-Sub-TLV, the value of this field requires IETF IANA allocation;

Length field: the total length of this Sub-Sub-TLV;

I field: indicates whether the bit index egress router supports cross-domain forwarding. When the field value is 1, it indicates that cross-domain forwarding is supported. When 0, cross-domain forwarding is not supported. The value of the adjacency AS number field is ignored.

E field: indicates whether the bit index egress router supports ECMP forwarding. When the field value is 1, it indicates that ECMP is supported. When 0, ECMP is not supported.

Adjacency AS number field: The autonomous system number of the connected autonomous system of the bit index egress router.

As shown in Figure 15, the BGP peer connection is established between the BFER11 and the BFR12 and the BIER-RP11, and the BGP route is exchanged. When the BGP update message is encapsulated in the BFER11, the BGP BIER TLV information is encapsulated. The AS Border BFER Sub-TLV proposed in this application carries the cross-domain capability attribute information of the bit index egress router BFER11 in the Sub-TLV, and the BFER11 sends the update message to the peers BFR12 and BIER-RP11, BFR12 and BIER-RP11. After the update message is received, it can be determined whether the BFER11 supports cross-domain forwarding according to the AS Border BFER Sub-TLV indication content carried in the message, and the AS number of other connected autonomous systems is known. At the same time, since the BGP peer connection is established between the BIER-RP11 and the bit index entry router BFIR11, and the BGP route is exchanged, the BFIR11 can also learn whether the BFER11 supports cross-domain forwarding through BIER-RP11 and implement the bit index of the boundary. The cross-domain capability attribute of the egress router is transmitted to BFR11, BFIR11, etc. in the BIER domain by means of BGP distribution and flooding.

16 is a process diagram of multicast data forwarding of the BIER cross-domain architecture of the present application. Figure 16 still takes four BIER domains as an example. The BFIR1 of BIER domain1 is the entry of the multicast data stream. The multicast data needs to be forwarded to the receivers of BIER domain 3 and BIER domain4. When the multicast data stream is forwarded to the BIER domain3 bit. The index exit router BFER32 needs to pass through the BIER domain1, BIER domain 2 and BIER domain3 domains (AS100, AS200, and AS300). When the multicast data stream is forwarded to the BIER domain4 bit index egress router BFER42, it needs to go through. BIER domain1 and BIER domain4 are two domains. The detailed data forwarding process is as follows:

In step S101, the BFIR11 in the BIER domain1 domain receives the multicast data stream, and finds that the receiver of the multicast data has a cross-domain receiver, and needs to perform cross-domain multicast forwarding. The BIER cross-domain multicast constructed by the BFIR11 according to the present invention. The architecture performs BIER encapsulation, in which the BIER bitstring field contains the arrival of the domain index exit routers BFER11 and BFER12.

In step S102, the BIER BFIR11 sends the encapsulated message to the BIER domain1, and the message is transmitted to the bit index egress routers BFER11, BFER12 via the intermediate transfer nodes BFR11, BFR12, and the like.

Step S103, the bit index egress routers BFER11 and BFER12 decapsulate the BIER packet encapsulation, and send the decapsulated multicast message to the bit index ingress router BFIR21 of BIER domain2 and the bit index ingress router BFIR41 of BIER domain4, respectively.

In step S104, the bit index ingress routers BFIR21 and BFIR41 perform forwarding behavior similar to BFIR11, and forward the multicast messages to BFER21 and BFER42, respectively.

In step S105, the bit index egress router BFER21 is similar to the forwarding behavior of the BFER11. The BIER message is decapsulated and then forwarded to the BFIR31. The bit index egress router BFER42 decapsulates the BIER message and forwards it to the multicast user receiver.

Step S106: After receiving the multicast packet, the bit index ingress router BFIR31 performs BIER encapsulation to forward the packet to the multicast receiver of the local domain, and completes the multicast data packet in multiple autonomy. Transmission between system domains.

It should be noted that, in FIG. 16, Label (such as Label11, Label12, etc.) represents a label, BIER Header (such as BIER Header11, BIER Header13, etc.) represents the head of the BIER message, Payload load, and the logo and figure in FIG. 4 is the same and will not be described here.

Through the foregoing embodiments, the problem of the need to consume more resources in packet forwarding in the related art can be solved by the modification of the nodes in the network architecture and the expansion of the protocol.

Example 2

According to an embodiment of the present invention, a method embodiment of a message sending method is provided, and it should be noted that the steps shown in the flowchart of the drawing may be executed in a computer system such as a set of computer executable instructions, and Although the logical order is shown in the flowcharts, in some cases the steps shown or described may be performed in a different order than the ones described herein.

FIG. 17 is a flowchart of a method for sending a message according to an embodiment of the present invention. As shown in FIG. 17, the method includes the following steps:

Step S1701, the bit index of the first domain shows that the copy-convergence point device BIER-RP advertises the cross-domain multicast group address to the controller.

Step S1702: After receiving the multicast data packet requesting the cross-domain transmission to the second domain, the BFIR transmits the multicast data packet to the bit index forwarding egress router of the first domain. BFER, the multicast data packet is forwarded by the BFER to the second domain.

Through the above embodiment, the bit index of the first domain shows that the copy-convergence point device BIER-RP advertises the cross-domain multicast group address to the controller; the bit index forwarding ingress router BFIR of the first domain transmits the request to the cross-domain transmission to the first After the multicast data packet of the second domain, the BFIR transmits the multicast data packet to the bit index forwarding egress router BFER of the first domain, and the BFER forwards the multicast data packet to the second domain, thereby solving the related art. The technical problem of occupying more resources of the network is required when transmitting multicast data packets, and the technical effect of reducing network resources for transmitting multicast data packets is achieved.

In the above embodiment, the bit index of the first domain displays the copy-convergence point device BIER-RP The device advertises the inter-domain multicast group address. The BIER-RP advertises the inter-domain multicast group address to the controller through the extended BGP-LS protocol.

Optionally, a sub-TLV is added to the Node Descriptor TLVs of the BGP-LS protocol, and the newly added sub-TLVs are used to carry the inter-domain multicast group address.

In an optional embodiment, the BFIR transmits the multicast data message to the bit index forwarding egress router BFER of the first domain, including: BFIR determines a BFER in the first domain that is connected to the second domain; and the BFIR multicasts the datagram. The text is transmitted to the BFER that is in communication with the second domain.

In another optional embodiment, forwarding, by the BFER, the multicast data packet to the second domain includes: determining, by the BFER, whether the second domain is adjacent to the first domain; determining that the second domain is adjacent to the first domain In the case of the BFER, the BFER transmits the multicast data packet to the BFIR of the second domain. When it is determined that the second domain is not adjacent to the first domain, the BFER transmits the multicast data packet to the third domain through the third domain. The BFIR of the two domains, wherein the third domain is in communication with the first domain and the second domain, respectively.

16 is a process diagram of multicast data forwarding of the BIER cross-domain architecture of the present application. Embodiments of the present application are described in detail below with reference to FIG.

In step S101, the BFIR11 in the BIER domain1 domain receives the multicast data stream, and finds that the receiver of the multicast data has a cross-domain receiver, and needs to perform cross-domain multicast forwarding. The BIER cross-domain multicast constructed by the BFIR11 according to the present invention. The architecture is BIER-encapsulated, where BIER's bitstring The field contains the arrival of this domain bit index exit routers BFER11 and BFER12.

Step S106: After receiving the multicast packet, the bit index ingress router BFIR31 performs BIER encapsulation to forward the packet to the multicast receiver of the local domain, and completes the transmission of the multicast data packet between multiple autonomous system domains.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.

Example 3

A packet sending apparatus is further provided in the embodiment of the present invention. The device is used to implement the above The embodiments and preferred embodiments have not been described again. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 18 is a schematic diagram of a message sending apparatus according to an embodiment of the present invention. As shown in FIG. 18, the apparatus may include: a first notification unit 181 and a transmission unit 182.

The first advertising unit 181 is configured to control the bit index of the first domain to display that the copy-convergence point device BIER-RP advertises the cross-domain multicast group address to the controller.

The transmitting unit 182, the bit index forwarding ingress router BFIR configured as the first domain controls the BFIR to transmit the multicast data message to the bit of the first domain after receiving the multicast data message requesting to be transmitted to the second domain across the domain. The index forwarding egress router BFER forwards the multicast data packet to the second domain by the BFER.

With the above embodiment, the first advertising unit controls the bit index of the first domain to display that the copy-convergence point device BIER-RP advertises the cross-domain multicast group address to the controller; the bit index forwarding ingress router BFIR of the first domain receives the request. After the multicast data packet is transmitted to the second domain, the transmission unit controls the BFIR to transmit the multicast data packet to the bit index forwarding egress router BFER of the first domain, and the BFER forwards the multicast data packet to the second The domain solves the technical problem that the network needs to occupy more resources when transmitting multicast data packets in the related art, and achieves the technical effect of reducing network resources for transmitting multicast data packets.

In the foregoing embodiment, the first advertising unit includes: a first advertising module configured to control the BIER-RP to advertise the cross-domain multicast group address to the controller by using the extended BGP-LS protocol.

The foregoing transmission unit includes: a determining module configured to determine, by using BFIR, a BFER that is connected to the second domain in the first domain; and the first transmission module is configured to transmit the multicast data packet by using the BFIR To the BFER connected to the second domain.

The foregoing transmission unit further includes: a determining module, configured to determine, by using a BFER, whether the second domain is adjacent to the first domain; and the second transmitting module is configured to: when determining that the second domain is adjacent to the first domain, The BFER transmits the multicast data packet to the BFIR of the second domain, and the third transmission module is configured to control the BFER to pass the multicast data packet to the third device when it is determined that the second domain is not adjacent to the first domain. The domain is transmitted to the BFIR of the second domain, wherein the third domain is in communication with the first domain and the second domain, respectively.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination. The forms are located in different processors.

Example 4

FIG. 19 is a flowchart of another method for sending a message according to an embodiment of the present invention. As shown in FIG. 19, the method includes the following steps:

Step S1901: The bit index forwarding egress router BFER of the first domain advertises the cross-domain capability attribute information of the BFER in the first domain by using the extended routing protocol.

Step S1902: The bit index forwarding ingress router BFIR in the first domain determines a BFER that is connected to the second domain when receiving the multicast data packet that is sent to the second domain, where the BFIR passes the BFER cross-domain capability attribute. The information determines if the BFER is in communication with the second domain.

The cross-domain capability attribute information carries the domain autonomous system information (such as the system number) that is connected to the BFER. The multicast data packet also carries the autonomous system number of the destination domain. Therefore, the mutual autonomy can be determined. Whether the system number is the same to determine whether the BFER is connected to the second domain; The second domain is the destination domain of the multicast data packet, or the domain through which the multicast data packet needs to reach the destination domain.

In step S1903, the BFIR transmits the multicast data packet to the BFER connected to the second domain, and sends the multicast data packet to the second domain through the BFER connected to the second domain.

Through the foregoing embodiment, the bit index forwarding egress router BFER of the first domain advertises the cross-domain capability attribute information of the BFER in the first domain by using the extended routing protocol; the bit index forwarding ingress router BFIR in the first domain sends the request to the BFIR. The BFER is connected to the second domain, and the BFIR determines whether the BFER is connected to the second domain by using the BFER cross-domain capability attribute information; the BFIR transmits the multicast data packet to the BFER. The BFER that is connected to the second domain sends the multicast data packet to the second domain through the BFER that is connected to the second domain, thereby solving the technology that needs to occupy more resources of the network when transmitting the multicast data packet in the related art. The problem is that the technical effect of reducing network resources for transmitting multicast data messages is achieved.

In the above embodiment, the bit index forwarding egress router BFER of the first domain advertises the cross-domain capability attribute information of the BFER in the first domain by using the extended routing protocol, and the BFER of the first domain is first to the extended routing protocol. The BFIR in the domain advertises the cross-domain capability attribute information of the BFER.

Optionally, in the case that the routing protocol is BGP, BGP BIER info of BGP protocol A new sub-TLV is added to the TLV, and the added sub-TLV is used to carry the cross-domain capability attribute information of the BFER.

It should be noted that the cross-domain capability attribute information includes a first flag field for indicating a cross-domain capability attribute, a second flag field for indicating whether to support forwarding equivalent multipath ECMP, and a BFIR for indicating the second domain. The third field of system information for the connected autonomous system.

Length field: the total length of this Sub-Sub-TLV;

As shown in Figure 15, the BGP peer connection is established between the BFER11 and the BFR12 and the BIER-RP11, and the BGP route is exchanged. When the BGP update message is encapsulated in the BFER11, the BGP BIER TLV information is encapsulated. The AS Border BFER Sub-TLV proposed in this application, the cross-domain capability of the sub-TLV carrying the bit index egress router BFER11 Attribute information, BFER11 sends the update message to the peers BFR12 and BIER-RP11. After receiving the update message, BFR12 and BIER-RP11 can determine whether BFER11 supports cross-domain according to the AS Border BFER Sub-TLV indication content carried in the message. Forward and know the AS number of other connected ASs. At the same time, since the BGP peer connection is established between the BIER-RP11 and the bit index entry router BFIR11, and the BGP route is exchanged, the BFIR11 can also learn whether the BFER11 supports cross-domain forwarding through BIER-RP11 and implement the bit index of the boundary. The cross-domain capability attribute of the egress router is transmitted to BFR11, BFIR11, etc. in the BIER domain by means of BGP distribution and flooding.

16 is a process diagram of multicast data forwarding of the BIER cross-domain architecture of the present application. Figure 16 still takes four BIER domains as an example. The BFIR1 of BIER domain1 is the entry of the multicast data stream. The multicast data needs to be forwarded to the receivers of BIER domain 3 and BIER domain4. When the multicast data stream is forwarded to the BIER domain3 bit. The index exit router BFER32 needs to pass through the BIER domain1, BIER domain 2 and BIER domain3 domains (AS100, AS200, and AS300). When the multicast data stream is forwarded to the BIER domain4 bit index egress router BFER42, it needs to go through. The BIER domain1 and the BIER domain4 are in the detailed description of the previous embodiment, and are not described here.

Example 5

A packet sending apparatus is further provided in the embodiment of the present invention. The device is used to implement the above embodiments and preferred embodiments, and the description thereof has been omitted. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 20 is a schematic diagram of another message transmitting apparatus according to an embodiment of the present invention. As shown in FIG. 20, the apparatus may include: a second advertising unit 201, a determining unit 202, and a transmitting unit 203.

The second advertising unit 201 is configured to control the bit index forwarding egress router BFER of the first domain to advertise the cross-domain capability attribute information of the BFER in the first domain by using the extended routing protocol.

The determining unit 202 is configured to control the bit index forwarding ingress router BFIR in the first domain to determine a BFER connected to the second domain when receiving the multicast data message requested to be sent to the second domain, where the BFIR passes the BFER The cross-domain capability attribute information determines whether the BFER is in communication with the second domain.

The sending unit 203 is configured to control the BFIR to transmit the multicast data packet to the BFER connected to the second domain, and send the multicast data packet to the second domain by using the BFER connected to the second domain.

Through the foregoing embodiment, the second advertising unit controls the bit index forwarding egress router BFER of the first domain to announce the cross-domain capability attribute information of the BFER in the first domain by using the extended routing protocol; the determining unit controls the bit index forwarding entry in the first domain. When receiving the multicast data packet sent to the second domain, the router BFIR determines a BFER that is connected to the second domain, where the BFIR determines whether the BFER is connected to the second domain by using the cross-domain capability attribute information of the BFER; The unit control BFIR transmits the multicast data packet to the BFER connected to the second domain, and sends the multicast data packet to the second domain through the BFER connected to the second domain, thereby solving the related art transmission multicast datagram. The technical problem of occupying more resources of the network is required in the text, and the technical effect of reducing the network resources for transmitting multicast data packets is achieved.

The second notification unit in the foregoing embodiment includes: a second notification module configured to control the first The BFER of the domain advertises the cross-domain capability attribute information of the BFER to the BFIR in the first domain through the extended routing protocol.

Figure 11 shows the format of the ISIS BIER info Sub-TLV. The ISIS BIER info Sub-TLV carries the basic parameters of the BIER, including sub-domain id and BFR-id. The Sub-TLV can also carry MPLS Encapsulation. Sub-Sub-TLV such as Sub-Sub-TLV and BIER sub-domain Tree Type, respectively for MPLS encapsulation carrying BIER The parameter information and the information of the tree used by the BIER to calculate the path. The application extends the ISIS BIER info Sub-TLV, and the added Sub-TLV is the AS Border BFER Sub-Sub-TLV, which carries the cross-domain capability attribute of the bit index egress router. information.

Length field: the total length of this Sub-Sub-TLV;

Example 6

Embodiments of the present invention also provide a computer storage medium. In the present embodiment, the above computer storage medium may be arranged to store program code for performing the following steps:

S1, controlling the bit index of the first domain to display that the replication-convergence point device BIER-RP advertises the cross-domain multicast group address to the controller;

S2, after the bit index forwarding ingress router BFIR of the first domain receives the multicast data packet requesting to be transmitted to the second domain, the BFIR transmits the multicast data packet to the bit index forwarding egress router BFER of the first domain. The multicast data packet is forwarded by the BFER to the second domain.

Optionally, the computer storage medium is further arranged to store program code for performing the following steps:

S3, the bit index forwarding egress router BFER of the first domain advertises the cross-domain capability attribute information of the BFER in the first domain by using the extended routing protocol;

S4, the bit index forwarding ingress router BFIR in the first domain determines the BFER connected to the second domain when receiving the multicast data packet that is sent to the second domain, where the BFIR passes the BFER cross-domain capability attribute information. Determining whether the BFER is connected to the second domain;

S5. The BFIR transmits the multicast data packet to the BFER connected to the second domain, and sends the multicast data packet to the second domain by using the BFER connected to the second domain.

In this embodiment, the computer storage medium may include, but is not limited to, a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or a magnetic disk. And other media that can store program code.

In this embodiment, the processor executes according to the stored program code in the computer storage medium: controlling the bit index of the first domain to display the copy-convergence point device BIER-RP advertises the cross-domain multicast group address to the controller; When receiving the multicast data packet, the bit index forwarding ingress router BFIR determines whether the second domain in which the receiving object of the multicast data packet is located is in the same domain as the first domain, and determines the second domain and the first domain. If the domain is not in the same domain, the BFIR is controlled to transmit the multicast data packet to the bit index forwarding egress router BFER of the first domain, and the BFER forwards the multicast data packet to the second domain.

In this embodiment, the processor executes according to the stored program code in the computer storage medium: When the cross-domain multicast data packet needs to be transmitted, the bit index forwarding egress router BFER that controls the first domain advertises the BFER cross-domain capability attribute information to the second domain by using the extended routing protocol, where the second domain is a group. The destination field of the broadcast data packet, or the domain through which the multicast data packet needs to reach the target domain; the BFER sends the multicast data packet to the second domain.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

In the technical solution of the embodiment of the present invention, the BIER-RP of the first domain advertises the inter-domain multicast group address to the controller; after receiving the multicast data packet requesting the cross-domain transmission to the second domain, the BFIR of the first domain is received. The multicast data packet is transmitted to the BFER of the first domain, and the BFER forwards the multicast data packet to the second domain, thereby solving the technology in the related art that needs to occupy more resources of the network when transmitting the multicast data packet. The problem is that the technical effect of reducing network resources for transmitting multicast data messages is achieved.

Claims

A method for sending a message, comprising:

The bit index of the first domain shows that the copy-convergence point device BIER-RP advertises the cross-domain multicast group address to the controller;

After receiving the multicast data packet requesting the cross-domain transmission to the second domain, the bit index forwarding ingress router BFIR of the first domain transmits the multicast data packet to the bit index forwarding of the first domain. The egress router BFER forwards the multicast data message to the second domain by the BFER.
The method of claim 1, wherein the bit index of the first domain shows that the copy-convergence point device BIER-RP advertises the cross-domain multicast group address to the controller comprises:

The BIER-RP advertises the cross-domain multicast group address to the controller through the extended BGP-LS protocol.
The method of claim 2, wherein the sub-TLVs are added to the Node Descriptor TLVs of the BGP-LS protocol, and the newly added sub-TLVs are used to carry the inter-domain multicast group addresses.
The method of claim 1, wherein the BFIR transmitting the multicast data message to the bit index forwarding egress router BFER of the first domain comprises:

Determining, by the BFIR, the BFER in the first domain that is in communication with the second domain;

The BFIR transmits the multicast data message to the BFER that is in communication with the second domain.
The method of claim 1, wherein forwarding the multicast data message to the second domain by the BFER comprises:

Determining, by the BFER, whether the second domain is adjacent to the first domain;

When it is determined that the second domain is adjacent to the first domain, the BFER transmits the multicast data packet to a BFIR of the second domain;

In the case that it is determined that the second domain is not adjacent to the first domain, the BFER will The multicast data packet is transmitted to the BFIR of the second domain by using a third domain, where the third domain is respectively connected to the first domain and the second domain.
A method for sending a message, comprising:

The bit index forwarding egress router BFER of the first domain advertises the cross-domain capability attribute information of the BFER in the first domain by using an extended routing protocol;

The bit index forwarding ingress router BFIR in the first domain determines the BFER that is in communication with the second domain when receiving the multicast data message that is sent to the second domain, where the BFIR passes through the Determining, by the cross-domain capability attribute information of the BFER, whether the BFER is connected to the second domain;

Transmitting, by the BFIR, the multicast data packet to the BFER that is in communication with the second domain, and sending the multicast data packet to the first part by using the BFER that is connected to the second domain Two domains.
The method according to claim 6, wherein the bit index forwarding egress router BFER of the first domain advertises the cross-domain capability attribute information of the BFER in the first domain by using an extended routing protocol, including:

The BFER of the first domain advertises the cross-domain capability attribute information of the BFER to the BFIR in the first domain by using an extended routing protocol.
The method according to claim 7, wherein in the case that the routing protocol is an OSPF protocol, a sub-sub-TLV is added to the OSPF BIER Sub-TLV of the OSPF protocol, and a new sub-sub-TLV is used. Carrying cross-domain capability attribute information of the BFER.
The method according to claim 7, wherein in the case that the routing protocol is an ISIS protocol, a sub-sub-TLV is added to the ISIS BIER info Sub-TLV of the ISIS protocol, and a new sub-sub-TLV is used. The cross-domain capability attribute information of the BFER is carried.
The method according to claim 7, wherein in the case that the routing protocol is a BGP protocol, a sub-TLV is added to the BGP BIER info TLV of the BGP protocol, new The added sub-TLV is used to carry the cross-domain capability attribute information of the BFER.
The method according to claim 7, wherein the cross-domain capability attribute information comprises a first flag field for indicating a cross-domain capability attribute, a second flag field for indicating whether to support forwarding equivalent multipath ECMP, and And a third field indicating system information of the autonomous system connected to the BFIR of the second domain.
A message sending device includes:

a first advertising unit configured to control a bit index of the first domain to display a replication-convergence point device BIER-RP advertises a cross-domain multicast group address to the controller;

a transmission unit configured to: the bit index forwarding ingress router BFIR of the first domain controls the BFIR to transmit the multicast data packet to the BFIR after receiving the multicast data packet requesting to be transmitted to the second domain The bit index of the first domain forwards the egress router BFER, and the BFER forwards the multicast data packet to the second domain.
The apparatus of claim 12, wherein the first notification unit comprises:

The first advertising module is configured to control the BIER-RP to advertise the cross-domain multicast group address to the controller by using the extended BGP-LS protocol.
The device of claim 13, wherein the sub-TLVs are added to the Node Descriptor TLVs of the BGP-LS protocol, and the newly added sub-TLVs are used to carry the inter-domain multicast group addresses.
The apparatus of claim 12, wherein the transmission unit comprises:

a determining module, configured to determine, by the BFIR, the BFER in the first domain that is in communication with the second domain;

The first transmission module is configured to transmit, by using the BFIR, the multicast data message to the BFER that is in communication with the second domain.
The apparatus of claim 12, wherein the transmission unit comprises:

a determining module, configured to determine, by using the BFER, whether the second domain is adjacent to the first domain;

a second transmission module, configured to: when the second domain is determined to be adjacent to the first domain, transmit the multicast data packet to the BFIR of the second domain by using the BFER;

a third transmission module, configured to control, by the BFER, to transmit the multicast data packet to the second domain by using a third domain, if it is determined that the second domain is not adjacent to the first domain BFIR of the domain, wherein the third domain is in communication with the first domain and the second domain, respectively.
A message sending device includes:

a second advertising unit, configured to control a bit index forwarding egress router BFER of the first domain to advertise the cross-domain capability attribute information of the BFER in the first domain by using an extended routing protocol;

a determining unit, configured to control a bit index forwarding ingress router BFIR in the first domain, when receiving a multicast data message requesting to be sent to the second domain, determining the BFER connected to the second domain, where The BFIR determines whether the BFER is connected to the second domain by using the cross-domain capability attribute information of the BFER;

a sending unit, configured to control the BFIR to transmit the multicast data packet to the BFER that is in communication with the second domain, and send the multicast data packet by using the BFER that is connected to the second domain The text is sent to the second domain.
The apparatus of claim 17, wherein the second notification unit comprises:

The second advertisement module is configured to control the BFER of the first domain to notify the BFER cross-domain capability attribute information to the BFIR in the first domain by using an extended routing protocol.
The device according to claim 18, wherein in the case that the routing protocol is an OSPF protocol, a sub-sub-TLV is added to the OSPF BIER Sub-TLV of the OSPF protocol, and a new sub-sub-TLV is used. Carrying cross-domain capability attribute information of the BFER.
The device according to claim 18, wherein in the case that the routing protocol is an ISIS protocol, a sub-TLV is added to the ISIS BIER info Sub-TLV of the ISIS protocol, and the new sub-TLV is used. The cross-domain capability attribute information of the BFER is carried.
The device according to claim 18, wherein in the case that the routing protocol is a BGP protocol, a sub-TLV is added to the BGP BIER info TLV of the BGP protocol, and the newly added sub-TLV is used to carry the BFER. Cross-domain capability attribute information.
The apparatus according to claim 18, wherein said cross-domain capability attribute information comprises a first flag field for indicating a cross-domain capability attribute, a second flag field for indicating whether to support forwarding equivalent multipath ECMP, and And a third field indicating system information of the autonomous system connected to the BFIR of the second domain.
A network architecture for forwarding packets across domains, including a hierarchical controller in a first domain, a bit index display copy-convergence point device BIER-RP, a bit index forwarding ingress router BFIR, and a bit index forwarding egress router BFER, wherein

The hierarchical controller is configured to manage cross-domain routing information, network topology information, and multicast group information;

The BIER-RP is respectively connected to the layered controller and the BFIR, configured to advertise an inter-domain multicast group address to the layered controller, and send cross-domain routing information to the second domain, where The cross-domain routing information received by the advertisement in a domain;

The BFIR is connected to the layered controller, and is configured to: according to the cross-domain multicast group address corresponding to the multicast data packet, when receiving the multicast data message that is requested to be transmitted to the second domain And autonomous system information forwarding the multicast data message to the corresponding BFER;

The BFER is configured to forward the received multicast data packet to the second domain.
The network architecture of claim 23, wherein the layered controller comprises an SDN controller and a super network controller, the super network controller for inter-domain multicast group address based on the multicast data message The system information of the second domain is used to generate control information for indicating a transmission route of the multicast data packet, and the SDN controller sends the multicast data packet and the control information to the BFIR.
The network architecture of claim 24 wherein said BIER-RP passes The extended BGP-LS protocol advertises the cross-domain multicast group address and the system information of the second domain to the SDN controller.
The network architecture of claim 25, wherein a sub-TLV is added to the Node Descriptor TLVs of the BGP-LS protocol, and the added sub-TLV is used to carry the inter-domain multicast group address and the second domain system. information.
The network architecture of claim 23, wherein the BFER is further configured to advertise the cross-domain capability attribute information of the BFER to the BFIR of the second domain by using an extended routing protocol.
The network architecture according to claim 27, wherein, in the case that the routing protocol is an OSPF protocol, a sub-sub-TLV is added to the OSPF BIER Sub-TLV of the OSPF protocol, and the added sub-sub-TLV is used. The cross-domain capability attribute information of the BFER is carried.
The network architecture according to claim 27, wherein in the case where the routing protocol is an ISIS protocol, a sub-TLV is added to the ISIS BIER info Sub-TLV of the ISIS protocol, and a new sub-TLV is added. The cross-domain capability attribute information used to carry the BFER.
The network architecture of claim 27, wherein, in the case that the routing protocol is a BGP protocol, a sub-TLV is added to the BGP BIER info TLV of the BGP protocol, and the newly added sub-TLV is used to carry the BFER. Cross-domain capability attribute information.
The network architecture according to claim 27, wherein the cross-domain capability attribute information comprises a first flag field for indicating a cross-domain capability attribute, a second flag field for indicating whether to support forwarding equivalent multipath ECMP, and A third field for indicating system information of an autonomous system connected to the BFIR of the second domain.
A computer storage medium having stored therein computer executable instructions configured to perform the message transmission method of any of claims 1-5.
A computer storage medium storing a computer in the computer storage medium The computer executable instructions are configured to perform the message transmitting method of any one of claims 6-11.