SYSTEMS AND METHODS FOR LOGIN AND AUTHORIZATION

• US 20180109509A1
• Filed: 12/18/2017
• Published: 04/19/2018
• Est. Priority Date: 06/25/2013
• Status: Active Grant

• Current Assignee: Tencent Technology Shenzhen Company Limited (Tencent Holdings Limited)
• Original Assignee: Tencent Technology Shenzhen Company Limited (Tencent Holdings Limited)
• Inventors: REN, MIN
• Granted Patent: US 10,462,118 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/77 Graphical identity

Abstract

Systems and methods are provided for login and authorization. For example, a third-party terminal receives a login request from a user and sends an authorization request from the third-party terminal to a network server; the network server generates first two-dimensional-barcode information and sends the first two-dimensional-barcode information to the third-party terminal; the third-party terminal displays a first two-dimensional-barcode image; a mobile terminal extracts the first two-dimensional-barcode information from the first two-dimensional-barcode image and sends first user account information and the first two-dimensional-barcode information to the network server; the network server validates the first user account information and the first two-dimensional-barcode information based on at least information associated with stored second user account information and second two-dimensional-barcode information generated by the network server.

Claims

1. A method for login and authorization, the method comprising:

receiving, at a third-party terminal, a login request from a user;

sending an authorization request from the third-party terminal to a network server;

generating, by the network server, first two-dimensional-barcode information;

sending the first two-dimensional-barcode information to the third-party terminal;

displaying, at the third-party terminal, a first two-dimensional-barcode image;

extracting, by a mobile terminal, the first two-dimensional-barcode information from the first two-dimensional-barcode image;

sending first user account information and the first two-dimensional-barcode information to the network server;

validating, by the network server, the first user account information and the first two-dimensional-barcode information based on at least information associated with stored second user account information and second two-dimensional-barcode information generated by the network server;

in response to the first user account information and the first two-dimensional-barcode information being validated, sending, by the network server, an authorization and a predetermined user identifier to a third-party server;

setting, by the third-party server, a user account associated with the user identifier to a logged-in state;

acquiring, by the third-party terminal, information related to the logged-in state from the third-party server; and

setting an interface of a first third-party application to a user-logged-in state.

2. The method of claim 1, wherein:

the authorization request includes one or more authorization parameters;

the method further comprises;

validating, by the network server, the authorization parameters in the authorization request.

3. The method of claim 2, wherein the authorization parameters include at least one of:

an application identifier, authorization scope information, an application callback address, anti-disguise information and an application key.

4. The method of claim 2, wherein the first two-dimensional-barcode information includes the authorization parameters.

5. The method of claim 1, further comprising:

sending, by the third-party terminal, at a predetermined time an authorization inquiry to the third-party server.

6. The method of claim 1, wherein the in response to the first user account information and the first two-dimensional-barcode information being validated, sending, by the network server, an authorization and a predetermined user identifier to a third-party server includes:

in response to the first user account information and the first two-dimensional-barcode information being validated, sending, by the network server, validation-success information to the mobile terminal;

displaying, by the mobile terminal, information related to authorization confirmation;

receiving, by the mobile terminal, an authorization confirmation from the user;

sending the authorization confirmation to the network server; and

sending, by the network server, the authorization and the predetermined user identifier to the third-party server.

7. The method of claim 6, wherein the information related to authorization confirmation includes a name and an authorization scope of the first third-party application.

8. The method of claim 1, wherein:

the user identifier corresponds to the user account; and

the user account corresponds to different user identifiers when the user account logs into different third-party applications.

9. The method of claim 1, further comprising:

validating, by the third-party server, the authorization.

10. The method of claim 9, wherein the authorization includes an authorization-validity character string and anti-disguise information.

11-22. -22. (canceled)

23. A third-party terminal comprising:

a login-request-receiving unit configured to receive a login request from a user;

a login-request-sending unit configured to send an authorization request to a network server;

a two-dimensional-barcode-information-receiving unit configured to receive two-dimensional-barcode information from the network server;

a display unit configured to display a two-dimensional-barcode image;

a login-information-receiving unit configured to receive information related to a logged-in state of a user account from a third-party server;

a control unit configured to set an interface of a third-party application to a user-logged-in state based on at least information associated with the information related to the logged-in state of the user account;

wherein the third-party server sets the user account to the logged-in state and sends the information related to the logged-in state of the user account after the network server validates user account information sent from a mobile terminal and the two-dimensional-barcode information extracted from the first two-dimensional-barcode image.

24. The third-party terminal of claim 23, wherein the authorization request includes one or more authorization parameters to be validated by the network server.

25. The third-party terminal of claim 24, wherein the authorization parameters include at least one of:

an application identifier, authorization scope information, an application callback address, anti-disguise information and an application key.

26. The third-party terminal of claim 24, wherein the two-dimensional-barcode information includes the authorization parameters.

27. The third-party terminal of claim 23, further comprising:

a polling unit configured to send at a predetermined time an authorization inquiry to the third-party server.

28. The third-party terminal of claim 23, further comprising:

one or more data processors; and

a computer-readable storage medium;

wherein one or more of the login-request-receiving unit, the login-request-sending unit, the two-dimensional-barcode-information-receiving unit, the display unit, the login-information-receiving unit, and the control unit are stored in the storage medium and configured to be executed by the one or more data processors.

29-36. -36. (canceled)

37. A non-transitory computer readable storage medium comprising programming instructions for login, the programming instructions configured to cause one or more data processors to execute operations comprising:

receiving a login request from a user;

sending an authorization request to a network server;

receiving two-dimensional-barcode information from the network server;

displaying a two-dimensional-barcode image;

acquiring information related to a logged-in state of a user account from a third-party server; and

setting an interface of a third-party application to a user-logged-in state;

wherein the third-party server sets the user account to the logged-in state and sends the information related to the logged-in state of the user account after the network server validates user account information sent from a mobile terminal and the two-dimensional-barcode information extracted from the first two-dimensional-barcode image.

38. A non-transitory computer readable storage medium comprising programming instructions for authorization, the programming instructions configured to cause one or more data processors to execute operations comprising:

receiving an authorization request from a third-party terminal;

generating first two-dimensional-barcode information;

sending the first two-dimensional-barcode information to the third-party terminal so that the third-party terminal displays a first two-dimensional-barcode image;

validating user account information and the first two-dimensional-barcode information sent from a mobile terminal based on at least information associated with stored user account information and second two-dimensional-barcode information, wherein the first two-dimensional-barcode information sent from the mobile terminal is extracted by the mobile terminal from the first two-dimensional-barcode image displayed on the third-party terminal; and

in response to the user account information and the first two-dimensional-barcode information being validated, sending an authorization and a predetermined user identifier to the third-party server.