# US 2012/0084165 A1 · Systems and methods for queuing access to network resources

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0084165 A1
- Document ID: US20120084165A1
- Status: Published application
- Kind: A1
- Application number: 13/323,251
- Filed: 2011-12-12
- Published: 2012-04-05
- Earliest claimed: 2003-12-16
- Assignees: Ticketmaster
- Inventors: Shigeki Hirose; Dennis Denker; Adam Sussman; Craig McLane; Sean Moriarty
- Web page: https://patentgrep.com/patent/US20120084165A1

## CPC

- G06Q 30/0601: Electronic shopping [e-shopping]
- G06Q 10/02: Reservations, e.g. for tickets, services or events
- G06Q 10/021: {Re-booking existing reservations}
- G06Q 10/027: {Changing the assignment of an existing reservation}
- G06Q 30/08: Auctions
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## 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

### Claim 1

A ticketing system configured to process queued requests for event tickets, the ticketing system comprising:
a network interface configured to communicate with user terminals submitting ticket-related requests;
one or more computing devices;
non-transitory media storing program instructions configured to cause the one or more computing devices to perform operations comprising:
receiving ticket-related requests via the network interface, the ticket-related requests including a ticket-related request of a first type;
queuing at least a portion of the received ticket-related requests;
determining if a current resource pool size for the first type of ticket-related request is below a first threshold;
if the current resource pool size for the first type of ticket-related request is below the first threshold,
causing additional resources to be allocated to the current resource pool for the first type of ticket-related request to service additional ticket-related requests of the first type received over the network interface;
determining if the current resource pool size for the first type of ticket-related request is above a second threshold; and
at least partly in response to determining that the current resource pool size for the first type of ticket-related request is above a second threshold,
causing a reduction of available resources from the current resource pool.

### Claim 2 (depends on 1)

The ticketing system as defined in claim 1, the operations further comprising:
receiving a first plurality of ticket-related requests of the first type, wherein the first type is a request for a ticket;
receiving a second plurality of requests of a second type, wherein the second type is a help request or an account information request;
if the second plurality of requests of the second type is consuming less than a first amount of resources, then assigning a new request of the second type a first resource prior to assigning the first resource to a new request of the first type; and
if the second plurality of requests of the second type is consuming more than a second amount of resources, then assigning a new request of the first type the first resource prior to assigning the first resource to a new request of the second type.

### Claim 3 (depends on 1)

The ticketing system as defined in claim 1, wherein the first type of ticket-related request is a request for an event ticket.

### Claim 4 (depends on 1)

The ticketing system as defined in claim 1, wherein the first type of ticket-related request is a request for account information.

### Claim 5 (depends on 1)

The ticketing system as defined in claim 1, wherein the first type of ticket-related request is a help request.

### Claim 6 (depends on 1)

The ticketing system as defined in claim 1, wherein an amount of resources allocated to the current resource pool is determined at least in part using a geometric mean equation including at least a desired ticketing system load value and a current ticketing system load value.

### Claim 7 (depends on 1)

The ticketing system as defined in claim 1, the operations further comprising calculating a value corresponding to how many new ticket-related requests are to be handled at a given time period by the ticketing system based at least in part on:
a desired ticketing system load value,
a current ticketing system load value,
a current number of ticket-related requests, and
a maximum request increase rate value.

### Claim 8 (depends on 1)

The ticketing system as defined in claim 1, the operations further comprising calculating a value corresponding to how many ticket-related requests of the first type are to be handled at a given time period based at least in part on:
a desired ticketing system load value,
a current ticketing system load value, and
a current number of ticket-related requests.

### Claim 9 (depends on 1)

The ticketing system as defined in claim 1, wherein an amount of resources allocated to the current resource pool is based at least in part on a current system load and a desired system load.

### Claim 10 (depends on 1)

The ticketing system as defined in claim 1, the operations further comprising adjusting an availability of resources to cause, at least in part, a quantity of connections with user terminals submitting ticket-related requests to remain within a first range.

### Claim 11 (depends on 1)

The ticketing system as defined in claim 1, the operations further comprising adjusting an availability of resources based at least in part on a response time of the ticketing system to one or more ticket-related requests.

### Claim 12 (depends on 1)

The ticketing system as defined in claim 1, the operations further comprising inhibiting an allocation of additional resources to the first type of ticket-related request at least partly in response to determining that servicing current ticket-related requests of the first type is consuming more than a first preset number of resources.

### Claim 13 (depends on 1)

The ticketing system as defined in claim 1, the operations further comprising allocating a next available resource to a first ticket-related request of the first type from the current resource pool at least partly in response to determining that servicing current ticket-related requests of the first type is consuming less than a first preset number of resources from the current resource pool.

### Claim 14 (depends on 1)

The ticketing system as defined in claim 1, the operations further comprising allocating a next available resource to a first ticket-related request of a second type from the current resource pool at least partly in response to determining that ticket-related requests of the second type is consuming the least amount of resources from the current resource pool relative to ticket-related requests of other types.

### Claim 15 (depends on 1)

The ticketing system as defined in claim 1, the operations further comprising allocating a next available resource to a first ticket-related request of a second type from the current resource pool at least partly in response to determining that ticket-related requests of the second type is consuming less than a preset amount.

### Claim 16

A method of managing a pool of event ticket-related resources associated with a queue including event ticket requests, the method comprising:
receiving, by a ticketing system including one or more computing devices, ticket-related requests, the ticket-related requests including a ticket-related request of a first type;
queuing, by the ticketing system, at least a portion of the received ticket-related requests, including a ticket-related request of a first type;
determining, by the ticketing system, if a current resource pool size for the first type of ticket-related request is below a first threshold;
if the current resource pool size for the first type of ticket-related request is below the first threshold,
causing, by the ticketing system, more resources to be allocated to the current resource pool for the first type of ticket-related request;
determining, by the ticketing system, if the current resource pool size for the first type of ticket-related request is above a second threshold; and
at least partly in response to determining that the current resource pool size for the first type of ticket-related request is above a second threshold,
causing, by the ticketing system, a reduction of available resources from the current resource pool.

### Claim 17 (depends on 16)

The method as defined in claim 16, the method comprising:
receiving a first plurality of ticket-related requests of the first type, wherein the first type is a request for a ticket;
receiving a second plurality of requests of a second type, wherein the second type is a help request or an account information request;
if the second plurality of requests of the second type is consuming less than a first amount of resources, then assigning a new request of the second type a first resource prior to assigning the first resource to a new request of the first type; and
if the second plurality of requests of the second type is consuming more than a second amount of resources, then assigning a new request of the first type the first resource prior to assigning the first resource to a new request of the second type.

### Claim 18 (depends on 16)

The method a defined in claim 16, wherein the first type of ticket-related request is a request for an event ticket.

### Claim 19 (depends on 16)

The method a defined in claim 16, wherein the first type of ticket-related request is a request for account information.

### Claim 20 (depends on 16)

The method a defined in claim 16, wherein the first type of ticket-related request is a help request.

### Claim 21 (depends on 16)

The method a defined in claim 16, wherein an amount of resources allocated to the current resource pool is determined at least in part using a geometric mean equation including at least a desired ticketing system load value and a current ticketing system load value.

### Claim 22 (depends on 16)

The method a defined in claim 16, the method further comprising calculating a value corresponding to how many new ticket-related requests are to be handled at a given time period by the ticketing system based at least in part on:
a desired ticketing system load value,
a current ticketing system load value,
a current number of ticket-related requests, and
a maximum request increase rate value.

### Claim 23 (depends on 16)

The method a defined in claim 16, the method further comprising calculating a value corresponding to how many ticket-related requests of the first type are to be handled at a given time period based at least in part on:
a desired ticketing system load value,
a current ticketing system load value, and
a current number of ticket-related requests.

### Claim 24 (depends on 16)

The method a defined in claim 16, wherein an amount of resources allocated to the current resource pool is based at least in part on a current system load and a desired system load.

### Claim 25 (depends on 16)

The method a defined in claim 16, the method further comprising adjusting an availability of resources to cause, at least in part, a quantity of connections with user terminals submitting ticket-related requests to remain within a first range.

### Claim 26 (depends on 16)

The method a defined in claim 16, the method further comprising adjusting an availability of resources based at least in part on a response time of the ticketing system to one or more ticket-related requests.

### Claim 27 (depends on 16)

The method a defined in claim 16, the method further comprising inhibiting an allocation of additional resources to the first type of ticket-related request at least partly in response to determining that servicing current ticket-related requests of the first type is consuming more than a first preset number of resources.

### Claim 28 (depends on 16)

The method a defined in claim 16, the method further comprising allocating a next available resource to a first ticket-related request of the first type from the current resource pool at least partly in response to determining that servicing current ticket-related requests of the first type is consuming less than a first preset number of resources from the current resource pool.

### Claim 29 (depends on 16)

The method a defined in claim 16, the method further comprising allocating a next available resource to a first ticket-related request of a second type from the current resource pool at least partly in response to determining that ticket-related requests of the second type is consuming the least amount of resources from the current resource pool relative to ticket-related requests of other types.

### Claim 30 (depends on 16)

The method a defined in claim 16, the method further comprising allocating a next available resource to a first ticket-related request of a second type from the current resource pool at least partly in response to determining that ticket-related requests of the second type is consuming less than a preset amount.

### Claim 31

Non-transitory media storing program instructions configured to cause a computing system including one or more computing device to perform operations comprising:
receiving a first plurality of ticket-related requests;
queuing at least a portion of the first plurality of ticket-related requests, including a ticket-related request of a first type;
determining if a current resource pool size for the first type of ticket-related request is below a first threshold;
if the current resource pool size for the first type of ticket-related request is below the first threshold,
causing additional resources to be allocated to the current resource pool for the first type of ticket-related request to service additional ticket-related requests of the first type;
determining if the current resource pool size for the first type of ticket-related request is above a second threshold; and
at least partly in response to determining that the current resource pool size for the first type of ticket-related request is above a second threshold,
causing a reduction of available resources from the current resource pool.

### Claim 32 (depends on 31)

The non-transitory media as defined in claim 31, the operations further comprising:
receiving a first plurality of ticket-related requests of the first type, wherein the first type is a request for a ticket;
receiving a second plurality of requests of a second type, wherein the second type is a help request or an account information request;
if the second plurality of requests of the second type is consuming less than a first amount of resources, then assigning a new request of the second type a first resource prior to assigning the first resource to a new request of the first type; and
if the second plurality of requests of the second type is consuming more than a second amount of resources, then assigning a new request of the first type the first resource prior to assigning the first resource to a new request of the second type.

### Claim 33 (depends on 31)

The non-transitory media as defined in claim 31, wherein the first type of ticket-related request is a request for an event ticket.

### Claim 34 (depends on 31)

The non-transitory media as defined in claim 31, wherein the first type of ticket-related request is a request for account information.

### Claim 35 (depends on 31)

The non-transitory media as defined in claim 31, wherein the first type of ticket-related request is a help request.

### Claim 36 (depends on 31)

The non-transitory media as defined in claim 31, wherein an amount of resources allocated to the current resource pool is determined at least in part using a geometric mean equation including at least a desired ticketing system load value and a current ticketing system load value.

### Claim 37 (depends on 31)

The non-transitory media as defined in claim 31, the operations further comprising calculating a value corresponding to how many new ticket-related requests are to be handled at a given time period by The non-transitory media based at least in part on:
a desired ticketing system load value,
a current ticketing system load value,
a current number of ticket-related requests, and
a maximum request increase rate value.

### Claim 38 (depends on 31)

The non-transitory media as defined in claim 31, the operations further comprising calculating a value corresponding to how many ticket-related requests of the first type are to be handled at a given time period based at least in part on:
a desired ticketing system load value,
a current ticketing system load value, and
a current number of ticket-related requests.

### Claim 39 (depends on 31)

The non-transitory media as defined in claim 31, wherein an amount of resources allocated to the current resource pool is based at least in part on a current system load and a desired system load.

### Claim 40 (depends on 31)

The non-transitory media as defined in claim 31, the operations further comprising adjusting an availability of resources to cause, at least in part, a quantity of connections with user terminals submitting ticket-related requests to remain within a first range.

### Claim 41 (depends on 31)

The non-transitory media as defined in claim 31, the operations further comprising adjusting an availability of resources based at least in part on a response time of The non-transitory media to one or more ticket-related requests.

### Claim 42 (depends on 31)

The non-transitory media as defined in claim 31, the operations further comprising inhibiting an allocation of additional resources to the first type of ticket-related request at least partly in response to determining that servicing current ticket-related requests of the first type is consuming more than a first preset number of resources.

### Claim 43 (depends on 31)

The non-transitory media as defined in claim 31, the operations further comprising allocating a next available resource to a first ticket-related request of the first type from the current resource pool at least partly in response to determining that servicing current ticket-related requests of the first type is consuming less than a first preset number of resources from the current resource pool.

### Claim 44 (depends on 31)

The non-transitory media as defined in claim 31, the operations further comprising allocating a next available resource to a first ticket-related request of a second type from the current resource pool at least partly in response to determining that ticket-related requests of the second type is consuming the least amount of resources from the current resource pool relative to ticket-related requests of other types.

### Claim 45 (depends on 31)

The non-transitory media as defined in claim 31, the operations further comprising allocating a next available resource to a first ticket-related request of a second type from the current resource pool at least partly in response to determining that ticket-related requests of the second type is consuming less than a preset amount.
