Identification of merchandise to be subsequently identified and delivered by a merchandise provider
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
exact text as granted — not AI-modified1 - 32 . (canceled)
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.
34 . 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.
35 . 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.
36 . 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.
37 . 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.
38 . (canceled)
39 . 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.
40 . The system of claim 39 , wherein the intermediary website is further configured to coordinate payment for one or more tickets to the ticketed event.
41 . 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.
42 . The system of claim 33 , wherein the triggering condition includes a user-specified time period.
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.
44 . 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.
45 . 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.
46 . (canceled)
47 . 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.
48 . 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.
49 . 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.
50 . The method of claim 43 , wherein the triggering condition includes a user-specified time period.Join the waitlist — get patent alerts
Track US2014236640A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.