Account distribution and management method and system, and identity authentication method based on system

Abstract

The account number distribution and management method and system and the identity authentication method based on the system comprise the steps that a user initiates a fixed or temporary account number registration request through a mobile terminal, and a server responds, analyzes and processes the account number registration request and feeds back account number information; the account information of the fixed account comprises main account information and sub-account information, the main account information comprises a main account user name and a main account password, and the sub-account information comprises a sub-account user name, a sub-account password and a main account user name bound with the sub-account. According to the method and the device, the main account is generated based on the requirements of the users, and meanwhile, the preset number of sub-accounts are adaptively generated for the main account, so that the problem that multiple persons in the same team cannot log in the application platform by using the same account at the same time is effectively solved, when the requirements of the application platform are concentrated, the main account and the multiple sub-accounts can be respectively distributed to different users, and the user experience is improved. And simultaneous login and simultaneous use of multiple persons are realized, so that the use convenience of the user is greatly improved.

Description

Technical Field

[0001] The present invention relates to the field of data information technology, and in particular to an account allocation and management method and system based on artificial intelligence, and an identity authentication method based on the system. Background Art

[0002] With the development of informatization and resource integration, massive data resources or integrated platforms have become a necessity in all walks of life. In response to the needs of different industries, commercial application platforms that integrate multiple data resources or multiple business functions have emerged.

[0003] In actual operation, for the same application platform, most companies or teams will only purchase one account, and the entire company or team will use the same account to save economic costs; however, the same account cannot be logged in on different devices at the same time. During the concentrated period of projects or business, or when facing work with a tight schedule, the demands of various users for the application platform are concentrated, and the same account cannot meet the usage needs of the entire team. Account snatching occurs frequently, and the situation of passively waiting for other users to use the account seriously restricts the work efficiency of the entire team.

[0004] In addition, most commercial application platforms offer a trial function, which provides users with a temporary account for free use for a period of time to determine whether to purchase. However, this mechanism provides some users with a malicious way to save money. Some users frequently apply for temporary trial accounts, which is very unfair to the developers of the application platform. Summary of the invention

[0005] In order to solve the shortcomings of the existing technology, the present invention provides an account allocation and management method, in which a user initiates an account registration request through a mobile terminal, and a server responds, parses and processes the account registration request and feeds back account information; wherein, When a user initiates a fixed account registration request through a mobile terminal, the server responds, parses and processes the fixed account registration request, and feeds back the main account information and sub-account information, where the main account information includes the main account username and main account password, and the sub-account information includes the sub-account username, sub-account password and the main account username bound to the sub-account; When a temporary account registration request is initiated through a mobile terminal, the server responds, parses and processes the temporary account registration request and feeds back the temporary account information, which includes the temporary account username, temporary account password and validity period.

[0006] When a user initiates a fixed account registration request through a mobile terminal, the server responds, parses and processes the fixed account registration request, and feeds back the main account information and sub-account information, including the following steps: Step S1: The user initiates a fixed account registration request through a mobile terminal and enters the primary account username on the mobile terminal interface; Step S2: The server matches the main account username with the main account username, sub-account username and temporary account username stored in the database: if there is a match, the server feeds back duplicate username information to the mobile terminal and asks the user to re-enter the main account username; if there is no match, the server feeds back registration information to the mobile terminal and executes step S3; Step S3: The user enters the main account password and the number of sub-accounts on the mobile terminal interface; Step S4: The server intelligently generates a predetermined number of sub-accounts based on the master account username, master account password and the number of sub-accounts, and feeds back the master account username, master account password and each sub-account's sub-account username, sub-account password and the master account username bound to the sub-account to the mobile terminal.

[0007] Among them, in step S4, the server intelligently generates a predetermined number of sub-accounts according to the main account username, the main account password and the number of sub-accounts, including the following steps: Step S41: extracting letter elements and number elements from the main account username and the main account password respectively, and randomly mixing them n times to obtain n sub-account chains, where n is the number of sub-accounts input by the user in step S3; For each sub-account chain, perform the following operations: Step S42: randomly extracting two segments of a preset length from the sub-account chain to obtain an initial sub-account username and an initial sub-account password respectively; Step S43: Add a serial number to the initial sub-account username in order to obtain a sub-account username, wherein the serial number is a natural integer from 1 to n, and 1, 2, ... or n is added to the corresponding initial sub-account username according to the execution order of the sub-account chain; Step S44: Add a serial number to the beginning of the initial sub-account password in order, perform a hash operation on the initial sub-account password with the serial number, and randomly intercept a predetermined segment of the obtained hash value to obtain the sub-account password; wherein the serial number is a natural integer from 1 to n, and 1, 2... or n is added to the beginning of the corresponding initial sub-account password according to the execution order of the sub-account chain; Step S45: Save the correspondence between each sub-account username and the main account username.

[0008] When a user initiates a temporary account registration request through a mobile terminal, the server responds, parses and processes the temporary account registration request and feeds back temporary account information, including the following steps: Step S1: The user initiates a temporary account registration request through a mobile terminal, and the request carries the unique device identification information of the mobile terminal; Step Sm: The server verifies whether the database stores the time string information and request number information corresponding to the unique identifier of the device: If not, execute step Sn; If yes, then the time interval information is obtained based on the time string information, and whether the registration condition is met is determined based on the time interval information and the request number information: if the condition is met, step Sn is executed; if the condition is not met, the user is reminded that the temporary account cannot be registered, and the current process ends; Step Sn: The server generates a temporary account username and temporary account password based on the time tag and the device unique identifier, and feeds back the temporary account username, temporary account password and validity period to the mobile terminal, where the validity period is a fixed value pre-set in the server; the time tag is a character string formed based on the current year, month, and day information.

[0009] Among them, in the step Sn, the server generates a temporary account username and a temporary account password based on the time tag and the device unique identifier, and feeds back the temporary account username, temporary account password and validity period to the mobile terminal, including the following steps: Step Sn1: extracting letter elements and digital elements from the time tag and the device unique identifier respectively, and obtaining letter vectors and digital vectors respectively based on CLIP technology; Step Sn2: Add the letter vector and the number vector, perform a hash operation on the resulting vector sum, and obtain a temporary account chain; Step Sn3: randomly extract two segments of preset length from the temporary account chain to obtain the temporary account username and temporary account password respectively; Step Sn4: Match the temporary account username with the existing primary account username, sub-account username, and temporary account username in the database: If there is a match, re-execute step Sn3; If there is no match, the temporary account username, temporary account password and validity period will be fed back to the mobile terminal.

[0010] The present invention further provides an account allocation and management system for implementing the above-mentioned account allocation and management method, comprising a mobile terminal and a server, wherein the mobile terminal provides a platform for users to interact with the server, so that users can send account registration requests to the server through the mobile terminal and receive account registration results fed back by the server; The server is a server that the application platform relies on to provide services, including multiple distributed fixed account intelligent allocation management modules and a distributed temporary account intelligent allocation management module. Each distributed fixed account intelligent allocation management module is connected to a fixed account database, and the distributed temporary account intelligent allocation management module is connected to a temporary account database. Each distributed fixed account intelligent allocation management module is also connected to a shared database; wherein, The distributed fixed account intelligent allocation management module is used to respond to, parse and process the fixed account registration request initiated by the mobile terminal, generate a predetermined number of sub-account usernames and sub-account passwords bound to the main account based on the main account username and main account password obtained from the mobile terminal, and feedback the main account information and sub-account information to the mobile terminal, the main account information includes the main account username and the main account password, and the sub-account information includes the sub-account username, the sub-account password and the main account username bound to the sub-account; The distributed temporary account intelligent allocation management module is used to respond to, parse and process temporary account registration requests initiated by mobile terminals, generate temporary account usernames and temporary account passwords based on time tags and device unique identification information obtained from mobile terminals, and feedback temporary account information to mobile terminals. The temporary account information includes temporary account usernames, temporary account passwords and validity periods. The shared database is used to store the primary account username and the random salt value and hash value corresponding to the primary account password; The fixed account database is used to store the user names of each sub-account bound to the subordinate main account of the fixed account database, as well as the random salt value and hash value corresponding to each sub-account password; the temporary account database is used to store the temporary account user name, the random salt value and hash value corresponding to the temporary account password, and the time tag corresponding to the temporary account user name. The time tag is a character string formed by the year, month, and day information corresponding to the generation of the temporary account.

[0011] The present invention also provides an identity authentication method for an account allocation and management system, wherein a user initiates a request to log in to an application platform through a mobile terminal, and a server on which the application platform relies responds, parses and processes the login request, and feeds back a login result; When a user initiates a request to log in to the application platform with a fixed account master account through a mobile terminal, the server responds, parses and processes the fixed account master account login request and feeds back the login result; When a user initiates a request to log in to the application platform using a fixed account or sub-account through a mobile terminal, the server responds, parses and processes the fixed account or sub-account login request and feeds back the login result; When a user initiates a request to log in to the application platform with a temporary account through a mobile terminal, the server responds, parses and processes the temporary account login request and feeds back the login result.

[0012] When a user initiates a request to log in to the application platform with a fixed account master account through a mobile terminal, the server responds, parses and processes the fixed account master account login request and feeds back the login result, including the following steps: Step SA: The user enters the primary account username and primary account password through the mobile terminal; Step SB: The server receives the master account username and the master account password, and matches the master account username with the master account username stored in the shared database one by one: If there is a match, execute step SC; If there is no match, a login failure message will be fed back; Step SC: The server obtains the random salt value and hash value of the master account password corresponding to the master account username from the shared database, performs a hash operation on the master account password received in step SB based on the random salt value, and compares the hash value obtained by the operation with the hash value obtained from the shared database. If the comparison is consistent, a login success message is fed back; if it is inconsistent, a login failure message is fed back.

[0013] When a user initiates a request to log in to an application platform using a fixed account sub-account through a mobile terminal, the server responds, parses and processes the fixed account sub-account login request and feeds back the login result, including the following steps: Step Sa: The user enters the sub-account username, sub-account password, and the main account username bound to the sub-account through the mobile terminal; Step Sb: The server receives the sub-account username, sub-account password, and the main account username bound to the sub-account, and matches the main account username with the main account username stored in the shared database one by one: If there is a match, execute step Sc; If there is no match, a login failure message will be fed back; Step Sc: The server matches the fixed account database corresponding to the primary account username based on the matching result of the primary account username; Step Sd: The server matches the sub-account username with the sub-account username stored in the fixed account database one by one: If there is a match, execute step Se; If there is no match, a login failure message will be fed back; Step Se: The server obtains the random salt value and hash value of the sub-account password corresponding to the sub-account username from the fixed account database, performs a hash operation on the sub-account password received in step Sb based on the random salt value, and compares the hash value obtained by the operation with the hash value obtained from the fixed account database. If the comparison is consistent, a login success message is fed back; if it is inconsistent, a login failure message is fed back.

[0014] When a user initiates a request to log in to the application platform using a temporary account through a mobile terminal, the server responds, parses and processes the temporary account login request and feeds back the login result, including the following steps: Step SL: The user enters the temporary account username and temporary account password through the mobile terminal; Step SM: The server receives the temporary account username and temporary account password, and matches the temporary account username with the temporary account username stored in the temporary account database: If there is a match, execute step SN; If there is no match, a login failure message will be fed back; Step SN: The server obtains the random salt value and hash value of the temporary account password corresponding to the temporary account username from the temporary account database, performs a hash operation on the temporary account password received in step SM based on the random salt value, and compares the hash value obtained by the operation with the hash value obtained from the temporary account database. If the comparison is consistent, a login success message is fed back; if it is inconsistent, a login failure message is fed back.

[0015] Based on the needs of users, the present invention adaptively generates a predetermined number of sub-accounts for a main account while generating the main account, effectively solving the problem that multiple people in the same team cannot log in to the application platform at the same time using the same account. When the demand for the application platform is concentrated, the main account and multiple sub-accounts can be respectively allocated to different users, achieving the technical effect of multiple people logging in and using the application platform at the same time, greatly improving the user's convenience. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 : The fixed account allocation management method of the present invention.

[0017] Figure 2 : The temporary account allocation management method of the present invention.

[0018] Figure 3 : The artificial intelligence-based account allocation and management system of the present invention.

[0019] Figure 4 : The present invention serves an identity authentication method for an account allocation and management system based on artificial intelligence. DETAILED DESCRIPTION

[0020] In order to have a further understanding of the technical solution and beneficial effects of the present invention, the technical solution and beneficial effects produced by the present invention are described in detail below with reference to the accompanying drawings.

[0021] 1. Account Allocation and Management The present invention provides an account allocation and management method based on artificial intelligence, which is completed by the interaction between a mobile terminal and a server; a user initiates an account registration request through a mobile terminal, and the server responds, parses and processes the account registration request, and feeds back the account registration result.

[0022] The mobile terminal can be any device that can provide a medium for the application services of the application platform, such as a smart phone, tablet computer, laptop computer, desktop computer, etc. The server can be a business server or background server on which the application platform relies to provide application services. It can be an independent physical server or a server cluster or distributed system composed of multiple physical servers.

[0023] In the present invention, the so-called application platform can be a paid application platform that provides commercial services, such as various patent database platforms that integrate patent information for use in patent analysis; it can also be a transaction information platform that integrates transaction information for use in analyzing transaction trends; it can also be an application development platform that provides a development environment for use in developing, compiling or repairing software; the present invention is not limited here, and any application platform that can provide information assistance and resource integration for a certain type of industry falls within the scope of protection of the present invention.

[0024] The artificial intelligence-based account allocation and management method of the present invention can complete registration requests for fixed accounts and temporary accounts. A fixed account can be understood as a paid account with a longer validity period (such as one year), and a temporary account can be understood as a free account with a shorter validity period (such as one week) for users to try out.

[0025] 1. Allocation and management of fixed accounts Considering that the existing application platform is usually shared by several individuals, the same account cannot be logged in at the same time. When the resource demand is strong and the data processing task is heavy, the users of the shared application platform cannot complete the work at the same time. The present invention proposes a method for directly allocating the main account and the sub-accounts bound to the main account. Figure 1 As shown, the fixed account allocation management method of the present invention is shown, and its specific implementation method is as follows.

[0026] 1. The user initiates a fixed account registration request through a mobile terminal and enters the primary account username on the mobile terminal interface.

[0027] 2. The server matches the main account username with the main account username, sub-account username and temporary account username stored in the database: If there is a match, the server will feedback the duplicate username information to the mobile terminal and ask the user to re-enter the main account username; if there is no match, the server will feedback the registration information to the mobile terminal and execute step 3.

[0028] 3. The user enters the main account password and the number of sub-accounts on the mobile terminal interface.

[0029] The server generates sub-accounts and manages the main account and sub-accounts through the following steps: 4. Extract letter elements and number elements from the main account username and password respectively, randomly confuse them n times, and obtain n sub-account chains, where n is the number of sub-accounts entered by the user in step 3; For each sub-account chain, perform the following operations: 5. Randomly extract two paragraphs of preset length from the sub-account chain to obtain the initial sub-account username and initial sub-account password respectively; 6. Add the serial number to the initial sub-account username in order to obtain the sub-account username, and match the main account username with the main account username, sub-account username, and temporary account username stored in the database: if there is a match, re-execute step 5; if there is no match, execute step 7; wherein the serial number is a natural integer from 1 to n, and 1, 2... or n is added to the corresponding initial sub-account username according to the execution order of the sub-account chain; 7. Add serial numbers to the beginning of the initial sub-account password in order, perform hash operations on the initial sub-account password with serial numbers, and cut off a predetermined section of the obtained hash value to obtain the sub-account password; wherein the serial number is a natural integer from 1 to n, and 1, 2... or n is added to the beginning of the corresponding initial sub-account password according to the execution order of the sub-account chain; Assuming that the user needs to create three sub-accounts for the main account, the server first adds serial number 1 to the initial sub-account username to obtain the first sub-account username, then adds serial number 1 to the initial sub-account password, and performs a hash operation on the initial sub-account password with serial number 1, and cuts a predetermined section of the obtained hash value to obtain the sub-account password of the first sub-account; then repeats the above steps to obtain the second and third sub-account usernames and sub-account passwords in turn.

[0030] It should be noted that, as a platform that provides commercial services, the application platform can directly generate sub-accounts for users for the convenience of users. However, in actual use, if the number of sub-accounts is not restricted, users may apply for too many sub-accounts and resell them to other users. Therefore, the server can limit the number of sub-accounts under each main account, such as configuring the number of sub-accounts to not exceed 3.

[0031] 8. Save the correspondence between the user names of each sub-account and the user name of the main account. This save operation is achieved by creating ID numbers for the databases to which the main account and sub-account belong, and for the function modules that provide allocation management functions for the main account and sub-account, which will be described in detail later.

[0032] 9. The master account username, master account password, and each sub-account's sub-account username, sub-account password, and the master account username bound to the sub-account are fed back to the mobile terminal.

[0033] 10. Save the primary account username and the random salt value and hash value of the primary account password corresponding to the primary account username; save the sub-account username and the random salt value and hash value of the sub-account password corresponding to the sub-account username. This save operation is achieved by directly saving the corresponding data in the database to which the primary account and sub-account belong, which will be described in detail later.

[0034] Based on this, the present invention adaptively generates a predetermined number of sub-accounts for users based on their needs, effectively solving the problem that multiple people in the same team cannot log in to the application platform at the same time using the same account. When the demand for the application platform is concentrated, the main account and multiple sub-accounts can be assigned to different users respectively, achieving the technical effect of multiple people logging in and using it at the same time, greatly improving the user's convenience.

[0035] In addition, when allocating a sub-account, a sub-account username and a sub-account password are generated based on the main account username and the main account password. Since the main account username is unique in the server, the present invention adopts a method of randomly confusing the letter elements and the number elements in the main account username and the main account password to obtain a sub-account chain, and then splits the sub-account chain and adds the serial number of the sub-account in sequence. When the main account is determined, the serial number corresponding to the sub-account is unique. Therefore, the method of first randomly combining, adding the serial number, and finally performing a hash calculation is equivalent to providing a triple protection mechanism, which ensures the uniqueness of the generated sub-account username and the security of the sub-account password.

[0036] In the present invention, different operation permissions can also be assigned to the main account and the sub-account. For example, the sub-account only has the permission to use the basic services provided by the application platform, while the main account can view all the operation logs of the sub-account in the process of using the application platform, thereby realizing the monitoring of the sub-account. For different application platforms, the attributes of the operation log are different. Continuing with the examples given above: for the patent database platform, the operation log can be the patent information retrieval record and patent data export record conducted by the user; for the transaction information platform, the operation log can be the order record and transaction record; for the application development platform, the operation log can be the development, compilation record, software patch record, etc. In actual applications, the owner of the main account can be the project leader or the operation leader, and the owner of the sub-account can be the staff of the small team managed by the owner of the main account.

[0037] (II) Allocation and management of temporary accounts like Figure 2 As shown, the specific implementation method is as follows: 1. The user initiates a temporary account registration request through a mobile terminal, and the request carries the unique device identification information of the mobile terminal; 2. The server verifies whether the database contains the time string information and request count information corresponding to the unique identifier of the device: If not, proceed to step 3. In this case, it is equivalent to that the mobile terminal has never initiated a temporary account registration request; If yes, then obtain the time interval information based on the time string information, and determine whether the registration conditions are met based on the time interval information and the number of requests information: if the conditions are met, execute step 3; if the conditions are not met, remind the user that a temporary account cannot be registered, and end the current process.

[0038] In the present invention, the unique device identifier can be a device identifier carried in the device, assigned by the device manufacturer, or it can be a unique ID number that can identify device information and is calculated based on the hardware characteristics of the device according to an intelligent algorithm. The present invention is not limited here.

[0039] In the present invention, once a mobile terminal has initiated a temporary account registration request and the registration is successful, the server will store the time string information and request count information corresponding to the device unique identifier corresponding to the mobile terminal; when the mobile terminal initiates a temporary account registration request again, the server obtains the time interval information based on the time string information, and determines whether the registration conditions are met based on the time interval information and the request count information. The time interval information is the time interval between the last time a temporary account was allocated to the mobile terminal and the time when the mobile terminal initiated the temporary account registration request this time (calculated by the string corresponding to the time of the last temporary account allocation and the time string corresponding to the temporary account registration request initiated this time), and the request count information is the total number of requests for allocating temporary accounts to the mobile terminal before; in actual operation, the time interval must be greater than a specific value, and / or the request count must be less than a specific value before a temporary account can be allocated, so as to avoid the defect that some users frequently apply for temporary accounts and maliciously evade the purchase of fixed accounts.

[0040] In the present invention, the allocation of temporary accounts can be managed by storing key-value pairs in the remote dictionary service Redis. For any mobile terminal, after the first temporary account registration is successful, the server allocates and stores two key-value pairs Key-Value for it, where the key values ​​are the device unique identifier "device-ID", and the values ​​are the time string "string" and the number of requests "number", respectively, and the storage forms are (device-ID, string) and (device-ID, number). After that, the server will extract the current time information, convert it into a time string, assign it to "string" in the (device-ID, string) key-value pair, and initialize "number" to 1.

[0041] Afterwards, when the mobile terminal applies for a temporary account registration request again, the server obtains the current time information and the device unique identifier corresponding to the mobile terminal, and obtains the time string and request count information corresponding to the device unique identifier from the database, converts the current time information into a time string, calculates the time interval based on the two sets of time strings, and determines whether a temporary account can be allocated for it this time based on the time interval and request count. If a temporary account is successfully allocated again, the "string" in the (device-ID, string) key-value pair is updated to the time string corresponding to the time when the temporary account was successfully registered this time. At the same time, the "number" value in (device-ID, number) is updated through the function "number=reidsUtil.incBy(number,1)". The technical meaning of the above function is: add 1 to the existing "number" value as the new "number" value.

[0042] In the present invention, the time string consists of year, month, and day, and its format is a common format, such as 2025-01-03, 2025 / 01 / 03, etc., which is easily understood by those skilled in the art and is not limited here.

[0043] When the temporary account registration conditions are met, the server generates a temporary account and manages the temporary account through the following steps: 3. Extract letter elements and numeric elements from the time tag and the device unique identifier respectively, and obtain letter vectors and numeric vectors respectively based on CLIP technology; the time tag is a string formed based on the current year, month, and day information, that is, the string formed by the year, month, and day information when the server executes this step.

[0044] 4. Add the letter vector and the number vector, perform a hash operation on the resulting vector sum, and obtain a temporary account chain; 5. Randomly extract two paragraphs of preset length from the temporary account chain to obtain the temporary account username and temporary account password respectively; 6. Match the temporary account username with the existing main account username, sub-account username, and temporary account username in the database: If there is a match, re-execute step 5; If there is no match, the temporary account username, temporary account password and validity period are fed back to the mobile terminal. The validity period is a fixed value pre-set in the server, which is the trial period during which the temporary account can be used free of charge, such as one week.

[0045] 7. Save the temporary account username, the random salt value and hash value of the sub-account password corresponding to the temporary account username, and the time tag corresponding to the temporary account username. This time tag is a string formed by the year, month, and day information when the temporary account is successfully assigned. That is, this time tag is consistent with the time string corresponding to the device's unique identifier.

[0046] In summary, it should be noted that the present invention involves multiple time character strings when allocating and managing temporary accounts, and each time character string corresponds to a character string formed by the year, month, and day information when the current operation is executed.

[0047] At the same time, when allocating a temporary account, the present invention generates a temporary account username and a temporary account password based on the device unique identifier and the time tag. Since the device unique identifier is unique, and the present invention converts the letter elements and digital elements in the main device unique identifier and the time tag into vectors and then performs hash operations to obtain a temporary account chain, and finally randomly intercepts it, which is also equivalent to providing a triple protection mechanism, ensuring the uniqueness of the generated temporary account username and the security of the temporary account password.

[0048] In addition, when the present invention allocates and manages fixed accounts and temporary accounts, the stored main account username and the random salt value and hash value of the main account password corresponding to the main account username, as well as the sub-account username and the random salt value and hash value of the sub-account password corresponding to the sub-account username, as well as the temporary account username, the random salt value and hash value of the sub-account password corresponding to the temporary account username, and the time tag corresponding to the temporary account username, etc. are all stored in different databases (to be described in detail below) to achieve efficient authentication during identity authentication. At the same time, deploying different data resources in blocks also helps save server resources and facilitates system decoupling.

[0049] 2. Account Allocation and Management System Based on Artificial Intelligence like Figure 3As shown, the artificial intelligence-based account allocation and management system of the present invention serves the artificial intelligence-based account allocation and management method described above, including a mobile terminal and a server. The mobile terminal provides a platform for user-server interaction, allowing the user to send an account registration request to the server through the mobile terminal and receive the account registration result fed back by the server. The server also has an identity authentication function and a function of recording and storing user operation logs.

[0050] The server is a server that the application platform relies on to provide services, including multiple distributed fixed account intelligent allocation management modules and a distributed temporary account intelligent allocation management module. Each distributed fixed account intelligent allocation management module is connected to a fixed account database, and the distributed temporary account intelligent allocation management module is connected to a temporary account database. Each distributed fixed account intelligent allocation management module is also connected to a shared database; wherein, The distributed fixed account intelligent allocation management module is used to respond to, parse and process the fixed account registration request initiated by the mobile terminal, generate a predetermined number of sub-account usernames and sub-account passwords bound to the main account based on the main account username, main account password and number of sub-accounts obtained from the mobile terminal, and feedback the main account information and sub-account information to the mobile terminal, the main account information includes the main account username and the main account password, and the sub-account information includes the sub-account username, the sub-account password and the main account username bound to the sub-account; The distributed temporary account intelligent allocation management module is used to respond to, parse and process temporary account registration requests initiated by mobile terminals, generate temporary account usernames and temporary account passwords based on time tags and device unique identification information obtained from mobile terminals, and feedback temporary account information to mobile terminals. The temporary account information includes temporary account usernames, temporary account passwords and validity periods. The shared database is used to store the primary account username and the random salt value and hash value corresponding to the primary account password; The fixed account database is used to store the user names of each sub-account bound to the subordinate master account of the fixed account database and the random salt value and hash value corresponding to each sub-account password; The temporary account database is used to store temporary account usernames, random salt values ​​and hash values ​​corresponding to temporary account passwords, and time tags corresponding to temporary account usernames. The time tag is a string formed by the year, month, and day information corresponding to when the temporary account was generated.

[0051] It also includes an identity authentication module, which is connected to the shared database, the fixed account database and the temporary account database, and is used to authenticate the user's login information. The specific identity authentication mechanism will be described in detail below.

[0052] It also includes a log storage module for storing operation logs of the main account, sub-account or temporary account.

[0053] In the present invention, the distributed fixed account intelligent allocation management module responds to, parses and processes the fixed account registration request initiated by the mobile terminal, generates a predetermined number of sub-account usernames and sub-account passwords bound to the main account based on the main account username, main account password and number of sub-accounts obtained from the mobile terminal, and feeds back the main account information and sub-account information to the mobile terminal. The implementation steps include: 1. Receive the domain name of the main account entered by the user on the mobile terminal interface, and match the main account username with the main account username, sub-account username and temporary account username stored in the database: If there is a match, the duplicate username information is fed back to the mobile terminal, and the user is asked to re-enter the main account username; if there is no match, the registration information is fed back to the mobile terminal, and step 2 is executed.

[0054] 2. Receive the main account password and sub-account number entered by the user on the mobile terminal interface.

[0055] 3. Extract letter elements and number elements from the main account username and password respectively, randomly confuse them n times, and obtain n sub-account chains, where n is the number of sub-accounts entered by the user in step 3; For each sub-account chain, perform the following operations: 4. Randomly extract two paragraphs of preset length from the sub-account chain to obtain the initial sub-account username and initial sub-account password respectively; 5. Add the serial number to the initial sub-account username in order to obtain the sub-account username, and match the main account username with the main account username, sub-account username, and temporary account username stored in the database: if there is a match, re-execute step 4; if there is no match, execute step 6; where the serial number is a natural integer from 1 to n, and 1, 2... or n is added to the corresponding initial sub-account username according to the execution order of the sub-account chain; 6. Add a serial number to the beginning of the initial sub-account password in order, perform a hash operation on the initial sub-account password with the serial number, and cut a predetermined section of the obtained hash value to obtain the sub-account password; wherein the serial number is a natural integer from 1 to n, and 1, 2... or n is added to the beginning of the corresponding initial sub-account password according to the execution order of the sub-account chain; 7. Create an ID number and match it to the primary account, as well as the corresponding fixed account database and distributed fixed account intelligent allocation management system.

[0056] 8. Feedback the master account username, master account password, and each sub-account's sub-account username, sub-account password, and the master account username bound to the sub-account to the mobile terminal.

[0057] 9. Save the primary account username and the random salt value and hash value of the primary account password corresponding to the primary account username to the shared database.

[0058] 10. Save the sub-account username and the random salt value and hash value of the sub-account password corresponding to the sub-account username to the corresponding fixed account database.

[0059] In the present invention, the distributed temporary account intelligent allocation management module is used to respond to, parse and process the temporary account registration request initiated by the mobile terminal, generate a temporary account username and a temporary account password based on the time tag and the device unique identification information obtained from the mobile terminal, and feedback the temporary account information to the mobile terminal on the premise of meeting the conditions, including the following implementation steps: 1. Receive a temporary account registration request initiated by a user on a mobile terminal, and obtain the unique device identification information of the mobile terminal from the request; 2. Verify whether the temporary account database contains the time string information and request count information corresponding to the unique identifier of the device: If not, proceed to step 3; If yes, then obtain the time interval information based on the time string information, and determine whether the registration conditions are met based on the time interval information and the number of requests information: if the conditions are met, execute step 3; if the conditions are not met, remind the user that a temporary account cannot be registered, and end the current process.

[0060] 3. Extract letter elements and numeric elements from the time tag and the device unique identifier respectively, and obtain letter vectors and numeric vectors respectively based on CLIP technology; the time tag is a string formed based on the current year, month, and day information, that is, the string formed by the year, month, and day information when the server executes this step.

[0061] 4. Add the letter vector and the number vector, perform a hash operation on the resulting vector sum, and obtain a temporary account chain; 5. Randomly extract two paragraphs of preset length from the temporary account chain to obtain the temporary account username and temporary account password respectively; 6. Match the temporary account username with the existing main account username, sub-account username, and temporary account username in the database: If there is a match, re-execute step 5; If there is no match, the temporary account username, temporary account password and validity period will be fed back to the mobile terminal.

[0062] 7. Save the temporary account username, the random salt value and hash value of the sub-account password corresponding to the temporary account username, and the time tag corresponding to the temporary account username to the temporary account database. The time tag is a string formed by the year, month, and day information when the temporary account is successfully assigned. In the present invention, temporary accounts are grouped and managed based on time tags. The server detects time tags every day and clears the temporary accounts corresponding to the time tags that have expired.

[0063] In summary, in the present invention, when managing the main account, sub-account and temporary account, they are all managed in the form of groups. Sub-accounts belonging to the same main account belong to the same group, and temporary accounts with the same time tag belong to the same group. The relevant information of the accounts belonging to the same group is stored in the same database, and batch management of identity authentication, account disabling, account expiration, etc. can be achieved later. While providing each main account with multiple attached sub-accounts, it does not bring exponential resource consumption to the server, greatly improving management efficiency. In addition, the group management mode also ensures good decoupling of the system, which is convenient for performance optimization, resource detection and fault screening.

[0064] In the present invention, the primary account username and the random salt value and hash value of the primary account password corresponding to the primary account username, the sub-account username and the random salt value and hash value of the sub-account password corresponding to the sub-account username, and the temporary account username and the random salt value and hash value of the sub-account password corresponding to the temporary account username are stored in the corresponding database in the following form:<username,H,SALT> , where username is the corresponding main account username / sub-account username / temporary account username, H is the hash value obtained by hashing the corresponding main account password / sub-account password / temporary account password, and SALT is the random salt value assigned when hashing the corresponding main account password / sub-account password / temporary account password. When performing identity authentication later, the hash value is compared to determine whether the login is successful.

[0065] (III) Identity Authentication Method like Figure 4 As shown, the identity authentication method provided by the present invention serves the above-mentioned artificial intelligence-based account allocation and management system. Based on different account attributes, the present invention provides different identity authentication methods.

[0066] For the primary account: 1. The user enters the primary account username and password through the mobile terminal; 2. The server receives the master account username and password, and matches the master account username with the master account username stored in the shared database: If there is a match, go to step 3; If there is no match, a login failure message will be fed back; 3. The server obtains the random salt value and hash value of the primary account password corresponding to the primary account username from the shared database, performs a hash operation on the primary account password received in step 2 based on the random salt value, and compares the hash value obtained by the operation with the hash value obtained from the shared database. If the comparison is consistent, a successful login message is fed back; if it is inconsistent, a failed login message is fed back.

[0067] For sub-accounts: 1. The user enters the sub-account username, sub-account password and the main account username bound to the sub-account through a mobile terminal; 2. The server receives the sub-account username, sub-account password, and the main account username bound to the sub-account, and matches the main account username with the main account username stored in the shared database: If there is a match, go to step 3; If there is no match, a login failure message will be fed back; 3. Based on the matching result of the primary account username, the server matches the fixed account database corresponding to the primary account username; specifically, through the ID assigned to the primary account, the server matches the fixed account database that is consistent with its ID; 4. The server matches the sub-account username with the sub-account username stored in the fixed account database: If there is a match, go to step 5; If there is no match, a login failure message will be fed back; 5. The server obtains the random salt value and hash value of the sub-account password corresponding to the sub-account username from the fixed account database, performs a hash operation on the sub-account password received in step 2 based on the random salt value, and compares the hash value obtained by the operation with the hash value obtained from the fixed account database. If the comparison is consistent, a successful login message is fed back; if it is inconsistent, a failed login message is fed back.

[0068] For the application platform, the massive value corresponds to the number of main accounts, and for a specific main account, the number of sub-accounts is limited (not more than 10, otherwise there is a risk that users will resell the sub-accounts and affect the profitability of the application platform provider); therefore, the present invention first matches the main account, and then matches the sub-account in the corresponding fixed account database. In this way, the main work is still to match the main account. The present invention does not cause the workload of the server to increase exponentially with the number of sub-accounts during the identity authentication process due to the allocation of sub-accounts. It achieves the exponential growth of the number of accounts without affecting the server resource consumption and work efficiency, and facilitates user use.

[0069] For temporary accounts: 1. The user enters the temporary account username and temporary account password through the mobile terminal; 2. The server receives the temporary account username and temporary account password, and matches the temporary account username with the temporary account username stored in the temporary account database: If there is a match, go to step 3; If there is no match, a login failure message will be fed back; 3. The server obtains the random salt value and hash value of the temporary account password corresponding to the temporary account username from the temporary account database, performs a hash operation on the temporary account password received in step 2 based on the random salt value, and compares the hash value obtained by the operation with the hash value obtained from the temporary account database. If the comparison is consistent, a successful login message is fed back; if it is inconsistent, a failed login message is fed back.

[0070] Although the present invention has been described using the above preferred embodiments, they are not intended to limit the scope of protection of the present invention. Any person skilled in the art may make various changes and modifications to the above embodiments without departing from the spirit and scope of the present invention. The scope of protection of the present invention shall be based on the definition of the claims.

Claims

1. Account allocation and management method, characterized by: The user initiates an account registration request through a mobile terminal, and the server responds, parses and processes the account registration request and feeds back the account information; When a user initiates a fixed account registration request through a mobile terminal, the server responds, parses and processes the fixed account registration request, and feeds back the main account information and sub-account information, where the main account information includes the main account username and main account password, and the sub-account information includes the sub-account username, sub-account password and the main account username bound to the sub-account; When a temporary account registration request is initiated through a mobile terminal, the server responds, parses and processes the temporary account registration request and feeds back the temporary account information, which includes the temporary account username, temporary account password and validity period.

2. The account allocation and management method according to claim 1, characterized in that: When a user initiates a fixed account registration request through a mobile terminal, the server responds, parses and processes the fixed account registration request, and feeds back the main account information and sub-account information, including the following steps: Step S1: The user initiates a fixed account registration request through a mobile terminal and enters the primary account username on the mobile terminal interface; Step S2: The server matches the main account username with the main account username, sub-account username and temporary account username stored in the database: if there is a match, the server feeds back duplicate username information to the mobile terminal and asks the user to re-enter the main account username; if there is no match, the server feeds back registration information to the mobile terminal and executes step S3; Step S3: The user enters the main account password and the number of sub-accounts on the mobile terminal interface; Step S4: The server intelligently generates a predetermined number of sub-accounts based on the master account username, master account password and the number of sub-accounts, and feeds back the master account username, master account password and each sub-account's sub-account username, sub-account password and the master account username bound to the sub-account to the mobile terminal.

3. The account allocation and management method according to claim 2, characterized in that: In step S4, the server intelligently generates a predetermined number of sub-accounts based on the main account username, the main account password and the number of sub-accounts, including the following steps: Step S41: extracting letter elements and number elements from the main account username and the main account password respectively, and randomly mixing them n times to obtain n sub-account chains, where n is the number of sub-accounts input by the user in step S3; For each sub-account chain, perform the following operations: Step S42: randomly extracting two segments of a preset length from the sub-account chain to obtain an initial sub-account username and an initial sub-account password respectively; Step S43: Add a serial number to the initial sub-account username in order to obtain a sub-account username, wherein the serial number is a natural integer from 1 to n, and 1, 2, ... or n is added to the corresponding initial sub-account username according to the execution order of the sub-account chain; Step S44: Add a serial number to the beginning of the initial sub-account password in order, perform a hash operation on the initial sub-account password with the serial number, and randomly intercept a predetermined segment of the obtained hash value to obtain the sub-account password; wherein the serial number is a natural integer from 1 to n, and 1, 2... or n is added to the beginning of the corresponding initial sub-account password according to the execution order of the sub-account chain; Step S45: Save the correspondence between each sub-account username and the main account username.

4. The account allocation and management method according to claim 1, characterized in that: When a user initiates a temporary account registration request through a mobile terminal, the server responds, parses and processes the temporary account registration request and feeds back the temporary account information, including the following steps: Step S1: The user initiates a temporary account registration request through a mobile terminal, and the request carries the unique device identification information of the mobile terminal; Step Sm: The server verifies whether the database stores the time string information and request number information corresponding to the unique identifier of the device: If not, execute step Sn; If yes, then obtain the time interval information based on the time string information, and determine whether the registration condition is met based on the time interval information and the request number information: if the condition is met, execute step Sn; If the conditions are not met, the user is reminded that they cannot register a temporary account and the current process ends; Step Sn: The server generates a temporary account username and temporary account password based on the time tag and the device unique identifier, and feeds back the temporary account username, temporary account password and validity period to the mobile terminal, where the validity period is a fixed value pre-set in the server; the time tag is a character string formed based on the current year, month, and day information.

5. The account allocation and management method according to claim 4, characterized in that: In the step Sn, the server generates a temporary account username and a temporary account password based on the time tag and the device unique identifier, and feeds back the temporary account username, temporary account password and validity period to the mobile terminal, including the following steps: Step Sn1: extracting letter elements and digital elements from the time tag and the device unique identifier respectively, and obtaining letter vectors and digital vectors respectively based on CLIP technology; Step Sn2: Add the letter vector and the number vector, perform a hash operation on the resulting vector sum, and obtain a temporary account chain; Step Sn3: randomly extract two segments of preset length from the temporary account chain to obtain the temporary account username and temporary account password respectively; Step Sn4: Match the temporary account username with the existing primary account username, sub-account username, and temporary account username in the database: If there is a match, re-execute step Sn3; If there is no match, the temporary account username, temporary account password and validity period will be fed back to the mobile terminal.

6. An account allocation and management system, used to implement the account allocation and management method according to claim 1, characterized in that: It includes a mobile terminal and a server. The mobile terminal provides a platform for users to interact with the server, allowing users to send account registration requests to the server through the mobile terminal and receive account registration results fed back by the server. The server is a server that the application platform relies on to provide services, including multiple distributed fixed account intelligent allocation management modules and a distributed temporary account intelligent allocation management module. Each distributed fixed account intelligent allocation management module is connected to a fixed account database, and the distributed temporary account intelligent allocation management module is connected to a temporary account database. Each distributed fixed account intelligent allocation management module is also connected to a shared database; wherein, The distributed fixed account intelligent allocation management module is used to respond to, parse and process the fixed account registration request initiated by the mobile terminal, generate a predetermined number of sub-account usernames and sub-account passwords bound to the main account based on the main account username and main account password obtained from the mobile terminal, and feedback the main account information and sub-account information to the mobile terminal, the main account information includes the main account username and the main account password, and the sub-account information includes the sub-account username, the sub-account password and the main account username bound to the sub-account; The distributed temporary account intelligent allocation management module is used to respond to, parse and process temporary account registration requests initiated by mobile terminals, generate temporary account usernames and temporary account passwords based on time tags and device unique identification information obtained from mobile terminals, and feedback temporary account information to mobile terminals. The temporary account information includes temporary account usernames, temporary account passwords and validity periods. The shared database is used to store the primary account username and the random salt value and hash value corresponding to the primary account password; The fixed account database is used to store the user names of each sub-account bound to the subordinate main account of the fixed account database, as well as the random salt value and hash value corresponding to each sub-account password; the temporary account database is used to store the temporary account user name, the random salt value and hash value corresponding to the temporary account password, and the time tag corresponding to the temporary account user name. The time tag is a character string formed by the year, month, and day information corresponding to the generation of the temporary account.

7. The identity authentication method based on the account allocation and management system of claim 6 is characterized by: The user initiates a request to log in to the application platform through the mobile terminal. The server on which the application platform relies responds, parses and processes the login request and feeds back the login result. When a user initiates a request to log in to the application platform with a fixed account master account through a mobile terminal, the server responds, parses and processes the fixed account master account login request and feeds back the login result; When a user initiates a request to log in to the application platform using a fixed account or sub-account through a mobile terminal, the server responds, parses and processes the fixed account or sub-account login request and feeds back the login result; When a user initiates a request to log in to the application platform with a temporary account through a mobile terminal, the server responds, parses and processes the temporary account login request and feeds back the login result.

8. The identity authentication method for the account allocation and management system as claimed in claim 6, characterized in that: When a user initiates a request to log in to the application platform with a fixed account master account through a mobile terminal, the server responds, parses and processes the fixed account master account login request and feeds back the login result, including the following steps: Step SA: The user enters the primary account username and primary account password through the mobile terminal; Step SB: The server receives the master account username and the master account password, and matches the master account username with the master account username stored in the shared database one by one: If there is a match, execute step SC; If there is no match, a login failure message will be fed back; Step SC: The server obtains the random salt value and hash value of the master account password corresponding to the master account username from the shared database, performs a hash operation on the master account password received in step SB based on the random salt value, and compares the hash value obtained by the operation with the hash value obtained from the shared database. If the comparison is consistent, a login success message is fed back; if it is inconsistent, a login failure message is fed back.

9. The identity authentication method for the account allocation and management system as claimed in claim 6, characterized in that: When a user initiates a request to log in to the application platform using a fixed account sub-account through a mobile terminal, the server responds, parses and processes the fixed account sub-account login request and feeds back the login result, including the following steps: Step Sa: The user enters the sub-account username, sub-account password, and the main account username bound to the sub-account through the mobile terminal; Step Sb: The server receives the sub-account username, sub-account password, and the main account username bound to the sub-account, and matches the main account username with the main account username stored in the shared database one by one: If there is a match, execute step Sc; If there is no match, a login failure message will be fed back; Step Sc: The server matches the fixed account database corresponding to the primary account username based on the matching result of the primary account username; Step Sd: The server matches the sub-account username with the sub-account username stored in the fixed account database one by one: If there is a match, execute step Se; If there is no match, a login failure message will be fed back; Step Se: The server obtains the random salt value and hash value of the sub-account password corresponding to the sub-account username from the fixed account database, performs a hash operation on the sub-account password received in step Sb based on the random salt value, and compares the hash value obtained by the operation with the hash value obtained from the fixed account database. If the comparison is consistent, a login success message is fed back; if it is inconsistent, a login failure message is fed back.

10. The identity authentication method for account allocation and management system as claimed in claim 6, characterized in that: When a user initiates a request to log in to the application platform using a temporary account through a mobile terminal, the server responds, parses and processes the temporary account login request and feeds back the login result, including the following steps: Step SL: The user enters the temporary account username and temporary account password through the mobile terminal; Step SM: The server receives the temporary account username and temporary account password, and matches the temporary account username with the temporary account username stored in the temporary account database: If there is a match, execute step SN; If there is no match, a login failure message will be fed back; Step SN: The server obtains the random salt value and hash value of the temporary account password corresponding to the temporary account username from the temporary account database, performs a hash operation on the temporary account password received in step SM based on the random salt value, and compares the hash value obtained by the operation with the hash value obtained from the temporary account database. If the comparison is consistent, a login success message is fed back; if it is inconsistent, a login failure message is fed back.

Images