Mobile application bar code identification method and system

• US 9,147,191 B2
• Filed: 12/29/2011
• Issued: 09/29/2015
• Est. Priority Date: 06/09/2000
• Status: Expired due to Fees

• Current Assignee: Flash Seats LLC (Anschutz Company)
• Original Assignee: Flash Seats LLC (Anschutz Company)
• Inventors: Cohen, Benjamin Charles, Rosenbaum, Andrew Michael
• Primary Examiner(s): Hewitt, II, Calvin L
• Assistant Examiner(s): Neubig, Margaret
• Application Number:
  US13/340,200
• Publication Number:
  US 20120091202A1
• Time in Patent Office: 1,370 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/33 using certificates
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G07B 15/00 Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points handling coins or valuable papers, e.g. banknotes, G07D; apparatus for vending or hiring articles or services activated by coins, credit cards, paper currency or the like G07F7/00, G07F17/00
• CPC Class Codes: G07C 9/215 the system having a variable access-code, e.g. varied as a function of time
• CPC Class Codes: G07C 9/27 with central registration
• CPC Class Codes: H04M 1/72403 with means for local support of applications that increase the functionality
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor

Abstract

Applicant'"'"'s Smartphone application provides ticket-holding patrons an alternative, digital means of verifying personal identification at entry to a venue or event. The Smartphone application periodically generates a unique QR code (barcode) that contains a unique identifier (i.e., mobile device ID) which prompts the venue/event entry system to recognize the patron. No barcode (serving as a ticket, or authentication/verification, or otherwise) is downloaded from the system server to the Smartphone/mobile device client in contrast to prior art systems.

Claims

1. A computer-implemented method of electronically authenticating a person at a venue or event entry subsystem, comprising:

storing, by a server, an application in a memory;

receiving, by the server, a member identification of a user and mobile device identification of a mobile device of the user from the user;

modifying, by the server, the application using the received mobile device identification and member identification;

transferring, from the server, the modified application to the mobile device of the user;

receiving, by the server, a purchase request of a ticket comprising the member identification and mobile device identification from the mobile device of the user;

associating, by the server, the purchase request with the member identification in a database;

receiving, by the server, a quick response (QR) code comprising a representation of the member identification, the mobile device identification, and a time of generation of the QR code from a scanner device;

decoding, by the server, a QR code using the mobile identification; and

comparing, by the server, a decoded member identification, mobile device identification, and decoded time of generation from the decoded QR code with the ticket associated with the member identification and mobile device identification in the database; and

based on the comparison, sending, by the server, an authenticating message to the scanner device.

2. The computer-implemented method of claim 1, further comprising:

at the mobile device;

using the mobile application downloaded from the server, generating the code having the mobile identification, the mobile device identification, and the time.

3. The method as claimed in claim 1, further comprising:

authenticating a person who is an account holding patron, the mobile device user being the person holding the account; and

wherein the database stores account information, including for each account, an indication of one mobile device associated with the person holding the account.

4. The method as claimed in claim 3 further comprising:

storing, per account, ticket information of one or more tickets owned by the user in the database;

retrieving ticket information after positively authenticating the mobile device user at the venue or event entry; and

allowing the mobile device user to redeem one or more tickets.

5. The method as claimed in claim 1 wherein the venue or an event entry subsystem includes a gate or turnstile, the method further comprising:

automatically positively authenticating the mobile device user by allowing the mobile device user to pass through the gate or turnstile.

6. The method as claimed in claim 1 wherein the mobile device is any of a mobile phone, a PDA, a smartphone and a handheld digital processing device.

7. The method as claimed in claim 1 wherein the verifying automatically authenticates identity of the mobile device user as an individual at the venue or event entry separate from and independent of authenticating him as a specific ticket holder.

8. The method as claimed in claim 1 further comprising:

after said authenticating the mobile device user at the venue or event entry, obtaining from the database ticket data of said user; and

redeeming a ticket of said user in the database by marking the ticket as used.

9. The method as claimed in claim 1, further comprising determining the code is valid based on the decoded time of generation being outside of an expiration time range.

10. An electronic authentication apparatus electronically authenticating a person at a venue or event entry, comprising:

a server having a memory storing executable instructions that when executed by the server causes the server to perform the operations of;

storing an application in the memory;

receiving a member identification of a user and mobile device identification of a mobile device of the user from the user;

modifying the application using the received mobile device identification and member identification;

transferring the modified application to the mobile device of the user;

receiving a purchase request of a ticket comprising the member identification and mobile device identification from the mobile device of the user;

associating the purchase request with the member identification in a database;

receiving a quick response (QR) code comprising a representation of the member identification, the mobile device identification, and a time of generation of the QR code from a scanner device;

decoding a QR code using the mobile identification; and

comparing a decoded member identification, mobile device identification, and

decoded time of generation from the decoded QR code with the ticket associated with the member identification and mobile device identification in the database; and

based on the comparison, sending an authenticating message to the scanner device.

11. The apparatus of claim 10, further comprising:

a mobile device configured to, using the mobile application downloaded from the server, generate the code having the mobile identification, the mobile device identification, and the time.

12. The apparatus of claim 10, further comprising the memory storing executable instructions that when executed by the server causes the server to perform the operations of:

authenticating a person who is an account holding patron, the mobile device user being the person holding the account; and

wherein the database stores account information, including for each account, an indication of one mobile device associated with the person holding the account.

13. The apparatus of claim 12 further comprising comprising the memory storing executable instructions that when executed by the server causes the server to perform the operations of:

storing, per account, ticket information of one or more tickets owned by the user in the database;

retrieving ticket information after positively authenticating the mobile device user at the venue or event entry; and

allowing the mobile device user to redeem one or more tickets.

14. The apparatus of claim 10 wherein the venue or an event entry subsystem includes a gate or turnstile, the server further configured to automatically positively authenticate the mobile device user by allowing the mobile device user to pass through the gate or turnstile.

15. The apparatus of claim 10 wherein the mobile device is any of a mobile phone, a PDA, a smartphone and a handheld digital processing device.

16. The apparatus of claim 10 wherein the verifying automatically authenticates identity of the mobile device user as an individual at the venue or event entry separate from and independent of authenticating him as a specific ticket holder.

17. The apparatus of claim 10, wherein the server is further configured to:

after said authenticating the mobile device user at the venue or event entry, obtain from the database ticket data of said user; and

redeem a ticket of said user in the database by marking the ticket as used.

18. The apparatus of claim 10, wherein the server is further configured to determine the code is valid based on the decoded time being outside of an expiration time range.

19. A computer-based electronic authentication system electronically authenticating a person at a venue or event entry, comprising:

at a server having a database;

a storage means for storing an application in memory;

an identification reception means for receiving a member identification of a user and mobile device identification of a mobile device of the user from the user;

an application configuration means for modifying the application using the received mobile device identification and member identification;

a transfer means for transferring the modified application to the mobile device of the user;

a request reception means for receiving a purchase request of a ticket comprising the member identification and mobile device identification from the mobile device of the user;

an association means for associating the purchase request with the member identification in a database;

a code reception means for receiving a quick response (QR) code comprising a representation of the member identification, the mobile device identification, and a time of generation of the QR code from a scanner device;

a decoding means for decoding a QR code using the mobile identification; and

a comparison means for comparing a decoded member identification, mobile device identification, and decoded time of generation from the decoded QR code with the ticket associated with the member identification and mobile device identification in the database; and

based on the comparison, sending an authenticating message to the scanner device.