IP Library Granted Patent US 8,850,542
Granted Patent B2
US 8,850,542 · App. 13/570,855 · Granted Sep 30, 2014

Code-based authorization of mobile device

Inventor: Jeremy Auger (Kitchener, CA)
Assignee: Desire2learn Incorporated
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,850,542
App. No.
13/570,855
Granted
Sep 30, 2014
Kind
B2
Abstract

A system and method for authenticating mobile communications devices. The method comprises: generating a code corresponding to a user configured to be rendered on a rendering device to produce a rendered code, the rendered code being readable by a mobile communications device having a code reading device, the rendered code comprising a secret token; storing the secret token along with information identifying the user on a first storage device; providing the code to the user; receiving, at the authentication server, a setup message from the mobile device, the message includes a device identifier and the secret token; comparing the received secret token and the secret token stored on the first storage device; if the received secret token matches the secret token stored on the first storage device, storing, on a second storage device, information identifying the user and a trusted device value corresponding to the device identifier.

Claims (52)

1. A method of authenticating a mobile communications device for access to secure web services, the method comprising:

generating, at an authentication server, a code corresponding to a user, the code configured to be rendered on a rendering device to produce a rendered code, the rendered code being readable by a mobile communications device having a code reading device, the rendered code comprising a secret token;

storing the secret token along with information identifying the user on a first storage device associated with the authentication server;

providing the code to the user;

receiving, at the authentication server, at least one setup message from the mobile communications device, the at least one setup message comprising a mobile communication device identifier and the secret token;

comparing, at the authentication server, the received secret token and the secret token stored on the first storage device; and

if the received secret token matches the secret token stored on the first storage device, storing, on a second storage device associated with the authentication server, information identifying the user and a trusted device value corresponding to the mobile communication device identifier.

2. The method of claim 1 , wherein the code comprises an identifier of a server for sending the setup message.

3. The method of claim 1 , further comprising:

receiving, at the authentication server, information pertaining to a request by a requesting mobile communications device for access to a web service, the information comprising a requesting device identifier;

determining whether the requesting device identifier corresponds to the trusted device value stored on the storage device; and

denying access to the web service if the requesting device identifier does not correspond to the trusted device value.

4. The method of claim 3 , wherein the authentication server comprises a web server hosting the web services.

5. The method of claim 3 , wherein determining whether the requesting device identifier corresponds to trusted device value comprises determining whether the requesting device identifier comprises the device identifier encrypted with the secret token, the method further comprising:

denying access to the web service if the requesting device identifier does not comprise the device identifier encrypted with the secret token.

6. The method of claim 5 , further comprising:

encrypting the device identifier with the secret token to generate an encrypted device identifier;

wherein the determination is made by comparing the encrypted device identifier with the trusted device value.

7. The method of claim 5 , wherein the trusted device value corresponding to the device identifier stored on the storage device comprises the encrypted device identifier.

8. The method of claim 1 , wherein the identifier comprises mobile device metadata.

9. The method of claim 1 , wherein the code comprises a Quick Response (QR) code.

10. The method of claim 1 , wherein the code comprises a bar code.

11. A system for authenticating a mobile communications device for access to secure web services, the system comprising:

a first storage device;

a second storage device; and

an authentication server comprising a processor, the processor configured to:

generate a code corresponding to a user, the code configured to be rendered on a rendering device to produce a rendered code, the rendered code being readable by a mobile communications device having a code reading device, the rendered code comprising a secret token;

store the secret token along with information identifying the user on the first storage device associated with the authentication server;

transmit the code to a computing device;

receive at least one setup message from a mobile communications device, the at least one setup message comprising a mobile communication device identifier and the secret token;

compare the received secret token and the secret token stored on the first storage device; and

if the received secret token matches the secret token stored on the first storage device, store, on the second storage device associated with the authentication server, information identifying the user and a trusted device value corresponding to the mobile communication device identifier.

12. The system of claim 11 , wherein the code comprises an identifier of a server for sending the setup message.

13. The system of claim 11 , wherein the processor is further configured to:

receive information pertaining to a request by a requesting mobile communications device for access to a web service, the information comprising a requesting device identifier;

determine whether the requesting device identifier corresponds to the trusted device value stored on the storage device; and

deny access to the web service if the requesting device identifier does not correspond to the trusted device value.

14. The system of claim 13 , wherein the processor is further configured to:

deny access to the web service if the requesting device identifier does not comprise the device identifier.

15. The system of claim 13 , wherein the processor is further configured to:

transmit the result of the determination step to a web server hosting the web service.

16. The system of claim 13 , wherein determining whether the requesting device identifier corresponds to trusted device value comprises determining whether the requesting device identifier comprises the device identifier encrypted with the secret token.

17. The system of claim 16 , wherein the trusted device value corresponding to the device identifier stored on the storage device comprises the encrypted device identifier.

18. The system of claim 11 , wherein the identifier comprises mobile device metadata.

19. The system of claim 11 , wherein the code comprises a Quick Response (QR) code.

20. A non-transitory machine-readable memory storing statements and instructions for execution by a processor for implementing a method of authenticating a mobile communications device for access to secure web services, the method comprising:

generating, at an authentication server, a code corresponding to a user, the code configured to be rendered on a rendering device to produce a rendered code, the rendered code being readable by a mobile communications device having a code reading device, the rendered code comprising a secret token;

storing the secret token along with information identifying the user on a first storage device associated with the authentication server;

providing the code to the user;

receiving, at the authentication server, at least one setup message from the mobile communications device, the at least one setup message comprising a mobile communication device identifier and the secret token;

comparing, at an authentication server, the received secret token and the secret token stored on the first storage device; and

if the received secret token matches the secret token stored on the first storage device, storing, on a second storage device associated with the authentication server, information identifying the user and a trusted device value corresponding to the mobile communication device identifier.

Assignments (3)
CHANGE OF NAME Recorded Feb 11, 2015
From: DESIRE2LEARN INCORPORATED
To: D2L INCORPORATED
Reel/Frame 034954/0483 →
CHANGE OF NAME Recorded Feb 11, 2015
From: D2L INCORPORATED
To: D2L CORPORATION
Reel/Frame 034954/0493 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 9, 2012
From: AUGER, JEREMY
To: DESIRE2LEARN INCORPORATED
Reel/Frame 028759/0522 →
Continuity (1)
Related Publication 20140047524A1 · Feb 13, 2014