Methods, devices and systems for managing authority

CROSS-REFERENCE TO RELATED APPLICATIONS

0001This application is a continuation of International Application No. PCT/CN2014/091746, filed Nov. 20, 2014, which is based upon and claims priority to Chinese Patent Application No. 201410286860.6, filed Jun. 24, 2014, the entire contents of all of which are incorporated herein by reference.

TECHNICAL FIELD

0002The present disclosure generally relates to smart devices and, more particularly, to methods, devices and systems for managing an authority.

BACKGROUND

0003Authority management has become important for smart devices as a number of applications may be installed in the smart devices. Authority management generally means that a user may only access resources that are authorized according to security rules or security strategies set by systems.

0004Conventionally, according to different levels of users, different authority operations may be granted by the systems. For example, in an Android system, authorities are classified into different levels, and predefined authorities in the system belong to different levels according to different functions granted. For example, general authorities may be granted to applications according to settings of the users, and system authorities may be granted only to applications that are certified at a platform level. When the applications try to perform operations without being granted authorities, the applications may not be permitted to perform the operations, and an alert may be provided to the user. On the other hand, system applications may be granted authority to perform any operation, and a declarant of an authority may be granted the authority without any limitations.

SUMMARY

0005According to a first aspect of the present disclosure, there is provided a method for managing an authority, comprising: acquiring authority use data of a user; processing the authority use data to obtain an authority result; and sending the authority result to a terminal device.

0006According to a second aspect of the present disclosure, there is provided a method for managing an authority, comprising: receiving an authority result sent from a server; acquiring configuration information of the authority based on the authority result; and updating a corresponding authority option based on the configuration information of the authority.

0007According to a third aspect of the present disclosure, there is provided a device for managing an authority, comprising: a processor; and a memory for storing instructions executable by the processor. The processor is configured to: acquire authority use data of a user; process the authority use data to obtain an authority result; and send the authority result to a terminal device.

0008It is to be understood that both the foregoing general description and the following detailed description are exemplary rather than limiting the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

0009The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments being consistent with the invention and serve to explain the principles of the invention.

0010<figref idref="DRAWINGS">FIG. 1</figref> is a flowchart of a method for managing an authority, according to an exemplary embodiment.

0011<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart of a method for managing an authority, according to an exemplary embodiment.

0012<figref idref="DRAWINGS">FIG. 3</figref> is a diagram illustrating an interface after an authority option is updated, according to an exemplary embodiment.

0013<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart of a method for managing an authority, according to an exemplary embodiment.

0014<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart of a method for obtaining an authority result, according to an exemplary embodiment.

0015<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart of a method for managing an authority, according to an exemplary embodiment.

0016<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart of a method for performing cluster analysis, according to an exemplary embodiment.

0017<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart of a method for managing an authority, according to an exemplary embodiment.

0018<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart of a method for determining an accuracy degree of an authority selection, according an exemplary embodiment.

0019<figref idref="DRAWINGS">FIG. 10</figref> is a flowchart of a method for managing an authority, according to an exemplary embodiment.

0020<figref idref="DRAWINGS">FIG. 11</figref> is a flowchart of a method for acquiring configuration information, according to an exemplary embodiment.

0021<figref idref="DRAWINGS">FIG. 12<i>a </i></figref>is a diagram illustrating an interface of authority options, according to an exemplary embodiment.

0022<figref idref="DRAWINGS">FIG. 12<i>b </i></figref>is a diagram illustrating an interface of authority options, according to an exemplary embodiment.

0023<figref idref="DRAWINGS">FIG. 13</figref> is a flowchart of a method for managing an authority, according to an exemplary embodiment.

0024<figref idref="DRAWINGS">FIG. 14</figref> is a diagram illustrating an interface of a white list application, according to an exemplary embodiment.

0025<figref idref="DRAWINGS">FIG. 15</figref> is a diagram illustrating an interface of auto-start type authority management, according to an exemplary embodiment.

0026<figref idref="DRAWINGS">FIG. 16</figref> is a diagram illustrating an interface of sensitive authority management, according to an exemplary embodiment.

0027<figref idref="DRAWINGS">FIG. 17</figref> is a diagram illustrating an interface of authority management in an application dimension, according to an exemplary embodiment.

0028<figref idref="DRAWINGS">FIG. 18</figref> is a diagram illustrating an interface of detailed information of an application authority, according to an exemplary embodiment.

0029<figref idref="DRAWINGS">FIG. 19</figref> is a diagram illustrating an interface of authority management in an authority dimension, according to an exemplary embodiment.

0030<figref idref="DRAWINGS">FIG. 20</figref> is a diagram of an interface of applications illustrated under management of an authority dimension, according to an exemplary embodiment.

0031<figref idref="DRAWINGS">FIG. 21</figref> is a diagram illustrating an interface of applications shown in a ROOT authority management page, according to an exemplary embodiment.

0032<figref idref="DRAWINGS">FIG. 22<i>a </i></figref>is a diagram illustrating an interface for applying a ROOT authority, according to an exemplary embodiment.

0033<figref idref="DRAWINGS">FIG. 22<i>b </i></figref>is a diagram illustrating an interface for applying a ROOT authority, according to an exemplary embodiment.

0034<figref idref="DRAWINGS">FIG. 22<i>c </i></figref>is a diagram illustrating an interface for applying a ROOT authority, according to an exemplary embodiment.

0035<figref idref="DRAWINGS">FIG. 22<i>d </i></figref>is a diagram illustrating an interface for applying a ROOT authority, according to an exemplary embodiment.

0036<figref idref="DRAWINGS">FIG. 22<i>e </i></figref>is a diagram illustrating an interface for applying a ROOT authority, according to an exemplary embodiment.

0037<figref idref="DRAWINGS">FIG. 23</figref> is a diagram illustrating an interface of an application in ROOT authority management, according to an exemplary embodiment.

0038<figref idref="DRAWINGS">FIG. 24</figref> is a flowchart of a method for managing an authority, according to an exemplary embodiment.

0039<figref idref="DRAWINGS">FIG. 25</figref> is a block diagram of a device for managing an authority, according to an exemplary embodiment.

0040<figref idref="DRAWINGS">FIG. 26</figref> is a block diagram of a processing module, according to an exemplary embodiment.

0041<figref idref="DRAWINGS">FIG. 27</figref> is a block diagram of a processing sub-module, according to an exemplary embodiment.

0042<figref idref="DRAWINGS">FIG. 28</figref> is a diagram of a processing sub-module, according to an exemplary embodiment.

0043<figref idref="DRAWINGS">FIG. 29</figref> is a block diagram of a processing sub-module, according to an exemplary embodiment.

0044<figref idref="DRAWINGS">FIG. 30</figref> is a block diagram of an adjustment sub-module, according to an exemplary embodiment.

0045<figref idref="DRAWINGS">FIG. 31</figref> is a block diagram of a device for managing an authority, according to an exemplary embodiment.

0046<figref idref="DRAWINGS">FIG. 32</figref> is a block diagram of an acquiring module, according to an exemplary embodiment.

0047<figref idref="DRAWINGS">FIG. 33</figref> is a block diagram of an acquiring unit, according to an exemplary embodiment.

0048<figref idref="DRAWINGS">FIG. 34</figref> is a block diagram of an updating module, according to an exemplary embodiment.

0049<figref idref="DRAWINGS">FIG. 35</figref> is a block diagram of an updating module, according to an exemplary embodiment.

0050<figref idref="DRAWINGS">FIG. 36</figref> is a block diagram of an updating module, according to an exemplary embodiment.

0051<figref idref="DRAWINGS">FIG. 37</figref> is a block diagram of a terminal device, according to an exemplary embodiment.

0052<figref idref="DRAWINGS">FIG. 38</figref> is a block diagram of a device, according to an exemplary embodiment.

DETAILED DESCRIPTION

0053Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When accompanying drawings are mentioned in the following description, the same numbers in different drawings represent the same or similar elements, unless otherwise represented. The following exemplary embodiments and description thereof intend to illustrate, rather than to limit, the present disclosure. Hereinafter, the present disclosure will be described with reference to the drawings.

0054<figref idref="DRAWINGS">FIG. 1</figref> is a flowchart of a method <b>100</b> for managing an authority, according to an exemplary embodiment. For example, the method <b>100</b> may be used in a server. Referring to <figref idref="DRAWINGS">FIG. 1</figref>, the method <b>100</b> includes the following steps.

0055In step S<b>11</b>, the server acquires authority use data of a user. The authority use data can be a use record of an authority option of the user. For example, the use record may include a user identification (ID), an application name, a defined operation granted by an authority, and/or an authority selection. The use record may also include a modification record of authority settings. In some embodiments, the authority use data may be acquired from a cloud.

0056In step S<b>12</b>, the server processes the authority use data to obtain an authority result.

0057In some embodiments, the authority selection may include permission, rejection, inquiry and default, where the default may refer to the initial authority selection that is not modified. For example, in SMS (Short Message Service), the operation granted by the authority is accessing SMS inbox. The authority selection may be acquired based on statistics of records used by the user. The authority selection of accessing SMS inbox may include, for example, permitting accessing SMS inbox, refusing accessing SMS inbox, inquiring of the user before accessing SMS inbox, or no authority of accessing SMS inbox being set. The server may classify and process the records based on the authority selection to obtain the authority result of the application of accessing SMS inbox.

0058In step S<b>13</b>, the server sends the authority result obtained by the processing to a terminal device, for the terminal device to update a corresponding authority option.

0059In some embodiments, the authority result may include a user ID, an application name, a defined operation granted by an authority, and/or, an authority selection. When the terminal device receives the authority result sent from the server, the terminal device may perform a corresponding update on the corresponding authority option.

0060In the method <b>100</b>, the authority use data of the user may be acquired from the cloud, the authority use data is analyzed and processed to obtain the authority result, and then the authority result is sent to the terminal device for the terminal device to update the authority option of the corresponding application. In doing so, the user may avoid manually changing the authority setting. Moreover, because the authority use data of the user to be analyzed may be acquired from the cloud, the corresponding authority can be automatically updated in time according to latest requirements, so as to simply the process for changing the authority settings of the application.

0061<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart of a method <b>200</b> for managing an authority, according to an exemplary embodiment. For example, the method <b>200</b> may be used in a server. Referring to <figref idref="DRAWINGS">FIG. 2</figref>, the method <b>200</b> includes the following steps.

0062In step S<b>21</b>, the server acquires authority use data of a user from a cloud. The authority use data can be a use record of an authority option of the user that is recorded in the cloud. The use record may include a user ID, an application name, a defined operation granted by an authority, and/or an authority selection. The use record may also include a modification record of authority settings.

0063In some embodiments, sample records may be acquired from history records used by the user in the cloud. The number of the acquired sample records may be set, and the number of the acquired sample records may be based on, for example, records of the user during a period of time, a preset number of the history records, etc. For example, the records used by the user during a period of time may be acquired as the sample records.

0064In step S<b>22</b>, the server processes the authority use data based on the authority selection to obtain an authority confidence value and an initial authority selection.

0065In some embodiments, the authority selection may include permission, rejection, inquiry and default, where the default may refer to the initial authority selection that is not modified. For example, in SMS (Short Message Service), the defined operation granted by the authority is accessing SMS inbox. The authority selection may be acquired based on statistics of records used by the user. The authority selection of accessing SMS inbox may include, for example, permitting accessing SMS inbox, refusing accessing SMS inbox, inquiring of the user before accessing SMS inbox or no authority of accessing SMS inbox being set. The records may be classified and processed according to the authority selection, to obtain the authority result of the application of accessing SMS inbox.

0066The processing of the authority use data in step S<b>22</b> may be online processing, or offline processing.

0067In step S<b>23</b>, the server adjusts the initial authority selection based on the authority confidence value and a threshold value, to obtain the authority result. For example, the authority confidence value is a value for representing reliability of the authority result, which indicates a degree of reliability. When the records of the user are sampled, by applying a statistical method, e.g., an interval estimation method in mathematical statistics, the probability that an estimated value is within a certain allowable error range of the true value can be determined. The probability is referred to as the authority confidence value, and the threshold value refers to the lowest authority confidence value that meets the requirements.

0068In step S<b>24</b>, the server sends the authority result to the terminal device, for the terminal device to update a corresponding authority option.

0069In some embodiments, the authority result may include a user ID, an application name, a defined operation granted by an authority, and/or an authority selection. When the terminal device receives the authority result from the server, the terminal device may perform a corresponding update on the authority option.

0070<figref idref="DRAWINGS">FIG. 3</figref> is a diagram illustrating an interface <b>300</b> of authority options, according to an exemplary embodiment. For example, in the authority result, the authority options for a mobile network, WiFi, Bluetooth, a floating window, a sleeping setting, and system settings are turning on the mobile network, turning on WiFi, turning on Bluetooth, popping up the floating window, controlling sleeping, modifying the system settings, respectively. As shown in <figref idref="DRAWINGS">FIG. 3</figref>, the terminal device updates the authority options in the interface <b>300</b> according to the authority result.

0071In the method <b>200</b>, the authority use data of the user is acquired from the cloud, the authority use data is analyzed and processed to obtain the authority result, and then the authority result is sent to the terminal device, for the terminal device to automatically update the authority option of the corresponding application. In doing so, the user may avoid manually changing the authority setting. Moreover, because the authority use data of the user may be acquired from the cloud, the corresponding authority can be automatically updated in time based on latest requirements, thereby simplifying the process for updating the authority settings of the application.

0072<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart of a method <b>400</b> for managing an authority, according to an exemplary embodiment. For example, the method <b>400</b> may be used in a server. Referring to FIG. <b>4</b>, the method <b>400</b> includes the following steps.

0073In step S<b>41</b>, the server acquires authority use data of a user from a cloud. The authority use data can be a use record of an authority option of the user that is recorded in a cloud. The use record may include a user <b>11</b>), an application name, a defined operation granted by an authority, and/or an authority selection. The use record may also include a modification record of authority settings. In the method <b>400</b>, the process for acquiring the authority use data of the user from the cloud is similar to step S<b>21</b> described above in connection with <figref idref="DRAWINGS">FIG. 2</figref>.

0074In step S<b>42</b>, the server performs de-noising processing on the authority use data. The de-noising processing includes, e.g., removing noise data and invalid data, which may be based on wavelet analysis, an offline curve de-noising processing, or the like.

0075In step S<b>43</b>, the server performs a Support Vector Machine (SVM) training on the de-noised authority use data based on the authority selection to obtain an authority confidence value and an initial authority selection of the corresponding authority option. The authority selection may be a permission or rejection in the authority option, and the SVM is known as a trainable machine learning method.

0076In some embodiments, a linear SVM training classifier f: (user, app, permission)→decision may be applied to the de-noised authority use data, where “user” refers to the user, “app” refers to the application name, and “permission” refers to whether the authority is permitting to be accessed while training. The training is performed with respect to the two selections “permission” or “rejection”, and “decision” refers to the obtained initial authority selection of the user. Based on the linear SVM training classifier f: (user, app, permission)→decision, the initial authority selection and the authority confidence value of the user are obtained. In the obtained training result, the result of the initial authority selection may include “permission” or “rejection”, and the authority confidence value refers to a value for representing reliability of the authority result.

0077In step S<b>44</b>, the server adjusts the initial authority selection based on the authority confidence value and a threshold value, to obtain the authority result. The authority result may include a user ID, an application name, a defined operation granted by an authority, and/or an authority selection.

0078<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart of a method <b>500</b> for obtaining an authority result, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 5</figref>, the method <b>500</b> includes the following steps.

0079In step S<b>44</b>-<b>1</b>, the server compares the authority confidence value corresponding to the authority option with the threshold value.

0080In some embodiments, the threshold value may be controlled by setting a total inquiry ratio. For example, the threshold value may be controlled by limiting the authority of the inquiry to no more than 10% of the total authority options.

0081In step S<b>44</b>-<b>2</b>, when the authority confidence value is lower than the threshold value, the server adjusts the initial authority selection to be an inquiry selection, as the authority result. For example, when the authority confidence value is lower than the threshold value that is set, the authority selection of the authority option may be set as inquiry. For example, when the threshold value is 0.3, and the authority confidence value is 0.25, the initial authority selection is adjusted to be the inquiry selection, as the authority result. The result of the initial authority selection may include “permission” and “rejection”, and after the confidence value is compared with the threshold value and the adjustment is made, the authority selection may be adjusted to be “inquiry”.

0082In step S<b>44</b>-<b>3</b>, when the authority confidence value is greater than or equal to the threshold value, the server uses the initial authority selection as the authority result. For example, when the threshold value is 0.3, and the authority confidence value is 0.5, the initial authority selection is used as the authority result.

0083Referring back to <figref idref="DRAWINGS">FIG. 4</figref>, in step S<b>45</b>, the server sends the authority result obtained by the adjustment to the terminal device, for the terminal device to update the corresponding authority option.

0084In some embodiments, the authority result may include a user ID, an application name, a defined operation granted by an authority, and/or an authority selection. When the terminal device receives the authority result from the server, the terminal device may perform a corresponding update on the authority options. For example, in the authority result, the authority options for a mobile network, WiFi, Bluetooth, a floating window, a sleeping setting, and system settings may be turning on the mobile network, turning on WiFi, turning on Bluetooth, popping up the floating window, controlling sleeping, and modifying the system settings, respectively.

0085In the method <b>400</b>, a SVM training is performed on the authority use data of the user that is acquired from the cloud based on the authority selection to obtain the authority result, and the trained authority result is sent to the terminal device for the terminal device to automatically update the corresponding authority option according to the received authority result. In doing so, the user may avoid manually changing the authority setting and improved authority result may be achieved.

0086<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart of a method <b>600</b> for managing an authority, according to an exemplary embodiment. For example, the method <b>600</b> may be used in a server. Referring to <figref idref="DRAWINGS">FIG. 6</figref>, the method <b>600</b> includes the following steps.

0087In step S<b>61</b>, the server acquires authority use data of a user from a cloud. The authority use data can be a use record of an authority option of the user that is recorded in the cloud. The use record may include a user ID, an application name, a defined operation granted by an authority, and/or an authority selection. The user record may also include a modification record of authority settings.

0088In the method <b>600</b>, the process for acquiring the authority use data of the user from the cloud is similar to step S<b>21</b> described above in connection with <figref idref="DRAWINGS">FIG. 2</figref>.

0089In step S<b>62</b>, the server performs de-noising processing on the authority use data. The de-noising processing includes removing, e.g., noise data and invalid data, which may be based on wavelet analysis, an offline curve de-noising processing, or the like.

0090In step S<b>63</b>, the server performs cluster analysis on the authority use data based on a cluster algorithm to obtain a cluster type of the user.

0091<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart of a method <b>700</b> for performing cluster analysis, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 7</figref>, the method <b>700</b> includes the following steps.

0092In step S<b>63</b>-<b>1</b>, the server analyzes an authority of each user based on the cluster algorithm to obtain a user similarity degree.

0093For example, suppose there are n authorities, each user may be represented as a n-dimensional vector, and clustering may be performed by using a K-means method to obtain an Euclidean distance of the user, where the Euclidean distance represents the user similarity degree.

0094In step S<b>63</b>-<b>2</b>, the server determines a cluster result based on a discrimination degree and the user similarity degree.

0095In step S<b>63</b>-<b>3</b>, the server selects a cluster number for a preset dataset as the cluster type of the user, based on the cluster result.

0096In some embodiments, the authority can be determined by using a general classifier at first, and after an amount of data is collected after a period of time, the server may determine the type to which the use belongs and then determine the authority by using a classifier of that type.

0097Referring back to <figref idref="DRAWINGS">FIG. 6</figref>, in step S<b>64</b>, based on the cluster type of the user, the server performs a SVM training on each type of the user respectively based on the authority selection to obtain an authority confidence value and an initial authority selection corresponding to the authority option, where the SVM is a trainable machine learning method.

0098In some embodiments, a corresponding linear SVM training classifier f: (user, app, permission)→decision is applied to the classified authority use data, where “user” refers to the user, “app” refers to the application name, “permission” refers to whether the authority is permitting to be accessed while training. The training may be performed with respect to the two authority selections “permission” and “rejection”, and “decision” refers to the obtained initial authority selection of the user. Based on the linear SVM training classifier f: (user, app, permission)→decision, the initial authority selection and the authority confidence value of the user are obtained. In the obtained training result, the result of the initial authority selection may include “permission” or “rejection”, and the authority confidence value refers to a value for representing reliability of the authority result.

0099In step S<b>65</b>, the server adjusts the initial authority selection based on the authority confidence value and a threshold value, to obtain the authority result. The authority result may include a user ID), an application name, a defined operation granted by an authority, and/or an authority selection.

0100In step S<b>66</b>, the server sends the authority result obtained by the adjustment to the terminal device, for the terminal device to update the corresponding authority option. The authority result may include a user ID, an application name, a defined operation granted by an authority, and/or an authority selection. When the terminal device receives the authority result sent from the server, the terminal device may perform corresponding update on the authority options. For example, in the authority result, the authority options in a mobile network, WiFi, Bluetooth, a floating window, a sleeping setting, and system settings may be turning on the mobile network, turning on WiFi, turning on Bluetooth, popping up the floating window, controlling sleeping, and modifying the system settings, respectively.

0101In the method <b>600</b>, the cluster analysis is performed with respect to the user, and users who have high similarity in habit of setting the authority are clustered and analyzed. Thus, the analyzed authority result is targeted for the user, and the update of the authority settings is more accurate, taking into account the habits of the users.

0102<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart of a method <b>800</b> for managing an authority, according to an exemplary embodiment. For example, the method <b>800</b> may be used in a server. Referring to <figref idref="DRAWINGS">FIG. 8</figref>, the method <b>800</b> includes the following steps.

0103In step S<b>81</b>, the server acquires authority use data of a user from a cloud. The authority use data can be a use record of an authority option of the user that is recorded in the cloud. The use record may include a user ID, an application name, a defined operation granted by an authority, and/or an authority selection. The use record may also include a modification record of authority settings.

0104In the method <b>800</b>, the process for acquiring the authority use data of the user from the cloud is similar to step S<b>21</b> described above in connection with <figref idref="DRAWINGS">FIG. 2</figref>.

0105In step S<b>82</b>, the server performs de-noising processing on the authority use data. The de-noising processing includes removing noise data and invalid data, which may be based on wavelet analysis, an offline curve de-noising processing, or the like.

0106In step S<b>83</b>, the server classifies the de-noised authority use data is into training set data and testing set data based on a classification ratio. The classification ratio may be set according to requirements of the testing set data and the training set data. For example, entire data of 90% users, as well as data of 20% applications of the remaining 10% users may be used as the training set data, and the other 80% applications of the remaining 10% users may be used as the testing set data. The data may be randomly assigned.

0107In step S<b>84</b>, the server performs a SVM training on the training set data based on the authority selection of permission or rejection in the authority option, to obtain an initial authority selection and an authority confidence value corresponding to the authority option. The SVM is a trainable machine learning method.

0108In some embodiments, a linear SVM training classifier f: (user, app, permission)→decision may be applied to the de-noised authority use data, where “user” refers to the user, “app” refers to the application name, “permission” refers to whether the authority is permitting to be accessed while training. The training is performed with respect to the authority selection of “permission” and “rejection”, and “decision” refers to the obtained initial authority selection of the user. Based on the linear SVM training classifier f: (user, app, permission)→decision, the initial authority selection and the authority confidence value of the user are obtained. In the obtained training result, the result of the initial authority selection may be “permission” or “rejection”, where the authority confidence value refers to a value for representing reliability of the authority result.

0109In step S<b>85</b>, the server determines an accuracy degree of the initial authority selection based on the testing set data, to obtain an accuracy degree of the authority selection.

0110<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart of a method <b>900</b> for determining accuracy degree of an authority selection, according an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 9</figref>, the method <b>900</b> includes the following steps.

0111In step S<b>85</b>-<b>1</b>, the server initializes a counter, and compares the authority confidence value with the threshold value, until all data are compared.

0112In step S<b>85</b>-<b>2</b>, when the authority confidence value is greater than the threshold value, the server determines whether the initial authority selection is the same as the corresponding authority selection in the testing set data. If the initial authority selection is the same as the corresponding authority selection in the testing set data, the value of the counter is increased by 1. If the initial authority selection is different from the corresponding authority selection in the testing set data, no operation is performed.

0113In step S<b>85</b>-<b>3</b>, when the authority confidence value is lower than the threshold value, the server adjusts the initial authority selection to be an inquiry selection and the value of the counter is increased by 1.

0114In step S<b>85</b>-<b>4</b>, the server calculates a ratio between the value of the counter and a total number of the compared data to obtain the accuracy degree of the authority selection.

0115Referring back to <figref idref="DRAWINGS">FIG. 8</figref>, in step S<b>86</b>, the server adjusts the initial authority selection based on the authority confidence value and the threshold value.

0116In some embodiments, step S<b>86</b> may include the same operations of steps S<b>44</b>-<b>1</b> to S<b>44</b>-<b>3</b> described above in connection with <figref idref="DRAWINGS">FIG. 5</figref>.

0117In step S<b>87</b>, the server sends the adjusted initial authority selection and the accuracy degree of the authority selection of the corresponding application to the terminal device as the authority result, for the terminal device to determine whether to update the corresponding authority option. The authority result may include, for example, a user ID, an application name, a defined operation granted by an authority, an authority selection, and/or an accuracy degree of the authority selection. When the terminal device receives the authority result sent from the server, the terminal device may perform corresponding update. For example, in the authority result, the authority options of a mobile network, WiFi, Bluetooth, a floating window, sleeping, and system settings may be respectively turning on the mobile network, turning on WiFi, turning on Bluetooth, popping up the floating window, controlling sleeping, and modifying the system settings.

0118In the method <b>800</b>, by calculating the accuracy degree of the authority selection, an accuracy degree of an analysis result of the authority use data may be determined, and whether to update the authority result of the user may be determined according to the accuracy degree, thereby an error rate of updating the authority may be decreased.

0119<figref idref="DRAWINGS">FIG. 10</figref> is a flowchart of a method <b>1000</b> for managing an authority, according to an exemplary embodiment. For example, the method <b>1000</b> may be used in a terminal device. Referring to <figref idref="DRAWINGS">FIG. 10</figref>, the method <b>1000</b> includes the following steps.

0120In step S<b>1001</b>, the terminal device receives an authority result sent from a server.

0121The authority result may include, for example, a user ID, an application name, a defined operation granted by an authority, and/or an authority selection. The user ID) may identify the user, which may be a cell phone number, a user name of a registered user, or other contents that may identify the user, such as a Mi-Talk number. The application name refers to a program or an application with respect to which an authority option may set. The application may include applications used by the user such as Mi-Talk, WeChat and the like, applications that auto-start in a system, system programs such as Computer, On-line Neighbor and the like. The authority selection may include permission, rejection, inquiry, and/or default. For example, in SMS (Short Message Service), the defined operation granted by the authority is accessing SMS inbox. Based on statistics of records used by the user, an application may be permitted accessing SMS inbox, rejected accessing SMS inbox, or required to inquire of the user before accessing SMS inbox. For an application with respect to which no authority of accessing SMS inbox is set, records used by the data maybe classified and processed based on the authority selection, to obtain the authority result of the application of accessing SMS inbox.

0122In step S<b>1002</b>, the terminal device acquires corresponding configuration information based on the authority result. The configuration information may include, for example, type information of an authority and setting information of the corresponding authority. For example, the type of an authority may be an auto-start type, an application type, or a ROOT type. The setting of an authority may be sensitive information or description information of the authority.

0123In some embodiments, a corresponding authority option is updated according to the authority result. <figref idref="DRAWINGS">FIG. 11</figref> is a flowchart of a method <b>1100</b> for acquiring configuration information, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 11</figref>, the method <b>1100</b> includes the following steps.

0124In step S<b>1002</b>-<b>1</b>, the terminal device acquires an application name in the received authority result.

0125In some embodiments, step S<b>1002</b>-<b>1</b> may further include acquiring a user ID in the received authority result, and when the user ID in the authority result matches a terminal user ID, acquiring the application name. When the user ID in the authority result does not match the terminal user ID, the operation may be ended.

0126In step S<b>1002</b>-<b>2</b>, the terminal device acquires configuration information of the authority based on the application name. The configuration information may include, for example, type information of the authority and setting information of the corresponding authority. The type of an authority may be an auto-start type, an application type or a ROOT type. The setting of an authority may be sensitive information or description information of the authority. For example, reading SMS is a sensitive authority, and the authority result is “permitting Calendar reading contents of SMS.” When the authority is acquired, according to the setting information, it may prompt the user whether a checked state of “remember my choice” is required. For the sensitive information, for purpose of privacy, generally, unchecking is set by default.

0127In step S<b>1003</b>, the terminal device updates the corresponding authority option based on the configuration information corresponding to the authority.

0128In exemplary embodiments, the authority option is an option for the user to select an authority setting. <figref idref="DRAWINGS">FIG. 12<i>a </i></figref>is a diagram illustrating an interface <b>1200</b><i>a </i>of authority options, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 12<i>a</i></figref>, the authority option includes: a fees related authority and a privacy related authority. For example, in accessing a contact list, the authority option may permit applications to access the contact list, refuse the applications to access the contact list, or may permit some applications to access the contact list but refusing other applications to access the contact list. <figref idref="DRAWINGS">FIG. 12<i>b </i></figref>is a diagram illustrating an interface <b>1200</b><i>b </i>of authority options, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 12<i>b</i></figref>, the authority option includes a multimedia related authority and a settings related authority.

0129In the method <b>1100</b>, by receiving the authority result sent from the server, the configuration information is acquired based on the authority result, and the authority option is updated based on the configuration information. In doing so, the user may avoid manually changing the authority setting, and the corresponding authority can be automatically updated in time according to latest requirements.

0130<figref idref="DRAWINGS">FIG. 13</figref> is a flowchart of a method <b>1300</b> for managing an authority, according to an exemplary embodiment. For example, the method <b>1300</b> may be used in a terminal device. Referring to <figref idref="DRAWINGS">FIG. 13</figref>, the method <b>1300</b> includes the following steps.

0131In step S<b>1301</b>, the terminal device receives an authority result sent from a server.

0132The authority result may include, for example, a user ID, an application name, a defined operation granted by an authority, and/or an authority selection. The user ID may identify the user, and the application name refers to a program or an application that may set an authority, which includes applications used by the user such as Mi-Talk, WeChat and the like, applications that auto-start in a system, and system programs such as Computer, On-line Neighbor and the like. The authority selection includes, for example, permission, rejection, inquiry, and default.

0133In step S<b>1302</b>, the terminal device acquires corresponding configuration based on the authority result. The configuration information may include type information of an authority and setting information of the corresponding authority. The type of an authority may be an auto-start type, an application type, or a ROOT type. The setting of an authority may be sensitive information or description information of the authority.

0134In step S<b>1303</b>, the terminal device queries a type of the authority based on the type information in the configuration information. When the type of the authority is the auto-start type, step S<b>1304</b> is performed. When the type of the authority is the application type, step S<b>1305</b> is performed. When the type of the authority is the ROOT type, step S<b>1306</b> is performed.

0135In step S<b>1304</b>, the terminal device determines whether the authority belongs to a white list. If it does, a dialog box is popped tip to prompt to update description information of a corresponding authority option. The white list refers to a predefined list including names of applications which may cause a window to automatically pop up to inquire of the user when the application is started for the first time.

0136<figref idref="DRAWINGS">FIG. 14</figref> is a diagram illustrating an interface <b>1400</b> of a white list application, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 14</figref>, when the white list includes an application “Bilin”, and Bilin is started for the first time, a dialog box may be popped up to prompt information whether “Bilin” is permitted to auto-start. The description information in <figref idref="DRAWINGS">FIG. 14</figref> shows that: Bilin is requesting for an authority of auto-starting, and if it is prohibited to auto-start, a call from Bilin cannot be received.

0137When the type of the authority is the auto-start type, in an auto-start management authority page, all applications may be present in one page, and controlled by switches. Additionally, after the switch is clicked, the page is not changed immediately until the page is entered next time. <figref idref="DRAWINGS">FIG. 15</figref> is a diagram illustrating an interface <b>1500</b> of auto-start type authority management, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 15</figref>, applications in an auto-start management page include QQ, WeChat, Unknown Alarm Clock, 58.com and Bilin. Among them, the applications that are permitted to auto-start include QQ, WeChat and Unknown Alarm Clock. The applications that are prohibited to auto-start include 58.com and Bilin. Permission or prohibition is controlled by the switch on the right, and when 58.com and Bilin are prohibited to auto-start, the page is not changed immediately until the page is entered next time.

0138After the step S<b>1304</b> is performed, step S<b>1307</b> is performed.

0139In step S<b>1305</b>, the terminal device determines whether the authority belongs to a sensitive authority, and if it does, a dialog box is popped up to inquire of the user whether to update the corresponding authority option. The sensitive authority refers to authority options that involve personal privacy and information security such as a network authority, a SMS authority, and an authority of reading contacts. For instance, in a MIUI system, pop-up inquiry is carried out with respect to sensitive authorities of an application that is installed through a non-Mi channel, or an application that is not operated. <figref idref="DRAWINGS">FIG. 16</figref> is a diagram illustrating an interface <b>1600</b> of sensitive authority management, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 16</figref>, when “Bilin” applies for acquiring an authority of sending SMS to register an account, since the authority of “sending SMS” is the sensitive authority, a widow may be popped up to inquire whether unchecking “remember my choice” should be set by default. Additionally, sensitivity may be graded, and with respect to a general sensitive authority, a window may be popped up to enquiry whether checking “remember my choice” should be set by default, while with respect to a non-sensitive authority, permission may be set by default.

0140When the type of the authority is the application type, in an application management authority page, an application management dimension and an authority management dimension may be presented. In some embodiments, presentation in accordance with the application dimension may be set by default. <figref idref="DRAWINGS">FIG. 17</figref> is a diagram illustrating an interface <b>1700</b> of authority management, according to an exemplary embodiment. In accordance with the application dimension, as shown in <figref idref="DRAWINGS">FIG. 17</figref>, application names are displayed in application management, detailed information of the application management may be presented by clicking right arrows on the right of the applications, which include authorities of the applications.

0141<figref idref="DRAWINGS">FIG. 18</figref> is a diagram illustrating an interface <b>1800</b> of detailed information of an application authority, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 18</figref>, the purpose of using the authority by the application may be indicated below the authority. A single function bar on the right can be clicked and popped up for the user to choose whether to inquire/permit/refuse. For example, in <figref idref="DRAWINGS">FIG. 18</figref>, the authorities of the application Weibo include sending SMS, phone call, call logs, and contacts. The purpose of using the authority of sending SMS by Weibo is indicated below the authority of sending SMS, which is for sharing to Weibo.

0142<figref idref="DRAWINGS">FIG. 19</figref> is a diagram illustrating an interface <b>1900</b> of authority management in an authority dimension, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 19</figref>, when the interface is presented according to the authority dimension, the page presents all authorities and shows applications included by the authorities. For example, in <figref idref="DRAWINGS">FIG. 19</figref>, the authorities presented in the page include sending SMS, phone call, SMS, and contacts. As shown in <figref idref="DRAWINGS">FIG. 19</figref>, “5 Apps” is displayed on the right of the authority of sending SMS, and applications under the authority may be presented by clicking the right arrow on the right of the authority management. <figref idref="DRAWINGS">FIG. 20</figref> is a diagram of an interface <b>2000</b> of applications illustrated under management of an authority dimension, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 20</figref>, the applications under the authority of sending SMS include QQ, WeChat, Unknown Alarm Clock, 58.com and Bilin.

0143Referring back to <figref idref="DRAWINGS">FIG. 13</figref>, after the step S<b>1305</b> is performed, step S<b>1307</b> is performed.

0144In step S<b>1306</b>, the terminal device determines whether the authority has obtained a ROOT authority in ROOT authority management. If the authority has obtained the ROOT authority in the ROOT authority management, a dialog box is popped up to inquire of the user whether to update the corresponding authority option. If the authority does not obtain the ROOT authority in the ROOT authority management, a dialog box is popped up to prompt the user that the authority option is not permitted to be updated.

0145In some embodiments, when the type of the authority is the ROOT type, the ROOT authority may be modified in a ROOT authority management page. For example, only applications that have applied for the ROOT authority are presented in the ROOT authority management page, and it is default that the authority setting is set to be off. <figref idref="DRAWINGS">FIG. 21</figref> is a diagram illustrating an interface <b>2100</b> of applications shown in a ROOT authority management page, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 21</figref>, in the ROOT authority management page, the applications include “360”, Baidu Phone Guardian, DXHome, Tencent Mobile Manger and LBE authority Master. If an off-switch is clicked, the ROOT authority of the application may be turned off immediately, and if an on-switch is clicked, a confirmation pop-up window is presented. Five steps of prompts for applying for the ROOT authority <b>2200</b><i>a</i>-<b>2200</b><i>e </i>are shown in <figref idref="DRAWINGS">FIGS. 22<i>a </i>to 22<i>e</i></figref>. If a third party application applies for the ROOT authority in its application, the user is prompted by a pop-up window that the application is prohibited using the ROOT authority. <figref idref="DRAWINGS">FIG. 23</figref> is a diagram illustrating an interface <b>2300</b> of an application in ROOT authority management, according to an exemplary embodiment. As shown in <figref idref="DRAWINGS">FIG. 23</figref>, when Bilin applies for the ROOT authority within its application, prompt information “Bilin is prohibited using the ROOT authority, if needed, it may be added in the authority management” is displayed.

0146Referring back to <figref idref="DRAWINGS">FIG. 13</figref>, in step S<b>1307</b>, the terminal device updates the authority option according to a selection of the user. For example, in the example in <figref idref="DRAWINGS">FIG. 16</figref>, when “Bilin” applies for acquiring the authority of sending SMS to register an account, there are two selections of “permission” and “rejection” in the interface, and when the user chooses “permission”, according to the selection of the user, the authority option of acquiring the authority of sending SMS for “Bilin” is updated. Additionally, “remember my choice” may also be checked.

0147In the method <b>1300</b>, by receiving the authority result sent from the server, the configuration information is acquired according to the authority result, and according to the type information and the setting information in the configuration information, a corresponding operation for updating the authority is adopted. By prompt of a white list, it may be brought to the user's attention that a particular function cannot be performed normally when a corresponding application does not auto-start. By setting the sensitive authority, the terminal device may alert the user a function of the authority of the application, such that the user makes an informed choice as to whether to grant authority.

0148<figref idref="DRAWINGS">FIG. 24</figref> is a flowchart of a method <b>2400</b> for managing an authority, according to an exemplary embodiment. For example, the method <b>2400</b> may be used in a terminal device. Referring to <figref idref="DRAWINGS">FIG. 24</figref>, the method <b>2400</b> includes the following steps.

0149In step S<b>2401</b>, the terminal device receives an authority result sent from a server.

0150The authority result may include, for example, a user ID, an application name, a defined operation granted by an authority, an authority selection, and an accuracy degree of the authority selection. The user ID may be used for identifying the user, which may be a cell phone number, a user name of a registered user, or other contents that may identify the user such as a Mi-Talk number. The application name refers to a program or an application that may set an authority, which includes applications used by the user such as Mi-Talk, WeChat and the like, applications that auto-start in a system, system programs such as Computer, On-line Neighbor and the like. The authority selection may include permission, rejection, inquiry and default. For example, in SMS (Short Message Service), the defined operation granted by the authority is accessing SMS inbox. The authority can be granted based on statistics of use records by the user. An application may be permitted accessing SMS inbox, rejected accessing SMS inbox, or required to enquiry the user before accessing SMS inbox. If no authority of accessing SMS inbox is set for an application, an authority result of the application of accessing SMS inbox may be obtained by classifying and processing the application based on the authority selection.

0151In step S<b>2402</b>, the terminal device acquires an accuracy degree of the authority selection in the authority result, and determines whether the accuracy degree of the authority selection is greater than a preset accuracy degree. When the accuracy degree of the authority selection is greater than the preset accuracy degree, step S<b>2403</b> is performed. When the accuracy of the authority selection is lower than the preset accuracy, the terminal device does not update the corresponding authority option.

0152The preset accuracy degree may be preset according to accuracy requirements of the system. For example, when the preset accuracy degree is 90%, and the accuracy degree of the authority selection is lower than 90%, the corresponding authority option is not updated.

0153In step S<b>2403</b>, the terminal device updates the corresponding authority option according to the authority result.

0154In one exemplary embodiment, the procedure for updating the corresponding authority option according to the authority result may include steps S<b>1302</b>-S<b>1307</b> described above in connection with <figref idref="DRAWINGS">FIG. 13</figref>.

0155In some embodiments, after the updating the corresponding authority option according to the authority result, the method <b>2400</b> may further include obtaining the authority use data of the user according to the updated authority option; and returning the authority use data of the user to the server, for the server to upload the authority use data of the user to a cloud.

0156In the method <b>2400</b>, by determining whether to update the authority result of the user based on the accuracy degree, an error rate of incorrectly updating the authority may be decreased.

0157<figref idref="DRAWINGS">FIG. 25</figref> is a block diagram of a device <b>2500</b> for managing an authority, according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 25</figref>, the device <b>2500</b> may include an acquiring module <b>251</b>, a processing module <b>252</b> and a sending module <b>253</b>.

0158The acquiring module <b>251</b> is configured to acquire authority use data of a user.

0159The processing module <b>252</b> is configured to process the authority use data to obtain an authority result.

0160The sending module <b>253</b> is configured to send the authority result obtained by the processing to a terminal device, for the terminal device to update a corresponding authority option.

0161<figref idref="DRAWINGS">FIG. 26</figref> is a block diagram of the processing module <b>252</b> (<figref idref="DRAWINGS">FIG. 25</figref>), according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 26</figref>, the processing module <b>252</b> includes a processing sub-module <b>261</b> and an adjustment sub-module <b>262</b>.

0162The processing sub-module <b>261</b> is configured to process the authority use data based on an authority selection, to obtain an authority confidence value and an initial authority selection.

0163The adjustment sub-module <b>262</b> is configured to adjust the initial authority selection based on the authority confidence value and a threshold value, to obtain the authority result.

0164<figref idref="DRAWINGS">FIG. 27</figref> is a block diagram of the processing sub-module <b>261</b> (<figref idref="DRAWINGS">FIG. 26</figref>), according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 27</figref>, the processing sub-module <b>261</b> may include a de-noising unit <b>271</b> and a training unit <b>272</b>.

0165The de-noising unit <b>271</b> is configured to perform de-noising processing on the authority use data.

0166The training unit <b>272</b> is configured to perform a SVM training on the de-noised authority use data based on the authority selection of permission and rejection, to obtain the authority confidence value and the initial authority selection of the corresponding authority option.

0167<figref idref="DRAWINGS">FIG. 28</figref> is a diagram of the processing sub-module <b>261</b> (<figref idref="DRAWINGS">FIG. 26</figref>), according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 28</figref>, the processing sub-module <b>261</b> may include a de-noising unit <b>281</b>, a clustering unit <b>282</b>, and a training unit <b>283</b>.

0168The de-noising unit <b>281</b> is configured to perform de-noising processing on the authority use data.

0169The clustering unit <b>282</b> is configured to perform cluster analysis on the authority use data with respect to the user based on a cluster algorithm, to obtain a cluster type of the user.

0170The training unit <b>283</b> is configured to, based on the cluster type of the user, perform a SVM training on each type of the user respectively based on the authority selection of permission or rejection in the authority option, to obtain the authority confidence value and the initial authority selection corresponding to the authority option.

0171<figref idref="DRAWINGS">FIG. 29</figref> is a block diagram of the processing sub-module <b>261</b> (<figref idref="DRAWINGS">FIG. 26</figref>), according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 29</figref>, the processing sub-module <b>261</b> may include a de-noising unit <b>291</b>, a classification unit <b>292</b>, and a training unit <b>293</b>.

0172The de-noising unit <b>291</b> is configured to perform de-noising processing on the authority use data.

0173The classification unit <b>292</b> is configured to classify the de-noised authority use data into training set data and testing set data based on a classification ratio.

0174The training unit <b>293</b> is configured to perform a SVM training on the training set data respectively based on the authority selection of permission or rejection in the authority option, to obtain the initial authority selection and the authority confidence value corresponding to the authority option.

0175In some embodiments, the device <b>2500</b> (<figref idref="DRAWINGS">FIG. 25</figref>) may further include a determination module configured to determine accuracy of the initial authority selection based on the testing set data, to obtain an accuracy degree of the authority selection.

0176<figref idref="DRAWINGS">FIG. 30</figref> is a block diagram of the adjustment sub-module <b>262</b> (<figref idref="DRAWINGS">FIG. 26</figref>), according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 30</figref>, the adjustment sub-module <b>262</b> may include a comparison unit <b>301</b>, a first adjustment unit <b>302</b>, and a second adjustment unit <b>303</b>.

0177The comparison unit <b>301</b> is configured to compare the authority confidence value corresponding to the authority option with a threshold value.

0178The first adjustment unit <b>302</b> is configured to, when the authority confidence value is lower than the threshold value, adjust the initial authority selection to be an inquiry selection as the authority result.

0179The second adjustment unit <b>303</b> is configured to, when the authority confidence value is greater than or equal to the threshold value, use the initial authority selection as the authority result.

0180<figref idref="DRAWINGS">FIG. 31</figref> is a block diagram of a device <b>3100</b> for managing an authority, according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 31</figref>, the device may include a receiving module <b>311</b>, an acquiring module <b>312</b>, and an updating module <b>313</b>.

0181The receiving module <b>311</b> is configured to receive an authority result sent from a server.

0182The acquiring module <b>312</b> is configured to acquire configuration information of a corresponding authority based on the authority result.

0183The updating module <b>313</b> is configured to update a corresponding authority option based on the configuration information corresponding to the current authority.

0184<figref idref="DRAWINGS">FIG. 32</figref> is a block diagram of the acquiring module <b>312</b> (<figref idref="DRAWINGS">FIG. 31</figref>), according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 32</figref>, the acquiring module <b>312</b> may include a first acquiring unit <b>321</b> and a second acquiring unit <b>322</b>.

0185The first acquiring unit <b>321</b> is configured to acquire an application name in the received authority result.

0186The second acquiring unit <b>322</b> is configured to acquire the configuration information of the authority based on the application name.

0187<figref idref="DRAWINGS">FIG. 33</figref> is a block diagram of the first acquiring unit <b>321</b> (<figref idref="DRAWINGS">FIG. 32</figref>), according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 33</figref>, the first acquiring unit <b>321</b> includes an acquiring sub-unit <b>331</b> and a matching sub-unit <b>332</b>.

0188The acquiring subunit <b>331</b> is configured to acquire a user ID in the received authority result.

0189The matching subunit <b>332</b> is configured to, when the user ID in the authority result matches a terminal user ID, acquire the application name.

0190<figref idref="DRAWINGS">FIG. 34</figref> is a block diagram of the updating module <b>313</b> (<figref idref="DRAWINGS">FIG. 31</figref>), according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 34</figref>, the updating module <b>313</b> may include a query unit <b>341</b>, a determination unit <b>342</b>, and an update unit <b>343</b>.

0191The query unit <b>341</b> is configured to query a type of an authority, based on the type information in the configuration information.

0192The determination unit <b>342</b> is configured to, when the authority is an auto-start type, determine whether the authority belongs to a white list, and if it does, pop up a dialog box to prompt to update description information of the corresponding authority option.

0193The update unit <b>343</b> is configured to update the authority option according to a selection of the user.

0194<figref idref="DRAWINGS">FIG. 35</figref> is a block diagram of the updating module <b>313</b> (<figref idref="DRAWINGS">FIG. 31</figref>), according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 35</figref>, the updating module <b>313</b> may include a query unit <b>351</b>, a determination unit <b>352</b>, and an update unit <b>353</b>.

0195The query unit <b>351</b> is configured to query a type of the authority, based on type information in the configuration information.

0196The determination unit <b>352</b> is configured to, when the authority is an application type, determine whether the authority belongs to a sensitive authority, and if it does, pop up a dialog box to inquire of the user whether to update the corresponding authority option.

0197The update unit <b>353</b> is configured to update the authority option according to a selection of the user.

0198<figref idref="DRAWINGS">FIG. 36</figref> is a block diagram of the updating module <b>313</b> (<figref idref="DRAWINGS">FIG. 31</figref>), according to an exemplary embodiment. Referring to <figref idref="DRAWINGS">FIG. 36</figref>, the update module <b>313</b> may include a query unit <b>361</b> and a determination unit <b>362</b>.

0199The query unit <b>361</b> is configured to query a type of the authority, based on type information in the configuration information.

0200The determination unit <b>362</b> is configured to, when a type of the authority is a ROOT type, determine whether the authority has obtained a ROOT authority in ROOT authority management, and if the current authority has obtained the ROOT authority in the ROOT authority management, pop up a dialog box to inquire of the user whether to update the corresponding authority option. If the current authority does not obtain the ROOT authority in the ROOT authority management, the determination unit <b>362</b> is configured to prompt the user that the authority option is not permitted to be updated.

0201In exemplary embodiments, the device <b>3100</b> (<figref idref="DRAWINGS">FIG. 31</figref>) further includes a determination module configured to acquire an accuracy of the authority selection in the authority result received from the server, determine whether the accuracy of the authority selection is greater than a preset accuracy, and when the accuracy of the authority selection is greater than the preset accuracy, update the corresponding authority option by the update module according to the authority result, and when the accuracy of the authority selection is smaller than the preset accuracy, not update the corresponding authority option.

0202In exemplary embodiments, the device <b>3100</b> may further include a returning module configure to, according to the updated authority option, send the updated authority use data of the user to the server, for the server to upload the authority use data of the user to a cloud.

0203With respect to the devices and the system in the above embodiments, the specific manners for performing operations for respective modules therein have been described in detail in the embodiments with regard to the methods for managing an authority.

0204<figref idref="DRAWINGS">FIG. 37</figref> is a block diagram of a terminal device <b>3700</b> for managing an authority, according to an exemplary embodiment. For example, the terminal device <b>3700</b> may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet, a medical device, exercise equipment, a personal digital assistant and/or the like.

0205Referring to <figref idref="DRAWINGS">FIG. 37</figref>, the terminal device <b>3700</b> may include one or more of the following components: a processing component <b>3702</b>, a memory <b>3704</b>, a power component <b>3706</b>, a multimedia component <b>3708</b>, an audio component <b>3710</b>, an input/output (I/O) interface <b>3712</b>, a sensor component <b>3714</b>, and a communication component <b>3716</b>. The person skilled in the art should appreciate that the structure of the terminal device <b>3700</b> as shown in <figref idref="DRAWINGS">FIG. 37</figref> does not intend to limit the terminal device <b>3700</b>. The terminal device <b>3700</b> may include more or less components or combine some components or other different components.

0206The processing component <b>3702</b> usually controls overall operations of the terminal device <b>3700</b>, such as operations associated with display, telephone calls, data communications, camera operations and recording operations. The processing component <b>3702</b> may include one or more processors <b>3720</b> to execute instructions to perform all or a part of the steps in the above described methods. Moreover, the processing component <b>3702</b> may include one or more modules which facilitate the interaction between the processing component <b>3702</b> and other components. For instance, the processing component <b>3702</b> may include a multimedia module to facilitate the interaction between the multimedia component <b>3708</b> and the processing component <b>3702</b>.

0207The memory <b>3704</b> is configured to store various types of data to support the operation of the terminal device <b>3700</b>. Examples of such data include instructions for any application or method operated on the terminal device <b>3700</b>, contact data, phonebook data, messages, pictures, videos, etc. The memory <b>3704</b> is also configured to store programs and modules. The processing component <b>3702</b> performs various functions and data processing by operating programs and modules stored in the memory <b>3704</b>. The memory <b>3704</b> may be implemented by any type of volatile or non-volatile memory device or combination thereof such as a static random access memory (SRAM), an electrically erasable programmable read-only memory (EEPROM), an erasable programmable read-only memory (EPROM), a programmable read-only memory (PROM), a read-only memory (ROM), a magnetic memory, a flash memory, a magnetic disk or an optical disk.

0208The power component <b>3706</b> is configured to provide power to various components of the terminal device <b>3700</b>. The power component <b>3706</b> may include a power management system, one or more power sources, and other components associated with the generation, management, and distribution of power in the terminal device <b>3700</b>.

0209The multimedia component <b>3708</b> includes a screen for providing an output interface between the terminal device <b>3700</b> and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and/or a touch panel (TP). If the screen includes the touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, slips, and gestures performed on the touch panel. The touch sensors may not only sense a boundary of a touch or slip action, but also sense a period of time and a pressure associated with the touch or slip action. In some embodiments, the multimedia component <b>3708</b> includes a front camera and/or a rear camera. The front camera and/or the rear camera may receive external multimedia data while the terminal device <b>3700</b> is in an operation mode, such as a photographing mode or a video mode. Each of the front camera and the rear camera may be a fixed optical lens system or have focus and optical zoom capability.

0210The audio component <b>3710</b> is configured to output and/or input audio signals. For example, the audio component <b>3710</b> includes a microphone configured to receive an external audio signal when the terminal device <b>3700</b> is in an operation mode, such as a call mode, a recording mode, and/or a voice recognition mode. The received audio signal may be further stored in the memory <b>3704</b> or transmitted via the communication component <b>3716</b>. In some embodiments, the audio component <b>3710</b> further includes a speaker to output audio signals.

0211The I/O interface <b>3712</b> provides an interface between the processing component <b>3702</b> and peripheral interface modules, such as a keyboard, a click wheel, a button, and the like. The button may include, but not limited to: a home button, a volume button, a starting button and a locking button.

0212The sensor component <b>3714</b> includes one or more sensors to provide status assessments of various aspects of the terminal device <b>3700</b>. For instance, the sensor component <b>3714</b> may detect an on/off status of the terminal device <b>3700</b>, relative position of components, e.g., the display and the keyboard, of the device <b>3700</b>, a change in position of the terminal device <b>3700</b> or a component of the terminal device <b>3700</b>, a presence or absence of an user contact with the terminal device <b>3700</b>, an orientation or an acceleration/deceleration of the terminal device <b>3700</b>, and/or a change in temperature of the terminal device <b>3700</b>. The sensor component <b>3714</b> may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor component <b>3714</b> may further include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component <b>3714</b> may further include an accelerometer sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

0213The communication component <b>3716</b> is configured to facilitate communication, in a wire or wireless manner, between the terminal device <b>3700</b> and other devices. The terminal device <b>3700</b> can access a wireless network based on a communication standard, such as WiFi, <b>20</b> or <b>30</b>, or a combination thereof. In one exemplary embodiment, the communication component <b>3716</b> receives a broadcast signal or information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component <b>3716</b> further includes a near field communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on a radio frequency identification (RFID) technology, an infrared data association (IrDA) technology, an ultra-bandwidth (UWB) technology, a Bluetooth (BT) technology, and/or other technologies.

0214In exemplary embodiments, the terminal device <b>3700</b> may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components, for performing the above described methods.

0215In exemplary embodiments, there further provides a non-transitory computer readable storage medium including instructions, such as included in the memory <b>3704</b>, executable by the processor <b>3720</b> in the terminal device <b>3700</b>, for performing the above described methods. For example, the non-transitory computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disc, an optical data storage device and the like.

0216<figref idref="DRAWINGS">FIG. 38</figref> is a block diagram illustrating a device <b>3800</b> for managing an authority, according to an exemplary embodiment. For example, the device <b>3800</b> may be provided as a server to perform the above described methods for managing an authority. Referring to <figref idref="DRAWINGS">FIG. 38</figref>, the device <b>3800</b> includes a processing component <b>3822</b> that further includes one or more processors, and memory resources represented by a memory <b>3832</b> for storing instructions executable by the processing component <b>3822</b>, such as application programs. The application programs stored in the memory <b>3832</b> may include one or more modules each corresponding to a set of instructions.

0217The device <b>3800</b> may further include one power component <b>3826</b> configured to perform power management of the device <b>3800</b>, one wired or wireless network interface <b>3850</b> configured to connect the device <b>3800</b> to a network, and one input/output (I/O) interface <b>3858</b>. The device <b>3800</b> may operate based on an operating system stored in the memory <b>3832</b>, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

0218It should be understood by those skilled in the art that the above described methods, devices, and modules/units can each be implemented through hardware, or software, or a combination of hardware and software. One of ordinary skill in the art will also understand that multiple ones of the above described modules/units may be combined as one module/unit, and each of the above described modules/units may be further divided into a plurality of sub-modules/sub-units.

0219Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed here. This application is intended to cover any variations, uses, or adaptations of the invention following the general principles thereof and including such departures from the present disclosure as come within known or customary practice in the art. The description and embodiments are only exemplary, and a true scope and spirit of the invention being indicated by the following claims.

0220It should be understood that the present disclosure is not limited to the exact structures that are described above and shown in the accompanying drawings, and may be modified and changed without departing from the range of the present disclosure. The scope of the invention is only limited by the appended claims.