WO2021254280A1

WO2021254280A1 - Disk mounting method and device, storage medium, and electronic device

Info

Publication number: WO2021254280A1
Application number: PCT/CN2021/099815
Authority: WO
Inventors: 冯茂
Original assignee: 中兴通讯股份有限公司
Priority date: 2020-06-15
Filing date: 2021-06-11
Publication date: 2021-12-23
Also published as: CN113806007A

Abstract

A disk mounting method and device. The method comprises: detecting startup of an application, and separating, from an application master disk of the application, an application disk corresponding to a virtual machine (S202); and mounting the application disk and a private data disk of the application to the virtual machine, wherein the virtual machine is configured to recognize the application in the application disk and to load the application to a system, and the private data disk is configured to store data of the application (S204).

Description

Disk mounting method, device, storage medium and electronic device

Cross-references to related applications

This application is based on a Chinese patent application with an application number of 202010546757.6 and an application date of June 15, 2020, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated by reference into this application.

Technical field

The embodiments of the present application relate to the field of communications, and in particular, to a disk mounting method, device, storage medium, and electronic device.

Background technique

At present, in order to achieve unified management of set-top boxes, reduce terminal set-top box performance requirements and operating costs, and solve many problems such as the difference in video experience between new and old set-top boxes, cloud-based set-top boxes are one of the development directions. That is, the thin client direction, the application and implementation are all Completed in the cloud, the client just sends the corresponding command, and the feedback operation interface is obtained from the cloud.

How to effectively reduce the resource allocation of Android virtual machines has become a key issue in the cloudized Android field. In the traditional way of external disks, because applications cannot be shared on other Android devices, users are required to log in to the designated virtual machine device, which cannot guarantee load balance and improve the utilization of the device; at the same time, larger disks are allocated to users In the case of space, since it cannot be reused, it will also cause a waste of resource space.

Summary of the invention

The embodiments of the present application provide a disk mounting method, device, storage medium, and electronic device, to at least solve some situations in the art that the clouded Android virtual machine needs to be expanded due to insufficient memory, and excessive memory space is allocated, and users try to play Or the problem of resource waste caused by long-term non-use of the application.

According to an embodiment of the present application, a method for mounting a disk is provided, which includes: detecting application startup, and deriving an application disk corresponding to a virtual machine based on the application master disk of the application; and combining the application disk and the application disk The private data disk is mounted to the virtual machine, wherein the virtual machine is configured to recognize the application in the application disk and load the application into the system, and the private data disk is configured to Store the data of the application.

According to another embodiment of the present application, there is provided a disk mounting method applied to a virtual machine, including: identifying an application in an application disk; loading the application into the system, wherein the application disk is a server detection When the application starts, it is derived from the application master disk and mounted to the virtual machine. At the same time, the server mounts the private data disk of the application to the virtual machine, and the private data disk Is configured to store data of the application.

According to another embodiment of the present application, there is provided a disk mounting device, which includes: a differential module configured to detect application startup, and differentiate an application disk corresponding to a virtual machine according to the application master disk of the application; and the mounting module , Configured to mount the application disk and the private data disk of the application to the virtual machine, wherein the virtual machine is configured to identify the application in the application disk, and to The application is loaded into the system, and the private data disk is configured to store data of the application.

According to another embodiment of the present application, there is provided a disk mounting device applied to a virtual machine, including: an identification module configured to identify an application in an application disk; a first loading module configured to load the application Loaded into the system, where the application disk is derived from the application master disk when the server detects that the application is started and mounted to the virtual machine. At the same time, the server saves the private data disk of the application Mounted to the virtual machine, the private data disk is configured to store data of the application.

According to another embodiment of the present application, there is also provided a computer-readable storage medium having a computer program stored in the computer-readable storage medium, wherein the computer program is configured to execute any of the above methods when running Steps in the embodiment.

According to another embodiment of the present application, there is also provided an electronic device, including a memory and a processor, the memory is stored with a computer program, and the processor is configured to run the computer program to execute any of the above Steps in the method embodiment.

Description of the drawings

FIG. 1 is a block diagram of the hardware structure of a mobile terminal of a disk mounting method according to an embodiment of the present application;

Fig. 2 is a first flowchart of a disk mounting method according to an embodiment of the present application;

Fig. 3 is a second flowchart of a disk mounting method according to an embodiment of the present application;

Figure 4 is a flowchart of a personalized disk creation according to an embodiment of the present application;

Figure 5 is a flowchart of a personalized disk mounting according to an embodiment of the present application;

Figure 6 is a flowchart of a personalized disk upgrade according to an embodiment of the present application;

Fig. 7 is a first structural block diagram of a disk mounting device according to an embodiment of the present application;

Fig. 8 is a second structural block diagram of a disk mounting device according to an embodiment of the present application.

detailed description

Hereinafter, the embodiments of the present application will be described in detail with reference to the drawings and in conjunction with the embodiments.

It should be noted that the terms "first" and "second" in the description and claims of the application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence.

The method embodiments provided in the embodiments of the present application may be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, FIG. 1 is a block diagram of the hardware structure of the mobile terminal of the disk mounting method according to the embodiment of the present application. As shown in FIG. 1, the mobile terminal may include one or more (only shown in FIG. A) A processor 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the above-mentioned mobile terminal may also include a communication function The transmission device 106 and the input and output device 108. Those of ordinary skill in the art can understand that the structure shown in FIG. 1 is only for illustration, and does not limit the structure of the above-mentioned mobile terminal. For example, the mobile terminal may also include more or fewer components than shown in FIG. 1, or have a different configuration from that shown in FIG.

The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer programs corresponding to the disk mounting method in the embodiment of the present application. The processor 102 executes the computer programs stored in the memory 104 by running Various functional applications and data processing, that is, to achieve the above methods. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely provided with respect to the processor 102, and these remote memories may be connected to the mobile terminal through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 106 is used to receive or send data via a network. The above-mentioned specific examples of the network may include a wireless network provided by a communication provider of a mobile terminal. In an example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC for short), which can be connected to other network devices through a base station to communicate with the Internet. In an example, the transmission device 106 may be a radio frequency (Radio Frequency, referred to as RF) module, which is used to communicate with the Internet in a wireless manner.

The virtual machine corresponding to the virtual Android system is stored in the cloud server, and the end user is more connected to the server through the remote connection protocol FreeRDP/Spice, etc., similar to the Windows remote desktop connection, connecting to the corresponding virtual machine, and The corresponding screen is transmitted back to the terminal. For unified management, the virtual machine of the native Android system basically maintains one copy, that is, the same content is copied into multiple copies for use after different users log in. Generally, in order to speed up the login speed and time, The corresponding virtual machines have been started in advance and entered the Android environment to wait for the user to log in.

Because different users log in to the Android system that has been started, the private data generated by each user can only be stored in the virtual machine. When the virtual machine is used by other users, only the previous user's use environment can be seen , The disk corresponding to the virtual machine is not completely separated from the private environment and data of each user, which is inconvenient for the unified management of VSTB. Therefore, there is a demand for VSTB user private data, that is, the public disk corresponding to the virtual machine is as complete as possible with the user data. Separately, the public disk corresponding to the virtual machine can be the same for all users, and user data needs to be stored in other disks or network storage paths.

In the Android system, the user's installed application package is placed in the /data/app directory, and the user's private data is generally stored in the /data/data/ and built-in /sdcard directories. In some cases in this field, the application is installed in an external sdcard or disk, but the application installation package is placed in the external sdcard or disk. The application data and application installation information still need to be saved in the android system, so the application in the external disk It cannot be used by other virtual machines and cannot be shared with other android devices.

In response to the above problems, this embodiment provides a disk mounting method running on the above-mentioned mobile terminal or network architecture. FIG. 2 is a flowchart of the disk mounting method according to an embodiment of the present application, as shown in FIG. 2. , The process includes the following steps:

Step S202: Detect the application startup, and obtain the application disk corresponding to the virtual machine according to the application master disk of the application. Specifically, when the user opens the application, the application disk corresponding to the virtual machine is derived according to the application master disk difference;

Step S204: Mount the application disk and the private data disk of the application to the virtual machine, where the virtual machine is configured to identify the application in the application disk and load the application into the system, and the private data disk is configured as storage Application data.

Through the above steps S202 to S204, when the application is started, the application is installed on the application disk and the user private data disk respectively; when the disk is mounted, different virtual machine devices can identify the application and user data in the disk without installation. Normal use can solve the problem of resource waste caused by cloudized Android virtual machines due to insufficient memory in some situations in this field, and excessive allocation of memory space and user trial play or long-term non-use of applications. This eliminates the need for users to manually install applications. Mount the disk to use the applications in the disk. The disk can be applied to different virtual machines without considering the remaining space of the virtual machine.

In some embodiments, before mounting the application disk and the private data disk of the application to the virtual machine, determine whether there is a private data disk of the application; if there is a private data disk of the application, obtain the private data disk of the application; if not There is a private data disk for the application, and a private data disk for the application is created.

In some embodiments, after mounting the application disk and the private data disk in the virtual machine, the integrity of the application installation file in the application disk is verified to ensure that the application installation file in the application disk is complete and valid.

In some embodiments, after the application disk and the private data disk are mounted to the virtual machine, the incremental upgrade file of the application pushed by the virtual machine is received; the application of the virtual machine in the non-running state according to the incremental upgrade file The disk is upgraded, and/or, after the application in the running virtual machine is exited, the application disk of the virtual machine is upgraded if the application has not been upgraded. When the application installation package or application resource package has a push update, when the user opens the application, the application or application resource package is updated to the application disk; after the application update is completed, the update resource is pushed to the application master disk; after the application master disk update is completed, push Applying the master disk to the user disk upgrade of each virtual machine can reduce the operation of users and operation and maintenance personnel, and at the same time reduce the occupation of network resources by the virtual machine.

In this embodiment, after the user installs the application, the installation data can be divided into two parts: the installation package data and the user's private application data. Among them, the installation package data is theoretically universal to all users and can be shared among different users; private application data belongs to the user's private data, mainly including the user's account information, progress information, and chat information.

If the application can be used like a disk, that is, mounted and used, then the operation and maintenance personnel do not need to consider the virtual machine memory problem.

In the personalized disk mounting solution of this embodiment, the application installation package can be installed on the application disk, and the existing application data loading process of the android system can be modified at the same time to directly read the data in the user data disk; during the running of the game, The user data produced can be directly stored in the private data disk; also for the inconvenience of disk application update, a personalized disk upgrade update plan is proposed.

The personalized disk mounting program can be divided into three parts: personalized disk production, personalized disk mounting, and personalized disk upgrade.

Personalized disk production mainly implements the installation of application installation package data and private application data in the application master disk and application data disk respectively, and then pushes them to users for use. The existing android system does not support the installation of an application on a disk or an sdcard. In this embodiment, it is necessary to modify the native installation process of the android system and re-specify the installation path of the application.

The personalized disk mounting mainly realizes the identification of the application in the disk and the normal operation of the application. At the same time, the private data generated by the application is saved in the application data disk. Specifically, when the user opens the application, the corresponding virtual machine is derived based on the application master disk difference The application disk; and then create a private application data disk based on the original application data disk. Finally, mount the created disk to the corresponding virtual machine; the virtual machine scans and recognizes the application in the disk, and loads the application into the system. The virtual machine opens the application, loads the data in the private data disk, and reads the user's historical data. At the same time, the private data generated by the application is written in the user's private data disk; when the user exits the application, the loading information of the application is cleared, and the disk is unloaded at the same time.

The personalized disk upgrade part mainly realizes the functions of application upgrade and application resource package upgrade, and solves the problem of manual upgrade by all users or unified upgrade by operation and maintenance personnel. Specifically, when the application installation package or application resource package has a push update, the user opens the application When the time, update the application or application resource package to the application disk; after the application update is completed, push the update resource to the application master disk; after the application master disk update is completed, push the application master disk to each virtual machine user.

In this embodiment, the application disk can be mounted and used immediately, eliminating the need for application installation steps. Since the application does not need to be installed on the virtual machine, the memory space occupied by the virtual machine itself can be reduced; the application master disk can be shared between the virtual machines, further different users use the space occupied by the application; the application is no longer used, no need to uninstall, directly delete the corresponding Just apply the disk, which is convenient for operation and maintenance management. At the same time, the personalized disk upgrade program can reduce the operations of users and operation and maintenance personnel, and at the same time reduce the occupation of network resources by virtual machines.

According to another embodiment of the present application, a disk mounting method is also provided, which is applied to a virtual machine. FIG. 3 is a flowchart of the disk mounting method according to an embodiment of the present application. As shown in FIG. 3, the process is shown in FIG. Including the following steps:

Step S302: Identify the application in the application disk;

In some embodiments, the above step S302 may specifically include: scanning the path where the application disk is mounted, and identifying the installation file of the application under the path.

In step S304, the application is loaded into the system, where the application disk is derived from the application master disk when the server detects that the application is started and mounted to the virtual machine. At the same time, the server mounts the private data disk of the application to the virtual machine. In the virtual machine, the private data disk is configured to store data of the application.

In some embodiments, the above step S304 may specifically include: parsing the installation file to obtain application information, and updating the application information to the system; modifying the file permissions in the private data disk according to the application information; broadcasting application installation in the system Success message.

In one embodiment, the virtual machine opens the application, loads the data in the private data disk, reads the user's historical data, and at the same time writes the private data generated by the application in the user's private data disk.

Through the above steps S302 to S304, when the application is started, the application is installed on the application disk and the user private data disk respectively; when the disk is mounted, different virtual machine devices can identify the application and user data in the disk without installation. Normal use can solve the problem of resource waste caused by cloudized Android virtual machines due to insufficient memory in some situations in this field, and excessive allocation of memory space and user trial play or long-term non-use of applications. This eliminates the need for users to manually install applications. Mount the disk to use the applications in the disk. The disk can be applied to different virtual machines without considering the remaining space of the virtual machine.

In some embodiments, after the application is loaded into the system, the application is opened and the data in the private data disk is loaded. In one embodiment, when the system creates the application process, the path of the application data is modified to the private data disk To load the data in the private data disk; read the historical data of the application and write the data generated by the application to the private data disk. In one embodiment, when the application requests the application data, the application The application data path of is modified to the path of the private data disk to write the data generated by the application into the private data disk.

In some embodiments, after the application is loaded into the system, when the application exits, the loading information of the application is cleared, and the application disk and the private data disk are unloaded at the same time.

In some embodiments, when the installation file is updated, the installation path of the application is updated, and the installation file is updated to the application disk; the updated application disk and the application master disk are compared to generate an incremental upgrade file; and the server is pushed The incremental upgrade file of the application, where the incremental upgrade file is used by the server to upgrade the application disk of the virtual machine in the non-running state, and/or, after the application in the virtual machine in the running state is exited, the application If the upgrade is not completed, upgrade the application disk of the virtual machine.

The following uses an application as a game as an example to further illustrate this embodiment.

In this embodiment, when the android application is installed on the external disk, the application can be installed on the application disk and the user private data disk respectively; when the disk is mounted, different android virtual machine devices can identify the application and user data in the disk. It can be used normally without installation. In turn, it solves the problems of resource waste caused by the existing cloudized Android virtual machine due to insufficient memory and need to expand due to insufficient memory, excessive allocation of memory space, and resource waste caused by users trying to play or not using applications for a long time. There is no need for users to manually install the application, and the application in the disk can be used by mounting the disk. The disk can be applied to different Android virtual machines, and there is no need to care about the remaining space of the Android virtual machine, including:

Step 1. When the new push application goes online, first create the application master disk of the game application and the original private application data disk through the personalized disk creation function. Figure 4 is a flowchart of the personalized disk creation according to an embodiment of the application. As shown in Figure 4, it includes:

Step S401, push the application online;

Step S402, judge whether the application is installed in the disk, if the judgment result is no, execute step S403, otherwise, execute step S404;

Step S403, install the application;

Step S404, mount the game master disk and the private data disk, that is, respectively mount the empty application master disk and the private application data disk to the designated private mount directory of the virtual machine;

In step S405, when the application is installed, the installation path of the application in the system installd is modified, and the application installation package and application data are respectively installed in different disks;

Step S406: After the application is successfully installed, MD5 information of the file in the application master disk is generated and stored in the server to provide integrity verification for subsequent mounting.

Step 2. When the application is opened, the personalized disk mounting function is triggered, and then the application is used normally. Fig. 5 is a flowchart of a personalized disk mounting according to an embodiment of the present application, as shown in Fig. 5, including:

Step S501, when the application is opened, trigger the virtual machine to mount the corresponding application disk and private data disk, where the application disk is differentiated from the application master disk; firstly, determine whether the user has a private data disk for the application, if not, then Create a new private data disk for the user based on the original application data disk.

Step S502, if the application disk and the private data disk are mounted normally, MD5 value verification is performed on the files in the application disk;

In step S503, the virtual machine scans and recognizes the application in the application disk, and loads the application into the system. Specifically include the following steps:

Step S5031, calling PMS (PackageManagerService) to scan the path where the disk is mounted, and then identifying the application installation file under the path;

Step S5032, call PackageParse to parse the application installation file, and update the application information to the system;

Step S5033, according to the parsed application installation file, change the file permissions (including user groups, user permissions, etc.) in the private data disk;

Step S5034: Send a broadcast message that the application is successfully installed in the system.

In step S504, the virtual machine starts the application, loads the data in the private data disk, and reads the historical data of the user. At the same time, write the private data generated by the application in the user's private data disk, including:

In step S5041, in the application process created by the android system through zygote, the path of the application data is modified to the path of the private application data disk, so as to ensure the normal loading of the game.

In step S5042, when the application requests application data, the application data path of the application is dynamically changed to the path of the user's private data disk, so that the user data can be directly stored in the disk for reading and writing.

In step S505, when the user exits the application, the loading information of the application is cleared, and the disk is unmounted at the same time.

Step 3. Virtual machine pushes application upgrades and application resource package upgrades. FIG. 6 is a flowchart of a personalized disk upgrade according to an embodiment of the present application, as shown in FIG. 6, including:

Step S601, the application is updated online, and the game application disk is updated. Specifically, when the user opens the application and the application installation package or application resource package has a push update, the installation path of the application or application resource package is updated, and the application is updated to the game disk , Upload the incremental upgrade package file to the server.

In step S602, the updated game disk is compared with the original game master disk, and an incremental upgrade file package is generated.

Step S603: It is judged whether the virtual machine is running the game application, if the judgment result is yes, step S604 is executed, otherwise, step S606 is executed;

Step S604, when the application exits, push the upgrade;

Step S605, it is judged whether the application disk has been upgraded, if the judgment result is no, step S606 is executed, otherwise, step S607 is executed;

Step S606, upgrade the application disk;

Step S607, the upgrade is completed.

The server queries the running status of the current application in each android virtual machine. If it is not running, it pushes the incremental upgrade package to the application disk of the corresponding virtual machine for upgrade, and reports the upgrade information to the server; otherwise, when waiting for the application to exit, Determine whether the application has been upgraded, if not, continue to push the upgrade.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is Better implementation. Based on this understanding, the technical solution of this application essentially or the part that contributes to the technology in the field can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) ) Includes several instructions to make a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) execute the method described in each embodiment of the present application.

In this embodiment, a disk mounting device is also provided, which is used to implement the above-mentioned embodiment and other implementation manners, and those that have been described will not be repeated. As used below, the term "module" can implement a combination of software and/or hardware with predetermined functions. Although the device described in the following embodiments can be implemented by software, implementation by hardware or a combination of software and hardware is also possible and conceived.

Fig. 7 is a structural block diagram 1 of a disk mounting device according to an embodiment of the present application. As shown in Fig. 7, the device includes:

The difference module 72 is configured to detect the startup of an application, and differentiate the application disk corresponding to the virtual machine according to the application master disk of the application;

The mounting module 74 is configured to mount the application disk and the private data disk of the application to the virtual machine, where the virtual machine is configured to recognize the application in the application disk and load the application into the system. The data disk is configured to store application data.

In some embodiments, the device further includes:

The judgment module is configured to judge whether there is a private data disk of the application;

The obtaining module is configured to obtain the private data disk of the application when the judgment result is yes;

The creation module is configured to create a private data disk of the application when the judgment result is no.

In some embodiments, the device further includes:

The verification module is configured to verify the integrity of the application installation file in the application disk.

In some embodiments, the device further includes:

The receiving module is configured to receive incremental upgrade files of the application pushed by the virtual machine;

The upgrade module is configured to upgrade the application disk of the virtual machine in the non-running state according to the incremental upgrade file, and/or, after exiting the application in the virtual machine in the running state, the application has not been upgraded Next, upgrade the application disk of the virtual machine.

It should be noted that each of the above-mentioned modules can be implemented by software or hardware. For the latter, it can be implemented in the following way, but not limited to this: the above-mentioned modules are all located in the same processor; or, the above-mentioned modules are in any combination The forms are located in different processors.

Fig. 8 is a second structural block diagram of a disk mounting device according to an embodiment of the present application. As shown in Fig. 8, the device includes:

The identification module 82 is configured to identify applications in the application disk;

The first loading module 84 is configured to load the application into the system, where the application disk is differentiated according to the application mother disk when the server detects that the application is started, and is mounted to the virtual machine. At the same time, the server keeps the application private The data disk is mounted to the virtual machine, and the private data disk is configured to store application data.

In some embodiments, the aforementioned identification module 82 includes:

The scanning sub-module is configured to scan the path where the application disk is mounted;

The identification sub-module is configured to identify the installation file of the application under the path.

In some embodiments, the aforementioned first loading module 84 includes:

The parsing sub-module is configured to parse the installation file, obtain application information, and update the application information to the system;

The modification sub-module is configured to modify the file permissions in the private data disk according to the application information;

The broadcast sub-module is configured to broadcast a message of successful application installation in the system.

In some embodiments, the device further includes:

The second loading module is configured to open the application and load the data in the private data disk;

The writing module is configured to read historical data of the application and write the data generated by the application into the private data disk.

In some embodiments, the aforementioned second loading module is further configured to modify the path of the application data to the path of the private data disk when the system creates the application process, so as to load the data in the private data disk;

The above-mentioned writing module is also configured to modify the application data path of the application to the path of the private data disk when the application requests application data, so as to write the data generated by the application into the private data disk.

In some embodiments, the device further includes:

The unloading module is configured to clear the loading information of the application when the application exits, and unload the application disk and the private data disk at the same time.

In some embodiments, the device further includes:

The update module is configured to update the installation path of the application when the installation file is updated, and update the installation file to the application disk;

The generation module is configured to compare the updated application disk with the application master disk, and generate an incremental upgrade file;

The push module is configured to push the incremental upgrade file of the application to the server, where the incremental upgrade file is used by the server to upgrade the application disk of the virtual machine in the non-running state, and/or to the running state After the application in the virtual machine exits, the application disk of the virtual machine is upgraded if the application has not been upgraded.

The embodiment of the present application also provides a computer-readable storage medium in which a computer program is stored, wherein the computer program is configured to execute the steps in any one of the foregoing method embodiments when running.

In one embodiment, the above-mentioned computer-readable storage medium may include, but is not limited to: U disk, read-only memory (Read-Only Memory, ROM for short), Random Access Memory (RAM for short), mobile Various media that can store computer programs, such as hard disks, magnetic disks, or optical disks.

An embodiment of the present application also provides an electronic device, including a memory and a processor, the memory is stored with a computer program, and the processor is configured to run the computer program to execute the steps in any of the foregoing method embodiments.

In one embodiment, the above-mentioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the aforementioned processor, and the input-output device is connected to the aforementioned processor.

Through this application, when the application is started, the application is installed in the application disk and the user private data disk; when the disk is mounted, different virtual machine devices can recognize the application and user data in the disk, and can be used normally without installation. It can solve the problem of resource wasted due to insufficient memory of clouded Android virtual machines in some situations in this field, and the allocation of excessive memory space and the user's trial play or long-term non-use of the application lead to waste of resources, so that the user does not need to manually install the application and mount the disk That is, the applications in the disk can be used, and the disk can be applied to different virtual machines without considering the remaining space of the virtual machine.

For specific examples in this embodiment, reference may be made to the examples described in the above-mentioned embodiments and some implementation manners, and this embodiment will not be repeated here.

Obviously, those skilled in the art should understand that the above-mentioned modules or steps of this application can be implemented by a general computing device, and they can be concentrated on a single computing device or distributed in a network composed of multiple computing devices. Above, they can be implemented with program codes executable by a computing device, so that they can be stored in a storage device for execution by the computing device, and in some cases, they can be executed in a different order than shown here. Or the described steps, or fabricate them into individual integrated circuit modules respectively, or fabricate multiple modules or steps of them into a single integrated circuit module to achieve. In this way, this application is not limited to any specific hardware and software combination.

The above are only some embodiments of the application, and are not used to limit the application. For those skilled in the art, the application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the principles of this application shall be included in the protection scope of this application.

Claims

A disk mounting method, including:

Detect application startup, and differentiate the application disk corresponding to the virtual machine according to the application master disk of the application;

Mount the application disk and the private data disk of the application to the virtual machine, wherein the virtual machine is configured to identify the application in the application disk and load the application into the system In the above, the private data disk is configured to store data of the application.
The method according to claim 1, wherein, before mounting the application disk and the private data disk of the application to the virtual machine, the method further comprises:

Determine whether there is a private data disk of the application;

In the case where the judgment result is yes, obtain the private data disk of the application;

In the case that the judgment result is negative, a private data disk of the application is created.
The method according to claim 1 or 2, wherein after mounting the application disk and the private data disk to the virtual machine, the method further comprises:

Receiving the incremental upgrade file of the application pushed by the virtual machine;

Upgrade the application disk of the virtual machine in the non-running state according to the incremental upgrade file, and/or, after exiting the application in the virtual machine in the running state, if the application has not been upgraded To upgrade the application disk of the virtual machine.
A disk mounting method, applied to a virtual machine, includes:

Identify the application in the application disk;

Load the application into the system, where the application disk is the server that detects the application startup, differentiates it based on the application master disk and mounts it in the virtual machine, and at the same time, the server saves the private application of the application. The data disk is mounted to the virtual machine, and the private data disk is configured to store data of the application.
The method of claim 4, wherein identifying the application in the application disk comprises:

Scanning the path where the application disk is mounted;

Identify the installation file of the application under the path.
The method of claim 5, wherein loading the application into the system comprises:

Parse the installation file to obtain application information, and update the application information to the system;

Modify the file permissions in the private data disk according to the application information;

Broadcasting a message that the application installation is successful in the system.
The method according to claim 4, wherein, after the application is loaded into the system, the method further comprises:

Open the application, and load the data in the private data disk;

Read the historical data of the application, and write the data generated by the application into the private data disk.
The method according to claim 7, wherein:

Loading the data in the private data disk includes: when the system creates an application process, modifying the path of the application data to the path of the private data disk to load the data in the private data disk;

Writing the data generated by the application into the private data disk includes: when the application requests the application data, modifying the application data path of the application to the path of the private data disk to change the The data generated by the application is written into the private data disk.
The method according to any one of claims 4 to 8, wherein, after the application is loaded into the system, the method further comprises:

When the application exits, the loading information of the application is cleared, and the application disk is unloaded from the private data disk at the same time.
The method according to any one of claims 4 to 8, wherein the method further comprises:

When the installation file is updated, the installation path of the application is updated, and the installation file is updated to the application disk;

Compare the updated application disk with the application master disk, and generate an incremental upgrade file;

Push the incremental upgrade file of the application to the server, where the incremental upgrade file is used by the server to upgrade the application disk of the virtual machine in the non-running state, and/or to the running state After the application in the virtual machine exits, if the application has not been upgraded, the application disk of the virtual machine is upgraded.
A disk mounting device includes:

The difference module is configured to detect the startup of the application, and differentiate the application disk corresponding to the virtual machine according to the application master disk of the application;

The mounting module is configured to mount the application disk and the private data disk of the application to the virtual machine, wherein the virtual machine is configured to identify the application in the application disk, and The application is loaded into the system, and the private data disk is configured to store data of the application.
A disk mounting device applied to a virtual machine, including:

The identification module is configured to identify the application in the application disk;

The first loading module is configured to load the application into the system, wherein the application disk is differentiated based on the application master disk and mounted to the virtual machine when the server detects that the application is started, At the same time, the server mounts the private data disk of the application to the virtual machine, and the private data disk is configured to store data of the application.
A computer-readable storage medium having a computer program stored in the computer-readable storage medium, wherein the computer program is configured to execute the method described in any one of claims 1 to 3 when running, or Perform the method described in any one of claims 4 to 10.
An electronic device comprising a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the one described in any one of claims 1 to 3 Method, or implement the method described in any one of claims 4 to 10.