CN118473968A - Message processing method, device, network equipment and storage medium - Google Patents

Abstract

The present application discloses a message processing method, apparatus, network device and storage medium, wherein the method comprises: a first network device encapsulates an outer message header for a first message to obtain a second message; wherein the first message represents a message that needs to be detected along with the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message and a first device identifier; the first information represents the along-flow detection information of the first message; the first device identifier is used to identify the first network device.

Description

Message processing method, device, network equipment and storage medium

Technical Field

The present application relates to the field of wireless technology, and in particular to a message processing method, apparatus, network equipment and storage medium.

Background Art

In the related art, when performing flow detection in a native IP scenario, the flow label field is used to carry quality detection information, where different service flows are identified by flow IDs. However, at present, the number of flow IDs is insufficient to support the explosive growth of service types and the number of services.

Summary of the invention

In order to solve the related technical problems, the embodiments of the present application provide a message processing method, apparatus, network equipment and storage medium.

The technical solution of the embodiment of the present application is implemented as follows:

The embodiment of the present application provides a message processing method, which is applied to a first network device, including:

Encapsulate the outer message header of the first message to obtain the second message; wherein,

The first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; the first device identifier is used to identify the first network device.

Wherein, in the above scheme, the method further comprises:

The second message is sent based on the forwarding path corresponding to the first message.

In the above solution, the flow identifier is carried in the flow label field of the outer packet header.

In the above scheme, the flow identifier is carried in the M first bits in the flow label field of the outer message header; the flow label field includes M first bits and N second bits; the second bit is used to carry the flow detection information of the first message; and M and N are both integers greater than 1.

In the above solution, the M first bits are represented by the highest or lowest M adjacent bits in the flow label field of the outer packet header.

In the above solution, the flow identifier is allocated by a software defined network (SDN) controller or generated by the first network device based on the five-tuple information of the first message.

In the above solution, the first device identifier is carried in the source address field of the outer message header.

In the above scheme, the first device identifier is carried in all bits of the source address field of the outer message header, or in L consecutive adjacent bits of the source address field of the outer message header; L is an integer greater than 1.

In the above solution, the first device identifier includes:

a routing identifier of the Border Gateway Protocol (BGP) of the first network device; or

A binary value of a set number of bits issued by the SDN controller based on global allocation; or,

The IPv4 and/or IPv6 loopback address of the first network device.

The embodiment of the present application further provides a message processing method, which is applied to a second network device, including:

Receive a second message; wherein,

The second message is obtained by encapsulating the first message with an outer message header by the first network device; the first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; the first device identifier is used to identify the first network device.

Wherein, in the above scheme, the method further comprises:

Reporting the second information to the SDN controller; wherein,

The second information includes a flow detection result of the second message by the second network device based on the first information; the second information also includes the flow identifier and the first device identifier.

In the above solution, the method further comprises:

sending the second message based on the forwarding path corresponding to the first message; or,

Decapsulate the second message to obtain the first message.

In the above solution, the flow identifier is carried in the flow label field of the outer packet header.

In the above scheme, the flow identifier is carried in the M first bits in the flow label field of the outer message header; the flow label field includes M first bits and N second bits; the second bit is used to carry the flow detection information of the first message; and M and N are both integers greater than 1.

In the above solution, the M first bits are represented by the highest or lowest M adjacent bits in the flow label field of the outer packet header.

In the above solution, the first device identifier is carried in the source address field of the outer message header.

In the above scheme, the first device identifier is carried in all bits of the source address field of the outer message header, or in L consecutive adjacent bits of the source address field of the outer message header; L is an integer greater than 1.

The present application also provides a message processing device, including:

The encapsulation unit is used to encapsulate the outer message header of the first message to obtain the second message; wherein,

The first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; the first device identifier is used to identify the first network device.

The present application also provides a message processing device, including:

A receiving unit, configured to receive a second message; wherein:

The second message is obtained by encapsulating the first message with an outer message header by the first network device; the first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; the first device identifier is used to identify the first network device.

The embodiment of the present application further provides a first network device, comprising: a first processor and a first communication interface; wherein,

The first processor is used to encapsulate the outer message header for the first message to obtain a second message; wherein,

The first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; the first device identifier is used to identify the first network device.

The embodiment of the present application further provides a second network device, including: a second processor and a second communication interface; wherein,

The second communication interface is used to receive a second message; wherein,

The second message is obtained by encapsulating the first message with an outer message header by the first network device; the first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; the first device identifier is used to identify the first network device.

The embodiment of the present application further provides a first network device, comprising: a first processor and a first memory for storing a computer program that can be run on the processor,

Wherein, when the first processor is used to run the computer program, it executes the steps of any one of the above-mentioned methods on the first network device side.

The embodiment of the present application further provides a second network device, comprising: a second processor and a second memory for storing a computer program that can be run on the processor,

Wherein, when the second processor is used to run the computer program, it executes the steps of any one of the above-mentioned methods on the second network device side.

An embodiment of the present application further provides a storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program implements the steps of any of the above-mentioned methods on the first network device side, or implements the steps of any of the above-mentioned methods on the second network device side.

In the message processing method, apparatus, network device and storage medium provided in the embodiments of the present application, the first network device encapsulates the outer message header of the first message to be detected along the flow to obtain a second message. The outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier for identifying the first network device; the first information represents the along-flow detection information of the first message. In the above scheme, the flow identifier is combined with the device identifier to identify the service flow, so that the along-flow detection can support more service types and service quantities.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a message processing method according to an embodiment of the present application;

FIG2 is a schematic diagram of a data structure of an example of an SRv6 BE message header according to an embodiment of the present application;

FIG3 is a schematic diagram of a naked IP flow detection process according to an embodiment of the present application;

FIG4 is an example diagram of an SRv6 BE message header according to an embodiment of the present application;

FIG5 is a flow chart of another message processing method according to an embodiment of the present application;

FIG6 is a schematic diagram of the structure of a message processing device according to an embodiment of the present application;

FIG7 is a schematic diagram of the structure of another message processing device according to an embodiment of the present application;

FIG8 is a schematic diagram of the structure of a first network device according to an embodiment of the present application;

FIG. 9 is a schematic diagram of the structure of the second network device according to an embodiment of the present application.

DETAILED DESCRIPTION

With the explosive growth of business types and business numbers, the network has diverse requirements for service level agreements (SLAs). Therefore, it is crucial to achieve different levels of SLA services with higher quality and to forward business messages with higher accuracy. Flow detection technology is a forwarding path quality detection technology directly related to the business. This technology carries the quality detection information of the forwarding path of the business message in the message. The detection process is deeply coupled with the actual forwarding path of the business message, which can more accurately detect the quality of the forwarding path.

For Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6) messages, the message format is fixed, and the reserved bits in the message format are not sufficient to support flow detection. Therefore, the relevant technology adopts the outer message header encapsulation method and does not modify the inner original message header. In this way, the quality detection of the forwarding path on the network side will not affect the inner service message. In actual application, in order to improve the forwarding performance while distinguishing different service messages, flow identifiers are used. Each flow identifier is used to uniquely identify a service flow. In addition, in order to realize flow detection in the bare IP scenario, the upper 4 bits of the "flow label" field are used to carry quality detection information, and the flow identifier bits in the flow label field are reduced to 16 bits. In this way, in theory, 65,535 different service flows can be supported by flow identifiers.

However, due to the unclear direction of service messages and the multiple forwarding paths, tens of thousands of network edge devices need to enable flow detection technology and use flow identifiers to distinguish different service flows. At the same time, in order to have higher detection accuracy and to solve the problem of being unable to identify the latency differences caused by different forwarding boards inside the head and tail node forwarding devices, flow identifiers need to be allocated by interface, that is, service messages on different interfaces of the same device need to use different flow identifiers, which makes the number of flow identifiers required for network edge forwarding devices increase exponentially according to the number of interfaces involved. In summary, the current number of flow identifiers is insufficient to support the explosive growth in the types and number of services.

Based on this, in each embodiment of the present application, the first network device encapsulates the outer message header of the first message to be detected along the flow to obtain a second message. The outer message header carries at least the first information, the flow identifier corresponding to the first message, and the first device identifier for identifying the first network device; the first information represents the along-flow detection information of the first message. In the above scheme, the flow identifier is combined with the device identifier to identify the service flow, so that the along-flow detection can support more service types and service quantities.

The present application is further described in detail below in conjunction with the accompanying drawings and embodiments.

The present application embodiment provides a message processing method, which is applied to a first network device. Referring to FIG. 1 , the method includes:

Step 101: encapsulate an outer message header for a first message to obtain a second message.

Among them, the first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; and the first device identifier is used to identify the first network device.

In the embodiment of the present application, the outer message header encapsulates the flow identifier and the first device identifier corresponding to the first message, so that in the message forwarding process, the service flow can be uniquely determined by combining the flow identifier and the first device identifier encapsulated in the outer message header. In other words, even if the flow identifiers of two network devices are repeated, since the device identifiers of different network devices are different, it is still possible to distinguish different service flows, thereby solving the technical problem that the flow identifier does not support the type and number of services.

For example, the flow identifiers encapsulated by network device 1 and network device 2 are both "100", but different service flows can be distinguished by combining the device identifier "Device IP:1.1.1.1" of network device 1 and the device identifier "Device IP:2.2.2.2" of network device 2.

In one embodiment, the method further comprises:

The second message is sent based on the forwarding path corresponding to the first message.

In actual application, in the public Internet, service messages are generally forwarded in the form of naked IP. When a message needs to be detected along with the flow, an outer message header is encapsulated for the message, and the along-flow detection information is encapsulated in the outer message header. Here, the outer message header includes but is not limited to the SRv6 BE message header, the IPv6 message header, etc. In the embodiment of the present application, the SRv6 BE message header is used as an example to illustrate the scheme, and other outer message header encapsulation schemes can be referred to accordingly.

In one embodiment, the flow identifier is carried in a flow label field of the outer packet header.

Further, in one embodiment, the flow identifier is carried in the M first bits in the flow label field of the outer message header; the flow label field includes M first bits and N second bits; the second bit is used to carry the flow detection information of the first message; and M and N are both integers greater than 1.

Optionally, the M first bits are represented by the highest or lowest M adjacent bits in the flow label field of the outer packet header.

In one embodiment, the flow identifier is allocated by an SDN controller or generated by the first network device based on quintuple information of the first message.

Furthermore, in one embodiment, the first device identifier is carried in a source address field of the outer message header.

In actual application, the source IPv6 address of the outer packet header, ie, the Device IP, is used to uniquely identify the first network device.

Optionally, the first device identifier is carried in all bits of the source address field of the outer message header, or in L consecutive adjacent bits of the source address field of the outer message header; L is an integer greater than 1.

In one embodiment, the first device identifier includes:

a BGP routing identifier of the first network device; or

An IPv6 address generated by converting a binary value of a set number of bits issued by the SDN controller based on global allocation; or,

The IPv4 and/or IPv6 loopback address of the first network device.

The embodiments of the present application are described below through specific examples.

Based on the initial SRv6 BE header data structure, Figure 2 shows a data structure diagram of an SRv6 BE header example that carries flow detection information. It can be seen that the fields that carry flow detection information are mainly concentrated in the two field areas of Traffic class and flow label; the fields used to distinguish different service flows are mainly concentrated in the two field areas of source address (Source address) and flow label.

Among them, the flow detection flag bit (F) and the flow detection mode bit (E) are mainly deployed in the Traffic class field, each occupying 1 bit; the flow detection information, including packet loss (L), delay (D) and detection period (P), is mainly deployed in the flow label field, occupying a total of 4 bits, of which the detection period (P) occupies 2 bits. Optionally, these 4 bits of information can be located in the highest adjacent 4 bits or the lowest adjacent 4 bits of the flow label field, and the bit positions of packet loss (L), delay (D) and detection period (P) in the flow label field are not limited, and the position order of these three types of flow detection information in the flow label field is also not limited, only requiring that the 2 bits occupied by the detection period (P) must be adjacent.

In actual application, when the flow detection flag (F) is set to 1, it indicates that the message is a message that needs to be detected. At this time, in the flow label field, excluding the 4 bits occupied by packet loss (L), delay (D) and detection period (P), the remaining 16 bits are used to carry the flow identifier. In a single forwarding device, the value of the flow identifier must be guaranteed to be unique to clearly distinguish different service flows.

In the source address field, all 128 bits or part of the low bits of the source IP address of the outer packet header are used to carry the first device identifier (Device IP) to identify the first network device, and the Device IP should be unique in the entire network. Here, taking the use of the lower 32 bits as an example, as shown in Figure 3, the first device identifier can be any of the following;

An IPv6 address generated by converting the BGP routing identifier of the first network device; or

An IPv6 address generated by converting a 32-bit binary value issued by the SDN controller based on global allocation; or,

The IPv6 loopback address of the first network device.

When the SDN controller converts the 32-bit binary value issued based on global allocation to generate an IPv6 address, the corresponding source IPv6 address encapsulated in the SRv6 BE message is converted and generated by the 32-bit binary value. At the same time, in order to prevent the downstream network device from filtering the message and causing packet loss, the network device forwarding the message should publish the corresponding IPv6 route externally.

When an IPv6 loopback address is used as the first device identifier, the lower 32 bits of the IPv6 loopback address should be ensured to be unique throughout the entire network, so as to ensure that the first device identifier is unique throughout the entire network.

Next, further examples are given to illustrate the corresponding naked IP flow detection process after the outer packet header is encapsulated using the embodiment of the present application.

As shown in Figure 3, first, the SDN controller sends basic configuration information through Netconf, and diverts and encapsulates the packets that need to be detected. In addition, the SDN controller also establishes a BGP flow peer with the network edge device to send redirection Flow spec information based on the service source and destination network segment.

Secondly, the head node device of the flow detection, that is, the edge device of the IP bearer network, redirects the message according to the Flow spec configuration information and encapsulates the message with the SRv6 BE message header. An example of SRv6 BE message header encapsulation is shown in Figure 4, where the flow detection flag (F) is set to 1, indicating that the message is a message that needs to be detected; the flow detection mode adopts the point-by-point detection mode; the bits corresponding to the packet loss (L), delay (D) and detection period (P) are marked according to the configuration information sent by the SDN controller, and the corresponding timestamp is recorded to facilitate the determination of the corresponding detection time when the flow detection information is sent to the SDN controller; the flow identifier is generated according to the five-tuple information of the inner layer message, or it is generated by the forwarding device itself, or it is uniformly allocated and issued by the SDN controller; the device identifier uses the last 32 bits of the source IP address of the message.

After encapsulating the message with the SRv6 BE message header, the head node device of the flow detection forwards the message according to the forwarding path. Afterwards, the intermediate network device responsible for message forwarding in the IP bearer network, that is, the intermediate node of the flow detection, performs relevant detection based on the flow detection information carried in the outer message header, and sends the collected detection data to the SDN controller. Here, in addition to the detection results of the flow detection, the intermediate network device should also send the flow identifier and device identifier to the SDN controller, so that a service flow can be jointly identified based on the flow identifier and device identifier.

After that, when the message is forwarded to the other side of the IP bearer network, that is, the tail node device for flow detection, on the one hand, the tail node device needs to perform the same flow detection-related operations as the intermediate network device; on the other hand, the tail node device also needs to remove the SRv6 BE message header encapsulated by the head node device and complete subsequent forwarding by querying the inner original message.

Finally, the SDN controller implements the flow detection for a certain service flow by collecting and processing the flow detection results sent by each network device and the flow identifier and device identifier information sent simultaneously with the flow detection results.

Correspondingly, the embodiment of the present application also provides a message processing method, which is applied to a second network device. Here, the second network device can be an intermediate network device responsible for message forwarding in the IP bearer network, that is, an intermediate network device for flow detection, or it can also be an end node device for flow detection. Referring to Figure 5, the method includes:

Step 501: Receive a second message.

Among them, the second message is obtained by the first network device encapsulating the first message with an outer message header; the first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; and the first device identifier is used to identify the first network device.

In one embodiment, the method further comprises:

Reporting the second information to the SDN controller; wherein,

The second information includes a flow detection result of the second message by the second network device based on the first information, and also includes the flow identifier and the first device identifier.

In one embodiment, the method further comprises:

sending the second message based on the forwarding path corresponding to the first message; or,

Decapsulate the second message to obtain the first message.

In one embodiment, the flow identifier is carried in a flow label field of the outer packet header.

In one embodiment, the flow identifier is carried in the M first bits in the flow label field of the outer message header; the flow label field includes M first bits and N second bits; the second bit is used to carry the flow detection information of the first message; and M and N are both integers greater than 1.

In one embodiment, the M first bits are represented by the highest or lowest M adjacent bits in the flow label field of the outer packet header.

In one embodiment, the first device identifier is carried in a source address field of the outer message header.

In one embodiment, the first device identifier is carried in all bits of the source address field of the outer message header, or in L consecutive adjacent bits of the source address field of the outer message header; L is an integer greater than 1.

In the embodiment of the present application, an outer message header is encapsulated in the outer layer of a bare IP service message, and field areas such as a Traffic class field, a flow label field, and a source address field in the outer message header are used to carry flow detection information, as well as a flow identifier and a device identifier. The flow identifier and the device identifier are combined to uniquely identify the service flow corresponding to the message, thereby enabling flow detection of service messages to be adapted to a larger-scale public IP bearer network.

In order to implement the message processing method on the first network device side of the embodiment of the present application, the embodiment of the present application further provides a message processing device, which is arranged on the first network device. As shown in FIG6 , the device includes:

The encapsulation unit 601 is used to encapsulate the outer message header of the first message to obtain a second message; wherein,

The first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; the first device identifier is used to identify the first network device.

In one embodiment, the device further comprises:

The first sending unit is used to send the second message based on the forwarding path corresponding to the first message.

In one embodiment, the flow identifier is carried in a flow label field of the outer packet header.

In one embodiment, the flow identifier is carried in the M first bits in the flow label field of the outer message header; the flow label field includes M first bits and N second bits; the second bit is used to carry the flow detection information of the first message; and M and N are both integers greater than 1.

In one embodiment, the M first bits are represented by the highest or lowest M adjacent bits in the flow label field of the outer packet header.

In one embodiment, the flow identifier is allocated by an SDN controller or generated by the first network device based on quintuple information of the first message.

In one embodiment, the first device identifier is carried in a source address field of the outer message header.

In one embodiment, the first device identifier is carried in all bits of the source address field of the outer message header, or in L consecutive adjacent bits of the source address field of the outer message header; L is an integer greater than 1.

In one embodiment, the first device identifier includes:

a BGP routing identifier of the first network device; or

An IPv6 address generated by converting a binary value of a set number of bits issued by the SDN controller based on global allocation; or,

The IPv4 and/or IPv6 loopback address of the first network device.

In actual application, the encapsulation unit 601 can be implemented by a processor in a message processing device; the first sending unit can be implemented by a communication interface in the message processing device.

In order to implement the message processing method on the second network device side of the embodiment of the present application, the embodiment of the present application further provides a message processing device, which is arranged on the first network device. As shown in FIG. 7 , the device includes:

The receiving unit 701 is used to receive a second message; wherein:

The second message is obtained by encapsulating the first message with an outer message header by the first network device; the first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; the first device identifier is used to identify the first network device.

In one embodiment, the device further comprises:

The second sending unit is used to report the second information to the SDN controller; wherein,

The second information includes a flow detection result of the second message by the second network device based on the first information; the second information also includes the flow identifier and the first device identifier.

In one embodiment, the device further comprises:

a third sending unit, configured to send the second message based on the forwarding path corresponding to the first message; or

A decapsulation unit is used to decapsulate the second message to obtain the first message.

In one embodiment, the flow identifier is carried in a flow label field of the outer packet header.

In one embodiment, the flow identifier is carried in the M first bits in the flow label field of the outer message header; the flow label field includes M first bits and N second bits; the second bit is used to carry the flow detection information of the first message; and M and N are both integers greater than 1.

In one embodiment, the M first bits are represented by the highest or lowest M adjacent bits in the flow label field of the outer packet header.

In one embodiment, the first device identifier is carried in a source address field of the outer message header.

In one embodiment, the first device identifier is carried in all bits of the source address field of the outer message header, or in L consecutive adjacent bits of the source address field of the outer message header; L is an integer greater than 1.

In actual application, the receiving unit 701, the second sending unit and the third sending unit can be implemented by a communication interface in the message processing device, and the decapsulation unit can be implemented by a processor in the message processing device.

It should be noted that: when the message processing device provided in the above embodiment performs message processing, only the division of the above program modules is used as an example. In actual application, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the message processing device provided in the above embodiment and the message processing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

Based on the hardware implementation of the above program module, and in order to implement the method on the first network device side of the embodiment of the present application, the embodiment of the present application further provides a first network device, as shown in FIG8 , the first network device 800 includes:

The first communication interface 801 is capable of exchanging information with other network nodes;

The first processor 802 is connected to the first communication interface 801 to implement information exchange with other network nodes, and is used to execute the method provided by one or more technical solutions of the first network device side when running a computer program. The computer program is stored in the first memory 803.

Specifically, the first processor 802 is used to encapsulate the outer message header for the first message to obtain the second message; wherein,

The first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; the first device identifier is used to identify the first network device.

In one embodiment, the first communication interface 801 is used to send the second message based on the forwarding path corresponding to the first message.

In one embodiment, the flow identifier is carried in a flow label field of the outer packet header.

In one embodiment, the flow identifier is carried in the M first bits in the flow label field of the outer message header; the flow label field includes M first bits and N second bits; the second bit is used to carry the flow detection information of the first message; and M and N are both integers greater than 1.

In one embodiment, the M first bits are represented by the highest or lowest M adjacent bits in the flow label field of the outer packet header.

In one embodiment, the flow identifier is allocated by an SDN controller or generated by the first network device based on quintuple information of the first message.

In one embodiment, the first device identifier is carried in a source address field of the outer message header.

In one embodiment, the first device identifier is carried in all bits of the source address field of the outer message header, or in L consecutive adjacent bits of the source address field of the outer message header; L is an integer greater than 1.

In one embodiment, the first device identifier includes:

a BGP routing identifier of the first network device; or

An IPv6 address generated by converting a binary value with a set number of bits issued by the SDN controller based on global allocation; or,

The IPv4 and/or IPv6 loopback address of the first network device.

It should be noted that the specific processing process of the first processor 802 and the first communication interface 801 can be understood by referring to the above method.

Of course, in actual application, the various components in the first network device 800 are coupled together through the bus system 804. It can be understood that the bus system 804 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 804 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, various buses are marked as the bus system 804 in FIG. 8.

The first memory 803 in the embodiment of the present application is used to store various types of data to support the operation of the first network device 800. Examples of such data include: any computer program used to operate on the first network device 800.

The method disclosed in the above embodiment of the present application can be applied to the first processor 802, or implemented by the first processor 802. The first processor 802 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the first processor 802. The above-mentioned first processor 802 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The first processor 802 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the first memory 803, and the first processor 802 reads the information in the first memory 803 and completes the steps of the above method in combination with its hardware.

In an exemplary embodiment, the first network device 800 may be implemented by one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to execute the aforementioned method.

Based on the hardware implementation of the above program module, and in order to implement the method on the second network device side of the embodiment of the present application, the embodiment of the present application further provides a second network device, as shown in FIG. 9 , the second network device 900 includes:

The second communication interface 901 is capable of exchanging information with other network nodes;

The second processor 902 is connected to the second communication interface 901 to implement information exchange with other network nodes, and is used to execute the method provided by one or more technical solutions of the second network device side when running a computer program. The computer program is stored in the second memory 903.

Specifically, the second communication interface 901 is used to receive a second message; wherein,

The second message is obtained by encapsulating the first message with an outer message header by the first network device; the first message represents a message that needs to be detected along the flow; the outer message header carries at least first information, a flow identifier corresponding to the first message, and a first device identifier; the first information represents the along-flow detection information of the first message; the first device identifier is used to identify the first network device.

In one embodiment, the second communication interface 901 is also used to report the second information to the SDN controller;

The second information includes a flow detection result of the second message by the second network device based on the first information; the second information also includes the flow identifier and the first device identifier.

In one embodiment, the second communication interface 901 is further configured to send the second message based on the forwarding path corresponding to the first message; or

The second processor 902 is configured to decapsulate the second message to obtain the first message.

In one embodiment, the flow identifier is carried in a flow label field of the outer packet header.

In one embodiment, the flow identifier is carried in the M first bits in the flow label field of the outer message header; the flow label field includes M first bits and N second bits; the second bit is used to carry the flow detection information of the first message; and M and N are both integers greater than 1.

In one embodiment, the M first bits are represented by the highest or lowest M adjacent bits in the flow label field of the outer packet header.

In one embodiment, the first device identifier is carried in a source address field of the outer message header.

In one embodiment, the first device identifier is carried in all bits of the source address field of the outer message header, or in L consecutive adjacent bits of the source address field of the outer message header; L is an integer greater than 1.

It should be noted that the specific processing process of the second processor 902 and the second communication interface 901 can be understood by referring to the above method.

Of course, in actual application, the various components in the second network device 900 are coupled together through the bus system 904. It can be understood that the bus system 904 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 904 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, various buses are marked as the bus system 904 in Figure 9.

The second memory 903 in the embodiment of the present application is used to store various types of data to support the operation of the second network device 900. Examples of such data include: any computer program used to operate on the second network device 900.

The method disclosed in the above embodiment of the present application can be applied to the second processor 902, or implemented by the second processor 902. The second processor 902 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of the hardware in the second processor 902 or an instruction in the form of software. The above-mentioned second processor 902 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The second processor 902 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the second memory 903, and the second processor 902 reads the information in the second memory 903 and completes the steps of the above method in combination with its hardware.

In an exemplary embodiment, the second network device 900 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned methods.

It can be understood that the memory (first memory 803, second memory 903) of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a ferromagnetic random access memory, a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), direct memory bus random access memory (DRRAM). The memory described in the embodiments of the present application is intended to include but is not limited to these and any other suitable types of memory.

In an exemplary embodiment, the embodiment of the present application further provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, for example, including a first memory 803 storing a computer program, and the computer program can be executed by the first processor 802 of the first network device 800 to complete the steps of the aforementioned first network device side method. For another example, a second memory 903 storing a computer program can be executed by the second processor 902 of the second network device 900 to complete the steps of the aforementioned second network device side method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM.

It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

The term "and/or" herein is only a description of the association relationship of the associated objects, indicating that there may be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "at least one" herein represents any combination of at least two of any one or more of a plurality of. For example, including at least one of A, B, and C can represent including any one or more elements selected from the set consisting of A, B, and C.

In addition, the technical solutions described in the embodiments of the present application can be combined arbitrarily without conflict.

The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application.

Claims (24)

1. The message processing method is characterized by being applied to first network equipment and comprising the following steps:

packaging an outer layer message header for the first message to obtain a second message; wherein,

The first message characterizes a message needing to be detected along with the flow; the outer layer message header at least carries first information, a flow identifier corresponding to the first message and a first equipment identifier; the first information characterizes the flow-following detection information of the first message; the first device identification is used to identify the first network device.

2. The method according to claim 1, wherein the method further comprises:

and sending the second message based on the forwarding path corresponding to the first message.

3. The method according to claim 1 or 2, wherein the flow identity is carried in a flow label field of the outer layer header.

4. A method according to claim 3, wherein the flow identity is carried in M first bits in a flow label field of the outer layer header; the stream tag field includes M first bits and N second bits; the second bit is used for bearing stream following detection information of the first message; and M and N are integers greater than 1.

5. The method of claim 4, wherein the M first bits are characterized as the highest or lowest M adjacent bits in a stream tag field of the outer layer header.

6. The method of claim 1 or 2, wherein the flow identification is assigned by a software defined network, SDN, controller or generated by the first network device based on five tuple information of the first message.

7. The method according to claim 1 or 2, wherein the first device identification is carried in a source address field of the outer layer header.

8. The method of claim 7, wherein the first device identifier is carried in all bits of a source address field of the outer layer header or in consecutive L adjacent bits of the source address field of the outer layer header; and L is an integer greater than 1.

9. The method of claim 8, wherein the first device identification comprises:

A route identification of a border gateway protocol BGP of the first network device; or alternatively

Binary values of the set number of bits issued by the SDN controller based on the global allocation; or alternatively

An IPv4 and/or IPv6 loop-back address of the first network device.

10. The message processing method is characterized by being applied to the second network equipment and comprising the following steps:

receiving a second message; wherein,

The second message is obtained by the first network equipment to the first message encapsulation outer layer message header; the first message characterizes a message needing to be detected along with the flow; the outer layer message header at least carries first information, a flow identifier corresponding to the first message and a first equipment identifier; the first information characterizes the flow-following detection information of the first message; the first device identification is used to identify the first network device.

11. The method according to claim 10, wherein the method further comprises:

reporting second information to the SDN controller; wherein,

The second information comprises a stream following detection result of the second message by the second network device based on the first information; the second information also includes the flow identification and the first device identification.

12. The method according to claim 10, wherein the method further comprises:

Transmitting the second message based on a forwarding path corresponding to the first message; or alternatively

And decapsulating the second message to obtain the first message.

13. The method according to any of claims 10 to 12, wherein the flow identity is carried in a flow label field of the outer layer header.

14. The method of claim 13, wherein the flow identification is carried in M first bits in a flow label field of the outer layer header; the stream tag field includes M first bits and N second bits; the second bit is used for bearing stream following detection information of the first message; and M and N are integers greater than 1.

15. The method of claim 14, wherein the M first bits are characterized by the highest or lowest M adjacent bits in a stream tag field of the outer layer header.

16. The method according to any of claims 10 to 12, wherein the first device identification is carried in a source address field of the outer layer header.

17. The method of claim 16, wherein the first device identifier is carried in all bits of a source address field of the outer layer header or in consecutive L adjacent bits of the source address field of the outer layer header; and L is an integer greater than 1.

18. A message processing apparatus, comprising:

The encapsulation unit is used for encapsulating the outer layer message header for the first message to obtain a second message; wherein,

The first message characterizes a message needing to be detected along with the flow; the outer layer message header at least carries first information, a flow identifier corresponding to the first message and a first equipment identifier; the first information characterizes the flow-following detection information of the first message; the first device identification is used to identify the first network device.

19. A message processing apparatus, comprising:

The receiving unit is used for receiving the second message; wherein,

The second message is obtained by the first network equipment to the first message encapsulation outer layer message header; the first message characterizes a message needing to be detected along with the flow; the outer layer message header at least carries first information, a flow identifier corresponding to the first message and a first equipment identifier; the first information characterizes the flow-following detection information of the first message; the first device identification is used to identify the first network device.

20. A first network device, comprising: a first processor and a first communication interface; wherein,

The first processor is used for packaging an outer layer message header for the first message to obtain a second message; wherein,

The first message characterizes a message needing to be detected along with the flow; the outer layer message header at least carries first information, a flow identifier corresponding to the first message and a first equipment identifier; the first information characterizes the flow-following detection information of the first message; the first device identification is used to identify the first network device.

21. A second network device, comprising: a second processor and a second communication interface; wherein,

The second communication interface is used for receiving a second message; wherein,

The second message is obtained by the first network equipment to the first message encapsulation outer layer message header; the first message characterizes a message needing to be detected along with the flow; the outer layer message header at least carries first information, a flow identifier corresponding to the first message and a first equipment identifier; the first information characterizes the flow-following detection information of the first message; the first device identification is used to identify the first network device.

22. A first network device, comprising: a first processor and a first memory for storing a computer program capable of running on the processor,

Wherein the first processor is adapted to perform the steps of the method of any of claims 1 to 9 when the computer program is run.

23. A second network device, comprising: a second processor and a second memory for storing a computer program capable of running on the processor,

Wherein the second processor is adapted to perform the steps of the method of any of claims 10 to 17 when the computer program is run.

24. A storage medium having stored thereon a computer program, which when executed by a processor, performs the steps of the method of any of claims 1 to 9 or performs the steps of the method of any of claims 10 to 17.