TIERED OVERSUBSCRIPTION

• US 20150120341A1
• Filed: 10/25/2013
• Published: 04/30/2015
• Est. Priority Date: 10/25/2013
• Status: Abandoned Application

• Current Assignee: Live Nation Entertainment Incorporated
• Original Assignee: Live Nation Entertainment Incorporated
• Inventors: Scarborough, David
• Application Number:
  US14/063,929
• Publication Number:
  US 20150120341A1
• Time in Patent Office: Days
• US Class Current: 705/5
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events

Abstract

Techniques are described for allocating and distributing tickets to an event at a venue. The tickets are distributed in a multi-step process in which first pre-issue tickets are allocated and distributed. Expected attendance for an event is calculated and pre-issue tickets are allocated and distributed based on the expected attendance. Seats are assigned at a later time when the user enters the venue or checks in for the event. When a user'"'"'s ticket is part of a group of tickets, seats are assigned for the entire group rather than merely assigning a ticket for the user.

Claims

1. A method for automatically managing an allocation of tickets to an event to select potential purchasers, the method comprising:

receiving an indication that a user is attending the event at a venue hosting the event;

validating that the user had been pre-issued a ticket for the event at the venue, wherein a pre-issued ticket does not include an assignment to any seat in the venue;

determining a characteristic characterizing assignments to seats in the venue for the event;

identifying a seat in the venue that has not been assigned for the event;

generating a ticket for the identified seat for the event, wherein the ticket includes an assignment to the identified seat; and

issuing the ticket that includes the assignment to the identified seat to the user.

2. The method of claim 1, wherein the indication that the user is attending the event at the venue comprises geolocation information, the geolocation information providing a proximity of the user to the venue.

3. The method of claim 1, wherein the indication that the user is attending the event at the venue comprises a presence of the user at the venue.

4. The method of claim 1, wherein seats are issued in an order such that there is a correlation between demands of seats assigned and times at which the indication that the user will attend the event is received.

5. The method of claim 1, further comprising:

pre-issuing a number of pre-issued tickets for the event, wherein the number exceeds a number of available seats at the venue.

6. The method of claim 5, wherein the number is determined based on a number of users that attended a past event and a number of users that were issued or pre-issued tickets to the event.

7. The method of claim 6, wherein the number of pre-issued tickets for the event is 20% larger than a capacity of the venue for the even.

8. The method of claim 1, further comprising grouping the pre-issued ticket with other pre-issued tickets of other users and identifying the seat in the venue that is collocated with assigned seats associated with the other pre-issued tickets of other users.

9. A ticket management system, the system comprising:

one or more processors; and

one or more memories coupled with the one or more processors, wherein the one or more processors and one or more memories are configured to;

receive an indication that a user is attending an event at a venue hosting the event;

validate that the user had been pre-issued a ticket for the event at the venue, wherein a pre-issued ticket does not include an assignment to any seat in the venue;

determine a characteristic characterizing assignments to seats in the venue for the event;

identify a seat in the venue that has not been assigned for the event;

generate a ticket for the identified seat for the event, wherein the ticket includes an assignment to the identified seat; and

issue the ticket that includes the assignment to the identified seat to the user.

10. The ticket management system of claim 9, wherein the indication that the user is attending the event at the venue comprises geolocation information, the geolocation information providing a proximity of the user to the venue.

11. The ticket management system of claim 9, wherein the indication that the user is attending the event at the venue comprises a presence of the user at the venue.

12. The ticket management system of claim 9, wherein seats are issued in an order such that there is a correlation between demands of seats assigned and times at which the indication that the user will attend the event is received.

13. The ticket management system of claim 9, wherein the one or more processors and one or more memories are further configured to issue a number of pre-issued tickets for the event, wherein the number exceeds a number of available seats at the venue.

14. The ticket management system of claim 13, wherein the number is determined based on a number of users that attended a past event and a number of users that were issued or pre-issued tickets to the event.

15. The ticket management system of claim 14, wherein the size of the number of pre-issued tickets is 20% larger than a capacity of the venue for the even.

16. The ticket management system of claim 9, wherein the one or more processors and one or more memories are further configured to group the pre-issued ticket with other pre-issued tickets of other users and identifying the seat in the venue that is collocated with assigned seats associated with the other pre-issued tickets of other users.

17. A ticket management system comprising:

a ticket engine that;

receives an indication that a user is attending an event at a venue; and

validates that the user had been pre-issued a ticket for the event at the venue, wherein a pre-issued ticket does not include an assignment to any seat in the venue;

a seat resource engine that;

identifies a seat in the venue that has not been assigned for the event; and

generates a ticket for the identified seat for the event, wherein the ticket includes an assignment to the identified seat; and

a ticket engine that;

causes the ticket that includes the assignment to the identified seat to be issued.

18. The ticket management system of claim 17, further comprising a location estimator that receives user geolocation information, the geolocation information providing a proximity of the user to the venue, wherein the geolocation information is received by the ticket engine as the indication that the user is attending the event.

19. The ticket management system of claim 17, wherein the indication that the user is attending the event at the venue comprises a presence of the user at the venue.

20. The ticket management system of claim 17, wherein the client interface engine is configured to issue a number of pre-issued tickets for the event, wherein the number exceeds a number of available seats at the venue.