Application circulation method, device and system and storage medium

Abstract

The invention relates to an application circulation method, device and system and a storage medium. The method comprises the steps that based on a target container, a target application runs in a first device, the target container is used for providing a running environment for the target application, and the target container is deployed in the first device and a second device; first information sent by the second device is obtained, the first information is used for indicating the first device to send target data to the second device, and the target data is data needed when the target application runs in the second device; and sending the target data to the second equipment based on the first information, so that the target application runs in the second equipment. Through the method, the application circulation without transmitting the application running environment data is realized, and the resource overhead of the application circulation is reduced.

Description

Technical Field

[0001] The present disclosure relates to the field of information processing, and in particular to an application flow method, device, system and storage medium. Background Art

[0002] Application transfer refers to the ability of a software application to migrate and run on different types of terminals. With the development of mobile Internet and terminal technology, users often need to transfer applications between various types of terminal platforms.

[0003] In the related technology, application transfer mainly relies on application cloning technology. In the process of application transfer, in order to enable the application to run on the transferred platform, it is often necessary to synchronously send the application running environment to the transferred platform. Therefore, the transfer process is relatively complicated and occupies a lot of resources. Summary of the invention

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

[0005] According to a first aspect of an embodiment of the present disclosure, there is provided an application flow method, which is applied to a first device, comprising: running a target application on the first device based on a target container, wherein the target container is used to provide a running environment for the target application, and the target container is deployed on the first device and a second device; obtaining first information sent by the second device, wherein the first information is used to instruct the first device to send target data to the second device, wherein the target data is data required for the target application when the target application is running on the second device; and sending the target data to the second device based on the first information, so that the target application runs on the second device.

[0006] In one embodiment, sending the target data to the second device based on the first information includes: if the first information includes a first detection result, there is no need to send the target data to the second device, and the first detection result indicates that the second device includes all the data required for the target application to run; if the first information includes a second detection result, determining the target data based on the first information, and sending the target data to the second device, and the second detection result indicates that the second device includes partial data or empty data required for the target application to run.

[0007] In another embodiment, determining the target data based on the first information includes: in response to the first information including a second detection result, obtaining first information sent by the second device, the first information including a list of the target data; and determining the target data based on the list of the target data.

[0008] In another embodiment, the obtaining of the first information sent by the second device includes: sending a first request to the second device, the first request being used to request the second device to perform a flow detection on the target application, the flow detection on the target application being used to determine the target data; and obtaining the first information sent by the second device, the first information being sent by the second device after a flow detection on the target application.

[0009] In yet another embodiment, an operating platform corresponding to the first device is different from an operating platform corresponding to the second device.

[0010] According to a second aspect of an embodiment of the present disclosure, there is provided an application flow method, which is applied to a second device, and includes: sending first information to a first device, wherein the first information is used to instruct the first device to send target data to the second device, wherein the target data is data required for a target application when the target application is running on the second device, wherein the target application is running on the first device based on a target container deployed on the first device, wherein the target container is used to provide a running environment for the target application, and wherein the target container is deployed on the first device and the second device; obtaining the target data sent by the first device based on the first information, and running the target application.

[0011] In one embodiment, the acquiring the target data sent by the first device based on the first information and running the target application includes: if the first information includes a first detection result, there is no need to acquire the target data sent by the first device, and the target application is directly run, and the first detection result indicates that the second device includes all the data required for the target application to run; if the first information includes a second detection result, the target data is acquired and the target application is run, and the target data is determined and sent by the first device based on the first information, and the second detection result indicates that the second device includes partial data or empty data required for the target application to run.

[0012] In another embodiment, the target data is determined by the first device based on the first information, including: in response to the detection result being the second detection result, sending the first information to the first device so that the first device determines the target data based on the list of target data, and the first information includes the list of target data.

[0013] In another embodiment, the sending of the first information to the first device includes: obtaining a first request sent by the first device, the first request being used to request a flow detection for the target application to the second device, the flow detection of the target application being used to determine the target data; performing a flow detection based on the first request and determining the first information; and sending the first information to the first device.

[0014] In yet another embodiment, an operating platform corresponding to the first device is different from an operating platform corresponding to the second device.

[0015] According to a third aspect of an embodiment of the present disclosure, there is provided an application flow method, including: a first device runs a target application on the first device based on a target container, the target container is used to provide a running environment for the target application, the target container is deployed on the first device and a second device, and the running platform corresponding to the first device is different from the running platform corresponding to the second device; the second device performs flow detection on the target application to determine target data, the target data being data required for the target application when the second device is running; the second device sends first information to the first device, the first information is used to instruct the first device to send target data to the second device; the first device sends the target data to the second device based on the first information, so that the target application runs on the second device; the second device obtains the target data sent by the first device based on the first information, and runs the target application.

[0016] According to a fourth aspect of an embodiment of the present disclosure, a first application circulation device is provided, comprising: a processing module, for running a target application on a first device based on a target container, the target container being used to provide a running environment for the target application, the target container being deployed on a first device and a second device; the processing module is also used to obtain first information sent by the second device, the first information being used to instruct the first device to send target data to the second device, the target data being data required for the target application when the target application is running on the second device; a transceiver module, for sending the target data to the second device based on the first information, so that the target application can run on the second device.

[0017] In one embodiment, the transceiver module sends the target data to the second device based on the first information, including: when the first information includes a first detection result, there is no need to send the target data to the second device, and the first detection result indicates that the second device includes all the data required for the target application to run; when the first information includes a second detection result, the target data is determined based on the first information, and the target data is sent to the second device, and the second detection result indicates that the second device includes partial data or empty data required for the target application to run.

[0018] In another embodiment, the transceiver module determines the target data based on the first information, including: when the detection result is the second detection result, obtaining the first information sent by the second device, the first information including the list of the target data; determining the target data based on the list of the target data.

[0019] In another embodiment, the transceiver module obtains the first information sent by the second device, including: sending a first request to the second device, the first request is used to request the second device to perform a flow detection on the target application, the flow detection of the target application is used to determine the target data; and obtaining the first information sent by the second device.

[0020] In yet another embodiment, an operating platform corresponding to the first device is different from an operating platform corresponding to the second device.

[0021] According to a fifth aspect of an embodiment of the present disclosure, a second application flow device is provided, including: a transceiver module, used to send first information to a first device, the first information is used to instruct the first device to send target data to the second device, which is data required for a target application when the target application is running on the second device, the target application is running on the first device based on a target container deployed on the first device, the target container is used to provide a running environment for the target application, and the target container is deployed on the first device and the second device; the transceiver module is also used to obtain the target data sent by the first device based on the first information.

[0022] In one embodiment, the transceiver module obtains the target data sent by the first device based on the first information, and runs the target application, including: if the first information includes a first detection result, the target application is directly run, and the transceiver module does not need to obtain the target data sent by the first device, and the first detection result indicates that the second device includes all the data required for the target application to run; if the first information includes a second detection result, the transceiver module obtains the target data, and the target data is determined and sent by the first device based on the first information, and the second detection result indicates that the second device includes partial data or empty data required for the target application to run.

[0023] In another embodiment, the target data is determined by the first device based on the first information, including: in response to the detection result being the second detection result, the transceiver module sends the first information to the first device, so that the first device determines the target data based on the list of target data, and the first information includes the list of target data.

[0024] In another embodiment, the transceiver module sends the first information to the first device, including: obtaining a first request sent by the first device, the first request is used to request the second device to perform a flow detection on the target application, the flow detection of the target application is used to determine the target data; performing a flow detection based on the first request and determining the first information; and sending the first information to the first device.

[0025] In yet another embodiment, an operating platform corresponding to the first device is different from an operating platform corresponding to the second device.

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

[0027] According to the seventh aspect of an embodiment of the present disclosure, an application flow system is provided, comprising a first device and a second device, wherein the first device is configured to execute the application flow method described in the first aspect or any one of the embodiments of the first aspect, and the second device is configured to execute the application flow method described in the second aspect or any one of the embodiments of the second aspect.

[0028] 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 device, the device is enabled to execute the application flow method described in the first aspect and any one of the implementations of the first aspect, or the second aspect and any one of the implementations of the second aspect.

[0029] The technical solution provided by the embodiments of the present disclosure may include the following beneficial effects: by providing a running environment for the target application based on the container, and determining the data required for the target application when running on the device after the flow based on the device after the flow, and transmitting the specified data so that the target application can run normally on the device after the flow, thereby realizing the application flow without transmitting the application running environment data, and reducing the resource overhead of the application flow.

[0030] 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

[0031] 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.

[0032] Figure 1 The diagram is a schematic diagram of a scenario of application transfer based on virtualization technology according to an exemplary embodiment.

[0033] Figure 2 The figure is a flow chart of an application transfer method according to an exemplary embodiment.

[0034] Figure 3 The figure is a flowchart of a method for sending target data according to an exemplary embodiment.

[0035] Figure 4 The invention is a flowchart showing a method for determining target data based on first information according to an exemplary embodiment.

[0036] Figure 5 The present invention is a flowchart showing a method for acquiring first information sent by a second device according to an exemplary embodiment.

[0037] Figure 6 The figure is a flow chart of an application transfer method according to an exemplary embodiment.

[0038] Figure 7 The figure is a flowchart of a method for sending target data according to an exemplary embodiment.

[0039] Figure 8The invention is a flowchart showing a method for determining target data by a first device based on first information according to an exemplary embodiment.

[0040] Fig. 9 The present invention is a flowchart of a method for sending first information to a first device according to an exemplary embodiment.

[0041] Fig.10 The diagram is a schematic diagram of an application flow method interaction system according to an exemplary embodiment.

[0042] Fig.11 The diagram is a schematic diagram of a scenario of application flow according to an exemplary embodiment.

[0043] Fig.12 The diagram is a schematic diagram of an application flow method interaction system according to an exemplary embodiment.

[0044] Fig.13 The figure is a block diagram of an application flow device according to an exemplary embodiment.

[0045] Fig.14 The figure is a block diagram of an application flow device according to an exemplary embodiment.

[0046] Fig.15 The invention is a block diagram showing a device for application streaming according to an exemplary embodiment.

[0047] Fig.16 The invention is a block diagram showing a device for application streaming according to an exemplary embodiment. DETAILED DESCRIPTION

[0048] 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.

[0049] Application mobility refers to the ability of an application (e.g., mobile application, computer software, etc.) to run on different devices or platforms. This capability enables users to seamlessly use the same application across different devices such as various types of terminals (e.g., mobile phones, tablets, TVs, wearable devices).

[0050] For example, a user may start using application A on a computer, and then continue interacting with application A on the user's phone or tablet without having to start over or lose your progress.

[0051] It is understandable that different types of terminals correspond to different operating systems or application running environments, such as the Android system on a mobile phone and the Windows system on a computer.

[0052] In some embodiments, for the above scenarios, application developers need to take into account the characteristics of various devices and operating systems to ensure that the application can be migrated and run seamlessly.

[0053] In related technologies, achieving this cross-device application flow faces certain challenges, mainly because each device and platform has its own operating system and hardware characteristics, which makes the development and maintenance of cross-device applications complicated. However, with the development of mobile Internet and the Internet of Things, it is becoming increasingly important to meet users' needs for seamless use of applications on various devices.

[0054] In some embodiments, application transfer can be achieved through application cloning technology.

[0055] It can be understood that "application cloning" refers to the technology of copying (or "cloning") an instance of an application and its state (including data in memory, application settings, application running environment, user session status, etc.) from one device to another by using system-level virtualization technology.

[0056] Figure 1 FIG. 1 is a schematic diagram of a scenario of application transfer based on virtualization technology according to an exemplary embodiment. Figure 1 As shown, during the application flow from the first device to the second device, all relevant information of the application (including the operating environment and the corresponding virtual machine) is copied, so that the application can continue to run on the new device in the same state as the original device. Therefore, users do not need to reinstall the application and will not lose their application status and data on the original device.

[0057] However, the main goal of virtualization technology is to create an environment similar to physical hardware, making applications and operating systems think that they are running on their own dedicated system. This involves replicating all the various functions and features of physical hardware, including the operating system, system libraries and other related components.

[0058] Simply packaging an application does not necessarily ensure that it will run correctly in the new environment. This is because applications often depend on specific versions of the operating system, system libraries, and other components. If these dependencies do not exist in the new environment or are inconsistent with the original environment, the application may not run properly.

[0059] Therefore, when users transfer applications based on virtualization technology, they need to include the entire system, not just an application, which is the "system-level virtualization technology" mentioned above.

[0060] However, although "system-level virtualization technology" helps create a consistent and repeatable environment and makes it easier for users to manage the system, in the actual application flow process, the resources occupied by the application running environment are often greater than the application itself. Therefore, this method undoubtedly generates serious resource overhead.

[0061] Based on this, the present disclosure proposes an application flow method, which provides a running environment for the application based on a container, determines the data required for the target application when running on the device after the flow based on the device after the flow, and transmits the specified data so that the target application can run normally on the device after the flow, thereby realizing application flow without transmitting the application running environment data, and reducing the resource overhead of application flow.

[0062] It should be noted that, in order to facilitate understanding of the embodiments of the present disclosure, some terms used in the embodiments of the present disclosure are explained below to facilitate understanding by those skilled in the art.

[0063] Container: In the software field, a container is a lightweight, independent, portable packaging technology designed to package and run applications. The container provides an independent operating environment for the application and all its dependencies, ensuring that the application can run in the same way regardless of the operating system and infrastructure.

[0064] Containers are more lightweight than traditional virtualization because they share the kernel of the host system without running a complete operating system. Each container runs in an isolated environment and has its own file system, network stack, etc. This property makes containers very suitable for scenarios such as microservice architecture, continuous integration / continuous deployment (CI / CD), and scalable cloud-native applications.

[0065] Exemplarily, the container technology includes at least one of the following: Docker, k8s (Kubernetes), containerd, and rkt (rocket).

[0066] Among them, Docker is an open source application container engine that allows developers to package their applications and dependent packages into a portable container, and then publish them to any popular Linux or Windows machine, and can also achieve virtualization. The container is completely sandboxed, and there is no interface between them. Docker uses a client-server (C / S) architecture. The Docker client communicates with the Docker daemon, which is responsible for building, running, and distributing Docker containers. The Docker client and daemon can run on the same system, or the Docker client can interact with the remote Docker daemon over the network.

[0067] k8s is an open source container orchestration system for automating the deployment, scaling, and management of application containers. Kubernetes originated from Google and is now maintained by the Cloud Native Computing Foundation (CNCF).

[0068] Containerd is a container supervisor designed to meet the requirements of being minimal, embeddable, robust (ie, robust), simple and efficient. The main responsibility of "containerd" is to handle container lifecycle issues such as image transfer and storage, container execution and monitoring, low-level storage and network interfaces, etc. It focuses on simplicity, robustness and portability, and can be easily embedded in larger systems.

[0069] rkt is an open source container runtime engine. Its goal is to create a modular, composable, secure, and simple container runtime solution.

[0070] It should be noted that the “container” involved in the embodiments of the present disclosure may refer to one or more of the above-mentioned containers, or other related container technologies.

[0071] Application installation package: A file that contains software or an application and its installation program, usually stored in a specific file format. Different operating systems have different application installation package formats. It also includes library files, data files, help documents, etc. required for the software to run. Users can install the application and all the files it needs on the device by running the application installation package. During the installation process, the installation program usually copies and configures files, creates necessary system links, etc. based on the user's input and system configuration, so that the application is ready and can run on the device.

[0072] Data serialization: In software development, serialization is the process of converting a data structure or object state into a format that can be stored or transmitted. Data serialization usually means converting data into a byte stream or string.

[0073] Data deserialization: In software development, deserialization is the process of converting serialized data back to their original data format or object state.

[0074] Application configuration information: Application configuration information refers to a set of parameters or settings used to determine how an application runs. This information can include server ports, database connection details, application programming interface (API) keys, log settings, application behavior switches, localization / internationalization settings, etc. Configuration information is usually separated from the application code and loaded when the application starts or runs, enabling the application to run in different ways in different environments (such as development, test, and production environments).

[0075] Application log: Application log is a series of information or events recorded during the running of the application. This information usually includes the status of the program, user operations, system events, errors or exceptions, etc.

[0076] Software Development Kit (SDK): is a set of tools including documents, samples, programs, etc. for developing specific software. These tools can help developers develop software that meets the requirements of specific platforms, specific systems or specific programming languages ​​more easily and conveniently.

[0077] The Disclosure Figure 2 is a flow chart of an application transfer method according to an exemplary embodiment. Figure 2 As shown, the application flow method is used for the first device, including the following steps.

[0078] In step S11, based on the target container, the target application is run on the first device, the target container is used to provide a running environment for the target application, and the target container is deployed on the first device and the second device.

[0079] In step S12, first information sent by the second device is obtained, where the first information is used to instruct the first device to send target data to the second device, where the target data is data required by a target application when running on the second device.

[0080] In step S13, target data is sent to the second device based on the first information, so that the target application runs on the second device.

[0081] The application flow method provided in the embodiment of the present disclosure provides an operating environment for the target application based on a container, determines the data required for the target application when running on the device after flow based on the device after flow, and transmits the specified data so that the target application can run normally on the device after flow, thereby realizing application flow without transmitting the application running environment data and reducing the resource overhead of application flow.

[0082] In some embodiments, the target data includes at least one of the following data required for the target application to run on the second device:

[0083] Application installation package, application private storage data, application status data, application configuration information, and application log information.

[0084] In some embodiments, the operating platform corresponding to the first device is the same as the operating platform corresponding to the second device.

[0085] In some embodiments, the operating platform corresponding to the first device is different from the operating platform corresponding to the second device.

[0086] In some embodiments, the target data is data required by the target application when it runs on the second device.

[0087] In some embodiments, the target data is data required by the second device when the second device detects that the target application is running.

[0088] In some embodiments, the private storage data includes at least one of the following:

[0089] User setting information and user application characteristics, etc.

[0090] In some embodiments, the application's state data includes:

[0091] The data corresponding to the serialized state and the data corresponding to the deserialized state.

[0092] In some embodiments, the application configuration information includes at least one of the following:

[0093] Server port, database connection details, Application Programming Interface (API) key, log settings, application behavior switches, localization / internationalization settings, etc.

[0094] In some embodiments, the log information includes at least one of the following:

[0095] Error log information, access log information, transaction log information, audit log information, and debug log information, etc.

[0096] Optionally, the error log information is used to characterize errors or exceptions generated during the running of the application.

[0097] Optionally, the access log information is used to characterize access events and behaviors of visitors to the application.

[0098] Optionally, transaction log information is used to characterize business operations in the application.

[0099] Optionally, the debugging log information is used to represent relevant information of the application being debugged.

[0100] In some embodiments, the target container may be deployed based on a pre-design.

[0101] In some embodiments, terms such as "certain", "preset", "preset", "set", "indicated", "some", "any", and "first" can be interchangeable, and "specific A", "preset A", "preset A", "set A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-defined in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., and can also be interpreted as specific A, some A, any A, or first A, etc., but is not limited to this.

[0102] In some embodiments, "obtain", "obtain", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from high levels, obtaining by self-processing, autonomous implementation, etc.

[0103] In some embodiments, "operating platform", "system platform", "development platform", "system environment", "operating environment" and "application operating environment" can be interchangeable, and can be interpreted as the environment in which the application runs.

[0104] In some embodiments, the first information may be demand information or demand instructions.

[0105] In some embodiments, the first information may be indication information.

[0106] The application transfer method involved in the embodiment of the present disclosure may include at least one of steps S11 to S13. For example, step S13 may be implemented as an independent embodiment, step S11 may be implemented as an independent embodiment, and step S11+step S12+step S13 may be implemented as independent embodiments, but are not limited thereto.

[0107] In some embodiments, steps S11 and S12 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0108] In some embodiments, steps S12 and S13 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0109] In some embodiments, steps S11 and S13 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0110] In some embodiments, see Figure 2 Other optional implementations recorded before or after the corresponding description.

[0111] Figure 3 is a flow chart of a method for sending target data according to an exemplary embodiment. Figure 3 As shown, sending target data to the second device based on the first information includes the following steps.

[0112] In step S21, if the first information includes the first detection result, there is no need to send the target data to the second device, and the first detection result indicates that the second device includes all the data required for the target application to run.

[0113] In step S22, if the first information includes a second detection result, target data is determined based on the first information and sent to the second device, and the second detection result indicates that the second device includes partial data or empty data required for the target application to run.

[0114] In the application flow method provided by the embodiment of the present disclosure, the first device receives the detection result of the second device and sends the specified target data according to the different detection results, thereby avoiding the waste of sending resources caused by repeated data sending.

[0115] In some embodiments, "no need to send", "no expectation of sending", and "no sending" can be interchangeable, which can be interpreted as in the process of executing the sending action, the priority of not sending is higher than the priority of sending, and so on.

[0116] In some embodiments, the first information includes the first detection result, and an exemplary scenario in which the target data does not need to be sent to the second device is as follows:

[0117] The first device and the second device share a storage space, such as a cloud storage space. And all the data of the target application are stored in the shared storage space. Based on this, the first device does not need to send the target data to the second device, and the second device can directly run the second application based on the shared storage space.

[0118] In some embodiments, if the first information includes the first detection result, empty data is sent to the second device.

[0119] In some embodiments, "empty data", "blank data" and "zero data" can be interchangeable, which can be interpreted as data that the data set is an empty set, and other meanings.

[0120] In some embodiments, when the first information includes the first detection result, the first device does not need to send any data to the second device, and the second device directly runs the target application.

[0121] In some embodiments, the second detection result indicates that the second device includes part of the data required for the target application to run, including at least one of the following situations:

[0122] -A) The target application requires M data when running on the second device, and the second device includes K data required by the target application when running on the second device, wherein M is an integer greater than or equal to 1, K is an integer greater than or equal to 1, and M is greater than K.

[0123] -B) M data required by the target application when running on the second device, and the second device includes 0 data required by the target application when running on the second device, where M is an integer greater than or equal to 1.

[0124] The application transfer method involved in the embodiment of the present disclosure may include one of step S21 to step S22. For example, step S21 may be implemented as an independent embodiment, and step S22 may be implemented as an independent embodiment, but is not limited thereto.

[0125] In some embodiments, step S21 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0126] In some embodiments, step S22 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0127] Figure 4 is a flowchart showing a method for determining target data based on first information according to an exemplary embodiment. Figure 4 As shown, sending target data to the second device based on the first information includes the following steps.

[0128] In step S31, in response to the first information including the second detection result, the first information sent by the second device is acquired, the first information including the list of target data.

[0129] In step S32, target data is determined based on the list of target data.

[0130] In some embodiments, the list of target data includes at least one of the following:

[0131] Identification of target data, identifier of target data, etc.

[0132] In some embodiments, the list of target data, the representation may include a collection representation.

[0133] Figure 5 is a flow chart showing a method for obtaining first information sent by a second device according to an exemplary embodiment. Figure 5 As shown, obtaining the first information sent by the second device includes the following steps.

[0134] In step S41, a first request is sent to the second device, where the first request is used to request the second device to perform a flow detection on a target application, where the flow detection on the target application is used to determine target data.

[0135] In step S42, first information sent by the second device is obtained, where the first information is sent by the second device after flow detection for the target application.

[0136] The application flow method provided in the embodiment of the present disclosure triggers the second device to perform application flow detection through a first request, thereby triggering the second device to send a first message. Compared with periodic sending, the second device can timely feedback the current application flow status, while also avoiding the waste of sending resources caused by repeatedly sending the first message.

[0137] In some embodiments, the first device sends a first request to the second device.

[0138] In some embodiments, the first device sends second information to the second device, where the second information is used to request flow detection for a target application from the second device, and the flow detection of the target application is used to determine target data.

[0139] In some embodiments, the first device sends third information to the second device, where the third information is used to carry the first request.

[0140] In some embodiments, the first device obtains second information sent by the second device.

[0141] Figure 6 is a flow chart of an application transfer method according to an exemplary embodiment. Figure 6As shown, the application flow method is used for the second device, including the following steps.

[0142] In step S51, first information is sent to the first device, and the first information is used to instruct the first device to send target data to the second device. The target data is data required for the target application when it runs on the second device. The target application runs on the first device based on the target container deployed on the first device. The target container is used to provide a running environment for the target application. The target container is deployed on the first device and the second device.

[0143] In step S52, target data sent by the first device based on the first information is acquired, and a target application is run.

[0144] In the application transfer method provided by the embodiment of the present disclosure, the second device performs a transfer detection on the target application to determine the data required by the target application when the second device is running. Based on this, the second device makes a data request to the first device, and runs the target application on the second platform based on the request data sent by the first device, thereby realizing the application transfer without transmitting the application running environment data, and reducing the resource overhead of the application transfer.

[0145] In some embodiments, the operating platform corresponding to the first device is the same as the operating platform corresponding to the second device.

[0146] In some embodiments, the operating platform corresponding to the first device is different from the operating platform corresponding to the second device.

[0147] In some embodiments, the target data is data required by the target application when it runs on the second device.

[0148] In some embodiments, the target data is data required by the second device when the second device detects that the target application is running.

[0149] In some embodiments, the target application is subjected to flow detection, and the detection content includes at least one of the following:

[0150] Application installation package, application private storage data, application status data, application configuration information, and application log information.

[0151] It is understandable that the specific information contained in the test content can be found in Figure 2 To avoid repeated reception, the embodiments of the relevant steps in are not repeated here.

[0152] In some embodiments, the first information may be demand information or demand instructions.

[0153] The application transfer method involved in the embodiment of the present disclosure may include at least one of step S51 to step S52. For example, step S52 may be implemented as an independent embodiment, step S51 may be implemented as an independent embodiment, and step S51+step S52 may be implemented as independent embodiments, but are not limited thereto.

[0154] In some embodiments, step S51 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0155] In some embodiments, step S52 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0156] In some embodiments, the description of the optional embodiments related to steps S51 to S52 can refer to steps S11 to S13 and Figure 2 The relevant optional embodiments will not be described in detail here.

[0157] Figure 7 is a flow chart of a method for sending target data according to an exemplary embodiment. Figure 7 As shown, obtaining the target data sent by the first device based on the first information and running the target application includes the following steps.

[0158] In step S61, if the first information includes the first detection result, the second device directly runs the target application without obtaining the target data sent by the first device, and the first detection result indicates that the second device includes all the data required for the target application to run.

[0159] In step S62, if the first information is the second detection result, the target data is obtained and the target application is run. The target data is determined and sent by the first device based on the first information. The second detection result indicates that the second device includes partial data or empty data required for the target application to run.

[0160] In the application transfer method provided by the embodiment of the present disclosure, the second device receives the target data sent by the first device under different detection results and runs the target application, thereby avoiding the waste of sending resources caused by repeated data sending.

[0161] The application transfer method involved in the embodiment of the present disclosure may include one of step S61 to step S62. For example, step S61 may be implemented as an independent embodiment, and step S62 may be implemented as an independent embodiment, but is not limited thereto.

[0162] In some embodiments, step S61 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0163] In some embodiments, step S62 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0164] In some embodiments, the description of the optional embodiments related to steps S61 to S62 can refer to steps S21 to S22 and Figure 3 The relevant optional embodiments will not be described in detail here.

[0165] Figure 8 is a flowchart showing a method for determining target data by a first device based on first information according to an exemplary embodiment. Figure 8 As shown, the target data is determined by the first device based on the first information, including the following steps.

[0166] In step S71, in response to the detection result being the second detection result, first information is sent to the first device so that the first device determines the target data based on the list of target data, and the first information includes the list of target data.

[0167] In some embodiments, the description of the optional embodiments of step S71 can refer to steps S31 to S32 and Figure 4 The relevant optional embodiments will not be described in detail here.

[0168] Fig. 9 is a flowchart of a method for sending first information to a first device according to an exemplary embodiment. Fig. 9 As shown, sending the first information to the first device includes the following steps.

[0169] In step S81, a first request sent by a first device is obtained, where the first request is used to request a flow detection for a target application from a second device, where the flow detection for the target application is used to determine target data.

[0170] In step S82, flow detection is performed based on the first request, and first information is determined.

[0171] In step S83, the first information is sent to the first device.

[0172] The application transfer method involved in the embodiment of the present disclosure may include at least one of steps S81 to S83. For example, step S83 may be implemented as an independent embodiment, step S81 may be implemented as an independent embodiment, and step S81+step S82+step S83 may be implemented as independent embodiments, but are not limited thereto.

[0173] In some embodiments, steps S81 and S82 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0174] In some embodiments, steps S82 and S83 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0175] In some embodiments, steps S81 and S83 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0176] In some embodiments, the description of the optional embodiments of steps S81 to S83 can refer to steps S41 to S42 and Figure 5 The relevant optional embodiments will not be described in detail here.

[0177] The application flow method provided in the embodiment of the present disclosure triggers the second device to perform application flow detection through a first request, thereby triggering the second device to send a first message. Compared with periodic sending, the second device can timely feedback the current application flow status, while also avoiding the waste of sending resources caused by repeatedly sending the first message.

[0178] Fig.10 is a schematic diagram of an application flow method interaction system according to an exemplary embodiment. Fig.10 As shown, the embodiment of the present disclosure relates to an application flow method, which includes the following steps.

[0179] In step S91 , the first device runs the target application.

[0180] In some embodiments, the first device runs the target application on the first device based on the target container.

[0181] In some embodiments, the target container is used to provide a running environment for the target application.

[0182] In some embodiments, the target container is deployed on the first device and the second device.

[0183] In some embodiments, the operating platform corresponding to the first device is different from the operating platform corresponding to the second device.

[0184] In step S92, the second device performs flow detection on the target application.

[0185] In some embodiments, the second device performs flow detection on the target application to determine the target data.

[0186] In some embodiments, the target data is data required by the target application when it runs on the second device.

[0187] In step S93, the second device sends the first information to the first device.

[0188] In some embodiments, the first information is used to request target data from the first device.

[0189] In some embodiments, the first device receives first information sent by the second device.

[0190] In step S94 , the first device sends the target data to the second device based on the first information.

[0191] In some embodiments, the second device receives target data sent from the first device based on the first information.

[0192] In step S95 , the second device runs the target application.

[0193] In some embodiments, the second device runs a target application based on the target data.

[0194] The application transfer method involved in the disclosed embodiment may include at least one of steps S91 to S95. For example, step S92 may be implemented as an independent embodiment, step S93 may be implemented as an independent embodiment, and step S91+step S92+step S93+step S94+step S95 may be implemented as independent embodiments, but are not limited thereto.

[0195] In some embodiments, steps S91, S92, S93, and S94 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0196] In some embodiments, steps S91, S92, S93, and S95 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0197] In some embodiments, steps S91, S92, S94, and S95 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0198] In some embodiments, steps S91, S93, S94, and S95 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0199] In some embodiments, steps S92, S93, S94, and S95 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0200] In some embodiments, the description of the optional embodiments of steps S91 to S95 can be found in Figures 2 to 9 Embodiments and alternative embodiments, Figures 2 to 9 The embodiments and optional embodiments corresponding to each step in the above are not described in detail here.

[0201] In some embodiments, the embodiments of the present disclosure provide an application flow method to achieve flexible application flow functions across heterogeneous platforms and devices, with high maintainability and scalability.

[0202] In some embodiments, applying a flow method includes at least one of the following:

[0203] Data packaging, flow control and data transmission.

[0204] Fig.11 FIG. 1 is a schematic diagram of a scenario of application flow according to an exemplary embodiment. Fig.11 As shown, during the application transfer process, there is no need to transfer the application running environment data, and the application and the corresponding transfer SDK are independently designed.

[0205] In some embodiments, the content of the packaged data includes at least one of the following:

[0206] Application package management, application status management, and application information management.

[0207] In some embodiments, application package management includes packaging the application installation package and private data.

[0208] In some embodiments, application state management includes serializing or deserializing application state.

[0209] In some embodiments, application information management includes: packaging application configuration, log information, etc.

[0210] In some embodiments, the target application runs based on an application running container.

[0211] Optionally, the application running container corresponds to the target container in the above embodiment.

[0212] In some embodiments, the target application container and the transfer SDK are independently configured and can run independently.

[0213] In some embodiments, when the target application is running, the data packaging function is registered to the circulation SDK through the callback function, so that the circulation SDK can call the packaging function corresponding to the target application through the callback function.

[0214] In some embodiments, flow control and data transmission include:

[0215] The source device sends a flow check request to the target device;

[0216] The target device performs a flow check;

[0217] The source device calls the packaged data required in the data requirement table when the application is running according to the data requirement table and sends it to the target device;

[0218] The target device launches the application after receiving the data.

[0219] In some embodiments, the target device performs a flow check including at least one of the following:

[0220] If the check passes, the application is started directly;

[0221] If the check fails, a data request form is sent to the source device.

[0222] In some embodiments, if the application data of the source device and the target device are both stored in a shared storage, the second device directly launches the application.

[0223] Fig.12 is a schematic diagram of an application flow method interaction system according to an exemplary embodiment. Fig.12 As shown, the embodiment of the present disclosure relates to an application flow method, which includes the following steps.

[0224] In step S101, the user initiates a transfer.

[0225] In step S102, the source device SDK initiates a transfer check request to the target device SDK.

[0226] In step S103, the target device SDK executes the transfer check request.

[0227] In step S104, the target device application runs the container to establish a data requirement table.

[0228] In step S105, the target device SDK sends a data requirement table to the source device SDK.

[0229] In step S106 , the source device SDK requests the source device application execution container for required data.

[0230] In step S107, the source device application runs the container to package the data to the source device SDK.

[0231] In step S108, the source device SDK sends the packaged book to the target device SDK.

[0232] In step S109, the application is unpacked and started in the application execution container of the target device.

[0233] In some embodiments, the optional embodiments corresponding to steps S101 to S109 can refer to and be combined with the above corresponding embodiments, which will not be described one by one here.

[0234] It is understandable that the embodiments of the present disclosure can be implemented separately or in combination. The present disclosure only lists the independent implementation schemes of the embodiments, and the implementation of the combined application of the embodiments should not be considered to exceed the scope of the technical solutions of the embodiments of the present disclosure.

[0235] Based on the same concept, the embodiment of the present disclosure also provides an application circulation device.

[0236] Fig.13 FIG. 1 is a block diagram of a first application transfer device 100 according to an exemplary embodiment. Fig.13 The device includes a processing module 101 and a transceiver module 102.

[0237] The processing module 101 is used to run the target application on the first device based on the target container, the target container is used to provide an operating environment for the target application, and the target container is deployed on the first device and the second device; the processing module 101 is also used to obtain the first information sent by the second device, the first information is used to instruct the first device to send target data to the second device, and the target data is the data required by the target application when it runs on the second device.

[0238] The transceiver module 102 is used to send target data to the second device based on the first information, so that the target application runs on the second device.

[0239] In some embodiments, the transceiver module 102 sends target data to the second device based on the first information, including: when the first information includes a first detection result, there is no need to send the target data to the second device, and the first detection result represents that the second device includes all the data required for the target application to run; when the first information includes a second detection result, the target data is determined based on the first information, and the target data is sent to the second device, and the second detection result represents that the second device includes partial data or empty data required for the target application to run.

[0240] In some embodiments, the transceiver module 102 determines the target data based on the first information, including: when the detection result is the second detection result, obtaining the first information sent by the second device, the first information including the list of the target data; determining the target data based on the list of target data.

[0241] In some embodiments, the transceiver module 102 obtains the first information sent by the second device, including: sending a first request to the second device, the first request is used to request the second device to perform flow detection on a target application, the flow detection of the target application is used to determine the target data; obtaining the first information sent by the second device.

[0242] In some embodiments, the operating platform corresponding to the first device is different from the operating platform corresponding to the second device.

[0243] Fig.14 FIG. 2 is a block diagram of a second application transfer device 200 according to an exemplary embodiment. Fig.14 , the device includes a transceiver module 201.

[0244] The transceiver module 201 is used to send the first information to the first device, where the first information is used to instruct the first device to send target data to the second device, which is data required for the target application when it runs on the second device. The target application runs on the first device based on the target container deployed on the first device. The target container is used to provide a running environment for the target application, and the target container is deployed on the first device and the second device. The transceiver module 201 is also used to obtain the target data sent by the first device based on the first information.

[0245] In some embodiments, the transceiver module 201 obtains target data sent by the first device based on the first information and runs the target application, including: if the first information includes a first detection result, the target application is directly run, and the transceiver module 201 does not need to obtain the target data sent by the first device, and the first detection result represents that the second device includes all the data required for the target application to run; if the first information includes a second detection result, the transceiver module 201 obtains the target data, and the target data is determined and sent by the first device based on the first information, and the second detection result represents that the second device includes part of the data required for the target application to run.

[0246] In some embodiments, the target data is determined by the first device based on the first information, including: in response to the detection result being the second detection result, the transceiver module 201 sends the first information to the first device so that the first device determines the target data based on the list of target data, and the first information includes the list of target data.

[0247] In some embodiments, the transceiver module 201 sends the first information to the first device, including: obtaining a first request sent by the first device, the first request is used to request a flow detection for a target application to the second device, the flow detection of the target application is used to determine the target data; performing a flow detection based on the first request and determining the first information; sending the first information to the first device.

[0248] Fig.151 is a block diagram of a device 300 for application streaming 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.

[0249] Reference Fig.15 The audio playback 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 .

[0250] 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.

[0251] 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.

[0252] 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.

[0253] 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.

[0254] 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.

[0255] 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.

[0256] 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.

[0257] 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.

[0258] 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.

[0259] 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.

[0260] Fig.16 4 is a block diagram of a device 400 for application streaming according to an exemplary embodiment. For example, the device 400 may be provided as a server. Fig.16 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 executable by the processing component 422, such as an application. 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 instructions to perform the above-mentioned screen display method.

[0261] 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.

[0262] 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.

[0263] 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.

[0264] It will be further understood that the terms “center”, “longitudinal”, “lateral”, “front”, “back”, “up”, “down”, “left”, “right”, “vertical”, “horizontal”, “top”, “bottom”, “inside”, “outside”, etc., indicating orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, are only for the convenience of describing the present embodiment and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation.

[0265] 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.

[0266] 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.

[0267] 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.

[0268] 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. An application circulation method, characterized in that: Applied to a first device, comprising: Based on a target container, running a target application on the first device, the target container is used to provide a running environment for the target application, and the target container is deployed on the first device and the second device; Acquire first information sent by the second device, where the first information is used to instruct the first device to send target data to the second device, where the target data is data required by the target application when the second device is running; The target data is sent to the second device based on the first information, so that the target application runs on the second device.

2. The method according to claim 1, characterized in that: The sending the target data to the second device based on the first information includes: If the first information includes a first detection result, there is no need to send the target data to the second device, and the first detection result indicates that the second device includes all the data required for the target application to run; If the first information includes a second detection result, target data is determined based on the first information and sent to the second device, wherein the second detection result indicates that the second device includes partial data or empty data required for the target application to run.

3. The method according to claim 2, characterized in that The determining target data based on the first information includes: In response to the first information including the second detection result, acquiring first information sent by the second device, where the first information includes the list of the target data; The target data is determined based on the list of target data.

4. The application circulation method according to claim 1, characterized in that: The acquiring the first information sent by the second device includes: Sending a first request to the second device, where the first request is used to request the second device to perform a flow detection on the target application, where the flow detection on the target application is used to determine the target data; The first information sent by the second device is obtained, where the first information is sent by the second device after flow detection on the target application.

5. The method according to any one of claims 1 to 4, characterized in that An operating platform corresponding to the first device is different from an operating platform corresponding to the second device.

6. An application circulation method, characterized in that: Applied to the second device, comprising: Sending first information to a first device, where the first information is used to instruct the first device to send target data to the second device, where the target data is data required by a target application when the target application is running on the second device, where the target application is running on the first device based on a target container deployed on the first device, where the target container is used to provide a running environment for the target application, and where the target container is deployed on the first device and the second device; The target data sent by the first device based on the first information is acquired, and the target application is run.

7. The method according to claim 6, characterized in that The acquiring the target data sent by the first device based on the first information and running the target application includes: If the first information includes a first detection result, the target application can be directly run without acquiring the target data sent by the first device, and the first detection result indicates that the second device includes all the data required for the target application to run; If the first information includes a second detection result, the target data is obtained and the target application is run. The target data is determined and sent by the first device based on the first information. The second detection result indicates that the second device includes partial data or empty data required for the target application to run.

8. The method according to claim 7, characterized in that The target data is determined by the first device based on the first information, including: In response to the detection result being the second detection result, the first information is sent to the first device so that the first device determines the target data based on the list of target data, wherein the first information includes the list of target data.

9. The method according to claim 8, characterized in that The sending the first information to the first device includes: Acquire a first request sent by the first device, where the first request is used to request the second device to perform a flow detection on the target application, where the flow detection on the target application is used to determine the target data; Performing flow detection based on the first request and determining the first information; The first information is sent to the first device.

10. The method according to any one of claims 6 to 9, characterized in that An operating platform corresponding to the first device is different from an operating platform corresponding to the second device.

11. A first application circulation device, characterized in that: include: A processing module, configured to run a target application on a first device based on a target container, wherein the target container is configured to provide a running environment for the target application, and wherein the target container is deployed on the first device and the second device; The processing module is further used to obtain first information sent by the second device, where the first information is used to instruct the first device to send target data to the second device, where the target data is data required by the target application when the second device is running; The transceiver module is used to send the target data to the second device based on the first information, so that the target application runs on the second device.

12. A second application circulation device, characterized in that: include: a transceiver module, configured to send first information to a first device, wherein the first information is used to instruct the first device to send target data to a second device, wherein the target data is data required by a target application when the second device is running, wherein the target application is running on the first device based on a target container deployed on the first device, wherein the target container is used to provide a running environment for the target application, and wherein the target container is deployed on the first device and the second device; The transceiver module is further used to obtain the target data sent by the first device based on the first information.

13. An application circulation device, characterized in that: include: a memory for storing processor executable instructions; Wherein, the processor is configured to: execute the application flow method described in any one of claims 1 to 5 or 6 to 10.

14. An application circulation system, characterized in that: The invention comprises a first device and a second device, wherein the first device is configured to implement the application transfer method described in any one of claims 1 to 5, and the second device is configured to implement the application transfer method described in any one of claims 6 to 10.

15. A storage medium storing instructions, characterized in that: When the instruction is executed on a device, the device executes the application transfer method as described in any one of claims 1 to 5 or 6 to 10.

Images