Multi-system control method of electronic equipment and electronic equipment
By generating the main operating system and multiple secondary operating systems, using the setting requirements information and the original sub-mirror in the main operating system to generate the secondary operating system, multi-system control is realized, and the problems of large storage space occupation and complex compatibility in the existing technology are solved, and the multi-system control effect with high security and storage space saving is achieved.
Patent Information
- Application Number
- CN202510088358.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-20
- Publication Date
- 2025-06-13
AI Technical Summary
When existing electronic devices implement multi-system control, the storage space occupies a large amount of storage space and the compatibility issues are more complex, which increases the risk of data leakage and security.
By generating the main operating system and multiple secondary operating systems, using the setting requirements information and the original sub-mirror in the main operating system to generate the secondary operating system, multi-system control is realized, storage space is saved, and the security of user data is improved through data partitioning.
It realizes multi-system control that saves storage space while ensuring security, solves compatibility problems, and improves the isolation and security of user data.
Smart Images

Figure CN120144189A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the technical field of multi - systems, and particularly to a multi - system control method and an electronic device for an electronic device. Background Art
[0002] With the continuous increase in the memory capacity of electronic devices, the storage space available to users is getting larger and larger. Therefore, an electronic device can support multiple users. For example, in the Android system, multiple users can be created, and different personal data can be created by switching different users. However, it is very easy to switch to other users, increasing the risk of data leakage.
[0003] In related technologies, multi - user operations can also be achieved through multi - systems. Taking the dual - system of Huawei mobile phones as an example, both EMUI and HarmonyOS operating systems are used at the same time. The two operating systems are independent, occupying a relatively large storage space, and compatibility issues also need to be considered. Summary of the Invention
[0004] In an exemplary embodiment of this application, a multi - system control method and an electronic device for an electronic device are provided to implement multi - system control of the electronic device, save storage space, and ensure security.
[0005] According to a first aspect of the exemplary embodiment, a multi - system control method for an electronic device is provided, including:
[0006] In response to an operating system switching request of a first user, display a first page; wherein, the first page includes N login controls; the N login controls are used to log in to N operating systems, each login control is used to log in to one operating system; the N operating systems include a main operating system and N - 1 secondary operating systems, and each secondary operating system is generated according to set requirement information and the main operating system;
[0007] In response to a click operation of the first user on the first login control in the first page, display an operation page of the first operating system; wherein, the first login control is a control for logging in to the first operating system; the first login control is any one of the N login controls, and the first operating system is any one of the N operating systems.
[0008] In an embodiment of the present application, N-1 secondary operating systems are generated according to set requirement information and a primary operating system. The N-1 secondary operating systems and a primary operating system can form N operating systems of an electronic device. Each login control can log in to one operating system, and N login controls can log in to N operating systems. The first user can be the primary user or other users. The electronic device responds to the operating system switching request of the first user and displays a first page including N login controls. The first login control can be used to log in to the first operating system. In this way, the electronic device responds to the click operation of the first user on the first login control in the first page and displays the first operating system. In this way, the first user can use the electronic device under the first operating system. Since each secondary system in the present application is generated according to set requirement information and the primary operating system, compared with multiple independent operating systems in the related art, storage space is saved. In addition, each user logs in to their respective operating systems, ensuring user data security at the same time.
[0009] In an alternative embodiment, the method further includes:
[0010] Analyze the set requirement information; wherein, the set requirement information includes N-1 set functions and data retention requirement information; the data retention requirement information indicates whether to retain user data during the process of switching different operating systems;
[0011] Generate N-1 secondary operating systems based on the set requirement information and M original sub-images included in the primary operating system;
[0012] Wherein, the type of the original sub-image is function type or user type; each secondary operating system includes M target sub-images; the M target sub-images include at least one original sub-image and / or at least one sub-image extended from the original sub-image; the M target sub-images include M1 function-type target sub-images and M2 user-type target sub-images, and the sum of M1 and M2 is M.
[0013] In the above embodiments, since the set requirement information includes N - 1 set functions and data retention information indicating whether to retain user data during the process of switching different operating systems, thus, for any set requirement information, the N - 1 set functions included therein and the information on whether user data needs to be retained can be determined. Additionally, since the types of the M original sub - images included in the main system include function - type and user - type, among the M target sub - images, there are M1 function - type target sub - images and M2 user - type target sub - images. Furthermore, different secondary systems can be generated according to the set requirement information and the data retention requirement information. The M target sub - images in the secondary system include at least one original sub - image and / or at least one sub - image extended from the original sub - image. Therefore, the generated secondary system incorporates the set functions in the set requirement information and the situation of whether to retain user data, without the need to expand all sub - images, saving storage space.
[0014] In an alternative embodiment, if the data retention requirement information indicates that user data needs to be cleared or there is no requirement, for each secondary system, the M1 function - type target sub - images include at least one sub - image extended from the function - type original sub - image, and the M2 user - type target sub - images are the user - type original sub - images.
[0015] If the data retention requirement information indicates that user data needs to be retained, for each secondary system, the M1 function - type target sub - images include at least one sub - image extended from the function - type original sub - image, and the M2 user - type target sub - images include at least one sub - image extended from the user - type original sub - image.
[0016] In the above embodiments, according to the situation where the data retention requirement information indicates that user data needs to be cleared, does not need to be cleared, and there is no requirement, it is determined whether user - type sub - images need to be expanded in the corresponding secondary system. Thus, in the case where the data retention requirement information indicates that user data needs to be cleared, the user - type sub - images are expanded to meet the user's needs; in the cases where the data retention requirement information indicates that user data does not need to be cleared and there is no requirement, there is no need to expand the user - type sub - images, saving storage space.
[0017] In an alternative embodiment, if the data retention requirement information indicates that user data needs to be retained, for the M2 user - type target sub - images, each target sub - image is stored in a data partition, and the data partitions for storing the respective target sub - images are different; among them, the user - type sub - images include user data sub - images and user metadata sub - images.
[0018] In the above embodiments, when the data retention requirement information indicates that user data needs to be retained, a data partition can be allocated to the target sub-images of each user class. Compared with the prior art where the user data in a single system with multiple users is stored in the same data partition, the data security is improved.
[0019] In an alternative embodiment, if among N - 1 functions representing N - 1 subsystems, the sub-images of the extended function classes in the first subsystem and the sub-images extended in the second subsystem are incompatible, it is determined that user data needs to be cleared.
[0020] In the above embodiments, considering the situation where the sub-images extended in each subsystem are incompatible, and combining the impact of incompatibility on data storage, it is determined that user data needs to be cleared when there is incompatibility. In this case, regardless of the user's set requirements, the user data will also be cleared, saving storage space.
[0021] In an alternative embodiment, the method further includes:
[0022] Generating N mounting files; wherein, each mounting file stores an operating system.
[0023] In the above embodiments, based on the principle that each mounting file stores an operating system, N mounting files are generated. In this way, when different users log in, the corresponding mounting files can be adapted to load the corresponding operating systems.
[0024] In an alternative embodiment, the method further includes:
[0025] Determining the operating system identifier corresponding to the click operation;
[0026] According to the operating system identifier, finding the first mounting file that matches the click operation among the N mounting files.
[0027] In the above embodiments, through the correspondence between the click operation and the operating system identifier, the first mounting file that matches the click operation can be found among the N mounting files.
[0028] In an alternative embodiment, presenting the operation page of the first operating system includes:
[0029] Generating the operation page of the first operating system stored in the first mounting file based on the first mounting file;
[0030] Presenting the operation page.
[0031] In the above embodiments, by loading the first mounting file, the corresponding operation page can be generated to meet the needs of different users logging in to the same operating system.
[0032] According to a second aspect of the exemplary embodiments, an electronic device is provided, including a processor and a display screen;
[0033] The processor is configured to perform: in response to an operating system switching request of a first user, display a first page on the display screen; wherein, the first page includes N login controls; the N login controls are used to log in to N operating systems, and each login control is used to log in to one operating system; the N operating systems include a main operating system and N - 1 secondary operating systems, and each secondary operating system is generated according to set requirement information and the main operating system;
[0034] The processor is further configured to perform: in response to a click operation of the first user on the first login control in the first page, display an operation page of the first operating system on the display screen; wherein, the first login control is a control for logging in to the first operating system; the first login control is any one of the N login controls, and the first operating system is any one of the N operating systems.
[0035] According to a third aspect of the exemplary embodiments, a multi - system control device for an electronic device is provided, including:
[0036] A processing unit, configured to, in response to an operating system switching request of a first user, display a first page through a display unit; wherein, the first page includes N login controls; the N login controls are used to log in to N operating systems, and each login control is used to log in to one operating system; the N operating systems include a main operating system and N - 1 secondary operating systems, and each secondary operating system is generated according to set requirement information and the main operating system;
[0037] The processing unit is further configured to, in response to a click operation of the first user on the first login control in the first page, display an operation page of the first operating system through the display unit; wherein, the first login control is a control for logging in to the first operating system; the first login control is any one of the N login controls, and the first operating system is any one of the N operating systems.
[0038] According to a fourth aspect of the exemplary embodiments, a computer storage medium is provided, in which computer program instructions are stored. When the instructions run on a computer, the computer is made to execute the multi - system control method of the electronic device as in the first aspect. Description of the Drawings
[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.
[0040] Figure 1 Exemplarily shown is a system switching interface diagram of an electronic device provided by an embodiment of the present application;
[0041] Figure 2 Exemplarily shown is a flowchart of a multi-system control method of an electronic device provided by an embodiment of the present application;
[0042] Figure 3 Exemplarily shown is a schematic diagram of a first page provided by an embodiment of the present application;
[0043] Figure 4 Exemplarily shown is a schematic diagram of an operation page of a first operating system provided by an embodiment of the present application;
[0044] Figure 5 Exemplarily shown is a flowchart of a method for generating a secondary operating system provided by an embodiment of the present application;
[0045] Figure 6 Exemplarily shown is a comparison diagram of sub-images before and after expansion provided by an embodiment of the present application;
[0046] Figure 7 Exemplarily shown is another comparison diagram of sub-images before and after expansion provided by an embodiment of the present application;
[0047] Figure 8 Exemplarily shown is another comparison diagram of sub-images before and after expansion provided by an embodiment of the present application;
[0048] Figure 9 Exemplarily shown is a schematic structural diagram of a multi-system control device of an electronic device provided by an embodiment of the present application;
[0049] Figure 10 Exemplarily shown is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners
[0050] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application.
[0051] For ease of understanding, the terms involved in the embodiments of the present application are explained below:
[0052] (1) System image refers to a system image file, which is a file that needs to be decompressed using some virtual optical drive tools before it can be used.
[0053] (2) The operating system (OS) is a built-in program used to coordinate various computer hardware components for interaction with users. Common operating systems include Windows, macOS, open-source Linux, and Huawei HarmonyOS. Depending on the operating environment, operating systems can be classified into desktop operating systems, mobile operating systems, server operating systems, embedded operating systems, etc. In the embodiments of the present application, taking a mobile phone as an example of the electronic device, the operating system is a mobile operating system.
[0054] In the prior art, there are mainly two implementation methods for an electronic device to support multiple users. In one method, a single system creates multiple users. For example, in the Android system, multiple users can be created, and different personal data can be created by switching between different users. However, it is very easy to switch to other users in this way, increasing the risk of data leakage. In another method, multiple systems are used to implement multi-user operations. Taking the dual-system of Huawei mobile phones as an example, both EMUI and HarmonyOS are used as operating systems at the same time. The two operating systems are independent, occupying a relatively large storage space, and compatibility issues also need to be considered.
[0055] To this end, the embodiments of the present application provide a multi-system control method for an electronic device, which loads different system images according to different startup methods or different users to realize the function of starting different systems. After power-on, the mobile phone loads different systems. A mobile phone can switch back and forth between multiple different systems, and a single mobile phone can be used as multiple mobile phones to experience different system functions. This saves storage space and has high security.
[0056] After introducing the design concept of the embodiments of the present application, the following briefly introduces the application scenarios applicable to the technical solutions of the embodiments of the present application. It should be noted that the application scenarios introduced below are only used to illustrate the embodiments of the present application rather than limiting them. In specific implementation, the technical solutions provided by the embodiments of the present application can be flexibly applied according to actual needs.
[0057] Reference Figure 1 , shows a system switching interface diagram of an electronic device. As can be seen from Figure 1 , the electronic device can display an operating system switching icon, and the electronic device responds to the user's operation on the operating system switching icon to generate an operating system switching request so as to switch to the operation associated with the user. In this way, the user can use the electronic device under the corresponding operating system.
[0058] To further illustrate the technical solutions provided by the embodiments of the present application, the following will provide a detailed description in conjunction with the accompanying drawings and specific implementation manners. Although the embodiments of the present application provide method operation steps as shown in the following embodiments or drawings, more or fewer operation steps may be included in the method based on routine or non-creative labor. In steps where there is no necessary causal relationship logically, the execution order of these steps is not limited to the execution order provided by the embodiments of the present application.
[0059] The following will Figure 1 illustrate the technical solutions provided by the embodiments of the present application with reference to the flowchart of a multi-system control method for an electronic device shown in the Figure 2 application scenario shown below.
[0060] S201: In response to an operating system switching request from a first user, display a first page.
[0061] Among them, the first page includes N login controls; the N login controls are used to log in to N operating systems, each login control is used to log in to one operating system; the N operating systems include a main operating system and N - 1 secondary operating systems, and each secondary operating system is generated based on the set requirement information and the main operating system.
[0062] S202: In response to a click operation by the first user on the first login control in the first page, display the operation page of the first operating system.
[0063] Among them, the first login control is the control used to log in to the first operating system; the first login control is any one of the N login controls, and the first operating system is any one of the N operating systems.
[0064] In the embodiments of the present application, N - 1 secondary operating systems are generated based on the set requirement information and the main operating system. The N - 1 secondary operating systems and one main operating system can form N operating systems of the electronic device. Each login control can log in to one operating system, and the N login controls can log in to N operating systems. The first user can be the main user or other users. The electronic device responds to the operating system switching request from the first user and displays the first page including N login controls. The first login control can be used to log in to the first operating system. In this way, the electronic device responds to the click operation by the first user on the first login control in the first page and displays the first operating system. In this way, the first user can use the electronic device under the first operating system. Since each secondary system in the present application is generated based on the set requirement information and the main operating system, compared with the multiple independent operating systems in the related art, storage space is saved. In addition, each user logs in to their respective operating systems, ensuring user data security at the same time.
[0065] Figure 3A schematic diagram showing a first page provided by an embodiment of the present application. The electronic device responds to a user's operation on an icon of a first operating system switching request in Figure 3 to display Figure 3 (b) in Figure 3 (b) in which includes N login controls, including one login control for logging in to the main system and N - 1 login controls for logging in to N - 1 sub - systems.
[0066] Figure 4 A schematic diagram showing an operation page of a first operating system provided by an embodiment of the present application.
[0067] Among them, Figure 4 (a) in is a schematic diagram of the first page, Figure 4 (b) in is a schematic diagram of the operation page of the first operating system.
[0068] It involves S201. N operating systems are set in the electronic device. The N operating systems include one main operating system and N - 1 sub - operating systems. Each sub - operating system is generated according to the set requirement information and the main operating system.
[0069] Optionally, for the generation process of the sub - operating system, reference can be made to steps S201 - 1 to S201 - 2 in Figure 5 :
[0070] S201 - 1: Analyze the set requirement information.
[0071] Among them, the set requirement information includes N - 1 set functions and data retention requirement information. Assuming there are two set functions, then N is 3. For example, the electronic device is an electronic device used by a bank. Set function A is for user 1, and set function B is for user 2. User 1 and user 2 may be responsible for different businesses or have different user permissions, etc.
[0072] Optionally, the data retention requirement information includes retaining user data and not retaining user data. Among them, retaining user data means retaining user data during the process of switching different operating systems, and not retaining user data means clearing user data during the process of switching different operating systems.
[0073] S201 - 2: Based on the set requirement information and M original sub - images included in the main operating system, generate N - 1 sub - operating systems.
[0074] Among them, each sub - operating system includes M target sub - images; among the M target sub - images, there are at least one original sub - image and / or at least one sub - image extended from the original sub - image; among the M target sub - images, there are M1 target sub - images of the function type and M2 target sub - images of the user type, and the sum of M1 and M2 is M.
[0075] Optionally, taking the Android system as an example of the main operating system, the main operating system includes M original sub-images, and these M original sub-images are divided into functional sub-images and user sub-images. M is illustrated by 7, and it may be more in the actual application process. Here is just an example and does not form a specific limitation.
[0076] Optionally, the functional sub-images are, for example, system.img, system_ext.img, vendor.img, product.img, boot.img, etc., which are sub-images for running different functions of the main operating system; the user sub-images are, for example, userdata.img and metadata.img. Among them, userdata.img is a sub-image for storing user data, and metadata.img is a sub-image for storing metadata (description data of user data, such as the encryption method).
[0077] Specifically, the process of generating N - 1 secondary operating systems according to the set functions and data retention requirement information is as follows:
[0078] The first case: If the data retention requirement information indicates that user data needs to be retained, then for each secondary system, the M1 functional target sub-images include at least one sub-image extended from the original functional sub-image, and the M2 user target sub-images include at least one sub-image extended from the original user sub-image.
[0079] Continuing to refer to the above example, M1 is 5 and M2 is 2, for example. According to the set function A, it is determined that system.img needs to be expanded, and the target sub-image obtained after expansion is system.img_c; according to the set function B, it is determined that system.img needs to be expanded, and the target sub-image obtained after expansion is system.img_d. According to the data retention requirement information, it is determined whether the sub-images of the user class need to be expanded. For example, if the data retention requirement information indicates the requirement to retain user data, it is determined that userdata.img and metadata.img need to be expanded, and the target sub-images obtained after expansion are userdata_c.img, userdata_d.img, metadata_c.img, and metadata_d.img. In this example, among the target sub-images of the 5 function classes, there is one expanded sub-image system.img_c (or system.img_d) and four original sub-images system_ext.img, vendor.img, product.img, and boot.img; among the target sub-images of the 2 user classes, there are two expanded sub-images userdata_c.img (or userdata_d.img) and metadata_c.img (or metadata_d.img).
[0080] Figure 6 This is a comparison diagram of the sub-images before and after expansion provided by the embodiment of the present application. Refer to Figure 6 , the target sub-images included in subsystem 1 are the target sub-images of 5 function classes system_c.img, system_ext.img, vendor.img, product.img, boot.img and the target sub-images of 2 user classes userdata_c.img and metadata_c.img; the target sub-images included in subsystem 2 are the target sub-images of 5 function classes system_d.img, system_ext.img, vendor.img, product.img, boot.img and the target sub-images of 2 user classes userdata_d.img and metadata_d.img. In this example, System_c.img, userdata_c.img, and metadata_c.img combined with other original images can achieve a system switch with complete isolation of user data and can not clear user data.
[0081] Figure 7 This is another comparison diagram of the sub-images before and after expansion provided by the embodiment of the present application, and is related to Figure 6Compared with the example in [reference], the extended sub-image changes from system.img to vendor.img.
[0082] Optionally, the description codes of the main system and the secondary system 1:
[0083] Main system:
[0084] System / system ext4 ro,barrier=1,discardwait,slotselect,avb=vbmetasystem,logical,first_stage_mount,avb_keys= / avb / q-gsi.avbpubkey: / avb / r-gsi.avbpubkey: / avb / s-gsi.avbpubkey
[0085] Secondary system 1:
[0086] System_c / system ext4 ro,barrier=1,discardwait,slotselect,avb=vbmeta_system,logical,first_stage_mount,avb_keys= / avb / q-gsi.avbpubkey: / avb / r-gsi.avbpubkey: / avb / s-gsi.avbpubkey
[0087] In this case, for the target sub-images of M2 user classes, each target sub-image is stored in a data partition, and the data partitions where the target sub-images are stored are different. Among them, the sub-images of user classes include user data sub-images (userdata.img) and user metadata sub-images (metadata.img). Compared with the related technology, the security of user data is improved.
[0088] Second case: If the data retention requirement information indicates that user data needs to be cleared or there is no requirement, then for each secondary system, the target sub-images of M1 function classes include at least one sub-image extended from the original sub-image of the function class, and the target sub-images of M2 user classes are the original sub-images of the user classes.
[0089] In this case, whether user data needs to be cleared or there is no requirement, it can be processed as clearing user data, which can save storage space. In this case, the target sub-images of M2 user classes are not extended.
[0090] Figure 8 This is another comparison diagram of the sub-images before and after extension provided by the embodiment of the present application. Refer to Figure 7, the target sub-images included in Sub-system 1 are 5 function-type target sub-images: system_c.img, system_ext.img, vendor.img, product.img, boot.img, and 2 user-type target sub-images: userdata.img and metadata.img; the target sub-images included in Sub-system 2 are 5 function-type target sub-images: system_d.img, system_ext.img, vendor.img, product.img, boot.img, and 2 user-type target sub-images: userdata and metadata.img.
[0091] In the actual application process, it is also possible to determine whether to clear user data according to the compatibility of the extended sub-images. For example, if among N - 1 functions representing N - 1 sub-systems, the extended function-type sub-images in the first sub-system and the extended sub-images in the second sub-system are not compatible, it is determined that user data needs to be cleared.
[0092] Optionally, System_c.img combined with other original images can achieve different system switches, and user data can be retained or cleared according to the compatibility between the System_c.img image and the original system.img image. If the two image data are compatible and user data can be used in both systems, then user data can be retained. If the two image data are not compatible, after mounting data at startup, perform a data format formatting process.
[0093] Specifically, user data is saved in the data partition. In scenarios where user data needs to be switched, after mounting the data partition when switching different users and booting up, perform a format formatting process on the data partition and re-execute the data creation process. In this way, each time the system is switched, the mobile phone does not retain user data, just like the first use.
[0094] Regarding S202, N mounting files are pre-generated, and each mounting file stores an operating system, which can be the main operating system or a secondary operating system. In this way, after obtaining the click operation of the first user on the first login control in the first page, the operating system identifier corresponding to the click operation can be determined, and then according to this operating system identifier, the first mounting file matching the click operation can be found among the N mounting files.
[0095] For example, if the first operating system is a secondary operating system and the first mounted file includes an extended sub-image (such as vendor), the identifier of the original mount table of the first mounted file is vendor / etc / fstab.default, and the identifier of the current mount table of the first mounted file is vendor / etc / fstab2.default. The identifier of the mount table represents the path to load the mount table.
[0096] In addition, different mounted files can be loaded according to different boot methods. The system adds an entry to control the boot method and users, and users can choose which system to enter. A special user can be launched by pressing the combination key boot method. For example, pressing the up volume and down volume together for 5 seconds to enter. The special user can be selected through settings or the systemui menu, and the boot user parameter is written to a special partition. When the bootloader boots up and loads at restart, the fixed position of the special partition is read to determine which user to boot, the cmdline property is set, and init is notified to select the appropriate mounted file when loading the mounted partition table.
[0097] In this way, based on the first mounted file, an operation page of the first operating system stored in the first mounted file is generated and the operation page is displayed.
[0098] In the above embodiment, if none of the original sub-images of the function class are extended and at least one of the sub-images of the user class is extended, then the situation of one system with multiple users can be realized.
[0099] For example, userdata_c.img and metadata_c.img can be combined with other original images to implement the same system, match different user partitions, and completely isolate user data, and be used as multiple mobile phones with the same system.
[0100] In the embodiments of the present application, different system images can be loaded according to different boot methods or user creations to implement the function of starting different systems. After booting, the mobile phone loads different systems, and a mobile phone can switch back and forth between multiple different systems to experience different system functions. In addition, the same system can support the switching of multiple user data. One system image corresponds to multiple user data partitions, and one device can be used as multiple mobile phones. User data can be created under different users without affecting each other.
[0101] As Figure 9 shown, based on the same inventive concept, the embodiments of the present application provide a multi-system control device for an electronic device, including a processing unit 91 and a display unit 92.
[0102] A processing unit 91, configured to display a first page through a display unit 92 in response to an operating system switching request of a first user; wherein, the first page includes N login controls; the N login controls are used to log in to N operating systems, and each login control is used to log in to one operating system; the N operating systems include a main operating system and N-1 secondary operating systems, and each secondary operating system is generated according to set requirement information and the main operating system;
[0103] The processing unit 91 is further configured to display an operation page of the first operating system through the display unit 92 in response to a click operation of the first user on the first login control in the first page; wherein, the first login control is a control for logging in to the first operating system; the first login control is any one of the N login controls, and the first operating system is any one of the N operating systems.
[0104] In an optional implementation manner, the processing unit 91 is further configured to:
[0105] Analyze the set requirement information; wherein, the set requirement information includes N-1 set functions and data retention requirement information; the data retention requirement information indicates whether to retain user data during the process of switching different operating systems;
[0106] Generate N-1 secondary operating systems based on the set requirement information and M original sub-images included in the main operating system;
[0107] Wherein, the type of the original sub-image is function type or user type; each secondary operating system includes M target sub-images; the M target sub-images include at least one original sub-image and / or at least one sub-image extended from the original sub-image; the M target sub-images include M1 function-type target sub-images and M2 user-type target sub-images, and the sum of M1 and M2 is M.
[0108] In an optional implementation manner, if the data retention requirement information indicates that user data needs to be cleared or there is no requirement, then for each secondary system, the M1 function-type target sub-images include at least one sub-image extended from the function-type original sub-image, and the M2 user-type target sub-images are user-type original sub-images;
[0109] If the data retention requirement information indicates that user data needs to be retained, then for each secondary system, the M1 function-type target sub-images include at least one sub-image extended from the function-type original sub-image, and the M2 user-type target sub-images include at least one sub-image extended from the user-type original sub-image.
[0110] In an alternative embodiment, if the data retention requirement information indicates that user data needs to be retained, for the target sub-images of M2 user classes, each target sub-image is stored in a data partition, and the data partitions for storing the respective target sub-images are different; wherein, the sub-images of a user class include a user data sub-image and a user metadata sub-image.
[0111] In an alternative embodiment, if it is determined that the sub-images of the function classes extended in the first subsystem and the sub-images extended in the second subsystem among N - 1 functions in N - 1 subsystems are incompatible, it is determined that user data needs to be cleared.
[0112] In an alternative embodiment, the processing unit 91 is further configured to:
[0113] Generate N mounting files; wherein, each mounting file stores an operating system.
[0114] In an alternative embodiment, the processing unit 91 is further configured to:
[0115] Determine the operating system identifier corresponding to the click operation;
[0116] Find the first mounting file that matches the click operation among the N mounting files according to the operating system identifier.
[0117] In an alternative embodiment, the display unit 92 is specifically configured to:
[0118] Generate an operation page of the first operating system stored in the first mounting file based on the first mounting file;
[0119] Display the operation page.
[0120] Since this device is the device in the method of the embodiments of the present application, and the principle by which this device solves problems is similar to that of the method, the implementation of this device can refer to the implementation of the method, and repeated parts will not be elaborated.
[0121] As Figure 10 shown, based on the same inventive concept, an embodiment of the present application provides an electronic device, including a processor 101 and a display screen 102.
[0122] The processor 101 is configured to execute: in response to an operating system switching request of a first user, display a first page on the display screen 102; wherein, the first page includes N login controls; the N login controls are used to log in to N operating systems, and each login control is used to log in to one operating system; the N operating systems include a main operating system and N - 1 secondary operating systems, and each secondary operating system is generated according to set requirement information and the main operating system;
[0123] The processor 101 is further configured to execute: in response to a click operation of a first user on a first login control in a first page, display an operation page of a first operating system on the display screen 102; wherein, the first login control is a control for logging in to the first operating system; the first login control is any one of N login controls, and the first operating system is any one of N operating systems.
[0124] In an alternative embodiment, the processor 101 is further configured to execute:
[0125] Analyze the set requirement information; wherein, the set requirement information includes N - 1 set functions and data retention requirement information; the data retention requirement information indicates whether to retain user data during the process of switching different operating systems;
[0126] Generate N - 1 secondary operating systems based on the set requirement information and M original sub - images included in the primary operating system;
[0127] Wherein, the type of the original sub - image is function - type or user - type; each secondary operating system includes M target sub - images; the M target sub - images include at least one original sub - image and / or at least one sub - image extended from the original sub - image; the M target sub - images include M1 function - type target sub - images and M2 user - type target sub - images, and the sum of M1 and M2 is M.
[0128] In an alternative embodiment, if the data retention requirement information indicates that user data needs to be cleared or there is no requirement, then for each secondary system, the M1 function - type target sub - images include at least one sub - image extended from the function - type original sub - image, and the M2 user - type target sub - images are the user - type original sub - images;
[0129] If the data retention requirement information indicates that user data needs to be retained, then for each secondary system, the M1 function - type target sub - images include at least one sub - image extended from the function - type original sub - image, and the M2 user - type target sub - images include at least one sub - image extended from the user - type original sub - image.
[0130] In an alternative embodiment, if the data retention requirement information indicates that user data needs to be retained, then for the M2 user - type target sub - images, each target sub - image is stored in a data partition, and the data partitions where the respective target sub - images are stored are different; wherein, the user - type sub - images include user data sub - images and user metadata sub - images.
[0131] In an alternative embodiment, if the N - 1 functions indicate that the function - type sub - images extended in the first secondary system and the sub - images extended in the second secondary system among the N - 1 secondary systems are incompatible, then it is determined that user data needs to be cleared.
[0132] In an alternative embodiment, the processor 101 is further configured to:
[0133] Generate N mounting files; wherein, each mounting file stores an operating system.
[0134] In an alternative embodiment, the processor 101 is further configured to:
[0135] Determine the operating system identifier corresponding to the click operation;
[0136] Find the first mounting file that matches the click operation from the N mounting files according to the operating system identifier.
[0137] In an alternative embodiment, the display 102 is specifically configured to:
[0138] Generate an operation page of the first operating system stored in the first mounting file based on the first mounting file;
[0139] Display the operation page.
[0140] The embodiment of the present application further provides a computer storage medium, in which computer program instructions are stored. When the instructions run on a computer, the computer is made to execute the steps of the multi-system control method of the above-mentioned electronic device.
[0141] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0142] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one or more of the flows or multiple flows and / or blocks Figure 1 one or more of the blocks or multiple blocks.
[0143] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart(s) Figure 1 a flowchart or flowcharts and / or block(s) Figure 1 a block or blocks.
[0144] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable apparatus provide steps for implementing the function specified in the flowchart(s) Figure 1 a flowchart or flowcharts and / or block(s) Figure 1 a block or blocks.
[0145] It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the scope of the application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.
Claims
1. A multi-system control method for an electronic device, characterized in that: include: In response to the operating system switching request of the first user, a first page is displayed; wherein the first page includes N login controls; the N login controls are used to log in to N operating systems, and each login control is used to log in to one operating system; the N operating systems include a main operating system and N-1 secondary operating systems, and each secondary operating system is generated according to the set requirement information and the main operating system; In response to the first user clicking the first login control in the first page, an operation page of the first operating system is displayed; wherein the first login control is a control for logging into the first operating system; the first login control is any one of the N login controls, and the first operating system is any one of the N operating systems.
2. The method according to claim 1, characterized in that The method further comprises: Parsing the setting requirement information; wherein the setting requirement information includes N-1 setting functions and data retention requirement information; the data retention requirement information indicates whether to retain user data during the process of switching between different operating systems; Generate N-1 secondary operating systems based on the setting requirement information and the M original sub-images included in the primary operating system; Among them, the type of the original sub-image is a function class or a user class; each secondary operating system includes M target sub-images; the M target sub-images include at least one original sub-image and / or at least one sub-image expanded according to the original sub-image; the M target sub-images include M1 function class target sub-images and M2 user class target sub-images, and the sum of M1 and M2 is M.
3. The method according to claim 2, characterized in that If the data retention requirement information indicates that user data needs to be cleaned up or there is no requirement, then for each secondary system, the target sub-images of the M1 functional classes include at least one sub-image extended from the original sub-image of the functional class, and the target sub-images of the M2 user classes are the original sub-images of the user classes; If the data retention requirement information indicates that user data needs to be retained, then for each sub-system, the target sub-mirrors of the M1 functional classes include at least one sub-mirror expanded from the original sub-mirror of the functional class, and the target sub-mirrors of the M2 user classes include at least one sub-mirror expanded from the original sub-mirror of the user class.
4. The method according to claim 3, characterized in that If the data retention requirement information indicates that user data needs to be retained, then for the target sub-mirrors of the M2 user classes, each target sub-mirror is stored in a data partition, and the data partitions stored in each target sub-mirror are different; wherein the sub-mirrors of the user class include user data sub-mirrors and user metadata sub-mirrors.
5. The method according to claim 1, characterized in that If the N-1 functions represent that in the N-1 sub-systems, the sub-image of the extended functional class in the first sub-system is incompatible with the sub-image extended in the second sub-system, it is determined that user data needs to be cleaned up.
6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Generate N mount files, each of which stores an operating system.
7. The method according to claim 6, characterized in that The method further comprises: Determine an operating system identifier corresponding to the click operation; According to the operating system identifier, a first mount file matching the click operation is found among the N mount files.
8. The method according to claim 7, characterized in that The displaying of the operation page of the first operating system includes: Based on the first mount file, generating an operation page of the first operating system stored in the first mount file; The operation page is displayed.
9. An electronic device, characterized in that: Includes processor and display; The processor is configured to execute: in response to an operating system switching request of a first user, display a first page on the display screen; wherein the first page includes N login controls; the N login controls are used to log in to N operating systems, and each login control is used to log in to one operating system; the N operating systems include a main operating system and N-1 secondary operating systems, and each secondary operating system is generated according to set requirement information and the main operating system; The processor is also configured to execute: in response to the first user clicking a first login control in the first page, displaying an operation page of the first operating system on the display screen; wherein the first login control is a control for logging into the first operating system; the first login control is any one of the N login controls, and the first operating system is any one of the N operating systems.
10. The electronic device according to claim 9, characterized in that: The processor is further configured to perform: Parsing the setting requirement information; wherein the setting requirement information includes N-1 setting functions and data retention requirement information; the data retention requirement information indicates whether to retain user data during the process of switching between different operating systems; Generate N-1 secondary operating systems based on the setting requirement information and the M original sub-images included in the primary operating system; Among them, the type of the original sub-image is a function class or a user class; each secondary operating system includes M target sub-images; the M target sub-images include at least one original sub-image and / or at least one sub-image expanded according to the original sub-image; the M target sub-images include M1 function class target sub-images and M2 user class target sub-images, and the sum of M1 and M2 is M.