# US 2010/0169130 A1 · System and methods for prioritizing and processing updated inventory information for event listings

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

- Number: US 2010/0169130 A1
- Document ID: US20100169130A1
- Status: Published application
- Kind: A1
- Application number: 12/346,981
- Filed: 2008-12-31
- Published: 2010-07-01
- Earliest claimed: 2008-12-31
- Assignees: Stubhub, Inc.
- Inventors: Charles Fineman; Mats G. Nilsson
- Web page: https://patentgrep.com/patent/US20100169130A1

## CPC

- G06Q 10/02: Reservations, e.g. for tickets, services or events
- G06Q 10/021: {Re-booking existing reservations}
- G06Q 10/0281: {for arena or stadium seating}
- G06Q 30/06: Buying, selling or leasing transactions
- 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

A system and methods for prioritizing and processing updated inventory information for event listings are described. In one embodiment, a network-based system may receive updated ticket information from a seller for multiple event listings, categorize the updated ticket information from the seller by event, prioritize event categories comprising updated ticket information in accordance with a prioritization policy, and process a prioritized event category comprising updated ticket information for a particular event listing out-of-order with respect to one or more other event categories comprising previously-received updated ticket information for other event listings. Other embodiments are described and claimed.

## Claims

### Claim 1

A computer-implemented method comprising:
receiving updated ticket information from a seller for multiple event listings at a network-based system;
categorizing the updated ticket information from the seller by event;
prioritizing event categories comprising updated ticket information in accordance with a prioritization policy; and
processing a prioritized event category comprising updated ticket information for a particular event listing out-of-order with respect to one or more other event categories comprising previously-received updated ticket information for other event listings.

### Claim 2 (depends on 1)

The method of claim 1, wherein the prioritization policy ensures that multiple updates for a specific event listing are processed in order according to time received by the network-based system.

### Claim 3 (depends on 1)

The method of claim 1, wherein the prioritization policy is based on event dates and ensures that updated ticket information for an event having an event date occurring within a certain threshold time period is processed ahead of updated ticket information for events having later-occurring event dates.

### Claim 4 (depends on 1)

The method of claim 1, wherein the prioritization policy is based on on-sale dates and ensures that updated ticket information for an event having an on-sale date occurring within a certain time period is processed ahead of updated ticket information for events having on-sale dates occurring outside of the certain time period.

### Claim 5 (depends on 4)

The method of claim 4, wherein the certain time period comprises a high-activity time period for ticket sales.

### Claim 6 (depends on 1)

The method of claim 1, wherein:
the prioritization policy is based on whether the updated ticket information is deleting ticket inventory, adding ticket inventory, or updating ticket details; and
the prioritization policy ensures that updated ticket information that deletes ticket inventory for an event is processed ahead of updated ticket information that adds ticket inventory or updates ticket details.

### Claim 7 (depends on 1)

The method of claim 1, wherein the prioritization policy is based on a priority level of the seller and ensures that inventory updates from higher-priority level sellers are processed ahead of inventory updates from lower-priority level sellers.

### Claim 8 (depends on 7)

The method of claim 7, wherein the priority level of the seller is based on one or more of number of listings, volume of sales, generated commission, feedback from buyers, and a paid premium.

### Claim 9 (depends on 1)

The method of claim 1, further comprising
matching updated inventory information for an event against events recognized by the network-based system;
creating a placeholder for an unmatched event; and
submitting a mapping request for the unmatched event.

### Claim 10 (depends on 9)

The method of claim 9, further comprising re-parenting the updated inventory information or adding an alias to an event when the placeholder is mapped to an event.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
matching updated inventory information for a venue against venues recognized by the network-based system;
creating a placeholder for an unmatched venue; and
submitting a mapping request for the unmatched venue.

### Claim 12 (depends on 1)

The method of claim 1, further comprising generating a ticket identifier in the event that the updated ticket information received from a seller does not comprise a ticket identifier.

### Claim 13

A computer-readable storage medium comprising executable computer program instructions that when executed enable a computer system to:
receive updated ticket information from a seller for multiple event listings at a network-based system;
categorize the updated ticket information from the seller by event;
prioritize event categories comprising updated ticket information in accordance with a prioritization policy; and
process a prioritized event category comprising updated ticket information for a particular event listing out-of-order with respect to one or more other event categories comprising previously-received updated ticket information for other event listings.

### Claim 14 (depends on 13)

The computer-readable storage medium of claim 13, wherein the prioritization policy ensures that multiple updates for a specific event listing are processed in order according to time received by the network-based system.

### Claim 15 (depends on 13)

The computer-readable storage medium of claim 13, wherein the prioritization policy is based on one or more of event dates, on-sale dates, and a priority level of the seller.

### Claim 16 (depends on 13)

The computer-readable storage medium of claim 13, wherein the prioritization policy is based on whether updated ticket information is deleting ticket inventory, adding ticket inventory, or updating ticket details.

### Claim 17 (depends on 13)

The computer-readable storage medium of claim 13, further comprising executable computer program instructions to:
match updated ticket information for an event against events recognized by the network-based system;
create a placeholder for an unmatched event; and
submit a mapping request for the unmatched event.

### Claim 18 (depends on 13)

The computer-readable storage medium of claim 13, further comprising executable computer program instructions to:
match updated inventory information for a venue against venues recognized by the network-based system;
create a placeholder for an unmatched venue; and
submit a mapping request for the unmatched venue.

### Claim 19 (depends on 18)

The computer-readable storage medium of claim 18, further comprising executable computer program instructions to generate a ticket identifier in the event that the updated ticket information received from a seller does not comprise a ticket identifier.

### Claim 20

A network-based system comprising:
one or more servers to receive updated ticket information from a seller for multiple event listings, categorize the updated ticket information from the seller by event, prioritize event categories comprising updated ticket information in accordance with a prioritization policy, and process a prioritized event category comprising updated ticket information for a particular event listing out-of-order with respect to one or more other event categories comprising previously-received updated ticket information for other event listings.
