WO2018049610A1

WO2018049610A1 - Permission control method and device

Info

Publication number: WO2018049610A1
Application number: PCT/CN2016/099066
Authority: WO
Inventors: 伍亮雄; 刘海涛; 刘鸣
Original assignee: 北京小米移动软件有限公司
Priority date: 2016-09-14
Filing date: 2016-09-14
Publication date: 2018-03-22
Also published as: CN106462698A

Abstract

Disclosed are a permission control method and device, belonging to the technical field of computers. The method comprises: obtaining an interface startup request sent by an application; detecting whether the application is running in the background; if the application is running in the background, detecting whether the application has a background interface startup permission, the background interface startup permission referring to a permission for the application to pop up an interface while running in the background; if the application does not have the background interface startup permission, prohibiting the application from popping up an interface. The background interface startup permission only permits applications which have the background interface startup permission to pop up an interface while running in the background, thereby preventing unpermitted applications from misusing the function of popping up an interface while running in the background, preventing user operations from being affected, and increasing system performance.

Description

Authority control method and device

Technical field

The present disclosure relates to the field of computer technologies, and in particular, to a rights control method and apparatus.

Background technique

Users can install various applications in terminal devices such as mobile phones and tablets to expand the functions of the terminal devices.

In the related art, the operating system of the terminal device allows the application to pop up the interface when it runs in the background. Some applications can use this function to pop up the setting interface when running in the background, such as the function guiding interface, the information pushing interface, the advertising interface, and the like.

Summary of the invention

Embodiments of the present disclosure provide a method and apparatus for controlling rights. The technical solution is as follows:

According to a first aspect of an embodiment of the present disclosure, there is provided an access control method, the method comprising:

Obtain an interface startup request sent by the application;

Detecting whether the application is running in the background;

If the application is running in the background, detecting whether the application has the background startup interface permission; wherein the background startup interface permission refers to the permission of the application to pop up the interface when running in the background;

If the application does not have the background startup interface right, the interface of the application is prohibited from popping up.

Optionally, the detecting whether the application has the background startup interface right includes:

Calling the permission detection method of the application rights manager, and sending the permission detection request to the permission detection method; wherein the permission detection request carries an identifier of the application, and the permission detection method is used to use the application permission manager The middle query obtains whether the application has the permission of the background startup interface;

Acquiring the permission detection result returned by the permission detection method; wherein the permission detection result is: the application has the background startup interface authority, or the application does not have the background startup interface authority.

Optionally, the method further includes:

Obtaining an identifier of the application from the interface startup request;

The identifier of the application includes: a package name of the application and a UID (User Identification) corresponding to the current system.

Optionally, the detecting whether the application is running in the background includes:

Obtaining a system stack top application, where the system top stack application refers to an application currently running in the foreground;

Detecting whether the application is the system top application;

If the application is not the system stack top application, determining that the application is running in the background;

If the application is the system top-of-stack application, it is determined that the application is running in the foreground.

Optionally, the prohibiting the interface of the application from popping up includes:

The execution of the interface startup request is terminated.

Optionally, the method further includes:

Receiving a recommendation switch setting of the background startup interface permission of the application sent by the cloud server, where the recommendation switch is set by the cloud server according to the number of users who open the background startup interface permission for the application and is the application The number of users who close the permission of the background startup interface is determined;

And setting, according to the recommendation switch, the right to enable or disable the background startup interface.

According to a second aspect of the embodiments of the present disclosure, there is provided an authority control apparatus, the apparatus comprising:

The request acquisition module is configured to obtain an interface startup request sent by the application;

Running a detection module configured to detect whether the application is running in the background;

The permission detection module is configured to detect, when the application is running in the background, whether the application has the background startup interface authority; wherein the background startup interface permission refers to the permission of the application to pop up the interface when running in the background;

The pop-up module is disabled, and is configured to prohibit the interface of the application from popping up when the application does not have the permission of the background startup interface.

Optionally, the permission detection module includes:

The method call submodule is configured to invoke a permission detection method of the application rights manager, and send a permission detection request to the permission detection method; wherein the permission detection request carries an identifier of the application, and the permission detection method uses Querying, by the application rights manager, whether the application has the background startup interface authority;

The result obtaining sub-module is configured to obtain the permission detection result returned by the permission detection method, wherein the permission detection result is: the application has the background startup interface authority, or the application does not have the background Start interface permissions.

Optionally, the device further includes:

An identifier obtaining module, configured to obtain an identifier of the application from the interface startup request;

The identifier of the application includes: a package name of the application and a UID corresponding to the current system.

Optionally, the running detection module includes:

a top-of-stack acquisition sub-module configured to acquire a system stack top application, where the system top-of-stack application refers to an application currently running in the foreground;

An application detection submodule configured to detect whether the application is the system top application;

a first determining submodule configured to determine that the application is running in the background when the application is not the system top application;

The second determining submodule is configured to determine that the application is running in the foreground when the application is the system stack top application.

Optionally, the prohibiting pop-up module is configured to terminate execution of the interface startup request.

Optionally, the device further includes:

a receiving module configured to receive a recommendation switch setting of the background startup interface permission of the application sent by the cloud server, where the recommendation switch is set by the cloud server according to the permission to open the background startup interface for the application The number of users and the number of users who have turned off the background startup interface rights for the application;

The permission switch module is configured to enable or disable the background startup interface authority for the application according to the recommended switch setting.

According to a third aspect of the embodiments of the present disclosure, there is provided an authority control apparatus, the apparatus comprising:

processor;

a memory for storing executable instructions of the processor;

Wherein the processor is configured to:

Obtain an interface startup request sent by the application;

Detecting whether the application is running in the background;

The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects:

Detect whether the application is running in the background after the request is initiated by the interface sent by the application. If it is detected that the application is running in the background, it continues to detect whether the application has the background startup interface right. If the application does not have the background startup interface permission, the application interface is prohibited from popping up; since the background startup interface permission is added, only the background is allowed. The application that launches the interface permission pops up the interface when running in the background, avoiding the function of popping up the interface when running in the background without the permission of the application, avoiding affecting the user operation and providing system performance.

The above general description and the following detailed description are intended to be illustrative and not restrictive.

DRAWINGS

The accompanying drawings, which are incorporated in the specification

FIG. 1 is a flowchart of a method for detecting rights according to an exemplary embodiment;

2A is a block diagram of an authority control apparatus according to an exemplary embodiment;

2B is a block diagram of an authority control apparatus according to another exemplary embodiment;

FIG. 3 is a block diagram of an apparatus, according to an exemplary embodiment.

detailed description

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. The following description refers to the same or similar elements in the different figures unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with aspects of the present disclosure as detailed in the appended claims.

In the related art, since the operating system provides the function of popping up the interface when running in the background, the right to use the function is not controlled, which causes some applications to abuse the function, affecting user operations and system performance. For example, when the user is watching the video, another background running application pops up an advertising interface, which is superimposed on the current video playing interface, affecting the normal viewing of the user. Based on this, the embodiments of the present disclosure provide a method for controlling rights, and an apparatus based on the method, to solve the problems in the related art. The core idea of the technical solution provided by the embodiment of the present disclosure is to add a background startup interface permission in the Application Operations Manager, and the background startup interface permission refers to the permission of the application to pop up the interface when running in the background. Manage by application rights The device manages whether each application installed in the terminal device has the permission, and only allows the application having the permission of the background startup interface to pop up the interface when running in the background, so as to prevent the unauthorized application from abusing the function of popping up the interface when running in the background.

The method provided by the embodiment of the present disclosure may be a terminal device, such as a mobile phone, a tablet computer, an e-book reader, a multimedia playback device, a PDA (Personal Digital Assistant), a wearable device, or the like. In the embodiment of the present disclosure, the type of the operating system of the terminal device is not limited, such as an Android (Android) operating system, an iOS operating system, a Windows Phone operating system, and the like.

FIG. 1 is a flowchart of a method for detecting rights according to an exemplary embodiment. This method can be applied to a terminal device. The method can include the following steps:

In step 101, an interface startup request sent by the application is obtained.

When the application needs to display the interface, an interface startup request is sent to the system service, and the interface startup request is used to request the display interface. In the embodiment of the present disclosure, the type of the application is not limited, and may be various types of applications installed and operated in the terminal device, such as a social application, a call communication application, an online shopping payment application, a living consumer application, a video playback application, and security. Antivirus applications, browsers, etc. In the embodiment of the present disclosure, the interface of the application is a user interface (UI). In the Android system, the interface is represented by activity. In the embodiment of the present disclosure, the system service may be an interface startup management service, such as an ActivityStack Supervisor of the Android system, and an interface startup management service is used to manage the interface startup in the system.

Taking the Android system as an example, the interface startup management service provides an ActivityStackSupervisor.startActivityLocked method, and the application can send an interface startup request to the interface startup management service by calling the method.

In step 102, it is detected whether the application is running in the background.

The system service detects if the app is running in the background. The application runs in the foreground, which means that the application runs directly from the window and displays an interface that can interact with the user. The application runs in the background, which means that the application runs in the resource manager. Generally, the interface is not displayed, but the system resources are occupied.

In one example, this step includes the following substeps:

1. Obtain the system top application;

2. Detect whether the application is a system top application;

3. If the application is not a system stack top application, it is determined that the application is running in the background;

4. If the application is a system stack top application, it is determined that the application is running in the foreground.

The system stack top application refers to an application that is currently running in the foreground. By acquiring the system stack top application, whether the application of the system stack top application and the above sending interface startup request is the same application, if the two are the same application, the sending is performed. The application of the interface startup request runs in the foreground, otherwise the application that determines the sending interface startup request runs in the background.

In step 103, if the application is running in the background, it is detected whether the application has the background startup interface authority.

When the system service detects that the application is running in the background, the system service continues to detect whether the application has the background startup interface permission. The background startup interface permission refers to the permission of the application to pop up the interface when running in the background. In the embodiment of the present disclosure, the pop-up interface when the application is running in the background refers to triggering the display of an interface superimposed on the interface of the application currently running in the foreground for display when the application is running in the background. In the embodiment of the present disclosure, by adding the background startup interface authority in the application rights manager in advance, the system can perform rights management on the function of the pop-up interface in the background runtime. Exemplarily, the name of the background startup interface permission is OP_BACKGROUND_START_ACTIVITY, and the identifier (also called value) of the background startup interface permission is 10021, which is used to uniquely identify the permission. In the application rights manager, the identifiers corresponding to different permissions are also different.

Optionally, this step may include the following sub-steps:

1. Calling the permission detection method of the application rights manager, and sending a permission detection request to the permission detection method;

The permission detection request carries an identifier of the application, and the identifier of the application is used to uniquely identify an application. Optionally, the identifier of the application includes: a package name of the application and a UID corresponding to the current system. The application package name and the UID corresponding to the current system can uniquely identify an application in the current system. Even if the terminal device supports multiple systems, the system can distinguish the system and accurately determine the application that makes the request in the current system. In addition, the application may carry the identifier of the application in the interface startup request, and accordingly, the system service may obtain the identifier of the application from the interface startup request.

The permission detection method is used to query whether the application has the background startup interface permission from the application permission manager. Taking the Android system as an example, the ActivityStackSupervisor may call the AppOpsManager.checkOpNoThrow method, and send a permission detection request carrying the identifier of the application to the method.

2. Obtain the permission detection result returned by the permission detection method;

Among them, the permission detection result is: the application has the background startup interface authority, or the application does not have Start the interface permissions in the background. Still taking the Android system as an example, after the AppOpsManager.checkOpNoThrow method is called, according to the application identifier, the application permission manager queries whether the application has the background startup interface permission. If the application has the background startup interface permission, the AppOpsManager.checkOpNoThrow method returns information indicating the information to the WindowManagerService; if the application does not have the background startup interface permission, the AppOpsManager.checkOpNoThrow method returns information indicating that the information is not available to the WindowManagerService.

In one example, an example of code that implements the ability to detect whether an application has background launch interface permissions is as follows:

In addition, if the system service detects that the application is running in the foreground in step 102, the system service processes the interface startup request according to the original normal processing flow, and executes logic of the subsequent startup interface (activity).

In step 104, if the application does not have the background startup interface permission, the application interface is prohibited from popping up.

If the application does not have the background startup interface permission, the system service prohibits the interface that the application requests to display from popping up. That is, the interface of the system service prohibiting the application from being requested to be displayed is superimposed on the interface of the application currently running in the foreground.

In an example, if the application does not have the background startup interface permission, the system service terminates the execution interface startup request, and does not execute the logic of the subsequent startup interface (activity).

In addition, if the application has the background startup interface permission, the system service processes the interface startup request according to the original normal processing flow, and executes the logic of the subsequent startup interface (activity).

In summary, the method provided in this embodiment detects whether the application is running in the background after acquiring the interface initiated by the application, and if it detects that the application is running in the background, it continues to detect whether the application has the background startup interface permission. If the application does not have the background startup interface permission, the application interface is prohibited from popping up; because the background startup interface permission is added, only the application having the background startup interface permission is allowed to pop up in the background to avoid unauthorized application abuse. The function of pop-up interface when running in the background avoids affecting user operations and providing system performance.

It should be added that the application has the background startup interface permission, which can be set by the system default or by the user.

Optionally, the cloud server corresponding to the operating system can be separately counted for each application to be turned on/off. The number of users who started the interface permissions in the background. For an application, the cloud server collects the number of users who have the background startup interface permission for the application and the number of users who turn off the background startup interface permission for the application. According to the above statistics, the recommendation switch setting of the background startup interface permission of the application is determined. . Exemplarily, the cloud server determines the recommended switch setting of the background startup interface permission of the application according to the proportion of the number of users who open the background startup interface permission for the application and the number of users who turn off the background startup interface authority. After the terminal device installs the application, the cloud server may send the recommended switch setting of the background startup interface permission of the application to the terminal device; correspondingly, the terminal device receives the recommended switch setting of the background startup interface permission of the application sent by the cloud server. The recommended switch setting refers to the permission to enable or disable the background startup interface. The terminal device sets the right to enable or disable the background startup interface according to the recommended switch setting. In one example, the terminal device automatically sets the background startup interface permission to be turned on or off according to the recommended switch setting. For example, if the recommended switch is set to be on, the terminal device turns on the background startup interface permission for the application; if the recommended switch is set to off, the terminal device turns off the background startup interface permission for the application. In another example, the terminal device displays the recommended switch setting, and the user sets the permission of the user to enable or disable the background startup interface according to the recommended switch setting and the actual requirement of the user, and the terminal device acquires the permission setting indication set by the user, according to The permission setting set by the user indicates that the background startup interface permission is turned on or off for the application. In addition, after the terminal device installs the application, the cloud server may send a recommendation switch setting of the background startup interface permission of the application to the terminal device; the cloud server may also send the recommendation of the background startup interface permission of the application to the terminal device every predetermined time interval. Switch settings.

In an example, for an application, if the number of users who open the background startup interface permission for the application is greater than the number of users who turn off the background startup interface permission for the application, the cloud server determines the recommendation of the background startup interface permission of the application. The switch is set to be turned on; if the number of users who have the background startup interface permission for the application is less than the number of users who have turned off the background startup interface permission for the application, the cloud server determines that the recommendation switch of the background startup interface permission of the application is set to off.

In another example, for a certain application, if the ratio of the number of users who open the background startup interface permission to the total number of users is greater than the first threshold, the cloud server determines the recommended switch setting of the background startup interface permission of the application. If the ratio of the number of users who have enabled the background startup interface to the total number of users is less than the second threshold, the cloud server determines that the recommended switch of the background startup interface permission of the application is set to off. The first threshold is equal to the second threshold, or the first threshold is greater than the second threshold. The total number of users refers to the sum of the number of users who have the background startup interface permission for the application and the number of users who have turned off the background startup interface permissions for the application.

In addition, in order to facilitate the user to adjust the switch of the background startup interface permissions of the application. In the system setting of the terminal device, the switch control of the background startup interface permission of each application can be correspondingly increased, so that the user can customize the setting through the switch control. For example, in the setting function-authorization management function-application authority management function, the above-mentioned switch control is added, and the user can turn on or off the background startup interface authority for the application by adjusting the switch control.

The following is an apparatus embodiment of the present disclosure, which may be used to implement the method embodiments of the present disclosure. For details not disclosed in the disclosed device embodiments, please refer to the method embodiments of the present disclosure.

FIG. 2A is a block diagram of an authority control apparatus according to an exemplary embodiment. The apparatus has a function of implementing the above-described method examples, and the functions may be implemented by hardware or by hardware to execute corresponding software. The apparatus may include: a request acquisition module 210, a operation detection module 220, an authority detection module 230, and a prohibition pop-up module 240.

The request obtaining module 210 is configured to acquire an interface startup request sent by the application.

The operation detection module 220 is configured to detect whether the application is running in the background.

The permission detection module 230 is configured to detect whether the application has a background startup interface right when the application is running in the background. The background startup interface permission refers to the permission of the application to pop up the interface when running in the background.

The pop-up module 240 is configured to prevent the interface of the application from popping up when the application does not have the background startup interface right.

In summary, the device provided in this embodiment detects whether the application is running in the background after acquiring the interface initiated by the application, and if it detects that the application is running in the background, it continues to detect whether the application has the background startup interface permission. If the application does not have the background startup interface permission, the application interface is prohibited from popping up; because the background startup interface permission is added, only the application having the background startup interface permission is allowed to pop up in the background to avoid unauthorized application abuse. The function of pop-up interface when running in the background avoids affecting user operations and providing system performance.

In an optional embodiment provided based on the embodiment shown in FIG. 2A, as shown in FIG. 2B, the rights detection module 230 includes a method invocation submodule 230a and a result obtaining submodule 230b.

The method invocation sub-module 230a is configured to invoke a permission detection method of the application rights manager, and send a permission detection request to the permission detection method. The privilege detection request carries the identifier of the application, and the privilege detection method is used to query, from the application privilege manager, whether the application has the background startup interface privilege.

The result obtaining submodule 230b is configured to acquire the authority detection result returned by the authority detecting method. The result of the permission detection is: the application has the background startup interface authority, or the application does not have the background startup interface authority.

In another optional embodiment provided based on the embodiment shown in FIG. 2A, as shown in FIG. 2B, the apparatus further includes: an identifier acquisition module 250.

The identity obtaining module 250 is configured to obtain an identifier of the application from the interface initiation request. The identifier of the application includes: a package name of the application and a UID corresponding to the current system.

In another optional embodiment provided based on the embodiment shown in FIG. 2A, as shown in FIG. 2B, the operation detecting module 220 includes: a top-of-stack acquisition sub-module 220a, an application detection sub-module 220b, and a first determiner. Module 220c and second determination sub-module 220d.

The top-of-stack acquisition sub-module 220a is configured to acquire a system top-of-stack application, which refers to an application currently running in the foreground.

The application detection sub-module 220b is configured to detect whether the application is the system top-of-stack application.

The first determining sub-module 220c is configured to determine that the application is running in the background when the application is not the system top-of-stack application.

The second determining sub-module 220d is configured to determine that the application is running in the foreground when the application is the system top-of-stack application.

In another optional embodiment provided based on the embodiment illustrated in FIG. 2A, the disable pop-up module 240 is configured to terminate execution of the interface launch request.

In another optional embodiment provided based on the embodiment shown in FIG. 2A, the apparatus further includes: a setting receiving module and a rights switch module.

a receiving module configured to receive a recommendation switch setting of the background startup interface permission of the application sent by the cloud server, where the recommendation switch is set by the cloud server according to the permission to open the background startup interface for the application The number of users and the number of users who have turned off the background launch interface permissions for the application.

It should be noted that, when the device provided by the foregoing embodiment implements its function, only the division of each functional module described above is illustrated. In actual applications, the function distribution may be completed by different functional modules according to actual needs. Divide the content structure of the device into different functional modules. To complete all or part of the functions described above.

With regard to the apparatus in the above embodiments, the specific manner in which the respective modules perform the operations has been described in detail in the embodiment relating to the method, and will not be explained in detail herein.

An exemplary embodiment of the present disclosure also provides an authority control apparatus capable of implementing the authority control method provided by the present disclosure. The apparatus includes a processor and a memory for storing executable instructions of the processor. Wherein the processor is configured to:

Obtain an interface startup request sent by the application;

Detecting whether the application is running in the background;

Optionally, the processor is configured to:

Optionally, the processor is further configured to:

Obtaining an identifier of the application from the interface startup request;

Optionally, the processor is configured to:

Detecting whether the application is the system top application;

Optionally, the processor is configured to:

The execution of the interface startup request is terminated.

Optionally, the processor is further configured to:

FIG. 3 is a block diagram of an apparatus 300, according to an exemplary embodiment. For example, device 300 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.

Referring to FIG. 3, apparatus 300 can include one or more of the following components: processing component 302, memory 304, power component 306, multimedia component 308, audio component 310, input/output (I/O) interface 312, sensor component 314, and Communication component 316.

Processing component 302 typically controls the overall operation of device 300, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. Processing component 302 can include one or more processors 320 to execute instructions to perform all or part of the steps described above. Moreover, processing component 302 can include one or more modules to facilitate interaction between component 302 and other components. For example, processing component 302 can include a multimedia module to facilitate interaction between multimedia component 308 and processing component 302.

Memory 304 is configured to store various types of data to support operation at device 300. Examples of such data include instructions for any application or method operating on device 300, contact data, phone book data, messages, pictures, videos, and the like. The memory 304 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable. Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.

Power component 306 provides power to various components of device 300. Power component 306 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 300.

The multimedia component 308 includes a screen between the device 300 and the user that provides an output interface. In some embodiments, the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and hand on the touch panel Potential. The touch sensor may sense not only the boundary of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 308 includes a front camera and/or a rear camera. When the device 300 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 310 is configured to output and/or input an audio signal. For example, audio component 310 includes a microphone (MIC) that is configured to receive an external audio signal when device 300 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may be further stored in memory 304 or transmitted via communication component 316. In some embodiments, audio component 310 also includes a speaker for outputting an audio signal.

The I/O interface 312 provides an interface between the processing component 302 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.

Sensor assembly 314 includes one or more sensors for providing status assessment of various aspects to device 300. For example, sensor assembly 314 can detect an open/closed state of device 300, relative positioning of components, such as the display and keypad of device 300, and sensor component 314 can also detect a change in position of one component of device 300 or device 300. The presence or absence of user contact with device 300, device 300 orientation or acceleration/deceleration, and temperature variation of device 300. Sensor assembly 314 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 314 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

Communication component 316 is configured to facilitate wired or wireless communication between device 300 and other devices. The device 300 can access a wireless network based on a communication standard, such as Wi-Fi, 2G or 3G, or a combination thereof. In an exemplary embodiment, communication component 316 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 316 also includes a near field communication (NFC) module to facilitate short range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, device 300 may be implemented by one or more application specific integrated circuits (ASIC), digital signal processor (DSP), digital signal processing device (DSPD), programmable logic device (PLD), field programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronics Component implementation for performing the above method.

In an exemplary embodiment, there is also provided a non-transitory computer readable storage medium comprising instructions, such as a memory 304 comprising instructions executable by processor 320 of apparatus 300 to perform the above method. For example, the non-transitory computer readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.

A non-transitory computer readable storage medium, when instructions in the storage medium are executed by a processor of apparatus 300, to enable apparatus 300 to perform the above method.

It should be understood that "a plurality" as referred to herein means two or more. "and/or", describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately. The character "/" generally indicates that the contextual object is an "or" relationship.

Other embodiments of the present disclosure will be apparent to those skilled in the <RTIgt; The present application is intended to cover any variations, uses, or adaptations of the present disclosure, which are in accordance with the general principles of the disclosure and include common general knowledge or common technical means in the art that are not disclosed in the present disclosure. . The specification and examples are to be regarded as illustrative only,

It is to be understood that the invention is not limited to the details of the details and The scope of the disclosure is to be limited only by the appended claims.

Claims

A method for controlling rights, characterized in that the method comprises:

Obtain an interface startup request sent by the application;

Detecting whether the application is running in the background;

If the application is running in the background, detecting whether the application has the background startup interface permission; wherein the background startup interface permission refers to the permission of the application to pop up the interface when running in the background;

If the application does not have the background startup interface right, the interface of the application is prohibited from popping up.
The method according to claim 1, wherein the detecting whether the application has a background startup interface permission comprises:

Calling the permission detection method of the application rights manager, and sending the permission detection request to the permission detection method; wherein the permission detection request carries an identifier of the application, and the permission detection method is used to use the application permission manager The middle query obtains whether the application has the permission of the background startup interface;

Acquiring the permission detection result returned by the permission detection method; wherein the permission detection result is: the application has the background startup interface authority, or the application does not have the background startup interface authority.
The method of claim 2, wherein the method further comprises:

Obtaining an identifier of the application from the interface startup request;

The identifier of the application includes: a package name of the application and a user personal identification code UID corresponding to the current system.
The method according to any one of claims 1 to 3, wherein the detecting whether the application is running in the background comprises:

Obtaining a system stack top application, where the system top stack application refers to an application currently running in the foreground;

Detecting whether the application is the system top application;

If the application is not the system stack top application, determining that the application is running in the background;

If the application is the system top-of-stack application, it is determined that the application is running in the foreground.
The method according to any one of claims 1 to 4, wherein the prohibiting the interface of the application from popping up comprises:

The execution of the interface startup request is terminated.
The method according to any one of claims 1 to 5, further comprising:

Receiving a recommendation switch setting of the background startup interface permission of the application sent by the cloud server, where the recommendation switch is set by the cloud server according to the number of users who open the background startup interface permission for the application and is the application The number of users who close the permission of the background startup interface is determined;

And setting, according to the recommendation switch, the right to enable or disable the background startup interface.
A permission control device, characterized in that the device comprises:

The request acquisition module is configured to obtain an interface startup request sent by the application;

Running a detection module configured to detect whether the application is running in the background;

The permission detection module is configured to detect, when the application is running in the background, whether the application has the background startup interface authority; wherein the background startup interface permission refers to the permission of the application to pop up the interface when running in the background;

The pop-up module is disabled, and is configured to prohibit the interface of the application from popping up when the application does not have the permission of the background startup interface.
The device according to claim 7, wherein the authority detecting module comprises:

The method call submodule is configured to invoke a permission detection method of the application rights manager, and send a permission detection request to the permission detection method; wherein the permission detection request carries an identifier of the application, and the permission detection method uses Querying, by the application rights manager, whether the application has the background startup interface authority;

The result obtaining sub-module is configured to obtain the permission detection result returned by the permission detection method, wherein the permission detection result is: the application has the background startup interface authority, or the application does not have the background Start interface permissions.
The device according to claim 8, wherein the device further comprises:

An identifier obtaining module, configured to obtain an identifier of the application from the interface startup request;

The identifier of the application includes: a package name of the application and a user corresponding to the current system. Human identification code UID.
The device according to any one of claims 7 to 9, wherein the operation detecting module comprises:

a top-of-stack acquisition sub-module configured to acquire a system stack top application, where the system top-of-stack application refers to an application currently running in the foreground;

An application detection submodule configured to detect whether the application is the system top application;

a first determining submodule configured to determine that the application is running in the background when the application is not the system top application;

The second determining submodule is configured to determine that the application is running in the foreground when the application is the system stack top application.
A device according to any one of claims 7 to 10, characterized in that

The prohibition pop-up module is configured to terminate execution of the interface initiation request.
The device according to any one of claims 7 to 11, wherein the device further comprises:

a receiving module configured to receive a recommendation switch setting of the background startup interface permission of the application sent by the cloud server, where the recommendation switch is set by the cloud server according to the permission to open the background startup interface for the application The number of users and the number of users who have turned off the background startup interface rights for the application;

The permission switch module is configured to enable or disable the background startup interface authority for the application according to the recommended switch setting.
A permission control device, characterized in that the device comprises:

processor;

a memory for storing executable instructions of the processor;

Wherein the processor is configured to:

Obtain an interface startup request sent by the application;

Detecting whether the application is running in the background;

If the application is running in the background, detecting whether the application has the background startup interface permission; The background startup interface permission refers to the permission of the application to pop up the interface when running in the background;

If the application does not have the background startup interface right, the interface of the application is prohibited from popping up.