WO2019184120A1

WO2019184120A1 - Account management method and apparatus, terminal device, and storage medium

Info

Publication number: WO2019184120A1
Application number: PCT/CN2018/094191
Authority: WO
Inventors: 叶力
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-03-29
Filing date: 2018-07-03
Publication date: 2019-10-03
Also published as: CN108564339A; CN108564339B

Abstract

Disclosed are an account management method and apparatus, a terminal device, and a storage medium. The account management method comprises the following steps: if a registration request for a target sub-service system from a user is detected, obtaining identification information of an account to be registered according to the registration request, and then searching for the identification information in a group account system; and if the identification information is queried in a sub-service system account table and not queried in a general account table, supplementing basic user information required by the target sub-service system, and upgrading the account to be registered to a group general account, thereby enabling the user to log into all group sub-service systems by means of the account to be registered. In this way, the efficiency of user login to a group service system is improved; in addition, server data redundancy caused by a large amount of account information generated by repeated registration in different sub-service systems is relieved, and the efficiency of server maintenance is improved.

Description

Account management method, device, terminal device and storage medium

This application is based on the Chinese Patent Application No. 201810268440.3 filed on March 29, 2018, entitled "An Account Management Method, Apparatus, Terminal Equipment, and Storage Medium", and claims priority.

Technical field

The present application relates to the field of computer technologies, and in particular, to an account management method, apparatus, terminal device, and storage medium.

Background technique

At present, with the globalization of the economy and the pace of China's opening up to the outside world, many group companies have developed rapidly. These group companies have different sub-business units to manage different business types. Therefore, each sub-business system has its own independence. The account system, with the further development of the group, may generate more sub-business systems.

When users use these sub-service systems of the group for the first time, they need to apply for the account corresponding to the sub-service system. If multiple sub-service systems are used, the user needs to open the accounts of multiple sub-service systems, and the process of opening the account is cumbersome. Therefore, the user needs to perform registration operations frequently, and a large amount of repeated account information also causes redundancy of server data, which brings inconvenience to the maintenance of the server.

Summary of the invention

The embodiment of the present invention provides an account management method, which solves the problem that the user repeatedly registers the different sub-service systems, resulting in cumbersome login operation, low efficiency, and a large number of duplicate account information, which causes server data redundancy and server maintenance inconvenience.

In a first aspect, an embodiment of the present application provides an account management method, including:

And if the registration request of the target sub-service system is detected, obtaining identity identification information of the account to be registered according to the registration request, wherein the target sub-service system is subordinate to the group sub-service system, and the group sub-service system is at least Contains two sub-business systems;

Locating the identity identification information in the group account system, wherein the group account system includes a group general account table and a group sub-service system account table, and the group sub-service account table includes at least two sub-service system account tables;

If the identity identification information is queried in the sub-service system account table, and the identity identification information is not queried in the universal account table, supplement the basic user information required by the target sub-service system, and The account to be registered is upgraded to a group general account;

The target sub-service system is logged into using the group general account.

In a second aspect, an embodiment of the present application provides an account management apparatus, including:

An identity information obtaining module, configured to acquire, according to the registration request, identity identification information of an account to be registered, where the target sub-service system belongs to the group sub-service system, if the registration request of the target sub-service system is detected by the user The group sub-business system includes at least two sub-business systems;

The identity information query module is configured to search the identity information in the group account system, where the group account system includes a group general account table and a group sub-service system account table, and the group sub-service account table includes at least two Sub-business system account table;

a group general account upgrade module, configured to: if the identity identification information is queried in the sub-service system account table, and the identity identification information is not queried in the general account table, supplement the target sub-service system Basic user information required, and the account to be registered is upgraded to a group general account;

A universal account login verification module is configured to log in to the target sub-service system using the group universal account.

In a third aspect, an embodiment of the present application provides a terminal device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, where the processor executes the computer The steps of the account management method are implemented when the instruction is read.

In a fourth aspect, the embodiment of the present application provides one or more non-volatile readable storage media storing computer readable instructions, when the computer readable instructions are executed by one or more processors, such that the one or A plurality of processors execute the steps of the account management method.

The details of one or more embodiments of the present invention are set forth in the accompanying drawings and the description of the claims.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application. Other drawings may also be obtained from those of ordinary skill in the art based on these drawings without the inventive labor.

1 is a flowchart of an account management method provided in Embodiment 1 of the present application;

2 is a flowchart of an implementation of step S2 in the account management method provided in Embodiment 1 of the present application;

3 is a flowchart of an implementation of step S22 in the account management method provided in Embodiment 1 of the present application;

4 is a schematic diagram of an account management apparatus provided in Embodiment 2 of the present application;

FIG. 5 is a schematic diagram of a terminal device according to Embodiment 4 of the present application.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

Example 1

Please refer to FIG. 1. FIG. 1 shows an implementation flow of an account management method provided by this embodiment. Details are as follows:

S1: If the registration request of the target sub-service system is detected, the identity information of the account to be registered is obtained according to the registration request, wherein the target sub-service system belongs to the group sub-service system, and the group sub-service system includes at least two sub-services. business system.

Specifically, when the user registers the target sub-service system, the client sends a Request object to the server, and after receiving the Request object, the server uses the string query method to obtain the registration of the target sub-service system. Register the identity information of the account.

The Request object sends a request from the client to the server, including the information submitted by the user and the cookie information of the client. The cookie information is data information stored by the server on the local terminal of the user in order to identify the identity of the user and perform session tracking. The client can submit data via a HyperText Markup Language (HTML) form or by providing parameters after the page address.

The identity information is a certificate for authenticating the user identity, including but not limited to: name, ID number, mobile phone number, and email address.

S2: Find the identity information of the account to be registered in the group account system, wherein the group account system includes a group general account table and a group sub-service system account table, and the group sub-service account table includes at least two sub-service system account tables.

Specifically, each group sub-service system has an independent sub-service system account table, and the group account system includes all group sub-service system account tables and group common account tables, and the identity identifier obtained in step S1 is obtained in the group account system. The information is queried to get the query result.

The group general account table includes identity identification information, a password, and all basic data fields, and a sub-service system account table includes an account number, a password, and a basic data field required by the sub-service system, and the sub-service system The account number is any one of the identity information, and the user basic data field required by the child service system is part of all the basic data fields of the user, that is, the field included in the sub-service system account table is a sub-field of the group common account table. set.

For example, in a specific embodiment, Table 1 shows the contents of the group general account table, and the group general account table includes: a user number, a user name, a password, an ID card number, a mobile phone number, and a user level. Table 2 shows The first sub-service system account table, Table 3 shows the contents of the second sub-service system account table, wherein the first sub-service system account table includes: user name, password and mobile phone number, and the second sub-service system account table Includes: user name, password, and user level.

Table I

Table II

Table 3

It is worth noting that the contents of all the basic data fields in the group's general account table can be empty.

S3: If the identity information of the account to be registered is queried in the sub-service system account table, and the identity information is not queried in the general account table, the basic user information required by the target sub-service system is supplemented and will be The registered account is upgraded to a group general account.

Specifically, if the query result in step S2 is that the identity identification information is queried in a sub-service system account table, and the identity identification information is not queried in the universal account table, that is, the user uses the identity identification information in other sub-services. The registration in the system guides the user to supplement the basic user information required by the target sub-service system, and then upgrades the account to be registered into a group general account and deposits it into the group general account table.

The specific process of guiding the user to supplement the basic user information required by the target sub-service system, and then upgrading the identity identification information into a group general account and depositing it into the group common account table is as follows:

Obtaining the field set A included in the basic user information required by the target sub-service system, and acquiring the field set B of the basic user information included in the sub-service system account table;

Comparing and analyzing the field set C belonging to the field set A but not belonging to the field set B, that is, the field set C is the relative complement of the field set A with respect to the field set B, expressed as: C=A-B;

Pushing the information to the user to complete the table, which contains all the fields in the field set C;

After receiving the user's information perfect form submission request, the content of the field in the field set C supplemented by the user is checked, and the information is supplemented successfully, otherwise the information supplementation is deemed to be failed;

If the information is successfully supplemented, the sub-service system account with the same account identity information to be registered is upgraded to the group general account, and the field content supplemented by the user is entered into the group general account, and the group general account is deposited into the group. In the general account table.

If the information is not replenished, a reminder is sent to the user, the reason for the failure is reported, and the step is jumped to the step of pushing the information to the user.

For example, in a specific implementation, the target sub-service system account table includes a field set A of {user name, password, ID number, mobile phone number}, and a field included in the sub-service system M account table containing the identity information. Set B is {user name, password, user level}. By comparison analysis, the field set C in this example is {ID number, mobile phone number}, and then pushes the user with "ID card number" and "mobile phone number". The information perfection table of the fields, after receiving the request of the user to submit the information perfect table, the content matching the contents of the "ID card number" and the "mobile phone number" in the information perfection table is regularly matched and matched. After successful, extract the account information corresponding to the identity information in the M account table of the child service system, and associate with the content of the user's perfect "ID card number" and "mobile phone number" to obtain the group general account, and Deposit the group's general account into the group's general account form.

S4: Log in to the target sub-business system using the group general account.

In the embodiment of the present application, the description of the identity identification information in step S1 indicates that the identity identification information includes, but is not limited to, a name, an ID card number, a mobile phone number, and a mailbox. When logging in to the target sub-service system, the user selects according to preferences. Any identity information is logged in as the account name. After receiving the login request from the user, the target sub-service system performs a regular match on the account name, determines the type of the identity information to which the account name belongs, and then verifies the identity information. If the verification is passed, jump to the interface after login.

In the embodiment corresponding to FIG. 1, when the registration request of the target sub-service system is detected by the user, the identity identification information of the account to be registered is obtained according to the registration request, and the identity identification information is searched in the group account system, if If the identity information is queried in the sub-service system account table, and the identity information is not queried in the general account table, the account to be registered is directly upgraded to the group general account, so that the user can log in to all groups through the account to be registered. The sub-service system improves the efficiency of the user's login to the group's business system. At the same time, it also alleviates the server data redundancy caused by the large amount of account information generated by repeated registration of different sub-service systems, and improves the efficiency of server maintenance.

Next, on the basis of the corresponding embodiment of FIG. 1, the specific implementation method for finding the identity identification information of the account to be registered in the group account system mentioned in step S2 is detailed by a specific embodiment. Description.

Referring to FIG. 2, FIG. 2 shows a specific implementation process of step S2 provided by the embodiment of the present application, which is described in detail as follows:

S21: Detect the identity information of the registered account based on the preset regular expression, and obtain the type of the identity information.

Specifically, after the identity information is obtained, the type identification of the identity information of the registered account is performed by using a preset regular expression. The identification information is at least one of a mobile phone number, an ID card number, an email address, and a name, but is not limited thereto. The identity identification information may further include other features for distinguishing the user identity, which may be specifically set according to actual application requirements. There are no restrictions here.

The following is a detailed description of the regular expressions of the four identification information of the mobile phone number, the ID number, the mailbox and the name.

a) The regular expression of the mobile phone number. The current domestic mobile phone number is mainly composed of 11 digits. The first 3 digits contain specific information, and the regular expression is:

^1(3[0-9]|4[5,7]|5((?!4)[0-9])|7(0|1|[6-8])|8[0-9] )\d{8}$

Wherein the symbol "^" indicates the beginning of the match, and the symbol "$" indicates the end of the match to confirm that no other characters can be followed. “|” means or, “[0-9]” “[5,7]” means any one of the data values in the range of “[]”, “(?!4)[0-9]” means 0 -9 range excludes any other integers other than 4, "\d" is an expression for positive values, indicating any one of all integers in the range of 0-9, understandably, "\d{8 } means that 8 integers ranging from 0-9 are selected.

b) The regular expression of the mailbox, the basic format of the mailbox is "name@domain name", and its regular expression is:

^[A-Za-z0-9\u4e00-\u9fa5]+@[a-zA-Z0-9_-]+(\.[a-zA-Z0-9])+$

Among them, "A-Za-z0-9" and "\u4e00-\u9fa5" use unicode encoding, "A-Za-z0-9" means 0-9 digits and az uppercase and lowercase letters in unicode encoding," \u4e00-\u9fa5" means all Chinese characters in unicode encoding, and "+" means at least once.

c) The regular expression of the ID card number, the mainland China ID card number is generally composed of 15 digits, 18 digits or "17 digits X". The regular expression is:

(^\d{15}$|^\d{18}$|^\d{17}(\d|X|x)$)

d) The regular expression of the name, the name of the Chinese citizen's name is generally two to five words in Chinese, but some minority names are separated by a dot "·", and the regular expression is:

^[\u4E00-\u9FA5]{2,5}(?:·[\u4E00-\u9FA5]{2,5})$

For example, in a specific implementation, the acquired identity information is “15600002266”, and the type of the identity information is identified as a mobile phone number by a preset regular expression matching.

S22: Determine a query range from the group common account table and the sub-service system account table according to the type of the identity identification information, and query the identity identification information in the query scope.

Specifically, according to the type of the identity identification information determined in step S21, in the fields of the group general account table and the sub-service system account table, find the fields included in the type, and search for the identity identification information in the fields. Get the query results.

In the embodiment corresponding to FIG. 2, the identity identification information is detected based on a preset regular expression, and the type of the identity identification information is obtained, and according to the type of the identity identification information, the group common account table and the sub-service system are obtained. The scope of the query is determined in the account table, and the identity information is queried in the scope of the query, and the query time is reduced by narrowing the scope of the query, thereby improving the efficiency of the query.

Next, based on the corresponding embodiment of FIG. 2, the type of the identity identification information mentioned in step S22 is determined from the group general account table and the sub-service system account table by a specific embodiment. The scope of the query is described in detail, and the specific implementation method for querying the identity information in the query scope is described in detail.

Referring to FIG. 3, FIG. 3 shows a specific implementation process of step S22 provided by the embodiment of the present application, which is described in detail as follows:

S221: Obtain a field for identity identification in the group common account table and the sub-business system account table.

In the embodiment of the present application, there is a group general account table and at least two sub-service system account tables, and the group common account table and each sub-service system account table respectively use respective preset identity information as the identity identifier when the business system logs in. Is the field for the user to log in to the account name of the sub-business system. For example, in the first sub-service system account table, the third sub-service system account, and the fifth sub-service system account table, the name is used as the identity field, and the second sub-service system account table and the fourth sub-service system account table are used. In the middle, use the mobile phone number as the identity field.

S222: If the field attribute is the same as the type of the identity information in the field for the identity identifier, the queried field is used as the first query field.

Specifically, in step S221, a group common account table and a field for identifying an account name in each sub-service system account table are obtained, and the fields used to identify the account name are filtered to find out the type of the identity information. The same field, these fields are used as the first query field. In this process, the query range of the account name field is narrowed, and the query efficiency is improved.

For example, in a specific implementation, the obtained identity information is: “13600002266”, and the regular matching of step S21 is performed, and the type of the identity information is obtained as the mobile phone number, and the first sub-service system account in step S221 is used. For example, the table to the fifth sub-service system account table, wherein the mobile phone number is used as the identity field, and the second sub-service system account table and the fourth sub-service system account table are used, and the identity field in the two account tables is used as The first query field.

S223: Obtain a first query scope, where the first query scope is content included in the first query field.

Specifically, the content included in each field in the first query field is obtained, and the content is used as the first query range.

S224: Query the identity information in the first query scope.

In the embodiment of the present application, the first query scope includes at least one group general account table or a sub-service system account table, and the field used by the account table in the first query scope for identity identification is consistent with the type of the identity identification information, and each The field used for identity identification contains multiple pieces of data, which are queried in the first scope, specifically, multiple pieces of data contained in the field used for identity identification in the first scope to find out whether the identity exists. The identification information, if the identity information exists, obtains the query result and ends the query process. If the identity information does not exist, the process proceeds to step S225 to perform the query operation.

Taking the sub-service system B account table and the sub-service system D account table of step S222 as an example, the two account tables belong to the first query range. In the mobile phone number field, the sub-service system B account table contains 33,000 data. The sub-service system D account table contains 56,000 data, and contains a total of 89000 data. When the user identification information is queried in the first query range, only the 89,000 data needs to be queried for the identity information. It does not need to search in other fields, which improves the efficiency of the query.

S225: If the identity information is not queried in the first query scope, the acquiring the group common account table and the sub-service system account table do not include the remaining fields of the first query field.

Specifically, if the identity information is not queried in the first query range, the remaining account table needs to be further queried, and the field used for the identity in the remaining account table has been verified with the identity in step S221. The identification information is inconsistent, so only the fields in the remaining account table that are not used for the identity identification need to be obtained, and the obtained fields are the remaining fields.

The remaining account table refers to the group common account table or the sub-business system account table in the group common account table and each sub-service system account table, which does not include the first query field.

It can be understood that, since the identity information is not queried in the first query field in the first scope, the other identifiers in the first range do not exist, and the account list in the first scope is subsequently There will be no query in the query.

Taking the sub-service system A account table in step S221 and step S224 to the sub-service system E account table as an example, wherein the first query field is a field for the identity number of the mobile phone number, and then the qualified condition is found. A query scope sub-service system B account table and a sub-service system D account table, the identity information "13600002266" is not queried in the first scope, and the sub-service system A account table, the sub-service system C account table and the sub-services are found. The fields in the system E account table that are not used for identity identification are used as the remaining fields to perform corresponding searches within these fields.

S226: Acquire a second query field, where the second query field is a field with the same field name as the identity identifier to be registered in the remaining fields.

Specifically, in the remaining fields determined in step S225, a field having the same field name as the identity information type is searched for as the second query field. The specific process is as follows: Step S222, to avoid repeated cumbersome, it will not be specifically described herein.

S227: Obtain a second query scope, where the second query scope is content included in the second query field.

Specifically, the content included in each field in the second query field is obtained, and the content is used as the second query range.

S228: Query the identity information in the second query scope.

Specifically, the second query field is queried for the second query field in the step S226. The specific query process is as described in step S224.

It is worth noting that in this query, whether or not the identity information is queried, the result of the query is used as the final query result.

In the embodiment corresponding to FIG. 3, the first query field is obtained by obtaining the fields for identifying the identity in the common account table and the sub-service system account table, and as the first query field in the fields corresponding to the identity information. All the contents are used as the first query range, and then the first search is performed within the first query range. If the identity information is queried, the query result is recorded and the query is terminated. If the identity information is not queried, Then, the fields in the remaining account table that are not used for the identity identifier are obtained, and if the identifier information type is consistent in the fields, the field is used as the second query field, and then all the second query fields are The content is queried as the second query scope, and the query result is used as the final query result, which is divided into two queries, each narrowing the scope, and improving the query efficiency.

On the basis of any of the corresponding embodiments of FIG. 1 to FIG. 3, after the identifier information is searched in the group account system mentioned in step S2, the account management method further includes:

If the identity information of the account to be registered is queried in the general account table, the group general account corresponding to the identity information is obtained, and an update operation is performed on the group general account, and the update operation is to add the target to the group general account. Basic user information required by the business system. In the embodiment of the present application, if the query is performed in step S2, the identity identification information is queried in the group general account table, that is, the identity identification information is registered in the group general account, and the target sub-service system is required. The basic user information is compared with the group's general account, and the information to be updated is updated and updated.

The specific process of comparing the basic user information required in the target sub-service system with the general account of the group, obtaining the information to be updated, and updating is as follows:

Obtaining the field set D included in the basic user information required by the target sub-service system, and acquiring the field set E that is not empty with the contents of the group common account;

Comparing and analyzing the field set F belonging to the field set D but not belonging to the field set E, that is, the field set F is the relative complement of the field set E with respect to the field set E, expressed as: F=D-E;

Pushing the information to the user to complete the table, which contains all the fields in the field set F;

After receiving the user's information perfect form submission request, the content of the field in the field set F supplemented by the user is checked, and the information is added successfully, and the information supplementation is considered successful; otherwise, the information supplementation failure is considered;

If the information is successfully replenished, the supplemental information is entered into the group's general account.

In this embodiment, by analyzing the result of the query in step S2, if the identity identification information is queried in the general account table, the group general account corresponding to the identity identification information is acquired, and an update operation is performed on the group general account, so that The user can add the user basic data required by the target sub-service system to the original group general account, and then log in to use the target sub-service system through the group general account, thereby improving the efficiency of the user logging into the group business system, and simultaneously improving the efficiency of the user logging into the group business system. It also avoids the problem of database data redundancy caused by repeated registrations, and improves the efficiency of server management.

If the identity information of the account to be registered is not queried in both the general account table and the sub-service system account table, the user is guided to use the identity information to register the group general account.

Specifically, if the identity information is not queried in the group general account table and the sub-service system account table after the query in step S2, the identity identification information is not registered as any group business system, and is popped up. Register the group's general account page to guide the user registration. This page contains the name, password and all user basic information of the registered group's general account. The account number, password and user basic data required by the sub-business system are required. Others For optional content.

For example, in a specific implementation, the user identity information is 13600000066, and the identity information is not queried in the existing group general account table and the sub-service system account table, and the system pops up the group general account registration page, including the account, Password, gender, date of birth, email, constellation, and personality signature, and the target sub-business system account table contains accounts, passwords, and genders. It is easy to understand that users only need to fill in accounts, passwords, and genders on the registration page. Yes, other options are free to choose based on user preferences.

In this embodiment, by analyzing the result of the step S2, if the identity information is not queried in the general account table and the sub-service system account table, the user is guided to use the identity information to register the group general account, so that the user is When using the group's business, the group's general account can be used to log in to all group sub-business systems, improving the efficiency of users logging into the group's business systems.

It should be understood that the size of the sequence of the steps in the above embodiments does not mean that the order of execution is performed. The order of execution of each process should be determined by its function and internal logic, and should not be construed as limiting the implementation process of the embodiments of the present application.

Example 2

Corresponding to the account management method in the first embodiment, FIG. 4 shows the account management apparatus corresponding to the account management method provided in the first embodiment, and for convenience of explanation, only the parts related to the embodiment of the present application are shown.

As shown in FIG. 4, the account management apparatus includes: an identity information acquisition module 41, an identity information query module 42, a group universal account upgrade module 43, and a universal account login verification module 44. Each function module is described in detail as follows:

The identity information obtaining module 41 is configured to: if the user requests the registration of the target sub-service system, obtain the identity identification information of the account to be registered according to the registration request, where the target sub-service system belongs to the group sub-service system, the group The business system contains at least two sub-business systems;

The identity information query module 42 is configured to search for identity identification information of the account to be registered in the group account system, wherein the group account system includes a group general account table and a group sub-service system account table, and the group sub-service account table includes at least two Sub-business system account table;

The group general account upgrade module 43 is configured to: if the identity identification information of the account to be registered is queried in the sub-service system account table, and the identity identification information is not queried in the general account table, supplement the target sub-service system Basic user information and upgrade the account to be registered to a group general account;

The universal account login verification module 44 is configured to log in to the target sub-service system using the group general account.

Further, the identity information query module 42 includes:

The identity information type obtaining sub-module 421 is configured to detect identity identification information based on a preset regular expression, to obtain a type of the identity identification information;

The identity information query sub-module 422 is configured to determine a query range from the group common account table and the sub-service system account table according to the type of the identity identification information, and query the identity identification information in the query scope.

Further, the identity information query sub-module 422 includes:

The identity field obtaining unit 4221 is configured to obtain a field for identity identification in the group common account table and the sub-service system account table;

The first query field obtaining unit 4222 is configured to: if the field attribute is the same as the type of the identity information in the field for the identity identifier, use the queried field as the first query field;

The first query scope obtaining unit 4223 is configured to obtain a first query scope, where the first query scope is content included in the first query field;

The first query range query unit 4224 is configured to query the identity identification information in the first query scope.

The remaining field obtaining unit 4225 is configured to: if the identity identification information is not queried in the first query scope, obtain the remaining fields of the group common account table and the sub-service system account table that do not include the first query field;

The second query field obtaining unit 4226 is configured to obtain a second query field, where the second query field is a field in which the field name in the remaining field is the same as the identity identifier to be registered;

The second query range obtaining unit 4227 is configured to obtain a second query range, where the second query range is content included in the second query field;

The second query range query unit 4228 is configured to query the identity identification information in the second query range.

Further, the account management device further includes:

The group general account update module 45 is configured to: if the identity information of the account to be registered is queried in the general account table, obtain the group general account corresponding to the identity information, and perform an update operation on the group general account, and the update operation is Supplementing the basic user information required by the target sub-business system to the group's general account;

The group general account registration module 46 is configured to guide the user to use the identity identification information to register the group general account if the identity information of the account to be registered is not queried in both the general account table and the sub-service system account table.

For the process of implementing the respective functions in the modules of the account management apparatus provided in this embodiment, refer to the description of the foregoing Embodiment 1, and details are not described herein again.

Example 3

The embodiment provides one or more non-volatile readable storage media having computer readable instructions stored thereon, the computer readable instructions being stored by one or more When the processor executes, causing the one or more processors to execute the account management method in Embodiment 1, or implementing the account management device in Embodiment 2 when the computer readable instructions are executed by one or more processors The function of each module/unit. To avoid repetition, we will not repeat them here.

It is to be understood that the non-volatile readable storage medium may include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, only Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier signals, and telecommunication signals.

Example 4

FIG. 5 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 5, the terminal device 5 of this embodiment includes a processor 51, a memory 52, and computer readable instructions 53 stored in the memory 52 and operable on the processor 51, such as an account management program. The processor 51 implements the steps of the account management method of the above-described Embodiment 1 when the computer readable instructions 53 are executed, such as steps S1 to S4 shown in FIG. Alternatively, when the processor 51 executes the computer readable instructions 53, the functions of the modules/units of the account management apparatus in the above embodiment 2 are implemented, such as the functions of the modules 41 to 44 shown in FIG.

Illustratively, computer readable instructions 53 may be partitioned into one or more modules/units, one or more modules/units being stored in memory 52 and executed by processor 51 to complete the application. The one or more modules/units may be an instruction segment of a series of computer readable instructions capable of performing a particular function, which is used to describe the execution of computer readable instructions 53 in the terminal device 5. For example, the computer readable instruction 53 may be divided into an identity information acquisition module, an identity information query module, a group universal account upgrade module, and a general account login verification module. The specific functions of each module are as shown in Embodiment 2, in order to avoid duplication. I will not repeat them here.

The terminal device 5 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The terminal device 5 may include, but is not limited to, a processor 51 and a memory 52. It will be understood by those skilled in the art that FIG. 5 is only an example of the terminal device 5, does not constitute a limitation of the terminal device 5, may include more or less components than the illustrated, or combine some components, or different components. For example, the terminal device 5 may further include an input/output device, a network access device, a bus, and the like.

The processor 51 may be a central processing unit (CPU), or may be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and an off-the-shelf Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 52 may be an internal storage unit of the terminal device 5, such as a hard disk or a memory of the terminal device 5. The memory 52 may also be an external storage device of the terminal device 5, such as a plug-in hard disk provided on the terminal device 5, a smart memory card (SMC), a Secure Digital (SD) card, and a flash memory card (Flash). Card) and so on. Further, the memory 52 may also include both an internal storage unit of the terminal device 5 and an external storage device. The memory 52 is used to store computer readable instructions and other programs and data required by the terminal device 5. The memory 52 can also be used to temporarily store data that has been or will be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the division of each functional unit and module described above is exemplified. In practical applications, the above functions may be assigned to different functional units as needed. The module is completed by dividing the internal structure of the device into different functional units or modules to perform all or part of the functions described above.

The above-mentioned embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still implement the foregoing embodiments. The technical solutions described in the examples are modified or equivalently replaced with some of the technical features; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in Within the scope of protection of this application.

Claims

An account management method, characterized in that it comprises:

And if the registration request of the target sub-service system is detected, obtaining identity identification information of the account to be registered according to the registration request, wherein the target sub-service system is subordinate to the group sub-service system, and the group sub-service system is at least Contains two sub-business systems;

Locating the identity identification information in the group account system, wherein the group account system includes a group general account table and a group sub-service system account table, and the group sub-service account table includes at least two sub-service system account tables;

If the identity identification information is queried in the sub-service system account table, and the identity identification information is not queried in the universal account table, supplement the basic user information required by the target sub-service system, and The account to be registered is upgraded to a group general account;

The target sub-service system is logged into using the group general account.
The account management method according to claim 1, wherein the searching for the identity identification information in the group account system comprises:

And detecting, by using a preset regular expression, the identity identification information, to obtain a type of the identity identification information;

Determining a query range from the group common account table and the sub-service system account table according to the type of the identity identification information, and querying the identity identification information in the query scope.
The account management method according to claim 2, wherein said determining a query range from said group general account table and said sub-service system account table according to said type of identity identification information, and said Querying the identity information in the query scope, including:

Obtaining a field for the identity identifier in the group common account table and the sub-service system account table;

If the field attribute is the same as the type of the identity information in the field for the identity identifier, the queried field is used as the first query field;

Obtaining a first query scope, where the first query scope is content included in the first query field;

Querying the identity identification information in the first query range;

If the identity information is not queried in the first query scope, obtaining the group common account table and the sub-service system account table do not include the remaining fields of the first query field;

Obtaining a second query field, where the second query field is a field in which the field name in the remaining field is the same as the identity identifier to be registered;

Obtaining a second query scope, where the second query scope is content included in the second query field;

Querying the identity identification information in the second query scope.
The account management method according to any one of claims 1 to 3, wherein after the searching for the identity identification information in the group account system, the account management method further comprises:

And if the identity information is queried in the universal account table, acquiring a group general account corresponding to the identity information, and performing an update operation on the group universal account, where the update operation is performed to the group The basic user information required to supplement the target sub-business system in the account.
The account management method according to any one of claims 1 to 3, wherein after the searching for the identity identification information in the group account system, the account management method further comprises:

If the identity information is not queried in the general account table and the sub-service system account table, the user is guided to use the identity information to register the group general account.
An account management apparatus, wherein the account management apparatus comprises:

An identity information obtaining module, configured to acquire, according to the registration request, identity identification information of an account to be registered, where the target sub-service system belongs to the group sub-service system, if the registration request of the target sub-service system is detected by the user The group sub-business system includes at least two sub-business systems;

The identity information query module is configured to search the identity information in the group account system, where the group account system includes a group general account table and a group sub-service system account table, and the group sub-service account table includes at least two Sub-business system account table;

a group general account upgrade module, configured to: if the identity identification information is queried in the sub-service system account table, and the identity identification information is not queried in the general account table, supplement the target sub-service system Basic user information required, and the account to be registered is upgraded to a group general account;

A universal account login verification module is configured to log in to the target sub-service system using the group universal account.
The account management apparatus according to claim 6, wherein the identity identification information query module comprises:

An identity information type obtaining submodule, configured to detect the identity identification information according to a preset regular expression, to obtain a type of the identity identification information;

The identity information query sub-module is configured to determine a query range from the group common account table and the sub-service system account table according to the type of the identity identification information, and identify the identity in the query scope Information is queried.
The account management apparatus according to claim 7, wherein the identity identification information query sub-module comprises:

An identity field obtaining unit, configured to obtain a field used in the group common account table and the sub-service system account table for the identity identifier;

a first query field obtaining unit, configured to: if the field attribute is the same as the type of the identity information in the field for the identity, the queried field is used as the first query field;

a first query scope obtaining unit, configured to obtain a first query scope, where the first query scope is content included in the first query field;

a first query range query unit, configured to query the identity identification information in the first query scope; and a remaining field obtaining unit, configured to: if the identity identification information is not queried in the first query scope, Obtaining the group common account table and the sub-service system account table not including the remaining fields of the first query field;

a second query field obtaining unit, configured to obtain a second query field, where the second query field is a field in which the field name in the remaining field is the same as the identity identifier to be registered;

a second query scope obtaining unit, configured to obtain a second query scope, where the second query scope is content included in the second query field;

The second query range query unit is configured to query the identity identification information in the second query range.
The account management apparatus according to any one of claims 6 to 8, wherein the account management apparatus further comprises:

a group general account update module, configured to acquire a group general account corresponding to the identity identification information, and perform an update operation on the group universal account, if the identity identification information is queried in the universal account table, The update operation is to supplement the basic user information required by the target sub-service system to the group general account.
The account management apparatus according to any one of claims 6 to 8, wherein the account management apparatus further comprises:

The group universal account registration module is configured to guide the user to register the group general account by using the identity identification information if the identity identification information is not queried in the general account table and the sub-service system account table.
A terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and operable on the processor, wherein the processor executes the computer readable instructions as follows step:

And if the registration request of the target sub-service system is detected, obtaining identity identification information of the account to be registered according to the registration request, wherein the target sub-service system is subordinate to the group sub-service system, and the group sub-service system is at least Contains two sub-business systems;

Locating the identity identification information in the group account system, wherein the group account system includes a group general account table and a group sub-service system account table, and the group sub-service account table includes at least two sub-service system account tables;

If the identity identification information is queried in the sub-service system account table, and the identity identification information is not queried in the universal account table, supplement the basic user information required by the target sub-service system, and The account to be registered is upgraded to a group general account;

The target sub-service system is logged into using the group general account.
The terminal device according to claim 11, wherein the searching for the identity identification information in the group account system comprises:

And detecting, by using a preset regular expression, the identity identification information, to obtain a type of the identity identification information;

Determining a query range from the group common account table and the sub-service system account table according to the type of the identity identification information, and querying the identity identification information in the query scope.
The terminal device according to claim 12, wherein said determining a query range from said group general account table and said sub-service system account table according to said type of identity identification information, and in said query Querying the identity information in the range, including:

Obtaining a field for the identity identifier in the group common account table and the sub-service system account table;

If the field attribute is the same as the type of the identity information in the field for the identity identifier, the queried field is used as the first query field;

Obtaining a first query scope, where the first query scope is content included in the first query field;

Querying the identity identification information in the first query range;

If the identity information is not queried in the first query scope, obtaining the group common account table and the sub-service system account table do not include the remaining fields of the first query field;

Obtaining a second query field, where the second query field is a field in which the field name in the remaining field is the same as the identity identifier to be registered;

Obtaining a second query scope, where the second query scope is content included in the second query field;

Querying the identity identification information in the second query scope.
The terminal device according to any one of claims 11 to 13, wherein after the processor searches for the identity identification information in the group account system, the processor further includes the implementation when the computer readable instructions are executed The following steps:

And if the identity information is queried in the universal account table, acquiring a group general account corresponding to the identity information, and performing an update operation on the group universal account, where the update operation is performed to the group The basic user information required to supplement the target sub-business system in the account.
The terminal device according to any one of claims 11 to 13, wherein after the processor searches for the identity identification information in the group account system, the processor further includes the implementation when the computer readable instructions are executed The following steps:

If the identity information is not queried in the general account table and the sub-service system account table, the user is guided to use the identity information to register the group general account.
One or more non-transitory readable storage mediums storing computer readable instructions, wherein when the computer readable instructions are executed by one or more processors, cause the one or more processors to execute The following steps:

And if the registration request of the target sub-service system is detected, obtaining identity identification information of the account to be registered according to the registration request, wherein the target sub-service system is subordinate to the group sub-service system, and the group sub-service system is at least Contains two sub-business systems;

Locating the identity identification information in the group account system, wherein the group account system includes a group general account table and a group sub-service system account table, and the group sub-service account table includes at least two sub-service system account tables;

If the identity identification information is queried in the sub-service system account table, and the identity identification information is not queried in the universal account table, supplement the basic user information required by the target sub-service system, and The account to be registered is upgraded to a group general account;

The target sub-service system is logged into using the group general account.
The non-volatile readable storage medium according to claim 16, wherein the searching for the identity identification information in the group account system comprises:

And detecting, by using a preset regular expression, the identity identification information, to obtain a type of the identity identification information;

Determining a query range from the group common account table and the sub-service system account table according to the type of the identity identification information, and querying the identity identification information in the query scope.
The non-volatile readable storage medium according to claim 17, wherein said determining a query range from said group general account table and said sub-service system account table according to said type of identity identification information And querying the identity identification information in the query scope, including:

Obtaining a field for the identity identifier in the group common account table and the sub-service system account table;

If the field attribute is the same as the type of the identity information in the field for the identity identifier, the queried field is used as the first query field;

Obtaining a first query scope, where the first query scope is content included in the first query field;

Querying the identity identification information in the first query range;

If the identity information is not queried in the first query scope, obtaining the group common account table and the sub-service system account table do not include the remaining fields of the first query field;

Obtaining a second query field, where the second query field is a field in which the field name in the remaining field is the same as the identity identifier to be registered;

Obtaining a second query scope, where the second query scope is content included in the second query field;

Querying the identity identification information in the second query scope.
The non-volatile readable storage medium according to any one of claims 16 to 18, wherein said computer readable instructions are one or after said locating said identity information in said group account system When the plurality of processors are executed, the one or more processors are further configured to perform the following steps:

And if the identity information is queried in the universal account table, acquiring a group general account corresponding to the identity information, and performing an update operation on the group universal account, where the update operation is performed to the group The basic user information required to supplement the target sub-business system in the account.
The non-volatile readable storage medium according to any one of claims 16 to 18, wherein said computer readable instructions are one or after said locating said identity information in said group account system When the plurality of processors are executed, the one or more processors are further configured to perform the following steps:

If the identity information is not queried in the general account table and the sub-service system account table, the user is guided to use the identity information to register the group general account.