METHODS AND SYSTEMS FOR REDUCING BURST USAGE OF A NETWORKED COMPUTER SYSTEM

• US 20120215573A1
• Filed: 05/02/2012
• Published: 08/23/2012
• Est. Priority Date: 02/07/2006
• Status: Active Grant

• Current Assignee: Ticketmaster LLC (Live Nation Entertainment Incorporated)
• Original Assignee: Ticketmaster LLC (Live Nation Entertainment Incorporated)
• Inventors: Sussman, Adam, Ross, Brendan, Bennett, Bob, Denker, Dennis, Karonis, Andrew
• Granted Patent: US 9,147,170 B2
• Time in Patent Office: Days
• US Class Current: 705/5
• CPC Class Codes: G06F 9/50 Allocation of resources, e.g. of the central processing unit [CPU]
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 10/025 Coordination of plural reservations, e.g. plural trip segments, transportation combined with accommodation
• CPC Class Codes: G06Q 30/0603 Catalogue ordering
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 43/0894 Packet rate
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 67/1014 based on the content of a request
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests

Abstract

Methods and systems for reducing burst usage of a networked computer system are described herein. In an embodiment, resource requesters can request, within a time window, resources over a computer network before the resources are available. The resources can then be allocated in batch mode when the resources are available. Thus, resource requests do not have to be processed in real-time, and resource requests can be received before the resources are available.

Claims

1. A method of performing delayed allocations of tickets via a computer system, the method comprising:

transmitting over a network to a first terminal associated with a user information regarding a first time period when ticket requests for a first event will be accepted, wherein a ticket for the first event provides one or more people with event access;

receiving a first plurality of ticket requests over the network from a first plurality of users during the first time period, wherein ticket requests in the first plurality of ticket requests are for tickets at a set price;

processing the first plurality of ticket requests using the computer system during a second time period, wherein the second time period begins after the first plurality of ticket requests has been received;

ranking, by the computer system, ticket requests in the first plurality of ticket requests based on one or more of the following criteria;

a location of one or more users requesting tickets;

historical transaction frequency with respect to ticket purchases of one or more users requesting tickets;

quantity of previous tickets purchased by one or more users requesting tickets;

value of ticket purchases made by one or more users requesting tickets;

information related to a resale of tickets by one or more users requesting tickets;

the quantity of event seating currently being requested by one or more users requesting tickets;

whether one or more users are requesting an odd number of event seats;

preferred membership status of one or more users requesting tickets;

allocating tickets to at least a portion of the plurality users based at least in part on corresponding ticket request rankings; and

transmitting a communication to one or more users allocated a requested ticket.

2. The method as defined in claim 1, wherein ticket requests in the first plurality of ticket requests are ranked based at least in part on one the following criteria:

a location of one or more users requesting tickets;

quantity of previous tickets purchased by one or more users requesting tickets;

value of ticket purchases made by one or more users requesting tickets;

information related to a resale of tickets by one or more users requesting tickets;

the quantity of event seating currently being requested by one or more users requesting tickets;

whether one or more users are requesting an odd number of event seats.

3. The method as defined in claim 1, wherein ticket requests in the first plurality of ticket requests are ranked based at least in part on a location of one or more users requesting tickets.

4. The method as defined in claim 1, wherein ticket requests in the first plurality of ticket requests are ranked based at least in part on whether one or more users are requesting an odd number of event seats.

5. The method as defined in claim 1, the method further comprising providing over the network a form including a field for indicating an acceptable alternate event.

6. The method as defined in claim 1, the method further comprising providing over the network a form to the first terminal including a field for indicating whether the user is willing to accept tickets for non-contiguous seats.

7. The method as defined in claim 1, wherein the second time period begins at least twelve hours after the first time period begins.

8. The method as defined in claim 1, wherein the first plurality of users are designated as eligible to submit ticket requests during the first time period based at least in part on a first common characteristic, and a second plurality of users without the first common characteristic are not eligible to submit ticket requests during the first time period, and wherein the second plurality of users are eligible to submit ticket requests during a third time period that begins after the first time period begins.

9. The method as defined in claim 1, wherein the first plurality of users are designated as eligible to submit ticket requests during the first time period based at least in part on a first common characteristic, and a second plurality of users without the first common characteristic are not eligible to submit ticket requests during the first time period, wherein the first common characteristic is a membership in a first organization associated with a performer scheduled to perform at the first event.

10. The method as defined in claim 1, wherein the first plurality of users are designated as eligible to submit ticket requests during the first time period based at least in part on a first common characteristic, and a second plurality of users without the first common characteristic are not eligible to submit ticket requests during the first time period, wherein the first common characteristic is being holder of a credit card issued by a first organization.

11. The method as defined in claim 1, the method further comprising assigning a better ranking to a request requesting a ticket for an even number of seats than a request requesting a ticket for an odd number of seats.

12. The method as defined in claim 1, the method further comprising assigning a better ranking to a request requesting a ticket for relatively fewer seats than a request requesting a ticket for a relatively larger number of seats.

13. The method as defined in claim 1, the method further comprising assigning a better ranking to a request associated with a user that had not previously purchased a ticket via an operator of the computer system than a request associated with a user that had previously purchased a ticket via an operator of the computer system.

14. The method as defined in claim 1, the method further comprising assigning a better ranking to a request associated with a user that has a lower frequency of ticket purchases than a request associated with a user that has a relatively higher frequency of ticket purchases.

15. The method as defined in claim 1, the method further comprising assigning a better ranking to a request associated with a user that has purchased at least one ticket relatively more recently than a request associated with a user that has not purchased at least one ticket as recently.

16. The method as defined in claim 1, wherein the first time period is selected based at least in part on an event-type.

17. The method as defined in claim 1, the method further comprising:

receiving during a third time period a ticket request for the first event; and

processing and allocating at least one ticket to the ticket request received during the third time period in substantially real-time.

18. A system comprising:

one or more computing devices;

a non-transitory computer readable medium storing instructions that when executed by the one or more computing devices are configured to cause the system to perform operations comprising;

transmitting over a network to a first terminal associated with a user information regarding a first time period when ticket requests for a first event will be accepted, wherein a ticket for the first event provides one or more people with event access;

receiving a first plurality of ticket requests over the network from a first plurality of users during the first time period, wherein ticket requests in the first plurality of ticket requests are for tickets at a set price;

ranking, by the computer system, ticket requests in the first plurality of ticket requests based on one or more of the following criteria;

a location of one or more users requesting tickets;

historical transaction frequency with respect to ticket purchases of one or more users requesting tickets;

quantity of previous tickets purchased by one or more users requesting tickets;

value of ticket purchases made by one or more users requesting tickets;

information related to a resale of tickets by one or more users requesting tickets;

the quantity of event seating currently being requested by one or more users requesting tickets;

whether one or more users are requesting an odd number of event seats;

preferred membership status of one or more users requesting tickets;

allocating, during a second time period, wherein the second time period begins after the first plurality of ticket requests has been received, tickets to at least a portion of the plurality users based at least in part on corresponding ticket request rankings; and

transmitting a communication to one or more users allocated a requested ticket.

19. The system as defined in claim 18, wherein ticket requests in the first plurality of ticket requests are ranked based at least in part on one the following criteria:

a location of one or more users requesting tickets;

quantity of previous tickets purchased by one or more users requesting tickets;

value of ticket purchases made by one or more users requesting tickets;

information related to a resale of tickets by one or more users requesting tickets;

the quantity of event seating currently being requested by one or more users requesting tickets;

whether one or more users are requesting an odd number of event seats.

20. The system as defined in claim 18, wherein ticket requests in the first plurality of ticket requests are ranked based at least in part on a location of one or more users requesting tickets.

21. The system as defined in claim 18, wherein ticket requests in the first plurality of ticket requests are ranked based at least in part on whether one or more users are requesting an odd number of event seats.

22. The system as defined in claim 18, the operations further comprising distributing at least one allocated ticket via a mobile phone.

23. The system as defined in claim 18, the operations further comprising distributing at least one allocated ticket for printing to at least one user terminal.

24. The system as defined in claim 18, the operations further comprising distributing at least one allocated ticket via a smart card.

25. The system as defined in claim 18, the operations further comprising providing over the network a form including a field for indicating an acceptable alternate event.

26. The system as defined in claim 18, the operations further comprising providing over the network a form to the first terminal including a field for indicating whether the user is willing to accept tickets for non-contiguous seats.

27. The system as defined in claim 18, wherein the second time period begins after the first time period ends.

28. The system as defined in claim 18, wherein the second time period begins at least twelve hours after the first time period begins.

29. The system as defined in claim 18, wherein the first plurality of users are designated as eligible to submit ticket requests during the first time period based at least in part on a first common characteristic, and a second plurality of users without the first common characteristic are not eligible to submit ticket requests during the first time period, and wherein the second plurality of users are eligible to submit ticket requests during a third time period that begins after the first time period begins.

30. The system as defined in claim 18, wherein the first plurality of users are designated as eligible to submit ticket requests during the first time period based at least in part on a first common characteristic, and a second plurality of users without the first common characteristic are not eligible to submit ticket requests during the first time period, and wherein the second plurality of users are eligible to submit ticket requests during a third time period that begins after the first time period ends.

31. The system as defined in claim 18, wherein the first plurality of users are designated as eligible to submit ticket requests during the first time period based at least in part on a first common characteristic, and a second plurality of users without the first common characteristic are not eligible to submit ticket requests during the first time period, wherein the first common characteristic is a membership in a first organization.

32. The system as defined in claim 18, wherein the first plurality of users are designated as eligible to submit ticket requests during the first time period based at least in part on a first common characteristic, and a second plurality of users without the first common characteristic are not eligible to submit ticket requests during the first time period, wherein the first common characteristic is a membership in a first organization associated with a performer scheduled to perform at the first event.

33. The system as defined in claim 18, wherein the first plurality of users are designated as eligible to submit ticket requests during the first time period based at least in part on a first common characteristic, and a second plurality of users without the first common characteristic are not eligible to submit ticket requests during the first time period, wherein the first common characteristic is being holder of a credit card issued by a first organization.

34. The system as defined in claim 18, the operations further comprising assigning a better ranking to a request requesting a ticket for an even number of seats than a request requesting a ticket for an odd number of seats.

35. The system as defined in claim 18, the operations further comprising assigning a better ranking to a request requesting a ticket for relatively fewer seats than a request requesting a ticket for a relatively larger number of seats.

36. The system as defined in claim 18, the operations further comprising assigning a better ranking to a request associated with a user that had not previously purchased a ticket via an operator of the computer system than a request associated with a user that had previously purchased a ticket via an operator of the computer system.

37. The system as defined in claim 18, the operations further comprising assigning a better ranking to a request associated with a user that has a greater frequency of ticket purchases than a request associated with a user that has a relatively lower frequency of ticket purchases.

38. The system as defined in claim 18, the operations further comprising assigning a better ranking to a request associated with a user that has a lower frequency of ticket purchases than a request associated with a user that has a relatively higher frequency of ticket purchases.

39. The system as defined in claim 18, the operations further comprising assigning a better ranking to a request associated with a user that has purchased at least one ticket relatively more recently than a request associated with a user that has not purchased at least one ticket as recently.

40. The system as defined in claim 18, wherein the ranking of the first plurality of ticket requests is based at least in part on at least one requested ticket'"'"'s quality.

41. The system as defined in claim 18, the operations further comprising extending the first time period from an initial length based at least in part on how many ticket requests were received during at least a first portion of the first time period and/or how many seats were requested during at least a second portion of the first time period.

42. The system as defined in claim 18, the operations further comprising:

determining that at least two ticket requests have been assigned the same ranking; and

using one or more criteria to re-rank at least one of the at least two ticket requests.

43. The system as defined in claim 18, the operations further comprising determining that at least one form of payment proffered in association with at least one ticket request has been declined or is not valid, and re-ranking at least one other ticket request at least partly in response.

44. The system as defined in claim 18, wherein the first time period is selected based at least in part on an event-type.

45. The system as defined in claim 18, wherein the second time period is longer than the first time period.

46. The system as defined in claim 18, wherein only a first portion of the first event seating is available to be allocated to ticket requests received during the first time period, and a second portion of the first event seating is available to be allocated to ticket requests received during a third time period.

47. The system as defined in claim 18, where only users in a first set of users are eligible to submit ticket requests during the first time period, and users in a second set of users are eligible to submit ticket requests at a later time, wherein the second set of users is larger than the first set of users, and the second set of users includes at least a portion of the first set of users.

48. The system as defined in claim 18, the operations further comprising:

receiving during a third time period a ticket request for the first event; and

processing the ticket request received during the third time period in substantially real-time.

49. A system comprising:

one or more computing devices;

a non-transitory computer readable medium storing instructions that when executed by the one or more computing devices are configured to cause the system to perform operations comprising;

receiving a first plurality of ticket requests over the network, at the computer system, from a first plurality of users during the first time period;

ranking, by the computer system the first plurality of ticket requests for set price tickets based on one or more of the following criteria;

a location of one or more users requesting tickets;

quantity of previous tickets purchased by one or more users requesting tickets;

value of ticket purchases made by one or more users requesting tickets;

information related to a resale of tickets by one or more users requesting tickets;

allocating, by the computer system, tickets to at least a portion of the plurality users based at least in part on corresponding ticket request rankings; and

transmitting a communication to one or more users allocated a requested ticket.

50. The system as defined in claim 49, wherein the ranking of the first plurality of ticket requests is performed, at least in part, during a second time period, wherein the second time period begins after the first plurality of ticket requests has been received.

51. The system as defined in claim 49, wherein ticket requests in the first plurality of ticket requests are ranked based at least in part on one the following criteria:

a location of one or more users requesting tickets;

quantity of previous tickets purchased by one or more users requesting tickets;

value of ticket purchases made by one or more users requesting tickets;

information related to a resale of tickets by one or more users requesting tickets;

the quantity of event seating currently being requested by one or more users requesting tickets;

whether one or more users are requesting an odd number of event seats.

52. The system as defined in claim 49, wherein ticket requests in the first plurality of ticket requests are ranked based at least in part on a location of one or more users requesting tickets.

53. The system as defined in claim 49, wherein ticket requests in the first plurality of ticket requests are ranked based at least in part on whether one or more users are requesting an odd number of event seats.

54. The system as defined in claim 49, the method further comprising providing over the network a form including a field for indicating an acceptable alternate event.

55. The system as defined in claim 49, the method further comprising providing over the network a form to the first terminal including a field for indicating whether the user is willing to accept tickets for non-contiguous seats.