Systems and methods for providing resource allocation in a networked environment

• US 8,255,486 B2
• Filed: 07/08/2011
• Issued: 08/28/2012
• Est. Priority Date: 08/07/2007
• Status: Active Grant

• Current Assignee: Ticketmaster LLC (Live Nation Entertainment Incorporated)
• Original Assignee: Ticketmaster LLC (Live Nation Entertainment Incorporated)
• Inventors: Denker, Dennis, Levin, Kip, Scarborough, David
• Primary Examiner(s): WON, MICHAEL YOUNG
• Application Number:
  US13/179,012
• Publication Number:
  US 20120136990A1
• Time in Patent Office: 417 Days
• Field of Search: 709/203, 709/217, 709/219, 709/225, 709/229
• US Class Current: 709/217
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 30/08 Auctions
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests

Abstract

Systems and methods are described for adjusting an item characteristic. An illustrative system includes a first network interface, a database storing information regarding a plurality of items, a load balancer, a web proxy processor configured to selectively block or route an inbound user browser request, a cache cluster system configured to cache data and states for access by other system components, and program code stored in computer readable memory, which, when executed is configured to receive a plurality of requests for items from corresponding users, wherein the plurality of requests are associated with corresponding offer amounts and determine what the users are to provide for the items based at least in part on how many requests were received, how many items are allocated to users, and/or how many unallocated items are available, wherein at least a portion of the users are to provide an amount different than their corresponding offer amount.

Claims

1. A system, comprising:

a first network interface via which a plurality of remote terminals can access the system;

a web proxy processor configured to selectively block an inbound user request or route an inbound request received over the network interface to a destination server;

a database storing information regarding a first plurality of tickets; and

program code stored in computer readable memory, which, when executed is configured to cause the system to perform operations comprising;

provide users with information regarding a ticketed event, including at least;

an event name,

a date for the ticketed event, and

a location for the ticketed event;

receive a first plurality of requests for event tickets from corresponding users, wherein the first plurality of requests are associated with corresponding currency amounts for the requested event tickets; and

calculate ticket prices for one or more tickets for the event based at least in part on a central tendency of the corresponding currency amounts for the requested event tickets associated with the first plurality of requests and on how many unallocated tickets are available;

wherein the central tendency is calculated at least in part by;

calculating an average of at least a portion of the corresponding currency amounts, a median of at least a portion the corresponding currency amounts, a trimedian of at least a portion the corresponding currency amounts, a mode of at least a portion the corresponding currency amounts, and/or a mean of at least a portion the corresponding currency amounts;

wherein the system is further configured to transmit, over the network to one or more remote terminals, the calculated ticket prices.

2. The system as defined in claim 1, wherein the central tendency is calculated at least in part by calculating an average of the corresponding currency amounts.

3. The system as defined in claim 1, wherein the central tendency is calculated at least in part by calculating a median of the corresponding currency amounts.

4. The system as defined in claim 1, wherein the central tendency is calculated at least in part by calculating a trimedian of the corresponding currency amounts.

5. The system as defined in claim 1, wherein the central tendency is calculated at least in part by a mode of the corresponding currency amounts.

6. The system as defined in claim 1, wherein the central tendency is calculated at least in part by calculating a mean of the corresponding currency amounts.

7. The system as defined in claim 1, wherein the central tendency is calculated at least in part by calculating a quadratic mean, a generalized mean, a weighted mean, a truncated mean, a midrange, a Winsorized mean, an exponential mean, a trimean, or a normalized mean.

8. The system as defined in claim 1, wherein the system is further configured to:

access an adjustment limit from computer readable memory, wherein the adjustment limit indicates an upper limit on a ticket price adjustment value for at least a first ticket; and

inhibit a ticket price for the first ticket from being adjusted beyond the upper limit.

9. The system as defined in claim 1, wherein the system is further configured to:

access an adjustment limit from computer readable memory, wherein the adjustment limit indicates an upper limit on a ticket price adjustment value for at least a first ticket; and

inhibit a ticket price for the first ticket from being adjusted beyond the upper limit, wherein the adjustment limit is expressed as a percentage or as a currency amount.

10. The system as defined in claim 1, wherein the system is further configured to:

store a ranking of the first plurality of requests;

store a ranking of the first plurality of tickets; and

allocate tickets to at least a portion of the corresponding users based at least in part on the ranking of the first plurality of requests and the ranking of the first plurality of tickets.

11. A method of calculating a ticket exchange value, the method comprising:

offering event tickets for allocation via a networked resource;

receiving over a network a plurality of requests for tickets from corresponding users,

wherein the plurality of requests are associated with corresponding currency amounts; and

calculating, using a computer system, ticket prices for at least a portion of the event tickets based at least in part on;

(a) how many ticket requests were received, or

(b) how many tickets are allocated to users, or

(c) how many unallocated tickets are available, or

(d) any combination of (a), (b), or (c);

calculating, using a computer system, ticket prices for at least a portion of the event tickets, based at least in part of a central tendency of the currency amounts,

wherein the central tendency is calculated at least in part by;

calculating an average of at least a portion of the corresponding currency amounts, a median of at least a portion the corresponding currency amounts, a trimedian of at least a portion the corresponding currency amounts, a mode of at least a portion the corresponding currency amounts, and/or a mean of at least a portion the corresponding currency amounts;

transmitting over the network to one or more terminals the calculated ticket prices.

12. The method as defined in claim 11, wherein the event ticket offering is in the form of an auction.

13. The method as defined in claim 11, wherein the plurality of requests are in the form of bids.

14. The method as defined in claim 11, the method further comprising requesting a first user via a user interface to agree that currency amount that the first user is to provide for a first ticket can be adjusted based at least in part on the acts of others.

15. The system as defined in claim 11, wherein the central tendency is calculated at least in part by calculating an average of the corresponding currency amounts.

16. The system as defined in claim 11, wherein the central tendency is calculated at least in part by calculating a median of the corresponding currency amounts.

17. The system as defined in claim 11, wherein the central tendency is calculated at least in part by calculating a trimedian of the corresponding currency amounts.

18. The system as defined in claim 11, wherein the central tendency is calculated at least in part by a mode of the corresponding currency amounts.

19. The system as defined in claim 11, wherein the central tendency is calculated at least in part by calculating a mean of the corresponding currency amounts.

20. The system as defined in claim 11, wherein the central tendency is calculated at least in part by calculating a quadratic mean, a generalized mean, a weighted mean, a truncated mean, a midrange, a Winsorized mean, an exponential mean, a trimean, or a normalized mean.

21. The system as defined in claim 11, wherein the system is further configured to:

access an adjustment limit from computer readable memory, wherein the adjustment limit indicates an upper limit on a ticket price adjustment value for at least a first ticket; and

inhibit a ticket price for the first ticket from being adjusted beyond the upper limit.

22. The system as defined in claim 11, wherein the system is further configured to:

access an adjustment limit from computer readable memory, wherein the adjustment limit indicates an upper limit on a ticket price adjustment value for at least a first ticket; and

inhibit a ticket price for the first ticket from being adjusted beyond the upper limit, wherein the adjustment limit is expressed as a percentage or as a currency amount.

23. The system as defined in claim 11, wherein the system is further configured to:

store a ranking of the first plurality of requests;

store a ranking of the first plurality of tickets; and

allocate tickets to at least a portion of the corresponding users based at least in part on the ranking of the first plurality of requests and the ranking of the first plurality of tickets.