WO2017152820A1 - 登录客户端的方法，装置及存储介质 - Google Patents

登录客户端的方法，装置及存储介质 Download PDF

Info

Publication number
WO2017152820A1
WO2017152820A1 PCT/CN2017/075757 CN2017075757W WO2017152820A1 WO 2017152820 A1 WO2017152820 A1 WO 2017152820A1 CN 2017075757 W CN2017075757 W CN 2017075757W WO 2017152820 A1 WO2017152820 A1 WO 2017152820A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
login
request
account
verification
Prior art date
Application number
PCT/CN2017/075757
Other languages
English (en)
French (fr)
Inventor
郭冲
俞尚
许弈
苟晓东
林国洪
谭秋航
李宏伟
林声炜
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Publication of WO2017152820A1 publication Critical patent/WO2017152820A1/zh
Priority to US15/955,488 priority Critical patent/US10776478B2/en
Priority to US16/938,503 priority patent/US11372963B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/41—User authentication where a single sign-on provides access to a plurality of computers
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/33—User authentication using certificates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/36—User authentication by graphic or iconic representation
    • 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

Definitions

  • the present invention relates to the field of computers, and in particular to a method, device and storage medium for logging in to a client.
  • the embodiment of the invention provides a method and a device for logging in to a client, so as to at least solve the technical problem that the login efficiency is low due to the existing login method.
  • a method for logging in to a client including: obtaining, at a login interface of a first client running on the terminal, a login account currently logged in by a second client running on the terminal, where The second client has an association relationship with the first client, and performs an operation on the acquired login account on the login interface of the first client, and obtains a login request generated after performing the operation on the login account, where The login request is used to request to log in to the first client by using the login account; and to log in to the first client by using the login account in response to the login request.
  • a method for logging in to a client including: receiving a login verification request of a terminal running a first client to a login account, where the login account is a And the second client has a relationship with the first client; and the second client responds to the login verification request to verify whether the first client uses the login account to perform login; when the verification succeeds, the foregoing The second client sends a response to successful login verification, so that the first client performs login using the login account.
  • an apparatus for logging in to a client including: a first acquiring unit, configured to acquire, at a login interface of a first client running by the terminal, a second client running on the terminal a login account currently logged in, wherein the second client has an association relationship with the first client, and the second obtaining unit is configured to acquire, after the operation on the login account, the operation of the login client on the login interface of the first client
  • the login request wherein the operation performed on the login account is performed on the login interface of the first client, the login request is used to request to log in to the first client by using the login account, and the login unit is configured to respond to the login request. Use the above login account to log in to the above first client.
  • an apparatus for logging in to a client including: a first receiving unit, configured to receive a login verification request for a login account by a terminal running the first client, where the login account is The second client has an association relationship with the first client, and the verification unit is configured to verify whether the first client uses the above-mentioned first client in response to the login verification request.
  • the login account performs a login;
  • the sending unit is configured to send, by the second client, a response that the login verification succeeds when the verification succeeds, so that the first client performs the login by using the login account.
  • a nonvolatile storage medium Computer readable instructions are stored therein. When the instructions are executed, the computer is caused to perform the method of logging in to the client as described above.
  • the login account that is currently logged in by the second client running on the terminal is obtained by using the login interface of the first client running on the terminal, where the second client has an association relationship with the first client; And obtaining the login request generated after the operation of the login account is performed on the login interface of the first client, where the login request is used to request to log in to the first client by using the login account; and further, the login client is used to log in to the first client in response to the login request. . That is, the first client obtains the login account currently logged in by the second client from the second client having the association relationship, and implements the fast login by using the obtained login account, thereby simplifying the login operation of the login client. Reduce the number of unnecessary interactions, save the login time of the login client, and achieve the effect of improving login efficiency. In order to overcome the prior art, the problem of low login efficiency caused by complicated operations such as multiple interactions is required.
  • FIG. 1 is a schematic diagram of a method for logging in to a client according to the prior art
  • FIG. 2 is a schematic diagram of another method for logging in to a client according to the prior art
  • FIG. 3 is a schematic diagram of an application environment of an optional method for logging in to a client according to an embodiment of the present invention
  • FIG. 4 is a flowchart of an optional method for logging in to a client according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of an optional method for logging in to a client according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of an application environment of another optional method for logging in to a client according to an embodiment of the present invention.
  • FIG. 7 is a flow chart of another optional method of logging in to a client in accordance with an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of another optional method for logging in to a client according to an embodiment of the present invention.
  • FIG. 9 is a flow chart of still another alternative method of logging in to a client, in accordance with an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of an optional device for logging in to a client according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of another optional device for logging in to a client according to an embodiment of the present invention.
  • FIG. 12 is a schematic diagram of an optional login client terminal according to an embodiment of the present invention.
  • FIG. 13 is a schematic diagram of an optional login client server according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a terminal of a login client according to an embodiment of the present invention.
  • an embodiment of a method for logging in to a client is provided.
  • the method for logging in to the client may be, but is not limited to, being applied to the login interface of the first client running in the terminal 302 in the application environment as shown in FIG.
  • the login account that is currently logged in by the second client running in the terminal 302 is obtained, wherein the second client has an association relationship with the first client, and then the obtained login is obtained on the login interface of the first client.
  • the account execution operation acquires a login request generated after the operation is performed on the login account, where the login request is used to request to log in to the first client by using the login account, and log in to the first client by using the login account in response to the login request, thereby implementing Send the login request
  • the server 306 is sent to the first client, and after the terminal 302 displays the login to the first client, the resource information is returned from the server 306 corresponding to the first client through the network 304, where the server corresponding to the first client is the first The server on which the client provides the service.
  • the login account that is currently logged in to the second client associated with the first client is obtained on the first client login interface, and the login account is directly used to log in, thereby simplifying the login operation of the login client, thereby saving login time and realizing the login time. Improve the efficiency of login efficiency.
  • the foregoing terminal may include, but is not limited to, at least one of the following: a mobile phone, a tablet computer, a notebook computer, and a desktop computer.
  • the foregoing network may include, but is not limited to, at least one of the following: a wide area network, a metropolitan area network, and a local area network. The above is only an example, and the embodiment does not limit this.
  • a method for logging in to a client includes:
  • S404 Perform an operation on the obtained login account on the login interface of the first client, and obtain a login request generated after performing an operation on the login account, where the login request is used to request to log in to the first client by using the login account;
  • the foregoing method for logging in to the client may be, but is not limited to being applied to, a client having an association relationship (for example, an instant messaging application client, and a community space sharing application client corresponding to the instant messaging application client). End) during the login process. That is, when logging in to the first client, using the association relationship between the first client and the second client, obtaining the login account currently running the second client on the terminal (for example, the account number 125253 shown in FIG. 5) Further, using the login account to implement fast login to the first client, as shown in FIG. 5(a)-5(c), thereby displaying the server corresponding to the first client after logging in to the first client. Returned resource information.
  • the above example is only an embodiment, and is not limited in this embodiment.
  • the login account currently logged in by the second client running in the terminal is obtained by using the login interface of the first client running on the terminal, where the second client is The first client has an association relationship, and obtains a login request generated after performing an operation on the login account on the login interface of the first client, where the login request is used to request to log in to the first client by using the login account; Log in to the first client using the login account.
  • the first client obtains the login account currently logged in by the second client from the second client having the association relationship, and implements the fast login by using the obtained login account, thereby simplifying the login operation of the login client and reducing unnecessary
  • the number of interactions can save the login time of the login client, thereby improving the login efficiency.
  • the problem of low login efficiency caused by complicated operations such as multiple interactions is required.
  • the obtaining, by the first client, the login request generated after performing the operation on the login account includes: the first client acquiring the selected instruction generated by performing the selected operation on the login account, A login verification request is sent to the second client in response to the selected instruction. Then, the server corresponding to the second client verifies whether the first client is allowed to perform login using the login account, and when the verification succeeds, the second client sends a response of successful login verification to make the first client
  • the terminal may perform a quick login by using the login account, where the server corresponding to the second client is a server that provides services for the second client.
  • the first client running by the terminal 302 acquires the login account currently logged in by the second client having the association relationship at the time of login, and generates a selection instruction by performing a selection operation on the login account.
  • the terminal 302 sends a login verification request to the server 602 corresponding to the second client, so that the server 602 uses the pre-registered information to verify whether the first client on the terminal 302 can perform the quick login using the login account.
  • the first client After receiving the response of the login verification succeeded by the server 602 by the second client, acquires a login request for requesting to log in to the first client by using the login account, and sends the login request to the first client.
  • the corresponding server 306 is configured to obtain resource information to be displayed after login.
  • the server corresponding to the second client may be, but is not limited to, verifying the login signature.
  • the registration request is sent to the server corresponding to the second client, where the registration request is used to request the login of the first client at the server.
  • Signature eg Sign A
  • the login verification request corresponding to the first client (such as Sign B) is carried in the login verification request sent to the server where the second client is located, and the second guest
  • the server corresponding to the client performs verification on the pre-registered login signature Sign A and the Sign B obtained from the first client requesting verification, thereby realizing whether the first client can use the account currently logged in by the second client.
  • Quick verification of fast login which saves the login time of the first client and improves the login efficiency.
  • acquiring the login account currently logged in by the second client running on the terminal may be, but is not limited to, performing the first client in the terminal.
  • the communication with the second client is such that the first client directly obtains the login account currently logged in by the second client, and displays the login account on the login interface of the first client.
  • the login account currently registered by the second client is displayed on the login interface of the first client.
  • sending the login verification request to the second client may include, but is not limited to: creating a transparent interface of the second client on the login interface of the first client, and second to the transparent interface.
  • the client sends a login verification request.
  • the first login signature corresponding to the first client for login verification is carried in the login verification request.
  • the first client 702 obtains the currently logged in login account from the second client 706, and performs an operation (such as a selected operation) on the login account, and the response is
  • the operation command generated by the operation sends a login verification request to the server 708 where the second client is located through the second client 706, and verifies in the second client corresponding server 708 whether the first client is allowed to perform login using the login account. If the verification succeeds, the server 708 where the second client is located sends a response to the first client to the first client by using the second client (if the response carries the login ticket), and the first client 702 obtains the response according to the response.
  • the login request for the login is sent to the server 704 where the first client is located, and after the login to the first client 702 is displayed, the returned resource information is obtained from the server 704 corresponding to the first client.
  • the login account currently logged in by the second client running in the terminal is obtained by using the login interface of the first client running on the terminal, where the second client has an association relationship with the first client. And obtaining a login request generated after performing an operation on the login account on the login interface of the first client, wherein the login request is used to request to log in to the first client by using the login account; and further, logging in to the first client by using the login account in response to the login request end.
  • the first client obtains the login account currently logged in by the second client from the second client having the association relationship, and implements the fast login by using the obtained login account, thereby simplifying the login operation of the login client and reducing unnecessary Pay
  • the number of mutual times can save the login time of the login client, thereby improving the login efficiency.
  • the problem of low login efficiency caused by complicated operations such as multiple interactions is required.
  • performing the operation on the obtained login account on the login interface of the first client, and obtaining the login request generated after performing the operation on the login account of the second client includes:
  • the foregoing first login signature may be, but is not limited to, a signature for uniquely identifying the first client.
  • the first login signature of the first client that is currently logged in is sent, and the first login signature is used to perform comparison verification with the pre-registered second login signature, thereby ensuring efficient and rapid verification of the first client fast login process. .
  • a selection instruction for a login account currently displayed by the second client displayed on the login interface of the first client is received, and a login verification request is sent in response to the selected instruction.
  • the waiting screen of "Login" is displayed on the terminal.
  • the login verification process of the first client may be implemented by, but not limited to, execution code as shown in FIG. 8.
  • the security of the first client to log in using the login account is ensured by verifying the obtained current login account of the second client.
  • the method before acquiring the login account currently logged in by the second client running in the terminal, the method further includes:
  • the association relationship between the first client and the second client may be a preset association relationship, for example, an instant messaging application client, and corresponding to the instant messaging application client.
  • the community space shares the application client.
  • the association relationship between the first client and the second client may also be established by registering the login signature. That is to say, before the first client logs in, the login signature of the first client is pre-registered in the server where the second client is located, so as to establish an association relationship between the first client and the second client.
  • the second login signature of the first client is registered by the server where the second client is located, so as to implement the first login signature obtained by using the second login signature and the first client that is requested to log in. Verification, so as to quickly verify whether the first client can use the above login account to perform fast effects.
  • the method further includes:
  • the server receives the first login signature by using the second client.
  • the server verifies whether the received first login signature is consistent with the registered second login signature.
  • the server sends a response of the login verification success by the second client.
  • the second client Before the first client (APP-1) acquires the login account (ID) currently registered by the second client (APP-2) running in the terminal, the second client (APP-2)
  • the server (S2) where the server is located (S2) sends a registration request to register the login signature of the first client (APP-1) (such as Sign A).
  • the login verification request sent to the server (S2) where the second client (APP-2) is located will carry the first The login signature (such as Sign B) corresponding to the client, and the server (S2) corresponding to the second client (APP-2) obtains the login signature (such as Sign A) registered in advance and the first client authenticated from the request.
  • the signature (such as Sign B) is verified, such as verifying that the received first login signature (such as Sign A) is consistent with the registered second login signature (such as Sign B), and verifying the first login signature (such as Sign A)
  • the second login signature (such as Sign B) is registered, the response of the login verification success is sent through the second client.
  • the embodiment of the present application provides a quick verification of whether the first client can use the account currently logged in by the second client by using the verification of the login signature, thereby saving the login time of the first client and improving the login time of the first client.
  • the effect of login efficiency is a quick verification of whether the first client can use the account currently logged in by the second client by using the verification of the login signature, thereby saving the login time of the first client and improving the login time of the first client.
  • sending a login verification request to the second client in response to the selected instruction includes:
  • the first client after receiving the selected instruction for “login using the second client login account 125253” as shown in FIG. 5, the first client creates a transparent interface of the second client on the login interface. For example, by calling the transparent interface of the second client through android startActivity(), after receiving the startActivity() request, the second client obtains the first login signature of the first client by using android Activity.getCallingActivity(), and goes to the second The server where the client is located sends a login verification request carrying the first login signature.
  • the transparent interface of the second client is created on the login interface of the first client, so as to reduce the number of interactions between the login process and the user, so that the user does not send the login verification interface by using the second client. Perceive to achieve an improved user experience.
  • obtaining the login account currently logged in by the second client running on the terminal includes:
  • the login interface of the first client is displayed on the terminal in response to the running request.
  • the operation request for running the first client is received, and after confirming that the terminal has installed the first client and the second client having an association relationship with the first client,
  • the login interface of the first client is displayed, and the login account currently logged in by the second client is obtained from the second client by using the android binder communication mechanism.
  • the login account is displayed on the login interface of the first client. For example, as shown in FIG. 5( a ), “using the second client to log in to the account 125253 Login button.
  • the login account currently logged in by the second client is obtained, so that the first client uses the login account to achieve fast login.
  • the effect is to save the login time of the login client, thereby achieving the effect of improving login efficiency.
  • the problem of low login efficiency caused by complicated operations such as multiple interactions is required.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • a method for logging in to a client includes:
  • S902 Receive a login verification request for the login account by the terminal running the first client, where the login account is a login account currently logged in by the second client running in the terminal, and the second client has an association relationship with the first client.
  • S906 When the verification is successful, send a response to successful login verification by the second client, so that the first client performs login by using the login account.
  • the foregoing method for logging in to the client may be, but is not limited to being applied to, a client having an association relationship (for example, an instant messaging application client, and a community space sharing application client corresponding to the instant messaging application client). End) during the login process. That is, in the process of the first client using the login account for the quick login, the second client having the association relationship with the first client performs a quick verification on the login verification request of the login account, and verifies whether the first client is Log in to the login account to ensure that the first client can log in quickly, simplify the login operation of the login client, reduce the number of unnecessary interactions, and save the login time of the login client, thus improving the login efficiency.
  • a client having an association relationship for example, an instant messaging application client, and a community space sharing application client corresponding to the instant messaging application client.
  • the login verification request may be sent to the second client after the first client obtains the selected instruction for the login account.
  • the first client running by the terminal 302 acquires the login account currently logged in by the second client having the association relationship at the time of login, and generates a selection instruction by performing a selection operation on the login account.
  • the terminal 302 will send a login verification request to the server 602 where the second client is located, so that the server 602 uses the pre-registered information to verify whether the first client on the terminal 302 can perform the quick login using the login account.
  • the first client After receiving the response of the login verification succeeded by the server 602 by the second client, acquires a login request for requesting to log in to the first client by using the login account, and sends the login request to the first client.
  • the corresponding server 306 is configured to obtain resource information to be displayed after login.
  • the server corresponding to the second client may be, but is not limited to, verifying the login signature.
  • the registration request is sent to the server corresponding to the second client, where the registration request is used to request the login of the first client at the server.
  • Signature eg Sign A
  • the login verification request corresponding to the first client (such as Sign B) is carried in the login verification request sent to the server where the second client is located, and the second client
  • the corresponding server performs verification by using the pre-registered login signature Sign A and the Sign B obtained from the first client requesting verification, so as to enable the first client to quickly log in using the account currently logged in by the second client.
  • Quick verification which in turn saves the login time of the first client Improve the efficiency of login.
  • the first client 702 obtains the currently logged in login account from the second client 706, and performs an operation (such as a selected operation) on the login account, and the response is
  • the operation command generated by the operation sends a login verification request to the second client server 708 through the second client 706, and verifies in the server 708 where the second client is located whether the first client is allowed to perform login using the login account. If the verification succeeds, the server 708 where the second client is located sends a response to the first client to the first client by using the second client (if the response carries the login ticket), and the first client 702 obtains the response according to the response.
  • the login request for the login is sent to the server 704 where the first client is located, and after the login to the first client 702 is displayed, the returned resource information is obtained from the server 704 corresponding to the first client.
  • the obtained current login account of the second client is verified, thereby ensuring fast verification of the login by the first client using the login account, so as to simplify the login operation of the login client, and reduce the login operation.
  • the number of necessary interactions can save the login time of the login client, thereby improving the login efficiency. Further, it is also possible to ensure the security of the first client to log in using the above login account.
  • the login verification request includes at least a first login signature corresponding to the first client, where the receiving, before receiving the login verification request for the login account by the terminal running the first client, the method further includes:
  • the association relationship between the first client and the second client may be a preset association relationship, for example, an instant messaging application client, and corresponding to the instant messaging application client.
  • the community space shares the application client.
  • the association relationship between the first client and the second client may also be established by registering the login signature. That is to say, before the first client logs in, the login signature of the first client is pre-registered in the server where the second client is located, so as to establish an association relationship between the first client and the second client.
  • the second login signature of the first client is registered by the server where the second client is located, so as to implement the first login signature obtained by using the second login signature and the first client that is requested to log in. Verification, so as to quickly verify whether the first client can use the above login account to perform fast effects.
  • Verifying whether the first client performs login using the login account in response to the login verification request includes: S11, verifying whether the first login signature is consistent with the registered second login signature;
  • the response that the login verification succeeds by the second client includes: S21.
  • the second client sends a response of the login verification success, where The response carries a login ticket that causes the first client to perform login.
  • the second client Before the first client (APP-1) acquires the login account (ID) currently registered by the second client (APP-2) running in the terminal, the second client (APP-2)
  • the server (S2) where the server is located (S2) sends a registration request to register the login signature of the first client (APP-1) (such as Sign A).
  • the login verification request sent to the server (S2) where the second client (APP-2) is located will carry the first
  • the login signature corresponding to the client (such as Sign B), and the server (S2) where the second client (APP-2) is located is obtained by registering the pre-registered login signature (such as Sign A) with the first client from the request verification.
  • the login signature (such as Sign B) is verified, such as verifying that the received first login signature (such as Sign A) is consistent with the registered second login signature (such as Sign B), verifying the first login signature (such as Sign A)
  • the second client sends a response that the login verification succeeds.
  • the embodiment of the present application provides a quick verification of whether the first client can use the account currently logged in by the second client by using the verification of the login signature, thereby saving the login time of the first client and improving the login time of the first client.
  • the effect of login efficiency is a quick verification of whether the first client can use the account currently logged in by the second client by using the verification of the login signature, thereby saving the login time of the first client and improving the login time of the first client.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • the device includes:
  • the first obtaining unit 1002 is configured to acquire, on the login interface of the first client running by the terminal, a login account currently logged in by the second client running in the terminal, where the second client is associated with the first client relationship;
  • the second obtaining unit 1004 is configured to obtain, on the login interface of the first client, a login request generated after performing an operation on the login account, where the operation performed on the login account is on the login interface of the first client The login request is used to request to log in to the first client by using the login account;
  • the login unit 1006 is configured to log in to the first client by using the login account in response to the login request.
  • the foregoing device for logging in to the client may be, but is not limited to being applied to, a client having an association relationship (such as an instant messaging application client, and a community space sharing application client corresponding to the instant messaging application client). End) during the login process. That is, when logging in to the first client, using the association relationship between the first client and the second client, obtaining the login account currently running the second client on the terminal (for example, the account number 125253 shown in FIG. 5) Further, using the login account to implement fast login to the first client, as shown in FIG. 5(a)-5(c), thereby displaying the server corresponding to the first client after logging in to the first client. Returned resource information.
  • the above example is only an embodiment, and is not limited in this embodiment.
  • the login interface of the first client running through the terminal is required. And obtaining a login account currently logged in by the second client running in the terminal, where the second client has an association relationship with the first client, and acquiring, after the operation of the login account is performed on the login interface of the first client.
  • the login request is used to request to log in to the first client by using the login account; and then log in to the first client by using the login account in response to the login request.
  • the first client obtains the login account currently logged in by the second client from the second client having the association relationship, and implements the fast login by using the obtained login account, thereby simplifying the login operation of the login client and reducing unnecessary
  • the number of interactions can save the login time of the login client, thereby improving the login efficiency.
  • the problem of low login efficiency caused by complicated operations such as multiple interactions is required.
  • the obtaining, by the first client, the login request generated after performing the operation on the login account includes: the first client acquiring the selected instruction generated by performing the selected operation on the login account, A login verification request is sent to the second client in response to the selected instruction. Then, the server corresponding to the second client verifies whether the first client is allowed to perform login using the login account, and when the verification succeeds, the second client sends a response of successful login verification to make the first client
  • the terminal can perform quick login using the above login account.
  • the first client running by the terminal 302 acquires the login account currently logged in by the second client having the association relationship at the time of login, and generates a selection instruction by performing a selection operation on the login account.
  • the terminal 302 will send a login verification request to the second client corresponding server 602 to enable the server 602 to verify whether the first client on the terminal 302 can perform the quick login using the login account using the pre-registered information.
  • the first client After receiving the response of the login verification succeeded by the server 602 by the second client, the first client acquires a login request for requesting to log in to the first client by using the login account, and sends the login request to the first client.
  • the corresponding server 306 is configured to obtain resource information to be displayed after login.
  • the server corresponding to the second client may be, but is not limited to, verifying the login signature.
  • the registration request is sent to the server corresponding to the second client, where the registration request is used to request the login of the first client at the server.
  • Signature eg Sign A
  • the login verification request corresponding to the first client (such as Sign B) is carried in the login verification request sent to the server where the second client is located, and the second guest
  • the server corresponding to the client performs verification on the pre-registered login signature Sign A and the Sign B obtained from the first client requesting verification, thereby realizing whether the first client can use the account currently logged in by the second client.
  • Quick verification of fast login which saves the login time of the first client and improves the login efficiency.
  • acquiring the login account currently logged in by the second client running on the terminal may be, but is not limited to, performing the first client in the terminal.
  • the communication with the second client is such that the first client directly obtains the login account currently logged in by the second client, and displays the login account on the login interface of the first client.
  • the login account currently registered by the second client is displayed on the login interface of the first client.
  • sending the login verification request to the second client may include, but is not limited to: creating a transparent interface of the second client on the login interface of the first client, and second to the transparent interface.
  • the client sends a login verification request.
  • the first login signature corresponding to the first client for login verification is carried in the login verification request.
  • the first client 702 obtains the currently logged in login account from the second client 706, and performs an operation (such as a selected operation) on the login account, and the response is
  • the operation command generated by the operation sends a login verification request to the second client server 708 through the second client 706, and verifies in the server 708 where the second client is located whether the first client is allowed to perform login using the login account. If the verification succeeds, the server 708 where the second client is located sends a response to the first client to the first client by using the second client (if the response carries the login ticket), and the first client 702 obtains the response according to the response.
  • the login request for the login is sent to the server 704 where the first client is located, and after the login to the first client 702 is displayed, the returned resource information is obtained from the server 704 corresponding to the first client.
  • the login account currently logged in by the second client running in the terminal is obtained by using the login interface of the first client running on the terminal, where the second client has an association relationship with the first client. And obtaining a login request generated after performing an operation on the login account on the login interface of the first client, wherein the login request is used to request to log in to the first client by using the login account; and further, logging in to the first client by using the login account in response to the login request end.
  • the first client obtains the login account currently logged in by the second client from the second client having the association relationship, and implements the fast login by using the obtained login account, thereby simplifying the login operation of the login client and reducing unnecessary Pay
  • the number of mutual times can save the login time of the login client, thereby improving the login efficiency.
  • the problem of low login efficiency caused by complicated operations such as multiple interactions is required.
  • the second obtaining unit 1004 includes:
  • a first receiving module configured to receive a selected command, wherein the selected command is used to select a login account displayed on the login interface
  • a sending module configured to send a login verification request to the second client in response to the selected instruction, where the login verification request carries at least a first login signature corresponding to the first client;
  • a first obtaining module configured to obtain a response to successful login verification sent by the second client, where the response carries a login ticket for logging in to the first client;
  • the second obtaining module is configured to obtain a login request generated by using the login ticket.
  • the foregoing first login signature may be, but is not limited to, a signature for uniquely identifying the first client.
  • the first login signature of the first client that is currently logged in is sent, and the first login signature is used to perform comparison verification with the pre-registered second login signature, thereby ensuring efficient and rapid verification of the first client fast login process. .
  • a selection instruction for a login account currently displayed by the second client displayed on the login interface of the first client is received, and a login verification request is sent in response to the selected instruction.
  • the waiting screen of "Login" is displayed on the terminal.
  • the login verification process of the first client may be implemented by, but not limited to, execution code as shown in FIG. 8.
  • the security of the first client to log in using the login account is ensured by verifying the obtained current login account of the second client.
  • a sending unit configured to send a registration request to a server corresponding to the second client before acquiring the login account currently logged in by the second client running in the terminal, where the registration request is used to request to register the first client at the server Second login signature;
  • An establishing unit for establishing an association relationship between the first client and the second client.
  • the association relationship between the first client and the second client may be a preset association relationship, for example, an instant messaging application client, and corresponding to the instant messaging application client.
  • the community space shares the application client.
  • the association relationship between the first client and the second client may also be established by registering the login signature. That is to say, before the first client logs in, the login signature of the first client is pre-registered in the server where the second client is located, so as to establish an association relationship between the first client and the second client.
  • the second login signature of the first client is registered by the server where the second client is located, so as to implement the first login signature obtained by using the second login signature and the first client that is requested to log in. Verification, so as to quickly verify whether the first client can use the above login account to perform fast effects.
  • the sending module includes:
  • the sending submodule is configured to send a login verification request to the second client on the transparent interface of the second client.
  • the second client Before the first client (APP-1) acquires the login account (ID) currently registered by the second client (APP-2) running in the terminal, the second client (APP-2)
  • the server (S2) where the server is located (S2) sends a registration request to register the login signature of the first client (APP-1) (such as Sign A).
  • the login verification request sent to the server (S2) where the second client (APP-2) is located will carry the first
  • the login signature corresponding to the client (such as Sign B), and the server (S2) where the second client (APP-2) is located is obtained by registering the pre-registered login signature (such as Sign A) with the first client from the request verification.
  • the login signature (such as Sign B) is verified, such as verifying that the received first login signature (such as Sign A) is consistent with the registered second login signature (such as Sign B), verifying the first login signature (such as Sign A)
  • the registered second login signature (such as Sign B) is consistent, the login verification is sent through the second client. Successful response.
  • the embodiment of the present application provides a quick verification of whether the first client can use the account currently logged in by the second client by using the verification of the login signature, thereby saving the login time of the first client and improving the login time of the first client.
  • the effect of login efficiency is a quick verification of whether the first client can use the account currently logged in by the second client by using the verification of the login signature, thereby saving the login time of the first client and improving the login time of the first client.
  • the first obtaining unit includes:
  • a second receiving module configured to receive a running request for running the first client
  • a display module configured to display a login interface of the first client in the terminal in response to the running request
  • a communication module configured to communicate between the first client and the second client, to obtain a login account currently logged in by the second client, and display the login account on the login interface of the first client.
  • the login interface of the first client is opened and displayed. And using the android binder communication mechanism to obtain the login account currently logged in by the second client from the second client. After the first client obtains the login account in the communication process, the login account is displayed on the login interface of the first client. For example, as shown in FIG. 5( a ), “using the second client to log in to the account 125253 Login button.
  • the login account currently logged in by the second client is obtained, so that the first client uses the login account to achieve fast login.
  • the effect is to save the login time of the login client, thereby achieving the effect of improving login efficiency.
  • the problem of low login efficiency caused by complicated operations such as multiple interactions is required.
  • the apparatus includes:
  • the first receiving unit 1102 is configured to receive a login verification request of the terminal running the first client to the login account, where the login account is a login account currently logged in by the second client running in the terminal, and the second client is The first client has an association relationship;
  • the verification unit 1104 is configured to verify, according to the login verification request, whether the first client uses the login account Number to perform login;
  • the sending unit 1106 is configured to send, by the second client, a response that the login verification succeeds when the verification succeeds, so that the first client performs the login by using the login account.
  • the foregoing device for logging in to the client may be, but is not limited to being applied to, a client having an association relationship (such as an instant messaging application client, and a community space sharing application client corresponding to the instant messaging application client). End) during the login process. That is, in the process of the first client using the login account for the quick login, the second client having the association relationship with the first client performs a quick verification on the login verification request of the login account, and verifies whether the first client is Log in to the login account to ensure that the first client can log in quickly, simplify the login operation of the login client, reduce the number of unnecessary interactions, and save the login time of the login client, thus improving the login efficiency.
  • a client having an association relationship such as an instant messaging application client, and a community space sharing application client corresponding to the instant messaging application client.
  • the login verification request may be sent to the second client after the first client obtains the selected instruction for the login account.
  • the first client running by the terminal 302 acquires the login account currently logged in by the second client having the association relationship at the time of login, and generates a selection instruction by performing a selection operation on the login account.
  • the terminal 302 will send a login verification request to the second client corresponding server 602 to enable the server 602 to verify whether the first client on the terminal 302 can perform the quick login using the login account using the pre-registered information.
  • the first client After receiving the response of the login verification succeeded by the server 602 by the second client, the first client acquires a login request for requesting to log in to the first client by using the login account, and sends the login request to the first client.
  • the corresponding server 306 is configured to obtain resource information to be displayed after login.
  • the server corresponding to the second client may be, but is not limited to, verifying the login signature.
  • the registration request is sent to the server corresponding to the second client, where the registration request is used to request the login of the first client at the server.
  • Signature eg Sign A
  • the login verification request corresponding to the first client (such as Sign B) is carried in the login verification request sent to the server where the second client is located, and the second client
  • the corresponding server verifies whether the first client can use the second client by verifying the pre-registered login signature Sign A and the sign B obtained from the first client requesting verification.
  • the currently logged in account performs fast verification of the quick login, thereby saving the login time of the first client and improving the login efficiency.
  • the first client 702 obtains the currently logged in login account from the second client 706, and performs an operation (such as a selected operation) on the login account, and the response is
  • the operation command generated by the operation sends a login verification request to the second client server 708 through the second client 706, and verifies in the server 708 where the second client is located whether the first client is allowed to perform login using the login account. If the verification succeeds, the server 708 where the second client is located sends a response to the first client to the first client by using the second client (if the response carries the login ticket), and the first client 702 obtains the response according to the response.
  • the login request for the login is sent to the server 704 where the first client is located, and after the login to the first client 702 is displayed, the returned resource information is obtained from the server 704 corresponding to the first client.
  • the obtained current login account of the second client is verified, thereby ensuring fast verification of the login by the first client using the login account, so as to simplify the login operation of the login client, and reduce the login operation.
  • the number of necessary interactions can save the login time of the login client, thereby improving the login efficiency. Further, it is also possible to ensure the security of the first client to log in using the above login account.
  • the login verification request carries at least a first login signature corresponding to the first client
  • the device further includes:
  • a second receiving unit configured to receive a registration request sent by the second client before receiving the login verification request of the terminal running the first client to the login account, where the registration request is used to request registration of the first client Second login signature;
  • An establishing unit for establishing an association relationship between the first client and the second client.
  • the association relationship between the first client and the second client may be a preset association relationship, for example, an instant messaging application client, and corresponding to the instant messaging application client.
  • the community space shares the application client.
  • the association relationship between the first client and the second client may also be established by registering the login signature. That is, before the first client logs in, the login signature of the first client is pre-registered in the server where the second client is located, so as to implement the first client with An association relationship is established between the second clients.
  • the second login signature of the first client is registered by the server where the second client is located, so as to implement the first login signature obtained by using the second login signature and the first client that is requested to log in. Verification, so as to quickly verify whether the first client can use the above login account to perform fast effects.
  • the verification unit 1104 includes: (1) a verification module, configured to verify whether the first login signature is consistent with the registered second login signature;
  • the sending unit 1106 includes: (1) a sending module, configured to send, by the second client, a response that the login verification succeeds when the first login signature is consistent with the registered second login signature, where the response carries A client performs a login login ticket.
  • the second client Before the first client (APP-1) acquires the login account (ID) currently registered by the second client (APP-2) running in the terminal, the second client (APP-2)
  • the server (S2) where the server is located (S2) sends a registration request to register the login signature of the first client (APP-1) (such as Sign A).
  • the login verification request sent to the server (S2) where the second client (APP-2) is located will carry the first
  • the login signature corresponding to the client (such as Sign B), and the server (S2) where the second client (APP-2) is located is obtained by registering the pre-registered login signature (such as Sign A) with the first client from the request verification.
  • the login signature (such as Sign B) is verified, such as verifying that the received first login signature (such as Sign A) is consistent with the registered second login signature (such as Sign B), verifying the first login signature (such as Sign A)
  • the second client sends a response that the login verification succeeds.
  • the embodiment of the present application provides a quick verification of whether the first client can use the account currently logged in by the second client by using the verification of the login signature, thereby saving the login time of the first client and improving the login time of the first client.
  • the effect of login efficiency is a quick verification of whether the first client can use the account currently logged in by the second client by using the verification of the login signature, thereby saving the login time of the first client and improving the login time of the first client.
  • the terminal of the client includes:
  • the communication interface 1202 is configured to obtain, on the login interface of the first client running on the terminal, the login account currently logged in by the second client running in the terminal, where the second client has an association relationship with the first client; And being configured to obtain, on the login interface of the first client, a login request generated after performing an operation on the login account, where the operation performed on the login account is performed on a login interface of the first client, and the login request is used for the request Log in to the first client using the login account.
  • the processor 1204 is connected to the communication interface 1202, and configured to acquire, on the login interface of the first client, a login request generated after performing an operation on the login account, where the login request is used to request to log in to the first client by using the login account. end;
  • the memory 1206 is connected to the communication interface 1202 and the processor 1204, and is configured to store a login account currently registered by the second client, and an association relationship between the second client and the first client.
  • a server for logging in a client for implementing the method for logging in to the client is further provided.
  • the server includes:
  • the communication interface 1302 is configured to receive a login verification request of the terminal running the first client to the login account, where the login account is a login account currently logged in by the second client running in the terminal, and the second client is first
  • the client has an association relationship; and is configured to send, by the second client, a response that the login verification succeeds when the verification succeeds, so that the first client performs login by using the login account;
  • the processor 1304 is connected to the communication interface 1302 and configured to verify whether the first client performs login using the login account in response to the login verification request;
  • the foregoing verification information may include, but is not limited to, a login signature of the first client.
  • a login signature of the first client For example, the first login signature corresponding to the first client and the second login signature of the first client registered by the second client carried in the login verification request sent by the first client.
  • Embodiments of the present invention also provide a storage medium.
  • the storage medium is arranged to store program code for performing the following steps:
  • S2 on the login interface of the first client, obtain a login request generated after performing an operation on the login account, where the login request is used to request to log in to the first client by using the login account;
  • the storage medium is further arranged to store program code for performing the following steps:
  • the second client sends a response that the login verification succeeds, so that the first client performs login by using the login account.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the embodiment of the present application further provides a terminal for implementing the foregoing method for logging in to the client.
  • a terminal for implementing the foregoing method for logging in to the client.
  • the terminal can be a mobile phone, a tablet, Any terminal device such as PDA (Personal Digital Assistant), POS (Point of Sales), and on-board computer, taking the terminal as a mobile phone as an example:
  • PDA Personal Digital Assistant
  • POS Point of Sales
  • on-board computer taking the terminal as a mobile phone as an example:
  • FIG. 14 is a block diagram showing a partial structure of a mobile phone related to a terminal provided by an embodiment of the present application.
  • the mobile phone includes: a memory 1410, an input unit 1420, a display unit 1430, a processor 1440, and the like.
  • the structure of the handset shown in FIG. 14 does not constitute a limitation to the handset, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements.
  • the memory 1410 can be used to store software programs and modules, and the processor 1440 executes various functional applications and data processing of the mobile phone by running software programs and modules stored in the memory 1410.
  • the memory 1410 can be used to store instruction codes for executing the above method embodiments, account information, resource information returned by the server, and the like.
  • the storage program area may include an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the storage data area may be stored according to the mobile phone. Use the created data (such as audio data, phone book, etc.).
  • memory 1410 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
  • the input unit 1420 can be configured to receive input numeric or character information and to generate key signal inputs related to user settings and function controls of the handset.
  • the login interface of the client may be operated through the input unit 1420, such as selecting a login account displayed on the login interface.
  • the input unit 1420 may include a touch panel 1421 and other input devices 1422.
  • the touch panel 1421 also referred to as a touch screen, can collect touch operations on or near the user (such as the user using a finger, a stylus, or the like on the touch panel 1421 or near the touch panel 1421. Operation), and drive the corresponding connecting device according to a preset program.
  • the touch panel 1421 can include two parts: a touch detection device and a touch controller.
  • the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information.
  • the processor 1440 is provided and can receive commands from the processor 1440 and execute them.
  • the touch panel 1421 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • the input unit 1420 may also include other input devices 1422.
  • other input devices 1422 may include, but are not limited to, One or more of a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, joystick, and the like.
  • the display unit 1430 can be used to display information input by the user or information provided to the user as well as various menus of the mobile phone.
  • the display unit 1430 can be used to display the login interface of the client and the resource information returned by the server.
  • the display unit 1430 may include a display panel 1431.
  • the display panel 1431 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
  • the touch panel 1421 can cover the display panel 1431. When the touch panel 1421 detects a touch operation thereon or nearby, the touch panel 1421 transmits to the processor 1440 to determine the type of the touch event, and then the processor 1440 according to the touch event.
  • the type provides a corresponding visual output on display panel 1431.
  • the touch panel 1421 and the display panel 1431 are used as two separate components to implement the input and input functions of the mobile phone in FIG. 14, in some embodiments, the touch panel 1421 can be integrated with the display panel 1431. Realize the input and output functions of the phone.
  • the processor 1440 is a control center for the handset that connects various portions of the entire handset using various interfaces and lines, by executing or executing software programs and/or modules stored in the memory 1410, and invoking data stored in the memory 1410, The phone's various functions and processing data, so that the overall monitoring of the phone.
  • the processor 1440 may include one or more processing units; preferably, the processor 1440 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, and the like.
  • the modem processor primarily handles wireless communications. It will be appreciated that the above described modem processor may also not be integrated into the processor 1440.
  • the processor 1440 included in the terminal further has a method flow for controlling execution by the terminal.
  • the integrated unit in the above embodiment if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in the above-described computer readable storage medium.
  • the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause one or more computer devices (which may be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the disclosed client may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, unit or module, and may be electrical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本发明公开了一种登录客户端的方法及装置。其中，该方法包括：在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号，其中，第二客户端与第一客户端具有关联关系；在第一客户端的登录界面上，获取对登录账号执行操作后所生成的登录请求，其中，登录请求用于请求使用登录账号登录第一客户端；响应登录请求使用登录账号登录第一客户端。

Description

登录客户端的方法，装置及存储介质
本申请要求于2016年3月11日提交中国专利局、申请号201610140719.4、发明名称为“登录客户端的方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及计算机领域，具体而言，涉及一种登录客户端的方法，装置及存储介质。
背景技术
目前，现有的登录客户端的方法通常包括以下两种：
1)使用账号密码登录，如图1(a)-图1(d)所示，先在客户端的登录界面输入登录账号，然后输入对应的密码，并等待对输入的账号和密码的登录验证，其中，用户的登录账号和密码往往都设置的很长。这样通过手动输入账号密码的过程来实现登录客户端的方案，所需执行的登录操作较为复杂，从而导致登录所花费的登录时间较长，进而造成登录效率较低的问题。
2)通过第三方授权登录，如图2(a)-图2(d)所示，通过向可靠的第三方授权实现登录，这样就需要增加授权登录的确认操作，如图2(b)-图2(c)所示，进而才能执行进一步的授权登录过程。然而，这种方式不仅安全性较低，而且增加了交互次数，使得登录操作变得更加复杂，也将影响登录客户端的登录效率。
针对上述的问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种登录客户端的方法及装置，以至少解决采用现有的登录方法所导致的登录效率较低的技术问题。
根据本发明实施例的一个方面，提供了一种登录客户端的方法，包括：在终端运行的第一客户端的登录界面上，获取在上述终端运行的第二客户端当前登录的登录账号，其中，上述第二客户端与上述第一客户端具有关联关系；在上述第一客户端的登录界面上，对获取到的登录账号执行操作，获取对上述登录账号执行操作后所生成的登录请求，其中，上述登录请求用于请求使用上述登录账号登录上述第一客户端；响应上述登录请求使用上述登录账号登录上述第一客户端。
根据本发明实施例的另一方面，还提供了一种登录客户端的方法，包括：接收运行有第一客户端的终端对登录账号的登录验证请求，其中，上述登录账号为在上述终端运行的第二客户端当前登录的登录账号，上述第二客户端与上述第一客户端具有关联关系；响应上述登录验证请求验证上述第一客户端是否使用上述登录账号执行登录；在验证成功时，通过上述第二客户端发送登录验证成功的响应，以使上述第一客户端使用上述登录账号执行登录。
根据本发明实施例的又一个方面，提供了一种登录客户端的装置，包括：第一获取单元，用于在终端运行的第一客户端的登录界面上，获取在上述终端运行的第二客户端当前登录的登录账号，其中，上述第二客户端与上述第一客户端具有关联关系；第二获取单元，用于在上述第一客户端的登录界面上，获取对上述登录账号执行操作后所生成的登录请求，其中，所述对登录账号执行的操作在第一客户端的登录界面上进行，上述登录请求用于请求使用上述登录账号登录上述第一客户端；登录单元，用于响应上述登录请求使用上述登录账号登录上述第一客户端。
根据本发明实施例的又一方面，还提供了一种登录客户端的装置，包括：第一接收单元，用于接收运行有第一客户端的终端对登录账号的登录验证请求，其中，上述登录账号为在上述终端运行的第二客户端当前登录的登录账号，上述第二客户端与上述第一客户端具有关联关系；验证单元，用于响应上述登录验证请求验证上述第一客户端是否使用上述登录账号执行登录；发送单元，用于在验证成功时，通过上述第二客户端发送登录验证成功的响应，以使上述第一客户端使用上述登录账号执行登录。
根据本发明实施例的又一方面，还提供了提供一种非易失性存储介质，其 中存储有计算机可读指令。当所述指令被执行时，使得计算机执行上述的登入客户端的方法。
在本发明实施例中，通过在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号，其中，第二客户端与第一客户端具有关联关系；并在第一客户端的登录界面上获取对登录账号执行操作后所生成的登录请求，其中，登录请求用于请求使用登录账号登录第一客户端；进而响应登录请求使用登录账号登录第一客户端。也就是说，第一客户端通过从具有关联关系的第二客户端获取第二客户端当前登录的登录账号，并使用获取到的该登录账号实现快速登录，从而实现简化登录客户端的登录操作，减少不必要的交互次数，达到节省登录客户端的登录时间，进而实现提高登录效率的效果。以克服现有技术需要通过多次交互等复杂的操作所导致的登录效率较低的问题。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据现有技术的一种登录客户端的方法的示意图；
图2是根据现有技术的另一种登录客户端的方法的示意图；
图3是根据本发明实施例的一种可选的登录客户端的方法的应用环境示意图；
图4是根据本发明实施例的一种可选的登录客户端的方法的流程图；
图5是根据本发明实施例的一种可选的登录客户端的方法的示意图；
图6是根据本发明实施例的另一种可选的登录客户端的方法的应用环境示意图；
图7是根据本发明实施例的另一种可选的登录客户端的方法的流程图；
图8是根据本发明实施例的另一种可选的登录客户端的方法的示意图；
图9是根据本发明实施例的又一种可选的登录客户端的方法的流程图；
图10是根据本发明实施例的一种可选的登录客户端的装置的示意图；
图11是根据本发明实施例的另一种可选的登录客户端的装置的示意图；
图12是根据本发明实施例的一种可选的登录客户端的终端的示意图；
图13是根据本发明实施例的一种可选的登录客户端的服务器的示意图；以及
图14为本发明实施例的一种登入客户端的终端的组成结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本发明方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分的实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本发明保护的范围。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本发明的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
实施例1
根据本发明实施例，提供了一种登录客户端的方法的实施例，该登录客户端的方法可以但不限于应用于如图3所示的应用环境中，在终端302运行的第一客户端的登录界面上，获取在该终端302运行的第二客户端当前登录的登录账号，其中，第二客户端与第一客户端具有关联关系，然后在第一客户端的登录界面上，对获取到的上述登录账号执行操作，获取对该登录账号执行操作后所生成的登录请求，其中，登录请求用于请求使用登录账号登录第一客户端，响应该登录请求使用上述登录账号登录第一客户端，从而实现将该登录请求发 送给第一客户端对应的服务器306，在终端302显示登录第一客户端后，通过网络304从第一客户端对应的服务器306返回资源信息，其中第一客户端对应的服务器是为第一客户端提供服务的服务器。通过在第一客户端登录界面上获取与第一客户端关联的第二客户端当前登录的登录账号，使用该登录账号直接登录，从而实现简化登录客户端的登录操作，达到节省登录时间，进而实现提高登录效率的效果。
可选地，在本实施例中，上述终端可以包括但不限于以下至少之一：手机、平板电脑、笔记本电脑、台式机。上述只是一种示例，本实施例对此不做任何限定。可选地，在本实施例中，上述网络可以包括但不限于以下至少之一：广域网、城域网、局域网。上述只是一种示例，本实施例对此不做任何限定。
根据本发明实施例，提供了一种登录客户端的方法，如图4所示，该方法包括：
S402，在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号，其中，第二客户端与第一客户端具有关联关系；
S404，在第一客户端的登录界面上，对获取到的登录账号执行操作，获取对登录账号执行操作后所生成的登录请求，其中，登录请求用于请求使用登录账号登录第一客户端；
S406，响应登录请求使用登录账号登录第一客户端。
可选地，在本实施例中，上述登录客户端的方法可以但不限于应用于具有关联关系的客户端(例如即时通讯应用客户端，及与该即时通讯应用客户端对应的社区空间共享应用客户端)的登录过程中。也就是说，在登录第一客户端时，利用第一客户端与第二客户端之间的关联关系，获取在终端上运行第二客户端当前登录的登录账号(例如图5所示账号125253)，进一步，使用该登录账号实现对第一客户端的快速登录，如图5(a)-5(c)所示，从而实现在登录第一客户端后，显示从第一客户端对应的服务器返回的资源信息。上述举例只是一种实施例，本实施例中对此不做任何限定。
需要说明的是，在本实施例中，通过在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号，其中，第二客户端与 第一客户端具有关联关系；并在第一客户端的登录界面上获取对登录账号执行操作后所生成的登录请求，其中，登录请求用于请求使用登录账号登录第一客户端；进而响应登录请求使用登录账号登录第一客户端。第一客户端通过从具有关联关系的第二客户端获取第二客户端当前登录的登录账号，并使用获取到的该登录账号实现快速登录，从而实现简化登录客户端的登录操作，减少不必要的交互次数，达到节省登录客户端的登录时间，进而实现提高登录效率的效果。以克服现有技术需要通过多次交互等复杂的操作所导致的登录效率较低的问题。
可选地，在本实施例中，在第一客户端的登录界面上，获取对登录账号执行操作后所生成的登录请求包括：第一客户端获取对登录账号执行选中操作所生成的选中指令，响应该选中指令向第二客户端发送登录验证请求。然后，由第二客户端对应的服务器来验证判断是否允许该第一客户端使用上述登录账号执行登录，并在验证成功时，通过第二客户端发送登录验证成功的响应，以使第一客户端可以使用上述登录账号执行快速登录，其中，所述第二客户端对应的服务器是为第二客户端提供服务的服务器。
也就是说，如图6所示，终端302运行的第一客户端在登录时获取具有关联关系的第二客户端当前登录的登录账号后，并通过对该登录账号执行选中操作生成选中指令，响应该选中指令，终端302将向第二客户端对应的服务器602发送登录验证请求，以使服务器602利用预先注册的信息验证终端302上的第一客户端是否可以使用上述登录账号执行快速登录。第一客户端在通过第二客户端收到服务器602发送的登录验证成功的响应后，将获取用于请求使用登录账号登录第一客户端的登录请求，并将该登录请求发送给第一客户端对应的服务器306，以获取登录后所要显示的资源信息。
可选地，在本实施例中，在上述验证过程中，第二客户端对应的服务器可以但不限于对登录签名进行验证。例如，在第一客户端获取在终端运行的第二客户端当前登录的登录账号之前，向第二客户端对应的服务器发送注册请求，其中，注册请求用于请求在服务器注册第一客户端的登录签名(如Sign A)。在第一客户端获取上述登录账号后执行登录时，在向第二客户端所在服务器发送登录验证请求中将携带有与该第一客户端对应的登录签名(如Sign B)，第二客 户端对应的服务器通过对预先注册的登录签名Sign A与从请求验证的第一客户端获取到的Sign B进行验证，从而实现对第一客户端是否可以使用第二客户端当前登录的账号进行快速登录的快速验证，进而达到节省第一客户端的登录时间，提高登录效率的效果。
可选地，在本实施例中，在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号可以但不限于：通过在终端中进行第一客户端与第二客户端之间的通信，以使第一客户端直接获取第二客户端当前登录的登录账号，并在第一客户端的登录界面显示该登录账号。如图5(a)所示在第一客户端的登录界面上显示第二客户端当前登录的登录账号。
可选地，在本实施例中，向第二客户端发送登录验证请求可以包括但不限于：在第一客户端的登录界面上创建第二客户端的透明界面，并在该透明界面上向第二客户端发送登录验证请求。从而实现在该登录验证请求中携带用于登录验证的与第一客户端对应的第一登录签名。
具体结合以下示例进行说明，如图7所示步骤S702-S716，第一客户端702从第二客户端706获取当前登录的登录账号，并对该登录账号执行操作(如选中操作)，响应由该操作生成的操作指令通过第二客户端706向第二客户端所在服务器708发送登录验证请求，在第二客户端对应服务器708中验证是否允许第一客户端使用该登录账号执行登录。在验证成功的情况下，第二客户端所在服务器708通过第二客户端向第一客户端发送登录验证成功的响应(如该响应中携带有登录票据)，第一客户端702根据该响应获取用于登录的登录请求，并将该登录请求发送给第一客户端所在服务器704，在显示登录第一客户端702后，从第一客户端对应的服务器704获取返回的资源信息。
通过本申请提供的实施例，通过在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号，其中，第二客户端与第一客户端具有关联关系；并在第一客户端的登录界面上获取对登录账号执行操作后所生成的登录请求，其中，登录请求用于请求使用登录账号登录第一客户端；进而响应登录请求使用登录账号登录第一客户端。第一客户端通过从具有关联关系的第二客户端获取第二客户端当前登录的登录账号，并使用获取到的该登录账号实现快速登录，从而实现简化登录客户端的登录操作，减少不必要的交 互次数，达到节省登录客户端的登录时间，进而实现提高登录效率的效果。以克服现有技术需要通过多次交互等复杂的操作所导致的登录效率较低的问题。
作为一种可选的方案，在第一客户端的登录界面上，对获取到的登录账号执行操作，获取对第二客户端的登录账号执行操作后所生成的登录请求包括：
S1，接收选中指令，其中，选中指令用于选择显示在登录界面上的登录账号；
S2，响应选中指令向第二客户端发送登录验证请求，其中，登录验证请求中至少携带有与第一客户端对应的第一登录签名；
S3，获取第二客户端发送的登录验证成功的响应，其中，响应中携带有用于登录第一客户端的登录票据；
S4，获取使用登录票据生成的登录请求。
可选地，在本实施例中，上述第一登录签名可以但不限于为用于唯一标识第一客户端的签名。通过发送当前请求登录的第一客户端的第一登录签名，实现利用该第一登录签名与预先注册的第二登录签名进行比对验证，从而保证对第一客户端快速登录过程的高效快速地验证。
具体结合以下示例进行说明，接收对显示在第一客户端的登录界面上的第二客户端当前登录的登录账号(如图5(a)所示)的选中指令，响应该选中指令发送登录验证请求，并在终端显示“登录中”的等待界面。在获取到第二客户端发送的登录验证成功的响应后，获取使用用于登录第一客户端的登录票据生成的登录请求，并将该登录请求发送给第一客户端所在服务器。
例如，在本实施例中可以但不限于通过如图8所示的执行代码实现第一客户端的登录验证过程。
通过本申请提供的实施例，通过对获取到的第二客户端当前登录账号进行验证，从而保证第一客户端使用该登录账号进行登录的安全性。
作为一种可选的方案，在获取在终端运行的第二客户端当前登录的登录账号之前，还包括：
S1，向第二客户端对应的服务器发送注册请求，其中，注册请求用于请求 在服务器注册第一客户端的第二登录签名；
S2，建立第一客户端与第二客户端之间的关联关系。
可选地，在本实施例中，上述第一客户端与第二客户端之间的关联关系可以为预设的关联关系，例如，即时通讯应用客户端，及与该即时通讯应用客户端对应的社区空间共享应用客户端。
此外，在本实施例中，也可以通过注册登录签名的方式，建立第一客户端与第二客户端之间的关联关系。也就是说，在第一客户端登录之前，在第二客户端所在服务器中预先注册该第一客户端的登录签名，以实现在第一客户端与第二客户端之间建立关联关系。
通过本申请提供的实施例，通过在第二客户端所在服务器注册第一客户端的第二登录签名，以实现利用该第二登录签名与从请求登录的第一客户端获取的第一登录签名进行验证，从而实现快速验证第一客户端是否可以利用上述登录账号执行快速的效果。
作为一种可选的方案，在响应选中指令向第二客户端发送登录验证请求之后，且在获取第二客户端发送的登录验证成功的响应之前，还包括：
S1，服务器通过第二客户端接收第一登录签名；
S2，服务器验证接收到的第一登录签名与注册的第二登录签名是否一致；
S3，在验证出第一登录签名与注册的第二登录签名一致时，服务器通过第二客户端发送登录验证成功的响应。
具体结合以下示例进行说明，在第一客户端(APP-1)获取在终端运行的第二客户端(APP-2)当前登录的登录账号(ID)之前，向第二客户端(APP-2)所在的服务器(S2)发送注册请求注册第一客户端(APP-1)的登录签名(如Sign A)。
在第一客户端(APP-1)获取上述登录账号(ID)后执行登录时，在向第二客户端(APP-2)所在服务器(S2)发送登录验证请求中将携带有与该第一客户端对应的登录签名(如Sign B)，第二客户端(APP-2)对应的服务器(S2)通过对预先注册的登录签名(如Sign A)与从请求验证的第一客户端获取到的登 录签名(如Sign B)进行验证，如验证接收到的第一登录签名(如Sign A)与注册的第二登录签名(如Sign B)是否一致，在验证出第一登录签名(如Sign A)与注册的第二登录签名(如Sign B)一致时，则通过第二客户端发送登录验证成功的响应。
通过本申请提供的实施例，通过对登录签名的验证，实现对第一客户端是否可以使用第二客户端当前登录的账号进行快速登录的快速验证，从而达到节省第一客户端的登录时间，提高登录效率的效果。
作为一种可选的方案，响应选中指令向第二客户端发送登录验证请求包括：
S1，响应选中指令在第一客户端的登录界面上创建第二客户端的透明界面；
S2，在第二客户端的透明界面上向第二客户端发送登录验证请求。
具体结合以下示例进行说明，在接收到对如图5所示的“使用第二客户端登录的账号125253登录”的选中指令后，第一客户端在登录界面上创建第二客户端的透明界面，如通过android startActivity()调用第二客户端的透明界面，第二客户端在接收到startActivity()请求后，通过使用android的Activity.getCallingActivity()获取第一客户端的第一登录签名，并向第二客户端所在服务器发送携带有第一登录签名的登录验证请求。
通过本申请提供的实施例，通过在第一客户端的登录界面上创建第二客户端的透明界面，以达到减少登录过程与用户的交互次数，使用户对利用第二客户端发送登录验证的界面无感知，从而实现改善用户体验的效果。
作为一种可选的方案，在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号包括：
S1，接收运行第一客户端的运行请求；
S2，响应运行请求在终端显示第一客户端的登录界面；
S3，在第一客户端与第二客户端之间进行通信，以获取第二客户端当前登录的登录账号，并在第一客户端的登录界面显示登录账号。
具体结合以下示例进行说明，接收运行第一客户端的运行请求，在确认终端已安装第一客户端及与第一客户端具有关联关系的第二客户端后，打开并显 示第一客户端的登录界面，并使用android binder通信机制从第二客户端获取第二客户端当前登录的登录账号。在第一客户端在通信过程中获取到上述登录账号后，在第一客户端的登录界面上显示上述登录账号，例如，如图5(a)所示，“使用第二客户端登录的账号125253登录”的按键。
通过本申请提供的实施例，通过在第一客户端与第二客户端之间进行通信，以获取第二客户端当前登录的登录账号，从而实现使第一客户端使用该登录账号达到快速登录的效果，达到节省登录客户端的登录时间，进而实现提高登录效率的效果。以克服现有技术需要通过多次交互等复杂的操作所导致的登录效率较低的问题。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
实施例2
根据本发明实施例，提供了一种登录客户端的方法，如图9所示，该方法包括：
S902，接收运行有第一客户端的终端对登录账号的登录验证请求，其中，登录账号为在终端运行的第二客户端当前登录的登录账号，第二客户端与第一客户端具有关联关系；
S904，响应登录验证请求验证第一客户端是否使用登录账号执行登录；
S906，在验证成功时，通过第二客户端发送登录验证成功的响应，以使第一客户端使用登录账号执行登录。
可选地，在本实施例中，上述登录客户端的方法可以但不限于应用于具有关联关系的客户端(例如即时通讯应用客户端，及与该即时通讯应用客户端对应的社区空间共享应用客户端)的登录过程中。也就是说，在第一客户端利用登录账号进行快速登录的过程中，由与第一客户端具有关联关系的第二客户端对登录账号的登录验证请求进行快速验证，验证第一客户端是否使用登录账号执行登录，从而保证第一客户端可以实现快速登录，简化登录客户端的登录操作，减少不必要的交互次数，达到节省登录客户端的登录时间，进而实现提高登录效率的效果。
可选地，在本实施例中，可以但不限于在第一客户端获取到对登录账号的选中指令后，将上述登录验证请求发送给第二客户端。
也就是说，如图6所示，终端302运行的第一客户端在登录时获取具有关联关系的第二客户端当前登录的登录账号后，并通过对该登录账号执行选中操作生成选中指令，响应该选中指令，终端302将向第二客户端所在服务器602发送登录验证请求，以使服务器602利用预先注册的信息验证终端302上的第一客户端是否可以使用上述登录账号执行快速登录。第一客户端在通过第二客户端收到服务器602发送的登录验证成功的响应后，将获取用于请求使用登录账号登录第一客户端的登录请求，并将该登录请求发送给第一客户端对应的服务器306，以获取登录后所要显示的资源信息。
可选地，在本实施例中，在上述验证过程中，第二客户端对应的服务器可以但不限于对登录签名进行验证。例如，在第一客户端获取在终端运行的第二客户端当前登录的登录账号之前，向第二客户端对应的服务器发送注册请求，其中，注册请求用于请求在服务器注册第一客户端的登录签名(如Sign A)。在第一客户端获取上述登录账号后执行登录时，在向第二客户端所在服务器发送登录验证请求中将携带有与该第一客户端对应的登录签名(如Sign B)，第二客户端对应的服务器通过对预先注册的登录签名Sign A与从请求验证的第一客户端获取到的Sign B进行验证，从而实现对第一客户端是否可以使用第二客户端当前登录的账号进行快速登录的快速验证，进而达到节省第一客户端的登录时 间，提高登录效率的效果。
具体结合以下示例进行说明，如图7所示步骤S702-S716，第一客户端702从第二客户端706获取当前登录的登录账号，并对该登录账号执行操作(如选中操作)，响应由该操作生成的操作指令通过第二客户端706向第二客户端所在服务器708发送登录验证请求，在第二客户端所在服务器708中验证是否允许第一客户端使用该登录账号执行登录。在验证成功的情况下，第二客户端所在服务器708通过第二客户端向第一客户端发送登录验证成功的响应(如该响应中携带有登录票据)，第一客户端702根据该响应获取用于登录的登录请求，并将该登录请求发送给第一客户端所在服务器704，在显示登录第一客户端702后，从第一客户端对应的服务器704获取返回的资源信息。
通过本申请提供的实施例，通过对获取到的第二客户端当前登录账号进行验证，从而保证对第一客户端使用该登录账号进行登录的快速验证，以简化登录客户端的登录操作，减少不必要的交互次数，达到节省登录客户端的登录时间，进而实现提高登录效率的效果。进一步，还可以保证第一客户端使用上述登录账号进行登录的安全性。
作为一种可选的方案，登录验证请求中至少携带有与第一客户端对应的第一登录签名，其中，在接收运行有第一客户端的终端对登录账号的登录验证请求之前，还包括：
S1，接收通过第二客户端发送的注册请求，其中，注册请求用于请求注册第一客户端的第二登录签名；
S2，建立第一客户端与第二客户端之间的关联关系。
可选地，在本实施例中，上述第一客户端与第二客户端之间的关联关系可以为预设的关联关系，例如，即时通讯应用客户端，及与该即时通讯应用客户端对应的社区空间共享应用客户端。
此外，在本实施例中，也可以通过注册登录签名的方式，建立第一客户端与第二客户端之间的关联关系。也就是说，在第一客户端登录之前，在第二客户端所在服务器中预先注册该第一客户端的登录签名，以实现在第一客户端与第二客户端之间建立关联关系。
通过本申请提供的实施例，通过在第二客户端所在服务器注册第一客户端的第二登录签名，以实现利用该第二登录签名与从请求登录的第一客户端获取的第一登录签名进行验证，从而实现快速验证第一客户端是否可以利用上述登录账号执行快速的效果。
作为一种可选的方案，
S1，响应登录验证请求验证第一客户端是否使用登录账号执行登录包括：S11，验证第一登录签名与注册的第二登录签名是否一致；
S2，在验证成功时，通过第二客户端发送登录验证成功的响应包括：S21，在第一登录签名与注册的第二登录签名一致时，通过第二客户端发送登录验证成功的响应，其中，响应中携带有使第一客户端执行登录的登录票据。
具体结合以下示例进行说明，在第一客户端(APP-1)获取在终端运行的第二客户端(APP-2)当前登录的登录账号(ID)之前，向第二客户端(APP-2)所在的服务器(S2)发送注册请求注册第一客户端(APP-1)的登录签名(如Sign A)。
在第一客户端(APP-1)获取上述登录账号(ID)后执行登录时，在向第二客户端(APP-2)所在服务器(S2)发送登录验证请求中将携带有与该第一客户端对应的登录签名(如Sign B)，第二客户端(APP-2)所在的服务器(S2)通过对预先注册的登录签名(如Sign A)与从请求验证的第一客户端获取到的登录签名(如Sign B)进行验证，如验证接收到的第一登录签名(如Sign A)与注册的第二登录签名(如Sign B)是否一致，在验证出第一登录签名(如Sign A)与注册的第二登录签名(如Sign B)一致时，则通过第二客户端发送登录验证成功的响应。
通过本申请提供的实施例，通过对登录签名的验证，实现对第一客户端是否可以使用第二客户端当前登录的账号进行快速登录的快速验证，从而达到节省第一客户端的登录时间，提高登录效率的效果。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。 其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
实施例3
根据本发明实施例，还提供了一种用于实施上述登录客户端的方法的登录客户端的装置，如图10所示，该装置包括：
1)第一获取单元1002，用于在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号，其中，第二客户端与第一客户端具有关联关系；
2)第二获取单元1004，用于在第一客户端的登录界面上，获取对登录账号执行操作后所生成的登录请求，其中，所述对登录账号执行的操作在第一客户端的登录界面上进行，登录请求用于请求使用登录账号登录第一客户端；
3)登录单元1006，用于响应登录请求使用登录账号登录第一客户端。
可选地，在本实施例中，上述登录客户端的装置可以但不限于应用于具有关联关系的客户端(例如即时通讯应用客户端，及与该即时通讯应用客户端对应的社区空间共享应用客户端)的登录过程中。也就是说，在登录第一客户端时，利用第一客户端与第二客户端之间的关联关系，获取在终端上运行第二客户端当前登录的登录账号(例如图5所示账号125253)，进一步，使用该登录账号实现对第一客户端的快速登录，如图5(a)-5(c)所示，从而实现在登录第一客户端后，显示从第一客户端对应的服务器返回的资源信息。上述举例只是一种实施例，本实施例中对此不做任何限定。
需要说明的是，在本实施例中，通过在终端运行的第一客户端的登录界面 上，获取在终端运行的第二客户端当前登录的登录账号，其中，第二客户端与第一客户端具有关联关系；并在第一客户端的登录界面上获取对登录账号执行操作后所生成的登录请求，其中，登录请求用于请求使用登录账号登录第一客户端；进而响应登录请求使用登录账号登录第一客户端。第一客户端通过从具有关联关系的第二客户端获取第二客户端当前登录的登录账号，并使用获取到的该登录账号实现快速登录，从而实现简化登录客户端的登录操作，减少不必要的交互次数，达到节省登录客户端的登录时间，进而实现提高登录效率的效果。以克服现有技术需要通过多次交互等复杂的操作所导致的登录效率较低的问题。
可选地，在本实施例中，在第一客户端的登录界面上，获取对登录账号执行操作后所生成的登录请求包括：第一客户端获取对登录账号执行选中操作所生成的选中指令，响应该选中指令向第二客户端发送登录验证请求。然后，由第二客户端对应的服务器来验证判断是否允许该第一客户端使用上述登录账号执行登录，并在验证成功时，通过第二客户端发送登录验证成功的响应，以使第一客户端可以使用上述登录账号执行快速登录。
也就是说，如图6所示，终端302运行的第一客户端在登录时获取具有关联关系的第二客户端当前登录的登录账号后，并通过对该登录账号执行选中操作生成选中指令，响应该选中指令，终端302将向第二客户端对应服务器602发送登录验证请求，以使服务器602利用预先注册的信息验证终端302上的第一客户端是否可以使用上述登录账号执行快速登录。第一客户端在通过第二客户端收到服务器602发送的登录验证成功的响应后，将获取用于请求使用登录账号登录第一客户端的登录请求，并将该登录请求发送给第一客户端对应的服务器306，以获取登录后所要显示的资源信息。
可选地，在本实施例中，在上述验证过程中，第二客户端对应的服务器可以但不限于对登录签名进行验证。例如，在第一客户端获取在终端运行的第二客户端当前登录的登录账号之前，向第二客户端对应的服务器发送注册请求，其中，注册请求用于请求在服务器注册第一客户端的登录签名(如Sign A)。在第一客户端获取上述登录账号后执行登录时，在向第二客户端所在服务器发送登录验证请求中将携带有与该第一客户端对应的登录签名(如Sign B)，第二客 户端对应的服务器通过对预先注册的登录签名Sign A与从请求验证的第一客户端获取到的Sign B进行验证，从而实现对第一客户端是否可以使用第二客户端当前登录的账号进行快速登录的快速验证，进而达到节省第一客户端的登录时间，提高登录效率的效果。
可选地，在本实施例中，在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号可以但不限于：通过在终端中进行第一客户端与第二客户端之间的通信，以使第一客户端直接获取第二客户端当前登录的登录账号，并在第一客户端的登录界面显示该登录账号。如图5(a)所示在第一客户端的登录界面上显示第二客户端当前登录的登录账号。
可选地，在本实施例中，向第二客户端发送登录验证请求可以包括但不限于：在第一客户端的登录界面上创建第二客户端的透明界面，并在该透明界面上向第二客户端发送登录验证请求。从而实现在该登录验证请求中携带用于登录验证的与第一客户端对应的第一登录签名。
具体结合以下示例进行说明，如图7所示步骤S702-S716，第一客户端702从第二客户端706获取当前登录的登录账号，并对该登录账号执行操作(如选中操作)，响应由该操作生成的操作指令通过第二客户端706向第二客户端所在服务器708发送登录验证请求，在第二客户端所在服务器708中验证是否允许第一客户端使用该登录账号执行登录。在验证成功的情况下，第二客户端所在服务器708通过第二客户端向第一客户端发送登录验证成功的响应(如该响应中携带有登录票据)，第一客户端702根据该响应获取用于登录的登录请求，并将该登录请求发送给第一客户端所在服务器704，在显示登录第一客户端702后，从第一客户端对应的服务器704获取返回的资源信息。
通过本申请提供的实施例，通过在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号，其中，第二客户端与第一客户端具有关联关系；并在第一客户端的登录界面上获取对登录账号执行操作后所生成的登录请求，其中，登录请求用于请求使用登录账号登录第一客户端；进而响应登录请求使用登录账号登录第一客户端。第一客户端通过从具有关联关系的第二客户端获取第二客户端当前登录的登录账号，并使用获取到的该登录账号实现快速登录，从而实现简化登录客户端的登录操作，减少不必要的交 互次数，达到节省登录客户端的登录时间，进而实现提高登录效率的效果。以克服现有技术需要通过多次交互等复杂的操作所导致的登录效率较低的问题。
作为一种可选的方案，第二获取单元1004包括：
1)第一接收模块，用于接收选中指令，其中，选中指令用于选择显示在登录界面上的登录账号；
2)发送模块，用于响应选中指令向第二客户端发送登录验证请求，其中，登录验证请求中至少携带有与第一客户端对应的第一登录签名；
3)第一获取模块，用于获取第二客户端发送的登录验证成功的响应，其中，响应中携带有用于登录第一客户端的登录票据；
4)第二获取模块，用于获取使用登录票据生成的登录请求。
可选地，在本实施例中，上述第一登录签名可以但不限于为用于唯一标识第一客户端的签名。通过发送当前请求登录的第一客户端的第一登录签名，实现利用该第一登录签名与预先注册的第二登录签名进行比对验证，从而保证对第一客户端快速登录过程的高效快速地验证。
具体结合以下示例进行说明，接收对显示在第一客户端的登录界面上的第二客户端当前登录的登录账号(如图5(a)所示)的选中指令，响应该选中指令发送登录验证请求，并在终端显示“登录中”的等待界面。在获取到第二客户端发送的登录验证成功的响应后，获取使用用于登录第一客户端的登录票据生成的登录请求，并将该登录请求发送给第一客户端所在服务器。
例如，在本实施例中可以但不限于通过如图8所示的执行代码实现第一客户端的登录验证过程。
通过本申请提供的实施例，通过对获取到的第二客户端当前登录账号进行验证，从而保证第一客户端使用该登录账号进行登录的安全性。
作为一种可选的方案，还包括：
1)发送单元，用于在获取在终端运行的第二客户端当前登录的登录账号之前，向第二客户端对应的服务器发送注册请求，其中，注册请求用于请求在服务器注册第一客户端的第二登录签名；
2)建立单元，用于建立第一客户端与第二客户端之间的关联关系。
可选地，在本实施例中，上述第一客户端与第二客户端之间的关联关系可以为预设的关联关系，例如，即时通讯应用客户端，及与该即时通讯应用客户端对应的社区空间共享应用客户端。
此外，在本实施例中，也可以通过注册登录签名的方式，建立第一客户端与第二客户端之间的关联关系。也就是说，在第一客户端登录之前，在第二客户端所在服务器中预先注册该第一客户端的登录签名，以实现在第一客户端与第二客户端之间建立关联关系。
通过本申请提供的实施例，通过在第二客户端所在服务器注册第一客户端的第二登录签名，以实现利用该第二登录签名与从请求登录的第一客户端获取的第一登录签名进行验证，从而实现快速验证第一客户端是否可以利用上述登录账号执行快速的效果。
作为一种可选的方案，发送模块包括：
1)创建子模块，用于响应选中指令在第一客户端的登录界面上创建第二客户端的透明界面；
2)发送子模块，用于在第二客户端的透明界面上向第二客户端发送登录验证请求。
具体结合以下示例进行说明，在第一客户端(APP-1)获取在终端运行的第二客户端(APP-2)当前登录的登录账号(ID)之前，向第二客户端(APP-2)所在的服务器(S2)发送注册请求注册第一客户端(APP-1)的登录签名(如Sign A)。
在第一客户端(APP-1)获取上述登录账号(ID)后执行登录时，在向第二客户端(APP-2)所在服务器(S2)发送登录验证请求中将携带有与该第一客户端对应的登录签名(如Sign B)，第二客户端(APP-2)所在的服务器(S2)通过对预先注册的登录签名(如Sign A)与从请求验证的第一客户端获取到的登录签名(如Sign B)进行验证，如验证接收到的第一登录签名(如Sign A)与注册的第二登录签名(如Sign B)是否一致，在验证出第一登录签名(如Sign A)与注册的第二登录签名(如Sign B)一致时，则通过第二客户端发送登录验证 成功的响应。
通过本申请提供的实施例，通过对登录签名的验证，实现对第一客户端是否可以使用第二客户端当前登录的账号进行快速登录的快速验证，从而达到节省第一客户端的登录时间，提高登录效率的效果。
作为一种可选的方案，第一获取单元包括：
1)第二接收模块，用于接收运行第一客户端的运行请求；
2)显示模块，用于响应运行请求在终端显示第一客户端的登录界面；
3)通信模块，用于在第一客户端与第二客户端之间进行通信，以获取第二客户端当前登录的登录账号，并在第一客户端的登录界面显示登录账号。
具体结合以下示例进行说明，接收运行第一客户端的运行请求，在确认终端已安装第一客户端及与第一客户端具有关联关系的第二客户端后，打开并显示第一客户端的登录界面，并使用android binder通信机制从第二客户端获取第二客户端当前登录的登录账号。在第一客户端在通信过程中获取到上述登录账号后，在第一客户端的登录界面上显示上述登录账号，例如，如图5(a)所示，“使用第二客户端登录的账号125253登录”的按键。
通过本申请提供的实施例，通过在第一客户端与第二客户端之间进行通信，以获取第二客户端当前登录的登录账号，从而实现使第一客户端使用该登录账号达到快速登录的效果，达到节省登录客户端的登录时间，进而实现提高登录效率的效果。以克服现有技术需要通过多次交互等复杂的操作所导致的登录效率较低的问题。
实施例4
根据本发明实施例，还提供了一种用于实施上述登录客户端的方法的登录客户端的装置，如图11所示，该装置包括：
1)第一接收单元1102，用于接收运行有第一客户端的终端对登录账号的登录验证请求，其中，登录账号为在终端运行的第二客户端当前登录的登录账号，第二客户端与第一客户端具有关联关系；
2)验证单元1104，用于响应登录验证请求验证第一客户端是否使用登录账 号执行登录；
3)发送单元1106，用于在验证成功时，通过第二客户端发送登录验证成功的响应，以使第一客户端使用登录账号执行登录。
可选地，在本实施例中，上述登录客户端的装置可以但不限于应用于具有关联关系的客户端(例如即时通讯应用客户端，及与该即时通讯应用客户端对应的社区空间共享应用客户端)的登录过程中。也就是说，在第一客户端利用登录账号进行快速登录的过程中，由与第一客户端具有关联关系的第二客户端对登录账号的登录验证请求进行快速验证，验证第一客户端是否使用登录账号执行登录，从而保证第一客户端可以实现快速登录，简化登录客户端的登录操作，减少不必要的交互次数，达到节省登录客户端的登录时间，进而实现提高登录效率的效果。
可选地，在本实施例中，可以但不限于在第一客户端获取到对登录账号的选中指令后，将上述登录验证请求发送给第二客户端。
也就是说，如图6所示，终端302运行的第一客户端在登录时获取具有关联关系的第二客户端当前登录的登录账号后，并通过对该登录账号执行选中操作生成选中指令，响应该选中指令，终端302将向第二客户端对应服务器602发送登录验证请求，以使服务器602利用预先注册的信息验证终端302上的第一客户端是否可以使用上述登录账号执行快速登录。第一客户端在通过第二客户端收到服务器602发送的登录验证成功的响应后，将获取用于请求使用登录账号登录第一客户端的登录请求，并将该登录请求发送给第一客户端对应的服务器306，以获取登录后所要显示的资源信息。
可选地，在本实施例中，在上述验证过程中，第二客户端对应的服务器可以但不限于对登录签名进行验证。例如，在第一客户端获取在终端运行的第二客户端当前登录的登录账号之前，向第二客户端对应的服务器发送注册请求，其中，注册请求用于请求在服务器注册第一客户端的登录签名(如Sign A)。在第一客户端获取上述登录账号后执行登录时，在向第二客户端所在服务器发送登录验证请求中将携带有与该第一客户端对应的登录签名(如Sign B)，第二客户端对应的服务器通过对预先注册的登录签名Sign A与从请求验证的第一客户端获取到的Sign B进行验证，从而实现对第一客户端是否可以使用第二客户端 当前登录的账号进行快速登录的快速验证，进而达到节省第一客户端的登录时间，提高登录效率的效果。
具体结合以下示例进行说明，如图7所示步骤S702-S716，第一客户端702从第二客户端706获取当前登录的登录账号，并对该登录账号执行操作(如选中操作)，响应由该操作生成的操作指令通过第二客户端706向第二客户端所在服务器708发送登录验证请求，在第二客户端所在服务器708中验证是否允许第一客户端使用该登录账号执行登录。在验证成功的情况下，第二客户端所在服务器708通过第二客户端向第一客户端发送登录验证成功的响应(如该响应中携带有登录票据)，第一客户端702根据该响应获取用于登录的登录请求，并将该登录请求发送给第一客户端所在服务器704，在显示登录第一客户端702后，从第一客户端对应的服务器704获取返回的资源信息。
通过本申请提供的实施例，通过对获取到的第二客户端当前登录账号进行验证，从而保证对第一客户端使用该登录账号进行登录的快速验证，以简化登录客户端的登录操作，减少不必要的交互次数，达到节省登录客户端的登录时间，进而实现提高登录效率的效果。进一步，还可以保证第一客户端使用上述登录账号进行登录的安全性。
作为一种可选的方案，登录验证请求中至少携带有与第一客户端对应的第一登录签名，上述装置还包括：
1)第二接收单元，用于在接收运行有第一客户端的终端对登录账号的登录验证请求之前，接收通过第二客户端发送的注册请求，其中，注册请求用于请求注册第一客户端的第二登录签名；
2)建立单元，用于建立第一客户端与第二客户端之间的关联关系。
可选地，在本实施例中，上述第一客户端与第二客户端之间的关联关系可以为预设的关联关系，例如，即时通讯应用客户端，及与该即时通讯应用客户端对应的社区空间共享应用客户端。
此外，在本实施例中，也可以通过注册登录签名的方式，建立第一客户端与第二客户端之间的关联关系。也就是说，在第一客户端登录之前，在第二客户端所在服务器中预先注册该第一客户端的登录签名，以实现在第一客户端与 第二客户端之间建立关联关系。
通过本申请提供的实施例，通过在第二客户端所在服务器注册第一客户端的第二登录签名，以实现利用该第二登录签名与从请求登录的第一客户端获取的第一登录签名进行验证，从而实现快速验证第一客户端是否可以利用上述登录账号执行快速的效果。
作为一种可选的方案，
1)验证单元1104包括：(1)验证模块，用于验证第一登录签名与注册的第二登录签名是否一致；
2)发送单元1106包括：(1)发送模块，用于在第一登录签名与注册的第二登录签名一致时，通过第二客户端发送登录验证成功的响应，其中，响应中携带有使第一客户端执行登录的登录票据。
具体结合以下示例进行说明，在第一客户端(APP-1)获取在终端运行的第二客户端(APP-2)当前登录的登录账号(ID)之前，向第二客户端(APP-2)所在的服务器(S2)发送注册请求注册第一客户端(APP-1)的登录签名(如Sign A)。
在第一客户端(APP-1)获取上述登录账号(ID)后执行登录时，在向第二客户端(APP-2)所在服务器(S2)发送登录验证请求中将携带有与该第一客户端对应的登录签名(如Sign B)，第二客户端(APP-2)所在的服务器(S2)通过对预先注册的登录签名(如Sign A)与从请求验证的第一客户端获取到的登录签名(如Sign B)进行验证，如验证接收到的第一登录签名(如Sign A)与注册的第二登录签名(如Sign B)是否一致，在验证出第一登录签名(如Sign A)与注册的第二登录签名(如Sign B)一致时，则通过第二客户端发送登录验证成功的响应。
通过本申请提供的实施例，通过对登录签名的验证，实现对第一客户端是否可以使用第二客户端当前登录的账号进行快速登录的快速验证，从而达到节省第一客户端的登录时间，提高登录效率的效果。
实施例5
根据本发明实施例，还提供了一种用于实施上述登录客户端的方法的登录 客户端的终端，如图12所示，该终端包括：
1)通讯接口1202，设置为在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号，其中，第二客户端与第一客户端具有关联关系；还设置为在第一客户端的登录界面上，获取对登录账号执行操作后所生成的登录请求，其中，所述对登录账号执行的操作在第一客户端的登录界面上进行，登录请求用于请求使用登录账号登录第一客户端；
2)处理器1204，与通讯接口1202连接，设置为在第一客户端的登录界面上，获取对登录账号执行操作后所生成的登录请求，其中，登录请求用于请求使用登录账号登录第一客户端；
3)存储器1206，与通讯接口1202及处理器1204连接，设置为存储第二客户端当前登录的登录账号，及第二客户端与第一客户端的关联关系。
可选地，本实施例中的具体示例可以参考上述实施例1和实施例2中所描述的示例，本实施例在此不再赘述。
实施例6
根据本发明实施例，还提供了一种用于实施上述登录客户端的方法的登录客户端的服务器，如图13所示，该服务器包括：
1)通讯接口1302，设置为接收运行有第一客户端的终端对登录账号的登录验证请求，其中，登录账号为在终端运行的第二客户端当前登录的登录账号，第二客户端与第一客户端具有关联关系；还设置为在验证成功时，通过第二客户端发送登录验证成功的响应，以使第一客户端使用登录账号执行登录；
2)处理器1304，与通讯接口1302连接，设置为响应登录验证请求验证第一客户端是否使用登录账号执行登录；
3)存储器1306，与通讯接口1302及处理器1304连接，设置为存储用于登录验证的验证信息。
可选地，在本实施例中，上述验证信息可以包括但不限于第一客户端的登录签名。例如，第一客户端发送的登录验证请求中携带的与第一客户端对应的第一登录签名及通过第二客户端请求注册的第一客户端的第二登录签名。
可选地，本实施例中的具体示例可以参考上述实施例1和实施例2中所描述的示例，本实施例在此不再赘述。
实施例7
本发明的实施例还提供了一种存储介质。
可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：
S1，在终端运行的第一客户端的登录界面上，获取在终端运行的第二客户端当前登录的登录账号，其中，第二客户端与第一客户端具有关联关系；
S2，在第一客户端的登录界面上，获取对登录账号执行操作后所生成的登录请求，其中，登录请求用于请求使用登录账号登录第一客户端；
S3，响应登录请求使用登录账号登录第一客户端。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，接收运行有第一客户端的终端对登录账号的登录验证请求，其中，登录账号为在终端运行的第二客户端当前登录的登录账号，第二客户端与第一客户端具有关联关系；
S2，响应登录验证请求验证第一客户端是否使用登录账号执行登录；
S3，在验证成功时，通过第二客户端发送登录验证成功的响应，以使第一客户端使用登录账号执行登录。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，本实施例中的具体示例可以参考上述实施例1至实施例4中所描述的示例，本实施例在此不再赘述。
实施例8
本申请实施例还提供了一种用于实施上述登录客户端的方法的终端，如图14所示，为了便于说明，仅示出了与本申请实施例相关的部分，具体技术细节未揭示的，请参照本申请实施例方法部分。该终端可以为包括手机、平板电脑、 PDA(Personal Digital Assistant，个人数字助理)、POS(Point of Sales，销售终端)、车载电脑等任意终端设备，以终端为手机为例：
图14示出的是与本申请实施例提供的终端相关的手机的部分结构的框图。参考图14，手机包括：存储器1410、输入单元1420、显示单元1430、处理器1440等部件。本领域技术人员可以理解，图14中示出的手机结构并不构成对手机的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
下面结合图14对手机的各个构成部件进行具体的介绍：
存储器1410可用于存储软件程序以及模块，处理器1440通过运行存储在存储器1410的软件程序以及模块，从而执行手机的各种功能应用以及数据处理。例如，存储器1410可用于存储用于执行上述方法实施例的指令代码，账号信息及服务器返回的资源信息等。可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器1410可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
输入单元1420可用于接收输入的数字或字符信息，以及产生与手机的用户设置以及功能控制有关的键信号输入。例如，可以通过输入单元1420对客户端的登陆界面进行操作，如选择显示在登陆界面上的登陆账号。具体地，输入单元1420可包括触控面板1421以及其他输入设备1422。触控面板1421，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板1421上或在触控面板1421附近的操作)，并根据预先设定的程式驱动相应的连接装置。可选的，触控面板1421可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器1440，并能接收处理器1440发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板1421。除了触控面板1421，输入单元1420还可以包括其他输入设备1422。具体地，其他输入设备1422可以包括但不限于 物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆等中的一种或多种。
显示单元1430可用于显示由用户输入的信息或提供给用户的信息以及手机的各种菜单。例如，显示单元1430可用于显示客户端的登陆界面及服务器返回的资源信息。显示单元1430可包括显示面板1431，可选的，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板1431。进一步的，触控面板1421可覆盖显示面板1431，当触控面板1421检测到在其上或附近的触摸操作后，传送给处理器1440以确定触摸事件的类型，随后处理器1440根据触摸事件的类型在显示面板1431上提供相应的视觉输出。虽然在图14中，触控面板1421与显示面板1431是作为两个独立的部件来实现手机的输入和输入功能，但是在某些实施例中，可以将触控面板1421与显示面板1431集成而实现手机的输入和输出功能。
处理器1440是手机的控制中心，利用各种接口和线路连接整个手机的各个部分，通过运行或执行存储在存储器1410内的软件程序和/或模块，以及调用存储在存储器1410内的数据，执行手机的各种功能和处理数据，从而对手机进行整体监控。可选的，处理器1440可包括一个或多个处理单元；优选的，处理器1440可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器1440中。
在本申请实施例中，该终端所包括的处理器1440还具有控制执行以上由终端执行的方法流程。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
上述实施例中的集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在上述计算机可读取的存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在存储介质中，包括若干指令用以使得一台或多台计算机设备(可为个人计算机、服务器或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。
在本发明的上述实施例中，对各个实施例的描述都各有侧重，某个实施例 中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的客户端，可通过其它的方式实现。其中，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元或模块的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
以上所述仅是本发明的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本发明原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本发明的保护范围。

Claims (18)

  1. 一种登录客户端的方法，其特征在于，包括：
    在终端运行的第一客户端的登录界面上，获取在所述终端运行的第二客户端当前登录的登录账号，其中，所述第二客户端与所述第一客户端具有关联关系；
    在所述第一客户端的登录界面上，对获取到的登录账号执行操作，获取对所述登录账号执行操作后所生成的登录请求，其中，所述登录请求用于请求使用所述登录账号登录所述第一客户端；以及
    响应所述登录请求使用所述登录账号登录所述第一客户端。
  2. 根据权利要求1所述的方法，其特征在于，所述在所述第一客户端的登录界面上，对获取到的登录账号执行操作，获取对所述第二客户端的所述登录账号执行操作后所生成的登录请求包括：
    接收选中指令，其中，所述选中指令用于选择显示在所述登录界面上的所述登录账号；
    响应所述选中指令向所述第二客户端发送登录验证请求，其中，所述登录验证请求中至少携带有与所述第一客户端对应的第一登录签名；
    获取所述第二客户端发送的登录验证成功的响应，其中，所述响应中携带有用于登录所述第一客户端的登录票据；以及
    获取使用所述登录票据生成的所述登录请求。
  3. 根据权利要求2所述的方法，其特征在于，在所述获取在所述终端运行的第二客户端当前登录的登录账号之前，还包括：
    向所述第二客户端对应的服务器发送注册请求，其中，所述注册请求用于请求在所述服务器注册所述第一客户端的第二登录签名，第二客户端对应的服务器为第二客户端提供服务；以及
    建立所述第一客户端与所述第二客户端之间的所述关联关系。
  4. 根据权利要求3所述的方法，其特征在于，在所述响应所述选中指令向所述第二客户端发送登录验证请求之后，且在所述获取所述第二客户端发送 的登录验证成功的响应之前，还包括：
    所述服务器通过所述第二客户端接收所述第一登录签名；
    所述服务器验证接收到的所述第一登录签名与注册的所述第二登录签名是否一致；以及
    在验证出所述第一登录签名与注册的所述第二登录签名一致时，所述服务器通过所述第二客户端发送所述登录验证成功的响应。
  5. 根据权利要求2所述的方法，其特征在于，所述响应所述选中指令向所述第二客户端发送登录验证请求包括：
    响应所述选中指令在所述第一客户端的登录界面上创建所述第二客户端的透明界面；以及
    在所述第二客户端的所述透明界面上向所述第二客户端发送所述登录验证请求。
  6. 根据权利要求1所述的方法，其特征在于，所述在终端运行的第一客户端的登录界面上，获取在所述终端运行的第二客户端当前登录的登录账号包括：
    接收运行所述第一客户端的运行请求；
    响应所述运行请求在所述终端显示所述第一客户端的登录界面；以及
    在所述第一客户端与所述第二客户端之间进行通信，以获取所述第二客户端当前登录的所述登录账号，并在所述第一客户端的登录界面显示所述登录账号。
  7. 一种登录客户端的方法，其特征在于，包括：
    接收运行有第一客户端的终端对登录账号的登录验证请求，其中，所述登录账号为在所述终端运行的第二客户端当前登录的登录账号，所述第二客户端与所述第一客户端具有关联关系；
    响应所述登录验证请求验证所述第一客户端是否使用所述登录账号执行登录；以及
    在验证成功时，通过所述第二客户端发送登录验证成功的响应，以使所述第一客户端使用所述登录账号执行登录。
  8. 根据权利要求7所述的方法，其特征在于，所述登录验证请求中至少携带有与所述第一客户端对应的第一登录签名，其中，在所述接收运行有第一客户端的终端对登录账号的登录验证请求之前，还包括：
    接收通过所述第二客户端发送的注册请求，其中，所述注册请求用于请求注册所述第一客户端的第二登录签名；以及
    建立所述第一客户端与所述第二客户端之间的所述关联关系。
  9. 根据权利要求8所述的方法，其特征在于，
    所述响应所述登录验证请求验证所述第一客户端是否使用所述登录账号执行登录包括：验证所述第一登录签名与注册的所述第二登录签名是否一致；
    所述在验证成功时，通过所述第二客户端发送登录验证成功的响应包括：在所述第一登录签名与注册的所述第二登录签名一致时，通过所述第二客户端发送所述登录验证成功的响应，其中，所述响应中携带有使所述第一客户端执行登录的登录票据。
  10. 一种登录客户端的装置，其特征在于，包括：
    第一获取单元，用于在终端运行的第一客户端的登录界面上，获取在所述终端运行的第二客户端当前登录的登录账号，其中，所述第二客户端与所述第一客户端具有关联关系；
    第二获取单元，用于在所述第一客户端的登录界面上，获取对所述登录账号执行操作后所生成的登录请求，其中，所述对登录账号执行的操作在第一客户端的登录界面上进行，所述登录请求用于请求使用所述登录账号登录所述第一客户端；以及
    登录单元，用于响应所述登录请求使用所述登录账号登录所述第一客户端。
  11. 根据权利要求10所述的装置，其特征在于，所述第二获取单元包括：
    第一接收模块，用于接收选中指令，其中，所述选中指令用于选择显示在所述登录界面上的所述登录账号；
    发送模块，用于响应所述选中指令向所述第二客户端发送登录验证请求，其中，所述登录验证请求中至少携带有与所述第一客户端对应的第一 登录签名；
    第一获取模块，用于获取所述第二客户端发送的登录验证成功的响应，其中，所述响应中携带有用于登录所述第一客户端的登录票据；以及
    第二获取模块，用于获取使用所述登录票据生成的所述登录请求。
  12. 根据权利要求11所述的装置，其特征在于，还包括：
    发送单元，用于在获取在所述终端运行的第二客户端当前登录的登录账号之前，向所述第二客户端对应的服务器发送注册请求，其中，所述注册请求用于请求在所述服务器注册所述第一客户端的第二登录签名，第二客户端对应的服务器为第二客户端提供服务；以及
    建立单元，用于建立所述第一客户端与所述第二客户端之间的所述关联关系。
  13. 根据权利要求11所述的装置，其特征在于，所述发送模块包括：
    创建子模块，用于响应所述选中指令在所述第一客户端的登录界面上创建所述第二客户端的透明界面；以及
    发送子模块，用于在所述第二客户端的所述透明界面上向所述第二客户端发送所述登录验证请求。
  14. 根据权利要求10所述的装置，其特征在于，所述第一获取单元包括：
    第二接收模块，用于接收运行所述第一客户端的运行请求；
    显示模块，用于响应所述运行请求在所述终端显示所述第一客户端的登录界面；以及
    通信模块，用于在所述第一客户端与所述第二客户端之间进行通信，以获取所述第二客户端当前登录的所述登录账号，并在所述第一客户端的登录界面显示所述登录账号。
  15. 一种登录客户端的装置，其特征在于，包括：
    第一接收单元，用于接收运行有第一客户端的终端对登录账号的登录验证请求，其中，所述登录账号为在所述终端运行的第二客户端当前登录的登录账号，所述第二客户端与所述第一客户端具有关联关系；
    验证单元，用于响应所述登录验证请求验证所述第一客户端是否使用 所述登录账号执行登录；以及
    发送单元，用于在验证成功时，通过所述第二客户端发送登录验证成功的响应，以使所述第一客户端使用所述登录账号执行登录。
  16. 根据权利要求15所述的装置，其特征在于，所述登录验证请求中至少携带有与所述第一客户端对应的第一登录签名，所述装置还包括：
    第二接收单元，用于在接收运行有第一客户端的终端对登录账号的登录验证请求之前，接收通过所述第二客户端发送的注册请求，其中，所述注册请求用于请求注册所述第一客户端的第二登录签名；以及
    建立单元，用于建立所述第一客户端与所述第二客户端之间的所述关联关系。
  17. 根据权利要求16所述的装置，其特征在于，
    所述验证单元包括：验证模块，用于验证所述第一登录签名与注册的所述第二登录签名是否一致；
    所述发送单元包括：发送模块，用于在所述第一登录签名与注册的所述第二登录签名一致时，通过所述第二客户端发送所述登录验证成功的响应，其中，所述响应中携带有使所述第一客户端执行登录的登录票据。
  18. 一种非易失性存储介质，用于存储一个或多个计算机程序，其中，所述计算机程序包括具有一个或多个处理器可运行的指令，所述指令被计算机执行时，使得所述计算机执行以下操作：
    在终端运行的第一客户端的登录界面上，获取在所述终端运行的第二客户端当前登录的登录账号，其中，所述第二客户端与所述第一客户端具有关联关系；
    在所述第一客户端的登录界面上，对获取到的登录账号执行操作，获取对所述登录账号执行操作后所生成的登录请求，其中，所述登录请求用于请求使用所述登录账号登录所述第一客户端；以及
    响应所述登录请求使用所述登录账号登录所述第一客户端。
PCT/CN2017/075757 2016-03-11 2017-03-06 登录客户端的方法，装置及存储介质 WO2017152820A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/955,488 US10776478B2 (en) 2016-03-11 2018-04-17 Client login method and apparatus and storage medium
US16/938,503 US11372963B2 (en) 2016-03-11 2020-07-24 Client login method and apparatus and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610140719.4 2016-03-11
CN201610140719.4A CN105827600B (zh) 2016-03-11 2016-03-11 登录客户端的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/955,488 Continuation US10776478B2 (en) 2016-03-11 2018-04-17 Client login method and apparatus and storage medium

Publications (1)

Publication Number Publication Date
WO2017152820A1 true WO2017152820A1 (zh) 2017-09-14

Family

ID=56987646

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/075757 WO2017152820A1 (zh) 2016-03-11 2017-03-06 登录客户端的方法，装置及存储介质

Country Status (3)

Country Link
US (2) US10776478B2 (zh)
CN (1) CN105827600B (zh)
WO (1) WO2017152820A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111666546A (zh) * 2020-06-19 2020-09-15 上海连尚网络科技有限公司 应用的登录方法和装置
CN114640880A (zh) * 2020-11-30 2022-06-17 腾讯科技（深圳）有限公司 账号登录控制方法、装置及介质

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105827600B (zh) 2016-03-11 2020-09-29 腾讯科技（深圳）有限公司 登录客户端的方法及装置
WO2018196153A1 (zh) * 2017-04-25 2018-11-01 华为技术有限公司 一种开放授权方法、装置和终端
CN107959757B (zh) * 2017-12-11 2020-12-15 北京小米移动软件有限公司 用户信息处理方法、装置、app服务器和终端设备
CN109840403B (zh) * 2019-01-14 2020-12-22 腾讯科技（深圳）有限公司 应用登录方法、装置、计算机可读存储介质和计算机设备
US11288347B2 (en) * 2019-03-07 2022-03-29 Paypal, Inc. Login from an alternate electronic device
CN112152902B (zh) * 2019-06-27 2022-07-29 腾讯科技（深圳）有限公司 媒体资源的推送方法及装置
CN111538965B (zh) * 2020-04-15 2021-10-12 支付宝(杭州)信息技术有限公司 一种应用程序的授权登录方法、装置及系统
CN113098839A (zh) * 2021-02-25 2021-07-09 北京大生在线科技有限公司 一种账号登录方法及系统
CN112948804B (zh) * 2021-03-05 2022-11-04 腾讯科技（深圳）有限公司 一种程序控制方法、装置和计算机可读存储介质
CN113225332B (zh) * 2021-04-30 2023-08-18 平安证券股份有限公司 用户登录管理方法、装置、终端设备及存储介质
CN114826610A (zh) * 2022-04-14 2022-07-29 函谷数巢品牌管理(广州)有限公司 基于多媒体进行账号绑定演示的方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102065141A (zh) * 2010-12-27 2011-05-18 广州欢网科技有限责任公司 一种跨应用与浏览器实现单点登录的方法及系统
CN103188237A (zh) * 2011-12-30 2013-07-03 盛大计算机（上海）有限公司 单点登录系统及方法
CN105288998A (zh) * 2015-09-23 2016-02-03 腾讯科技（深圳）有限公司 智能硬件的交互方法及装置
CN105827600A (zh) * 2016-03-11 2016-08-03 腾讯科技（深圳）有限公司 登录客户端的方法及装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7383307B2 (en) * 2004-01-07 2008-06-03 International Business Machines Corporation Instant messaging windowing for topic threads
US8676979B2 (en) * 2010-05-18 2014-03-18 Salesforce.Com, Inc. Methods and systems for efficient API integrated login in a multi-tenant database environment
US8544069B1 (en) * 2011-04-29 2013-09-24 Intuit Inc. Methods systems and articles of manufacture for implementing user access to remote resources
CN102262552B (zh) * 2011-07-06 2015-08-19 惠州Tcl移动通信有限公司 一种应用程序跨设备同步方法及系统
US9277017B2 (en) * 2012-10-30 2016-03-01 Netiq Corporation Techniques for device independent session migration
CN103905497B (zh) * 2012-12-27 2018-04-27 腾讯科技（深圳）有限公司 实现第三方应用业务网站登录的方法、装置及应用平台
US9419963B2 (en) * 2013-07-02 2016-08-16 Open Text S.A. System and method for controlling access
CN103634316A (zh) * 2013-11-26 2014-03-12 乐视网信息技术（北京）股份有限公司 一种账号登录方法及电子设备
CN104753943B (zh) * 2015-03-30 2016-04-20 努比亚技术有限公司 第三方账号的登录控制方法及装置
CN104917778A (zh) * 2015-06-25 2015-09-16 努比亚技术有限公司 应用登录方法和装置
CN105072133B (zh) * 2015-08-28 2018-07-10 北京金山安全软件有限公司 一种应用程序的登录方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102065141A (zh) * 2010-12-27 2011-05-18 广州欢网科技有限责任公司 一种跨应用与浏览器实现单点登录的方法及系统
CN103188237A (zh) * 2011-12-30 2013-07-03 盛大计算机（上海）有限公司 单点登录系统及方法
CN105288998A (zh) * 2015-09-23 2016-02-03 腾讯科技（深圳）有限公司 智能硬件的交互方法及装置
CN105827600A (zh) * 2016-03-11 2016-08-03 腾讯科技（深圳）有限公司 登录客户端的方法及装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111666546A (zh) * 2020-06-19 2020-09-15 上海连尚网络科技有限公司 应用的登录方法和装置
CN111666546B (zh) * 2020-06-19 2023-10-13 上海连尚网络科技有限公司 应用的登录方法和装置
CN114640880A (zh) * 2020-11-30 2022-06-17 腾讯科技（深圳）有限公司 账号登录控制方法、装置及介质
CN114640880B (zh) * 2020-11-30 2023-06-30 腾讯科技（深圳）有限公司 账号登录控制方法、装置及介质

Also Published As

Publication number Publication date
US20180232515A1 (en) 2018-08-16
CN105827600A (zh) 2016-08-03
US20200356655A1 (en) 2020-11-12
CN105827600B (zh) 2020-09-29
US11372963B2 (en) 2022-06-28
US10776478B2 (en) 2020-09-15

Similar Documents

Publication Publication Date Title
WO2017152820A1 (zh) 登录客户端的方法，装置及存储介质
US10116643B2 (en) Virtualized data storage and management of policy and credential data sources
US10091197B2 (en) Configuring, controlling and monitoring computers using mobile devices
CN107113326B (zh) 用于基于规则的设备注册的方法、系统和介质
WO2018001293A1 (zh) 一种WiFi密码共享方法及移动终端
CN107111696B (zh) 多租户计算系统以及在其中实现的方法
JP6052912B2 (ja) ２次承認者による認証
WO2017092553A1 (zh) 用户界面切换方法和终端
EP3065074A1 (en) Fingerprint authentication method and device, intelligent terminal, and computer storage medium
JP2018533141A (ja) エンドユーザによって起動されるアクセスサーバ真正性チェック
US11855982B2 (en) Caller and recipient alternate channel identity confirmation
WO2014075566A1 (zh) 敏感操作验证方法、终端设备、服务器和验证系统
US20110219429A1 (en) Online service providing system, method, server and mobile device thereof, and computer program product
WO2018098941A1 (zh) 一种通信标识绑定的处理方法及终端
WO2013143343A1 (zh) 账号登录方法、装置和系统以及网络服务器
US20160262196A1 (en) Mobile Terminal Control Method, Apparatus And System
WO2018108123A1 (zh) 身份验证方法、装置与系统
US11233897B1 (en) Secure call center communications
JP2023516973A (ja) 抽出不可能な非対称鍵を介したブラウザログインセッション
CN108475304A (zh) 一种关联应用程序和生物特征的方法、装置以及移动终端
WO2016131181A1 (zh) 一种指纹事件的处理方法、装置及终端
JP6531468B2 (ja) 画面表示方法、画面表示プログラム、及び通信装置
US20230345240A1 (en) Contextual authentication for secure remote sessions
JP2017219918A (ja) サービス提供システム、サービス提供方法、および、プログラム
WO2014026322A1 (zh) 共享图形信息的方法和装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17762506

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17762506

Country of ref document: EP

Kind code of ref document: A1