CN110895603B

CN110895603B - Multi-system account information integration method and device

Info

Publication number: CN110895603B
Application number: CN201911070396.6A
Authority: CN
Inventors: 欧阳娅; 绳栋国
Original assignee: Taikang Insurance Group Co Ltd
Current assignee: Taikang Insurance Group Co Ltd
Priority date: 2019-11-05
Filing date: 2019-11-05
Publication date: 2021-11-26
Anticipated expiration: 2039-11-05
Also published as: CN110895603A

Abstract

The invention discloses a method and a device for integrating multi-system account information, and relates to the technical field of computers. Wherein, the method comprises the following steps: responding to a trigger operation of a user for logging in a second system, and acquiring user information of the user under a first account in a logged first system; under the condition that a second account bound with a first account exists in a second system and the user information in the binding relation between the first account and the second account is inconsistent with the user information under the first account in the first system, verifying whether the user information under the first account in the first system belongs to the user; and under the condition that the verification result is yes, updating the user information in the binding relationship according to the user information under the first account in the first system. Through the steps, the complicated operation of the user can be reduced when the account information is changed, the user experience is improved, and the safety in the account information synchronization process can be improved.

Description

Multi-system account information integration method and device

Technical Field

The invention relates to the technical field of computers, in particular to a method and a device for integrating multi-system account information.

Background

With the development of internet technology, application systems such as various websites and APPs (applications) come out endlessly. Generally, a user needs to register an account in each application system, and then manually input an account name and a password on a login interface provided by each application system to log in.

In order to simplify the login operation of a user when entering a plurality of systems, a single-point login solution is proposed in the prior art. Single Sign On (Single Sign On) means that a user can access all mutually trusted application systems only by logging On once in a plurality of application systems. For example, in a multi-application system composed of a system a and a system B, an account a of a user on the system a is bound with an account B of the user on the system B, and after the user logs in the system a through the account a, the user can directly log in the system B through a code scanning mode and the like without manually inputting information of the account B.

After the information of the account a of the user in the system a is changed, in the prior art, there are three processing modes for the binding relationship between the accounts. In the process of implementing the invention, the inventor of the invention finds that the three treatment modes have at least the following problems:

in the first existing processing mode, a user is required to manually release the binding relationship between an account a and an account B, and then the account a and a newly-built account c are manually bound by the user, so that the user operation is very complicated, and old account information which is not used by the user any more still exists in a system B, and data redundancy is caused.

In the second conventional processing mode, the binding relationship between the account a and the account b is still maintained, and the related information in the binding relationship between the account a and the account b is not updated synchronously, which may cause the problems of inconsistency of the account information existing in the two systems, inconvenience in use for users, and the like.

In the third existing processing mode, the binding relationship between the account a and the account B is still maintained, and the related information in the binding relationship in the system B is directly synchronized, which may result in information security holes. For example, in system B, some information is not allowed to be modified, but the purpose of modifying the information in system B can be achieved by modifying the information in system a, thereby causing a security risk. Moreover, in some cases, after some information of the account a is modified, it is uncertain whether the system B allows the account a to be continuously bound with the account B, and directly performing synchronization may cause a problem that a business processing flow in the system B is wrong.

Disclosure of Invention

In view of this, the invention provides a method and a device for integrating multi-system account information, which can reduce the complicated operations of a user when account information is changed, improve user experience, and improve the security in the account information synchronization process.

In order to achieve the above object, according to an aspect of the present invention, a method for integrating information of multiple system accounts is provided.

The multi-system account information integration method comprises the following steps: responding to a trigger operation of a user for logging in a second system, and acquiring user information of the user under a first account in a logged first system; under the condition that a second account bound with a first account exists in a second system and the user information in the binding relation between the first account and the second account is inconsistent with the user information under the first account in the first system, verifying whether the user information under the first account in the first system belongs to the user; and under the condition that the verification result is yes, updating the user information in the binding relationship according to the user information under the first account in the first system.

Optionally, the method further comprises: before the step of verifying whether the user information under the first account in the first system belongs to the user is executed, sending update prompt information to the user, and receiving response information for updating corresponding to confirmation of the update prompt information.

Optionally, the user information under the first account in the first system includes: a user mobile phone number; the step of verifying whether the user information under the first account in the first system belongs to the user comprises: acquiring a verification code input by a user from the response information for confirming updating; comparing the verification code input by the user with the short message verification code sent to the mobile phone number of the user; and if the verification code input by the user is consistent with the short message verification code sent to the mobile phone number of the user, confirming that the user information under the first account number in the first system belongs to the user.

Optionally, the step of sending the update prompt information to the user includes: judging whether the user information under the first account in the first system is used by other accounts in the second system; if the judgment result is yes, sending first updating prompt information to the user; under the condition that the judgment result is negative, sending second updating prompt information to the user; wherein, the first updating prompt message comprises: prompt information indicating that the user information is used by other accounts in the second system and prompt information indicating whether the user information in the binding relationship is updated or not; the second update prompt message includes: and prompt information for judging whether to update the user information in the binding relationship.

Optionally, the method further comprises: and if the verification result is yes and the user information under the first account in the first system is used by other accounts in the second system, setting other accounts using the user information in the second system as invalid.

Optionally, the method further comprises: sending binding prompt information to a user under the condition that a second account bound with a first account does not exist in a second system and the user information under the first account in the first system is used by other accounts in the second system; after response information corresponding to the binding prompt information and confirmed by the user to be bound is received, binding the first account with other accounts using the user information in a second system; and/or generating a new account in the second system according to the user information under the first account under the condition that it is determined that the second account bound with the first account does not exist in the second system and the user information under the first account in the first system is not used by other accounts in the second system, and binding the first account with the new account.

In order to achieve the above object, according to another aspect of the present invention, a multi-system account information integrating device is provided.

The multi-system account information integration device comprises: the acquisition module is used for responding to the triggering operation of the user for logging in the second system and acquiring the user information of the user under the first account in the logged first system; the verification module is used for verifying whether the user information under the first account in the first system belongs to the user or not under the condition that the second account bound with the first account exists in the second system and the user information in the binding relation between the first account and the second account is inconsistent with the user information under the first account in the first system; and the updating module is used for updating the user information in the binding relationship according to the user information under the first account in the first system under the condition that the verification result is yes.

Optionally, the apparatus further comprises: the communication module is used for sending update prompt information to the user and receiving response information for updating corresponding to the confirmation of the update prompt information before the verification module verifies whether the user information under the first account in the first system belongs to the user.

To achieve the above object, according to still another aspect of the present invention, there is provided an electronic apparatus.

The electronic device of the present invention includes: one or more processors; and storage means for storing one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors implement the multi-system account information integration method.

To achieve the above object, according to still another aspect of the present invention, there is provided a computer-readable medium.

The computer-readable medium of the present invention stores thereon a computer program, which when executed by a processor implements the multi-system account information integration method of the present invention.

One embodiment of the above invention has the following advantages or benefits: the method comprises the steps of acquiring user information of a user under a first account in a logged first system after the user triggers the operation of logging in a second system, and updating the user information in a binding relationship according to the user information under the first account in the first system under the condition that the second account bound with the first account exists in the second system and the user information in the binding relationship between the first account and the second account is inconsistent with the user information under the first account in the first system, so that the user information in the binding relationship can be automatically updated when the account information of one system is changed, the operation of manually unbinding and then binding the accounts by the user is not required, the complicated operation of the user is reduced, and the user experience is improved; and whether the user information under the first account in the first system belongs to the user is verified, and the step of updating the user information in the binding relationship is executed under the condition that the verification result is yes, so that the safety in the account information synchronization process can be improved.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

fig. 1 is a schematic main flow diagram of a multi-system account information integration method according to a first embodiment of the present invention;

fig. 2 is a schematic main flow diagram of a multi-system account information integration method according to a second embodiment of the present invention;

fig. 3 is a partial flowchart illustrating a multisystem account information integration method according to a third embodiment of the present invention;

fig. 4 is a partial flowchart illustrating a multisystem account information integration method according to a third embodiment of the present invention;

fig. 5 is a schematic diagram of main modules of a multi-system account information integrating device according to a fourth embodiment of the present invention;

fig. 6 is a schematic diagram of main modules of a multi-system account information integrating device according to a fifth embodiment of the present invention;

FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

FIG. 8 is a schematic block diagram of a computer system suitable for use with the electronic device to implement an embodiment of the invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict.

Fig. 1 is a main flow diagram of a multi-system account information integration method according to a first embodiment of the present invention. The method of the embodiment of the invention can be executed by a multi-system account information integration device. As shown in fig. 1, the method for integrating information of multiple system accounts according to the embodiment of the present invention includes:

step S101, responding to a trigger operation of a user for logging in a second system, and acquiring user information of the user under a first account in a logged first system.

For example, after a user logs in a first system through a first account, the triggering operation of the user to log in a second system may be: scanning the two-dimensional code of the second system on the page of the first system, clicking a link control for jumping to the second system on the page of the first system, and the like.

In this step, the acquired user information under the first account in the first system may include one or more of the following items: account ID (identification), user name, user mobile phone number, user mailbox, user certificate type, user certificate number and the like. The user information under the first account in the first system is the user information under the account used by the user to log in the first system at this time.

Step S102, when it is determined that a second account bound with a first account exists in a second system and user information in a binding relation between the first account and the second account is inconsistent with user information under the first account in the first system, whether the user information under the first account in the first system belongs to the user is verified.

Prior to step S102, the method of embodiments of the present invention may further include the steps of: and judging whether a second account bound with the first account exists in the second system or not, and judging whether the user information in the binding relationship between the first account and the second account is consistent with the user information under the first account in the first system or not. In specific implementation, user information under the account concerned in the process, such as a user mobile phone number and/or a user mailbox, can be selected according to business requirements.

In an optional example, the user information concerned by the process is a mobile phone number. In this optional example, step S102 specifically includes: comparing a verification code input by a user through a terminal with a short message verification code sent to a mobile phone number under a first account in a first system; and if the mobile phone number and the user number are consistent, determining that the mobile phone number belongs to the user. In addition, in specific implementation, when the verification code input by the user is inconsistent with the verification code sent to the mobile phone number, the short message verification code can be sent to the mobile phone number again, and the verification is carried out again.

In another optional example, the user information concerned by the process is a mailbox. In this optional example, step S102 specifically includes: comparing an authentication code input by a user through a terminal with an authentication code sent to a mailbox under a first account in a first system; if the two are consistent, the mailbox is determined to belong to the user. In addition, in the specific implementation, when the verification code input by the user is inconsistent with the verification code sent to the mailbox, the verification code can be sent to the mailbox again and verified again.

And step S103, under the condition that the verification result is yes, updating the user information in the binding relationship according to the user information under the first account in the first system.

In an optional example, the user information under the first account of the first system is a mobile phone number. In this alternative example, step S103 includes: and updating the mobile phone number in the binding relationship according to the mobile phone number under the first account number in the first system. For example, if the mobile phone number under the first account in the first system is "130 XXXX 1256" and the mobile phone number in the binding relationship is "132 XXXX 2568", the mobile phone number in the binding relationship is modified to be "130 XXXX 1256".

In the embodiment of the invention, after a user triggers the operation of logging in a second system, the user information of the user under a first account in a logged first system is acquired, and under the condition that a second account bound with the first account exists in the second system and the user information in the binding relationship between the first account and the second account is determined to be inconsistent with the user information under the first account in the first system, the user information in the binding relationship is updated according to the user information under the first account in the first system, so that when the account information of one system is changed, the user information in the binding relationship of the other system can be automatically updated, the operation of manually executing account unbinding and rebinding is not required by the user, the complicated operation of the user is reduced, and the user experience is improved; and whether the user information under the first account in the first system belongs to the user is verified, and the step of updating the user information in the binding relationship is executed under the condition that the verification result is yes, so that the safety in the account information synchronization process can be improved.

Fig. 2 is a main flow diagram illustrating a multi-system account information integration method according to a second embodiment of the present invention. As shown in fig. 2, the method for integrating information of multiple system accounts according to the embodiment of the present invention includes:

step S201, in response to a trigger operation of a user to log in a second system, obtaining user information of the user under a first account in a logged-in first system.

For example, after a user logs in a first system through a first account, the triggering operation of the user to log in a second system may be: and scanning the two-dimensional code of the second system on the page of the first system, or clicking a link control for jumping to the second system on the page of the first system, and the like.

Step S202, determining that a second account bound with the first account exists in the second system, and the user information in the binding relationship between the first account and the second account is inconsistent with the user information under the first account in the first system.

Further, before step S202, the method of the embodiment of the present invention may further include the following steps: and judging whether a second account bound with the first account exists in the second system or not, and judging whether the user information in the binding relationship between the first account and the second account is consistent with the user information under the first account in the first system or not.

The step of determining whether a second account bound to the first account exists in the second system may specifically include: inquiring the binding relationship in a second system according to the account ID in the first account to acquire a second account bound with the first account; if the query result is null, indicating that a second account bound with the first account does not exist in the second system; and if the query result is not null, indicating that a second account bound with the first account exists in the second system. After determining that the second account bound to the first account exists in the second system according to the above optional embodiments, the user information in the binding relationship may be compared with the user information under the first account in the first system to determine whether the two are consistent.

The binding relationship between the first account and the second account may include: the user information under the first account is bound with the user information under the second account. The first account is an account of a user in a first system, and the second account is an account of the user in a second system. Illustratively, the binding relationship may be as shown in table 1 or table 2.

TABLE 1

Account ID under first account	Account ID under the second account (user mobile phone number)
		1_1	130XXXX3433
1_2	132XXXX3789

TABLE 2

The binding relationships shown in table 1 include: the account ID under the first account and the account ID under the second account bound with the first account. In table 1, the account ID under the first account is specifically a user number automatically generated by the first system, and the account ID under the second account is specifically a mobile phone number of the user. In addition, in specific implementation, the account ID under the first account may also be an account name, a user name, and the like manually input by the user when the user registers in the first system.

The binding relationships shown in table 2 include: the mobile phone number of the user under the first account is bound with the account ID under the second account. In table 1, the account ID under the first account is specifically a user number automatically generated by the first system, and the account ID under the second account is a number automatically generated by the second system.

Step S203, determining whether the user information is already used by other accounts in the second system.

In an optional example, the user information focused on by the flow is a mobile phone number. In this alternative example, step S203 specifically includes: inquiring an account information table in a second system according to a mobile phone number under a first account in a first system, and if a record of using the account of the mobile phone number exists in the account information table, confirming that the mobile phone number is used by other accounts in the second system; and if the account information table does not have records of the account using the mobile phone number, determining that the mobile phone number is not used by other accounts in the second system.

Further, if it is determined through step S203 that the user information is already used by another account in the second system, step S204 to step S208 may be executed; if not, steps S209 to S212 may be performed.

And step S204, sending first updating prompt information to the user.

In this step, first update prompt information may be returned to the client of the first system corresponding to the user. Wherein the first update prompt message may include: the user information is used by other accounts in the second system, and whether the user information in the binding relationship is updated or not is provided.

After receiving the first update prompt message, the user may confirm to update by clicking a selection control on a client page of the first system, or confirm not to update. In addition, the user can also input the verification code on the client page of the first system after receiving the verification code sent by the multi-system account information integration device.

And step S205, receiving response information of user confirmation updating corresponding to the first updating prompt information.

Step S206, whether the user information under the first account in the first system belongs to the user is verified.

In an optional example, the user information focused on by the flow is a mobile phone number. In this optional example, step S202 specifically includes: acquiring a verification code input by a user from the response information, and comparing the verification code input by the user with a short message verification code sent to a mobile phone number under a first account in the first system; and if the mobile phone number and the user number are consistent, determining that the mobile phone number belongs to the user. In addition, in specific implementation, if the verification code input by the user is inconsistent with the short message verification code sent to the mobile phone number, the short message verification code can be sent to the mobile phone number again, and the verification is carried out again.

In another alternative example, the user information of interest to the process is a mailbox. In this optional example, step S202 specifically includes: acquiring a verification code input by a user from the response message, and comparing the verification code input by the user with a verification code sent to a mailbox under a first account in the first system; if the two are consistent, the mailbox is determined to belong to the user. In addition, in the specific implementation, if the verification code input by the user is inconsistent with the verification code sent to the mailbox, the verification code can be sent to the mailbox again, and the verification can be carried out again.

And step S207, if the verification result is positive, updating the user information in the binding relationship according to the user information under the first account in the first system.

In an optional example, the user information under the first account of the first system is a mobile phone number. In this alternative example, step S207 includes: and updating the mobile phone number in the binding relationship according to the mobile phone number under the first account number in the first system. For example, if the mobile phone number under the first account in the first system is "130 XXXX 1256" and the mobile phone number in the binding relationship is "132 XXXX 2568", the mobile phone number in the binding relationship is modified to be "130 XXXX 1256".

In the embodiment of the present invention, whether the user information under the first account in the first system belongs to the user is verified in step S206, and the user information in the binding relationship is updated in step S207 when the verification result is yes, so that the security in the account information synchronization process can be improved.

And step S208, setting other accounts using the user information in the second system as invalid.

In this step, the record of the other account using the user information in the account information table in the second system may be deleted, or the value of the valid status field in the record may be set to "invalid".

In the embodiment of the invention, after the user information is judged to be used by other accounts in the second system and the user information under the first account in the first system is confirmed to belong to the user, the other accounts using the user information are set to be invalid, so that the condition that a plurality of accounts use the same user information (especially user unique identification information such as mobile phone numbers) in the second system caused by directly carrying out synchronous processing on the account information can be avoided, and further the problems of service processing flow errors and the like in the second system possibly caused by the condition are avoided.

And step S209, sending second updating prompt information to the user.

In this step, second update prompt information may be returned to the client of the first system corresponding to the user. Wherein the second update prompt message includes: and prompt information for judging whether to update the user information in the binding relationship.

After receiving the second update prompt message, the user may make a response to confirm that the update is performed or confirm that the update is not performed by clicking a selection control on a client page of the first system. In addition, the user can also input the verification code on the client page of the first system after receiving the verification code sent by the multi-system account information integration device.

In the embodiment of the present invention, step S203 is used to determine whether the user information is already used by other accounts in the second system, and send the first update prompt information or the second update prompt information to the user according to the difference of the determination result, so that the user can better know the registered use condition of the user information under the first account in the second system, and the user experience in the account information synchronization process is improved.

And step S210, receiving response information corresponding to the second updating prompt information and confirming to update by the user.

Step S211, verifying whether the user information under the first account in the first system belongs to the user.

In an optional example, the user information focused on by the flow is a mobile phone number. In this optional example, step S211 specifically includes: acquiring a verification code input by a user from the response information, and comparing the verification code input by the user with a short message verification code sent to a mobile phone number under a first account in the first system; and if the mobile phone number and the user number are consistent, determining that the mobile phone number belongs to the user. In addition, in specific implementation, if the verification code input by the user is inconsistent with the short message verification code sent to the mobile phone number, the short message verification code can be sent to the mobile phone number again, and the verification is carried out again.

Step S212, if the verification result is yes, updating the user information in the binding relationship according to the user information under the first account in the first system.

In the embodiment of the invention, through the steps, when the account information of one system is changed, the user information in the binding relationship of the other system can be automatically updated, the operation of manually unbinding and binding the account by the user is not needed, the complicated operation of the user is reduced, the user experience is improved, and the safety in the account information synchronization process can be improved. In addition, the problems of inconsistent account information in the two systems, inconvenience in use of users and the like caused by the fact that the user information in the account binding relationship is not updated in the prior art are solved through the steps.

A method for integrating information of multiple system accounts according to a third embodiment of the present invention is described below with reference to fig. 3 and 4. Fig. 3 is a partial flowchart of a multisystem account information integration method according to a third embodiment of the present invention. As shown in fig. 3, the method for integrating information of multiple system accounts according to the embodiment of the present invention includes:

step S301, a user scans the two-dimensional code of the second system in the first system.

Illustratively, the first system may be an insurance financing application and the second system may be a customer service application associated therewith. The first system and the second system independently manage own account numbers, and account number IDs, user names, mobile phone numbers, certificate types, certificate numbers and other user information are arranged under the account numbers in the two systems.

In specific implementation, after logging in the first system through the first account, the user may trigger the multi-system account information integration apparatus to perform subsequent steps such as step S302 by scanning the two-dimensional code of the second system.

Step S302, user information such as a mobile phone number of the user under a first account of a first system is obtained.

In this step, the multi-system account information integrating device may obtain user information such as an account ID and a mobile phone number under a first account used by the user to log in the first system.

Step S303, determining whether the second system has a second account bound to the first account. If yes, go to step S304; if not, the corresponding steps in FIG. 4 may be performed.

In this step, the binding relationship in the second system can be queried according to the account ID in the first account to obtain the second account bound with the first account; if the query result is null, indicating that a second account bound with the first account does not exist in the second system; and if the query result is not null, indicating that a second account bound with the first account exists in the second system.

And S304, acquiring the mobile phone number in the binding relationship between the first account and the second account.

Step S305, judging whether the mobile phone number in the binding relationship is consistent with the mobile phone number under the first account number in the first system. If yes, step S314 may be executed, namely logging in the second system based on the account bound to the first account; if not, step S306 can be executed.

Step S306, whether the mobile phone number under the first account in the first system is used by other accounts in the second system is judged. If yes, go through steps S307, S308, S309, and S313; if not, steps S310, S311, S312, and S313 can be performed.

In this step, an account information table in the second system can be queried according to the mobile phone number under the first account in the first system, and if a record of using the account of the mobile phone number exists in the account information table, it is determined that the mobile phone number is used by other accounts in the second system; and if the account information table does not have records of the account using the mobile phone number, determining that the mobile phone number is not used by other accounts in the second system.

Step S307, sending the first update prompt information to the user, and receiving response information for confirming the update.

After receiving the first update prompt message, the user may make a response to confirm that the update is performed or make a response to confirm that the update is not performed by clicking a selection control on a client page of the first system. If the response message confirming the update is received, step S308 may be executed; if response information confirming that updating is not performed is received, prompt information of login failure can be returned to the user.

And step S308, acquiring the verification code input by the user from the response message, and confirming that the verification code is consistent with the short message verification code sent to the mobile phone number.

And S309, updating the mobile phone number in the binding relationship, and setting other account numbers using the mobile phone number in the second system as invalid.

The step of setting the other account numbers using the mobile phone number in the second system as invalid may be deleting records of the other account numbers using the user information in an account information table in the second system, or setting a value of an effective status field in the record as invalid.

Further, after step S309, step S313 of logging in to the second system based on the account bound to the first account may be performed.

Step S310, sending a second updating prompt message to the user, and receiving a response message for confirming the updating.

After receiving the second update prompt message, the user may make a response to confirm that the update is performed or make a response to confirm that the update is not performed by clicking a selection control on a client page of the first system. If the response information for confirming the updating is received, the multi-system account information integrating device may execute step S311; if response information confirming that updating is not performed is received, the multi-system account information integration device can return prompt information of login failure to the user.

Step S311, the verification code input by the user is obtained from the response message, and the consistency with the short message verification code sent to the mobile phone number is confirmed.

And step S312, updating the mobile phone number in the binding relationship.

And step 313, logging in a second system based on the second account bound with the first account.

Fig. 4 is a partial flowchart illustrating a multisystem account information integration method according to a third embodiment of the present invention. Fig. 4 mainly illustrates a flow branch after it is determined that there is no second account bound to the first account in the second system. As shown in fig. 4, the method for integrating information of multiple system accounts according to the embodiment of the present invention further includes:

step S401, the user scans the two-dimensional code of the second system on the first system.

And S402, acquiring user information such as a mobile phone number of the user under the first account of the first system.

Step S403, determining whether the second system has a second account bound to the first account. If not, executing step S404; if yes, the corresponding steps in FIG. 3 are executed.

Step S404, judging whether the mobile phone number under the first account number in the first system is used by other account numbers in the second system. If yes, steps S405, S406, S407, and S409 can be executed; if not, steps S408 and S409 may be performed.

Step S405, sending binding prompt information to the user and receiving response information for confirming the binding by the user.

In this step, binding prompt information may be returned to the client of the first system corresponding to the user. Wherein the binding prompt message may include: prompt information that the user information has been used by other accounts in the second system, and prompt information whether to bind the accounts.

After receiving the binding prompt message, the user can make a response for confirming binding by clicking a selection control on a client page of the first system or the like, or make a response for confirming that the binding is not performed. If response information confirming the binding is received, the multi-system account information integrating device may execute step S406; if response information for confirming that the binding is not carried out is received, prompt information of login failure can be returned to the user.

And step S406, acquiring the verification code input by the user from the response message, and confirming that the verification code is consistent with the short message verification code sent by the mobile phone number.

And step S407, binding the first account with other accounts using the mobile phone number in the second system. After step S407, step S409 of logging in to the second system based on the account bound to the first account may be performed.

Step S408, generating a new account in the second system according to the mobile phone number under the first account, and binding the first account with the new account.

And step S409, logging in a second system based on the account bound with the first account.

In the embodiment of the invention, the accounts of the user in the first system and the second system can be automatically bound through the steps, and the user can automatically log in the second system based on the bound accounts, so that the complicated operation of the user in account binding is reduced, and the user experience is improved; in addition, when it is determined that the mobile phone number under the first account in the first system is used by another account in the second system in step S404, whether the mobile phone number belongs to the user is verified in steps S405 to S406, so that the security in the account binding process can be improved.

Fig. 5 is a schematic diagram of main modules of a multi-system account information integrating device according to a fourth embodiment of the present invention. As shown in fig. 5, a multi-system account information integrating apparatus 500 according to an embodiment of the present invention includes: an acquisition module 501, a verification module 502 and an update module 503.

The obtaining module 501 is configured to, in response to a trigger operation of a user to log in a second system, obtain user information of the user under a first account in a first system that has logged in.

The user information under the first account in the first system acquired by the acquiring module 501 may include one or more of the following items: account ID (identification), user name, user mobile phone number, user mailbox, user certificate type, user certificate number and the like. The user information under the first account in the first system is the user information under the account used by the user to log in the first system at this time.

The verification module 502 is configured to verify whether the user information in the first account in the first system belongs to the user when it is determined that the second account bound to the first account exists in the second system and the user information in the binding relationship between the first account and the second account is inconsistent with the user information in the first account in the first system.

In an alternative example, the user information to be authenticated is a mobile phone number. In this optional example, the verifying module 502 specifically verifies whether the user information under the first account in the first system belongs to the user includes: the verification module 502 compares a verification code input by a user through a terminal with a short message verification code sent to a mobile phone number under a first account in the first system; and if the mobile phone number and the user number are consistent, determining that the mobile phone number belongs to the user. In addition, in specific implementation, when the verification code input by the user is inconsistent with the verification code sent to the mobile phone number, the short message verification code can be sent to the mobile phone number again, and the verification module 502 is used for verifying again.

In another alternative example, the user information to be authenticated is a mailbox. In this optional example, the verifying module 502 specifically verifies whether the user information under the first account in the first system belongs to the user includes: the verification module 502 compares a verification code input by a user through a terminal with a verification code sent to a mailbox under a first account in the first system; if the two are consistent, the mailbox is determined to belong to the user. In addition, in specific implementation, when the verification code input by the user is inconsistent with the verification code sent to the mailbox, the verification code may be sent to the mailbox again, and the verification module 502 may perform the verification again.

An updating module 503, configured to update the user information in the binding relationship according to the user information under the first account in the first system if the verification result is yes.

In an optional example, the user information under the first account of the first system is a mobile phone number. In this optional example, the updating module 503 is specifically configured to update the mobile phone number in the binding relationship according to the mobile phone number under the first account in the first system. For example, if the mobile phone number under the first account in the first system is "130 XXXX 1256" and the mobile phone number in the binding relationship is "132 XXXX 2568", the mobile phone number in the binding relationship is modified to be "130 XXXX 1256".

In the embodiment of the invention, after a user triggers a login operation on a second system, user information of the user under a first account in the logged-in first system is acquired through an acquisition module, and under the condition that a second account bound with the first account exists in the second system and the user information in the binding relationship between the first account and the second account is inconsistent with the user information under the first account in the first system, the user information in the binding relationship is updated through an updating module according to the user information under the first account in the first system, so that when the account information of one system is changed, the user information in the binding relationship of the other system can be automatically updated, the operation of manually unbinding and then binding the account by the user is not required, the complicated operation of the user is reduced, and the user experience is improved; and whether the user information under the first account in the first system belongs to the user is verified through the verification module, and the user information in the binding relationship is updated under the condition that the verification result is yes, so that the safety in the account information synchronization process can be improved.

Fig. 6 is a schematic diagram of main modules of a multi-system account information integrating device according to a fifth embodiment of the present invention. As shown in fig. 6, a multi-system account information integrating apparatus 600 according to an embodiment of the present invention includes: an acquisition module 601, a judgment module 602, a communication module 603, a verification module 604, and an update module 605.

The obtaining module 601 is configured to obtain, in response to a trigger operation of a user to log in a second system, user information of the user under a first account in a first system that has logged in.

For example, after a user logs in a first system through a first account, the triggering operation of the user to log in a second system may be: scanning the two-dimensional code of the second system on the page of the first system, clicking a link control for jumping to the second system on the page of the first system, and the like. The user information under the first account in the first system acquired by the acquiring module 601 may include one or more of the following items: account ID (identification), user name, user mobile phone number, user mailbox, user certificate type, user certificate number and the like. The user information under the first account in the first system is the user information under the account used by the user to log in the first system at this time.

The determining module 602 is configured to determine whether a second account bound to the first account exists in the second system, and determine whether user information in a binding relationship between the first account and the second account is consistent with user information under the first account in the first system.

Specifically, the determining module 602 determines whether a second account bound to the first account exists in the second system specifically includes: the determining module 602 queries a binding relationship in a second system according to an account ID in the first account to obtain a second account bound to the first account; if the query result is null, indicating that a second account bound with the first account does not exist in the second system; and if the query result is not null, indicating that a second account bound with the first account exists in the second system. After determining that the second account bound to the first account exists in the second system, the determining module 602 may compare the user information in the binding relationship with the user information under the first account in the first system to determine whether the two are consistent.

A communication module 603, configured to send an update prompt message to the user and receive a response message for updating corresponding to a confirmation of the update prompt message when the determining module 602 determines that the second account bound to the first account exists in the second system and the user information in the binding relationship between the first account and the second account is inconsistent with the user information under the first account in the first system.

In an optional embodiment, the sending, by the communication module 603, the update prompting message to the user specifically includes: the communication module 603 determines whether the user information under the first account in the first system is already used by other accounts in the second system; if the determination result is yes, the communication module 603 sends a first update prompt message to the user; if the determination result is negative, the communication module 603 sends a second update prompting message to the user; wherein, the first updating prompt message comprises: prompt information indicating that the user information is used by other accounts in the second system and prompt information indicating whether the user information in the binding relationship is updated or not; the second update prompt message includes: and prompt information for judging whether to update the user information in the binding relationship.

The verifying module 604 is configured to verify whether the user information under the first account in the first system belongs to the user after receiving the response information for confirming the update.

In an alternative example, the user information to be authenticated is a mobile phone number. In this alternative example, the verification module 604 is specifically configured to: acquiring a verification code input by a user from the response information, and comparing the verification code input by the user with a short message verification code sent to a mobile phone number under a first account in the first system; and if the mobile phone number and the user number are consistent, determining that the mobile phone number belongs to the user. In addition, in specific implementation, if the verification code input by the user is inconsistent with the short message verification code sent to the mobile phone number, the short message verification code may be sent to the mobile phone number again, and the verification module 604 performs the verification again.

An updating module 605, configured to update the user information in the binding relationship according to the user information under the first account in the first system if the verification result of the verifying module 604 is yes. For example, when the user information under the first account of the first system is a mobile phone number, the updating module 503 may update the mobile phone number in the binding relationship according to the mobile phone number under the first account of the first system.

Further, the updating module 605 is further configured to set, as a failure, another account in the second system that uses the user information when the verification result of the verifying module 604 is yes and it is determined that the user information under the first account in the first system is used by another account in the second system.

In the embodiment of the invention, the device can automatically update the user information in the binding relationship of another system when the account information of one system is changed, and the user does not need to manually perform the operation of unbinding and binding the account, so that the complicated operation of the user is reduced, the user experience is improved, and the safety in the account information synchronization process can be improved. In addition, the device solves the problems of inconsistent account information in the two systems, inconvenience in use of users and the like caused by the fact that user information in the account binding relationship is not updated in the prior art.

Fig. 7 shows an exemplary system architecture 700 of a multi-system account information integration method or a multi-system account information integration apparatus to which an embodiment of the present invention may be applied.

As shown in fig. 7, the system architecture 700 may include

terminal devices

701, 702, 703, a network 704, and a server 705. The network 704 serves to provide a medium for communication links between the

terminal devices

701, 702, 703 and the server 705. Network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

A user may use the

terminal devices

701, 702, 703 to interact with a server 705 over a network 704, to receive or send messages or the like. Various communication client applications, such as an insurance and financing application, a web browser application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like, may be installed on the

terminal devices

701, 702, and 703.

The

terminal devices

701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 705 may be a server providing various services, such as a background management server providing support for insurance financing websites or clients browsed by users using the

terminal devices

701, 702, 703. The background management server may analyze and perform other processing on the received data such as the code scanning login request, and feed back a processing result (e.g., a system page after login) to the terminal device.

It should be noted that the multi-system account information integration method provided in the embodiment of the present invention is generally executed by the server 705, and accordingly, a multi-system account information integration apparatus is generally disposed in the server 705.

It should be understood that the number of terminal devices, networks, and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 8, shown is a block diagram of a computer system 800 suitable for use with a terminal device implementing an embodiment of the present invention. The computer system illustrated in FIG. 8 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the invention.

As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU)801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data necessary for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program executes the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 801.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes an acquisition module. The device comprises a verification module and an updating module. The names of the modules do not form a limitation on the modules themselves in some cases, for example, the obtaining module may also be described as a module for obtaining user information of a user under a first account in a first system.

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to perform the following: responding to a trigger operation of a user for logging in a second system, and acquiring user information of the user under a first account in a logged first system; under the condition that a second account bound with a first account exists in a second system and the user information in the binding relation between the first account and the second account is inconsistent with the user information under the first account in the first system, verifying whether the user information under the first account in the first system belongs to the user; and under the condition that the verification result is yes, updating the user information in the binding relationship according to the user information under the first account in the first system.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A multi-system account information integration method is characterized by comprising the following steps:

responding to a trigger operation of a user for logging in a second system, and acquiring user information of the user under a first account in a logged first system;

under the condition that a second account bound with a first account exists in a second system and the user information in the binding relation between the first account and the second account is inconsistent with the user information under the first account in the first system, verifying whether the user information under the first account in the first system belongs to the user;

if the verification result is yes, updating the user information in the binding relationship according to the user information under the first account in the first system;

the method further comprises the following steps:

sending binding prompt information to a user under the condition that a second account bound with a first account does not exist in a second system and the user information under the first account in the first system is used by other accounts in the second system; after response information corresponding to the binding prompt information and confirmed by the user to be bound is received, binding the first account with other accounts using the user information in a second system;

and/or the presence of a gas in the gas,

and under the condition that a second account bound with the first account does not exist in the second system and the user information under the first account in the first system is not used by other accounts in the second system, generating a new account in the second system according to the user information under the first account, and binding the first account with the new account.

2. The method of claim 1, further comprising:

before the step of verifying whether the user information under the first account in the first system belongs to the user is executed, sending update prompt information to the user, and receiving response information for updating corresponding to confirmation of the update prompt information.

3. The method of claim 2, wherein the user information under the first account in the first system comprises: a user mobile phone number;

the step of verifying whether the user information under the first account in the first system belongs to the user comprises: acquiring a verification code input by a user from the response information for confirming updating; comparing the verification code input by the user with the short message verification code sent to the mobile phone number of the user; and if the verification code input by the user is consistent with the short message verification code sent to the mobile phone number of the user, confirming that the user information under the first account number in the first system belongs to the user.

4. The method of claim 2, wherein the step of sending an update prompt to the user comprises:

judging whether the user information under the first account in the first system is used by other accounts in the second system; if the judgment result is yes, sending first updating prompt information to the user; under the condition that the judgment result is negative, sending second updating prompt information to the user; wherein, the first updating prompt message comprises: prompt information indicating that the user information is used by other accounts in the second system and prompt information indicating whether the user information in the binding relationship is updated or not; the second update prompt message includes: and prompt information for judging whether to update the user information in the binding relationship.

5. The method of claim 4, further comprising:

and if the verification result is yes and the user information under the first account in the first system is used by other accounts in the second system, setting other accounts using the user information in the second system as invalid.

6. A multi-system account information integration device is characterized by comprising:

the acquisition module is used for responding to the triggering operation of the user for logging in the second system and acquiring the user information of the user under the first account in the logged first system;

the verification module is used for verifying whether the user information under the first account in the first system belongs to the user or not under the condition that the second account bound with the first account exists in the second system and the user information in the binding relation between the first account and the second account is inconsistent with the user information under the first account in the first system;

the updating module is used for updating the user information in the binding relationship according to the user information under the first account in the first system under the condition that the verification result is yes;

the device further comprises:

the communication module is used for sending binding prompt information to the user when determining that a second account bound with the first account does not exist in the second system and the user information under the first account in the first system is used by other accounts in the second system; the binding module is used for binding the first account with other accounts using the user information in the second system after receiving response information of binding confirmation of the user corresponding to the binding prompt information;

and/or the presence of a gas in the gas,

the binding module is used for generating a new account in the second system according to the user information under the first account and binding the first account with the new account when it is determined that the second account bound with the first account does not exist in the second system and the user information under the first account in the first system is not used by other accounts in the second system.

7. The apparatus of claim 6, further comprising:

the communication module is used for sending update prompt information to the user and receiving response information for updating corresponding to the confirmation of the update prompt information before the verification module verifies whether the user information under the first account in the first system belongs to the user.

8. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-5.

9. A computer-readable medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the method of any one of claims 1 to 5.