WO2024104007A1

WO2024104007A1 - Packet transmission method and apparatus, storage medium and electronic device

Info

Publication number: WO2024104007A1
Application number: PCT/CN2023/123829
Authority: WO
Inventors: 周华东; 刘爱华; 温建中
Original assignee: 中兴通讯股份有限公司
Priority date: 2022-11-18
Filing date: 2023-10-10
Publication date: 2024-05-23
Also published as: CN118057787A

Abstract

Disclosed in the present disclosure are a packet transmission method and apparatus, a storage medium and an electronic device. The method comprises: determining a forwarding label of each data stream in a target packet, wherein the target packet comprises a plurality of data streams, the forwarding label of each data stream comprises a routing field of each data stream and an identification field of each data stream, and the forwarding label of each data stream is provided in an outer label of the target packet; on the basis of the routing field of each data stream, determining a next-hop forwarding device used for transmitting the target packet; and distributing the plurality of data streams to a plurality of parallel links in a link aggregation group on the basis of the identification field of each data stream.

Description

Message sending method, device, storage medium and electronic device

CROSS-REFERENCE TO RELATED APPLICATIONS

This disclosure is based on Chinese patent application CN202211463771.5, filed on November 18, 2022, with the invention name “Message sending method, device, storage medium and electronic device”, and claims the priority of the patent application, and all the contents disclosed therein are incorporated into this disclosure by reference.

Technical Field

The embodiments of the present disclosure relate to the field of communications, and in particular, to a message sending method, device, storage medium, and electronic device.

Background technique

As the demand for service bandwidth increases, the network needs to expand capacity by adding links, and multi-link load balancing technology is needed. Taking the Segment Routing MPLS (SR-MPLS) network based on the MPLS forwarding plane as an example, the top layer of the SR-MPLS label stack is mainly set to path forwarding, and the service flow cannot be identified in detail, so only packet-based load sharing can be achieved. However, packet-by-packet will affect the terminal service experience, and flow-based load balancing needs to be achieved. However, in the source routing scenario, to achieve flow-based load balancing, the intermediate nodes need to perceive the flow and identify the flow. The current technical solution can only be based on deep analysis of the message, which is relatively costly and inefficient.

Summary of the invention

The embodiments of the present disclosure provide a message sending method, device, storage medium and electronic device to at least solve the problem in the related art that message parsing has high requirements on equipment due to too deep forwarding labels or too many label layers lead to low data encapsulation efficiency.

According to an embodiment of the present disclosure, a message sending method is provided, comprising: determining a forwarding label of each data stream in a target message, wherein the target message includes multiple data streams, the forwarding label of each data stream includes a routing field of each data stream and an identification field of each data stream, and the forwarding label of each data stream is set in an outer label of the target message; determining a next-hop forwarding device for sending the target message based on the routing field of each data stream; and distributing the multiple data streams to multiple parallel links in a link aggregation group based on the identification field of each data stream.

According to another embodiment of the present disclosure, a message sending device is also provided, including: a first determination module, configured to determine the forwarding label of each data stream in a target message, wherein the target message includes multiple data streams, the forwarding label of each data stream includes a routing field of each data stream and an identification field of each data stream, and the forwarding label of each data stream is set in an outer label of the target message; a second determination module, configured to determine the next-hop forwarding device for sending the target message based on the routing field of each data stream; a first distribution module, configured to distribute the multiple data streams to multiple parallel links in a link aggregation group based on the identification field of each data stream.

In an exemplary embodiment, the first determination module includes: a first determination unit, configured to generate a routing field of each of the data flows and an identification field of each of the data flows through a controller, and obtain a forwarding label of each of the data flows, wherein the routing field of each of the data flows is a routing field generated by the controller according to the routing topology of the plurality of routing devices. The identification field of each of the above-mentioned data streams is determined by the information of the flutter, and includes one of the following: setting the identification field of each of the above-mentioned data streams to a zero value through the above-mentioned controller, and setting the identification field of each of the above-mentioned data streams to a non-zero preset value through the above-mentioned controller.

In an exemplary embodiment, the above-mentioned device also includes: a first parsing module, which is configured to generate a routing field for each of the above-mentioned data flows and an identification field for each of the above-mentioned data flows through a controller, and after obtaining the forwarding label of each of the above-mentioned data flows, when the identification field of each of the above-mentioned data flows is the above-mentioned zero value, parse the above-mentioned target message through a source routing device to obtain the message information of the above-mentioned target message; a first configuration module, which is configured to configure the identification field of each of the above-mentioned data flows based on the above-mentioned message information; or, a second configuration module, which is configured to configure the identification field of each of the above-mentioned data flows on a network management device according to a preset whitelist mechanism.

In an exemplary embodiment, the above-mentioned device also includes: a first encapsulation module, which is configured to generate a routing field for each of the above-mentioned data streams and an identification field for each of the above-mentioned data streams through a controller, and after obtaining a forwarding label for each of the above-mentioned data streams, when the identification field of each of the above-mentioned data streams is a non-zero preset value, encapsulate the above-mentioned target message according to the forwarding label of each of the above-mentioned data streams through a source routing device.

In an exemplary embodiment, the first determination module includes: a first generation unit, configured to generate a routing field for each of the data streams and an identification field for each of the data streams to obtain a forwarding label for each of the data streams, wherein the routing field for each of the data streams is determined by the source routing device according to routing topology information of the plurality of routing devices, and the identification field for each of the data streams is configured by the source routing device based on information of each of the data streams.

In an exemplary embodiment, the above-mentioned first distribution module includes: a second determination unit, configured to determine the value of the identification field of each of the above-mentioned data streams as the hash value of each of the above-mentioned data streams; a first distribution unit, configured to use a preset algorithm to determine the parallel links corresponding to the distribution of the hash value of each of the above-mentioned data streams.

In an exemplary embodiment, the above-mentioned device also includes: a third determination module, which is configured to determine the tunnel type for transmitting the above-mentioned target message before determining the forwarding label of each data flow in the target message; a fourth determination module, which is configured to determine the bits occupied by each of the above-mentioned data flow forwarding labels and the format of each of the above-mentioned data flow forwarding labels based on the above-mentioned tunnel type.

According to another embodiment of the present disclosure, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any one of the above method embodiments when running.

According to another embodiment of the present disclosure, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

Through the present disclosure, by determining the forwarding label of each data stream in the target message, wherein the target message includes multiple data streams, the forwarding label of each data stream includes the routing field of each data stream and the identification field of each data stream, and the forwarding label of each data stream is set in the outer label of the target message; based on the routing field of each data stream, the next hop forwarding device for sending the target message is determined; based on the identification field of each data stream, the multiple data streams are distributed to multiple parallel links in the link aggregation group. Since the above method is based on flow-based load balancing, it will not increase the burden on the equipment, making the message encapsulation efficiency higher, reducing the cost of network equipment and the demand for network bandwidth. Therefore, it can solve the problem in the related art that the message parsing has high requirements on the equipment due to the excessive depth of the forwarding label or the low data encapsulation efficiency due to too many label layers.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a hardware structure block diagram of a mobile terminal of a message sending method according to an embodiment of the present disclosure;

FIG2 is a flow chart of a method for sending a message according to an embodiment of the present disclosure;

FIG3 is a schematic diagram of a FA-SID data structure according to an embodiment of the present disclosure;

FIG4 is a schematic diagram of an SR-MPLS TE service scenario according to an embodiment of the present disclosure;

FIG5 is a schematic diagram of a SR-MPLS BE service scenario according to an embodiment of the present disclosure;

FIG6 is a schematic diagram of a business scenario based on SRv6 policy according to an embodiment of the present disclosure;

FIG. 7 is a structural block diagram of a message sending device according to an embodiment of the present disclosure.

Detailed ways

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings and in combination with the embodiments.

It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are set to distinguish similar objects, and are not necessarily set to describe a specific order or sequence.

The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, FIG1 is a hardware structure block diagram of a mobile terminal of a message sending method of an embodiment of the present disclosure. As shown in FIG1, the mobile terminal may include one or more (only one is shown in FIG1) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 configured to store data, wherein the mobile terminal may also include a transmission device 106 configured to have a communication function and an input/output device 108. It can be understood by those skilled in the art that the structure shown in FIG1 is only for illustration and does not limit the structure of the mobile terminal. For example, the mobile terminal may also include more or fewer components than those shown in FIG1, or have a configuration different from that shown in FIG1.

The memory 104 may be configured to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the message sending method in the embodiment of the present disclosure. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, to implement the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the mobile terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

The transmission device 106 is configured to receive or send data via a network. Specific examples of the above-mentioned network may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (Radio Frequency, referred to as RF) module, which is configured to communicate with the Internet wirelessly.

In this embodiment, a message sending method is provided. FIG. 2 is a flow chart of the message sending method according to an embodiment of the present disclosure. As shown in FIG. 2 , the process includes the following steps:

Step S202, determining a forwarding label of each data flow in the target message, wherein the target message includes multiple data flows, the forwarding label of each data flow includes a routing field of each data flow and an identification field of each data flow, and the forwarding label of each data flow is set in the outer label of the target message;

Step S204, determining the next hop forwarding device to which the target message is sent based on the routing field of each data flow;

Step S206: Distribute the multiple data flows to the multiple parallel links in the link aggregation group based on the identification field of each data flow.

This embodiment includes but is not limited to the scenario where source routing should be set. In the source routing scenario, flow-based load balancing needs to be implemented, and the intermediate nodes need to perceive the flow and identify the flow.

Optionally, the forwarding label may be a label including a routing field and an identification field of the data flow. This is Multi-Protocol Label Switching (MPLS for short), the MPLS Label field is 20 bits, and this embodiment divides the MPLS Label into two parts, the Forwarding Equivalent Class FEC (Forwarding Equivalent Class) and the Flow Entropy Aware SID (Flow Entropy Aware SID). The FEC part can occupy 16 bits to represent the outbound adjacency of the node or multiple links, and the FEA part can occupy 4 bits, which is set based on the flow and used as the hash value hash key for load balancing of the equal-cost routing ECMP node. As shown in Figure 3, the FEA-SID can be used as a prefix-SID label, set for forwarding of SR-BE tunnels; it can also be used as an adjacent SID, set for path forwarding in the form of SR-TE and SR-policy.

Optionally, this embodiment is mainly configured to load balance multiple links between two adjacent network elements.

The execution subject of the above steps may be a terminal, a server, a specific processor provided in the terminal or the server, or a processor or processing device provided relatively independently from the terminal or the server, but is not limited thereto.

Through the above steps, by determining the forwarding label of each data stream in the target message, wherein the target message includes multiple data streams, the forwarding label of each data stream includes the routing field of each data stream and the identification field of each data stream, and the forwarding label of each data stream is set in the outer label of the target message; based on the routing field of each data stream, the next hop forwarding device for sending the target message is determined; based on the identification field of each data stream, the multiple data streams are distributed to multiple parallel links in the link aggregation group. Since the above method is based on flow-based load balancing, it will not increase the burden on the equipment, making the message encapsulation efficiency higher, reducing the cost of network equipment and the demand for network bandwidth. Therefore, it can solve the problem in the related art that the message parsing has high requirements on the equipment due to the excessive forwarding label or the data encapsulation efficiency is low due to too many label layers, so as to improve the message encapsulation efficiency and reduce the requirements of the device for message parsing.

In an exemplary embodiment, determining a forwarding label for each data flow in a target message includes:

S1, generating a routing field for each data flow and an identification field for each data flow through a controller to obtain a forwarding label for each data flow, wherein the routing field for each data flow is determined by the controller according to routing topology information of multiple routing devices, and the identification field for each data flow includes one of the following: setting the identification field of each data flow to a zero value through the controller, and setting the identification field of each data flow to a non-zero preset value through the controller.

Optionally, the routing field of each data flow and the identification field of each data flow are generated by the controller mainly in two ways:

Method 1: The controller directly sends the routing field FEC, and the identification field FEA field defaults to 0.

Method 2: The controller configures the FEA field according to different data streams and a certain algorithm (for example, random, polling, etc.).

Optionally, the controller in this embodiment needs to obtain information about the data flow.

In an exemplary embodiment, after the controller generates a routing field for each data flow and an identification field for each data flow and obtains a forwarding label for each data flow, the method further includes:

S1, when the identification field of each data flow is zero, the target message is parsed by the source routing device to obtain the message information of the target message;

S2, configuring the identification field of each data flow based on the message information; or,

S3, configure the identification field of each data flow on the network management device according to the preset whitelist mechanism.

Optionally, when the identification field of each data flow is zero, the forwarding label generated by the above method 1 is adopted, and the source routing device configures the identification field FEA of FEA-SID according to different message information and a certain algorithm (for example, random, polling, etc.).

In an exemplary embodiment, the controller generates a routing field for each data flow and a tag for each data flow. After the identification field is obtained and the forwarding label of each data flow is obtained, the method includes:

S1, when the identification field of each data flow is a non-zero preset value, the target message is encapsulated according to the forwarding label of each data flow by the source routing device.

Optionally, when the identification field of each data flow is a non-zero preset value, that is, the forwarding label determined in the second manner is adopted, the source routing device only needs to encapsulate the message according to the label stack sent by the controller.

S1, generate a routing field for each data flow and an identification field for each data flow, and obtain a forwarding label for each data flow, wherein the routing field for each data flow is determined by a source routing device according to routing topology information of multiple routing devices, and the identification field for each data flow is configured by the source routing device based on information of each data flow.

In an exemplary embodiment, distributing multiple data streams to multiple parallel links in a link aggregation group based on an identification field of each data stream includes:

S1, determining the value of the identification field of each data flow as the hash value of each data flow;

S2, using a preset algorithm to determine the parallel link corresponding to the hash value of each data stream.

Optionally, the value of the identification field for each data flow is set based on the data flow and used as a hash key for load balancing among ECMP nodes.

In an exemplary embodiment, before determining the forwarding label of each data flow in the target message, the method further includes:

S1, determine the tunnel type for transmitting the target message;

S2: Determine the bits occupied by each data flow forwarding label and the format of each data flow forwarding label based on the tunnel type.

Optionally, the tunnel type includes SR-TE, SR-TP, etc. SR-TP tunnel is a commonly used tunnel type, which provides customers with connection-oriented bidirectional path consistent services. SR-TP tunnel is an extension of unidirectional SR-TE tunnel, which is equivalent to binding two SR-TE tunnels with completely consistent paths and opposite directions.

The present disclosure is described below in conjunction with specific embodiments:

This embodiment provides a flow-based load balancing to meet the demand for network link expansion based on source routing technologies such as SR-MPLS and SRv6, without increasing the burden on devices and with higher message encapsulation efficiency.

This embodiment defines a forwarding label, which provides forwarding and certain service awareness capabilities. The forwarding label is called FEA-SID (Flow Entropy Aware SID) in this embodiment.

In the SR-MPLS network, for the MPLS label, the MPLS Label field is 20 bits. This embodiment divides the MPLS Label into two parts: FEC and FEA. The FEC part (occupying 16 bits) is used to characterize the outbound adjacency of the node or multi-link, and the FEA (occupying 4 bits) is set based on the flow and used as the hash key for load balancing of the ECMP node, as shown in Figure 3.

FEA-SID can be used as a prefix-SID label and set for SR-BE tunnel forwarding; it can also be used as an adjacent SID and set for SR-TE or SR-policy path forwarding.

This embodiment is mainly configured to balance the load of multiple links between two adjacent network elements, and is not configured to balance the load of multiple paths (paths passing through different network element nodes).

1) FEA-SID label space and label publishing methods include:

FEA-SID is used as a prefix-SID label. A segment is reserved in the SRGB (Segment Routing Global Block) global label range as FEA-SID. Like prefix-SID, FEA-SID is advertised with IGP routing information.

FEA-SID is used as an adjacent SID (adj-SID) label. A section is reserved in the SRLB (Segment Routing Local Block) local label range as FEA-SID. FEA-SID, like adj-SID, is published with IGP link information.

When FEA-SID is released, the FEC field is mainly released, and the FEA field defaults to 0. The length of the FEA field adopts a unified method across the entire network and does not need to be carried in the release information.

2) The configuration methods of FEA-SID in SDN mode include:

The controller sends the FEA-SID together with other SIDs in the label stack mode to the head node (source routing device) of the network. For the FEA field, the controller has two configuration methods:

Method 1: The controller sends FEA-SID, mainly the FEC field. The FEA field defaults to 0.

Method 2: The controller configures the FEA field of the FEA-SID according to different data flows and a certain algorithm (eg, random, polling, etc.) This embodiment requires the controller to have information about the data flows.

3) The processing methods of FEA-SID at the head node include:

The head node does not need to perceive the number of ECMP group members of the intermediate network ECMP nodes, nor does it need to perceive the link status of the ECMP group members. As a source node, the head node is the node for packet identification and label stack loading.

If the controller is implemented in mode 1, the head node configures the FEA field of the FEA-SID according to different flows and a certain algorithm (eg, random, polling, etc.). The judgment criteria for different data flows can refer to the loading rules of the general flow ID.

If the controller is implemented in mode 2, the head node only needs to encapsulate the message according to the label stack sent by the controller. The controller and the head node need to be consistent in the processing method of FEA.

4) FEA-SID is processed in ECMP nodes in the following ways:

After receiving the message, the intermediate ECMP node can determine that the current SID is FEA-SID based on the value of the currently processed SID. Then, based on the FEC field of the FEA-SID, the outbound ECMP group is determined. Then, the FEA field of the FEA-SID is used as the key value of the hash to load-share the message in the ECMP group.

In the SRv6 network, for the SRv6 label, the SRv6 SID is divided into three parts: locator, function, and argument. Compared with the implementation of SR-MPLS, the locator of SRv6 corresponds to the FEC field of SR-MPLS, and the argument field corresponds to the FEA field of SR-MPLS. The difference is that in SR-MPLS, a specific range is assigned to the FEC of the FEA-SID to identify the SID as a FEA-SID, while in SRv6, the function field is used to identify the SID as a FEA-SID. In the specific implementation, a new instruction atomic function FEA is introduced, which is set to identify the load sharing based on the value of the argument as the hash key of ECMP. If the FEA-SID belongs to an END.X instruction type, the FEA-SID can be defined as END.XFEA.

For SRv6 non-programmable scenarios, SRv6 SID is divided into two parts, one is the locator and the other is the FEA. The implementation method is similar to MPLS.

By adopting the solution of this embodiment, flow-based load balancing can be achieved in the source routing technology scenario. On the one hand, it solves the problem that the intermediate nodes lack the flow identification capability and can only hash each packet under the source routing technology. On the other hand, the solution has low requirements on device capabilities and high message encapsulation efficiency, reducing network device costs and network bandwidth requirements.

The present embodiment is described below in conjunction with a specific business scenario:

1. Service scenarios based on SR-MPLS TE/TP:

SR-MPLS TE tunnel is a common tunnel type and service carrying mode in source routing technology. In SPN network (ITU-T MTN standard), SR-TP tunnel is a common tunnel type, providing customers with connection-oriented bidirectional path consistent services. SR-TP tunnel is an extension of unidirectional SR-TE tunnel, which is equivalent to binding two SR-TE tunnels with completely consistent paths and opposite directions.

This embodiment takes SR-MPLS TE as an example. As shown in Figure 4, the network is a network based on SR-MPLS technology. There are multi-link ECMP groups between P1-P2 and P3-PE8 in the network. SR-TE1 is an SR-TE tunnel that passes through two ECMP groups. Flow 1, flow 2, and flow n are flows coming from the PE7 head node and need to be forwarded to the sink node PE8 through the SR-TE1 tunnel.

The controller uses method 2 to handle FEA. The label stack is issued according to the calculated path. P1 is an ECMP forwarding node, and the inbound SID it processes is FEA-SID, where the FEC field is 900. For flow 1, the FEA assigned by the head node PE7 is 1; for flow 2, the FEA assigned by the head node PE7 is 2. For other flows, the FEA assigned by the head node PE7 is a value between 0 and 15, depending on the allocation algorithm.

After receiving the message, the P1 node determines that the outgoing interface is a multi-link connected to P2 based on FEC; it performs hashing based on FEA to determine which specific flow is distributed to which link member of the ECMP group. The P3 forwarding direction page has an ECMP group, and the processing method is the same as that of the P1 node.

2. Service scenarios based on SR-MPLS BE:

SR-BE packets only carry the prefix-SID of the destination node, and the SR-BE forwarding path may pass through multiple nodes that need to perform ECMP. In this scenario, if flow-based load balancing is implemented on these ECMP nodes, prefix-SIDs are required to be FEA-SIDs. Each ECMP node uses the FEA of the destination node prefix-SID (FEA-SID type) as the hash key value to perform flow-based load balancing.

As shown in Figure 5, 0008 is the FEC part of the prefix-SID of node PE8. SR-BE1 is the SR-MPLS BE tunnel from PE7 to PE8.

The controller uses method 1 to handle FEA. The label stack is issued according to the final destination node. The SR-BE tunnel has only one label layer. P1 is an ECMP forwarding node, and the inbound SID it processes is FEA-SID, where the FEC field is 0008. For flow 1, the controller assigns FEA 1; for flow 2, the head node PE7 assigns FEA 2. For other flows, the head node PE7 assigns FEA values between 0 and 15, depending on the allocation algorithm.

After receiving the message, the P1 node determines that the outgoing interface is a multi-link connected to P2 based on FEC; it performs hashing based on FEA to determine which specific flow is distributed to which link member of the ECMP group.

P3 also has an ECMP group in the forwarding direction, and the processing method is the same as that of the P1 node.

3. Business scenarios based on SRv6 policy:

SRv6 is an SR technology system based on IPv6. As shown in Figure 6, the network is an SRv6 technology-based network with multiple-link ECMP groups between P1-P2 and P3-PE8. The SRv6 policy 1 shown in the figure is an SRv6 policy that passes through two ECMP groups. Flow 1, flow 2, and flow n are flows coming from the PE7 head node and need to be forwarded to the sink node PE8 through policy 1.

The controller uses method 2 to handle FEA. The label stack is issued according to the calculated path. P1 is an ECMP forwarding node. The function field of the incoming SID it processes is END.XFEA, and the locator field is 1002. For flow 1, the argument field FEA assigned by the head node PE7 is 1; for flow 2, the argument field FEA assigned by the head node PE7 is 2. For other flows, the head node PE7 assigns them specific FEA values. The value range depends on the length of the argument field, and the specific value depends on the allocation algorithm.

After receiving the message, the P1 node determines that the outgoing interface is a multi-link connected to P2 based on the locator; it performs hashing based on the FEA to determine which specific flow is distributed to which link member of the ECMP group. The P3 forwarding direction also has an ECMP group, and the processing method is the same as that of the P1 node.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiment The method can be implemented by means of software plus a necessary general hardware platform, or by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, disk, CD), and includes several instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present disclosure.

In the present embodiment, a message sending device is also provided, and the device is arranged to implement the above-mentioned embodiment and preferred implementation mode, and the descriptions which have been made are not repeated. As used below, the term "module" can implement a combination of software and/or hardware of a predetermined function. Although the device described in the following embodiments is preferably implemented with software, the implementation of hardware, or a combination of software and hardware is also possible and conceived.

FIG. 7 is a structural block diagram of a message sending device according to an embodiment of the present disclosure. As shown in FIG. 7 , the device includes:

A first determination module 72 is configured to determine a forwarding label of each data flow in a target message, wherein the target message includes multiple data flows, the forwarding label of each data flow includes a routing field of each data flow and an identification field of each data flow, and the forwarding label of each data flow is set in an outer label of the target message;

A second determination module 74 is configured to determine a next hop forwarding device to send a target message based on a routing field of each data flow;

The first distribution module 76 is configured to distribute the multiple data streams to the multiple parallel links in the link aggregation group based on the identification field of each data stream.

In an exemplary embodiment, the first determining module includes:

The first determination unit is configured to generate a routing field for each of the above-mentioned data flows and an identification field for each of the above-mentioned data flows through a controller to obtain a forwarding label for each of the above-mentioned data flows, wherein the routing field for each of the above-mentioned data flows is determined by the above-mentioned controller according to the routing topology information of the multiple above-mentioned routing devices, and the identification field for each of the above-mentioned data flows includes one of the following: setting the identification field of each of the above-mentioned data flows to a zero value through the above-mentioned controller, and setting the identification field of each of the above-mentioned data flows to a non-zero preset value through the above-mentioned controller.

In an exemplary embodiment, the apparatus further comprises:

A first parsing module is configured to generate a routing field of each of the above-mentioned data flows and an identification field of each of the above-mentioned data flows through a controller, and after obtaining a forwarding label of each of the above-mentioned data flows, when the identification field of each of the above-mentioned data flows is the above-mentioned zero value, parse the above-mentioned target message through a source routing device to obtain the message information of the above-mentioned target message;

A first configuration module is configured to configure the identification field of each of the above data flows based on the above message information; or,

The second configuration module is configured to configure the identification field of each of the above data flows according to a preset whitelist mechanism on the network management device.

In an exemplary embodiment, the apparatus further comprises:

The first encapsulation module is configured to generate a routing field for each of the above-mentioned data flows and an identification field for each of the above-mentioned data flows through a controller, and after obtaining a forwarding label for each of the above-mentioned data flows, when the identification field of each of the above-mentioned data flows is the above-mentioned preset value that is non-zero, encapsulate the above-mentioned target message according to the forwarding label of each of the above-mentioned data flows through a source routing device.

In an exemplary embodiment, the first determining module includes:

The first generating unit is configured to generate a routing field for each of the above-mentioned data flows and an identification field for each of the above-mentioned data flows, and obtain a forwarding label for each of the above-mentioned data flows, wherein the routing field for each of the above-mentioned data flows is determined by the above-mentioned source routing device according to the routing topology information of the plurality of above-mentioned routing devices, and the identification field for each of the above-mentioned data flows is determined by the above-mentioned source routing device based on the routing topology information of the plurality of above-mentioned routing devices. Information configuration for each of the above data flows.

In an exemplary embodiment, the first distribution module includes:

The second determining unit is configured to determine the value of the identification field of each of the above data flows as a hash value of each of the above data flows:

The first distribution unit is configured to use a preset algorithm to determine the parallel link corresponding to the hash value of each of the above data streams.

In an exemplary embodiment, the apparatus further comprises:

A third determination module is configured to determine a tunnel type for transmitting the target message before determining a forwarding label of each data flow in the target message;

The fourth determination module is configured to determine the bits occupied by each of the data flow forwarding labels and the format of each of the data flow forwarding labels based on the tunnel type.

It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

An embodiment of the present disclosure further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

In an exemplary embodiment, the above-mentioned computer-readable 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 an optical disk, and other media that can store computer programs.

An embodiment of the present disclosure further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

In an exemplary embodiment, the electronic device may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.

For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

Obviously, those skilled in the art should understand that the above modules or steps of the present disclosure can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present disclosure is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present disclosure and is not intended to limit the present disclosure. For those skilled in the art, the present disclosure may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principles of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

A message sending method, comprising:

Determine a forwarding label of each data stream in a target message, wherein the target message includes a plurality of the data streams, the forwarding label of each of the data streams includes a routing field of each of the data streams and an identification field of each of the data streams, and the forwarding label of each of the data streams is set in an outer label of the target message;

Determine a next-hop forwarding device for sending the target message based on the routing field of each of the data flows;

The multiple data flows are distributed to multiple parallel links in a link aggregation group based on the identification field of each data flow.
The method according to claim 1, wherein determining the forwarding label of each data flow in the target message comprises:

The controller generates a routing field for each of the data flows and an identification field for each of the data flows to obtain a forwarding label for each of the data flows, wherein the routing field for each of the data flows is determined by the controller according to routing topology information of a plurality of routing devices, and the identification field for each of the data flows includes one of the following: setting the identification field for each of the data flows to a zero value by the controller, and setting the identification field for each of the data flows to a non-zero preset value by the controller.
The method according to claim 2, wherein, after the controller generates the routing field of each of the data flows and the identification field of each of the data flows and obtains the forwarding label of each of the data flows, the method further comprises:

When the identification field of each of the data flows is the zero value, the target message is parsed by a source routing device to obtain message information of the target message;

configuring an identification field of each of the data flows based on the message information; or,

The identification field of each data flow is configured on the network management device according to the preset whitelist mechanism.
The method according to claim 2, wherein, after the controller generates the routing field of each of the data flows and the identification field of each of the data flows and obtains the forwarding label of each of the data flows, the method comprises:

In a case where the identification field of each of the data flows is the preset value that is not zero, the target message is encapsulated according to the forwarding label of each of the data flows by the source routing device.
The method according to claim 1, wherein determining the forwarding label of each data flow in the target message includes:

Generate a routing field for each of the data flows and an identification field for each of the data flows, and obtain a forwarding label for each of the data flows, wherein the routing field for each of the data flows is determined by a source routing device according to routing topology information of a plurality of the routing devices, and the identification field for each of the data flows is configured by the source routing device based on information of each of the data flows.
The method according to claim 1, wherein distributing the plurality of data streams to the plurality of parallel links in the link aggregation group based on the identification field of each of the data streams comprises:

Determine the value of the identification field of each of the data flows as a hash value of each of the data flows;

A preset algorithm is used to determine the parallel link to which the hash value of each data stream is distributed.
The method according to claim 1, wherein before determining the forwarding label of each data flow in the target message, the method further comprises:

Determining a tunnel type for transmitting the target message;

The bits occupied by each of the data flow forwarding labels and the format of each of the data flow forwarding labels are determined based on the tunnel type.
A message sending device, comprising:

A first determination module is configured to determine a forwarding label of each data stream in a target message, wherein the target message includes a plurality of the data streams, the forwarding label of each of the data streams includes a routing field of each of the data streams and an identification field of each of the data streams, and the forwarding label of each of the data streams is set in an outer label of the target message;

A second determination module is configured to determine a next-hop forwarding device for sending the target message based on a routing field of each of the data flows;

The first distribution module is configured to distribute the multiple data streams to multiple parallel links in a link aggregation group based on the identification field of each data stream.
A computer-readable storage medium having a computer program stored therein, wherein the computer program implements the method described in any one of claims 1 to 7 when executed by a processor.
An electronic device comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the method described in any one of claims 1 to 7.