# US 11,451,540 B2 · Method of authentication > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,451,540 B2 - Document ID: US11451540B2 - Status: Granted - Kind: B2 - Application number: 15/309,854 - Filed: 2015-05-08 - Published: 2017-06-01 - Granted: 2022-09-20 - Earliest claimed: 2014-05-09 - Assignees: Smartglyph Limited - Applicants: Smartglyph Limited - Inventors: Martin Hooley - Web page: https://patentgrep.com/patent/US11451540B2 ## CPC - H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint} - G06K 7/1095: {the scanner comprising adaptations for scanning a record carrier that is displayed on a display-screen or the like} - G06K 19/06037: {multi-dimensional coding} - G06K 19/06093: {the marking being constructed out of a plurality of similar markings, e.g. a plurality of barcodes randomly oriented on an object} - G06Q 20/085: {involving remote charge determination or related payment systems} - G06Q 20/12: specially adapted for electronic shopping systems - G06Q 20/3276: {using a pictured code, e.g. barcode or QR-code, being read by the M-device} - G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists - G06Q 30/0635: {replenishment orders; recurring orders} - H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)} - 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)} - G06K 2007/10524: {Hand-held scanners} - H04L 2463/121: Timestamp - H04W 12/77: Graphical identity - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06K: GRAPHICAL DATA READING (image or video recognition or understanding G06V); PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A method, of authenticating a user with a service and a server having means to enable a user to be authenticated with a service. The method having the steps of, the user requesting a session with the service on a first device. The server requesting a unique code from a host server, the host server generating the unique code, associating it with a session-identifier. The session-identifier containing information relating to the code request. The host server then sending the unique code, which does not contain the session-identifier, to the service. The server then optically presents the unique code to the user on a display of the first device. The code is then acquired by a verification application running on a second device. Optionally the first device and the second device may be the same device. The second device is previously registered with the host server. The verification application sends the unique code, and device-identifying information of the second device, to the host server. The host server, on receiving the unique code and device-identifying information, uses the unique code to retrieve the session-identifier, and uses the device-identifying information to retrieve associated user-identifying information. This user-identifying information is stored on the host server. The host server then sends the user-identifying information to the service. ## Claims ### Claim 1 A method of authenticating a user with a service, having the steps of: receiving with a host server a request for a unique code from the service over a first secure communication channel in response to the user requesting a session with the service on a first device, wherein the first device has previously been registered with the host server, and wherein the request for a unique code contains no registration credentials; generating with the host server the unique code and associating the unique code with a session-identifier, the session-identifier containing information relating to the code request; sending the unique code without the session-identifier from the host server to the service over the first secure communication channel, such that the unique code is presented to the first device by the service; the host server receiving from a verification application running on the first device the unique code and device-identifying information of the first device acquired by the verification application over a second secure communication channel; the host server using: the received unique code to retrieve the session-identifier, and the device-identifying information to retrieve associated user-identifying information stored on the host server; when the user is previously known to the service based on the user-identifying information received by the service from the host server, the host server sending the retrieved user-identifying information to the service over the first secure communication channel, such that the user is authenticated and granted the request for a session on the first device by the server and the first device receives data from the service as part of the session. ### Claim 2 (depends on 1) The method of claim 1 wherein the session-identifier contains information identifying the service which requested the unique code. ### Claim 3 (depends on 1) The method of claim 1 wherein the session-identifier additionally contains information identifying the request for a session with the service. ### Claim 4 (depends on 1) The method of claim 1 wherein the user-identifying information associated with the device includes at least one of, a username, a password, a date of birth, an address, a telephone number, a host server specific username, a host server specific password, a service specific username, a service specific password. ### Claim 5 (depends on 1) The method of claim 1 wherein when the user is not previously known to the service: the host server receives from the service a request for additional user-identifying information; and the host server sends the requested additional user identifying information to the service. ### Claim 6 (depends on 5) The method of claim 5 wherein the service uses the additional user-identifying information to register the user with the service. ### Claim 7 (depends on 5) The method of claim 5 wherein the additional user-identifying information is selected by the user. ### Claim 8 (depends on 1) The method of claim 1 wherein the unique code is a unique locator code for use in a look-up table of the host server. ### Claim 9 (depends on 1) The method of claim 1 wherein the device-identifying information contains a unique device-identifying code in a same format to the unique code. ### Claim 10 (depends on 1) The method of claim 1 wherein the device-identifying information contains a MAC address or similar hardware identifying information of the first device. ### Claim 11 (depends on 1) The method of claim 1 wherein the user requests a session with the service by navigating to a webpage of the service on the first device. ### Claim 12 (depends on 1) The method of claim 1 wherein the first device is known to the host server in that a MAC address or similar device-identifying information is stored on the host server, the device-identifying information being associated with user-identifying information. ### Claim 13 (depends on 1) The method of claim 1 wherein the session-identifier remains local to the host server's network at all times. ### Claim 14 (depends on 1) The method of claim 1 wherein the unique code is presented to the user on a screen of the device. ### Claim 15 (depends on 1) The method of claim 1 wherein acquisition of the unique code is initiated through the user selecting the code on the screen of the device. ### Claim 16 (depends on 1) The method of claim 1, wherein the method is used for authenticating a user prior to using a method of authorizing a transaction. ### Claim 17 (depends on 16) The method of claim 16 wherein the method of authorizing the transaction has the steps of: the host server opening a communications channel with a payment merchant and receiving from the payment merchant details of the user's transaction received by the payment merchant from the service; the host server opening a communications channel with the first device, and sending the details of the user's transaction to the first device; the host server receiving an authorization from the first device when the user verifies that the details of the transaction are accurate; the host server sending the authorization to the payment merchant, such that the payment merchant authorizes the transaction. ### Claim 18 (depends on 1) The method of claim 1 wherein the unique code is formed of an array of equal-area elements, each element being the smallest representation of a data value, wherein each element is one of the following types of element: a first type wherein the entire area of the element is a single colour; and a second type wherein the area is divided into two colours, each colour filling 50% of the element, wherein the array is a plurality of the second type of element. ### Claim 19 (depends on 18) The method of claim 18, wherein: at least one of the plurality of the second type of element comprises a diagonal line; or the at least one of the plurality of the second type of element comprises a line running from one side to an opposing side.