CN115242456A

CN115242456A - User permission management system, method, device, electronic device and storage medium

Info

Publication number: CN115242456A
Application number: CN202210742945.5A
Authority: CN
Inventors: 王艺婷; 彭锦图; 余志应
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2022-06-28
Filing date: 2022-06-28
Publication date: 2022-10-25
Anticipated expiration: 2042-06-28
Also published as: CN115242456B

Abstract

The present disclosure relates to a user license management system, method, apparatus, electronic device, and storage medium, including: the operation server acquires the behavior information of each candidate account, determines the candidate accounts with the activity meeting the preset conditions as reserved accounts, and sets the user attribute of the reserved accounts as a first attribute; the business server releases the user permission of the reserved account; the operation server acquires a login request of a target account; acquiring user attributes of a target account; under the condition that the user attribute of the target account is the first attribute, sending the activation request to a service server; the service server responds to the activation request and activates the target account; and interacting with the target account in the case of successful activation. Therefore, the service server can release the user permission of the reserved account of the account with lower activity, reduce the occupation of the user with low activity rate on the permitted resource, and save the computing resource of the system because the operation server does not need to bind again.

Description

User permission management system, method, device, electronic device and storage medium

Technical Field

The present disclosure relates to the field of database technologies, and in particular, to a user permission management system, method, apparatus, electronic device, and storage medium.

Background

In some scenarios, an operator and a third-party platform cooperate to build and operate a project, and the terminal device can register and activate on the third-party platform through an operator server to obtain user permission, so that interaction with the third-party platform is realized, and corresponding services are used.

In the prior art, each user usually occupies one user license of the third-party platform, and it can be understood that the more the user licenses are issued, the more the user information that needs to be maintained by the third-party platform is, and then, the more investment is required by the operator and the third-party platform.

However, under the condition that the activity rates of the users are uneven, the users with lower activity occupy part of the user permission resources of the third-party platform, so that part of the users with higher activity cannot complete registration activation, or the investment of the operator and the third-party platform needs to be increased, so that the value of ARPU (average revenue per user) of the project is reduced, and the input-output proportion of the cooperative project is high.

Disclosure of Invention

The present disclosure provides a user permission management system, method, apparatus, electronic device, and storage medium, to at least solve the problem in the related art that a user with a low liveness occupies part of user permission resources of a third party platform, and lowers an ARPU value of a project, resulting in a high input-output ratio of a collaborative project. The technical scheme of the disclosure is as follows:

according to a first aspect of embodiments of the present disclosure, there is provided a user license management system including:

the operation server is used for acquiring the behavior information of each candidate account, the behavior information is related to the activity of the candidate account, and the candidate account is an account which is obtained from the operation server and is permitted by a user; according to the behavior information, determining a candidate account with the activity meeting a preset condition as a reserved account, and setting the user attribute of the reserved account as a first attribute; sending the user information of the reserved account to the service server;

the business server is used for releasing the user permission of the reserved account according to the user information of the reserved account;

the operation server is further used for obtaining a login request of a target account, wherein the login request carries user information of the target account; responding to the login request, and acquiring the user attribute of the target account according to the user information of the target account; sending an activation request to the service server under the condition that the user attribute of the target account is the first attribute, wherein the activation request carries the user information of the target account;

the business server is further used for responding to the activation request and activating the target account according to the user information of the target account; and under the condition of successful activation, generating and returning corresponding user permission to the target account to serve as the target user permission, so that the target account interacts with the service server based on the target user permission.

Optionally, the operation server is specifically configured to perform primary authentication on the target account according to the user information of the target account in response to the login request; and under the condition that the primary authentication is successful, acquiring the user attribute of the target account.

Optionally, the operation server is further configured to send the login request to the service server under the condition that the primary authentication on the target account is successful and the user attribute of the target account is not the first attribute, where the login request further carries the target user permission;

the business server is also used for responding to the login request and performing secondary authentication on the target account according to the permission of the target user; and returning login success information to the target account under the condition that the secondary authentication is successful.

Optionally, the service server is further configured to respond to a data processing request sent by the target account and interact with the target account under the condition that the secondary authentication on the target account is successful, where the data processing request carries the permission of the target user.

Optionally, the behavior information includes login times and/or login duration of the candidate account within a preset time;

the operation server is specifically configured to determine the activity of each candidate account within the preset time according to the login times and/or the login duration; and determining a preset number of candidate accounts as reserved accounts from the candidate accounts according to the sequence of the activity degrees from low to high, wherein the preset number is a preset percentage of the total number of the candidate accounts.

According to a second aspect of the embodiments of the present disclosure, there is provided a user license management method applied to an operation server, including:

acquiring behavior information of each candidate account, wherein the behavior information is related to the activity of the candidate account, and the candidate account is an account which is obtained from a business server and is permitted by a user;

according to the behavior information, determining a candidate account with the activity meeting a preset condition as a reserved account, and setting the user attribute of the reserved account as a first attribute;

sending the user information of the reserved account to a service server so that the service server releases the user permission of the reserved account;

acquiring a login request of a target account, wherein the login request carries user information of the target account;

responding to the login request, and acquiring the user attribute of the target account according to the user information of the target account;

and sending an activation request to the service server under the condition that the user attribute of the target account is the first attribute, wherein the activation request carries the user information of the target account, so that the service server activates the target account and returns target user permission to the target account.

Optionally, the obtaining, according to the user information of the target account, the user attribute of the target account includes:

performing primary authentication on the target account according to the user information of the target account;

and acquiring the user attribute of the target account under the condition that the primary authentication is successful.

Optionally, in a case that the primary authentication on the target account is successful and the user attribute of the target account is not the first attribute, the method further includes:

and sending the login request to the service server so that the service server performs secondary authentication on the target account, wherein the login request also carries the permission of the target user.

Optionally, the determining, according to the behavior information, a candidate account whose activity meets a preset condition as a reserved account includes:

determining the activity of each candidate account in the preset time according to the login times and/or the login duration;

and determining a preset number of candidate accounts as reserved accounts from the candidate accounts according to the sequence of the activity degrees from low to high, wherein the preset number is a preset percentage of the total number of the candidate accounts.

According to a third aspect of the embodiments of the present disclosure, there is provided a user license management method applied to a service server, including:

releasing user permission of a reserved account according to received user information of the reserved account, wherein the reserved account is a candidate account of which the activity degree determined by an operation server meets a preset condition;

under the condition that an activation request is received, activating a target account according to user information of the target account carried in the activation request;

and under the condition of successful activation, generating and returning corresponding user permission to the target account to serve as the target user permission, so that the target account interacts with the service server based on the target user permission.

Optionally, when a login request is received and the login request further carries the permission of the target user, the method further includes:

responding to the login request, and performing secondary authentication on the target account according to the permission of the target user;

and returning login success information to the target account under the condition that the secondary authentication is successful.

Optionally, the method further includes:

and under the condition that the secondary authentication of the target account is successful, responding to a data processing request sent by the target account, and interacting with the target account, wherein the data processing request carries the permission of the target user.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a user license management apparatus, applied to an operation server, including:

an acquisition unit configured to perform acquisition of behavior information of each candidate account, the behavior information being related to an activity of the candidate account, the candidate account being an account for which user permission has been acquired from a service server;

the determining unit is configured to execute the steps of determining a candidate account with the activity meeting a preset condition as a reserved account according to the behavior information, and setting the user attribute of the reserved account as a first attribute;

a sending unit configured to execute sending the user information of the reserved account to a service server so as to enable the service server to release the user permission of the reserved account;

the system comprises a login unit, a storage unit and a processing unit, wherein the login unit is configured to execute a login request for acquiring a target account, and the login request carries user information of the target account;

the query unit is configured to execute responding to the login request and acquire the user attribute of the target account according to the user information of the target account;

the request unit is configured to send an activation request to the service server when the user attribute of the target account is the first attribute, wherein the activation request carries user information of the target account, so that the service server activates the target account and returns target user permission to the target account.

Optionally, the querying unit is configured to perform:

Optionally, in a case that the primary authentication on the target account is successful and the user attribute of the target account is not the first attribute, the requesting unit is further configured to perform:

Optionally, the behavior information includes login times and/or login duration of the candidate account within a preset time, and the determining unit is configured to perform:

determining the activity of each candidate account within the preset time according to the login times and/or the login duration;

According to a fifth aspect of the embodiments of the present disclosure, there is provided a user license management device, applied to a service server, including:

the release unit is configured to release the user permission of the reserved account according to the received user information of the reserved account, wherein the reserved account is a candidate account of which the activity degree determined by the operation server meets a preset condition;

the activation unit is configured to activate the target account according to user information of the target account carried in the activation request under the condition that the activation request is received;

and the returning unit is configured to generate and return corresponding user permission to the target account as target user permission under the condition that the activation is successful, so that the target account interacts with the service server based on the target user permission.

Optionally, the apparatus further comprises:

the authentication unit is configured to perform secondary authentication on the target account according to the permission of the target user in response to the login request under the condition that the login request is received and the permission of the target user is also carried in the login request; and returning login success information to the target account under the condition that the secondary authentication is successful.

Optionally, the apparatus further includes a processing unit configured to perform:

According to a sixth aspect of embodiments of the present disclosure, there is provided a user license management electronic device including:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement any of the user license management methods described above.

According to a seventh aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium, wherein instructions, when executed by a processor of a user license management electronic device, enable the user license management electronic device to perform any of the user license management methods described above.

According to an eighth aspect of embodiments of the present disclosure, there is provided a computer program product comprising computer programs/instructions which, when executed by a processor, implement the user license management method of any of the above.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

the operation server acquires the behavior information of each candidate account, the behavior information is related to the activity of the candidate account, and the candidate account is an account which is obtained from the operation server and permitted by a user; determining a candidate account with the activity meeting a preset condition as a reserved account according to the behavior information, and setting the user attribute of the reserved account as a first attribute; sending the user information of the reserved account to a service server; the service server releases the user permission of the reserved account according to the user information of the reserved account; the operation server acquires a login request of a target account, wherein the login request carries user information of the target account; acquiring user attributes of the target account according to the user information of the target account; under the condition that the user attribute of the target account is the first attribute, sending an activation request to a service server, wherein the activation request carries user information of the target account; the service server activates the target account according to the user information of the target account; and under the condition that the activation is successful, generating and returning corresponding user permission to the target account to serve as the target user permission, so that the target account interacts with the service server based on the target user permission.

Therefore, for the reserved accounts with the activity degree not meeting the preset condition, the operation server can set the user attributes of the accounts as the first attributes, and further applies for activation to the service server under the condition that the user attribute of the target account is the first attribute after receiving the login request of any target account.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.

FIG. 1 is an interaction diagram illustrating a user license management system in accordance with an exemplary embodiment.

FIG. 2 is a logical diagram illustrating a user license management scheme in accordance with an exemplary embodiment.

FIG. 3 is a system architecture diagram illustrating one user license management scheme in accordance with an exemplary embodiment.

FIG. 4 is a flow diagram illustrating a method of user license management according to an example embodiment.

FIG. 5 is a flow diagram illustrating a method of user license management according to an example embodiment.

FIG. 6 is a block diagram illustrating a user license management arrangement in accordance with an exemplary embodiment.

FIG. 7 is a block diagram illustrating a user license management apparatus in accordance with an example embodiment.

FIG. 8 is a block diagram illustrating an electronic device for user license management in accordance with an exemplary embodiment.

FIG. 9 is a block diagram illustrating an apparatus for user license management in accordance with an example embodiment.

Detailed Description

In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below do not represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the disclosure, as detailed in the appended claims.

Fig. 1 is an interaction diagram illustrating a user license management system according to an exemplary embodiment, where the user license management system includes an operation server and a service server, as shown in fig. 1, and the following steps are respectively performed.

In step S11, the operation server obtains behavior information of each candidate account, where the behavior information is related to activity of the candidate account, and the candidate account is an account that has obtained user permission from the operation server; and determining candidate accounts with the activity meeting the preset conditions as reserved accounts according to the behavior information, and setting the user attribute of the reserved accounts as a first attribute.

In some scenarios, an operator and a third-party platform cooperate to build and operate a project to provide corresponding services for the terminal device, that is, the operator provides communication services through an operation server, and the third-party platform executes services required by the terminal device through a service server.

In the disclosure, a user interacts with a terminal device, an account is registered and activated in a service server through an operation server, a user permission returned by the service server is acquired, and further, based on the acquired user permission, interaction between the terminal device and the service server is realized, and a service provided by the service server is used.

Specifically, first, a user may send a registration application to an operation server through a terminal device, where the registration application carries user information, where the user information may include but is not limited to: and the business account number and the account information of the account to be registered. It can be understood that the operation server and the service server may provide multiple different service services at the same time, each service corresponds to a different service account number, and the account information may be an ID or a name of an account to be registered, which is not limited specifically. Then, the operation server responds to the registration application, can register the target service corresponding to the service account number for the account to be registered, and sends the activation request to the service server, wherein the activation request also carries the user information of the account to be registered. Furthermore, the service server can open the target service for the account to be registered, realize the registration and activation of the account to be registered, and simultaneously allocate the corresponding user permission for the account to be registered.

Therefore, the registration and activation of the account to be registered are realized, and the terminal equipment can log in the operation server and the service server after acquiring the corresponding user permission, so that the target service is realized.

In the present disclosure, for convenience of description, the account in which registration and activation are implemented may be referred to as a candidate account, and for each candidate account, login authentication is required before interacting with the service server to implement the target service. The login authentication of the candidate account comprises two processes, first-stage authentication of the candidate account needs to be performed through the operation server, then second-stage authentication of the candidate account needs to be performed through the service server after the first-stage authentication is successful, after the second-stage authentication is successful, the successful login of the candidate account is indicated, and target service interaction can be performed with the service server. The secondary authentication of the business server to the candidate account includes authentication of user permission of the candidate account.

It can be understood that the user licenses allocated to each account by the service server are in one-to-one correspondence, and the number of user licenses that can be provided by the service server is limited, the more user licenses allocated, the less the number of user licenses remaining and issuable by the service server, and if the user licenses are allocated, the new account cannot be registered and activated.

In order to reduce the possibility of occurrence of the above situation, in this step, a candidate account with an activity meeting a preset condition may be determined as a reserved account according to the behavior information. In one implementation, the behavior information may include login times and/or login duration of the candidate account within a preset time; then, the operation server may determine the activity of each candidate account within a preset time according to the login times and/or the login duration; and determining a preset number of candidate accounts as reserved accounts according to the sequence of the activity degrees from low to high from the candidate accounts, wherein the preset number is a preset percentage of the total number of the candidate accounts.

In this way, the operation server can optimize the rule of user license distribution according to the usage activity rate of the user, add an activity degree statistic function in the operation server, and determine the reserved accounts with lower activity degrees from the candidate accounts, so that the service server releases the user licenses of the reserved accounts, thereby reducing the occupation of the licensed resources by the user with low activity rate.

The activity can be determined only according to the login times, for example, it can be set that the login times are more within a preset time, the login activity is higher; or the activity may be determined only according to the login duration, for example, it may be set that the longer the login duration is within the preset time, the higher the login activity is; in addition, the activity can also be determined jointly according to the login times and the login duration, for example, the login times and the login duration within the preset time can be subjected to weighted summation, and the higher the obtained numerical value is, the higher the login activity is. The specific login activity calculation mode can be set according to the user requirement, and the method is not limited by the disclosure.

The preset number is a preset percentage of the total number of the candidate accounts, namely, the inactive accounts with the last n% of the statistics of the activity of the candidate accounts. For example, the value may be a fixed value, such as 10%, 5%, or the like, or may also be determined according to the number of received registration requests within a preset time, for example, if the number of received registration requests within the preset time exceeds a preset value, n is determined to be 20, and if the number of received registration requests within the preset time does not exceed the preset value, n is determined to be 10, and the like. The present disclosure is not limited thereto.

In addition, when determining the reserved account, the number of interactions between the candidate account and the service server, the resource conversion rate, and the like may also be considered, for example, if the number of interactions between the candidate account and the service server is large, it indicates that the frequency of using the target service by the candidate account is high, and therefore, the candidate account is excluded from the reserved account; or, if the virtual resources put into the target service by the candidate account are more, it indicates that the candidate account is an important user of the target service, and therefore the candidate account is excluded from the reserved account, whereas if the virtual resources put into the target service by the candidate account are lower than a preset threshold, it indicates that the candidate account has a lower contribution to the target service, and the candidate account may be used as the reserved account, and so on, which is not limited specifically.

In step S12, the operation server transmits the user information of the reserved account to the service server.

It can be understood that the activity of the reserved accounts is low, that is, the accounts may make less investment in the target service, but occupy a large amount of user license resources. In this case, the operation server may send a disconnection application to the service server, and send the user information of the reserved account to the service server, so as to implement reasonable allocation and utilization of the user-permitted resources.

In step S13, the service server releases the user permission of the reserved account according to the user information of the reserved account.

In this step, the service server responds to the disconnection application, and releases the user permission of the reserved account according to the user information of the reserved account, that is, deletes the user permission allocated to the reserved account before. Therefore, the number of the user licenses which can be distributed in the service server is increased, and the newly activated accounts can be reserved for use, so that the rule of distributing the user licenses is optimized, and the utilization rate of the user license resources is improved.

In step S14, the operation server obtains a login request of the target account, where the login request carries user information of the target account; and responding to the login request, and acquiring the user attribute of the target account according to the user information of the target account.

As can be seen from the foregoing, for each candidate account, before interacting with the service server to implement the target service, login authentication needs to be performed, which includes first-level authentication of the candidate account by the operation server, and second-level authentication of the candidate account by the service server after the first-level authentication is successful.

In this step, the operation server may respond to the login request and obtain the user attribute of the target account according to the user information of the target account. According to step S11, if the activity of the candidate account meets the preset condition, the candidate account is used as the reserved account, and the user attribute of the candidate account is set as the first attribute, for example, the first attribute may be represented as "reserved", or may be represented by a corresponding code, which is not limited specifically.

Specifically, the step of obtaining the user attribute of the target account according to the user information of the target account may include: responding to the login request, and performing primary authentication on the target account according to the user information of the target account; and under the condition that the primary authentication is successful, acquiring the user attribute of the target account. That is to say, the operation server may first perform primary authentication on the target account, further determine whether the target account is a reserved account if the primary authentication is successful, and return a login error prompt to the target account if the primary authentication is successful, or generate a login error alarm, and so on. Thus, the security of the primary authentication can be ensured.

Or, in one case, if the reserved account and the other candidate accounts except the reserved account correspond to different user attributes in the operation server, in response to the login request, the operation server may directly obtain the user attribute of the target account, and perform different subsequent operations according to the different user attributes, and if the user attribute is not obtained, which indicates that the target account is an unregistered account, the target account may be registered, or a login error prompt is returned to the target account, or a login error alarm is generated, and the like, which is not limited specifically. Therefore, the operation efficiency of the operation server can be further improved, the steps are simplified, and the occupation of system resources is reduced.

In step S15, the operation server sends an activation request to the service server when the user attribute of the target account is the first attribute, where the activation request carries user information of the target account.

As can be seen from the foregoing description, if the user attribute of the target account is the first attribute, it indicates that the target account is a reserved account, that is, although the user information of the accounts is reserved in the operation server, the service server has released the user permission of the accounts, and therefore, the operation server needs to send an activation request to the service server, so that the service server reactivates the reserved account, thereby ensuring normal use of the reserved account for the target service.

In addition, under the condition that the primary authentication of the target account is successful and the user attribute of the target account is not the first attribute, the target account is an activated non-reserved account with higher activity, and the user permissions of the accounts are not released by the service server and can be used continuously, so that the operation server can send the login request to the service server, wherein the login request also carries the target user permission, and further, the service server can respond to the login request and perform secondary authentication on the target account according to the target user permission; and returning login success information to the target account under the condition that the secondary authentication is successful.

In step S16, the service server responds to the activation request, and activates the target account according to the user information of the target account; and under the condition that the activation is successful, generating and returning corresponding user permission to the target account to serve as the target user permission, so that the target account interacts with the service server based on the target user permission.

In this step, after the operation server sends the activation request to the service server, the service server activates the reserved account, generates and returns a corresponding user permission to the target account, and the target account may interact with the service server based on the target user permission. As can be seen from the foregoing, the target account corresponding to the activation request may be a reserved account, or may also be an account to be registered that has not been activated.

Further, the target account may interact with the service server based on the target user permission, and first-level authentication between the target account and the operation server is required, after the first-level authentication is successful, the service server performs second-level authentication on the target account according to the target user permission, and in the case that the second-level authentication on the target account is successful, the service server interacts with the target account in response to a data processing request sent by the target account, where the data processing request carries the target user permission. The data processing request may be any data processing request related to a target service, which is not limited in this disclosure.

In addition, if the secondary authentication is not successful, the service server may return a login error prompt to the target account, or generate a login error alarm, and the like, which is not limited specifically.

As shown in fig. 2, a logic diagram of the present solution is shown, and the present solution is divided into three flows:

scheme 1: and the service opening, activating and using processes comprise business acceptance, service activation and user login authentication. In the business acceptance flow 1.1, a business can be opened, and a business account is generated and sent to an operation server; in the service activation process 1.2, a service account and a device ID can be bound, the device ID can be used as account information, then the service account and the device ID are sent to an operation server for registration, and further the service account and the device ID are sent to the service server for activation; in the authentication process 1.3, the first-level authentication of the service account and the equipment ID by the operation server and the second-level authentication of the service account and the equipment ID by the service server can be performed; in the service using process 1.4, after the authentication is successful, the terminal and the service server can interact to use the service.

And (2) a process: the link of releasing the user permission of the cooperation platform comprises the following steps:

sorting according to the heat degree of a user login period, extracting users with the last inactivity of n percent, namely determining candidate accounts with lower activity as reserved accounts, reserving the information of the accounts, and marking the attribute of the user as 'reserved'; and sending the disconnection application of the reserved account to the service server through an interface, disconnecting the service server, and releasing the user permission of n% of the total number of the users.

And (3) a flow scheme: changes in business processes, including:

after the target account is started, sending a login application, judging the user attribute of the target account by the operation server, and if the user attribute is 'in use', continuing the secondary authentication, user login authentication flow 1.3 and service use flow 1.4; if the user attribute is 'reserved', namely the first attribute, the service account and the equipment ID are sent to a service server for activation, and then the secondary authentication, user login authentication process 1.3 and service use process 1.4 are continued.

As shown in fig. 3, is a system architecture diagram of the present application. Firstly, a terminal device builds a user service inlet for interacting with a user, an operation server builds an operator self-built service management platform, primary service management is carried out on an account and comprises account registration and primary authentication, a service server builds a cooperation building or cooperation operation platform, secondary service management is carried out on the account and comprises account activation and secondary authentication, and the cooperation building or cooperation operation platform can interact with the user service inlet. Meanwhile, the operator self-built service management platform can carry out user login heat statistics, namely, a reserved account with lower activity is determined, and for an inactive account with the last n percent, a shutdown application is initiated to the cooperative building or cooperative operation platform, and meanwhile, the user attribute of the reserved account which is sent to shutdown is set as 'reserved'. When the user is online, the operator self-built service management platform judges that the user attribute is the account reserved, and sends the account to the cooperation building or cooperation operation platform for activation, and then the cooperation building or cooperation operation platform can interact with the user service entrance.

As can be seen from the above, according to the technical scheme provided by the embodiment of the disclosure, for reserved accounts with liveness not meeting preset conditions, the operation server may set the user attributes of the accounts as the first attributes, and then, after receiving a login request of any one target account, apply for activation to the service server if the user attribute of the target account is the first attribute, on one hand, the service server may release the user permission of the reserved accounts with lower liveness, so as to implement a rule for optimizing user permission allocation according to the user use liveness, reduce occupation of the permitted resources by users with low liveness, and on the other hand, the operation server reserves information of the accounts, and does not need to bind again, and the users do not need to re-execute operation of opening the service, thereby saving computing resources of the system, and improving user experience.

Fig. 4 is a flowchart illustrating a user license management method applied to an operation server according to an exemplary embodiment, and the user license management method includes the following steps, as shown in fig. 4.

In step S21, acquiring behavior information of each candidate account, the behavior information being related to the activity of the candidate account, the candidate account being an account that has acquired user permission from a service server;

in step S22, according to the behavior information, determining a candidate account with an activity meeting a preset condition as a reserved account, and setting a user attribute of the reserved account as a first attribute;

in step S23, sending the user information of the reserved account to a service server, so that the service server releases the user permission of the reserved account;

in step S24, a login request of a target account is obtained, where the login request carries user information of the target account;

in step S25, in response to the login request, acquiring a user attribute of the target account according to the user information of the target account;

in step S26, when the user attribute of the target account is the first attribute, an activation request is sent to the service server, where the activation request carries user information of the target account, so that the service server activates the target account and returns a target user permission to the target account.

In one implementation manner, the obtaining, according to the user information of the target account, the user attribute of the target account includes:

and under the condition that the primary authentication is successful, acquiring the user attribute of the target account.

In one implementation, in the case that the primary authentication of the target account is successful and the user attribute of the target account is not the first attribute, the method further comprises:

In one implementation manner, the determining, according to the behavior information, a candidate account whose activity level meets a preset condition as a reserved account includes:

Fig. 5 is a flowchart illustrating a user license management method applied to a service server according to an exemplary embodiment, and the user license management method includes the following steps, as shown in fig. 5.

In step S31, according to the received user information of the reserved account, releasing the user permission of the reserved account, where the reserved account is a candidate account whose activity level determined by the operation server meets a preset condition;

in step S32, in the case of receiving an activation request, activating a target account according to user information of the target account carried in the activation request;

in step S33, if the activation is successful, a corresponding user permission is generated and returned to the target account as a target user permission, so that the target account interacts with the service server based on the target user permission.

In an implementation manner, when a login request is received and the login request further carries permission of the target user, the method further includes:

In one implementation, the method further comprises:

Fig. 6 is a block diagram of a user license management apparatus according to an exemplary embodiment, applied to an operation server, the apparatus including:

an obtaining unit 401 configured to perform obtaining behavior information of each candidate account, the behavior information being related to an activity of the candidate account, the candidate account being an account that has obtained user permission from a service server;

a determining unit 402, configured to execute determining, according to the behavior information, a candidate account whose activity level meets a preset condition as a reserved account, and setting a user attribute of the reserved account as a first attribute;

a sending unit 403, configured to execute sending the user information of the reserved account to a service server, so that the service server releases the user permission of the reserved account;

a login unit 404 configured to execute a login request for obtaining a target account, where the login request carries user information of the target account;

the query unit 405 is configured to perform, in response to the login request, acquiring a user attribute of the target account according to the user information of the target account;

a requesting unit 406, configured to send an activation request to the service server when the user attribute of the target account is a first attribute, where the activation request carries user information of the target account, so that the service server activates the target account and returns a target user permission to the target account.

In one implementation, the querying unit 405 is configured to perform:

In one implementation, in a case that the primary authentication on the target account is successful and the user attribute of the target account is not the first attribute, the requesting unit 406 is further configured to perform:

In one implementation manner, the behavior information includes login times and/or login duration of the candidate account within a preset time, and the determining unit 402 is configured to perform:

Fig. 7 is a block diagram of a user license management apparatus according to an exemplary embodiment, which is applied to a service server and includes:

a releasing unit 501, configured to release user permission of a reserved account according to received user information of the reserved account, where the reserved account is a candidate account whose activity level determined by an operation server meets a preset condition;

an activation unit 502 configured to activate a target account according to user information of the target account carried in an activation request when the activation request is received;

a returning unit 503, configured to perform, in a case that the activation is successful, generating and returning a corresponding user license to the target account as a target user license, so that the target account interacts with the service server based on the target user license.

In one implementation, the apparatus further includes:

In one implementation, the apparatus further includes a processing unit configured to perform:

With regard to the apparatus in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be described in detail here.

FIG. 8 is a block diagram illustrating an electronic device for user license management, including a processor and a memory, where the memory is used to house a computer program, according to an exemplary embodiment; the processor is used for executing the program stored in the memory.

The Memory may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.

The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.

In an exemplary embodiment, a computer-readable storage medium comprising instructions, such as a memory comprising instructions, executable by a processor of an electronic device to perform the above-described method is also provided. Alternatively, the computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, there is also provided a computer program product which, when run on a computer, causes the computer to implement the above-described method for pending user license management.

FIG. 9 is a block diagram illustrating an apparatus 800 for user license management according to an example embodiment.

For example, the apparatus 800 may be a mobile phone, a computer, a digital broadcast electronic device, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.

Referring to fig. 9, the apparatus 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.

The processing component 802 generally controls overall operation of the device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 802 may include one or more processors 820 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.

The memory 804 is configured to store various types of data to support operation at the device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

A power supply component 807 provides power to the various components of the device 800. The power components 807 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the apparatus 800.

The multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front facing camera and/or a rear facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data to be processed when the device 800 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 810 is configured to output and/or input audio signals. For example, audio component 810 includes a Microphone (MIC) configured to receive external audio signals when apparatus 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

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

The communication component 816 is configured to facilitate communications between the apparatus 800 and other devices in a wired or wireless manner. The apparatus 800 may access a wireless network based on a communication standard, such as WiFi, an operator network (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the apparatus 800 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 methods of the first and second aspects.

In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 804 comprising instructions, executable by the processor 820 of the device 800 to perform the above-described method is also provided. Alternatively, for example, the storage medium may be a non-transitory computer-readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the user license management method of any of the above embodiments.

From the above, it can be seen that the technical solutions provided by the embodiments of the present disclosure,

for the reserved accounts with the activity degree not meeting the preset condition, the operation server can set the user attributes of the accounts as the first attributes, and further applies for activation to the service server under the condition that the user attribute of the target account is the first attribute after receiving the login request of any target account.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A user license management system, comprising:

the operation server is used for acquiring the behavior information of each candidate account, the behavior information is related to the activity of the candidate account, and the candidate account is an account which is obtained from the operation server and is permitted by a user; determining a candidate account with the activity meeting a preset condition as a reserved account according to the behavior information, and setting the user attribute of the reserved account as a first attribute; sending the user information of the reserved account to the service server;

the operation server is further used for obtaining a login request of a target account, wherein the login request carries user information of the target account; responding to the login request, and acquiring the user attribute of the target account according to the user information of the target account; under the condition that the user attribute of the target account is the first attribute, sending an activation request to the service server, wherein the activation request carries user information of the target account;

the service server is further used for responding to the activation request and activating the target account according to the user information of the target account; and under the condition of successful activation, generating and returning corresponding user permission to the target account to serve as target user permission, so that the target account interacts with the service server based on the target user permission.

2. The user license management system according to claim 1,

the operation server is specifically used for responding to the login request and performing primary authentication on the target account according to the user information of the target account; and under the condition that the primary authentication is successful, acquiring the user attribute of the target account.

3. The user license management system according to claim 2,

the operation server is further configured to send the login request to the service server under the condition that the primary authentication on the target account is successful and the user attribute of the target account is not the first attribute, where the login request also carries the target user permission;

4. The user license management system according to claim 3,

the business server is further configured to interact with the target account in response to a data processing request sent by the target account under the condition that the secondary authentication of the target account is successful.

5. The user permission management system according to any one of claims 1 to 4, wherein the behavior information includes a login number and/or a login duration of the candidate account within a preset time;

6. A user permission management method is applied to an operation server and comprises the following steps:

determining a candidate account with the activity meeting a preset condition as a reserved account according to the behavior information, and setting the user attribute of the reserved account as a first attribute;

7. The method according to claim 6, wherein the obtaining the user attribute of the target account according to the user information of the target account comprises:

8. The method of claim 7, wherein in the event that the primary authentication of the target account is successful and the user attribute of the target account is not the first attribute, the method further comprises:

9. The user permission management method according to any one of claims 6 to 8, wherein the behavior information includes login times and/or login duration of the candidate account within a preset time, and the determining, as the reserved account, the candidate account whose activity level meets a preset condition according to the behavior information includes:

10. A user permission management method is applied to a service server and comprises the following steps:

and under the condition of successful activation, generating and returning corresponding user permission to the target account to serve as target user permission, so that the target account interacts with the service server based on the target user permission.

11. The user permission management method according to claim 10, wherein when a login request is received and the login request further carries the target user permission, the method further comprises:

12. The user license management method of claim 11, the method further comprising:

and under the condition that the secondary authentication of the target account is successful, responding to a data processing request sent by the target account, and interacting with the target account.

13. A user license management apparatus, applied to an operation server, comprising:

the system comprises a login unit, a processing unit and a processing unit, wherein the login unit is configured to execute a login request for acquiring a target account, and the login request carries user information of the target account;

14. The apparatus according to claim 13, wherein the querying unit is configured to perform:

15. The user license management apparatus according to claim 14, wherein in a case where the primary authentication on the target account is successful and the user attribute of the target account is not the first attribute, the requesting unit is further configured to perform:

16. The apparatus according to any one of claims 13 to 15, wherein the behavior information includes a login number and/or a login duration of the candidate account within a preset time, and the determining unit is configured to perform:

17. A user license management apparatus, applied to a service server, comprising:

18. The user license management apparatus of claim 17, wherein the apparatus further comprises:

19. The apparatus according to claim 18, wherein the apparatus further comprises a processing unit configured to execute:

20. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the user permission management method of any of claims 6 to 9 or 10 to 12.

21. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of a user license management electronic device, enable the user license management electronic device to perform the user license management method of any of claims 6-9 or 10-12.