Fast application control method and device and storage medium

Abstract

The invention relates to a fast application control method and device and a storage medium. The fast application control method comprises the following steps: sending a transfer request to a second device, wherein the transfer request is used for requesting to transfer a fast application running in a first device from the first device to the second device for running; receiving a transfer request reply message, wherein the transfer request reply message is sent by the second device in response to the transfer request; transmitting transfer data to the second equipment based on the transfer request reply message, and transferring the fast application to the second equipment for operation; the transfer data comprises a fast application start RPK file package and application state data. According to the method and the device, when the fast application is transferred between the devices, the RPK file package and the application state data do not need to be downloaded through networking, and the performance loss of the devices is reduced.

Description

Technical Field

[0001] The present disclosure relates to the technical field of quick application cross-terminal operation, and in particular to a quick application control method, device and storage medium. Background Art

[0002] In the related technology, quick applications are supported to be transferred between different devices so as to run on multiple terminals.

[0003] When a quick app is transferred between different devices, the transferred device needs to connect to the Internet and download the quick app installation package (RPK). This method has a large performance loss, and the transferred device needs to request the first device to obtain application status data and run the quick app after starting the quick app, resulting in a long transfer time and a poor user experience. Summary of the invention

[0004] In order to overcome the problems existing in the related art, the present disclosure provides a quick application control method, device and storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, a quick application control method is provided, the method comprising:

[0006] Send a transfer request to the second device, where the transfer request is used to request that the quick application running on the first device be transferred from the first device to the second device for execution; receive a transfer request reply message, where the transfer request reply message is sent by the second device in response to the transfer request; send transfer data to the second device based on the transfer request reply message, and transfer the quick application to the second device for execution; the transfer data includes a quick application startup RPK file package and application status data.

[0007] In one embodiment, sending a transfer request to the second device includes: discovering the second device based on a communication discovery capability, and sending a transfer request to the second device in a first protocol format using the communication discovery capability; the first protocol format includes a first target device identifier, a first source device identifier, a first message type identifier, and a first message content; the first target device identifier is used to identify the second device, and the first source device identifier is used to identify the first device; the first message type identifier is used to identify the transfer request, and the first message content includes data content corresponding to the transfer request.

[0008] In one embodiment, the transfer request reply message has a second protocol format; the second protocol format includes a second target device identifier, a second source device identifier, a second message type identifier and a second message content; the second target device identifier is used to identify the first device, and the second source device identifier is used to identify the second device; the second message type identifier is used to identify the transfer request reply message, and the second message content includes data content indicating whether the transfer request is allowed.

[0009] In one embodiment, the transfer data has a third protocol format; the third protocol format includes a third target device identifier, a third source device identifier, a third message type identifier and a third message content; the third target device identifier is used to identify the second device, and the third source device identifier is used to identify the first device; the third message type identifier is used to identify the transfer data, and the third message content includes an RPK file package and application status data.

[0010] In one implementation, sending the transfer data to the second device based on the transfer request reply message includes: if the transfer request reply message indicates that the transfer is allowed, sending the transfer data to the second device.

[0011] In one embodiment, after sending the transfer data to the second device, the method further includes: receiving a transfer data reply message, the transfer data reply message being used to indicate whether the second device has successfully received the transfer data; if the transfer data reply message indicates that the second device has not successfully received the transfer data, calling a first callback function, the first callback function being used to indicate that the transfer of the quick application to the second device has failed.

[0012] In one embodiment, after the quick application is transferred to the second device for execution, the method further includes: receiving successful transfer indication information sent by the second device, the successful transfer indication information is used to indicate that the quick application is successfully transferred to the second device for execution; and calling a second callback function, the second callback function is used to indicate that the quick application is successfully transferred to the second device for execution.

[0013] In one implementation, the method further includes: in response to successfully transferring the quick application to the second device for execution, synchronizing the running state of the quick application with the second device.

[0014] According to a second aspect of an embodiment of the present disclosure, a quick application control method is provided, the method comprising:

[0015] Receive a transfer request sent by a first device, wherein the transfer request is used to request that a quick application running on the first device be transferred from the first device to a second device for execution; respond to the transfer request and send a transfer request reply message; receive transfer data sent by the first device based on the transfer request reply message, and transfer the quick application to the second device for execution; the transfer data includes a quick application startup RPK file package and application status data.

[0016] In one embodiment, the receiving of a transfer request sent by a first device includes: discovering the first device based on a communication discovery capability, and receiving the transfer request sent by the first device in a first protocol format using the communication discovery capability; the first protocol format includes a first target device identifier, a first source device identifier, a first message type identifier, and a first message content; the first target device identifier is used to identify the second device, and the first source device identifier is used to identify the first device; the first message type identifier is used to identify the transfer request, and the first message content includes data content corresponding to the transfer request.

[0017] In one embodiment, the transfer request reply message has a second protocol format; the second protocol format includes a second target device identifier, a second source device identifier, a second message type identifier and a second message content; the second target device identifier is used to identify the first device, and the second source device identifier is used to identify the second device; the second message type identifier is used to identify the transfer request reply message, and the second message content includes data content indicating whether the transfer request is allowed.

[0018] In one embodiment, the transfer data has a third protocol format; the third protocol format includes a third target device identifier, a third source device identifier, a third message type identifier and a third message content; the third target device identifier is used to identify the second device, and the third source device identifier is used to identify the first device; the third message type identifier is used to identify the transfer data, and the third message content includes an RPK file package and application status data.

[0019] In one implementation, the receiving the transfer data sent by the first device based on the transfer request reply message includes: if the transfer request reply message indicates that the transfer is allowed, receiving the transfer data sent by the first device based on the transfer request reply message.

[0020] In one implementation, after receiving the transfer data sent by the first device based on the transfer request reply message, the method further includes: sending a transfer data reply message, wherein the transfer data reply message is used to indicate whether the second device successfully receives the transfer data.

[0021] In one implementation, after the quick application is transferred to the second device for execution, the method further includes: sending successful transfer indication information, where the successful transfer indication information is used to indicate that the quick application is successfully transferred to the second device for execution.

[0022] In one implementation, the method further includes: in response to successfully transferring the quick application to the second device for execution, synchronizing the running state of the quick application with the first device.

[0023] According to a third aspect of an embodiment of the present disclosure, a quick application control device is provided, the device comprising: a sending unit, used to send a transfer request to the second device, the transfer request is used to request to transfer the quick application running on the first device from the first device to the second device for execution; a receiving unit, used to receive a transfer request reply message, the transfer request reply message is sent by the second device in response to the transfer request; a transfer unit, used to send transfer data to the second device based on the transfer request reply message, and transfer the quick application to the second device for execution; the transfer data includes a quick application startup RPK file package and application status data.

[0024] In one embodiment, the sending unit sends a transfer request to the second device in the following manner: discovering the second device based on the communication discovery capability, and sending the transfer request to the second device in a first protocol format using the communication discovery capability; the first protocol format includes a first target device identifier, a first source device identifier, a first message type identifier, and a first message content; the first target device identifier is used to identify the second device, and the first source device identifier is used to identify the first device; the first message type identifier is used to identify the transfer request, and the first message content includes data content corresponding to the transfer request.

[0025] In one embodiment, the transfer request reply message has a second protocol format; the second protocol format includes a second target device identifier, a second source device identifier, a second message type identifier and a second message content; the second target device identifier is used to identify the first device, and the second source device identifier is used to identify the second device; the second message type identifier is used to identify the transfer request reply message, and the second message content includes data content indicating whether the transfer request is allowed.

[0026] In one embodiment, the transfer data has a third protocol format; the third protocol format includes a third target device identifier, a third source device identifier, a third message type identifier and a third message content; the third target device identifier is used to identify the second device, and the third source device identifier is used to identify the first device; the third message type identifier is used to identify the transfer data, and the third message content includes an RPK file package and application status data.

[0027] In one implementation, the transfer unit sends the transfer data to the second device based on the transfer request reply message in the following manner: if the transfer request reply message indicates that the transfer is allowed, sending the transfer data to the second device.

[0028] In one embodiment, the receiving unit is also used to: receive a transfer data reply message after the sending unit sends the transfer data to the second device, and the transfer data reply message is used to indicate whether the second device successfully receives the transfer data; if the transfer data reply message indicates that the second device has not successfully received the transfer data, call a first callback function, and the first callback function is used to indicate that the transfer of the quick application to the second device has failed.

[0029] In one embodiment, the receiving unit is further used to receive successful transfer indication information sent by the second device after the transfer unit transfers the quick application to the second device for execution, wherein the successful transfer indication information is used to indicate that the quick application has been successfully transferred to the second device for execution; and call a second callback function, wherein the second callback function is used to indicate that the quick application has been successfully transferred to the second device for execution.

[0030] In one implementation, the transfer unit is further configured to: in response to successfully transferring the quick application to the second device for execution, synchronize the running state of the quick application with the second device.

[0031] According to a fourth aspect of an embodiment of the present disclosure, a quick application control device is provided, the device comprising: a receiving unit, configured to receive a transfer request sent by a first device, the transfer request being used to request that a quick application running on the first device be transferred from the first device to a second device for execution; a sending unit, configured to respond to the transfer request and send a transfer request reply message; a transfer unit, configured to receive transfer data sent by the first device based on the transfer request reply message, and transfer the quick application to the second device for execution; the transfer data comprising a quick application startup RPK file package and application status data.

[0032] In one embodiment, the receiving unit receives the transfer request sent by the first device in the following manner: discovering the first device based on the communication discovery capability, and receiving the transfer request sent by the first device in a first protocol format using the communication discovery capability; the first protocol format includes a first target device identifier, a first source device identifier, a first message type identifier, and a first message content; the first target device identifier is used to identify the second device, and the first source device identifier is used to identify the first device; the first message type identifier is used to identify the transfer request, and the first message content includes data content corresponding to the transfer request.

[0033] In one embodiment, the transfer request reply message has a second protocol format; the second protocol format includes a second target device identifier, a second source device identifier, a second message type identifier and a second message content; the second target device identifier is used to identify the first device, and the second source device identifier is used to identify the second device; the second message type identifier is used to identify the transfer request reply message, and the second message content includes data content indicating whether the transfer request is allowed.

[0034] In one embodiment, the transfer data has a third protocol format; the third protocol format includes a third target device identifier, a third source device identifier, a third message type identifier and a third message content; the third target device identifier is used to identify the second device, and the third source device identifier is used to identify the first device; the third message type identifier is used to identify the transfer data, and the third message content includes an RPK file package and application status data.

[0035] In one implementation, the receiving unit receives the transfer data sent by the first device based on the transfer request reply message in the following manner: if the transfer request reply message indicates that the transfer is allowed, the transfer data sent by the first device based on the transfer request reply message is received.

[0036] In one embodiment, the sending unit is also used to send a transfer data reply message after the receiving unit receives the transfer data sent by the first device based on the transfer request reply message, and the transfer data reply message is used to indicate whether the second device successfully receives the transfer data.

[0037] In one implementation, the sending unit is further used to send successful transfer indication information after the transfer unit transfers the quick application to the second device for execution, wherein the successful transfer indication information is used to indicate that the quick application is successfully transferred to the second device for execution.

[0038] In one implementation, the transfer unit is further configured to: successfully transfer the quick application to the second device for execution, and synchronize the running state of the quick application with the first device.

[0039] According to the fifth aspect of the embodiments of the present disclosure, a quick application control device is provided, including: a processor; a memory for storing processor executable instructions; wherein the processor is configured to: execute the quick application control method described in the first aspect or any one of the embodiments of the first aspect.

[0040] According to a sixth aspect of an embodiment of the present disclosure, a quick application control device is provided, comprising: a processor; a memory for storing processor executable instructions; wherein the processor is configured to: execute the quick application control method described in the second aspect or any one of the implementations of the second aspect.

[0041] According to the seventh aspect of the embodiments of the present disclosure, a storage medium is provided, in which instructions are stored. When the instructions in the storage medium are executed by a processor of a first device, the first device can execute the quick application control method described in the first aspect or any one of the embodiments of the first aspect.

[0042] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is provided, in which instructions are stored. When the instructions in the storage medium are executed by a processor of a second device, the second device is enabled to execute the quick application control method described in the second aspect or any one of the embodiments of the second aspect.

[0043] The technical solution provided by the embodiments of the present disclosure may include the following beneficial effects: a first device running a quick application sends a transfer request to a second device and receives a transfer request reply message, and sends an RPK file package and application status data to the second device based on the transfer request reply message, so that the first device and the second device can realize the transfer operation of the quick application based on the message sending between the devices, without the need for the second device to connect to the Internet to download the RPK file, and without the need to make a separate request to obtain the application status data, thereby reducing device performance loss and improving user experience.

[0044] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0046] Figure 1 It is a schematic diagram showing a quick application scenario according to an exemplary embodiment.

[0047] Figure 2 The figure is a schematic diagram showing a quick application transfer between multiple devices according to an exemplary embodiment.

[0048] Figure 3 The figure is a flowchart of a quick application transfer method according to an exemplary embodiment.

[0049] Figure 4 The invention is a flowchart of a quick application control method executed by a first device according to an exemplary embodiment.

[0050] Figure 5 It is a block diagram showing a protocol format according to an exemplary embodiment.

[0051] Figure 6 The invention is a flowchart showing a method for unsuccessfully receiving transferred data according to an exemplary embodiment.

[0052] Figure 7 The invention is a flowchart showing a method for successfully receiving transferred data according to an exemplary embodiment.

[0053] Figure 8 A protocol diagram of different messages involved in an embodiment of the present disclosure is shown.

[0054] Fig. 9 The invention is a flowchart showing a quick application control method executed by a second device according to an exemplary embodiment.

[0055] Fig.10 It is a block diagram of a design architecture of a quick application control method according to an exemplary embodiment.

[0056] Fig.11 The figure is a block diagram showing the process of a quick application control method according to an exemplary embodiment.

[0057] Fig.12 The figure is a block diagram of a quick application control device according to an exemplary embodiment.

[0058] Fig.13 The figure is a block diagram of another quick application control device according to an exemplary embodiment.

[0059] Fig.14 The invention is a block diagram showing a device for quick application control according to an exemplary embodiment.

[0060] Fig.15 The invention is a block diagram showing a device for quick application control according to an exemplary embodiment. DETAILED DESCRIPTION

[0061] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present disclosure.

[0062] The quick application control method provided by the embodiment of the present disclosure is applied to the scenario of quick application transfer between multiple devices. For example, the quick application is applied to the scenario of quick application transfer between different devices.

[0063] Figure 1 FIG. 1 is a schematic diagram showing a scenario in which a quick application is transferred and executed between multiple devices according to an exemplary embodiment. Figure 1 As shown, in different scenarios, quick applications can be transferred from one device to another and maintain the current application status based on transfer coordination between multiple devices. For example, in scenarios such as meetings, watching videos, playing games, taking online classes, and video conferences, quick applications can be transferred and run synchronously between terminals, TVs, tablets, car computers, speakers, and computers. For example, when the terminal battery is too low, the quick application can be transferred to other devices such as tablets. Among them, Figure 1 This is just a schematic illustration. It is understood that the scenarios include but are not limited to meetings, watching videos, playing games, taking online classes, video conferences, etc. Quick applications include but are not limited to quick applications. Devices include but are not limited to terminals, TVs, tablets, car computers, speakers, and computers.

[0064] Figure 2 FIG. 1 is a schematic diagram showing a quick application transfer between multiple devices according to an exemplary embodiment. Figure 2 As shown in the figure, quick applications can be transferred between device A, device B, device C, device D, and device E. When a quick application is transferred between devices, it can be directly transferred between different devices to be transferred, or it can be transferred through one or more devices. For example, a quick application is transferred from device A to device B to achieve the transfer between device A and device B. You can also transfer the quick application device A to device B first and then to device C to achieve the quick application transfer between device A and device C.

[0065] In related technologies, the transfer of quick applications between multiple devices mainly relies on the following technologies:

[0066] 1) Developers use text editors and other IDEs in a PC environment to write code similar to HyperText Markup Language (HTML) pages: components (similar to HTML tags, (such as: div, a), CSS, Javascript scripts); this is called the compilation side; 2) After development is completed, the developer code is compiled to generate an rpk file, called an application (Application, app) (this app can have multiple pages), which is uploaded to the Xiaomi server; 3) When the user runs the page on the terminal, the RPK file will be downloaded, and then the JS in this file will be run to complete the logic of the page UI display, etc., which is called the running side.

[0067] The above-mentioned technology of transferring quick applications on multiple terminals can also be called quick application circulation technology. Among them, quick application circulation technology is generally based on deep linking, connecting the running side to the quick application distribution platform, and running the quick application after downloading from the quick application distribution platform.

[0068] Figure 3 FIG. 1 is a process diagram of a quick application transfer method according to an exemplary embodiment. Figure 3 As shown, the device that originally runs the application is called the first device. The device that runs the application after the transfer is called the second device. The user starts running the quick application on the first device. The first device discovers the second device through the communication discovery capability of the networking device, and sends deeplink information to the second device through the communication discovery capability. The second device parses the deeplink information to obtain the package name, and then requests the quick application distribution service (such as the cloud) to download the RPK package. The quick application distribution service feeds back the RPK package, and the second device pulls the corresponding RPK package, loads and starts the quick application. The second device requests the first device to obtain the application status information. The application status information is synchronized between the first device and the second device to load the application status on the second device, and then the quick application is run on the second device to realize the transfer of the application from the first device to the second device.

[0069] The above-mentioned solution for transferring quick applications between devices requires the quick application RPK file from the application distribution service (such as the cloud). That is, the second device needs to access the Internet to obtain the RPK file. On the one hand, networking will reduce performance, and on the other hand, if networking is not available, the quick application cannot be transferred between devices. In addition, after the second device starts the quick application, it needs to request the first device separately to obtain the application status information, and then load the application status information, which will also prolong the time it takes to transfer the application between devices, and the user experience is poor.

[0070] In view of this, the present disclosure proposes a method for transferring quick applications between multiple devices by sending RPK files and application status data between devices, thereby achieving the purpose of obtaining RPK files and application status data without connecting to the Internet, reducing performance loss, and improving user experience.

[0071] Figure 4 is a flowchart of a quick application control method according to an exemplary embodiment. Figure 4 As shown, the quick application control method can be applied to a first device, comprising the following steps:

[0072] In step S11, a transfer request is sent to the second device, where the transfer request is used to request to transfer the quick application running on the first device from the first device to the second device for execution.

[0073] In step S12, a transfer request reply message is received, where the transfer request reply message is sent by the second device in response to the transfer request.

[0074] In step S13, transfer data is sent to the second device based on the transfer request reply message, and the quick application is transferred to the second device for execution.

[0075] In the disclosed embodiment, the first device sends transfer data to the second device based on the transfer request reply message; wherein the transfer data includes a quick application startup RPK file package and application status data.

[0076] In the disclosed embodiment, a first device running a quick application sends a transfer request to a second device and receives a transfer request reply message, and sends an RPK file package and application status data to the second device based on the transfer request reply message, so that the first device and the second device can realize the transfer operation of the quick application based on the message sending between the devices, without the need for the second device to connect to the Internet to download the RPK file, and without the need to make a separate request to obtain the application status data, thereby reducing device performance loss and improving user experience.

[0077] The following is an explanation of the implementation process of the first device sending a transfer request to the second device in the embodiment of the present disclosure.

[0078] In the embodiment of the present disclosure, the first device discovers the second device based on the communication discovery capability, wherein the communication discovery capability can establish a connection between devices through communication protocols such as Bluetooth and wireless local area network.

[0079] In the embodiment of the present disclosure, information interaction between the first device and the second device may adopt a predefined protocol format, and the protocol format is described below.

[0080] Figure 5 is a schematic diagram showing a protocol format according to an exemplary embodiment. Figure 5 In the disclosed embodiment, the predefined protocol format used for information exchange between devices includes a message target device identity (Identity, ID), a message source device ID, a message type representation, and content.

[0081] Among them, the protocol format for message transmission between devices in the embodiments of the present disclosure is represented differently according to the message type and corresponds to different protocol formats.

[0082] In one example, a first device sends a transfer request to a second device according to a first protocol format.

[0083] The first protocol format includes a first target device identifier, a first source device identifier, a first message type identifier, and a first message content.

[0084] The first target device identifier is used to identify the second device, the first source device identifier is used to identify the first device; the first message type identifier is used to identify the transfer request, and the first message content includes data content corresponding to the transfer request.

[0085] In another example, the transfer request reply message has a second protocol format.

[0086] The second protocol format includes a second target device identifier, a second source device identifier, a second message type identifier, and second message content.

[0087] The second target device identifier is used to identify the first device, the second source device identifier is used to identify the second device; the second message type identifier is used to identify the transfer request reply message, and the second message content includes data content indicating whether the transfer request is allowed.

[0088] In one implementation, if the transfer request reply message indicates that the transfer is allowed, transfer data is sent to the second device; wherein the transfer data may include a quick application startup RPK file package and application status data.

[0089] In one implementation, if the transfer request reply message indicates that the transfer is not allowed, the transfer data is not sent to the second device.

[0090] In yet another example, the transfer data has a third protocol format.

[0091] The third protocol format includes a third target device identifier, a third source device identifier, a third message type identifier, and third message content.

[0092] The third target device identifier is used to identify the second device, the third source device identifier is used to identify the first device; the third message type identifier is used to identify the transfer data, and the third message content includes the RPK file package and application status data.

[0093] Among them, in the embodiment of the present disclosure, the second device receives the transfer data sent by the first device, and sends a transfer data reply message to the first device based on whether the transfer data is successfully received, so as to indicate to the first device whether the second device successfully receives the transfer data.

[0094] In the embodiment of the present disclosure, after the first device sends the transfer data to the second device, the second device is caused to load the application state of the transfer data, start the RPK, and cause the second device to send a transfer data reception reply message to the first device; wherein the transfer data reception reply message is used to indicate whether the second device has successfully received the transfer data. When the second device successfully receives the transfer data, the transfer data reply message indicates that the second device has successfully received the transfer data. When the second device has not successfully received the transfer data, the transfer data reply message indicates that the second device has not successfully received the transfer data.

[0095] In yet another example, the received transfer data reply has a fourth protocol format.

[0096] The fourth protocol format includes a fourth target device identifier, a fourth source device identifier, a fourth message type identifier, and a fourth message content.

[0097] Among them, the fourth target device identifier is used to identify the first device, the fourth source device identifier is used to identify the second device; the fourth message type identifier is used to identify the received transfer data reply message, and the fourth message content includes data content of success or failure status.

[0098] Figure 6 FIG. 1 is a flow chart showing a method for unsuccessfully receiving transferred data according to an exemplary embodiment. Figure 6 As shown, the method for unsuccessfully receiving transferred data includes the following steps:

[0099] In step S21, a transfer data reply message is received, where the transfer data reply message is used to indicate whether the second device successfully receives the transfer data.

[0100] In step S22, it is determined that the received transfer data reply message indicates that the second device has not successfully received the transfer data.

[0101] In step S23, the first callback function is called.

[0102] In the disclosed embodiment, if the second device fails to successfully receive the transferred data, the first device responds to the message based on the received transferred data, determines that the second device fails to successfully receive the transferred data, confirms that the transfer fails, and the first device calls the first callback function to notify the developer of the transfer failure, and the process ends. The first callback function can be a related function that prompts the transfer failure information.

[0103] In the embodiment of the present disclosure, when the first device and the second device successfully complete the transfer of the application, the second device may send successful transfer indication information to the first device to indicate that the quick application is successfully transferred to the second device for execution.

[0104] The successful transfer indication information may also be understood as the completion of the transfer.

[0105] In yet another example, the transfer is completed in a fifth protocol format.

[0106] The fifth protocol format includes a fifth target device identifier, a fifth source device identifier, a fifth message type identifier, and a fifth message content.

[0107] The fifth target device identifier is used to identify the first device, and the fifth source device identifier is used to identify the second device; the fifth message type identifier is used to identify the transfer completion message, and the fifth message content may not send any data content.

[0108] The following is an explanation of a method for successfully receiving transfer data in an embodiment of the present disclosure.

[0109] Figure 7 FIG. 1 is a flow chart showing a method for successfully receiving transferred data according to an exemplary embodiment. Figure 7 As shown, the method for successfully receiving the transferred data includes the following steps:

[0110] In step S31, successful transfer indication information sent by the second device is received, where the successful transfer indication information is used to indicate that the quick application is successfully transferred to the second device for execution.

[0111] In the disclosed embodiment, after the first device sends the transfer data to the second device, the second device loads the application state of the transfer data, starts the RPK, and causes the second device to send a transfer data reception reply message to the first device; wherein the transfer data reception reply message is used to indicate whether the second device successfully receives the transfer data. If the quick application is successfully transferred to the second device for operation, the first device receives a successful transfer indication message sent by the second device. wherein the successful transfer indication message is used to indicate that the quick application is successfully transferred to the second device for operation.

[0112] In step S32, the second callback function is called.

[0113] In the embodiment of the present disclosure, after receiving the completion of the transfer sent by the second device, the first device calls the second callback function to notify the developer that the transfer of the quick app is complete. The second callback function can be a function for prompting the developer with prompt information for successful transfer of the reference.

[0114] In the disclosed embodiment, a callback function is used to call back whether the application transfer is successful or not, which improves the reusability and flexibility of the code, makes it easy to maintain and expand in the later stage, improves work efficiency, and saves equipment performance.

[0115] In the disclosed embodiment, the quick application is successfully transferred to the second device for operation, and the first device and the second device synchronize the running status of the quick application. After the transfer between the devices is completed, the first device and the second device establish communication between the first device and the second device on the quick application through communication discovery capabilities, and through data transmission, the developer can synchronize the status as required so that the status of the first device and the second device are consistent. The first device can also determine whether to exit and stop working as required.

[0116] In yet another example, the data transmission message has a sixth protocol format.

[0117] The sixth protocol format includes a sixth target device identifier, a sixth source device identifier, a sixth message type identifier, and a sixth message content.

[0118] The data transmission is bidirectional, that is, the sixth target device and the sixth source device can be used to identify the first device or the second device; the sixth message type identifier is used to identify the data transmission message, and the sixth message content can send any message content.

[0119] Based on the above embodiments, it can be known that the embodiments of the present disclosure implement application transfer through different protocol formats of predefined different messages between the first device and the second device. Figure 8 A protocol diagram of different messages involved in an embodiment of the present disclosure is shown. Figure 8 As shown, the name column in the content format can represent different messages, such as transfer request, transfer request reply, transfer data, transfer data reply, completed transfer, and data transfer. Among them, the content includes the specific data content of different messages. The message type identifier is used to identify different message types. For example, "1" is used to identify a transfer request. "2" is used to identify a transfer request reply. "3" is used to identify transfer data. "4" is used to identify a transfer data reply. "5" is used to identify a completed transfer. "6" is used to identify data transfer.

[0120] The quick application control method provided by the embodiment of the present disclosure realizes the transmission of various information during the quick application transfer process based on the protocol format between devices, and can complete the quick application transfer without connecting to the Internet to download the RPK file. After the quick application is started, the application running status can be directly synchronized between devices, which can improve the user experience.

[0121] Based on the same concept, an embodiment of the present disclosure also provides a quick application control method executed by a second device.

[0122] Fig. 9 is a flowchart of a quick application control method according to an exemplary embodiment. Fig. 9 As shown, the quick application control method is executed by the second device and includes the following steps:

[0123] In step S41, a transfer request sent by a first device is received, where the transfer request is used to request to transfer a quick application running on the first device from the first device to a second device for execution.

[0124] The following is an explanation of the implementation process of receiving the transfer request sent by the first device in the embodiment of the present disclosure.

[0125] In the embodiment of the present disclosure, the second device discovers the first device based on the communication discovery capability, wherein the communication discovery capability can establish a connection between devices through communication protocols such as Bluetooth and wireless local area network.

[0126] In the embodiment of the present disclosure, information interaction between the first device and the second device may adopt a predefined protocol format, wherein the predefined protocol format is the same as the predefined protocol format involved in the above embodiment, and will not be repeated here.

[0127] In step S42, respond to the transfer request and send a transfer request reply message.

[0128] In the disclosed embodiment, the second device receives a transfer request sent by the first device, wherein the second device receives the transfer request based on the communication discovery capability, and the second device determines whether the local device contains a local RPK file package, whether the RPK can be run, etc. After the determination is completed, the determination result is sent to the first device as a transfer request reply message.

[0129] In step S43, the transfer data sent by the first device based on the transfer request reply message is received, and the quick application is transferred to the second device for execution.

[0130] In the disclosed embodiment, the second device determines whether to allow data transfer. In one implementation, if the transfer is allowed, the second device sends a transfer request reply message to the first device and receives the transfer data sent by the first device. The transfer data may include a quick application startup RPK file package and application status data. In one implementation, if the transfer is not allowed, the transfer request reply message is not sent to the first device.

[0131] The following is an explanation of the method for unsuccessfully receiving the transferred data in the embodiment of the present disclosure.

[0132] In the disclosed embodiment, a transfer data reply message is sent, and the transfer data reply message is used to indicate whether the second device has successfully received the transfer data. It is understandable that after the second device receives the transfer data sent by the first device, the second device loads the application state of the transfer data and starts the RPK; the second device sends a transfer data reception reply message to the first device. Among them, the transfer data reception reply message is used to indicate whether the second device has successfully received the transfer data.

[0133] The following is an explanation of a method for successfully receiving transfer data in an embodiment of the present disclosure.

[0134] In the disclosed embodiment, a successful transfer indication message is sent, and the successful transfer indication message is used to indicate that the quick application is successfully transferred to the second device for operation. It can be understood that after the second device receives the transfer data sent by the first device, the second device loads the application state of the transfer data and starts the RPK; the second device sends a transfer data reception reply message to the first device; wherein the transfer data reception reply message is used to indicate whether the second device successfully receives the transfer data. If the quick application is successfully transferred to the second device for operation, the second device sends a successful transfer indication message to the first device. wherein the successful transfer indication message is used to indicate that the quick application is successfully transferred to the second device for operation.

[0135] In one example, in response to the quick application being successfully transferred to the second device for operation, the running state of the quick application is synchronized with the second device. After the transfer between the devices is completed, the first device and the second device establish communication between the first device and the second device on the quick application through communication discovery capabilities, and through data transmission, the developer can synchronize the state as required so that the state of the first device and the second device are consistent. The first device can also determine whether to exit and stop working as required.

[0136] Based on the above embodiments, the embodiments of the present disclosure can adopt Fig.10 The quick app architecture shown implements quick app transfer between devices. Fig.10 is a block diagram showing a design architecture of a quick application control method according to an exemplary embodiment. Fig.10 As shown, the design architecture includes quick apps, quick app runtime, and quick app migration service.

[0137] In the disclosed embodiment, the quick application can be understood as a direct service developed by a developer that can call a transfer interface; the quick application runtime can be understood as a quick application runtime environment that implements a transfer interface for quick application calls; the quick application transfer service can be understood as managing quick application transfer tasks, generating and parsing quick application transfer protocols, and communicating with the quick application transfer services of other devices through the device discovery communication capability service. The device discovery communication capability service can be understood as establishing a connection between devices through communication protocols such as Bluetooth, providing device discovery, and message sending capabilities.

[0138] Based on the above quick application design architecture, quick application transfer between the first device and the second device can be achieved.

[0139] Fig.11 is a block diagram showing a quick application control method flow according to an exemplary embodiment. Fig.11 As shown, it can be divided into four processes: initiating transfer, transferring data and starting, completing transfer and calling developer callback, and status synchronization.

[0140] In the disclosed embodiment, initiating a transfer includes: the first device discovers the second device through the device discovery communication capability, the quick application calls the transfer interface to initiate a transfer request, the second device receives the transfer request through the device discovery communication capability, the second device determines whether the local device contains a local RPK package, whether the RPK can be run, etc., and sends a transfer request reply to the first device.

[0141] In the disclosed embodiment, transferring data and starting includes: the first device receives a transfer request reply, parses the transfer request reply, determines whether the transfer condition is met, and if the transfer is possible, constructs the transfer data and sends it to the second device, the second device loads the application state of the transfer data to start the RPK, and sends a transfer data reception reply to the first device, which may be replied multiple times. The second device receives the transfer data reception reply, and if the reception fails, calls the developer failure callback to notify the developer of the transfer failure, and the process ends.

[0142] In the embodiment of the present disclosure, completing the transfer and calling the developer callback includes: if the second device completes the transfer, the second device sends a transfer completion message, the first device receives the transfer completion message, and calls the developer success callback, and the transfer is completed.

[0143] In the disclosed embodiment, status synchronization includes: after the transfer is completed, the second device and the first device establish quick application communication on the second device and the first device through device discovery communication capabilities. Through two-way data transmission, the developer can synchronize the status as needed to keep the status of the first device and the second device consistent. The first device determines whether to exit as needed.

[0144] The above embodiments of the present disclosure implement the transfer of quick applications between devices by sending different protocols without the need for the Internet, and after the transfer is successful and the quick application is started, the second device does not need to synchronize the running status of the first device, saving time, improving user experience, and saving device performance. Based on the same concept, the embodiments of the present disclosure also provide a quick application control device.

[0145] It is understandable that in order to realize the above functions, the quick application control device provided by the embodiment of the present disclosure includes hardware structures and / or software modules corresponding to the execution of each function. In combination with the units and algorithm steps of the various examples disclosed in the embodiment of the present disclosure, the embodiment of the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific quick applications and design constraints of the technical solution. Those skilled in the art can use different methods for each specific quick application to implement the described functions, but such implementation should not be considered to exceed the scope of the technical solution of the embodiment of the present disclosure.

[0146] Fig.12 is a block diagram of a quick application control device according to an exemplary embodiment. Fig.12 As shown, the device 100 includes a sending unit 101 , a receiving unit 102 , and a transferring unit 103 .

[0147] The sending unit 101 is used to send a transfer request to the second device, where the transfer request is used to request to transfer the quick application running on the first device from the first device to the second device for execution.

[0148] The receiving unit 102 is used to receive a transfer request reply message, where the transfer request reply message is sent by the second device in response to the transfer request.

[0149] The transfer unit 103 is used to send transfer data to the second device based on the transfer request reply message, and transfer the quick application to the second device for execution; the transfer data includes a quick application startup RPK file package and application status data.

[0150] In one implementation, the sending unit 101 sends a transfer request to the second device in the following manner: discovering the second device based on the communication discovery capability, and sending the transfer request to the second device in a first protocol format using the communication discovery capability. The first protocol format includes a first target device identifier, a first source device identifier, a first message type identifier, and a first message content. The first target device identifier is used to identify the second device, and the first source device identifier is used to identify the first device. The first message type identifier is used to identify the transfer request, and the first message content includes data content corresponding to the transfer request.

[0151] In one embodiment, the transfer request reply message has a second protocol format. The second protocol format includes a second target device identifier, a second source device identifier, a second message type identifier, and a second message content. The second target device identifier is used to identify the first device, and the second source device identifier is used to identify the second device. The second message type identifier is used to identify the transfer request reply message, and the second message content includes data content of whether the transfer request is allowed.

[0152] In one embodiment, the transfer data has a third protocol format. The third protocol format includes a third target device identifier, a third source device identifier, a third message type identifier, and a third message content. The third target device identifier is used to identify the second device, and the third source device identifier is used to identify the first device. The third message type identifier is used to identify the transfer data, and the third message content includes an RPK file package and application status data.

[0153] In one implementation, the transfer unit 103 sends the transfer data to the second device based on the transfer request reply message in the following manner: if the transfer request reply message indicates that the transfer is allowed, the transfer data is sent to the second device.

[0154] In one embodiment, the receiving unit 102 is further configured to: after the sending unit 101 sends the transfer data to the second device, receive a transfer data reply message, the transfer data reply message being used to indicate whether the second device successfully receives the transfer data. If the transfer data reply message indicates that the second device has not successfully received the transfer data, call the first callback function, the first callback function being used to indicate that the transfer of the quick application to the second device has failed.

[0155] In one embodiment, the receiving unit 102 is further configured to receive successful transfer indication information sent by the second device after the transfer unit 103 transfers the quick application to the second device for execution, the successful transfer indication information being used to indicate that the quick application has been successfully transferred to the second device for execution, and to call a second callback function, the second callback function being used to indicate that the quick application has been successfully transferred to the second device for execution.

[0156] In one implementation, the transfer unit 103 is further configured to: in response to successfully transferring the quick application to the second device for execution, synchronize the running state of the quick application with the second device.

[0157] Based on the same concept, the embodiment of the present disclosure also provides a quick application control device.

[0158] Fig.13 is a block diagram of another quick application control device according to an exemplary embodiment. Fig.13 As shown, the device 200 includes a receiving unit 201 , a sending unit 202 , and a transferring unit 203 .

[0159] The receiving unit 201 is used to receive a transfer request sent by a first device, where the transfer request is used to request to transfer a quick application running on the first device from the first device to a second device for execution.

[0160] The sending unit 202 is used to respond to the transfer request and send a transfer request reply message.

[0161] The transfer unit 203 is configured to receive transfer data sent by the first device based on the transfer request reply message, and transfer the quick application to the second device for execution. The transfer data includes a quick application startup RPK file package and application status data.

[0162] In one implementation, the receiving unit 201 receives the transfer request sent by the first device in the following manner: discovering the first device based on the communication discovery capability, and receiving the transfer request sent by the first device in accordance with the first protocol format using the communication discovery capability. The first protocol format includes a first target device identifier, a first source device identifier, a first message type identifier, and a first message content. The first target device identifier is used to identify the second device, and the first source device identifier is used to identify the first device. The first message type identifier is used to identify the transfer request, and the first message content includes data content corresponding to the transfer request.

[0163] In one embodiment, the transfer request reply message has a second protocol format. The second protocol format includes a second target device identifier, a second source device identifier, a second message type identifier, and a second message content. The second target device identifier is used to identify the first device, and the second source device identifier is used to identify the second device. The second message type identifier is used to identify the transfer request reply message, and the second message content includes data content of whether the transfer request is allowed.

[0164] In one embodiment, the transfer data has a third protocol format. The third protocol format includes a third target device identifier, a third source device identifier, a third message type identifier, and a third message content. The third target device identifier is used to identify the second device, and the third source device identifier is used to identify the first device. The third message type identifier is used to identify the transfer data, and the third message content includes an RPK file package and application status data.

[0165] In one implementation, the receiving unit 201 receives the transfer data sent by the first device based on the transfer request reply message in the following manner: if the transfer request reply message indicates that the transfer is allowed, then the transfer data sent by the first device based on the transfer request reply message is received.

[0166] In one implementation, the sending unit 202 is further used to send a transfer data reply message after the receiving unit 201 receives the transfer data sent by the first device based on the transfer request reply message, and the transfer data reply message is used to indicate whether the second device successfully receives the transfer data.

[0167] In one implementation, the sending unit 202 is further configured to send successful transfer indication information after the transfer unit 203 transfers the quick application to the second device for execution, where the successful transfer indication information is used to indicate that the quick application is successfully transferred to the second device for execution.

[0168] In one implementation, the transfer unit 203 is further configured to: successfully transfer the quick application to the second device for execution, and synchronize the running state of the quick application with the first device.

[0169] Fig.14 1 is a block diagram of a device 300 for quick application control according to an exemplary embodiment. For example, the device 300 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0170] Reference Fig.14 , the device 300 may include one or more of the following components: a processing component 302 , a memory 304 , a power component 306 , a multimedia component 308 , an audio component 310 , an input / output (I / O) interface 312 , a sensor component 314 , and a communication component 316 .

[0171] The processing component 302 generally controls the overall operation of the device 300, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 302 may include one or more processors 320 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 302 may include one or more modules to facilitate the interaction between the processing component 302 and other components. For example, the processing component 302 may include a multimedia module to facilitate the interaction between the multimedia component 308 and the processing component 302.

[0172] The memory 304 is configured to store various types of data to support operations on the device 300. Examples of such data include instructions for any application or method operating on the device 300, contact data, phone book data, messages, pictures, videos, etc. The memory 304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0173] The power component 306 provides power to the various components of the device 300. The power component 306 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 300.

[0174] The multimedia component 308 includes a screen that provides an output interface between the device 300 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 308 includes a front camera and / or a rear camera. When the device 300 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0175] The audio component 310 is configured to output and / or input audio signals. For example, the audio component 310 includes a microphone (MIC), and when the device 300 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 304 or sent via the communication component 316. In some embodiments, the audio component 310 also includes a speaker for outputting audio signals.

[0176] I / O interface 312 provides an interface between processing component 302 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0177] The sensor assembly 314 includes one or more sensors for providing various aspects of the status assessment of the device 300. For example, the sensor assembly 314 can detect the open / closed state of the device 300, the relative positioning of components, such as the display and keypad of the device 300, the sensor assembly 314 can also detect the position change of the device 300 or a component of the device 300, the presence or absence of user contact with the device 300, the orientation or acceleration / deceleration of the device 300, and the temperature change of the device 300. The sensor assembly 314 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 314 can also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 314 can also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0178] The communication component 316 is configured to facilitate wired or wireless communication between the device 300 and other devices. The device 300 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 316 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 316 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0179] In an exemplary embodiment, the apparatus 300 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

[0180] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 304 including instructions, and the instructions can be executed by the processor 320 of the device 300 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0181] Fig.15 4 is a block diagram of a device 400 for quick application control according to an exemplary embodiment. For example, the device 400 may be provided as a server. Fig.15 , the apparatus 400 includes a processing component 422, which further includes one or more processors, and a memory resource represented by a memory 432 for storing instructions, such as an application, that can be executed by the processing component 422. The application stored in the memory 432 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 422 is configured to execute the instructions to perform the above method.

[0182] The device 400 may also include a power supply component 426 configured to perform power management of the device 400, a wired or wireless network interface 450 configured to connect the device 400 to a network, and an input / output (I / O) interface 458. The device 400 may operate based on an operating system stored in the memory 432, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0183] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 432 including instructions, which can be executed by the processing component 422 of the device 400 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0184] It is to be understood that in the present disclosure, "plurality" refers to two or more than two, and other quantifiers are similar. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. The singular forms "a", "the" and "the" are also intended to include plural forms, unless the context clearly indicates other meanings.

[0185] It is further understood that the terms "first", "second", etc. are used to describe various information, but such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other, and do not indicate a specific order or degree of importance. In fact, the expressions "first", "second", etc. can be used interchangeably. For example, without departing from the scope of the present disclosure, the first information can also be referred to as the second information, and similarly, the second information can also be referred to as the first information.

[0186] It can be further understood that, unless otherwise specified, “connection” includes a direct connection without other components between the two, and also includes an indirect connection with other components between the two.

[0187] It is further understood that, although the operations are described in a specific order in the drawings in the embodiments of the present disclosure, it should not be understood as requiring the operations to be performed in the specific order shown or in a serial order, or requiring the execution of all the operations shown to obtain the desired results. In certain environments, multitasking and parallel processing may be advantageous.

[0188] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any modifications, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure.

[0189] It should be understood that the present disclosure is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the scope of the appended claims.

Claims

1. A fast application control method, characterized in that: include: Sending a transfer request to the second device, where the transfer request is used to request that a quick application running on the first device be transferred from the first device to the second device for execution; receiving a transfer request reply message, where the transfer request reply message is sent by the second device in response to the transfer request; Sending transfer data to the second device based on the transfer request reply message, and transferring the quick application to the second device for execution; The transfer data includes the quick application startup RPK file package and application status data.

2. The method according to claim 1, characterized in that The sending a transfer request to the second device includes: discovering a second device based on the communication discovery capability, and sending a transfer request to the second device in a first protocol format using the communication discovery capability; The first protocol format includes a first target device identifier, a first source device identifier, a first message type identifier, and a first message content; The first target device identifier is used to identify the second device, and the first source device identifier is used to identify the first device; The first message type identifier is used to identify the transfer request, and the first message content includes data content corresponding to the transfer request.

3. The method according to claim 1, characterized in that The transfer request reply message has a second protocol format; The second protocol format includes a second target device identifier, a second source device identifier, a second message type identifier, and second message content; The second target device identifier is used to identify the first device, and the second source device identifier is used to identify the second device; The second message type identifier is used to identify the transfer request reply message, and the second message content includes data content indicating whether the transfer request is allowed.

4. The method according to claim 1, characterized in that: The transfer data has a third protocol format; The third protocol format includes a third target device identifier, a third source device identifier, a third message type identifier, and a third message content; The third target device identifier is used to identify the second device, and the third source device identifier is used to identify the first device; The third message type identifier is used to identify the transfer data, and the third message content includes an RPK file package and application status data.

5. The method according to any one of claims 1 to 4, characterized in that: The sending the transfer data to the second device based on the transfer request reply message includes: If the transfer request reply message indicates that the transfer is allowed, the transfer data is sent to the second device.

6. The method according to claim 1, characterized in that After sending the transfer data to the second device, the method further includes: receiving a transfer data reply message, where the transfer data reply message is used to indicate whether the second device successfully receives the transfer data; If the transfer data reply message indicates that the second device has not successfully received the transfer data, a first callback function is called, where the first callback function is used to indicate that the transfer of the quick application to the second device for operation has failed.

7. The method according to claim 1, characterized in that After transferring the quick application to the second device for execution, the method further includes: receiving successful transfer indication information sent by the second device, where the successful transfer indication information is used to indicate that the quick application has been successfully transferred to the second device for execution; A second callback function is called, where the second callback function is used to indicate that the quick application is successfully transferred to the second device for execution.

8. The method according to claim 1, characterized in that The method further comprises: In response to successfully transferring the quick app to the second device for execution, synchronizing the running state of the quick app with the second device.

9. A quick application control method, characterized in that: include: receiving a transfer request sent by a first device, wherein the transfer request is used to request to transfer a quick application running on the first device from the first device to a second device for execution; Responding to the transfer request and sending a transfer request reply message; receiving transfer data sent by the first device based on the transfer request reply message, and transferring the quick application to the second device for execution; The transfer data includes the quick application startup RPK file package and application status data.

10. The method according to claim 9, characterized in that The receiving a transfer request sent by the first device includes: receiving, using a communication discovery capability and in accordance with a first protocol format, a transfer request sent by a first device; The first protocol format includes a first target device identifier, a first source device identifier, a first message type identifier, and a first message content; The first target device identifier is used to identify the second device, and the first source device identifier is used to identify the first device; The first message type identifier is used to identify the transfer request, and the first message content includes data content corresponding to the transfer request.

11. The method according to claim 9, characterized in that The transfer request reply message has a second protocol format; The second protocol format includes a second target device identifier, a second source device identifier, a second message type identifier, and second message content; The second target device identifier is used to identify the first device, and the second source device identifier is used to identify the second device; The second message type identifier is used to identify the transfer request reply message, and the second message content includes data content indicating whether the transfer request is allowed.

12. The method according to claim 9, characterized in that The transfer data has a third protocol format; The third protocol format includes a third target device identifier, a third source device identifier, a third message type identifier, and a third message content; The third target device identifier is used to identify the second device, and the third source device identifier is used to identify the first device; The third message type identifier is used to identify the transfer data, and the third message content includes an RPK file package and application status data.

13. The method according to any one of claims 9 to 12, characterized in that The receiving the transfer data sent by the first device based on the transfer request reply message includes: If the transfer request reply message indicates that the transfer is allowed, the transfer data sent by the first device based on the transfer request reply message is received.

14. The method according to claim 9, characterized in that After receiving the transfer data sent by the first device based on the transfer request reply message, the method further includes: A transfer data reply message is sent, where the transfer data reply message is used to indicate whether the second device successfully receives the transfer data.

15. The method according to claim 9, characterized in that After transferring the quick application to the second device for execution, the method further includes: Send successful transfer indication information, where the successful transfer indication information is used to indicate that the quick application is successfully transferred to the second device for execution.

16. The method according to claim 9, characterized in that The method further comprises: In response to successfully transferring the quick app to the second device for execution, synchronizing the running state of the quick app with the first device.

17. A quick application control device, characterized in that: include: a sending unit, configured to send a transfer request to the second device, wherein the transfer request is used to request to transfer the quick application running on the first device from the first device to the second device for execution; a receiving unit, configured to receive a transfer request reply message, wherein the transfer request reply message is sent by the second device in response to the transfer request; A transfer unit, configured to send transfer data to the second device based on the transfer request reply message, so as to transfer the quick application to the second device for execution; The transfer data includes the quick application startup RPK file package and application status data.

18. A quick application control device, characterized in that: include: A receiving unit, configured to receive a transfer request sent by a first device, wherein the transfer request is used to request to transfer a quick application running on the first device from the first device to a second device for execution; a sending unit, configured to respond to the transfer request and send a transfer request reply message; A transfer unit, configured to receive transfer data sent by the first device based on the transfer request reply message, and transfer the quick application to the second device for execution; The transfer data includes the quick application startup RPK file package and application status data.

19. A quick application control device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to: execute the quick application control method described in any one of claims 1-8, or execute the quick application control method described in any one of claims 9-16.

20. A storage medium, characterized in that: The storage medium stores instructions, and when the instructions in the storage medium are executed by the processor of the first device, the first device is able to execute the quick application control method according to any one of claims 1 to 8; Or when the instructions in the storage medium are executed by the processor of the second device, the second device is enabled to execute the quick application control method described in any one of claims 9-16.

Images