A data processing method, apparatus, and system

Abstract

The application provides a data processing method, device and system, wherein a first application is deployed in a second device. First, the first device acquires a first execution request sent by the second device, and the first execution request comprises a first operation instruction for operating the first application in the first device. When the first device determines that the first resource data does not exist in the first device according to the first execution request, the first device sends a first synchronization request to the second device, wherein the first resource data is data required by the first device for executing the first operation instruction, and the first synchronization request is used for indicating that the first resource data does not exist in the first device. Finally, the first device acquires the first resource data sent by the second device, and executes the first operation instruction based on the first resource data. The data processing method provided by the application can realize high-speed data transmission and seamless flow between the first device and the second device.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of Internet of Things, and in particular to a data processing method, device and system for vehicle terminal and mobile terminal. BACKGROUND

[0002] The seamless data flow technology refers to a technology allowing seamless exchange of information and applications between one device and another. This technology can provide a coherent and seamless user experience, that is, it can realize no delay in running the tasks issued by the user on different devices, and can continue to complete or switch the tasks on another device.

[0003] The current seamless data flow technology for vehicle terminal and mobile terminal is still in its infancy. In order to realize this technology, the vehicle system needs to be integrated with various devices and operating systems to meet the compatibility, so it is necessary to open up the mobile device manufacturers and customize the software development, which makes it necessary to implement the seamless data flow technology for vehicle terminal and mobile terminal with a huge workload. SUMMARY

[0004] The present application provides a data processing method, device and system. The data processing method provided by the present application directly connects the second device with the OS system of the first device to realize the discovery connection and data transmission between devices, and monitors the system state of the first device and the second device and the user instruction in real time during the data flow process to ensure the realization of seamless data flow. At the same time, the data processing method provided by the present application can not only realize the seamless data flow of the first device and the second device carrying different types of systems, but also realize the seamless data flow of the first device and the second device in different application resources.

[0005] In a first aspect, a data processing method is provided, which is applied to data transmission between a first device and a second device, wherein the second device is deployed with a first application. First, the first device obtains a first execution request sent by the second device. The first execution request includes a first operation instruction for operating the first application on the first device. Second, the first device determines whether there is first resource data in the first device according to the first execution request. The first resource data is the data required by the first device to execute the first operation instruction. Third, in the case that the first device determines that there is no first resource data, the first device sends a first synchronization request to the second device. The first synchronization request is used to indicate that there is no first resource data in the first device. Finally, the first device obtains the first resource data sent by the second device, and executes the first operation instruction based on the first resource data.

[0006] In some possible embodiments, after the first operation instruction is executed based on the first resource data, the method further includes the following steps: first, when the first device detects a first operation event, the first device sends a second synchronization request to the second device, wherein the first operation event includes an event in which a user operates the first application on the first device, the second synchronization request includes an identifier of the first application and application operation data, and the application operation data includes an instruction or coordinates triggered by the first operation event; second, the first device acquires second resource data and a second operation instruction sent by the second device, wherein the second operation instruction is an instruction triggered by the first operation event, the second resource data is data required by the first device to execute the second operation instruction, and the second resource data and the second operation instruction are determined by the second device based on the application operation data; and third, the first device executes the second operation instruction based on the second resource data.

[0007] In some possible embodiments, the first device stores first monitoring data, and the first monitoring data includes an identifier of an application deployed on the first device and a running state of the application deployed on the first device. The method further includes the following steps: first, the first device determines the running state of the first application after the first device executes the second operation instruction, and the running state of the first application includes a user interface (UI) state, a control activation state, and an application display state; and second, the first device writes the running state of the first application after the first device executes the second operation instruction into the first monitoring data.

[0008] In some possible embodiments, the first device determines whether the first resource data exists in the first device based on the first execution request, including the following steps: first, the first device determines whether the first resource data exists in the first device by comparing the identifier of the first application in the first execution request with first monitoring data, wherein the first monitoring data includes an identifier of an application deployed on the first device and a running state of the application deployed on the first device; second, when the first monitoring data contains the identifier of the first application, the first device determines that the first resource data exists in the first device; and third, when the first monitoring data does not contain the identifier of the first application in the first execution request, the first device determines that the first resource data does not exist in the first device.

[0009] In some possible embodiments, the data processing method provided in the application further includes, when the first device determines that the first resource data exists, executing the first resource data based on the first operation instruction.

[0010] In some possible embodiments, after the first device runs the first resource data according to the first operation instruction, the method further includes the following steps: first, in the case that the first device detects a second operation event, the first device generates a third operation instruction in response to the second operation event. The second operation event includes an event that a user operates the first application on the first device. Second, the first device acquires third resource data according to the third operation instruction, and executes the third operation instruction based on the third resource data. Finally, after the first device determines the response to the second operation event, the first device sends a third synchronization request to the second device. The third synchronization request includes the identification of the first application and the third operation instruction, so that the second device determines the running state of the first application on the first device according to the third operation instruction.

[0011] In some possible embodiments, the first device mentioned in the foregoing is a vehicle-mounted device, and the second device is a mobile device.

[0012] In the second aspect, a data processing apparatus is provided, which is applied to a first device and includes an operating system (OS) module, an instruction monitoring module, and an instruction management module.

[0013] First, the instruction monitoring module is configured to acquire a first execution request sent by a second device. The first execution request includes a first operation instruction for operating a first application, and the second device is deployed with the first application. The instruction monitoring module is further configured to determine whether the first resource data exists in the OS module according to the first execution request. The first resource data is data required by the OS module to execute the first operation instruction. The instruction monitoring module is further configured to send a first synchronization request to the second device in the case that the OS module does not exist the first resource data. The first synchronization request is used to indicate that the first resource data does not exist in the OS module. Second, the OS module is configured to acquire the first resource data from the second device, and execute the first operation instruction based on the first resource data.

[0014] In some possible embodiments, the instruction monitoring module is further configured to send a second synchronization request to the second device in the case that the OS module detects a first operation event. The first operation event includes a triggering event of a user operating the first application, and the second synchronization request includes the identification of the first application and application operation data. The application operation data includes an instruction or coordinates triggered by the first operation event. The instruction monitoring module is further configured to acquire a second operation instruction. The second operation instruction is used to instruct the OS module to respond to the first operation event. The OS module is further configured to acquire second resource data from the second device, and execute the second operation instruction based on the second resource data. The second resource data includes data required to execute the second operation instruction.

[0015] In some possible embodiments, the data processing apparatus provided in the present application further comprises an instruction management module. The instruction management module is configured to store first monitoring data. The first monitoring data comprises an identifier of a deployed application of the OS module and a running state of the deployed application. The instruction management module is further configured to determine the running state of the first application after execution of the second operation instruction. The running state of the first application comprises a user interface (UI) state, a control activation state and an application display state. The instruction management module is further configured to write the running state of the first application after execution of the second operation instruction into the first monitoring data.

[0016] In some possible embodiments, the instruction monitoring module is further configured to call the first monitoring data from the instruction management module after obtaining the first execution request. The first monitoring data comprises an identifier of a deployed application resource of the OS module. The instruction monitoring module is further configured to determine whether the OS module has the first resource data by comparing the identifier of the first application in the first execution request with the first monitoring data. Specifically, when the first monitoring data contains the identifier of the first application, the instruction monitoring module determines that the OS module has the first resource data; when the first monitoring data does not contain the identifier of the first application in the first execution request, the instruction monitoring module determines that the OS module does not have the first resource data.

[0017] In some possible embodiments, the OS module is further configured to run the first resource data according to the first operation instruction when the instruction monitoring module determines that the OS module has the first resource data.

[0018] In some possible embodiments, the OS module is further configured to generate a third operation instruction to respond to a second operation event when the second operation event is detected. The second operation event comprises an event in which a user operates the first application on the first device. The OS module is further configured to obtain third resource data according to the third operation instruction, and execute the third operation instruction based on the third resource data. The instruction monitoring module is further configured to send a third synchronization request to the second device. The third synchronization request comprises an identifier of the first application and the third operation instruction for synchronizing the second operation event, so that the second device determines the running state of the first application on the first device according to the third operation instruction.

[0019] In some possible embodiments, the first device involved in the data processing apparatus provided in the present application is a vehicle-mounted device, and the second device is a mobile device.

[0020] In a third aspect, a data processing system is provided, including a first device and a second device, and the second device is deployed with a first application. The second device is configured to send a first execution request to the first device, where the first execution request includes an identification of the first application and a first operation instruction for operating the first application on the first device. The first device is configured to determine whether the first resource data exists in the first device according to the first execution request, where the first resource data is data required for the first device to execute the first operation instruction. The first device is further configured to send a first synchronization request to the second device if the first device determines that the first resource data does not exist in the first device, where the first synchronization request is used to indicate that the first resource data does not exist in the first device. The second device is further configured to send the first resource data to the first device according to the first synchronization request. The first resource data can include data of the first application used to respond to the first execution request, and in some specific examples, can include data in the form of user interface components and layouts, streaming media content data, and the like, without limitation. The first device is further configured to obtain the first resource data and execute the first operation instruction based on the first resource data.

[0021] In some possible embodiments, after executing the first operation instruction based on the first resource data, the first device is further configured to send a second synchronization request to the second device if the first device detects a first operation event. The first operation event includes an event of a user operating the first application on the first device, and the second synchronization request includes the identification of the first application and application operation data, where the application operation data includes an instruction or coordinates triggered by the first operation event. The second device is configured to determine second resource data and a second operation instruction according to the second synchronization request. The second operation instruction is an instruction triggered by the first operation event, and the second resource data is data required for the first device to execute the second operation instruction. The second resource data and the second operation instruction are determined by the second device according to the application operation data. The second device is further configured to send the second resource data and the second operation instruction to the first device. The first device is further configured to obtain the second resource data and the second operation instruction sent by the second device, and execute the second operation instruction according to the second resource data.

[0022] In some possible embodiments, the first device is further configured to store first monitoring data. The first monitoring data includes an identification of the deployed application resource of the first device and a running state of the deployed application resource. The second device is further configured to store second monitoring data. The second monitoring data includes an identification of the deployed application resource of the second device and a running state of the deployed application resource. The second device is further configured to determine the running state of the first application after responding to the second synchronization request. The running state of the first application includes a user interface (UI) state, a control activation state, and an application display state. The second device is further configured to write the resource sending history of the first application after responding to the second synchronization request into the second monitoring data. The first device is further configured to determine the running state of the first application after executing the second operation instruction. The first device is further configured to write the running state of the first application after executing the second operation instruction into the first monitoring data.

[0023] In some possible embodiments, the first device is configured to determine whether the first device has the first resource data by comparing the identification of the first application in the first execution request with the first monitoring data. The first monitoring data includes an identification of the deployed application resource of the first device and a running state of the deployed application resource. The first device is further configured to determine that the first device has the first resource data when the first monitoring data contains the identification of the first application. The first device is further configured to determine that the first device does not have the first resource data when the first monitoring data does not contain the identification of the first application in the first execution request.

[0024] In some possible embodiments, the first device is configured to execute the first resource data according to the first operation instruction when the first device determines that the first device has the first resource data.

[0025] In some possible embodiments, the second device includes second monitoring data. The second monitoring data includes an identification of the deployed application resource of the second device and a running state of the deployed application resource. The first device is further configured to respond to a second operation event when the first device detects the second operation event. The second operation event includes an event in which a user operates the first application on the first device. The first device is further configured to obtain third resource data according to a third operation instruction, and execute the third operation instruction based on the third resource data. The first device is further configured to send a third synchronization request to the second device. The third synchronization request includes an identification of the first application and the third operation instruction for synchronizing the second operation event on the second device, so that the second device determines the running state of the first application on the first device according to the third operation instruction. The second device is further configured to update the second monitoring data according to the third synchronization request. The second monitoring data includes an identification of the deployed application resource of the second device and a running state of the deployed application resource.

[0026] In some possible embodiments, the first device in the data processing system provided by the present application is a vehicle-mounted device, and the second device is a mobile device.

[0027] In a fourth aspect, a computing device is provided, which includes a processor and a memory, the memory is configured to store instructions, and the processor is configured to execute the instructions so that the computing device implements the method of any of the embodiments of the first aspect.

[0028] In a fifth aspect, a computer readable storage medium is provided, which stores instructions, and the instructions are executed by a computing device to implement the method of any of the embodiments of the first aspect.

[0029] In a sixth aspect, a vehicle is provided, which includes the data processing apparatus according to the second aspect or any of the possible embodiments of the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0030] Figure 1 is a schematic diagram of a data processing system between a vehicle-mounted system and a mobile device provided by the present application;

[0031] Figure 2 is a flowchart of a data processing method of a first device and a second device provided by the present application;

[0032] Figure 3 is a flowchart of a data processing method of a first device and a second device provided by the present application;

[0033] Figure 4 is a schematic diagram of a data processing apparatus provided by the present application;

[0034] Figure 5 is a structural schematic diagram of a computing device provided by the present application. DETAILED DESCRIPTION

[0035] In order to make the purpose, technical scheme and advantages of the present application clearer, the technical scheme of the present application will be described in detail below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0036] In the description of the present application, unless otherwise explicitly limited, the setting words such as words should be interpreted in a broad sense, and those skilled in the art can reasonably determine the specific meaning of the above words in the present application in combination with the specific content of the technical scheme.

[0037] In the description of the present application, the description of the terms "one embodiment", "some embodiments", "exemplary embodiment", "example", "specific embodiment", or "some examples" means that the specific features or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In the present specification, the exemplary description of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features or characteristics described can be combined in any suitable manner in one or more embodiments or examples. For the understanding of the relevant person, the application scenarios and data processing systems involved in the present application will be introduced in the following with one embodiment.

[0038] The application scenarios and data processing systems involved in the present application will be introduced in the following with one specific embodiment.

[0039] Please refer to Figure 1 , Figure 1 The present application provides a schematic diagram of a data processing system between a vehicle-mounted system and a mobile device. The application scenario provided in the present embodiment includes a first device 110 and a second device 120, the first device 110 is arranged at the vehicle terminal with the vehicle-mounted system, and the second device 120 is arranged at the mobile terminal with the mobile phone system. When one of the first device 110 or the second device 120 has the need of data flow, the seamless exchange of data information between the first device 110 (the vehicle-mounted system in the present embodiment) and the second device 120 (the smart phone system in the present embodiment) is realized through the data flow method provided in the present application.

[0040] Among the application scenarios shown in the present embodiment, the data flow between the first device 110 and the second device 120 can specifically include one or more of a data synchronization function, an application continuity function, a voice assistant integration function, a networking services function, and a multi-screen collaboration function. Among them, the data synchronization function can be a data flow between the first device 110 and the second device 120 for real-time synchronization of personal information, preference settings, maps, playlists, etc. of the user between the car machine system and other devices. The application continuity function can be a data flow between the first device 110 and the second device 120 for the user to start using a certain application, such as navigation or music playing, and then seamlessly flow from one device to another and continue to use, or vice versa. The voice assistant integration function can be a data flow that allows hands-free operation and cross-device instruction execution through an integrated AI voice assistant (such as Google Assistant, Siri, or other custom voice assistants) of the first device 110 or the second device 120. The networking services function provides a consistent user experience between the first device 110 and the second device 120 through data synchronization and application state management using cloud services and the Internet. The multi-screen collaboration function can be a data flow technology that can extend the screen content of the first device 110 to the second device 120, or push the screen content of the second device 120 to the first device 110.

[0041] Figure 1The illustration demonstrates an application scenario for a data processing system between an in-vehicle infotainment system and a mobile device. It is understood that the device types of the first device 110 and the second device 120 provided in this embodiment are merely examples. In other possible application scenarios, the first device 110 or the second device 120 may also include one or more devices with data exchange capabilities, such as smartphones, tablet computers, smartwatches, laptop computers, home automation devices, wearable health devices, virtual reality devices, augmented reality devices, cloud storage and cloud computing servers, etc. Furthermore, depending on the different device types of the first device 110 and the second device 120, for… Figure 1 The data transfer application scenarios shown can be not only the interactive sharing and playback of streaming media data such as video or audio, but also a variety of other application scenarios such as personal data transfer, mobile office document processing, smart home control, health monitoring and emergency services, etc., which are not limited here.

[0042] pass Figure 1 As can be easily understood from the embodiments shown, there is a strong demand and broad application prospects for achieving seamless data transfer between devices. Therefore, providing a data transfer solution that enables rapid response between devices is of practical significance.

[0043] The following two embodiments illustrate a data processing method between a first device and a second device provided in this application. This method achieves device discovery, connection, and data transmission by directly connecting the second device to the OS system of the first device. Furthermore, it monitors the system status and user commands of both devices in real time during the data transfer process to ensure seamless data flow. Moreover, this method can achieve seamless data transfer not only between multiple second devices running different types of systems and the first device, but also between the first and second devices using different application resources.

[0044] Please see Figure 2 , Figure 2 This is a flowchart illustrating a data processing method using a first device and a second device provided in this application. The data processing method using the first device and the second device provided in this embodiment can be applied to…Figure 1 The vehicle-mounted system and the mobile device are shown between the data processing system. In this embodiment, including the first device and the second device, wherein the second device is deployed with the first application, however the first device is not deployed with the first application. The specific steps are as follows:

[0045] S201: The second device sends the first execution request to the first device.

[0046] The first execution request sent by the second device to the first device includes the identification of the first application and the first operation instruction for operating the first application in the first device, and the first execution request is used to indicate the first operation instruction corresponding to the first execution request in the first device. The first execution request given in this embodiment can be the case that the second device sends the execution request to the first device for the first time, and can also be the case that the second device sends the execution request to the first device for the Nth time, without limitation, wherein N is a positive integer.

[0047] S202: The first device determines whether the first resource data exists in the first device according to the first execution request.

[0048] The first resource data is the data required by the first device to execute the first operation instruction. Since the operation instruction contained in the first execution request needs to be run on the first application to realize the function, the first device needs to determine whether the first application is deployed on the first device and whether the first resource data exists.

[0049] In some specific examples, the first device saves the first monitoring data, wherein the first monitoring data includes the identification of the deployed application resource in the first device and the running state of the deployed application resource. The first device calls the identification of the deployed application resource in the first monitoring data, and compares the identification with the identification of the first application in the first execution request to determine whether the first application exists in the first device. Specifically, in the case that the first monitoring data contains the identification of the first application in the first execution request, the first device determines that the first device has the first resource data; in the case that the first monitoring data does not contain the identification of the first application in the first execution request, the first device determines that the first device does not have the first resource data.

[0050] It can be understood that whether the identification of the deployed application resource and the running state of the deployed application resource in the first monitoring data, or the identification of the first application in the first execution request, these identifications are identifiers after the same processing. The command data of the device operating system, the service type data and the unique identifier of the application resource and other data are converted into unified instruction identification data according to the universal data structure.

[0051] In some possible examples, the first monitoring data is further used to record a history of instruction data interaction between the first device and the second device. The first monitoring data is updated each time the first device and the second device perform data transmission or instruction interaction.

[0052] S203: In a case where the first device determines that the first resource data does not exist, the first device sends a first synchronization request to the second device.

[0053] Since the first device of the embodiment is not deployed with the first application, after the first device compares the first monitoring data with the identifier of the first application of the first execution request, the first device determines that the first resource data does not exist in the first device. Subsequently, in response to the first execution request of the second device, the first device generates the first synchronization request and sends the first synchronization request to the second device, where the first synchronization request is used to indicate that the first resource data does not exist in the first device.

[0054] In some specific embodiments, the first synchronization request is used to update the first monitoring data before being sent to the second device, so as to record the history of instruction data interaction between the first device and the second device.

[0055] S204: The second device sends the first resource data to the first device according to the first synchronization request.

[0056] In some specific examples, the second device stores second monitoring data, where the second monitoring data includes identifiers of deployed application resources of the second device and running states of the deployed application resources, and is further used to record the history of instruction data interaction between the first device and the second device. Therefore, after the second device obtains the first synchronization request from the first device, the second monitoring data is updated according to the first synchronization request.

[0057] Subsequently, the second device determines the first resource data required to be sent to the first device according to the first synchronization request, where the first resource data includes data required for the first device to respond to the first execution request and execute the first operation instruction, and the first operation instruction is used to implement the operation instruction of the first execution request in the first device.

[0058] The first application resource data can include all data or partial data for implementing all functions of the first application. However, for the technical effect of seamless data flow conversion of the present method, the first application resource data is usually only a part of the application resource data of the first application, and usually is the minimum amount of data for implementing the first execution request, including a user interface (UI), a component layout form of the user interface, and content data necessary for implementing the first operation instruction. The content data varies according to different first applications and first operation instructions, and is not limited. For example, in the case where the first application is a music application or a video application, the content data can be one or more stream media data, such as audio stream data and video stream data.

[0059] For implementing the data flow conversion method provided in the present application, the process of sending the first resource data by the second device to the first device does not need to go through synchronization or updating of the second monitoring data and the first monitoring data. In some specific examples, the first resource data can be directly sent into the operating system (OS) framework of the first device through the software development kit (SDK) framework of the second device, so as to accelerate the data flow conversion speed between the first device and the second device and realize the function of seamless data flow conversion.

[0060] S205: The first device acquires the first resource data sent by the second device, and executes the first operation instruction based on the first resource data.

[0061] After the first device acquires the first resource data sent by the second device, the operating system of the first device executes the first operation instruction based on the first resource data.

[0062] In some specific examples, the first device writes an event of receiving the first resource data into the first monitoring data, and at this time, the first monitoring data monitors and updates the running state of the first application resource in the first device in real time.

[0063] S206: In the case where the first device detects the first operation event, the first device sends a second synchronization request to the second device.

[0064] The first operation event includes an event of operating the first application by the user on the first device, and the second synchronization request includes an identifier of the first application and application operation data, and the application operation data includes an instruction or a coordinate triggered by the first operation event.

[0065] In some specific examples, in the case that the user triggers the first operation event on the first device, the first device first determines whether there is an application resource locally (the first device itself) for responding to the first operation event. In the case that the first device determines that there is no application resource locally for responding to the first operation event, the first device sends a synchronization request to the second device; in the case that the first device determines that there is an application resource locally for responding to the first operation event, the process of the first device responding to the second operation event can be seen in steps S304-S305, and will not be described again.

[0066] S207: The second device determines the second resource data and the second operation instruction according to the second synchronization request, and sends the second resource data and the second operation instruction to the first device.

[0067] In some specific examples, the second device stores second monitoring data, which includes the identification of the deployed application resource of the second device and the running state of the deployed application resource, and further records the history of the instruction data interaction between the first device and the second device. Therefore, after the second device obtains the second synchronization request from the first device, the second monitoring data will be updated according to the second synchronization request.

[0068] Subsequently, the second device determines the second resource data and the second operation instruction required to be sent to the first device according to the second synchronization request, the second resource data including the data required for the first device to respond to the first operation event and execute the second operation instruction, and the second operation instruction being used for the operation instruction of the first operation event on the first device.

[0069] The second application resource data can include all data or part of data for implementing all functions of the first application, however, in order to achieve the technical effect of seamless data flow of the method, the second application resource data is usually only a part of the application resource data of the first application, and usually is the minimum amount of data required for the first device to respond to the first operation event, including the user interface (User Interface), the component layout form of the user interface, and the content data necessary for the first device to respond to the first operation event, which varies according to the first application and the first operation event, and is not limited. For example, in the case that the first application is a music application or a video application, the content data can be one or more stream media data such as audio stream data and video stream data.

[0070] To implement the data flow conversion method provided in the present application, the process of the second device sending the second resource data to the first device does not need to go through the synchronization or updating of the second monitoring data and the first monitoring data. In some specific examples, the second resource data can be directly sent into the operating system (OS) framework of the first device through the software development kit (SDK) framework of the second device, thereby accelerating the data flow conversion speed between the first device and the second device to realize the function of seamless data flow conversion.

[0071] S208: The first device acquires the second resource data and the second operation instruction sent by the second device, and executes the second operation instruction according to the second resource data.

[0072] After the first device acquires the second resource, it has the ability to respond to the first operation event, and then the first device executes the second operation instruction according to the second resource data to respond to the first operation event of the user.

[0073] In some specific examples, the first device can also determine the running state of the first application after executing the second operation instruction, and write the running state of the first application after responding to the second operation instruction into the first monitoring data.

[0074] It can be seen that steps S206-S208 show the flow steps of the event that the user operates the first application on the first device after the first device acquires the first resource data. In other possible embodiments, when the user repeatedly operates the flow steps of the first application on the second device, the specific content shown in steps S201-S205 can be referred to, and will not be described again.

[0075] Please refer to Figure 3 , Figure 3 Another flowchart of the data flow conversion method between the first device and the second device provided in the present application. The data flow conversion method between the first device and the second device provided in the present embodiment can be applied to the data flow conversion system between the vehicle-mounted system and the mobile device shown in Figure 1 In the present embodiment, it includes the first device and the second device, wherein the second device is deployed with the first application, and the first device is also deployed with the first application. The specific steps are as follows:

[0076] S301: The second device sends a first execution request to the first device.

[0077] The first execution request sent by the second device to the first device includes the identification of the first application and the first operation instruction for operating the first application on the first device, and the first execution request is used to instruct the first device to respond to the first operation instruction corresponding to the first execution request.

[0078] S302: The first device determines whether the first resource data exists in the first device according to the first execution request.

[0079] The first resource data is data required by the first device to execute the first operation instruction. Since the operation instruction contained in the first execution request needs to run on the first application to realize the function, the first device needs to determine whether the first application is deployed on the first device and whether the first resource data exists.

[0080] In some specific examples, the first device stores first monitoring data, wherein the first monitoring data includes the identification of the deployed application resources of the first device and the running state of the deployed application resources. The first device calls the identification of the deployed application resources in the first monitoring data, and compares the identification with the identification of the first application in the first execution request to determine whether the first application exists on the first device. Specifically, in the case that the first monitoring data contains the identification of the first application in the first execution request, the first device determines that the first resource data exists in the first device; in the case that the first monitoring data does not contain the identification of the first application in the first execution request, the first device determines that the first resource data does not exist in the first device.

[0081] It can be understood that, whether it is the identification of the deployed application resources in the first monitoring data and the running state of the deployed application resources, or the identification of the first application in the first execution request, these identifications are identifiers after homogenization processing. Through the device operating system command data, service type data, and unique identifier of the application resource, etc., the data is converted into unified instruction identification data according to the universal data structure.

[0082] In some possible examples, the first monitoring data is also used to record the instruction data interaction history between the first device and the second device. The first monitoring data is updated every time the first device and the second device perform data transmission or instruction interaction.

[0083] S303: In the case that the first device determines that the first resource data exists, the first device runs the first resource data according to the first operation instruction.

[0084] Since the first device of the embodiment deploys the first application, after the first device compares the first monitoring data and the identification of the first application in the first execution request, the first device will obtain the result that the first resource data exists in the first device. Subsequently, the first device exists the first resource data locally to respond to the first execution request from the second device in response to the first execution request of the second device.

[0085] In some specific examples, after the first device determines that the first resource data exists locally, the first device updates the first monitoring data according to the running state of the first application, and sends synchronization information to the second device, where the synchronization information is used to indicate the first device to the second device that the first resource data exists.

[0086] In some specific examples, the second device stores second monitoring data, where the second monitoring data includes the identification of the deployed application resource of the second device and the running state of the deployed application resource, and the second monitoring data is also used to record the instruction data interaction history between the first device and the second device. Therefore, after the second device obtains the synchronization information from the first device, the second monitoring data is updated according to the synchronization information.

[0087] S304: In the case that the first device detects the second operation event, the first device responds to the second operation event, and sends a third synchronization request to the second device.

[0088] The second operation event includes the event that the user operates the first application on the first device, and the third synchronization request includes the identification of the first application and the instruction for synchronizing the second operation event on the second device.

[0089] In some specific examples, in the case that the user triggers the second operation event on the first device, the first device first determines whether the third application resource for responding to the second operation event exists locally (in the first device itself). In the case that the first device determines that the third application resource for responding to the second operation event exists locally, the first device generates a third operation instruction, and executes the third operation instruction based on the third resource data to respond to the second operation event. Then, the first device determines the third synchronization request, and sends the third synchronization request to the second device. The third synchronization request includes the identification of the first application and the third operation instruction for synchronizing the second operation event on the second device, so that the second device determines the running state of the first application in the first device according to the third operation instruction.

[0090] In the case that the first device determines that the application resource for responding to the first operation event does not exist locally, the process that the first device responds to the second operation event can be referred to steps S206-S208, and will not be described herein.

[0091] S305: The second device synchronizes the second monitoring data according to the third synchronization request, and sends the second resource data and the second operation instruction to the first device.

[0092] In some specific examples, the second device stores second monitoring data, which includes the identification of the deployed application resource of the second device and the running state of the deployed application resource, and which is used to record the instruction data interaction history between the first device and the second device. Therefore, after receiving the third synchronization request, the second device synchronizes the second monitoring data according to the third synchronization request, which includes the identification of the deployed application resource of the second device and the running state of the deployed application resource.

[0093] It can be seen that steps S304-S305 show the flow steps of the event that the user operates the first application on the first device after the first device acquires the first resource data. In other possible embodiments, when the user repeatedly operates the flow steps of the first application on the second device, the specific content shown in steps S301-S303 can be referred to, and will not be described again.

[0094] The foregoing introduces a data processing method and system provided by the present application. Next, a data processing device provided by the present application is introduced.

[0095] Please refer to Figure 4 , Figure 4 is a schematic diagram of a data processing device provided by the present application. The data processing device provided by the present embodiment can be applied to the data processing system shown in Figure 1 and is used to implement the data processing method shown in steps S201-S208 and steps S301-S305. The data processing device 400 of the present embodiment includes a first device 410 and a second device 420. In the present embodiment, the first application is not deployed in the first OS framework 415 included in the first device 410, and the first application is deployed in the second device 420. Each device of the present embodiment has at least one software development kit (SDK) framework and one operating system (OS) framework.

[0096] First, the first device 410 is introduced, which includes a first SDK framework 411 and a first OS framework 415. The first SDK framework 411 includes a first instruction type virtualization module 412 and a first monitoring module 414, and the first OS framework 415 includes a distributed soft bus 416.

[0097] For the first instruction type virtualization module 412, used for storing and updating the first monitoring data, wherein the first monitoring data includes the identification of the application resources deployed by the first device and the running state of the deployed application resources. It can be understood that the identification of the deployed application resources and the running state of the deployed application resources in the first monitoring data are identifiers that have been unified by the first instruction type virtualization module 412. By converting the command data, service type data, and unique identifier of the application resource stored in the first OS framework 415 into unified instruction identifier data according to the universal data structure, the first instruction type virtualization module 412 can be understood. In some possible examples, the first monitoring data is also used to record the instruction data interaction history between the first device 410 and the second device 420. In the case of each data transmission or instruction interaction between the first device 410 and the second device 420, the first monitoring data is updated.

[0098] For the first monitoring module 414, used for real-time data interaction with the second monitoring module 422 in the second device 420, monitoring the record of data transmission and instruction flow between the first device 410 and the second device 420. At the same time, the first monitoring module 414 is also used to retrieve the first monitoring data from the first instruction type virtualization module 412 for comparison in the case of receiving the request or instruction of the second device 420, to determine the next operation of the first device 410. Furthermore, the first monitoring module 414 is also used to monitor the application resource data in the first OS framework 415 that may come from the second device 420 in real time.

[0099] For the first OS framework 415, including a distributed soft bus 416. The first OS framework 415 is used to deploy and run application resources and software programs, and obtain application resource data from the second device 420 through the distributed soft bus 416. At the same time, the first OS framework 415 is also used to obtain the request instruction from the first SDK framework 411 and perform operations according to the request. Furthermore, the first OS framework 415 is also used to interact with the first instruction type virtualization module 412, so that the first instruction type virtualization module 412 obtains the deployed application resources and the application running state in the first OS framework 415, so that the first instruction type virtualization module 412 realizes the update and synchronization of the first monitoring data.

[0100] Next, the second device 420 is introduced, including a second SDK framework 421 and a second OS framework 423. The second SDK framework 421 includes a second monitoring module 422, a second instruction type virtualization module 424, a distributed virtualization 426, and a device management module 428.

[0101] For the second monitoring module 422, it is used to record the data transmission and instruction flow between the first device 410 and the second device 420 by interacting with the first monitoring module 414 in the first device 410 in real time. Meanwhile, the second monitoring module 422 is also used to retrieve the second monitoring data from the second instruction virtualization module 424 for comparison to determine the next operation of the second device 420 upon receiving the request or instruction of the first device 410. Furthermore, the second monitoring module 422 is also used to monitor the application resource data sent by the device management module 428 to the first device 410 in real time.

[0102] For the second instruction virtualization module 424, it is used to store and update the second monitoring data, wherein the second monitoring data includes the identification of the deployed application resource of the second device and the running state of the deployed application resource. It can be understood that the identification of the deployed application resource and the running state of the deployed application resource in the second monitoring data are identifiers processed by the second instruction virtualization module 424. The command data, service type data, and unique identifier of the application resource stored in the second OS framework 423 are converted into unified instruction identifier data according to the universal data structure. In some possible examples, the second monitoring data is also used to record the instruction data interaction history between the first device 410 and the second device 420. The second monitoring data is updated each time the first device 410 and the second device 420 perform data transmission or instruction interaction.

[0103] For the distributed virtualization 426, it is used to distribute the related application resource of the first application and the instruction for operating the related application resource of the first application stored in the second OS framework 423 through the distributed virtualization 426 when the second device 420 needs to send the related application resource of the first application to the first device 410. On the one hand, for the data of the related application resource of the first application, such as application program data, streaming media data, and user interface data, the distributed virtualization 426 sends these data to the distributed soft bus in the first device 410 through the device management module 428, which is suitable for fast transmission of large amounts of data to realize seamless data flow between the first device 410 and the second device 420. On the other hand, for the instruction for operating the related application resource of the first application, such as the instruction for operating the application program data and the user interface data, the distributed virtualization 426 sends these data to the first monitoring module 414 in the first device 410 through the second monitoring module 422 to realize the interaction of the instruction.

[0104] The device management module 428 is used to receive relevant application resource data from the first application in the distributed virtualization 426, and send the relevant application resource data of the first application to the first OS framework 415 through the distributed soft bus 416 in the first OS framework 415. In some possible embodiments, the device management module 428 of the second device 420 is also used to realize the discovery connection and data flow between the first device 410 and the second device 420 through the distributed soft bus 416 of the first device 410, and to perform parallel high-speed data transmission through this link to achieve seamless data flow between the first device 410 and the second device 420.

[0105] The second OS framework 423 is used to deploy and run application resources and software programs. Simultaneously, the second OS framework 423 is also used to receive request instructions from the second SDK framework 421 and execute operations based on those requests. Furthermore, the second OS framework 423 is also used to interact with the second instruction-based virtualization module 424, enabling the second instruction-based virtualization module 424 to obtain the application resources and application running status deployed within the second OS framework 423, thus allowing the second instruction-based virtualization module 424 to update and synchronize the second monitoring data.

[0106] It is understood that this embodiment only introduces the functions of the first device 410, the second device 420, and each component. For more information on the first device 410, the first SDK framework 411, the first OS framework 415, the first instruction-based virtualization module 412, the first monitoring module 414, and the distributed soft bus 416, please refer to [the relevant documentation / reference needed]. Figure 1 The detailed descriptions of the illustrated embodiments and steps S201-S208 and S301-S305 will not be repeated here. For more information on the second device 420, the second SDK framework 421, the second OS framework 423, the second monitoring module 422, the second instruction-based virtualization module 424, the distributed virtualization 426, and the device management module 428, please refer to [reference needed]. Figure 1 The specific details of the illustrated embodiments and steps S201-S208 and S301-S305 will not be repeated here.

[0107] Figure 5 This is a schematic diagram of the structure of a computing device provided in this application. The computing device can be as described above. Figure 1 The various devices of the data processing system in the illustrated embodiment, or Figure 4 The various modules of the data processing apparatus in the illustrated embodiment.

[0108] Further, the computing device includes a processor 501, a storage unit 502, a storage medium 503, and a communication interface 504, wherein the processor 501, the storage unit 502, the storage medium 503, and the communication interface 504 communicate through a bus 505, and also communicate through other means such as wireless transmission.

[0109] The processor 501 is composed of one or more general-purpose processors, such as a CPU, an NPU, or a combination of a CPU and a hardware chip. The hardware chip is an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD is a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), a data processing unit (DPU), a system on chip (SoC), or any combination thereof. The processor 501 executes various types of digital storage instructions, such as program codes of software or firmware stored in the storage unit 502, which enables the computing device to provide a wide variety of services.

[0110] In a specific implementation, as an example, the processor 501 includes one or more CPUs, such as the CPU0 and the CPU1 shown in FIG. 5. Figure 5 In a specific implementation, as an example, the processor 501 includes one or more CPUs, such as the CPU0 and the CPU1 shown in FIG. 5.

[0111] In a specific implementation, as an example, the computing device also includes multiple processors, such as the processor 501 and the processor 506 shown in FIG. 5. Each of these processors can be a single-CPU or a multi-CPU. Here, the processor refers to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions). Figure 5

[0112] The storage unit 502 is used to store program codes and kernels, and is controlled by the processor 501 to perform the processing steps of the data processing method, apparatus, and system of any of the embodiments described above. The program codes include one or more software units. Figures 1 to 4

[0113] ​​Among the many possible examples, the storage unit 502 also includes read-only memory and random access memory, and provides instructions and data to the processor 501. The storage unit 502 also includes non-volatile random access memory. The storage unit 502 is either volatile or non-volatile, or both. The non-volatile memory is read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), or flash memory. The volatile memory is random access memory (RAM), which is used as the external cache. By way of example, and not limitation, many forms of RAM are used, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM). The hard disk (hard disk drive, HDD), the universal serial bus (USB), the flash, the secure digital memory Card (SD card), the memory stick, and the like, the hard disk is the hard disk drive (HDD), the solid state disk (SSD), the mechanical hard disk (HDD), and the like, which are not specifically limited in the present application.

[0114] The storage medium 503 is a carrier for storing data, such as a hard disk, a universal serial bus (USB) flash disk, a flash memory, a secure digital memory card (SD card), a memory stick, and the like. The hard disk can be a hard disk drive (HDD), a solid state disk (SSD), a mechanical hard disk (HDD), and the like, which are not specifically limited in the present application.

[0115] The communication interface 504 is a wired interface (for example, an Ethernet interface), an internal interface (for example, a Peripheral Component Interconnect express (PCIe) bus interface), a wired interface (for example, an Ethernet interface), or a wireless interface (for example, a cellular network interface or a wireless local area network interface), which is used for communication with other servers or units.

[0116] The bus 505 is a Peripheral Component Interconnect Express (PCIe) bus, or an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), and the like. The bus 505 is divided into an address bus, a data bus, a control bus, and the like.

[0117] In addition to the data bus, the bus 505 also includes a power supply bus, a control bus, and a status signal bus, and the like. However, for the purpose of clear illustration, all kinds of buses are marked as the bus 505 in the figure.

[0118] It should be noted that, Figure 5 Only one possible implementation of the embodiments of the present application is described above, and in actual applications, the computing device can further include more or fewer components, which are not limited herein. For the content not shown or described in the embodiments of the present application, please refer to the foregoing Figures 1 to 3 The related descriptions in the embodiments, which will not be repeated here.

[0119] The embodiments of the present application further provide a computer program product containing instructions. The computer program product can be software or program product containing instructions, which can run on a computing device or be stored in any available medium. When the computer program product runs on at least one computing device, the at least one computing device is caused to perform the data processing method provided by the present application.

[0120] The embodiments of the present application further provide a computer readable storage medium. The computer readable storage medium can be any available medium or data storage device containing one or more available media that is accessible by a computing device, such as a data center. The available medium can be a magnetic medium, such as a floppy diskette, a hard disk, a magnetic tape, an optical medium, such as a compact disk (CD), a digital video disk (DVD), or a semiconductor medium, such as a solid state disk, etc. The computer readable storage medium contains instructions, which instruct the computing device to perform the information identification method or instruct the computing device to perform the information identification method.

[0121] The above embodiments can be realized by software, hardware, firmware or any combination thereof, in whole or in part. When realized by software, the above embodiments can be realized in the form of a computer program product, in whole or in part. The computer program product contains a plurality of computer instructions. When the computer program instructions are loaded or executed on a computer, the flow or function according to the embodiments of the present application is generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another.

[0122] The above merely provides a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present application, and these modifications or replacements shall be encompassed in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data processing method, characterized by, The method is applied to data transmission between a first device and a second device, wherein the first device is a vehicle-mounted device, the second device is a mobile device, and the second device is deployed with a first application; the method comprises: The first device acquires a first execution request sent by the second device; wherein the first execution request comprises a first operation instruction for operating the first application on the first device; When the first device determines that the first resource data does not exist in the first device according to the first execution request, the first device sends a first synchronization request to the second device; wherein the first resource data is data required by the first device for executing the first operation instruction, and the first synchronization request is used for indicating that the first resource data does not exist in the first device; The first device acquires the first resource data sent by the second device, and executes the first operation instruction based on the first resource data; Before the first device sends the first synchronization request to the second device, the method further comprises: The first device determines whether the first resource data exists in the first device by comparing the identifier of the first application in the first execution request with first monitoring data; wherein the first monitoring data comprises identifiers of applications already deployed on the first device and running states of the applications already deployed; When the first monitoring data contains the identifier of the first application, the first device determines that the first resource data exists in the first device; When the first monitoring data does not contain the identifier of the first application, the first device determines that the first resource data does not exist in the first device.

2. The method of claim 1, wherein, After executing the first operation instruction based on the first resource data, the method further comprises: When the first device detects a first operation event, the first device sends a second synchronization request to the second device; wherein the first operation event comprises an event in which a user operates the first application on the first device, the second synchronization request comprises an identifier of the first application and application operation data, and the application operation data comprises an instruction or coordinates triggered by the first operation event; The first device acquires second resource data and a second operation instruction sent by the second device; wherein the second operation instruction is an instruction triggered by the first operation event, the second resource data is data required by the first device for executing the second operation instruction, and the second resource data and the second operation instruction are determined by the second device according to the application operation data; The first device executes the second operation instruction according to the second resource data.

3. The method of claim 2, wherein, The first device stores first monitoring data, and the first monitoring data comprises identifiers of applications already deployed on the first device and running states of the applications already deployed; the method further comprises: The first device determines a running state of the first application after the first device executes the second operation instruction, and the running state of the first application comprises a user interface (UI) state, a control activation state and an application display state; The first device writes a running state of the first application after executing the second operation instruction into the first monitoring data.

4. The method of claim 3, wherein, The method further comprises: In a case where the first device determines that the first resource data exists, the first device runs the first resource data according to the first operation instruction.

5. The method of claim 4, wherein, After the first device runs the first resource data according to the first operation instruction, the method further comprises: In a case where the first device detects a second operation event, the first device generates a third operation instruction in response to the second operation event, wherein the second operation event comprises an event that a user operates the first application on the first device; The first device acquires third resource data according to the third operation instruction, and executes the third operation instruction based on the third resource data; after the first device determines the response to the second operation event, the first device sends a third synchronization request to the second device; wherein the third synchronization request comprises an identifier of the first application and the third operation instruction, so that the second device determines a running state of the first application in the first device according to the third operation instruction.

6. A data processing apparatus, characterized by, Applied to a first device, comprising an operating system (OS) module, an instruction monitoring module and an instruction management module, wherein: The instruction monitoring module is configured to acquire a first execution request sent by a second device; wherein the first execution request comprises a first operation instruction for operating a first application, and the second device is deployed with the first application; The instruction monitoring module is further configured to, in a case where the instruction monitoring module determines that first resource data does not exist in the OS module according to the first execution request, send a first synchronization request to the second device; wherein the first resource data is data required by the OS module for executing the first operation instruction, and the first synchronization request is used to indicate that the first resource data does not exist in the OS module; The OS module is configured to acquire the first resource data from the second device, and execute the first operation instruction based on the first resource data; wherein the first device is a vehicle-mounted device, and the second device is a mobile device; The instruction monitoring module is further configured to: invoke first monitoring data from the instruction management module after acquiring the first execution request, wherein the first monitoring data comprises data of an identifier of a deployed application of the OS module; determine whether the first resource data exists in the OS module by comparing the identifier of the first application in the first execution request with the first monitoring data; wherein, in a case where the first monitoring data contains the identifier of the first application, the instruction monitoring module determines that the first resource data exists in the OS module; in a case where the first monitoring data does not contain the identifier of the first application, the instruction monitoring module determines that the first resource data does not exist in the OS module.

7. The apparatus of claim 6, wherein, The instruction monitoring module is further configured to send a second synchronization request to the second device in a case where the OS module detects a first operation event; the first operation event includes a trigger event in a case where a user operates the first application, and the second synchronization request includes an identifier of the first application and application operation data, and the application operation data includes an instruction or coordinates triggered by the first operation event; The instruction monitoring module is further configured to obtain a second operation instruction from the second device; the second operation instruction is used to respond to instruction data of the first operation event by the OS module; The OS module is further configured to obtain second resource data from the second device, and execute the second operation instruction based on the second resource data; the second resource data includes data required for executing the second operation instruction.

8. The apparatus of claim 7, wherein, The apparatus further includes an instruction management module, and the instruction management module is configured to: The instruction management module is configured to save first monitoring data, and the first monitoring data includes an identifier of a deployed application of the OS module and a running state of the deployed application; The instruction management module is further configured to determine a running state of the first application after executing the second operation instruction, and the running state of the first application includes a user interface (UI) state, a control activation state, and an application display state; The instruction management module is further configured to write the running state of the first application after executing the second operation instruction into the first monitoring data.

9. The apparatus of claim 8, wherein, The OS module is further configured to: In a case where the instruction monitoring module determines that the first resource data exists, run the first resource data according to the first operation instruction.

10. The apparatus of claim 9, wherein: The OS module is further configured to, in a case where a second operation event is detected, generate a third operation instruction to respond to the second operation event, and the second operation event includes an event in a case where a user operates the first application on the first device; The OS module is further configured to obtain third resource data according to the third operation instruction, and execute the third operation instruction based on the third resource data; The instruction monitoring module is further configured to send a third synchronization request to the second device; the third synchronization request includes an identifier of the first application and the third operation instruction for synchronizing the second operation event, so that the second device determines a running state of the first application on the first device according to the third operation instruction.

11. A data processing system, characterized by The apparatus includes a first device and a second device, the first device is a vehicle-mounted device, the second device is a mobile device, and the second device deploys a first application, and the apparatus includes: The second device is configured to send a first execution request to the first device, and the first execution request includes an identifier of the first application and a first operation instruction for operating the first application on the first device; The first device is configured to send a first synchronization request to the second device according to the first execution request, in a case where it is determined that the first resource data does not exist in the first device; wherein the first resource data is data required by the first device to execute the first operation instruction, and the first synchronization request is used to indicate that the first resource data does not exist in the first device. The second device is further configured to send the first resource data to the first device according to the first synchronization request. The first device is further configured to acquire the first resource data, and execute the first operation instruction based on the first resource data. The first device is further configured to: determine whether the first resource data exists in the first device by comparing the identifier of the first application in the first execution request with first monitoring data; wherein the first monitoring data includes identifiers of deployed applications of the first device and running states of the deployed applications. In a case where the first monitoring data contains the identifier of the first application in the first execution request, the first device determines that the first resource data exists in the first device. In a case where the first monitoring data does not contain the identifier of the first application in the first execution request, the first device determines that the first resource data does not exist in the first device.

12. The system of claim 11, wherein, After the first operation instruction is executed based on the first resource data, The first device is further configured to send a second synchronization request to the second device in a case where the first device detects a first operation event; wherein the first operation event includes an event in which a user operates the first application on the first device, the second synchronization request includes an identifier of the first application and application operation data, and the application operation data includes an instruction or coordinates triggered by the first operation event. The second device is configured to determine second resource data and a second operation instruction according to the second synchronization request; wherein the second operation instruction is an instruction triggered by the first operation event, the second resource data is data required by the first device to execute the second operation instruction, and the second resource data and the second operation instruction are determined by the second device according to the application operation data. The second device is further configured to send the second resource data and the second operation instruction to the first device. The first device is further configured to acquire the second resource data and the second operation instruction sent by the second device, and execute the second operation instruction according to the second resource data.

13. The system of claim 12, wherein The first device is configured to store first monitoring data, wherein the first monitoring data includes identifiers of deployed applications of the first device and running states of the deployed applications. The first device is configured to determine a running state of the first application after the second operation instruction is executed. The first device is configured to write the running state of the first application after the second operation instruction is responded to into the first monitoring data.

14. The system of claim 13, wherein The first device is configured to run the first resource data according to the first operation instruction when the first device determines that the first resource data exists.

15. The system of claim 14, wherein, The second device comprises second monitoring data, the second monitoring data comprising an identifier of a deployed application of the second device and a running state of the deployed application; the first device is further configured to generate a third operation instruction to respond to a second operation event when the first device detects the second operation event, wherein the second operation event comprises an event that a user operates the first application on the first device; The first device is further configured to acquire third resource data according to the third operation instruction, and execute the third operation instruction based on the third resource data; The first device is further configured to send a third synchronization request to the second device; wherein the third synchronization request comprises an identifier of the first application and the third operation instruction for synchronizing the second operation event on the second device, so that the second device determines the running state of the first application in the first device according to the third operation instruction; the second device is further configured to update the second monitoring data according to the third synchronization request; wherein the second monitoring data comprises an identifier of a deployed application of the second device and a running state of the deployed application.

16. A computing device, comprising: The computing device comprises a processor and a memory, the memory is configured to store instructions, and the processor is configured to execute the instructions to enable the computing device to implement the method according to any one of claims 1 to 5.

17. A computer-readable storage medium, characterized in that, The computer readable storage medium stores instructions, and the instructions are executed by a computing device to implement the method according to any one of claims 1 to 5.

18. A vehicle characterized by comprising: The vehicle comprises the data processing apparatus according to any one of claims 6 to 10.

Images