CN112448876A

CN112448876A - Method and device for realizing message transmission

Info

Publication number: CN112448876A
Application number: CN201910815189.2A
Authority: CN
Inventors: 徐本崇; 彭少富; 朱永庆; 龚霞
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2019-08-30
Filing date: 2019-08-30
Publication date: 2021-03-05
Anticipated expiration: 2039-08-30
Also published as: WO2021036482A1; CN112448876B

Abstract

In the method, the sub-domain information carried in the message received by the node and not belonging to the node indicates the sub-domain ID information of the sub-domain to which the boundary node sending the message belongs, and the corresponding BIER sub-domain route is established for the sub-domain to which the node does not belong, and the BIER is sent out to the tunnel reaching the boundary node sending the received message, so that the intercommunication of the BIER in different sub-domains is realized.

Description

Method and device for realizing message transmission

Technical Field

The present application relates to, but not limited to, internet communication technologies, and in particular, to a method and an apparatus for implementing message transmission.

Background

After the Internet Protocol (IP) multicast forwarding technology, a Bit Index Explicit Replication (BIER) based technology is slowly developing, where BIER is a new technology for constructing a multicast forwarding path, and provides a multicast technology architecture without constructing a multicast distribution tree.

The relevant standards define in detail the detailed routing procedure of the unicast protocol in one BIER sub-domain, but BIER interworking cannot be implemented if the BIER is in a different sub-domain (Subdomain).

Disclosure of Invention

The application provides a method and a device for realizing message transmission, which can realize intercommunication of BIER in different sub-domains.

The application provides a method for realizing message transmission, which comprises the following steps:

the node receives a message carrying sub-domain information and determines that the sub-domain information comprises a sub-domain to which the node does not belong;

and the nodes establish subdomain routes and exit to tunnels pointing to the boundary nodes, wherein the boundary nodes are the nodes for sending the messages.

In one illustrative example, the sub-domain information includes: the sub-field indicates ID information; the method is also preceded by:

and the boundary node sending the message carries subdomain Identification (ID) information of a subdomain to which the boundary node belongs in the message.

In an exemplary embodiment, the performing, in the packet, sub-domain ID information of a sub-domain to which the border node itself belongs includes:

by expanding the unicast protocol message type, a sub-domain boundary type-length-value tlv structure, or a sub-tlv structure, or a sub-tlv structure, or an attribute structure is added for carrying sub-domain ID information of the sub-domain which can be reached by the boundary node sending the message.

In one illustrative example, the unicast protocol packet includes: an intermediate system to intermediate system ISIS protocol message and an open shortest path first OSPF protocol message.

In an exemplary embodiment, the packet is carried in a published route or prefix.

In one illustrative example, the node is a bit-indexed explicit replication BIER node; the creating a sub-domain route includes:

and generating corresponding BIER subdomain routing for subdomains to which the nodes do not belong, wherein the keywords are target subdomain IDs and are sent out to tunnels for reaching the boundary nodes which send the received messages.

In an exemplary embodiment, the tunnel is a BIER tunnel of a common sub-domain of the node and a boundary node that sends the received packet, and a Prefix of the BIER tunnel to the boundary node that sends the received packet is output; alternatively, the first and second electrodes may be,

the tunnel is also a unicast tunnel, and the destination address of the unicast tunnel is Prefix of the boundary node sending the received message.

In one illustrative example, the node is a non-BIER node; the creating a sub-domain route includes:

and generating corresponding BIER subdomain routing for subdomains to which the nodes do not belong, wherein the keywords are the target subdomain IDs and are sent out to a unicast tunnel reaching the boundary node which sends the received message.

In one illustrative example, before or after the creating the sub-domain route, further comprising:

the node replaces the route or the prefix with the local route or the prefix of the node, and the carried sub-domain ID is the sub-domain ID of the received message and the sub-domain ID of the node.

In one illustrative example, the method further comprises:

and the node receives the multicast flow, encapsulates the BIER head if the BIER output direction of the far-end sub-domain is appointed by multicast, encapsulates a layer of outer head according to the output direction tunnel of the sub-domain route and then forwards the outer head to the boundary node.

In an exemplary embodiment, the node is a BIER node, and when forwarding the multicast packet, the method further includes:

encapsulating the BIER head of the remote BIER subdomain as inner-layer BIER encapsulation;

and finding that the node does not have the BIER forwarding table of the sub-domain, searching the route of the BIER sub-domain, encapsulating the tunnel at the outer layer, and delivering the tunnel to the boundary node of the BIER sub-domain.

In an exemplary embodiment, the node is a non-BIER node, and when forwarding the multicast packet, the method further includes: and selecting to route and forward through the BIER subdomain through the strategy.

In an exemplary embodiment, the node is a BIER sub-domain boundary node, and after receiving the packet, the method further includes: and stripping the outer tunnel package, and normally forwarding through the inner BIER.

The application also provides a computer-readable storage medium, which stores computer-executable instructions for executing any one of the above methods for implementing message transmission.

The application also provides a device for realizing message transmission, which comprises a processor and a memory; wherein the memory has stored thereon a computer program operable on the processor to: for executing the steps of the method for implementing message transmission described in any one of the above.

The application further provides a device for implementing message transmission, including: the device comprises a confirmation module and a first processing module; wherein the content of the first and second substances,

the confirming module is used for receiving the message carrying the sub-domain information and determining that the sub-domain information comprises a sub-domain to which the node does not belong;

and the first processing module is used for creating a subdomain route and outputting the route to a tunnel pointing to a boundary node, wherein the boundary node is a node for sending the message.

In an exemplary example, the boundary node sending the packet adds a sub-domain boundary type-length-value tlv structure, or a sub-tlv structure, or a sub-tlv structure, or an attribute structure by extending a unicast protocol packet type in the packet, so as to carry sub-domain ID information of a sub-domain that can be reached by the boundary node sending the packet.

In an exemplary embodiment, the apparatus further includes a second processing module, configured to receive a multicast traffic, encapsulate a BIER header if a BIER egress direction of a far-end sub-domain is specified by multicast, encapsulate a layer of outer header in a tunnel according to an egress direction of a route of the sub-domain, and forward the encapsulated layer of outer header to the border node.

In the application, the sub-domain information carried in the message received by the node and not belonging to the node indicates the sub-domain ID information of the sub-domain to which the boundary node sending the message belongs, and the BIER sub-domain route is established for the sub-domain to which the node does not belong, and the tunnel for reaching the boundary node sending the received message is sent out, so that the intercommunication of BIER in different sub-domains is realized.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The accompanying drawings are included to provide a further understanding of the claimed subject matter and are incorporated in and constitute a part of this specification, illustrate embodiments of the subject matter and together with the description serve to explain the principles of the subject matter and not to limit the subject matter.

Fig. 1 is a flowchart of a method for implementing message transmission according to the present application;

fig. 2 is a schematic diagram of an embodiment of the structure of the ISIS protocol extension sub _ sub _ tlv of the present application;

FIG. 3 is a schematic diagram of an embodiment of the structure of an OSPF protocol extension sub _ sub _ tlv according to the present application;

FIG. 4 is a network diagram of an embodiment of BIER cross-subdomain of the present application;

fig. 5 is a schematic diagram of an embodiment of implementing packet transmission across a network with multiple BIER sub-domain functions according to the present application;

fig. 6 is a schematic diagram of a structure of a device for implementing packet transmission according to the present application.

Detailed Description

In one exemplary configuration of the present application, a computing device includes one or more processors (CPUs), input/output interfaces, a network interface, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.

To make the objects, technical solutions and advantages of the present application more apparent, embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.

Fig. 1 is a flowchart of a method for implementing packet transmission according to the present application, as shown in fig. 1, including:

step 100: and the node receives the message carrying the sub-domain information and determines that the sub-domain information comprises a sub-domain to which the node does not belong.

In an exemplary embodiment, the step further comprises:

and the boundary node sending the message carries sub-domain Identification (ID) information of a sub-domain to which the boundary node belongs in the message. That is, the sub-domain information carried in the packet to which the node itself does not belong is included in the sub-domain ID information of the sub-domain to which the boundary node itself that transmits the packet belongs.

by expanding the unicast protocol message type, a sub-domain boundary type-length-value (tlv) structure, or a sub-tlv (sub _ tlv) structure, or a sub-tlv (sub _ sub _ tlv) structure, or an attribute structure is added, which is used for carrying sub-domain ID information of the sub-domain which can be reached by the boundary node sending the message.

In an illustrative example, the unicast protocol packet may include, for example: an Intermediate System to Intermediate System (ISIS) protocol packet, an Open Shortest Path First (OSPF) protocol packet, and the like.

In an exemplary embodiment, the packet is carried in a published route or prefix, and specifically includes:

if the border node finds itself belongs to different BIER sub-domains simultaneously through a local policy (for example, configuring a BIER sub-domain border 12, which indicates that the device is a border device of the BIER sub-domain 1 and the sub-domain 2) or automatically, the expanded message is carried in the issued route or prefix.

In one illustrative example, the border node is a BIER-enabled device. Alternatively, the border node may comprise, for example, a router, switch, or other device or virtual device that supports BIER forwarding functionality. Border nodes may also be referred to as BIER nodes.

Step 101: and the nodes establish subdomain routes and exit to tunnels pointing to the boundary nodes, wherein the boundary nodes are the nodes for sending the messages.

In an exemplary embodiment, the node is a BIER node, and the node checks and finds that it does not belong to the sub-domain of the received packet advertisement at the same time, step 101 may include:

and generating corresponding BIER subdomain routing for subdomains to which the nodes do not belong, wherein the keywords are the destination subdomain IDs, such as the subdomain IDs of the subdomains to which the nodes do not belong, and are sent out to tunnels reaching the boundary nodes for sending the received messages.

In an exemplary example, the created tunnel may be a BIER tunnel of a common sub-domain of the local node and a boundary node (here, a BIER node) that sends the received packet, where the BIER tunnel is a Prefix to the boundary node that sends the received packet;

in an exemplary embodiment, the created tunnel may also be a unicast tunnel, and the destination address of the unicast tunnel is the Prefix of the border node that sends the received packet.

In an exemplary embodiment, the node is a non-BIER node, that is, a node not enabling BIER function, and step 101 may include:

and generating corresponding BIER subdomain routing for subdomains to which the nodes do not belong, wherein the keywords are the target subdomain ID and are sent out to a unicast tunnel reaching the boundary node which sends the received message.

In an illustrative example, before or after step 101, the present application further comprises:

the node replaces the route or the prefix with the local route or the prefix of the node through the existing rule or the local strategy, and the carried subdomain ID is the subdomain ID of the received message and the subdomain ID of the node. It should be noted that the existing rules or local policies mentioned herein are related to the regional area deployment and policy of IGP, and the application is not limited, for example: the subdomain ID is carried in a prefix tlv, and the boundary node can select a prefix tlv which is not received by direct flooding, and places the subdomain ID in the bier prefix tlv of the boundary node to be issued; or continue to flood the received prefix tlv, etc.

The sub-domain information carried in the message received by the node indicates the sub-domain ID information of the sub-domain to which the boundary node sending the message belongs, and the corresponding BIER sub-domain route is established for the sub-domain to which the node does not belong, and the tunnel to reach the boundary node sending the received message is sent out, so that the intercommunication of BIER in different sub-domains is realized.

In an exemplary embodiment, the method for implementing packet transmission further includes:

and the node receives the multicast flow, if the BIER output direction of the far-end subdomain is appointed by multicast, the BIER head is encapsulated, and then a layer of outer head is encapsulated according to the output direction tunnel of the far-end subdomain route and then is forwarded to the boundary node.

In an exemplary embodiment, the node is a BIER node, and when forwarding a multicast packet at a BFIR (ingress node in BIER domain) node, the method further includes:

firstly, encapsulating a BIER head of a remote BIER sub-domain as inner-layer BIER encapsulation, finding that the equipment does not have a BIER forwarding table of the sub-domain, searching BIER sub-domain routing, and delivering an outer-layer encapsulation tunnel to a BIER sub-domain boundary node.

In an exemplary embodiment, the node is a non-BIER node, that is, a node that does not enable a BIER function, and when the non-BIER node forwards a multicast packet, the method further includes:

the forwarding can be routed through the BIER sub-domain by policy selection, the method is the same as the above steps.

In an exemplary embodiment, the node is a BIER sub-domain boundary node, and after receiving the packet, the method further includes:

and stripping the outer tunnel package, and normally forwarding through the inner BIER.

An embodiment of the present invention further provides a computer-readable storage medium, in which computer-executable instructions are stored, where the computer-executable instructions are used to execute any one of the above methods for implementing packet transmission.

The embodiment of the invention also provides a device for realizing message transmission, which comprises a processor and a memory; wherein the memory has stored thereon a computer program operable on the processor to: for executing the steps of the method for implementing message transmission described in any one of the above.

Fig. 2 is a schematic diagram of an embodiment of a structure of an ISIS protocol extension sub _ sub _ tlv according to the present application, in which a sub-type-length-value (sub _ sub _ tlv) structure of a sub-domain boundary is added as shown in fig. 2. The Type field is undetermined, the Length field is variable, and the Length is related to the Sub-domain id number.

Fig. 3 is a schematic diagram of an embodiment of a sub sub tlv structure extended by the OSPF protocol of the present application, and as shown in fig. 3, a sub-domain boundary subtype-length-value (sub _ tlv) structure is added. The Type field is undetermined, the Length field is variable, and the Length is related to the number of the Subdomain id.

Taking the ISIS protocol extended sub tlv structure shown in fig. 2 as an example, when the ISIS protocol finds that itself belongs to multiple sub domains (subdomains) at the same time, when a prefix tlv is issued, it carries the BIER sub tlv and the sub _ sub _ tlv of the sub domain boundary, where the prefix is a configured BIER prefix;

it should be noted that, in the present application, whether the sub-domain boundary can be regarded as the sub-domain boundary or not may be controlled by a local policy, and if the sub-domain boundary cannot be regarded as the sub-domain boundary, the sub-tlv option is not carried.

If it is controlled by local configuration as a certain Subdomain boundary or boundaries, the Subdomain boundary sub _ sub _ tlv carries only its Subdomain id as a boundary. Optionally, at the ISIS domain boundary, the prefix tlv is leaked to other domains through policy, and the sub _ sub _ tlv option is carried on the sub _ sub _ tlv.

Fig. 4 is a schematic network diagram of an embodiment of BIER cross-sub domain in the present application, and in combination with the network shown in fig. 4, in a first embodiment, a sub domain id 1 and a sub domain id 2 are carried in a sub domain boundary sub _ sub _ tlv sent by a node R2.

Thus, after receiving the above message, the node R1 creates a sub-domain route to the Subdomain id 2, and goes out to a unicast tunnel pointing to the node R2 or a BIER tunnel using the prefix of the Subdomain id 1 of the node R2 as a BFER, and the tunnel type can be controlled by configuration. The node R1 receives the multicast flow, finds the flow direction as the node R3 of the subdomain 2 through a multicast protocol or a controller, and then encapsulates the BIER head according to the BFER of the subdomain 2; because the node R1 is not in the subdomain 2, the created subdomain route is searched, and the message delivery is carried out after the corresponding outer layer encapsulation is carried out according to the outgoing direction of the subdomain route; for the node R2, after receiving the message from the node R1, the outer header is stripped off to obtain the BIER message of the sub-domain 2, and then the BIER message is further forwarded.

Still as shown in fig. 4, assume that there are nodes in the network (non-BIER nodes) that do not enable BIER functionality, such as node R1; node R2 and node R3 enable BIER functionality and belong to sub-domain 2. Then, through a local policy, in the second embodiment, the sub-domain border node R2 may be caused to send an ISIS packet carrying the sub-domain border sub _ sub _ tlv as in the first embodiment, but only includes the Subdomain id 2, unlike the first embodiment, only supports unicast tunnel encapsulation. Others will not be described in detail herein.

Fig. 5 is a schematic diagram of an embodiment of implementing packet transmission across a network with multiple BIER sub-domain functions according to the present application, where as shown in fig. 5, a node R3 issues a prefix tlv, which carries BIER sub tlv and the sub-sub _ tlv sub _ sub _ tlv, where the sub _ sub _ tlv includes a sub domain id 2 and a sub domain id 3, and the prefix is BIER prefix locally configured at the node R3.

After receiving the message, the node R2 sends a prefix tlv to the node R1, where the prefix is a BIER prefix locally configured in the node R2 and carries BIER sub tlv and the sub-domain boundary sub _ sub _ tlv, and the carried sub _ sub _ tlv includes a Subdomain id 1, a Subdomain id 2 and a Subdomain id 3; node R2 also creates a Subdomain routing table for Subdomain id 3, out to BIER tunnel with BFER as node R3 or unicast tunnel to node R3.

After receiving the prefix tlv sent from the node R2, the node R1 creates a Subdomain routing table of Subdomain id 2 and Subdomain id 3, and goes out to a BIER tunnel which is the node R2 for BFER or a unicast tunnel which points to R2. Other implementations are not described in detail herein.

Fig. 6 is a schematic structural diagram of a device for implementing packet transmission according to the present application, as shown in fig. 6, the structural diagram at least includes: the device comprises a confirmation module and a first processing module; wherein the content of the first and second substances,

In an exemplary embodiment, the packet carries sub-domain ID information of a sub-domain to which the boundary node that transmits the packet belongs. Optionally, a sub-domain boundary type-length-value tlv structure, or a sub-tlv (sub _ tlv) structure, or a sub-tlv (sub _ sub _ tlv) structure, or an attribute structure may be added by extending the unicast protocol packet type, so as to carry sub-domain ID information of the sub-domain that can be reached by the boundary node sending the packet.

In an exemplary embodiment, the border node that sends the packet is a device that enables a BIER function. Alternatively, the border node may comprise, for example, a router, switch, or other device or virtual device that supports BIER forwarding functionality. Border nodes may also be referred to as BIER nodes.

In an exemplary embodiment, the node is a BIER node, and the first processing module is specifically configured to:

and generating corresponding BIER subdomain routing for subdomains which the device to which the first processing module belongs does not belong, wherein the key word is a target subdomain ID, and the key word is sent out to a tunnel for reaching a boundary node for sending the received message.

In an exemplary example, the created tunnel may be a BIER tunnel of a common sub-domain of the device to which the first processing module belongs and a border node (here, a BIER node) that sends the received packet, where the BIER tunnel is a Prefix to the border node that sends the received packet;

In an exemplary embodiment, the node is a non-BIER node, that is, a node that does not enable a BIER function, and the first processing module is specifically configured to:

and generating corresponding BIER subdomain routing for subdomains which the device to which the first processing module belongs does not belong, wherein the key word is a target subdomain ID, and sending a unicast tunnel to a boundary node for sending the received message.

In one illustrative example, the first processing module is further configured to:

and replacing the route or the prefix with the local route or the prefix of the device to which the first processing module belongs through the existing rule or the local strategy, wherein the carried subdomain ID is the subdomain ID of the received message and the subdomain ID of the device to which the first processing module belongs.

In an exemplary embodiment, the apparatus for implementing message transmission further includes a second processing module, configured to:

and receiving the multicast flow, if the BIER output direction of the far-end sub-domain is appointed by multicast, encapsulating a BIER head, encapsulating a layer of outer head according to the output direction tunnel of the far-end sub-domain route, and then forwarding to the boundary node.

In an exemplary embodiment, the apparatus to which the second processing module belongs is a BIER node, and when a BFIR (node in BIER domain) node forwards a multicast packet, the second processing module is further configured to:

firstly, a BIER head of a remote BIER sub-domain is packaged as inner layer BIER packaging, if a device to which a second processing module belongs does not have a BIER forwarding table of the sub-domain, the route of the BIER sub-domain is searched, and an outer layer packaging tunnel is delivered to a BIER sub-domain boundary node.

In an exemplary embodiment, the device to which the second processing module belongs is a non-BIER node, that is, a node that does not enable a BIER function, and when the non-BIER node forwards the multicast packet, the second processing module is further configured to:

forwarding may be routed through the BIER sub-domain via policy selection.

In an exemplary embodiment, the device to which the second processing module belongs is a BIER sub-domain border node, and after receiving the packet, the second processing module is further configured to:

The application also provides a node, which comprises any one of the above devices for realizing message transmission.

The above description is only a preferred example of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for realizing message transmission comprises the following steps:

2. The method of claim 1, the sub-domain information comprising: the sub-field indicates ID information; the method is also preceded by:

3. The method of claim 2, wherein the carrying of the sub-domain ID information of the sub-domain to which the border node itself belongs in the message comprises:

4. The method of claim 3, wherein the unicast protocol packet comprises: an intermediate system to intermediate system ISIS protocol message and an open shortest path first OSPF protocol message.

5. A method according to any one of claims 1 to 4, wherein the message is carried in a published route or prefix.

6. The method of claim 1, wherein the node is a bit-indexed explicit replication BIER node; the creating a sub-domain route includes:

7. The method according to claim 6, wherein the tunnel is a BIER tunnel of a common sub-domain of the node and a border node sending the received packet, and a BIER of the BIER tunnel sends out a Prefix to the border node sending the received packet; alternatively, the first and second electrodes may be,

8. The method of claim 1, wherein the node is a non-BIER node; the creating a sub-domain route includes:

9. The method of claim 1, 6 or 8, before or after said creating a sub-domain route, further comprising:

10. The method of claim 1, further comprising:

11. The method according to claim 10, wherein the node is a BIER node, and when forwarding the multicast packet, the method further comprises:

12. The method according to claim 10, wherein the node is a non-BIER node, and when forwarding the multicast packet, the method further comprises: and selecting to route and forward through the BIER subdomain through the strategy.

13. The method of claim 10, wherein the node is a BIER sub-domain border node, and after receiving the packet, the method further comprises: and stripping the outer tunnel package, and normally forwarding through the inner BIER.

14. A computer-readable storage medium storing computer-executable instructions for performing the method of implementing message transmission according to any one of claims 1 to 13.

15. A device for realizing message transmission comprises a processor and a memory; wherein the memory has stored thereon a computer program operable on the processor to: for performing the steps of the method of implementing message transmission according to any one of claims 1 to 13.

16. An apparatus for implementing message transmission, comprising: the device comprises a confirmation module and a first processing module; wherein the content of the first and second substances,

17. The apparatus of claim 16, wherein the border node sending the packet adds a sub-domain border type-length-value tlv structure, or a sub-tlv structure, or a sub-tlv structure, or an attribute structure by extending a unicast protocol packet type in the packet, for carrying sub-domain ID information of a sub-domain that can be reached by the border node sending the packet itself.

18. The apparatus according to claim 16, further comprising a second processing module, configured to receive multicast traffic, encapsulate a BIER header if the multicast specifies a BIER egress direction of a far-end sub-domain, and encapsulate a layer of outer header according to an egress direction tunnel of the sub-domain route, and then forward the encapsulated layer of outer header to the border node.