CN110225035B - Third party account binding and logging method, server, terminal and device - Google Patents
Third party account binding and logging method, server, terminal and device Download PDFInfo
- Publication number
- CN110225035B CN110225035B CN201910502798.2A CN201910502798A CN110225035B CN 110225035 B CN110225035 B CN 110225035B CN 201910502798 A CN201910502798 A CN 201910502798A CN 110225035 B CN110225035 B CN 110225035B
- Authority
- CN
- China
- Prior art keywords
- user
- account
- virtual card
- server
- party account
- 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
Images
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
Abstract
The application discloses a third party account binding method, a third party account login method, a server, a mobile terminal and a device with a storage function. The method comprises the following steps: the server receives a third party account which is sent by the mobile terminal and authorized by the user and used for logging in a virtual card client operated by the mobile terminal, wherein the third party account comprises a first user unique identifier; and binding the first user unique identification and a second user unique identification corresponding to the virtual card account of the user so as to form a binding mapping relation between the third party account and the virtual card account. By means of the method, the virtual card client can be logged in by a plurality of third party accounts and can also uniquely correspond to the same virtual card account, and management of user accounts and improvement of user experience are facilitated.
Description
Technical Field
The present application relates to the field of internet, and in particular, to a third party account binding method, a third party account login method, a server, a mobile terminal, and a computer-readable storage medium.
Background
With the development of network technology, various websites and APPs come out endlessly, and the user may be lost due to the cumbersome registration or login procedure. In order to simplify the registration and login process of the user and improve the user experience, the provision of third-party account joint login has become the choice of multiple websites and APPs.
The third party account login means that third party platform authorization is obtained, public information such as a nickname, a head portrait, a sex, a location and the like of a user of the third party account is quickly obtained, and the information is used for logging in an authorized website or APP, so that the third party account is quickly logged in. The third party account generally comprises platform accounts such as WeChat, QQ, paibao, microblog and the like.
The same user often has a plurality of third party accounts, and if the user uses different third party accounts to log in the same platform, the same user has a plurality of accounts on the same platform, and the data of the accounts are not intercommunicated, which brings inconvenience to the user.
Disclosure of Invention
The application mainly solves the technical problem of providing a third party account binding method, a third party account login method, a server and a mobile terminal, which can realize that a plurality of third party account login virtual card clients correspond to the same virtual card account.
In order to solve the technical problem, the application adopts a technical scheme that: an account binding method is provided, and the method comprises the following steps: the server receives user authorization sent by the mobile terminal and is used for logging in a third party account of a virtual card client operated by the mobile terminal, wherein the third party account carries the unique identifier of the first user; and binding the first user unique identification and a second user unique identification corresponding to the virtual card account of the user so as to form a binding mapping relation between the third party account and the virtual card account.
In order to solve the above technical problem, another technical solution adopted by the present application is: an account binding method is provided, and the method comprises the following steps: the method comprises the steps that a mobile terminal obtains a third party account authorized by a user and used for logging in a virtual card client operated by the mobile terminal, wherein the third party account carries a first user unique identification; and sending the third party account to a server so that the server binds the first user unique identifier and a second user unique identifier corresponding to the virtual card account of the user to form a binding mapping relation between the third party account and the virtual card account.
In order to solve the above technical problem, another technical solution adopted by the present application is: a third party account login method is provided, and the method comprises the following steps: the mobile terminal receives an instruction that a user authorizes to use a third party account to log in; sending a request for logging in by using a third party account to a server, wherein the third party account comprises a first user unique identifier so as to enable the server to search a virtual card account bound with the third party account, and the binding mapping relationship between the third party account and the virtual card account is established by binding the first user unique identifier and a second user unique identifier corresponding to the virtual card account; and receiving personal data of the user and data of the virtual card account bound by the third party account, which are called by the server from the third party account platform, and completing third party account login.
In order to solve the above technical problem, another technical solution adopted by the present application is: there is provided a server comprising a processor, a memory, and a communication circuit, wherein the processor is coupled to the memory and the communication circuit and is operable to execute instructions to implement the third party account binding method in cooperation with the memory and the communication circuit.
In order to solve the above technical problem, another technical solution adopted by the present application is: the mobile terminal comprises a processor, a memory and a communication circuit, wherein the processor is coupled with the memory and the communication circuit and executes instructions in work to realize the third party account binding and logging method by matching the memory and the communication circuit.
In order to solve the above technical problem, another technical solution adopted by the present application is: there is provided a computer readable storage medium storing a program which, when executed, implements the third party account binding and logging method described above.
The beneficial effect of this application is: different from the situation of the prior art, according to the scheme provided by the application, when the user logs in the virtual card client side by using the third party account, the unique user identifier of the third party account and the unique user identifier of the virtual card account are bound, so that the third party account and the virtual card account form a binding mapping relation, even if multiple third party accounts are used for logging in, the third party accounts can uniquely correspond to the same virtual card account, data intercommunication under logging in of different third party accounts is realized, and the user experience is improved. Meanwhile, inconvenience brought to the user by the fact that the same user has multiple accounts on the virtual card platform is avoided, user experience is improved, and maintenance and management of the virtual card platform to the user are facilitated.
Drawings
FIG. 1 is a schematic diagram illustrating an embodiment of a third party account binding system according to the present application;
FIG. 2 is a schematic view of an interaction flow of the third party account binding method implemented by the third party account binding system according to the present application;
FIG. 3 is a flowchart illustrating a first embodiment of a third party account binding method according to the present application;
FIG. 4 is a flowchart illustrating a third party account binding method according to a second embodiment of the present application;
FIG. 5 is a flowchart illustrating a third embodiment of a third party account binding method according to the present application;
FIG. 6 is a flowchart illustrating an embodiment of a third party account login method according to the present application;
FIG. 7 is a schematic structural diagram of an embodiment of a mobile terminal according to the present application;
FIG. 8 is a schematic structural diagram of an embodiment of a server according to the present application;
FIG. 9 is a schematic structural diagram of an embodiment of a computer-readable storage medium according to the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art without any inventive work based on the embodiments in the present application are within the scope of protection of the present application.
Reference herein to "embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiments can be included in at least some embodiments of the present application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
Furthermore, it should be noted that the terms "first", "second" and "third" in the embodiments of the present application are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of the feature. Furthermore, the terms "including" and "having" and any variations thereof in the embodiments of the present application are intended to cover non-exclusive inclusions.
Referring to fig. 1, fig. 1 is a schematic structural diagram of an embodiment of a third party account binding system according to the present application. In this embodiment, the system 10 includes a server 11, a mobile terminal 12, and a third party account platform 13. The server may be a remote server, the mobile terminal may be equipped with a virtual card client, and the mobile terminal may be a mobile phone, a tablet computer, a wearable device, and the like.
Referring to fig. 1 and fig. 2 together, fig. 2 is an interaction flow diagram illustrating a third-party account binding method implemented based on a third-party account binding system according to the present application. Specifically, after receiving an instruction that a user authorizes to log in a virtual card client running on the mobile terminal 12 by using a third party account, the mobile terminal 12 sends a request for authorizing the third party account to log in the virtual card client to the third party account platform 13. The third party account platform 13 processes the request and returns the related data of the third party account, wherein the third party account includes the unique identifier of the first user. The mobile terminal 12 receives a third party account returned by the third party account platform 13, and sends related data of the third party account to the server 11, and the server 11 binds the first user unique identifier and the second user unique identifier corresponding to the user virtual card account, so that the third party account and the virtual card account form a binding mapping relationship.
The following detailed description of the implementation of the present invention is made with reference to specific embodiments:
referring to fig. 3, fig. 3 is a flowchart illustrating a third party account binding method according to a first embodiment of the present application. The embodiment takes a server as an execution main body and comprises the following steps:
s101: and the server receives user authorization sent by the mobile terminal and is used for logging in a third party account of the virtual card client operated by the mobile terminal, wherein the third party account contains the unique identifier of the first user.
The third-party account can be a WeChat account, a QQ account, a Paibao account, a microblog account and the like, and can also be other third-party accounts, and the user can select one of the accounts to log in the virtual card client according to the self condition, and can also log in the virtual card client by using a plurality of the third-party accounts. For example, a user logs in by using a WeChat account at a certain time, forgets which third-party account is selected for logging in at the last time when logging in next time, and reselects a Payment account for logging in.
The virtual card client operated by the mobile terminal can be a virtual card APP, and can also be an applet embedded in a third party APP, such as a WeChat applet and a Paibao applet.
In this embodiment, the oauth2.0 protocol (open authorization protocol) is used for the third party authorized login. Specifically, a user clicks a third-party account login button on a virtual card client login interface operated by the mobile terminal, the interface jumps to a corresponding third-party account login interface or pulls up a third-party application, the user inputs an account number password of a third-party account on the third-party account login interface, in other embodiments, a confirmation authorization button displayed on a page can be clicked, after the user confirms the authorization login, the interface is redirected to the virtual card client and carries a temporary authorization code (code), and the mobile terminal exchanges an interface calling certificate (access _ token) and a first user unique identifier (openid/userid/uid/unionid) for the third-party account platform through the code, the application unique identifier, the application key and the like. And the server executes S102 after receiving the unique user identifier of the third-party account of the user sent by the mobile terminal.
In other embodiments, the server may store sensitive data such as the application key, and the mobile terminal sends the code to the server after obtaining the code returned by the third-party account platform, and the server exchanges data such as the access _ token and the user unique identifier for the third-party account platform. The third-party account data of the user is acquired from the third-party account platform through the server, so that the leakage risk of the user data can be reduced, and the safety of the user data is improved.
S102: and the server binds the first user unique identification and a second user unique identification corresponding to the virtual card account of the user so as to enable the third party account and the virtual card account to form a binding mapping relation.
A user has a virtual card account on the virtual card platform, the virtual card account has a corresponding second user unique identifier, and the first user unique identifier and the second user unique identifier are bound, so that a binding mapping relation between a third party account and the virtual card account can be formed, and data intercommunication between the third party account and the virtual card account is realized. For example, after logging in the virtual card client through the third party account for consumption, the transaction data is accumulated in the virtual card account.
Through the method, the unique user identification of the third party account of the user and the unique identification of the virtual card account are bound, even if the user logs in the virtual card client by using a plurality of third party accounts, the unique identification can be uniquely corresponding to the virtual card account of the user, data communication between the plurality of third party accounts and the virtual card account is realized, inconvenience caused by the fact that a plurality of accounts exist in the virtual card platform of the same user due to the fact that the plurality of third party accounts log in the virtual card client is reduced, user experience is improved, and maintenance and management of the virtual card platform on the user are facilitated.
Referring to fig. 4 specifically, fig. 4 is a schematic flowchart of a second embodiment of the third-party account binding method according to the present application, where the second embodiment is based on the first embodiment of the third-party account binding method, and the same steps in this embodiment as in the first embodiment may refer to the contents of the first embodiment, which is not described herein again. The embodiment takes a server as an execution main body and comprises the following steps:
s201: and the server receives user authorization sent by the mobile terminal and is used for logging in a third party account of the virtual card client operated by the mobile terminal, wherein the third party account contains the unique identifier of the first user.
S202: the server inquires whether the first user unique identification has a bound second user unique identification.
Third party authorized logins typically have a certain expiration date beyond which the user is required to re-authorize the login. Therefore, the third party account may be a virtual card account that authorizes the user to log in the virtual card client for the first time, or may be a virtual card account that is already bound before the nth time for logging in the virtual card client, where the nth time is used for logging in the virtual card client. After receiving the first user unique identifier, the server firstly inquires whether the first user unique identifier is a second user unique identifier which is bound with the virtual card account in advance, so that repeated binding operation is avoided.
S203: and if the first user unique identifier is not bound with any second user unique identifier, the server acquires the user information of the user.
The first user unique identifier is not bound with any second user unique identifier, which shows that the third party account is used for logging in the virtual card client for the first time, and user information needs to be acquired to associate the virtual card account with the third party account. The acquired user information can be one or more of a mobile phone number, an identification card number, a bank card number, an electronic mailbox, a biological characteristic, a mobile terminal identification and the like of the user, and can also be an account number and a password of a virtual card account of the user. The server sends a request for acquiring the user information to the mobile terminal, and the mobile terminal collects the required user information.
In some embodiments, the mobile terminal may present an interface for inputting user information to a user, and obtain information for querying a virtual card account of the same user by inputting the information on the interface by the user, for example, an interface for inputting a mobile phone number and a short message verification code is presented, and the server receives the mobile phone number and the verification code input by the user, determines that the mobile phone number is the user information if the verification code is correct. It is of course possible to guide the user to collect biometric information of the user, such as a fingerprint, a face, a voice, etc.
In other embodiments, the user may authorize the user to call the user information from the third party account, and obtain the mobile phone number, the identification card number, the bank card number, and the like bound to the third party account. Taking the virtual card wechat applet as an example to obtain the mobile phone number bound by the user wechat, after the server obtains the openid and the session key of the third party account, the virtual card wechat applet of the mobile terminal shows the virtual card applet to the user to apply for obtaining a mobile phone number interface bound by the wechat, the user clicks an allowed button, the wechat server sends encrypted data containing the mobile phone number to the virtual card server, and the virtual card server decrypts the data to obtain the mobile phone number of the user.
In still other embodiments, it may also be the user authorization to read user information from the mobile terminal, such as reading the terminal identifier of the mobile terminal, the user's mobile phone number stored by the mobile terminal, and so on. For example, the user has previously logged in the virtual card account in the same mobile terminal, and the server stores the terminal identifier of the mobile terminal, where the terminal identifier may be, for example, an IMEI, a MAC address, and the like, and is a unique identifier of the mobile terminal, so that the third party account and the virtual card account may be associated according to the terminal identifier.
The information obtained from different third party accounts may be different user information or the same user information, and is not limited herein.
S204: the server judges whether a virtual card account matched with the user information exists or not.
And searching the virtual card account matched and bound with the same user information in the virtual card user database according to the acquired user information.
In other embodiments, the user feature vector may also be established according to the obtained user information, and the virtual card account closest to the user feature vector in the user database may be matched.
If the virtual card account matched with the user information exists, executing S205; if the virtual card account matching the user information does not exist, S206 is executed.
S205: and the server acquires the unique identifier of the second user corresponding to the virtual card account.
When the user registers the virtual card account, the server configures a user unique identifier of the virtual card account for each user, namely a second user unique identifier, and stores the user unique identifier in the user information table of the user in the database. And after the matched virtual card account is inquired according to the user information, the second user unique identifier under the user virtual card account is extracted, and S207 is executed.
S206: and the server creates a virtual card account of the user and generates a second user unique identifier corresponding to the virtual card account.
If the virtual card account matched with the user information does not exist, which indicates that the user does not register the virtual card account in the virtual card platform in advance, a virtual card account is created for the user according to the acquired user information, and a corresponding second user unique identifier is generated, and then S207 is executed.
S207: and the server binds the first user unique identification and a second user unique identification corresponding to the virtual card account of the user so as to enable the third party account and the virtual card account to form a binding mapping relation.
By the method, the server firstly inquires whether the virtual card account bound in advance exists or not after obtaining the user unique identifier of the third party account, and repeated binding operation can be avoided. When no virtual card is bound, user information is obtained, the virtual card account of the same user is inquired according to the user information, so that the user unique identification of the virtual card account is obtained and is bound with the user unique identification of the third party account, even if the user logs in the virtual card client by using a plurality of third party accounts, the user can uniquely correspond to the virtual card account of the user, the data communication between the login of the plurality of third party accounts and the virtual card account is realized, the inconvenience caused by the fact that the plurality of third party accounts log in the virtual card client and the existence of the plurality of accounts in the virtual card platform of the same user is reduced, the user experience is improved, and the maintenance and the management of the virtual card platform on the user are facilitated.
Referring to fig. 5, fig. 5 is a flowchart illustrating a third embodiment of a third-party account binding method according to the present application. The embodiment takes a mobile terminal as an execution main body, and comprises the following steps:
s301: the mobile terminal obtains a third party account authorized by the user and used for logging in a virtual card client operated by the mobile terminal, wherein the third party account contains the unique identifier of the first user.
S302: the mobile terminal sends the third party account to the server.
S303: and the mobile terminal receives a request for acquiring the user information of the user, which is sent by the server.
Specifically, the user information includes one or more of a mobile phone number, an identification number, a bank card number, an e-mail box, a biometric feature, and a mobile terminal identifier of the user.
S304: the mobile terminal responds to the request and acquires the user information of the user.
S305: the mobile terminal transmits the user information to the server.
The mobile terminal sends the user information to the server, so that the server binds the first user unique identification and the second user unique identification corresponding to the virtual card account after inquiring the virtual card account matched with the user information.
The embodiment describes a method flow of the mobile terminal in the third party account binding method, and please refer to the description of the embodiment specifically, which is not described herein again.
Referring to fig. 6, fig. 6 is a flowchart illustrating a third party account login method according to an embodiment of the present application. The embodiment takes a mobile terminal as an execution main body, and comprises the following steps:
s401: and the mobile terminal receives an instruction that the user authorizes to log in by using the third party account.
S402: the mobile terminal sends a request for logging in by using the third party account to the server so that the server searches the virtual card account bound with the third party account.
The third party account comprises a first user unique identifier and an access _ token, and the binding mapping relationship between the third party account and the virtual card account is established by binding the first user unique identifier and a second user unique identifier corresponding to the virtual card account.
S403: and the mobile terminal receives the user personal data of the third party account and the data of the virtual card account bound by the third party account, which are sent by the server, and completes the login of the third party account.
In this embodiment, the first user unique identifier and the access _ token of the third-party account are obtained by the mobile terminal from the third-party account platform, and are sent to the server, and the server binds the second user unique identifier and calls the user personal data from the third-party account platform. In other embodiments, after receiving the code, the mobile terminal may send the code to the server, and the server uses the code to exchange the first user unique identifier and the access _ token of the third party account for the third party account platform.
After the third party account is bound with the virtual card account, the server combines the user personal data of the third party account and the virtual card data of the virtual card account and sends the user personal data and the virtual card data to the mobile terminal, and the mobile terminal receives the combined user personal data of the third party account and the virtual card data of the virtual card account to complete login. After logging in, transaction data performed by logging in the virtual card client based on the third party account is updated to the virtual card data. Even if the user uses different third party accounts to log in the virtual card client, due to the binding mechanism, the transaction data generated by the different third party accounts correspond to the same virtual card account of the user, and account management is facilitated.
The present application further provides a mobile terminal for implementing the third party account binding method and the third party account login method, specifically please refer to fig. 7, where fig. 7 is a schematic structural diagram of an embodiment of the mobile terminal according to the present application. In this embodiment, the mobile terminal includes a processor 701, a memory 702, and a communication circuit 703, where the processor 701 is coupled to the memory 702 and the communication circuit 703, and executes an instruction when operating to implement the third-party account binding method and the third-party account login method in cooperation with the memory 702 and the communication circuit 703, and a specific working process is consistent with the above method embodiments, so that details are not repeated herein, and please refer to the description of the corresponding method steps. The mobile terminal can be a mobile phone, a tablet computer, a wearable device and the like.
The present application further provides a server for implementing the third party account binding method and the third party account login method, specifically please refer to fig. 8, where fig. 8 is a schematic structural diagram of an embodiment of the server according to the present application. In this embodiment, the server includes a processor 801, a memory 802, and a communication circuit 803, where the processor 801 is coupled to the memory 802 and the communication circuit 803, and executes an instruction when operating to implement the third-party account binding method and the third-party account login method in cooperation with the memory 802 and the communication circuit 803, and a specific operating process is consistent with the above method embodiments, so that details are not repeated herein, and please refer to the description of the corresponding method steps above in detail.
The present application further provides a computer-readable storage medium for implementing the third party account binding method and the third party account login method, specifically please refer to fig. 9, where fig. 9 is a schematic structural diagram of a first embodiment of the computer-readable storage medium according to the present application. In this embodiment, the computer-readable storage medium 100 stores a program 1001, and the program 1001 realizes the third party account binding method and the third party account login method when executed. The specific working process is the same as that in the above method embodiment, and therefore, the details are not repeated herein, and please refer to the description of the corresponding method steps. The storage device may be a portable storage medium such as a usb disk, an optical disk, a portable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or other various media that can store program codes, and may also be a terminal, a server, or other media.
The above description is only for the purpose of illustrating embodiments of the present application and is 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 are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.
Claims (10)
1. A third party account binding method is characterized in that the third party account binding method comprises the following steps:
the method comprises the steps that a server receives user authorization sent by a mobile terminal and is used for logging in a third party account of a virtual card client operated by the mobile terminal, wherein the third party account comprises a first user unique identifier;
the server binds the first user unique identification and a second user unique identification corresponding to the virtual card account of the user, so that the third party account and the virtual card account form a binding mapping relation;
before the step of binding the first user unique identifier and a second user unique identifier corresponding to the virtual card account by the server, the method comprises the following steps:
the server judges whether the first user unique identification has the bound second user unique identification;
if the first user unique identification is not bound with any second user unique identification, the server acquires the user information of the user;
the server inquires whether the virtual card account matched with the user information exists or not;
if a virtual card account matched with the user information exists, the server acquires the second user unique identifier corresponding to the virtual card account;
the server acquires the user information of the user, and the method comprises the following steps:
the server reads the terminal identification of the mobile terminal of the user.
2. The third party account binding method of claim 1, further comprising:
and if the virtual card account matched with the user information does not exist, the server creates the virtual card account of the user and generates the second user unique identification corresponding to the virtual card account.
3. The third party account binding method according to claim 1, wherein the step of the server obtaining the user information of the user comprises:
the server sends a request for acquiring the user information to the mobile terminal so that the user can call/authorize from a third party account through the virtual card client to read the user information from the mobile terminal;
and the server receives the user information fed back by the mobile terminal.
4. The third party account binding method according to any one of claims 1 to 3, wherein the third party account is one or more of a WeChat account, a QQ account, a Payment treament account and a microblog account.
5. A third party account binding method is characterized in that the third party account binding method comprises the following steps:
the method comprises the steps that a mobile terminal obtains a third party account authorized by a user and used for logging in a virtual card client operated by the mobile terminal, wherein the third party account comprises a first user unique identifier;
the mobile terminal sends the third party account to a server so that the server binds the first user unique identification and a second user unique identification corresponding to the virtual card account of the user to form a binding mapping relation between the third party account and the virtual card account;
wherein, after sending the third party account to the server, the method further comprises:
the mobile terminal receives a request for acquiring the user information of the user, which is sent by the server;
the mobile terminal responds to the request and acquires the user information of the user;
the mobile terminal sends the user information to the server, so that the server binds the first user unique identifier and a second user unique identifier corresponding to the virtual card account after inquiring the virtual card account matched with the user information;
the obtaining of the user information of the user includes:
the terminal identification of the user's mobile terminal is read.
6. The third party account binding method according to claim 5, wherein the obtaining the user information of the user comprises:
and the mobile terminal displays a preset interface to the user through the virtual card client so that the user inputs the user information/authorizes to call the user information/authorizes to read the locally stored user information of the third party account.
7. A third party account login method is characterized by comprising the following steps:
the mobile terminal receives an instruction that a user authorizes to use a third party account to log in;
the mobile terminal sends a login request using the third party account and the third party account to a server so that the server searches a virtual card account bound with the third party account, wherein the third party account comprises a first user unique identifier and an interface calling certificate, and a binding mapping relation between the third party account and the virtual card account is established by binding the first user unique identifier and a second user unique identifier corresponding to the virtual card account;
the mobile terminal receives user personal data of the third party account sent by a server and data of the virtual card account bound by the third party account, and completes third party account login, wherein the user personal data is called from a third party account platform by using an interface calling certificate;
after the mobile terminal sends the request for logging in by using the third party account and the third party account to the server, the method further comprises the following steps:
the mobile terminal receives a request for acquiring the user information of the user, which is sent by the server;
the mobile terminal responds to the request and acquires the user information of the user;
the mobile terminal sends the user information to the server, so that the server binds the first user unique identifier and a second user unique identifier corresponding to the virtual card account after inquiring the virtual card account matched with the user information;
the acquiring the user information of the user includes:
the terminal identification of the user's mobile terminal is read.
8. A server, comprising a processor, a memory, and a communication circuit, wherein the processor is coupled to the memory and the communication circuit and, when operating, executes instructions to implement the third party account binding method of any of claims 1 to 4 in cooperation with the memory and the communication circuit.
9. A mobile terminal, comprising a processor, a memory, and a communication circuit, wherein the processor is coupled to the memory and the communication circuit, and when operating, executes instructions to implement the third party account binding method or the third party account login method of any one of claims 5 to 7 in cooperation with the memory and the communication circuit.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores program data which, when executed by a processor, implements the third party account binding method or third party account login method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910502798.2A CN110225035B (en) | 2019-06-11 | 2019-06-11 | Third party account binding and logging method, server, terminal and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910502798.2A CN110225035B (en) | 2019-06-11 | 2019-06-11 | Third party account binding and logging method, server, terminal and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110225035A CN110225035A (en) | 2019-09-10 |
| CN110225035B true CN110225035B (en) | 2022-11-11 |
Family
ID=67816573
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910502798.2A Active CN110225035B (en) | 2019-06-11 | 2019-06-11 | Third party account binding and logging method, server, terminal and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110225035B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110535884B (en) * | 2019-09-26 | 2021-10-22 | 招商局金融科技有限公司 | Method, device and storage medium for cross-enterprise inter-system access control |
| CN112738143B (en) * | 2019-10-14 | 2022-05-10 | 华为技术有限公司 | Account number binding method, device and system |
| CN112069488B (en) * | 2020-07-27 | 2023-05-16 | 合肥美的智能科技有限公司 | Application login method in communication program and related device thereof |
| CN112184249B (en) * | 2020-11-27 | 2021-04-27 | 深圳市深圳通有限公司 | User signing method, device, equipment and storage medium |
| CN114866268B (en) * | 2021-02-04 | 2023-03-17 | 腾讯科技（深圳）有限公司 | Method and device for realizing account intercommunication and electronic equipment |
| CN113572826B (en) * | 2021-07-12 | 2023-09-26 | 绿盟科技集团股份有限公司 | Device information binding method and system and electronic device |
| CN113746857B (en) * | 2021-09-09 | 2023-04-18 | 深圳市腾讯网域计算机网络有限公司 | Login method, device, equipment and computer readable storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103327043A (en) * | 2012-03-21 | 2013-09-25 | 腾讯科技（深圳）有限公司 | Method and system and relation chain platform server for pushing messages |
| CN103986720A (en) * | 2014-05-26 | 2014-08-13 | 网之易信息技术（北京）有限公司 | Log-in method and device |
| CN104753943A (en) * | 2015-03-30 | 2015-07-01 | 努比亚技术有限公司 | Method and device for log-in control of third-party account |
| CN105871838A (en) * | 2016-03-30 | 2016-08-17 | 努比亚技术有限公司 | Third party account login control method and user center platform |
| CN106295271A (en) * | 2015-06-29 | 2017-01-04 | 阿里巴巴集团控股有限公司 | Account automatic logging method, device and related system |
| CN109635212A (en) * | 2018-12-11 | 2019-04-16 | 杭州启博科技有限公司 | The method by user-association to APP based on wechat |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016127407A1 (en) * | 2015-02-13 | 2016-08-18 | 华为技术有限公司 | Account information management method and apparatus |
| CN105306733B (en) * | 2015-11-13 | 2018-11-09 | 深圳正品创想科技有限公司 | Third party login based on cell phone application binds cell-phone number method |
| US10931637B2 (en) * | 2017-09-15 | 2021-02-23 | Palo Alto Networks, Inc. | Outbound/inbound lateral traffic punting based on process risk |
-
2019
- 2019-06-11 CN CN201910502798.2A patent/CN110225035B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103327043A (en) * | 2012-03-21 | 2013-09-25 | 腾讯科技（深圳）有限公司 | Method and system and relation chain platform server for pushing messages |
| CN103986720A (en) * | 2014-05-26 | 2014-08-13 | 网之易信息技术（北京）有限公司 | Log-in method and device |
| CN104753943A (en) * | 2015-03-30 | 2015-07-01 | 努比亚技术有限公司 | Method and device for log-in control of third-party account |
| CN106295271A (en) * | 2015-06-29 | 2017-01-04 | 阿里巴巴集团控股有限公司 | Account automatic logging method, device and related system |
| CN105871838A (en) * | 2016-03-30 | 2016-08-17 | 努比亚技术有限公司 | Third party account login control method and user center platform |
| CN109635212A (en) * | 2018-12-11 | 2019-04-16 | 杭州启博科技有限公司 | The method by user-association to APP based on wechat |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110225035A (en) | 2019-09-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110225035B (en) | Third party account binding and logging method, server, terminal and device | |
| CN109600306B (en) | Method, device and storage medium for creating session | |
| US8572701B2 (en) | Authenticating via mobile device | |
| TW201424324A (en) | Method and apparatus of account login | |
| JP2001319186A (en) | Authentication method and authentication device | |
| KR20120107434A (en) | Method for providing card payment system using phnone number and system thereof | |
| JP2007264835A (en) | Authentication method and system | |
| TW201525894A (en) | Method, mobile terminal, server and system of payment account management | |
| WO2019033840A1 (en) | Password authentication method for shared device, shared device, cloud server, and system | |
| CN108650098B (en) | Method and device for user-defined verification mode | |
| CN109831441B (en) | Identity authentication method, system and related components | |
| CN114268462B (en) | Asset information changing method, server, client, and storage medium | |
| CN111405036A (en) | Service access method, device, related equipment and computer readable storage medium | |
| CN109379388B (en) | Identity recognition method, terminal and wearable device | |
| US10149160B2 (en) | Recognizing and authenticating mobile devices based on unique cross-channel bindings | |
| JP2009245273A (en) | Individual identification system and method | |
| KR20090051966A (en) | Website login processing method and apparatus | |
| KR100946410B1 (en) | Method and system for approval of another party mobile payment | |
| JP2015170334A (en) | Authentication information management system, authentication information management device and program | |
| JP5536511B2 (en) | Authentication device, authentication system, authentication program, and authentication method for personal authentication using a mobile phone | |
| CN113709740A (en) | Method and system for displaying account information on authorized login page | |
| CN111400684B (en) | Electronic license information acquisition method, system, device, equipment and storage medium | |
| JP5582663B2 (en) | Method for generating identifier, method for blocking cryptographic device, program, block system, and computer system | |
| JP6325654B2 (en) | Network service providing apparatus, network service providing method, and program | |
| JP4276022B2 (en) | User authentication method, user authentication system, computer program, and program storage medium in WWW service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |