CN108681668B - Equipment manager management method and device and mobile terminal - Google Patents
Equipment manager management method and device and mobile terminal Download PDFInfo
- Publication number
- CN108681668B CN108681668B CN201810351173.6A CN201810351173A CN108681668B CN 108681668 B CN108681668 B CN 108681668B CN 201810351173 A CN201810351173 A CN 201810351173A CN 108681668 B CN108681668 B CN 108681668B
- Authority
- CN
- China
- Prior art keywords
- device manager
- permission
- mobile terminal
- application program
- authority
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/45—Structures or tools for the administration of authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/442—Shutdown
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
- H04M1/72463—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions to restrict the functionality of the device
Abstract
The embodiment of the application discloses a device manager management method, a device and a mobile terminal. The method comprises the following steps: acquiring a device manager closing request; responding to the device manager closing request, and acquiring the application program which has acquired the device manager permission; and canceling the device manager authority of the application program which acquires the device manager authority. According to the method, the device manager permission of all the application programs which acquire the device manager permission can be cancelled by triggering the device manager closing request once, so that a user can conveniently manage the device manager permission, and the problems that the management mode of the device manager is complex and the management of the user is not facilitated are solved.
Description
Technical Field
The present application relates to the field of mobile terminals, and in particular, to a method and an apparatus for managing a device manager, and a mobile terminal.
Background
With the richness of the third-party application programs, users often install various third-party application programs in the mobile terminal, and some third-party application programs can guide the opened device manager authority in various ways. After the third-party application program obtains the device manager permission, operations with higher permissions, such as clearing all user data, changing a screen locking password, setting a password rule, monitoring screen unlocking attempt times, locking a screen and the like, can be performed on the mobile terminal, which is not beneficial to ensuring the safety of the mobile terminal. Moreover, the management mode of the device manager is complex, which is not beneficial for the user to manage.
Disclosure of Invention
In view of the foregoing problems, the present application provides a method and an apparatus for managing a device manager, and a mobile terminal, so as to solve the problem that the management manner of the device manager is complicated and is not conducive to user management.
In a first aspect, the present application provides a device manager management method, applied to a mobile terminal, the method including: acquiring a device manager closing request; responding to the device manager closing request, and acquiring the application program which has acquired the device manager permission; and canceling the device manager authority of the application program which acquires the device manager authority.
In a second aspect, the present application provides an apparatus for managing a device manager, which is executed in a mobile terminal, and includes: a management instruction acquisition unit for acquiring a device manager close request; an application acquisition unit configured to acquire an application that has acquired a device manager authority in response to the device manager close request; and the authority management unit is used for canceling the device manager authority of the application program which acquires the device manager authority.
In a third aspect, the present application provides a mobile terminal comprising one or more processors and a memory; one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the methods described above.
In a fourth aspect, the present application provides a computer-readable storage medium comprising a stored program, wherein the method described above is performed when the program is executed.
According to the device manager management method and device and the mobile terminal, the device manager closing request is obtained, the application program with the device manager permission is obtained in response to the device manager closing request, the device manager permission of the application program with the device manager permission is cancelled, so that all the device manager permissions of the application programs with the device manager permission can be cancelled by triggering the device manager closing request once, a user can conveniently manage the device manager permission, and the problems that the management mode of the device manager is complex and the management of the user is not facilitated are solved.
These and other aspects of the present application will be more readily apparent from the following description of the embodiments.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a network environment diagram illustrating a device manager management method proposed in the present application;
fig. 2 is a schematic diagram illustrating a device manager configuration interface in a device manager management method proposed in the present application;
FIG. 3 illustrates a flow chart of another device manager management method presented herein;
FIG. 4 is a schematic diagram of an interface in a device manager management method proposed in the present application;
fig. 5 is a block diagram illustrating a structure of a screen control apparatus according to the present application;
fig. 6 is a block diagram showing the structure of another screen control device proposed in the present application;
fig. 7 is a block diagram illustrating a structure of a mobile terminal according to the present application;
fig. 8 is a block diagram illustrating a mobile terminal according to the present application for performing a device manager management method according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The mobile terminal is usually provided with a right capable of managing and operating the mobile terminal, for example, a device manager right, and an application installed in the mobile terminal can operate and manage the mobile terminal after the device manager right is activated, that is, after the device manager right is acquired. For example, in a mobile terminal based on an Android operating system, the Android SDK provides an API called DevicePolicyManager that can manage and operate devices, and an application developed based on the API can take over the management authority of a mobile phone to perform a lot of bold operations on the mobile terminal, such as screen locking, factory setting restoration, password setting, password forced clearing, password modification, setting of a screen light dimming time interval, and the like.
However, the inventor finds that whether the application program of the system itself or the application program of the third party requests to activate the device manager authority, and the path of the device manager authority provided for the user to manage the application program in the mobile terminal is relatively deep, so that the user management is inconvenient and is not beneficial to the user management. Therefore, the inventor proposes a device manager management method, a device and a mobile terminal in the application, which solve the problem that the management mode of the device manager is complex and is not beneficial to the management of the user.
Embodiments of the present application will be described in detail below with reference to the accompanying drawings.
Referring to fig. 1, a device manager management method provided in the present application is applied to a mobile terminal, and the method includes:
step 110: a device manager close request is obtained.
The device manager closing request can be generated after being triggered by a user or automatically triggered by the mobile terminal. As a way for generating the user trigger, a desktop icon of a mobile terminal management program may be displayed on a desktop of the mobile terminal, an interface of the mobile terminal management program is directly displayed after the user clicks the desktop icon of the icon to start the mobile terminal management program, an equipment manager configuration interface is displayed in the interface, a configuration control is displayed in the equipment manager configuration interface, and when it is detected that the user clicks the configuration control to generate an equipment manager closing request, the mobile terminal may acquire the generated equipment manager closing request. As shown in fig. 2, a device manager configuration interface 111 is shown, and after the user clicks the configuration control 112 in fig. 2, the generation of the device manager shutdown request may be triggered.
In addition, when the mobile terminal management program runs in the background, a calling control can be displayed on the desktop, and the interface of the mobile terminal management program is directly displayed after the user clicks the calling control.
Alternatively, the mobile terminal may generate the device manager close request at a predetermined cycle, and may acquire the generated device manager close request after generating the device manager close request. For example, the mobile terminal may increase detection of an application program that has activated the device manager in a regular security detection, and in the detection process, a device manager shutdown request may be generated after detecting that the application program has acquired the device manager rights or detecting that the application program has executed a preset special right. The preset special permission comprises a preset permission which can be obtained after the permission of the device manager is obtained.
In addition, a list of all applications having the function of acquiring the device manager is displayed in the existing device manager configuration interface, a configuration control is displayed in the list corresponding to each application, the configuration control can represent whether the corresponding application has acquired the device manager authority, and the device manager authority of the application can be activated or canceled by responding to the touch of the user. In this case, as a way, after detecting that the user closes the device manager permissions of one of the applications, a prompt option of whether to close the device manager permissions of all the applications may be displayed, and after the user selects yes, the device manager close request may be generated, so that after detecting that the user closes the device manager permissions of one of the applications, the device manager permissions of all the remaining applications that have acquired the device manager permissions may be closed by one key, and in this case, it is not necessary to develop new pages and controls in the pages, but existing configuration interfaces may be directly utilized, which reduces development time consumption.
It should be noted that, in the operating system of the mobile terminal, any operation is performed based on the execution code, and in this example, the obtaining of the device manager closing request may be understood as that the code configured in the mobile terminal and instructing the mobile terminal to cancel the device manager authority of the application program is detected to be executed.
Step 120: and responding to the device manager closing request, and acquiring the application program which acquires the device manager authority.
After the application program in the mobile terminal acquires the authority of the device manager, the mobile terminal stores the application program in a storage area of the system. For example, the identification of the application that has acquired device manager privileges may be saved in the device policy manager DevicePolicyManager's management class. After the device manager closing request is obtained, the device manager closing request can be responded, and the application program stored in the storage area of the system and having the device manager permission obtained can be obtained. It is understood that when storing the application program for obtaining the device manager authority, the identifier of the application program is stored, and the identifier may include, but is not limited to, the name, version number, and the like of the application program, which uniquely represent the application program.
Step 130: and canceling the device manager authority of the application program which acquires the device manager authority.
As one way, the mobile terminal may further execute a RemoveActiveAdmin function to delete the device manager rights that the application has acquired. When the RemoveActiveAdmin function is executed, the identifier of the application program which is to cancel the device manager permission is transmitted to the RemoveActiveAdmin function, so that the device manager permission of all the application programs which acquire the device manager permission can be canceled by executing the RemoveActiveAdmin function once.
According to the device manager management method, the device manager closing request is obtained, the application program with the device manager permission is obtained in response to the device manager closing request, the device manager permission of the application program with the device manager permission is cancelled, and therefore the device manager permission of all the application programs with the device manager permission can be cancelled by triggering the device manager closing request once, a user can conveniently manage the device manager permission, the problem that the management mode of the device manager is complex and management of the user is not facilitated is solved.
Referring to fig. 3, a device manager management method provided in the present application is applied to a mobile terminal, and the method includes:
step 210: a device manager close request is obtained.
Step 220: and responding to the device manager closing request, and acquiring the application program which acquires the device manager authority.
Step 230: and acquiring a target application program, wherein the target application program is an application program which executes preset special authority in the application programs which acquire the authority of the device manager.
After the rights of the device manager are acquired, the acquired rights for managing the mobile terminal may be different for different applications. Therefore, after part of the application programs acquire the device management authority, the mobile terminal cannot be damaged greatly. As a way, the device manager right which is harmful to the mobile terminal after execution may be configured in advance as a preset special right, and when the device manager right of the application program is cancelled, only the application program which has executed the preset special right is cancelled.
It should be noted that the preset special authority includes at least one of the following authorities: clearing all user data, changing a lock screen password, monitoring a screen, changing a lock screen password, setting password rules, monitoring a number of screen unlock attempts, locking a screen, setting a device global proxy, setting a validity period for a lock screen password, setting storage device encryption, deactivating a camera, and deactivating a screen lock.
Moreover, some applications may intentionally collect the private information of the user after acquiring the device manager authority, for example, acquire the personal identity information of the user and the payment password of the user, thereby causing harm to the user. As one way, a preset application may be configured in advance, and the preset application includes: an application program requiring input of a payment password; and applications that require entry of user personal identification information. In this case of setting the preset application, the obtained target application is the application that has already obtained the device manager permission, and the application with the preset special permission is executed in the process of running the preset application by the mobile terminal.
Step 240: and canceling the device manager authority of the target application program.
As a way, when the application program that has cancelled the device manager permission receives the request for activating the device manager permission sent by the application program that has cancelled the device manager permission again, the device manager acquisition request is intercepted, so as to prevent the application program that has cancelled the device manager permission from acquiring the device manager permission again.
Furthermore, for the application program that has executed the preset special authority in the process of running the preset application program on the mobile terminal, after the authority of the device manager is cancelled, as shown in fig. 4, the mobile terminal may further display a pop frame 241, and display a prompt message indicating whether to uninstall the dangerous application program in the pop frame 241, so that the user may select whether to completely delete the application program suspected of collecting the private information of the user, thereby further improving the security of the moving data. It is understood that the dangerous application is an application that has executed a preset special authority during the process of the mobile terminal running a preset application.
The device manager management method provided by the application acquires a device manager closing request, responds to the device manager closing request, acquires an application program which has acquired the device manager permission, cancels the device manager permission of the application program which has acquired the device manager permission, thereby triggering one-time device manager closing request, the device manager authority of the application program which executes the preset special authority among the application programs which have acquired the device manager authority can be cancelled, and further, the authority of the device manager of the application program which executes the preset special authority in the process of running the preset application program by the mobile terminal can be cancelled, therefore, the user can conveniently manage the authority of the device manager, and the problems that the management mode of the device manager is complex and the management by the user is not facilitated are solved.
Referring to fig. 5, a device manager management apparatus 300 provided by the present application operates in a mobile terminal, where the apparatus 300 includes: a management instruction acquisition unit 310, an application acquisition unit 320, and a rights management unit 330.
The management instruction obtaining unit 310 is configured to obtain a device manager closing request.
As one way, the mobile terminal may display a device manager configuration interface, where a configuration control is displayed in the device manager configuration interface. The management instruction obtaining unit 310 is specifically configured to obtain an apparatus manager closing request generated after the touch operation performed on the configuration control.
An application acquisition unit 320, configured to acquire, in response to the device manager close request, an application that has acquired device manager rights.
A right management unit 330, configured to cancel the device manager right of the application program that has acquired the device manager right.
Referring to fig. 6, a device manager management apparatus 400 provided by the present application, operating in a mobile terminal, includes: a management instruction acquisition unit 410, an application acquisition unit 420, a target determination unit 430, and a rights management unit 440.
The management instruction obtaining unit 410 is configured to obtain a device manager closing request.
As one way, the mobile terminal may display a device manager configuration interface, where a configuration control is displayed in the device manager configuration interface. The management instruction obtaining unit 410 is specifically configured to obtain an apparatus manager closing request generated after the touch operation performed on the configuration control.
An application acquiring unit 420, configured to acquire, in response to the device manager close request, an application that has acquired device manager rights.
And a target determining unit 430, configured to obtain a target application, where the target application is an application that has executed a preset special permission among the applications that have obtained the device manager permission.
As one mode, the preset application includes: an application program requiring input of a payment password; and applications that require entry of user personal identification information.
As one way, the preset special authority includes at least one of the following authorities: clearing all user data; changing a screen locking password; and a monitor screen.
A right management unit 440, configured to cancel the device manager right of the target application.
The authority management unit 440 is further configured to intercept the device manager acquisition request when detecting the device manager acquisition request sent by the application program that has acquired the device manager authority.
It should be noted that the device embodiment and the method embodiment in the present application correspond to each other, and specific principles in the device embodiment may refer to the contents in the method embodiment, which is not described herein again.
To sum up, the device manager management method, the device and the mobile terminal provided by the application obtain the device manager closing request, respond to the device manager closing request, obtain the application program that has obtained the device manager permission, and cancel the device manager permission of the application program that has obtained the device manager permission, so that by triggering the device manager closing request once, the device manager permission of all the application programs that have obtained the device manager permission can be cancelled, and then the user can manage the device manager permission very conveniently, thereby improving the problem that the management mode of the device manager is complicated and is not beneficial to the user to manage.
A mobile terminal provided by the present application will be described with reference to fig. 7 and 8.
Referring to fig. 7, based on the device manager management method and apparatus, the embodiment of the present application further provides a mobile terminal 100 capable of executing the device manager management method. The mobile terminal 100 includes an electronic body 10, and the electronic body 10 includes a housing 12 and a first screen 120 disposed on the housing 12. The housing 12 may be made of metal, such as steel or aluminum alloy. In this embodiment, the first screen 120 and the second screen 121 generally include a display panel 111, and may also include a circuit and the like for responding to a touch operation performed on the display panel 111. The Display panel 111 may be a Liquid Crystal Display (LCD) panel, and in some embodiments, the Display panel 111 is a touch screen 109.
As shown in fig. 8, in an actual application scenario, the mobile terminal 100 may be used as a smartphone terminal, in which case the electronic body 10 generally further includes one or more processors 102 (only one is shown in the figure), a memory 104, an RF (Radio Frequency) module 106, an audio circuit 110, a sensor 114, an input module 118, and a power module 122. It will be understood by those skilled in the art that the present application is not intended to be limited to the configuration of the electronics body portion 10. For example, the electronics body section 10 may include more or fewer components than shown, or have a different configuration than shown.
Those skilled in the art will appreciate that all other components are peripheral devices with respect to the processor 102, and the processor 102 is coupled to the peripheral devices through a plurality of peripheral interfaces 124. The peripheral interface 124 may be implemented based on the following criteria: universal Asynchronous Receiver/Transmitter (UART), General Purpose Input/Output (GPIO), Serial Peripheral Interface (SPI), and Inter-Integrated Circuit (I2C), but the present invention is not limited to these standards. In some examples, the peripheral interface 124 may comprise only a bus; in other examples, the peripheral interface 124 may also include other elements, such as one or more controllers, for example, a display controller for interfacing with the display panel 111 or a memory controller for interfacing with a memory. These controllers may also be separate from the peripheral interface 124 and integrated within the processor 102 or a corresponding peripheral.
The memory 104 may be used to store software programs and modules, and the processor 102 executes various functional applications and data processing by executing the software programs and modules stored in the memory 104. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, the memory 104 may further include memory remotely located from the processor 102, which may be connected to the electronic body portion 10 or the first screen 120 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The RF module 106 is configured to receive and transmit electromagnetic waves, and achieve interconversion between the electromagnetic waves and electrical signals, so as to communicate with a communication network or other devices. The RF module 106 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a Subscriber Identity Module (SIM) card, memory, and so forth. The RF module 106 may communicate with various networks such as the internet, an intranet, a wireless network, or with other devices via a wireless network. The wireless network may comprise a cellular telephone network, a wireless local area network, or a metropolitan area network. The Wireless network may use various Communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communication (GSM), Enhanced Mobile Communication (Enhanced Data GSM Environment, EDGE), wideband Code division multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Wireless Fidelity (WiFi) (e.g., Institute of Electrical and Electronics Engineers (IEEE) standard IEEE 802.10A, IEEE802.11 b, IEEE802.1 g, and/or IEEE802.11 n), Voice over internet protocol (VoIP), world wide mail Access (Microwave for Wireless Communication), Wi-11 Wireless Access (wimax), and any other suitable protocol for instant messaging, and may even include those protocols that have not yet been developed.
The audio circuitry 110, speaker 101, sound jack 103, microphone 105 collectively provide an audio interface between a user and the electronic body portion 10 or the first screen 120. Specifically, the audio circuit 110 receives sound data from the processor 102, converts the sound data into an electrical signal, and transmits the electrical signal to the speaker 101. The speaker 101 converts an electric signal into a sound wave audible to the human ear. The audio circuitry 110 also receives electrical signals from the microphone 105, converts the electrical signals to sound data, and transmits the sound data to the processor 102 for further processing. Audio data may be retrieved from the memory 104 or through the RF module 106. In addition, audio data may also be stored in the memory 104 or transmitted through the RF module 106.
The sensor 114 is disposed in the electronic body portion 10 or the first screen 120, and examples of the sensor 114 include, but are not limited to: light sensors, operational sensors, pressure sensors, infrared heat sensors, distance sensors, gravitational acceleration sensors, and other sensors.
Specifically, the light sensors may include a light sensor 114F, a pressure sensor 114G. Among them, the pressure sensor 114G may detect a pressure generated by pressing on the mobile terminal 100. That is, the pressure sensor 114G detects pressure generated by contact or pressing between the user and the mobile terminal, for example, contact or pressing between the user's ear and the mobile terminal. Accordingly, the pressure sensor 114G may be used to determine whether contact or pressing has occurred between the user and the mobile terminal 100, as well as the magnitude of the pressure.
Referring to fig. 8 again, in the embodiment shown in fig. 8, the light sensor 114F and the pressure sensor 114G are disposed adjacent to the display panel 111. The light sensor 114F can turn off the display output when an object is near the first screen 120, for example, when the electronic body 10 moves to the ear.
As one of the motion sensors, the gravity acceleration sensor can detect the magnitude of acceleration in various directions (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used for applications (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping) and the like for recognizing the attitude of the mobile terminal 100. In addition, the electronic body 10 may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer and a thermometer, which are not described herein,
in this embodiment, the input module 118 may include the touch screen 109 disposed on the first screen 120, and the touch screen 109 may collect a touch operation of a user on or near the touch screen 109 (for example, an operation of the user on or near the touch screen 109 using any suitable object or accessory such as a finger, a stylus, etc.) and drive a corresponding connection device according to a preset program. Optionally, the touch screen 109 may include a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 102, and can receive and execute commands sent by the processor 102. In addition, the touch detection function of the touch screen 109 may be implemented by using resistive, capacitive, infrared, and surface acoustic wave types. In addition to the touch screen 109, in other variations, the input module 118 may include other input devices, such as keys. The keys may include, for example, character keys for inputting characters, and control keys for triggering control functions. Examples of such control keys include a "back to home" key, a power on/off key, and the like.
The first screen 120 is used to display information input by a user, information provided to the user, and various graphic user interfaces of the electronic main body part 10, which may be composed of graphics, text, icons, numbers, videos, and any combination thereof, and in one example, the touch screen 109 may be provided on the display panel 111 so as to be integrated with the display panel 111.
The power module 122 is used to provide power supply to the processor 102 and other components. Specifically, the power module 122 may include a power management system, one or more power sources (e.g., batteries or ac power), a charging circuit, a power failure detection circuit, an inverter, a power status indicator light, and any other components related to the generation, management, and distribution of power in the electronic body 10 or the first screen 120.
The mobile terminal 100 further comprises a locator 119, the locator 119 being configured to determine an actual location of the mobile terminal 100. In this embodiment, the locator 119 implements the positioning of the mobile terminal 100 by using a positioning service, which is understood to be a technology or a service for obtaining the position information (e.g., longitude and latitude coordinates) of the mobile terminal 100 by using a specific positioning technology and marking the position of the positioned object on an electronic map.
It should be understood that the mobile terminal 100 described above is not limited to a smartphone terminal, but it should refer to a computer device that can be used in mobility. Specifically, the mobile terminal 100 refers to a mobile computer device equipped with an intelligent operating system, and the mobile terminal 100 includes, but is not limited to, a smart phone, a smart watch, a tablet computer, and the like.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (mobile terminal) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments. In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not necessarily depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (8)
1. A device manager management method applied to a mobile terminal, the method comprising:
acquiring a device manager closing request, wherein the device manager closing request is used for indicating the device manager permission for closing one application program in the mobile terminal;
responding to the device manager closing request, and acquiring the application programs which have acquired the device manager permission, wherein the application programs which have acquired the device manager permission are all the application programs which have acquired the device manager permission;
acquiring a target application program, wherein the target application program is an application program which is executed with a preset special authority in the application programs which have acquired the authority of the device manager, and the preset special authority is the authority of the device manager which has great harm to the mobile terminal after execution;
canceling the device manager permission of the target application program;
the method further comprises the following steps:
and if the request for activating the device manager permission sent by the target application program of which the device manager permission has been cancelled is received again, intercepting the request for activating the device manager permission.
2. The method of claim 1, wherein the step of obtaining a device manager shutdown request comprises:
displaying a configuration interface of an equipment manager, wherein a configuration control is displayed in the configuration interface of the equipment manager;
and acquiring a device manager closing request generated after the touch operation acting on the configuration control.
3. The method according to claim 1, wherein the target application is an application that has executed a preset special permission during a process of running a preset application by the mobile terminal, among all applications that have acquired device manager permission.
4. The method of claim 3, wherein the default application comprises:
an application program requiring input of a payment password; and
an application that inputs the user's personal identification information is required.
5. The method according to any of claims 3-4, wherein the pre-set special rights comprise at least one of the following rights:
clearing all user data;
changing a screen locking password; and
and monitoring the screen.
6. An apparatus for device manager management, operating in a mobile terminal, the apparatus comprising:
a management instruction obtaining unit, configured to obtain a device manager closing request, where the device manager closing request is used to indicate a device manager permission to close one of application programs in the mobile terminal;
an application program obtaining unit, configured to obtain, in response to the device manager closing request, application programs that have obtained device manager permissions, where the application programs that have obtained device manager permissions are all application programs that have obtained device manager permissions;
the target determining unit is used for acquiring a target application program, wherein the target application program is an application program which is executed with a preset special authority in the application programs which have acquired the authority of the device manager, and the preset special authority is the authority of the device manager which has great harm to the mobile terminal after execution;
the authority management unit is used for canceling the device manager authority of the target application program;
the permission management unit is further configured to intercept the request for activating the device manager permission, when the request for activating the device manager permission is received again, where the request is sent by the target application program and the device manager permission of the target application program has been cancelled.
7. A mobile terminal comprising one or more processors and memory;
one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the method of any of claims 1-5.
8. A computer-readable storage medium storing program code executable by a processor, the computer-readable storage medium comprising a stored program, wherein the method of any of claims 1-5 is performed when the program is executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810351173.6A CN108681668B (en) | 2018-04-18 | 2018-04-18 | Equipment manager management method and device and mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810351173.6A CN108681668B (en) | 2018-04-18 | 2018-04-18 | Equipment manager management method and device and mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108681668A CN108681668A (en) | 2018-10-19 |
| CN108681668B true CN108681668B (en) | 2021-03-12 |
Family
ID=63801351
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810351173.6A Active CN108681668B (en) | 2018-04-18 | 2018-04-18 | Equipment manager management method and device and mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108681668B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110210206B (en) * | 2019-05-28 | 2021-04-06 | 维沃移动通信有限公司 | Authority management method and terminal |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103824016A (en) * | 2013-11-28 | 2014-05-28 | 北京奇虎科技有限公司 | Application anti-uninstalling method and equipment |
| CN104123165B (en) * | 2014-07-31 | 2017-12-01 | 北京金山安全软件有限公司 | Application program unloading method and device and mobile terminal |
| CN104392176A (en) * | 2014-12-12 | 2015-03-04 | 北京奇虎科技有限公司 | Mobile terminal and method for intercepting device manager authority thereof |
| CN105955789B (en) * | 2016-05-18 | 2019-08-16 | Oppo 广东移动通信有限公司 | A kind of application program discharging method, device and equipment |
| CN106778173B (en) * | 2016-12-15 | 2021-02-23 | 北京数字天域科技有限责任公司 | Method and device for setting application lock based on intelligent operating system |
-
2018
- 2018-04-18 CN CN201810351173.6A patent/CN108681668B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN108681668A (en) | 2018-10-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108712561B (en) | Authority management method, device, mobile terminal and storage medium | |
| EP2798871B1 (en) | Method and apparatus providing privacy setting and monitoring user interface | |
| CN108710795B (en) | Information prompting method and device, mobile terminal and storage medium | |
| CN107133498B (en) | Privacy application management method and device and mobile terminal | |
| CN106778175B (en) | Interface locking method and device and terminal equipment | |
| CN108710456B (en) | Application icon processing method and device and mobile terminal | |
| CN110674490B (en) | Application permission display method and device and mobile terminal | |
| CN106921799A (en) | A kind of mobile terminal safety means of defence and mobile terminal | |
| CN107038358B (en) | Self-starting processing method and device and mobile terminal | |
| CN108737638B (en) | Application control method and device, mobile terminal and computer readable medium | |
| CN105281906A (en) | Safety authentication method and device | |
| CN108235767B (en) | Payment application isolation method and device and terminal | |
| CN107908939B (en) | Terminal alarm method and device and mobile terminal | |
| KR20160003399A (en) | Method and apparatus for notifying smishing | |
| AU2022201487B2 (en) | Authentication window display method and apparatus | |
| WO2018214748A1 (en) | Method and apparatus for displaying application interface, terminal and storage medium | |
| CN108763892A (en) | Right management method, device, mobile terminal and storage medium | |
| CN110557499B (en) | Information processing method and device and mobile terminal | |
| CN108769366B (en) | Authority management method, device, mobile terminal and storage medium | |
| CN110457935B (en) | Permission configuration method and terminal equipment | |
| WO2019071581A1 (en) | Application startup control method and user terminal | |
| WO2017193645A1 (en) | Method and apparatus for displaying data, and terminal | |
| CN108540645B (en) | Mobile terminal operation method and mobile terminal | |
| CN108763884B (en) | Authority management method, device, mobile terminal and storage medium | |
| CN108681668B (en) | Equipment manager management method and device and mobile terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |