CN118555263A - Message processing system and method, message updating method and subscription request processing method - Google Patents

Abstract

The embodiments of this specification provide a message processing system and method, a message update method, and a subscription request processing method. The message processing system includes a sender, a server, and multiple subscribers; the sender determines the message format of the initial field message and the associated server, converts the initial field message into a target field message according to the message format, and sends the target field message to the server; the server updates the local field message to a global field message based on the target field message; when receiving a subscription request submitted by a target subscriber among multiple subscribers, the subscription request is parsed, and subscription information and field configuration rules are determined according to the parsing result; field information is extracted from the global field message according to the subscription information; a target message is generated based on the field information and field configuration rules, and the target message is sent to the target subscriber. The sender and the subscriber are decoupled, and the message format is unified. The message processing pressure on the sender is reduced.

Description

Message processing system and method, message updating method and subscription request processing method

Technical Field

The embodiments of the present specification relate to the field of computer technology, and in particular, to a message processing system and method, a message updating method, and a subscription request processing method.

Background Art

In the message publishing and subscription scenario, the subscriber usually submits a subscription request to the sender, and the sender directly processes the received subscription request. In the MQ-based message communication mode, the message sender needs to construct and send messages of different formats for different subscribers. If subscriber A needs three fields in the message: ID, name, and time, and subscriber B needs three fields: ID, description, and tag. The sender needs to construct and send messages of these two formats respectively. This greatly increases the complexity of message construction on the sender. When a new subscriber joins, the sender needs to add a new set of message construction and sending processes. With the increase in subscribers, the types of messages that the sender needs to construct and send expand rapidly, duplication of work increases, and the message processing pressure on the sender increases. Therefore, a more effective message processing system is urgently needed to solve the above problems.

Summary of the invention

In view of this, an embodiment of this specification provides a message processing system. One or more embodiments of this specification also relate to a message processing method, a message processing device, a message update method, a subscription request processing method, a computing device, a computer-readable storage medium and a computer program product to solve the technical defects existing in the prior art.

According to a first aspect of an embodiment of this specification, a message processing system is provided, including a sending end, a service end, and a plurality of subscribers;

The sending end is used to determine the message format of the initial field message and the associated server, convert the initial field message into a target field message according to the message format, and send the target field message to the server;

The server is used to update the local field message to a global field message based on the target field message; when receiving a subscription request submitted by a target subscriber among multiple subscribers, parse the subscription request, and determine the subscription information and field configuration rules according to the parsing result; extract field information from the global field message according to the subscription information; generate a target message based on the field information and the field configuration rules, and send the target message to the target subscriber.

Optionally, the sending end is further used to, upon receiving a message to be updated for the target field message, convert the message to be updated into an update message according to the message format, and send the update message to the server.

Optionally, the server is used to add the target field message to the message set where the local field message is located, and determine the global field message stored in the message set according to the adding result.

Optionally, the server is used to determine at least one subscription field contained in the subscription information; call a message splitter to split the global field message based on the at least one subscription field, and determine the target field information corresponding to the at least one subscription field according to the splitting result; and the field information is composed of the target field information corresponding to the at least one subscription field.

Optionally, the server is used to determine in the field information subscription field information corresponding to at least one subscription field contained in the subscription information, and combine the at least one subscription field and the subscription field information corresponding to the at least one subscription field according to the field configuration rule to generate the target message.

Optionally, the server is used to call a parser to parse the field configuration rules, determine a subscription relationship model containing the topic information based on the parsing results, and combine the at least one subscription field and the subscription field information corresponding to the at least one subscription field based on the subscription relationship model to generate the target message.

Optionally, the server is further configured to determine the target subscriber according to the subscriber information carried in the subscription request, and send the target message to the target subscriber.

According to a second aspect of an embodiment of this specification, a message processing method is provided, which is applied to a server, wherein the server associates a message format, including:

Receiving a target field message sent by a sending end, wherein the target field message is determined by converting an initial field message according to the message format;

updating the local field message to a global field message based on the target field message;

When receiving a subscription request submitted by a target subscriber among multiple subscribers, parsing the subscription request, and determining subscription information and field configuration rules according to the parsing result;

extracting field information from the global field message according to the subscription information;

A target message is generated based on the field information and the field configuration rule, and the target message is sent to the target subscriber.

According to a third aspect of an embodiment of this specification, a message processing device is provided, which is applied to a server, wherein the server associates a message format, including:

A receiving module is configured to receive a target field message sent by a sending end, wherein the target field message is determined by converting the initial field message according to the message format;

an updating module, configured to update the local field message to a global field message based on the target field message;

A parsing module is configured to parse the subscription request submitted by a target subscriber among multiple subscribers when receiving the subscription request, and determine the subscription information and field configuration rules according to the parsing result;

An extraction module, configured to extract field information from the global field message according to the subscription information;

A generating module is configured to generate a target message based on the field information and the field configuration rule, and send the target message to the target subscriber.

According to a fourth aspect of an embodiment of this specification, a message updating method is provided, which is applied to a server, wherein the server associates a message format, including:

Receiving a target field message sent by a sending end, wherein the target field message is determined by converting an initial field message according to the message format;

The local field message is updated to a global field message based on the target field message, wherein the global field message is used to generate a target message corresponding to a subscription request associated with a target subscriber.

According to a fifth aspect of the embodiments of this specification, a message updating device is provided, which is applied to a server, wherein the server associates a message format, including:

A receiving module is configured to receive a target field message sent by a sending end, wherein the target field message is determined by converting the initial field message according to the message format;

The generating module is configured to update the local field message into a global field message based on the target field message, wherein the global field message is used to generate a target message corresponding to a subscription request associated with a target subscriber.

According to a sixth aspect of an embodiment of this specification, a subscription request processing method is provided, which is applied to a server, including:

Receive the subscription request submitted by the target subscriber;

Parsing the subscription request, and determining subscription information and field configuration rules according to the parsing result;

Extracting field information from a global field message according to the subscription information, wherein the global field message is determined based on a field message sent by a sending end;

A target message is generated based on the field information and the field configuration rule, and the target message is sent to the target subscriber.

According to a seventh aspect of an embodiment of this specification, a subscription request processing device is provided, which is applied to a server, including:

A receiving module, configured to receive a subscription request submitted by a target subscriber;

A parsing module, configured to parse the subscription request and determine subscription information and field configuration rules according to the parsing result;

an extraction module, configured to extract field information from a global field message according to the subscription information, wherein the global field message is determined based on a field message sent by a sending end;

A generating module is configured to generate a target message based on the field information and the field configuration rule, and send the target message to the target subscriber.

According to an eighth aspect of the embodiments of this specification, a computing device is provided, including:

Memory and processor;

The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the above method are implemented.

According to a ninth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores computer-executable instructions, and the instructions implement the steps of the above method when executed by a processor.

According to the tenth aspect of the embodiments of this specification, a computer program product is provided, including a computer program or instructions, which implement the steps of the above method when executed by a processor.

The message processing system provided by one embodiment of the present specification includes a sender, a server, and multiple subscribers. The sender determines the message format of the initial field message and the associated server, converts the initial field message into a target field message according to the message format, and sends the target field message to the server. The server updates the local field message to a global field message based on the target field message. In the case of receiving a subscription request submitted by a target subscriber among multiple subscribers, the server parses the subscription request and determines the subscription information and field configuration rules according to the parsing result. The field information is extracted from the global field message according to the subscription information. The target message is generated based on the field information and the field configuration rules, and the target message is sent to the target subscriber. The sender only needs to send a target field message that conforms to the message format to the server, and the server receives the subscription request of the subscriber instead of the sender and processes the subscription request. The decoupling of the sender and the subscriber is achieved, and the message format is unified. The redundant sending of the sender's message is avoided, the message processing pressure of the sender is reduced, and the complexity of the custom message required for the server to build the subscriber is reduced.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a message processing system provided by an embodiment of the present specification;

FIG2 is a structural diagram of a message processing system provided by an embodiment of the present specification;

FIG3 is a schematic diagram of message subscription of a message processing system provided by an embodiment of the present specification;

FIG4 is a flow chart of a processing process of a message processing system provided by an embodiment of the present specification;

FIG5 is a flow chart of a message processing method provided by an embodiment of the present specification;

FIG6 is a schematic diagram of the structure of a message processing device provided by an embodiment of this specification;

FIG7 is a flow chart of a message updating method provided by an embodiment of this specification;

FIG8 is a schematic diagram of the structure of a message updating device provided by an embodiment of this specification;

FIG9 is a flowchart of a subscription request processing method provided by an embodiment of the present specification;

FIG10 is a schematic diagram of the structure of a subscription request processing device provided by an embodiment of the present specification;

FIG. 11 is a structural block diagram of a computing device provided in one embodiment of the present specification.

DETAILED DESCRIPTION

Many specific details are described in the following description to facilitate a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of this specification, so this specification is not limited to the specific implementation disclosed below.

The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and/or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

In addition, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

First, the terms involved in one or more embodiments of this specification are explained.

Pulsar: A high-performance, scalable distributed messaging system that provides a publish/subscribe model to handle large-scale message streams. Pulsar is designed to provide a high-throughput, low-latency, persistent storage, and high-availability messaging platform.

MQ communication: Message Queue communication is a method of inter-process communication in a distributed system. Message queues allow asynchronous communication between processes through messages, where messages are stored in a queue until they are consumed by the recipient.

FIG1 shows a schematic diagram of a message processing system provided according to an embodiment of the present specification, wherein the message processing system includes a sending end, a server end, and multiple subscribers. The sending end determines the message format of the initial field message and the associated server end, and the message format is a unified message format between the sending end and the server end. The initial field message is converted into a target field message according to the message format, and the target field message is sent to the server end. After the server end receives the target field message, since the server end stores the local field message, the local field message can be updated based on the target field message, and the target field message is added to the storage location where the local field message is located to obtain a global field message. When receiving a subscription request submitted by a target subscriber end among multiple subscriber ends, the server end parses the subscription request and determines the subscription information and field configuration rules based on the parsing results. Field information is extracted from the global field message based on the subscription information. A target message is generated based on the field information and the field configuration rules, and the target message is sent to the target subscriber end.

The sender only needs to send a target field message that conforms to the message format to the server. The server receives the subscription request from the subscriber on behalf of the sender and processes the subscription request. This achieves the decoupling of the sender and the subscriber and unifies the message format. It avoids redundant sending of messages on the sender, reduces the message processing pressure on the sender, and reduces the complexity of the server building the customized messages required for the subscriber.

In this specification, a message processing method is provided. This specification also involves a message processing method, a message processing device, a message update method, a subscription request processing method, a computing device, a computer-readable storage medium and a computer program product, which are described in detail one by one in the following embodiments.

Referring to FIG. 2 , FIG. 2 shows a structural diagram of a message processing system provided according to an embodiment of the present specification, wherein the message processing system 200 includes a sending end 210, a server end 220, and multiple subscribers 230. The sending end 210 is used to determine the message format of the initial field message and the associated server end 220, convert the initial field message into a target field message according to the message format, and send the target field message to the server end 220; the server end 220 is used to update the local field message to a global field message based on the target field message; when receiving a subscription request submitted by a target subscriber among multiple subscribers 230, the subscription request is parsed, and subscription information and field configuration rules are determined according to the parsing result; field information is extracted from the global field message according to the subscription information; a target message is generated based on the field information and the field configuration rules, and the target message is sent to the target subscriber.

Specifically, the message processing system 200 includes a sender 210, a server 220 and multiple subscribers 230. The sender 210 can be a message holder in a message subscription scenario; the subscriber refers to a message demander who has a message subscription demand; the server 220 can be regarded as a medium between the sender 210 and the subscriber. When the server 220 is connected to the sender 210, it is used to receive the field message sent by the sender 210; when the server 220 is connected to the subscriber, it is used to receive the subscription request submitted by the subscriber and process the subscription request. The existence of the server 220 can decouple the sender 210 and the subscriber. The server 220 receives and processes the subscription request of the subscriber instead of the sender 210. Both the sender 210 and the server 220 store messages according to the message format. The initial field message refers to the field message that has not been formatted and received by the sending end 210; the message format can be the format of the message storage dimension, such as storing in the format of key-value pairs, or the format of the field editing dimension, such as the field name is in English and the field content is added in brackets (label). Correspondingly, the target field message is the initial field message after format conversion according to the message format.

The local field message refers to the field message stored by the server 220, and the global field message is the field message obtained after the local field message is updated based on the target field message. The subscription request refers to the computer instruction sent by the subscriber to the server 220 for subscribing to some or all fields in the global field message stored by the server 220. The subscription information is the description information of the subscription requirements of the subscriber, and the subscription information may include the field information subscribed by the subscriber. The field configuration rule is the field message combination or arrangement rule corresponding to the subscriber. Among multiple subscribers 230, the field configuration rules of each subscriber may be different. The field information may be the field value corresponding to the field in the global field message. The target message refers to the message that complies with the field configuration rule. The target message corresponds to the subscription request submitted by the subscriber and is the feedback to the subscription request. The target message contains the field information of at least one field required by the subscriber, that is, the field and the field value corresponding to the field.

Based on this, the message processing system includes a sending end 210, a server end 220 and multiple subscribers 230. The sending end 210 determines the message format of the initial field message and the associated server end 220, and the message format is a unified message format between the sending end 210 and the server end 220. The initial field message is converted into a target field message according to the message format, and the target field message is sent to the server end 220 after the format of the initial field message is unified. After the server end 220 receives the target field message, since the server end 220 stores the local field message, the local field message can be updated based on the target field message, and the target field message is added to the storage location where the local field message is located to obtain the global field message. In the case of receiving a subscription request submitted by a target subscriber among multiple subscribers 230, the server end 220 parses the subscription request and determines the subscription information and field configuration rules according to the parsing result. The field information is extracted from the global field message according to the subscription information. The target message is generated based on the field information and the field configuration rules, and the target message is sent to the target subscriber.

In practical applications, the message processing system can be applied to message subscription scenarios in various fields. The message processing system can be applied to stock quote subscriptions in the financial transaction field, order status subscriptions and inventory message subscriptions in the e-commerce field, dynamic information subscriptions in social media, news and program subscriptions in the news and media field, and flight information and logistics information subscriptions in logistics and transportation.

For example, in the case where the message processing system is applied to the news field, the subscriber can be a news subscriber. The sender and the server constitute a news subscription platform. When the sender receives the initial field messages such as the title, summary, date, and category of the news, the message format associated with the server is determined, and the initial field messages such as the title, summary, date, and category of the news are converted into target field messages corresponding to the message format, and the target field messages are sent to the server. The server updates the stored local field messages such as the introduction, conclusion, background, and author based on the target field message, and the global field message is composed of the field messages such as the title, summary, date, category, introduction, conclusion, background, and author of the news. After receiving the subscription request submitted by the subscriber 1, the subscription request is parsed to obtain the subscription information composed of the title, summary, and date of the news, as well as the field configuration rules representing the message configuration rules. The global field message is split based on the subscription information, and the field values corresponding to the title, summary, and date are extracted from the global field message to form the field information, and the target message is generated according to the field configuration rules and sent to the subscriber 1.

In summary, the sender only needs to send a target field message that conforms to the message format to the server, and the server receives the subscription request from the subscriber on behalf of the sender and processes the subscription request. This achieves the decoupling of the sender and the subscriber, and unifies the message format. This avoids redundant sending of messages on the sender, reduces the message processing pressure on the sender, and reduces the complexity of the server building the customized messages required for the subscriber.

Furthermore, considering that messages in different fields have different message formats, if field messages with multiple message formats are sent to the server 220, the server 220 will consume a lot of resources and time in the message format conversion when subsequently processing the subscription request. Therefore, the format conversion can be performed based on the message format before the message to be updated is sent to the server 220. In specific implementation, the sending end 210 is also used to convert the message to be updated into an update message according to the message format when receiving the message to be updated for the target field message, and send the update message to the server 220.

Specifically, the message to be updated refers to a new message field other than the initial field message received by the sending end 210. The update message is a message obtained after format conversion of the message to be updated based on the message format.

Based on this, when the sender 210 receives a message to be updated for the target field message, it indicates that in addition to the initial field message, other new message fields are also included. The message to be updated is converted into an update message according to the message format, and the update message is sent to the server 220. It is used to update the global field message stored in the server 220 and store the update message in the global field message.

Using the above example, when the sender receives the update message about the "label" field "technology" of the news, it converts the update message according to the message format and converts the "label" field "technology" to label (news label). The label (news label) update message is sent to the server.

In summary, when the sending end receives a message to be updated, the message to be updated is converted into an update message based on the message format of the associated server, thereby ensuring that the message sent to the server has a unified message format.

Furthermore, considering that the local field message occupies a certain storage space in the server 220, the local field message can be stored according to a fixed data structure, and additional storage is performed according to the fixed data structure when the target field message sent by the sender 210 is received. In specific implementation, the server 220 is used to add the target field message to the message set where the local field message is located, and determine the global field message stored in the message set according to the addition result.

Specifically, the message set refers to a set of field messages received from the sender 210 and stored by the server 220. The message set can be a message set or a data structure such as a queue with a data read and write order. The addition result is the storage result of adding the target field message to the message set.

Based on this, after the server 220 adds the target field message to the message set where the local field message is located, the target field message and the local field message stored in the message set form a global field message.

Using the above example, the server stores local field messages such as introduction, conclusion, background, and author. After receiving the target field message composed of news title, summary, date, category, introduction, conclusion, background, author, etc., the target field message is added to the message set where the local field message is located. The message set stores global field messages such as news title, summary, date, category, introduction, conclusion, background, author, etc.

In summary, the server adds the target field message to the message set where the local field message is located, and the message set stores the global field message, thus realizing the integration of adding the target field message and the local field message.

Furthermore, considering that the global field message stored in the server 220 has a fixed message format, and the global field message contains multiple fields and field values corresponding to the fields, when extracting field information in the global field message, it can be obtained by splitting the field message in the global field message. In specific implementation, the server 220 is used to determine at least one subscription field contained in the subscription information; call the message splitter to split the global field message based on the at least one subscription field, and determine the target field information corresponding to the at least one subscription field according to the splitting result; the field information is composed of the target field information corresponding to the at least one subscription field.

Specifically, the subscription field refers to the message field that the subscriber needs to subscribe to, and the field value is the message corresponding to the message field; the message splitter is a component in the server 220 for splitting field messages. The split result is the message splitting result obtained by splitting the global field message based on at least one subscription field. The split result represents the split point for splitting the global field message, and the split string corresponding to the split point. For example, based on the field message title, the global field message "title: title 1, abstract: abstract 1, date: date 1" is split, and the split string is "title: title 1". The split string is the target field information.

Based on this, the server 220 determines at least one subscription field included in the subscription information. The message splitter is called to determine the split point of the global field message based on the at least one subscription field, and split the global field message based on the split point to obtain the target field information corresponding to the at least one subscription field. The target field information corresponding to the at least one subscription field constitutes the field information.

Using the above example, when subscriber 1 subscribes to subscription fields such as title, summary, and date, the global field message is split based on title, summary, and date to obtain the target field information corresponding to the title, summary, and date. The field information is composed of the target field information corresponding to the title, the target field information corresponding to the summary, and the target field information corresponding to the date.

In summary, by calling the message splitter, the global field message is split based on at least one subscription field included in the subscription information, thereby improving the accuracy of field message splitting.

Furthermore, considering that there are multiple subscribers associated with the server 220, each of which has different field configuration rules, it is necessary to package the field configuration rules in the subscription request when sending a subscription request to the server 220. When the server 220 generates a target message, a target message matching the field configuration rule can be generated. In specific implementation, the server 220 is used to determine the subscription field information corresponding to at least one subscription field included in the subscription information in the field information, and combine the at least one subscription field and the subscription field information corresponding to the at least one subscription field according to the field configuration rule to generate the target message.

Based on this, the subscription field information is the field value corresponding to the subscription field. The server 220 determines the subscription field information corresponding to at least one subscription field included in the subscription information in the field information. The subscription field information corresponding to at least one subscription field and at least one subscription field is combined according to the field configuration rule to generate a target message.

Using the above example, when subscriber 1 subscribes to title, summary, and date, the field configuration rules are determined, and the field title, summary, date, and target field information corresponding to each field are combined according to the field configuration rules to obtain the target message.

In summary, at least one subscription field and the subscription field information respectively corresponding to at least one subscription field are combined according to the field configuration rule to generate a target message, thereby obtaining a target message that meets the subscription requirements of the subscriber.

Furthermore, considering that different subscribers have different field configuration rules, the field configuration rules represent the subscription relationship model of the subscriber, and can be implemented according to the subscription relationship model when generating the target message. In specific implementation, the server 220 is used to call the parser to parse the field configuration rules, determine the subscription relationship model containing the subject information according to the parsing results, and combine the at least one subscription field and the subscription field information corresponding to the at least one subscription field based on the subscription relationship model to generate the target message.

Specifically, the parser is a component used for information parsing by the server 220. The subscription relationship model includes the subject information and message format that the subscriber needs to subscribe to.

Based on this, the server 220 calls the parser to parse the field configuration rule, and determines the subscription relationship model containing the subject information according to the parsing result. The subscription relationship model can reflect the message format matched by the subscriber. Based on the subscription relationship model, at least one subscription field and the subscription field information corresponding to at least one subscription field are combined to generate a target message matching the message format.

Using the above example, calling the parser to parse the field configuration rules can obtain a subscription relationship model containing topic information and message format: topic1-topic11: title, abstract, date. The subscription relationship model contains the source topic, the secondary topic to be split, the topic information is separated by -, and the part after the colon separator is the field name information of the message body. Combine the subscription field and subscription field information according to the subscription relationship model to obtain the target message.

In summary, at least one subscription field and the subscription field information corresponding to at least one subscription field are combined based on the subscription relationship model to generate a target message matching the message format, thereby meeting the message format and message content requirements of the subscriber.

Furthermore, considering that there may be multiple subscribers corresponding to the server 220, in order to ensure the accuracy of message sending, the subscriber to which the target message belongs can be determined before sending the target message to the subscriber. In specific implementation, the server 220 is also used to determine the target subscriber based on the subscriber information carried by the subscription request, and send the target message to the target subscriber.

Based on this, the server 220 determines the target subscriber among the multiple subscribers 230 according to the subscriber information carried in the subscription request, and sends the target message to the target subscriber. Before sending the target message to the target subscriber, the subscriber to which the target message belongs is detected and determined.

Using the above example, determine the subscriber information carried in the subscription request: Subscriber 1. According to the subscriber information, it can be determined that the subscriber to which the target message belongs is the target subscriber. Send the target message to the target subscriber.

In summary, before sending the target message to the target subscriber, the subscriber to which the target message belongs is detected and determined to improve the accuracy of message sending.

The message processing system provided by one embodiment of the present specification includes a sender, a server, and multiple subscribers. The sender determines the message format of the initial field message and the associated server, converts the initial field message into a target field message according to the message format, and sends the target field message to the server. The server updates the local field message to a global field message based on the target field message. In the case of receiving a subscription request submitted by a target subscriber among multiple subscribers, the server parses the subscription request and determines the subscription information and field configuration rules according to the parsing result. The field information is extracted from the global field message according to the subscription information. The target message is generated based on the field information and the field configuration rules, and the target message is sent to the target subscriber. The sender only needs to send a target field message that conforms to the message format to the server, and the server receives the subscription request of the subscriber instead of the sender and processes the subscription request. The decoupling of the sender and the subscriber is achieved, and the message format is unified. The redundant sending of the sender's message is avoided, the message processing pressure of the sender is reduced, and the complexity of the custom message required for the server to build the subscriber is reduced.

The following further describes the message processing method provided in this specification by taking the application of the message processing method in transaction message subscription as an example in conjunction with Figure 3. Figure 3 shows a message subscription schematic diagram of a message processing system provided in an embodiment of this specification, which specifically includes the following steps.

Step 302: The sending end receives the initial field message and determines the message format, and converts the initial field message into a target field message according to the message format.

Step 304: The sender sends the target field message to the server.

The message processing system can be applied to stock quote subscriptions in the field of financial transactions. The subscriber can be a risk control system, a user trading terminal, a data analysis system, etc. On the message sending end, construct a unified message format that contains all possible fields. For example, create a message template that contains predefined fields such as ID, time, name, description, and tags, and ensure that each message sent is filled with these fields. When new real-time data (such as stock quotes) arrives, the sender fills in all fields in a unified format and publishes the complete message to the Pulsar topic.

In actual applications, as shown in Figure 4, the sender can send initial field messages such as messageid (message ID), ctime (time), StockID (stock ID), StockCode (stock code), StockName (stock name), Industry (industry), Market (listing market), ListedDate (listing date), SnapshotID (market snapshot ID), StockID (associated stock ID), TradeDate (trading date), TradeTime (trading time), OpenPrice (opening price), ClosePrice (closing price), HighestPrice (highest price), LowestPrice (lowest price), LatestPrice (latest price), ChangeRate (rise and fall), Volume (trading volume), Turnover (trading amount), PE (price-earnings ratio), PB (price-to-book ratio), CirculateMarketValue (circulating market value) to the server in a unified format.

Step 306: The target subscriber among the multiple subscribers submits a subscription request to the server.

The server receives the target field message sent by the sender and splits and reassembles the message based on Pulsar. A message splitter component is set on the server to implement the message splitting function. When subscribing to a Pulsar topic, the subscriber not only specifies the topic, but also submits their respective field subscription lists.

Subscriber A subscribes to fields such as message ID, time, stock ID, stock code, and latest price; Subscriber B subscribes to fields such as message ID, time, stock ID, stock code, opening price, and closing price; Subscriber C subscribes to fields such as message ID, time, stock ID, stock code, stock name, industry, listing market, and listing date. Therefore, each subscriber can create a subscription request based on the required fields and send the subscription request to the server.

Step 308: The server parses the subscription request to obtain field information.

When subscribing to a message, the subscriber submits a list of subscription fields. The subscription information of each subscriber is as follows: Subscriber A subscribes to fields such as message ID, time, stock ID, stock code, and latest price; Subscriber B subscribes to fields such as message ID, time, stock ID, stock code, opening price, and closing price; Subscriber C subscribes to fields such as message ID, time, stock ID, stock code, stock name, industry, listing market, and listing date.

Step 310: The server splits the target field message based on the field information to obtain the target field value.

The message splitter on the server contains a subscription rule engine. The subscriber needs to submit the subscription field configuration rules when subscribing. The rule engine will parse the subscription field configuration rules and save the subscription relationship model.

In actual applications, the subscription relationship model can be: topicA-topicA1:messageid, ctime, StockID, StockCode, atestPrice; topicA-topicA2:messageid, ctime, StockID, StockCode, OpenPrice, ClosePrice; topicA-topicA3:mssageid, ctime, StockID, StockCode, StockID, StockCode, Industry, Market, ListedDate, etc. The subscription relationship model contains the source topic, the secondary topic to be split, the topic information is separated by -, and the part after the colon separator is the field name information of the message body. The splitter uses the assembler module to extract the corresponding field values from the original message according to the subscription field list of each subscriber, and combine them into personalized messages that meet the needs of the subscriber.

Step 312: The server constructs a target message based on the target field value and field information.

The assembler module extracts the corresponding fields according to the subscription field configuration, assembles them into the target message, and delivers the message. Taking the subscription relationship topicA-topicA1:messageid, ctime, StockID, StockCode, LatestPric as an example, the messageA extracted from topicA will be split into messagegaeA1, and the message body contains the subscription 5 field information.

Step 314: The server sends the target message to a target subscriber among the multiple subscribers.

After completing the message splitting and reassembly, the message splitter on the server side delivers the personalized messages to the corresponding subscribers, and each subscriber receives only the field data they subscribe to. The subscriber receives the message delivered by the server that only contains the fields they need, and performs targeted data processing and business logic execution.

In summary, the message format of the sender is unified, and only one format message is constructed. There is no need to change the sender when a new subscriber joins. The server-side message splitter realizes flexible subscription configuration, and the subscriber only subscribes to the required fields to avoid unnecessary data transmission. Even when there are many fields, personalized subscription is easy to implement. The amount of repeated data transmission is greatly reduced, saving communication resources and traffic costs. For example, the ID field only needs to be transmitted once. Decouple the sender and the subscriber. As long as the unified message format remains unchanged, the sender and the subscriber can be expanded and evolved independently. It is easy to implement billing by field, and only the message volume of the subscription field of the subscriber is calculated. By adding a message splitter in the middle of MQ communication to realize the decoupling of unified format message sending and personalized subscription, the complexity of building messages is reduced, flexibility is improved, and system resources and communication costs are also saved.

Corresponding to the above system embodiment, this specification also provides a message processing method embodiment, and Figure 5 shows a flow chart of a message processing method provided by an embodiment of this specification. As shown in Figure 5, the message processing method is applied to the server, wherein the server associates the message format, specifically including the following steps:

Step 502: receiving a target field message sent by a transmitting end, wherein the target field message converts and determines the initial field message according to the message format;

Step 504: updating the local field message to a global field message based on the target field message;

Step 506: when receiving a subscription request submitted by a target subscriber among multiple subscribers, parsing the subscription request, and determining subscription information and field configuration rules according to the parsing result;

Step 508: extracting field information from the global field message according to the subscription information;

Step 510: Generate a target message based on the field information and the field configuration rule, and send the target message to the target subscriber.

Optionally, updating the local field message to the global field message based on the target field message includes: adding the target field message to the message set where the local field message is located, and determining the global field message stored in the message set according to the adding result.

Optionally, extracting field information from the global field message according to the subscription information includes: determining at least one subscription field contained in the subscription information; calling a message splitter to split the global field message based on the at least one subscription field, and determining target field information corresponding to the at least one subscription field according to the splitting result; and composing the field information by the target field information corresponding to the at least one subscription field.

Optionally, generating the target message based on the field information and the field configuration rule includes: determining subscription field information corresponding to at least one subscription field contained in the subscription information in the field information, and combining the at least one subscription field and the subscription field information corresponding to the at least one subscription field according to the field configuration rule to generate the target message.

Optionally, generating a target message based on the field information and the field configuration rules includes: calling a parser to parse the field configuration rules, determining a subscription relationship model containing the subject information based on the parsing results, and combining the at least one subscription field and the subscription field information corresponding to the at least one subscription field based on the subscription relationship model to generate the target message.

Optionally, sending the target message to the target subscriber further includes: determining the target subscriber according to the subscriber information carried in the subscription request, and sending the target message to the target subscriber.

In practical applications, the message processing method includes a sender, a server, and multiple subscribers. The message processing method is applied to the server. A target field message sent by the sender is received. The target field message is generated by the sender based on the initial field message and the message format, that is, the sender determines the message format of the initial field message and the associated server, and the message format is a unified message format between the sender and the server. The initial field message is converted into a target field message according to the message format, and the target field message is sent to the server. After the server receives the target field message, since the server stores the local field message, the local field message can be updated based on the target field message, and the target field message is added to the storage location where the local field message is located to obtain the global field message. In the case of receiving a subscription request submitted by a target subscriber among multiple subscribers, the server parses the subscription request and determines the subscription information and field configuration rules according to the parsing result. Field information is extracted from the global field message according to the subscription information. A target message is generated based on the field information and the field configuration rules, and the target message is sent to the target subscriber.

A message processing method provided by an embodiment of the present specification includes a sending end, a server end and multiple subscribers. The sending end determines the message format of the initial field message and the associated server end, converts the initial field message into a target field message according to the message format, and sends the target field message to the server end. The server end updates the local field message to a global field message based on the target field message. In the case of receiving a subscription request submitted by a target subscriber end among multiple subscriber ends, the server end parses the subscription request and determines the subscription information and field configuration rules according to the parsing result. Field information is extracted from the global field message according to the subscription information. A target message is generated based on the field information and the field configuration rules, and the target message is sent to the target subscriber end. The sending end only needs to send a target field message that conforms to the message format to the server end, and the server end receives the subscription request of the subscriber end instead of the sending end, and processes the subscription request. The decoupling of the sending end and the subscriber end is achieved, and the message format is unified. The redundant sending of the sending end message is avoided, the message processing pressure of the sending end is reduced, and the complexity of the custom message required for the server end to build the subscriber end is reduced.

Corresponding to the above method embodiment, this specification also provides a message processing device embodiment, and Figure 6 shows a structural schematic diagram of a message processing device provided by an embodiment of this specification. As shown in Figure 6, the message processing device is applied to the server, wherein the server associates the message format, and the device includes:

The receiving module 602 is configured to receive a target field message sent by a sending end, wherein the target field message is determined by converting the initial field message according to the message format;

An updating module 604 is configured to update the local field message to a global field message based on the target field message;

The parsing module 606 is configured to parse the subscription request submitted by the target subscriber among the multiple subscribers when receiving the subscription request, and determine the subscription information and field configuration rules according to the parsing result;

An extraction module 608 is configured to extract field information from the global field message according to the subscription information;

The generating module 610 is configured to generate a target message based on the field information and the field configuration rule, and send the target message to the target subscriber.

In an optional embodiment, the updating module 604 is further configured to: add the target field message to the message set where the local field message is located, and determine the global field message stored in the message set according to the adding result.

In an optional embodiment, the extraction module 608 is further configured to: determine at least one subscription field contained in the subscription information; call a message splitter to split the global field message based on the at least one subscription field, and determine the target field information corresponding to the at least one subscription field according to the splitting result; and form the field information by the target field information corresponding to the at least one subscription field.

In an optional embodiment, the generation module 610 is further configured to: determine in the field information the subscription field information corresponding to at least one subscription field contained in the subscription information, and combine the at least one subscription field and the subscription field information corresponding to the at least one subscription field according to the field configuration rule to generate the target message.

In an optional embodiment, the generation module 610 is further configured to: call a parser to parse the field configuration rules, determine a subscription relationship model containing the topic information based on the parsing results, and combine the at least one subscription field and the subscription field information corresponding to the at least one subscription field based on the subscription relationship model to generate the target message.

In an optional embodiment, the generating module 610 is further configured to: determine the target subscriber according to the subscriber information carried in the subscription request, and send the target message to the target subscriber.

A message processing device provided by an embodiment of the present specification includes a sending end, a service end and multiple subscribers. The sending end determines the message format of the initial field message and the associated service end, converts the initial field message into a target field message according to the message format, and sends the target field message to the service end. The service end updates the local field message to a global field message based on the target field message. In the case of receiving a subscription request submitted by a target subscriber among multiple subscribers, the service end parses the subscription request and determines the subscription information and field configuration rules according to the parsing result. Field information is extracted from the global field message according to the subscription information. A target message is generated based on the field information and the field configuration rules, and the target message is sent to the target subscriber. The sending end only needs to send a target field message that conforms to the message format to the service end, and the service end receives the subscription request of the subscriber end instead of the sending end, and processes the subscription request. The decoupling of the sending end and the subscriber end is achieved, and the message format is unified. The redundant sending of the sending end message is avoided, the message processing pressure of the sending end is reduced, and the complexity of the custom message required for the server end to build the subscriber end is reduced.

The above is a schematic scheme of a message processing device of this embodiment. It should be noted that the technical scheme of the message processing device and the technical scheme of the message processing method described above are of the same concept, and the details not described in detail in the technical scheme of the message processing device can be found in the description of the technical scheme of the message processing method described above.

Corresponding to the above system embodiment, this specification also provides a message update method embodiment. FIG7 shows a flow chart of a message update method provided according to an embodiment of this specification. The message update method is applied to the server, wherein the server associates the message format. As shown in FIG7, it specifically includes the following steps:

Step 702: receiving a target field message sent by a transmitting end, wherein the target field message converts and determines the initial field message according to the message format;

Step 704: Based on the target field message, the local field message is updated to a global field message, wherein the global field message is used to generate a target message corresponding to a subscription request associated with a target subscriber.

In practical applications, the message update method is applied to the server. Receive the target field message sent by the sender. The target field message is generated by the sender based on the initial field message and the message format, that is, the sender determines the message format of the initial field message and the associated server, and the message format is a unified message format between the sender and the server. Convert the initial field message into a target field message according to the message format, and send the target field message to the server. After the server receives the target field message, since the server stores the local field message, it can update the local field message based on the target field message, add the target field message to the storage location of the local field message, and obtain the global field message. In the case of receiving a subscription request submitted by a target subscriber among multiple subscribers, the target message required by the subscriber can be generated based on the global field message.

In summary, the sender only needs to send a target field message that conforms to the message format to the server, and the server receives the subscription request from the subscriber on behalf of the sender and processes the subscription request. This achieves the decoupling of the sender and the subscriber, unifies the message format, avoids redundant sending of messages on the sender, and reduces the message processing pressure on the sender.

Corresponding to the above method embodiment, this specification also provides a message updating device embodiment, and FIG8 shows a schematic diagram of the structure of a message updating device provided by an embodiment of this specification. The message updating device is applied to a server, wherein the server associates a message format. As shown in FIG8, the device includes:

The receiving module 802 is configured to receive a target field message sent by a sending end, wherein the target field message is determined by converting the initial field message according to the message format;

The generating module 804 is configured to update the local field message into a global field message based on the target field message, wherein the global field message is used to generate a target message corresponding to a subscription request associated with a target subscriber.

In summary, the sender only needs to send a target field message that conforms to the message format to the server, and the server receives the subscription request from the subscriber on behalf of the sender and processes the subscription request. This achieves the decoupling of the sender and the subscriber, unifies the message format, avoids redundant sending of messages on the sender, and reduces the message processing pressure on the sender.

The above is a schematic scheme of a message updating device of this embodiment. It should be noted that the technical scheme of the message updating device and the technical scheme of the message updating method described above are of the same concept, and the details not described in detail in the technical scheme of the message updating device can be found in the description of the technical scheme of the message updating method described above.

Corresponding to the above system embodiment, this specification also provides a subscription request processing method embodiment. FIG9 shows a flowchart of a subscription request processing method provided according to an embodiment of this specification. The subscription request processing method is applied to the server. As shown in FIG9, it specifically includes the following steps:

Step 902: receiving a subscription request submitted by a target subscriber;

Step 904: Parse the subscription request, and determine subscription information and field configuration rules according to the parsing result;

Step 906: extracting field information from a global field message according to the subscription information, wherein the global field message is determined based on a field message sent by the sender;

Step 908: Generate a target message based on the field information and the field configuration rule, and send the target message to the target subscriber.

In practical applications, the subscription request processing method is applied to the server. When receiving a subscription request submitted by a target subscriber among multiple subscribers, the server parses the subscription request and determines the subscription information and field configuration rules based on the parsing results. Extract field information from the global field message based on the subscription information. Generate a target message based on the field information and the field configuration rules, and send the target message to the target subscriber. Among them, the global field message is determined based on the field message sent by the sender. After the server receives the field message sent by the sender, since the server stores the local field message, it can update the local field message based on the field message, add the field message to the storage location where the local field message is located, and obtain the global field message.

In summary, the server receives the subscription request from the subscriber instead of the sender and processes the subscription request. This decouples the sender and the subscriber and unifies the message format. It also reduces the complexity of the custom message required by the server to build the subscriber.

Corresponding to the above method embodiment, this specification also provides a subscription request processing device embodiment. FIG10 shows a schematic diagram of the structure of a subscription request processing device provided by an embodiment of this specification. The subscription request processing device is applied to the server. As shown in FIG10, the device includes:

The receiving module 1002 is configured to receive a subscription request submitted by a target subscriber;

The parsing module 1004 is configured to parse the subscription request and determine the subscription information and field configuration rules according to the parsing result;

An extraction module 1006 is configured to extract field information from a global field message according to the subscription information, wherein the global field message is determined based on a field message sent by a sending end;

The generating module 1008 is configured to generate a target message based on the field information and the field configuration rule, and send the target message to the target subscriber.

In summary, the server receives the subscription request from the subscriber instead of the sender and processes the subscription request. This decouples the sender and the subscriber and unifies the message format. It also reduces the complexity of the custom message required by the server to build the subscriber.

The above is a schematic scheme of a subscription request processing device of this embodiment. It should be noted that the technical scheme of the subscription request processing device and the technical scheme of the subscription request processing method described above belong to the same concept, and the details not described in detail in the technical scheme of the subscription request processing device can be found in the description of the technical scheme of the subscription request processing method described above.

Fig. 11 shows a block diagram of a computing device 1100 according to an embodiment of the present specification. The components of the computing device 1100 include but are not limited to a memory 1110 and a processor 1120. The processor 1120 is connected to the memory 1110 via a bus 1130, and a database 1150 is used to store data.

The computing device 1100 also includes an access device 1140 that enables the computing device 1100 to communicate via one or more networks 1160. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 1140 may include one or more of any type of network interface (e.g., a network interface card (NIC)) of wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a world-wide interoperability for microwave access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, and a near field communication (NFC).

In one embodiment of the present specification, the above components of the computing device 1100 and other components not shown in FIG. 11 may also be connected to each other, for example, through a bus. It should be understood that the computing device structure block diagram shown in FIG. 11 is only for illustrative purposes and is not intended to limit the scope of the present specification. Those skilled in the art may add or replace other components as needed.

The computing device 1100 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a personal computer (PC). The computing device 1100 may also be a mobile or stationary server.

The processor 1120 is used to execute the following computer executable instructions, which implement the steps of the above-mentioned message processing method when executed by the processor.

The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the above message processing method belong to the same concept, and the details not described in detail in the technical scheme of the computing device can be referred to the description of the technical scheme of the above message processing method.

An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which can implement the steps of the above-mentioned message processing method when executed by a processor.

The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the message processing method described above are of the same concept, and the details not described in detail in the technical scheme of the storage medium can be found in the description of the technical scheme of the message processing method described above.

An embodiment of the present specification also provides a computer program product, including a computer program or instructions, which implement the steps of the above-mentioned message processing method when executed by a processor.

The above is a schematic scheme of a computer program product of this embodiment. It should be noted that the technical scheme of the computer program product and the technical scheme of the message processing method described above are of the same concept, and the details not described in detail in the technical scheme of the computer program product can be found in the description of the technical scheme of the message processing method described above.

The above is a description of a specific embodiment of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

The preferred embodiments of this specification disclosed above are only used to help explain this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that technicians in the relevant technical field can understand and use this specification well.

Claims (13)

1. A message processing system, characterized by comprising a sending end, a service end and a plurality of subscribers; The sending end is used to determine the message format of the initial field message and the associated server, convert the initial field message into a target field message according to the message format, and send the target field message to the server; The server is used to update the local field message to a global field message based on the target field message; when receiving a subscription request submitted by a target subscriber among multiple subscribers, parse the subscription request, and determine the subscription information and field configuration rules according to the parsing result; extract field information from the global field message according to the subscription information; generate a target message based on the field information and the field configuration rules, and send the target message to the target subscriber. 2. The message processing system according to claim 1 is characterized in that the sending end is also used to convert the message to be updated into an update message according to the message format when receiving the message to be updated for the target field message, and send the update message to the server. 3. The message processing system according to claim 1 is characterized in that the server is used to add the target field message to the message set where the local field message is located, and determine the global field message stored in the message set according to the adding result. 4. The message processing system according to claim 1 is characterized in that the server is used to determine at least one subscription field contained in the subscription information; call the message splitter to split the global field message based on the at least one subscription field, and determine the target field information corresponding to the at least one subscription field according to the splitting result; and the field information is composed of the target field information corresponding to the at least one subscription field. 5. The message processing system according to claim 4 is characterized in that the server is used to determine the subscription field information corresponding to at least one subscription field contained in the subscription information in the field information, and combine the at least one subscription field and the subscription field information corresponding to the at least one subscription field according to the field configuration rule to generate the target message. 6. The message processing system according to claim 5 is characterized in that the server is used to call a parser to parse the field configuration rules, determine a subscription relationship model containing topic information based on the parsing results, and combine the at least one subscription field and the subscription field information corresponding to the at least one subscription field based on the subscription relationship model to generate the target message. 7. The message processing system according to claim 1 is characterized in that the server is also used to determine the target subscriber according to the subscriber information carried in the subscription request, and send the target message to the target subscriber. 8. A message processing method, characterized in that it is applied to a server, wherein the server associates the message format, including: Receiving a target field message sent by a sending end, wherein the target field message is determined by converting an initial field message according to the message format; updating the local field message to a global field message based on the target field message; When receiving a subscription request submitted by a target subscriber among multiple subscribers, parsing the subscription request, and determining subscription information and field configuration rules according to the parsing result; extracting field information from the global field message according to the subscription information; A target message is generated based on the field information and the field configuration rule, and the target message is sent to the target subscriber. 9. A message update method, characterized in that it is applied to a server, wherein the server associates the message format, including: Receiving a target field message sent by a sending end, wherein the target field message is determined by converting an initial field message according to the message format; The local field message is updated to a global field message based on the target field message, wherein the global field message is used to generate a target message corresponding to a subscription request associated with a target subscriber. 10. A subscription request processing method, characterized in that it is applied to a server and includes: Receive the subscription request submitted by the target subscriber; Parsing the subscription request, and determining subscription information and field configuration rules according to the parsing result; Extracting field information from a global field message according to the subscription information, wherein the global field message is determined based on a field message sent by a sending end; A target message is generated based on the field information and the field configuration rule, and the target message is sent to the target subscriber. 11. A computing device, comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the method described in any one of claims 8 to 10 are implemented. 12. A computer-readable storage medium, characterized in that it stores computer-executable instructions, which, when executed by a processor, implement the steps of the method described in any one of claims 8 to 10. 13. A computer program product, characterized in that it comprises a computer program or instructions, which implement the steps of the method according to any one of claims 8 to 10 when executed by a processor.