Authority management method, intelligent terminal and storage medium

Abstract

The invention provides an authority management method, an intelligent terminal and a readable storage medium, and the authority management method is applied to the intelligent terminal and comprises the following steps: determining a target account for exchanging user authority; and configuring or updating the target account according to the first authority information corresponding to the current account or the historical account, so that the target account has the management authority corresponding to the first authority information. According to the technical scheme, when the management authority of the current account number is transferred, the account number and the password of the administrator do not need to be transferred, and the operation is simple.

Description

Technical Field

[0001] The present application relates to the technical field of account management, and in particular to a permission management method, a smart terminal and a storage medium. Background Art

[0002] Currently, various types of smart terminals integrate more and more functions. In order to improve the utilization rate of smart terminals or the privacy of device data usage, multiple user accounts can be configured on the smart terminals.

[0003] In the process of conceiving and implementing this application, the inventors found that there are at least the following problems: among the multiple user accounts configured on the smart terminal, if the current account wants to transfer management permissions, it is usually necessary to delete the corresponding privacy data under the current account and transfer the account number and password of the current account to other users, so that other users can log in according to the account number and password and exercise the management permissions corresponding to the current account. The operation is cumbersome.

[0004] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Summary of the invention

[0005] In response to the above technical problems, the present application provides a permission management method, a smart terminal and a readable storage medium, so that users do not need to transfer their account and password when transferring management permissions, and the operation is simple and convenient.

[0006] To solve the above technical problems, the present application provides a rights management method, including:

[0007] S10: Determine the target account for exchanging user permissions;

[0008] S20: configuring or updating the target account according to the first permission information corresponding to the current account or the historical account, so that the target account has the management permission corresponding to the first permission information.

[0009] Optionally, step S10 includes at least one of the following:

[0010] Responding to the authority transfer instruction, determining or generating the target account according to the authority transfer instruction;

[0011] In response to the permission request operation, determining or generating the target account according to the permission request operation;

[0012] When the current time matches the preset time, the target account is determined or generated according to the current time.

[0013] Optionally, the method further comprises:

[0014] The number of times the permission transfer instruction or the permission request operation is received within a preset time period is obtained, and when the number is less than or equal to the preset number, the permission transfer instruction or the permission request operation is responded to to determine the target account.

[0015] Optionally, step S20 includes:

[0016] Obtaining first permission information corresponding to the current account and / or the historical account, and deleting the current account and / or the historical account;

[0017] The second permission information corresponding to the target account is configured as the first permission information.

[0018] Optionally, step S20 includes:

[0019] Acquire target information of the current account and / or the historical account, and determine the first authority information according to the target information;

[0020] The target account is configured or updated according to the first permission information so that the target account has the management permission corresponding to the first permission information.

[0021] Optionally, the step of obtaining target information of the current account and / or the historical account includes:

[0022] Display or output account information corresponding to the current account and / or historical account;

[0023] In response to a selection instruction for the account information, target information is determined or generated according to the selection instruction.

[0024] Optionally, before step S20, the method further includes:

[0025] Storing second permission information corresponding to the target account;

[0026] After step S20, the method further includes:

[0027] The first permission information of the current account or the historical account is configured or updated according to the second permission information, so that the current account or the historical account has the management permission corresponding to the second permission information.

[0028] Optionally, before step S20, the method further includes:

[0029] Saving the second permission information corresponding to the target account;

[0030] After step S20, the method further includes:

[0031] When the duration for which the target account has the user authority corresponding to the first authority information is greater than or equal to a preset duration, the second authority information corresponding to the target account is updated according to the saved second authority information.

[0032] The present application also provides an intelligent terminal, comprising: a memory and a processor, wherein a rights management program is stored in the memory, and when the rights management program is executed by the processor, the steps of the above method are implemented.

[0033] The present application also provides a readable storage medium, wherein the readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0034] As described above, the permission management method of the present application is applied to a smart terminal, and includes the steps of: determining a target account for exchanging user permissions; configuring or updating the target account according to the first permission information corresponding to the current account or the historical account, so that the target account has the management permission corresponding to the first permission information. Through the above technical solution, it can be achieved that when the management permission is transferred, there is no need to transfer the account and password, which solves the problem of cumbersome operations when transferring the management permission, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor.

[0036] Figure 1 A schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application;

[0037] Figure 2 A communication network system architecture diagram provided for an embodiment of the present application;

[0038] Figure 3 is a flowchart of a rights management method according to the first embodiment;

[0039] Figure 4 This is a schematic diagram of the composition of user accounts in the first embodiment of the permission management method of this application;

[0040] Figure 5 is a flowchart of a method for managing rights according to a second embodiment;

[0041] Figure 6This is a schematic diagram of the transfer of management rights in the first embodiment of the rights management method of the present application;

[0042] Figure 7 It is a flowchart of the permission management method according to the second embodiment.

[0043] The realization of the purpose, functional features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. The above-mentioned drawings have shown clear embodiments of this application, which will be described in more detail later. These drawings and textual descriptions are not intended to limit the scope of the concept of this application in any way, but to illustrate the concept of this application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

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

[0045] It should be noted that, in this article, the terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element. Optionally, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context in the specific embodiment.

[0046] It should be understood that, although the terms first, second, third, etc. may be used to describe various information in this article, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this article, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determination". Furthermore, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising" and "including" indicate that there are the described features, steps, operations, elements, components, projects, kinds, and / or groups, but do not exclude the existence, occurrence or addition of one or more other features, steps, operations, elements, components, projects, kinds, and / or groups. The terms "or", "and / or", "including at least one of the following" etc. used in this application can be interpreted as inclusive, or mean any one or any combination. For example, “comprising at least one of the following: A, B, C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”, and for another example, “A, B or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”. An exception to this definition will only occur when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0047] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are displayed in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and it can be performed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0048] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.

[0049] It should be noted that in this article, step codes such as S10 and S20 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the sequence. When implementing the step, those skilled in the art may execute S20 first and then S10, etc., but these should all be within the scope of protection of this application.

[0050] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0051] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.

[0052] The smart terminal may be implemented in various forms. For example, the smart terminal described in this application may include mobile terminals such as mobile phones, tablet computers, laptop computers, PDAs, portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminals such as digital TVs and desktop computers.

[0053] The following description will be made by taking a mobile terminal as an example, and those skilled in the art will understand that, in addition to components specifically used for mobile purposes, the construction according to the embodiments of the present application can also be applied to fixed-type terminals.

[0054] See also Figure 1 , which is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application, the mobile terminal 100 may include: RF (Radio Frequency, radio frequency) unit 101, WiFi module 102, audio output unit 103, A / V (audio / video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111 and other components. Those skilled in the art can understand that Figure 1 The structure of the mobile terminal shown in the figure does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0055] Combine the following Figure 1 The following is a detailed introduction to the various components of the mobile terminal:

[0056] The radio frequency unit 101 can be used for receiving and sending signals during information transmission or communication. Specifically, after receiving the downlink information of the base station, it is sent to the processor 110 for processing; in addition, the uplink data is sent to the base station. Generally, the radio frequency unit 101 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc. In addition, the radio frequency unit 101 can also communicate with the network and other devices through wireless communication. The above-mentioned wireless communications can use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution) and 5G, etc.

[0057] WiFi is a short-range wireless transmission technology. Mobile terminals can help users send and receive emails, browse web pages, and access streaming media through WiFi module 102. It provides users with wireless broadband Internet access. Figure 1 The WiFi module 102 is shown, but it is understandable that it is not an essential component of the mobile terminal and can be omitted as needed without changing the essence of the invention.

[0058] The audio output unit 103 can convert the audio data received by the RF unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output it as sound when the mobile terminal 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, etc. Moreover, the audio output unit 103 can also provide audio output related to a specific function performed by the mobile terminal 100 (for example, a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.

[0059] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processor (GPU) 1041 and a microphone 1042, and the graphics processor 1041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The processed image frame can be displayed on the display unit 106. The image frame processed by the graphics processor 1041 can be stored in the memory 109 (or other storage medium) or sent via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) via the microphone 1042 in a telephone call mode, a recording mode, a voice recognition mode, and other operating modes, and can process such sound into audio data. The processed audio (voice) data can be converted into a format output that can be sent to a mobile communication base station via the radio frequency unit 101 in the case of a telephone call mode. The microphone 1042 can implement various types of noise elimination (or suppression) algorithms to eliminate (or suppress) noise or interference generated in the process of receiving and sending audio signals.

[0060] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 1061 and / or the backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured on the mobile phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be repeated here.

[0061] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0062] The user input unit 107 can be used to receive input digital or character information, and to generate key signal input related to the user settings and function control of the mobile terminal. Optionally, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 1071 or near the touch panel 1071 using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a pre-set program. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Optionally, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the touch point coordinates, and then sends it to the processor 110, and can receive and execute the command sent by the processor 110. In addition, the touch panel 1071 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may further include other input devices 1072. Optionally, the other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, a function key (such as a volume control key, a switch key, etc.), a trackball, a mouse, a joystick, etc., which are not specifically limited here.

[0063] Optionally, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Then, the processor 110 provides corresponding visual output on the display panel 1061 according to the type of touch event. Figure 1 In the figure, the touch panel 1071 and the display panel 1061 are used as two independent components to implement the input and output functions of the mobile terminal. However, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to implement the input and output functions of the mobile terminal, which is not limited here.

[0064] The interface unit 108 serves as an interface through which at least one external device can be connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.

[0065] The memory 109 can be used to store software programs and various data. The memory 109 can mainly include a program storage area and a data storage area. Optionally, the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 109 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0066] The processor 110 is the control center of the mobile terminal. It uses various interfaces and lines to connect various parts of the entire mobile terminal. It executes various functions of the mobile terminal and processes data by running or executing software programs and / or modules stored in the memory 109, and calling data stored in the memory 109, so as to monitor the mobile terminal as a whole. The processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor. Optionally, the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 110.

[0067] The mobile terminal 100 may also include a power supply 111 (such as a battery) for supplying power to various components. Preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system.

[0068] although Figure 1 Not shown, the mobile terminal 100 may further include a Bluetooth module, etc., which will not be described in detail here.

[0069] In order to facilitate understanding of the embodiments of the present application, the communication network system on which the mobile terminal of the present application is based is described below.

[0070] See also Figure 2 , Figure 2 A communication network system architecture diagram is provided for an embodiment of the present application, wherein the communication network system is an LTE system of universal mobile communication technology, and the LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203 and an operator's IP service 204, which are connected in sequence for communication.

[0071] Optionally, UE201 may be the above-mentioned terminal 100, which will not be described in detail here.

[0072] E-UTRAN 202 includes eNodeB 2021 and other eNodeBs 2022 , etc. Optionally, eNodeB 2021 may be connected to other eNodeBs 2022 via a backhaul (eg, an X2 interface), and eNodeB 2021 is connected to EPC 203 , and eNodeB 2021 may provide UE 201 with access to EPC 203 .

[0073] EPC203 may include MME (Mobility Management Entity) 2031, HSS (Home Subscriber Server) 2032, other MMEs 2033, SGW (Serving Gate Way) 2034, PGW (PDN Gate Way) 2035 and PCRF (Policy and Charging Rules Function) 2036, etc. Optionally, MME 2031 is a control node that processes signaling between UE 201 and EPC 203, and provides bearer and connection management. HSS 2032 is used to provide some registers to manage functions such as home location register (not shown in the figure), and store some user-specific information such as service features and data rates. All user data can be sent through SGW2034, PGW2035 can provide IP address allocation and other functions for UE 201, PCRF2036 is the policy and charging control policy decision point for service data flow and IP bearer resources, which selects and provides available policy and charging control decisions for the policy and charging execution function unit (not shown in the figure).

[0074] The IP service 204 may include the Internet, an intranet, an IMS (IP Multimedia Subsystem) or other IP services.

[0075] Although the above introduction takes the LTE system as an example, those skilled in the art should know that the present application is not only applicable to the LTE system, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA and future new network systems (such as 5G), etc., without limitation here.

[0076] Based on the above-mentioned mobile terminal hardware structure and communication network system, various embodiments of the present application are proposed.

[0077] First embodiment

[0078] Reference Figure 3 , Figure 3 FIG. 1 is a flow chart of a method for managing rights according to a first embodiment, wherein the method comprises the following steps:

[0079] S10: Determine the target account for exchanging user permissions;

[0080] S20: According to the first permission information corresponding to the current account or the historical account, the target account is configured or updated so that the target account has the management permission corresponding to the first permission information.

[0081] In order to improve the utilization rate of the smart terminal or the privacy of the device data usage, multiple user accounts can be configured on the smart terminal as needed. Optionally, the user accounts include but are not limited to administrator accounts and ordinary personnel accounts. It should be noted that different user accounts can have different user permissions or the same user permissions.

[0082] Optionally, the administrator account is equipped with management authority, which has higher access authority and control authority. It should be noted that the highest access authority indicates that it has all access operations, and the highest control authority indicates that it has all control operations. Optionally, management authority can be used to add, delete, check, and modify accounts, and can also be used to control the installation and uninstallation of applications under each user account. The management authority or ordinary personnel authority corresponding to ordinary personnel accounts does not have all access operations and / or all control operations. The management authority or ordinary personnel authority corresponding to ordinary personnel accounts can be set by the administrator so that the management authority or ordinary personnel authority corresponding to ordinary personnel accounts has some access operations and / or some control operations. For example, ordinary personnel authority does not have the operations of adding, deleting, checking, and modifying accounts, but has the operations of installing and uninstalling applications.

[0083] Optionally, according to different application scenarios or functional divisions of different personnel, ordinary personnel accounts can be divided into staff accounts and guest accounts, etc. as needed, and this embodiment does not limit this.

[0084] Optionally, the number of the administrator account and / or the general staff account may be one or at least two, and the specific number may be set according to the requirements.

[0085] In this embodiment, the current account can be an administrator account or a common account, and there is no limitation on this. Optionally, the target account can be an administrator account or a common account. The historical account can be a user account that has been registered, set up, or used by the smart terminal.

[0086] Optionally, the transfer of management authority of a smart terminal can be applied when the smart terminal is a shared device in a family, such as a smart terminal used by parents and children. The parents hold management authority and the children have ordinary personnel authority. The parents can manage and control the use of the smart terminal by the children. When the use of the smart terminal by the children no longer requires management, the parents can transfer the management authority of the smart terminal to the children to make it easier for the children to operate the smart terminal. It can also be applied when the smart terminal is a public machine for an enterprise and the person in charge of the enterprise holds management authority. When the person in charge of the enterprise is replaced, the management authority of the smart terminal can be transferred to other staff members of the enterprise so that the other staff members hold management authority. This embodiment does not limit this.

[0087] As an optional implementation, step S10 may include at least one of the following:

[0088] Responding to the authority transfer instruction, determining or generating the target account according to the authority transfer instruction;

[0089] In response to the permission request operation, determining or generating the target account according to the permission request operation;

[0090] When the current time matches the preset time, the target account is determined or generated according to the current time.

[0091] Optionally, step S10 may include: responding to an authority transfer instruction, determining or generating the target account according to the authority transfer instruction; responding to the authority transfer instruction, determining or generating the target account with which the user authority is exchanged based on the user account selected by the authority transfer instruction.

[0092] In actual application, the user holding the current account can directly actively select the user account with exchange management authority.

[0093] Based on the user account selected by the authority transfer instruction, the target account for exchanging user authorities is determined or generated by outputting a management authority transfer page. Optionally, the management authority transfer page includes all user accounts of the smart terminal to be selected. By receiving the authority transfer instruction on the management authority transfer page, the user account selected by the authority transfer instruction is determined or generated as the target account for exchanging user authorities.

[0094] Optionally, when receiving a permission transfer instruction on the management permission transfer page, the permission transfer instruction may be triggered based on the touch operation corresponding to the permission transfer instruction detected on the management permission transfer page; it may also be triggered by selecting a virtual button corresponding to a user account on the management permission transfer page, such as by a click operation; it may also be triggered by identifying a matching voice control instruction when the management permission transfer page is displayed, so as to be triggered according to the voice control instruction. Optionally, a voice control instruction such as "select user 1 as the target account" or "select user 1" is identified to determine the account corresponding to user 1 as the target account, which is not limited in this embodiment.

[0095] Optionally, step S10 may include: responding to a permission request operation, determining or generating the target account based on the permission request operation; responding to the permission request operation, and determining or generating a target account for exchanging user permissions based on the user account corresponding to the response to the permission request operation.

[0096] In actual application, a user holding a common user account may passively initiate an application for management authority, so that the user account initiating the application for management authority is determined as a target account for exchanging user authority.

[0097] Optionally, the permission request operation can be triggered based on detecting a touch operation corresponding to the permission request operation, or by selecting a virtual button corresponding to a user account in the management permission transfer page, such as by clicking on it, or by recognizing a matching voice control instruction to trigger it according to the voice control instruction. For example, a voice control instruction such as "apply for management permission" or "management permission" is recognized to determine that the account corresponding to the initiating permission request operation is the target account. This embodiment does not limit this.

[0098] Optionally, step S10 may include determining or generating the target account according to the current time when the current time matches the preset time.

[0099] In the actual application process, different users can be given different management permissions at different time points or different time periods as needed. Optionally, it can be pre-set that in the first time period of each day, such as 9:00-12:00, the target account of the first user is configured or updated according to the first permission information corresponding to the administrator account, so that the target account has the management permissions corresponding to the administrator account from 9:00 to 12:00; in the second time period of each day, such as 12:00-16:00, the target account of the second user is configured or updated according to the first permission information corresponding to the administrator account, so that the target account has the management permissions corresponding to the administrator account from 12:00 to 16:00. For another example, it can be pre-set at 13:00-15:00 on January 4, 2023, and the target account of the third user is configured or updated according to the first permission information corresponding to the first user, so that the target account has the management permissions corresponding to the first user from 13:00 to 15:00 on January 4, 2023.

[0100] When it is detected that the current time matches the preset time, it indicates that the time point or time period for exchanging user permissions has been reached, and based on the mapping relationship between the user account to be exchanged and the target account for exchanging user permissions at different time points or different time periods preset in advance, the target account is determined or generated according to the current time. That is, the target account corresponding to the current time is obtained, and then the target account is configured or updated according to the first permission information corresponding to the user account to be exchanged, so that the target account has the management permission corresponding to the first permission information.

[0101] Optionally, the user account to be exchanged includes a current account and / or a historical account.

[0102] In actual application, the user account configured by the smart terminal can be formed by setting the corresponding relationship formed by the user authority, user identity, user identification and the corresponding user information storage path. For example, reference can be made to Figure 4 , Figure 4 This is a schematic diagram of the composition of user accounts in the first embodiment of the permission management method of the present application. Optionally, the multiple user accounts of the smart terminal can be configured as required, and the user identities corresponding to each of them are the owner (also known as the administrator), sub-users, and visitors. Among them, the user authority corresponding to the owner is the management authority, the user identification corresponding to the owner is user 1, and the information storage path corresponding to the owner is path 1. The privacy data corresponding to the owner can be stored in the storage space determined by path 1. Optionally, user authority, user identification, and user information storage path are set for each sub-user and visitor, which can be specifically referred to in Figure 4 , I will not go into details here.

[0103] Optionally, different access rights and control rights may be set corresponding to different user rights. Exemplarily, the correspondence between different user rights and access rights and control rights may be pre-set, such as the mapping relationship between user rights, access rights and control rights set by a mapping table. Optionally, the access rights correspond to limited access operations, and the control rights correspond to limited control operations. When performing access operations and / or control operations, based on the mapping relationship between user rights, access rights and control rights, the user account of the user corresponding to the access operation and / or control operation may be first determined, and the user rights corresponding to the user account may be clarified. When the access operation belongs to the operation corresponding to the access right corresponding to the user right, the access operation may be performed; when the control operation belongs to the operation corresponding to the control right corresponding to the user right, the control operation may be performed. Optionally, when the access operation does not belong to the operation corresponding to the access right corresponding to the user right, the access operation may be refused to be performed; when the control operation does not belong to the operation corresponding to the control right corresponding to the user right, the control operation may be refused to be performed.

[0104] Optionally, the user permission information corresponding to the administrator account includes management permission, access permission corresponding to the management permission, and control permission corresponding to the management permission. The user permission information corresponding to the general personnel account includes general user permission (such as sub-user permission, customer permission), access permission corresponding to the general user permission setting, and control permission corresponding to the general user permission setting.

[0105] In this embodiment, when the current account is an administrator account, the first permission information corresponding to the current account is the user permission information corresponding to the administrator account. When the current account is an ordinary personnel account, the first permission information corresponding to the current account is the user permission information corresponding to the ordinary personnel account.

[0106] According to the first permission information corresponding to the current account or the historical account, the target account is configured or updated, that is, the second permission information corresponding to the target account is updated according to the first permission information, so that the target account has the management permission corresponding to the first permission information.

[0107] Optionally, updating the second permission information corresponding to the target account according to the first permission information may be directly configuring or updating the target account according to all permissions corresponding to the first permission information, so that the target account has all permissions corresponding to the first permission information.

[0108] Optionally, updating the second permission information corresponding to the target account according to the first permission information may be configuring or updating the target account according to the partial permission corresponding to the first permission information so that the target account has the partial permission corresponding to the first permission information.

[0109] Optionally, the determination of all permissions or partial permissions corresponding to the first permission information can be determined based on the option selected in the permission setting list containing all permissions corresponding to the first permission information. Exemplarily, the options corresponding to the permission setting list include select all, permission 1, permission 2, permission 3... permission n, where n is a positive integer. When the option selects select all, it indicates that all permissions corresponding to the first permission information are determined. When the option selects non-select all, such as selecting permission 1, permission 3, and permission 7, it indicates that partial permissions corresponding to the first permission information are determined.

[0110] Optionally, all permissions or part of the permissions corresponding to the first permission information can be determined based on the target account. A mapping relationship between the target account and the first permission information corresponding to the user account to be exchanged can be set in advance. Based on the mapping relationship, it is determined whether the user permission information configured or updated for the target account is all permissions corresponding to the first permission information, or part of the permissions corresponding to the first user permission.

[0111] Optionally, when the current account is an administrator account and the target account is an ordinary personnel account, the target account is configured or updated according to the first permission information corresponding to the current account, that is, the second user permission information corresponding to the ordinary personnel account is updated according to the user permission information corresponding to the administrator account. The ordinary user permissions in the second user permission information can be directly updated to management permissions, the access permissions corresponding to the ordinary user permission settings are updated to the access permissions corresponding to the management permissions, and the control permissions corresponding to the ordinary user permission settings are updated to the control permissions corresponding to the management permissions; the ordinary user permissions in the second user permission information can also be updated to management permissions, and then based on the mapping relationship between user permissions, access permissions and control permissions set in the mapping table, the access permissions and control permissions corresponding to the management permissions are obtained, the access permissions of the ordinary user permission settings are updated according to the access permissions, and the control permissions of the ordinary user permission settings are updated according to the control permissions. There is no limitation on this.

[0112] Optionally, when the current account is an ordinary personnel account corresponding to the first user, and the target account is an ordinary personnel account corresponding to the second user, the target account is configured or updated according to the first permission information corresponding to the current account, that is, the second user permission information corresponding to the second user is updated according to the first permission information corresponding to the first user, and the ordinary user permissions in the second user permission information can be updated to all permissions or part of permissions corresponding to the first permission information, such as updating the access permission of the ordinary user permission setting corresponding to the first user to the access permission corresponding to the second user. Optionally, the control permission of the ordinary user permission setting corresponding to the first user is updated to the control permission corresponding to the second user; or after the ordinary user permissions in the second user permission information are updated to all permissions or part of permissions corresponding to the first permission information, based on the mapping relationship between the user permissions, access permissions and control permissions corresponding to the first user in the mapping table, the access permissions and control permissions corresponding to the first user are obtained, the access permissions of the ordinary user permission settings corresponding to the second user are updated according to the access permissions, and the control permissions of the ordinary user permission settings corresponding to the second user are updated according to the control permissions, and there is no limitation on this.

[0113] As an optional implementation, step S20 includes: obtaining the first permission information corresponding to the current account and / or the historical account, and deleting the current account and / or the historical account; configuring the second permission information corresponding to the target account as the first permission information.

[0114] In actual application, when the holder of the current account of the smart terminal no longer holds management authority or ordinary user authority, and / or the holder of the historical account of the smart terminal no longer holds management authority or ordinary user authority, such as the holder changes the smart terminal job, or the holder resigns, etc., the holder no longer logs in to the current account or historical account, and needs to transfer the corresponding management authority or ordinary user authority to other users, the first authority information corresponding to the current account or historical account is obtained, and the current account or historical account is deleted, so that when the second authority information corresponding to the target account is configured as the first authority information, the target account is configured as the current account so that the target account has management authority, ensuring that there is only one current account, which is convenient for administrator operation.

[0115] Optionally, when the holder of a historical account on a smart terminal no longer has management authority or ordinary user authority, such as when the holder changes jobs on the smart terminal or resigns, the holder no longer logs in to the current account or historical account and needs to transfer the corresponding management authority or ordinary user authority to other users, the first authority information corresponding to the historical account is obtained, and the historical account is deleted. When the second authority information corresponding to the target account is configured as the first authority information, that is, when the target account is configured to have management authority or ordinary user authority corresponding to the historical account, it is ensured that there is only one current account, which is convenient for administrator operations.

[0116] Optionally, the second permission information corresponding to the target account is configured as the first permission information, that is, the second user permission information is updated according to the first permission information.

[0117] As an optional implementation, step S20 includes: obtaining target information of the current account and / or the historical account, and determining the first authority information based on the target information; configuring or updating the target account based on the first authority information so that the target account has management authority corresponding to the first authority information.

[0118] In actual application, the first user authority is determined based on the target information of the current account and / or the historical account. The first user authority can be all authorities corresponding to the current account and / or the historical account, and then the second authority information corresponding to the target account is updated according to the first authority information so that the target account has all authorities corresponding to the first authority information; it can also be partial authorities corresponding to the current account and / or the historical account, and then the second authority information corresponding to the target account is updated according to the first authority information so that the target account has partial authorities corresponding to the first permission information.

[0119] Optionally, determination of all permissions or part of the permissions corresponding to the first permission information may be determined based on target information of the current account and / or the historical account.

[0120] Optionally, the step of obtaining target information of the current account and / or the historical account includes: displaying or outputting account information corresponding to the current account and / or the historical account; responding to a selection instruction for the account information, and determining or generating target information according to the selection instruction.

[0121] Optionally, the account information includes but is not limited to the account name, the permission information corresponding to the account, and the level information corresponding to the account. Optionally, the permission information corresponding to different accounts may be different. Optionally, the permission information corresponding to the administrator account has all access operations and all control operations, and the permission information corresponding to the ordinary personnel account may be only the permission of all or part of the access operations, or only the permission of all or part of the control operations, or the permission of part of the access operations and all the control operations, without limitation.

[0122] Optionally, different level information can be set for different accounts. Optionally, the level information set for the administrator account can be the first level, the level information set for the staff account can be the second level, and the level information set for the visitor account can be the third level. The higher the level of the account, the higher the access and control operation permissions the account has, such as the first level is higher than the second level, and the second level is higher than the third level.

[0123] Optionally, for the selection instruction of account information, the account name can be directly selected, and the target information can be generated according to the user authority information of the account corresponding to the account name; the level information corresponding to the account can also be directly selected to obtain the user authority information corresponding to the level information, and the target information can be determined or generated according to the user authority information; it can also be directly selected The permission information corresponding to the account, such as the option selected based on the permission setting list of all permissions corresponding to the account limit information. Optionally, the options corresponding to the permission setting list include select all, permission 1, permission 2, permission 3... permission n, where n is a positive integer. When the option selects select all, it indicates that all permissions corresponding to the permission information are determined. When the option selects non-select all, such as selecting permission 1, permission 3, and permission 7, it indicates that some permissions corresponding to the first permission information are determined, and then the target information is determined or generated according to the permission information corresponding to the selected account.

[0124] Optionally, the second permission information corresponding to the target account is configured as the first permission information so that both the current account and the target account have management authority, so that the administrator can authorize other ordinary users with management authority to exercise access rights and control rights corresponding to the management authority.

[0125] Optionally, to facilitate administrator operation and management, before S20, the method may further include: saving the second permission information corresponding to the target account; after S20, the method may further include: when the duration of the target account being configured as the current account is greater than or equal to the preset duration, updating the second permission information corresponding to the target account according to the saved second user permission information, so that the user permission of the target account is restored to the ordinary user permission before being configured as the current account. The preset duration is used to limit the management duration of the target account's management permission, so as to achieve a time-limited transfer of the management permission of the current account, and ensure that there is only one current account.

[0126] Optionally, the target account before the update and the target account after the update differ only in user rights. It is understandable that the user rights of the target account before the update are ordinary user rights, while the user rights of the target account after the update are management rights. Since the target account before the update and the target account after the update differ only in user rights, when the management rights of the current account are transferred, the user rights information of the target account is simply configured as the user rights information of the administrator, so that the updated target account has management rights, and there is no need to transfer the administrator's account and password, thereby avoiding the risk of privacy leakage when transferring the administrator's account and password, and there is no need to delete the corresponding privacy data under the current account, which is simple to operate.

[0127] In the technical solution disclosed in this embodiment, a target account for exchanging user permissions is determined, and the target account is configured or updated according to the first permission information corresponding to the current account or the historical account, and the user permission information of the target account is updated to the user permission information corresponding to the current account or the historical account, so that the target account has the management permission corresponding to the first permission information. When the management permission of the current account is transferred, there is no need to transfer the administrator's account and password, and the operation is simple.

[0128] Second embodiment

[0129] Based on the first embodiment, the rights management method of this application proposes a second embodiment, please refer to Figure 5 , Figure 5 It is a flow chart of the permission management method according to the second embodiment. Before S20, it also includes: step S30, storing the second permission information corresponding to the target account; after step S20, it also includes: step S40, configuring or updating the first permission information corresponding to the current account or the historical account according to the second permission information, so that the current account or the historical account has the management permission corresponding to the second permission information.

[0130] Before updating the user authority corresponding to the target account, save the second authority information corresponding to the target account to record the second authority information corresponding to the target account before the update, and configure or update the first authority information corresponding to the current account or the historical account according to the second authority information corresponding to the target account, that is, configure the first authority information corresponding to the current account or the historical account as the saved second user authority information, so as to configure the current account or the historical account to have the management authority corresponding to the target account before the update, so as to achieve the purpose of exchanging user authorities between the target account and the current account or between the target account and the historical account.

[0131] Optionally, refer to Figure 6 , Figure 6 The schematic diagram of the transfer of management rights in the first embodiment of the rights management method of the present application is shown in FIG. Optionally, the user rights between the current account and the target account or between the target account and the historical account are exchanged, which only involves the change of user rights and user identities. For example, before the user rights are exchanged, user 1 is the machine owner (administrator) with management rights, and user 2 is a sub-user with sub-user rights. When user 2 is determined to be the target account, and user 1 is a historical account or the current account, after user 2 and user 1 exchange user rights, user 1 is a sub-user with sub-user rights, and user 2 is the machine owner (administrator) with management rights.

[0132] Optionally, since the user rights exchange between the current account and the target account or between the target account and the historical account differ only in terms of user rights and user identities, when implementing the transfer of management rights of the current account, the user rights information of the target account is simply configured as the user rights information corresponding to the current account or the historical account, so that the updated target account has the same management rights as the current account or the historical account. The user rights information of the current account or the historical account is configured as the user rights information of the target account before the update, so that the updated current account or the historical account has the user rights corresponding to the target account before the update, and does not involve the transfer of the account number and password, avoiding the risk of privacy leakage when the account number and password are transferred, with higher security, and no need to delete the privacy data corresponding to the account, and the operation is simple.

[0133] In the technical solution disclosed in this embodiment, the first permission information corresponding to the current account or the historical account is configured or updated through the second permission information corresponding to the target account before the update, so as to configure the current account or the historical account to have the management authority corresponding to the target account before the update, thereby achieving the purpose of exchanging user permissions between the target account and the current account or between the target account and the historical account.

[0134] Third embodiment

[0135] Based on the first embodiment or the second embodiment, the permission management method of the present application proposes a second embodiment, please refer to Figure 7 , Figure 7 It is a flow chart of the permission management method according to the second embodiment, and before S20, it also includes: S50, saving the second permission information corresponding to the target account; after S20, it also includes: S60, when the duration of the target account having the user permission corresponding to the first permission information is greater than or equal to the preset duration, updating the second permission information corresponding to the target account according to the saved second user permission information.

[0136] Optionally, before updating the user rights corresponding to the target account, the second permission information corresponding to the target account is saved to record the second permission information corresponding to the target account before the update. In the actual application process, in order to achieve the transfer of management rights or user rights, it is not necessary to transfer the account number and password of the user account, so as to avoid the risk of privacy leakage when the account number and password are transferred, and to enable other users to have management rights. After updating the second permission information corresponding to the target account according to the first permission information corresponding to the current account, the user right information of the target account is updated to the user right information corresponding to the current account or the historical account, so that the target account has the management rights corresponding to the current account or the historical account, and the duration of the target account configuration as the current account can be obtained. When the duration is greater than or equal to the preset duration, it indicates that the management duration of the management rights of the target account has been used up. According to the saved second user right information, the second permission information corresponding to the target account is updated so that the user rights of the target account are restored to the user rights before being configured to have the user rights corresponding to the current account or the historical account, thereby achieving the purpose of the limited-time transfer of the user rights of the current account or the historical account.

[0137] In the technical solution disclosed in this embodiment, when the duration of the target account being configured to have the user rights corresponding to the current account or the historical account is greater than or equal to the preset duration, it indicates that the duration of the target account having the user rights corresponding to the current account or the historical account has reached the limited duration. The second permission information corresponding to the target account is updated according to the saved second user permission information, so that the user rights of the target account are restored to the user rights before being configured to have the user rights corresponding to the current account or the historical account. The duration of the target account having the user rights corresponding to the current account or the historical account is limited by the preset duration, so as to realize the time-limited transfer of the management rights of the user rights of the current account or the historical account, and the operation is simple.

[0138] The present application also provides an intelligent terminal, which includes a memory and a processor. The memory stores a rights management program, and when the rights management program is executed by the processor, the steps of the rights management method in any of the above embodiments are implemented.

[0139] The present application also provides a computer-readable storage medium, on which a rights management program is stored. When the rights management program is executed by a processor, the steps of the rights management method in any of the above embodiments are implemented.

[0140] In the embodiments of the smart terminal and computer-readable storage medium provided in the present application, all technical features of any of the above-mentioned permission management method embodiments may be included, and the expanded and explained contents of the specification are basically the same as those of the above-mentioned method embodiments, and will not be repeated here.

[0141] The embodiment of the present application further provides a computer program product, which includes a computer program code. When the computer program code runs on a computer, the computer executes the methods in the above various possible implementation modes.

[0142] An embodiment of the present application also provides a chip, including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device equipped with the chip executes the methods in various possible implementation modes as described above.

[0143] It is understood that the above scenarios are only examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of the present application. The technical solutions of the present application can also be applied to other scenarios. For example, it is known to those skilled in the art that with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0144] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0145] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0146] The units in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0147] In the present application, the same or similar terminology concepts, technical solutions and / or application scenario descriptions are generally described in detail only the first time they appear. When they appear again later, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of the present application, for the same or similar terminology concepts, technical solutions and / or application scenario descriptions that are not described in detail later, reference can be made to the previous related detailed descriptions.

[0148] In the present application, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0149] The various technical features of the technical solution of the present application can be arbitrarily combined. In order to make the description concise, not all possible combinations of the various technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of the present application.

[0150] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as above, and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, a controlled terminal, or a network device, etc.) to execute the method of each embodiment of the present application.

[0151] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integrated. The available medium can be a magnetic medium, (e.g., a floppy disk, a storage disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state storage disk Solid State Disk (SSD)), etc.

[0152] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A rights management method, characterized in that: The following steps are involved: S10: Determine the target account for exchanging user permissions; S20: According to the first permission information corresponding to the current account or the historical account, the target account is configured or updated so that the target account has the management permission corresponding to the first permission information.

2. The method according to claim 1, characterized in that The step S10 includes at least one of the following: Responding to the authority transfer instruction, determining or generating the target account according to the authority transfer instruction; In response to the permission request operation, determining or generating the target account according to the permission request operation; When the current time matches the preset time, the target account is determined or generated according to the current time.

3. The method according to claim 2, characterized in that The method further comprises: Obtaining the number of times the permission transfer instruction or the permission request operation is received within a preset time period; When the number is less than or equal to the preset number, respond to the permission transfer instruction or the permission request operation to determine the target account.

4. The method according to claim 1, characterized in that The step S20 comprises: Obtaining first permission information corresponding to the current account and / or the historical account, and deleting the current account and / or the historical account; The second permission information corresponding to the target account is configured as the first permission information.

5. The method according to claim 1, characterized in that The step S20 comprises: Acquire target information of the current account and / or the historical account, and determine the first authority information according to the target information; The target account is configured or updated according to the first permission information so that the target account has the management permission corresponding to the first permission information.

6. The method according to claim 5, characterized in that The step of obtaining target information of the current account and / or the historical account includes: Display or output account information corresponding to the current account and / or historical account; In response to a selection instruction for the account information, target information is determined or generated according to the selection instruction.

7. The method according to any one of claims 1 to 6, characterized in that Before step S20, the method further includes: Storing second permission information corresponding to the target account; After step S20, the method further includes: The first permission information of the current account or the historical account is configured or updated according to the second permission information, so that the current account or the historical account has the management permission corresponding to the second permission information.

8. The method according to any one of claims 1 to 6, characterized in that Before step S20, the method further includes: Saving the second permission information corresponding to the target account; After step S20, the method further includes: When the duration for which the target account has the user authority corresponding to the first authority information is greater than or equal to a preset duration, the second authority information corresponding to the target account is updated according to the saved second authority information.

9. An intelligent terminal, characterized in that: The smart terminal comprises: a memory and a processor, wherein a rights management program is stored in the memory, and when the rights management program is executed by the processor, the steps of the rights management method according to any one of claims 1 to 8 are implemented.

10. A storage medium, characterized in that: The storage medium stores a computer program, which, when executed by a processor, implements the steps of the rights management method according to any one of claims 1 to 8.

Images