Multi-system application running method and device, storage medium and program product
By listening to the operation instructions of the native system and calling the corresponding instructions of the container system, the problem of inconsistent application operation in multiple system environments is solved, accurate transmission and closed-loop feedback of cross-system operations are achieved, and the user's unconscious interactive experience is improved.
Patent Information
- Application Number
- CN202411536779.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-31
- Publication Date
- 2024-11-29
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The prior art is difficult to run applications of other systems without perceptually in a multi-system environment, resulting in inconsistent application window display, inconsistent life cycle calls, and reduced user interaction experience.
By listening to the operation instructions of the native system and calling the corresponding container system operation instructions, we ensure the operation consistency between the native system and the container system, and feedback the operation results on the proxy application, achieving accurate transmission and closed-loop feedback across systems operations.
It improves the unsensed interactive experience of users running applications on multiple systems, reduces system adaptation work, ensures operation accuracy and consistency, and enhances the user's immediate feedback experience.
Smart Images

Figure CN119045953A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method, device, storage medium and program product for running a multi-system application. Background Art
[0002] With the development of containerization and virtualization technologies, application-level running methods that are compatible with various other systems on desktop systems are also constantly developing, such as Anbox (Android in a box) technology and Waydroid technology. By running a complete Android system in a container, Linux users are provided with a way to experience Android applications in a desktop environment.
[0003] However, most conventional application-level compatibility methods make it difficult to run applications of other systems without noticing, and may cause problems such as inconsistent application window display and inconsistent application life cycle calls. In addition, the management and use of the application itself, such as installation, uninstallation, operation and configuration, usually require users to manually perform them in the Anbox application manager interface or command line, which may reduce the user's interactive experience.
[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention
[0005] The main purpose of this application is to provide a multi-system application running method, device, storage medium and program product, aiming to improve the user's non-perceptual interactive experience of running applications on multiple systems.
[0006] To achieve the above objectives, the present application proposes a multi-system application operation method, the method comprising: When a first operation instruction of a proxy application for a native system is monitored, performing a first operation corresponding to the first operation instruction on the proxy application; calling, through an operation interface corresponding to the first operation instruction, a second operation instruction for a container application of the container system, wherein the container application matches the proxy application; Execute a second operation corresponding to the second operation instruction on the container application; An execution result of the second operation is determined, and an operation corresponding to the execution result is performed on the proxy application.
[0007] In one embodiment, before the step of performing a first operation corresponding to the first operation instruction on the proxy application when a first operation instruction for the native system is monitored, the step further includes: On the native system, decompress the obtained system application installation package to obtain the proxy application installation package and the container application installation package; Sending information of the container application installation package to the container system so that the container system installs the container application; When the installation result of the container application is successful, the proxy application is installed on the native system.
[0008] In one embodiment, the method further comprises: In a case where a first uninstallation instruction for the native system is monitored, determining a package name of an uninstallation application corresponding to the first uninstallation instruction; In the case where the package name of the uninstalled application is the package name of the proxy application, the proxy application is uninstalled, and a second uninstall instruction for the container application is sent to the container system, so that the container system uninstalls the container application according to the second uninstall instruction.
[0009] In one embodiment, the operations corresponding to the first operation instruction and the second operation instruction are the same, and the step of performing the second operation corresponding to the second operation instruction on the container application includes: In the case where the first operation instruction is a pull-up instruction, the container application is pulled up on the container system, and an image interaction link is established with the proxy application, wherein the image interaction link is used to synchronously display images between the native system and the container system.
[0010] In one embodiment, the step of performing the second operation corresponding to the second operation instruction on the container application includes: In the case where the first operation instruction is an exit instruction, the container application is exited on the container system, and the image interaction link is terminated.
[0011] In one embodiment, the step of performing the second operation corresponding to the second operation instruction on the container application includes: In the case where the first operation instruction is a switch foreground instruction, the container application is displayed in a display area on the container system, and the image interactive link is restored.
[0012] In one embodiment, the step of performing the second operation corresponding to the second operation instruction on the container application includes: In a case where the first operation instruction is a background switching instruction, the container application is switched to a non-display area on the container system, and the image interaction link is disconnected.
[0013] In addition, to achieve the above-mentioned purpose, the present application also proposes a multi-system application running device, the multi-system application running device comprising: The proxy application operation module is used to perform a first operation corresponding to the first operation instruction on the proxy application when a first operation instruction for the native system is monitored; an operation instruction calling module, configured to call a second operation instruction for a container application of the container system through an operation interface corresponding to the first operation instruction, wherein the container application matches the proxy application; a container application operation module, configured to execute a second operation corresponding to the second operation instruction on the container application; The result execution module is used to determine the execution result of the second operation and execute an operation corresponding to the execution result on the proxy application.
[0014] In addition, to achieve the above-mentioned purpose, the present application also proposes an electronic device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the multi-system application running method as described above.
[0015] In addition, to achieve the above objectives, the present application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the multi-system application running method described above are implemented.
[0016] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the multi-system application running method described above are implemented.
[0017] One or more technical solutions proposed in the present application have at least the following technical effects: when a first operation instruction of a proxy application for a native system is monitored, a first operation corresponding to the first operation instruction is executed on the proxy application. By implementing the monitoring of the operation for the proxy application, it is convenient to respond to user input or system events in a timely manner, thereby enhancing the user's instant feedback experience; then, through the operation interface corresponding to the first operation instruction, a second operation instruction for the container application of the container system is called. The operation interface realizes loose coupling between the native system and the container system, reduces the adaptation work between the systems, and at the same time, by corresponding each operation instruction to a different operation interface, it is ensured that the second operation instruction for the container application can be accurately found, thereby realizing accurate transmission of cross-system operations; further, the second operation corresponding to the second operation instruction is executed on the container application, thereby ensuring the consistency of the execution of the two operations, that is, ensuring the accuracy of the user's operation perception; finally, the execution result of the second operation is determined, and the operation corresponding to the execution result is executed on the proxy application, thereby realizing closed-loop feedback of the operation, so that the user can operate the container application like operating a native application, and can instantly see the operation result of the container application on the proxy application, thereby improving the user's imperceptible interaction experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0019] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0020] Figure 1 A flowchart diagram of a method for running a multi-system application according to a first embodiment of the present invention; Figure 2 A schematic diagram of the installation process provided for the first embodiment of the multi-system application operation method of the present application; Figure 3 A schematic diagram of an uninstallation process provided in Embodiment 1 of the multi-system application running method of the present application; Figure 4 A schematic diagram of the multi-system application launch process provided in Embodiment 2 of the present application; Figure 5 A schematic diagram of a multi-system application exit process provided in Embodiment 2 of the present application; Figure 6 A schematic diagram of a multi-system application switching foreground process provided in Embodiment 2 of the present application; Figure 7A schematic diagram of a background process of switching applications in multiple systems provided in Embodiment 2 of the present application; Figure 8 A compatible application control architecture diagram provided for the multi-system application operation method of this application; Fig. 9 This is a schematic diagram of the module structure of the application running device of multiple systems in an embodiment of the present application; Fig.10 Schematic diagram of the device structure of the hardware operating environment involved in the multi-system application running method in the embodiment of the present application. DETAILED DESCRIPTION
[0021] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.
[0022] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0023] In this embodiment, for the convenience of description, the following description is made with the terminal as the execution subject.
[0024] Since it is difficult to run applications of other systems imperceptibly with conventional technologies, that is, users can often perceive that the application is running in another system or container when using it, for example, in the Anbox environment, the life cycle of Android applications may be more closely integrated with the window environment of the host machine. When users switch applications or close windows in the window environment of the host machine, the Android application in Anbox may not respond to these operations as expected, resulting in inconsistency or abnormality in the application state, resulting in differences in the life cycle management of applications inside and outside the container. This difference may cause problems such as abnormal application state, crash, or malfunction, reducing the user's imperceptible interactive experience.
[0025] The present application provides a solution, in the case of monitoring a first operation instruction of a proxy application for a native system, executing a first operation corresponding to the first operation instruction on the proxy application, by implementing monitoring of the operation on the proxy application, immediately responding and executing the corresponding first operation on the proxy application, and reacting to the user input in a timely manner; then, through the operation interface corresponding to the first operation instruction, calling a second operation instruction for a container application of the container system, converting the operation on the proxy application into an operation on the container application, and accurately transmitting the corresponding operation instructions between cross-system applications; after determining the second operation instruction for the container application, executing the second operation corresponding to the second operation instruction on the container application, so that the user can obtain a consistent operation experience in the two systems regardless of opening an application, switching interfaces or executing other functions, thereby ensuring the accuracy of the user's operation perception; finally, determining the execution result of the second operation, executing an operation corresponding to the execution result on the proxy application, such as updating the interface display, prompting the user that the operation is successful, etc., by displaying the operation result of the container application on the proxy application, the user's imperceptible interactive experience running on multiple systems is improved.
[0026] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, etc. The following takes an electronic terminal as an example to illustrate this embodiment and the following embodiments.
[0027] Based on this, the embodiment of the present application provides a multi-system application running method, referring to Figure 1 , Figure 1 This is a flowchart of the first embodiment of the multi-system application running method of the present application.
[0028] In this embodiment, the multi-system application running method includes steps S10 to S40: Step S10, when a first operation instruction for the proxy application of the native system is monitored, executing a first operation corresponding to the first operation instruction on the proxy application; It should be noted that the native system refers to the desktop operating system that is pre-installed on the terminal when it leaves the factory or installed by the user, such as the Openharmony system, Android system, etc., which can provide the basic functions and user interface of the terminal; the proxy application can be regarded as the medium between the native system and other system applications, which implements operations on other system applications by passing the operation instructions of the proxy application to other systems, and displays the operation results accordingly on the proxy application.
[0029] In addition, it should be noted that monitoring refers to the process in which a system or application continuously monitors a specific event or signal; the first operation instruction refers to a signal containing specific operation information, which is used to control or operate the proxy application.
[0030] Exemplarily, on the desktop of the Openharmony system, the main system of the current device, a user clicks on the desktop icon of an application, and the first operation instruction corresponding to the click is an application launch instruction. The device executes a launch operation on the application according to the application launch instruction to display the application content.
[0031] It is understandable that by monitoring system operations in real time, it is easier to respond to user operation instructions in a timely manner, reduce perception time, and improve the user's unconscious experience.
[0032] Step S20, calling a second operation instruction for a container application of the container system through an operation interface corresponding to the first operation instruction, wherein the container application matches the proxy application; It should be noted that the operation interface is a set of rules or functions provided by the system that allow communication and data exchange between different operating systems or software components. A call is an action in which a program or process requests another program or service to perform a specific task; the second operation instruction is equivalent to what the proxy application needs the container application to complete in order to complete the first operation instruction.
[0033] In addition, it should be noted that the container system refers to a software environment used to run different operating systems on a host machine (user terminal); and the container application refers to the application program running in the container system.
[0034] Exemplarily, a first operation instruction to launch application A (proxy application) is monitored, a launch operation is performed on application A, a preset application startup page is displayed, and a launch interface between the native system and the container system is found. Based on the matching information between application A and the container application in the configuration information, application B is determined to be the real operation application of application A in the container system, and a second operation instruction for application B is called, so that the subsequent container system can directly respond to the operation instruction.
[0035] It can be understood that the interaction between user operations and the container system is achieved through the calling of the operation interface and the conversion of instructions.
[0036] Step S30, executing a second operation corresponding to the second operation instruction on the container application; It should be noted that the second operation refers to an operation for the container application. The second operation instruction can be passed from the native system to the container system through the communication service module of the native system and the communication client module of the container system. The communication service module and the communication client module are components in the system responsible for receiving, processing and sending communication requests (such as data, instructions, etc.). They can monitor and respond to communication requests sent from external systems, and socket sockets can be used to achieve communication between the two. This implementation does not make specific limitations on this.
[0037] Exemplarily, the communication service module of the native system sends a pull-up instruction (second operation instruction) to the communication client module of the Docker container, performs a pull-up operation on application B (container application), and establishes an image interaction link with application A for displaying image information.
[0038] Step S40: determining the execution result of the second operation, and executing an operation corresponding to the execution result on the proxy application.
[0039] It should be noted that the execution result refers to the output or state change generated by the container application after executing the second operation, and the proxy application can perform subsequent processing or feedback according to the execution result.
[0040] Exemplarily, after the pull-up operation is performed on application B, the execution result is that application B displays the home page interface. According to the execution result, the home page interface of application B is displayed on application A.
[0041] Exemplarily, a pull-up operation is performed on application B. Due to environmental configuration reasons, application B fails to start. According to the execution result, an error message can be displayed on application A, or application A can be closed.
[0042] This embodiment provides a multi-system application running method, which can complete complex operations on applications in the container system through a proxy application, and directly manage the life cycle of the container application through the native system, thereby reducing the steps for users to interact with the system applications in the container; at the same time, the operation execution results are displayed on the proxy application of the desktop system, giving the user an intuitive result display and enhancing the user's interactive experience. Together, the two reduce the operation steps for users to operate other system applications on the desktop system, and realize the imperceptible running of other system applications on the native system.
[0043] In a feasible implementation manner, before step S10, the method further includes: Step S01, on the native system, decompress the obtained system application installation package to obtain the proxy application installation package and the container application installation package; It should be noted that the system application installation package refers to a compressed package that includes the installation environment and configuration files corresponding to the proxy application and container application; the proxy application installation package and the container application installation package are the parts obtained after decompressing the system application installation package, and both contain the files, configuration information, execution code and other resources required to run the application in a specific environment (such as the local end or container).
[0044] Exemplarily, if the Android application is compatible with running on the Openharmony system, the downloaded system application installation package may include the hap installation package (proxy application installation package) of the proxy application in the Openharmony system and the Android apk installation package (container application installation package).
[0045] It can be understood that by downloading and decompressing once, the proxy application installation package for the native system and the container application installation package for the container system are obtained, which reduces the number of steps for users to download the corresponding container application in the container and improves the user's non-perceptual interactive experience.
[0046] Step S02, sending information of the container application installation package to the container system, so that the container system installs the container application; It should be noted that the information of the container application installation package may refer to the container application installation package itself or the storage address of the container application installation package, so that the container system can obtain the installation package according to the received information and install the corresponding container application. This embodiment does not specifically limit this.
[0047] Exemplarily, after decompressing the container application installation package, the installation package is automatically copied to the shared directory of the native system and the container system. After the copy is completed, the container system is notified to install it. The container application installation package information is received on the container system, and the location of the installation package is read. After the installation is completed, the application configuration information in the container system is updated, and the matching relationship between the container application and the proxy application is added, and the installation result is returned to the native system.
[0048] Step S03: When the installation result of the container application is successful, the proxy application is installed on the native system.
[0049] For example, please refer to Figure 2 , Figure 2A schematic diagram of an installation process is provided. In step S101, after the user downloads the system application installation package, the electronic terminal executes step S102, that is, decompressing the system application installation package through the application management service of the native system, and copying the container application installation package to a shared directory. Step S103 refers to sending the installation instruction to the container system through the communication service module and the communication client module (communication module), executing step S104 to install the corresponding container application on the container system through the application management service of the container system, and step S105 returning the installation result to the native system through the communication module. If the container application is successfully installed, the corresponding step S106 is to install the corresponding proxy application on the native system through the application management service of the native system. After the installation is complete, step S107 is executed to monitor the application installation event of the native system through the application management service of the native system, and display the icon of the proxy application on the desktop.
[0050] For example, if the container application fails to be installed, an error message is displayed on the desktop, so that the user can troubleshoot and correct the error in a timely manner according to the error message.
[0051] In this implementation, the installation process of the proxy application and the container application can be automatically completed through a single download, which is equivalent to the user only needing to download on the native system to automatically complete the deployment and installation of the application in the container system, reducing the user's manual installation steps, thereby improving the user's non-perceptual interactive experience.
[0052] In a feasible implementation manner, the method further includes: Step A10, when a first uninstallation instruction for the native system is monitored, determining a package name of an uninstallation application corresponding to the first uninstallation instruction; It should be noted that the first uninstall instruction is a command issued by the user to remove the installed application in the system; the package name is a string used to uniquely identify the system application, and uninstalling the application package name can help the system accurately identify the application that needs to be uninstalled.
[0053] Step A20, when the uninstall application package name is the proxy application package name, uninstall the proxy application, and send a second uninstall instruction for the container application to the container system, so that the container system uninstalls the container application according to the second uninstall instruction.
[0054] It should be noted that the second uninstallation instruction is an uninstallation command for the container application determined according to the package name of the proxy application (ie, the uninstallation application), and is automatically generated by the system without user input.
[0055] Exemplarily, it is monitored that a user is uninstalling application A, which is a proxy application. Application A is uninstalled on the native system, and an uninstall instruction of the container application is sent to the container system. The uninstall instruction may include configuration information of the container application to be uninstalled.
[0056] For example, please refer to Figure 3 , Figure 3 A flowchart of uninstalling a proxy application is provided. In step A201, after a user issues a first uninstallation instruction for the proxy application, the electronic terminal executes step A202 to uninstall the proxy application in the native system. After completing step A203, the electronic terminal monitors the application uninstallation event of the native system through the application management service of the native system, and then executes step A204 to update the application information, such as deleting the relevant version information of the proxy application. Step A205 is to send a second uninstallation instruction for the corresponding container application to the container system through the communication service module and the communication client module (communication module), and then execute step A206 to uninstall the corresponding container application through the application management service of the container system, and step A207 returns the uninstallation result of the container application to the native system through the communication module. Finally, step A208 is executed to update the application information in the native system again according to the uninstallation result. For example, if the uninstallation is successful, the configuration information about the container application in the application information is deleted; if the uninstallation fails, the relevant information is retained, and when the user installs again, it is reminded that there is no need to repeat the installation, or the user is reminded whether to uninstall the container application again.
[0057] In this implementation, by synchronously uninstalling the proxy application and the container application, the number of steps for the user to enter the container system to perform the uninstall operation is reduced, the consistency of application management is improved, and thus the imperceptible interactive experience is enhanced.
[0058] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated later. On this basis, the operations corresponding to the first operation instruction and the second operation instruction are the same, and step S30 includes: Step E10: According to the second operation instruction, a container application is launched on the container system, and an image interaction link is established with the proxy application, wherein the image interaction link is used to synchronously display images between the native system and the container system.
[0059] It should be noted that launching refers to the process of starting or running an application. Image interaction link refers to the communication channel established between the proxy application and the container application for transmitting image data.
[0060] For example, please refer to Figure 4 , Figure 4A schematic diagram of an application launch process is provided. After executing a launch operation on a proxy application in a native system, executing step E101 through a launch interface of an application management module to call a container application launch and image interactive link establishment instruction (a second operation instruction) of a container system, executing step E102 through a communication service module of the native system and a communication client module (communication module) of the container system to send the second operation instruction for the container application to the container system, then executing step E103 on the container system through the application management service of the container system to launch the corresponding container application, and step E104 to establish an image interactive link between the corresponding container application and the proxy application, then executing step E105 through the communication module to return the execution result to the native system, and if the execution is successful, executing step E106 to directly display the image data of the container application on the proxy application of the native system.
[0061] In this embodiment, the accessibility of the container application is increased by directly launching the container application in the proxy application. At the same time, after the container application is launched, a link for image interaction with the proxy application is automatically established, and image data is sent to the proxy application, so that the user can operate the container application like a local application, thereby enhancing the user's non-perceptual interaction experience.
[0062] In a feasible implementation manner, step S30 includes: Step E20, when the first operation instruction is an exit instruction, exit the container application on the container system and terminate the image interactive link.
[0063] For example, please refer to Figure 5 , Figure 5 A schematic diagram of an application exit process is provided. After exiting a proxy application in a native system, step E201 is executed to call an application exit instruction and a link destruction instruction (a second operation instruction) for a container application through an exit interface, and step E202 is executed to send the second operation instruction to the container system through a communication service module of the native system and a communication client module (communication module) of the container system. Then, in the container system, step E203 is executed to exit the corresponding container application through an application management service of the container system, step E204 terminates an image data interactive link established when the container application is pulled up, and step E205 returns an execution result to the native system.
[0064] For example, if the container application fails to exit, it can remain in the background in the container system. When the user launches the container application again through the corresponding proxy application, it can be directly switched to the foreground to avoid repeated launching.
[0065] In this implementation, after the proxy application of the native system exits, the exit instruction of the container system is automatically called to execute the exit operation on the container application and destroy the interactive link, so that the user can exit the proxy application and the container application just like exiting the local application without performing additional exit operations, thereby improving the user's imperceptible experience when performing multi-system application exit operations.
[0066] In a feasible implementation manner, step S30 includes: Step E30, when the first operation instruction is a switch foreground instruction, the container application is displayed in the display area on the container system, and the image interactive link is restored.
[0067] For example, please refer to Figure 6 , Figure 6 A flowchart of switching the foreground is provided. After the proxy application is switched to the foreground in the native system, step E301 is executed to call the foreground switching instruction and the link start instruction (second operation instruction) for the container application by switching the foreground interface. Step E302 is executed to send the second operation instruction to the container system through the communication service module of the native system and the communication client module (communication module) of the container system. In the container system, step E303 is executed to switch the corresponding container application to the display area of the container system desktop through the application management service of the container system, and step E304 is performed to restore the image interaction link established before. Finally, step E305 is completed to return the execution result and the current container application interface to the native system through the communication module, and step E306 is completed to re-render the corresponding image screen in the proxy application.
[0068] In this implementation, by quickly switching the container application to the foreground and restarting the image interaction link, the container application can quickly become active from the background dormant state, and respond quickly to user operations or system commands, thereby improving the user's imperceptible interaction experience.
[0069] In a feasible implementation manner, step S30 includes: Step E40: When the first operation instruction is a background switching instruction, the container application is switched to a non-display area on the container system, and the image interaction link is disconnected.
[0070] For example, please refer to Figure 7 , Figure 7A process diagram of switching the background is provided. After the proxy application is switched to the background on the native system, the corresponding switching background interface is called, and step E401 is executed to find the instruction (second operation instruction) for switching to the background and suspending the image interaction link for the corresponding container application, and step E402 is executed through the communication module to send the second operation instruction to the container system. After the container system receives the second operation instruction, step E403 is executed to switch the corresponding container application to the container system background, that is, to the non-display area through the application management service of the container system, and step E404 is executed to disconnect the image interaction link established before, and the image communication between the proxy application and the container application is stopped. After completing step E405 and returning the execution result to the proxy application, it can be seen that the display interface of the current proxy application is switched to the native system background.
[0071] In this implementation, by switching the container application to the background and pausing the image interaction link, the user can easily pause and resume the container application without completely closing the application, thereby improving the user's imperceptible interaction experience.
[0072] For example, to help understand the implementation process of the multi-system application running method obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 8 , Figure 8 A compatible application control architecture diagram of a multi-system application running method is provided, specifically: Although the container system runs on the native system, the native system and the container system can be regarded as two independent operating systems that run independently. Multiple container systems and multiple proxy applications can run on the native system, and multiple container applications can also run on the container system.
[0073] Both the native system and the container system contain application management modules. The application layer interfaces on the two systems can help the two systems call operation instructions for each other's applications. The application management service can help both parties manage their own local applications.
[0074] The native system also has a communication service module, which corresponds to the communication client module of the container system. The registration services of these two modules provide the container system with a container system registration function, so that the native system knows that the container system has been added to the current system and can communicate. Both parties provide event monitoring services, which can quickly respond to user operations by timely transmitting the monitored operation instructions and / or execution results to the other party, thereby improving the user's imperceptible experience.
[0075] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the multi-system application operation method of the present application. More simple transformations based on this technical concept are all within the protection scope of the present application.
[0076] The present application also provides a multi-system application running device, please refer to Fig. 9 , the multi-system application running device includes: The proxy application operation module 10 is used to perform a first operation corresponding to the first operation instruction on the proxy application when a first operation instruction for the native system is monitored; An operation instruction calling module 20, configured to call a second operation instruction for a container application of the container system through an operation interface corresponding to the first operation instruction, wherein the container application matches the proxy application; The container application operation module 30 is used to perform a second operation corresponding to the second operation instruction on the container application; The result execution module 40 is used to determine the execution result of the second operation and execute an operation corresponding to the execution result on the proxy application.
[0077] The multi-system application running device provided in the embodiment of the present application adopts the multi-system application running method in the above embodiment, which can enhance the user's non-perceptual interactive experience running on multiple systems. Compared with the prior art, the beneficial effects of the multi-system application running device provided in the present application are the same as the beneficial effects of the multi-system application running method provided in the above embodiment, and other technical features in the multi-system application running device are the same as the features disclosed in the above embodiment method, which will not be repeated here.
[0078] An embodiment of the present application provides an electronic device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the multi-system application running method in the above-mentioned embodiment one.
[0079] Reference below Fig.10 , which shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present application. The electronic devices in the embodiments of the present application may include but are not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions: tablet computers), PMPs (Portable Media Players: portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig.10 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0080] like Fig.10 As shown, the electronic device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the electronic device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows an electronic device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.
[0081] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0082] The electronic device provided in the embodiment of the present application adopts the multi-system application running method in the above embodiment, which can enhance the user's imperceptible interactive experience running on multiple systems. Compared with the prior art, the beneficial effects of the electronic device provided in the present application are the same as the beneficial effects of the multi-system application running method provided in the above embodiment, and the other technical features in the electronic device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.
[0083] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.
[0084] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0085] An embodiment of the present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, the computer-readable program instructions being used to execute the multi-system application running method in the above-mentioned embodiment.
[0086] The computer-readable storage medium provided in the embodiment of the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM: Random Access Memory), a read-only memory (ROM: Read Only Memory), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency: Radio Frequency), etc., or any suitable combination of the above.
[0087] The computer-readable storage medium may be included in the electronic device, or may exist independently without being installed in the electronic device.
[0088] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by an electronic device, the electronic device: upon monitoring a first operation instruction of a proxy application for a native system, performs a first operation corresponding to the first operation instruction on the proxy application; calls a second operation instruction of a container application for a container system through an operation interface corresponding to the first operation instruction, wherein the container application matches the proxy application; performs a second operation corresponding to the second operation instruction on the container application; determines an execution result of the second operation, and performs an operation corresponding to the execution result on the proxy application.
[0089] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0090] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0091] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.
[0092] The readable storage medium provided in the embodiment of the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned multi-system application running method, and can enhance the user's non-perceptual interactive experience running on multiple systems. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the present application are the same as the beneficial effects of the multi-system application running method provided in the above-mentioned embodiment, and will not be elaborated here.
[0093] An embodiment of the present application also provides a computer program product, including a computer program, which implements the steps of the multi-system application running method as described above when executed by a processor.
[0094] The computer program product provided in the embodiment of the present application can enhance the user's non-perceptual interactive experience running on multiple systems. Compared with the prior art, the beneficial effects of the computer program product provided in the present application are the same as the beneficial effects of the multi-system application running method provided in the above embodiment, and will not be repeated here.
[0095] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. A multi-system application running method, characterized in that: The method includes: When a first operation instruction of a proxy application for a native system is monitored, performing a first operation corresponding to the first operation instruction on the proxy application; calling, through an operation interface corresponding to the first operation instruction, a second operation instruction for a container application of the container system, wherein the container application matches the proxy application; Execute a second operation corresponding to the second operation instruction on the container application; An execution result of the second operation is determined, and an operation corresponding to the execution result is performed on the proxy application.
2. The multi-system application running method according to claim 1, characterized in that: Before the step of performing a first operation corresponding to the first operation instruction on the proxy application when a first operation instruction for the native system is monitored, the method further includes: On the native system, decompress the obtained system application installation package to obtain the proxy application installation package and the container application installation package; Sending information of the container application installation package to the container system so that the container system installs the container application; When the installation result of the container application is successful, the proxy application is installed on the native system.
3. The multi-system application running method according to claim 1, characterized in that: The method further comprises: In a case where a first uninstallation instruction for the native system is monitored, determining a package name of an uninstallation application corresponding to the first uninstallation instruction; In the case where the package name of the uninstalled application is the package name of the proxy application, the proxy application is uninstalled, and a second uninstall instruction for the container application is sent to the container system, so that the container system uninstalls the container application according to the second uninstall instruction.
4. The multi-system application running method according to claim 1, characterized in that: The operations corresponding to the first operation instruction and the second operation instruction are the same, and the step of performing the second operation corresponding to the second operation instruction on the container application includes: In the case where the first operation instruction is a pull-up instruction, the container application is pulled up on the container system, and an image interaction link is established with the proxy application, wherein the image interaction link is used to synchronously display images between the native system and the container system.
5. The multi-system application running method according to claim 4, characterized in that: The step of performing the second operation corresponding to the second operation instruction on the container application includes: In the case where the first operation instruction is an exit instruction, the container application is exited on the container system, and the image interaction link is terminated.
6. The multi-system application running method according to claim 4, characterized in that: The step of performing the second operation corresponding to the second operation instruction on the container application includes: In the case where the first operation instruction is a switch foreground instruction, the container application is displayed in a display area on the container system, and the image interactive link is restored.
7. The multi-system application running method according to claim 4, characterized in that: The step of performing the second operation corresponding to the second operation instruction on the container application includes: In a case where the first operation instruction is a background switching instruction, the container application is switched to a non-display area on the container system, and the image interaction link is disconnected.
8. An electronic device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the multi-system application running method according to any one of claims 1 to 7.
9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the multi-system application running method according to any one of claims 1 to 7 are implemented.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the multi-system application running method according to any one of claims 1 to 7 are implemented.
Citation Information
Patent Citations
Multi-system application management method and mobile terminal
CN106897152A
Request processing method and device, electronic equipment and storage medium
CN111078367A
Touch input method and system, electronic equipment and storage medium
CN117631939A
Application calling method and electronic equipment
CN118585294A
