A data transmission processing method, device, equipment and medium

Abstract

The application discloses a kind of data transmission processing methods, device and equipment based on task transfer and medium.The method comprises: when the first device receives the application task transfer instruction of second device, the task identification of the application task transferred by the second device is obtained;The task identification is determined by the second device when the application task is generated;In the process of executing the application task in the first device, the change event of the application page of corresponding target application is listened to, and the post-transfer page dynamic data is obtained;The post-transfer page dynamic data is bound with the task identification;The post-transfer page dynamic data and the bound task identification are sent to target device, so that the target device merges corresponding pre-transfer page dynamic data and the post-transfer page dynamic data according to the task identification.The application embodiment can ensure the continuity of data, improve data analysis efficiency.

Description

Technical Field

[0001] This invention relates to the field of Internet technology, and in particular to a data transmission and processing method, apparatus, device and medium based on task transfer. Background Technology

[0002] To observe application usage, view data is typically collected. With the development of distributed operating systems, users can switch their sessions from one device to another while using an application, continuing their operations on the new device. When analyzing application usage, it's necessary to merge the view data collected after the switch with the view data collected before the switch.

[0003] Currently, data transfer processing methods based on task transfer primarily involve data collection and uploading. This method cannot identify whether data reported by different devices belongs to the same session. When analyzing application usage, the view data collected before and after the task transfer can only be manually merged based on human records. Therefore, existing data transfer processing methods suffer from data fragmentation, reducing the efficiency of data analysis. Summary of the Invention

[0004] This invention provides a data transfer processing method, apparatus, device, and medium based on task transfer, which can ensure the continuity of view data and improve data analysis efficiency.

[0005] According to one aspect of the present invention, an embodiment of the present invention provides a data transfer processing method based on task transfer, the method comprising:

[0006] When the first device receives an application task transfer instruction from the second device, it obtains the task identifier of the application task transferred by the second device; the task identifier is determined by the second device when the application task is generated.

[0007] During the execution of the application task by the first device, listen for changes in the application page of the corresponding target application and obtain dynamic data of the page after the transfer;

[0008] Bind the transferred page dynamic data to the task identifier;

[0009] The transferred page dynamic data and the bound task identifier are sent to the target device, so that the target device can merge the corresponding pre-transfer page dynamic data and the transferred page dynamic data according to the task identifier.

[0010] According to another aspect of the present invention, embodiments of the present invention also provide a data transfer processing apparatus based on task transfer, the apparatus comprising:

[0011] The data acquisition module is used to acquire the task identifier of the application task transferred by the second device when the first device receives the application task transfer instruction from the second device; the task identifier is determined by the second device when the application task is generated.

[0012] The event listening module is used to listen for changes in the application page of the corresponding target application during the execution of the application task on the first device, and to obtain dynamic data of the page after the transfer.

[0013] The data association module is used to bind the dynamic data of the transferred page with the task identifier;

[0014] The data transmission module is used to send the transferred page dynamic data and the bound task identifier to the target device, so that the target device can merge the corresponding pre-transfer page dynamic data and the transferred page dynamic data according to the task identifier.

[0015] According to another aspect of the present invention, embodiments of the present invention also provide a data transfer processing device based on task transfer, the data transfer processing device based on task transfer comprising:

[0016] At least one processor; and

[0017] A memory that is communicatively connected to at least one processor; wherein,

[0018] The memory stores a computer program that can be executed by at least one processor, such that the at least one processor is able to execute the task-transfer-based data transfer processing method of any embodiment of the present invention.

[0019] According to another aspect of the present invention, a computer-readable storage medium is provided, which stores computer instructions for causing a processor to execute and implement the task-transfer-based data transfer processing method of any embodiment of the present invention.

[0020] According to another aspect of the present invention, a computer program product is provided, the computer program product comprising a computer program that, when executed by a processor, implements the data transfer processing method based on task transfer as described in any embodiment of the present invention.

[0021] The technical solution of this invention obtains the task identifier of the application task upon receiving an application task transfer instruction from a second device, listens for changes in the application page during the execution of the application task, and acquires the dynamic data of the transferred page. This dynamic data is then bound to the task identifier and sent to the target device. This allows the target device to accurately match the dynamic page data of the corresponding application task based on the unique task identifier, merging the dynamic page data from different devices to reconstruct the complete execution process of the application task. This solves the problem of difficulty in matching dynamic page data during cross-device task transfer, ensuring the continuity of view data and improving the efficiency of dynamic page data analysis.

[0022] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of the present invention, 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 the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a flowchart of a data transfer processing method based on task transfer according to an embodiment of the present invention;

[0025] Figure 2A This is a flowchart of a data transfer processing method based on task transfer according to an embodiment of the present invention;

[0026] Figure 2B This is a flowchart of a data transfer processing method based on task transfer according to an embodiment of the present invention;

[0027] Figure 3 This is a structural diagram of a data transfer processing device based on task transfer according to an embodiment of the present invention;

[0028] Figure 4 This is a schematic diagram of the structure of a data transfer and processing device based on task transfer provided in an embodiment of the present invention. Detailed Implementation

[0029] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0031] The acquisition, storage, and application of dynamic page data involved in the technical solutions of this invention comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0032] Figure 1 This is a flowchart illustrating a data transfer processing method based on task transfer, provided in an embodiment of the present invention. This embodiment is applicable to multi-device interconnection systems where application tasks of a target application are transferred from one device to another. The method can be executed by a task transfer-based data transfer processing device, which can be implemented in hardware and / or software. This task transfer-based data transfer processing device can be configured in a server.

[0033] See Figure 1 The data transfer processing method based on task transfer shown includes:

[0034] S101. When the first device receives the application task transfer instruction from the second device, it obtains the task identifier of the application task transferred by the second device; the task identifier is determined by the second device when the application task is generated.

[0035] A multi-device linkage system can be a distributed system where multiple devices are interconnected. In such a system, application tasks can be transferred from one device to another. For example, in a multi-device linkage system, there are two interconnected devices: a mobile phone and a tablet. On the tablet, an application with shopping functionality is launched, desired items are selected, and added to the order. After addition, the application task is transferred from the tablet to the mobile phone. On the mobile phone, the order is submitted and payment is made. The process of selecting items on the tablet and submitting payment on the mobile phone can be viewed as the transfer of application tasks between devices. An application task can refer to a task that completes a specific goal through a series of operations.

[0036] The first device can be the device after the application task is transferred. The second device can be the device before the application task transfer. The application task transfer instruction can be an instruction to transfer the application task across devices. The application task transfer instruction is sent from the second device to the first device. The application task transfer instruction contains application task-related data so that the first device can know the execution status of the application task based on the data in the application task transfer instruction. For example: the application is a video playback application. When the video plays to 30% on the phone, the user switches devices, transferring the application task to the computer. At this time, the application task transfer instruction sent from the phone to the computer can include the video playback progress, i.e., 30%.

[0037] The application task transfer instruction includes at least a task identifier and launch parameters. The launch parameters may be those required to launch the application on the first device. The first device launches the application based on the launch parameters and loads the page of the transferred application task. In some embodiments, the launch of the application on the second device is triggered by a user's instruction. The launch of the application on the first device is triggered by the application task transfer instruction on the second device. For example, when a user clicks the application icon on a mobile phone to launch the application, transferring the application task from the phone to the tablet, the phone sends an application task transfer instruction to the tablet. Upon receiving the instruction, the tablet launches the application corresponding to the transferred application task.

[0038] In an optional embodiment, the first device and the second device have the same operating system and the same user permissions.

[0039] The operating system can be a software system that manages and controls device resources. Understandably, the first device needs to support running application tasks transferred from the second device. If the first and second devices have the same operating system, and the application task can run on the second device, then the application task can correspondingly run on the first device. The fact that the first and second devices have the same operating system ensures that the first device can run the transferred application task.

[0040] In addition, to ensure information security, the first device and the second device need to have the same user permissions. In some embodiments, the user accounts logged into the operating systems of the first device and the second device are the same, confirming that the first device and the second device are in the same multi-device linkage system.

[0041] It is evident that by ensuring that the operating systems of the first and second devices are the same, the successful transfer of application tasks can be ensured. By ensuring that the user permissions of the first and second devices are the same, information security can be guaranteed and application tasks can be prevented from being transferred to unknown devices.

[0042] Users can transfer application tasks currently running on the second device by clicking a button or making a transfer gesture. After recognizing the user's intention to transfer the application task, the second device obtains the current execution status of the application task and generates an application task transfer command.

[0043] A task identifier can be a unique identifier for an application task. Each application task has a unique task identifier. Different application tasks have different task identifiers. The task identifier is used for application task identification. The task identifier is generated on a second device when an application task is created on that second device. Optionally, after the application has started, the application task is determined to be generated when the user performs their first interaction with the application. For example, after the launch page of a shopping application has loaded, the user's first click or swipe on the page indicates that an application task has been generated, and a task identifier is created.

[0044] In a specific embodiment, the specific process for a user to perform application task transfer is as follows:

[0045] 1. The user launches the application on the second device, generating an application task and its corresponding task identifier;

[0046] 2. When a user triggers an application task transfer operation, the second device displays a list of devices that can perform task transfer;

[0047] 3. The user selects the first device from the list of transferable devices and confirms;

[0048] 4. After receiving the transfer request, the first device displays the application icon of the corresponding application to prompt the user for confirmation;

[0049] 5. The user clicks the application icon on the first device to confirm the transfer of the application task;

[0050] 6. The first device sends a confirmation command to the second device;

[0051] 7. After receiving confirmation from the first device, the second device sends an application task transfer instruction to the first device to transfer the application task to the first device for execution.

[0052] In an optional embodiment, while the first device receives the application task transfer instruction from the second device, the method further includes: querying whether a task identifier field exists in the application task transfer instruction; if a field corresponding to the task identifier exists in the application task transfer instruction, then obtaining the task identifier of the application task transferred by the second device from the application task transfer instruction; if a field corresponding to the task identifier does not exist in the application task transfer instruction, then determining that the task transfer has failed, and generating a new task identifier.

[0053] The task identifier field can be any field corresponding to a task identifier. For example, the Trace ID can be used as the task identifier field.

[0054] The application task transfer instruction generated by the second device is typically in a data format that facilitates data transmission. After receiving the application task transfer instruction, the first device needs to parse it into a data format that facilitates data content reading.

[0055] Generally, after parsing the application task transfer instruction, the task identifier is displayed in the form of key-value pairs. For example: Trace ID: 123. Here, Trace ID represents the task identifier field, that is, the key of the task identifier; 123 represents the value of the task identifier.

[0056] Check if the application task transfer instruction contains a task identifier field. If the instruction contains the field corresponding to the task identifier, retrieve the task identifier; if it does not, the transfer may have data anomalies or loss, and the transfer is considered a failure. In the event of a failed transfer, to prevent the application task from lacking a task identifier, the first device generates a new task identifier. In this case, the first device is considered the second device.

[0057] As can be seen, by adding a task identifier field to the query, the missing task identifier can be avoided, effectively preventing the occurrence of situations where there is no task identifier to bind to, improving the rationality of the solution, and ensuring the integrity of the data.

[0058] S102. During the execution of the application task by the first device, listen for changes in the application page of the corresponding target application and obtain dynamic data of the page after the transfer.

[0059] The target application can be the application to which the application task belongs. The application page can be the page of the application task. The application task is the application task of the target application; it is executed through the application page. Change events can refer to events that cause changes in the content displayed on the application page. Page dynamic data can be data describing the state and characteristics of each page component within the application page at a given moment. Post-transfer page dynamic data can refer to the page dynamic data generated on the device after the application task is transferred. Page components can refer to visual components on the page used to display information or receive user actions. Page components include: text, buttons, images, input boxes, list items, and icons, etc.

[0060] During the execution of an application task on the first device, the application page may undergo dynamic changes such as navigation or scrolling. By acquiring and recording the dynamic data of the page after the transition, the execution process of the application task can be completely recorded.

[0061] Understandably, if methods for periodically retrieving dynamic page data are used, a large amount of duplicate data will be generated if the user does not interact for a long time. By listening for change events on the target application's page, and retrieving dynamic page data when a change in the displayed content is detected, duplicate data can be avoided. Specifically, after the application page responds to user actions and changes, the change event can be detected. At this time, the data collection method is triggered and called to obtain the dynamic page data after the change.

[0062] S103. Bind the transferred page dynamic data to the task identifier.

[0063] Specifically, the dynamic data of the transferred page is bound to the task identifier, so that the dynamic data of the transferred page carries the task identifier.

[0064] Furthermore, when the application task is executed on the second device, the second device obtains the dynamic page data before the transfer of the application task execution process. In the second device, the dynamic page data before the transfer is bound to a task identifier. The dynamic page data before the transfer on the second device and the dynamic page data after the transfer on the first device are bound to the same task identifier.

[0065] In one specific embodiment, the task identifier can be added to the context object to bind the dynamic page data after the transfer with the task identifier.

[0066] A context object is a carrier object that contains information needed for program execution in a specific environment. Context objects are used to store relevant information required for task execution. Context objects can include: device information, configuration information, and functions, etc.

[0067] Generally, when an application task begins execution on the device, the device creates a context object for that application task. Adding a task identifier to the context object integrates the task identifier with other relevant information required for the application task's execution, aggregating fragmented information into a standardized object. The collected, transferred dynamic page data is then bound to the context object.

[0068] S104. The transferred page dynamic data and the bound task identifier are sent to the target device, so that the target device merges the corresponding pre-transfer page dynamic data and the transferred page dynamic data according to the task identifier.

[0069] The target device can refer to a device that receives data sent by the first device. In some embodiments, the target device is a data analysis device; in other embodiments, the target device is a second device.

[0070] The target device collects dynamic page data from different devices belonging to the same application task based on the same task identifier, and sorts the dynamic page data reported by each device according to the chronological order of page changes. This merges the dynamic page data from different devices into a continuous and complete page execution data stream, ultimately reconstructing the entire execution process of the application task from initiation to completion.

[0071] In an optional embodiment, sending the transferred page dynamic data and the bound task identifier to the target device includes: determining the transferred page dynamic data and the bound task identifier as identifier data; putting the identifier data into an asynchronous thread pool, asynchronously parsing the identifier data, and filtering out sensitive fields containing sensitive information; desensitizing the field values ​​of the sensitive fields; and sending the desensitized identifier data to the target device.

[0072] The identifier data can be dynamic page data bound to a task identifier. The asynchronous thread pool can be a task pool with independent asynchronous threads. The identifier data is added to the asynchronous thread pool, and the de-identification process is completed in a separate thread.

[0073] Specifically, the identification data is put into an asynchronous thread pool. In an independent thread, the identification data is parsed into structured data. The parsed structured data is then queried based on preset sensitive fields containing sensitive information, and the sensitive fields in the structured data are filtered out. The values ​​of the sensitive fields are then de-identified; optionally, the field values ​​are replaced with values ​​that do not contain sensitive information or the field values ​​are deleted.

[0074] As can be seen, by putting the identifier data into an asynchronous thread pool for asynchronous parsing and desensitization, the data processing flow is separated from the main thread execution, which effectively solves the problem of main flow blocking caused by the long time consumption of data parsing and desensitization operations, and improves the system response speed and running smoothness; at the same time, the identifier view data is desensitized to prevent the leakage of user information and ensure user information security.

[0075] In an optional embodiment, the target device includes: a second device; the step of sending the transferred page dynamic data and the bound task identifier to the target device includes: performing statistics on the untransferred transferred page dynamic data generated by the first device to obtain statistical data; when the statistical data meets the data transmission conditions, sending the untransferred transferred page dynamic data and the corresponding bound task identifier to the second device, so that the second device merges the page dynamic data according to the task identifier and the page component identifier.

[0076] Among these, statistical data can be statistics compiled from the dynamic data of the transferred page that was not transmitted. Data transmission conditions can be the conditions that trigger data transmission. Page component identifiers can be the identification marks of page components within the page.

[0077] After obtaining the dynamic data of the transferred page, it can be stored in the task to be transferred. The dynamic data of the transferred page can be statistically analyzed in the task to be transferred, which can include the time since the last data transfer and / or the capacity of the untransferred dynamic data of the transferred page in the task to be transferred.

[0078] If the time since the last data transmission reaches a time threshold, or if the volume of the untransmitted transferred page dynamic data reaches a data volume threshold, the untransmitted transferred page dynamic data along with the corresponding bound task identifier is sent to the second device. In the second device, the page dynamic data is merged.

[0079] In some embodiments, after the second device transfers the application task to the first device, the application task can continue to be executed on both the second and first devices. At this time, both the second and first devices acquire dynamic page data. The dynamic page data acquired by the first device is identified as the dynamic page data after the transfer, and the dynamic page data acquired by the second device is identified as the dynamic page data before the transfer. To avoid data redundancy, the target device can be set as the second device, allowing the first device to transmit the dynamic page data after the transfer to the second device. Upon receiving the dynamic page data after the transfer, the second device filters the dynamic page data before and after the transfer based on the task identifier, removing duplicate dynamic page data and merging them.

[0080] A specific deduplication and merging method is as follows: A view mapping table is synchronized between the second and first devices using a Distributed Data Object (DDoS). The view mapping table records the correspondence between the page component identifiers of page components on the second device and those on the first device. Identical page components are identified through this correspondence. A time window is set, optionally between 50 and 100 ms. If the same page component undergoes the same change in the dynamic data of page components on different devices within the time window, it is considered a duplicate. Only one record of duplicate dynamic data is retained. Optionally, the earliest record of dynamic data is retained.

[0081] As can be seen, by statistically analyzing the dynamic page data transferred but not transmitted by the first device, and synchronizing the dynamic page data and task identifier to the second device when the data transmission conditions are met, the second device can deduplicate and merge the dynamic page data based on the task identifier and page component identifier, thereby reducing invalid data transmission and improving data transmission efficiency.

[0082] The technical solution of this invention obtains the task identifier of the application task upon receiving an application task transfer instruction from a second device, listens for changes in the application page during the execution of the application task, and acquires the dynamic data of the transferred page. This dynamic data is then bound to the task identifier and sent to the target device. This allows the target device to accurately match the dynamic page data of the corresponding application task based on the unique task identifier, merging the dynamic page data from different devices to reconstruct the complete execution process of the application task. This solves the problem of difficulty in matching dynamic page data during cross-device task transfer, ensuring the continuity of view data and improving the efficiency of dynamic page data analysis.

[0083] Figure 2AThis is a flowchart of a data transfer processing method based on task transfer provided by an embodiment of the present invention. Based on the above embodiments, before monitoring application page change events during the execution of the application task by the first device, the embodiment further includes: launching the target application according to application startup data carried by the application task transfer instruction, and generating a page view tree of the application page; the nodes of the page view tree correspond one-to-one with the page components of the application page; so that the startup state of the application page on the first device is consistent with the transfer state on the second device; the transfer state is the running state of the application page on the second device when the second device generates the application task transfer instruction; the step of monitoring application page change events and obtaining dynamic page data after transfer during the execution of the application task by the first device includes: monitoring the page view tree in real time during the execution of the application task by the first device; and obtaining the dynamic page data after transfer corresponding to the changed nodes when the page view tree changes.

[0084] It should be noted that for parts not described in detail in the embodiments of the present invention, please refer to the descriptions in other embodiments.

[0085] See Figure 2A The data transfer processing method based on task transfer shown includes:

[0086] S201. When the first device receives the application task transfer instruction from the second device, it obtains the task identifier of the application task transferred by the second device; the task identifier is determined by the second device when the application task is generated.

[0087] S202. Based on the application startup data carried by the application task transfer instruction, start the target application and generate a page view tree of the application page; the nodes of the page view tree correspond one-to-one with the page components of the application page; so that the startup state of the application page on the first device is consistent with the transfer state on the second device; the transfer state is the running state of the application page on the second device when the second device generates the application task transfer instruction.

[0088] The application startup data can be data describing the application startup state. This data is used to restore the execution state of the application task when the target application starts on the first device. The page view tree can be a tree diagram describing the application pages. It's a tree structure that organizes all page components on the application page according to their containment relationships. Each node represents a page component, and the hierarchical relationship reflects the containment relationship between page components. The page view tree describes the structural layout of the page components in the current application page. The transfer state can be the state of the application page collected when the second device receives a command from the user to transfer the application task. The startup state can be the state of the application page loaded when the target application starts on the first device.

[0089] The application startup data carried in the application task transfer instruction is read, and the application page is loaded according to the parameters in the application startup data to launch the target application on the first device. Simultaneously with loading the application page, a page view tree of the application page is generated.

[0090] S203. During the execution of the application task by the first device, the page view tree is monitored in real time.

[0091] Specifically, when the content displayed on the application page changes, the page view tree also changes accordingly. The page view tree is monitored in real time to capture changes in the application page of the first device executing the application task.

[0092] S204. When the page view tree changes, obtain the dynamic data of the page after the transfer corresponding to the changed node.

[0093] In this context, a change node can be a node in the view tree that has undergone changes. Change nodes represent page components that have changed within the application page.

[0094] When content changes on an application page, it's possible that only some page components change, rather than the entire application page changing completely. For example, in response to a user action, an image on the application page might change, while buttons and input fields might remain unchanged. Therefore, it's only necessary to obtain the dynamic page data corresponding to the changed nodes after the transition.

[0095] In an optional embodiment, monitoring the page view tree includes: monitoring for dynamic nodes with dynamic layout attributes in the page view tree; the dynamic layout attribute is a dynamically changing attribute; and when the page view tree changes, obtaining the dynamic data of the transferred page corresponding to the changed node includes: when it is determined that the dynamic layout attribute of a dynamic node has changed, identifying the dynamic node with the changed dynamic layout attribute as the changed node; and identifying the updated dynamic layout attribute of the changed node as the dynamic data of the transferred page corresponding to the changed node.

[0096] Dynamic nodes can be nodes in the page view tree that can change. Dynamic layout properties are properties that can change dynamically.

[0097] You can use decorators to mark dynamic nodes in the page view tree and listen for their dynamic layout properties. When the dynamic layout properties of a dynamic node change, you can use interceptors to obtain the changed dynamic layout properties of that node.

[0098] As can be seen, by listening to dynamic nodes with dynamic layout attributes and obtaining the changed dynamic layout attributes of the changed dynamic nodes, we can not only describe the changes of the application page and reflect the execution process of the application task, but also reduce the amount of data and improve space utilization.

[0099] S205. Bind the transferred page dynamic data to the task identifier.

[0100] S206. The transferred page dynamic data and the bound task identifier are sent to the target device, so that the target device merges the corresponding pre-transfer page dynamic data and the transferred page dynamic data according to the task identifier.

[0101] The technical solution of this invention starts the target application, generates a page view tree, listens to the page view tree, and obtains the dynamic data of the page after the transfer corresponding to the changed nodes. Based on the structured features of the view tree, data can be obtained only for the changed nodes, which can greatly reduce the redundancy of data collection, reduce the resource consumption of data transmission, and improve the efficiency of subsequent data merging.

[0102] In one specific embodiment, the view data transfer process is as follows: Figure 2B As shown.

[0103] In the second device, in response to the user's activation command, the target application is launched and an application task is generated. A task identifier for the application task is generated using a task identifier generator. In response to the user's transfer command, the task identifier is retrieved, and application startup data is generated. A task transfer request, carrying the application startup data, is sent to the first device.

[0104] In the first device, the application startup data is received and parsed. The target application is launched according to the startup parameters in the startup data, and the application page of the application task is loaded. A context object is created based on the task identifier in the application startup data. The page view tree is monitored through a listener; when a change in the view tree is detected, dynamic data of the transferred page is collected. This dynamic data of the transferred page is bound to the context object and sent to the target device for data processing and analysis.

[0105] Figure 3This is a schematic diagram of a data transfer processing device based on task transfer, provided in an embodiment of the present invention. This embodiment is applicable to multi-device interconnection systems where the application task of a target application is transferred from one device to another. The device can execute a data transfer processing method based on task transfer and can be implemented in hardware and / or software.

[0106] See Figure 3 The data transfer processing apparatus based on task transfer shown includes:

[0107] The data acquisition module 301 is used to acquire the task identifier of the application task transferred by the second device when the first device receives the application task transfer instruction from the second device; the task identifier is determined by the second device when the application task is generated.

[0108] The event listening module 302 is used to listen for changes in the application page of the corresponding target application during the execution of the application task by the first device, and to obtain dynamic data of the page after the transfer.

[0109] The data association module 303 is used to bind the transferred page dynamic data with the task identifier;

[0110] The data transmission module 304 is used to send the transferred page dynamic data and the bound task identifier to the target device, so that the target device can merge the corresponding pre-transfer page dynamic data and the transferred page dynamic data according to the task identifier.

[0111] The technical solution of this invention obtains the task identifier of the application task upon receiving an application task transfer instruction from a second device, listens for changes in the application page during the execution of the application task, and acquires the dynamic data of the transferred page. This dynamic data is then bound to the task identifier and sent to the target device. This allows the target device to accurately match the dynamic page data of the corresponding application task based on the unique task identifier, merging the dynamic page data from different devices to reconstruct the complete execution process of the application task. This solves the problem of difficulty in matching dynamic page data during cross-device task transfer, ensuring the continuity of view data and improving the efficiency of dynamic page data analysis.

[0112] In an optional embodiment, the event listening module 302 includes:

[0113] The view tree generation unit is used to launch the target application according to the application launch data carried by the application task transfer instruction, and generate a page view tree of the application page; the nodes of the page view tree correspond one-to-one with the page components of the application page; so that the application page is consistent in the launch state of the first device and the transfer state of the second device; the transfer state is the running state of the application page on the second device when the second device generates the application task transfer instruction;

[0114] A view tree monitoring unit is used to monitor the page view tree in real time during the execution of the application task by the first device;

[0115] The data acquisition unit is used to acquire dynamic page data corresponding to the changed node after the page view tree changes.

[0116] In an optional embodiment, the view tree listening unit includes:

[0117] The node listening subunit is used to listen for dynamic nodes in the page view tree that have dynamic layout attributes; the dynamic layout attributes are attributes that can change dynamically.

[0118] The data acquisition unit includes:

[0119] The node determination sub-unit is used to identify the dynamic node whose dynamic layout attribute has changed as the changed node when the dynamic layout attribute of the identified dynamic node changes.

[0120] The data acquisition subunit is used to determine the updated dynamic layout attributes of the changed node as the dynamic data of the transferred page corresponding to the changed node.

[0121] In an optional embodiment, the data acquisition module 301 includes:

[0122] The query unit is used to query whether a task identifier field exists in the application task transfer instruction;

[0123] The identifier acquisition unit is used to acquire the task identifier of the application task transferred by the second device from the application task transfer instruction if there is a field corresponding to the task identifier in the application task transfer instruction.

[0124] The identifier generation unit is used to determine that the task transfer has failed and generate a new task identifier if the field corresponding to the task identifier does not exist in the application task transfer instruction.

[0125] In an optional embodiment, the data transmission module 304 includes:

[0126] The identification data determination unit is used to determine the transferred page dynamic data and the bound task identifier as identification data;

[0127] The sensitive information filtering unit is used to put the identification data into an asynchronous thread pool, perform asynchronous parsing on the identification data, and filter out sensitive fields containing sensitive information.

[0128] The desensitization unit is used to desensitize the field values ​​of the sensitive fields;

[0129] The first data transmission unit is used to send the de-identified identification data to the target device.

[0130] In an optional embodiment, the target device includes: a second device; and a data transmission module 304, including:

[0131] The data statistics unit is used to perform statistics on the untransferred dynamic data of the transferred page generated by the first device to obtain statistical data.

[0132] The second data transmission unit is used to send the untransmitted transferred page dynamic data and the corresponding bound task identifier to the second device when the statistical data meets the data transmission conditions, so that the second device can merge the page dynamic data according to the task identifier and the page component identifier.

[0133] In an optional embodiment, the first device and the second device have the same operating system and the same user permissions.

[0134] The data transfer processing apparatus based on task transfer provided in the embodiments of the present invention can execute the data transfer processing method based on task transfer provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the data transfer processing method based on task transfer.

[0135] Figure 4 A schematic diagram of the structure of a task-transfer-based data transfer processing device 400 that can be used to implement embodiments of the present invention is shown.

[0136] like Figure 4As shown, the task-transfer-based data transfer processing device 400 includes at least one processor 401 and a memory, such as a read-only memory 402 or a random access memory 403, communicatively connected to the at least one processor 401. The memory stores computer programs executable by the at least one processor. The processor 401 can perform various appropriate actions and processes based on the computer program stored in the read-only memory 402 or loaded from storage unit 408 into the random access memory 403. The random access memory 403 may also store various programs and data required for the operation of the task-transfer-based data transfer processing device 400. The processor 401, read-only memory 402, and random access memory 403 are interconnected via a bus 404. An input / output interface 405 is also connected to the bus 404.

[0137] Multiple components in the task-transfer-based data transfer processing device 400 are connected to the input / output interface 405, including: an input unit 406, such as a keyboard, mouse, etc.; an output unit 407, such as various types of displays, speakers, etc.; a storage unit 408, such as a disk, optical disk, etc.; and a communication unit 409, such as a network interface card, modem, wireless transceiver, etc. The communication unit 409 allows the task-transfer-based data transfer processing device 400 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0138] Processor 401 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 401 include, but are not limited to, central processing units, graphics processing units, various special-purpose artificial intelligence computing chips, various processors running machine learning model algorithms, digital signal processors, and any suitable processor, controller, microcontroller, etc. Processor 401 performs the various methods and processes described above, such as task-transfer-based data transfer processing methods.

[0139] In some embodiments, the task-transfer-based data transfer processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 408. In some embodiments, part or all of the computer program may be loaded and / or installed onto the task-transfer-based data transfer processing device 400 via read-only memory 402 and / or communication unit 409. When the computer program is loaded into random access memory 403 and executed by processor 401, one or more steps of the task-transfer-based data transfer processing method described above may be performed. Alternatively, in other embodiments, processor 401 may be configured to perform the task-transfer-based data transfer processing method by any other suitable means (e.g., by means of firmware).

[0140] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays, application-specific integrated circuits (ASICs), application-specific standard products (ASICs), systems-on-a-chip (SoCs), complex programmable logic devices, computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0141] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0142] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory, flash memory, optical fiber, portable compact disk read-only memory, optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0143] To provide user interaction, the systems and techniques described herein can be implemented on an operational detection device. This task-transfer-based data transfer processing device includes: a display device (e.g., a cathode ray tube or liquid crystal display monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the task-transfer-based data transfer processing device. Other types of devices can also be used to provide user interaction; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0144] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0145] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product within the cloud computing service system. This addresses the shortcomings of traditional physical hosts and virtual private servers, such as high management difficulty and weak business scalability.

[0146] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0147] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A data transfer processing method based on task transfer, characterized in that, The method, applied to a first device in a multi-device linkage system, includes: When the first device receives an application task transfer instruction from the second device, it obtains the task identifier of the application task transferred by the second device; the task identifier is determined by the second device when the application task is generated. During the execution of the application task by the first device, listen for changes in the application page of the corresponding target application and obtain dynamic data of the page after the transfer. Bind the transferred page dynamic data to the task identifier; The transferred page dynamic data and the bound task identifier are sent to the target device, so that the target device can merge the corresponding pre-transfer page dynamic data and the transferred page dynamic data according to the task identifier.

2. The method according to claim 1, characterized in that, Before listening for changes to the application page during the execution of the application task by the first device, the method further includes: Based on the application startup data carried by the application task transfer instruction, the target application is launched, and a page view tree of the application page is generated; the nodes of the page view tree correspond one-to-one with the page components of the application page; so that the application page is consistent in the startup state of the first device and the transfer state of the second device; the transfer state is the running state of the application page on the second device when the second device generates the application task transfer instruction; The step of listening to changes in the application page during the execution of the application task on the first device and obtaining dynamic data of the page after the transfer includes: During the execution of the application task on the first device, the page view tree is monitored in real time; When the page view tree changes, obtain the dynamic data of the page after the transition corresponding to the changed node.

3. The method according to claim 2, characterized in that, The monitoring of the page view tree includes: Listen for dynamic nodes in the page view tree that have dynamic layout attributes; the dynamic layout attributes are attributes that can change dynamically. When the page view tree changes, the dynamic data of the page after the transition corresponding to the changed node is obtained, including: When it is determined that the dynamic layout attribute of a dynamic node changes, the dynamic node whose dynamic layout attribute changes is identified as the changed node. The updated dynamic layout attributes of the changed node are determined as the dynamic data of the page after the change node is transferred.

4. The method according to claim 1, characterized in that, While the first device receives the application task transfer instruction from the second device, it also includes: In the application task transfer instruction, check if a task identifier field exists; If the application task transfer instruction contains a field corresponding to the task identifier, then the task identifier of the application task transferred by the second device is obtained from the application task transfer instruction; If the application task transfer instruction does not contain a field corresponding to the task identifier, the task transfer is determined to have failed, and a new task identifier is generated.

5. The method according to claim 1, characterized in that, Sending the transferred page dynamic data and the bound task identifier to the target device includes: The transferred page dynamic data and the bound task identifier are determined as identifier data; The identification data is put into an asynchronous thread pool, and the identification data is parsed asynchronously to filter out sensitive fields containing sensitive information; Desensitize the values ​​of the sensitive fields; The de-identified identification data is sent to the target device.

6. The method according to claim 1, characterized in that, The target device includes: a second device; Sending the transferred page dynamic data and the bound task identifier to the target device includes: The untransferred dynamic data of the transferred page generated by the first device is statistically analyzed to obtain statistical data. When the statistical data meets the data transmission conditions, the untransmitted transferred page dynamic data and the corresponding bound task identifier are sent to the second device, so that the second device can merge the page dynamic data according to the task identifier and the page component identifier.

7. The method according to claim 1, characterized in that, The first device and the second device have the same operating system and the same user permissions.

8. A data transmission and processing device based on task transfer, applied to the first device in a multi-device linkage system, characterized in that, The device includes: The data acquisition module is used to acquire the task identifier of the application task transferred by the second device when the first device receives the application task transfer instruction from the second device; the task identifier is determined by the second device when the application task is generated. The event listening module is used to listen for changes in the application page of the corresponding target application during the execution of the application task on the first device, and to obtain dynamic data of the page after the transfer. The data association module is used to bind the dynamic data of the transferred page with the task identifier; The data transmission module is used to send the transferred page dynamic data and the bound task identifier to the target device, so that the target device can merge the corresponding pre-transfer page dynamic data and the transferred page dynamic data according to the task identifier.

9. A data transmission and processing device based on task transfer, characterized in that, The data transmission and processing device based on task transfer includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data transfer processing method based on task transfer as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the data transfer processing method based on task transfer as described in any one of claims 1-7.

Images