Whitelist management method, electronic device and computer-readable storage medium

Abstract

The present application provides a method, device, and storage medium for managing a whitelist. [Solution] The whitelist management method of the present application includes a step of receiving a clone app creation request from a first user requesting the creation of a clone app corresponding to a main app (S100), a step of obtaining a first whitelist corresponding to the first user, the first whitelist being a list of apps that are allowed to transition to a standby sleep mode (S200), and a step of adding the clone app to the first whitelist if the main app is in the first whitelist (S300).

Description

[Technical Field]

[0001] This application is filed based on a Chinese patent application bearing application number 202111238364.X and filed on October 25, 2021, and claims priority to that Chinese patent application, the entire contents of which are incorporated herein by reference.

[0002] The embodiments of the present application relate to, but are not limited to, the technical field of communications, for example, a method for managing a whitelist, electronic Equipment and computer readable Regarding storage media. [Background technology]

[0003] Standby sleep mode is a power-saving feature implemented in devices. It is an application mode of a device, such as Doze mode or App Standby mode, that helps users extend the battery life of the device by managing the behavior of apps when the device is not connected to a power source. However, in actual use, a clone app is typically created for a certain app so that apps from different accounts can be used simultaneously on the same device. After a device enters standby sleep mode, the main app corresponding to the clone app continues to operate normally, but the clone app is typically managed to save power. In this case, the user cannot use the clone app normally, and the management power consumption of the current device increases. Summary of the Invention [Problem to be solved by the invention]

[0004] The following is a brief summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

[0005] The embodiments of the present application provide a whitelist management method that can reduce power consumption for management. electronic Equipment and computer readable Provide a storage medium. [Means for solving the problem]

[0006] In a first aspect, an embodiment of the present application provides a whitelist management method, the method including: receiving a clone app creation request from a first user requesting creation of a clone app corresponding to a main app; obtaining a first whitelist corresponding to the first user, the first whitelist being a list of apps that are allowed to transition to a standby sleep mode; and, if the main app is in the first whitelist, adding the clone app to the first whitelist.

[0007] In a second aspect, an embodiment of the present application further provides an electronic device, the device comprising: a receiving processing module that receives a clone app creation request from a first user requesting the creation of a clone app corresponding to a main app; an acquisition module that acquires a first whitelist corresponding to the first user, the first whitelist being a list of apps that are allowed to transition to a standby sleep mode; and a list processing module that adds the clone app to the first whitelist if the main app is in the first whitelist.

[0008] In a third aspect, an embodiment of the present application further provides an electronic device, the electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor, when executing the computer program, realizing the whitelist management method described in any one of the first aspects.

[0009] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, the computer-executable instructions being configured to perform the whitelist management method described in any one of the first aspects.

[0010] Other features and advantages of the present application will be set forth in the following description, and in part will be obvious from the description, or may be learned by the practice of the present application. The objectives and other advantages of the present application may be achieved and obtained by the structures particularly pointed out in the description, claims and drawings.

[0011] The accompanying drawings are intended to provide a further understanding of the technical solution of the present application, constitute a part of the specification, and are used to interpret the technical solution of the present application together with the examples of the present application, and are not intended to constitute limitations on the technical solution of the present application. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a schematic diagram of a module block diagram of an electronic device according to an embodiment of the present application. [Figure 2] 1 is a schematic flowchart of a method for managing a whitelist according to an embodiment of the present application; [Figure 3] 1 is a schematic flowchart of a user switching process in a whitelist management method according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0013] In order to make the purpose, technical solution and advantages of the present application clearer, the present application will be described in more detail below in conjunction with the accompanying drawings and examples, in which the specific examples described herein are used only to interpret the present application and are not used to limit the present application.

[0014] Although the schematic diagrams of the devices show functional module divisions and the flowcharts show logical orders, in some cases the module divisions within the devices may differ, or the steps shown or described may be performed in a different order than in the flowcharts. The terms "first," "second," etc. in the specification, claims, and drawings are used to distinguish between similar objects and are not necessarily intended to describe a specific order or chronology.

[0015] In the related art, standby sleep mode is a power-saving feature implemented in a device. It is an application mode of a device, such as a low-power consumption (Doze) mode or an application standby mode, that helps users extend the battery life of the device by managing the behavior of applications when the device is not connected to a power source. At the same time, during actual use, a clone application is typically created for a certain application. After a device enters standby sleep mode, the main application corresponding to the clone application is still running. However, the clone application is typically managed for power saving purposes, resulting in delays and even failures to receive messages from the clone application. For example, if a social application is cloned and the device enters standby sleep mode, messages from the clone application may be delayed or even fail to be received. Therefore, the user must frequently switch between standby sleep mode and normal mode to properly receive messages from the clone application, which increases the device's power consumption for management. Based on this, embodiments of the present application propose a whitelist management method, device, and storage medium that can reduce unnecessary management and ultimately reduce power consumption for management.

[0016] First, the related noun terms according to the embodiments of the present application will be explained as follows.

[0017] Doze mode refers to reducing battery consumption by slowing down background CPU and network activity in apps when the device is idle for extended periods of time.

[0018] App Standby mode prohibits apps from accessing the network or executing pending tasks or synchronization if the user has not tapped the app for a certain period of time. If the device is idle for a long period of time, the system will allow idle apps to access the network approximately once a day.

[0019] In the following, reference will be made to the embodiment shown in FIG. 1. The embodiment of the present application proposes an electronic device, and the electronic device includes: a reception processing module 100 that receives a clone application creation request from a first user requesting creation of a clone application corresponding to a main application; An acquisition module 200 for acquiring a first whitelist corresponding to a first user, the first whitelist being a list of applications that are allowed to transition to a standby sleep mode; and a list processing module 300 that adds the clone app to the first whitelist if the main app is in the first whitelist.

[0020] The standby sleep mode includes at least one of a low-power consumption mode and an application standby mode, and the electronic device is, for example, a terminal such as a mobile phone or a tablet. In the case of a mobile phone, when the mobile phone receives a request to create a clone application of application A from a first user, a clone application B is obtained. Application A being on the first whitelist means that application A can continue to operate normally in the background in standby sleep mode. At this time, the acquisition module 200 and the list processing module 300 automatically add clone application B to the first whitelist. In some embodiments, after application A and clone application B operate, if the terminal is switched from normal mode to standby sleep mode, application A and clone application B continue to operate normally. In other embodiments, after clone application B operates normally, if the terminal is switched from normal mode to standby sleep mode, clone application B continues to operate normally. Therefore, according to the embodiments of the present application, unnecessary management of clone application B can be reduced, and thus the management power consumption of the entire device can be reduced.

[0021] Referring to the embodiment of FIG. 1 , the device further includes a clone application listening module 400 and a multi-user listening module 500. The multi-user listening module 500 listens to the execution status of user creation and user switching operations, collects the current user's app list, and sends the app list to the list processing module 300. The list processing module 300 adjusts the current user's whitelist based on the app list and the first whitelist. For a single user or any user in a multi-user system, after listening for the successful creation of a clone application by the reception processing module 100, the clone application listening module 400 obtains information about clone application B and sends it to the list processing module 300 to adjust the first whitelist. In the case of a multi-user system, after a successful user switch, the current user's whitelist is adjusted again. For example, assume that the first user is the current user and the second user is the user to be switched to. The reception processing module 100 processes the user switch request and switches to the second user. The multi-user listening module 500 listens for the successful switch and transmits the second user's app list information to the list processing module 300, which then adjusts the list based on the app list. For example, when a new second user is created, the multi-user listening module 500 listens for the successful creation of the second user and transmits the second user's user information to the list processing module 300. The list processing module 300 can then obtain an app list corresponding to the second user's user information. At this time, the multi-user listening module 500 traverses the app list to determine whether an app with a name matching an app in the first whitelist exists. If an app exists, the module adds the app identifier of the clone app corresponding to the app name to the first whitelist.

[0022] It should be noted that the multi-user listening module 500 and the clone application listening module 400 can create different threads for listening, and further realize efficient list adjustment in real time.

[0023] Therefore, based on the above-described embodiment, by automatically adding the clone app corresponding to the main app to the first whitelist, both the main app and the corresponding clone app can operate normally after the device enters standby sleep mode, and there is no need to perform unnecessary management of the clone app. Therefore, compared to conventional methods that require management of the clone app after entering standby sleep mode, the embodiment of the present application can reduce power consumption for management.

[0024] As will be appreciated by those skilled in the art, the topology configuration shown in FIG. 1 does not constitute a limitation on embodiments of the present application, and may include more or fewer modules than shown, or may combine some modules or have different module arrangements.

[0025] Meanwhile, the embodiments of the present application further propose a method for managing a whitelist. Various embodiments of the present application will be further described below in conjunction with the accompanying drawings.

[0026] Referring to the embodiment shown in FIG. 2, the whitelist management method includes the following steps:

[0027] In step S100, a request to create a clone application corresponding to a main application is received from a first user.

[0028] The main app is pre-installed on the device's system or downloaded from an app store. If the clone app processing request is successfully created, a clone app with the same app functions and app name as the main app is generated. The main app and the clone app can be executed simultaneously under the same system user. For example, a first user can log in to the main app and the clone app using two different login accounts.

[0029] Note that the app names of the cloned app and the main app are the same. In some embodiments, the cloned app is assigned a unique app identifier after successful creation, and the main app also has a unique app identifier. In some embodiments, the app identifier is a series of numbers.

[0030] For example, taking a main app A as an example, a first user issues a request to create a clone app for the main app A, and the terminal generates a clone app B corresponding to the main app A, and in some embodiments, an app identifier for the clone app B is generated.

[0031] In step S200, a first whitelist corresponding to a first user is obtained, which is a list of applications that are permitted to transition to a standby sleep mode.

[0032] The first whitelist is a whitelist that runs on the terminal. After the first whitelist is set and the terminal enters standby sleep mode, it manages apps other than those in the first whitelist, thereby ensuring that only apps in the first whitelist operate normally, thereby achieving the purpose of power saving.

[0033] In step S300, if the main application is in the first whitelist, the clone application is added to the first whitelist.

[0034] In addition, the app functions of the main app and the clone app are the same, and for the same system user, taking WeChat as an example, suppose that user 1 has two WeChat accounts. In this case, user 1 can log in to WeChat A with WeChat account 1 and log in to the clone app of WeChat A with WeChat account 2, and can use the two WeChat accounts on the same device to handle different tasks. Meanwhile, user 1's needs for WeChat A and the corresponding clone app are similar or the same, and both require timely acquisition and processing of information on WeChat. Therefore, by determining whether the main app is on the first whitelist and automatically adding the clone app, unnecessary management of the clone app in standby sleep mode can be reduced, and user operations on the clone app can be reduced, thereby improving the user experience.

[0035] In some embodiments, referring to the embodiment of FIG. 1, after step S100, the clone application listening module 400 can obtain information about clone application B by listening and transmit it to the list processing module 300 to perform processing step S300. This allows the list processing to be performed in synchronization with the user request processing, and improves the efficiency of modularized processing.

[0036] Therefore, by automatically adding the clone app corresponding to the main app to the first whitelist, both the main app and the corresponding clone app can operate normally after the device enters standby sleep mode, and there is no need to manage the clone app. Therefore, compared to conventional methods that require management of the clone app after entering standby sleep mode, the embodiments of the present application can reduce power consumption for management.

[0037] The standby sleep mode includes at least one of a low power consumption mode and an app standby mode, and correspondingly, the first whitelist includes at least one of a low power consumption whitelist, which is a list of apps that are allowed to transition to the low power consumption mode, and an app standby whitelist, which is a list of apps that are allowed to transition to the app standby mode.

[0038] In some embodiments, the terminal supports both the low power consumption mode and the application standby mode. In this case, a low power consumption whitelist is set for the low power consumption mode, and an application standby whitelist is set for the application standby mode. Step S200 is performed to obtain a low power consumption whitelist and an application standby whitelist, respectively. Step S300 is performed on the low power consumption whitelist and the application standby whitelist, respectively, to update the first user's low power consumption whitelist and application standby whitelist. In other embodiments, the terminal supports only the low power consumption mode. In this case, after obtaining the low power consumption whitelist in step S200, an updated low power consumption whitelist is obtained in step S300. In other embodiments, since the terminal supports only the application standby mode, after obtaining the application standby whitelist in step S200, an updated application standby whitelist is obtained in step S300. After the corresponding whitelists are updated, the terminal system applies the updated whitelists.

[0039] In step S300, if the main app corresponding to the clone app is in the first whitelist, adding the clone app to the first whitelist includes obtaining an app name set corresponding to the first whitelist, and if the app name set contains an app whose app name matches the app name of the main app, adding the clone app to the first whitelist.

[0040] Note that an application name exists corresponding to every application in the first whitelist, and the set of application names of all applications in the first whitelist is an application name set.

[0041] For example, suppose the first whitelist contains app information corresponding to apps C, D, E, F, and G. If the app name of app D is the same as the main app (i.e., the current request is to create a clone app of app D), clone app B corresponding to the main app is automatically added to the first whitelist. If the app names of apps C, D, E, F, and G are all different from the main app, no operation is required for clone app B.

[0042] The step of adding the cloned application to the first whitelist includes the step of adding an application identifier of the cloned application to the first whitelist.

[0043] Each app (including the main app and clone apps) is distinguished by a unique identifier (app identifier) ​​on the device. By adding the app identifier to the first whitelist, managing and maintaining the first whitelist currently running on the device becomes simpler and more efficient because only the app identifier needs to be maintained.

[0044] As an example, assume that a first whitelist has app identifiers {1, 2, 3, 4, 5} corresponding to app C, app D, app E, app F, and app G, and the app identifier of the clone app is 6, then after the clone app is added, the first whitelist becomes {1, 2, 3, 4, 5, 6}.

[0045] Furthermore, after logging in with the new user account, because the other user's app is in the first whitelist, the other user's app will still be allowed by the terminal system, and the execution of data services by the other user's app may result in increased power consumption. Based on this, referring to the embodiment shown in Figure 3, taking the case where the current user is the first user in a multi-user system as an example, the method of the embodiment of the present application further includes the following steps:

[0046] In step S400, in response to the received user switching request, the current user of the terminal is switched from the first user to the second user.

[0047] In step S500, a first pre-set corresponding to a second user is acquired, the first pre-set being a list of applications of the second user that are permitted to enter the standby sleep mode.

[0048] The first application set is a list of applications configured by the second user. Each application on the terminal also includes application configuration information for a different user.

[0049] In step S600, an adjustment process is performed on the first whitelist according to the first preset to obtain a second whitelist for a second user, where the adjustment process includes: removing apps from the first whitelist that are not in the first app set; and adding apps that are in the first set of apps and that are not in the first whitelist to the first whitelist.

[0050] In a multi-user system, after a user switch occurs, if the first whitelist contains app information for the previous user and the app exists in the system of the second user, the app will continue to be permitted by the system even after the system enters standby sleep mode, allowing power-consuming actions such as data services to be performed. Therefore, by deleting the app identifiers of apps that do not exist in the first app set from the first whitelist, it is possible to ensure that only apps set for the second user can be executed.

[0051] Note that there are situations where the app lists permitted to be added to the whitelist by the first user and the second user are different. For example, some apps set for the second user, such as a drawing software, are not included in the first whitelist at the time of execution of the first user, so it is necessary to add an app that is not included in the first whitelist of the second user.

[0052] In some embodiments, only one of the two adjustment methods described above is present, but there are also cases where two are present, and there is no contradiction between the two adjustment methods.

[0053] As an example, assume that a first whitelist is {1, 2, 3, 4, 5}, where 1, 2, 3, 4, and 5 correspond to app C, app D, app E, app F, and app G, respectively. In some embodiments, if a first set of apps is {app C, app D, app E, app F}, then the app with app identifier 5 in the first whitelist needs to be removed to obtain a second whitelist with {1, 2, 3, 4}. In other embodiments, if the app identifiers corresponding to the first set of apps are {1, 2, 3, 4, 7}, where app C, app D, app E, app F, app G, and app H, respectively, then the app with app identifier 5 in the first whitelist needs to be removed and the app with app identifier 7 needs to be added to the first whitelist to obtain a second whitelist with {1, 2, 3, 4, 7}, in which case apps C, app D, app E, app F, and app H can run in standby sleep mode.

[0054] The second whitelist is a whitelist executed on the terminal after execution of step S600.

[0055] In addition, for multi-users, taking as an example a case where creation of a new user is permitted and the second user is the user to be created, an embodiment of the present application further includes a step of obtaining a first app set corresponding to the second user in response to a user creation request from the second user, and a step of adding a first app that exists in the first app set and whose app name matches an app in the first whitelist to the first whitelist.

[0056] Note that a match between applications means a match between application names, and in the case of the first application, the first application is a main application or a clone application.

[0057] Furthermore, clone apps that match apps in the first whitelist of the second user can be added to the whitelist, and when switching from the first user to the second user, apps whose main apps are not in the first whitelist and their corresponding clone apps can be added. This reduces the need for app adjustments in the second whitelist, thereby improving switching efficiency when switching to the second user.

[0058] The step of adding a first app that exists in the first application set and whose application name matches an application in the first whitelist to the first whitelist includes the steps of: obtaining an application name set corresponding to the first whitelist; traversing all applications in the application name set to match the application names with the applications in the first whitelist to obtain several first applications; and adding application identifiers of clone applications corresponding to the first applications to the first whitelist, respectively.

[0059] Note that the first whitelist is managed using app identifiers, and in a multi-user system, in some embodiments, each main app shares an app identifier under different users, so it is only necessary to add the clone app of the app to the first whitelist, and the clone app can be quickly enabled after switching.

[0060] For example, when creating a second user, a clone app B is created for a main app A, the first whitelist is {1, 2, 3, 4, 5}, and the app name of the main app A matches the app name of the app corresponding to app identifier 1, then the app identifier 6 of the clone app B is added to the first whitelist, i.e., the first whitelist becomes {1, 2, 3, 4, 5, 6}.

[0061] Note that with reference to the embodiments shown in FIGS. 2 and 3, in some embodiments, the terminal supports only adding a clone app in steps S100 to S300. In some other embodiments, the terminal supports steps S100 to S300, and identifying and deleting apps other than those of the current user when switching between multiple users. Furthermore, the terminal automatically whitelists clone apps for a single user, and ensures that all apps entering standby sleep mode in a multi-user environment are apps that the current user is permitted to run, thereby reducing power consumption behavior of abnormal apps. In some other embodiments, the terminal supports steps S100 to S300, and adding a clone app created for a new user. In some other embodiments, the terminal supports steps S100 to S300, adding a clone app when creating a new user, and identifying and deleting apps other than those of the current user when switching between multiple users.

[0062] In a multi-user system, there is no order to the creation of new users and the switching of users.

[0063] In addition, an embodiment of the present application further proposes an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, it realizes the above-mentioned whitelist management method.

[0064] The memory can be used as a non-transitory computer-readable storage medium to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, the memory may include high-speed random access memory, or may include non-transitory memory, such as at least one magnetic disk memory device, flash memory device, or other non-transitory solid-state memory device. In some embodiments, the memory may include memory located remotely from the processor, and these remote memories may be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, a company intranet, a local area network, a mobile communication network, and combinations thereof.

[0065] In addition, the network device of this embodiment may be applied as an electronic device of the network architecture of the embodiment shown in Figure 1, and since the electronic device in this embodiment has the same inventive concept as the electronic device of the embodiment shown in Figure 1 and the whitelist management method shown in Figure 2, these embodiments have the same realization principle and technical effect, and detailed explanations are omitted here.

[0066] The non-transitory software programs and instructions necessary to implement the whitelist management method of the above-described embodiment are stored in a memory, and when executed by a processor, perform the whitelist management method of the above-described embodiment, for example, method steps corresponding to method steps S100 to S300 in FIG. 2 described above, or method steps S100 to S300, S400 to S600, and sub-steps shown in FIG. 2 and FIG. 3. For example, referring to the embodiment shown in FIG. 2, the processor listens for a main app processing request from a first user, obtains app information of the clone app, obtains a first whitelist, compares the app name of each app in the first whitelist with the app name of the main app, and if there is an app name in the first whitelist that matches an app, adds the app identifier of the clone app to the first whitelist.

[0067] The present application further provides a computer-readable storage medium storing computer-executable instructions for performing the first whitelist management method described above, for example, performing method steps corresponding to method steps S100 to S300 in Fig. 2 described above, or method steps S100 to S300, S400 to S600, and sub-steps shown in Figs. 2 and 3.

[0068] All or part of the steps in the methods and systems disclosed above can be implemented as software, firmware, hardware, or any suitable combination thereof. Some or all of the physical assemblies can be implemented as software executed by a processor such as a central processing unit, digital signal processor, or microprocessor, as hardware, or as an integrated circuit such as an application-specific integrated circuit. Such software can be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). Those skilled in the art will recognize that the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or any other medium that can be used to store desired information and that can be accessed by a computer. Additionally, communication media typically includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery media, as known to those skilled in the art.

[0069] Although several examples of the present application have been specifically described above, the present application is not limited to the above embodiments. Those skilled in the art may make various equivalent modifications or substitutions that fall within the scope of the claims of the present application without departing from the essence of the present application. [Explanation of symbols]

[0070] 100 Receiving Processing Module 200 Acquisition Module 300 List Processing Module 400 Clone App Listening Module 500 Multi-User Listening Modules

Claims

1. A method for managing a whitelist executed by an electronic device, comprising: receiving a clone application creation request from a first user requesting creation of a clone application corresponding to the main application; obtaining a first whitelist corresponding to the first user, the first whitelist being a list of applications that are permitted to transition to a standby sleep mode; If the main app is in the first whitelist, adding the clone app to the first whitelist; How to manage whitelists, including:

2. the standby sleep mode includes at least one of a low power consumption mode and an application standby mode; Correspondingly, the first whitelist includes at least one of a low power consumption whitelist, which is a list of apps that are allowed to transition to a low power consumption mode, and an app standby whitelist, which is a list of apps that are allowed to transition to the app standby mode.

3. If the main app is in the first whitelist, adding the clone app to the first whitelist may include: obtaining a set of application names corresponding to the first whitelist; adding the cloned app to the first whitelist if the set of app names includes an app whose name matches the app name of the main app; The method for managing a whitelist according to claim 1 , comprising:

4. The step of adding the cloned app to the first whitelist includes: The whitelist management method according to claim 3 , further comprising adding an application identifier of the clone application to the first whitelist.

5. switching a current user of the terminal from the first user to a second user in response to the received user switching request; obtaining a first preset set corresponding to the second user, the first preset set being a list of apps of the second user that are permitted to transition to the standby sleep mode; performing an adjustment process on the first whitelist according to the first preset to obtain a second whitelist of the second user; further comprising The adjustment process includes: removing apps from the first whitelist that are not in the first set of apps; adding apps that are in the first set of apps and that are not in the first whitelist to the first whitelist; The method for managing a whitelist according to claim 1 , comprising at least one of:

6. acquiring a first preset corresponding to a second user in response to a user creation request of the second user; adding a first app that is in the first set of apps and has an app name that matches an app in the first whitelist to the first whitelist; The method of claim 1 further comprising:

7. The step of adding a first app that is present in the first app set and has an app name that matches an app on the first whitelist to the first whitelist includes: obtaining a set of application names corresponding to the first whitelist; traversing all apps in the set of app names and matching app names with apps in the first whitelist to obtain a number of first apps; adding application identifiers of clone applications corresponding to the first application to the first whitelist; The method for managing a whitelist according to claim 6, comprising:

8. a reception processing module that receives a clone application creation request from a first user, the clone application creation request requesting creation of a clone application corresponding to the main application; an acquisition module that acquires a first whitelist corresponding to the first user, the first whitelist being a list of applications that are permitted to transition to a standby sleep mode; a list processing module that adds the cloned app to the first whitelist if the main app is in the first whitelist; An electronic device comprising:

9. 1. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, When the processor executes the computer program, the processor realizes the whitelist management method according to any one of claims 1 to 7. electronic equipment.

10. A computer-readable storage medium storing computer-executable instructions, comprising: The computer-executable instructions are configured to perform at least the method for managing a whitelist according to any one of claims 1 to 7. A computer-readable storage medium.

Images