Account distribution management method based on account pool and medium
Through the dynamic allocation and recycling mechanism of the account pool, the account is managed according to the user's usage period, which solves the problem of waste of account resources in the existing technology and improves the utilization rate and management efficiency of the account.
Patent Information
- Application Number
- CN202411105280.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-13
- Publication Date
- 2024-12-06
AI Technical Summary
The existing account allocation management methods cannot effectively predict and utilize the number of users on the Internet platform, resulting in wasting account resources by trial users and reducing the account utilization rate.
By establishing an account pool, users are classified as ordinary users and non-ordinary users according to their usage period, setting up storage time and management strategies for different accounts, realizing dynamic allocation and recycling of accounts, and improving the efficiency of account utilization.
It effectively improves the utilization rate of accounts, avoids waste of resources, and optimizes account management through the billing system and account type modification permissions.
Smart Images

Figure CN119094169A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of network management, and in particular to an account allocation management method and medium based on an account pool. Background Art
[0002] With the continuous development and application of computer network technology, various account-based applications continue to emerge, and different applications and platforms will also meet the actual needs of users to use the same account to log in to different applications.
[0003] In the actual application usage process, some network platforms will integrate the network platform's own functions by purchasing third-party applications, and the third-party applications will also allocate a limited number of accounts to the network platform, so that the network platform has richer applications and meets the user's requirements for account allocation management by using the account allocated to the network platform by the third-party application.
[0004] However, the existing account allocation management method has shortcomings: the number of users of the network platform is usually unpredictable, and some of these unpredictable users only try to use the account allocated by the network platform and will not really use the account for a long time. If the trial user permanently occupies the account allocated by the network platform, it will waste the account resources allocated by the third-party application to the network platform and reduce the utilization rate of the account allocated by the network platform. Summary of the invention
[0005] The first technical problem to be solved by the present invention is to provide an account allocation management method based on an account pool for improving account utilization in view of the above-mentioned prior art.
[0006] The second technical problem to be solved by the present invention is to provide a readable storage medium for implementing the above-mentioned account allocation management method based on the account pool.
[0007] The technical solution adopted by the present invention to solve the first technical problem is: an account allocation management method based on an account pool, characterized in that it includes the following steps:
[0008] Step 1: Establish a connection between the network platform and the third-party application, and classify all users of the network platform in advance according to the usage period of the third-party application to obtain ordinary users and non-ordinary users of the network platform; among them, users who need to use the third-party application for a short period of time are ordinary users, and users who need to use the third-party application for a long period of time are non-ordinary users;
[0009] Step 2, respectively managing the storage duration of the history records of common users and non-common users for third-party applications; wherein the history records of common users for third-party applications are set to be stored temporarily, and the history records of non-common users for third-party applications are set to be stored permanently;
[0010] Step 3: pre-build an account pool that belongs to the network platform and is operated by the network platform management party; wherein the account pool corresponds to the third-party application one by one, the accounts in the account pool include ordinary accounts and non-ordinary accounts corresponding to the third-party application, and the network platform management party operation includes the management party adding, deleting and modifying the third-party application account in the account pool;
[0011] Step 4: Check whether the user of the network platform has logged into the third-party application;
[0012] Step 5: Make a judgment based on the login detection result:
[0013] When the user of the network platform logs in to the third-party application, go to step 6; otherwise, go to step 4;
[0014] Step 6: Determine the user type of the network platform:
[0015] When the user type is a non-ordinary user of the network platform, proceed to step 7; otherwise, proceed to step 9;
[0016] Step 7: Determine whether the non-ordinary user has been bound to a third-party application:
[0017] When the third-party application has been bound, the non-ordinary account that has been bound to the third-party application and is in the account pool is assigned to the non-ordinary user; otherwise, proceed to step 8;
[0018] Step 8: submit an account allocation request to the administrator of the network platform and allocate a new non-ordinary account added by the administrator to the account pool to the non-ordinary user, so as to establish a binding relationship between the non-ordinary user and the new non-ordinary account added to the account pool;
[0019] Step 9: Select a common account in the account pool and assign it to the common user.
[0020] Improved, in the account allocation management method based on the account pool, in step 9, the process of selecting a common account in the account pool and allocating it to the common user includes the following steps:
[0021] Step a1: determine whether the common user has bound a third-party application.
[0022] If the third-party application has been bound, the common account that has been most recently bound to the third-party application and is in the account pool is assigned to the common user; otherwise, proceed to step a2;
[0023] Step a2: assigning the common account in the account pool and having the longest interval from the last use to the common user, so as to establish a binding relationship between the common user and the assigned common account.
[0024] Improved, in the invention, the account allocation management method based on the account pool further includes:
[0025] Step b1, detecting the rotation frequency of each common account in the account pool; wherein, if the same common account is allocated and used twice in succession, it is considered to be rotated once;
[0026] Step b2: determine whether the rotation frequency of each common account exceeds a preset rotation frequency threshold:
[0027] When the rotation frequency of any common account exceeds a preset rotation frequency threshold, the management of the network platform is prompted to purchase a new third-party application account from the third-party application to add to the account pool.
[0028] Furthermore, in the invention, the account allocation management method based on the account pool also includes: granting the account type modification authority to the administrator of the network platform to modify the account type in the account pool; and, according to the account type modification operation of the administrator of the network platform, changing the type of the account in the account pool; wherein the account type modification authority includes modifying the account to be an ordinary account or a non-ordinary account.
[0029] Further improved, in this invention, the account allocation management method based on the account pool also includes: establishing a connection between the network platform and the billing system of the third-party application; and the billing system of the third-party application performs billing operations based on the length of time and frequency of the user using the account in the account pool to log in to the third-party application.
[0030] Improved, in the invention, the account allocation management method based on the account pool further includes:
[0031] Step c1, setting an account recovery time limit switch operation for recovering accounts in the account pool; wherein, when the account recovery time limit is reached, the accounts in the account pool are recovered and are in a state where they cannot be allocated for use; and when the account recovery time limit is not reached, the accounts in the account pool are in a state where they can be allocated for use;
[0032] Step c2, detecting the account recovery time limit switch status;
[0033] Step c3: make a judgment based on the account recovery time limit switch status detection result:
[0034] When the account recycling time limit is in the on state, the account that has reached the account recycling time limit will be recycled to a state where it cannot be allocated for use; otherwise, proceed to step c2.
[0035] Improved, in the account allocation management method based on the account pool, the management of the network platform adjusts the level of the ordinary user according to the frequency of use of the assigned account by the ordinary user; wherein the level of the ordinary user is positively correlated with the number of accounts assigned to the ordinary user.
[0036] As a further improvement, in the account allocation management method based on the account pool, the operations of step 1 to step 9 are respectively performed according to the number of third-party applications; wherein the account pool corresponds to the third-party application one by one.
[0037] The second technical problem to be solved by the present invention is: a readable storage medium having a computer program stored thereon, characterized in that when the computer program is executed by a processor, any one of the account allocation management methods based on an account pool is implemented.
[0038] Compared with the prior art, the advantages of the present invention are as follows: the account allocation management method based on the account pool of the present invention obtains ordinary users and non-ordinary users by classifying the usage period of the third-party application that needs to be used in the network platform, and constructs an account pool corresponding to the third-party application, wherein the account pool includes ordinary accounts and non-ordinary accounts corresponding to the third-party application. Once it is detected that a user of the network platform logs in to the third-party application and it is determined that the user type is a non-ordinary user who has been bound to the third-party application, the non-ordinary account of the non-ordinary user that has been bound to the third-party application and is located in the account pool is allocated to the non-ordinary user; and when the non-ordinary user who has logged in to the third-party application is not bound to the third-party application, a non-ordinary account newly added by the management party in the account pool is allocated to the non-ordinary user. The user establishes a binding relationship between the non-ordinary user and the newly added non-ordinary account in the account pool; as for the non-ordinary user who logs in to the third-party application, the network platform manager selects an ordinary account in the account pool and allocates it to the ordinary user, thereby realizing the use of the network platform to permanently save the account and historical records for the third-party application for its non-ordinary users, and the ordinary users who frequently log in to third parties can save their account and historical records for logging into the third-party application. As for the accounts in the account pool that have not been used for a long time, they will be allocated to other users for use, thereby realizing the allocation and use efficiency of the accounts in the account pool for logging in to the third-party application, avoiding the waste of account resources allocated to the network platform by the third-party application, and improving the utilization rate of the accounts allocated to the network platform. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] Figure 1 The figure is a flow chart of an account allocation management method based on an account pool in an embodiment of the present invention. DETAILED DESCRIPTION
[0040] The present invention is further described in detail below with reference to the accompanying drawings.
[0041] This embodiment provides an account allocation management method based on an account pool. Figure 1 As shown, the account allocation management method based on the account pool includes the following steps 1 to 9:
[0042] Step 1: Establish a connection between the network platform and the third-party application, and classify all users of the network platform in advance according to the usage period of the third-party application to obtain ordinary users and non-ordinary users of the network platform; among them, users who need to use the third-party application for a short period of time are ordinary users, and users who need to use the third-party application for a long period of time are non-ordinary users; the sharing of user information between the network platform and the third-party application needs to have been legally authorized by the user in a legal manner;
[0043] It should be noted that, in this embodiment, ordinary users and non-ordinary users of the network platform are classified based on the usage period of the third-party application; for example:
[0044] For network platform C, the third-party application connected to the network platform C is marked as APP1. Then, network platform C will classify all users of network platform C in advance according to the required usage period of third-party application APP1, and obtain ordinary users and non-ordinary users of the network platform; after classification, according to the required usage period of third-party application APP1, ordinary users of network platform C are X APP1,1 , X APP1,2 , …, X APP1,m , the non-ordinary user of the network platform C is Y APP1,1 , Y APP1,2 , …, Y APP1,n ;
[0045] For network platform C, the second third-party application connected to the network platform C is marked as APP2. Then, network platform C will classify all users of network platform C in advance according to the required usage period of third-party application APP2, and obtain ordinary users and non-ordinary users of the network platform; after classification, according to the required usage period of third-party application APP2, ordinary users of network platform C are X. APP2,1 , X APP2,2 , …, X APP2,m , the non-ordinary user of the network platform C is Y APP2,1 , Y APP2,2 , …, Y APP2,n ;
[0046] The same applies to ordinary users and non-ordinary users corresponding to other third-party applications connected to network platform C;
[0047] It should be noted again that among all users of the network platform C, the same user may be a common user of a third-party application, and the user may also be a non-common user of another third-party application;
[0048] Step 2, respectively managing the storage duration of the history records of common users and non-common users for third-party applications; wherein the history records of common users for third-party applications are set to be stored temporarily, and the history records of non-common users for third-party applications are set to be stored permanently;
[0049] Step 3: pre-build an account pool that belongs to the network platform and is operated by the network platform management party; wherein the account pool corresponds to the third-party application one by one, the accounts in the account pool include ordinary accounts and non-ordinary accounts corresponding to the third-party application, and the network platform management party operation includes the management party adding, deleting and modifying the third-party application account in the account pool;
[0050] For example, for the third-party application APP1, the pre-built account pool is POOL APP1 , the account pool POOL APP1 The common accounts corresponding to the third-party APP1 application include Account1 APP1 、Account2 APP1 and Account3 APP1 ; The account pool POOL APP1 The non-ordinary accounts corresponding to the third-party APP1 application include Account1 VIP,APP1 、Account2 VIP,APP1 、Account3 VIP,APP1 and Account4 VIP,APP1 ;
[0051] Step 4: Check whether the user of the network platform has logged into the third-party application;
[0052] Step 5: Make a judgment based on the login detection result:
[0053] When the user of the network platform logs in to the third-party application, go to step 6; otherwise, go to step 4;
[0054] Step 6: Determine the user type of the network platform:
[0055] When the user type is a non-ordinary user of the network platform, proceed to step 7; otherwise, proceed to step 9;
[0056] Step 7: Determine whether the non-ordinary user has been bound to a third-party application:
[0057] When the third-party application has been bound, the non-ordinary account that has been bound to the third-party application and is in the account pool is assigned to the non-ordinary user; otherwise, proceed to step 8;
[0058] For example, if the third-party application is APP1, if the type is determined, the non-ordinary user is user Y. APP1,2 Once it is determined that the non-ordinary user Y APP1,2 When the third-party application APP1 has been bound, the non-ordinary user Y APP1,2 Already bound to the third-party application APP1 and located in the account pool POOL APP1 The non-ordinary account Account2 VIP,APP1 Assign this non-ordinary user Y APP1,2 ; Of course, the identity information of the non-ordinary user that has been bound to the third-party application has been legally authorized by the user to be shared with the third-party platform;
[0059] Step 8: submit an account allocation request to the administrator of the network platform and allocate a new non-ordinary account added by the administrator to the account pool to the non-ordinary user, so as to establish a binding relationship between the non-ordinary user and the new non-ordinary account added to the account pool;
[0060] Step 9: Select a common account in the account pool and assign it to the common user.
[0061] Specifically, in the above step 9, the process of selecting a common account from the account pool and assigning it to the common user includes the following steps a1 to a2:
[0062] Step a1: determine whether the common user has bound a third-party application.
[0063] If the third-party application has been bound, the common account that has been most recently bound to the third-party application and is in the account pool is assigned to the common user; otherwise, proceed to step a2;
[0064] Step a2: assigning the common account in the account pool and having the longest interval from the last use to the common user, so as to establish a binding relationship between the common user and the assigned common account.
[0065] In order to timely update and supplement the accounts in the account pool to meet the actual needs of users of the network platform to use third-party applications, the account allocation management method based on the account pool of this embodiment also includes the following steps:
[0066] Step b1, detecting the rotation frequency of each common account in the account pool; wherein, if the same common account is allocated and used twice in succession, it is considered to be rotated once;
[0067] Step b2: determine whether the rotation frequency of each common account exceeds a preset rotation frequency threshold:
[0068] When the rotation frequency of any common account exceeds a preset rotation frequency threshold, the management of the network platform is prompted to purchase a new third-party application account from the third-party application to add to the account pool.
[0069] In order to meet the needs of the network platform's management fee party for modifying the account type in the account pool, the account allocation management method based on the account pool of this embodiment also includes: granting the network platform's management party account type modification authority to modify the account type in the account pool; and, according to the network platform's management party's modification operation on the account type, changing the type of the account in the account pool; wherein the account type modification authority includes modifying the account to be an ordinary account or a non-ordinary account.
[0070] In order to meet the billing statistics of users' use of third-party applications, the account allocation management method based on the account pool of this embodiment also includes: establishing a connection between the network platform and the billing system of the third-party application; and the billing system of the third-party application performs billing operations based on the length of time and frequency of the user's use of the third-party application using an account in the account pool to log in.
[0071] In order to effectively utilize the accounts in the account pool and prevent the accounts from being idle for a long time, the account allocation management method based on the account pool of this embodiment further includes the following operations:
[0072] Step c1, setting an account recovery time limit switch operation for recovering accounts in the account pool; wherein, when the account recovery time limit is reached, the accounts in the account pool are recovered and are in a state where they cannot be allocated for use; and when the account recovery time limit is not reached, the accounts in the account pool are in a state where they can be allocated for use;
[0073] Step c2, detecting the account recovery time limit switch status;
[0074] Step c3: make a judgment based on the account recovery time limit switch status detection result:
[0075] When the account recycling time limit is in the on state, the account that has reached the account recycling time limit will be recycled to a state where it cannot be allocated for use; otherwise, proceed to step c2.
[0076] In order to facilitate the administrator of the network platform to adjust the account data allocated to its ordinary users according to actual needs, in the account allocation management method based on the account pool of this embodiment, the administrator of the network platform adjusts the level of the ordinary user according to the frequency of use of the allocated account by the ordinary user; wherein the level of the ordinary user is positively correlated with the number of accounts allocated to the ordinary user.
[0077] In order to meet the needs of users on the network platform for using multiple third-party applications, the account allocation management method based on the account pool of this embodiment will also execute the operations of steps 1 to 9 respectively according to the number of third-party applications; wherein the account pool corresponds one-to-one to the third-party application.
[0078] This embodiment also provides a readable storage medium. Specifically, the readable storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned account allocation management method based on the account pool is implemented.
[0079] Although the preferred embodiments of the present invention are described in detail above, it should be clearly understood that various modifications and variations are possible for those skilled in the art. Any modification, equivalent substitution, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.
Claims
1. An account allocation management method based on an account pool, characterized in that: The steps include: Step 1: Establish a connection between the network platform and the third-party application, and classify all users of the network platform in advance according to the usage period of the third-party application to obtain ordinary users and non-ordinary users of the network platform; among them, users who need to use the third-party application for a short period of time are ordinary users, and users who need to use the third-party application for a long period of time are non-ordinary users; Step 2, respectively managing the storage duration of the history records of common users and non-common users for third-party applications; wherein the history records of common users for third-party applications are set to be stored temporarily, and the history records of non-common users for third-party applications are set to be stored permanently; Step 3: pre-build an account pool that belongs to the network platform and is operated by the network platform management party; wherein the account pool corresponds to the third-party application one by one, the accounts in the account pool include ordinary accounts and non-ordinary accounts corresponding to the third-party application, and the network platform management party operation includes the management party adding, deleting and modifying the third-party application account in the account pool; Step 4: Check whether the user of the network platform has logged into the third-party application; Step 5: Make a judgment based on the login detection result: When the user of the network platform logs in to the third-party application, go to step 6; otherwise, go to step 4; Step 6: Determine the user type of the network platform: When the user type is a non-ordinary user of the network platform, proceed to step 7; otherwise, proceed to step 9; Step 7: Determine whether the non-ordinary user has been bound to a third-party application: When the third-party application has been bound, the non-ordinary account that has been bound to the third-party application and is in the account pool is assigned to the non-ordinary user; otherwise, proceed to step 8; Step 8: submit an account allocation request to the administrator of the network platform and allocate a new non-ordinary account added by the administrator to the account pool to the non-ordinary user, so as to establish a binding relationship between the non-ordinary user and the new non-ordinary account added to the account pool; Step 9: Select a common account in the account pool and assign it to the common user.
2. The account allocation management method based on the account pool according to claim 1 is characterized in that: In step 9, the process of selecting a common account from the account pool and assigning it to the common user includes the following steps: Step a1: determine whether the common user has bound a third-party application. If the third-party application has been bound, the common account that has been most recently bound to the third-party application and is in the account pool is assigned to the common user; otherwise, proceed to step a2; Step a2: assigning the common account in the account pool and having the longest interval from the last use to the common user, so as to establish a binding relationship between the common user and the assigned common account.
3. The account allocation management method based on the account pool according to claim 2 is characterized in that: Also includes: Step b1, detecting the rotation frequency of each common account in the account pool; wherein, if the same common account is allocated and used twice in succession, it is considered to be rotated once; Step b2: determine whether the rotation frequency of each common account exceeds a preset rotation frequency threshold: When the rotation frequency of any common account exceeds a preset rotation frequency threshold, the management of the network platform is prompted to purchase a new third-party application account from the third-party application to add to the account pool.
4. The account allocation management method based on the account pool according to claim 3 is characterized in that: Also includes: Granting the administrator of the network platform the authority to modify the account types in the account pool; And, according to the modification operation of the account type by the administrator of the network platform, the type of the account in the account pool is changed; wherein the account type modification authority includes modifying the account to be a common account or a non-common account.
5. The account allocation management method based on the account pool according to any one of claims 1 to 4, characterized in that: Also includes: Establish the connection between the network platform and the billing system of third-party applications; In addition, the billing system of the third-party application performs billing operations based on the length of time and frequency of the user using the account in the account pool to log in and use the third-party application.
6. The account allocation management method based on the account pool according to any one of claims 1 to 4, characterized in that: Also includes: Step c1, setting an account recovery time limit switch operation for recovering accounts in the account pool; wherein, when the account recovery time limit is reached, the accounts in the account pool are recovered and are in a state where they cannot be allocated for use; and when the account recovery time limit is not reached, the accounts in the account pool are in a state where they can be allocated for use; Step c2, detecting the account recovery time limit switch status; Step c3: make a judgment based on the account recovery time limit switch status detection result: When the account recycling time limit is in the on state, the account that has reached the account recycling time limit will be recycled to a state where it cannot be allocated for use; otherwise, proceed to step c2.
7. The account allocation management method based on the account pool according to any one of claims 1 to 4, characterized in that: Also includes: The administrator of the network platform adjusts the level of the ordinary user according to the frequency of use of the assigned account by the ordinary user; wherein the level of the ordinary user is positively correlated with the number of accounts assigned to the ordinary user.
8. The account allocation management method based on the account pool according to any one of claims 1 to 4, characterized in that: Also includes: According to the number of third-party applications, the operations of step 1 to step 9 are respectively performed; wherein the account pool corresponds to the third-party application one by one.
9. A readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the account allocation management method based on the account pool according to any one of claims 1 to 8 is implemented.
Citation Information
Cited By
Supplier system account management method and system
CN120856449A
