Ticket reselling using software notes

• US 20040153374A1
• Filed: 01/31/2003
• Published: 08/05/2004
• Est. Priority Date: 01/31/2003
• Status: Abandoned Application

• Current Assignee: 3M Innovative Properties Company (3M Company)
• Original Assignee: 3M Innovative Properties Company (3M Company)
• Inventors: Nelson, Kerry S.
• Application Number:
  US10/357,045
• Publication Number:
  US 20040153374A1
• Time in Patent Office: Days
• US Class Current: 705/26
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0633 Lists, e.g. purchase orders, compilation or processing
• CPC Class Codes: G06Q 30/0641 Shopping interfaces

Abstract

A network-based ticket reselling system is described that makes use of “software notes” for the reselling of tickets. The ticket reselling system generates the software notes in response to ticket data from a seller that identifies one or more tickets for resale and request data from a buyer that indicates a desire to purchase tickets for an event. A first client device may execute notepad software to access the software note on the ticket reselling system and display at least one of the software notes to the buyer for accepting or rejecting an offer to sell the tickets. A second client device may execute notepad software to access the software notes on the ticket reselling system and display at least one of the software notes to the seller for accepting or rejecting an offer to buy the tickets.

Claims

1. A method comprising:

receiving ticket data from a seller that identifies one or more tickets for resale; and

posting a software note at a ticket reselling system in response to the ticket data.

2. The method of claim 1, further comprising:

receiving request data from a buyer that identifies one or more desired tickets;

determining whether a match exists between the desired tickets and the tickets for resale; and

posting the software note based on the determination.

3. The method of claim 2, wherein posting a software note comprises posting a software note for the seller indicating an offer from the buyer to purchase the tickets.

4. The method of claim 3, further comprising generating the software note to include an offer price from the buyer.

5. The method of claim 3, further comprising generating the software note to include user inputs for rejecting and accepting the offer.

6. The method of claim 3, further comprising:

receiving a response from the seller via interaction with the software note; and

transacting the sale of the tickets from the seller to the buyer based on the response.

7. The method of claim 1, wherein posting a software note comprises posting a software note for a buyer.

8. The method of claim 7, further comprising generating the software note to include an asking price from the seller.

9. The method of claim 7, further comprising generating the software note to include a user input for rejecting and accepting the offer.

10. The method of claim 9, further comprising:

receiving a response from the seller via interaction with the user input; and

transacting the sale of the tickets from the seller to the buyer based on the response.

11. The method of claim 2, wherein posting a software note comprises:

generating a software note based on one of the ticket data and the request data;

embedding the software note within a web page; and

presenting the web page using a web server hosted by the ticket reselling system.

12. The method of claim 2, wherein at least one of the ticket data and the request data specifies a price, the method further comprising:

automatically adjusting the price; and

regenerating the software note to indicate the adjusted price.

13. The method of claim 12, wherein automatically adjusting the price comprises:

determining an amount of time until expiration of the ticket; and

automatically adjusting the price based on the amount of time.

14. The method of claim 1, wherein receiving ticket data from a seller comprises receiving ticket data from a ticket holder.

15. The method of claim 1, wherein receiving ticket data from a seller comprises receiving ticket data from a vendor.

16. The method of claim 15, further comprising:

receiving a response via user interaction with the software note;

electronically transacting the sale of the tickets from the seller to the buyer; and

distributing at least a portion of proceeds from the transaction to the vendor.

17. A computer-readable medium comprising instructions thereon to cause a programmable processor to:

receive ticket data from a seller that identifies one or more tickets for resale; and

post a software note at a ticket reselling system in response to the ticket data.

18. The computer-readable medium of claim 17, further comprising instructions to cause the processor to receive request data from a buyer that identifies one or more desired tickets, determine whether a match exists between the desired tickets and the tickets for resale, and post the software note based on the determination.

19. The computer-readable medium of claim 17, further comprising instructions to cause the processor to post a software note for the seller indicating an offer from the buyer to purchase the tickets.

20. The computer-readable medium of claim 19, further comprising instructions to cause the processor to generate the software note to include an offer price from the buyer.

21. The computer-readable medium of claim 19, further comprising instructions to cause the processor to generate the software note to include user inputs for rejecting and accepting the offer.

22. The computer-readable medium of claim 19, further comprising instructions to cause the processor to receive a response from the seller via interaction with the software note, and transact the sale of the tickets from the seller to the buyer based on the response.

23. The computer-readable medium of claim 19, further comprising instructions to cause the processor to post a software note for the buyer.

24. The computer-readable medium of claim 23, further comprising instructions to cause the processor to generate the software note to include an asking price from the seller.

25. The computer-readable medium of claim 23, further comprising instructions to cause the processor to generate the software note to include user inputs for rejecting and accepting the offer.

26. The computer-readable medium of claim 25, further comprising instructions to cause the processor to receive a response from the seller via interaction with the inputs, and transact the sale of the tickets from the seller to the buyer based on the response.

27. The computer-readable medium of claim 18, further comprising instructions to cause the processor to generate a software note based on one of the ticket data and the request data, embed the software note within a web page, and present the web page using a web server hosted by the ticket reselling system.

28. The computer-readable medium of claim 18, wherein at least one of the ticket data and the request data specifies a price, and the instructions to cause the processor to automatically adjust the price, and regenerate the software note to indicate the adjusted price.

29. The computer-readable medium of claim 18, further comprising instructions to cause the processor to determine an amount of time until the expiration of the ticket, and automatically adjust the price based on the amount of time.

30. The computer-readable medium of claim 18, further comprising instructions to cause the processor to receiving ticket data from a ticket holder.

31. The computer-readable medium of claim 18, further comprising instructions to cause the processor to receive ticket data from a vendor.

32. The computer-readable medium of claim 18, further comprising instructions to cause the processor to receive a response via user interaction with the software note, electronically transact the sale of the tickets from the seller to the buyer, and distribute at least a portion of proceeds from the transaction to the vendor.

33. A system comprising:

a database to store ticket data from a seller that identifies one or more tickets for resale; and

a server to access the ticket data and generate a software note in response to the ticket data.

34. The system of claim 33, further comprising a client device executing notepad software to access the software note on the server, and display the software note to a user.

35. The system of claim 33, wherein the database stores request data from a buyer that identifies one or more desired tickets, and the server determines whether a match exists between the desired tickets and the tickets for resale, and posts the software note based on the determination.

36. The system of claim 33, wherein the server generates a software note for the seller indicating an offer from the buyer to purchase the tickets.

37. The system of claim 36, wherein the server generates the software note to include an offer price from the buyer.

38. The system of claim 36, wherein the server generates the software note to include user inputs for rejecting and accepting the offer.

39. The system of claim 36, wherein the server receives a response from the seller via interaction with the software note, and transacts the sale of the tickets from the seller to the buyer based on the response.

40. The system of claim 35, wherein the server generates a software note for the buyer.

41. The system of claim 40, wherein the server generates the software note to include an asking price from the seller.

42. The system of claim 40, wherein the server generates the software note to include user inputs for rejecting and accepting the offer.

43. The system of claim 42, wherein the server receives a response from the seller via interaction with the inputs, and transacts the sale of the tickets from the seller to the buyer based on the response.

44. The system of claim 42, wherein the server embeds the software note within a web page, and presents the web page to a user via a web server.

45. The system of claim 33, wherein the server automatically adjusts a price for the tickets, and regenerates the software note to indicate the adjusted price.

46. The system of claim 45, wherein the server determines an amount of time until the expiration of the ticket, and automatically adjusts the price based on the amount of time.

47. The system of claim 33, wherein the server receives a response via user interaction with the software note, electronically transacts the sale of the tickets from the seller to the buyer, and distributes at least a portion of proceeds from the transaction to the vendor.

48. A system comprising:

a ticket reselling system to generate software notes in response to ticket data from a seller that identifies one or more tickets for resale and request data from a buyer that indicates a desire to purchase tickets for an event;

a first client device executing notepad software to access the software note on the ticket reselling system and display at least one of the software notes to the buyer for accepting or rejecting an offer to sell the tickets; and

a second client device executing notepad software to access the software notes on the ticket reselling system and display at least one of the software notes to the seller for accepting or rejecting an offer to buy the tickets.

49. The system of claim 48, wherein the ticket reselling system comprises:

a database to store the ticket data and the request data; and

a server to access the ticket data and the request data and generate the software notes.

50. The system of claim 49, wherein the server determines whether a match exists between the desired tickets and the tickets for resale, and generate the software notes based on the determination.