Methods and systems for reducing burst usage of a networked computer system

• US 20070245351A1
• Filed: 02/07/2007
• Published: 10/18/2007
• Est. Priority Date: 02/07/2006
• Status: Active Grant

• Current Assignee: Live Nation Entertainment Incorporated
• Original Assignee: Ticketmaster (Live Nation Entertainment Incorporated)
• Inventors: Denker, Dennis, Karonis, Andrew, Sussman, Andrew, Bennett, Bob, Ross, Brendan
• Granted Patent: US 8,176,177 B2
• Time in Patent Office: Days
• US Class Current: 718/104
• 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 reducing burst usage in a networked computer system, the method comprising:

transmitting over a network to a plurality of computers information regarding a future first time period when resource requests for a first set of resources will be accepted, wherein resources in the first set of resources are not allocated during the first time period;

receiving a plurality of resource requests from a plurality of requesters during the first period of time, wherein the plurality of resource requests are received over the network,

wherein the plurality of resource requests include a request from a first of the resource requesters for a preferred resource and an indication as to whether an alternate resource different than the preferred resource would be acceptable;

during a second time period beginning after the first time period ends, processing the plurality of resource requests in batch mode using a processing system, the processing further comprising;

ranking the plurality of resource requests based on one or more of the following criteria;

corresponding locations for some or all of the resource requesters;

history of resource requests for some or all of the resource requesters;

allocating resources to at least a portion of the plurality requesters based at least in part on corresponding resource request rankings and availability of requested resources;

transmitting a communication over the network to one or more requesters receiving an allocation, the communication providing information regarding the corresponding allocation;

allocating the alternate resource to the first requester if the first requester indicated a willingness to accept the alternate resource, was not allocated the preferred resource, and if the alternate resource is available to be allocated to the first requester; and

transmitting a communication over the network regarding the alternate resource allocation to the first requester.

2. The method as defined in claim 1, the method further comprising selecting the second period based at least in part on an anticipated utilization level of the processing system.

3. The method as defined in claim 1, the method further comprising transmitting over the network to one or more computers information regarding a maximum permissible resource request.

5. The method as defined in claim 1, wherein a start time of the first time period is selected based at least in part on a resource-type.

6. The method as defined in claim 1, wherein the second time period is longer than the first time period.

7. The method as defined in claim 1, wherein the ranking of the plurality of resource requests is based at least in part on historical resource request frequency information for at least a portion of the resource requesters.

8. The method as defined in claim 1, wherein the ranking of the plurality of resource requests is based at least in part on at least one requested resource'"'"'s quality.

9. The method as defined in claim 1, the method further comprising transmitting to at least one computer a specific price for a first resource requested via the computer.

10. The method as defined in claim 1, the method further comprising transmitting to at least one computer an indication that the actual price a first requested resource is not yet known.

11. The method as defined in claim 1, the method further comprising transmitting to at least one computer an indication that the actual price a first requested resource is not yet known and providing a price range within which the actual price will fall.

12. The method as defined in claim 1, where the resources are related to event seating for one or more events, and only a portion of the event seating for the one or more events is available to be allocated to resource requests received during the first time period.

13. The method as defined in claim 12, wherein the preferred resource is related to seating for a first event, and the alternate resource is related to seating for a second event.

14. The method as defined in claim 13, wherein the first event and the second event have a common event performer.

15. The method as defined in claim 1, where only users in a first set of users are eligible to submit resource requests during the first time period, and users in a second set of users are eligible to submit resource requests at a later time, wherein the second set of users is larger than the first set of users.

16. The method as defined in claim 15, where the second set of users includes at least a portion of the first set of users.

17. The method as defined in claim 1, wherein at least some of the resource requests are related to the right to utilize a first physical location for a first event.

18. The method as defined in claim 17, wherein the first physical location corresponds to an area in a venue.

19. The method as defined in claim 17, wherein the first physical location includes at least one seat.

20. The method as defined in claim 1, wherein the alternate requested resource is associated with a performer that is also associated with at least one requested resource.

4. The method as defined in claim 4, the method further comprising rejecting at least one resource request that requests more than the maximum permissible resources.

21. A method of allocating resources in batch mode via a computer system, the method comprising:

transmitting over a network to a plurality of terminals information regarding a future first time period when resource requests for a first set of resources will be accepted but will not be allocated;

receiving a plurality of resource requests over the network from a plurality of requesters during the first period of time;

ranking the plurality of resource requests based on one or more of the following criteria;

location of one or more resource requesters;

historical transaction frequency of one or more resource requesters;

quantity of previous resource allocations to one or more resource requesters;

historical transaction value of resource allocations to one or more resource requesters;

information related to reallocation of resources by one or more resource requesters to others;

a quantity of resources currently being requested by one or more resource requesters;

whether a number of resources currently being requested by one or more resource requesters is an odd or even number of resources;

preferred membership status of one or more resource requesters;

during a second period of time, allocating resources using a processing system to at least a portion of the plurality requesters based at least in part on corresponding resource request rankings; and

transmitting a communication over the network to at least one requester allocated a requested resource, the communication including a notification regarding the requested resource allocation.

22. The method as defined in claim 21, wherein the second period of time is selected based on part on an anticipated utilization level of the processing system.

23. The method as defined in claim 21, the method further comprising transmitting over the network to one or more terminals information regarding a maximum permissible resource request.

24. The method as defined in claim 22, the method further comprising rejecting at least one resource request that requests more than the maximum permissible resources.

25. The method as defined in claim 21, wherein the first time period is selected based at least in part on a resource-type.

26. The method as defined in claim 21, wherein the second time period is longer than the first time period.

27. The method as defined in claim 21, wherein the ranking of the plurality of resource requests is based at least in part on at least one requested resource'"'"'s quality.

28. The method as defined in claim 21, the method further comprising transmitting to at least one terminal a specific cost for a first resource requested via the at least one terminal.

29. The method as defined in claim 21, the method further comprising transmitting to at least one terminal an indication that the actual cost of a first requested resource is not yet known.

30. The method as defined in claim 21, the method further comprising transmitting to at least one terminal an indication that the actual cost of a first requested resource is not yet known and providing a cost range within which the actual cost will fall.

31. The method as defined in claim 21, where the requested resources are related to event seating, and only a portion of the event seating is available to be allocated to resource requests received during the first time period.

32. The method as defined in claim 21, where only users in a first set of users are eligible to submit resource requests during the first time period, and users in a second set of users are eligible to submit resource requests at a later time, wherein the second set of users is larger than the first set of users.

33. The method as defined in claim 32, where the second set of users includes at least a portion of the first set of users.

34. The method as defined in claim 21, wherein at least a portion of the resource requests are related to the right to utilize a first physical location for a first event.

35. The method as defined in claim 34, wherein the first location corresponds to an area in a venue.

36. The method as defined in claim 34, wherein the first location includes at least one seat.

37. The method as defined in claim 21, wherein the plurality of resource requests are ranked using a price asked by one or more resource requesters for at least one resource previously offered by the one or more resource requesters.

38. The method as defined in claim 21, the method further comprising storing in computer readable memory:

an event date of an event associated with requested resources, wherein the event is a sports event or a musical event;

a performer or team identity associated with the event;

a venue identifier where the event is to take place; and

information related to the amount of resources available for allocation during the first time period.

39. The method as defined in claim 21, wherein at least a portion of the resource requests are related to the right to utilize a first physical location for a first event, the method further comprising:

receiving during a third time period a resource request related to the right to utilize at least one physical location for the first event; and

determining in substantially real-time if there is an available resource corresponding to the resource request received during the third time period.

40. The method as defined in claim 21, wherein the communication is provided via a Web page.

41. The method as defined in claim 21, wherein the communication is provided via an email and/or an SMS message.

42. The method as defined in claim 21, wherein the communication is provided via an instant messaging service.

43. The method as defined in claim 21, wherein the communication confirming the resource allocation includes seating information for an event, and is sent before the event takes place.

44. The method as defined in claim 21, wherein the plurality of terminals includes a computer.

45. The method as defined in claim 21, wherein the plurality of terminals includes an interactive television.

46. The method as defined in claim 21, wherein the plurality of terminals includes a phone.

47. 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 period of time;

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

ranking 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 is 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.

48. The method as defined in claim 47, the method further comprising distributing at least one allocated ticket via a mobile phone.

49. The method as defined in claim 47, the method further comprising distributing at least one allocated ticket for printing to at least one user terminal.

50. The method as defined in claim 47, the method further comprising distributing at least one allocated ticket via a smart card.

51. The method as defined in claim 47, the method further comprising providing over the network a form to at least one user terminal, the form including a field for indicating how many tickets are being requested, and a field for indicating information related to a price associated with the requested tickets.

52. The method as defined in claim 47, the method further comprising providing over the network a form including a field for indicating a desired type of seating.

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

54. The method as defined in claim 47, 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.

55. The method as defined in claim 47, wherein the second time period begins after the first time period ends.

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

57. The method as defined in claim 47, wherein the first plurality of users are designated as eligible to submit ticket requests during the first time period based at least in part 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 period of time.

58. The method as defined in claim 57, 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.

59. The method as defined in claim 57, 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.

60. The method as defined in claim 57, wherein the first common characteristic is a membership in a first organization.

61. The method as defined in claim 60, wherein the first organization is associated with a performer scheduled to perform at the first event.

62. The method as defined in claim 57, wherein the first common characteristic is being holder of a credit card issued by a first organization.

63. The method as defined in claim 57, 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.

64. The method as defined in claim 57, 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.

65. The method as defined in claim 57, 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 processing system than a request associated with a user that had previously purchased a ticket via an operator of the processing system.

66. The method as defined in claim 57, the method 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.

67. The method as defined in claim 57, 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.

68. The method as defined in claim 57, 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.

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

70. The method as defined in claim 57, the method further comprising extending the first period of time 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 period of time and/or how many seats were requested during at least a second portion of the first period of time.

71. The method as defined in claim 57, the method 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.

72. The method as defined in claim 57, the method 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.

73. The method as defined in claim 57, the method further comprising transmitting over the network to one or more terminals information related to a maximum permissible ticket request.

74. The method as defined in claim 73, the method further comprising rejecting at least one ticket request that requests more than the maximum permissible tickets.

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

76. The method as defined in claim 57, wherein the second time period is longer than the first time period.

77. The method as defined in claim 57, the method further comprising transmitting to at least one terminal an indication that a price of a first requested ticket is not yet known.

78. The method as defined in claim 57, the method further comprising transmitting to at least one terminal an indication that the price of a first requested ticket is not yet known and providing a cost range within which the price will fall.

79. The method as defined in claim 57, 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.

80. The method as defined in claim 57, 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.

81. The method as defined in claim 80, where the second set of users includes at least a portion of the first set of users.

82. The method as defined in claim 57, the method further comprising storing in computer readable memory:

an event date on which the first event will take place;

a performer or team identity associated with the first event; and

a venue identifier associated with the first event.

83. The method as defined in claim 57, the method 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.

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

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

ranking 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;

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.

85. The method as defined in claim 84, the method further comprising distributing at least one allocated ticket via a mobile phone.

86. The method as defined in claim 84, the method further comprising distributing at least one allocated ticket for printing to at least one user terminal.

87. The method as defined in claim 84, the method further comprising distributing at least one allocated ticket via a smart card.

88. The method as defined in claim 84, the method further comprising providing over the network a form to at least one user terminal, the form including a field for indicating how many tickets are being requested, and a field for indicating information related to a price associated with the requested tickets.

89. The method as defined in claim 84, the method further comprising providing over the network a form including a field for indicating a desired type of seating.

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

91. The method as defined in claim 84, 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.