Method and device for isolating x86 cloud application registry

Abstract

The invention provides a method and device for isolating an x86 cloud application registry, and the method comprises the steps: associating a cloud application session with a pre-created virtual registry space when the cloud application session starts; when the registry is operated by the cloud application, the registry virtualization layer between the operating system and the operating system registry maps the operation of the cloud application on the registry to the virtual registry space corresponding to the cloud application, so that the operation of different cloud applications on the same x86 server on the system registry is not mutually influenced.

Description

Technical Field

[0001] The present invention relates to the field of cloud applications, and in particular to a method and device for implementing x86 cloud application registry isolation. Background Art

[0002] In traditional systems, the registry is a key component that stores a large amount of configuration information. With the rise of x86 cloud applications (i.e., cloud applications running on x86 servers), multiple users may run different cloud applications or multiple instances of the same cloud application on the same x86 server at the same time. In this shared environment, operations on the registry by different x86 cloud applications may interfere with each other, causing system instability or errors.

[0003] In view of this, how to provide a method to implement x86 cloud application registry isolation so that operations of different cloud applications on the same x86 server on the system registry do not affect each other has become a technical problem that needs to be solved urgently. Summary of the invention

[0004] In view of the technical problems existing in the prior art, the embodiments of the present application provide a method and device for implementing x86 cloud application registry isolation.

[0005] In a first aspect, an embodiment of the present application provides a method for implementing x86 cloud application registry isolation, which is applied to an x86 server, including: When the cloud application session starts, associating the cloud application session with a pre-created virtual registry space; When a cloud application operates a registry, a registry virtualization layer located between the operating system and the operating system registry maps the cloud application's operation on the registry to a virtual registry space corresponding to the cloud application.

[0006] In a second aspect, an embodiment of the present application further provides a device for implementing x86 cloud application registry isolation, which is applied to an x86 server and includes: an associating unit, configured to associate the cloud application session with a pre-created virtual registry space when the cloud application session starts; The mapping unit is used for mapping the registry operation of the cloud application to the virtual registry space corresponding to the cloud application by the registry virtualization layer located between the operating system and the operating system registry when the cloud application operates the registry.

[0007] In a third aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method for implementing x86 cloud application registry isolation as described in the first aspect are executed.

[0008] In a fourth aspect, an embodiment of the present application further provides an electronic device, comprising: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium through the bus, and the processor executes the machine-readable instructions to perform the steps of the method for implementing x86 cloud application registry isolation as described in the first aspect.

[0009] In summary, the method and device, electronic device and storage medium for implementing x86 cloud application registry isolation provided by the embodiments of the present application, when a cloud application operates the registry, the cloud application's operation on the registry is mapped to the virtual registry space corresponding to the cloud application through the registry virtualization layer located between the operating system and the operating system registry. The virtual registry spaces corresponding to different cloud applications are isolated from each other, so that the operations of different cloud applications on the system registry on the same x86 server do not affect each other. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 A flowchart of an embodiment of a method for implementing x86 cloud application registry isolation provided in an embodiment of the present application; Figure 2 A structural diagram of an embodiment of a device for implementing x86 cloud application registry isolation provided in an embodiment of the present application; Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0011] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of sequence, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of the present application, or remove one or more operations from the flowchart.

[0012] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0013] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.

[0014] Reference Figure 1 As shown, an embodiment of the present application provides a flow chart of a method for implementing x86 cloud application registry isolation, the method is applied to an x86 server (the server is a cloud server running a cloud application), including: S10, when the cloud application session starts, associating the cloud application session with a pre-created virtual registry space; S11. When the cloud application operates the registry, the registry virtualization layer located between the operating system and the operating system registry maps the cloud application's operation on the registry to the virtual registry space corresponding to the cloud application.

[0015] In this embodiment, it should be noted that the virtual registry spaces of different cloud applications are completely isolated. The registry virtualization layer is located between the Window system and the actual operating system registry, and can be implemented through a registry filter driver, which is responsible for intercepting cloud application operation requests to the system registry and mapping the request to the virtual registry space corresponding to the cloud application. For example, user A's cloud application XXX's registry operation request is mapped to the virtual registry space HUK\gs1\, and user B's cloud application YYY's registry operation request is mapped to the virtual registry space HUK\gs2\. In other words, by creating a virtual registry environment, the registry operations of each cloud application are isolated, ensuring that the registry operations of cloud applications of different users do not affect each other, and achieving stable multi-user simultaneous use.

[0016] The method for implementing x86 cloud application registry isolation provided in the embodiment of the present application, when a cloud application operates the registry, the cloud application's operation on the registry is mapped to the virtual registry space corresponding to the cloud application through the registry virtualization layer located between the operating system and the operating system registry. The virtual registry spaces corresponding to different cloud applications are isolated from each other, so that the operations of different cloud applications on the system registry on the same x86 server do not affect each other.

[0017] Based on the above method embodiment, the registry virtualization layer located between the operating system and the operating system registry maps the cloud application's operation on the registry to the virtual registry space corresponding to the cloud application, which may include: When the cloud application requests to open the target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application. If so, the handle of the subkey corresponding to the mapping path is returned; otherwise, the handle of the target subkey requested to be opened by the cloud application is returned; and / or When the cloud application requests to create a target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and if not, creates the target subkey based on the mapping path; and / or When a cloud application requests to modify a target subkey, the registry virtualization layer determines whether a mapping path corresponding to the target subkey exists in the virtual registry space corresponding to the cloud application. If so, the subkey corresponding to the mapping path is modified; otherwise, the target subkey requested to be modified by the cloud application is copied based on the mapping path, and the copied target subkey is modified; and / or When the cloud application requests to delete the target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and if so, deletes the subkey corresponding to the mapping path; and / or When a cloud application requests to rename a target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application. If so, the subkey corresponding to the mapping path is renamed. Otherwise, the target subkey that the cloud application requests to rename is copied based on the mapping path, and the copied target subkey is renamed.

[0018] In this embodiment, it should be noted that the path of the target subkey corresponds one-to-one to the mapping path corresponding to the target subkey.

[0019] When a cloud application requests to open a target subkey, the registry virtualization layer will preferentially return the handle of the subkey corresponding to the mapping path. Only when the mapping path corresponding to the target subkey does not exist in the virtual registry space corresponding to the cloud application, will the actual system registry subkey handle be returned. For example, the virtual registry space corresponding to the cloud application is HUK\gs1\, and the path of the target subkey requested to be opened by the cloud application is HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip. If the mapping path corresponding to the target subkey exists, HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip, the handle of the subkey 7-Zip corresponding to HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip is returned; otherwise, the handle of the subkey 7-Zip corresponding to HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip is returned.

[0020] When a cloud application requests to create a target subkey, the registry virtualization layer maps the target subkey path to the virtual registry space corresponding to the cloud application to create the target subkey in the virtual registry space. For example, if the virtual registry space corresponding to the cloud application is HUK\gs1\ and the path of the target subkey requested to be created by the cloud application is HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip, it is necessary to determine whether the mapping path HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip corresponding to the target subkey exists. If it does not exist, the target subkey 7-Zip is created directly (the path is HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip). Otherwise, the target subkey 7-Zip is created in an overwrite manner (the path is HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip, and the newly created subkey 7-Zip overwrites the subkey corresponding to the original path HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip).

[0021] When a cloud application requests to modify a target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application. If so, the subkey corresponding to the mapping path is modified. Otherwise, the target subkey requested to be modified by the cloud application is copied based on the mapping path, and the copied target subkey is modified. For example, the virtual registry space corresponding to the cloud application is HUK\gs1\, and the path of the target subkey that the cloud application requests to modify is HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip. If the path HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip exists in the virtual registry space, the subkey 7-Zip corresponding to HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip is modified directly. Otherwise, the subkey 7-Zip corresponding to HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip is first copied to the virtual registry space, and then the subkey 7-Zip copied to the virtual registry space is modified. The path of the subkey 7-Zip copied to the virtual registry space is HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip.

[0022] When a cloud application requests to delete a target subkey, the registry virtualization layer will determine whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application. If so, the subkey corresponding to the mapping path will be deleted. Otherwise, a successful deletion message can be directly returned to the cloud application, or the real target subkey can be copied to the virtual registry space first, and then the target subkey copied to the virtual registry space can be deleted. For example, the virtual registry space corresponding to the cloud application is HUK\gs1\, and the path of the target subkey that the cloud application requests to delete is HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip. If the path HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip exists in the virtual registry space, the subkey 7-Zip corresponding to HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip can be directly deleted. Otherwise, HKEY_LOCAL_MAC can be directly returned to the cloud application. The message that the subkey corresponding to HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip is successfully deleted is displayed, or first copy the subkey 7-Zip corresponding to HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip to HUK\gs1\, and then delete the subkey 7-Zip corresponding to HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip. The path of the subkey 7-Zip copied to HUK\gs1\ is HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip.

[0023] The operation of the registry virtualization layer when the cloud application requests to rename the target subkey is consistent with the operation of the registry virtualization layer when the cloud application requests to modify the target subkey. Specifically: if a mapping path corresponding to the target subkey exists in the virtual registry space corresponding to the cloud application, the subkey corresponding to the mapping path is renamed; otherwise, the target subkey is first copied to the virtual registry space, and then the copied target subkey is renamed. For example, the virtual registry space corresponding to the cloud application is HUK\gs1\, and the path of the target subkey that the cloud application requests to be renamed is HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip. If the path HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip exists in the virtual registry space, the subkey 7-Zip corresponding to HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip is directly renamed. Otherwise, the subkey 7-Zip corresponding to HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip is first copied to the virtual registry space, and then the subkey 7-Zip copied to the virtual registry space is renamed. The path of the subkey 7-Zip copied to the virtual registry space is HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip.

[0024] In addition, it should be noted that each time a cloud application operates a target subkey, relevant operation information can be recorded, such as the path of the target subkey, the operation time, the operation method (such as creation, modification, deletion, renaming, etc.), etc.

[0025] Based on the above method embodiment, the registry virtualization layer located between the operating system and the operating system registry maps the cloud application's operation on the registry to the virtual registry space corresponding to the cloud application, and may also include: When a cloud application requests to query the next level subkey of a target subkey, the registry virtualization layer merges the next level subkey of the target subkey with the next level subkey of the mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and returns the merged result.

[0026] In this embodiment, it should be noted that, for cloud applications, their operations on the target subkey are mapped to the virtual registry space. Therefore, when the cloud application requests to query the target subkey, it is necessary to merge the path of the target subkey and the mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application to return an accurate merge result. For example, the path of the target subkey is HKEY_LOCAL_MACHINE\SOFTWARE, and its next-level subkeys include HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip and HKEY_LOCAL_MACHINE\SOFTWARE\360Safe. The mapping path corresponding to HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip is HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip, and HKEY_LOCAL_MACHINE\SOFTWARE\360Safe. The mapping path HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\360Safe corresponding to 360Safe is marked for deletion. In addition to HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip, the next-level subkeys of HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE also include HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\AAA. When the cloud application requests to query the next-level subkeys of HKEY_LOCAL_MACHINE\SOFTWARE, the subkeys corresponding to HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\7-Zip and the subkey list corresponding to HUK\gs1\HKEY_LOCAL_MACHINE\SOFTWARE\AAA are returned to the cloud application.

[0027] Based on the foregoing method embodiment, the method may further include: When the cloud application exits, all subkeys in the virtual registry space corresponding to the cloud application are deleted.

[0028] In this embodiment, assuming that the virtual registry space corresponding to the cloud application is HUK\gs1\, when the cloud application exits, it is necessary to delete all subkeys under HUK\gs1\ to release resources to ensure that the system state is restored to the state before the cloud application starts, and prepare for the next cloud application session or user.

[0029] Based on the foregoing method embodiment, the method may further include: Caches the cloud application's operation information on the target subkey.

[0030] In this embodiment, by caching the operation information of the cloud application on the target subkey (such as the information of creating the subkey corresponding to the mapping path, etc.), the reading speed of the frequently operated subkey can be improved.

[0031] Reference Figure 2 FIG. 1 is a schematic diagram of a structure of a device for implementing x86 cloud application registry isolation provided by an embodiment of the present application. The device is applied to an x86 server and includes: an associating unit 20, configured to associate the cloud application session with a pre-created virtual registry space when the cloud application session starts; The mapping unit 21 is used for mapping the registry operation of the cloud application to the virtual registry space corresponding to the cloud application by the registry virtualization layer located between the operating system and the operating system registry when the cloud application operates the registry.

[0032] The device for implementing x86 cloud application registry isolation provided in the embodiment of the present application, when a cloud application operates the registry, maps the cloud application's operation on the registry to the virtual registry space corresponding to the cloud application through the registry virtualization layer located between the operating system and the operating system registry. The virtual registry spaces corresponding to different cloud applications are isolated from each other, so that the operations of different cloud applications on the system registry on the same x86 server do not affect each other.

[0033] Based on the above device embodiment, the mapping unit may be used for: When the cloud application requests to open the target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application. If so, the handle of the subkey corresponding to the mapping path is returned; otherwise, the handle of the target subkey requested to be opened by the cloud application is returned; and / or When the cloud application requests to create a target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and if not, creates the target subkey based on the mapping path; and / or When a cloud application requests to modify a target subkey, the registry virtualization layer determines whether a mapping path corresponding to the target subkey exists in the virtual registry space corresponding to the cloud application. If so, the subkey corresponding to the mapping path is modified; otherwise, the target subkey requested to be modified by the cloud application is copied based on the mapping path, and the copied target subkey is modified; and / or When the cloud application requests to delete the target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and if so, deletes the subkey corresponding to the mapping path; and / or When a cloud application requests to rename a target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application. If so, the subkey corresponding to the mapping path is renamed. Otherwise, the target subkey that the cloud application requests to rename is copied based on the mapping path, and the copied target subkey is renamed.

[0034] Based on the above device embodiment, the mapping unit may also be used for: When a cloud application requests to query the next level subkey of a target subkey, the registry virtualization layer merges the next level subkey of the target subkey with the next level subkey of the mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and returns the merged result.

[0035] Based on the above device embodiment, the mapping unit may also be used for: When the cloud application exits, all subkeys in the virtual registry space corresponding to the cloud application are deleted.

[0036] Based on the above device embodiment, the mapping unit may also be used for: Caches the cloud application's operation information on the target subkey.

[0037] The device for implementing x86 cloud application registry isolation provided in the embodiment of the present application has an implementation process that is consistent with the method for implementing x86 cloud application registry isolation provided in the embodiment of the present application, and the effect that can be achieved is also the same as the method for implementing x86 cloud application registry isolation provided in the embodiment of the present application, and will not be repeated here.

[0038] Through the above scheme, the following functions can be achieved: 1. Isolate cloud application registry operations of different users to ensure that traces can be quickly and accurately cleaned up after the user leaves; 2. Ensure that when multiple users log in to an x86 server and run the same cloud application at the same time, their operations will not affect each other; 3. After the cloud application ends, the registry status can be restored in time without restarting the system so that the next user can use it immediately.

[0039] like Figure 3 As shown, an electronic device provided by an embodiment of the present application includes: a processor 30, a memory 31 and a bus 32, wherein the memory 31 stores machine-readable instructions executable by the processor 30, and when the electronic device is running, the processor 30 communicates with the memory 31 through the bus 32, and the processor 30 executes the machine-readable instructions to perform the steps of the method for implementing x86 cloud application registry isolation as described above.

[0040] Specifically, the above-mentioned memory 31 and processor 30 can be general-purpose memory and processor, which are not specifically limited here. When the processor 30 runs the computer program stored in the memory 31, it can execute the above-mentioned method for implementing x86 cloud application registry isolation.

[0041] Corresponding to the above-mentioned method for implementing x86 cloud application registry isolation, an embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned method for implementing x86 cloud application registry isolation are executed.

[0042] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for implementing x86 cloud application registry isolation, characterized in that: Applicable to x86 servers, including: When the cloud application session starts, associating the cloud application session with a pre-created virtual registry space; When a cloud application operates a registry, a registry virtualization layer located between the operating system and the operating system registry maps the cloud application's operation on the registry to a virtual registry space corresponding to the cloud application.

2. The method according to claim 1, characterized in that The registry virtualization layer located between the operating system and the operating system registry maps the cloud application's operation on the registry to the virtual registry space corresponding to the cloud application, including: When the cloud application requests to open the target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application. If so, the handle of the subkey corresponding to the mapping path is returned; otherwise, the handle of the target subkey requested to be opened by the cloud application is returned; and / or When the cloud application requests to create a target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and if not, creates the target subkey based on the mapping path; and / or When a cloud application requests to modify a target subkey, the registry virtualization layer determines whether a mapping path corresponding to the target subkey exists in the virtual registry space corresponding to the cloud application. If so, the subkey corresponding to the mapping path is modified; otherwise, the target subkey requested to be modified by the cloud application is copied based on the mapping path, and the copied target subkey is modified; and / or When the cloud application requests to delete the target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and if so, deletes the subkey corresponding to the mapping path; and / or When a cloud application requests to rename a target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application. If so, the subkey corresponding to the mapping path is renamed. Otherwise, the target subkey that the cloud application requests to rename is copied based on the mapping path, and the copied target subkey is renamed.

3. The method according to claim 1 or 2, characterized in that The registry virtualization layer located between the operating system and the operating system registry maps the cloud application's operation on the registry to the virtual registry space corresponding to the cloud application, and also includes: When a cloud application requests to query the next level subkey of a target subkey, the registry virtualization layer merges the next level subkey of the target subkey with the next level subkey of the mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and returns the merged result.

4. The method according to claim 1, characterized in that Also includes: When the cloud application exits, all subkeys in the virtual registry space corresponding to the cloud application are deleted.

5. The method according to claim 1, characterized in that Also includes: Caches the cloud application's operation information on the target subkey.

6. A device for implementing x86 cloud application registry isolation, characterized in that: Applicable to x86 servers, including: an associating unit, configured to associate the cloud application session with a pre-created virtual registry space when the cloud application session starts; The mapping unit is used for mapping the registry operation of the cloud application to the virtual registry space corresponding to the cloud application by the registry virtualization layer located between the operating system and the operating system registry when the cloud application operates the registry.

7. The device according to claim 6, characterized in that The mapping unit is used for: When a cloud application requests to open a target subkey, the registry virtualization layer determines whether a mapping path corresponding to the target subkey exists in the virtual registry space corresponding to the cloud application. If so, the handle of the subkey corresponding to the mapping path is returned. Otherwise, the handle of the target subkey requested to be opened by the cloud application is returned. and / or When the cloud application requests to create a target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and if not, creates the target subkey based on the mapping path; and / or When a cloud application requests to modify a target subkey, the registry virtualization layer determines whether a mapping path corresponding to the target subkey exists in the virtual registry space corresponding to the cloud application. If so, the subkey corresponding to the mapping path is modified. Otherwise, the target subkey requested to be modified by the cloud application is copied based on the mapping path, and the copied target subkey is modified. and / or When the cloud application requests to delete the target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and if so, deletes the subkey corresponding to the mapping path; and / or When a cloud application requests to rename a target subkey, the registry virtualization layer determines whether there is a mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application. If so, the subkey corresponding to the mapping path is renamed. Otherwise, the target subkey that the cloud application requests to rename is copied based on the mapping path, and the copied target subkey is renamed.

8. The device according to claim 6 or 7, characterized in that The mapping unit is further used for: When a cloud application requests to query the next level subkey of a target subkey, the registry virtualization layer merges the next level subkey of the target subkey with the next level subkey of the mapping path corresponding to the target subkey in the virtual registry space corresponding to the cloud application, and returns the merged result.

9. The device according to claim 6, characterized in that The mapping unit is further used for: When the cloud application exits, all subkeys in the virtual registry space corresponding to the cloud application are deleted.

10. The device according to claim 6, characterized in that The mapping unit is further used for: Caches the cloud application's operation information on the target subkey.

Images