WO2024125103A1 - Packet processing method and network side device - Google Patents

Abstract

Embodiments of the present application provide a packet processing method and a network side device. The method comprises: obtaining a first packet feature corresponding to a packet to be processed; according to the first packet feature, determining a target packet processing rule from pre-configured packet processing rules, wherein different first packet features correspond to different packet processing rules; and processing said packet according to configuration data of at least one processing sub-rule in the target packet processing rule.

Description

Message processing method and network side device

cross reference

This application claims priority to a Chinese patent application filed with the China Patent Office on December 13, 2022, with application number 202211596157.6 and title “Message Processing Method and Network Side Device”. The entire contents of the application are incorporated by reference into this application.

Technical Field

The embodiments of the present application relate to the field of communication technology, and in particular to a message processing method and a network-side device.

Background technique

With the rapid development of 5G communication technology, various fields have higher and higher requirements for network acceleration performance. Hardware is usually used to accelerate the processing of messages to meet the acceleration performance of the network, such as routers, switches, servers, and smart network cards.

In some scenarios, when hardware is used to accelerate the processing of messages, messages are usually processed in a fixed manner. For example, the message distribution strategy is relatively rigid when processing messages. A type of message will only be delivered to a single queue or evenly distributed to multiple queues, and only fixed and simple message information can be provided to upper-level software users, such as the address, offset, and length of the message. However, different services require different message information, and using a fixed method to process messages cannot meet different business needs, and the flexibility of message processing is low.

Summary of the invention

The embodiments of the present application provide a message processing method and a network-side device to solve the problem that the message processing method cannot meet different business requirements and the message processing flexibility.

In a first aspect, a message processing method is provided, comprising: obtaining a first message feature corresponding to a message to be processed; determining a target message processing rule from pre-configured message processing rules based on the first message feature, wherein different first message features correspond to different message processing rules; and processing the message to be processed according to configuration data of at least one processing sub-rule in the target message processing rule.

In a second aspect, a message processing device is provided, including: an acquisition module, used to obtain a first message feature corresponding to a message to be processed; a determination module, used to determine a target message processing rule from pre-configured message processing rules based on the first message feature, wherein different first message features correspond to different message processing rules; and a processing module, used to process the message to be processed according to configuration data of at least one processing sub-rule in the target message processing rule.

In a third aspect, a network side device is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

In a fourth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

In a fifth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.

In a sixth aspect, a computer program/program product is provided, wherein the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the steps of the message processing method as described in the first aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic flow chart of a message processing method provided in an embodiment of the present application;

FIG2 is a schematic diagram showing data source information provided by an embodiment of the present application;

FIG3 is a schematic diagram showing a configuration of a message processing rule provided in an embodiment of the present application;

FIG4 is a schematic diagram showing the deep parsing configuration information provided by an embodiment of the present application;

FIG5 is a schematic diagram showing a buffer pool provided in an embodiment of the present application;

6 and 7 are schematic diagrams showing queue configurations provided in embodiments of the present application;

FIG8 is a schematic diagram showing the structure of a message processing device provided in an embodiment of the present application;

FIG9 shows a schematic diagram of the structure of a network side device provided in an embodiment of the present application.

Detailed ways

The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and/or" in the specification and claims represents at least one of the connected objects, and the character "/" generally represents that the objects associated with each other are in an "or" relationship.

The message processing method provided in the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

As shown in FIG1 , a flow chart of a message processing method provided in an embodiment of the present application is provided, and the method includes:

Step S101, obtaining a first message feature corresponding to a message to be processed.

The first message feature refers to the feature of the message to be processed, which includes but is not limited to: the number of bytes offset from the message header, the length of the extracted data, the data matching mask, etc. For the first message feature, the message feature description information in the predefined data source information can be used to extract the first message feature from the message to be processed. Obtain a first message feature.

In order to ensure that a standardized and effective first message feature is obtained to improve the efficiency of message processing, in a possible implementation manner, obtaining the first message feature corresponding to the message to be processed includes:

Determine target data source information from pre-configured data source information, where the target data source information includes first message feature description information; and obtain a first message feature corresponding to the first message feature description information from a message to be processed.

The data source information is a predefined standard table for extracting message features. The message features are extracted according to the message feature description information in the predefined data source in the table, wherein the message feature description information is used to indicate the required message features to be extracted from the message.

For example, as shown in FIG2 , the data source information includes n pieces of data source information, namely, data source 1 to data source n, and each piece of data source information corresponds to a first identifier (the first identifier is the digital number after the data source). Each piece of data source information includes, but is not limited to, the number of bytes offset from the message header, the length of the extracted data, the data matching mask, whether the data source is cascaded, and the first identifier of the cascaded data source. Whether the data source is cascaded refers to whether it is associated with other data sources. Among them, the number of bytes offset from the message header and the corresponding value, the length of the extracted data and the corresponding value, the data matching mask and the corresponding value, whether the data source is cascaded and the corresponding value, and the first identifier of the cascaded data source and the corresponding value are the first message description information.

In order to improve the hardware processing and storage efficiency, the maximum length of data extracted by a single data source can be set to 4 or 8 bytes. When 4 or 8 bytes are not enough, data source cascading can be configured. The maximum cascading level and maximum cascading number of data sources can be configured so that the extracted information can be stored in the message feature description information. There are multiple entries of data source information, for example, 16 entries can be configured.

Step S103: determining a target message processing rule from pre-configured message processing rules according to the first message feature.

Among them, different first message features correspond to different message processing rules.

Specifically, the message processing rule refers to the processing method for processing message features. The message processing rule pre-configures at least one configuration data for processing message features. The processing rule is also configured with a second identifier to indicate the data source information used by the message processing rule, and the message feature corresponding to the second identifier in the message processing rule. As shown in Figure 3, the configuration data in the message processing rule includes but is not limited to message upload configuration data, deep analysis configuration data, queue identifier, buffer identifier (Pool number), second identifier (data source information identifier), second message feature (matching value, mask, whether to cascade and cascade rule ID), and hash configuration data (HASH identifier). Among them, the message upload configuration data is configured with an identifier of whether to only send message fragments and the offset and length of the message fragments to be sent, or an identifier of sending a complete message is configured to send a complete message; the deep analysis configuration information includes a deep analysis identifier and deep analysis configuration information, and the deep analysis identifier indicates whether the message needs to enter the deep analysis model for further analysis. If further analysis is required, deep analysis configuration information is configured, which mainly includes custom levels, L2, L3~L5 and other levels. As shown in Figure 4, the deep analysis configuration information includes the extraction offset position and length of multiple custom fields; the L2 analysis configuration includes the destination media access control address (Media Access Control, MAC) extraction identifier, the source MAC extraction identifier, the virtual local area network (Virtual Local Area Network, VLAN) extraction identifier, and the Ethernet type Ether TYPE extraction identifier; the configuration information of L3~L5 is mainly the four-tuple/five-tuple/seven-tuple analysis and extraction identifiers related to the standard protocol information; the queue identifier indicates the starting queue number when the message is queued. If the hash configuration data is configured, the starting queue number + hash value is used as the queue for entry. If the hash configuration data is not configured, the queue is entered according to the starting queue number; the buffer identifier indicates which buffer the extracted message features are stored in; the second identifier indicates the digital number of the data source information referenced in the message processing rule, and the second message feature indicates the feature of the message that can be processed in the message processing rule.

Among them, multiple message processing rules can also be configured, such as the commonly used maximum of 32 or 64 entries. When the user configures less than the maximum number of entries, the hardware can detect the actual number of configured entries. Matching entries can be configured with priorities to solve multi-entry matching problems. For example, there are n matching entries with IDs from 1 to n. The priorities of message processing rules can be configured to decrease in sequence or increase in sequence. Furthermore, if the message does not hit any message processing rule, the default rule configuration needs to be configured. The default rule configuration needs to configure the message to continue to be sent or discarded. If it continues to be sent, the default sending needs to be configured. queue.

In a possible implementation, the message processing rule includes a second identifier and a second message feature, and determining a target message processing rule from preconfigured message processing rules according to the first message feature includes:

The first identifier and the first message feature corresponding to the target data source information are matched with the second identifier and the second message feature in each message processing rule. The message processing rule in which the first identifier matches the second identifier and the first message feature matches the second message feature is determined as the target message processing rule.

Specifically, when searching for a target message processing rule that is compatible with the first message feature from multiple message processing rules, the message processing rule is searched from multiple message processing rules according to the feature information in the first message feature and the first identifier of the first message feature. The message processing rule whose second identifier is consistent with the first identifier and whose second message feature is consistent with the first message feature is the target message processing rule.

Step S105: Process the message to be processed according to the configuration data of at least one processing sub-rule in the target message processing rule.

As mentioned above, the configuration data includes but is not limited to message upload configuration data, deep analysis configuration data, queue identifier, buffer identifier, second identifier, second message characteristics, hash configuration data, etc. The message to be processed is processed according to these configuration data in the message processing rules, which will be explained in detail later.

Through the technical solution disclosed in the embodiment of the present application, the first message feature corresponding to the message to be processed is obtained; the target message processing rule is determined from the pre-configured message processing rules according to the first message feature, wherein different first message features correspond to different message processing rules; and the message to be processed is processed according to the configuration data of at least one processing sub-rule in the target message processing rule. It is possible to flexibly process the message to be processed by using different message processing rules according to different message features, thereby using different message processing rules according to different business needs, improving the flexibility of message processing. During processing, the message can be processed according to at least one processing sub-rule in the message processing rule, further improving the flexibility of message processing.

In a possible implementation, before determining the message upload configuration data in the target message processing rule, the method further includes: configuring the buffer identifier in the message processing rule; when the message upload segment is configured as the third identifier, configuring the buffer identifier as the fifth identifier, The fifth identifier corresponds to the first buffer; when the message uploading segment is configured as the fourth identifier, the identifier of the buffer is configured as the sixth identifier, and the sixth identifier corresponds to the second buffer.

Specifically, each buffer pool (Buffer Pool) contains several buffers (Regions), as shown in Figure 5. Each buffer pool Pool in the figure contains three buffer regions, namely Region 0, Region 1, and Region 2. The buffer size in each buffer region is the same and can be applied for independently. Each buffer pool Buffer Pool sets multiple buffer regions to store different information of the message. The buffer pool Buffer Pool can support multiple, as shown in Figure 5, there are n. For each buffer region, each buffer region contains N memory buffer block addresses, each memory buffer block address corresponds to a memory buffer block, and the memory buffer blocks in different buffer regions can store different information of the message. For example, the memory buffer block in Region 0 can store the largest message, the memory buffer block in Region 1 can be used to store the smallest message description information, and the buffer block in Region 2 is neither too large nor too small and can be used to store message fragments.

When configuring a buffer pool Buffer Pool, each buffer Region can be configured separately according to the needs. For example, each memory buffer block in Region 0 is larger, such as 2K bytes, which can be used to store the complete content of the message. The memory buffer block Buffer in Region 1 is smaller, such as 64 bytes, which can be used to store message description information. The memory buffer block Buffer in Region 2 is medium, such as 256 bytes, which is used to store extracted message fragments. In a possible implementation, the buffer pool is divided into a first buffer and a second buffer; the first buffer is used to store complete messages, and the second buffer is used to store message fragments. Corresponding to the buffer, different identifiers can be configured to distinguish, so that the corresponding information can be stored in the corresponding buffer according to different identifiers of the buffer.

The message upload fragment configuration data includes the fourth identifier and the third identifier, and specifically configures the message upload fragment in the message processing rule to obtain the message upload configuration data; the configuration includes one of the following: configuring the fourth identifier of the message upload fragment, and the offset and length of the message fragment to be uploaded; configuring the third identifier of the complete message to be uploaded. Different identifiers configured in the message upload fragment are used to determine whether to upload a message fragment or a complete message.

When uploading a message fragment or a complete message, you can include the data storage sub-rule according to the processing sub-rule. The rule is stored in the corresponding buffer, specifically determining the message upload configuration data pre-configured in the data storage sub-rule of the target message processing rule; determining the buffer identifier in the message upload configuration data, and storing the message to be processed in the buffer corresponding to the buffer identifier.

Among them, determining the buffer identifier in the message upload configuration data and storing the message to be processed in the buffer corresponding to the buffer identifier includes: when the buffer identifier is a third identifier, storing the complete message corresponding to the message to be processed in the first buffer of the buffer pool; when the buffer identifier is a fourth identifier, storing at least one message fragment in the message to be processed in the second buffer of the buffer pool, and the first buffer and the second buffer are different.

In one possible implementation, the configuration data includes deep analysis configuration data, the processing sub-rules include deep analysis sub-rules, and processing the message to be processed according to the configuration data of at least one processing sub-rule in the target message processing rule includes: determining the deep analysis configuration data pre-configured in the deep analysis sub-rule of the target processing rule, the deep analysis configuration information including a deep analysis identifier and deep analysis configuration information; when the deep analysis identifier is configured as the seventh identifier, performing deep analysis processing on the message to be processed according to the deep analysis configuration information to obtain deep analysis data.

The deep analysis configuration information includes at least one of the following:

The message offset position and length of the custom field.

Destination MAC data extraction identifier.

Data extraction identifier of the source media access control address.

The data extraction identifier of the VLAN corresponding to the media access control address.

A data extraction identifier of a four-tuple and/or a five-tuple and/or a seven-tuple of a standard protocol.

Determine the queue ID in the target processing rule.

Specifically, the deep parsing configuration information includes a deep parsing flag and deep parsing configuration information. The deep parsing flag indicates whether the message needs to enter the deep parsing model for further parsing. For example, the seventh flag can be 1. When the deep parsing flag is configured as 1, it indicates whether the message needs to enter the deep parsing model for further parsing. If further parsing is required, configure the deep parsing configuration information, which mainly includes custom levels, L2, L3~L5, etc. As shown in Figure 4 above, the deep parsing The L2 parsing configuration information includes the extraction offset position and length of multiple custom fields; the L2 parsing configuration includes the destination MAC extraction identifier, source MAC extraction identifier, VLAN extraction identifier, and Ether TYPE extraction identifier; the L3~L5 configuration information mainly includes the parsing extraction identifiers such as the four-tuple/five-tuple/seven-tuple related to the standard protocol information.

In a possible implementation, when the deep analysis identifier is the eighth identifier, the processing sub-rule includes a queue processing sub-rule, the configuration data includes a queue identifier, and processing the message to be processed according to the configuration data of at least one processing sub-rule in the target message processing rule includes: determining the queue identifier pre-configured in the queue processing sub-rule of the target message processing rule; and sending the deep analysis data to the target queue corresponding to the queue identifier.

Specifically, each queue corresponds to a queue identifier. The queue identifier is preconfigured in the queue processing sub-rule, and the deep analysis data obtained after deep analysis of the identifier to be processed can be stored in the target queue.

In a possible implementation, before sending the deep parsing data to the target queue corresponding to the target queue identifier, the method further includes: determining second message feature description information corresponding to the message to be processed, the second message feature description information including the deep parsing data and configuration data of at least one processing sub-rule in the target message processing rule; sending the deep parsing data to the target queue corresponding to the target queue identifier includes: sending a storage address corresponding to the second message feature description information to the target queue corresponding to the target queue identifier. The storage address corresponding to the second message feature description information refers to the physical address of the buffer storing the second message feature description information.

Before determining the queue identifier preconfigured in the queue processing sub-rule of the target message processing rule, the method further includes: configuring the queue. The configuration includes at least one of the following: an identifier of the queue. A first alarm depth of the queue. A second alarm depth of the queue, the second alarm depth being greater than the first alarm depth.

Specifically, as shown in Figures 6 and 7, each queue can be configured with a maximum depth of n, a first alarm depth of j, and a second alarm depth of k. The number of queues can be configured to m, which can be configured according to actual needs. The receiving module in the queue management is used to extract the message queue information in the second message description information. The queue information may be a directly given queue number, or it may need to be based on the second message feature. The configuration data in the description information calculates the HASH value and uses the original queue number + HASH value as the final queue number and hands it over to the queue management module. The queue management module puts the first address of the message description information into the queue according to the queue number transmitted by the receiving module and updates the actual depth of the queue. When the actual depth of the queue reaches the first alarm depth, the message feature description information is delivered to other queues. After the actual depths of other queues reach the first alarm depth, the message feature description information is delivered to the queue again, until the actual depth of the queue reaches the second alarm depth and no longer receives the delivered message feature description information.

In a possible implementation, after performing deep parsing on the message to be processed according to the deep parsing configuration information to obtain deep parsing data, the method further includes:

Determine the hash configuration data pre-configured in the hash calculation sub-rule of the target message processing rule, the hash configuration data including the calculation hash value identifier and the hash value range; when the calculation hash value identifier is configured as the ninth identifier, calculate the target hash value according to the hash value range; determine the queue identifier pre-configured in the queue processing sub-rule of the target message processing rule; determine the target queue identifier according to the target hash value and the queue identifier; and send the deep analysis data to the target queue corresponding to the target queue identifier.

Specifically, after obtaining the deep analysis data, determine whether to update the queue to be delivered according to the hash configuration data configured in the message processing rule. If the hash value calculation identifier is configured as the hash value calculation identifier (such as configured as 1), a hash value is calculated according to the range of the HASH value range, and the hash value and the queue identifier pre-configured in the queue processing sub-rule are added to obtain a target queue identifier. Among them, the pre-configured queue identifier can be a digital number, and the target queue identifier obtained by adding the hash value and the queue identifier pre-configured in the queue processing sub-rule is also a digital number, and the corresponding queue is found according to the target queue identifier.

In a possible implementation, sending the storage address corresponding to the second message feature description information to the target queue corresponding to the target queue identifier includes: determining an actual depth of the first queue corresponding to the target queue identifier; when the actual depth of the first queue is greater than the first alarm depth of the first queue, selecting a target queue from the second queue, and the actual depth of the target queue does not exceed the first alarm depth of the target queue; sending the storage address corresponding to the second message feature description information to the target queue until the target queue identifier is reached. The actual depth of the target queue exceeds the first alarm depth. When the actual depth of the target queue exceeds the first alarm depth, the method further includes: sending the storage address corresponding to the second message feature description information to the first queue until the actual depth of the first queue is greater than the second alarm depth of the first queue.

Specifically, after obtaining the second message description information and the target queue identifier, it is first determined whether the queue corresponding to the target queue identifier is configured with a load sharing queue. If not, the physical address corresponding to the second message description information is directly stored in the queue corresponding to the target queue identifier according to the target queue identifier; if the queue is configured with a load sharing queue, that is, when the actual depth of the queue i corresponding to the target queue identifier is greater than or equal to the first alarm depth of the queue i, the storage address corresponding to the second message description information will be delivered to other queues according to the user's configuration information. This user configuration information can be configured separately. For example, several (assuming q) consecutive queues can be configured as load sharing queues with each other. In the flow-by-flow scenario (fixed into a certain queue according to message characteristics or fixed into a HASH value), a certain queue), when the queue i corresponding to the target queue identifier reaches the first alarm depth, the next adjacent queue i+1 can be preferentially selected as the queue for entry; when the i-th and i+1-th queues both reach the first alarm depth, the i+2 queue is entered, and so on, to ensure that the storage address corresponding to the same second message feature description information enters the least queue as possible; in a packet-by-packet scenario, when the queue i corresponding to the target queue identifier reaches the first alarm depth, the second message description information can be distributed to the remaining queues for processing one by one. Here, if the first alarm depth is set to 1, it means that the messages are evenly distributed to multiple queues. After multiple queues have reached the first alarm depth, the messages can still be stored in the queues according to the flow-by-flow or packet-by-packet process until the actual depth of the queue reaches the second alarm depth and no more messages are received.

In a possible implementation, there are multiple target queues, and sending at least part of the second message feature description information to the target queues includes: sending the storage address corresponding to the second message feature description information to the target queue with the highest priority in sequence according to the priority of each target queue.

It should be noted that the message processing method provided in the embodiment of the present application may be executed by a message processing device. In the embodiment of the present application, the message processing device is used as an example to execute the loading message processing method. The message processing device provided in the embodiment of the present application is described.

Fig. 8 is a schematic diagram of the structure of a message processing device according to an embodiment of the present application. As shown in Fig. 8, the message processing device 800 includes: an acquisition module 801, which is used to acquire a first message feature corresponding to a message to be processed; a determination module 802, which is used to determine a target message processing rule from pre-configured message processing rules according to the first message feature, wherein different first message features correspond to different message processing rules; and a processing module 803, which is used to process the message to be processed according to the configuration data of at least one processing sub-rule in the target message processing rule.

In the embodiment of the present application, by obtaining the first message feature corresponding to the message to be processed; determining the target message processing rule from the pre-configured message processing rules according to the first message feature, wherein different first message features correspond to different message processing rules; and processing the message to be processed according to the configuration data of at least one processing sub-rule in the target message processing rule. It is possible to flexibly process the message to be processed by using different message processing rules according to different message features, thereby using different message processing rules according to different business needs, improving the flexibility of message processing. During processing, the message can be processed according to at least one processing sub-rule in the message processing rule, further improving the flexibility of message processing.

In a possible implementation, the acquisition module 801 is further used to determine target data source information from pre-configured data source information, where the target data source information includes first message feature description information; and to obtain a first message feature corresponding to the first message feature description information from the message to be processed.

In one possible implementation, the message processing rule includes a second identifier and a second message feature, and the determination module 802 is also used to match the first identifier and the first message feature corresponding to the target data source information with the second identifier and the second message feature in each message processing rule; and determine that the message processing rule in which the first identifier matches the second identifier and the first message feature matches the second message feature is the target message processing rule.

In a possible implementation, the configuration data includes message upload configuration data, the processing sub-rule includes a data storage sub-rule, and the processing module 803 is further used to determine the message upload configuration data pre-configured in the data storage sub-rule of the target message processing rule; determine the message upload configuration data in the message upload configuration data; The buffer identifier of the buffer is used to store the message to be processed in the buffer corresponding to the buffer identifier.

In one possible implementation, the processing module 803 is also used to store the complete message corresponding to the message to be processed in the first buffer of the buffer pool when the buffer identifier is the third identifier; and to store at least one message fragment in the message to be processed in the second buffer of the buffer pool when the buffer identifier is the fourth identifier, and the first buffer and the second buffer are different.

In a possible implementation, it also includes: a configuration module, used to configure the message upload fragment in the message processing rule to obtain the message upload configuration data; the configuration includes one of the following: configuring the fourth identifier of the message upload fragment, and the offset and length of the message fragment to be uploaded; configuring the third identifier of the complete message to be uploaded.

In a possible implementation, the configuration module is also used to configure the buffer identifier in the message processing rule; when the message sending segment is configured as the third identifier, the buffer identifier is configured as the fifth identifier, and the fifth identifier corresponds to the first buffer; when the message sending segment is configured as the fourth identifier, the buffer identifier is configured as the sixth identifier, and the sixth identifier corresponds to the second buffer.

In a possible implementation, the method further includes: a division module, configured to divide the buffer pool into a first buffer and a second buffer; the first buffer is configured to store complete messages, and the second buffer is configured to store message fragments.

In a possible implementation, the configuration data includes deep parsing configuration data, the processing sub-rules include deep parsing sub-rules, and the processing module 803 is also used to determine the deep parsing configuration data pre-configured in the deep parsing sub-rules of the target processing rules, and the deep parsing configuration information includes a deep parsing identifier and deep parsing configuration information; when the deep parsing identifier is configured as the seventh identifier, deep parsing processing is performed on the message to be processed according to the deep parsing configuration information to obtain deep parsing data; the deep parsing configuration information includes at least one of the following: the message offset position and length of the custom field; the data extraction identifier of the destination media access control address; the data extraction identifier of the source media access control address; the data extraction identifier of the virtual local area network corresponding to the media access control address; the data extraction identifier of the quadruple and/or quintuple and/or septuple of the standard protocol; determine the queue identifier in the target processing rule knowledge.

In one possible implementation, when the deep analysis identifier is the eighth identifier, the processing sub-rule includes a queue processing sub-rule, the configuration data includes a queue identifier, and the processing module 803 is also used to determine the queue identifier pre-configured in the queue processing sub-rule of the target message processing rule; and send the deep analysis data to the target queue corresponding to the queue identifier.

In one possible implementation, the determination module 802 is also used to determine the hash configuration data pre-configured in the hash calculation sub-rule of the target message processing rule, the hash configuration data including a calculated hash value identifier and a hash value range; when the calculated hash value identifier is configured as the ninth identifier, the target hash value is calculated according to the hash value range; the queue identifier pre-configured in the queue processing sub-rule of the target message processing rule is determined; the target queue identifier is determined according to the target hash value and the queue identifier; and the deep analysis data is sent to the target queue corresponding to the target queue identifier.

In one possible implementation, the determination module 802 is also used to determine second message feature description information corresponding to the message to be processed, the second message feature description information including deep analysis data and configuration data of at least one processing sub-rule in the target message processing rule; sending the deep analysis data to the target queue corresponding to the target queue identifier includes: sending the storage address corresponding to the second message feature description information to the target queue corresponding to the target queue identifier.

In a possible implementation, the configuration module is also used to configure the queue; the configuration includes at least one of the following: an identifier of the queue; a first alarm depth of the queue; a second alarm depth of the queue, the second alarm depth being greater than the first alarm depth. In a possible implementation, the configuration module is also used to determine the actual depth of the first queue corresponding to the target queue identifier; when the actual depth of the first queue is greater than the first alarm depth of the first queue, select a target queue from the second queue, the actual depth of the target queue not exceeding the first alarm depth of the target queue; send the storage address corresponding to the second message feature description information to the target queue until the actual depth of the target queue exceeds the first alarm depth.

In a possible implementation, the configuration module is further configured to send the storage address corresponding to the second message feature description information to the first queue until the actual depth of the first queue is greater than the first queue. Second alarm depth.

In a possible implementation manner, the configuration module is further configured to send the storage address corresponding to the second message feature description information to the target queue with the highest priority according to the priorities of the target queues.

The message processing device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a network-side device. Exemplarily, the network-side device can be a server, a network attached storage (NAS), etc., which is not specifically limited in the embodiment of the present application.

The message processing device provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 1 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

Optionally, as shown in Figure 9, an embodiment of the present application also provides a network side device 900, including a processor 901 and a memory 902, and the memory 902 stores a program or instruction that can be executed on the processor 901. When the program or instruction is executed by the processor 901, the various steps of the above-mentioned message processing method embodiment are implemented and the same technical effect can be achieved.

An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned message processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

The processor is the processor in the terminal in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned message processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

The present application embodiment further provides a computer program/program product, which is stored in a storage medium and executed by at least one processor to implement the above The various processes of the message processing method embodiment are described in detail, and the same technical effect can be achieved. To avoid repetition, they will not be described here.

It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

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

The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims (18)

A message processing method, the method comprising: Obtaining a first message feature corresponding to the message to be processed; Determining a target message processing rule from pre-configured message processing rules according to the first message feature, wherein different first message features correspond to different message processing rules; The message to be processed is processed according to configuration data of at least one processing sub-rule in the target message processing rule. The method according to claim 1, wherein obtaining the first message feature corresponding to the message to be processed comprises: Determine target data source information from pre-configured data source information, wherein the target data source information includes first message feature description information; A first message feature corresponding to the first message feature description information is obtained from the message to be processed. The method according to claim 2, wherein the message processing rule includes a second identifier and a second message feature, and determining the target message processing rule from the preconfigured message processing rules according to the first message feature includes: Matching the first identifier and the first message feature corresponding to the target data source information with the second identifier and the second message feature in each of the message processing rules; It is determined that the first identifier matches the second identifier, and the message processing rule in which the first message feature matches the second message feature is the target message processing rule. The method according to claim 1, wherein the configuration data includes message upload configuration data, the processing sub-rule includes a data storage sub-rule, and the processing of the to-be-processed message according to the configuration data of at least one processing sub-rule in the target message processing rule includes: Determine the message upload configuration data pre-configured in the data storage sub-rule of the target message processing rule; Determine a buffer identifier in the message upload configuration data, and store the message to be processed in a buffer corresponding to the buffer identifier. The method according to claim 4, wherein the determining the buffer identifier in the message upload configuration data and storing the message to be processed in the buffer corresponding to the buffer identifier comprises: When the buffer zone identifier is the third identifier, storing the complete message corresponding to the to-be-processed message in the first buffer zone of the buffer pool; When the buffer zone identifier is the fourth identifier, at least one message fragment in the to-be-processed message is stored in a second buffer zone of the buffer pool, and the first buffer zone and the second buffer zone are different. The method according to claim 5, wherein, before determining the message upload configuration data pre-configured in the target message processing rule, the method further comprises: Configuring the message upload segment in the message processing rule to obtain the message upload configuration data; The configuration includes one of the following: Configure the fourth identifier of the message upload segment, as well as the offset and length of the message segment to be uploaded; Configure the third flag for sending complete messages. The method according to claim 6, wherein, before determining the message upload configuration data in the target message processing rule, the method further comprises: Configuring the buffer zone identifier in the message processing rule; When the message sending segment is configured as the third identifier, the identifier of the buffer is configured as a fifth identifier, and the fifth identifier corresponds to the first buffer; In a case where the message sending segment is configured as the fourth identifier, the identifier of the buffer is configured as a sixth identifier, and the sixth identifier corresponds to the second buffer. The method according to any one of claims 4 to 7, wherein, before determining the message upload configuration data in the target message processing rule, the method further comprises: Dividing the buffer pool into a first buffer zone and a second buffer zone; The first buffer is used to store complete messages, and the second buffer is used to store message fragments. The method according to any one of claims 1 to 7, wherein the configuration data includes deep parsing configuration data, the processing sub-rule includes a deep parsing sub-rule, and the processing of the to-be-processed message according to the configuration data of at least one processing sub-rule in the target message processing rule includes: Determine the deep parsing configuration data pre-configured in the deep parsing sub-rule of the target processing rule, wherein the deep parsing configuration information includes a deep parsing identifier and deep parsing configuration information; When the deep analysis flag is configured as the seventh flag, deep analysis processing is performed on the message to be processed according to the deep analysis configuration information to obtain deep analysis data; The deep analysis configuration information includes at least one of the following: The message offset position and length of the custom field; A data extraction identifier of a destination media access control address; A data extraction identifier of a source media access control address; A data extraction identifier of a virtual local area network corresponding to the media access control address; A data extraction identifier of a four-tuple and/or a five-tuple and/or a seven-tuple of a standard protocol; The queue identifier in the target processing rule. The method according to claim 9, wherein, when the deep parsing identifier is the eighth identifier, the processing sub-rule includes a queue processing sub-rule, the configuration data includes a queue identifier, and the processing of the to-be-processed message according to the configuration data of at least one processing sub-rule in the target message processing rule includes: Determine a queue identifier preconfigured in a queue processing sub-rule of the target message processing rule; The deep parsing data is sent to a target queue corresponding to the queue identifier. The method according to claim 9, wherein in the After performing deep analysis on the message to be processed according to the configuration information and obtaining deep analysis data, the method further includes: Determine the hash configuration data pre-configured in the hash calculation sub-rule of the target message processing rule, wherein the hash configuration data includes a calculation hash value identifier and a hash value range; When the calculation hash value identifier is configured as a ninth identifier, a target hash value is calculated according to the hash value range; Determine a queue identifier preconfigured in a queue processing sub-rule of the target message processing rule; Determine the target queue identifier according to the target hash value and the queue identifier; The deep parsing data is sent to a target queue corresponding to the target queue identifier. The method according to claim 11, wherein, before sending the deep parsing data to the target queue corresponding to the target queue identifier, the method further comprises: Determine second message feature description information corresponding to the message to be processed, where the second message feature description information includes the deep analysis data and configuration data of at least one processing sub-rule in the target message processing rule; Sending the deep parsing data to the target queue corresponding to the target queue identifier includes: The storage address corresponding to the second message feature description information is sent to the target queue corresponding to the target queue identifier. The method according to claim 10, wherein, before determining the queue identifier preconfigured in the queue processing sub-rule of the target message processing rule, the method further comprises: Configure the queue; The configuration includes at least one of the following: The ID of the queue; The first alarm depth of the queue; A second alarm depth of the queue, wherein the second alarm depth is greater than the first alarm depth. The method according to claim 12, wherein the second message feature is described as follows: The storage address corresponding to the information is sent to the target queue corresponding to the target queue identifier, including: Determine an actual depth of a first queue corresponding to the target queue identifier; In a case where the actual depth of the first queue is greater than the first alarm depth of the first queue, selecting a target queue from the second queue, the actual depth of the target queue not exceeding the first alarm depth of the target queue; The storage address corresponding to the second message feature description information is sent to the target queue until the actual depth of the target queue exceeds the first alarm depth. The method according to claim 14, wherein, when the actual depth of the target queue exceeds the first alarm depth, the method further comprises: The storage address corresponding to the second message feature description information is sent to the first queue until the actual depth of the first queue is greater than the second alarm depth of the first queue. The method according to claim 14, wherein there are multiple target queues, and sending the storage address corresponding to the second message feature description information to the target queue comprises: The storage address corresponding to the second message feature description information is sent to the target queue with the highest priority according to the priority of each target queue. A network side device comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method according to any one of claims 1 to 16 are implemented. A readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 16 are implemented.