IP Library Granted Patent US 11,593,501
Granted Patent B2
US 11,593,501 · App. 17/135,650 · Granted Feb 28, 2023

System and method for using unique device identifiers to enhance security

Inventors: Samuel Levin (Los Angeles, CA); David Scarborough (Ashburn, VA); Fengpei Du (Santa Monica, CA); Richard DiStefano (Burbank, CA); Dennis Denker (Scottsdale, AZ); Sean Moriarty (Pasadena, CA); Charles Plamondon (Quebec, CA); Matthew Siegel (Tampa, FL); Benjamin Marti (Gilbert, AZ)
Assignee: Live Nation Entertainment, Inc.
G06F21/6218G06F21/10G06F21/44G06F21/73G06Q10/02G06Q30/0185H04L63/04H04L63/101H04L63/102H04W4/80H04W12/08H04W76/11G06F2221/0706G06F2221/2141G06Q2220/00
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 11,593,501
App. No.
17/135,650
Granted
Feb 28, 2023
Kind
B2
Abstract

A method for detection and use of device identifiers to enhance the security of data transfers between electronic devices. A first electronic device can transmit access data to a second electronic device. The access data can be associated with a first access code that can be generated based at least in part on data representing a device identifier of the first electronic device. A device identifier can uniquely identify the first electronic device from a plurality of electronic devices. Transferring the access data can involve transforming the first access code into a second access code that can include data representing a device identifier associated with the second electronic device. Transforming the first access code into the second access code can facilitate access to a resource associated with the access data for a second user, but not for a first user.

Claims (72)

1. A networked ticketing system for verifying a ticket for an event, comprising:

a database including records that contain identifier codes associated with a plurality tickets;

a computing device including one or more processors;

a tangible non-transitory computer readable memory; and

a first networkable server including instructions, stored in the tangible non-transitory computer readable memory, that when executed by the computing device, are configured to:

provide a user interface for display via a first user terminal to a first user, the user interface including a list of the plurality tickets that are currently available for use at the event, and wherein:

the ticket from the plurality of tickets comprise a first code, and

the first code is configured for authenticating the ticket upon access to the event, at least a portion of the first code includes a representation of a first device identifier of the first terminal;

select, by the first user, the ticket from the plurality of tickets to be forwarded to a second user;

determine if the ticket selected by the first user is eligible to be forwarded;

if the ticket selected by the first user is not eligible for forwarding, notify the first user via a first communication that the ticket selected by the first user cannot be forwarded to the second user;

if the ticket selected by the first user is eligible for forwarding:

generate a second code, different from the first code,

invalidate the first code, whereby the first user having the ticket with the first code would not be allowed to enter in the event using the first code, and

forward the second code with the ticket; and

verify the second code upon ingress to the event to confirm that the ticket is authentic.

2. The networked ticketing system for verifying the ticket for the event as recited in claim 1 , wherein the second code further indicates that the ticket forwarded to the second user is a result of resale operation.

3. The networked ticketing system for verifying the ticket for the event as recited in claim 1 , further configured to provide and store an invalidation indication in the database to inhibit use of the ticket.

4. The networked ticketing system for verifying the ticket for the event as recited in claim 1 , further comprising:

a sale posting control configured to accept an instruction from the first user to post the ticket for sale to other users accessing a networked computer resource, wherein other users, different from the first user, submit purchase requests for the ticket via the networked computer resource.

5. The networked ticketing system for verifying the ticket for the event as recited in claim 1 , further comprising:

determining that the first user has returned the ticket; and

at least partly in response to determining that the first user has returned the ticket, issuing a credit to the first user.

6. The networked ticketing system for verifying the ticket for the event as recited in claim 1 , further comprising:

storing in the database information regarding issuance of the first code to the first user and issuance of the second code to the second user for a seat at the event.

7. A ticketing system for verifying a ticket for an event, comprising:

a database of information on tickets previously sold to users that are being offered for resale by the users, the database including at least seating and price information for a first ticket of a first user, and being stored in non-transitory tangible computer media, the first ticket being a physical ticket;

a search engine configured to receive a search request transmitted over a network from a terminal associated with a second user and to selectively transmit to the terminal associated with second user information retrieved from the database, including at least seating and price information for the ticket; and

one or more non-transitory tangible computer readable memories and one or more processors with at least computer instructions, stored in the one or more non-transitory tangible computer readable memories that, when executed by the one or more processors, is configured to:

provide a user interface for display with a first user terminal to the first user, the user interface including a list of the tickets that are currently available for use at the event, and wherein:

the ticket from the list of the tickets comprise a first code, and

the first code is used to authenticate the ticket and allow access to the event,

at least a portion of the first code includes a representation of a first device identifier of the first terminal;

select, by the first user, the ticket from the list of the tickets to be forwarded to the second user;

determine if the ticket selected by the first user is eligible to be forwarded;

if the ticket selected by the first user is not eligible for forwarding, notify the first user via a first communication that the ticket selected by the first user cannot be forwarded to the second user;

if the ticket selected by the first user is eligible for forwarding:

generate a second code, different from the first code,

forward the second code to the second user with the ticket, and

invalidate the first code so that the first user having the ticket with the first code is not authorized to enter in the event; and

verify the second code with the ticket at ingress to the event, wherein the verifying of the second code indicates that the ticket forwarded to the second user is authentic.

8. The ticketing system for verifying the ticket for the event as recited in claim 7 , wherein the second code further indicates that the ticket forwarded to the second user is associated with resale.

9. The ticketing system for verifying the ticket for the event as recited in claim 7 , further configured to provide and store an invalidation indication in the database associated with the ticket to inhibit use of the first code.

10. The ticketing system for verifying the ticket for the event as recited in claim 7 , further comprising:

a sale posting control configured to accept an instruction from the first user to post the ticket for sale to other users accessing the search engine, wherein other users, different from the first user, submit purchase requests for the ticket via the search engine.

11. The ticketing system for verifying the ticket for the event as recited in claim 7 , further comprising:

determining that the first user has returned the first ticket; and

at least partly in response to determining that the first user has returned the first ticket, issuing a credit to the first user.

12. The ticketing system for verifying the ticket for the event as recited in claim 7 , further comprising:

storing in the database information regarding issuance of the ticket to the first user and issuance of the second code to the second user for a seat at the event.

13. A computer-implemented method for verifying a ticket for an event, comprising:

providing a user interface for display via a first user terminal to a first user, the user interface including a list of tickets that are currently available for use at the event, and wherein:

the ticket from the list of tickets comprise a first code, and

first code is used to authenticate the ticket and allow access to the event,

at least a portion of the first code includes a representation of a first device identifier of the first terminal;

selecting, by the first user, the ticket from the list of tickets to be forwarded to a second user;

determining if the ticket selected by the first user is eligible to be forwarded;

if the ticket selected by the first user is not eligible for forwarding, notify the first user via a first communication that the ticket selected by the first user cannot be forwarded to the second user;

if the ticket selected by the first user is eligible for forwarding:

generate a second code, different from the first code,

forward the second code to the second user with the ticket, and

invalidate the first code so that the first user having the ticket with the first code is not allowed to enter in the event; and

verifying the second code along with the ticket with ingress to the event, wherein the verifying of the second code indicates that the ticket forwarded to the second user is authentic.

14. The computer-implemented method for verifying the ticket for the event as recited in claim 13 , wherein the second code further indicates that the ticket forwarded to the second user is a result of a resale operation.

15. The computer-implemented method for verifying the ticket for the event as recited in claim 13 , further comprising storing an invalidation indication in a database record associated with eh first code to inhibit use of the ticket.

16. The computer-implemented method for verifying the ticket for the event as recited in claim 13 , further comprising:

accepting an instruction from the first user to post the ticket for sale to other users, wherein other users, different from the first user, submit purchase requests for the ticket.

17. The computer-implemented method for verifying the ticket for the event as recited in claim 13 , further comprising:

determining that the first user has returned the ticket; and

at least partly in response to determining that the first user has returned the ticket, issuing a credit to the first user.

18. The computer-implemented method for verifying the ticket for the event as recited in claim 13 , further comprising:

storing in a database information regarding issuance of the ticket to the first user and the issuance of the ticket to the second user for a seat at the event.

Assignments (3)
SECURITY AGREEMENT Recorded Nov 17, 2023
From: LIVE NATION ENTERTAINMENT, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 065613/0867 →
NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Recorded Nov 17, 2023
From: LIVE NATION ENTERTAINMENT, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION, AS SUCCESSOR IN INTEREST TO U.S. BANK NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 065615/0001 →
NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Recorded Nov 17, 2023
From: LIVE NATION ENTERTAINMENT, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION, AS SUCCESSOR IN INTEREST TO U.S. BANK NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 065615/0257 →
Continuity (16)
Continuation 16556434 · Aug 30, 2019
Continuation 16160867 · Oct 15, 2018
Continuation 15627231 · Jun 19, 2017
Continuation 15233473 · Aug 10, 2016
Continuation 15005970 · Jan 25, 2016
Continuation In Part 10731410 · Dec 9, 2003
Continuation In Part 14049909 · Oct 9, 2013
Continuation In Part 14202218 · Mar 10, 2014
Continuation In Part 14553902 · Nov 25, 2014
Continuation 13948906 · Jul 23, 2013
Division 12716616 · Mar 3, 2010
Provisional Application 60431865 · Dec 9, 2002
Provisional Application 61712009 · Oct 10, 2012
Provisional Application 61791123 · Mar 15, 2013
Provisional Application 61158237 · Mar 6, 2009
Related Publication 20210286888A1 · Sep 16, 2021