An Android multi-user switching method and system based on setting item classification

Abstract

The application provides an Android multi-user switching method and system based on setting item classification, wherein the method steps include dividing Android system setting items into single-user setting items, globally shared setting items and main-user exclusive setting items; creating independent storage areas for each user; in response to a user setting operation, acquiring a setting item and a target value thereof; performing user switching; and after completing system bottom-layer user switching, reconstructing an environment according to the setting item category. Through the classified management mode, the application effectively solves the rigid problem of setting item permission division in the Android multi-user mode, improves user privacy and device security; through the creation of independent storage areas for each user, the application realizes data isolation between users, effectively prevents the mutual influence of setting items between users, and guarantees the data security and privacy of users.

Description

Technical Field

[0001] This invention relates to the field of terminal device management technology, and specifically to an Android multi-user switching method and system based on settings classification. Background Technology

[0002] With the widespread adoption of smart terminal devices, such as home tablets, in-vehicle central control screens, or shared enterprise devices, it is increasingly common for a single device to be used by multiple people. To address this, the Android operating system offers a multi-user mode, allowing the creation of different user accounts. However, this mode has significant design limitations in system settings management, leading to a fragmented user experience, increased risks of privacy leaks, and restrictions on flexible device sharing. Specifically, this is mainly reflected in the following two aspects: Rigid Permission Division for Settings: Android's settings permissions are overly simplistic, merely categorizing them as either individually configurable or shared. This lack of fine-grained management logic leads to numerous unreasonable issues in actual use. For example, private information such as Wi-Fi passwords and Bluetooth pairing lists are forcibly shared globally. When a primary user connects to a public Wi-Fi network or pairs a personal Bluetooth headset under their account, switching to another user's account automatically maintains these connections. This not only risks other users' devices passively accessing networks with unknown security but also allows other accounts to directly access the primary user's personal Bluetooth device, infringing on user privacy and device security. Furthermore, different users may have legitimate independent configuration needs for the same system functions. For instance, the primary user and other users may want to set different personalized configurations for their respective accounts, but these are often forcibly unified globally or completely isolated by the system, preventing on-demand, fine-grained personalized management.

[0003] Exclusive Principal User Permissions: The system assigns absolute authority to the device administrator (primary user), preventing other users from exercising necessary legal control over the device, even when using their own accounts. For example, only the primary user has the right to configure VPNs, install system certificates, modify APNs, or enable developer options. Even basic management functions like restoring factory settings are only available to the primary account. If other users wish to completely erase their data and reset the device, they must contact the primary account holder, severely impacting user autonomy and convenience.

[0004] Therefore, a multi-user management system and method are urgently needed to achieve flexible, secure, and independent management of settings. By classifying and managing system settings, complete isolation of settings for different users can be achieved, while allowing all users to have the permission to modify key settings, thereby improving the flexibility and security of multi-user management. Summary of the Invention

[0005] To address the shortcomings of existing technologies, the purpose of this invention is to provide an Android multi-user switching method based on settings category, thereby resolving the problems mentioned in the background section.

[0006] As a first aspect of the present invention, an Android multi-user switching method based on settings category is proposed, the steps of which include: The Android system settings are divided into single-user settings, globally shared settings, and settings exclusive to the main user; a separate storage area is created for each user, including a storage area for globally shared settings and a storage area for settings exclusive to the main user. Respond to user setting actions, retrieve the settings and their target values, and process them according to their categories: If it is a single-user setting, the setting will be made by calling the native Android system interface; If it is a globally shared setting, it will first be stored in the current user's global shared settings storage area and then synchronized to the system global settings through the mobile device management interface to take effect immediately; If it is a setting exclusive to the primary user, it is first stored in the primary user's exclusive settings storage area, and then the execution path is determined according to the current user's identity: if it is the primary user, it is set directly through the mobile device management interface; if it is a secondary user, the setting request is passed to the primary user through inter-user communication, and the primary user calls the mobile device management interface to set it. Perform user switching, and after completing the system-level switching, read the settings from the storage area corresponding to the target user according to the category of the settings and apply them to the system to rebuild the target user environment.

[0007] Furthermore, the step of reconstructing the target user environment includes: For globally shared settings, first clear the current system settings through the mobile device management interface, then read the settings from the target user's global shared settings storage area and apply them to the system; For settings exclusive to the primary user, the settings are loaded based on the target user's identity: if the target user is the primary user, the settings are read from the primary user's exclusive settings storage area and applied; if the target user is a secondary user, the settings are read from their own primary user exclusive settings storage area and then handed over to the primary user for processing and application through inter-user communication.

[0008] Furthermore, in the settings operation classification processing steps, the processing of globally shared settings includes: first saving the globally shared settings input by the user and their target values ​​to the current user's exclusive global shared settings storage area; then calling the mobile device management interface corresponding to the settings to synchronously write the settings and their target values ​​stored in the storage area into the Android system's global settings database.

[0009] Furthermore, in the step of classifying and processing the settings operation, the processing of the primary user-specific settings for secondary users includes: saving the primary user-specific settings input by the user and their target values ​​to the primary user-specific settings storage area for that secondary user; transmitting the stored setting request to the primary user process through the cross-user communication mechanism provided by the Android system; after receiving the request, the primary user stores the setting and target values ​​in its own primary user-specific settings storage area and calls the corresponding mobile device management interface to apply the setting to the system.

[0010] Furthermore, when the target user is the primary user, the processing of primary user-specific settings includes: calling the mobile device management interface to clear the corresponding primary user-specific settings currently in effect at the system level; reading all primary user-specific settings and their target values ​​saved in the primary user's own primary user-specific settings storage area; and for each setting read, calling the corresponding mobile device management interface to apply it to the system.

[0011] Furthermore, when the target user is a secondary user, the processing of the primary user's exclusive settings includes: reading all the primary user's exclusive settings and their target values ​​from the secondary user's primary user exclusive settings storage area; transmitting each setting request to the primary user through inter-user communication; and after receiving the request, the primary user sequentially calls the corresponding mobile device management interface to apply it to the system.

[0012] Furthermore, the single-user settings include at least wallpaper, theme and style, sound and vibration, and display brightness; The global sharing settings include at least a Wi-Fi network connection list and a Bluetooth device pairing list; The main user-specific settings include at least VPN configuration, developer options, APN access point, and system certificate management.

[0013] As a second aspect of the present invention, an Android multi-user switching system based on settings category is proposed, comprising: The settings category module is used to identify and classify user-inputted system settings into single-user settings, globally shared settings, or main user-exclusive settings. The user storage management module is used to create and manage a separate globally shared settings storage area and a main user-specific settings storage area for each user. The user settings application module is used to coordinate and execute the storage, communication, and operation of various settings items through the mobile device management interface during user settings operations and user switching. The user switching module is used to trigger the user switching process and drive the user settings application module to perform environment reconstruction after the switching is completed.

[0014] Furthermore, the user settings application module includes: The shared settings application unit is used to handle the storage and synchronization of globally shared settings items; The primary user-specific settings application unit is used to handle the storage of primary user-specific settings, identity verification, cross-user communication, and application authorization.

[0015] Furthermore, the user switching module includes: The authentication unit is used to verify the identity of the target user being switched. The process management unit is used to manage the state of user processes during user switching to ensure the continuity of application operation; The settings synchronization unit is used to trigger and coordinate the synchronization and reconstruction of globally shared settings and main user-specific settings after a user switch is completed.

[0016] Compared with the prior art, the beneficial effects of the present invention are as follows: This invention innovatively divides system settings into three categories: single-user, globally shared, and exclusive to the main user, and implements different management strategies for each category, breaking the simple mode of complete isolation or forced sharing in the native Android system; it enables key settings such as Wi-Fi and Bluetooth to be virtualized and isolated by user, fundamentally solving the privacy leakage and security risks caused by globally sharing settings.

[0017] This invention isolates logically shared or restricted-access settings at the physical storage level by creating a separate globally shared settings storage area for each user and a settings storage area exclusively for the main user. Each user's settings are stored independently and are not visible to each other, achieving strong data isolation between users and effectively protecting their data security and privacy.

[0018] This invention allows secondary users to request modifications to critical settings such as VPN and developer options, breaking the exclusive permissions of primary users and enabling secondary users to perform necessary personalized configurations. Simultaneously, based on a user-independent storage area switching mechanism, no complex process shutdowns or partition remounting operations are required when switching users. The complete personal settings environment can be quickly and automatically rebuilt, achieving a seamless and smooth user switching experience and significantly improving the device's usability in multi-user sharing scenarios. Attached Figure Description

[0019] The disclosure of this invention is illustrated with reference to the accompanying drawings. It should be understood that the drawings are for illustrative purposes only and are not intended to limit the scope of protection of this invention. In the drawings, the same reference numerals are used to refer to the same parts. Wherein: Figure 1This is a schematic diagram of the overall processing flow of the Android multi-user switching method proposed in one embodiment of the present invention; Figure 2 This is a block diagram of the user settings storage area structure proposed in one embodiment of the present invention; Figure 3 This is a schematic diagram of the user switching process proposed in one embodiment of the present invention. Detailed Implementation

[0020] It is readily understood that, based on the technical solution of this invention, those skilled in the art can propose various interchangeable structural methods and implementations without altering the essential spirit of the invention. Therefore, the following detailed embodiments and accompanying drawings are merely illustrative examples of the technical solution of this invention and should not be considered as the entirety of the invention or as limitations or restrictions on the technical solution of this invention.

[0021] The present invention will be further described in detail below with reference to the accompanying drawings, but this is not intended to limit the scope of the invention.

[0022] Combination Figures 1-3 As shown, as a first aspect of the present invention, an Android multi-user switching method based on settings item classification is proposed, comprising the following steps: Step 1: Categorization and Storage of User System Settings Understandably, to achieve isolation and flexible management of settings among multiple users, this system first divides all user settings in the Android system into three categories based on their operable permissions and management modes, and establishes the corresponding storage logic as follows. Specifically, this includes: S1-1. Perform a categorization operation, dividing the settings into single-user settings, globally shared settings, and settings exclusive to the primary user. Specifically: Single-user settings: These are defined as settings that can be configured independently for each user without affecting others, including at least wallpaper, themes and styles, sound and vibration, and display brightness. Globally shared settings: These are defined as settings shared by all users in the native system, such as the Wi-Fi network list and the paired Bluetooth device list. Principal user-exclusive settings: These are defined as settings that only the primary user can modify in the native system, such as VPN configuration, developer options, APN access points, system certificate management, and factory reset.

[0023] S1-2. Perform storage operations to create an independent storage area for each user, storing different categories of settings in a physically isolated manner. The global shared settings storage area stores the user's virtualization global settings, such as a separate Wi-Fi list and Bluetooth pairing information; the main user's dedicated settings storage area stores key setting requests and statuses initiated by the user, such as VPN configuration and developer options on / off status.

[0024] It should be noted that for single-user settings, the native Android user configuration file is used directly, without the need to create a storage area for repeated storage.

[0025] Step 2: User-defined request interception, routing, and execution. When a user makes a setting change, the system architecture will intervene to ensure that the request takes effect according to the new category logic.

[0026] S2-1. The system obtains the settings and their target values ​​input by the user through the user input module. The target value is the specific content or parameter corresponding to the settings. Then, the settings classification module identifies and determines the settings as a single-user settings, a globally shared settings, or a main user exclusive settings according to the preset classification rules.

[0027] S2-2. Based on the judgment result, the system uses the path corresponding to this category for setting and application: For single-user settings: the system directly calls the corresponding native Android interface to make the settings. This means that by leveraging Android's native support for these settings, the settings take effect immediately and only affect the current user, achieving simple and efficient personalized configuration.

[0028] For globally shared settings: The system first stores the setting and its value in the current user's dedicated globally shared settings storage area, completing the backup of the user's personal settings; then, it calls the Mobile Device Management (MDM) interface corresponding to the setting to synchronize the newly stored setting and value to the Android system's underlying global settings, writing it into the Android system's global settings database, so that the changes take effect immediately on the device globally.

[0029] For example, a secondary user adds "Office-WiFi," and this password is stored only in their personal storage area, and the system will only connect to the network when they use the device.

[0030] For settings exclusive to the primary user: the system first stores the settings and their values ​​in the primary user-specific settings storage area for the current user; then, it determines the current user's identity: If the current user is the primary user: the system directly calls the corresponding system or MDM interface to synchronize the settings and values ​​in the primary user's exclusive settings storage area to the system and make them effective, thereby giving the primary user the ability to modify key settings. If the current user is a secondary user: the system does not directly operate on the underlying settings, but instead passes the stored setting request to the primary user through the user-to-user communication mechanism; after receiving the primary user-specific setting, the primary user first stores the setting in its own storage area (the primary user's storage area) for recording, and then calls the corresponding MDM interface to apply the setting to the system, thereby making the setting effective.

[0031] Therefore, it can be understood that by handling and responding to users' real-time setting requests, the rigid permission boundaries set in the native Android multi-user mode are broken: by first storing users' private storage, and then establishing a conditional synchronization mechanism, it is ensured that all users' modifications to various settings are recorded and transmitted, and by using the MDM interface and the main user agent mechanism, the security and controllability of global setting modifications are ensured. Ultimately, an independent, flexible and secure setting space is built for each user, overcoming the problem of exclusive permissions.

[0032] Step 3: Dynamic reconstruction of the environment during user switching When switching user accounts, the system needs to dynamically refresh the settings environment according to category, creating a completely independent usage space for the target user. The system completes the underlying user context switch, officially changing the device's operating environment from the current user to the target user. The reconstruction process is as follows: Handling single-user settings: After the identity switch is completed, for single-user settings (such as wallpaper and theme), these settings are natively supported by the Android system and have automatically taken effect with the change of user identity, thus immediately presenting the target user's personalized interface and preferences. Based on this, no additional operations are required.

[0033] Handling global sharing settings: For global sharing settings, such as the Wi-Fi list, the system performs a clear and restore operation to ensure that the target user's privacy and configuration become the device's current unique global state. First, the MDM interface is called to clear all current global shared settings in the system's underlying layer (such as the global settings database), such as Wi-Fi connection and Bluetooth pairing. The purpose is to eliminate the global influence left by the previous user and prepare a clean underlying environment for loading the new user's configuration.

[0034] Secondly, read all of the target user's global virtualization configurations from the target user's storage area.

[0035] Finally, the MDM interface is called again to write the read configurations into the system's underlying layer, so that the device's global environment is completely consistent with the target user's personal configuration.

[0036] For example, when switching from user A to user B, the system will disconnect A's Wi-Fi and Bluetooth headset, and then immediately connect to B's stored Wi-Fi and pair it with its Bluetooth speaker.

[0037] Handling settings specific to the primary user: For settings specific to the primary user, such as VPN and developer options, it should be noted that the processing logic for this step depends on the identity of the currently running user after the switch, i.e., the target user's identity. If switched to the primary user: the system applies all active settings in the primary user's storage area, including its own configuration and configurations that have been authorized to others.

[0038] If switching to a secondary user: the system does not directly set the settings at the operating system level, but instead reads the primary user's personal settings from the secondary user's storage area; then, through the user communication mechanism, it forwards the primary user's primary user settings request to the primary user; after receiving it, the primary user stores the settings in its own storage area for recording, and calls the MDM interface to apply this configuration to the system, thereby indirectly fulfilling the secondary user's setting requirements.

[0039] Therefore, it can be understood that through the above steps, each time a user switches, the system proactively and categorizes the shared and exclusive settings at the system's underlying level, resetting them from the previous user's state and refreshing them to the state desired by the target user, thus solving existing technical problems and achieving complete isolation and autonomous switching between multiple users.

[0040] As a second aspect of the present invention, an Android multi-user switching system based on settings category is proposed, comprising a user input module, a settings category module, a user storage management module, a user settings application module, and a user switching module; wherein: The user input module is used to obtain system settings and their target values ​​input by the user, including single-user settings, globally shared settings, and settings exclusive to the main user.

[0041] The settings category module has preset category rules for identifying and classifying user-input system settings into single-user settings, globally shared settings, or settings exclusive to the primary user.

[0042] The individual user settings should include at least wallpaper, theme and style, sound and vibration, and display brightness; the global sharing settings should include at least a list of Wi-Fi networks and a list of paired Bluetooth devices; and the main user's exclusive settings should include at least VPN configuration, developer options, APN access point, system certificate management, and factory reset.

[0043] The user storage management module is used to create and manage a separate globally shared settings storage area and a main user-specific settings storage area for each user. This module maintains a virtual settings policy space for each user, isolated from the Android native data area.

[0044] The user settings application module coordinates the application flow of settings after a user modifies system settings or after a user switch. This module includes a shared settings application unit and a primary user-specific settings application unit.

[0045] The shared settings application unit is used to obtain the current user's shared settings and call the MDM (Mobile Device Management) interface to apply the settings to the system. Specifically, when the shared settings application unit detects a change in a shared setting, it first stores it in the corresponding user's storage area, and then directly calls the MDM interface to synchronize the new settings to the system settings database so that the settings take effect immediately in the current session.

[0046] For example, when a user connects to a new Wi-Fi network under their personal account, the unit not only stores the password in its private storage area, but also enables the system to immediately connect to the network through the MDM interface, but this network is not visible to other user accounts.

[0047] The primary user-specific settings application unit retrieves the primary user-specific settings for the current user and determines whether the current user is the primary user. If the current user is the primary user, the settings are applied to the system directly by calling the MDM interface; otherwise, if the current user is not the primary user, a secure channel is established between the current user and the primary user to pass the settings to the primary user for authorization. Upon receiving the settings, the primary user processes them and stores them in their own storage area. If approved, the settings are applied by calling the MDM interface.

[0048] The user switching module is used to trigger the user switching process and drive the user settings application module to perform environment reconstruction after the switching is completed. It includes an authentication unit, a process management unit, and a settings synchronization unit.

[0049] The identity verification unit verifies the identity of the target user through at least biometric identification, fingerprint recognition, and password verification to ensure the security of the switching operation; after successful verification, the user switching module switches the current user to the target user.

[0050] The process management unit dynamically adjusts the running status of user processes according to user switching needs without affecting the normal operation of the system, so as to identify and handle running application processes and ensure the continuity and stability of applications during the switching process.

[0051] The settings synchronization unit automatically synchronizes the corresponding settings based on the user's switching. Specifically, when a user switches to the target user, this module first performs the following steps for globally shared settings: clearing the current system settings, reading them from the target user's storage, and applying them to the system. Second, for settings exclusive to the primary user, it determines whether to load the target user's own configuration or query the primary user's authorized list and apply it, based on the target user's identity, thereby avoiding settings confusion or interruption caused by the switching operation.

[0052] In one embodiment of the present invention, the proposed Android multi-user switching system based on setting item classification also includes a log recording module, which is used to record relevant information of user setting item modification operations and switching operations, including operator, operation item, timestamp and approval status, to support data traceability and security auditing, and to allow the main user or administrator to configure classification rules, approval strategies and other fine-grained settings, such as defining new exclusive settings, or setting whether certain shared settings can be modified by secondary users.

[0053] The technical scope of this invention is not limited to the content described above. Those skilled in the art can make various modifications and variations to the above embodiments without departing from the technical concept of this invention, and all such modifications and variations should fall within the protection scope of this invention.

Claims

1. A method for Android multi-user switching based on settings category, characterized by the following steps: include: The Android system settings are divided into single-user settings, globally shared settings, and settings exclusive to the main user. Create a separate storage area for each user, including a globally shared settings storage area and a settings storage area for the main user; Respond to user setting actions, retrieve the settings and their target values, and process them according to their categories: If it is a single-user setting, the setting will be made by calling the native Android system interface; If it is a globally shared setting, it will first be stored in the current user's global shared settings storage area and then synchronized to the system global settings through the mobile device management interface to take effect immediately; If it is a setting exclusive to the primary user, it is first stored in the primary user's exclusive settings storage area, and then the execution path is determined according to the current user's identity: if it is the primary user, it is set directly through the mobile device management interface; if it is a secondary user, the setting request is passed to the primary user through inter-user communication, and the primary user calls the mobile device management interface to set it. Perform user switching, and after completing the system-level switching, read the settings from the storage area corresponding to the target user according to the category of the settings and apply them to the system to rebuild the target user environment.

2. The multi-user handover method according to claim 1, characterized in that, The steps for reconstructing the target user environment include: For globally shared settings, first clear the current system settings through the mobile device management interface, then read the settings from the target user's global shared settings storage area and apply them to the system; For settings exclusive to the primary user, the settings are loaded based on the target user's identity: if the target user is the primary user, the settings are read from the primary user's exclusive settings storage area and applied; if the target user is a secondary user, the settings are read from their own primary user exclusive settings storage area and then handed over to the primary user for processing and application through inter-user communication.

3. The multi-user handover method according to claim 1, characterized in that, In the settings operation classification processing steps, the processing of globally shared settings includes: first saving the globally shared settings input by the user and their target values ​​to the current user's exclusive global shared settings storage area; then calling the mobile device management interface corresponding to the settings to synchronously write the settings and their target values ​​stored in the storage area into the Android system's global settings database.

4. The multi-user handover method according to claim 1 or 3, characterized in that, In the aforementioned settings operation classification processing steps, the processing of primary user-specific settings for secondary users includes: saving the primary user-specific settings input by the user and their target values ​​to the primary user-specific settings storage area for that secondary user; transmitting the stored settings request to the primary user process through the cross-user communication mechanism provided by the Android system; after receiving the request, the primary user stores the settings and target values ​​in its own primary user-specific settings storage area and calls the corresponding mobile device management interface to apply the settings to the system.

5. The multi-user handover method according to claim 2, characterized in that, When the target user is the primary user, the processing of primary user-specific settings includes: calling the mobile device management interface to clear the corresponding primary user-specific settings currently in effect at the system level; reading all primary user-specific settings and their target values ​​saved in the primary user's own primary user-specific settings storage area; and for each setting read, calling the corresponding mobile device management interface to apply it to the system.

6. The multi-user handover method according to claim 2 or 5, characterized in that, When the target user is a secondary user, the processing of primary user-specific settings includes: reading all primary user-specific settings and their target values ​​from the secondary user's primary user-specific settings storage area; transmitting each setting request to the primary user through inter-user communication; and after receiving the request, the primary user sequentially calls the corresponding mobile device management interface to apply it to the system.

7. The multi-user handover method according to claim 1, characterized in that, The single-user settings include at least wallpaper, theme and style, sound and vibration, and display brightness; The global sharing settings include at least a Wi-Fi network connection list and a Bluetooth device pairing list; The main user-specific settings include at least VPN configuration, developer options, APN access point, and system certificate management.

8. An Android multi-user switching system for implementing the method of any one of claims 1 to 7, characterized in that, include: The settings category module is used to identify and classify user-inputted system settings into single-user settings, globally shared settings, or main user-exclusive settings. The user storage management module is used to create and manage a separate globally shared settings storage area and a main user-specific settings storage area for each user. The user settings application module is used to coordinate and execute the storage, communication, and operation of various settings items through the mobile device management interface during user settings operations and user switching. The user switching module is used to trigger the user switching process and drive the user settings application module to perform environment reconstruction after the switching is completed.

9. The user switching system according to claim 8, characterized in that: The user settings application module includes: The shared settings application unit is used to handle the storage and synchronization of globally shared settings items; The primary user-specific settings application unit is used to handle the storage of primary user-specific settings, identity verification, cross-user communication, and application authorization.

10. The multi-user handover system according to claim 8, characterized in that, The user switching module includes: The authentication unit is used to verify the identity of the target user being switched. The process management unit is used to manage the state of user processes during user switching to ensure the continuity of application operation; The settings synchronization unit is used to trigger and coordinate the synchronization and reconstruction of globally shared settings and main user-specific settings after a user switch is completed.

Images