CN105656946B - A kind of method, business service end and account server-side handling login account - Google Patents
A kind of method, business service end and account server-side handling login account Download PDFInfo
- Publication number
- CN105656946B CN105656946B CN201610188787.8A CN201610188787A CN105656946B CN 105656946 B CN105656946 B CN 105656946B CN 201610188787 A CN201610188787 A CN 201610188787A CN 105656946 B CN105656946 B CN 105656946B
- Authority
- CN
- China
- Prior art keywords
- account
- server
- user
- information corresponding
- user identification
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Power Engineering (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
A kind of method, business service end and account server-side for handling login account is announced herein, this method comprises: checking whether the User Identity account has other User Identity accounts in another business service end associated with the business service end when business service end judges that itself conflicts with account server-side there are account；When checking the User Identity account does not have other User Identity accounts in another business service end associated with the business service end, the corresponding login account information of the User Identity account of itself is sent to account server-side to notify account server-side to complete the binding of the corresponding login account information of the User Identity account by business service end；It is to have moved and user is notified to request keeps that business service end, which marks the state of the User Identity account,.The embodiment of the present invention solves the problems, such as the conflict of the account between different application and realizes data sharing, and the user experience is improved.
Description
Technical Field
The embodiment of the invention relates to but is not limited to an intelligent terminal technology, in particular to a method for processing a login account, a business server and an account server.
Background
With the continuous development of the mobile internet, more and more user data can be stored in the cloud instead of the mobile terminal. The basis for the user data to be correctly stored is the account system. When a user uses an application program (APP), the user needs to register at a client of the APP according to a user identity identification account (including a mobile phone number, a mailbox or a third party application account), and then requests a service server of the APP to log in or perform other operations. With the increase of APPs, a user needs to register an account at a client of each APP. When a user uses the same user identification account to register on clients of two APPs belonging to the same company, login account information possibly filled in is different, for example, a user name filled in APP1 is Zhang III, a user name filled in APP2 is Li IV, a communication address is filled in APP1, and a birthday of the user is filled in APP2, so that login account information of the same user identification account in different applications is different, account conflict is caused, and data sharing between different APPs of the same company cannot be realized.
Therefore, how to solve the problem of account conflicts among different applications and implement data sharing becomes a problem which needs to be solved urgently at present.
Disclosure of Invention
The application provides a method for processing a login account, a service server and an account server, which can solve the problem of account conflict among different applications, realize data sharing and improve user experience.
In order to achieve the purpose of the present application, the present application provides a method for processing a login account, including:
the service server judges whether an account conflict exists between the service server and a pre-established account server according to the received user identity identification account sent by the client;
when the business server judges that the business server has an account conflict with the account server, checking whether the user identity identification account has other user identity identification accounts in another business server related to the business server;
when the user identification account is checked to have no other user identification account in another service end associated with the service end, the service end sends login account information corresponding to the user identification account to the account service end so as to inform the account service end of finishing binding the login account information corresponding to the user identification account;
and the service server marks the state of the user identity identification account as transferred and informs the client of requesting the account server.
Optionally, the method further comprises, before: and creating an account server and importing login account information of another service terminal related to the service terminal into the account server.
Optionally, the login account information at least includes a user name and a user identification account;
the user identification account comprises: a mobile phone number, a mailbox or a third party application account.
Optionally, the determining, by the service end, whether an account conflict exists between the service end and a pre-created account service end according to the received user identity identification account includes:
the business server side searches whether the user identity identification account exists or not;
when the business server retrieves that the user identity identification account exists, the business server judges whether login account information corresponding to the user identity identification account is transferred to the account server;
when the business server side judges that login account information corresponding to the user identity identification account is not transferred to the account server side, the business server side requests the account server side to search whether the user identity identification account exists or not; when the account server side does not retrieve the user identity identification account, the business server side judges that no account conflict exists between the business server side and the account server side;
when the account server retrieves that the user identification account exists, the service server judges whether login account information corresponding to the user identification account of the service server is the same as login account information corresponding to the user identification account of the service server;
when the business server judges that the login account information corresponding to the user identification account of the business server is the same as the login account information corresponding to the user identification account of the account server, the business server judges that no account conflict exists between the business server and the account server;
when the business server side judges that login account information corresponding to the user identification account of the business server side is different from login account information corresponding to the user identification account of the account server side, the business server side judges that account conflict exists between the business server side and the account server side.
Optionally, when the service server determines that the login account information corresponding to the user identity identification account is not migrated to the account server, the method further includes: and the business server side migrates login account information corresponding to the user identification account into the account server side and marks the state of the user identification account as migrated.
Optionally, the determining, by the service end, whether login account information corresponding to the user identity identification account is migrated to the account service end includes:
the business server side retrieves the marked state of the user identity identification account;
when the marked state of the user identification account retrieved by the business server is transferred, the business server judges that login account information corresponding to the user identification account is transferred to the account server;
when the business server side does not retrieve that the marked state of the user identification account is transferred, the business server side judges that login account information corresponding to the user identification account is not transferred to the account server side.
Optionally, when the service server determines that the login account information corresponding to the user identity identification account is migrated to the account server, the method further includes: and the service server side informs the client side of requesting the account server.
Optionally, when the service server determines that login account information corresponding to the user identification account of the service server is the same as login account information corresponding to the user identification account of the service server, the method further includes: and the service server marks the state of the user identity identification account as transferred and informs the client to request the account server.
Optionally, when the service server does not retrieve the user identification account, the method further includes: and informing the client to request the account server.
Optionally, when it is checked that the user identification account has another user identification account in another service terminal associated with the service terminal, the method further includes: the account server backups login account information corresponding to the user identification account of the account server and login account information corresponding to the other detected user identification accounts;
the business server sends login account information corresponding to the user identification account to the account server so as to inform the account server of finishing binding the login account information corresponding to the user identification account; the business server marks the state of the user identity identification account as transferred and informs the client to request the account server;
and the business server sends the checked other user identification accounts to the account server to inform the account server to create the checked other user identification accounts and the corresponding log-in account information records.
The present application further provides a service server, including: the system comprises a first judgment module, a checking module, a first transceiver module, a mark processing module and a first notification module; wherein,
the first judgment module is used for judging whether the business server side to which the user belongs has account conflict with a pre-established account server side according to the received user identity identification account sent by the client side; when the fact that account conflict exists between the business server side to which the business server side belongs and the account server side is judged, a checking module is informed;
the checking module is used for receiving the notification from the first judging module and checking whether the user identification account has other user identification accounts in another service end related to the service end; when the user identification account is checked to have no other user identification account in another service terminal associated with the service terminal, the first transceiver module is informed;
the first transceiver module is used for receiving the notification of the checking module, and sending login account information corresponding to the user identification account of the service server to which the first transceiver module belongs to the account server so as to notify the account server of completing the binding of the login account information corresponding to the user identification account;
the marking processing module is used for marking the state of the user identity identification account as transferred;
and the first notification module is used for notifying the client to request the account server.
Optionally, the first determining module is specifically configured to:
searching whether a business server side to which the business server side belongs has the user identity identification account;
when the service server to which the service server belongs is searched to have the user identification account, judging whether login account information corresponding to the user identification account is transferred to the account server;
when the terminal judges that the login account information corresponding to the user identification account is not transferred to the account server, the account server is requested to search whether the user identification account exists or not; when the account server does not retrieve the user identity identification account, judging that no account conflict exists between the business server to which the account server belongs and the account server;
when the account server retrieves that the user identity identification account exists, judging whether login account information corresponding to the user identity identification account of the business server to which the account server belongs is the same as login account information corresponding to the user identity identification account of the account server;
when the fact that the login account information corresponding to the user identification account of the user is the same as the login account information corresponding to the user identification account of the account server is judged, it is judged that no account conflict exists between the business server to which the user belongs and the account server;
when the fact that the login account information corresponding to the user identification account of the business server side to which the user belongs is different from the login account information corresponding to the user identification account of the account server side is judged, the fact that account conflict exists between the user and the account server side is judged.
Optionally, the service end further includes a migration module;
the first judging module is further configured to notify the migration module when it is judged that login account information corresponding to the user identification account is not migrated to the account server; accordingly, the number of the first and second electrodes,
the migration module is used for migrating login account information corresponding to the user identification account into the account server and marking the state of the user identification account as migrated.
Optionally, the determining, by the first determining module, whether login account information corresponding to the user identity account is migrated to the account server includes:
retrieving the marked state of the user identification account;
when the marked state of the retrieved user identification account is transferred, judging that login account information corresponding to the user identification account is transferred to the account server;
and when the marked state of the user identification account is not retrieved and is transferred, judging that the login account information corresponding to the user identification account is not transferred to the account server.
Optionally, the first determining module is further configured to notify the first notifying module when the terminal determines that the login account information corresponding to the user identity account is migrated to the account server;
the first notification module is further configured to receive a notification from the first determination module, and notify the client to request the account server.
Optionally, the first determining module is further configured to notify the mark processing module when it is determined that login account information corresponding to the user id account of the service server to which the first determining module belongs is the same as login account information corresponding to the user id account of the account server;
the marking processing module is further configured to receive a notification from the first determining module, and mark the state of the user identity account as migrated; accordingly, the number of the first and second electrodes,
the first notification module is further configured to notify the client to request the account server.
Optionally, the first determining module is further configured to notify the first notification module when the service server to which the first determining module belongs is not retrieved and the user identity account exists;
the first notification module is further configured to receive a notification from the first determination module, and notify the client to request the account server.
Optionally, the checking module is further configured to notify the first transceiver module when it is checked that the user identification account has another user identification account in another service terminal associated with the service terminal; accordingly, the number of the first and second electrodes,
the first transceiver module is further configured to receive a notification from the checking module, and send login account information corresponding to the user identification account of the service server to which the first transceiver module belongs to the account server to notify the account server of completing binding of the login account information corresponding to the user identification account; accordingly, the number of the first and second electrodes,
the marking processing module is further configured to mark that the state of the user identification account is migrated;
the first notification module is further configured to notify the client of the request of the account server.
The application also provides an account server, including: the second transceiver module, the second judging module, the second informing module and the binding module; wherein,
the second transceiving module is used for receiving an account conflict request sent by the service server; receiving login account information corresponding to a user identity identification account of a business server;
the second judgment module is used for judging whether account conflict exists between the account server and the business server to which the second judgment module belongs according to the received account conflict request; when the fact that account conflict exists between the account server side to which the user belongs and the service server side is judged, a second notification module is notified;
the second notification module is used for receiving the notification from the second judgment module and notifying the service server that account conflict exists;
and the binding module is used for combining the received login account information corresponding to the user identification account of the service server with the login account information corresponding to the user identification account of the account server to which the binding module belongs.
Optionally, the account server further includes an importing module, configured to import login account information of another service server associated with the service server into the account server.
Optionally, the account server further includes a backup module, configured to backup login account information corresponding to the user id account of the account server to which the account server belongs and login account information corresponding to the checked other user id account when it is checked that the user id account has another user id account in another service server associated with the service server; accordingly, the number of the first and second electrodes,
the binding module is further configured to create a record of the checked other user identification account and the log-in account information corresponding to the other user identification account.
The embodiment of the invention comprises the following steps: the service terminal judges whether an account conflict exists between the service terminal and a pre-established account server according to a received user identity identification account sent by a user; when the business server judges that the business server has an account conflict with the account server, checking whether the user identity identification account has other user identity identification accounts in another business server related to the business server; when the user identification account is checked to have no other user identification account in another service end associated with the service end, the service end sends login account information corresponding to the user identification account to the account service end so as to inform the account service end of finishing binding the login account information corresponding to the user identification account; and the service server marks the state of the user identity identification account as transferred and informs the user of requesting the account server. The embodiment of the invention solves the problem of account number conflict among different applications, realizes data sharing and improves user experience.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a flowchart of a method for handling a login account according to the present invention;
FIG. 2 is a flowchart of an embodiment of a method for processing a login account according to the present invention;
FIG. 3 is a schematic structural diagram of a service end according to the present invention;
fig. 4 is a schematic structural diagram of the account server according to the present invention.
Detailed Description
The technical solution of the present invention will be described in more detail with reference to the accompanying drawings and examples.
A mobile terminal implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in themselves. Thus, "module" and "component" may be used in a mixture.
Fig. 1 is a flowchart of a method for processing a login account according to the present invention, as shown in fig. 1, including:
step 101: and the service server judges whether the service server has account conflict with a pre-established account server according to the received user identity identification account sent by the client.
The method specifically comprises the following steps:
the service server searches whether the user identity identification account exists or not;
when the business server retrieves that the user identity identification account exists, the business server judges whether login account information corresponding to the user identity identification account is transferred to the account server;
when the business server side judges that login account information corresponding to the user identity identification account is not transferred to the account server side, the business server side requests the account server side to search whether the user identity identification account exists or not; when the account server side does not retrieve the user identity identification account, the service server side judges that no account conflict exists between the service server side and the account server side;
when the account server retrieves the user identification account, the service server judges whether login account information corresponding to the user identification account of the service server is the same as login account information corresponding to the user identification account of the account server;
when the business server judges that the login account information corresponding to the user identification account of the business server is the same as the login account information corresponding to the user identification account of the account server, the business server judges that no account conflict exists between the business server and the account server;
when the business server side judges that the login account information corresponding to the user identification account of the business server side is different from the login account information corresponding to the user identification account of the account server side, the business server side judges that account conflict exists between the business server side and the account server side. The business server requesting the account server to search whether the user identification account exists or not comprises the following steps: the service terminal sends the user identity identification account to an account server terminal; the account server searches whether the account server has a user identity identification account.
Optionally, when the service end determines that the login account information corresponding to the user identity identification account is not migrated to the account service end, the method further includes: and the service server migrates login account information corresponding to the user identification account into the account server and marks the state of the user identification account as migrated.
The business server judges whether login account information corresponding to the user identity identification account is transferred to the account server or not, wherein the step of judging whether the login account information corresponding to the user identity identification account is transferred to the account server comprises the following steps:
the service end searches the marked state of the user identity identification account;
when the marked state of the user identification account retrieved by the service terminal is transferred, the service terminal judges that login account information corresponding to the user identification account is transferred to the account server terminal;
when the business server side does not retrieve that the marked state of the user identification account is transferred, the business server side judges that the login account information corresponding to the user identification account is not transferred to the account server side.
Optionally, when the service end determines that the login account information corresponding to the user identity identification account is migrated to the account service end, the method further includes: and the service server informs the client of requesting an account server.
Optionally, when the service end determines that the login account information corresponding to the user identification account of the service end is the same as the login account information corresponding to the user identification account of the account service end, the method further includes: and the service server marks the state of the user identity identification account as transferred and informs the client to request the account server.
Optionally, when the service end does not retrieve the user identification account, the method further includes: and informing the client to request the account server.
Step 102: when the business server judges that the business server has an account conflict with the account server, whether the user identification account has other user identification accounts in another business server related to the business server is checked.
Here, the association means that the application corresponding to the business service end and the application corresponding to another business service belong to the same company (or manufacturer).
Optionally, the method further comprises, before: and creating an account server and importing login account information of another business server related to the business server into the account server.
Step 103: when the fact that the user identification account does not have other user identification accounts in another service end related to the service end is detected, the service end sends login account information corresponding to the user identification account to the account service end so as to inform the account service end of finishing binding the login account information corresponding to the user identification account.
The login account information at least comprises a user name and a user identity identification account;
the user identification account comprises: a mobile phone number, a mailbox or a third party application account. Optionally, the login account information may further include user personal information, such as gender, and/or hobbies, and/or date of birth, and/or address.
The account server side binding the login account information corresponding to the user identification account comprises the following steps: the account server side combines the received login account information corresponding to the user identification account of the business server side with the login account information corresponding to the user identification account of the business server side. Optionally, after the service end sends login account information corresponding to the user identification account of the service end to the account service end, before the account service end completes binding of the login account information corresponding to the user identification account, the method further includes: the account server prompts a user whether to combine login account information corresponding to a user identification account of the account server with login account information corresponding to the user identification account of the service server; when detecting that a user does not need to merge login account information corresponding to a user identification account of an account server and login account information corresponding to the user identification account of a service server, the account server does not merge the login account information corresponding to the user identification account of the account server and the login account information corresponding to the user identification account of the service server; and when detecting that the user needs to combine the login account information corresponding to the user identification account of the account server with the login account information corresponding to the user identification account of the service server, switching to the step that the account server completes the binding of the login account information corresponding to the user identification account.
Optionally, when it is checked that the user identification account has another user identification account in another service terminal associated with the service terminal, the method further includes: the account server backups login account information corresponding to a user identification account of the account server and login account information corresponding to other detected user identification accounts;
the service server sends login account information corresponding to a user identity identification account to the account server so as to inform the account server of finishing binding the login account information corresponding to the user identity identification account; the service server marks the state of the user identity identification account as transferred and informs the client to request an account server;
and the business server sends the checked other user identification accounts to the account server to inform the account server to create the checked other user identification accounts and the corresponding records of login account information.
Step 104: and the service server marks the state of the user identity identification account as transferred and informs the client of requesting the account server.
In the embodiment of the invention, when the business server judges that the business server has an account conflict with the account server and checks that the user identification account does not have other user identification accounts in another business server associated with the business server, the business server sends the login account information corresponding to the user identification account to the account server to inform the account server to finish the binding of the login account information corresponding to the user identification account and to inform the client to request the account server when the business server marks the state of the user identification account as migrated, so that the problem of account conflict among different applications is solved, data sharing is realized, and user experience is improved.
Fig. 2 is a flowchart of an embodiment of a method for processing a login account according to the present invention, as shown in fig. 2, the method includes:
step 201: and creating an account server and importing login account information of another business server related to the business server into the account server.
It should be noted that how to create the account server belongs to the conventional technical means known to those skilled in the art, and the description is not repeated herein, and is not intended to limit the present invention.
Step 202: and the service server receives a request carrying a user identity identification account sent by the client.
Step 203: and the service server searches whether the user identity identification account exists or not. When the service server retrieves that the service server has the user identification account, the step 204 is carried out; when the service end does not retrieve the account with the user identity, the process proceeds to step 211.
Step 204: and the service server judges whether login account information corresponding to the user identity identification account is transferred to the account server. When the service end judges that the login account information corresponding to the user identity identification account is not transferred to the account service end, the operation proceeds to step 205; when the service end determines that the login account information corresponding to the user identification account is migrated to the account service end, the process proceeds to step 211.
The login account information at least comprises a user name and a user identity identification account;
the user identification account comprises: a mobile phone number, a mailbox or a third party application account. Optionally, the login account information may further include user personal information, such as gender, and/or hobbies, and/or date of birth, and/or address.
Wherein, this step specifically includes:
the service end searches the marked state of the user identity identification account;
when the marked state of the user identification account retrieved by the service terminal is transferred, the service terminal judges that login account information corresponding to the user identification account is transferred to the account server terminal;
when the business server side does not retrieve that the marked state of the user identification account is transferred, the business server side judges that the login account information corresponding to the user identification account is not transferred to the account server side.
Step 205: the service terminal requests the account server terminal to search whether the service terminal has a user identity identification account. When the account server retrieves the user identification account, step 206 is performed; when the account server does not retrieve the account with the user identification, the process proceeds to step 212.
Step 206: the service terminal judges whether the login account information corresponding to the user identification account of the service terminal is the same as the login account information corresponding to the user identification account of the account service terminal. When the service end judges that the login account information corresponding to the user identification account of the service end is the same as the login account information corresponding to the user identification account of the service end, the operation proceeds to step 207; when the service end judges that the login account information corresponding to the user identification account of the service end is different from the login account information corresponding to the user identification account of the account service end, the operation proceeds to step 208.
When the business server judges that login account information corresponding to the user identification account of the business server is different from login account information corresponding to the user identification account of the account server, the business server judges that account conflict exists between the business server and the account server; when the business server side judges that the login account information corresponding to the user identification account of the business server side is the same as the login account information corresponding to the user identification account of the account server side, the business server side judges that no account conflict exists between the business server side and the account server side.
Step 207: and the service server marks the state of the user identity identification account as migrated. Proceed to step 211.
Step 208: and checking whether the user identification account has other user identification accounts in another service end associated with the service end. When it is checked that the user id account does not have any other user id account in another service end associated with the service end, go to step 209; otherwise, go to step 210.
Step 209: and the service server sends login account information corresponding to the user identification account to the account server so as to inform the account server of finishing binding the login account information corresponding to the user identification account.
Step 210: and the business server sends the checked other user identification accounts to the account server to inform the account server to create the checked other user identification accounts and the corresponding records of login account information.
Step 211: and the service server informs the client of requesting the account number server.
Step 212: and the account server informs the service server of returning login account information corresponding to the user identity identification account. Proceed to step 207.
Fig. 3 is a schematic structural diagram of a service end of the present invention, as shown in fig. 3, including: a first judging module 30, a checking module 31, a first transceiver module 32, a mark processing module 33 and a first notification module 34. Wherein,
the first judging module 30 is configured to judge whether an account conflict exists between a service server to which the client belongs and a pre-established account server according to a received user identity identification account sent by the client; and when determining that the account conflict exists between the service end to which the service end belongs and the account service end, notifying the checking module 31.
The first determining module 30 is specifically configured to:
searching whether a business server side of the business server side has a user identity identification account;
when a business server to which the business server belongs is searched to have a user identity identification account, judging whether login account information corresponding to the user identity identification account is transferred to the account server;
when judging that the login account information corresponding to the user identification account is not transferred to the account server, requesting the account server to search whether the user identification account exists or not; when the account server does not retrieve the user identity identification account, judging that no account conflict exists between the business server and the account server;
when the account server retrieves the user identification account, judging whether login account information corresponding to the user identification account of the business server to which the account server belongs is the same as login account information corresponding to the user identification account of the account server;
when the fact that the login account information corresponding to the user identification account of the user is the same as the login account information corresponding to the user identification account of the account server is judged, it is judged that no account conflict exists between the business server and the account server to which the user belongs;
and when the fact that the login account information corresponding to the user identification account of the business server side to which the user belongs is different from the login account information corresponding to the user identification account of the account server side is judged, the fact that account conflict exists between the user and the account server side is judged.
The first determining module 30 determines whether the login account information corresponding to the user identification account is migrated to the account server, including:
retrieving the marked state of the user identification account;
when the marked state of the retrieved user identification account is transferred, judging that login account information corresponding to the user identification account is transferred to an account server;
and when the marked state of the user identification account is not retrieved and is transferred, judging that the login account information corresponding to the user identification account is not transferred to the account server.
A checking module 31, configured to receive the notification from the first determining module 30, and check whether the user id account has another user id account in another service end associated with the service end; when it is checked that the user id account does not have any other user id account in another service end associated with the service end, the first transceiver module 32 is notified.
The first transceiver module 32 is configured to receive the notification from the checking module 31, and send login account information corresponding to the user id account of the service server to the account server to notify the account server of completing binding of the login account information corresponding to the user id account.
The login account information at least comprises a user name and a user identity identification account;
the user identification account comprises: a mobile phone number, a mailbox or a third party application account. The third-party application account comprises a WeChat account or a microblog account and the like.
Optionally, the login account information may further include user personal information, such as gender, and/or hobbies, and/or date of birth, and/or address.
Optionally, the first transceiver module 32 is further configured to receive a request carrying a user identity account sent by the client.
The first determining module 30 determines whether the login account information corresponding to the user id account of the service end to which the first determining module belongs is the same as the login account information corresponding to the user id account of the account service end, including: the first transceiver module 32 is notified to send an account conflict request to the account server; judging whether login account information corresponding to a user identity identification account of a business server to which the account server belongs is the same as login account information corresponding to a user identity identification account of the account server according to a notification whether account conflict exists or not, wherein the notification is sent by the account server;
accordingly, the number of the first and second electrodes,
the first transceiver module 32 is further configured to receive the notification from the first determining module 30, and send an account conflict request to the account server; and receiving a notification whether account conflict exists or not, which is sent by an account server.
The account conflict request carries login account information corresponding to a user identity identification account of the service server.
And the marking processing module 33 is used for marking the state of the user identification account as migrated.
The first notification module 34 is configured to notify the client of the request of the account server.
Optionally, the first determining module 30 is further configured to notify the first notifying module 34 when it is determined that the login account information corresponding to the user identity account is migrated to the account server;
the first notification module 34 is further configured to receive a notification from the first determination module 30, notifying the client to request the account server.
Optionally, the service end further includes a migration module 35; at this time, the process of the present invention,
the first determining module 30 is further configured to notify the migration module 35 when it is determined that the login account information corresponding to the user identity identification account is not migrated to the account server; accordingly, the number of the first and second electrodes,
the migration module 35 is configured to migrate login account information corresponding to the user id account to the account server and mark the state of the user id account as migrated.
Optionally, the first determining module 30 is further configured to notify the mark processing module 33 when it is determined that login account information corresponding to the user identification account of the service server to which the first determining module belongs is the same as login account information corresponding to the user identification account of the account server;
the marking processing module 33 is further configured to receive a notification from the first determining module 30, and mark the state of the user id account as migrated; accordingly, the number of the first and second electrodes,
the first notification module 34 is further configured to notify the client of the request for the account server.
Optionally, the first determining module 30 is further configured to notify the first notifying module 34 when the service server to which the first determining module belongs does not retrieve the user identification account;
the first notification module 34 is further configured to receive a notification from the first determination module 30, notifying the client to request the account server.
Optionally, the checking module 31 is further configured to notify the first transceiver module 32 when it is checked that the user identification account has another user identification account in another service end associated with the service end; accordingly, the number of the first and second electrodes,
the first transceiver module 32 is further configured to receive the notification from the checking module 31, and send login account information corresponding to the user identification account of the service server to which the first transceiver module belongs to the account server to notify the account server of completing binding of the login account information corresponding to the user identification account; accordingly, the number of the first and second electrodes,
the marking processing module 33 is further configured to mark that the status of the user identity identification account is migrated;
the first notification module 34 is further configured to notify the client of the request for the account server.
Fig. 4 is a schematic structural diagram of the account server according to the present invention, as shown in fig. 4, including: a second transceiver module 40, a second determination module 41, a second notification module 42, and a binding module 43. Wherein,
the second transceiving module 40 is configured to receive an account collision request sent by a service server; and receiving login account information corresponding to the user identity identification account of the service server.
The second judging module 41 is configured to judge whether an account conflict exists between the account server and the service server according to the received account conflict request; and when the account number conflict between the account number service end to which the user belongs and the service end is judged, the second notification module 42 is notified.
And the second notification module 42 is configured to receive a notification from the second determining module 41, and notify the service end that an account conflict exists.
The binding module 43 is configured to combine the received login account information corresponding to the user id account of the service server with the login account information corresponding to the user id account of the account server to which the binding module belongs.
Optionally, the account server further includes an importing module 44, configured to import login account information of another business server associated with the business server into the account server.
The login account information at least comprises a user name and a user identity identification account;
the user identification account comprises: a mobile phone number, a mailbox or a third party application account. The third-party application account comprises a WeChat account or a microblog account and the like.
Optionally, the login account information may further include user personal information, such as gender, and/or hobbies, and/or date of birth, and/or address.
Optionally, the account server further includes a backup module 45, configured to backup login account information corresponding to the user id account of the account server to which the account server belongs and login account information corresponding to the other detected user id account when it is detected that the user id account has another user id account in another service server associated with the service server; accordingly, the number of the first and second electrodes,
the binding module 43 is further configured to create a record of the checked other user id accounts and their corresponding login account information.
Optionally, the account server further includes a recovery module 46, configured to prompt a user whether to merge login account information corresponding to a user identification account of an account server to which the user belongs with login account information corresponding to the user identification account of a service server; when detecting that a user does not need to merge login account information corresponding to a user identification account of an account server to which the user belongs and login account information corresponding to the user identification account of a service server, the login account information corresponding to the user identification account of the account server to which the user belongs and the login account information corresponding to the user identification account of the service server are not merged; when detecting that the user needs to combine the login account information corresponding to the user identification account of the account server to which the user belongs with the login account information corresponding to the user identification account of the service server, notifying the binding module 43; accordingly, the number of the first and second electrodes,
the binding module 43 is specifically configured to, after receiving the notification from the reply module, combine the received login account information corresponding to the user identification account of the service server with the login account information corresponding to the user identification account of the account server to which the binding module belongs.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by a program instructing associated hardware (e.g., a processor) to perform the steps, and the program may be stored in a computer readable storage medium, such as a read only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, the modules/units in the above embodiments may be implemented in hardware, for example, by an integrated circuit, or may be implemented in software, for example, by a processor executing programs/instructions stored in a memory to implement the corresponding functions. The present invention is not limited to any specific form of combination of hardware and software.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are included in the scope of the present application.
Claims (20)
1. A method for processing a login account is characterized by comprising the following steps:
the service server judges whether an account conflict exists between the service server and a pre-established account server according to the received user identity identification account sent by the client;
when the business server judges that the business server has an account conflict with the account server, checking whether the user identity identification account has other user identity identification accounts in another business server related to the business server;
when the user identification account is checked to have no other user identification account in another service end associated with the service end, the service end sends login account information corresponding to the user identification account to the account service end so as to inform the account service end of finishing binding the login account information corresponding to the user identification account;
and the service server marks the state of the user identity identification account as transferred and informs the client of requesting the account server.
2. The method of claim 1, further comprising, prior to the method: and creating an account server and importing login account information of another service terminal related to the service terminal into the account server.
3. The method according to claim 1 or 2, wherein the login account information at least comprises a user name and a user identification account;
the user identification account comprises: a mobile phone number, a mailbox or a third party application account.
4. The method according to claim 1 or 2, wherein the step of the service terminal judging whether an account conflict exists between the service terminal and a pre-established account service terminal according to the received user identity identification account comprises the following steps:
the business server side searches whether the user identity identification account exists or not;
when the business server retrieves that the user identity identification account exists, the business server judges whether login account information corresponding to the user identity identification account is transferred to the account server;
when the business server side judges that login account information corresponding to the user identity identification account is not transferred to the account server side, the business server side requests the account server side to search whether the user identity identification account exists or not; when the account server side does not retrieve the user identity identification account, the business server side judges that no account conflict exists between the business server side and the account server side;
when the account server retrieves that the user identification account exists, the service server judges whether login account information corresponding to the user identification account of the service server is the same as login account information corresponding to the user identification account of the service server;
when the business server judges that the login account information corresponding to the user identification account of the business server is the same as the login account information corresponding to the user identification account of the account server, the business server judges that no account conflict exists between the business server and the account server;
when the business server side judges that login account information corresponding to the user identification account of the business server side is different from login account information corresponding to the user identification account of the account server side, the business server side judges that account conflict exists between the business server side and the account server side.
5. The method according to claim 4, wherein when the service end determines that the login account information corresponding to the user identification account is not migrated to the account service end, the method further comprises: and the business server side migrates login account information corresponding to the user identification account into the account server side and marks the state of the user identification account as migrated.
6. The method of claim 4, wherein the step of the service side determining whether the login account information corresponding to the user identification account is migrated to the account service side comprises:
the business server side retrieves the marked state of the user identity identification account;
when the marked state of the user identification account retrieved by the business server is transferred, the business server judges that login account information corresponding to the user identification account is transferred to the account server;
when the business server side does not retrieve that the marked state of the user identification account is transferred, the business server side judges that login account information corresponding to the user identification account is not transferred to the account server side.
7. The method according to claim 6, wherein when the service server determines that the login account information corresponding to the user identification account is migrated to the account server, the method further comprises: and the service server side informs the client side of requesting the account server.
8. The method of claim 4, wherein when the service server determines that login account information corresponding to the user identification account of the service server is the same as login account information corresponding to the user identification account of the service server, the method further comprises: and the service server marks the state of the user identity identification account as transferred and informs the client to request the account server.
9. The method of claim 4, wherein when the service end does not retrieve the account with the user identity, the method further comprises: and informing the client to request the account server.
10. The method of claim 1, wherein when the user id account is detected to have another user id account in another service associated with the service, the method further comprises: the account server backups login account information corresponding to the user identification account of the account server and login account information corresponding to the other detected user identification accounts;
the business server sends login account information corresponding to the user identification account to the account server so as to inform the account server of finishing binding the login account information corresponding to the user identification account; the business server marks the state of the user identity identification account as transferred and informs the client to request the account server;
and the business server sends the checked other user identification accounts to the account server to inform the account server to create the checked other user identification accounts and the corresponding log-in account information records.
11. A service end, comprising: the system comprises a first judgment module, a checking module, a first transceiver module, a mark processing module and a first notification module; wherein,
the first judgment module is used for judging whether the business server side to which the user belongs has account conflict with a pre-established account server side according to the received user identity identification account sent by the client side; when the fact that account conflict exists between the business server side to which the business server side belongs and the account server side is judged, a checking module is informed;
the checking module is used for receiving the notification from the first judging module and checking whether the user identification account has other user identification accounts in another service end related to the service end; when the user identification account is checked to have no other user identification account in another service terminal associated with the service terminal, the first transceiver module is informed;
the first transceiver module is used for receiving the notification of the checking module, and sending login account information corresponding to the user identification account of the service server to which the first transceiver module belongs to the account server so as to notify the account server of completing the binding of the login account information corresponding to the user identification account;
the marking processing module is used for marking the state of the user identity identification account as transferred;
and the first notification module is used for notifying the client to request the account server.
12. The service server according to claim 11, wherein the first determining module is specifically configured to:
searching whether a business server side to which the business server side belongs has the user identity identification account;
when the service server to which the service server belongs is searched to have the user identification account, judging whether login account information corresponding to the user identification account is transferred to the account server;
when judging that the login account information corresponding to the user identification account is not transferred to the account server, requesting the account server to search whether the user identification account exists or not; when the account server does not retrieve the user identity identification account, judging that no account conflict exists between the business server to which the account server belongs and the account server;
when the account server retrieves that the user identity identification account exists, judging whether login account information corresponding to the user identity identification account of the business server to which the account server belongs is the same as login account information corresponding to the user identity identification account of the account server;
when the fact that the login account information corresponding to the user identification account of the user is the same as the login account information corresponding to the user identification account of the account server is judged, it is judged that no account conflict exists between the business server to which the user belongs and the account server;
when the fact that the login account information corresponding to the user identification account of the business server side to which the user belongs is different from the login account information corresponding to the user identification account of the account server side is judged, the fact that account conflict exists between the user and the account server side is judged.
13. The service end of claim 12, wherein the service end further comprises a migration module;
the first judging module is further configured to notify the migration module when it is judged that login account information corresponding to the user identification account is not migrated to the account server; accordingly, the number of the first and second electrodes,
the migration module is used for migrating login account information corresponding to the user identification account into the account server and marking the state of the user identification account as migrated.
14. The service server according to claim 12, wherein the determining, by the first determining module, whether login account information corresponding to the user id account is migrated to the account server comprises:
retrieving the marked state of the user identification account;
when the marked state of the retrieved user identification account is transferred, judging that login account information corresponding to the user identification account is transferred to the account server;
and when the marked state of the user identification account is not retrieved and is transferred, judging that the login account information corresponding to the user identification account is not transferred to the account server.
15. The service server according to claim 13, wherein the first determining module is further configured to notify the first notifying module when it is determined that login account information corresponding to the user identification account is migrated to the account server;
the first notification module is further configured to receive a notification from the first determination module, and notify the client to request the account server.
16. The service server of claim 12, wherein the first determining module is further configured to notify the mark processing module when it is determined that login account information corresponding to the user id account of the service server to which the first determining module belongs is the same as login account information corresponding to the user id account of the account server;
the marking processing module is further configured to receive a notification from the first determining module, and mark the state of the user identity account as migrated; accordingly, the number of the first and second electrodes,
the first notification module is further configured to notify the client to request the account server.
17. The service server according to claim 12, wherein the first determining module is further configured to notify the first notifying module when the service server to which the service server belongs has the user id account, which is not retrieved;
the first notification module is further configured to receive a notification from the first determination module, and notify the client to request the account server.
18. The service server according to claim 11, wherein the checking module is further configured to notify the first transceiver module when it is checked that the user id account has another user id account in another service server associated with the service server; accordingly, the number of the first and second electrodes,
the first transceiver module is further configured to receive a notification from the checking module, and send login account information corresponding to the user identification account of the service server to which the first transceiver module belongs to the account server to notify the account server of completing binding of the login account information corresponding to the user identification account; accordingly, the number of the first and second electrodes,
the marking processing module is further configured to mark that the state of the user identification account is migrated;
the first notification module is further configured to notify the client of the request of the account server.
19. An account server, comprising: the device comprises a second transceiver module, a second judgment module, a second notification module, a binding module and an importing module; wherein,
the second transceiving module is used for receiving an account conflict request sent by the service server; receiving login account information corresponding to a user identity identification account of a business server;
the second judgment module is used for judging whether account conflict exists between the account server and the business server to which the second judgment module belongs according to the received account conflict request; when the fact that account conflict exists between the account server side to which the user belongs and the service server side is judged, a second notification module is notified;
the second notification module is used for receiving the notification from the second judgment module and notifying the service server that account conflict exists;
the binding module is used for combining the received login account information corresponding to the user identification account of the service server with the login account information corresponding to the user identification account of the account server to which the binding module belongs;
and the import module is used for importing login account information of another business server associated with the business server into the account server.
20. The account server according to claim 19, wherein the account server further comprises a backup module, configured to backup login account information corresponding to the user id account of the account server to which the account server belongs and login account information corresponding to the detected other user id account when it is detected that the user id account has another user id account in another service server associated with the service server; accordingly, the number of the first and second electrodes,
the binding module is further configured to create a record of the checked other user identification account and the log-in account information corresponding to the other user identification account.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610188787.8A CN105656946B (en) | 2016-03-29 | 2016-03-29 | A kind of method, business service end and account server-side handling login account |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610188787.8A CN105656946B (en) | 2016-03-29 | 2016-03-29 | A kind of method, business service end and account server-side handling login account |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105656946A CN105656946A (en) | 2016-06-08 |
| CN105656946B true CN105656946B (en) | 2019-04-19 |
Family
ID=56495834
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610188787.8A Active CN105656946B (en) | 2016-03-29 | 2016-03-29 | A kind of method, business service end and account server-side handling login account |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105656946B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110019508B (en) * | 2017-09-28 | 2021-05-07 | 北京国双科技有限公司 | Data synchronization method, device and system |
| CN108234475B (en) * | 2017-12-28 | 2019-03-26 | 掌阅科技股份有限公司 | Account management method, electronic equipment and computer storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103268233A (en) * | 2013-06-05 | 2013-08-28 | 四目信息科技（上海）有限公司 | Method for combining account number of platform system and account number of third party system in computer system |
| CN104753943A (en) * | 2015-03-30 | 2015-07-01 | 努比亚技术有限公司 | Method and device for log-in control of third-party account |
| CN105024975A (en) * | 2014-04-23 | 2015-11-04 | 腾讯科技（北京）有限公司 | Account number login method, device and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8955065B2 (en) * | 2012-02-01 | 2015-02-10 | Amazon Technologies, Inc. | Recovery of managed security credentials |
-
2016
- 2016-03-29 CN CN201610188787.8A patent/CN105656946B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103268233A (en) * | 2013-06-05 | 2013-08-28 | 四目信息科技（上海）有限公司 | Method for combining account number of platform system and account number of third party system in computer system |
| CN105024975A (en) * | 2014-04-23 | 2015-11-04 | 腾讯科技（北京）有限公司 | Account number login method, device and system |
| CN104753943A (en) * | 2015-03-30 | 2015-07-01 | 努比亚技术有限公司 | Method and device for log-in control of third-party account |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105656946A (en) | 2016-06-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10257187B2 (en) | Prompting login account | |
| CN104025539B (en) | The method and apparatus for promoting single-sign-on services | |
| CN109428737B (en) | Method for changing group type, group creation method and device | |
| EP3541098B1 (en) | Processing method for communication identifier binding and terminal | |
| JP2017528845A (en) | System and method for partition identifier determination in a multi-tenant application server environment | |
| CN109831494B (en) | User data management method and device | |
| CN106302595B (en) | Method and equipment for carrying out health check on server | |
| US20130179495A1 (en) | System and method for alerting leakage of personal information in cloud computing environment | |
| US20200036812A1 (en) | Resource Download Method, Electronic Device, and Apparatus | |
| CN106227893A (en) | A kind of file type acquisition methods and device | |
| CN106294387B (en) | Data migration method and device | |
| US8510423B2 (en) | Install system and install method | |
| CN105656946B (en) | A kind of method, business service end and account server-side handling login account | |
| CN104618388A (en) | Quick registration and login method and corresponding reset server and information server | |
| WO2015184094A1 (en) | Data uniqueness control and information storage | |
| CN106156190B (en) | Data pushing method and device | |
| CN110365640A (en) | Method and device for controlling single page application routing | |
| CN107886008B (en) | File management method, system, device and computer readable storage medium | |
| US20140297953A1 (en) | Removable Storage Device Identity and Configuration Information | |
| CN110830492B (en) | Method and system for mutually scheduling edge applications based on CoreDNS registration service | |
| US20160065679A1 (en) | Registration of document services provided by an online document management system | |
| CN105187508A (en) | User relationship processing method and system | |
| CN116074921A (en) | Network slice connection method, device, equipment and medium | |
| US10949397B1 (en) | Data locking and state management on distributed storage systems | |
| CN113806393B (en) | Electronic resource processing method and device, electronic equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20201230 Address after: 18 / F, A1 North building, 32 Fengzhan Road, Yuhuatai District, Nanjing, Jiangsu 225000 Patentee after: Jiangsu Huchuan Technology Co.,Ltd. Address before: 518000 6-8 / F, 10-11 / F, 6 / F, 6-10 / F, C zone, Han's innovation building, No. 9018, Beihuan Avenue, high tech Zone, Nanshan District, Shenzhen City, Guangdong Province Patentee before: NUBIA TECHNOLOGY Co.,Ltd. |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: A method for handling login accounts, business server, and account server Effective date of registration: 20231130 Granted publication date: 20190419 Pledgee: Nanjing Bank Co.,Ltd. Nanjing Financial City Branch Pledgor: Jiangsu Huchuan Technology Co.,Ltd. Registration number: Y2023980067998 |