# US 2014/0236640 A1 · Identification of merchandise to be subsequently identified and delivered by a merchandise provider

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

- Number: US 2014/0236640 A1
- Document ID: US20140236640A1
- Status: Published application
- Kind: A1
- Application number: 13/272,826
- Filed: 2011-10-13
- Published: 2014-08-21
- Earliest claimed: 2000-07-27
- Assignees: Union Beach, L.P.
- Inventors: David H. Tannenbaum
- Web page: https://patentgrep.com/patent/US20140236640A1

## CPC

- H04N 21/47202: {for requesting content on demand, e.g. video on demand}
- G06Q 10/02: Reservations, e.g. for tickets, services or events
- G06Q 10/0281: {for arena or stadium seating}
- G06Q 30/0613: {using intermediate agents}
- G06Q 30/0625: {by formulating product or service queries, e.g. using keywords or predefined options}
- G06Q 30/0635: {replenishment orders; recurring orders}
- H04N 5/782: on tape
- H04N 7/17327: {with deferred transmission or handling of upstream communications}
- H04N 7/17336: {Handling of requests in head-ends}
- H04N 21/2543: Billing {, e.g. for subscription services (payment schemes, architectures or protocols G06Q20/00; e-commerce G06Q30/00; arrangements for billing for the use of broadcast information or broadcast-related information H04H60/21)}
- H04N 21/47214: {for content reservation or setting reminders; for requesting event notification, e.g. of sport results or stock market (stock exchange data over packet-switching network H04L12/1804; push services over packet-switching network H04L12/1859; notification of incoming messages in packet switching networks H04L51/224)}
- H04N 21/6543: for forcing some client operations, e.g. recording {(remote booting in general G06F9/4416)}
- H04N 21/6582: {Data stored in the client, e.g. viewing habits, hardware capabilities, credit card number (arrangements where receivers interact with the broadcast H04H20/38)}
- H04N 21/4622: {Retrieving content or additional data from different sources, e.g. from a broadcast channel and the Internet (web site content organization and management for information retrieval from the Internet G06F16/958; transmission by internet of broadcast information H04H60/82; stock exchange data over packet-switching network H04L12/1804; push services including data channel over packet-switching network H04L12/1859)}
- H04N 21/482: End-user interface for programme selection
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION
- 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

Users may identify on an interactive network merchandise that they desire and merchandise providers may access the identified merchandise from time to time so as to provide merchandise that matches the identified merchandise. In one embodiment, merchandise providers may access merchandise requests from time to time and provide the requested merchandise, even if the merchandise had not been available at the time the request was initially posted. Prior to delivery of the merchandise the parties, if desired, may negotiate when and how delivery will occur, what the cost of the merchandise is and the responsibilities of each of the parties pertaining to the merchandise. The requests may be stored local to the user or at one or more central sites.

## Claims

### Claim at position 1

1-32. (canceled)

### Claim 33

A system for searching and purchasing tickets to a ticketed event, the system comprising:
a server in communication with a search engine, the search engine configured to receive one or more search queries associated with a ticketed event and to search one or more databases for information associated with the ticketed event; and
a processor in communication with the search engine, the processor configured to:
instruct the search engine to perform a search of the one or more databases for information associated with the ticketed event, thereby generating a search result;
determine whether a search result generated by the search engine indicates that any of at least one scheduled location for the ticketed event matches a desired location; and
in response to the search result indicating that none of the at least one scheduled location for the ticketed event matches the desired location, instruct the search engine to continue searching the one or more databases until a triggering condition is satisfied.

### Claim 34 (depends on 33)

The system of claim 33, further comprising:
a delivery unit in communication with the processor, the processor further configured to communicate the search result to the delivery unit in response to the search result indicating that any of the at least one scheduled location for the ticketed event matches the desired location, wherein the delivery unit is configured to deliver a message to a user indicating that the ticketed event is scheduled for the desired location.

### Claim 35 (depends on 34)

The system of claim 34, wherein the delivery unit is further configured to receive a response to the message, the response indicating whether the user would like to purchase one or more tickets to the ticketed event.

### Claim 36 (depends on 34)

The system of claim 34, wherein the server is in communication with a memory unit, wherein the memory unit is configured to store the one or more search queries associated with the ticketed event, and wherein the search engine is configured to access the one or more search queries stored in the memory unit.

### Claim 37 (depends on 36)

The system of claim 36, wherein the memory unit is configured to be accessible by a third-party provider to provide access to the third-party provider to the one or more search queries, and wherein the delivery unit is further configured to transmit a message from the third-party provider to the user regarding the ticketed event.

### Claim 38

(canceled)

### Claim 39 (depends on 33)

The system of claim 33, further comprising:
an intermediary website in communication with the processor, the intermediary website configured to receive one or more messages associated with the ticketed event from a ticket provider and to communicate the one or more messages to a user.

### Claim 40 (depends on 39)

The system of claim 39, wherein the intermediary website is further configured to coordinate payment for one or more tickets to the ticketed event.

### Claim 41 (depends on 33)

The system of claim 33, wherein the triggering condition includes the search result indicating that any of the at least one scheduled location for the ticketed event matches the desired location.

### Claim 42 (depends on 33)

The system of claim 33, wherein the triggering condition includes a user-specified time period.

### Claim 43

A method of searching and purchasing items, the method comprising:
receiving, via a server in communication with a processor, one or more search queries associated with a ticketed event;
causing a search engine, in communication with the processor, to search one or more databases for information associated with the ticketed event, thereby generating a search result indicating whether any of at least one scheduled location for the ticketed event matches a desired location; and
in response to the search result indicating that none of the at least one scheduled location for the ticketed event matches the desired location, instructing the search engine to continue searching the one or more databases until a triggering condition is satisfied.

### Claim 44 (depends on 43)

The method of claim 43, further comprising:
communicating, via the server, a message to a user indicating that one or more tickets to the ticketed event are available for purchase.

### Claim 45 (depends on 44)

The method of claim 44, further comprising:
receiving, via the server, a response to the message indicating whether the user would like to purchase the one or more tickets.

### Claim 46

(canceled)

### Claim 47 (depends on 43)

The method of claim 43, further comprising:
storing the one or more search queries in a memory unit, and wherein the receiving step further comprises accessing, via the processor, the memory unit for at least one of the one or more search queries.

### Claim 48 (depends on 43)

The method of claim 43, further comprising:
receiving, via the server, from a ticket provider a message regarding the ticketed event; and
communicating, via the server, the message regarding the ticketed event to a user.

### Claim 49 (depends on 43)

The method of claim 43, wherein the triggering condition includes the search result indicating that any of the at least one scheduled location for the ticketed event matches the desired location.

### Claim 50 (depends on 43)

The method of claim 43, wherein the triggering condition includes a user-specified time period.
