Multi-system data isolation method and device, equipment and storage medium

Abstract

The invention provides a multi-system data isolation method and device, equipment and a storage medium. The method is applied to a user terminal and comprises the following steps: in response to a received system creation instruction triggered by a user, creating a plurality of operating systems and a control system; the control system comprises operating system data files respectively created for each operating system; obtaining partition information of the target disk; determining disk sub-partitions with a mapping relation for each operating system data file based on the partition information; and in response to user data generated by a user based on any operating system, storing the user data to the disk sub-partitions of the corresponding operating system data files so as to realize data isolation of each operating system. According to the method and the device, the respective disk sub-partitions are allocated to the operating systems and used for storing the user data generated by the operating systems, so that the data can be isolated by storing the user data generated by the operating systems to the corresponding disk sub-partitions, and the interference of the user data is reduced.

Description

Technical Field

[0001] This application relates to computer technology, and in particular, to a method, apparatus, device, and storage medium for data isolation of multiple systems. Background Art

[0002] With the development of the Internet, terminals such as mobile phones and computers have become a powerful communication tool in society and life and are favored by users. A terminal can carry multiple different systems, and each system can support the work of the corresponding system.

[0003] In the prior art, a user terminal creates two operating systems and a control system, and the user terminal uses the control system to control the user data of the two operating systems to be stored in the corresponding disk partitions.

[0004] However, the user data of the two operating systems is stored in the disk, which may cause one operating system to read the user data corresponding to the other operating system, so there is interference between user data. Summary of the Invention

[0005] This application provides a method, apparatus, device, and storage medium for data isolation of multiple systems, which is used to solve the problem that the user data of two operating systems is stored in the disk, which may cause one operating system to read the user data corresponding to the other operating system, so there is interference between user data.

[0006] In a first aspect, this application provides a method for data isolation of multiple systems. The method is applied to a user terminal and includes:

[0007] In response to receiving a system creation instruction triggered by a user, create multiple operating systems and a control system; the control system includes operating system data files created for each operating system respectively;

[0008] Obtain the partition information of the target disk;

[0009] Based on the partition information, determine disk sub-partitions with a mapping relationship for each operating system data file;

[0010] In response to the user generating user data based on any operating system, store the user data in the disk sub-partition of the corresponding operating system data file to implement data isolation for each operating system.

[0011] In one way, the partition information includes the carrying capacity of each disk sub-partition in the target disk;

[0012] The determining disk sub-partitions with a mapping relationship for each operating system data file based on the partition information includes:

[0013] Obtain the required load capacity preset for each operating system;

[0014] Based on the load capacity of each disk sub - partition and the required load capacity, determine the disk sub - partitions that have a mapping relationship with the data files of each operating system.

[0015] In one way, the determining the disk sub - partitions that have a mapping relationship with the data files of each operating system based on the load capacity of each disk sub - partition and the required load capacity includes:

[0016] According to the principle of ascending load capacity, sequentially determine the respective disk sub - partitions for the operating systems corresponding to each required load capacity from the load capacities of each disk sub - partition;

[0017] Determine the disk sub - partition of the operating system as the disk sub - partition that has a mapping relationship with the corresponding operating system data file.

[0018] In one way, the sequentially determining the respective disk sub - partitions for the operating systems corresponding to each required load capacity from the load capacities of each disk sub - partition according to the principle of ascending load capacity includes:

[0019] Obtain the smallest required load capacity from the required load capacities according to the principle of ascending load capacity;

[0020] Determine the load capacity of the disk sub - partition that is greater than and closest to the smallest required load capacity from the load capacities of each disk sub - partition, and determine the corresponding disk sub - partition as the disk sub - partition of the operating system corresponding to the smallest required load capacity;

[0021] Continue to determine the disk sub - partitions corresponding to the remaining operating systems from the load capacities of the remaining disk sub - partitions according to the principle of ascending load capacity from the remaining required load capacities.

[0022] In one way, after determining the disk sub - partitions that have a mapping relationship with the data files of each operating system based on the partition information, it includes:

[0023] Store the created mapping relationship information in the control system; the mapping relationship information includes the disk sub - partition information that has a mapping relationship with the data files of each operating system.

[0024] In one way, the storing the user data in the disk sub - partitions corresponding to the data files of each operating system to achieve data isolation for each operating system includes:

[0025] Send the user data to the control system; the user data includes the corresponding operating system identifier;

[0026] Using the control system, determine the corresponding operating system data file based on the operating system identifier, and determine the disk subpartition where the user data is to be stored based on the mapping relationship information;

[0027] Using the control system, send the user data to the disk subpartition to be stored and store it.

[0028] In one approach, the method includes:

[0029] In response to an upgrade instruction triggered by any operating system, use the control system to determine the disk subpartition corresponding to the operating system to be upgraded, and obtain the upgrade installation package corresponding to the operating system to be upgraded from the disk subpartition;

[0030] Send the upgrade installation package to the operating system to be upgraded so that the operating system to be upgraded completes the upgrade operation;

[0031] The method further includes:

[0032] Receive a factory-level factory reset instruction; the factory-level factory reset instruction includes the operating system identifier to be factory reset;

[0033] Using the control system, determine the disk subpartition to be factory reset corresponding to the operating system to be factory reset based on the operating system identifier to be factory reset;

[0034] Format all user data in the disk subpartition to be factory reset to implement the factory reset of the operating system to be factory reset.

[0035] In a second aspect, the present application provides a multi-system data isolation device, which is located in a user terminal. The device includes:

[0036] A creation module, configured to create multiple operating systems and a control system in response to receiving a system creation instruction triggered by a user; the control system includes operating system data files created for each operating system respectively;

[0037] An acquisition module, configured to acquire partition information of a target disk;

[0038] A determination module, configured to determine disk subpartitions with a mapping relationship for each operating system data file based on the partition information;

[0039] A storage module, configured to store the user data in the disk subpartition corresponding to the corresponding operating system data file in response to the user generating user data based on any operating system, so as to implement data isolation for each operating system.

[0040] In a third aspect, the present application provides a user terminal, including: a processor, and a memory communicatively connected to the processor;

[0041] The memory stores computer-executable instructions;

[0042] The processor executes the computer-executable instructions stored in the memory to implement the method described in the first aspect or any of the above manners.

[0043] In a fourth aspect, the present application provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the method described in the first aspect or any of the above manners when executed by a processor.

[0044] The present application provides a method, apparatus, device, and storage medium for data isolation in multiple systems. The method of the present application is applied to a terminal and includes: the user terminal receives a system creation instruction to create multiple operating systems and a control system, where the control system includes operating system data files created for each operating system respectively. Further, the user terminal obtains partition information of the target disk, and then determines disk sub-partitions with a mapping relationship for each operating system data file based on the partition information. In response to user data generated by the user based on any operating system, the user data is stored in the disk sub-partition corresponding to the operating system data file of the corresponding operating system. Thus, the present application realizes allocating respective disk sub-partitions for each operating system, and the disk sub-partitions are used to store user data generated by each operating system. Therefore, storing user data generated by each operating system in the disk sub-partition corresponding to the operating system can isolate the data and reduce the interference of user data of each operating system. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0046] Figure 1 It is an application scenario diagram of a method for data isolation in multiple systems provided by the present application;

[0047] Figure 2 It is a schematic flowchart of a method for data isolation in multiple systems provided in Embodiment 1;

[0048] Figure 3 It is a schematic flowchart of a method for data isolation in multiple systems provided in Embodiment 2;

[0049] Figure 4 It is a schematic flowchart of a method for data isolation in multiple systems provided in Embodiment 3;

[0050] Figure 5 Schematic diagram of a data isolation method for multiple systems provided for Example 4;

[0051] Figure 6 Schematic diagram of a data isolation method for multiple systems provided for Example 6;

[0052] Figure 7 Schematic diagram of a data isolation method for multiple systems provided for Example 7;

[0053] Figure 8 Another schematic diagram of a data isolation method for multiple systems provided for Example 7;

[0054] Figure 9 Diagram of the relationship between multiple systems in a user terminal provided for Example 7;

[0055] Figure 10 Diagram of the relationship between multiple systems in the prior art;

[0056] Figure 11 Schematic diagram of a data isolation device for multiple systems provided for Example 8;

[0057] Figure 12 Schematic diagram of the structure of a user terminal provided for Example 9.

[0058] Through the above-mentioned drawings, the specific embodiments of the present application have been shown, and there will be more detailed descriptions hereinafter. These drawings and the textual descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. Detailed implementation manners

[0059] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present application. On the contrary, they are merely examples of the devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0060] In the prior art, a user terminal creates two operating systems and a control system, and the user terminal uses the control system to control the user data of the two operating systems to be stored in the corresponding disk partitions.

[0061] However, the user data of the two operating systems is stored in the disk, which may cause one operating system to read the user data corresponding to the other operating system, so there is interference between user data.

[0062] To address the deficiencies of the prior art, the inventors of this solution conducted creative research and designed a new solution. This solution provides a data isolation method for multiple systems. To solve the problem that when the user data of two operating systems is stored on a disk, it may cause one operating system to read the user data corresponding to the other operating system, resulting in interference between user data, this solution creates multiple operating systems and a control system on the user terminal. In the control system, there are operating system data files created for each operating system respectively. Then, the partition information of the target disk is obtained, and based on the partition information, disk sub-partitions with a mapping relationship are determined for each operating system data file. Thus, this solution determines the disk sub-partitions corresponding to each operating system data file, that is, determines the disk sub-partitions for the user data corresponding to each operating system. Therefore, when any operating system generates user data, the user data is stored in the disk sub-partition of the corresponding operating system data file. Since it is stored in the disk sub-partition of the corresponding operating system data file, this solution can store user data in a partitioned manner according to the operating system, thereby achieving data isolation for each operating system and reducing interference from user data of different operating systems.

[0063] The following introduces the application scenarios of a data isolation method, device, equipment, and storage medium for multiple systems provided by this application.

[0064] Figure 1 This is an application scenario diagram of a data isolation method for multiple systems provided by this application. As Figure 1 shown, this application scenario diagram includes a user terminal 101.

[0065] Among them, the user terminal 101 can be a device such as a mobile phone or a computer, and there is no limitation here.

[0066] Specifically, in this scenario, the user triggers a system creation instruction through the operation interface of the user terminal 101, and thus the user terminal 101 receives the system creation instruction.

[0067] Furthermore, the user terminal 101 creates multiple operating systems and a control system. Among them, the control system includes operating system data files created for each operating system respectively.

[0068] Furthermore, the user terminal 101 obtains the partition information of the target disk and determines disk sub-partitions with a mapping relationship for each operating system data file based on the partition information.

[0069] Furthermore, the user terminal 101 stores the user data in the disk sub-partition of the corresponding operating system data file in response to the user generating user data based on any operating system.

[0070] It should be noted that if there are multiple operating systems including a first operating system and a second operating system, the control system includes a first operating system data file corresponding to the first operating system and a second operating system data file corresponding to the second operating system.

[0071] Exemplarily, if a user generates user data based on the first operating system, the user terminal stores the user data in the disk subpartition corresponding to the first operating system data file; similarly, if the user generates user data based on the second operating system, the user terminal stores the user data in the disk subpartition corresponding to the second operating system data file, thereby achieving data isolation for each operating system.

[0072] A multi-system data isolation method provided by this application aims to solve the above technical problems in the prior art.

[0073] The following uses specific embodiments to elaborate in detail on the technical solution of this application and how the technical solution of this application solves the above technical problems. These specific embodiments below can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0074] Embodiment 1

[0075] The execution subject of Embodiment 1 to Embodiment 7 of this application is a multi-system data isolation device (hereinafter referred to as the isolation device), and this isolation device is located in the user terminal.

[0076] Figure 2 It is a schematic flowchart of a multi-system data isolation method provided for Embodiment 1. As Figure 2 shown, the specific steps are as follows.

[0077] S201, in response to receiving a system creation instruction triggered by a user, create multiple operating systems and a control system; the control system includes operating system data files respectively created for each operating system.

[0078] Among them, the system creation instruction refers to an instruction for creating a system.

[0079] Among them, the operating system refers to a working system, and the control system refers to a system for controlling various aspects of the operating system.

[0080] Among them, the operating system data file refers to a storage file for user data corresponding to the operating system. It should be noted that the user data in the operating system data file is actually stored on their respective corresponding disk subpartitions, and the storage of user data is carried out with the disk as the carrier. It is possible to know which user data is in the operating system data file.

[0081] It should be noted that assuming that there are multiple operating systems including a first operating system and a second operating system, the control system includes a first operating system data file corresponding to the first operating system and a second operating system data file corresponding to the second operating system.

[0082] S202. Obtain the partition information of the target disk.

[0083] The partition information of the target disk refers to the size information of each disk sub - partition of the target disk carried in the user terminal.

[0084] In one way, the partition information of the target disk is pre - stored locally in the user terminal. The user terminal obtains the partition information of the target disk from the local.

[0085] It should be noted that multiple disks can be carried in the user terminal, and one of the disks can be the target disk, and the target disk is used to store the user data of each operating system.

[0086] S203. Based on the partition information, determine the disk sub - partitions with a mapping relationship for each operating system data file.

[0087] In one way, the user mainly determines the disk sub - partitions with a mapping relationship for each operating system data file based on the size of each disk sub - partition in the partition information.

[0088] It should be noted that, by way of example, assuming that the target disk includes a first disk sub - partition, a second disk sub - partition, a third disk sub - partition, and a fourth disk sub - partition, the user terminal determines that the disk sub - partition with a mapping relationship for the first operating system data file is the first disk sub - partition according to the size of each disk sub - partition in the partition information, and the disk sub - partition with a mapping relationship for the second operating system data file is the second disk sub - partition.

[0089] S204. In response to the user generating user data based on any operating system, store the user data in the disk sub - partition of the corresponding operating system data file to achieve data isolation for each operating system.

[0090] Any operating system here means any one or more operating systems.

[0091] User data refers to the data related to the user generated by the operating system.

[0092] By way of example, if the user generates user data through the first operating system, the user terminal stores the user data in the disk sub - partition corresponding to the first operating system data file.

[0093] This embodiment provides a data isolation method for multiple systems. The method of this embodiment is applied to a terminal and includes: the user terminal receives a system creation instruction, thereby creating multiple operating systems and a control system. Among them, the control system includes operating system data files created for each operating system respectively. Further, the user terminal obtains the partition information of the target disk, and then determines disk sub-partitions with a mapping relationship for each operating system data file based on the partition information. In response to the user generating user data based on any operating system, the user data is stored in the disk sub-partition corresponding to the corresponding operating system data file, and the corresponding operating system data file corresponds to this operating system. Thus, this embodiment realizes the allocation of respective disk sub-partitions for each operating system, and these disk sub-partitions are used to store the user data generated by each operating system. Therefore, storing the user data generated by each operating system in the disk sub-partition corresponding to this operating system can isolate the data and reduce the interference of the user data of each operating system.

[0094] Embodiment 2

[0095] This embodiment is a further refinement of any of the above embodiments. In this embodiment, the partition information includes the carrying capacity of each disk sub-partition in the target disk.

[0096] In one way, assume that the target disk includes a first disk sub-partition, a second disk sub-partition, a third disk sub-partition, and a fourth disk sub-partition. Then, the partition information includes the carrying capacity of the first disk sub-partition, the carrying capacity of the second disk sub-partition, the carrying capacity of the third disk sub-partition, and the carrying capacity of the fourth disk sub-partition.

[0097] An optional way in this embodiment to determine disk sub-partitions with a mapping relationship for each operating system data file based on the partition information.

[0098] Figure 3 A schematic flow diagram of a data isolation method for multiple systems provided for Embodiment 2. As Figure 3 shown, the specific steps are as follows.

[0099] S301, obtain the required carrying capacity preset for each operating system.

[0100] Among them, the required carrying capacity refers to the capacity required by the operating system. Among them, the carrying capacity can be in units of GB or MB.

[0101] It should be noted that after creating multiple operating systems, the user can preset the required carrying capacity corresponding to each operating system for each operating system, and the user inputs each required carrying capacity through the operation interface of the user terminal. The user terminal receives the required carrying capacity of each operating system and stores it locally.

[0102] S302. Determine the disk sub - partitions with mapping relationships for each operating system's data files based on the carrying capacity of each disk sub - partition and the required carrying capacity.

[0103] Further, the user terminal determines the disk sub - partitions to which each operating system's data files have mapping relationships based on the sizes of the carrying capacities of each disk sub - partition and the required carrying capacities.

[0104] This embodiment provides a multi - system data isolation method. In this embodiment, the partition information includes the carrying capacity of each disk sub - partition in the target disk. The user terminal first obtains the required carrying capacities preset by each operating system, and then determines the disk sub - partitions with mapping relationships for each operating system's data files based on the carrying capacity of each disk sub - partition and the required carrying capacity, thereby determining the corresponding disk sub - partitions for each operating system, which is conducive to data isolation.

[0105] Embodiment Three

[0106] This embodiment is a further refinement of any of the above embodiments and is an optional way to determine the disk sub - partitions with mapping relationships for each operating system's data files based on the carrying capacity of each disk sub - partition and the required carrying capacity.

[0107] Figure 4 It is a schematic flowchart of a multi - system data isolation method provided for Embodiment Three. As Figure 3 shown, the specific steps are as follows.

[0108] S401. Sequentially determine the respective disk sub - partitions for each operating system corresponding to each required carrying capacity from the carrying capacities of each disk sub - partition in ascending order of the carrying capacity.

[0109] S402. Determine the disk sub - partition of the operating system as the disk sub - partition with mapping relationships for the corresponding operating system's data files.

[0110] It should be noted that there is a corresponding relationship between the operating system and the operating system's data files, and there is also a corresponding relationship between the operating system and its respective disk sub - partitions. Thus, the disk sub - partition corresponding to the operating system can be determined as the disk sub - partition with mapping relationships for the operating system's data files corresponding to this operating system.

[0111] Table 1: Relationships of disk sub - partitions.

[0112]

[0113] As shown in Table 1, the first operating system corresponds to the first operating system data file, and at the same time, the first operating system corresponds to the first disk sub - partition. Therefore, the first operating system data file corresponds to the first disk sub - partition. Similarly, the second operating system corresponds to the second operating system data file, and at the same time, the second operating system corresponds to the second disk sub - partition. Therefore, the second operating system data file corresponds to the second disk sub - partition.

[0114] This embodiment provides a method for data isolation of multiple systems. In this embodiment, the user terminal determines the respective disk sub - partitions for the operating systems corresponding to each required capacity in turn from the capacities of each disk sub - partition according to the principle of increasing capacity from small to large. Then, the disk sub - partition of the operating system is determined as the disk sub - partition that has a mapping relationship with the corresponding operating system data file. Thus, the present application can orderly determine the disk sub - partitions that have a mapping relationship with each operating system data file.

[0115] Embodiment Four

[0116] This embodiment is a further refinement of any of the above - mentioned embodiments. This embodiment is an optional way to determine the respective disk sub - partitions for the operating systems corresponding to each required capacity in turn from the capacities of each disk sub - partition according to the principle of increasing capacity from small to large.

[0117] Figure 5 It is a schematic flowchart of a method for data isolation of multiple systems provided for Embodiment Four. As Figure 5 shown, the specific steps are as follows.

[0118] S501, obtain the smallest required capacity from the required capacities according to the principle of increasing capacity from small to large.

[0119] Exemplarily, assume that the required capacity of the first operating system is the first capacity, and the required capacity of the second operating system is the second capacity, where the first capacity is less than the second capacity.

[0120] Further, the user terminal obtains the smallest required capacity from the two required capacities according to the principle of increasing capacity from small to large, that is, the required capacity of the first operating system.

[0121] S502, determine the capacity of the disk sub - partition that is greater than and closest to the smallest required capacity from the capacities of each disk sub - partition, and determine the corresponding disk sub - partition as the disk sub - partition of the operating system corresponding to the smallest required capacity.

[0122] Exemplarily, assume that the capacities of the four disk sub - partitions are the first sub - partition capacity, the second sub - partition capacity, the third sub - partition capacity, and the fourth sub - partition capacity respectively.

[0123] Further, the user terminal determines from the capacities of the four disk sub - partitions that the capacities of the first sub - partition and the second sub - partition are greater than the required capacity of the first operating system. At the same time, the user terminal determines that the capacity of the first sub - partition is the closest to the required capacity of the first operating system. Thus, it is determined that the capacity of the disk sub - partition that is greater than and closest to the smallest required capacity is the capacity of the first sub - partition. The user terminal determines the disk sub - partition (i.e., the first disk sub - partition) corresponding to this disk sub - partition capacity as the disk sub - partition of the operating system corresponding to the smallest required capacity (i.e., the first operating system).

[0124] S503. Continue to determine the disk sub - partitions corresponding to the remaining operating systems from the remaining disk sub - partition capacities in ascending order of capacity according to the remaining required capacity.

[0125] Among them, the remaining required capacity refers to the required capacity of the operating system for which the disk sub - partition has not been determined. Exemplarily, according to the above steps, the disk sub - partition corresponding to the first operating system has been determined, and further, the disk sub - partition corresponding to the second operating system has not been determined yet. So the remaining required capacity is the required capacity of the second operating system.

[0126] Among them, the remaining disk sub - partitions refer to the remaining disk sub - partitions that have not been determined as operating systems. Exemplarily, according to the above steps, the disk sub - partition corresponding to the first operating system is determined as the first disk sub - partition. Thus, the remaining disk sub - partitions are the second disk sub - partition, the third disk sub - partition, and the fourth disk sub - partition.

[0127] Among them, the remaining operating systems refer to the operating systems for which the disk sub - partitions have not been determined. Exemplarily, according to the above steps, the disk sub - partition of the first operating system is determined. Thus, the remaining operating system is the second operating system.

[0128] Further, the user terminal determines based on the remaining required capacity and the remaining disk sub - partitions according to the method steps of S501 - S502

[0129] This embodiment provides a multi - system data isolation method. In this embodiment, the user terminal obtains the smallest required capacity from the required capacities in ascending order of capacity. Further, it determines the capacity of the disk sub - partition that is greater than and closest to the smallest required capacity from the capacities of each disk sub - partition. Therefore, a more suitable disk sub - partition for the operating system can be determined. The disk sub - partition of the operating system can bear the required capacity of the operating system, and at the same time, the space of this disk sub - partition is not wasted. So in this embodiment, a more suitable disk sub - partition for the operating system is found.

[0130] Embodiment Five

[0131] This embodiment is a further refinement of any of the above embodiments. This embodiment is an optional method after determining disk sub - partitions with mapping relationships for each operating system data file based on partition information.

[0132] Store the created mapping relationship information in the control system; the mapping relationship information includes disk sub - partition information with mapping relationships for each operating system data file.

[0133] It should be noted that the control system can be used to control the normal operation of the operating system. Therefore, storing the mapping relationship information in the control system is beneficial for the control system to control the operating system.

[0134] This embodiment provides a data isolation method for multiple systems. Storing the mapping relationship information in the control system is beneficial for the control system to control the operating system.

[0135] Embodiment Six

[0136] This embodiment is a further refinement of any of the above embodiments. This embodiment is an optional method of storing user data in the disk sub - partitions corresponding to each operating system data file to achieve data isolation for each operating system.

[0137] Figure 6 It is a schematic flow diagram of a data isolation method for multiple systems provided in Embodiment Six. As Figure 6 shown, the specific steps are as follows.

[0138] S601, Send the user data to the control system; the user data includes the corresponding operating system identifier.

[0139] Among them, the operating system identifier refers to the name of the operating system or other unique identification codes, etc., which is not limited here.

[0140] Exemplarily, the user generates corresponding user data through the first operating system installed in the user terminal. Further, the user terminal sends the user data to the control system.

[0141] S602, Use the control system to determine the corresponding operating system data file based on the operating system identifier, and determine the disk sub - partition where the user data is to be stored based on the mapping relationship information.

[0142] Further, the control system reads the corresponding operating system identifier in the user data, and then determines the operating system data file where the user data is stored, that is, the first operating system data file.

[0143] Further, the control system obtains the mapping relationship information and determines that the disk sub - partition with a mapping relationship to the first operating system data file is the first disk sub - partition, so as to determine that the disk sub - partition where the user data is to be stored is the first disk sub - partition.

[0144] S603. Use the control system to send user data to the disk sub - partition to be stored and store it.

[0145] Furthermore, the control system receives the user data sent by the first operating system, stores the user data in the disk sub - partition to be stored, and can be displayed in the first operating system data file.

[0146] It should be noted that this embodiment illustrates that the user terminal can differentially send and store the user data of the operating system to the corresponding disk sub - partitions.

[0147] This embodiment provides a data isolation method for multiple systems. In this embodiment, the user data is sent to the control system. Since the user data includes the corresponding operating system identifier, the control system is used to determine the corresponding operating system data file, and based on the mapping relationship information, the disk sub - partition where the user data is to be stored is determined. Therefore, in this embodiment, the user data is sent and stored in the disk sub - partition to be stored. Since the user data generated by each operating system is stored in the corresponding disk sub - partition, data isolation is achieved, and the data interference between each operating system is reduced.

[0148] Embodiment Seven

[0149] This embodiment is a further refinement of any of the above embodiments.

[0150] Figure 7 It is a schematic flow diagram of a data isolation method for multiple systems provided for Embodiment Seven. As Figure 7 shown, the specific steps are as follows.

[0151] S701. In response to an upgrade instruction triggered by any operating system, use the control system to determine the disk sub - partition corresponding to the operating system to be upgraded, and obtain the upgrade installation package corresponding to the operating system to be upgraded from the disk sub - partition.

[0152] In one way, the user triggers an upgrade instruction in the first operating system through the user terminal.

[0153] In one way, the user triggers an upgrade instruction for the first operating system of the user terminal through another device, and the other device sends the upgrade instruction of the first operating system to the user terminal.

[0154] Further, the user terminal receives an upgrade instruction, which includes the identifier of the operating system to be upgraded (assumed to be the first operating system identifier). Thus, the control system reads the upgrade instruction and determines the identifier of the operating system to be upgraded (i.e., the first operating system identifier) from the upgrade instruction. Further, according to the identifier of the operating system to be upgraded, the corresponding disk sub-partition (i.e., the first disk sub-partition) of the operating system to be upgraded (i.e., the first operating system) is determined. Thus, the control system obtains the upgrade installation package of the operating system to be upgraded from the above disk sub-partition (i.e., the first disk sub-partition).

[0155] S702, Send the upgrade installation package to the operating system to be upgraded so that the operating system to be upgraded can complete the upgrade operation.

[0156] Further, the user terminal sends the upgrade installation package to the operating system to be upgraded, so that the user terminal completes the upgrade operation for the operating system to be upgraded based on the upgrade installation package.

[0157] It should be noted that this embodiment illustrates that the user terminal can obtain user data from the disk sub-partitions corresponding to the respective operating systems differently. In this embodiment, the user data can be the upgrade installation package.

[0158] This embodiment provides a method for data isolation of multiple systems. In this embodiment, the user terminal can implement the upgrade operation for the operating system to be upgraded.

[0159] Figure 8 It is a schematic flowchart of another method for data isolation of multiple systems provided for Embodiment 7. As Figure 8 shown, the specific steps are as follows.

[0160] S801, Receive the factory-level factory reset instruction; the factory-level factory reset instruction includes the identifier of the operating system to be factory reset.

[0161] Among them, the factory-level factory reset instruction refers to an instruction that makes multiple operating systems in the user terminal restore to the factory settings at the factory level.

[0162] In one way, the user can generate a factory-level factory reset instruction through another device, and the other device sends the factory-level factory reset instruction to the user terminal.

[0163] Among them, the operating system to be factory reset refers to the identifier of the operating system to be factory reset. Exemplarily, assuming that the first operating system is the operating system to be factory reset, then the operating system to be factory reset is the first operating system identifier.

[0164] S802, Use the control system to determine the disk sub-partition to be factory reset corresponding to the operating system to be factory reset based on the identifier of the operating system to be factory reset.

[0165] Further, the control system reads the operating system identifier to be restored to the factory settings from the factory-level restore-to-factory settings instruction, so as to determine the operating system to be restored to the factory settings. Further, the control system obtains the mapping relationship information and determines the disk sub-partition corresponding to the operating system to be restored to the factory settings from the mapping relationship information, and this disk sub-partition is the disk sub-partition to be restored to the factory settings.

[0166] Wherein, the disk sub-partition to be restored to the factory settings refers to the disk sub-partition that is about to be restored to the factory settings.

[0167] S803, format all user data in the disk sub-partition to be restored to the factory settings, so as to implement the restore-to-factory settings of the operating system to be restored to the factory settings.

[0168] Further, the user terminal formats all user data in the disk sub-partition to be restored to the factory settings, thus implementing the restore-to-factory settings of the operating system to be restored to the factory settings.

[0169] Exemplarily, assume that the operating system to be restored to the factory settings is the first operating system, then the disk sub-partition to be restored to the factory settings is the first disk sub-partition. Therefore, the user terminal formats the user data in the first disk sub-partition, thus implementing the restore-to-factory settings of the first operating system.

[0170] It should be noted that in the prior art, to clear the user data corresponding to the operating system, the user data of this operating system is deleted.

[0171] This embodiment provides a multi-system data isolation method. In this embodiment, the user terminal receives the factory-level restore-to-factory settings instruction, and then the control system determines the operating system to be restored to the factory settings and determines the corresponding disk sub-partition to be restored to the factory settings. Further, format all user data in the disk sub-partition to be restored to the factory settings, and all implement the restore-to-factory settings of the operating system to be restored to the factory settings.

[0172] This embodiment provides a multi-system data isolation method. In this embodiment, the corresponding operating system to be restored to the factory settings is determined according to the operating system identifier to be restored to the factory settings, and the disk sub-partition to be restored to the factory settings corresponding to the operating system to be restored to the factory settings is determined.

[0173] Figure 9 It is a relationship diagram of multiple systems in a user terminal provided for Embodiment 7. As Figure 9 shown, the user terminal 900 specifically includes a first operating system 901, a second operating system 902, a control system 903, and a target disk 904.

[0174] Among them, the first operating system 901 includes a first root file 9011. Under the first root file 9011, there are a first data file 9012, a first system file 9013, and a first base file 9014. Among them, the first system file 9013 and the first base file 9014 include fixed data information about the first operating system 901 and the user terminal 900, such as the supplier identifier, etc.

[0175] Among them, the second operating system 902 includes a second root file 9021. Under the second root file 9021, there are a second data file 9022, a second system file 9023, and a second base file 9024. Among them, the second system file 9023 and the second base file 9024 include fixed data information about the second operating system 902 and the user terminal 900, such as the supplier identifier, etc.

[0176] Among them, the control system 903 includes a control root file 9031, a first operating system data file 9032, a second operating system data file 9033, a control system data file 9034, a control system file 9035, and a control base file 9036. Among them, the control system file 9035 and the control base file 9036 include fixed data information about the control system 903 and the user terminal 900.

[0177] Among them, the target disk 904 includes a first disk sub - partition 9041, a second disk sub - partition 9042, a third disk sub - partition 9043, and a fourth disk sub - partition 9044.

[0178] Among them, the first operating system data file 9032 is partition - mounted on the first disk sub - partition 9041, the second operating system data file 9033 is partition - mounted on the second disk sub - partition 9042, the control system data file 9034 is partition - mounted on the third disk sub - partition 9043, and the control system file 9035 and the control base file 9036 are partition - mounted on the fourth disk sub - partition.

[0179] It should be noted that the user terminal of this application uses a preset container technology to create the operating system and the control system.

[0180] Figure 10 It is a relationship diagram of multiple systems in the prior art. As Figure 10 shown, in the prior art, the user terminal 1000 includes a first operating system 1001, a second operating system 1002, and a control system 1003.

[0181] Among them, the first operating system 1001 includes a first root file 10011. Under the first root file 10011, there are a first data file 10012, a first system file 10013, and a first base file 10014. Among them, the first system file 10013 and the first base file 10014 include data information fixed for the first operating system 10011 and the user terminal 1000 in the prior art, such as supplier identification, etc.

[0182] Among them, the second operating system 1002 includes a second root file 10021. Under the second root file 10021, there are a second data file 10022, a second system file 10023, and a second base file 10024. Among them, the second system file 10023 and the second base file 10024 include data information fixed for the second operating system 1002 and the user terminal 1000 in the prior art, such as supplier identification, etc.

[0183] Among them, the control system 1003 includes a control root file 10031. Under the control root file 10031, there are a control system data file 10032, a control system file 10033, and a control base file 10034. Under the control system data file 10032, there are a first operating system data file 10035 and a second operating system data file 10036. Among them, the control system file 10033 and the control base file 10034 include data information fixed for the control system 1003 and the user terminal 1000 in the prior art.

[0184] Among them, the target disk 1004 includes a user data disk partition 10041 and other disk partitions 10042.

[0185] Among them, the control system data file 10032 is partition-mounted on the user data disk partition 10041, and the control system file 10033 and the control base file 10034 are partition-mounted on the other disk partitions 10042.

[0186] According to Figure 9 and Figure 10 It can be seen that in the prior art, separate disk sub-partitions are not allocated for the first operating system and the second operating system. Instead, only one user data disk partition 10041 is allocated to store all the user data of the first operating system 1001, the second operating system 1002, and the control system 1003, so there is data interference between them.

[0187] In this application, a disk sub-partition is allocated for each of the first operating system 1001, the second operating system 1002, and the control system 1003 to store the corresponding user data.

[0188] It should be noted that Figure 9 and Figure 10 the dotted lines in represent the mapping relationship.

[0189] Embodiment VIII

[0190] The following is the device embodiment provided by the present application. Figure 11 A schematic diagram of a multi-system data isolation device provided for Embodiment VIII. The isolation device 1100 is located at the user terminal, and the isolation device includes the following modules:

[0191] A creation module 1101, configured to create multiple operating systems and a control system in response to receiving a system creation instruction triggered by a user; the control system includes operating system data files respectively created for each operating system;

[0192] An acquisition module 1102, configured to acquire partition information of a target disk;

[0193] A determination module 1103, configured to determine disk sub-partitions with a mapping relationship for each operating system data file based on the partition information;

[0194] A storage module 1104, configured to store user data in the disk sub-partition corresponding to the operating system data file in response to user data generated by the user based on any operating system, so as to implement data isolation for each operating system.

[0195] In one way, the partition information includes the carrying capacity of each disk sub-partition in the target disk;

[0196] The determination module 1103, when determining disk sub-partitions with a mapping relationship for each operating system data file based on the partition information, specifically is configured to:

[0197] Acquire the required carrying capacity preset for each operating system;

[0198] Determine disk sub-partitions with a mapping relationship for each operating system data file based on the carrying capacity of each disk sub-partition and the required carrying capacity.

[0199] In one way, the determination module 1103, when determining disk sub-partitions with a mapping relationship for each operating system data file based on the carrying capacity of each disk sub-partition and the required carrying capacity, specifically is configured to:

[0200] Sequentially determine respective disk sub-partitions for each operating system corresponding to each required carrying capacity from the carrying capacities of each disk sub-partition in ascending order of the carrying capacity;

[0201] Determine the disk sub-partition of the operating system as the disk sub-partition with a mapping relationship for the corresponding operating system data file.

[0202] In one way, the determining module 1103, when determining respective disk sub - partitions for each operating system corresponding to each required capacity in ascending order of capacity from the capacities of each disk sub - partition, is specifically configured to:

[0203] Obtain the smallest required capacity from the required capacities in ascending order of capacity;

[0204] Determine the capacity of the disk sub - partition that is greater than and closest to the smallest required capacity from the capacities of each disk sub - partition, and determine the corresponding disk sub - partition as the disk sub - partition for the operating system corresponding to the smallest required capacity;

[0205] Continue to determine the disk sub - partitions corresponding to the remaining operating systems from the capacities of the remaining disk sub - partitions in ascending order of capacity from the remaining required capacities.

[0206] In one way, the storage module 1104, after determining the disk sub - partitions with mapping relationships for each operating system data file based on the partition information, is specifically further configured to:

[0207] Store the created mapping relationship information in the control system; the mapping relationship information includes the disk sub - partition information with mapping relationships for each operating system data file.

[0208] In one way, the storage module 1104, when storing user data in the disk sub - partitions corresponding to each operating system data file to achieve data isolation for each operating system, is specifically configured to:

[0209] Send the user data to the control system; the user data includes the corresponding operating system identifier;

[0210] Use the control system to determine the corresponding operating system data file based on the operating system identifier, and determine the disk sub - partition where the user data is to be stored based on the mapping relationship information;

[0211] Use the control system to send the user data to the disk sub - partition to be stored and store it.

[0212] In one way, this embodiment provides a multi - system data isolation device, which further includes: a sending module;

[0213] The determining module 1103 is further configured to, in response to an upgrade instruction triggered by any operating system, use the control system to determine the disk sub - partition corresponding to the operating system. The obtaining module 1102 is further configured to obtain the upgrade installation package corresponding to the operating system from the disk sub - partition;

[0214] The sending module is configured to send the upgrade installation package to the operating system to be upgraded so that the operating system to be upgraded completes the upgrade operation;

[0215] This embodiment provides a data isolation device for multiple systems, further comprising: a receiving module and a formatting module;

[0216] The receiving module is configured to receive a factory-level reset instruction, where the factory-level reset instruction includes an operating system identifier to be reset to factory settings;

[0217] The determining module 1103 is further configured to use the control system to determine the disk subpartition to be reset to factory settings corresponding to the operating system to be reset to factory settings based on the operating system identifier to be reset to factory settings;

[0218] The formatting module is configured to format all user data in the disk subpartition to be reset to factory settings, so as to implement the factory reset of the operating system to be reset to factory settings.

[0219] Embodiment Nine

[0220] Figure 12 A schematic structural diagram of a user terminal provided for Embodiment Nine is shown in FIG. Figure 12 As shown, the user terminal 1200 may include: a processor 1201 and a memory 1202 communicatively connected to the processor 1201. Among them, the memory 1202 stores computer execution instructions; the processor 1201 executes the computer execution instructions stored in the memory 1202 to implement any one of the method embodiments in Embodiments One to Seven as described above. The specific implementation manners and technical effects are similar and will not be elaborated here.

[0221] In this embodiment, the memory 1202 and the processor 1201 are connected through a bus. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 12 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0222] Embodiment Ten

[0223] The present application provides a computer-readable storage medium storing computer-executable instructions, which are used to implement any of the method embodiments of Embodiments 1 to 7 as described above when executed by a processor. The specific implementation manners and technical effects are similar and will not be elaborated here. Those skilled in the art will readily conceive of other implementation manners of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include known common general knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and embodiments are only regarded as exemplary, and the true scope and spirit of the present application are pointed out by the following claims.

[0224] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A method for data isolation in multiple systems, characterized in that, The method is applied to a user terminal, and the method includes: In response to receiving a system creation instruction triggered by a user, creating multiple operating systems and a control system; the control system includes operating system data files respectively created for each operating system; Obtaining partition information of a target disk; Based on the partition information, determining disk sub-partitions with a mapping relationship for each operating system data file; In response to user data generated by the user based on any operating system, storing the user data in the disk sub-partition of the corresponding operating system data file to achieve data isolation for each operating system.

2. The method according to claim 1, characterized in that, The partition information includes the carrying capacity of each disk sub-partition in the target disk; The determining disk sub-partitions with a mapping relationship for each operating system data file based on the partition information includes: Obtaining the required carrying capacity preset for each operating system; Based on the carrying capacity of each disk sub-partition and the required carrying capacity, determining disk sub-partitions with a mapping relationship for each operating system data file.

3. The method according to claim 2, characterized in that, The determining disk sub-partitions with a mapping relationship for each operating system data file based on the carrying capacity of each disk sub-partition and the required carrying capacity includes: According to the principle of ascending carrying capacity, sequentially determining respective disk sub-partitions for each operating system corresponding to each required carrying capacity from the carrying capacities of each disk sub-partition; Determining the disk sub-partition of the operating system as the disk sub-partition with a mapping relationship for the corresponding operating system data file.

4. The method according to claim 3, characterized in that, The sequentially determining respective disk sub-partitions for each operating system corresponding to each required carrying capacity from the carrying capacities of each disk sub-partition according to the principle of ascending carrying capacity includes: Obtaining the smallest required carrying capacity from the required carrying capacities according to the principle of ascending carrying capacity; Determining the carrying capacity of the disk sub-partition in each disk sub-partition that is greater than and closest to the smallest required carrying capacity, and determining the corresponding disk sub-partition as the disk sub-partition of the operating system corresponding to the smallest required carrying capacity; Continuing to determine the disk sub-partitions corresponding to the remaining operating systems from the carrying capacities of the remaining disk sub-partitions according to the principle of ascending carrying capacity from the remaining required carrying capacities.

5. The method according to claim 4, characterized in that, After determining disk sub-partitions with a mapping relationship for each operating system data file based on the partition information, it includes: Storing the created mapping relationship information in the control system; the mapping relationship information includes disk sub-partition information with a mapping relationship for each operating system data file.

6. The method according to claim 5, characterized in that, The storing the user data in the disk sub-partition corresponding to each operating system data file to achieve data isolation for each operating system includes: Sending the user data to the control system; the user data includes the corresponding operating system identifier; Using the control system to determine the corresponding operating system data file based on the operating system identifier, and determining the disk sub-partition where the user data is to be stored based on the mapping relationship information; Using the control system to send the user data to the disk sub-partition to be stored and storing it.

7. The method according to any one of claims 1 - 6, characterized in that, The method includes: In response to an upgrade instruction triggered by any operating system, a control system is used to determine the disk sub-partition corresponding to the operating system to be upgraded, and an upgrade installation package corresponding to the operating system to be upgraded is obtained from the disk sub-partition; The upgrade installation package is sent to the operating system to be upgraded so that the operating system to be upgraded completes the upgrade operation; The method further includes: Receiving a factory-level factory reset instruction; the factory-level factory reset instruction includes an operating system identifier to be factory reset; Using a control system to determine the disk sub-partition to be factory reset corresponding to the operating system to be factory reset based on the operating system identifier to be factory reset; Formatting all user data in the disk sub-partition to be factory reset to implement the factory reset of the operating system to be factory reset.

8. A data isolation device for multiple systems, characterized in that, The device is located in a user terminal, and the device includes: A creation module, configured to create a plurality of operating systems and a control system in response to receiving a system creation instruction triggered by a user; the control system includes operating system data files respectively created for each operating system; An acquisition module, configured to acquire partition information of a target disk; A determination module, configured to determine, based on the partition information, disk sub-partitions having a mapping relationship for each operating system data file; A storage module, configured to store the user data in the disk sub-partition corresponding to the corresponding operating system data file in response to the user generating user data based on any operating system, so as to implement data isolation for each operating system.

9. A user terminal, comprising: A processor and a memory communicatively connected to the processor; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory to implement the method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that Computer execution instructions are stored in the computer-readable storage medium, and when the computer execution instructions are executed by a processor, they are used to implement the method according to any one of claims 1-7.

Images