WO2021180025A1

WO2021180025A1 - Message processing method and apparatus, electronic device and medium

Info

Publication number: WO2021180025A1
Application number: PCT/CN2021/079512
Authority: WO
Inventors: 郑舒力
Original assignee: 北京金山云网络技术有限公司
Priority date: 2020-03-13
Filing date: 2021-03-08
Publication date: 2021-09-16
Also published as: CN111381987A

Abstract

A message processing method and apparatus, an electronic device and a medium, which relate to the technical field of communications and can simplify a method for message processing. The method comprises: monitoring whether a message main queue of a remote dictionary server (Redis) comprises a message to be consumed (201), wherein the message to be consumed is a message written into the message main queue by a message producer; then, when it is detected that the message main queue comprises the message to be consumed, acquiring the message to be consumed, and transferring the message to be consumed to a message backup queue (202); and processing the message to be consumed (203).

Description

Message processing method, device, electronic equipment and medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on March 13, 2020 with the application number 202010174823.1 and the invention title is "a message processing method, device, electronic equipment and medium", the entire content of which is incorporated by reference In this application.

Technical field

This application relates to the field of communication technology, and in particular to a message processing method, device, electronic equipment, and medium.

Background technique

With the development of the Internet and information technology, there are a large number of messages in the network. In some special scenarios, it is necessary to ensure that the messages generated by the producers will not be omitted when processed by the consumers. Among them, the producer refers to the source of the message, which is used to write the produced message into the message system; the consumer is used to obtain and process the message from the message system. For example, in the online shopping scenario, in order to ensure the user's successful shopping, the order message generated by the user through the terminal (producer) is recorded in the message system, and each order message in the message system needs to be processed by the server (consumer).

In related technologies, the message system can be RocketMQ or Kafka. Taking Kafka as an example, the method of processing each message in the message system is: after the producer writes the produced message to the Kafka message queue, the consumer first reads it from the Kafka message queue When getting messages from the Kafka message queue, the sequence number of the message that first enters the message queue and the preset number of messages are obtained from the Kafka message queue. After processing the obtained message, the consumer updates the obtained sequence number (updated sequence number = obtained sequence number + preset number), and then continues to obtain the message corresponding to the updated sequence number from the Kafka message queue.

Because RocketMQ and Kafka are distributed messaging systems, they are composed of multiple components. For example, Kafka includes components such as controller, coordinator, log management, and copy manager. Because RocketMQ and Kafka include many components, the deployment and operation of RocketMQ and Kafka are complicated, and the development workload for terminals used by producers and consumers is relatively large, which leads to more complicated methods for processing messages.

Summary of the invention

The purpose of the embodiments of the present application is to provide a message processing method, device, electronic device, and medium, so as to implement a simplified method for processing messages. The specific technical solutions are as follows:

In the first aspect, an embodiment of the present application provides a message processing method. The method includes: monitoring whether a message to be consumed is included in the message main queue of the remote dictionary service Redis, and the message to be consumed is a message written by the message producer to the message main queue ; When it is monitored that the message to be consumed is included in the main message queue, the message to be consumed is obtained, and the message to be consumed is transferred to the message backup queue; the message to be consumed is processed.

In a second aspect, an embodiment of the present application provides a message processing device, which includes: a monitoring module configured to monitor whether messages to be consumed are included in the main message queue of the remote dictionary service Redis, and the messages to be consumed are written by the message producer Messages in the main message queue; acquisition module, used to obtain the messages to be consumed when the listening module monitors that the message main queue includes messages to be consumed, and transfer the messages to be consumed to the message backup queue; processing module, used to process the acquisition The message to be consumed obtained by the module.

In the third aspect, an embodiment of the present application provides an electronic device, including a processor, a communication interface, a memory, and a communication bus. The processor, the communication interface, and the memory communicate with each other through the communication bus; the memory is used for storing Computer program; processor, used to implement the steps of any of the above message processing methods when executing the program stored on the memory.

In a fourth aspect, the embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any of the above message processing methods are implemented.

In a fifth aspect, the embodiments of the present application also provide a computer program product containing instructions, which when run on a computer, cause the computer to execute any of the above message processing methods.

In a sixth aspect, the embodiments of the present application provide a computer program, which when the computer program runs on a computer, causes the computer to execute the steps of the message processing method provided in the embodiments of the present application.

The beneficial effects of the embodiments of the application: since the message producer can write the message to be consumed into the message main queue in Redis, the consumer can obtain the message to be consumed from Redis and transfer the message to be consumed to the message backup queue of Redis , And then process the messages to be consumed. Since the message to be consumed is transferred to the message backup queue at the same time as it is obtained, even if the consumer does not process the message to be consumed successfully, the message to be consumed can still be obtained from the message backup queue and processed again, so the message producer generates The omissions will not be dealt with when each message is to be consumed. And because Redis is an in-memory database, compared to RocketMQ and Kafka and other messaging systems that include multiple components, Redis has a simple structure, convenient deployment, operation and maintenance, and simplifies the method of processing messages.

Of course, implementing any product or method of the present application does not necessarily need to achieve all the advantages described above at the same time.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application or related technologies, the following will briefly introduce the drawings that need to be used in the description of the embodiments or related technologies. Obviously, the drawings in the following description are merely present For some of the embodiments of the application, for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work.

FIG. 1 is a schematic structural diagram of a message processing system provided by an embodiment of this application;

FIG. 2 is a flowchart of a message processing method provided by an embodiment of the application;

FIG. 3 is a flowchart of another message processing method provided by an embodiment of the application;

FIG. 4 is a schematic structural diagram of a message processing apparatus provided by an embodiment of the application;

FIG. 5 is a schematic structural diagram of an electronic device provided by an embodiment of the application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

Since the method of using RocketMQ and Kafka to implement message processing in the related technology is relatively complicated, the message processing method in the related technology is not applicable when the amount of processed messages is small. In order to provide a lighter and simpler message processing method, an embodiment of the present application provides a message processing method, which will be described in detail below.

In the embodiments of the present application, the device that generates the message is called the message producer, and the device that processes the message is called the message consumer. The message producer can be a terminal or server, and the message consumer can also be a terminal or server. The terminal can be a mobile phone, a tablet computer, a computer, and other electronic devices. The embodiment of the present application does not specifically limit the specific equipment corresponding to the message producer and the message consumer.

The embodiment of the present application provides a message processing system. As shown in FIG. 1, the system includes: a message producer 101, a message consumer 102, and a database 103. Among them, the message producer 101 and the message consumer 102 in FIG. 1 both take a server as an example.

The message producer 101 is set to produce messages, and writes the produced messages into the database 103.

The message consumer 102 is set to read and process messages from the database 103.

The database 103 is set up to store messages. Among them, the database can be a remote dictionary service (Redis).

The Redis database may be deployed in a Redis server. The Redis server in the embodiment of the present application includes a main Redis server and a backup Redis server corresponding to the main Redis server. The main Redis server includes the Redis message main queue, the backup Redis server includes the Redis message backup queue, and the Redis message backup queue is used to back up messages to be consumed in the Redis message main queue.

The number of Redis servers in the embodiment of the present application can be set according to actual needs. Each master Redis server corresponds to at least one slave Redis server, which is equivalent to one Redis message master queue corresponding to at least one Redis message backup queue.

In the embodiment of the present application, the message main queue of Redis is referred to as the message main queue for short, and the message backup queue of Redis is referred to as the message backup queue for short.

In the message processing system shown in FIG. 1, the number of devices in the message processing system is only an example provided in the embodiment of the present application, and the embodiment of the present application does not specifically limit the number of devices in the message processing system.

Referring to FIG. 2, an embodiment of the present application provides a message processing method, which can be applied to the message consumer of the message processing system shown in FIG. 1, and the method includes the following steps.

Step 201: Monitor whether the message to be consumed is included in the message main queue of Redis.

Among them, the message to be consumed is the message written by the message producer into the main message queue.

In an implementation manner, the message consumer can monitor whether the message to be consumed is included in the message main queue of Redis through the blocking command (BRPOPLPUSH).

The BRPOPLPUSH command is a blocking command. When the main message queue monitored by the BRPOPLPUSH command does not include messages to be consumed, the BRPOPLPUSH command is in a waiting state until the main queue includes messages to be consumed, and the messages to be consumed are obtained from the main queue.

In the embodiment of the present application, the message producer can write a batch of produced messages into the message main queue of Redis each time through a push command (LPUSH). When this batch of messages is successfully written to the main message queue, the message producer will receive a return message indicating that the batch of messages was successfully written. If the message producer does not receive the return message within the preset period of time when the message is written to the main message queue, the batch of messages can be rewritten into the main message queue.

In an implementation of the embodiment of the present application, Redis in the embodiment of the present application can enable Append Only File (AOF) persistence, so that the data in the message main queue and message backup queue of Redis can be written to disk In, the integrity of the message is guaranteed.

Step 202: When it is monitored that the message to be consumed is included in the main message queue, the message to be consumed is obtained, and the message to be consumed is transferred to the message backup queue.

In one embodiment, the message consumer can start multiple threads, while obtaining the message to be consumed from the main message queue through the BRPOPLPUSH command, delete the message to be consumed from the main message queue, and insert the message to be consumed into the message backup In the queue.

Among them, the operation of deleting the message to be consumed from the main message queue and inserting it into the message backup queue is atomic. Atomicity (Atomicity) refers to the indivisibility of a transaction, all operations of a transaction are executed without interruption, or an operation is not executed. Applied in the embodiments of this application, the above-mentioned atomicity means that the operation process of deleting messages to be consumed from the main message queue and inserting them into the message backup queue cannot be interrupted, and there will be no interruption of only messages to be consumed from the main message queue. Delete from the column, or just insert the message to be consumed into the message backup queue.

If the message to be consumed is deleted from the main message queue and the message to be consumed is not inserted into the backup message queue, the message to be consumed is not stored in Redis at this time. When the message consumer fails to process the message to be consumed, the message to be consumed cannot be obtained again, so that the message to be consumed is not successfully processed.

However, in the embodiment of the present application, the operation of transferring the message to be consumed to the message backup queue is atomic, which reduces the occurrence of the above situation and reduces the omission of the message to be consumed in the message processing process.

Step 203: Process the message to be consumed.

The technical solution provided by the embodiments of the present application brings at least the following beneficial effects: since the message producer can write the message to be consumed into the message main queue in Redis, the consumer can obtain the message to be consumed from Redis and transfer the message to be consumed Transfer to the message backup queue of Redis, and then process the messages to be consumed. Since the message to be consumed is transferred to the message backup queue at the same time as it is obtained, even if the consumer does not process the message to be consumed successfully, the message to be consumed can still be obtained from the message backup queue and processed again, so the message producer generates The omissions will not be dealt with when each message is to be consumed. And because Redis is an in-memory database, compared to RocketMQ and Kafka and other messaging systems that include multiple components, Redis has a simple structure, convenient deployment, operation and maintenance, and simplifies the method of processing messages.

In the embodiment of this application, there may be one or more message main queues and message backup queues in Redis, and message consumers can monitor one of the message main queues by opening multiple threads, or monitor multiple message main queues separately, The messages to be consumed in each message main queue are transferred to the corresponding message backup queue. In an implementation manner, the number of message main queues may be the same as the number of message backup queues, and there is a one-to-one correspondence. The message consumer monitors multiple message main queues at the same time, and when a message to be consumed is monitored from one message main queue, the message to be consumed is transferred to the message backup queue corresponding to the message main queue.

The message main queue and message backup queue may store messages in the form of key-value, where key is the identifier of the message queue, and value is the identifier of the message. One key can correspond to multiple values.

In one embodiment, the main message queue and the message backup queue may be monitored by multiple message consumers.

In another embodiment of the present application, after the above step 203, if the message to be consumed is processed successfully, the message consumer can delete the message to be consumed in the message backup queue.

In an implementation manner, the message to be consumed in the message backup queue can be deleted through a delete command (LREM). The LREM command is a Redis command used to remove elements in the list. In the embodiment of the present application, the LREM command is used to delete backup messages in the message backup queue.

If the processing of the message to be consumed fails, the message consumer keeps the message to be consumed in the message backup queue.

The technical solution of the embodiment of the present application can also bring the following beneficial effects: the message consumer will delete the message to be consumed in the message backup queue only when the message to be consumed is successfully processed. If the processing of the message to be consumed fails, the message to be consumed can also be acquired and processed again until the processing of the message to be consumed is successful, so the embodiment of the present application reduces the omission of the message to be consumed in the message processing process.

In addition, since the message consumer obtains the message to be consumed from the main message queue at the same time, deletes the message to be consumed from the message main queue, avoiding the situation that other message consumers repeatedly obtain and process the message to be consumed from the main message queue, and reduce The situation where the same message to be consumed is processed repeatedly.

In another embodiment of the present application, after the message consumer obtains the message to be consumed from the main message queue and transfers the message to be consumed to the message backup queue as a backup message, if the processing of the message to be consumed fails, the message to be consumed The backup messages are kept in the message backup queue, so the message backup queue may include backup messages of messages to be consumed that have failed to be processed. Referring to Figure 3, in order to avoid omissions in processing messages to be consumed, message consumers can also process backup messages in the message backup queue, including the following steps:

Step 301: Determine whether a backup message is included in the message backup queue every preset time duration.

In an implementation manner, the preset duration of monitoring blocking can be set in the BRPOPLPUSH command of the monitoring message main queue, and the message consumer can monitor whether the backup message is included in the message backup queue by using the BRPOPLPUSH command to monitor whether the backup message is included in the message backup queue at each interval preset duration.

For example, the preset duration may be a random value within a preset range, and the preset range may be 5-10 minutes.

Step 302: If a backup message is included in the message backup queue, obtain the backup message.

In an implementation manner, the message consumer can use the LINDEX command to obtain the backup message that enters the message backup queue first among the backup messages included in the message backup queue according to the order in which each backup message enters the message backup queue. Wherein, the LINDEX command is a Redis command used to obtain elements in the list. In the embodiment of the present application, the LINDEX command is used to obtain the backup message that first enters the backup queue.

Step 303: Process the backup message.

Among them, the message consumer can process the obtained backup message.

Step 304: If the backup message is processed successfully, delete the backup message from the message backup queue.

In an implementation manner, the message consumer can delete the backup message in the message backup queue through the LREM command.

In this step, if the backup message is successfully processed by the message consumer, the message consumer can delete the backup message from the message backup queue. If the backup message is not processed successfully, the message consumer does not delete the backup message from the backup queue.

The technical solution provided by the embodiments of the present application can also bring the following beneficial effects: because the message consumer can obtain and process the backup message from the message backup queue every interval preset time, and the message backup can be deleted when the backup message is processed successfully. The backup messages in the queue reduce the omission of messages during message processing.

In an implementation manner, the message backup queue in the embodiment of the present application may further include the timestamp of each backup message. Among them, the time stamp is the time when the backup message enters the message backup queue. In the above step 303, before processing the backup message, the message consumer can also determine whether the acquired backup message needs to be processed, including the following steps:

Step 1: Obtain the timestamp of the backup message.

Step 2: If the time difference between the current time and the time stamp of the backup message is greater than the preset time difference, execute the step of processing the backup message.

It is understandable that if the time difference between the current time and the timestamp of the backup message is greater than the preset time difference, it means that the backup message has been in the message backup queue for a long time and has not been deleted, and the processing of the backup message is more likely to fail. , Needs to be processed again.

In another embodiment, if the time difference between the current time and the time stamp of the backup message is not greater than the preset time difference, the acquired backup message is not processed.

Understandably, if the time difference between the current time and the timestamp of the backup message is not greater than the preset time difference, it means that the backup message has entered the message backup queue for a short time and has not been deleted, and the backup message may be being processed by the message consumer , So you don’t need to process the backup message.

For example, the preset time difference is ten minutes.

The technical solution provided by the embodiments of this application can also bring about the following beneficial effects: since it takes a certain time for the message consumer to process the message, and the message consumer will delete the backup message in the backup message queue after the processing is successful, the implementation of this application For example, it can process backup messages that take a long time to enter the message backup queue, reducing the number of repeated processing of messages.

Corresponding to the foregoing method embodiment, as shown in FIG. 4, an embodiment of the present application provides a message processing device, which includes: a monitoring module 401, an acquisition module 402, and a processing module 403;

The monitoring module 401 is configured to monitor whether messages to be consumed are included in the main message queue of the remote dictionary service Redis, and the messages to be consumed are messages written by the message producer to the main message queue;

The obtaining module 402 is configured to obtain the message to be consumed when the monitoring module 701 detects that the message to be consumed is included in the main message queue, and transfer the message to be consumed to the message backup queue;

The processing module 403 is configured to process the message to be consumed acquired by the acquiring module 402.

In another embodiment of the present application, the device may further include: a deletion module;

The delete module is set to delete the message to be consumed in the message backup queue if the message to be consumed is processed successfully after processing the message to be consumed.

In another embodiment of the present application, the device may further include: a determination module and a deletion module;

The determining module is set to the preset duration of each interval to determine whether the backup message is included in the message backup queue;

The obtaining module 402 is further configured to obtain the backup message if the backup message is included in the message backup queue;

The processing module 403 is also set to process backup messages;

The delete module is set to delete the backup message from the message backup queue if the backup message is processed successfully.

In another embodiment of the present application, the obtaining module 402 may be configured as:

According to the sequence in which each backup message enters the message backup queue, the backup message that enters the message backup queue first among the backup messages included in the message backup queue is obtained.

In another embodiment of the present application, the message backup queue further includes a timestamp of each backup message, and the timestamp is the time when the backup message enters the message backup queue; the device may further include: a calling module;

The obtaining module is also set to obtain the timestamp of the backup message before processing the backup message;

The calling module is set to call the processing module to execute the step of processing the backup message when the time difference between the current time and the time stamp of the backup message is greater than the preset time difference.

The embodiment of the present application also provides an electronic device. As shown in FIG. Complete the communication between each other,

The memory 503 is set to store computer programs;

The processor 501 is configured to implement the method steps in the foregoing method embodiment when it is configured to execute the program stored in the memory 503.

The communication bus mentioned in the above electronic device may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

The communication interface is used for communication between the above-mentioned electronic device and other devices.

The memory may include random access memory (Random Access Memory, RAM), and may also include non-volatile memory (Non-Volatile Memory, NVM), such as at least one disk storage. Optionally, the memory may also be at least one storage device located far away from the foregoing processor.

The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (Network Processor, NP), etc.; it can also be a digital signal processor (Digital Signal Processing, DSP), a dedicated integrated Circuit (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

In yet another embodiment provided in this application, a computer-readable storage medium is also provided. The computer-readable storage medium stores a computer program, and the computer program implements any of the above message processing methods when executed by a processor. A step of.

In another embodiment provided by the present application, a computer program product containing instructions is also provided, which when running on a computer, causes the computer to execute any message processing method in the above-mentioned embodiments.

In another embodiment provided in this application, a computer program is also provided, which when running on a computer, causes the computer to execute any message processing method in the above-mentioned embodiments.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply one of these entities or operations. There is any such actual relationship or order between. Moreover, the terms "include", "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 not only includes those elements, but also includes those that are not explicitly listed Other elements of, or also include elements inherent to this process, method, article or equipment. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, article, or equipment that includes the element.

The various embodiments in this specification are described in a related manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.

The foregoing descriptions are only preferred embodiments of the present application, and are not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application are all included in the protection scope of this application.

Industrial applicability

Based on the message processing method, device, electronic device, and medium provided by the embodiments of the present application, the message can use the message main queue and message backup queue in Redis as message middleware, which can simplify the difficulty of deploying message middleware and simplify the process of message processing. method.

Claims

A message processing method, the method includes:

Monitoring whether the message main queue of the remote dictionary service Redis includes a message to be consumed, and the message to be consumed is a message written by a message producer to the message main queue;

When it is monitored that the message to be consumed is included in the main message queue, acquiring the message to be consumed, and transferring the message to be consumed to the message backup queue;

Process the message to be consumed.
The method according to claim 1, wherein, after the processing the message to be consumed, the method further comprises:

If the processing of the message to be consumed is successful, the message to be consumed in the message backup queue is deleted.
The method according to claim 1, wherein the method further comprises:

Each interval preset time length, determine whether the message backup queue includes a backup message;

If the message backup queue includes a backup message, acquiring the backup message;

Processing the backup message;

If the processing of the backup message is successful, the backup message is deleted from the message backup queue.
The method according to claim 3, wherein said obtaining said backup message comprises:

According to the sequence in which each backup message enters the message backup queue, among the backup messages included in the message backup queue, the backup message that first enters the message backup queue is obtained.
The method according to claim 3 or 4, wherein the message backup queue further includes a time stamp of each backup message, and the time stamp is the time when the backup message enters the message backup queue; Before backing up the message, the method further includes:

Obtaining the timestamp of the backup message;

If the time difference between the current time and the time stamp of the backup message is greater than the preset time difference, the step of processing the backup message is executed.
A message processing device, the device includes:

A monitoring module, configured to monitor whether messages to be consumed are included in the message main queue of the remote dictionary service Redis, and the messages to be consumed are messages written into the message main queue by a message producer;

An acquiring module, configured to acquire the message to be consumed when the monitoring module detects that the message to be consumed is included in the main message queue, and transfer the message to be consumed to the message backup queue;

The processing module is configured to process the message to be consumed acquired by the acquisition module.
The device according to claim 6, wherein the device further comprises: a deletion module;

The deleting module is configured to delete the message to be consumed in the message backup queue if the message to be consumed is successfully processed after the processing of the message to be consumed.
The device according to claim 6, wherein the device further comprises: a determination module and a deletion module;

The determining module is set to a preset duration of each interval, and determines whether a backup message is included in the message backup queue;

The acquiring module is further configured to acquire the backup message if the backup message is included in the message backup queue;

The processing module is further configured to process the backup message;

The deletion module is configured to delete the backup message from the message backup queue if the processing of the backup message is successful.
The device according to claim 8, wherein the acquiring module is configured to:

According to the sequence in which each backup message enters the message backup queue, among the backup messages included in the message backup queue, the backup message that first enters the message backup queue is obtained.
The device according to claim 8 or 9, wherein the message backup queue further includes a timestamp of each backup message, and the timestamp is the time when the backup message enters the message backup queue; the device further comprises: Call module

The acquiring module is further configured to acquire the time stamp of the backup message before the processing of the backup message;

The calling module is configured to call the processing module to execute the step of processing the backup message when the time difference between the current moment and the time stamp of the backup message is greater than a preset time difference.
An electronic device, including a processor, a communication interface, a memory, and a communication bus. The processor, the communication interface, and the memory communicate with each other through the communication bus;

Memory, set to store computer programs;

The processor is configured to implement the method steps described in any one of claims 1-5 when it is configured to execute the program stored in the memory.
A computer-readable storage medium in which a computer program is stored, and when the computer program is executed by a processor, the method steps according to any one of claims 1 to 5 are realized.
A computer program product containing instructions, which when running on a computer, causes the computer to execute the method steps of any one of claims 1-5.
A computer program that, when run on a computer, causes the computer to execute the method steps described in any one of claims 1-5.