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
- user identity
- service end
- business service
- server
- 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
- 238000000034 method Methods 0.000 title claims abstract description 48
- 238000012545 processing Methods 0.000 claims description 19
- 238000012546 transfer Methods 0.000 claims description 17
- 230000008676 import Effects 0.000 claims description 10
- 230000005540 biological transmission Effects 0.000 claims description 4
- 238000007689 inspection Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 101150053844 APP1 gene Proteins 0.000 description 2
- 101100055496 Arabidopsis thaliana APP2 gene Proteins 0.000 description 2
- 101100189105 Homo sapiens PABPC4 gene Proteins 0.000 description 2
- 102100039424 Polyadenylate-binding protein 4 Human genes 0.000 description 2
- 101100016250 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) GYL1 gene Proteins 0.000 description 2
- 238000004080 punching Methods 0.000 description 2
- 238000007796 conventional method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
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
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 present embodiments relate to but be not limited to intelligent terminal technology, espespecially it is a kind of handle login account method, business
Server-side and account server-side.
Background technique
With the continuous development of mobile Internet, more and more users' data can all be stored beyond the clouds, rather than mobile
Terminal local.And the basis that these user data can be saved correctly is exactly account system.User uses application program (APP)
When, then it needs in the client of APP according to User Identity account (including cell-phone number, mailbox or third-party application account)
It is registered, the business service end of the APP is then requested to carry out login or other operations.With increasing for APP, user needs
The client registers account of each APP.When user is belonging to the two of same company using the same User Identity account
When being registered in the client of a APP, it is possible to which the login account information filled in is different, the use such as filled in APP1
Name in an account book is Zhang San, and the user name filled in APP2 is Li Si, and address is filled in APP1, and is filled in APP2
The birthday of user results in login account information of the same User Identity account in different application different in this way, from
And account conflict is led to the problem of, and cannot achieve the data sharing between same company's difference APP.
Therefore, how to solve the problems, such as that the account conflict between different application and realization data sharing become currently to need
It solves the problems, such as.
Summary of the invention
This application provides a kind of method, business service end and account server-sides for handling login account, are able to solve not
With the problem of account conflict between application and data sharing is realized, user experience is promoted.
In order to reach the application purpose, this application provides a kind of methods for handling login account, comprising:
Business service end according to the User Identity account that the client that receives is sent judge itself whether in advance
There are account conflicts for the account server-side of creation；
When business service end judges that itself conflicts with account server-side there are account, the User Identity account is checked
Number whether there are other User Identity accounts in another business service end associated with the business service end；
Do not have when checking the User Identity account in another business service end associated with the business service end
When having other User Identity accounts, the corresponding login account of the User Identity account of itself is believed at business service end
Breath is sent to account server-side to notify account server-side to complete the corresponding login account information of the User Identity account
Binding；
It is to have moved and client request account is notified to take that business service end, which marks the state of the User Identity account,
Business device.
Optionally, before this method further include: creation account server-side simultaneously will be associated with the business service end another
The login account information at one business service end imports in the account server-side.
Optionally, the login account information includes at least user name and User Identity account；
The User Identity account includes: phone number, mailbox or third-party application account.
Optionally, the business service end according to the User Identity account received judge itself whether with preparatory wound
There are account conflicts to include: for the account server-side built
Whether the business service end is retrieved itself the User Identity account；
When the business service end, which retrieves, itself the User Identity account, the business service end judgement
Whether the corresponding login account information of the User Identity account migrates into the account server-side；
When the business service end judge the corresponding login account information of the User Identity account do not migrate to
When in the account server-side, the business service end requests the account server-side to retrieve whether itself has the user identity
Identify account；When the account server-side, which does not retrieve, itself the User Identity account, the business service end is sentenced
It is disconnected to go out itself to conflict with the account server-side there is no account；
When the account server-side, which retrieves, itself the User Identity account, the business service end judgement
The user identity mark of itself the corresponding login account information of the User Identity account and the account server-side
Whether identical know the corresponding login account information of account；
When the business service end judge itself the corresponding login account information of the User Identity account and
When the corresponding login account information of the User Identity account of the account server-side is identical, the business service end is sentenced
It is disconnected to go out itself to conflict with the account server-side there is no account；
When the business service end judge itself the corresponding login account information of the User Identity account and
When the corresponding login account information difference of the User Identity account of the account server-side, the business service end is sentenced
It is disconnected go out itself there are accounts to conflict with the account server-side.
Optionally, when the corresponding login account information of the User Identity account is judged not in the business service end
When migrating into the account server-side, this method further include: the business service end is by the User Identity account pair
The login account information transfer answered is into the account server-side and marks the state of the User Identity account to have moved
It moves.
Optionally, the business service end judges whether the corresponding login account information of the User Identity account moves
It moves in the account server-side and includes:
Retrieve the labeled state of the User Identity account in the business service end；
When the labeled state for the User Identity account that the business service end retrieves is to have moved,
Judge the corresponding login account information transfer of the User Identity account to the account service in the business service end
In end；
When the labeled state that the business service end does not retrieve the User Identity account is to have moved,
Judge that the corresponding login account information of the User Identity account does not migrate to the account and take in the business service end
It is engaged in end.
Optionally, when the business service end judges that the corresponding login account information of the User Identity account is moved
When moving in the account server-side, this method further include: the business service end notifies account described in the client request
Server.
Optionally, when the corresponding login account of the User Identity account of itself is judged at the business service end
When information is identical with the corresponding login account information of the User Identity account of the account server-side, this method is also wrapped
Include: the business service end marks the state of the User Identity account to have moved and notifying the client request institute
State keeps.
Optionally, when the business service end, which does not retrieve, itself the User Identity account, this method is also
It include: to notify keeps described in the client request.
Optionally, when checking the User Identity account in another business service associated with the business service end
When having other User Identity accounts in end, this method further include: the account server-side backs up the user's body of itself
Part corresponding login account information of mark account login account corresponding with the other User Identity accounts checked
Information；
The corresponding login account information of the User Identity account of itself is sent to institute by the business service end
Account server-side is stated to notify the account server-side to complete the corresponding login account information of the User Identity account
Binding；It is to have moved and notify the client request that the business service end, which marks the state of the User Identity account,
The keeps；
The other User Identity accounts checked are sent to the account server-side by the business service end
The other User Identity accounts and its corresponding login account checked with notifying the account server-side to create
The record of information.
Present invention also provides a kind of business service ends, comprising: first judgment module, check module, the first transceiver module,
Mark processing module and the first notification module；Wherein,
First judgment module, the User Identity account for being sent according to the client received judge belonging to itself
Whether there are accounts to conflict with the account server-side that is pre-created at business service end；When judging the business service belonging to itself
When end conflicts with account server-side there are account, notice checks module；
Check module, for receiving the notice from first judgment module, check the User Identity account with
Whether the business service end has other User Identity accounts in associated another business service end；When checking the user
Identity account does not have other User Identity accounts in another business service end associated with the business service end
When, notify the first transceiver module；
First transceiver module, for receiving the notice for checking module, by the user at the business service end belonging to itself
The corresponding login account information of identity account is sent to account server-side to notify account server-side to complete the user identity
Identify the binding of the corresponding login account information of account；
Processing module is marked, is to have moved with the state for remembering the User Identity account is marked in；
First notification module, for notifying client request keeps.
Optionally, the first judgment module, is specifically used for:
Retrieve whether the business service end belonging to itself has the User Identity account；
When retrieving the business service end belonging to itself has the User Identity account, the user identity is judged
Whether the corresponding login account information of mark account migrates into the account server-side；
When end judges that the corresponding login account information of the User Identity account does not migrate to the account service
Whether when in end, requesting the account server-side to be retrieved itself has the User Identity account；When the account server-side
It does not retrieve when itself having the User Identity account, judges the business service end and the account server-side belonging to itself
There is no account conflicts；
When the account server-side, which retrieves, itself the User Identity account, the business belonging to itself is judged
The user identity of the User Identity the account corresponding login account information and the account server-side of server-side
Whether identical identify the corresponding login account information of account；
When judging itself the corresponding login account information of the User Identity account and the account server-side
The corresponding login account information of the User Identity account it is identical when, judge the business service end and institute belonging to itself
Stating account server-side, there is no account conflicts；
When the corresponding login account information of the User Identity account for judging the business service end belonging to itself
It is described to judge itself when different with the corresponding login account information of the User Identity account of the account server-side
There are accounts to conflict with the account server-side.
Optionally, which further includes transferring module；
The first judgment module is also used to work as and judges the corresponding login account information of the User Identity account
When not migrating into the account server-side, the transferring module is notified；Correspondingly,
The transferring module is used for the corresponding login account information transfer of the User Identity account to the account
In number server-side and to mark the state of the User Identity account be to have moved.
Optionally, whether the first judgment module judges the corresponding login account information of the User Identity account
It migrates and includes: into the account server-side
Retrieve the labeled state of the User Identity account；
When the labeled state of the User Identity account retrieved is to have moved, the user is judged
The corresponding login account information transfer of identity account is into the account server-side；
When the labeled state for not retrieving the User Identity account is to have moved, the user is judged
The corresponding login account information of identity account does not migrate into the account server-side.
Optionally, the first judgment module is also used to judge that the User Identity account is corresponding when end to step on
When land account information is migrated into the account server-side, first notification module is notified；
First notification module, is also used to receive the notice from the first judgment module, notifies the client
Request the keeps in end.
Optionally, the first judgment module is also used to judge the user at the business service end belonging to itself
The User Identity account of the corresponding login account information of identity account and the account server-side is corresponding to step on
When land account information is identical, the label processing module is notified；
The label processing module, is also used to receive the notice from the first judgment module, marks the user
The state of identity account is to have moved；Correspondingly,
First notification module is also used to notify keeps described in the client request.
Optionally, the first judgment module, being also used to not retrieve the business service end belonging to itself has the use
When the identity account of family, first notification module is notified；
First notification module, is also used to receive the notice from the first judgment module, notifies the client
Request the keeps in end.
Optionally, the inspection module, be also used to when check the User Identity account with the business service end
When there are other User Identity accounts in associated another business service end, first transceiver module is notified；Correspondingly,
First transceiver module is also used to receive the notice for checking module, by the business service end belonging to itself
The corresponding login account information of the User Identity account is sent to the account server-side to notify the account service
Complete the binding of the corresponding login account information of the User Identity account in end；Correspondingly,
The label processing module, being also used to mark the state of the User Identity account is to have moved；
First notification module is also used to notify client request keeps.
Present invention also provides a kind of account server-sides, comprising: the second transceiver module, the second judgment module, the second notice
Module, binding module；Wherein,
Second transceiver module, for receiving the account conflict request of business service end transmission；Receive the use at business service end
The corresponding login account information of family identity account；
Second judgment module, for judging account server-side and industry belonging to itself according to the account conflict request received
Server-side of being engaged in whether there is account conflict；When judging the account server-side belonging to itself, there are accounts to conflict with business service end
When, notify the second notification module；
Second notification module, for receiving the notice from the second judgment module, there are accounts at notice business service end
Conflict；
Binding module, the corresponding login account information of the User Identity account at the business service end for will receive
It is merged with the corresponding login account information of the User Identity account of account server-side belonging to itself.
Optionally, which further includes import modul, and being used for will be associated another with the business service end
The login account information at business service end imports in the account server-side.
Optionally, which further includes backup module, for when check the User Identity account with
When there are other User Identity accounts in the associated another business service end in the business service end, the account belonging to itself is backed up
The corresponding login account information of the User Identity account of number server-side and the other user identity marks checked
Know the corresponding login account information of account；Correspondingly,
The binding module, is also used to create other User Identity accounts for checking and its corresponding is stepped on
The record of land account information.
The embodiment of the present invention includes: the User Identity account judgement that business service end is sent according to the user received
Whether there are accounts to conflict with the account server-side that is pre-created for itself；When itself and account server-side are judged in business service end
There are when account conflict, check the User Identity account in another business service end associated with the business service end
Whether other User Identity accounts are had；When checking the User Identity account associated with the business service end
When not having other User Identity accounts in another business service end, business service end is by the User Identity account of itself
Number corresponding login account information is sent to account server-side to notify account server-side to complete the User Identity account pair
The binding for the login account information answered；It is to have moved and notify to use that business service end, which marks the state of the User Identity account,
Request keeps in family.The embodiment of the present invention solves the problems, such as the conflict of the account between different application and realizes data
Shared, the user experience is improved.
Detailed description of the invention
The drawings described herein are used to provide a further understanding of the present invention, constitutes part of this application, this hair
Bright illustrative embodiments and their description are used to explain the present invention, and are not constituted improper limitations of the present invention.In the accompanying drawings:
Fig. 1 is the flow chart of the method for present invention processing login account；
Fig. 2 is the flow chart of the embodiment of the method for present invention processing login account；
Fig. 3 is the structural schematic diagram at business service end of the present invention；
Fig. 4 is the structural schematic diagram of account server-side of the present invention.
Specific embodiment
Technical solution of the present invention is described in detail below in conjunction with accompanying drawings and embodiments.
The mobile terminal of each embodiment of the present invention is realized in description with reference to the drawings.In subsequent description, use
For indicate element such as " module ", " component " or " unit " suffix only for being conducive to explanation of the invention, itself
There is no specific meanings.Therefore, " module " can be used mixedly with " component ".
Fig. 1 is the flow chart of the method for present invention processing login account, as shown in Figure 1, comprising:
Step 101: business service end judges that itself is according to the User Identity account that the client received is sent
It is no that there are accounts to conflict with the account server-side being pre-created.
This step specifically includes:
Whether business service end is retrieved itself the User Identity account；
When business service end, which retrieves, itself the User Identity account, business service end judges user identity mark
Know whether the corresponding login account information of account migrates into account server-side；
When business service end judges that the corresponding login account information of User Identity account does not migrate to account service
When in end, business service end request account server-side retrieves whether itself has User Identity account；When account server-side not
It retrieves when itself having the User Identity account, itself is judged in business service end, and there is no account punchings with account server-side
It is prominent；
When account server-side, which retrieves, itself User Identity account, business service end judges the user's body of itself
The corresponding login account information of User Identity account of part mark account corresponding login account information and account server-side
It is whether identical；
When the corresponding login account information of User Identity account and account service of itself are judged in business service end
When the corresponding login account information of the User Identity account at end is identical, itself and account server-side are judged in business service end
There is no account conflicts；
When the corresponding login account information of User Identity account and account service of itself are judged in business service end
When the corresponding login account information difference of the User Identity account at end, itself and account server-side are judged in business service end
There are account conflicts.Wherein, request account server-side in business service end retrieves itself whether have the User Identity account packet
Include: User Identity account is sent to account server-side by business service end；Account server-side retrieves whether itself has user
Identity account.
Optionally, when business service end judges that the corresponding login account information of User Identity account does not migrate to account
When in number server-side, this method further include: business service end is by the corresponding login account information transfer of User Identity account
Into account server-side and the state of User Identity account is marked to have moved.
Wherein, business service end judges whether the corresponding login account information of User Identity account migrates to account clothes
Business end in include:
The labeled state of business service end retrieval User Identity account；
When the labeled state for the User Identity account that business service end retrieves is to have moved, business service
Judge the corresponding login account information transfer of User Identity account into account server-side in end；
When the labeled state that business service end does not retrieve User Identity account is to have moved, business service
Judge that the corresponding login account information of User Identity account does not migrate into account server-side in end.
Optionally, when business service end judges the corresponding login account information transfer of User Identity account to account
When in server-side, this method further include: business service end notifies client request keeps.
Optionally, when the corresponding login account information of User Identity account and account of itself are judged in business service end
When the corresponding login account information of User Identity account of number server-side is identical, this method further include: business service end mark
The state of note User Identity account is to have moved and notify client request keeps.
Optionally, when business service end, which does not retrieve, itself User Identity account, this method further include: notice
Client request keeps.
Step 102: when business service end judges that itself conflicts with account server-side there are account, checking user's body
Whether part mark account has other User Identity accounts in another business service end associated with the business service end.
Wherein, herein associated refers to that the corresponding application in business service end application corresponding with another business service belongs to
Same company (or producer).
Optionally, before this method further include: creation account server-side simultaneously will another industry associated with business service end
The login account information for server-side of being engaged in imports in account server-side.
Step 103: being taken when checking the User Identity account in another business associated with the business service end
In business end when not having other User Identity accounts, by itself this, User Identity account is corresponding steps at business service end
Land account information is sent to account server-side, and to notify account server-side to complete this, User Identity account is corresponding logs in account
The binding of number information.
Wherein, login account information includes at least user name and User Identity account；
User Identity account includes: phone number, mailbox or third-party application account.Optionally, login account is believed
Breath can also include userspersonal information, such as gender, and/or hobby and/or date of birth and/or address.
Wherein, the binding that account server-side completes the corresponding login account information of the User Identity account includes: account
Number server-side is by the use of the User Identity account at the business service end received corresponding login account information and itself
Identity account corresponding login account information in family merges.Optionally, at business service end by the user's body of itself
The corresponding login account information of part mark account is sent to after account server-side, completes the user identity mark in account server-side
Before the binding for knowing the corresponding login account information of account, this method further include: account server-side prompt the user whether to need by
The User Identity account of the corresponding login account information of the User Identity account of account server-side and business service end
Number corresponding login account information merges；When detecting that user do not need the User Identity account of account server-side
The corresponding login account information of the User Identity account of corresponding login account information and business service end merges
When, the use of the User Identity account of account server-side nonjoinder itself corresponding login account information and business service end
The corresponding login account information of family identity account；When detecting that user needs the User Identity account of account server-side
The corresponding login account information of the User Identity account of number corresponding login account information and business service end is closed
And when, it is transferred to the step of account server-side completes the binding of the corresponding login account information of the User Identity account.
Optionally, when checking the User Identity account in another business service associated with the business service end
When having other User Identity accounts in end, this method further include: account server-side backs up the User Identity account of itself
Number corresponding login account information login account information corresponding with the other User Identity accounts checked；
The corresponding login account information of the User Identity account of itself is sent to account server-side by business service end
To notify account server-side to complete the binding of the corresponding login account information of User Identity account；Business service end label is used
The state of family identity account is to have moved and notify client request keeps；
The other User Identity accounts checked are sent to account server-side to notify account to take by business service end
The record of other User Identity accounts and its corresponding login account information that the creation of business end checks.
Step 104: it is to have moved and client is notified to ask that business service end, which marks the state of the User Identity account,
Seek keeps.
In embodiment of the present invention, by judging itself to conflict with account server-side there are account when business service end and
Checking the User Identity account does not have other users in another business service end associated with the business service end
When identity account, the corresponding login account information of the User Identity account of itself is sent to account by business service end
Number server-side is to notify account server-side to complete the binding and industry of the corresponding login account information of the User Identity account
It is to have moved and notify client request keeps that business server-side, which marks the state of the User Identity account, is solved
Between different application account conflict the problem of and realize data sharing, the user experience is improved.
Fig. 2 is the flow chart of the embodiment of the method for present invention processing login account, as shown in Figure 2, comprising:
Step 201: another business service end associated with business service end is simultaneously logged in account by creation keeps
Number information imports in account server-side.
It should be noted that belonging to conventional techniques well-known to those skilled in the art on how to create keeps
Means, details are not described herein, is not intended to limit the invention.
Step 202: business service end receives the request for the carrying User Identity account that client is sent.
Step 203: whether business service end is retrieved itself the User Identity account.When business service end retrieves
When itself having the User Identity account, it is transferred to step 204；Itself there is the user identity mark when business service end does not retrieve
When knowing account, it is transferred to step 211.
Step 204: business service end judges whether the corresponding login account information of User Identity account migrates to account
In number server-side.Judge that the corresponding login account information of User Identity account does not migrate to account when business service end to take
When being engaged in end, it is transferred to step 205；When the corresponding login account information transfer of User Identity account is judged at business service end
When into account server-side, it is transferred to step 211.
Wherein, login account information includes at least user name and User Identity account；
User Identity account includes: phone number, mailbox or third-party application account.Optionally, login account is believed
Breath can also include userspersonal information, such as gender, and/or hobby and/or date of birth and/or address.
Wherein, this step specifically includes:
The labeled state of business service end retrieval User Identity account；
When the labeled state for the User Identity account that business service end retrieves is to have moved, business service
Judge the corresponding login account information transfer of User Identity account into account server-side in end；
When the labeled state that business service end does not retrieve User Identity account is to have moved, business service
Judge that the corresponding login account information of User Identity account does not migrate into account server-side in end.
Step 205: business service end request account server-side retrieves whether itself has User Identity account.Work as account
Server-side retrieves when itself having User Identity account, is transferred to step 206；Itself there is this when account server-side does not retrieve
When User Identity account, it is transferred to step 212.
Step 206: business service end judges the corresponding login account information of User Identity account and account of itself
Whether the corresponding login account information of the User Identity account of server-side is identical.When the use of itself is judged at business service end
The corresponding login account of User Identity account of the corresponding login account information of family identity account and account server-side
When information is identical, it is transferred to step 207；When the corresponding login account of User Identity account of itself is judged at business service end
Information when corresponding login account information difference, is transferred to step 208 with the User Identity account of account server-side.
Wherein, when the corresponding login account information of User Identity account and account of itself are judged in business service end
When the corresponding login account information difference of the User Identity account of server-side, business service end judges that itself and account take
Being engaged in, there are account conflicts at end；When business service end judge itself the corresponding login account information of User Identity account and
When the corresponding login account information of the User Identity account of account server-side is identical, itself and account are judged in business service end
Account conflict is not present in number server-side.
Step 207: it is to have moved that business service end, which marks the state of the User Identity account,.It is transferred to step 211.
Step 208: checking the User Identity account at another business service end associated with the business service end
In whether have other User Identity accounts.When checking the User Identity account associated with the business service end
Another business service end in when there is no other User Identity accounts, be transferred to step 209；Otherwise, it is transferred to step 210.
Step 209: the corresponding login account information of the User Identity account of itself is sent to by business service end
Account server-side is to notify account server-side to complete the binding of the corresponding login account information of the User Identity account.
Step 210: the other User Identity accounts checked are sent to account server-side with logical by business service end
Know the record for the other User Identity accounts and its corresponding login account information that the creation of account server-side checks.
Step 211: business service end notifies client request account server-side.
Step 212: account server-side notice business service end returns to the corresponding login account of User Identity account
Information.It is transferred to step 207.
Fig. 3 is the structural schematic diagram at business service end of the present invention, as shown in Figure 3, comprising: first judgment module 30 checks
Module 31, the first transceiver module 32, label processing module 33 and the first notification module 34.Wherein,
First judgment module 30, the User Identity account for being sent according to the client received judge itself institute
Whether there are accounts to conflict with the account server-side that is pre-created at the business service end of category；When judging the business clothes belonging to itself
When business end conflicts with account server-side there are account, notice checks module 31.
Wherein, first judgment module 30 are specifically used for:
Retrieve whether the business service end belonging to itself has User Identity account；
When retrieving the business service end belonging to itself has User Identity account, User Identity account is judged
Whether corresponding login account information migrates into account server-side；
When judging that the corresponding login account information of User Identity account does not migrate into account server-side, request
Whether account server-side is retrieved itself the User Identity account；Itself there is user's body when account server-side does not retrieve
When part mark account, judge that the business service end and account server-side belonging to itself conflict there is no account；
When account server-side, which retrieves, itself User Identity account, the business service end belonging to itself is judged
The User Identity account of the corresponding login account information of User Identity account and account server-side is corresponding to log in account
Whether number information is identical；
When user's body of the User Identity account for judging itself corresponding login account information and account server-side
When the corresponding login account information of part mark account is identical, judge that the business service end and account server-side belonging to itself are not deposited
In account conflict；
When the corresponding login account information of User Identity account and account for judging the business service end belonging to itself
When the corresponding login account information difference of the User Identity account of number server-side, judge that itself and account server-side exist
Account conflict.
Wherein, first judgment module 30 judges whether the corresponding login account information of User Identity account migrates to account
Include: in number server-side
Retrieve the labeled state of User Identity account；
When the labeled state of the User Identity account retrieved is to have moved, User Identity is judged
The corresponding login account information transfer of account is into account server-side；
When the labeled state for not retrieving User Identity account is to have moved, User Identity is judged
The corresponding login account information of account does not migrate into account server-side.
Check that module 31 checks the User Identity account for receiving the notice from first judgment module 30
Whether there are other User Identity accounts in another business service end associated with the business service end；When checking this
User Identity account does not have other User Identity in another business service end associated with the business service end
When account, the first transceiver module 32 is notified.
First transceiver module 32, for receiving the notice for checking module 31, by the business service end belonging to itself should
The corresponding login account information of User Identity account is sent to account server-side to notify account server-side to complete the user
The binding of the corresponding login account information of identity account.
Wherein, login account information includes at least user name and User Identity account；
User Identity account includes: phone number, mailbox or third-party application account.Wherein, third-party application account
It number include wechat account or microblog account etc..
Optionally, login account information can also include userspersonal information, such as gender, and/or hobby, and/or birth
Date and/or address.
Optionally, the first transceiver module 32 is also used to receive the carrying User Identity account of client transmission
Request.
Wherein, first judgment module 30 judges that the User Identity account at the business service end belonging to itself is corresponding and steps on
The whether identical corresponding login account information of the User Identity account of land account information and account server-side includes: to notify
One transceiver module 32 sends account conflict request to account server-side；It whether there is account conflict according to what account server-side was sent
Notice judge the corresponding login account information of User Identity account and account service at the business service end belonging to itself
Whether the corresponding login account information of the User Identity account at end is identical；
Correspondingly,
First transceiver module 32, is also used to receive the notice of first judgment module 30, sends account to account server-side
Conflict request；Receive the notice with the presence or absence of account conflict that account server-side is sent.
Wherein, the corresponding login account letter of User Identity account at business service end is carried in account conflict request
Breath.
Processing module 33 is marked, is to have moved with the state for remembering the User Identity account is marked in.
First notification module 34, for notifying client request keeps.
Optionally, first judgment module 30 are also used to work as and judge the corresponding login account letter of User Identity account
When breath is migrated into account server-side, the first notification module 34 is notified；
First notification module 34 is also used to receive the notice from first judgment module 30, notifies client request account
Number server.
Optionally, which further includes transferring module 35；At this point,
First judgment module 30 is also used to work as and judges that the corresponding login account information of User Identity account does not migrate
When into account server-side, informing removal module 35；Correspondingly,
Transferring module 35 is used for the corresponding login account information transfer of User Identity account into account server-side
And marking the state of User Identity account is to have moved.
Optionally, first judgment module 30 are also used to judge the user identity mark at the business service end belonging to itself
Knowing the corresponding login account information of account, corresponding login account information is identical with the User Identity account of account server-side
When, notification indicia processing module 33；
Processing module 33 is marked, is also used to receive the notice from first judgment module 30, marks User Identity
The state of account is to have moved；Correspondingly,
First notification module 34 is also used to notify client request keeps.
Optionally, first judgment module 30, being also used to not retrieve the business service end belonging to itself has user identity
When identifying account, the first notification module 34 is notified；
First notification module 34 is also used to receive the notice from first judgment module 30, notifies client request account
Number server.
Optionally, check module 31, be also used to when check the User Identity account with the business service end phase
When there are other User Identity accounts in associated another business service end, the first transceiver module 32 is notified；Correspondingly,
First transceiver module 32 is also used to receive the notice for checking module 31, by the business service end belonging to itself
The corresponding login account information of User Identity account is sent to account server-side to notify account server-side to complete user's body
The binding of the corresponding login account information of part mark account；Correspondingly,
Processing module 33 is marked, being also used to mark the state of User Identity account is to have moved；
First notification module 34 is also used to notify client request keeps.
Fig. 4 is the structural schematic diagram of account server-side of the present invention, as shown in Figure 4, comprising: the second transceiver module 40, second
Judgment module 41, the second notification module 42, binding module 43.Wherein,
Second transceiver module 40, for receiving the account conflict request of business service end transmission；Receive business service end
The corresponding login account information of User Identity account.
Second judgment module 41, for judge according to the account conflict request received account server-side belonging to itself and
Business service end whether there is account conflict；When judging the account server-side belonging to itself, there are account punchings with business service end
When prominent, the second notification module 42 is notified.
Second notification module 42, for receiving the notice from the second judgment module 41, notice business service end exists
Account conflict.
Binding module 43, the corresponding login account letter of the User Identity account at the business service end for will receive
Cease with itself belonging to the corresponding login account information of the User Identity account of account server-side merge.
Optionally, which further includes import modul 44, and being used for will another industry associated with business service end
The login account information for server-side of being engaged in imports in account server-side.
Wherein, login account information includes at least user name and User Identity account；
User Identity account includes: phone number, mailbox or third-party application account.Wherein, third-party application account
It number include wechat account or microblog account etc..
Optionally, login account information can also include userspersonal information, such as gender, and/or hobby, and/or birth
Date and/or address.
Optionally, which further includes backup module 45, is existed for that ought check the User Identity account
When there are other User Identity accounts in another business service end associated with the business service end, back up belonging to itself
The corresponding login account information of the User Identity account of account server-side and the other User Identity accounts checked
Corresponding login account information；Correspondingly,
Binding module 43 is also used to create the other User Identity accounts and its corresponding login account checked
The record of information.
Optionally, which further includes recovery module 46, will be belonging to itself for prompting the user whether to need
The User Identity account of the corresponding login account information of the User Identity account of account server-side and business service end
Number corresponding login account information merges；When detecting that user do not need user's body of the account server-side belonging to itself
The corresponding login account information of part mark account and the corresponding login account letter of the User Identity account at business service end
Breath is when merging, the corresponding login account information of User Identity account of account server-side belonging to nonjoinder itself and
The corresponding login account information of the User Identity account at business service end；It will be belonging to itself when detecting that user needs
The User Identity account of the corresponding login account information of the User Identity account of account server-side and business service end
When number corresponding login account information merges, binding module 43 is notified；Correspondingly,
Binding module 43, is specifically used for, and receives from the notice for replying module, by the use at the business service end received
The User Identity account pair of the corresponding login account information of family identity account and the account server-side belonging to itself
The login account information answered merges.
It should be noted that, in this document, the terms "include", "comprise" or its any other variant are intended to non-row
His property includes, so that the process, method, article or the device that include a series of elements not only include those elements, and
And further include other elements that are not explicitly listed, or further include for this process, method, article or device institute it is intrinsic
Element.In the absence of more restrictions, the element limited by sentence "including a ...", it is not excluded that including being somebody's turn to do
There is also other identical elements in the process, method of element, article or device.
The serial number of the above embodiments of the invention is only for description, does not represent the advantages or disadvantages of the embodiments.
Those of ordinary skill in the art will appreciate that all or part of the steps in the above method can be instructed by program
Related hardware (such as processor) is completed, and described program can store in computer readable storage medium, as read-only memory,
Disk or CD etc..Optionally, one or more integrated circuits also can be used in all or part of the steps of above-described embodiment
It realizes.Correspondingly, each module/unit in above-described embodiment can take the form of hardware realization, such as pass through integrated circuit
It realizes its corresponding function, can also be realized in the form of software function module, such as be stored in and deposited by processor execution
Program/instruction in reservoir realizes its corresponding function.The present invention is not limited to the knots of the hardware and software of any particular form
It closes.
The above is only preferred embodiment of the present application, are not intended to limit the scope of the patents of the application, all to utilize this Shen
Please equivalent structure or equivalent flow shift made by specification and accompanying drawing content, be applied directly or indirectly in other relevant skills
Art field similarly includes in the scope of patent protection of the application.
Claims (20)
1. a kind of method for handling login account characterized by comprising
Business service end according to the User Identity account that the client that receives is sent judge itself whether be pre-created
Account server-side there are account conflicts；
When business service end judges that itself conflicts with account server-side there are account, check that the User Identity account exists
Whether there are other User Identity accounts in another business service end associated with the business service end；
There is no it when checking the User Identity account in another business service end associated with the business service end
When its User Identity account, the corresponding login account information of the User Identity account of itself is sent out at business service end
Account server-side is given to notify account server-side to complete the binding of the corresponding login account information of the User Identity account；
It is to have moved and notify client request keeps that business service end, which marks the state of the User Identity account,.
2. the method according to claim 1, wherein before this method further include: creation account server-side simultaneously will
The login account information at another business service end associated with the business service end imports in the account server-side.
3. method according to claim 1 or 2, which is characterized in that the login account information include at least user name and
User Identity account；
The User Identity account includes: phone number, mailbox or third-party application account.
4. method according to claim 1 or 2, which is characterized in that the business service end is according to the user's body received
Part mark account judges whether itself conflicts with the account server-side being pre-created there are account and includes:
Whether the business service end is retrieved itself the User Identity account；
When the business service end, which retrieves, itself the User Identity account, described in the business service end judgement
Whether the corresponding login account information of User Identity account migrates into the account server-side；
When the business service end judges that the corresponding login account information of the User Identity account does not migrate to described
When in account server-side, the business service end requests the account server-side to retrieve whether itself has the User Identity
Account；When the account server-side, which does not retrieve, itself the User Identity account, the business service end is judged
Itself conflicts with the account server-side there is no account；
When the account server-side, which retrieves, itself the User Identity account, the business service end judges itself
The corresponding login account information of the User Identity account and the account server-side the User Identity account
Whether number corresponding login account information is identical；
When the corresponding login account information of the User Identity account and described of itself is judged at the business service end
When the corresponding login account information of the User Identity account of account server-side is identical, the business service end is judged
Itself conflicts with the account server-side there is no account；
When the corresponding login account information of the User Identity account and described of itself is judged at the business service end
When the corresponding login account information difference of the User Identity account of account server-side, the business service end is judged
There are accounts to conflict with the account server-side for itself.
5. according to the method described in claim 4, it is characterized in that, when the user identity mark is judged at the business service end
When the corresponding login account information of knowledge account is not migrated into the account server-side, this method further include: the business service
The corresponding login account information transfer of the User Identity account into the account server-side and is marked the use by end
The state of family identity account is to have moved.
6. according to the method described in claim 4, it is characterized in that, the business service end judges the User Identity account
Whether number corresponding login account information migrates includes: into the account server-side
Retrieve the labeled state of the User Identity account in the business service end；
It is described when the labeled state for the User Identity account that the business service end retrieves is to have moved
Judge the corresponding login account information transfer of the User Identity account into the account server-side in business service end；
It is described when the labeled state that the business service end does not retrieve the User Identity account is to have moved
Judge that the corresponding login account information of the User Identity account does not migrate to the account server-side in business service end
In.
7. according to the method described in claim 6, it is characterized in that, when the user identity mark is judged at the business service end
When knowing the corresponding login account information transfer of account into the account server-side, this method further include: the business service end
Notify keeps described in the client request.
8. according to the method described in claim 4, it is characterized in that, when the user of itself is judged at the business service end
The User Identity account of the corresponding login account information of identity account and the account server-side is corresponding to step on
When land account information is identical, this method further include: the business service end marks the state of the User Identity account to be
It has moved and notifies keeps described in the client request.
9. according to the method described in claim 4, it is characterized in that, itself having the use when the business service end does not retrieve
When the identity account of family, this method further include: notify keeps described in the client request.
10. the method according to claim 1, wherein when check the User Identity account with the industry
When having other User Identity accounts in the business associated another business service end of server-side, this method further include: the account
Other use that number server-side backs up the corresponding login account information of the User Identity account of itself and checks
The corresponding login account information of family identity account；
The corresponding login account information of the User Identity account of itself is sent to the account by the business service end
Number server-side is to notify the account server-side to complete the binding of the corresponding login account information of the User Identity account；
It is to have moved and notify described in the client request that the business service end, which marks the state of the User Identity account,
Keeps；
The other User Identity accounts checked are sent to the account server-side with logical by the business service end
Know that the account server-side creates the other User Identity accounts and its corresponding login account information checked
Record.
11. a kind of business service end characterized by comprising first judgment module checks module, the first transceiver module, label
Processing module and the first notification module；Wherein,
First judgment module, the User Identity account for being sent according to the client received judge the industry belonging to itself
Whether there are accounts to conflict with the account server-side that is pre-created for business server-side；When judge the business service end belonging to itself with
For account server-side there are when account conflict, notice checks module；
Check module, for receiving the notice from first judgment module, check the User Identity account with the industry
Whether business has other User Identity accounts in the associated another business service end of server-side；When checking the user identity
When mark account does not have other User Identity accounts in another business service end associated with the business service end, lead to
Know the first transceiver module；
First transceiver module, for receiving the notice for checking module, by the user identity at the business service end belonging to itself
The corresponding login account information of mark account is sent to account server-side to notify account server-side to complete the User Identity
The binding of the corresponding login account information of account；
Processing module is marked, is to have moved with the state for remembering the User Identity account is marked in；
First notification module, for notifying client request keeps.
12. business service end according to claim 11, which is characterized in that the first judgment module is specifically used for:
Retrieve whether the business service end belonging to itself has the User Identity account；
When retrieving the business service end belonging to itself has the User Identity account, the User Identity is judged
Whether the corresponding login account information of account migrates into the account server-side；
When judging that the corresponding login account information of the User Identity account does not migrate into the account server-side,
Whether the account server-side is requested to be retrieved itself the User Identity account；When the account server-side does not retrieve
When itself having the User Identity account, judge that account is not present in the business service end and the account server-side belonging to itself
Number conflict；
When the account server-side, which retrieves, itself the User Identity account, the business service belonging to itself is judged
The User Identity of the User Identity the account corresponding login account information and the account server-side at end
Whether the corresponding login account information of account is identical；
When the institute for the User Identity the account corresponding login account information and the account server-side for judging itself
State the corresponding login account information of User Identity account it is identical when, judge business service end belonging to itself and the account
Account conflict is not present in number server-side；
When the corresponding login account information of the User Identity account and institute for judging the business service end belonging to itself
It is described to judge itself and institute when stating the corresponding login account information difference of the User Identity account of account server-side
Stating account server-side, there are account conflicts.
13. business service end according to claim 12, which is characterized in that the business service end further includes transferring module；
The first judgment module is also used to work as and judges that the corresponding login account information of the User Identity account is not moved
When moving in the account server-side, the transferring module is notified；Correspondingly,
The transferring module, for taking the corresponding login account information transfer of the User Identity account to the account
In business end and the state of the User Identity account is marked to have moved.
14. business service end according to claim 12, which is characterized in that the first judgment module judges the user
Whether the corresponding login account information of identity account migrates includes: into the account server-side
Retrieve the labeled state of the User Identity account；
When the labeled state of the User Identity account retrieved is to have moved, the user identity is judged
The corresponding login account information transfer of account is identified into the account server-side；
When the labeled state for not retrieving the User Identity account is to have moved, the user identity is judged
The corresponding login account information of mark account does not migrate into the account server-side.
15. business service end according to claim 13, which is characterized in that the first judgment module is also used to work as and sentence
It is disconnected go out the corresponding login account information transfer of the User Identity account into the account server-side when, notify described the
One notification module；
First notification module, is also used to receive the notice from the first judgment module, and the client is notified to ask
Seek the keeps.
16. business service end according to claim 12, which is characterized in that the first judgment module is also used to work as and sentence
It is disconnected go out itself belonging to business service end the corresponding login account information of the User Identity account and account clothes
When the corresponding login account information of the User Identity account at business end is identical, the label processing module is notified；
The label processing module, is also used to receive the notice from the first judgment module, marks the user identity
The state of mark account is to have moved；Correspondingly,
First notification module is also used to notify keeps described in the client request.
17. business service end according to claim 12, which is characterized in that the first judgment module, being also used to ought be not
When retrieving the business service end belonging to itself has the User Identity account, first notification module is notified；
First notification module, is also used to receive the notice from the first judgment module, and the client is notified to ask
Seek the keeps.
18. business service end according to claim 11, which is characterized in that the inspection module is also used to check
The User Identity account has other User Identity in another business service end associated with the business service end
When account, first transceiver module is notified；Correspondingly,
First transceiver module is also used to receive the notice for checking module, will be described in the business service end belonging to itself
The corresponding login account information of User Identity account is sent to the account server-side to notify the account server-side complete
At the binding of the corresponding login account information of the User Identity account；Correspondingly,
The label processing module, being also used to mark the state of the User Identity account is to have moved；
First notification module is also used to notify client request keeps.
19. a kind of account server-side characterized by comprising the second transceiver module, the second judgment module, the second notification module,
Binding module and import modul；Wherein,
Second transceiver module, for receiving the account conflict request of business service end transmission；Receive user's body at business service end
The corresponding login account information of part mark account；
Second judgment module, for judge account server-side and business clothes belonging to itself according to the account conflict request received
End be engaged in the presence or absence of account conflict；When judging that the account server-side belonging to itself conflicts with business service end there are account,
Notify the second notification module；
Second notification module, for receiving the notice from the second judgment module, there are account conflicts at notice business service end；
Binding module, the corresponding login account information of the User Identity account at the business service end for will receive and from
The corresponding login account information of the User Identity account of account server-side belonging to body merges；
Import modul, for the login account information at another business service end associated with the business service end to be imported institute
It states in account server-side.
20. account server-side according to claim 19, which is characterized in that the account server-side further includes backup module,
For when check the User Identity account have in another business service end associated with the business service end it is other
When User Identity account, the User Identity account for backing up the account server-side belonging to itself corresponding logs in account
Number information login account information corresponding with the other User Identity accounts checked；Correspondingly,
The binding module, is also used to create other User Identity accounts for checking and its corresponding logs in account
The record of number information.
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 |
|---|---|---|
| US9743251B2 (en) | Adding location names using private frequent location data | |
| US11860900B2 (en) | Log-based distributed transaction management | |
| US9282153B2 (en) | Content suggestion for posting on communication network | |
| CN110494857B (en) | Predictive local pre-caching for reducing latency in digital content access rights determination | |
| CN1848849B (en) | Method and device for replicating modifications of a directory | |
| US9973394B2 (en) | Eventual consistency among many clusters including entities in a master member regime | |
| US10803013B2 (en) | Efficient similarity detection | |
| US20110044512A1 (en) | Automatic Image Tagging | |
| US9641406B1 (en) | Updating virtual machine images | |
| JP2007502464A5 (en) | ||
| CN107832099A (en) | A kind of client release compatible method, apparatus and storage medium | |
| US20140214984A1 (en) | Method and system for sending e-mail attached with large file on mobile device | |
| CN107943572A (en) | Data migration method, device, computer equipment and storage medium | |
| CN107633016A (en) | Data processing method and device and electronic equipment | |
| CN108509275A (en) | A kind of catalogue moving method and metadata load-balancing method | |
| CN105656946B (en) | A kind of method, business service end and account server-side handling login account | |
| US9781053B1 (en) | Request routing and processing using a cancellation token | |
| WO2015008450A1 (en) | Directory service discovery and/or learning | |
| CN105308590A (en) | Centralized management of link data for multiple applications, computers and resources, through operating systems and networked storage services | |
| US20210150528A1 (en) | Processing messages for attribute-value pair extraction | |
| US10594839B2 (en) | Virtual assistant skill deployment | |
| CN114331057A (en) | Storage and management system of electronic book | |
| CN106528830A (en) | Method and device for recovering file index catalogue | |
| US9053109B1 (en) | Systems and methods for efficient data storage for content management systems | |
| US20130246347A1 (en) | Database file groups |
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 |