Message data processing method and device, storage medium and electronic equipment
By deduplication and merging in the message queue, the problem of repetition of change messages captured by message middleware or database binlog is solved, which improves downstream business processing efficiency and reduces data processing volume and cost.
Patent Information
- Application Number
- CN202411827154.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-11
- Publication Date
- 2025-03-21
- Estimated Expiration
- 2044-12-11
AI Technical Summary
In the case of large-scale subscription business changes, the change messages captured by the message middleware or database binlog may have a large number of duplications, resulting in downstream businesses that need to process the same data multiple times, affecting efficiency.
By obtaining the target business message data of the preset time interval in the message queue, it is divided into deduplication class and merge class message groups according to the operation type, deduplication and merge processing are performed, and valid message content is filtered out, and business execution and dependencies remain unchanged.
It effectively reduces the data processing volume of downstream services, improves the processing efficiency of downstream services, and avoids performance bottlenecks and cost increase caused by repeated processing.
Smart Images

Figure CN119668900A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of data processing technology, and in particular to a message data processing method, device, storage medium and electronic device. Background Art
[0002] With the rapid development of Internet business, various demands continue to emerge, especially in scenarios where a large number of subscription businesses change. For example, synchronizing video content from a third-party platform to a private platform, or monitoring changes in a business in order to handle related dependent businesses. In these scenarios, upstream businesses usually actively send messages through message middleware (Message Queue, MQ), or monitor the binlog (MySQL data binary log) of the database table to capture changes. Downstream businesses adjust their own logic based on these change messages. However, these change messages may be repeated in large quantities within a certain period of time, causing downstream businesses to need to process the same data multiple times, affecting efficiency.
[0003] There are two main solutions in the past: one is to reduce the processing time of a single message by optimizing the downstream business code to improve efficiency, but this method faces the bottleneck of performance optimization; the other is to increase the number of instances and threads of downstream business services to improve processing performance, but this method will increase service costs, and repeated processing is not only inefficient, but may also extend the message processing time due to business ID locking operations.
[0004] Therefore, how to effectively handle duplicate message data becomes the key to improving downstream business processing efficiency. Summary of the invention
[0005] In view of the above problems, the present invention provides a message data processing method, device, storage medium and electronic device that overcome the above problems or at least partially solve the above problems. The technical solution is as follows:
[0006] A message data processing method, comprising:
[0007] Obtaining a preset number of target business message data from a specified message queue at a preset time interval, wherein the target business message data includes message data attribute information, and the message data attribute information includes an operation type, a message identifier, a message timestamp, grouping attribute information, and a deduplication unique identifier of the target business message data;
[0008] According to the operation type of the target business message data, determine the message attribute category of the target business message data, divide each of the target business message data whose message attribute category is the deduplication category into a deduplication category message group, and divide each of the target business message data whose message attribute type is the merging category into a merging category message group;
[0009] In the deduplication class message group, the target business message data with the same grouping attribute information are divided into the same deduplication group, and each target business message data with the same deduplication unique identifier in each deduplication group is deduplicated respectively, and the target business message data with the earliest message timestamp is retained to obtain a message deduplication result;
[0010] In the merged message group, the target business message data with the same grouping attribute information are divided into the same merged group, and according to the positive and negative hedging relationship of the operation type, each target business message data in each merged group is divided into a corresponding merged type group, and adjacent target business message data with the same deduplication unique identifier in each merged type group are deduplicated. After deduplication, hedging processing is performed according to the positive and negative hedging of the operation type of each target business message data in the merged type group to obtain a message merging result;
[0011] Combining the message deduplication result and the message merging result into a target message set;
[0012] The target service message data in the target message set are sorted in ascending order according to the message timestamp, and the target service message data in the target message set are pushed to the target service processing queue in sequence according to the sorted order.
[0013] Optionally, the operation types include adding, modifying, passing review, going online, going offline, deleting and restoring.
[0014] Optionally, determining the message attribute category of the target service message data according to the operation type of the target service message data includes:
[0015] In a case where the operation type of the target business message data is a first preset operation, determining that the message attribute category of the target business message data is a deduplication category, wherein the first preset operation includes adding, modifying, and reviewing and passing;
[0016] When the operation type of the target business message data is a second preset operation, the message attribute category of the target business message data is determined to be a merge category, wherein the second preset operation includes going online, going offline, deleting, and restoring.
[0017] Optionally, the target business message data in each merged group is divided into corresponding merged type groups according to the positive and negative hedging relationship of the operation type, including:
[0018] Classify the target business message data whose operation type is online or offline in the same merged group into a first merged type group;
[0019] The target business message data whose operation type is deletion or restoration in the same merged group is divided into a second merged type group.
[0020] Optionally, when the operation type of the target business message data is online or restored, a positive identifier is added to the target business message data; when the operation type of the target business message data is offline or deleted, a negative identifier is added to the target business message data, and after deduplication, hedging processing is performed according to the positive and negative properties of the operation types of each target business message data in the merge type group, including:
[0021] Calculate the hedging value of the merged type group by using the positive identifier or negative identifier carried by each target business message data in the merged type group after deduplication;
[0022] When the hedging value is 1, the target business message data retained by the merge type group is a forward operation type;
[0023] When the hedging value is -1, the target business message data retained by the merge type group is a reverse operation type;
[0024] When the hedge value is 0, the consolidation type group is empty.
[0025] Optionally, the message data attribute information further includes a service type and a service ID of the target service message data. Before acquiring a preset amount of target service message data from a specified message queue at a preset time interval, the method further includes:
[0026] Monitor the original service message data pushed by the upstream service producer at the current moment;
[0027] Parsing the original service message data to obtain the service type, service ID, operation type and message identifier;
[0028] Assigning the current time to the message timestamp of the original service message data;
[0029] Generate a deduplicated unique identifier for the original business message data using the business ID and operation type of the original business message data;
[0030] Generate a cache unique identifier for the original service message data using the service type and service ID of the original service message data;
[0031] A query is made in the designated memory database as to whether the cache unique identifier exists. If yes, the cache unique identifier is set as the grouping attribute information of the original business message data to obtain the target business message data. If not, the cache unique identifier is stored in the designated memory database, and the step of setting the cache unique identifier as the grouping attribute information of the original business message data to obtain the target business message data is executed.
[0032] Optionally, the generating a deduplicated unique identifier of the original business message data by using the business ID and operation type of the original business message data includes:
[0033] Concatenate the service ID of the target service message data with the attribute name and attribute value of the operation type to obtain a service attribute string;
[0034] A hash value of the service attribute character string is calculated, and the hash value is confirmed as the deduplicated unique identifier of the target service message data.
[0035] A message data processing device comprises: a target business message data acquisition unit, a message attribute classification unit, a message deduplication result acquisition unit, a message merging result acquisition unit, a target message set acquisition unit and a message pushing unit.
[0036] The target business message data acquisition unit is used to acquire a preset number of target business message data from a specified message queue at a preset time interval, wherein the target business message data includes message data attribute information, and the message data attribute information includes an operation type, a message identifier, a message timestamp, grouping attribute information, and a deduplication unique identifier of the target business message data;
[0037] The message attribute category division unit is used to determine the message attribute category of the target business message data according to the operation type of the target business message data, and divide each of the target business message data whose message attribute category is the deduplication category into a deduplication category message group, and divide each of the target business message data whose message attribute type is the merging category into a merging category message group;
[0038] The message deduplication result obtaining unit is used to divide the target business message data having the same grouping attribute information into the same deduplication group in the deduplication class message group, deduplicate the target business message data having the same deduplication unique identifier in each deduplication group, retain the target business message data having the earliest message timestamp, and obtain the message deduplication result;
[0039] The message merging result obtaining unit is used to divide the target business message data having the same grouping attribute information into the same merged group in the merged message group, and divide each target business message data in each merged group into a corresponding merged type group according to the positive and negative hedging relationship of the operation type, and deduplicate adjacent target business message data having the same deduplication unique identifier in each merged type group, and after deduplication, perform hedging processing according to the positive and negative hedging of the operation type of each target business message data in the merged type group to obtain a message merging result;
[0040] The target message set obtaining unit is used to combine the message deduplication result and the message merging result into a target message set;
[0041] The message pushing unit is used to sort each of the target business message data in the target message set in ascending order according to the message timestamp, and push each of the target business message data in the target message set to the target business processing queue in the sorted order.
[0042] A computer-readable storage medium stores a program, wherein when the program is executed by a processor, the message data processing method described in any one of the above items is implemented.
[0043] An electronic device, comprising at least one processor, and at least one memory and a bus connected to the processor; wherein the processor and the memory communicate with each other via the bus; and the processor is used to call program instructions in the memory to execute any of the message data processing methods described above.
[0044] By means of the above technical scheme, the present invention provides a message data processing method, device, storage medium and electronic device, which obtain a preset number of target business message data from a specified message queue at a preset time interval, wherein the target business message data includes message data attribute information, and the message data attribute information includes an operation type, a message identifier, a message timestamp, grouping attribute information and a deduplication unique identifier of the target business message data; according to the operation type of the target business message data, the message attribute category of the target business message data is determined, and each target business message data with a message attribute category of the deduplication category is divided into a deduplication category message group, and each target business message data with a message attribute type of the merging category is divided into a merging category message group; in the deduplication category message group, the target business message data with the same grouping attribute information are divided into the same deduplication group, and each target business message data with the same deduplication unique identifier in each deduplication group is respectively Message data is deduplicated, and the target business message data with the earliest message timestamp is retained to obtain the message deduplication result; in the merged message group, the target business message data with the same grouping attribute information is divided into the same merge group, and each target business message data in each merge group is divided into the corresponding merge type group according to the positive and negative hedging relationship of the operation type, and the adjacent target business message data with the same deduplication unique identifier in each merge type group is deduplicated, and after deduplication, the positive and negative hedging of the operation type of each target business message data in the merge type group is performed to obtain the message merging result; the message deduplication result and the message merging result are combined into a target message set; each target business message data in the target message set is sorted in ascending order according to the message timestamp, and each target business message data in the target message set is pushed to the target business processing queue in sequence according to the sorted order. The present invention adopts the idea of summary algorithm for deduplication, uses the delayed task queue, and performs timestamp order preservation processing to realize deduplication and merging of message data, thereby filtering out effective message content, while ensuring that business execution and dependency relationships remain unchanged, thereby helping to improve downstream business processing efficiency.
[0045] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0046] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:
[0047] Figure 1 An architecture diagram of message data deduplication and merging processing provided by an embodiment of the present invention is shown;
[0048] Figure 2 A schematic diagram showing a flow chart of an implementation of a message data processing method provided by an embodiment of the present invention;
[0049] Figure 3 An example diagram of message data attribute information provided by an embodiment of the present invention is shown;
[0050] Figure 4 An example diagram showing message data deduplication and merging provided by an embodiment of the present invention is shown;
[0051] Figure 5 A flow chart showing another implementation of a message data processing method provided by an embodiment of the present invention;
[0052] Figure 6 A schematic diagram showing the structure of a message data processing device provided by an embodiment of the present invention is shown;
[0053] Figure 7 A schematic structural diagram of an electronic device provided by an embodiment of the present invention is shown. DETAILED DESCRIPTION
[0054] The exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present invention and to enable the scope of the present invention to be fully communicated to those skilled in the art.
[0055] With the rapid development of Internet business, various demands continue to emerge, especially in scenarios with large-scale subscription changes, such as synchronizing video content or monitoring business changes. Upstream businesses usually use message middleware (Message Queue, MQ) or listen to database binlog (MySQL data binary log) to capture changes, and downstream businesses adjust their logic based on these messages. However, these messages may be repeated in large quantities in a short period of time, causing downstream businesses to repeatedly process the same data, affecting efficiency. Traditional solutions include optimizing downstream business code to reduce processing time, but face performance bottlenecks; or increasing the number of service instances and threads, but this will increase costs and extend processing time due to business ID locking operations.
[0056] Therefore, it is necessary to introduce an imperceptible intermediate processing layer between message producers and consumers to ensure that the processed message results are consistent with the original results and do not affect the business process. In addition, the dependency and order issues between messages must be resolved. This deduplication and merging of message data is fundamentally different from the traditional deduplication of raw data sets, which does not need to consider the complex dependencies between message objects and data. Solving these problems is crucial to improving downstream business processing efficiency and reducing costs.
[0057] like Figure 1 The figure shows an architecture diagram of message data deduplication and merging processing provided by an embodiment of the present invention. In order to solve the problem of message processing efficiency between upstream and downstream businesses, the present invention introduces an intermediate layer processing module between the two, that is, changing the message consumer end, which is used to obtain and encapsulate message content, push into the delay queue, group deduplication and merge the messages, and sort the merged messages and push them to downstream businesses. This module is transparent to upstream and downstream businesses and does not involve modifying its code. In order to achieve efficient message processing, a summary algorithm is used for deduplication processing, and a Redis delay task queue and a timestamp order preservation method are used to ensure that only valid message content is transmitted without affecting business execution and dependencies. The processed messages are pushed to downstream businesses in sequence, which significantly improves the efficiency of synchronous processing. This method is essentially different from the traditional method of increasing the number of downstream business instances and consumer threads, or optimizing code logic. The traditional method is prone to processing delays when a distributed lock is required, and message backlog problems are prone to occur during peak hours. The solution provided by this patent can fundamentally solve these problems and improve overall processing efficiency.
[0058] like Figure 2 As shown, a flow chart of an implementation of a message data processing method provided by an embodiment of the present invention is provided, and the method includes:
[0059] S100. Obtain a preset number of target business message data from a specified message queue at a preset time interval, wherein the target business message data includes message data attribute information, and the message data attribute information includes an operation type, a message identifier, a message timestamp, grouping attribute information, and a deduplicated unique identifier of the target business message data.
[0060] The message queue refers to a specific queue configured in a message middleware environment for temporarily storing and transmitting message data. In the embodiment of the present invention, the specified message queue may be an RQueue queue, wherein the RQueue queue refers to a message queue mode implemented by Redis, and the queue is implemented using the list structure of Redis.
[0061] The target business message data refers to the message data pushed by the upstream producer, which usually contains business-related information, such as operation instructions, status updates, etc. The target business message data is generally a string in JSON format or XML format.
[0062] The message data attribute information is additional information or metadata related to the data content carried by the target service message data itself. Figure 3 The diagram shows an example of message data attribute information provided by an embodiment of the present invention, which may include the business type, business ID, operation type, message identifier, message timestamp, grouping attribute information and deduplication unique identifier of the target business message data.
[0063] The operation type is used to indicate the specific operation involved in the target business message data.
[0064] Optionally, the operation type may include adding, modifying, passing review, going online, going offline, deleting, and restoring. Taking video as an example, going online and going offline are similar to publishing and unpublishing videos to network users.
[0065] Among them, the message identifier is used to uniquely identify a target business message data, which can be a unique string or number. Different from the business ID, the message identifier focuses on the uniqueness of the target business message data itself during the transmission process.
[0066] The message timestamp is also called the message receiving timestamp, which is the system timestamp when the target business message data is received and is used to maintain time sequence or perform timing analysis.
[0067] Among them, the group attribute information (group ID) is the attribute information used to group multiple messages together, and is usually used to batch or merge messages. For example, all target business message data with the same group ID can be divided into the same group. The group attribute information carried by the target business message data is related to its business type and business ID.
[0068] The deduplication unique identifier (deduplication key) is a unique identifier used for message deduplication. The deduplication unique identifier carried by the target business message data is related to its business ID and operation type.
[0069] Specifically, the embodiment of the present invention can start a thread from a thread pool and pull a preset number of target business message data from the RQueue queue at a preset time interval. The preset time interval and the preset number can be set according to specific business needs and traffic conditions to avoid delays in message data processing or poor deduplication and merging effects.
[0070] S110. Determine the message attribute category of the target business message data according to the operation type of the target business message data, divide each target business message data whose message attribute category is the deduplication category into a deduplication category message group, and divide each target business message data whose message attribute type is the merging category into a merging category message group.
[0071] The message attribute category refers to the attribute classification of the message, which is used to help the processing system understand how to process or route the message. The message attribute category includes deduplication category and merging category.
[0072] Specifically, an embodiment of the present invention can pre-create deduplication message groups and merge message groups, and based on the operation types of the acquired target business message data, classify the target business message data of operation types that do not have positive and negative hedging relationships into the deduplication message groups, and classify the target business message data of operation types that have positive and negative hedging relationships into the merge message groups.
[0073] S120. In the deduplication message group, target business message data with the same grouping attribute information are divided into the same deduplication group, and each target business message data with the same deduplication unique identifier in each deduplication group is deduplicated respectively, and the target business message data with the earliest message timestamp is retained to obtain the message deduplication result.
[0074] Each target business message data in the deduplication message group is a deduplication-capable message, and the grouping attribute information includes a group ID generated based on the business type and business ID of the target business message data. The same group ID indicates that the business objects to be operated by these target business message data are the same, and these target business message data can be divided into the same deduplication group.
[0075] For each target business message data in the same deduplication group, although the business objects to be operated by these target business message data are the same, the specific operation types involved may be different. For example: in deduplication group A, there are target business message data a and target business message data b. The target business message data a is a new operation for business B, and the target business message data b is a modification operation for business B. Therefore, the embodiment of the present invention can use the deduplication unique identifier related to the business ID and operation type of the target business message data as the basis for deduplication. The same deduplication unique identifier indicates that these target business message data are deduplicated messages of repeated operations. In the same deduplication group, multiple target business message data with the same deduplication unique identifier are deduplicated, and the target business message data with the earliest message timestamp is retained, and other target business message data are discarded. After each deduplication group completes the above-mentioned deduplication operation, the deduplication results of each deduplication group are integrated to obtain the message deduplication result.
[0076] It should be noted that the deduplication unique identifier related to the business ID and operation type of the target business message data is used as the basis for deduplication here because each target business message data has a unique message identifier. If the overall message body content of the target business message data is used as the basis for deduplication, the program will identify each target business message data as a different message body. After deduplication, each target business message data will be retained and the deduplication effect cannot be achieved.
[0077] S130. In the merged message group, target business message data with the same grouping attribute information are divided into the same merged group. According to the positive and negative hedging relationship of the operation type, each target business message data in each merged group is divided into a corresponding merged type group. Adjacent target business message data with the same deduplication unique identifier in each merged type group are deduplicated. After deduplication, hedging processing is performed according to the positive and negative hedging relationship of the operation type of each target business message data in the merged type group to obtain the message merging result.
[0078] Among them, the positive and negative hedging relationship refers to offsetting or merging certain operations according to the relative relationship of the operation types when processing business messages to simplify the results or achieve the final desired state. Positive and negative hedging relationships appear in operations that need to be merged or offset each other, such as "increase-decrease", "add-remove" and "enable-disable".
[0079] Each target business message data in the merged message group is a mergeable message, and the grouping attribute information includes a group ID generated based on the business type and business ID of the target business message data. The same group ID indicates that the business objects to be operated by these target business message data are the same, and these target business message data can be divided into the same merged group.
[0080] For each target business message data in the same merge group, although the business objects to be operated by these target business message data are the same, the positive and negative hedging relationships involved in the specific operation types may be different. For example, in merge group C, there are target business message data c, target business message data d, target business message data e and target business message data h. The target business message data c is an online operation for business D, the target business message data d is an offline operation for business D, the target business message data e is a deletion operation for business D, and the target business message data h is a restoration operation for business D. Here, the operation types of the target business message data c and the target business message data d have a positive and negative hedging relationship, and the operation types of the target business message data e and the target business message data h have a positive and negative hedging relationship.
[0081] In the embodiment of the present invention, in the same merged group, a merged type group can be created with an online-offline positive and negative hedging relationship, and another merged type group can be created with a delete-restore positive and negative hedging relationship. All target business message data in the same merged group are assigned to the corresponding merged type group. For the same merged type group, since the original business may need to support idempotence, two target business message data with adjacent timestamps in the merged type group may contain repeated positive or reverse messages, so it is necessary to perform deduplication between adjacent target business message data. Here, deduplication is still based on the deduplication unique identifier. If the deduplication unique identifiers between at least two target business message data with adjacent timestamps in the same merged type group are the same, then these target business message data are deduplicated, and the target business message data with the earliest message timestamp is retained. After deduplication, the target business message data in the merged type group are merged (hedged) according to the positive and negative nature of the operation types. For example, one online operation offsets one offline operation, and one deletion operation offsets one restoration operation. The remaining business operation messages after the merger are used as the merge result of the merged type group. After each merge group completes the aforementioned deduplication and merging operations, the merge results of each merge type group are integrated to obtain the message merge result.
[0082] S140: Combine the message deduplication result and the message merging result into a target message set.
[0083] like Figure 4 The figure shows an example diagram of message data deduplication and merging provided by an embodiment of the present invention. By deduplication and merging of message data, the data processing volume of downstream business can be effectively reduced, thereby improving the processing efficiency of downstream business.
[0084] S150 , sorting each target service message data in the target message set in ascending order according to the message timestamp, and pushing each target service message data in the target message set to the target service processing queue in sequence according to the sorted order.
[0085] The target business processing queue is the message queue to be processed by downstream consumers. After receiving the target business message data in the target business processing queue, the downstream consumer parses the target business message data to extract the business type, business ID and operation type, and then calls the third-party API interface according to the business ID to obtain complete business information, which is then written into the downstream business database, or other business logic processing is performed as needed.
[0086] The present invention provides a message data processing method, which includes: obtaining a preset number of target business message data from a designated message queue at a preset time interval, wherein the target business message data includes message data attribute information, and the message data attribute information includes an operation type, a message identifier, a message timestamp, grouping attribute information and a deduplication unique identifier of the target business message data; determining the message attribute category of the target business message data according to the operation type of the target business message data, dividing each target business message data whose message attribute category is a deduplication category into a deduplication category message group, and dividing each target business message data whose message attribute type is a merging category into a merging category message group; in the deduplication category message group, dividing the target business message data with the same grouping attribute information into the same deduplication group, and deduplicating each target business message data with the same deduplication unique identifier in each deduplication group. , retain the target business message data with the earliest message timestamp to obtain the message deduplication result; in the merged message group, divide the target business message data with the same grouping attribute information into the same merged group, and divide each target business message data in each merged group into the corresponding merged type group according to the positive and negative hedging relationship of the operation type, and deduplicate the adjacent target business message data with the same deduplication unique identifier in each merged type group, and after deduplication, perform hedging processing according to the positive and negative properties of the operation types of each target business message data in the merged type group to obtain the message merging result; combine the message deduplication result and the message merging result into a target message set; sort each target business message data in the target message set in ascending order according to the message timestamp, and push each target business message data in the target message set to the target business processing queue in sequence according to the sorted order. The present invention adopts the idea of summary algorithm for deduplication, uses delayed task queue, and performs timestamp order-keeping processing to realize deduplication and merging of message data, thereby filtering out effective message content, while ensuring that business execution and dependency relationships remain unchanged, thereby helping to improve downstream business processing efficiency.
[0087] Optional, in the above Figure 2 On the basis of one or more corresponding embodiments, determining the message attribute category of the target business message data according to the operation type of the target business message data may specifically include:
[0088] When the operation type of the target business message data is the first preset operation, the message attribute category of the target business message data is determined to be a deduplication category, wherein the first preset operation includes adding, modifying, and reviewing. When the operation type of the target business message data is the second preset operation, the message attribute category of the target business message data is determined to be a merge category, wherein the second preset operation includes going online, going offline, deleting, and restoring.
[0089] Specifically, an embodiment of the present invention can determine the message attribute category of the target business message data with operation types of adding, modifying and passing review as a deduplication category, which means that when processing these operations, special attention needs to be paid to repeatability to ensure that the same operation is not repeated or the same data is not repeatedly inserted in downstream processing.
[0090] Specifically, the embodiment of the present invention can determine the message attribute category of the target business message data whose operation types are online, offline, delete and restore as a merge class, which indicates that when processing these operations, multiple related messages or operations may need to be merged to ensure the consistency of the final state. For example, fast online and offline operations may need to be merged to prevent unnecessary fluctuations in the system.
[0091] Through clear classification and processing strategies, the embodiments of the present invention enable the system to better cope with concurrent operations, reduce potential problems caused by repeated or conflicting operations, improve overall reliability and stability, and enable users to experience faster and more consistent system responses. In particular, when operations involve approval and status changes, the system can provide a smoother experience.
[0092] Optional, in the above Figure 2 On the basis of one or more corresponding embodiments, each target business message data in each merged group is divided into a corresponding merged type group according to the positive and negative hedging relationship of the operation type, including:
[0093] The target business message data with the operation type of going online or going offline in the same merge group is divided into the first merge type group.
[0094] In the merge group, all operations involving online or offline operations are classified into the first merge type group. Such operations usually involve changes in the status of resources or services, and may need to be merged to ensure that there is only one unified status in the end under multiple similar requests.
[0095] The target business message data with the operation type of deletion or restoration in the same merge group is divided into the second merge type group.
[0096] Within the merge group, all operations involving deletion or restoration are grouped into the second merge type group. This type of operation involves the existence of resources, so it requires special handling to avoid problems such as accidental deletion or repeated restoration.
[0097] The embodiments of the present invention can effectively reduce conflicts between different operations by grouping different operation types. For example, the operations of going online and offline focus more on the switching of states, while the operations of deleting and restoring focus on the existence of resources. Processing them separately can reduce the complexity caused by different operation types. At the same time, through reasonable grouping and merging strategies, data consistency can be better maintained to ensure that the final operation results accurately reflect business needs.
[0098] Optional, in the above Figure 2 On the basis of one or more corresponding embodiments, when the operation type of the target business message data is online or restored, a positive identifier is added to the target business message data; when the operation type of the target business message data is offline or deleted, a negative identifier is added to the target business message data, and after deduplication, hedging processing is performed according to the positive and negative nature of the operation types of each target business message data in the merge type group, which may specifically include:
[0099] The hedging value of the merge type group is calculated by using the positive or negative identifier carried by each target business message data in the merge type group after deduplication; when the hedging value is 1, the target business message data retained by the merge type group is a forward operation type; when the hedging value is -1, the target business message data retained by the merge type group is a reverse operation type; when the hedging value is 0, the merge type group is empty.
[0100] The embodiment of the present invention simplifies the complex decision-making process by converting the operation of the message into the calculation of the hedging value, and can quickly determine the type of operation that needs to be performed in the end. At the same time, through accurate positive and negative marking and hedging calculation, the positive and negative nature of the operation can be reflected, ensuring the consistency of the system state and the business logic.
[0101] Optionally, the message data attribute information provided by the embodiment of the present invention also includes the service type and service ID of the target service message data. Figure 2 The method shown, such as Figure 5 As shown, a flow chart of another implementation of a message data processing method provided by an embodiment of the present invention is shown. Before step S100, the method may further include:
[0102] S200: Monitor the original business message data pushed by the upstream business producer at the current moment.
[0103] Specifically, the embodiment of the present invention can start a thread as an intermediate intervention consumer at the change message consumption end to monitor the business message data pushed by the upstream business producer to ensure that the business message data can be captured and processed in the first time.
[0104] S210: parse out the service type, service ID, operation type and message identifier of the original service message data.
[0105] The business type is an identifier of the business category to which the target business message data belongs, and is used to distinguish different types of business. The business type of the target business message data is based on the business of each business system itself. For example, the media asset management system refers to: video, collection, playlist, star, etc.
[0106] Among them, the business ID (Business Identifier) is an identifier used to uniquely identify a specific business entity, that is, a unique identification ID corresponding to each business type. For example, when the business type is video, the business ID represents the video ID. When the business type is collection, the business ID represents the collection ID, etc.
[0107] S220. Assign the current time to the message timestamp of the original business message data.
[0108] The embodiments of the present invention can add a message timestamp to the service message data and record its receiving time so as to perform time-related processing or sorting.
[0109] S230. Generate a deduplicated unique identifier for the original business message data using the business ID and operation type of the original business message data.
[0110] The embodiment of the present invention generates a deduplication unique identifier for deduplication processing, ensuring that duplicate messages of the same operation type will not be processed repeatedly.
[0111] S240: Generate a cache unique identifier for the original business message data using the business type and business ID of the original business message data.
[0112] The cache unique identifier is an identifier used to uniquely identify a data record in the cache system, that is, a group ID. The embodiment of the present invention can concatenate the service type and service ID of the original service message data to obtain the cache unique identifier of the original service message data.
[0113] S250. Query in the specified memory database whether there is a cache unique identifier. If yes, execute step S260; if not, execute step S270.
[0114] S260: Set the cache unique identifier as the grouping attribute information of the original business message data to obtain the target business message data.
[0115] The embodiment of the present invention uses the cache unique identifier as a grouping attribute of the service message data to facilitate subsequent grouping operations.
[0116] S270. Store the cache unique identifier in the specified memory database and execute step S260.
[0117] The embodiment of the present invention sets the message timestamp, grouping attribute information and deduplication unique identifier of the business message data, which helps to quickly group, deduplicate and merge the message data in subsequent message data processing, thereby improving the efficiency of message data processing and downstream business processing.
[0118] Optional, in the above Figure 5 Based on one or more corresponding embodiments, the service ID and operation type of the original service message data are used to generate a deduplicated unique identifier of the original service message data, which may specifically include:
[0119] The business ID of the target business message data and the attribute name and attribute value of the operation type are concatenated to obtain a business attribute string; a hash value of the business attribute string is calculated, and the hash value is confirmed as a deduplicated unique identifier of the target business message data.
[0120] The embodiment of the present invention can sort the attribute names and attribute values of the service ID and operation type of the target service message data, and splice them in the sorting order to form an ordered string containing the attribute names and attribute values of the service ID and operation type. Figure 2 The message data attribute information shown has a corresponding business attribute string of "businessld150779920optType1". Next, the business attribute string is hashed using the MD5 message digest algorithm to generate a 32-bit fixed-length hash value. Finally, the generated hash value is set as the deduplicated unique identifier of the business message data.
[0121] The embodiment of the present invention can quickly determine the duplication between different messages by generating a unique hash value as a deduplication identifier, and can quickly identify and eliminate duplicate business message data in large-scale data processing, thereby improving the processing efficiency of the system. At the same time, it avoids using the overall message body content of the business message data as the basis for deduplication, which causes the problem of being unable to deduplicate.
[0122] Although operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order.Multitasking and parallel processing may be advantageous under certain circumstances.
[0123] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.
[0124] Corresponding to the above method embodiment, the embodiment of the present invention also provides a message data processing device, whose structure is as follows: Figure 6 As shown, it may include: a target business message data acquisition unit 10, a message attribute category classification unit 20, a message deduplication result acquisition unit 30, a message merging result acquisition unit 40, a target message set acquisition unit 50 and a message pushing unit 60.
[0125] The target business message data acquisition unit 10 is used to obtain a preset number of target business message data from a specified message queue at a preset time interval, wherein the target business message data includes message data attribute information, and the message data attribute information includes the operation type, message identifier, message timestamp, grouping attribute information and deduplication unique identifier of the target business message data.
[0126] The message attribute category division unit 20 is used to determine the message attribute category of the target business message data according to the operation type of the target business message data, and to divide each target business message data whose message attribute category is the deduplication category into a deduplication category message group, and to divide each target business message data whose message attribute type is the merging category into a merging category message group.
[0127] The message deduplication result obtaining unit 30 is used to divide the target business message data with the same grouping attribute information into the same deduplication group in the deduplication message group, and deduplicate each target business message data with the same deduplication unique identifier in each deduplication group, retain the target business message data with the earliest message timestamp, and obtain the message deduplication result.
[0128] The message merging result obtaining unit 40 is used to divide the target business message data with the same grouping attribute information into the same merged group in the merged message group, and divide each target business message data in each merged group into a corresponding merged type group according to the positive and negative hedging relationship of the operation type, and deduplicate the adjacent target business message data with the same deduplication unique identifier in each merged type group. After deduplication, hedging processing is performed according to the positive and negative hedging of the operation type of each target business message data in the merged type group to obtain the message merging result.
[0129] The target message set obtaining unit 50 is used to combine the message deduplication result and the message merging result into a target message set.
[0130] The message pushing unit 60 is used to sort each target service message data in the target message set in ascending order according to the message timestamp, and push each target service message data in the target message set to the target service processing queue in the sorted order.
[0131] Optional, operation types include add, modify, approve, go online, go offline, delete, and restore.
[0132] Optionally, the message attribute category division unit 20 can be specifically used to determine the message attribute category of the target business message data as a deduplication category when the operation type of the target business message data is a first preset operation, wherein the first preset operation includes adding, modifying and reviewing; and to determine the message attribute category of the target business message data as a merge category when the operation type of the target business message data is a second preset operation, wherein the second preset operation includes going online, going offline, deleting and restoring.
[0133] Optionally, the message merging result obtaining unit 40 can be specifically used to classify the target business message data with the operation type of going online or going offline in the same merged group into a first merged type group; and classify the target business message data with the operation type of deleting or restoring in the same merged group into a second merged type group.
[0134] Optionally, the message data processing device may further include an identification adding unit.
[0135] The identification adding unit is used to add a positive identification to the target business message data when the operation type of the target business message data is online or restored; and to add a negative identification to the target business message data when the operation type of the target business message data is offline or deleted.
[0136] The message merging result obtaining unit 40 can be specifically used to calculate the hedging value of the merge type group by utilizing the positive identifier or negative identifier carried by each target business message data in the merge type group after deduplication; when the hedging value is 1, the target business message data retained by the merge type group is a forward operation type; when the hedging value is -1, the target business message data retained by the merge type group is a reverse operation type; when the hedging value is 0, the merge type group is empty.
[0137] Optionally, the message data attribute information provided by the embodiment of the present invention also includes the business type and business ID of the target business message data. The message data processing device may also include a business message data monitoring unit, a business message data parsing unit, a message timestamp assignment unit, a deduplication unique identifier generation unit, a cache unique identifier generation unit, a cache unique identifier query unit, a group attribute information setting unit and a cache unique identifier storage unit.
[0138] The service message data monitoring unit is used to monitor the original service message data pushed by the upstream service producer at the current moment before the target service message data acquisition unit 10 acquires a preset amount of target service message data from the designated message queue at a preset time interval.
[0139] The business message data parsing unit is used to parse out the business type, business ID, operation type and message identifier of the original business message data.
[0140] The message timestamp assignment unit is used to assign the current time to the message timestamp of the original business message data.
[0141] The deduplication unique identifier generating unit is used to generate a deduplication unique identifier for the original business message data by using the business ID and operation type of the original business message data.
[0142] The cache unique identifier generating unit is used to generate a cache unique identifier of the original service message data by using the service type and service ID of the original service message data.
[0143] The cache unique identifier query unit is used to query whether the cache unique identifier exists in the specified memory database. If yes, the group attribute information setting unit is triggered; if not, the cache unique identifier storage unit is triggered.
[0144] The group attribute information setting unit is used to set the cache unique identifier as the group attribute information of the original service message data to obtain the target service message data.
[0145] The cache unique identifier storage unit is used to store the cache unique identifier in a specified memory database and trigger the group attribute information setting unit.
[0146] Optionally, a deduplicated unique identifier generation unit is specifically used to concatenate the attribute name and attribute value of the business ID and operation type of the target business message data to obtain a business attribute string; calculate the hash value of the business attribute string, and confirm the hash value as the deduplicated unique identifier of the target business message data.
[0147] The present invention provides a message data processing device, which is used to: obtain a preset number of target business message data from a designated message queue at a preset time interval, wherein the target business message data includes message data attribute information, and the message data attribute information includes an operation type, a message identifier, a message timestamp, grouping attribute information and a deduplication unique identifier of the target business message data; determine the message attribute category of the target business message data based on the operation type of the target business message data, divide each target business message data whose message attribute category is a deduplication category into a deduplication category message group, and divide each target business message data whose message attribute type is a merging category into a merging category message group; in the deduplication category message group, divide the target business message data with the same grouping attribute information into the same deduplication group, and deduplicate each target business message data with the same deduplication unique identifier in each deduplication group. , retain the target business message data with the earliest message timestamp to obtain the message deduplication result; in the merged message group, divide the target business message data with the same grouping attribute information into the same merged group, and divide each target business message data in each merged group into the corresponding merged type group according to the positive and negative hedging relationship of the operation type, and deduplicate the adjacent target business message data with the same deduplication unique identifier in each merged type group, and after deduplication, perform hedging processing according to the positive and negative properties of the operation types of each target business message data in the merged type group to obtain the message merging result; combine the message deduplication result and the message merging result into a target message set; sort each target business message data in the target message set in ascending order according to the message timestamp, and push each target business message data in the target message set to the target business processing queue in sequence according to the sorted order. The present invention adopts the idea of summary algorithm for deduplication, uses delayed task queue, and performs timestamp order-keeping processing to realize deduplication and merging of message data, thereby filtering out effective message content, while ensuring that business execution and dependency relationships remain unchanged, thereby helping to improve downstream business processing efficiency.
[0148] Regarding the device in the above embodiment, the specific manner in which each unit performs the operation has been described in detail in the embodiment of the method, and will not be elaborated here.
[0149] The message data processing device includes a processor and a memory. The above-mentioned target business message data acquisition unit 10, message attribute category division unit 20, message deduplication result acquisition unit 30, message merging result acquisition unit 40, target message set acquisition unit 50 and message push unit 60 are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.
[0150] The processor contains a kernel, which calls the corresponding program unit from the memory. One or more kernels can be set. By adjusting the kernel parameters, the digest algorithm is used for deduplication and the timestamp is used for order preservation to achieve deduplication and merging of message data, while ensuring that business execution and dependencies remain unchanged, which helps to improve the efficiency of downstream business processing.
[0151] An embodiment of the present invention provides a computer-readable storage medium on which a program is stored. When the program is executed by a processor, the message data processing method is implemented.
[0152] An embodiment of the present invention provides a processor, which is used to run a program, wherein the message data processing method is executed when the program is running.
[0153] like Figure 7 As shown, an embodiment of the present invention provides an electronic device 1000, which includes at least one processor 1001, at least one memory 1002 connected to the processor 1001, and a bus 1003; wherein the processor 1001 and the memory 1002 communicate with each other through the bus 1003; the processor 1001 is used to call the program instructions in the memory 1002 to execute the above-mentioned message data processing method. The electronic device in this article can be a server, a PC, a PAD, a mobile phone, etc.
[0154] The present invention also provides a computer program product, which, when executed on an electronic device, is suitable for executing a program of initializing the steps of the message data processing method.
[0155] The present invention is described with reference to flowcharts and / or block diagrams of methods, apparatuses, electronic devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable device to generate a machine, so that the instructions executed by the processor of the computer or other programmable device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0156] In a typical configuration, an electronic device includes one or more processors (CPU), a memory, and a bus. The electronic device may also include an input / output interface, a network interface, and the like.
[0157] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip. The memory is an example of a computer-readable medium.
[0158] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0159] In the description of the present invention, it should be understood that the terms "up", "down", "front", "back", "left" and "right" etc. indicating directions or positional relationships are based on the directions or positional relationships shown in the accompanying drawings. They are only for the convenience of describing the present invention and simplifying the description. They do not indicate or imply that the positions or elements referred to must have specific directions, be constructed and operate in specific directions. Therefore, they should not be understood as limitations of the present invention.
[0160] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. It should also be noted that the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0161] It should be understood by those skilled in the art that the embodiments of the present invention may be provided as methods, systems or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware aspects. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0162] The above are only embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent substitution, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.
Claims
1. A message data processing method, characterized in that: include: Obtaining a preset number of target business message data from a specified message queue at a preset time interval, wherein the target business message data includes message data attribute information, and the message data attribute information includes an operation type, a message identifier, a message timestamp, grouping attribute information, and a deduplication unique identifier of the target business message data; According to the operation type of the target business message data, determine the message attribute category of the target business message data, divide each of the target business message data whose message attribute category is the deduplication category into a deduplication category message group, and divide each of the target business message data whose message attribute type is the merging category into a merging category message group; In the deduplication class message group, the target business message data with the same grouping attribute information are divided into the same deduplication group, and each target business message data with the same deduplication unique identifier in each deduplication group is deduplicated respectively, and the target business message data with the earliest message timestamp is retained to obtain a message deduplication result; In the merged message group, the target business message data with the same grouping attribute information are divided into the same merged group, and according to the positive and negative hedging relationship of the operation type, each target business message data in each merged group is divided into a corresponding merged type group, and adjacent target business message data with the same deduplication unique identifier in each merged type group are deduplicated. After deduplication, hedging processing is performed according to the positive and negative hedging of the operation type of each target business message data in the merged type group to obtain a message merging result; Combining the message deduplication result and the message merging result into a target message set; The target service message data in the target message set are sorted in ascending order according to the message timestamp, and the target service message data in the target message set are pushed to the target service processing queue in sequence according to the sorted order.
2. The method according to claim 1, characterized in that The operation types include adding, modifying, reviewing and passing, going online, going offline, deleting and restoring.
3. The method according to claim 2, characterized in that The determining, according to the operation type of the target service message data, the message attribute category of the target service message data comprises: In a case where the operation type of the target business message data is a first preset operation, determining that the message attribute category of the target business message data is a deduplication category, wherein the first preset operation includes adding, modifying, and reviewing and passing; When the operation type of the target business message data is a second preset operation, the message attribute category of the target business message data is determined to be a merge category, wherein the second preset operation includes going online, going offline, deleting, and restoring.
4. The method according to claim 2, characterized in that: The target business message data in each merged group is divided into corresponding merged type groups according to the positive and negative hedging relationship of the operation type, including: Classify the target business message data whose operation type is online or offline in the same merged group into a first merged type group; The target business message data whose operation type is deletion or restoration in the same merged group is divided into a second merged type group.
5. The method according to claim 2, characterized in that: When the operation type of the target business message data is online or restored, a positive identifier is added to the target business message data; when the operation type of the target business message data is offline or deleted, a negative identifier is added to the target business message data, and after deduplication, hedging processing is performed according to the positive and negative properties of the operation types of each target business message data in the merge type group, including: Calculate the hedging value of the merged type group by using the positive identifier or negative identifier carried by each target business message data in the merged type group after deduplication; When the hedging value is 1, the target business message data retained by the merge type group is a forward operation type; When the hedging value is -1, the target business message data retained by the merge type group is a reverse operation type; When the hedge value is 0, the consolidation type group is empty.
6. The method according to any one of claims 1 to 5, characterized in that The message data attribute information also includes the service type and service ID of the target service message data. Before obtaining a preset number of target service message data from a specified message queue at a preset time interval, the method further includes: Monitor the original service message data pushed by the upstream service producer at the current moment; Parsing the original service message data to obtain the service type, service ID, operation type and message identifier; Assigning the current time to the message timestamp of the original service message data; Generate a deduplicated unique identifier for the original business message data using the business ID and operation type of the original business message data; Generate a cache unique identifier for the original service message data using the service type and service ID of the original service message data; A query is made in the designated memory database as to whether the cache unique identifier exists. If yes, the cache unique identifier is set as the grouping attribute information of the original business message data to obtain the target business message data. If not, the cache unique identifier is stored in the designated memory database, and the step of setting the cache unique identifier as the grouping attribute information of the original business message data to obtain the target business message data is executed.
7. The method according to claim 6, characterized in that The generating a deduplicated unique identifier of the original business message data by using the business ID and the operation type of the original business message data comprises: Concatenate the service ID of the target service message data with the attribute name and attribute value of the operation type to obtain a service attribute string; A hash value of the service attribute character string is calculated, and the hash value is confirmed as the deduplicated unique identifier of the target service message data.
8. A message data processing device, characterized in that: include: target business message data acquisition unit, message attribute classification unit, merged message classification unit, message deduplication result acquisition unit, message merging result acquisition unit, target message set acquisition unit and message push unit, The target business message data acquisition unit is used to acquire a preset number of target business message data from a specified message queue at a preset time interval, wherein the target business message data includes message data attribute information, and the message data attribute information includes an operation type, a message identifier, a message timestamp, grouping attribute information, and a deduplication unique identifier of the target business message data; The message attribute category division unit is used to determine the message attribute category of the target business message data according to the operation type of the target business message data, and divide each of the target business message data whose message attribute category is the deduplication category into a deduplication category message group, and divide each of the target business message data whose message attribute type is the merging category into a merging category message group; The message deduplication result obtaining unit is used to divide the target business message data having the same grouping attribute information into the same deduplication group in the deduplication class message group, deduplicate the target business message data having the same deduplication unique identifier in each deduplication group, retain the target business message data having the earliest message timestamp, and obtain the message deduplication result; The message merging result obtaining unit is used to divide the target business message data having the same grouping attribute information into the same merged group in the merged message group, and divide each target business message data in each merged group into a corresponding merged type group according to the positive and negative hedging relationship of the operation type, and deduplicate adjacent target business message data having the same deduplication unique identifier in each merged type group, and after deduplication, perform hedging processing according to the positive and negative hedging of the operation type of each target business message data in the merged type group to obtain a message merging result; The target message set obtaining unit is used to combine the message deduplication result and the message merging result into a target message set; The message pushing unit is used to sort each of the target business message data in the target message set in ascending order according to the message timestamp, and push each of the target business message data in the target message set to the target business processing queue in the sorted order.
9. A computer-readable storage medium having a program stored thereon, characterized in that: When the program is executed by a processor, the message data processing method according to any one of claims 1 to 7 is implemented.
10. An electronic device, comprising at least one processor, and at least one memory and a bus connected to the processor; wherein: The processor and the memory communicate with each other via the bus; The processor is used to call the program instructions in the memory to execute the message data processing method according to any one of claims 1 to 7.
Citation Information
Patent Citations
Method, device and system for processing messages
CN103209153A
Network communication method and device, equipment and storage medium
CN115190173A
Message processing method and device, medium and electronic equipment
CN117201437A
Cited By
Timestamp-based data change intelligent deduplication and message simplification method and system
CN120578653A
