CN106162612A - Control the method and device of Root authority - Google Patents
Control the method and device of Root authority Download PDFInfo
- Publication number
- CN106162612A CN106162612A CN201610483675.5A CN201610483675A CN106162612A CN 106162612 A CN106162612 A CN 106162612A CN 201610483675 A CN201610483675 A CN 201610483675A CN 106162612 A CN106162612 A CN 106162612A
- Authority
- CN
- China
- Prior art keywords
- version
- root authority
- aku
- root
- request
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
- H04W8/245—Transfer of terminal data from a network towards a terminal
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The disclosure is directed to control the method and device of Root authority.The method includes: receive the first request obtaining Root authority；Described first request comprises the version information of the current non-Root authority version of terminal；Version information according to described current non-Root authority, it is thus achieved that the AKU of corresponding Root authority version；Send the described AKU obtained.This technical scheme both can guarantee that the safety of a part of user terminal, the user obtaining Root authority demand can be had to provide convenient for another part again.
Description
Technical field
It relates to Internet technical field, particularly relate to control the method and device of Root authority.
Background technology
Root is present in Linux (a kind of operating system) system, UNIX (a kind of operating system) system and class unix system
In, it is unique power user in system, is equivalent to the administrator (pipe in Windows (a kind of operating system) system
Reason person) user.It has all of authority in system, as started or stoped a process, deletes or increase user, increase or
Disabling hardware etc..
Exploitation edition system is that this version is write from memory in order to allow some development of users provide the version of a regular upgrading of Root authority
Offer Root authority is provided, but owing to exploitation version user base number becomes larger, owing to acquiescence provides Root authority, it is impossible to well
Ensure the safety of user mobile phone.
Summary of the invention
Disclosure embodiment provides the method and device controlling Root authority.Described technical scheme is as follows:
First aspect according to disclosure embodiment, it is provided that a kind of method controlling Root authority, for server, bag
Include:
Receive the first request obtaining Root authority；Described first request comprises the version of the current non-Root authority version of terminal
This information；
Version information according to described current non-Root authority, it is thus achieved that the AKU of corresponding Root authority version；
Send the described AKU obtained.
In one embodiment, described AKU is that the identical Root authority version of version number is relative to non-Root authority version
This delta package.
In one embodiment, described method may also include that
Receiving the second request carrying out version updating, described second request comprises the version information of current system；
Version information according to the current system in described second request, it is thus achieved that up-to-date and version information is worked as higher than described
The installation kit that the non-Root authority version of the version information of front system is corresponding；
Send described installation kit.
Second aspect according to disclosure embodiment, it is provided that a kind of method controlling Root authority, for terminal, including:
The first request obtaining Root authority is sent to server；Described first request comprises local current non-Root authority
The version information of version；
Receive the AKU of server feedback；Described AKU is the AKU of corresponding Root authority version；
Described AKU is installed, to obtain Root authority.
In one embodiment, described AKU is that the identical Root authority version of version number is relative to non-Root authority version
This delta package.
In one embodiment, described method may also include that
Send the second request carrying out version updating to server, described second request comprises the version letter of current system
Breath；
Receive the up-to-date and version information non-Root power higher than the version information of described current system of server feedback
Limited in edition corresponding installation kit；
Described installation kit is installed.
In one embodiment, the version of described current system is version or the version of Root authority of non-Root authority
This.
In one embodiment, described method may also include that
Receive the operation closing Root authority；
Close Root authority.
The third aspect according to disclosure embodiment, it is provided that a kind of device controlling Root authority, for server, bag
Include:
First receiver module, for receiving the first request obtaining Root authority；It is current that described first request comprises terminal
The version information of non-Root authority version；
First obtains module, for the version information according to described current non-Root authority, it is thus achieved that corresponding Root authority
The AKU of version；
First sending module, for sending the described AKU of acquisition.
In one embodiment, described AKU is that the identical Root authority version of version number is relative to non-Root authority version
This delta package.
In one embodiment, described device may also include that
Second receiver module, for receiving the second request carrying out version updating, described second request comprises current system
Version information；
Second obtains module, for according to the version information of current system in described second request, it is thus achieved that up-to-date and
The installation kit that version information is corresponding higher than the non-Root authority version of the version information of described current system；
Second sending module, is used for sending described installation kit.
Fourth aspect according to disclosure embodiment, it is provided that a kind of device controlling Root authority, for terminal, including:
First sending module, for sending the first request obtaining Root authority to server；Described first request comprises
The version information of local current non-Root authority version；
First receiver module, for receiving the AKU of server feedback；Described AKU is corresponding Root authority version
This AKU；
First installs module, is used for installing described AKU, to obtain Root authority.
In one embodiment, described AKU is that the identical Root authority version of version number is relative to non-Root authority version
This delta package.
In one embodiment, described device may also include that
Second sending module, for sending the second request carrying out version updating to server, described second request comprises
The version information of current system；
Second receiver module, for receiving the up-to-date of server feedback and the version information version higher than described current system
The installation kit that the non-Root authority version of this information is corresponding；
Second installs module, is used for installing described installation kit.
In one embodiment, the version of described current system is version or the version of Root authority of non-Root authority
This.
In one embodiment, described device may also include that
3rd receiver module, for receiving the operation closing Root authority；
Close module, be used for closing Root authority.
The 5th aspect according to disclosure embodiment, it is provided that a kind of device controlling Root authority, including:
Processor；
For storing the memorizer of processor executable；
Wherein, described processor is configured to:
Receive the first request obtaining Root authority；Described first request comprises the version of the current non-Root authority version of terminal
This information；
Version information according to described current non-Root authority, it is thus achieved that the AKU of corresponding Root authority version；
Send the described AKU obtained.
The 6th aspect according to disclosure embodiment, it is provided that a kind of device controlling Root authority, including:
Processor；
For storing the memorizer of processor executable；
Wherein, described processor is configured to:
The first request obtaining Root authority is sent to server；Described first request comprises local current non-Root authority
The version information of version；
Receive the AKU of server feedback；Described AKU is the AKU of corresponding Root authority version；
Described AKU is installed, to obtain Root authority.
Embodiment of the disclosure that the technical scheme of offer can include following beneficial effect:
In one embodiment, by sending request to server, server is believed according to the version of current non-Root authority
Breath, it is thus achieved that the AKU of corresponding Root authority version, after terminal receives the AKU of server feedback, user needs actively again
The AKU of this Root authority version corresponding with current operation system version information is installed, just can obtain Root authority, this
Balance in safety and demand side, both can guarantee that the safety of a part of user terminal, can have acquisition for another part again
The user of Root authority demand provides convenient.
In another embodiment, no matter the most whether operating system has Root authority, upper once upgrade time, all can
Control to be upgraded to non-Root authority version at server end, now, send the request updating system version, server to server
After receiving this request, it is thus achieved that the AKU of non-Root authority version, and this AKU is sent to terminal, updates behaviour for terminal
Make system.Owing to current system is updated non-Root authority version by acquiescence, thereby ensure that the safety of user terminal.
In another embodiment, after obtaining Root authority, in order to ensure stability and the safety of user terminal,
User can also close Root authority at any time.
It should be appreciated that it is only exemplary and explanatory, not that above general description and details hereinafter describe
The disclosure can be limited.
Accompanying drawing explanation
Accompanying drawing herein is merged in description and constitutes the part of this specification, it is shown that meet the enforcement of the disclosure
Example, and for explaining the principle of the disclosure together with description.
Fig. 1 is the flow chart of the method according to the control Root authority shown in an exemplary embodiment.
Fig. 2 is the flow chart according to the another kind of method controlling Root authority shown in an exemplary embodiment.
Fig. 3 is the flow chart according to the another kind of method controlling Root authority shown in an exemplary embodiment.
Fig. 4 is the flow chart according to the another kind of method controlling Root authority shown in an exemplary embodiment.
Fig. 5 is the flow chart according to the another kind of method controlling Root authority shown in an exemplary embodiment.
Fig. 6 is the flow chart of the method according to the control Root authority shown in an exemplary embodiment one.
Fig. 7 is the block diagram of the device according to the control Root authority shown in an exemplary embodiment.
Fig. 8 is the block diagram according to the another kind of device controlling Root authority shown in an exemplary embodiment.
Fig. 9 is the block diagram according to the another kind of device controlling Root authority shown in an exemplary embodiment.
Figure 10 is the block diagram according to the another kind of device controlling Root authority shown in an exemplary embodiment.
Figure 11 is the block diagram according to the another kind of device controlling Root authority shown in an exemplary embodiment.
Figure 12 is the block diagram controlling the device of Root authority according to being applicable to shown in an exemplary embodiment.
Figure 13 is the block diagram controlling the device of Root authority according to being applicable to shown in an exemplary embodiment.
Detailed description of the invention
Here will illustrate exemplary embodiment in detail, its example represents in the accompanying drawings.Explained below relates to
During accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawings represents same or analogous key element.Following exemplary embodiment
Described in embodiment do not represent all embodiments consistent with the disclosure.On the contrary, they are only with the most appended
The example of the apparatus and method that some aspects that described in detail in claims, the disclosure are consistent.
Fig. 1 is the flow chart according to a kind of method controlling Root authority shown in an exemplary embodiment, is used for servicing
Device, as it is shown in figure 1, the method comprises the following steps S101-S103:
In step S101, receive the first request obtaining Root authority；First request comprises terminal current non-Root power
The version information of limited in edition.
When user wants the Root authority obtaining current operation system, send to server and obtain asking of Root authority
Asking, comprise the version information of the current non-Root authority version of terminal in request, version information can comprise version number, such as,
5.9.9 non-Root version.
In step s 102, according to the version information of current non-Root authority, it is thus achieved that the liter of corresponding Root authority version
Level bag.
In one embodiment, AKU is that the identical Root authority version of version number is relative to non-Root authority version
Delta package.It is to say, the AKU of Root authority version and first request in comprise non-Root authority version version letter
Version number in breath is identical.Can go out two system upgrade bags simultaneously, such as, 5.9.9 non-Root authority version and 5.9.9's
Root authority version, in order to save flow and install facility, it is also possible to the Root authority version generating 5.9.9 is non-with 5.9.9
Delta package 5.9.9-root.patch of Root authority version.
In step s 103, the AKU obtained is sent.
Currently, there is regular (such as, each week) upgraded version providing the user Root authority, operating system update is arrived
After this version, user the most just obtains Root authority, but owing to this version acquiescence provides Root authority, along with Root version is used
The constantly change of family radix is big, it is impossible to well ensure the safety of user mobile phone, the said method of disclosure embodiment, Yong Humo
Recognize and there is no Root authority, but have certain customers to have the demand wanting Root authority, therefore, it is desirable to send request to server,
Server is according to the version information of current non-Root authority, it is thus achieved that the AKU of corresponding Root authority version, and user needs again
The AKU of this Root authority version corresponding with current operation system version information is actively installed, just can obtain Root power
Limit, this balances in safety and demand side, both can guarantee that the safety of a part of user terminal, can have for another part again
The user obtaining Root authority demand provides convenient.
In one embodiment, as in figure 2 it is shown, before step S101, said method can also include the steps of S104-
S106:
In step S104, receiving the second request carrying out version updating, the second request comprises the version letter of current system
Breath.
In step S105, according to the version information of the current system in the second request, it is thus achieved that up-to-date and version information
The installation kit corresponding higher than the non-Root authority version of the version information of current system.
In step s 106, installation kit is sent.
In the present embodiment, no matter the most whether operating system has Root authority, upper once upgrade time, all can be in service
Device end controls to be upgraded to non-Root version, now, sends the request updating system version to server, and server receives this please
After asking, it is thus achieved that the AKU of non-Root authority version, and this AKU is sent to terminal, updates operating system for terminal.By
In acquiescence, current system updated non-Root authority version, thereby ensure that the safety of user terminal.
In one embodiment, the AKU of the Root authority version in step S102 and the non-Root power in step S105
The version number of limited in edition corresponding installation kit is identical.
Illustrate, be the Root power of 5.9.9 non-Root authority version or 5.9.9 regardless of the version of current operation system
Limited in edition, when upgrading next time, all can give tacit consent to and be upgraded to 5.9.10 non-Root authority version rather than be directly upgraded to 5.9.10
Root authority version, when user needs Root authority, it is necessary to the Root authority version of the 5.9.10 that again upgrades and non-Root
OTA (increment upgrading) delta package 5.9.10-root.patch of authority version.
Fig. 3 is the flow chart according to a kind of method controlling Root authority shown in an exemplary embodiment, for terminal,
Terminal can be mobile terminal, it is also possible to be fixed terminal, and disclosure embodiment does not limits.As it is shown on figure 3, the method includes
Following steps S301-S303:
In step S301, send the first request obtaining Root authority to server；First request comprises local current
The version information of non-Root authority version.
When user wants the Root authority obtaining current operation system, send to server and obtain asking of Root authority
Asking, comprise the version information of the current non-Root authority version of terminal in request, version information can comprise version number, such as,
5.9.10 non-Root version.
In step s 302, the AKU of server feedback is received；AKU is the upgrading of corresponding Root authority version
Bag.
In one embodiment, AKU is that the identical Root authority version of version number is relative to non-Root authority version
Delta package.It is to say, the AKU of Root authority version and first request in comprise non-Root authority version version letter
Version number in breath is identical.
In step S303, AKU is installed, to obtain Root authority.
Currently, there is regular (such as, each week) upgraded version providing the user Root authority, operating system update is arrived
After this version, user the most just obtains Root authority, but owing to this version acquiescence provides Root authority, along with Root version is used
The constantly change of family radix is big, it is impossible to well ensure the safety of user mobile phone, the said method of disclosure embodiment, Yong Humo
Recognize and there is no Root authority, but have certain customers to have the demand wanting Root authority, therefore, it is desirable to send request to server,
Server is according to the version information of current non-Root authority, it is thus achieved that the AKU of corresponding Root authority version, and terminal receives clothes
After the AKU of business device feedback, user needs the most actively to install this Root authority version corresponding with current operation system version information
This AKU, just can obtain Root authority, and this balances in safety and demand side, both can guarantee that a part of user is eventually
The safety of end, can have the user obtaining Root authority demand to provide convenient for another part again.
In one embodiment, as shown in Figure 4, said method can also include the steps of S304-S306:
In step s 304, sending the second request carrying out version updating to server, the second request comprises current system
Version information.
In step S305, the up-to-date and version information of reception server feedback is higher than the version information of current system
The installation kit that non-Root authority version is corresponding.
In step S306, this installation kit is installed.
In the present embodiment, no matter the most whether operating system has Root authority, upper once upgrade time, all can be in service
Device end controls to be upgraded to non-Root authority version, now, sends the request updating system version to server, and server receives
After this request, it is thus achieved that the AKU of non-Root authority version, and this AKU is sent to terminal, updates operation system for terminal
System.Owing to current system is updated non-Root authority version by acquiescence, thereby ensure that the safety of user terminal.
In one embodiment, the AKU of the Root authority version in step S102 and the non-Root power in step S105
The version number of limited in edition corresponding installation kit is identical.
Illustrate, be the Root power of 5.9.9 non-Root authority version or 5.9.9 regardless of the version of current operation system
Limited in edition, when upgrading next time, all can give tacit consent to and be upgraded to 5.9.10 non-Root authority version rather than be directly upgraded to 5.9.10
Root authority version, when user needs Root authority, it is necessary to the Root authority version of the 5.9.10 that again upgrades and non-Root
OTA (increment upgrading) delta package 5.9.10-root.patch of authority version.
In one embodiment, the version of current system is version or the version of Root authority of non-Root authority.
In the present embodiment, it is version or the version of Root authority of non-Root authority regardless of the version of current system,
When upgrading, all give tacit consent to the version upgrading to non-Root authority, when user has the demand obtaining Root authority, it is necessary to more next time
Secondary upgrading, thus ensure that the safety of user terminal.
In one embodiment, as it is shown in figure 5, said method can also include the steps of S307-S308:
In step S307, receive the operation closing Root authority.
In step S308, close Root authority.
In the present embodiment, after obtaining Root authority, in order to ensure stability and the safety of user terminal, user is also
Root authority can be closed at any time.
With specific embodiment, the technique scheme that disclosure embodiment provides is described below.
The method utilizing the control Root authority that disclosure embodiment provides, provides the user Root authority, such as Fig. 6 institute
Showing, the method is followed by following operation:
In step s 601, terminal to server sends the request carrying out version updating, comprises current system in this request
Version information (the Root authority version of 5.9.8 or 5.9.8 non-Root authority version).
In step S602, server receives the request carrying out version updating, according to the version of the current system in request
Information, it is thus achieved that the installation kit (5.9.9 that up-to-date and version information is corresponding higher than the non-Root authority version of current version information
Non-Root authority version), and send installation kit to terminal.
In step S603, terminal receives the up-to-date and version information of server feedback higher than current version information
The installation kit that non-Root authority version (5.9.9 non-Root authority version) is corresponding.
In step s 604, terminal installs this installation kit.
In step s 605, terminal to server sends and obtains asking of Root authority, and it is the most non-that this request comprises this locality
The version information of Root authority version,
In step S606, server receives the request obtaining Root authority, believes according to the version of current non-Root authority
Breath, it is thus achieved that the identical Root authority version (5.9.9Root authority version) of version number is relative to non-Root authority version (5.9.9
Non-Root authority version) delta package (5.9.9-root.patch).
In step S607, this delta package is sent to terminal by server.
In step S608, terminal receives the delta package of server feedback, installs this delta package, and system upgrade is 5.9.9
Root authority version.
In the present embodiment, when system is upgraded, first acquiescence is upgraded to non-Root authority version, when user wants Root to weigh
In limited time, need again to be upgraded to Root authority version, therefore, both can guarantee that the safety of a part of user terminal, and can be again another
A part has the user obtaining Root authority demand to provide convenient.
Following for disclosure device embodiment, may be used for performing method of disclosure embodiment.
Fig. 7 is according to a kind of block diagram controlling Root authority shown in an exemplary embodiment, for server, such as Fig. 7
Shown in, the device of this control Root authority includes:
First receiver module 71, is configured to receive the first request obtaining Root authority；First request comprises terminal and works as
The version information of front non-Root authority version.
First obtains module 72, is configured to the version information according to current non-Root authority, it is thus achieved that corresponding Root power
The AKU of limited in edition.
First sending module 73, is configured to send the AKU obtained.
The said apparatus of disclosure embodiment, user's acquiescence does not has Root authority, but has certain customers to have and want Root
The demand of authority, therefore, it is desirable to sending request to server, server is according to the version information of current non-Root authority, it is thus achieved that
The AKU of corresponding Root authority version, it is corresponding with current operation system version information that user needs the most actively to install this
The AKU of Root authority version, just can obtain Root authority, and this balances in safety and demand side, both can guarantee that one
The safety of certain customers' terminal, can have the user obtaining Root authority demand to provide convenient for another part again.
In one embodiment, AKU is that the identical Root authority version of version number is relative to non-Root authority version
Delta package.
In one embodiment, as shown in Figure 8, said apparatus may also include that
Second receiver module 74, is configured to receive the second request carrying out version updating, and the second request comprises current system
The version information of system.
Second obtains module 75, is configured to the version information according to the current system in the second request, it is thus achieved that up-to-date
And the installation kit that version information is corresponding higher than the non-Root authority version of the version information of current system.
Second sending module 76, is configured to send installation kit.
In the present embodiment, no matter the most whether operating system has Root authority, upper once upgrade time, all can be in service
Device end controls to be upgraded to non-Root version, now, sends the request updating system version to server, and server receives this please
After asking, it is thus achieved that the AKU of non-Root authority version, and this AKU is sent to terminal, updates operating system for terminal.By
In acquiescence, current system updated non-Root authority version, thereby ensure that the safety of user terminal.
Fig. 9 is that for terminal, this device can according to a kind of block diagram controlling Root authority shown in an exemplary embodiment
With by software, hardware or both be implemented in combination with become the some or all of of electronic equipment.As it is shown in figure 9, this control
The device of Root authority includes:
First sending module 91, is configured to send the first request obtaining Root authority to server；First request bag
Version information containing local current non-Root authority version.
First receiver module 92, is configured to receive the AKU of server feedback；AKU is corresponding Root authority
The AKU of version.
First installs module 93, is configured to install AKU, to obtain Root authority.
The said apparatus of disclosure embodiment, user's acquiescence does not has Root authority, but has certain customers to have and want Root
The demand of authority, therefore, it is desirable to sending request to server, server is according to the version information of current non-Root authority, it is thus achieved that
The AKU of corresponding Root authority version, after terminal receives the AKU of server feedback, user needs active again to install should
The AKU of the Root authority version corresponding with current operation system version information, just can obtain Root authority, and this is in safety
Balance with demand side, both can guarantee that the safety of a part of user terminal, can have acquisition Root power for another part again
The user of limit demand provides convenient.
In one embodiment, AKU is that the identical Root authority version of version number is relative to non-Root authority version
Delta package.
In one embodiment, as shown in Figure 10, said apparatus may also include that
Second sending module 94, is configured to send the second request carrying out version updating to server, the second request bag
Version information containing current system.
Second receiver module 95, is configured to the up-to-date and version information receiving server feedback higher than current system
The installation kit that the non-Root authority version of version information is corresponding.
Second installs module 96, is configured to install this installation kit.
In the present embodiment, no matter the most whether operating system has Root authority, upper once upgrade time, all can be in service
Device end controls to be upgraded to non-Root authority version, now, sends the request updating system version to server, and server receives
After this request, it is thus achieved that the AKU of non-Root authority version, and this AKU is sent to terminal, updates operation system for terminal
System.Owing to current system is updated non-Root authority version by acquiescence, thereby ensure that the safety of user terminal.
In one embodiment, the version of current system is version or the version of Root authority of non-Root authority.
In the present embodiment, it is version or the version of Root authority of non-Root authority regardless of the version of current system,
When upgrading, all give tacit consent to the version upgrading to non-Root authority, when user has the demand obtaining Root authority, it is necessary to more next time
Secondary upgrading, thus ensure that the safety of user terminal.
In one embodiment, as shown in figure 11, said apparatus may also include that
3rd receiver module 97, is configured to receive the operation closing Root authority.
Close module 98, be configured to close Root authority.
In the present embodiment, after obtaining Root authority, in order to ensure stability and the safety of user terminal, user is also
Root authority can be closed at any time.
Disclosure embodiment also provides for a kind of device controlling Root authority, including:
Processor；
For storing the memorizer of processor executable；
Wherein, described processor is configured to:
Receive the first request obtaining Root authority；Described first request comprises the version of the current non-Root authority version of terminal
This information；
Version information according to described current non-Root authority, it is thus achieved that the AKU of corresponding Root authority version；
Send the described AKU obtained.
It is that the identical Root authority version of version number is relative to non-Root that above-mentioned processor is also configured to described AKU
The delta package of authority version.
Above-mentioned processor is also configured to
Receiving the second request carrying out version updating, described second request comprises the version information of current system；
Version information according to the current system in described second request, it is thus achieved that up-to-date and version information is worked as higher than described
The installation kit that the non-Root authority version of the version information of front system is corresponding；
Send described installation kit.
Disclosure embodiment also provides for a kind of device controlling Root authority, including:
Processor；
For storing the memorizer of processor executable；
Wherein, described processor is configured to:
The first request obtaining Root authority is sent to server；Described first request comprises local current non-Root authority
The version information of version；
Receive the AKU of server feedback；Described AKU is the AKU of corresponding Root authority version；
Described AKU is installed, to obtain Root authority.
It is that the identical Root authority version of version number is relative to non-Root that above-mentioned processor is also configured to described AKU
The delta package of authority version.
Above-mentioned processor is also configured to send the second request carrying out version updating to server, described second request
Comprise the version information of current system；
Receive the up-to-date and version information non-Root power higher than the version information of described current system of server feedback
Limited in edition corresponding installation kit；
Described installation kit is installed.
Above-mentioned processor is also configured to the version that version is non-Root authority or the Root authority of described current system
Version.
Above-mentioned processor is also configured to receive the operation cutting out Root authority；
Close Root authority.
About the device in above-described embodiment, wherein modules performs the concrete mode of operation in relevant the method
Embodiment in be described in detail, explanation will be not set forth in detail herein.
Figure 12 is the block diagram according to a kind of device for controlling Root authority shown in an exemplary embodiment, this device
It is applicable to terminal unit.Such as, device 1200 can be mobile phone, computer, digital broadcast terminal, messaging devices,
Game console, tablet device, armarium, body-building equipment, personal digital assistant etc..
Device 1200 can include following one or more assembly: processes assembly 1202, memorizer 1204, power supply module
1206, multimedia groupware 1208, audio-frequency assembly 1210, the interface 1212 of input/output (I/O), sensor cluster 1214, and
Communications component 1216.
Process assembly 1202 and generally control the integrated operation of device 1200, such as with display, call, data communication,
The operation that camera operation and record operation are associated.Treatment element 1202 can include that one or more processor 1220 performs
Instruction, to complete all or part of step of above-mentioned method.Additionally, process assembly 1202 can include one or more mould
Block, it is simple to process between assembly 1202 and other assemblies is mutual.Such as, process assembly 1202 and can include multi-media module,
With facilitate multimedia groupware 1208 and process between assembly 1202 mutual.
Memorizer 1204 is configured to store various types of data to support the operation at device 1200.These data
Example include on device 1200 operation any application program or the instruction of method, contact data, telephone book data,
Message, picture, video etc..Memorizer 1204 can by any kind of volatibility or non-volatile memory device or they
Combination realizes, such as static RAM (SRAM), Electrically Erasable Read Only Memory (EEPROM), erasable can
Program read-only memory (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic memory, flash memory
Reservoir, disk or CD.
The various assemblies that power supply module 1206 is device 1200 provide electric power.Power supply module 1206 can include power management
System, one or more power supplys, and other generate, manage and distribute, with for device 1200, the assembly that electric power is associated.
The screen of one output interface of offer that multimedia groupware 1208 is included between described device 1200 and user.?
In some embodiments, screen can include liquid crystal display (LCD) and touch panel (TP).If screen includes touch panel,
Screen may be implemented as touch screen, to receive the input signal from user.Touch panel includes that one or more touch passes
Sensor is with the gesture on sensing touch, slip and touch panel.Described touch sensor can not only sense touch or slide dynamic
The border made, but also detect the persistent period relevant to described touch or slide and pressure.In certain embodiments, many
Media component 1208 includes a front-facing camera and/or post-positioned pick-up head.When device 1200 is in operator scheme, such as shooting mould
When formula or video mode, front-facing camera and/or post-positioned pick-up head can receive the multi-medium data of outside.Each preposition shooting
Head and post-positioned pick-up head can be a fixing optical lens system or have focal length and optical zoom ability.
Audio-frequency assembly 1210 is configured to output and/or input audio signal.Such as, audio-frequency assembly 1210 includes a wheat
Gram wind (MIC), when device 1200 is in operator scheme, during such as call model, logging mode and speech recognition mode, mike quilt
It is configured to receive external audio signal.The audio signal received can be further stored at memorizer 1204 or via communication
Assembly 1216 sends.In certain embodiments, audio-frequency assembly 1210 also includes a speaker, is used for exporting audio signal.
I/O interface 1212 provides interface, above-mentioned peripheral interface module for processing between assembly 1202 and peripheral interface module
Can be keyboard, put striking wheel, button etc..These buttons may include but be not limited to: home button, volume button, start button and
Locking press button.
Sensor cluster 1214 includes one or more sensor, for providing the state of various aspects to comment for device 1200
Estimate.Such as, what sensor cluster 1214 can detect device 1200 opens/closed mode, the relative localization of assembly, such as institute
Stating display and keypad that assembly is device 1200, sensor cluster 1214 can also detect device 1200 or device 1,200 1
The position change of individual assembly, the presence or absence that user contacts with device 1200, device 1200 orientation or acceleration/deceleration and dress
Put the variations in temperature of 1200.Sensor cluster 1214 can include proximity transducer, is configured to do not having any physics
The existence of object near detection during contact.Sensor cluster 1214 can also include optical sensor, as CMOS or ccd image sense
Device, for using in imaging applications.In certain embodiments, this sensor cluster 1214 can also include acceleration sensing
Device, gyro sensor, Magnetic Sensor, pressure transducer or temperature sensor.
Communications component 1216 is configured to facilitate the communication of wired or wireless mode between device 1200 and other equipment.Dress
Put 1200 and can access wireless network based on communication standard, such as WiFi, 2G or 3G, or combinations thereof.Exemplary at one
In embodiment, broadcast singal or broadcast that communications component 1216 receives from external broadcasting management system via broadcast channel are relevant
Information.In one exemplary embodiment, described communications component 1216 also includes near-field communication (NFC) module, to promote short distance
Communication.Such as, can be based on RF identification (RFID) technology in NFC module, Infrared Data Association (IrDA) technology, ultra broadband
(UWB) technology, bluetooth (BT) technology and other technologies realize.
In the exemplary embodiment, device 1200 can be by one or more application specific integrated circuits (ASIC), numeral
Signal processor (DSP), digital signal processing appts (DSPD), PLD (PLD), field programmable gate array
(FPGA), controller, microcontroller, microprocessor or other electronic components realize, be used for performing said method.
In the exemplary embodiment, a kind of non-transitory computer-readable recording medium including instruction, example are additionally provided
As included the memorizer 1204 of instruction, above-mentioned instruction can have been performed said method by the processor 1220 of device 1200.Example
If, described non-transitory computer-readable recording medium can be ROM, random access memory (RAM), CD-ROM, tape, soft
Dish and optical data storage devices etc..
Figure 13 is the block diagram according to a kind of device for controlling Root authority shown in an exemplary embodiment.Such as,
Device 1900 may be provided in a server.Device 1900 includes processing assembly 1922, and it farther includes one or more
Processor, and by the memory resource representated by memorizer 1932, can be by the finger of the execution processing assembly 1922 for storage
Order, such as application program.In memorizer 1932, the application program of storage can include each correspondence one or more
Module in one group of instruction.It is configured to perform instruction, to perform said method additionally, process assembly 1922.
Device 1900 can also include a power supply module 1926 be configured to perform device 1900 power management, one
Wired or wireless network interface 1950 is configured to be connected to device 1900 network, and input and output (I/O) interface
1958.Device 1900 can operate based on the operating system being stored in memorizer 1932, such as Windows ServerTM, Mac
OS XTM, UnixTM, LinuxTM, FreeBSDTM or similar.
A kind of non-transitory computer-readable recording medium, when the instruction in described storage medium is by the process of device 1200
When device performs so that device 1200 is able to carry out the method for above-mentioned control Root authority, and described method includes:
The first request obtaining Root authority is sent to server；Described first request comprises local current non-Root authority
The version information of version；
Receive the AKU of server feedback；Described AKU is the AKU of corresponding Root authority version；
Described AKU is installed, to obtain Root authority.
In one embodiment, described AKU is that the identical Root authority version of version number is relative to non-Root authority version
This delta package.
In one embodiment, described method may also include that
Send the second request carrying out version updating to server, described second request comprises the version letter of current system
Breath；
Receive the up-to-date and version information non-Root power higher than the version information of described current system of server feedback
Limited in edition corresponding installation kit；
Described installation kit is installed.
In one embodiment, the version of described current system is version or the version of Root authority of non-Root authority
This.
In one embodiment, described method may also include that
Receive the operation closing Root authority；
Close Root authority.
A kind of non-transitory computer-readable recording medium, when the instruction in described storage medium is by the process of device 1900
When device performs so that device 1900 is able to carry out the method for above-mentioned control Root authority, and described method includes:
Receive the first request obtaining Root authority；Described first request comprises the version of the current non-Root authority version of terminal
This information；
Version information according to described current non-Root authority, it is thus achieved that the AKU of corresponding Root authority version；
Send the described AKU obtained.
In one embodiment, described AKU is that the identical Root authority version of version number is relative to non-Root authority version
This delta package.
In one embodiment, described method may also include that
Receiving the second request carrying out version updating, described second request comprises the version information of current system；
Version information according to the current system in described second request, it is thus achieved that up-to-date and version information is worked as higher than described
The installation kit that the non-Root authority version of the version information of front system is corresponding；
Send described installation kit.
Those skilled in the art, after considering description and putting into practice disclosure disclosed herein, will readily occur to its of the disclosure
Its embodiment.The application is intended to any modification, purposes or the adaptations of the disclosure, these modification, purposes or
Person's adaptations is followed the general principle of the disclosure and includes the undocumented common knowledge in the art of the disclosure
Or conventional techniques means.Description and embodiments is considered only as exemplary, and the true scope of the disclosure and spirit are by following
Claim is pointed out.
It should be appreciated that the disclosure is not limited to precision architecture described above and illustrated in the accompanying drawings, and
And various modifications and changes can carried out without departing from the scope.The scope of the present disclosure is only limited by appended claim.
Claims (17)
1. the method controlling Root authority, it is characterised in that for server, including:
Receive the first request obtaining Root authority；Described first request comprises the version letter of the current non-Root authority version of terminal
Breath；
Version information according to described current non-Root authority, it is thus achieved that the AKU of corresponding Root authority version；
Send the described AKU obtained.
2. the method for claim 1, it is characterised in that described AKU is the Root authority version phase that version number is identical
Delta package for non-Root authority version.
3. method as claimed in claim 1 or 2, it is characterised in that described method also includes:
Receiving the second request carrying out version updating, described second request comprises the version information of current system；
Version information according to the current system in described second request, it is thus achieved that up-to-date and version information is higher than described current system
The installation kit that the non-Root authority version of version information of system is corresponding；
Send described installation kit.
4. the method controlling Root authority, it is characterised in that for terminal, including:
The first request obtaining Root authority is sent to server；Described first request comprises local current non-Root authority version
Version information；
Receive the AKU of server feedback；Described AKU is the AKU of corresponding Root authority version；
Described AKU is installed, to obtain Root authority.
5. method as claimed in claim 4, it is characterised in that described AKU is the Root authority version phase that version number is identical
Delta package for non-Root authority version.
6. the method as described in claim 4 or 5, it is characterised in that described method also includes:
Send the second request carrying out version updating to server, described second request comprises the version information of current system；
Receive the up-to-date and version information non-Root authority version higher than the version information of described current system of server feedback
The installation kit of this correspondence；
Described installation kit is installed.
7. method as claimed in claim 6, it is characterised in that the version of described current system be non-Root authority version or
The version of person's Root authority.
8. the method as according to any one of claim 4-7, it is characterised in that described method also includes:
Receive the operation closing Root authority；
Close Root authority.
9. the device controlling Root authority, it is characterised in that for server, including:
First receiver module, for receiving the first request obtaining Root authority；It is the most non-that described first request comprises terminal
The version information of Root authority version；
First obtains module, for the version information according to described current non-Root authority, it is thus achieved that corresponding Root authority version
AKU；
First sending module, for sending the described AKU of acquisition.
10. device as claimed in claim 9, it is characterised in that described AKU is the Root authority version that version number is identical
Delta package relative to non-Root authority version.
11. devices as described in claim 9 or 10, it is characterised in that described device also includes:
Second receiver module, for receiving the second request carrying out version updating, described second request comprises the version of current system
This information；
Second obtains module, for the version information according to the current system in described second request, it is thus achieved that up-to-date and version
The installation kit that information is corresponding higher than the non-Root authority version of the version information of described current system；
Second sending module, is used for sending described installation kit.
12. 1 kinds of devices controlling Root authority, it is characterised in that for terminal, including:
First sending module, for sending the first request obtaining Root authority to server；Described first request comprises this locality
The version information of current non-Root authority version；
First receiver module, for receiving the AKU of server feedback；Described AKU is corresponding Root authority version
AKU；
First installs module, is used for installing described AKU, to obtain Root authority.
13. devices as claimed in claim 12, it is characterised in that described AKU is the Root authority version that version number is identical
Delta package relative to non-Root authority version.
14. devices as described in claim 12 or 13, it is characterised in that described device also includes:
Second sending module, for sending the second request carrying out version updating to server, described second request comprises current
The version information of system；
Second receiver module, for receiving the up-to-date of server feedback and the version information version letter higher than described current system
The installation kit corresponding to non-Root authority version of breath；
Second installs module, is used for installing described installation kit.
15. devices as claimed in claim 14, it is characterised in that the version of described current system is the version of non-Root authority
Or the version of Root authority.
16. devices as according to any one of claim 12-15, it is characterised in that described device also includes:
3rd receiver module, for receiving the operation closing Root authority；
Close module, be used for closing Root authority.
17. 1 kinds of devices controlling Root authority, it is characterised in that including:
Processor；
For storing the memorizer of processor executable；
Wherein, described processor is configured to:
Receive the first request obtaining Root authority；Described first request comprises the version letter of the current non-Root authority version of terminal
Breath；
Version information according to described current non-Root authority, it is thus achieved that the AKU of corresponding Root authority version；
Send the described AKU obtained.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610483675.5A CN106162612B (en) | 2016-06-27 | 2016-06-27 | Control the method and device of Root authority |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610483675.5A CN106162612B (en) | 2016-06-27 | 2016-06-27 | Control the method and device of Root authority |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106162612A true CN106162612A (en) | 2016-11-23 |
| CN106162612B CN106162612B (en) | 2019-11-08 |
Family
ID=57350045
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610483675.5A Active CN106162612B (en) | 2016-06-27 | 2016-06-27 | Control the method and device of Root authority |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106162612B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107332728A (en) * | 2017-06-06 | 2017-11-07 | 努比亚技术有限公司 | A kind of detection method, terminal device and computer can storage mediums |
| CN109657448A (en) * | 2018-12-21 | 2019-04-19 | 惠州Tcl移动通信有限公司 | A kind of method, apparatus, electronic equipment and storage medium obtaining Root authority |
| CN115562696A (en) * | 2022-02-24 | 2023-01-03 | 荣耀终端有限公司 | Software upgrading method, control equipment and intelligent screen |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104506639A (en) * | 2014-12-29 | 2015-04-08 | 北京奇虎科技有限公司 | Root right acquiring method and device |
| CN104778057A (en) * | 2015-03-11 | 2015-07-15 | 小米科技有限责任公司 | Terminal system upgrading method and device, and server |
| US20160170782A1 (en) * | 2012-06-28 | 2016-06-16 | Amazon Technologies, Inc. | Network policy implementation with multiple interfaces |
-
2016
- 2016-06-27 CN CN201610483675.5A patent/CN106162612B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160170782A1 (en) * | 2012-06-28 | 2016-06-16 | Amazon Technologies, Inc. | Network policy implementation with multiple interfaces |
| CN104506639A (en) * | 2014-12-29 | 2015-04-08 | 北京奇虎科技有限公司 | Root right acquiring method and device |
| CN104778057A (en) * | 2015-03-11 | 2015-07-15 | 小米科技有限责任公司 | Terminal system upgrading method and device, and server |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107332728A (en) * | 2017-06-06 | 2017-11-07 | 努比亚技术有限公司 | A kind of detection method, terminal device and computer can storage mediums |
| CN109657448A (en) * | 2018-12-21 | 2019-04-19 | 惠州Tcl移动通信有限公司 | A kind of method, apparatus, electronic equipment and storage medium obtaining Root authority |
| CN115562696A (en) * | 2022-02-24 | 2023-01-03 | 荣耀终端有限公司 | Software upgrading method, control equipment and intelligent screen |
| CN115562696B (en) * | 2022-02-24 | 2023-09-08 | 荣耀终端有限公司 | Software upgrading method, control equipment and intelligent screen |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106162612B (en) | 2019-11-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3188414B1 (en) | Method and apparatus for controlling smart device | |
| US20180365004A1 (en) | Method and device for calling software development kit | |
| EP3151507A1 (en) | Methods and apparatuses for controlling device | |
| CN104038263A (en) | Method and device for establishing Bluetooth connection | |
| CN104320774A (en) | Updating method, device and facility | |
| CN103916468B (en) | Method for upgrading system, terminal, server and upgrade-system | |
| CN105094931A (en) | Software upgrading method and device | |
| CN105722064A (en) | Method and device for acquiring terminal information | |
| CN103944963A (en) | Data synchronization method, device and system and equipment | |
| EP2981116A1 (en) | Method and apparatus for accessing wi-fi network and computer program product | |
| CN103957103A (en) | Safety authentication method and device and mobile terminal | |
| CN104766005A (en) | Management method and device for application software access authority | |
| CN104486451A (en) | Application program recommendation method and device | |
| CN106371327A (en) | Control right sharing method and device | |
| CN104811776A (en) | Multimedia playing method and device | |
| KR20170038178A (en) | Method, apparatus, and mobile terminal for identificating fingerprint | |
| CN105068848A (en) | System upgrading method and apparatus | |
| CN104767857A (en) | Telephone calling method and device based on cloud name cards | |
| CN105631254A (en) | Unlocking method and unlocking device | |
| CN104714826A (en) | Application theme loading method and device | |
| CN105094830A (en) | Method and device for executing target functions | |
| CN106162612A (en) | Control the method and device of Root authority | |
| US20170075671A1 (en) | Method and apparatus for installing application and smart device using the same | |
| CN104866349A (en) | Application updating method and device | |
| CN105323318A (en) | Parameter modifying method, parameter modifying device and parameter modifying equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |