Data processing method and device, computer device, and storage medium

By splitting business data and using multi-threaded parallel processing, the data conflict problem in a multi-threaded environment was solved, improving data processing efficiency and stability.

CN117131121BActive Publication Date: 2026-03-27BOOMING TECH (HANGZHOU) CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-09-08
Publication Date
2026-03-27

AI Technical Summary

Technical Problem

In a multithreaded environment, when multiple threads access the same data resource simultaneously, data conflicts can easily occur, leading to reduced data processing efficiency.

Method used

By splitting the business data, multiple logically independent business sub-data are obtained, and multi-threading is used for parallel processing to avoid data conflicts.

Benefits of technology

It simplifies business execution logic, improves data processing efficiency, avoids data contention, and enhances the stability of multi-threaded data processing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117131121B_ABST
    Figure CN117131121B_ABST
Patent Text Reader

Abstract

The application provides a data processing method and device, computer equipment and a storage medium, and belongs to the technical field of computers. The method comprises the following steps: collecting business data based on an interaction layer of a target application, the interaction layer being used for receiving operations, and the business data being data generated based on operations on an application interface of the target application; splitting the business data according to the business logic of a business associated with the business data based on a conversion layer of the target application to obtain a plurality of business sub-data, the conversion layer being used for data conversion, and the business logic of the plurality of business sub-data being independent of each other; and performing parallel processing on the plurality of business sub-data based on an engine layer of the target application through multi-threading to obtain a plurality of response sub-data of the business data. The above technical solution can avoid data conflict by performing parallel processing on the plurality of business sub-data through multi-threading.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a data processing method, apparatus, computer equipment, and storage medium. Background Technology

[0002] With the development of computer technology, multithreaded data reading and writing operations can greatly improve data processing efficiency. However, in a multithreaded environment, data conflicts can occur when multiple threads access the same data resource simultaneously. Therefore, how to avoid data conflicts in a multithreaded environment is a technical problem that needs to be solved.

[0003] In related technologies, when multiple threads access the same data resource simultaneously, the data resource is typically locked. This ensures that only one thread can access the data resource at a time, while other threads must wait for the lock to release the lock before proceeding. This effectively avoids data conflicts caused by multiple threads operating on the same resource concurrently.

[0004] However, in the above scheme, when data resources are locked, other threads can only access the data resources after the locking thread releases the data resources, which reduces the efficiency of data processing. Summary of the Invention

[0005] This application provides a data processing method, apparatus, computer device, and storage medium. By using multi-threading to process multiple business sub-data in parallel, it simplifies the execution logic of business processes and avoids data conflicts. The technical solution is as follows:

[0006] On the one hand, a data processing method is provided, the method comprising:

[0007] Based on the interaction layer of the target application, business data is collected. The target application is any application in the terminal. The interaction layer is used to receive operations. The business data is data generated based on the operations on the application interface of the target application.

[0008] Based on the conversion layer of the target application, the business data is split into multiple business sub-data according to the business logic of the business associated with the business data. The conversion layer is used for data transfer, and the business logic of the multiple business sub-data is independent of each other.

[0009] Based on the engine layer of the target application, multiple business sub-data are processed in parallel through multi-threading to obtain multiple response sub-data of the business data. The engine layer is used to perform logical processing on the data, and the multiple response sub-data corresponds one-to-one with the multiple business sub-data.

[0010] On the other hand, a data processing apparatus is provided, the apparatus comprising:

[0011] The data acquisition module is used to collect business data based on the interaction layer of the target application, wherein the target application is any application in the terminal, the interaction layer is used to receive operations, and the business data is data generated based on the operations on the application interface of the target application.

[0012] The splitting module is used to split the business data according to the business logic of the business associated with the business data based on the conversion layer of the target application, so as to obtain multiple business sub-data. The conversion layer is used for data transfer, and the business logic of the multiple business sub-data is independent of each other.

[0013] The processing module is used to process the multiple business sub-data in parallel through multi-threading based on the engine layer of the target application to obtain multiple response sub-data of the business data. The engine layer is used to perform logical processing on the data, and the multiple response sub-data corresponds one-to-one with the multiple business sub-data.

[0014] In some embodiments, the splitting module includes:

[0015] The first determining unit is used to determine, based on the conversion layer, the number of business logics contained in the business data from the business logics of the business associated with the business data;

[0016] The splitting unit is used to split the business data to obtain the multiple business sub-data when the quantity is greater than the quantity threshold.

[0017] In some embodiments, the first determining unit is further configured to determine the data type of the business data based on the conversion layer;

[0018] The splitting unit is further configured to split the business data according to the business logic, when the data type is a preset data type, to obtain the multiple business sub-data.

[0019] In some embodiments, the apparatus further includes:

[0020] The determination module is used to determine the data synchronization method of the plurality of response sub-data based on the real-time requirements of the business data. The data synchronization method includes a first data synchronization method and a second data synchronization method. The first data synchronization method is used to synchronize data with high real-time requirements, and the second data synchronization method is used to synchronize data with low real-time requirements.

[0021] The synchronization module is used to synchronize the multiple response sub-data from the engine layer to the interaction layer based on the conversion layer and through the data synchronization method.

[0022] In some embodiments, the synchronization module includes:

[0023] The second determining unit is used to determine the data volume of the business data when the data synchronization method is the first data synchronization method;

[0024] The acquisition unit is configured to acquire the plurality of response sub-data from the engine layer based on the conversion layer, provided that the amount of data is not greater than a quantity threshold.

[0025] The merging unit is used to merge the multiple response sub-data according to the business logic of the business associated with the business data based on the conversion layer, so as to obtain the response data of the business data;

[0026] A synchronization unit is used to synchronize the response data to the interaction layer based on the conversion layer.

[0027] In some embodiments, the second determining unit is further configured to, based on the engine layer, determine at least one target response sub-data from the plurality of response sub-data when the data volume is greater than the quantity threshold, wherein the target response sub-data is data to be synchronized to the interaction layer from the plurality of response data;

[0028] The acquisition unit is further configured to acquire the at least one target response sub-data from the engine layer based on the conversion layer;

[0029] The merging unit is further configured to merge the at least one target response sub-data based on the conversion layer and according to the business logic of the business associated with the business data, to obtain the response data of the business data;

[0030] The synchronization unit is also used to synchronize the response data to the interaction layer based on the conversion layer.

[0031] In some embodiments, the acquiring unit includes:

[0032] The first acquisition subunit is used to acquire at least one data identifier from the engine layer based on the conversion layer, the data identifier being used to indicate data to be synchronized to the interaction layer;

[0033] The second acquisition subunit is used to acquire the at least one target response subdata indicated by the at least one data identifier from the plurality of response subdata.

[0034] In some embodiments, the acquisition unit is further configured to, when the data synchronization method is the second data synchronization method, acquire a target number of response sub-data from the engine layer every X seconds based on the conversion layer, where X is a positive number;

[0035] The merging unit is further configured to, in response to the completion of the acquisition of the plurality of response sub-data, merge the plurality of response sub-data according to the business logic of the business associated with the business data based on the conversion layer, to obtain the response data of the business data;

[0036] The synchronization unit is also used to synchronize the response data to the interaction layer based on the conversion layer.

[0037] In some embodiments, the synchronization unit includes:

[0038] A conversion subunit is used to convert the data type of the response data into a target data type based on the conversion layer, wherein the target data type is the data type of the data in the interaction layer;

[0039] The synchronization subunit is used to synchronize the response data to the interaction layer based on the conversion layer.

[0040] On the other hand, a computer device is provided, the computer device including a processor and a memory, the memory being used to store at least one computer program, the at least one computer program being loaded and executed by the processor to implement the data processing method in the embodiments of this application.

[0041] On the other hand, a computer-readable storage medium is provided, wherein at least one computer program is stored in the computer-readable storage medium, the at least one computer program being loaded and executed by a processor to implement the data processing method as described in the embodiments of this application.

[0042] On the other hand, a computer program product is provided, including a computer program stored in a computer-readable storage medium, a processor of a computer device reading the computer program from the computer-readable storage medium, and the processor executing the computer program, causing the computer device to perform the data processing methods provided in the above-described aspects or various alternative implementations of the aspects.

[0043] This application provides a data processing method that, based on the conversion layer of a target application, can decompose business data collected from the interaction layer of the target application into multiple business sub-data with independent business logic. Based on the engine layer of the target application, multiple business sub-data are processed in parallel using multi-threading, which simplifies the execution logic of the business and improves the processing efficiency of business data. Furthermore, since the business logic associated with each business sub-data is independent, the multiple threads used to process multiple business sub-data in parallel will not experience data contention, thereby avoiding data conflict problems. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 This is a schematic diagram of the implementation environment of a data processing method provided in an embodiment of this application;

[0046] Figure 2 This is a flowchart of a data processing method provided according to an embodiment of this application;

[0047] Figure 3 This is a flowchart of another data processing method provided according to an embodiment of this application;

[0048] Figure 4 This is a flowchart of a data synchronization process provided according to an embodiment of this application;

[0049] Figure 5 This is a block diagram of a data processing apparatus provided according to an embodiment of this application;

[0050] Figure 6 This is a block diagram of another data processing apparatus provided according to an embodiment of this application;

[0051] Figure 7 This is a schematic diagram of the structure of a terminal according to an embodiment of this application. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0053] In this application, the terms "first," "second," etc., are used to distinguish identical or similar items with essentially the same function. It should be understood that there is no logical or temporal dependency between "first," "second," and "nth," nor are there any restrictions on quantity or execution order.

[0054] In this application, the term "at least one" means one or more, and "multiple" means two or more.

[0055] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the business data involved in this application were all obtained with full authorization.

[0056] The data processing method provided in this application can be executed by a terminal. In some embodiments, the computer device is the terminal. The following describes the implementation environment of the data processing method provided in this application, using a computer device as an example. Figure 1 This is a schematic diagram illustrating the implementation environment of a data processing method provided in an embodiment of this application. See also... Figure 1 The implementation environment includes terminal 101 and server 102. Terminal 101 and server 102 can be connected directly or indirectly via wired or wireless communication, which is not limited herein.

[0057] In some embodiments, terminal 101 may be a smartphone, tablet computer, laptop computer, desktop computer, smart speaker, smartwatch, smart voice interaction device, smart home appliance, in-vehicle terminal, etc., but is not limited to these. Terminal 101 has a target application installed and running. Illustratively, terminal 101 is a terminal used by a user, who can perform various operations on the application interface of the target application installed on terminal 101. Terminal 101 can process various data in response to user-triggered operations.

[0058] In some embodiments, server 102 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), big data, and artificial intelligence platforms. Server 102 is used to provide backend services for the target application.

[0059] In some embodiments, server 102 undertakes the main computing work and terminal 101 undertakes the secondary computing work; or, server 102 undertakes the secondary computing work and terminal 101 undertakes the main computing work; or, server 102 and terminal 101 collaborate on computing using a distributed computing architecture.

[0060] Figure 2 This is a flowchart of a data processing method provided according to an embodiment of this application. See also... Figure 2 In this embodiment, the method is described using an execution method performed by a terminal as an example. The data processing method includes the following steps:

[0061] 201. Based on the interaction layer of the target application, business data is collected. The target application is any application in the terminal. The interaction layer is used to receive operations. The business data is the data generated by the operations on the application interface of the target application.

[0062] In this embodiment, the target application can be any application on the terminal, such as a social application, a shopping application, a game application, etc., and this embodiment does not impose any limitations on this. The target application includes an interaction layer, a conversion layer, and an engine layer. The terminal can collect business data generated based on user operations on the target application's interface using the interaction layer. The interaction layer mainly refers to the interface of the target application that interacts with the user, i.e., the target application's interface. The interaction layer can receive user operations, as well as user-inputted data and display processed data required by the user. The conversion layer is used for data relay; that is, the terminal needs to use the conversion layer to achieve data interaction between the interaction layer and the engine layer. The engine layer is used to perform logical processing on the business data transmitted by the conversion layer to obtain response data for the business data.

[0063] 202. Based on the target application, the transformation layer splits the business data into multiple business sub-data according to the business logic of the business associated with the business data. The transformation layer is used to transfer the data, and the business logic of the multiple business sub-data is independent of each other.

[0064] In this embodiment, the conversion layer is used for data relay. Specifically, business data collected by the terminal based on the interaction layer needs to be processed by the conversion layer before being synchronized to the engine layer. Similarly, response data obtained by the terminal based on the engine layer after processing the business data also needs to be processed by the conversion layer before being synchronized to the interaction layer, which then displays it to the user. After receiving the business data collected by the interaction layer, the terminal can, based on the conversion layer, split the business data according to the business logic associated with the business data, obtaining multiple data blocks of appropriate size—that is, multiple business sub-data with independent business logic. Then, the terminal, based on the conversion layer, can send these multiple business sub-data to the engine layer for logical processing.

[0065] 203. Based on the target application's engine layer, multiple business sub-data are processed in parallel through multi-threading to obtain multiple response sub-data of the business data. The engine layer is used to perform logical processing on the data, and the multiple response sub-data corresponds one-to-one with the multiple business sub-data.

[0066] In this embodiment, the engine layer receives service data transmitted from the conversion layer and performs logical processing on the service data to obtain response data. After the terminal receives multiple service sub-data sent by the conversion layer based on the engine layer, the terminal can perform parallel processing on the multiple service sub-data through multi-threading based on the engine layer to obtain multiple response sub-data corresponding one-to-one with the multiple service sub-data.

[0067] This application provides a data processing method that, based on the conversion layer of a target application, can decompose business data collected from the interaction layer of the target application into multiple business sub-data with independent business logic. Based on the engine layer of the target application, multiple business sub-data are processed in parallel using multi-threading, which simplifies the execution logic of the business and improves the processing efficiency of business data. Furthermore, since the business logic associated with each business sub-data is independent, the multiple threads used to process multiple business sub-data in parallel will not experience data contention, thereby avoiding data conflict problems.

[0068] Figure 3 This is a flowchart of another data processing method provided according to an embodiment of this application, see [link / reference]. Figure 3 In this embodiment, the method is described using an execution method performed by a terminal as an example. The data processing method includes the following steps:

[0069] 301. Based on the interaction layer of the target application, business data is collected. The target application is any application in the terminal. The interaction layer is used to receive operations. The business data is the data generated by the operations on the application interface of the target application.

[0070] In this embodiment, the target application can be any application on the terminal, such as a social application, a shopping application, a game application, etc., and this embodiment does not impose any limitations on this. The target application includes an interaction layer, a conversion layer, and an engine layer. The terminal can collect business data generated based on user operations on the target application's interface using the interaction layer. The interaction layer mainly refers to the interface of the target application that interacts with the user, i.e., the target application's interface. The interaction layer can receive user operations, as well as user-inputted data and display processed data required by the user. The conversion layer is used for data relay; that is, the terminal needs to use the conversion layer to achieve data interaction between the interaction layer and the engine layer. The engine layer is used to perform logical processing on the business data transmitted by the conversion layer to obtain response data for the business data.

[0071] 302. Based on the target application, the transformation layer splits the business data into multiple business sub-data according to the business logic of the business associated with the business data. The transformation layer is used to transfer the data, and the business logic of the multiple business sub-data is independent of each other.

[0072] In this embodiment, the conversion layer is used for data relay. Specifically, business data collected by the terminal based on the interaction layer needs to be processed by the conversion layer before being synchronized to the engine layer. Similarly, response data obtained by the terminal based on the engine layer after processing the business data also needs to be processed by the conversion layer before being synchronized to the interaction layer, which then displays it to the user. After receiving the business data collected by the interaction layer, the terminal can, based on the conversion layer, split the business data according to the business logic associated with the business data, obtaining multiple data blocks of appropriate size—that is, multiple business sub-data with independent business logic. Then, the terminal, based on the conversion layer, can send these multiple business sub-data to the engine layer for logical processing.

[0073] In some embodiments, the terminal can split business data based on the conversion layer of the target application in the following two ways.

[0074] Method 1: The terminal determines whether to split the business data based on the amount of business logic it contains. Accordingly, the terminal, based on the transformation layer, determines the amount of business logic contained in the business data from the business logic of the business associated with it. If the number exceeds a threshold, the business data is split into multiple business sub-data. The terminal, based on the transformation layer, can determine the business logic of the business associated with the business data. Since the business data may only involve a portion of the business logic of the business associated with it, the terminal can determine the amount of business logic contained in the business data from the business logic of the business, that is, the amount of business logic that the terminal needs to execute when processing the business data based on the engine layer. When the amount of business logic exceeds the threshold, it indicates that the business data contains a large amount of business logic, and the business logic that the terminal needs to execute when processing the business data based on the engine layer is more complex. In this case, splitting the business data into multiple business sub-data simplifies the processing of the business logic and improves data processing efficiency.

[0075] Method 2: The terminal determines whether to split the business data based on its data type. Accordingly, the terminal, based on the transformation layer, determines the data type of the business data. If the data type is a preset data type, the terminal splits the business data according to the business logic, obtaining multiple business sub-data. Specifically, after receiving the business data, the terminal, based on the transformation layer, can detect the data type. If the data type is a preset data type, it indicates that the data volume is large or the real-time requirements are high. Therefore, the terminal can, based on the transformation layer, split the business data according to the business logic of the associated business, obtaining multiple business sub-data with independent business logic. By determining the data type of the business data, the terminal can split the business data when certain conditions are met, improving data processing efficiency.

[0076] 303. Based on the target application's engine layer, multiple business sub-data are processed in parallel through multi-threading to obtain multiple response sub-data of the business data. The engine layer is used to perform logical processing on the data, and the multiple response sub-data corresponds one-to-one with the multiple business sub-data.

[0077] In this embodiment, the engine layer receives service data transmitted from the conversion layer and performs logical processing on the service data to obtain response data. After the terminal receives multiple service sub-data sent by the conversion layer based on the engine layer, the terminal can perform parallel processing on the multiple service sub-data through multi-threading based on the engine layer to obtain multiple response sub-data corresponding one-to-one with the multiple service sub-data.

[0078] 304. Based on the real-time requirements of business data, determine the data synchronization methods for multiple response sub-data. The data synchronization methods include a first data synchronization method and a second data synchronization method. The first data synchronization method is used to synchronize data with high real-time requirements, and the second data synchronization method is used to synchronize data with low real-time requirements.

[0079] In this embodiment, the terminal can determine the data synchronization method for synchronizing multiple response sub-data from the engine layer to the interaction layer based on the real-time requirements of the business data. The data synchronization method includes a first data synchronization method and a second data synchronization method. The first data synchronization method is used to synchronize data with high real-time requirements, while the second data synchronization method is used to synchronize data with low real-time requirements. By employing different data synchronization methods based on the characteristics of the business data, the terminal synchronizes the response sub-data to the interactive interface, improving the operational efficiency of data synchronization.

[0080] 305. Based on the conversion layer, multiple response sub-data are synchronized from the engine layer to the interaction layer through data synchronization.

[0081] In this embodiment of the application, the terminal needs to synchronize the response data obtained by processing business data based on the engine layer to the interaction layer through the conversion layer. Therefore, the terminal can obtain multiple response sub-data obtained by parallel processing of multiple business sub-data from the engine layer based on the conversion layer, merge the multiple response sub-data, and synchronize the merged response data to the interaction layer.

[0082] In some embodiments, when the data synchronization method is the first data synchronization method, the terminal synchronizes multiple response sub-data from the engine layer to the interaction layer using the following method one; when the data synchronization method is the second data synchronization method, the terminal synchronizes multiple response sub-data from the engine layer to the interaction layer using the following method two.

[0083] Method 1: When the business data has high real-time requirements, the terminal can synchronize multiple response sub-data from the engine layer to the interaction layer using the first data synchronization method. Accordingly, when the data synchronization method is the first data synchronization method, the terminal determines the amount of business data; if the amount of data does not exceed a quantity threshold, it obtains multiple response sub-data from the engine layer based on the conversion layer; based on the conversion layer, according to the business logic associated with the business data, the multiple response sub-data are merged to obtain the response data of the business data; based on the conversion layer, the response data is synchronized to the interaction layer. In the case of the first data synchronization method, it indicates that the business data has very high real-time requirements. In this case, the terminal needs to immediately synchronize the response data of the business data from the engine layer to the interaction layer, which then displays it to the user. By determining the amount of business data, the terminal can identify the business data as a small amount of data with high real-time requirements, provided the amount of data does not exceed a quantity threshold. For this type of data, after processing and obtaining multiple response sub-data, the terminal can send a data synchronization task to the conversion layer based on the engine layer. Upon receiving the data synchronization task, the conversion layer immediately retrieves multiple response sub-data from the engine layer. Based on the rules used when splitting the business data—that is, the business logic associated with the business data—it merges these multiple response sub-data to obtain the response data. The terminal then transmits the response data to the interaction layer through the conversion layer, achieving data synchronization between the engine layer and the interaction layer.

[0084] In some embodiments, when the business data is large in volume and has high real-time requirements, the terminal can synchronize some response sub-data to the interaction layer. Correspondingly, when the data volume exceeds a threshold, the terminal, based on the engine layer, determines at least one target response sub-data from multiple response sub-data. The target response sub-data is the data to be synchronized to the interaction layer from the multiple response data. Based on the conversion layer, it obtains at least one target response sub-data from the engine layer. Based on the conversion layer, it merges the at least one target response sub-data according to the business logic of the business associated with the business data to obtain the response data of the business data. Based on the conversion layer, it synchronizes the response data to the interaction layer. Wherein, when the data volume exceeds the threshold, the terminal can determine that the business data is large in volume and has high real-time requirements. For this type of data, after processing and obtaining multiple response sub-data, the terminal can, based on the engine layer, determine the response sub-data to be synchronized to the interaction layer, i.e., the target response sub-data, from the multiple response sub-data. Then, the terminal, based on the engine layer, sends a data synchronization task to the conversion layer. After receiving the data synchronization task, the conversion layer can obtain the target response sub-data from multiple response sub-data from the engine layer. Based on the rules used when splitting the business data—that is, the business logic associated with the business data—it merges at least one target response sub-data to obtain the response data of the business data. By using the conversion layer to obtain partial response sub-data from the engine layer, the terminal can synchronize only the portion of the multiple response sub-data that truly needs to be synchronized to the interaction layer when the volume of business data is large, thereby improving the efficiency of data synchronization.

[0085] In some embodiments, the conversion layer can obtain response sub-data to be synchronized to the interaction layer from the engine layer based on data identifiers. Correspondingly, the terminal, based on the conversion layer, obtains at least one data identifier from the engine layer, the data identifier indicating the data to be synchronized to the interaction layer; and obtains at least one target response sub-data indicated by the at least one data identifier from multiple response sub-data. Specifically, the terminal can, based on the engine layer, determine the response sub-data to be synchronized to the interaction layer from multiple response sub-data of the business data, and send these response sub-data identifiers to the conversion layer. That is, the terminal can, based on the engine layer, send a data synchronization task carrying at least one data identifier to the conversion layer. Upon receiving the data synchronization task, the conversion layer can obtain the at least one data identifier and, based on the data identifier, obtain the target response sub-data indicated by the data identifier from multiple response sub-data of the engine layer. By obtaining the target response sub-data indicated by the data identifier from the engine layer based on the conversion layer, the terminal can synchronize the target response sub-data that truly needs to be synchronized to the interaction layer from multiple response sub-data when the amount of business data is large, thus improving the operational efficiency of data synchronization.

[0086] Method 2: When the business data has low real-time requirements, the terminal can synchronize multiple response sub-data from the engine layer to the interaction layer using a second data synchronization method. Accordingly, with the second data synchronization method, the terminal, based on the conversion layer, retrieves a target number of response sub-data from the engine layer every X seconds (X is a positive number). Once all multiple response sub-data have been retrieved, based on the conversion layer, the multiple response sub-data are merged according to the business logic associated with the business data to obtain the business data's response data. Based on the conversion layer, the response data is then synchronized to the interaction layer. In the case of the second data synchronization method, it indicates that the business data has low real-time requirements. In this case, the terminal does not need to immediately synchronize the business data's response data from the engine layer to the interaction layer for display to the user. Therefore, the terminal can retrieve the target number of response sub-data from the engine layer every X seconds based on the conversion layer until all multiple response sub-data for the business data have been retrieved. Then, the terminal merges multiple response sub-data according to the rules used when splitting the business data—that is, the business logic of the business associated with the business data—to obtain the response data of the business data. Finally, through the transformation layer, the response data is transmitted to the interaction layer, realizing data synchronization between the engine layer and the interaction layer. When the real-time requirements of the business data are not high, the terminal can reduce the performance consumption of the terminal during data synchronization and improve the stability of data synchronization between the interaction layer and the engine layer by periodically and in batches retrieving the response sub-data of the business data from the engine layer.

[0087] In some embodiments, before synchronizing the response data to the interaction layer, the terminal can convert the response data into the data required by the interaction layer based on the conversion layer before synchronizing it to the interaction layer. Accordingly, the terminal converts the data type of the response data to a target data type based on the conversion layer, where the target data type is the data type of the data in the interaction layer; then, it synchronizes the response data to the interaction layer based on the conversion layer. Specifically, the data type of the response data obtained by the terminal from the engine layer based on the conversion layer is the data type of the data in the engine layer, and the data type of the response data can be an integer. Therefore, when the terminal synchronizes the merged response data to the interaction layer based on the conversion layer, it needs to convert the data type of the response data. That is, the terminal can convert the data type of the response data to the data type of the data in the interaction layer, i.e., the target data type, which can be a string. Only then does the terminal synchronize the response data to the interaction layer based on the conversion layer.

[0088] Figure 4 This is a flowchart illustrating a data synchronization process according to an embodiment of this application. See also... Figure 4Taking Sequencer (a non-linear animation editor) as an example, the terminal first collects interaction layer data based on the Sequencer's interaction layer—that is, business data generated based on user actions on the Sequencer's application interface. Then, the terminal sends this interaction layer data to the conversion layer. The terminal uses the conversion layer to convert the data type of the interaction layer data to the data type required by the conversion layer, obtaining the conversion layer data. Next, based on the characteristics of the business data, the terminal determines whether to split the business data. For example, if the business data volume is large or the real-time requirements are high, the terminal splits the business data. In this case, the terminal, based on the conversion layer, splits the business data according to the business logic associated with the business, obtaining multiple business sub-data with independent business logic. Then, the split business sub-data is sent to the data synchronization task in the engine layer. When the engine executes the data synchronization task, it synchronizes the multiple business sub-data to the engine layer. If the business data is not split, the terminal can directly send the business data to the data synchronization task based on the conversion layer. After acquiring multiple business sub-data, the terminal can process these sub-data in parallel using multi-threading at the engine layer, obtaining multiple response sub-data corresponding one-to-one. Then, when the business data has high real-time requirements, the terminal can determine the data volume. If the business data is small, the terminal sends a data synchronization task to the conversion layer at the engine layer. Upon receiving this task, the conversion layer retrieves data from the engine layer, specifically multiple response sub-data, merges them to obtain the response data, and then converts it into interaction layer data for synchronization. When the business data is not small, the terminal, at the engine layer, determines the target response sub-data to be synchronized to the interaction layer from the multiple response sub-data. Then, the terminal sends a data synchronization task carrying a data identifier to the conversion layer at the engine layer. Upon receiving this task, the conversion layer obtains at least one data identifier and, based on the identifier, retrieves the target response sub-data indicated by the identifier from the multiple response sub-data at the engine layer. Then, at least one target response sub-data is merged to obtain the response data of the business data, and the response data is converted into interaction layer data and synchronized to the interaction layer. When the business data does not have high real-time requirements, the terminal, based on the conversion layer, periodically retrieves a target number of response sub-data from the engine layer in batches until all multiple response sub-data of the business data have been retrieved. Then, the terminal merges the multiple response sub-data to obtain the response data of the business data. Finally, through the conversion layer, the response data is converted into interaction layer data and synchronized to the interaction layer.

[0089] This application provides a data processing method that, based on the conversion layer of a target application, can decompose business data collected from the interaction layer of the target application into multiple business sub-data with independent business logic. Based on the engine layer of the target application, multiple business sub-data are processed in parallel using multi-threading, which simplifies the execution logic of the business and improves the processing efficiency of business data. Furthermore, since the business logic associated with each business sub-data is independent, the multiple threads used to process multiple business sub-data in parallel will not experience data contention, thereby avoiding data conflict problems.

[0090] Figure 5 This is a block diagram of a data processing apparatus according to an embodiment of this application. The apparatus is used to perform the steps of the data processing method described above, see below. Figure 5 The data processing device includes: an acquisition module 501, a splitting module 502, and a processing module 503.

[0091] The acquisition module 501 is used to acquire business data based on the interaction layer of the target application. The target application can be any application in the terminal. The interaction layer is used to receive operations. The business data is the data generated by the operations on the application interface of the target application.

[0092] The splitting module 502 is used by the transformation layer based on the target application to split the business data according to the business logic of the business associated with the business data, resulting in multiple business sub-data. The transformation layer is used for data transfer, and the business logic of the multiple business sub-data is independent of each other.

[0093] The processing module 503 is used to process multiple business sub-data in parallel through multi-threading based on the engine layer of the target application, so as to obtain multiple response sub-data of the business data. The engine layer is used to perform logical processing on the data, and the multiple response sub-data corresponds one-to-one with the multiple business sub-data.

[0094] In some embodiments, Figure 6 This is a block diagram of another data processing apparatus provided according to an embodiment of this application. See also Figure 6 Module 502 is split into:

[0095] The first determining unit 601 is used to determine the number of business logics contained in the business data from the business logic of the business associated with the business data, based on the conversion layer.

[0096] The splitting unit 602 is used to split business data into multiple business sub-data when the quantity exceeds a quantity threshold.

[0097] In some embodiments, the first determining unit 601 is further configured to determine the data type of the business data based on the conversion layer;

[0098] The splitting unit 602 is also used to split business data according to business logic to obtain multiple business sub-data when the data type is a preset data type.

[0099] In some embodiments, see continue to see Figure 6 The device also includes:

[0100] The determination module 504 is used to determine the data synchronization method of multiple response sub-data based on the real-time requirements of business data. The data synchronization method includes a first data synchronization method and a second data synchronization method. The first data synchronization method is used to synchronize data with high real-time requirements, and the second data synchronization method is used to synchronize data with low real-time requirements.

[0101] The synchronization module 505 is used to synchronize multiple response sub-data from the engine layer to the interaction layer based on the conversion layer through data synchronization.

[0102] In some embodiments, see continue to see Figure 6 Synchronization module 505 includes:

[0103] The second determining unit 603 is used to determine the amount of business data when the data synchronization mode is the first data synchronization mode;

[0104] The acquisition unit 604 is used to acquire multiple response sub-data from the engine layer based on the transformation layer when the data volume is not greater than the quantity threshold.

[0105] The merging unit 605 is used to merge multiple response sub-data according to the business logic of the business associated with the business data based on the transformation layer, so as to obtain the response data of the business data.

[0106] Synchronization unit 606 is used to synchronize response data to the interaction layer based on the conversion layer.

[0107] In some embodiments, the second determining unit 603 is further configured to determine at least one target response sub-data from multiple response sub-data based on the engine layer when the data volume is greater than a quantity threshold. The target response sub-data is the data to be synchronized to the interaction layer from the multiple response data.

[0108] The acquisition unit 604 is also used to acquire at least one target response sub-data from the engine layer based on the transformation layer;

[0109] The merging unit 605 is also used to merge at least one target response sub-data based on the transformation layer and according to the business logic of the business associated with the business data, to obtain the response data of the business data.

[0110] The synchronization unit 606 is also used to synchronize response data to the interaction layer based on the conversion layer.

[0111] In some embodiments, see continue to see Figure 6 The acquisition unit 604 includes:

[0112] The first acquisition subunit 6041 is used to acquire at least one data identifier from the engine layer based on the conversion layer. The data identifier is used to indicate the data to be synchronized to the interaction layer.

[0113] The second acquisition subunit 6042 is used to acquire at least one target response subdata indicated by at least one data identifier from a plurality of response subdata.

[0114] In some embodiments, the acquisition unit 604 is further configured to, when the data synchronization mode is the second data synchronization mode, acquire a target number of response sub-data from the engine layer every X seconds based on the conversion layer, where X is a positive number;

[0115] The merging unit 605 is also used to merge the multiple response sub-data in response to the completion of the acquisition of multiple response sub-data, based on the transformation layer and according to the business logic of the business associated with the business data, to obtain the response data of the business data;

[0116] The synchronization unit 606 is also used to synchronize response data to the interaction layer based on the conversion layer.

[0117] In some embodiments, the synchronization unit 606 includes:

[0118] The conversion subunit 6061 is used to convert the data type of the response data into the target data type based on the conversion layer, where the target data type is the data type of the data in the interaction layer;

[0119] Synchronization subunit 6062 is used to synchronize response data to the interaction layer based on the conversion layer.

[0120] This application provides a data processing apparatus. Based on the conversion layer of a target application, it can decompose business data collected from the interaction layer of the target application into multiple business sub-data with independent business logic. Based on the engine layer of the target application, multiple business sub-data are processed in parallel by multi-threading, which simplifies the execution logic of the business and improves the processing efficiency of business data. Furthermore, since the business logic associated with each business sub-data is independent, the multiple threads used to process multiple business sub-data in parallel will not experience data contention, thereby avoiding data conflict problems.

[0121] It should be noted that the data processing apparatus provided in the above embodiments is only illustrated by the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the apparatus can be divided into different functional modules to complete all or part of the functions described above. In addition, the data processing apparatus and data processing method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0122] Figure 7 This is a structural schematic diagram of a terminal 700 provided according to an embodiment of this application. The terminal 700 can be a portable mobile terminal, such as a smartphone, tablet computer, MP3 player (Moving Picture Experts Group Audio Layer III), MP4 player (Moving Picture Experts Group Audio Layer IV), laptop computer, or desktop computer. The terminal 700 may also be referred to as user equipment, portable terminal, laptop terminal, desktop terminal, or other names.

[0123] Typically, terminal 700 includes a processor 701 and a memory 702.

[0124] Processor 701 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 701 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 701 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 701 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 701 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0125] The memory 702 may include one or more computer-readable storage media, which may be non-transitory. The memory 702 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 702 are used to store at least one computer program, which is executed by the processor 701 to implement the data processing method provided in the method embodiments of this application.

[0126] In some embodiments, the terminal 700 may also optionally include a peripheral device interface 703 and at least one peripheral device. The processor 701, memory 702, and peripheral device interface 703 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 703 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency circuit 704, a display screen 705, a camera assembly 706, an audio circuit 707, and a power supply 708.

[0127] Peripheral device interface 703 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 701 and memory 702. In some embodiments, processor 701, memory 702 and peripheral device interface 703 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 701, memory 702 and peripheral device interface 703 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0128] The radio frequency (RF) circuit 704 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 704 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 704 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. In some embodiments, the RF circuit 704 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 704 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 704 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0129] Display screen 705 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 705 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 701 for processing. In this case, display screen 705 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one display screen 705, disposed on the front panel of terminal 700; in other embodiments, there may be at least two display screens 705, disposed on different surfaces of terminal 700 or in a folded design; in other embodiments, display screen 705 may be a flexible display screen, disposed on a curved or folded surface of terminal 700. Furthermore, display screen 705 may be configured as a non-rectangular irregular shape, i.e., a non-rectangular screen. Display screen 705 may be made of materials such as LCD (Liquid Crystal Display) or OLED (Organic Light-Emitting Diode).

[0130] The camera assembly 706 is used to acquire images or videos. In some embodiments, the camera assembly 706 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 706 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash is a combination of a warm-light flash and a cool-light flash, which can be used for light compensation at different color temperatures.

[0131] The audio circuit 707 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting the sound waves into electrical signals that are input to the processor 701 for processing, or input to the radio frequency circuit 704 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each located at a different part of the terminal 700. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert the electrical signals from the processor 701 or the radio frequency circuit 704 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 707 may also include a headphone jack.

[0132] Power supply 708 is used to power the various components in terminal 700. Power supply 708 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 708 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, while a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0133] In some embodiments, the terminal 700 further includes one or more sensors 709. The one or more sensors 709 include, but are not limited to: an accelerometer 710, a gyroscope 711, a pressure sensor 712, an optical sensor 713, and a proximity sensor 714.

[0134] Accelerometer 710 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established by terminal 700. For example, accelerometer 710 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 701 can control display screen 705 to display the user interface in either a landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 710. Accelerometer 710 can also be used for games or for acquiring user motion data.

[0135] The gyroscope sensor 711 can detect the orientation and rotation angle of the terminal 700. The gyroscope sensor 711, in conjunction with the accelerometer sensor 710, can collect 3D motion data from the user on the terminal 700. Based on the data collected by the gyroscope sensor 711, the processor 701 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

[0136] The pressure sensor 712 can be disposed on the side bezel of the terminal 700 and / or the lower layer of the display screen 705. When the pressure sensor 712 is disposed on the side bezel of the terminal 700, it can detect the user's grip signal on the terminal 700, and the processor 701 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 712. When the pressure sensor 712 is disposed on the lower layer of the display screen 705, the processor 701 can control the operable controls on the UI interface based on the user's pressure operation on the display screen 705. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0137] An optical sensor 713 is used to collect ambient light intensity. In one embodiment, the processor 701 can control the display brightness of the display screen 705 based on the ambient light intensity collected by the optical sensor 713. Specifically, when the ambient light intensity is high, the display brightness of the display screen 705 is increased; when the ambient light intensity is low, the display brightness of the display screen 705 is decreased. In another embodiment, the processor 701 can also dynamically adjust the shooting parameters of the camera assembly 706 based on the ambient light intensity collected by the optical sensor 713.

[0138] The proximity sensor 714, also known as a distance sensor, is typically located on the front panel of the terminal 700. The proximity sensor 714 is used to detect the distance between the user and the front of the terminal 700. In one embodiment, when the proximity sensor 714 detects that the distance between the user and the front of the terminal 700 is gradually decreasing, the processor 701 controls the display screen 705 to switch from a screen-on state to a screen-off state; when the proximity sensor 714 detects that the distance between the user and the front of the terminal 700 is gradually increasing, the processor 701 controls the display screen 705 to switch from a screen-off state to a screen-on state.

[0139] Those skilled in the art will understand that Figure 7 The structure shown does not constitute a limitation on terminal 700, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0140] This application also provides a computer-readable storage medium storing at least one computer program. This computer program is loaded and executed by a processor of a computer device to implement the operations performed by the computer device in the data processing method of the above embodiments. For example, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0141] This application also provides a computer program product, including a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, causing the computer device to perform the data processing methods provided in the various optional implementations described above.

[0142] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0143] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A data processing method, characterized in that, The method includes: Based on the interaction layer of the target application, business data is collected. The target application is any application in the terminal. The interaction layer is used to receive operations. The business data is data generated based on the operations on the application interface of the target application. Based on the conversion layer of the target application, the business data is split into multiple business sub-data according to the business logic of the business associated with the business data. The conversion layer is used for data transfer, and the business logic of the multiple business sub-data is independent of each other. Based on the engine layer of the target application, the multiple business sub-data are processed in parallel through multi-threading to obtain multiple response sub-data of the business data. The engine layer is used to perform logical processing on the data, and the multiple response sub-data corresponds one-to-one with the multiple business sub-data. When the data synchronization method is the first data synchronization method used to synchronize data with high real-time requirements, the data volume of the business data is determined; If the amount of data exceeds a threshold, based on the engine layer, at least one target response sub-data is determined from the plurality of response sub-data, wherein the target response sub-data is the data among the plurality of response sub-data that needs to be synchronized to the interaction layer; Based on the conversion layer, at least one data identifier is obtained from the engine layer, the data identifier being used to indicate data to be synchronized to the interaction layer; From the plurality of response sub-data, obtain at least one target response sub-data indicated by the at least one data identifier; The at least one target response sub-data is merged to obtain the response data of the business data; The response data is synchronized to the interaction layer.

2. The method according to claim 1, characterized in that, The conversion layer based on the target application splits the business data according to the business logic of the business associated with the business data, resulting in multiple business sub-data, including: Based on the transformation layer, the number of business logics contained in the business data is determined from the business logic of the business associated with the business data; If the quantity exceeds a threshold, the business data is split to obtain the multiple business sub-data; or, Based on the transformation layer, the data type of the business data is determined; When the data type is a preset data type, the business data is split according to the business logic to obtain the multiple business sub-data.

3. The method according to claim 1, characterized in that, The method further includes: Based on the real-time requirements of the business data, a data synchronization method for the plurality of response sub-data is determined. The data synchronization method includes a first data synchronization method and a second data synchronization method. The second data synchronization method is used to synchronize data with low real-time requirements. Based on the conversion layer, the multiple response sub-data are synchronized from the engine layer to the interaction layer through the data synchronization method.

4. The method according to claim 3, characterized in that, When the data synchronization method is a first data synchronization method used for synchronizing data with high real-time requirements, after determining the data volume of the business data, the method further includes: If the amount of data is not greater than the quantity threshold, the multiple response sub-data are obtained from the engine layer based on the conversion layer; Based on the transformation layer, the multiple response sub-data are merged according to the business logic of the business associated with the business data to obtain the response data of the business data; Based on the conversion layer, the response data is synchronized to the interaction layer.

5. The method according to claim 4, characterized in that, The step of merging the at least one target response sub-data to obtain the response data of the business data includes: Based on the transformation layer, the at least one target response sub-data is merged according to the business logic of the business associated with the business data to obtain the response data of the business data; Based on the conversion layer, the response data is synchronized to the interaction layer.

6. The method according to claim 3, characterized in that, The step of synchronizing the multiple response sub-data from the engine layer to the interaction layer based on the conversion layer and through the data synchronization method includes: When the data synchronization method is the second data synchronization method, based on the conversion layer, a target number of response sub-data are obtained from the engine layer every X seconds, where X is a positive number; In response to the completion of acquiring the multiple response sub-data, based on the conversion layer, the multiple response sub-data are merged according to the business logic of the business associated with the business data to obtain the response data of the business data; Based on the conversion layer, the response data is synchronized to the interaction layer.

7. The method according to any one of claims 4, 5 or 6, characterized in that, The step of synchronizing the response data to the interaction layer based on the conversion layer includes: Based on the conversion layer, the data type of the response data is converted into the target data type, where the target data type is the data type of the data in the interaction layer; Based on the conversion layer, the response data is synchronized to the interaction layer.

8. A data processing apparatus, characterized in that, The device includes: The data acquisition module is used to collect business data based on the interaction layer of the target application, wherein the target application is any application in the terminal, the interaction layer is used to receive operations, and the business data is data generated based on the operations on the application interface of the target application. The splitting module is used to split the business data according to the business logic of the business associated with the business data based on the conversion layer of the target application, so as to obtain multiple business sub-data. The conversion layer is used for data transfer, and the business logic of the multiple business sub-data is independent of each other. The processing module is used to process the multiple business sub-data in parallel through multi-threading based on the engine layer of the target application to obtain multiple response sub-data of the business data. The engine layer is used to perform logical processing on the data. The multiple response sub-data corresponds one-to-one with the multiple business sub-data. The synchronization module includes: The second determining unit is used to determine the amount of business data when the data synchronization method is a first data synchronization method for synchronizing data with high real-time requirements; when the amount of data is greater than a quantity threshold, based on the engine layer, it determines at least one target response sub-data from the plurality of response sub-data, wherein the target response sub-data is the data to be synchronized to the interaction layer from the plurality of response sub-data. The acquisition unit is configured to acquire at least one data identifier from the engine layer based on the conversion layer, the data identifier being used to indicate data to be synchronized to the interaction layer; acquire at least one target response sub-data indicated by the at least one data identifier from the plurality of response sub-data; and merge the at least one target response sub-data to obtain the response data of the business data. A synchronization unit is used to synchronize the response data to the interaction layer.

9. A computer device, characterized in that, The computer device includes a processor and a memory, the memory being used to store at least one computer program, the at least one computer program being loaded by the processor and executing the data processing method according to any one of claims 1 to 7.

Citation Information

Patent Citations

  • Decoupling method and device for business logic and circulation logic

    CN115080257A

  • Heterogeneous computing framework-based processing method and apparatus, and device and medium

    WO2023125463A1