Venue-related multi-media management, streaming, online ticketing, and electronic commerce techniques implemented via computer networks and mobile devices

• US 9,218,413 B2
• Filed: 01/09/2015
• Issued: 12/22/2015
• Est. Priority Date: 06/13/2011
• Status: Active Grant

• Current Assignee: Opus Deli, Inc.
• Original Assignee: Opus Deli, Inc.
• Inventors: Skeen, Wayne Donald Maddock, Ross, Christopher Thomas, Cockrill, Howard Gregg, Mertz, Sara Anne, Smith, Matthew Paul, Mayeri, David Mendel
• Primary Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US14/593,422
• Publication Number:
  US 20150120767A1
• Time in Patent Office: 347 Days
• Field of Search: 707/705, 707/706, 707/805, 709/203, 705/1.1, 705/5, 705/6, 705/7.13, 705/14.23
• US Class Current: 1/1
• CPC Class Codes: G06F 16/168 Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs query results presentation G06F16/156
• CPC Class Codes: G06F 16/242 Query formulation
• CPC Class Codes: G06F 16/335 Filtering based on additional data, e.g. user or group profiles filtering in web context G06F16/9535, G06F16/9536
• CPC Class Codes: G06F 16/639 using playlists
• CPC Class Codes: G06F 16/686 using information manually generated, e.g. tags, keywords, comments, title or artist information, time, location or usage information, user ratings
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 10/06311 Scheduling, planning or task assignment for a person or group
• CPC Class Codes: G06Q 20/045 using payment protocols involving tickets
• CPC Class Codes: G06Q 20/0457 the tickets being sent electronically
• CPC Class Codes: G06Q 20/047 using payment protocols involving electronic receipts
• CPC Class Codes: G06Q 20/201 Price look-up processing, e.g. updating
• CPC Class Codes: G06Q 20/384 using social networks
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 30/0222 During e-commerce, i.e. online transactions
• CPC Class Codes: G06Q 30/0258 Registration
• CPC Class Codes: G06Q 30/0259 based on store location
• CPC Class Codes: G06Q 30/0261 based on user location
• CPC Class Codes: G06Q 30/0263 based upon Internet or website rating
• CPC Class Codes: G06Q 30/0264 based upon schedule
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: H04L 65/612 : for unicast
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04N 21/00 : Selective content distribution, e.g. interactive television or video on demand [VOD] real-time bi-directional transmission of motion video data H04N7/14 ; broadcast or conference over packet switching networks H04L12/18
• CPC Class Codes: H04N 21/252 : Processing of multiple end-users' preferences to derive collaborative data
• CPC Class Codes: H04N 21/25891 : being end-user preferences retrieval of video data in a video database based on user preferences G06F16/739; arrangements for recognizing users' preferences H04H60/46; user profiles in network data switching protocols H04L67/306; processing of user preferences or user profiles in wireless networks H04W8/18
• CPC Class Codes: 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
• CPC Class Codes: H04N 21/4725 : using interactive regions of the image, e.g. hot spots details of information retrieval from the Internet by using URLs G06F16/955; processing chained hypermedia data for information retrieval G06F16/94
• CPC Class Codes: H04N 21/4755 : for defining user preferences, e.g. favourite actors or genre retrieval personalisation and generation of user profiles for the retrieval of video data G06F16/739; user profiles in network data switching protocols H04L67/306
• CPC Class Codes: H04N 21/47815 : Electronic shopping payment schemes, payment architectures or payment protocols for electronic shopping systems G06Q20/12
• CPC Class Codes: H04N 21/4788 : communicating with other users, e.g. chatting arrangements for providing for computer conferences, e.g. chat rooms, to substation in data switching networks H04L12/1813; distributed application using peer-to-peer [P2P] networks H04L67/104
• CPC Class Codes: H04N 21/4825 : using a list of items to be played back in a given order, e.g. playlists
• CPC Class Codes: H04N 21/4826 : using recommendation lists, e.g. of programs or channels sorted out according to their score
• CPC Class Codes: H04N 21/4828 : for searching program descriptors retrieval of video data G06F16/739
• CPC Class Codes: Y10S 707/944 : Business related
• CPC Class Codes: Y10S 707/99943 : Generating database or data structure, e.g. via user interface

Abstract

Various aspects described or referenced herein are directed to different methods, systems, and computer program products relating to multi-media management and streaming techniques implemented over a computer network, including, for example, one or more features and/or functions relation to one or more of the following (or combinations thereof): venue-based streaming radio stations, mobile user graphical user interfaces, creation and streaming of dynamic streaming radio stations based on a user'"'"'s geolocation, ticketing and reservations, etc.

Claims

1. A computer implemented method for facilitating automated conditional purchasing of entertainment event tickets via a computer network, the method comprising causing at least one processor to execute a plurality of instructions for:

causing at least one component of the computer network to identify a first upcoming live performance of a first artist or band (“

artist/band”

) which is scheduled to be performed in a first geographic region;

causing at least one component of the computer network to generate, using the first ticketing information, a first set of instructions for causing a Ticketing graphical user interface (“

Ticketing GUI”

) to be displayed at an end user'"'"'s device, wherein the first set of instructions include instructions for configuring the Ticketing GUI to enable a first end user to initiate a ticket reservation invitation transaction for inviting at least one identified recipient to accept at least one reserved ticket for the first upcoming live performance;

causing at least one component of the computer network to notify the at least one identified recipient of the ticket reservation invitation transaction;

causing at least one component of the computer network to monitor the ticket reservation invitation transaction in order to determine if the at least one identified recipient has accepted ticket reservation invitation; and

if it is determined that the at least one identified recipient has accepted the ticket reservation invitation, automatically causing at least one component of the computer network to fund at least one ticket purchase transaction relating to a purchase of at least one ticket for the first upcoming live performance.

2. The computer implemented method of claim 1 wherein the funding of the at least one ticket purchase transaction includes causing at least one component of the computer network to automatically fund a first ticket purchase transaction relating to a purchase of a first ticket for the first end user for the first upcoming live performance.

3. The computer implemented method of claim 1 wherein the funding of the at least one ticket purchase transaction includes:

includes causing at least one component of the computer network to automatically fund a first ticket purchase transaction relating to a purchase of a first ticket for the first end user for the first upcoming live performance; and

includes causing at least one component of the computer network to automatically fund a second ticket purchase transaction relating to a purchase of a second ticket for the at least one identified recipient for the first upcoming live performance.

4. The computer implemented method of claim 1 wherein the funding of the at least one ticket purchase transaction includes causing at least one component of the computer network to automatically fund a plurality of ticket purchase transactions for the first upcoming live performance relating to purchase of tickets for the first end user and for the at least one identified recipient.

5. The computer implemented method of claim 1 further comprising causing the at least one processor to execute additional instructions for:

causing the at least one reserved ticket associated with the ticket reservation invitation transaction to automatically expire in response to determining that a first amount of time has elapsed without detecting confirmation of the at least one identified recipient'"'"'s acceptance of the at least one reserved ticket.

6. The computer implemented method of claim 1 further comprising causing the at least one processor to execute additional instructions for:

causing at least one component of the computer network to receive a first set of user input instructions, the first set of user input instructions being generated from the end user'"'"'s device in response to user interaction with the Ticketing GUI, the first set of user input instructions including a request to access ticketing information relating to the first upcoming live performance; and

causing at least one component of the computer network to generate, in response to the first set of user input instructions, a third set of instructions for causing a Ticketing graphical user interface (“

Ticketing GUI”

) to be displayed at an end user'"'"'s device, wherein the third set of instructions include instructions for configuring the Ticketing GUI to enable an end user to;

initiate a ticket reservation transaction relating to a reservation of a first set of tickets for the first upcoming live performance;

initiate a ticket purchase transaction relating to a purchase of a second set of tickets for the first upcoming live performance;

initiate a ticket reservation invitation transaction for inviting at least one identified recipient to accept at least one reserved ticket for the first upcoming live performance;

access updated ticket reservation status information relating to one or more of the end user'"'"'s ticket reservations; and

access updated ticket reservation invitation status information relating to one or more of the end user'"'"'s ticket reservation invitations.

7. The computer implemented method of claim 1 further comprising causing the at least one processor to execute additional instructions for:

causing at least one component of the computer network to receive a first set of user input instructions, the first set of user input instructions being generated from the end user'"'"'s device in response to a first user'"'"'s interaction with the Ticketing GUI, the first set of user input instructions including instructions to initiate a ticket reservation transaction relating to a reservation of a first set of tickets for the first upcoming live performance;

causing at least one component of the computer network to initiate, in response to the first set of user input instructions, a first ticket reservation transaction relating to a reservation of a first ticket for the first upcoming live performance;

causing at least one component of the computer network to associate the reserved first ticket with a first identifier representing the first user;

causing at least one component of the computer network to initiate, in response to the first set of user input instructions, a second ticket reservation transaction relating to a reservation of a second ticket for the first upcoming live performance;

causing at least one component of the computer network to determine, using input provided by the first user, a second identifier for identifying a specific person who is to be associated with the reserved second ticket; and

causing at least one component of the computer network to associate the reserved second ticket with the second identifier.

8. The computer implemented method of claim 1 further comprising causing the at least one processor to execute additional instructions for:

causing at least one component of the computer network to automatically track ticket reservation invitation responses from the at least one identified recipient; and

causing at least one component of the computer network to generate a third set of instructions for causing a Ticketing graphical user interface (“

Ticketing GUI”

) to be displayed at an end user'"'"'s device, wherein the third set of instructions include instructions for configuring the Ticketing GUI to enable an end user to access updated ticket reservation status information relating to one or more of the end user'"'"'s ticket reservations, and to access updated ticket reservation invitation status information relating to one or more of the end user'"'"'s ticket reservation invitations, wherein the ticket reservation invitation status information includes information identifying which ticket reservation invitations have been accepted, which ticket reservation invitations have not yet been accepted, and/or which ticket reservation invitations have been declined.

9. A computer implemented system for facilitating automated conditional purchasing of entertainment event tickets via a computer network, the system comprising:

at least one processor;

at least one interface;

a memory storing a plurality of instructions;

the at least one processor being operable to execute the plurality of instructions stored in the memory, and being operable to operate with the memory and the at least one interface for;

causing at least one component of the computer network to identify a first upcoming live performance of a first artist or band (“

artist/band”

) which is scheduled to be performed in a first geographic region;

causing at least one component of the computer network to generate, using the first ticketing information, a first set of instructions for causing a Ticketing graphical user interface (“

Ticketing GUI”

) to be displayed at an end user'"'"'s device, wherein the first set of instructions include instructions for configuring the Ticketing GUI to enable a first end user to initiate a ticket reservation invitation transaction for inviting at least one identified recipient to accept at least one reserved ticket for the first upcoming live performance;

causing at least one component of the computer network to notify the at least one identified recipient of the ticket reservation invitation transaction;

causing at least one component of the computer network to monitor the ticket reservation invitation transaction in order to determine if the at least one identified recipient has accepted ticket reservation invitation; and

if it is determined that the at least one identified recipient has accepted the ticket reservation invitation, automatically causing at least one component of the computer network to fund at least one ticket purchase transaction relating to a purchase of at least one ticket for the first upcoming live performance.

10. The computer implemented system of claim 9 wherein the funding of the at least one ticket purchase transaction includes causing at least one component of the computer network to automatically fund a first ticket purchase transaction relating to a purchase of a first ticket for the first end user for the first upcoming live performance.

11. The computer implemented system of claim 9 wherein the funding of the at least one ticket purchase transaction includes:

includes causing at least one component of the computer network to automatically fund a first ticket purchase transaction relating to a purchase of a first ticket for the first end user for the first upcoming live performance; and

includes causing at least one component of the computer network to automatically fund a second ticket purchase transaction relating to a purchase of a second ticket for the at least one identified recipient for the first upcoming live performance.

12. The computer implemented system of claim 9 wherein the funding of the at least one ticket purchase transaction includes causing at least one component of the computer network to automatically fund a plurality of ticket purchase transactions for the first upcoming live performance relating to purchase of tickets for the first end user and for the at least one identified recipient.

13. The computer implemented system of claim 9 being further operable to cause the at least one processor to execute additional instructions for:

causing the at least one reserved ticket associated with the ticket reservation invitation transaction to automatically expire in response to determining that a first amount of time has elapsed without detecting confirmation of the at least one identified recipient'"'"'s acceptance of the at least one reserved ticket.

14. The computer implemented system of claim 9 being further operable to cause the at least one processor to execute additional instructions for:

causing at least one component of the computer network to receive a first set of user input instructions, the first set of user input instructions being generated from the end user'"'"'s device in response to user interaction with the Ticketing GUI, the first set of user input instructions including a request to access ticketing information relating to the first upcoming live performance; and

causing at least one component of the computer network to generate, in response to the first set of user input instructions, a third set of instructions for causing a Ticketing graphical user interface (“

Ticketing GUI”

) to be displayed at an end user'"'"'s device, wherein the third set of instructions include instructions for configuring the Ticketing GUI to enable an end user to;

initiate a ticket reservation transaction relating to a reservation of a first set of tickets for the first upcoming live performance;

initiate a ticket purchase transaction relating to a purchase of a second set of tickets for the first upcoming live performance;

initiate a ticket reservation invitation transaction for inviting at least one identified recipient to accept at least one reserved ticket for the first upcoming live performance;

access updated ticket reservation status information relating to one or more of the end user'"'"'s ticket reservations; and

access updated ticket reservation invitation status information relating to one or more of the end user'"'"'s ticket reservation invitations.

15. The computer implemented system of claim 9 being further operable to cause the at least one processor to execute additional instructions for:

causing at least one component of the computer network to receive a first set of user input instructions, the first set of user input instructions being generated from the end user'"'"'s device in response to a first user'"'"'s interaction with the Ticketing GUI, the first set of user input instructions including instructions to initiate a ticket reservation transaction relating to a reservation of a first set of tickets for the first upcoming live performance;

causing at least one component of the computer network to initiate, in response to the first set of user input instructions, a first ticket reservation transaction relating to a reservation of a first ticket for the first upcoming live performance;

causing at least one component of the computer network to associate the reserved first ticket with a first identifier representing the first user;

causing at least one component of the computer network to initiate, in response to the first set of user input instructions, a second ticket reservation transaction relating to a reservation of a second ticket for the first upcoming live performance;

causing at least one component of the computer network to determine, using input provided by the first user, a second identifier for identifying a specific person who is to be associated with the reserved second ticket; and

causing at least one component of the computer network to associate the reserved second ticket with the second identifier.

16. The computer implemented system of claim 9 being further operable to cause the at least one processor to execute additional instructions for:

causing at least one component of the computer network to automatically track ticket reservation invitation responses from the at least one identified recipient; and

causing at least one component of the computer network to generate a third set of instructions for causing a Ticketing graphical user interface (“

Ticketing GUI”

) to be displayed at an end user'"'"'s device, wherein the third set of instructions include instructions for configuring the Ticketing GUI to enable an end user to access updated ticket reservation status information relating to one or more of the end user'"'"'s ticket reservations, and to access updated ticket reservation invitation status information relating to one or more of the end user'"'"'s ticket reservation invitations, wherein the ticket reservation invitation status information includes information identifying which ticket reservation invitations have been accepted, which ticket reservation invitations have not yet been accepted, and/or which ticket reservation invitations have been declined.