SYSTEMS AND METHODS FOR QUEUING ACCESS TO NETWORK RESOURCES

• US 20120078668A1
• Filed: 12/06/2011
• Published: 03/29/2012
• Est. Priority Date: 12/16/2003
• Status: Active Grant

• Current Assignee: Live Nation Entertainment Incorporated
• Original Assignee: Ticketmaster LLC (Live Nation Entertainment Incorporated)
• Inventors: Hirose, Shigeki, Denker, Dennis, Sussman, Adam, McLane, Craig, Moriarty, Sean
• Granted Patent: US 8,463,630 B2
• Time in Patent Office: Days
• US Class Current: 705/5
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/08 Auctions
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters

Abstract

One embodiment of the present invention provides apparatus and methods for queuing access by large numbers of Internet or other network-based users to networked systems and resources with limited capacity. In one example embodiment, a queuing system provides user access to network resources, such as that of a ticketing system. A ticket queue queues a request received from a client system. A request processing module causes the client system to repeatedly transmit messages to the system during a first period, and in response to determining that the client system has ceased transmitting messages during the first period, the request is remove from the queue and/or cause the request goes unfulfilled.

Claims

1. An electronic ticketing system, comprising:

a computing system including one or more computing device;

non-transitory memory storing one or more modules, that when executed by the computing system, cause the computing system to perform operations, comprising;

providing over a network a first ticketing Web page form for display on a first client system to a user;

determining if the user has a ticket in a reserved state by accessing information stored in computer readable memory;

retrieving from computer readable memory a first value related to an amount of time the user has to complete the first ticketing Web page form before expiration of the ticket reservation;

using the first value, providing an indication to be displayed to the user via the first client system as to the amount of time the user to complete the first ticketing Web page form before expiration of the ticket reservation;

determining if the user has failed to timely complete the first ticketing Web page form; and

at least partly in response to a determination that the user has failed to timely complete the first ticketing Web page form,

causing a reservation expiration notice to be presented to the user by the first client system.

2. The system as defined in claim 1, the operations further comprising:

providing for display to the user a second ticketing Web page form;

retrieving from computer readable memory a second value related to an amount of time the user has to complete the second ticketing Web page form before expiration of the ticket reservation,

wherein the second value, related to the amount of time the user has to complete the second ticketing Web page form before expiration of the ticket reservation, is different than the first value, related to the amount of time the user has to complete the first ticketing Web page form before expiration of the ticket reservation;

providing an indication to the user as to the amount of time the user to complete the second ticketing Web page form before expiration of the ticket reservation.

3. The system as defined in claim 1, wherein the first ticketing Web page form is a ticket delivery page configured to enable the user to specify how the ticket is to be delivered to the user.

4. The system as defined in claim 1, wherein the first ticketing Web page form is an account information page.

5. The system as defined in claim 1, wherein the first ticketing Web page form is a payment page configured to enable the user to specify a form of payment to be used.

6. The system as defined in claim 1, wherein the reservation expiration notice is a Web page provided for display on the first client device.

7. The system as defined in claim 1, wherein the first value is based in part on a first computer system load.

8. The system as defined in claim 1, the operations further comprising:

receiving a ticket request transmitted from a second client system associated with a second user;

transmitting an instruction to the second client system, the instruction indicating that the second client system is to periodically transmit messages to the computer system during a first time period;

determining if the second client system is transmitting messages at greater than the first frequency during the first period; and

based at least in part on determining that the second client system is transmitting messages at greater than a first frequency during the first time period, causing the request to go unfulfilled.

9. The system as defined in claim 1, wherein the first client device is a cellular phone.

10. A method of managing ticketing interfaces, comprising:

providing over a network, by a computer system including at least one computing device, a first ticketing form for display on a first client system to a user;

determining by the computing system if the user has a ticket in a reserved state by accessing information stored in computer readable memory;

retrieving from computer readable memory a first value related to an amount of time the user has to complete the first ticketing form before expiration of the ticket reservation;

using the first value, providing an indication to be displayed to the user via the first client system as to the amount of time the user to complete the first ticketing form before expiration of the ticket reservation;

determining by the computer system if the user has failed to timely complete the first ticketing form;

at least partly in response to a determination by the computer system that the user has failed to timely complete the first ticketing form,

causing a reservation expiration notice to be presented to the user by the first client system.

11. The method as defined in claim 10, the method further comprising:

providing for display to the user a second ticketing form;

retrieving from computer readable memory a second value related to an amount of time the user has to complete the second ticketing form before expiration of the ticket reservation,

wherein the second value, related to the amount of time the user has to complete the second ticketing form before expiration of the ticket reservation, is different than the first value, related to the amount of time the user has to complete the first ticketing form before expiration of the ticket reservation; and

providing an indication to the user as to the amount of time the user to complete the second ticketing form before expiration of the ticket reservation.

12. The method as defined in claim 11, wherein the first ticketing form is a ticket delivery page configured to enable the user to specify how the ticket is to be delivered to the user.

13. The method as defined in claim 11, wherein the first ticketing form is an account information page.

14. The method as defined in claim 11, wherein the first ticketing form comprises a Web page.

15. The method as defined in claim 11, wherein the first ticketing form is a payment page configured to enable the user to specify a form of payment to be used.

16. The method as defined in claim 11, wherein the notice is provided for display on first client device.

17. The method as defined in claim 11, wherein the first value is based in part on a first computer system load.

18. The method as defined in claim 11, the method further comprising:

receiving at the computer system a ticket request transmitted from a second client system associated with a second user;

transmitting an instruction from the computer system to the second client system, the instruction indicating that the second client system is to periodically transmit messages to the computer system during a first time period;

determining if the second client system is transmitting messages at greater than the first frequency during the first period; and

based at least in part on determining that the second client system is transmitting messages at greater than a first frequency during the first time period, causing the request to go unfulfilled.

19. Non-transitory memory storing programmatic instructions, that when executed by a computing system, cause the computing system to perform operations, comprising:

providing over a network a first ticketing form for display on a first client system to a user;

determining if the user has a ticket in a reserved state by accessing information stored in computer readable memory;

retrieving from computer readable memory a first value related to an amount of time the user has to complete the first ticketing form before expiration of the ticket reservation;

using the first value, providing an indication to be displayed to the user via the first client system as to the amount of time the user to complete the first ticketing form before expiration of the ticket reservation;

determining if the user has failed to timely complete the first ticketing form; and

at least partly in response to a determination that the user has failed to timely complete the first ticketing form,

causing a reservation expiration notice to be presented to the user by the first client system.

20. The non-transitory memory as defined in claim 20, the operations further comprising:

providing for display to the user a second ticketing form;

retrieving from computer readable memory a second value related to an amount of time the user has to complete the second ticketing form before expiration of the ticket reservation,

wherein the second value, related to the amount of time the user has to complete the second ticketing form before expiration of the ticket reservation, is different than the first value, related to the amount of time the user has to complete the first ticketing form before expiration of the ticket reservation; and

providing an indication to the user as to the amount of time the user to complete the second ticketing form before expiration of the ticket reservation.

21. The non-transitory memory as defined in claim 20, wherein the first ticketing form is a ticket delivery page configured to enable the user to specify how the ticket is to be delivered to the user.

22. The non-transitory memory as defined in claim 20, wherein the first ticketing form is an account information page.

23. The non-transitory memory as defined in claim 20, wherein the first ticketing form is a payment page configured to enable the user to specify a form of payment to be used.

24. The non-transitory memory as defined in claim 20, wherein the first ticketing form comprises a Web page.

25. The non-transitory memory as defined in claim 20, wherein the reservation expiration notice is a provided for display on the first client device.

26. The non-transitory memory as defined in claim 20, wherein the first value is based in part on a first computer system load.

27. The non-transitory memory as defined in claim 20, the operations further comprising:

receiving a ticket request transmitted from a second client system associated with a second user;

transmitting an instruction to the second client system, the instruction indicating that the second client system is to periodically transmit messages to the computer system during a first time period;

determining if the second client system is transmitting messages at greater than the first frequency during the first period; and

based at least in part on determining that the second client system is transmitting messages at greater than a first frequency during the first time period, causing the request to go unfulfilled.