WO2018090528A1 - Method and system for mirror image package preparation and application operation - Google Patents

Abstract

A method and system for mirror image package preparation and application operation. The application operation method comprises: acquiring, before installing a target application, a launch operation package and a launch mirror image package of the target application (601); upon launching of the target application, establishing a local buffer manager, establishing a first channel between the local buffer manager and the launch mirror image package, and establishing a second channel between the local buffer manager and a server (602); creating a first virtual memory unit locally, and establishing a third channel between the local buffer manager and the first virtual memory unit (603); the local buffer manager receiving, via the third channel, a request previously received by the first virtual memory unit from the target application (604); and if the request is a read request, the local buffer manager acquiring, via the first channel, first data from the launch mirror image package for the read request, and/or acquiring, via the second channel, the first data from an original mirror image package on the server for the read request (605). The method of the present invention saves time for a first-time launch of a target application, and reduces memory space occupied by the target application on a terminal.

Description

Image package making, application running method and system Technical field

The present invention relates to the field of information processing technologies, and in particular, to a method and system for fabricating an original image package, a method and system for fabricating an application boot image package, and an application operation method and system.

Background technique

With the continuous development of computer technology, the functions of various applications are constantly being enriched and improved, such as the various functions displayed by the toolbar of photo editing software (Photoshop, PS), the increase of various game software levels, and the like; In order to enhance the visual effect, some applications render all the images in the application into three-dimensional (3D) effects, such as 3D games, and virtual reality applications require more and more computing resources. For example, artificial intelligence, mathematical calculations, etc., the requirements of the central processing unit (CPU) processing capability, graphics computing requirements for the processing power of the graphics processor, pictures, character models, map models, large-scale database storage space This requires that the functionality of the application is increasingly complex and the data packets are getting larger.

Since the user needs to download the application complete software installation package and data package from the server when using the application for the first time, and need to install the application software installation package on the terminal to start the application, this results in downloading the package and installing the software installation. The process of packing often takes a long time. In order to solve this problem, some companies currently manage executable programs and resource data separately according to the characteristics of their own applications, and the resource data such as pictures, models, built-in videos, etc., generally account for the majority of the program packet size. The quotas are split, modularized, and the necessary executables and resource module data are packaged to create a micro client.

In the process of splitting the application, it is often necessary to (1) analyze the program to run the executable file that needs to be loaded, and the resource file that the executable file depends on. (2) Analyze the dependencies between multiple executable files, and the resources that each executable file depends on at the same time, for example, which resources are triggered by a function interface, or program calls. (3) Because some large programs rely on many third-party libraries, or system function components, such as 3D graphics engine, data transfer library, image video compression/decompression library, local operating system hardware--CPU, graphics card, memory, Network management interfaces, etc. These components are generally very complex in internal structure, and require a lot of background knowledge to understand the relevant details; the process of parsing third-party libraries requires a lot of learning work to understand the ways and features of accessing resources at runtime. However, often due to incomplete understanding of the relevant mechanisms, it will lead to a large number of compatibility and performance problems, which is time-consuming and labor-intensive; it can be seen that the above-mentioned splitting of the application is complicated, and a large amount of additional labor and time costs are introduced.

Summary of the invention

The technical problem to be solved by the embodiments of the present invention is to provide an application running method, an application original image package manufacturing method, and an application startup image package manufacturing method, to solve the problem in the prior art for making a micro client. Splitting, resulting in low efficiency and high cost.

Correspondingly, the embodiment of the present invention further provides a corresponding system for the foregoing method, which is: an application running system, an application original image package making system, and an application startup image package making system, to ensure the above method. Implementation and application.

The invention discloses a method for running an application, which comprises: acquiring a startup running package and a startup image package of the target application in advance when the target application is not installed, wherein the startup running package is used to start the target application. The boot image package includes the The startup data of the target application; when the target application is started by the startup package, establishing a local cache manager, establishing a first path of the local cache manager and the startup image package, and establishing a local cache manager and a second path of the server; locally creating a first virtual storage unit, establishing a third path of the local cache manager and the first virtual storage unit; the local cache manager receiving a request through the third path, The request is received by the first virtual storage unit from the target application; when the request is a read request, the local cache manager obtains the boot image package from the boot image package through the first path Reading the first data of the request; and/or, the local cache manager obtaining, by the second path, the first data of the read request from the original image package of the server; wherein the original image package Including startup data and operational data of the target application; feeding the first data to the target application through the third path, so that the target should Run with.

Correspondingly, the embodiment of the present invention further discloses an application running system, which specifically includes: a data packet obtaining module, configured to acquire a startup running package and a startup image package of the target application in advance when the target application is not installed, where The startup running package is configured to start the target application, where the startup image package includes startup data of the target application, and a local cache manager establishment module, configured to establish, when the target application is started by using the startup operation package, a local cache manager, establishing a first path of the local cache manager and the boot image package, and establishing a second path of the local cache manager and the server; the first virtual storage unit establishing module, locally creating the first virtual storage a unit, establishing a third path of the local cache manager and the first virtual storage unit; a first data request receiving module, configured to invoke the local cache manager, to receive a data request through the third path, The data request is received by the first virtual storage unit from the target application; a data acquisition module is configured to be When the data request is a read request, the local cache manager is invoked to obtain first data of the read request from the boot image package through the first path; and/or, the local cache manager is invoked Obtaining, by the second path, first data of the read request from an original image package of the server; wherein the original image package includes startup data and operation data of the target application; and a data feedback module, And transmitting, by the third path, the first data to the target application to enable the target application to run.

The invention discloses a method for manufacturing an original image package, which comprises: establishing a data packet creation manager and creating an empty original image package, and establishing an eighth path of the data packet creation manager and the original image package; Creating a second virtual storage unit locally, establishing a ninth path of the second virtual storage unit and the data packet creation manager; the data packet creation manager receiving a data write request by using the ninth path, where The data write request is obtained by the second virtual storage unit from the process; the data packet creation manager writes the third data corresponding to the data write request into the original image package through the eighth path, where The third data is data included in the original data of the target application.

Correspondingly, the present invention also discloses an application original image package creation system, which specifically includes: a data packet creation manager establishing module, configured to establish a data packet creation manager, create an empty original image package, and establish the data package. An eighth path of the production manager and the original image package; a second virtual storage unit establishing module, configured to locally create a second virtual storage unit, and establish the second virtual storage unit and the data packet creation manager a ninth path; a second data request receiving module, configured to invoke the data packet creation manager to receive a data write request through the ninth path, wherein the data write request is the second virtual storage unit slave process Obtaining; the original image packet data writing module is configured to invoke the data packet creation manager, and write the third data corresponding to the data write request into the original image package by using an eighth path, where The third data is the data contained in the original data of the target application.

The invention discloses a method for manufacturing an application startup image package, which comprises: establishing a local manager when starting a target application, and establishing a tenth path of the local manager and the original image package; establishing an empty startup image package, and establishing The local manager and the eleventh path of the boot image package; locally creating a third virtual storage unit, establishing a twelfth path of the local manager and the third virtual storage unit; the local manager passes The twelfth path receives a data request, the data request is received by the third virtual storage unit from the target application; when the request is a read request, the local manager passes the tenth path From the stated Acquiring fourth data corresponding to the read request in the original image package; and writing the fourth data into the startup image package by using the eleventh path; stopping the installation when the target application stops running The fourth data is written to the boot image package.

Correspondingly, the present invention also discloses an application startup image package creation system, which specifically includes: a local manager establishment module, configured to establish a local manager when starting a target application, and establish a local manager and an original image package. Ten paths; starting an image package creation module, establishing an empty boot image package, and establishing an eleventh path of the local manager and the boot image package; and a third virtual storage unit establishing module for locally creating a third a virtual storage unit, establishing a twelfth path of the local manager and the third virtual storage unit; a third data request receiving module, configured to invoke the local manager to receive a data request through the twelfth path The data request is received by the third virtual storage unit from the target application; the boot image packet data writing module is configured to invoke the local manager when the request is a read request, by using the The tenth path acquires fourth data corresponding to the read request from the original image package; and the fourth number is performed by the eleventh path The boot image is written in a packet; when the target application stops running, stopping the fourth write data packet to the boot image.

Compared with the prior art, the embodiments of the invention include the following advantages:

In the embodiment of the present invention, when the original image package is created, only the data packet creation manager, the second virtual storage unit, and the empty original image package, and the path between the three are established; that is, when the write request is obtained, Copy all the data in the original data packet of the target application to the original image package through the corresponding path; similarly, when creating the boot image package, you only need to create an empty boot image package, local manager and third. a virtual storage unit; and establishing a path between the boot image package, the original image package, the third virtual storage unit, and the local manager, and then copying the startup data of the target application from the original image package to the boot through the corresponding path In the image package, when the original image package and the startup image package are created, the analysis of the runtime environment that the application depends on and the modular splitting work are eliminated, which greatly reduces the labor cost and the time cost.

Further, after the original image package, the startup image package, and the startup package are created, the embodiment of the present invention acquires the startup operation package and the startup image package of the target application when the user first makes the target application; and starts the application by using the startup operation package. The program establishes a local cache manager, and establishes a path between the local cache manager, the boot image package, and the original image package; establishes a first virtual storage unit, and its path to the local cache manager; locally caches When the manager receives the read request, the data corresponding to the read request may be obtained from the boot image package and/or the original image package of the server through the corresponding path, and fed back to the target application to make the target The application runs; thus, in the case that only the startup running package and the startup image package are obtained, the data of the target application is obtained from the original image package of the startup image package and/or the server during the running of the target application, Ensure the normal operation of the target application. In addition, since the amount of startup data of the target application included in the startup image package is much smaller than the original data amount of the target application, the time for the user to start the target application is greatly saved, and the user experience is enhanced; In the process of running, in general, all functions will not be used, and only part of the program data will be downloaded, so that the space occupied by the user's local device storage system will be greatly reduced.

DRAWINGS

1 is a structural block diagram of an embodiment of an application original image package creation system of the present invention;

2A is a flow chart showing the steps of an embodiment of the application original image package creation system of the present invention;

2B is a structural block diagram of another embodiment of an application original image package creation system of the present invention;

3 is a structural block diagram of an embodiment of an application boot image package creation system of the present invention;

4A is a flow chart showing the steps of an embodiment of an application startup image package manufacturing method according to the present invention;

4B is a structural block diagram of another embodiment of an application startup image package creation system of the present invention;

5A is a structural block diagram of an embodiment of an application operating system of the present invention;

5B is a structural block diagram of another embodiment of an application operating system of the present invention;

6A is a flow chart showing the steps of an embodiment of an application operation method of the present invention;

6B is a structural block diagram of another embodiment of an application operating system of the present invention;

7 is a flow chart showing the steps of another embodiment of an application operation method of the present invention;

8 is a block diagram of a computing device for performing a mirrored package creation, application running method in accordance with the present invention;

9 is a storage unit for holding or carrying program code implementing the image package creation and application execution method according to the present invention.

detailed description

The present invention will be further described in detail with reference to the accompanying drawings and specific embodiments.

The embodiments of the present invention can be applied to various operating systems of a terminal, where the terminal includes a personal computer (PC) and a mobile terminal, and the operating system includes a PC-side operating system such as Windows, Linux, Unix, and virtual machine emulation. The system and the like also include an operating system of the mobile terminal such as Android, IOS, and the like.

The target application in the embodiment of the present invention refers to a software installation package and a large application file, such as a 3D game, a PS, and the like; wherein the target application may be a PC-side application or a mobile terminal application. (Application, APP); The method and system of the embodiment of the present invention will be described below by taking a mobile terminal as an example.

An embodiment of the present invention provides an application running system, after acquiring a startup running package and a startup image package corresponding to a target application, when the target application is running, from the original image package in the startup image package and/or the server, The data required by the target application is obtained to enable the target application to run normally. Therefore, the startup image package and the original image package of the target application are required to be pre-made to ensure the normal operation of the target application. Therefore, the embodiment of the present invention further provides a The original image package creation method and system are used to create an original image package of the target application, and an application startup image package creation method and system for creating a startup image package of the target application. The above three systems and corresponding methods will be described in detail below.

Referring to FIG. 1 , a block diagram of an embodiment of an application original image package creation system of the present invention is shown, which may include: a data packet creation manager establishing module 101, a second virtual storage unit establishing module 102, and a second data request. a receiving module 103 and an original image packet data writing module 104, wherein

The packet creation manager establishing module 101 is configured to establish a packet creation manager and create an empty original image package, and establish an eighth path of the data packet creation manager and the original image package.

The second virtual storage unit establishing module 102 is configured to locally create a second virtual storage unit, and establish a ninth path of the second virtual storage unit and the data packet creation manager.

The second data request receiving module 103 is configured to invoke the data packet creation manager to receive a data write request through the ninth path, wherein the data write request is obtained by the second virtual storage unit from a process.

The original image package data writing module 104 is configured to invoke the data packet creation manager to write the third data corresponding to the data write request into the original image package through the eighth path, where the third The data is the data contained in the original data of the target application.

In the embodiment of the present invention, the second virtual storage unit establishing module 102 is deployed in the mobile terminal, and the data packet creation manager establishing module 101, the second data request receiving module 103, and the original image packet data writing module 104 may all be deployed on the mobile terminal. The terminal may also be deployed on the server, where the original data packet of the target application and the target application is installed in the mobile terminal, and the target application can be normally operated in the mobile terminal, for example, the mobile terminal installs the game A. APP; in addition, one provided by the embodiment of the present invention The application original image package creation system has a corresponding control panel in the mobile terminal. After the control panel is started, the corresponding process can be started by controlling the corresponding control module to control the above four modules. The control module acquires configuration information of the target application in the mobile terminal, where the configuration information includes: content description information such as a target application name, an original data packet size, and the like; Applying the original image package creation process, after the process is started, the data packet creation manager establishing module 101 establishes a data packet creation manager; the control module sends the acquired configuration information to the data packet creation manager, and the data packet creation management According to the configuration information, an empty original image package is created, and the capacity of the original image package is greater than the capacity of the original data packet of the target application. For example, the original data packet of game A has a capacity of 4 GB, and the original image package of game A is The capacity can be 4.2GB; the created empty original image package includes: an empty mirror data area, an empty checksum database data area, and a formatted configuration data area; the packet creation manager will then configure the information. Add to the configuration data area; then establish a relationship between the original image package and the packet creation manager The eighth pathway.

Then, the control module starts the storage unit creation process, creates a second virtual storage unit in the mobile terminal by the second virtual storage unit establishing module 102, and the second virtual storage unit establishing module 102 creates the second virtual storage unit and the data package. The ninth path between the managers, and through the system's Application Programming Interface (API), notifies the operating system to identify the created virtual storage unit. Specifically, the system enumerates various file systems such as --ext2. 3,4\yaffs\jffs\fat\ntfs..., verify the storage unit device one by one, and try to take over; after identifying the virtual storage unit device, create a mount point such as /apps/app_id for the second virtual storage unit. The second virtual storage unit can be accessed.

After the eighth path and the ninth path are established, the control module starts a data copy process to copy the data in the original data packet of the target application, including the resource file and the execution file, into the empty mirror data area of the original image package; Specifically, after the copy process is started, sending a data write request to the second virtual storage unit, and the second virtual storage unit sends the data write request to the data packet creation manager through the ninth path, the second data The request receiving module 103 calls the data packet creation manager to receive the data write request; the original image package data writing module 104 invokes the data packet creation manager to write the data according to the acquired data write request. The corresponding third data is requested to be written into the empty mirror data area of the original image package; until the original data of the target application is completely copied into the mirror data area of the original image package.

In the embodiment of the present invention, the storage unit has a function of storing data and reading and writing data. In different operating systems and different terminals, the representation form of the storage unit is also different; the type of the storage device corresponding to the storage unit includes A variety of, such as tape, disk, NOR-flash (non-type flash chip), NAND-flash (data storage type flash chip), CD ROM (disc read-only memory), DVD ROM (digital video disk), BD ROM (only Read CD), SSD (Solid State Drive), etc., not listed here.

The production of the original image package is completed. If the data packet creation manager establishing module 101, the second data request receiving module 103, and the original image packet data writing module 104 are deployed on the server, the original data of the target application in the mobile terminal is completed. The packet is copied to the original image package of the server; if the packet creation manager establishing module 101, the second data request receiving module 103, and the original image packet data writing module 104 are all deployed on the mobile terminal, the package may be The completed original image package is uploaded to the server to facilitate different users to use when running the target application.

In another embodiment of the present invention, a method corresponding to the application of the original image package creation system is described. Referring specifically to FIGS. 2A and 2B, FIG. 2A illustrates an application original image package creation system of the present invention. Steps of the steps of the embodiment; FIG. 2B is a block diagram showing the structure of another embodiment of the application original image package making system of the present invention.

The data packet creation manager M2 in the embodiment of the present invention may include: a second application manager M2A and a second storage stack M2B, wherein the second application manager M2A may include a second configuration manager M20; the second storage stack M2B The method may include: a second storage unit simulator M21, a second incremental data manager M22, and a second mirror cache manager M23. The manager and the storage stack included in the processor M2 are taken as an example, and the method of making the original image package is described in detail.

In the embodiment of the present invention, the original image package includes a mirrored data area, a configuration data area, and a checksum database data area; wherein the data area is implemented in multiple manners, and one implementation manner is to create a large file for the original image package. Alternatively, the original image package is divided into a separate storage partition, and the file, or the independent storage partition, is divided into three areas to implement a mirror data area, a configuration data area, and a checksum database data area, so as to implement related data storage. The other implementation manner is that the mirrored data area, the configuration data area, and the checksum database data area in the original image package are respectively divided into corresponding independent common files, and the corresponding original image package includes: an image file, Configuration files and checksum database files.

Step 201: Establish a packet creation manager and create an empty original image package, and establish an eighth path of the data packet creation manager and the original image package.

Since the capacity of the original image package and the configuration information of the data are determined according to the original data packet of the target application; therefore, in the mobile terminal in which the target application is installed, the second control panel M24 is activated according to the operation of the user, and the second control is performed. The module M25 scans the original data packet M26 of the target application of the mobile terminal by acquiring the configuration information acquisition process, and acquires the configuration information of the original data packet M26 of the target application, where the configuration information includes: the name of the target application, and the original data packet size. Etc. Content description information. At the same time, the second control module M25 can also start the application original image package creation process, and call the data package creation manager establishing module 101 to establish a data packet creation manager M2. Specifically, the data packet creation manager establishing module 101 starts the second application management. M2A, and establishing a second storage unit simulator M21, a second incremental data manager M22, and a second mirror cache manager M23; at this time, the second configuration manager M20 in the second application manager M2A is also started . After the establishment of the packet creation manager M2, the second application manager M2A acquires the configuration information corresponding to the target application, and saves the acquired configuration information in the second configuration manager M20; and then creates an empty space according to the configuration information. The original image package M27, the capacity of the original image package M27 is larger than the capacity of the original data packet M26; wherein, the empty original image package M27 includes: an empty mirror data area, an empty checksum database data area, and a set The empty configuration data area of the good format; the second configuration manager M20 is called, and the configuration information corresponding to the target application is added to the empty configuration data area of the format. Then, an eighth path S8 between the packet creation manager M2 and the original image package M27 is established.

The process of specifically establishing the eighth path S8 is as follows: (1) The second image cache manager M23 opens the mirror data area in the original image package M27, and initializes related content description information in the configuration data area, wherein the second image cache management The M23 is for managing the original image package M27; (2) the second incremental data manager M22 creates a file stream instance, establishes a data path with the second image cache manager M23, and can pass the second image cache. The manager M23 opens the mirror data area in the original image package M27; (3) the second storage unit simulator M21 opens the file stream instance created by the second incremental data manager M22, and establishes a second incremental data manager M22 The data path between the second incremental data manager M22 forwards the request of the second storage unit simulator M21 directly to the second mirrored cache manager M23.

Step 202: Create a second virtual storage unit locally, and establish a ninth path of the second virtual storage unit and the data packet creation manager.

After the eighth path S8 of the packet creation manager M2 and the original image package M27 is established, the second control module M25 starts the storage unit creation process, and the second virtual storage unit establishing module 102 is in the mobile terminal. Creating a second virtual storage unit M28, and creating a ninth path S9 of the second virtual storage unit M28 and the second storage unit simulator M21; then the operating system of the mobile terminal creates a mount point for the second virtual storage unit, The process in the operating system can access the second virtual storage unit M28 through the mount point. Further, in the operating system, there is a second virtual storage unit IO simulator M29 corresponding to the second virtual storage unit for identifying a read/write operation for the second virtual storage unit M28.

Step 203: The data packet creation manager receives a data write request by using the ninth path, where the data write request is obtained by the second virtual storage unit from a process.

After the eighth path S8 and the ninth path S9 are established, the second control module M25 starts the data copy process to copy the data in the original data packet M26 of the target application to the empty mirror data area of the original image package M27. Specifically, after the copy process is started, the copy process sends a data write request to the second virtual storage unit M28, and after receiving the data write request, the second virtual storage unit IO simulator M29 passes through the ninth path S9. The data write request is forwarded to the second storage unit simulator M21, and the second data request receiving module 103 invokes the second storage unit simulator M21 to acquire the write request through the ninth path S9.

Step 204: The data packet creation manager writes the third data corresponding to the data write request into the original image package by using an eighth path.

The second storage unit simulator M21 forwards the write request to the second incremental data manager M22; the original mirrored packet data writing module 104 invokes the second incremental data manager M22, according to the created file stream instance, The mirrored data area in the original image package M27 is opened by the second image cache manager M23, and the third data corresponding to the write request is written into the mirror data area until all the original data of the target application is copied to the In the original image package M27, wherein the third data is data included in the original data of the target application.

In addition, after copying the original data of the target application to the original image package, the second virtual storage unit establishing module 102 invokes the operating system API to close the second virtual storage unit M28, and unmounts the mount point, and disconnects the second virtual storage. a ninth path S9 between the unit M28 and the packet creation manager M2; the packet creation manager establishing module 101 disconnects the packet creation manager M2 from the eighth path S8 of the original image package M27; and generates a target application The corresponding startup package starts the runner; wherein the startup package includes the most basic file of the startup target application, and when the terminal runs the corresponding application by using the startup package, the startup package completes the target application. During the installation process, the basic component installation and configuration and the interaction between the target application and the terminal. At the same time, the second control module M25 starts the configuration process, so that the packet creation manager establishing module 101 calls the second application manager M2A to scan the mirror data area in the original image package block by block, and generates each data block in the mirror data area. Corresponding checksum, wherein the size of the data block can be 8KB, 16KB, 64KB consecutively, and the checksum of each data block is saved into the checksum database data area; then, the checksum database data area is scanned, The value of the Message-Digest Algorithm 5 (MD5) of the database is generated, and the MD5 value and the feature information of each data block when the original image package is created, such as the download priority, are updated to the configuration data area.

The above-mentioned application original image package creation system and method can be used to produce original image packages of various large applications to reduce application development costs, such as 3D games, PS, etc.; for example, 3D games, A method for making an original image package of the 3D game by using the original image package creation system, specifically: the 3D game is already installed on the mobile terminal, and the original data package supporting the 3D game operation is stored in the mobile terminal. The original image package of the 3D game can be created on the mobile terminal, and the eighth path S8 and the ninth path S9 are established; then all the data in the original data packet of the 3D game, including resources, is passed through the eighth path S8. The file and the execution file are copied to the mirror data area of the original image package of the 3D game; the data of the mirror data area in the original image package contains data for supporting the startup and normal operation of the 3D game; after the data copy is completed, The 3D game generates a corresponding App Launcher; the user can launch the 3D game through the APP Launcher.

In the embodiment of the present invention, when the original image package is created, only the data packet creation manager and the second virtual storage unit are created, and the original original image package is created; and the path between the three is obtained; that is, when the write request is obtained Copy all the data in the original data packet of the target application to the original image package through the corresponding path; without analyzing the original binary code and data of the target application, the original data of the target application can be copied. To the original image package; greatly reducing the target application requires modular splitting Development time and labor costs of work.

After the startup package and the original image package of the target application are created, if the startup package of the target application is not stored in the mobile terminal, the server may download from the server; if the startup package of the target application is stored in the mobile terminal, the The startup package is obtained locally, and then the target application is started by the startup package. During the startup of the target application, the data required by the target application can be obtained from the original image package, because the data required for the target application is started. The original image package is stored in the server, which causes the user to wait for a long time when the target application is started for the first time. To reduce the waiting time when the user starts the target application for the first time, the startup image package corresponding to the target application can be pre-created. The startup image package includes startup data of the target application; when the mobile terminal obtains the startup image package while acquiring the startup operation package, when the target application is started, the corresponding data can be directly obtained locally, which greatly reduces the target. The time the application was launched.

Referring to FIG. 3, a block diagram of an embodiment of an application boot image package creation system of the present invention is shown, which may include: a local manager setup module 301, a boot image package creation module 302, and a third virtual storage unit setup module 303. a third data request receiving module 304 and a boot image packet data writing module 305; wherein

The local manager establishing module 301 is configured to establish a local manager when starting the target application, and establish a tenth path of the local manager and the original image package.

The boot image package establishing module 302 is configured to establish an empty boot image package, and establish an eleventh path of the local manager and the boot image package.

The third virtual storage unit establishing module 303 is configured to locally create a third virtual storage unit, and establish a twelfth path of the local manager and the third virtual storage unit.

The third data request receiving module 304 is configured to invoke the local manager to receive a data request through the twelfth path, where the data request is received by the third virtual storage unit from the target application.

The startup image package data writing module 305 is configured to: when the request is a read request, invoke the local manager, and obtain, by using the tenth path, the fourth data corresponding to the read request from the original image package. And writing the fourth data into the boot image package through the eleventh path; stopping writing the fourth data to the boot image package when the target application stops running.

In the embodiment of the present invention, the local manager establishment module 301, the startup image package creation module 302, the third virtual storage unit establishment module 303, the third data request receiving module 304, and the startup image package data writing module 305 are all deployed in the mobile terminal. on.

In the embodiment of the present invention, the target application may be started by starting the running package, or the target application may be started through the control panel, wherein the control panel and the startup running package both correspond to different control modules; when the target application starts, the control module obtains from the startup running package. The corresponding identifier of the target application, such as the APP ID, and the packet creation process is started, so that the local manager establishing module 301 establishes a local manager, and then the control module sends the identifier of the target application to the local manager; if the original image of the target application is stored In the local cache, the local manager looks up the original image package corresponding to the identity of the target application, and then establishes the tenth path between the local manager and the original image package; if the original image package of the target application is stored in the server, The local manager establishes a tenth path with the original image package corresponding to the identifier of the target application in the server according to the identifier of the target application; and then the startup image package creation module 302 creates an empty startup image package according to the obtained configuration information; the startup image package Capacity, equal to the capacity of the original image package; The checksum database data area and configuration information corresponding to the identifier of the target application are copied to the boot image package; the created empty boot image package further includes a mirror data area and an incremental data area. The boot image package creation module 302 then establishes an eleventh path between the local manager and the boot image package. The third virtual storage unit establishing module 303 locally creates a third virtual storage unit, establishing a twelfth path of the local manager and the third virtual storage unit; and the third data request receiving module 304 calls the local manager Receiving a data request through the twelfth path; due to the role of the third virtual storage unit establishing module 303 and the third data request receiving module 304, and the second virtual storage list The functions of the meta-establishment module 102 and the second data request receiving module 103 are the same, and are not described herein again. After the local manager obtains the data request, when the data request is a read request, the startup image package data writing module calls the local manager, and obtains the first image package from the original image package through the tenth path. Reading the fourth data corresponding to the request; and writing the fourth data into the startup image package through the eleventh path; meanwhile, the local manager returns the acquired fourth data through the twelfth path Give the target application.

Stop writing the fourth data into the boot image package when the target application stops running. In the embodiment of the present invention, when the target application stops running, it may be that the target application is just started, or may be a short time after the target application is started, to ensure that the data in the boot image package only occupies a small portion of the original image package. Preferably, the data of the startup image package is less than 5% of the data of the original image package, 30 minutes after the target application is started; thereby ensuring that the time for the mobile terminal to obtain the startup image package is short. For example, if the game A is played for 20 minutes in the mobile terminal, the sixth level of the game A can be played, and the startup image package of the game A includes the data of the game A from the start to the sixth level. For example, if the boot image package stores 3% of the original image package; if Game A's original image package is 4.3 GB, the game A's boot image package has a capacity of 4.3 GB, and the boot image package stores 4.3 GB. 3%; that is, the storage space that the boot image package actually occupies is only 4.3 GB * 3% = 0.129 GB. Preferably, the boot image package can be further processed by the compression algorithm, so that the boot image package is smaller.

In another embodiment of the present invention, a method for fabricating an application startup image package corresponding to an application startup image package creation system is described. Referring specifically to FIGS. 4A and 4B, FIG. 4A illustrates the present invention. A flow chart of steps of an embodiment of an application startup image package creation method; and FIG. 4B is a structural block diagram of another embodiment of an application startup image package creation system of the present invention.

The local manager M4 in the embodiment of the present invention may include: a third application manager M4A and a third storage stack M4B, wherein the third application manager may include a third configuration manager M40; the third storage stack M4B may include: The third storage unit simulator M41, the third incremental data manager M42, the third mirror cache manager M43, and the third splitter M44; the following is an example of the manager and the storage stack included in the local manager M4; The method of starting the image package is described in detail.

In the embodiment of the present invention, the boot image package includes a mirror data area, a configuration data area, an incremental data area, and a checksum database data area; wherein the data area is implemented in multiple manners, and one implementation manner is to start the image package. Create a large file, or divide a separate storage partition; divide four areas in the file or storage partition to implement the mirrored data area, the configuration data area, the incremental data area, and the checksum database data area to implement related data. The storage function; another implementation manner is that the mirror data area, the incremental data area, the configuration data area, and the checksum database data area in the startup image package are respectively divided into corresponding independent common files, and the corresponding startup is started. Image packages include: image files, delta files, configuration files, and checksum database files.

Step 401: When the target application is started, the local manager is established, and the tenth path of the local manager and the original image package is established.

Step 402: Establish an empty boot image package, and establish an eleventh path of the local manager and the boot image package.

In the embodiment of the present invention, when the startup package P1 of the target application is started, or the third control panel M45 starts the startup program P1 corresponding to the target application, the local manager establishment module 301 establishes the local manager M4. Specifically, the third control module M46 starts. a third application manager M4A, and a third storage unit simulator M41, a third incremental data manager M42, a third mirror cache manager M43, and a third splitter M44; wherein, in the third application manager M4A The third configuration manager M40 is also started. If the original image package M47 of the target application is stored locally, the tenth path of the local manager M4 and the local original image package M47 is established. If the original image package M47 of the target application is stored in the server, the tenth path of the local manager M4 and the original image package M47 on the server is established; preferably, the server SE includes the configuration server SE1 and the data server SE2, and the local manager M4 is established. The tenth path with the original image package M47 on the server includes: establishing a path S101 of the third application manager M4A and the configuration server SE1 to acquire configuration information and a checksum database data area; and establishing a third splitter M44 and the data server Path S102 of SE2 to obtain data of the mirrored data area in the original image package. The third application manager M4A calls the third configuration manager M40 to raw data The configuration information and the checksum database data area in the package M47 are added to the empty boot image package. In addition, the boot image package includes an empty incremental data area and an empty mirror data area.

Then, the boot image package establishing module 302 establishes an eleventh path between the local manager M4 and the boot image package M48, that is, establishes the local manager M4 and the path S111 of the mirrored data area in the boot image package, specifically, (1) The three-mirror cache manager M43 opens the mirrored data area in the boot image package M48 and initializes the content description information. (2) The third shunt M44 will initialize a file stream instance, establish a path of the third shunt M44 and the mirrored data area in the original image package M47, to obtain the data of the mirrored data area in the original image package M47, and the third The mirrored data area instance of the boot image package M48 opened by the mirror cache manager M43 establishes a data path. (3) The third incremental data manager M42 will create a file stream instance, establish a path with the file stream instance in the third splitter M44, and open the incremental data area in the boot image package M48 to check the initial dirty data distribution. Create a description in memory. (4) The third storage unit simulator M41 opens the file stream instance created by the third incremental data manager M42.

Step 403: Create a third virtual storage unit locally, and establish a twelfth path of the local manager and the third virtual storage unit.

After the eleventh path and the tenth path are established, the third control module M46 starts the storage unit creation process, creates a third virtual storage unit M49 in the mobile terminal through the third virtual storage unit establishing module 303, and creates the The third virtual storage unit M49 and the twelfth path S12 of the third storage unit simulator M41; then the operating system of the mobile terminal creates a mount point for the third virtual storage unit M49, and the process in the operating system can pass the mount point Accessing the third virtual storage unit. Further, in the operating system, there is a third virtual storage unit IO simulator M410 corresponding to the third virtual storage unit M49 for identifying a read/write operation for the third virtual storage unit M49.

Step 404: The local manager receives a data request by using the twelfth path, where the data request is received by the third virtual storage unit from the target application.

During the running of the target application, the third virtual storage unit M49 can be accessed to obtain the required data through the third virtual storage unit M49; after the third virtual storage unit IO simulator M410 obtains the request of the target application, the third The twelve path S12 forwards the request to the third storage unit simulator M41; the third data request receiving module 304 invokes the third storage unit simulator M41 to acquire the request through the twelfth path S12.

Step 405: When the request is a read request, the local manager acquires fourth data corresponding to the read request from the original image package by using the tenth path; and The fourth data is written into the boot image package; when the target application stops running, stopping writing the fourth data to the boot image package.

The third storage unit simulator M41 forwards the request to the third incremental data manager M42; when the third incremental data manager M42 determines that the request is a read request, starts image packet data writing The module 305 calls the third incremental data manager M42 to forward the read request to the third splitter M44 according to the created file stream instance, the third splitter M44 from the mirrored data area of the original image package M47 And acquiring the fourth data corresponding to the read request; after acquiring the fourth data, generating a corresponding checksum for the data block of the fourth data; and verifying the checksum of the data block corresponding to the fourth data, The fourth data is compared in a checksum of the corresponding data block in the checksum database data area; when the two match, the fourth data is saved in the boot image package, and the fourth data corresponds to the data block The two-bit identifier is set to the third state; when the two do not match, the fourth data is re-acquired from the original image package M47, and the checksum matching operation is repeated; if the checksum of the fourth data is not successfully matched, Can fourth data first The presence of boot image packet and the fourth data corresponding to the second identification data block to the fourth state; target application can be started next time, re-acquiring the image data from the original fourth packet. The second bit identifier is an identifier of a data block in the mirrored data area; the third state is an effective state of the data block in the mirrored data area; and the fourth state is the mirrored data area Medium data block Invalid state.

In addition, the third shunt M44 identifies the second bit corresponding to the data block as the fourth data of the third state by the file stream instance, and returns to the third incremental data manager M42, and the third incremental data manager M42 The fourth data is returned to the third storage unit simulator M41, and the third storage unit simulator M41 returns the fourth data to the target application through the twelfth path S12.

In addition, when establishing a path between the local manager M4 and the boot image package M48, the method further includes establishing a path S112 between the third incremental data manager M42 and the incremental data area in the boot image package M48, when the When the three-increment data manager M42 determines that the received request is a write request, it directly writes the data corresponding to the write request into the incremental data area of the boot image package M48.

After the target application runs for a period of time, when the operation is stopped, the fourth data is stopped from being written into the startup image package M48; at this time, the creation of the startup image package M48 is completed; in order to make more mobile terminals The startup image package M48 of the target application is obtained, and the created startup image package can be uploaded to the data server.

The application startup image package creation system and method provided above can be used to create a startup image package for 3D games, PS and other applications; since the startup image package is much smaller than the original image package, the user can reduce the use of the 3D game for the first time. Waiting time for PS; taking 3D game as an example, the method of starting the image package creation system by using the above application to create a startup image package of the 3D game, specifically: on the mobile terminal of the APP Launcher that has acquired the 3D game The 3D game is played by launching the APP Launcher; after the 3D game is started; the system will create a boot image package of the 3D game, and then establish the above tenth, eleventh and twelfth paths; the system will pass the tenth path The original image package obtains the data required by the 3D game; returns the 3D game through the twelfth path to ensure the normal operation of the 3D game; and then writes the data acquired from the original image package through the eleventh path. Start the image package; try to play for about 20 to 30 minutes, at this time, the 3D game has been started, and run to the first few levels; then close 3D At this time, the startup image package contains the startup data of the 3D game and the data of the first few levels; thus, when the APP starts next time, it can directly obtain the startup data and the resources of the first few levels from the local startup image package. The data, the time and content of the trial can be determined according to the size of the 3D game or the game mode. In addition, the time of the trial can be different for games of different types, such as real-time strategic games and character-playing games.

In the embodiment of the present invention, when the boot image package is created, only an empty boot image package and a local manager are created; and a path between the boot image package, the original image package, and the local manager is established, and then the corresponding path can be adopted. Copy the data from the original image package to the boot image package. Because the target application runs for a short time, the amount of data of the boot image package is much smaller than the data volume of the original image package. Therefore, the mobile terminal obtains the boot image for the first time. When you pack, the waiting time is short. Moreover, when the boot image package is created, the analysis of the runtime environment on which the application depends and the modular splitting work can be eliminated, which greatly reduces the labor cost and the time cost.

If the original image package and the startup image package of the target application are created by the same mobile terminal, the second control panel and the third control panel are the same control panel; if not created on the same mobile terminal, the second control panel and the third control panel The control panel is different.

Through the application of the original image package creation system, the original image package and the startup package of the target application can be created, and the image package creation system is started by the above application, and the startup image package of the target application can be created. Therefore, before the target application is started by starting the running package in the mobile terminal, the application running system provided by the embodiment of the present invention obtains the startup running package and the startup image package in advance; when the target application is running, the path is initiated through the established path. Obtain the data required for the target application to run in the image package and/or the original image package; the following describes an application runtime system.

Referring to FIG. 5A, a structural block diagram of an embodiment of an application running system of the present invention is shown. The system specifically includes: a data packet obtaining module 501, a local cache manager establishing module 502, and a first virtual storage unit establishing module 503. a first data request receiving module 504, a data obtaining module 505, and a data feedback module 506, wherein

a data packet obtaining module 501, configured to acquire, in advance, a startup running package and a startup mirror of the target application when the target application is not installed Like a package, wherein the startup package is used to start the target application, and the startup image package includes startup data of the target application.

The local cache manager establishing module 502 is configured to establish a local cache manager, establish a first path of the local cache manager and the boot image package, and establish a local cache when the target application is started by the startup run package. The second path of the manager and server.

The first virtual storage unit establishing module 503 is configured to locally create a first virtual storage unit, and establish a third path of the local cache manager and the first virtual storage unit.

The first data request receiving module 504 is configured to invoke the local cache manager to receive a data request through the third path, where the data request is received by the first virtual storage unit from the target application.

The data obtaining module 505 is configured to: when the data request is a read request, invoke the local cache manager to acquire, by using the first path, the first data of the read request from the startup image package; and Or calling the local cache manager to obtain first data of the read request from the original image package of the server by using the second path; wherein the original image package includes startup of the target application Data and operational data.

The data feedback module 506 is configured to feed back the first data to the target application through the third path to enable the target application to run.

In the embodiment of the present invention, the data packet obtaining module 501, the local cache manager establishing module 502, the first virtual storage unit establishing module 503, the first data request receiving module 504, the data obtaining module 505, and the data feedback module 506 are all deployed in the embodiment. On the mobile terminal, the application running system can be deployed on each of the different mobile terminals, that is, the target application can be run on each mobile terminal. If the mobile terminal that runs the target application is the same as the mobile terminal that creates the boot image package of the target application, the first path, the second path, and the third path in the embodiment of the present invention are respectively associated with the eleventh path. The tenth path and the twelfth path are the same path, and the first virtual storage unit and the third virtual storage unit are the same virtual storage unit; if the mobile terminal that starts the image package of the target application is different, the embodiment of the present invention The first path, the second path, and the third path are not in the same path as the eleventh, tenth, and twelfth paths, respectively, and the first virtual storage unit and the third virtual storage unit are not the same virtual storage unit. .

The packet obtaining module 501 may obtain the startup running package and the startup image package of the target application locally when the target application is not installed in advance; or may obtain the startup running package and the startup image package from the server, because the target application is started. Both the running package and the boot image package are relatively small, thus greatly saving the user's waiting time. After installing the startup package of the target application, the user can start the target application by starting the running package; the local cache manager establishing module 502 establishes a local cache manager after the target application is started; and then calls the local cache manager to find and And starting a boot image package corresponding to the boot package; establishing a first path of the local cache manager and the boot image package, and establishing a second path of the local cache manager and the server; and the first path and the second path After the establishment is completed, the first virtual storage unit establishing module 503 locally creates a first virtual storage unit, and establishes a third path of the local cache manager and the first virtual storage unit; the first data request receiving module 504 uses Retrieving the local cache manager, receiving a data request through the third path, the data request is received by the first virtual storage unit from the target application; where the local cache manager establishing module 502, first a virtual storage unit establishing module 503 and a first data request receiving module 504, respectively, respectively Establishing module processor 301, to establish a data request module 303 and the third receiving module 304 is the same function as a third virtual storage unit, are not repeated here. The data obtaining module 505, when the data request is a read request, invoking the local cache manager, by using the first path, acquiring first data of the read request from the startup image package; or calling the a local cache manager, by using the second path, acquiring first data of the read request from an original image package of the server; or acquiring the first data from a startup image package and an original image package; The feedback module 506 feeds back the first data to the target application through the third path to cause the target application to run.

In addition, when the target application is initially started, or when the target application is started, the local cache manager establishing module 502 establishes a local cache manager, and establishes the first path of the local cache manager and the boot image package. And establishing a second path of the local cache manager and the server; and the first virtual storage unit establishing module 503 locally creates the first virtual storage unit, establishing the local cache manager and the first virtual storage unit Three pathways.

Preferably, in another example of the present invention, the application running system further includes: a data writing module 507 and a data upgrading module 508; and referring to FIG. 5B, the structure of another application operating system embodiment of the present invention is shown. Block diagram; among them,

The data writing module 507 is configured to: when the request is a write request, the local cache manager writes the second data of the write request into the incremental data area by using the first path; The first bit of the second data corresponding data block is identified as the first state.

The data upgrade module 508 is configured to obtain a target application upgrade startup image package when the target application needs to be upgraded, where the upgrade startup image package includes partial update data of the target application; after the local cache manager is established, local cache management is established. And a sixth path of the upgrade boot image package, and a seventh path establishing a local cache manager and the server; the local data before acquiring the first data from the boot image package and/or the original image package The cache manager obtains first data of the read request from the upgrade boot image package through the sixth path; and/or, the local cache manager upgrades from the server through the seventh path Acquiring the first data of the read request in the original image package; wherein the upgrade original image package includes all update data of the target application.

The data obtaining module 505 is specifically configured to: when the local cache manager obtains the first data of the read request from the startup image package by using the first path, the local cache manager passes the a first path, obtaining the first data from the incremental data area, and/or acquiring the first data from the mirrored data area; wherein the boot image package includes an incremental data area and Mirror the data area.

In the embodiment of the present invention, the boot image package includes a mirror data area and an incremental data area, and the mirror data area is used to store original data of the target application. During the running of the target application, the data request sent to the first virtual storage unit may be a write request or a read request; the data write module 507 determines that the data request is a write request, in order not to destroy the storage in the boot image package. The original data of the application may be used to write the second data corresponding to the request into the incremental data area of the startup image package; and when the data block update is successful, the first bit identifier of the data block is updated to the first state. 1; when the data block update fails, the first bit identifier of the data block is updated to a second state such as 0. The first bit is the identifier of the data block in the incremental data area, the first state is the success state of the first bit identifier, and the second state is the failure state of the first bit identifier. It can be seen that the mirrored data area and the incremental data area of the boot image package store the data related to the target application; therefore, when the data obtaining module 505 obtains the first data from the boot image package, the increment of the image package can be started. The data area acquires the first data, and the first data may also be obtained from the mirror data area of the boot image package.

In the prior art, if the target application needs to be upgraded, the company to which the target application belongs needs to split the program data package of the target application again, and modularize the process to create a new micro client; greatly reducing the upgrade target. The efficiency of the application. Therefore, in the embodiment of the present invention, after the target application is upgraded, all the data that needs to be upgraded by the target application is copied to the upgrade original image package according to the process of creating the original image package, and then the image is started according to the target application. During the production process of the package, an upgrade boot image package for the upgrade data is created; when the user selects the upgrade in the mobile terminal, the mobile terminal only needs to download the upgrade boot image package directly from the server; when the target application is started, in addition to establishing the above data path, Then, the sixth path of the local cache manager and the upgrade boot image package is established; and the seventh path of the local cache manager and the upgrade original image package in the server is established. During the running of the target application, if the request is a read request, the data corresponding to the read request is obtained from the local upgrade boot image package and/or the upgrade original image package; when the local cache manager is in the upgrade boot image package and/or Or upgrade the original image package, if the corresponding data is not obtained, or only part of the data can be obtained; then the corresponding data is obtained from the local startup image package and/or the original image package; thereby improving the effect of the target application upgrade. rate.

In another embodiment of the present invention, a method corresponding to an application running system is described, with specific reference to FIGS. 6A and 6B, wherein FIG. 6A shows a flow chart of steps of an application running method embodiment of the present invention. FIG. 6B is a block diagram showing the structure of another embodiment of the application operating system of the present invention.

The local cache manager M6 in the embodiment of the present invention may include: a first application manager M6A and a first storage stack M6B, wherein the first application manager M6A may include a first configuration manager M60; the first storage stack M6B may The first storage unit simulator M61, the first incremental data manager M62, the first mirror cache manager M63 and the first splitter M64 are included.

Step 601: Obtain a startup running package and a startup image package of the target application when the target application is not installed, where the startup operation package is used to start the target application, and the startup image package includes the target application. Startup data.

If the target application is run in any mobile terminal that does not have the target application installed, the startup running package M65 and the startup image package M68 of the target application need to be obtained locally; if the local application does not exist, the startup running package M65 and the startup image are not present. Package M68, the boot package M65 and the boot image package M68 are obtained from the server and saved locally. After obtaining the startup running package M65 and the startup image package M68, when the user clicks the startup running package M65, the mobile terminal directly opens the startup running package M65, completes the installation of the basic components required to start the target application, and runs the corresponding startup program P2. To launch the corresponding target application. The startup data included in the acquired startup image package M68 may be data required by the target application in the process of the target application from the shutdown state to the full startup state, or may be a process running from the shutdown state to the full startup state for a period of time. The data required by the target application; this depends on the time when the target application is running when the boot image package of the target application in the above embodiment is created.

Step 602: When the target application is started by using the startup package, establish a local cache manager, and establish a first path of the local cache manager and a startup image package, and establish a local cache manager and a server. Two pathways.

The local cache manager establishing module 502 establishes a local cache manager M6 when the target application is started. Specifically, the first control module M66 calls to establish a local cache process, starts the first application manager M6A, and controls the first application manager. The M6A establishes a first storage unit simulator M61, a first incremental data manager M62, a first mirror cache manager M63 and a first splitter M64; wherein the first configuration manager M60 in the first application manager M6A is also Was started. Then, the first path of the local cache manager M6 and the boot image package M68 is established, and the second path of the local cache manager M6 and the server is established.

Step 603: Create a first virtual storage unit locally, and establish a third path of the local cache manager and the first virtual storage unit.

Step 604: The local cache manager receives a data request by using the third path, where the data request is received by the first virtual storage unit from the target application.

Steps 603 and 604 are the same as steps 403 and 404, respectively, and are not described herein again.

Step 605: When the data request is a read request, the local cache manager acquires first data of the read request from the startup image package by using the first path; and/or, the local cache The manager obtains the first data of the read request from the original image package of the server through the second path; wherein the original image package includes startup data and operation data of the target application.

After the first path and the second path are established, the first control module M66 starts the storage unit creation process, creates a first virtual storage unit M69 in the mobile terminal by the first virtual storage unit establishing module 503, and creates the first a virtual storage unit M69 and a third path S3 of the first storage unit simulator M61; then the operating system of the mobile terminal creates a mount point for the first virtual storage unit M69, and the process in the operating system can pass the mount point, The first virtual storage unit is accessed. In addition, in the operating system, there is a first virtual storage unit IO simulator M610 corresponding to the first virtual storage unit M69, for identifying A read and write operation of a virtual storage unit M69.

The first storage unit simulator M61 forwards the request to the first incremental data manager M62; the first incremental data manager M62 determines whether the request is a read request or a write request; when the first increment When the data manager M62 determines that the request is a read request, the read request is sent to the first shunt M64. After receiving the read request, the first shunt M64 first determines the locally stored boot image package through the first path. Whether there is first data corresponding to the read request in the mirror data area; if yes, determining whether the first data is valid; if the first data is valid, the image package can be locally started through the first path The first data is obtained in M68. If the first data does not exist in the locally stored boot image package M68, or the state of the first data in the local boot image package is invalid, the first splitter may pass the second path from the original image of the server. The first data is obtained in the package M67. If part of the data in the first data is valid in the locally stored boot image package, obtain part of the data in the first data from the boot image package, and obtain the first image from the original image package M67 of the server. Data from other parts of the data.

Step 606: Feed the first data to the target application through the third path, so that the target application runs.

The first shunt M64 returns the acquired first data to the first incremental data manager M62, and the first incremental data manager M62 forwards the first data to the first storage unit simulator; the first storage The unit simulator M61 returns to the first virtual storage unit M69 through the third path S3, and the first virtual storage unit M69 feeds back the first data to the target application through the first virtual storage unit IO simulator M610.

In the embodiment of the present invention, after the original image package, the startup image package, and the startup operation package are created, when the user first makes the target application, the startup application package and the startup image package of the target application are obtained; when the application is started by the startup operation package, Establishing a local cache manager, and establishing a path between the local cache manager, the boot image package, and the original image package; when the local cache manager receives the read request, the image package can be booted from the local storage through the corresponding path, and And obtaining the data corresponding to the read request in the original image package of the server and feeding back to the target application, so that the target application is run; thereby implementing, in the case of only acquiring the startup running package and the startup image package, During the running of the target application, the data required by the target application is obtained from the original image package of the boot image package and/or the server to ensure the normal operation of the target application. In addition, since the startup image package contains the startup data of the target application, which is much smaller than the original data packet size of the target application, the time for the user to start the target application is greatly saved, and the user experience is enhanced; in addition, the target application is long. During the running of the time, in general, all functions will not be used, and only part of the program data will be downloaded, so that the space occupied by the user's local device storage system will be greatly reduced.

In another embodiment of the present invention, a detailed description of the processing procedure after the first incremental data manager obtains the request is provided. Referring specifically to FIGS. 7 and 6B, FIG. 7 illustrates another embodiment of the present invention. A flow chart of the steps of the application running method embodiment.

In the embodiment of the present invention, establishing the first path may include establishing a data path S1A between the incremental data area of the first incremental data manager M62 and the startup image package M68, so that the first incremental data manager M62 The data is written into the delta data area of the boot image package M68, and the data path S1B of the mirrored data area in the first mirror cache manager M63 and the boot image pack M68.

Step 701: Determine whether the request is a read request. If not, execute step 702; if yes, execute step 703.

During the running of the target application, a data request is sent to the first virtual storage unit M69, and the sent data request may be a write request or a read request; when the data request is a write request, in order not to destroy the boot image package In the mirrored data area of the M68, the first incremental data manager M62 can write the second data corresponding to the write request into the incremental data area of the boot image package M68, that is, step 702 is performed; when the data request is read Upon request, the first incremental data manager M62 can send the read request to the first splitter M64, and the first splitter M64 performs step 703.

Step 702: Write, by using the first path, the second data of the write request into the incremental data area; and set a second data pair. The first bit of the data block is identified as the first state, and then the end step is performed.

When the first incremental data manager M62 determines that the data request is a write request, the data corresponding to the write request is determined as the second data; the first incremental data manager M62 passes the first path, and the boot image package M68 In the mirrored data area, and/or, through the second path, read the data block corresponding to the second data from the original image package of the server, and place the data block corresponding to the second data in the memory, the first incremental data The manager M62 updates the corresponding data in the data block corresponding to the second data, such as changing data or adding data according to the write request; and updating the first bit identifier of the data block when the data block is successfully updated. The first state is 1, and when the data block update fails, the first bit of the data block is updated to be the second state, such as 0. Then, through the path S1A, the data block corresponding to the second data and the first bit identifier corresponding to each data block are written into the incremental data area of the boot image package M68, and then the end step is performed; wherein the first bit identifier is The identifier of the data block in the incremental data area, the first state is the success state of the first bit identifier, and the second state is the failure state of the first bit identifier.

When the first incremental data manager M62 determines that the request is a read request, the read request is sent to the first splitter M64; the first splitter M64 can locally boot the image package M68 and/or the data server Obtained in the original image package M67; wherein the first incremental data manager M62 obtains the first data from the local boot image package M68, and may start from the incremental data area of the boot image package M68 and/or start the image package M68. Obtained in the mirrored data area, where the boot image package includes: an incremental data area, a mirrored data area, a configuration data area, and a checksum database data area. The specific steps are as follows:

Step 703: Determine whether the first data exists in the incremental data area; if yes, execute step 704; if not, perform step 706.

When the first incremental data manager M62 obtains the first data from the startup image package M68, it first determines whether the data block corresponding to the first data exists in the incremental data area of the startup image package M68, and is in the incremental data area. When there is a data block corresponding to the first data, step 704 is performed; when there is no data block corresponding to the first data in the incremental data area, step 706 is performed.

Step 704: Determine whether the state of the first bit identifier of the data block corresponding to the first data in the incremental data area is the first state. If yes, execute step 705; if no, perform step 706.

When the data block corresponding to the first data exists in the incremental data area, determining whether the data block corresponding to the first data is successfully updated according to the first bit identifier corresponding to the data block in the incremental data area. When the state of the first bit identifier of the data block is the first state, determining that the data in the data block is successfully updated, step 705 is performed; and when the state of the first bit identifier of the data block is the second state, determining the data. The data in the block is not successfully updated, and step 706 is performed. The data block corresponding to the first data may be one or more than one; the first data may include all data of each data block, or may be partial data of each data block.

Step 705: Acquire the first data from the incremental data area, and then perform step 714.

When the state of the first bit identifier is the first state, the first data is obtained from the delta data area. Since the first data may include a plurality of data blocks, the first data includes a plurality of data blocks, and the first bit in the incremental data area is identified as the first state, and then from the incremental data area The data of the data blocks is obtained, and step 714 is performed. Step 706 is performed for the other data blocks whose status of the first bit is the second state.

When the state of the first bit identifier is the second state, the first data is read from the mirror data area, and the steps are as follows:

Step 706: Determine whether the first data exists in the mirrored data area. If yes, execute step 707. If not, perform step 709.

Before the first data is read from the mirrored data area, the first current divider M64 needs to determine whether the first data exists in the mirrored data area. If yes, step 707 is performed. If not, step 709 is performed. .

Step 707: Determine whether the state of the second bit identifier of the data block corresponding to the first data is the third state, and if yes, execute Step 708; if no, step 709 is performed.

When the data block corresponding to the first data exists in the mirror data area, it is required to determine whether the data in the data block corresponding to the first data is valid, so as to ensure that the first data fed back to the target application can support the normal operation of the target application. Specifically, it is determined whether the data block corresponding to the first data in the mirrored data area is valid according to the status of the second bit identifier of the data block in the mirrored data area; and when the status of the second bit identifier is the third status, determining the corresponding The data in the data block is valid; when the state of the second bit identifier is the fourth state, it is determined that the data in the corresponding data block is invalid; wherein the third state is the valid state of the second bit identifier, and the fourth state is the second bit identifier Invalid state.

Step 708: Acquire the first data from the mirrored data area, and then perform step 714.

When the state of the second bit identifier corresponding to the data block is the third state, the first data is obtained from the mirror data area. Since the first data may include a plurality of data blocks, the first data includes several of the plurality of data blocks, and the second bit in the mirrored data area is identified as the third state, and the data is obtained from the mirrored data area. For the data of several data blocks, step 714 is performed; for the other data blocks whose status of the second bit is the fourth state, step 709 is performed.

Step 709: Acquire the first data from an original image package of the server.

When the first shunt M64 determines that the local cache of the mobile terminal is in the incremental data area and the mirrored data area of the boot image package M68, the first data does not exist, or a part of the first data exists, or When the first data is invalid, the first data may be obtained from the original image package M67 of the data server.

Step 710: Calculate a first checksum of the first data corresponding data block, and query a second checksum of the first data corresponding data block in the checksum database data area.

Step 711: Match the first checksum with the second checksum.

Due to network instability or other factors, the first data obtained from the server may be wrong or incomplete; when the first data is obtained from the original image package M67 of the data server The first shunt M64 needs to check the obtained first data to determine whether the first data acquired from the data server is correct; therefore, calculating the first checksum of the data block corresponding to the acquired first data; And searching for a second checksum of the data block corresponding to the first data in the checksum database data area of the boot image package M68. The first checksum is matched with the second checksum, and based on the result of the matching, it is determined whether the first data acquired from the original image package M67 is correct.

Step 712: Determine whether the first checksum and the second checksum are successfully matched. If successful, perform step 713; if not, perform step 709.

Determining whether the first checksum is successfully matched with the second checksum. If the match is successful, step 713 may be performed. If the match is unsuccessful, step 709 is performed, that is, the first data is obtained from the server again. When the first checksum of the first data acquired from the server is not successfully matched with the second checksum, the failed information is returned to the target application, and the step of ending is performed.

Step 713: Save the first data to the mirrored data area, and set a second bit identifier of the first data corresponding data block to a third state.

Before returning the acquired first data to the first incremental data manager M62, the first shunt M64 saves the first data in the mirror data area of the boot image package M68; and sets the first data corresponding data block The second bit is identified as a valid state, the third state.

Step 714: Feed the first data to the target application.

If the data acquired by the first shunt M64 includes data acquired from the boot image package M68, and data acquired from the original image package M67, the two pieces of data are merged and returned to the first incremental data manager M62. If the data acquired by the first shunt M64 includes only the data obtained from the boot image package M68, the data obtained from the boot image package M68 is returned to the first increase. The data manager M62; if the data acquired by the first shunt M64 includes only the data acquired from the original image package M67, the data acquired from the original image package M67 is returned to the first incremental data manager M62. If the first incremental data manager M62 acquires data from the incremental data area of the boot image package M68, merge the data sent by the first splitter M64 with the two pieces of data acquired from the incremental data area. Returning to the first storage unit simulator M61; if the first incremental data manager M62 only acquires data from the first flow divider M64, directly transmitting the acquired data to the first storage unit simulator M61; The incremental data manager M62 only obtains the data from the incremental data area, and directly sends the acquired data to the first storage unit simulator M61, and the first storage unit simulator M61 passes the read through the third path S3. The corresponding first data is requested to be fed back to the target application.

Preferably, the server SE of the embodiment of the present invention may include a configuration server SE1 for storing configuration information of various different target applications, and a data server SE2 for storing different target applications. The original image package M67 and the startup image package M68 and the startup operation package M65; the second path of establishing the local cache manager M6 and the server SE includes: establishing a fourth path S21 of the first application manager M6A and the configuration server SE1, and then, An application manager M6A acquires first configuration information and a checksum database data area corresponding to the identifier of the target application from the configuration server SE1 according to the identifier of the target application. The second path of the local cache manager M6 and the server SE is further configured to: establish a fifth path S22 between the first splitter M64 and the data server SE2; specifically, the first splitter M64 is configured according to the acquired first configuration information. The original image package M67 corresponding to the configuration information is searched in the data server SE2, and then connected to the original image package M67. In the embodiment of the present invention, before the path of the local cache manager M6 and the boot image package M68 is established, the boot image package corresponding to the boot package M65 needs to be searched in the local cache. Specifically, the first application manager M6A runs the package according to the startup. The identifier of the target application in the M65 is locally searched for the startup image package corresponding to the identifier of the target application, and then the second configuration information is obtained from the startup image package, and the second configuration information and the first obtained from the configuration server SE1 are obtained. The configuration information is compared. When the two match, the startup image package is determined as the startup image package M68 of the target application. When the match is unsuccessful, the boot image package corresponding to the identifier of the target application can be newly found locally.

The first data, the second data, and the like related data in the embodiment of the present invention may be implemented in the form of a fixed size (8 KB, 16 KB, 64 KB, etc.) data block set, or may be implemented in the form of a data range, such as establishing data. The descriptor records the data start offset (StartOffset) and the data size (Size) to describe the range corresponding to the data.

In the embodiment of the present invention, if the target application needs to be upgraded, all the data that needs to be upgraded by the target application is copied to the upgrade original image package according to the process of creating the original image package M27 in the above embodiment; Applying the startup image package M48 to create an upgrade boot image package for the upgrade data; when the user selects the upgrade in the mobile terminal, the mobile terminal only needs to download the upgrade boot image package directly from the server; when the target application starts, in addition to establishing In addition to the above data path, the sixth path of the local cache manager and the upgrade boot image package is established; and the seventh path of the local cache manager and the upgrade original image package in the server is established; in the process of running the target application, if the request is When the request is read, the data corresponding to the read request is obtained from the local upgrade boot image package and/or the upgrade original image package; when the local cache manager upgrades the boot image package and/or upgrades the original image package, the corresponding response is not obtained. Data, or only when part of the data is obtained; then the image package is started locally and / Acquiring original image data corresponding to the packet; the same particular local boot image upgrade package and / or the step of upgrading the original image package, the corresponding data is acquired from the above-mentioned steps 703-712 will not be repeated here.

If the number of subsequent target application upgrades is large, you can generate an upgrade original image package for all upgraded data, or merge all upgraded data with the original data, use the merged data packet as the original data package, and then re-create the original image. Package and boot image package.

Various large-scale applications, such as online games, PS, etc., may utilize an application running system and method according to an embodiment of the present invention. Start and run on the mobile terminal that does not have the application installed. Take online game A as an example. Specifically, on the mobile terminal that does not have online game A installed, obtain the APP Launcher of online game A, and the startup image package of online game A, and start the image. The package only contains the data when the online game A starts and the data when the online game A runs to the fifth level; the user can start the online game A by clicking the APP Launcher, and when the online game A is started, the local cache manager is created and the first virtual storage is created. a unit; and establishing the first path, the second path, and the third path, when the user registers in the online game A, the online game A sends a write request to the first virtual storage unit; the local cache manager acquires the After the request is written, the information registered by the user is written into the incremental data area of the startup image package; when the online game A is started to run to the fifth level, the local cache manager obtains the online game A from the startup image package through the first path. All the data needed, and the data obtained through the third path is fed back to the online game A; when the online game A runs to the sixth level, the local cache manager passes the second pass. The road obtains the data of the sixth level from the original image package of the server, and feeds the acquired data to the online game A through the third path; and saves the data of the sixth level in the startup image package; thereby realizing the online game A At the same time of operation, make a boot image package for online game A. When the online game A is started again, when the online game A runs to the sixth level, the local cache manager can obtain the data required for the sixth level of the online game A from the local startup image package. If the first, fifth, and tenth levels of the online game A are upgraded, the upgraded data corresponding to the first, fifth, and tenth levels of the online game A can be made into an upgrade original image package, and the corresponding upgrade startup image package. The upgraded original image package is stored on the server, and the upgraded startup image package is stored on the mobile terminal having the startup image package of the online game A; at this time, the upgraded online game A can be run on the mobile terminal.

In the process of the target operation, the data may be obtained from the startup image package and/or the original image package to ensure the normal operation of the target application; on the other hand, the original image package may be obtained from the original image package. The data is saved in the boot image package, so that when the target application needs the data for the next run, the data can be directly obtained from the boot image package in the local cache, ensuring the smooth running of the target application. In addition, when upgrading the target application, you only need to obtain the upgrade original image package and the upgrade startup image package. When the target application is run, the target application can be upgraded, which greatly improves the efficiency of the target application upgrade and saves costs.

The various embodiments in the present specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the various embodiments can be referred to each other.

Those skilled in the art will appreciate that embodiments of the embodiments of the invention may be provided as a method, apparatus, or computer program product. Thus, embodiments of the invention may be in the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, embodiments of the invention may take the form of a computer program product embodied on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

For example, FIG. 8 shows a computing device that can implement the image package creation and application running method according to the present invention, and the computing device includes: a computing device that applies an original image package making method, a computing device that uses an application boot image package manufacturing method, And computing devices that apply the method of operation. The computing device conventionally includes a processor 810 and a program product or readable medium in the form of a memory 820. Memory 820 can be an electronic memory such as a flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM, or ROM. Memory 820 has a memory space 830 for program code 831 for performing any of the method steps described above. For example, storage space 830 for program code may include various program code 831 for implementing various steps in the above methods, respectively. These program codes can be read from or written to one or more program products. These program products include program code carriers such as memory cards. Such a program product is typically a portable or fixed storage unit as described with reference to FIG. The storage unit may have storage segments, storage spaces, and the like that are similar to the storage 820 in the computing device of FIG. The program code can be compressed, for example, in an appropriate form. Typically, the storage unit includes readable code 831', ie, code readable by a processor, such as 810, that when executed by a computing device causes the computing device to perform various steps in the methods described above .

One of ordinary skill in the art can understand that all or part of the steps of implementing the foregoing embodiments may be completed by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, such as a ROM/RAM or a disk. , CD, etc.

Embodiments of the invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing terminal device to produce a machine such that instructions are executed by a processor of a computer or other programmable data processing terminal device Means are provided for implementing the functions specified in one or more of the flow or in one or more blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The instruction device implements the functions specified in one or more blocks of the flowchart or in a flow or block of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device such that a series of operational steps are performed on the computer or other programmable terminal device to produce computer-implemented processing, such that the computer or other programmable terminal device The instructions executed above provide steps for implementing the functions specified in one or more blocks of the flowchart or in a block or blocks of the flowchart.

While a preferred embodiment of the present invention has been described, it will be apparent that those skilled in the art can make further changes and modifications to the embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and

Finally, it should also be noted that in this context, relational terms such as first and second are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities. There is any such actual relationship or order between operations. Furthermore, the terms "comprises" or "comprising" or "comprising" or any other variations are intended to encompass a non-exclusive inclusion, such that a process, method, article, or terminal device that includes a plurality of elements includes not only those elements but also Other elements that are included, or include elements inherent to such a process, method, article, or terminal device. An element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or terminal device that comprises the element, without further limitation.

The above describes a mirror package creation, application operation method, and an image package creation and application operation system provided by the present invention. The principle and implementation manner of the present invention are described in the following. The description of the embodiments is only for helping to understand the method of the present invention and its core ideas; at the same time, for those skilled in the art, according to the idea of the present invention, there will be changes in the specific embodiments and application scopes. The description herein is not to be construed as limiting the invention.

Claims (30)

An application running method, comprising: Obtaining a startup running package and a startup image package of the target application when the target application is not installed, wherein the startup running package is used to start the target application, and the startup image package includes startup data of the target application. ; When the target application is started by the startup running package, a local cache manager is established, and a first path of the local cache manager and the startup image package is established, and a second path of the local cache manager and the server is established; Creating a first virtual storage unit locally, establishing a third path of the local cache manager and the first virtual storage unit; The local cache manager receives a request through the third path, the request being received by the first virtual storage unit from the target application; When the request is a read request, the local cache manager acquires first data of the read request from the boot image package through the first path; and/or, the local cache manager passes the Determining, by the second path, the first data of the read request from the original image package of the server; wherein the original image package includes startup data and operation data of the target application; The first data is fed back to the target application through the third path to cause the target application to run. The method of claim 1, wherein the boot image package comprises an incremental data area, the method further comprising: When the request is a write request, the local cache manager writes the second data of the write request into the incremental data area through the first path; The first bit identifier of the second data corresponding data block is set to be the first state. The method according to claim 1, wherein said boot image package comprises an incremental data area and a mirrored data area, said local cache manager obtaining said said image from said boot image package via said first path The steps of reading the first data of the request include: The local cache manager obtains the first data from the delta data area through the first path, and/or acquires the first data from the mirror data area. The method according to claim 3, further comprising: before the step of acquiring the first data from the incremental data area, further comprising: Determining whether the first data exists in the incremental data area; Determining, when present, a state of the first bit identifier of the data block corresponding to the first data; When not present, the step of obtaining the first data from the mirrored data area is performed. The method according to claim 4, further comprising: after determining the state of the first bit identifier of the data block corresponding to the first data, further comprising: When the state of the first bit identifier is the first state, performing the step of acquiring the first data from the incremental data region; When the state of the first bit identifier is the second state, the step of acquiring the first data from the mirror data area is performed. The method according to claim 3, further comprising: before the step of acquiring the first data from the mirrored data area, further comprising: Determining whether the first data exists in the mirror data area; Determining, when present, a state of the second bit identifier of the data block corresponding to the first data; When not present, the step of obtaining the first data from the original image package of the server is performed. The method according to claim 6, wherein after the step of determining the state of the second bit identifier of the data block corresponding to the first data, the method comprises: When the state of the second bit identifier is the third state, performing the step of acquiring the first data from the mirror data area; When the state of the second bit identifier is the fourth state, the step of acquiring the first data from the original image package of the server is performed. The method of claim 1 wherein said boot image package comprises a checksum database data area, After the step of acquiring the first data from the original image package of the server, the method further includes: Calculating a first checksum of the first data corresponding data block, and querying a second checksum of the first data corresponding data block in the checksum database data area; Matching the first checksum with the second checksum; When the first checksum and the second checksum are successfully matched, performing the step of feeding back the first data to the target application; When the first checksum and the second checksum match are unsuccessful, the step of acquiring the first data from the original image package of the server is performed. The method according to claim 8, wherein the boot image package comprises a mirrored data area, and when the first checksum and the second checksum are successfully matched, the method further comprises: Saving the first data into the mirrored data area, and setting a second bit identifier of the first data corresponding data block to a third state. The method according to claim 1, wherein the server comprises a configuration server, and the step of establishing a fourth path of the local cache manager and the configuration server comprises: Obtaining an identifier of the target application; And establishing, according to the identifier, a fourth path of the local cache manager and the configuration server, and acquiring first configuration information corresponding to the identifier. The method according to claim 10, wherein the server comprises a data server, and the step of establishing a fifth path of the local cache manager and the data server, further comprising: And establishing, according to the first configuration information, a fifth path of the local cache manager and the data server. The method according to claim 10, wherein the boot image package comprises a configuration data area, and the configuration data area comprises configuration information; Before the step of establishing the local cache manager and starting the first path of the image package, the method further includes: Searching, according to the identifier, a startup image package corresponding to the identifier in a local cache, and searching for a second configuration information from a configuration data area of the startup image package; Matching the first configuration information with the second configuration information; And when the first configuration information is successfully matched with the second configuration information, determining the startup image package as a startup image package of the target application. The method of claim 1, wherein the boot image package comprises a mirrored data area, and the local cache manager comprises a mirrored cache manager; The step of establishing the local cache manager and starting the first path of the image package includes: The mirror cache manager opens the mirror data area and establishes the first path of the mirror cache manager and the mirror data area. The method according to claim 1, wherein when the target application needs to be upgraded, the method further includes: Obtaining a target application upgrade startup image package, where the upgrade startup image package includes partial update data of the target application; After establishing the local cache manager, establishing a sixth path of the local cache manager and the upgrade boot image package, and establishing a seventh path of the local cache manager and the server; Before obtaining the first data from the boot image package and/or the original image package, the local cache manager obtains the first data of the read request from the upgrade boot image package through the sixth path And/or, the local cache manager obtains first data of the read request from the upgrade original image package of the server through the seventh path; wherein the upgrade original image package includes the target All updated data for the app. An application method for fabricating an original image package, comprising: Establishing a packet creation manager and creating an empty original image package, and establishing an eighth path of the packet creation manager and the original image package; Creating a second virtual storage unit locally, establishing a ninth path of the second virtual storage unit and the data packet creation manager; The data packet creation manager receives a data write request through the ninth path, wherein the data write request is obtained by the second virtual storage unit from a process; The data packet creation manager writes the third data corresponding to the data write request into the original image package by using an eighth path, where the third data is data included in the original data of the target application. The method according to claim 15, wherein after all the third data in the original data packet is written into the original image package, the method further comprises: The data packet creation manager generates a startup operation package corresponding to the target application, and the startup operation package is used to start the target application. An application startup image package manufacturing method, comprising: When the target application is started, the local manager is established, and the tenth path of the local manager and the original image package is established; Establishing an empty boot image package, and establishing an eleventh path of the local manager and the boot image package; Creating a third virtual storage unit locally, establishing a twelfth path of the local manager and the third virtual storage unit; The local manager receives a data request through the twelfth path, the data request being received by the third virtual storage unit from the target application; When the request is a read request, the local manager acquires fourth data corresponding to the read request from the original image package through the tenth path; and the first through the eleventh path Four data is written into the boot image package; when the target application stops running, stopping writing the fourth data to the boot image package. The method of claim 17, wherein the amount of data of the boot image package is less than 5% of the amount of data of the original image package. An application operating system, comprising: a data packet obtaining module, configured to acquire a startup running package and a startup image package of the target application in advance when the target application is not installed, where the startup running package is used to start the target application, and the startup image package includes The startup data of the target application; a local cache manager establishing module, configured to establish a local cache manager, establish a first path of the local cache manager and the boot image package, and establish a local cache management when the target application is started by the startup run package Second path between the device and the server; a first virtual storage unit establishing module, locally creating a first virtual storage unit, establishing a third path of the local cache manager and the first virtual storage unit; a first data request receiving module, configured to invoke the local cache manager, to receive a data request by using the third path, where the data request is received by the first virtual storage unit from the target application; a data obtaining module, configured to: when the data request is a read request, invoke the local cache manager to obtain first data of the read request from the boot image package through the first path; and/or And calling, by the local cache manager, the first data of the read request from the original image package of the server by using the second path; wherein the original image package includes startup data of the target application And running data; And a data feedback module, configured to feed back the first data to the target application by using the third path, so that the target application runs. The application running system according to claim 19, further comprising: a data writing module, configured to: when the request is a write request, the local cache manager writes the second data of the write request into the incremental data area by using the first path; setting a second The first bit of the data corresponding data block is identified as the first state. The application execution system according to claim 19, wherein The data acquisition module is configured to: when the local cache manager obtains the first data of the read request from the startup image package by using the first path, the local cache manager passes the a first path, obtaining the first data from the incremental data area, and/or acquiring the first data from the mirrored data area; wherein the boot image package includes an incremental data area and a mirror Data area. The application running system according to claim 19, further comprising: The data upgrade module is configured to obtain a target application upgrade startup image package when the target application needs to be upgraded, where the upgrade startup image package includes partial update data of the target application; after the local cache manager is established, the local cache manager is established. a sixth path with the upgrade boot image package, and a seventh path establishing a local cache manager and server; the local cache before the first data is obtained from the boot image package and/or the original image package The manager obtains first data of the read request from the upgrade boot image package through the sixth path; and/or, the local cache manager upgrades the original from the server through the seventh path Acquiring the first data of the read request in the image package; wherein the upgrade original image package includes all update data of the target application. An application original image package creation system, comprising: a packet creation manager establishing module, configured to establish a packet creation manager and create an empty original image package, and establish an eighth path of the data packet creation manager and the original image package; a second virtual storage unit establishing module, configured to locally create a second virtual storage unit, and establish a ninth path of the second virtual storage unit and the data packet creation manager; a second data request receiving module, configured to invoke the data packet creation manager, to receive a data write request by using the ninth path, wherein the data write request is obtained by the second virtual storage unit from a process; The original image packet data writing module is configured to invoke the data packet creation manager to write the third data corresponding to the data write request into the original image package by using an eighth path, where the third data is Is the data contained in the raw data of the target application. An application startup image package creation system, comprising: a local manager establishing module, configured to establish a local manager when starting the target application, and establish a tenth path of the local manager and the original image package; Initiating an image package creation module, establishing an empty boot image package, and establishing an eleventh path of the local manager and the boot image package; a third virtual storage unit establishing module, configured to locally create a third virtual storage unit, and establish a twelfth path of the local manager and the third virtual storage unit; a third data request receiving module, configured to invoke the local manager, to receive a data request by using the twelfth path, where the data request is received by the third virtual storage unit from the target application; Activating a mirror packet data writing module, configured to: when the request is a read request, invoke the local manager, and obtain, by using the tenth path, the fourth data corresponding to the read request from the original image packet; And writing, by the eleventh path, the fourth data into the boot image package; when the target application stops running, stopping writing the fourth data to the boot image package. A program comprising readable code that, when executed on a computing device, causes the computing device to perform an application running method according to any one of claims 1-14. A readable medium storing the program as recited in claim 25. A program comprising readable code that, when executed on a computing device, causes the computing device to perform the method of creating an original image package according to any one of claims 15-16. A readable medium storing the program as recited in claim 27. A program comprising readable code that, when executed on a computing device, causes the computing device to perform an application launch image package authoring method according to any of claims 17-18. A readable medium storing the program as recited in claim 29.

Images