WO2019119071A1

WO2019119071A1 - Systems and methods for real-time video streaming

Info

Publication number: WO2019119071A1
Application number: PCT/AU2018/051404
Authority: WO
Inventors: Imran Bonser; Keith William BONSER
Original assignee: Keith William BONSER; Streamy Limited
Priority date: 2017-12-22
Filing date: 2018-12-21
Publication date: 2019-06-27

Abstract

Described embodiments generally relate to computer-implemented method for facilitating electronic event ticketing, the method comprising receiving at least one search criterion from a user interface; retrieving a sub-set of stored events based on the received at least one criterion; displaying the sub-set of stored events on the user interface; receiving a user selection of at least one event from the sub-set of events; displaying real-time video footage captured by a camera associated with the at least one event; and presenting the user with an option to purchase a ticket to the at least one event. Described embodiments also relate to a computing device and server system for performing the method.

Description

"Systems and methods for real-time video streaming"

Technical Field The present disclosure relates to methods and systems of electronic event ticketing.

Background

Online ticketing systems allow users to purchase tickets to events that they are interested in attending. However, users can find it difficult to determine what events are available in their area, and whether or not they are likely to enjoy attending any given event.

It is desired to address or ameliorate one or more shortcomings or disadvantages associated with prior methods, systems and machines for gaming, or to at least provide a useful alternative thereto.

Any discussion of documents, acts, materials, devices, articles or the like which has been included in the present specification is not to be taken as an admission that any or all of these matters form part of the prior art base or were common general knowledge in the field relevant to the present disclosure as it existed before the priority date of each claim of this application.

Throughout this specification the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated element, integer or step, or group of elements, integers or steps, but not the exclusion of any other element, integer or step, or group of elements, integers or steps.

Summary

Some embodiments relate to a computer-implemented method for facilitating electronic event ticketing, the method comprising:

receiving at least one search criterion from a user interface;

retrieving a sub-set of stored events based on the received at least one criterion;

displaying the sub-set of stored events on the user interface; receiving a user selection of at least one event from the sub-set of events; presenting the user with an option to view real-time video footage captured by a camera associated with the at least one event; and

presenting the user with an option to purchase a ticket to the at least one event.

According to some embodiments, presenting the user with an option to view real-time video footage captured by a camera comprises presenting the user with an option to purchase access to the real-time video footage.

receiving at least one search criterion from a computing device; retrieving a sub- set of stored events from a database based on the received at least one criterion;

sending the sub-set of stored events to the computing device; receiving a selection of at least one event from the sub- set of events from the computing device;

receiving an instruction from the computing device to provide a real-time video footage stream captured by a camera associated with the at least one event;

providing the real-time video footage stream to the computing device; receiving an instruction from the computing device to generate a digital ticket to the at least one event;

generating a digital ticket to the at least one event; and

providing the digital ticket to the computing device.

receiving at least one search criterion from a user interface; retrieving a sub-set of stored events based on the received at least one criterion;

displaying the sub-set of stored events on the user interface; receiving a user selection of at least one event from the sub-set of events; displaying real-time video footage captured by a camera associated with the at least one event; and

presenting the user with an option to purchase a ticket to the at least one event. Some embodiments further comprise making a digital ticket available to the user in response to the user electing to purchase a ticket. According to some embodiments, making a digital ticket available to the user comprises displaying a digital ticket on the user interface. In some embodiments, the digital ticket comprises a barcode. In some embodiments, the digital ticket comprises a QR code.

According to some embodiments, the at least one search criterion comprises a geographical location. According to some embodiments, the geographical location is selected based on data received from a GPS module.

Some embodiments relate to a computing device comprising:

at least one processor;

memory accessible to the at least one processor; and

at least one user interface;

wherein the memory stores instructions executable by the at least one processor to cause the computing device to perform the method of some previously recited embodiments. Some embodiments relate to a computer-implemented method for facilitating electronic event ticketing, the method comprising:

providing a real-time video footage stream captured by a camera associated with the at least one event to the computing device;

receiving an instruction from the computing device to generate a digital ticket to the at least one event;

generating a digital ticket to the at least one event; and

providing the digital ticket to the computing device. According to some embodiments, providing the digital ticket to the computing device comprises emailing the digital ticket. According to some embodiments, providing the digital ticket to the computing device comprises sending the digital ticket via MMS. According to some embodiments, providing the digital ticket to the computing device comprises making the digital ticket available for download from a URL.

According to some embodiments, the at least one search criterion comprises a geographical location.

Some embodiments further comprise receiving the real-time video footage stream from a camera located in proximity to the at least one event.

Some embodiments further comprise receiving the real-time video footage stream from a camera located in proximity to the at least one event via an image processing and handling server.

Some embodiments relate to a server system comprising:

at least one server; and

at least one database accessible to the at least one server;

wherein the database stores instructions executable by the at least one server to cause the server to perform the method of some previously described embodiments.

Some embodiments relate to a system for facilitating electronic event ticketing, the system comprising:

the server of some previously described embodiments; and

at least one computing device according to some previously described embodiments.

Some embodiments further comprise a device comprising a scanner, the scanner configured to scan the digital ticket provided to the computing device.

According to some embodiments, the device is configured to communicate with the at least one server to determine whether the ticket is valid.

Some embodiments further comprise a camera configured to capture at least one of still images and video footage. According to some embodiments, the camera is configured to captured at least one of still images and video footage and to transmit the captured images and/or video footage to the at least one server. Brief Description of Drawings

Embodiments are described below in further detail and by way of example, with reference to the accompanying drawing, in which:

Figure 1 is a diagrammatic representation of a ticketing system in accordance with some embodiments;

Figure 2 is a schematic block diagram of ticketing service components of the ticketing system of Figure 1 ;

Figure 3 is a flow diagram illustrating a method of creating events for the ticketing system of Figure 1 according to some embodiments;

Figure 4 is a flow diagram illustrating a method of purchasing tickets using the ticketing system of Figure 1 according to some embodiments;

Figure 5 is an example screen shot showing a login page of the ticketing system of Figure 1 according to some embodiments;

Figure 6 is an example screen shot showing an account creation page of the ticketing system of Figure 1 according to some embodiments;

Figure 7 is an example screen shot showing a user account page of the ticketing system of Figure 1 according to some embodiments;

Figure 8 is an example screen shot showing an event list page of the ticketing system of Figure 1 according to some embodiments;

Figure 9 is an example screen shot showing an event search page of the ticketing system of Figure 1 according to some embodiments;

Figure 10 is an example screen shot showing an event detail page of the ticketing system of Figure 1 according to some embodiments;

Figure 11 is an example screen shot showing a venue account page of the ticketing system of Figure 1 according to some embodiments;

Figure 12 is an example screen shot showing an event overview page of the ticketing system of Figure 1 according to some embodiments; and

Figure 13 is an example screen shot showing an event dashboard page of the ticketing system of Figure 1 according to some embodiments.

Detailed Description The present disclosure relates to methods and systems of electronic event ticketing. Figure 1 shows an example ticketing system 100 in accordance with some embodiments. A venue 110 is illustrated, with a camera 120 and a staff device 140 located within or in proximity to venue 110. Venue 110 has a specific geographic location and may be defined by built structures. For example, venue 110 may be a bar, theatre, hall, stadium, restaurant, club, or other physical location at which events may be held. Events may include shows, concerts, parties, festivals, meals, or other events. A server system 160 is located remotely from the physical location of venue 110.

Camera 120 may be or comprise one or more cameras configured to capture images and video footage of venue 110. According to some embodiments, camera 120 may be configured to capture a series of images. This may include video footage captured at different locations around the venue 110, such as within and outside of venue 110. For example, according to some embodiments, camera 110 may be configured to capture footage of the door of venue 110, to show whether or not there is a line to get into venue 110.

According to some embodiments, camera 120 may be configured to capture and transmit images live, in real-time or near-real time. Capturing and transmitting images in real-time or near-real time may involve transmitting the images immediately after capturing them, or without a significant delay. For example, the images may be transmitted within 5 minutes, 3 minutes, 30 seconds, 20 seconds, 10 seconds, 5 seconds or 1 second of being captured. According to some embodiments, transmitting images in real-time or near-real time may require that the images are transmitted without being stored to a memory of camera 120. According to some embodiments, transmitting images in real-time or near-real time may require that the images are transmitted as immediately as practically possible by camera 120.

According to some embodiments, camera 120 may be fixed in a stationary location. In some embodiments, camera 120 may be a portable camera. According to some embodiments, camera 120 may be a mobile phone or tablet camera. According to some embodiments, camera 120 may be part of or affixed to staff device 140. According to some embodiments, camera 120 may include a microphone, and may be configured to capture and transmit audio as well as image and video data.

Camera 120 may be configured to communicate with a remotely located server system 160 external to venue 110. Camera 120 may communicate with server system 160 via a wired or wireless communication means, which may include one or more of Wi-Fi, Bluetooth, USB and Ethernet, for example. According to some embodiments, camera 120 may communicate with a dedicated image handling and processing server within server system 160. According to some embodiments, camera 120 may communicate with a dedicated image handling and processing server outside of server system 160, which may then communicate with server system 160.

Staff device 140 may be a computing device, such as a mobile phone, tablet, or custom computing device, located within or in proximity of venue 110. Staff device 140 is configured to be used by staff of venue 110 to assist with ticketing and authentication of tickets. According to some embodiments, staff device 140 may be a handheld computing device such as a mobile phone or a tablet. In some embodiments, staff device 140 may be a desktop computing device or a laptop. Staff device 140 includes a processor 142, and memory 144 accessible by processor 142. Memory 144 stores data and executable code, which may include a ticketing application 145. Ticketing application 145 is executable by processor 142 to cause staff device 140 to perform ticketing functions.

Staff device 140 may also include a communications module 148. Communications module 148 may comprise one or more of a Wi-Fi, Bluetooth, USB, Ethernet, or other communications modules, configured to allow staff device to communication with remotely located server system 160.

Staff device 140 also includes a user interface 146. User interface 146 may include a scanner 147, which may be integrated into the staff device 140 or separate from but coupled thereto. User interface 146 may also include a display, which may be an LCD screen, touchscreen, or other display, buttons, speakers, microphones, and other input and output devices allowing a user to interact with staff device 140. For example, a user may use a touch screen of user interface 146 to give commands to staff device 140 to scan a ticket using scanner 147, in some embodiments.

Scanner 147 may be a laser scanner, infra-red scanner, near-field communications (NFC) scanner or a camera in some embodiments, and may be configured to allow visual codes or other codes, such as NFC codes, to be captured and analysed by staff device 140. For example, scanner 147 may be configured to scan QR codes or barcodes in some embodiments. Scanner 147 may be used by staff at venue 110 to scan and authenticate attendee tickets, to ensure attendees have paid for their entry to venue 110 and that their tickets are valid. According to some embodiments, software stored in memory 144 and executed by processor 142 may be configured to decode codes scanned by scanner 147, to allow staff device 147 to send the codes to server system 160 for authentication.

Server system 160 may comprise one or more computing devices and servers, and may be a cloud-based system in some embodiments. Server system 160 may host a ticketing service 165, which may be accessible as a website using a web browser application on a computing device, or via a dedicated application running on a computing device. Ticketing service 165 may store data relating to venues 110, and may allow for information and ticketing services to be provided to users with respect to venues 110. Ticketing service 165 may also allow venues 110 to upload information, stream live videos, create events, and regulate ticket purchases to events and to live streams. According to some embodiments, ticketing service 165 may be hosted on an Ethereum platform, or another blockchain based or smart contract platform. Ticketing service 165 also allows for event staff to authenticate and validate tickets presented at venue 110. Ticketing service 165 is described in further detail below with reference to Figure 4.

While a number of code modules, databases, and functions are described below as being stored within or performed by ticketing service 165 on server system 160, according to some embodiments, some or all of the code modules, databases, and functions of ticketing service 165 may be stored within or performed by computing device 130 and/or staff device 140.

Prior to attending venue 110, users may use a computing device 130 to view venue 110 and to purchase tickets to an event at venue 110, if they choose to attend. In some embodiments, a user may alternatively be able to purchase access to a live stream of an event at venue 110, if they choose not to attend. If a user purchases a ticket, they may use computing device 130 to digitally present tickets at venue 110. If a user purchases access to a live stream, they may use computing device 130 to access the live stream. Access to a live stream may be regulated by the supply of a virtual ticket to computing device 130, and provision of such tickets may be regulated by ticketing service 165.

In the illustrated embodiment, computing device l30a is being used to communicate with server system 160 to view details about venue 110 and to purchase tickets to venue 110 prior to attending venue 110, while computing device l30b is being used at a venue 110 to present purchased tickets to staff at venue 110. In this documents, “computing device 130” will be used to refer to either of computing device l30a and computing device l30b. According to some embodiments, computing device 130 may be a handheld computing device, such as a tablet or mobile phone. In some embodiments, computing device 130 may be a desktop computing device or a laptop.

Computing device 130 may include a processor 132 and a memory 134 accessible to processor 134. Memory 134 may store data and executable code, which may include an application 135. Application 135 may be executable by processor 132 to cause computing device 130 to access information and ticketing functions for venue 110. Functions of application 135 are explained in further detail below, but may include streaming live footage from venue 110 as captured by camera 120, viewing event and venue information for venue 110, purchasing tickets to venue 110 and presenting tickets at a venue 110.

According to some embodiments, application 135 may be a web browser that allows computing device 130 to access ticketing service 165 via a website hosted on server system 160. According to some alternative embodiments, application 135 may be a customised and dedicated application configured to communicate with server system 160 to access ticketing service 165, and to cause information and ticketing functions to be displayed by computing device 130. Thus, application 135 may function as a customised event searching and ticketing application.

Computing device 130 may also include a user interface 136. User interface 136 may include a display 137, which may be an LCD screen, touchscreen, or other display. User interface 136 may also include buttons, displays, touch screens, speakers, microphones, and other input and output devices allowing a user to interact with computing device 130. For example, a user may use a touch screen of user interface 136 to give commands to computing device 130 to display a live stream of venue 110, and the live stream may be shown on display 137 of user interface 136, in some embodiments.

Computing device 130 may also include a communications module 138. Communications module 138 may comprise one or more of a Wi-Fi, Bluetooth, USB, Ethernet, or other communications modules, configured to allow computing device 130 to communication with remotely located server system 160.

Once a user has purchased a ticket to venue 110, they may choose to print or otherwise receive a physical ticket, which may be a scannable ticket 150, for example. Scannable ticket 150 may have a scannable code 155 formed or printed thereon that can be read and interpreted by scanner 147 of staff device 140. According to some embodiments, scannable code 155 may be a visual code such as a barcode or a QR code. According to some embodiments, code 155 may be an NFC, magnetic, electronic or other code capable of being scanned and interpreted by scanner 147.

In some alternative embodiments, once a user has purchased a ticket to venue 110, they may choose to use their computing device 130 to display a digital ticket to event staff at venue 110 via display 130. Users may have a digital ticket sent to them by server system 160 via email or text, or may download a digital ticket from a website hosted by server system 160. According to some embodiments, where application 135 is a dedicated ticketing application, application 135 may make the digital ticket available by saving it locally to memory 134 of computing device 130, or may retrieve it from ticketing service 165 of server system 160 as required on an ad-hoc basis. When the user arrives at venue 110, the user may operate user interface 136 to cause application 135 to display the digital ticket on display 137, or may otherwise retrieve or open the digital ticket to display on display 137.

A staff member at venue 110 can then operate staff device 140 to scan scannable tickets 150 and digital tickets presented on computing device l30b using scanner 147, to authenticate and validate the tickets. Staff device 140 may execute ticketing application 145 to cause scanner 147 to scan the digital or physical ticket, and to send the ticket information to server system 160 for validation and authentication. If the digital ticket is valid, staff device 140 may receive a confirmation signal from server system 160, and can allow the user of the scanned digital ticket displayed on computing device l30b or the holder of scannable ticket 150 into venue 110.

Figure 2 shows ticketing service 165 in further detail. Ticketing service 165 may store a number of data sets in database 200, and a number of executable code modules within application code 240. As described above, while ticketing service 165 is illustrated as being within server system 160, according to some embodiments, some or all of the code modules, databases, and functions of ticketing service 165 may be stored within or performed by computing device 130 and/or staff device 140.

Application code 240 may be executable by server system 160 when in communication with computing device 130 or staff device 140, in order to cause data and instructions to be sent between server system 160 and computing device 130 or staff device 140. Database 200 may be accessed by server system 160 in response to instructions read from application code 240 and executed by server system 160.

Database 200 may store account verification data 205, user account data 210 and venue account data 215. Account verification data 205 may include usernames, passwords, and password retrieval options for user and venue accounts, and may be stored in a secure and encoded form. User account data 210 may store account data for users of computing device 130, including user preferences, user names, contact information, and payment preferences. Venue account data 215 may store account data for venues 110 associated with staff device 140, including venue names, addresses, associated social media accounts, and contact information. Database 200 may also store venue payment data 220 in association with venue account data 215. Venue payment data may include banking details of venue 110 to allow venue 110 to be paid for any ticket sales, physical or virtual, made by the venue.

For each venue stored in venue account data 215, database 200 may also store venue data 295, and one or more instances of event data 225. Venue data 295 may include data about venues 110 that is made available to computing devices 130, such as venue location, venue accessibility, venue opening hours, associated social media accounts, and opening hours. Venue data 295 may also include articles, blog posts, or other data made available by the venue or on behalf of the venue. Users may be able to interact and add to this data by adding comments, likes, and/or reviews, in some embodiments. In some embodiments, users may also be able to connect with or follow other users of the application 165. Venue data 295 may display which users are currently attending, planning to attend, or have previously attended the venue or event being displayed.

Event data 225 may include event names, event types, event locations, and event streaming Uniform Resource Locator (URL) data. Ticket data 230 for physical tickets and virtual tickets for live stream events may also be stored in association with each event. Ticket data 230 may include ticket prices, tickets available, tickets sold, and authentication details for any sold tickets.

Database 200 may also record streaming configuration data 235 for any camera 120 associated with an event stored in event data 225. Streaming configuration data 235 may include details of the communication channel between server system 160 and camera 120, to allow footage captured by camera 120 to be made available to computing devices 130. According to some embodiments, the streamed footage may be made available via the URL stored in event data 225.

According to some embodiments, each venue 110 may elect whether streamed footage captured at their venue is made available to the user for free, or whether the access must be purchased by acquiring a virtual ticket to view the footage. For example, a concert venue may require live stream footage to be purchased for people who would like to watch the show without attending the venue, while a bar might stream footage for free to advertise the atmosphere of the bar and encourage customers to attend the bar. In some embodiments, venues 110 may be able to make some footage free, while requiring payment for other footage. For example, a concert venue may make footage of people arriving at the concert free, to advertise to potential customers and show the atmosphere of the event. Once the concert commences, the venue may require users to pay for footage of the concert.

Application code 200 may include a create user account module 245, executable by server system 160 upon instructions received from computing device 130 that a new user account is to be created. Create user account module 245 may cause server system 160 to instruct computing device 130 to prompt the user to enter new user account data. When this data is received by server system 160 from computing device 130, create user account module 245 may cause the data to be stored in account verification data 205 and user account data 210.

Application code 200 may also include an authentication module 250. Authentication module 250 may be executed by server system 160 when a user is attempting to log in to an account via computing device 130. Computing device 130 may send the login details to server system 160, and server system 160 may execute authentication module 250 to compare the received data with account verification data 205, to authenticate the account. If the account is authenticated, authentication module 250 may cause a confirmation signal to be sent from server system 160 to computing device 130.

Application code 240 may further include search module 255 and information retrieval module 260. Search module 255 may be executed by server system 160 in response to receiving search instructions and search criteria from computing device 130. Search module 255 is executed by server system 160 to perform a search of venue data 295 and event data 225 according to the search criteria, and to send a list of the results to computing device 130. Information retrieval module 260 may be executed by server system 160 in response to a command received from computing device 130 instructing server system 160 to retrieve information about a specific venue or event. When executed by server system 160, information retrieval module 260 may cause server system 160 to retrieve the requested information from venue data 295 and/or event data 225.

Event streaming module 265 is executed by server system 160 in response to a user navigating to an event stream URL using computing device 130. Computing device 130 communicates with server system 160 to retrieve the streamed video or image feed, if the venue has elected to provide the streamed video or image feed for free or if the user has purchased a virtual ticket providing them with access to the footage. Where the user is authorised to access the footage, event streaming module 265 causes server system to retrieve the video or image feed from the URL stored in event data 225.

Create event account module 270 is executable by server system 160 upon instruction received from staff device 140 that a new event account is to be created. Create event account module 270 may cause server system 160 to instruct staff device 140 to prompt a user to enter new venue account data. When this data is received by server system 160 from staff device 140, create event account module 270 may cause the data to be stored in account verification data 205 and venue account data 215. Staff device 140 may also prompt a user to enter venue details, which may be stored by create event account module 270 to venue data 295.

Payment processing module 275 facilitates payments between users of computing device 130 buying tickets and live stream access through ticketing service 165, and venues 110 hosting events facilitated by ticketing service 165. When a ticket purchase or live stream access purchase is being made via computing device 130, purchase information including ticket price and user payment preferences are retrieved by payment processing module 275 from user account data 210 and ticket data 230. Venue account details are retrieved from venue payment data 220 to ensure the payment is being made to the correct location. Once the payment has been processed by payment processing module 275, a payment receipt is generated by server system 160 and sent to computing device 130.

Configure camera module 280 is executed by server system 160 in response to instructions from staff device 140 to configure a camera 120 to be used to stream video footage or a series of images of an event in venue 110. Configure camera module 280 receives camera configuration data and stores it in streaming configuration data 235, to allow for communication to be established between camera 120 and server system 160.

Generate ticket module 285 may be executed by server system 160 in response to a successful payment result generated by payment processing module 275. Generate ticket module 285 uses ticket data 230 to generate a unique ticket for every ticket purchase made through ticketing service 165. The generated ticket data is sent to computing device 130, and also stored in ticket data 230. If a user attempts to scan a generated ticket at an event via a staff device 140, staff device 140 communicates the ticket details to server system 160, which executes validate ticket module 290 to determine if the scanned ticket is valid. Validate ticket module 290 compares the received ticket data with data retrieved from ticket data 230 to determine the validity of the scanned ticket, and causes server system 160 to send the result of the determination to staff device 140.

Figure 3 illustrates a flowchart showing a method 300 of using staff device 140 to access the functions of ticketing service 165 from an event host perspective.

Method 300 starts with step 305, when a user of staff device 140 accesses ticketing service 165 via server system 160. Ticketing service 165 may be accessed using a dedicated ticketing application 145 installed on staff device 140, or, in some embodiments, ticketing service 165 may be accessed via a website accessed by a browser on staff device 140. Processor 142 causes communications module 148 to communicate with server system 160 to retrieve information from ticketing service 165 and to cause it to be displayed on staff device 140. At step 310, processor 142 causes staff device 140 to prompt the user to indicate whether or not the venue 110 associated with staff device 140 has an existing account with ticketing service 165. If the user indicates via a user interface of staff device 140 that the venue 110 does not have an existing account, method 300 moves to step 315, and processor 142 causes staff device 140 to show instructions to the user prompting them to create a new venue account.

At step 320, staff device 140 prompts the user to enter venue information. Venue information may include venue location, venue size, venue accessibility, venue name, and other criteria. Data entered as venue information by a user of staff device 140 may be communicated by communications module 138 to server system 160, and create event account module 270 is executed by ticketing service 165 to cause the venue information to be stored within venue account data 215 and venue data 295. Information stored in venue account data 215 may be available only to the account holder of the venue account for venue 110, while venue data 295 may be made available by ticketing service 165 to users who access the venue information via a computing device 130.

At step 325, staff device 140 prompts the user to enter bank information to allow for payment of ticket sales and other purchases made by event attendees to be credited to an account associated with the venue 110. Bank information entered by a user of staff device 140 may be securely sent to server system 160. Ticketing service 165 may execute create event account module 270 to cause the bank information to be stored in venue payment data 220. According to some embodiment, this information is not available to users of ticketing service 165, aside from the account holder of the venue account for venue 110.

At optional step 330, staff device 140 may prompt the user to enter social media account information associates with the venue 110. Social media account information may include Facebook, Twitter, Instagram, Snapchat, and other social media accounts. If the user elects to enter social media account information, the information may be sent to server system 160 to be stored within venue account data 215 and/or venue data 295 of ticketing service 165 as part of the venue information, to be displayed to users who access the venue information via a computing device 130. Once the user has entered the relevant information to create a venue account, and the account has been created by create event account module 270, staff device 140 may load a login page to allow the user to login at step 335.

If the venue does have an existing account, at step 335 staff device 140 may perform a login process. This may include asking the user for their login credentials, and authenticating the credentials with ticketing service 165. According to some embodiments, the credentials may be a username and a password. According to some embodiments, the credentials may include a biometric authentication credential, such as a fingerprint or retina scan. The credentials may be sent to ticketing service 165, which may be configured to execute authentication module 250. Authentication module 250 may compare the received credentials with credentials stored in account verification data 205 to determine whether or not the account is valid. If it is valid, ticketing service 165 may be caused to send a positive authentication response to staff device 140.

Once the credentials have been authenticated, at step 340, processor 142 causes venue account information to be displayed by staff device 140. This may include a list of any events being hosted by venue 110, ticket sale numbers, ticket sale analytics and statistics, reviews, and other account information, as retrieved from venue account data 215 and venue data 225 by ticketing service 165. According to some embodiments, the venue account information may be displayed on a screen similar to that shown on screenshot 1100 of Figure 11, as described in further detail below. From the account information screen, the user may have the option to create a new event at step 345. If the user does not wish to create a new event, the user may continue browsing event account information at step 340. If a user does wish to create a new event, they may indicate this using a user interface of staff device 140, and method 300 may move to step 350.

At step 350, having received an input from the user indicating that a new event is to be created, staff device 140 prompts the user to enter event information. The event information may include event name, event location, event genre, event date, ticket price, availability of tickets, availability of live stream footage, ticket price for accessing live stream footage, venue size, venue accessibility, performer names, venue name, and other criteria. Event information entered by a user of staff device 140 may be sent to ticketing service 165 by communications module 138, to be stored as part of event data 225 associated with the logged in venue account. At step 355, staff device 140 may optionally prompt the user to add event media, such as photos, videos, and audio clips, to the event information. Event media uploaded by a user using staff device 140 may also be sent to ticketing service 165 by communications module 138, to be stored as part of the event data 225.

Details of all of the events saved by a venue 110 may be available on an event overview page, such as screenshot 1200 described in further detail below with reference to Figure 12. Particular details of an event created by a venue may be made available for viewing by the venue account holder via an event details page such as screenshot 1300, described in further detail below with reference to Figure 13.

Once a user has entered the event details and uploaded any associated media to ticketing service 165, staff device 140 may present an option to allow the user to publish the event, making it accessible to computing devices 130 via the search function when accessing ticketing service 165. According to some embodiments, staff device 140 may also present options to allow the user to save the event as a draft, and/or to schedule the publication of the event for a later date. Once the event has been published, at step 365 staff device 140 may present instructions to the user of staff device 140 for configuring a camera 120 for use for the created event. According to some embodiments, the configuration may include registering an IP address of camera 120 with ticketing service 165 to allow ticketing service 165 to establish communication between server system 160 and camera 120. According to some embodiments, configuration may include establishing a communication channel between camera 120 and staff device 140, to allow staff device 140 to stream images captured by camera 120 to server system 160 to be made accessible to ticketing service 165. The communication channel may include a Bluetooth, Wi-Fi, Ethernet, USB, or other communication channel. Ticketing service 165 may execute configure camera module 280 to allow for the communication channel to be established, and the camera configuration details may be stored to streaming configuration data 235.

At step 370, once camera 120 is configured to communicate captured images to ticketing service 165, ticketing service 165 may begin streaming images captured by camera 120 to the associated event page stored within ticketing service 165 and made available to computing devices 130. According to some embodiments, streaming may occur only once the associated event has begun, or only a predetermined time period before the event, such as 24 hours, 12 hours, 6 hours, 3 hours, 1 hour or 30 minutes before the event, for example. According to some embodiments, streaming may begin as soon as the event is published, to allow potential attendees to ascertain the facilities, mood and vibe of the venue hosting the event. As described above, in some embodiments the stream may be provided to all users for free. In some embodiments, users may need to purchase access to view the stream.

Figure 4 illustrates a flowchart showing a method 400 of using computing device 130 to access the functions of ticketing service 165 from an event attendee perspective.

Method 400 starts with step 405, when a user of computing device 130 accesses ticketing service 165 via server system 160. Ticketing service 165 may be accessed using a dedicated application 135 installed on computing device 130, or, where application 135 is a web browser, ticketing service 165 may be accessed via a website. Processor 132 causes communications module 138 to communicate with server system 160 to retrieve information from ticketing service 165 and to cause it to be displayed on display 137.

At step 410, processor 132 causes display 137 to prompt the user to indicate whether or not the user has an existing account with ticketing service 165. For example, screenshot 500, as described in further detail below with reference to Figure 5, may be displayed. The existing account may be linked to a social media account of the user, or may be an independent account. If the user indicates via user interface 136 that they do not have an existing account, method 400 moves to step 415, and processor 132 causes display 137 to show instructions to the user prompting them to create an account. For example, screenshot 600, as described below in further detail with reference to Figure 6, may be displayed. Once the user has entered account information to create an account, the information they enter is sent by communications module 138 to ticketing service 165. Create user account module 245 may be executed by ticketing service 165 to cause the user account to be created and store within user account data 210.

At step 420, ticketing service 165 may optionally send a confirmation message to the user to confirm their account. This may be sent via text, email, or a messaging application. Once the user has created and confirmed their account, they may be directed to the login page to login at step 425.

If the user does have an existing account, at step 425 computing device 130 may perform a login process. This may include asking the user for their login credentials, and authenticating the credentials with ticketing service 165. According to some embodiments, the credentials may be a username and a password. According to some embodiments, the credentials may include a biometric authentication credential, such as a fingerprint or retina scan. The credentials may be sent to ticketing service 165, which may be configured to execute authentication module 250. Authentication module 250 may compare the received credentials with credentials stored in account verification data 205 to determine whether or not the account is valid. If it is valid, ticketing service 165 may be caused to send a positive authentication response to computing device 130.

Once the credentials have been authenticated, at step 430 processor 132 causes a home screen to appear on display 137, which may be screenshot 700 as described below with reference to Figure 7, in some embodiments. The home screen may present a number of options to the user, such as enabling them to edit their account details, view settings, and search for venues and events.

If the user elects to search for a venue or event, processor 132 causes a search screen to appear on display 137, which may be screenshot 800 as described in further detail below with reference to Figure 8. The user may be able to use user interface 136 to enter search criteria such as location, event genre, event date, ticket price, availability of tickets, venue size, venue accessibility, performer name, venue name, event name, and other criteria. In some embodiments, processor 132 may access GPS data to cause a map to be displayed on display 137, allowing a user to browse venues and events in their vicinity. According to some embodiments, the user may be able to enter filters for the search using screenshot 900, described in further detail below with reference to Figure 9. According to some embodiments, processor 132 may cause a calendar to be displayed on display 137, allowing a user to browse events by event date.

Once the user enters the search criteria via user interface 136 at step 435, communications module 138 retrieves a list of venues and/or events from ticketing service 165 that match the search criteria. Ticketing service 165 executes search module 255 to search through venue data 295 and/or event data 225 and to retrieve a list of venues and/or events that match the search criteria. Processor 132 causes the retrieved information to be displayed on display 137 at step 440.

At step 445, computing device 130 receives a selection made by the user via user interface, the selection corresponding to a listed venue or event displayed on display 137. At step 450, processor 132 causes communications module 138 to retrieve the venue and/or event details from ticketing service 165 by executing information retrieval module 260. Information retrieval module 260 retrieves data from event data 225 and/or venue data 295 and sends the data to computing device 130. These details are then displayed to the user via display 137, which may be via screenshot 1000 as described in further detail below with reference to Figure 10. Details may include the location, reviews, photos, line-up, facilities, and a video stream or series of images of the event as supplied to ticketing service 165 by camera 120. According to some embodiments, the video stream or series of images may include audio.

According to some embodiments, ticketing service 165 may be configured to transmit video and/or images in real-time or near-real time. Transmitting in real-time or near- real time may involve transmitting the images immediately after receiving them, or without a significant delay. For example, the images may be transmitted within 5 minutes, 3 minutes, 30 seconds, 20 seconds, 10 seconds, 5 seconds or 1 second of being received by ticketing service 165. According to some embodiments, transmitting images in real-time or near-real time may require that the images are transmitted without being stored to a memory of ticketing service 165. According to some embodiments, transmitting images in real-time or near-real time may require that the images are transmitted as immediately as practically possible by ticketing system 165.

Where a live stream video is available for viewing, the live stream may be provided via a third party streaming application interface, such as Facebook, Youtube or Wowza. According to some embodiments, a custom streaming application interface may be used. Ticketing service 165 may execute event streaming module 265 to cause a live stream to be sent to computing device 130 for display on display 137. The live stream may be communicated from camera 120 to server system 160 based on streaming configuration data 235, and made available on a URL as stored in event data 225.

Processor 132 may also cause a ticket purchase option for the event to be displayed to the user via display 137 at step 455. In some embodiments, where the live stream footage ios only available by purchase, processor 132 may also cause a live stream footage access purchase option for the event to be displayed to the user via display 137 at step 455

If the user is uninterested in the event, the user may exit the details screen and return to the search result screen at step 440. If the user wished to purchase a ticket or purchase access to the live stream footage, the user may activate the ticket purchase option using user interface 136. The user may be prompted to select from further options for their purchase. For example, where the user has elected to attend the event, the user may be asked to select a seat or seating area within the venue. Where the user has elected to watch the live stream, the user may be prompted to select from a standard or high definition video stream option. Once the user selected from the presented options, the user may be prompted to enter payment information for the tickets, such as by entering their credit card details or by logging on to a payment service such as PayPal™.

Once the user has completed the purchase, the tickets may be generated by ticketing service 165 executing generate ticket module 285, using data retrieved from ticket data 230 associated with event data 225 for the viewed event. Generated tickets are stored to ticket data 230, and may also be stored to user account data 210 in association with the user account of the user that purchased the tickets. Once the tickets are generated, tickets are made available to the user by ticketing service 165 at step 460. This may be by email, SMS, digital download, or by storing or associating the ticket to the user account within ticketing service 165 on server system 160. The user may be given the option of printing the ticket, or of using the ticket electronically. According to some embodiments, the user may be given the option to collect a physical ticket in person, or of having a physical ticket mailed to them. Where the ticket is a virtual ticket for viewing a live stream, the ticket may not be made available to the user, but merely stored on server system 160.

When a user attends an event and presents a ticket to staff device 140, staff device 140 may scan the ticket using scanner 147 and may communicate the scanned details to ticketing service 165. Ticketing service 165 may execute validate ticket module 290 to determine whether the scanned ticket is valid, by comparing the scanned ticket data to ticket data 230. If the scanned ticket is found to be valid by validate ticket module 290, a positive validation response is sent by server system 160 to staff device 140. Where a user purchases live stream footage, at the time of accessing the link to the love stream footage ticketing service 165 may validate the user account details to authenticate the user and ensure they have authorisation to access the footage.

Figure 5 shows an example screenshot 500 displayed on computing device 130 accessing ticketing service 165. Screenshot 500 shows a login page displayed on computing device 130 when a user accesses ticketing service 165 via server system 160 at steps 405 and 410 of method 400 illustrated in Figure 4. Screenshot 500 includes social media login buttons 510 to allow a user to login to ticketing service 165 with a social media account, or credential entry fields 520 to allow a user to log in using an email address and password. Alternatively, if a user does not have an account with ticketing service 165, screenshot 500 includes an option 530 to allow a user to create a new account, as per step 415 of method 400.

If the user activates option 530, computing device 130 may cause screenshot 600 to be displayed. Figure 6 shows an example screenshot 600 displayed on computing device 130 accessing ticketing service 165. Screenshot 600 shows an account creation page displayed on computing device 130 when the user wishes to create a new account, as described above with reference to step 415 of method 400. Screenshot 600 includes an image upload field 610 to allow the user to upload a profile picture to associate with their account. Screenshot 600 also includes account information entry fields 620, 630 and 640, allowing a user to input information including their name, date of birth and email address, for example.

Figure 7 shows an example screenshot 700 displaying a user account page displayed on computing device 130 when a user has successfully logged into ticketing service 165, as described above with respect to step 425 of method 400. Screenshot 700 shows a menu 710. Menu 710 includes a favourites option 720, to allow a user to access their favourite events and venues, and a history option 730 to allow a user to access their recently visited events and venues. Menu 710 also includes an info option 740 to allow the user to access further information about ticketing service 165, and a settings option 750 to allow a user to update their account settings, such as their preferred payment method and contact details, for example. Menu 710 also has a connect to venue option 760, allowing a user to search for and virtually connect to a venue to receive information about the venue, and any events the venue is hosting. Pressing on the connect to venue option 760 may cause computing device 130 to display screenshot 800, as shown in Figure 8. Screenshot 800 displays an event list page. Screenshot 800 includes a dropdown location box 810 allowing a user to input a location. Screenshot 800 displays venues in the selected location in list 850, when location list tab 820 is selected. Screenshot 800 also includes map tab 830, allowing a user to browse a map for locations in a particular area, and search tab 840, allowing a user to search for venues by keywords or by filtering. According to some embodiments, computing device 130 may include a GPS module, which may be used to identify a location of computing device 130, which may be used as a default location for list tab 820 and map tab 830.

Figure 9 shows an example screenshot 900 displayed on computing device 130 accessing ticketing service 165 when a user selects the search tab 840 on screenshot 800. Screenshot 900 shows an event search page having selectable options for venue types 910, an area 920, and districts 930. Once a user has made their desired selections, they can activate the start searching button 940 to search for venues fitting in the selected criteria.

Figure 10 shows an example screenshot 1000 displayed on computing device 130 accessing ticketing service 165 when a user selects a particular event from the results displayed on screenshot 800 or as a result of the search carried out using screenshot 900. Screenshot 1000 displays the event name 1010, a ticket price 1020, and an event info tab 1030 displaying event information 1050. A gallery tab 1040 is also provided, allowing for access to images of the displayed event.

Figure 11 shows an example screenshot 1100 displayed on staff device 140 accessing ticketing service 165. Screenshot 1100 shows a venue account page, displaying information about a venue including a venue name 1110 and accepted payment methods 1120 accepted by the venue, among other information.

Figure 12 shows an example screenshot 1200 displayed on staff device 140 accessing ticketing service 165 showing an event overview page. The event overview page provides details of all events being hosted by the venue 110 associated with the logged- in venue account, including an event name 1210, and event details 1220. The event details include the number of tickets sold, the price of tickets, and the date of the event. Figure 13 shows an example screenshot 1300 of an event dashboard page displayed on staff device 140. Screenshot 1300 includes detailed information regarding an event selected by a user from screenshot 1200. The detailed information includes the number of seats sold, the overall rating of the event, the turn out, and the total revenue generated by the event.

It will be appreciated by persons skilled in the art that numerous variations and/or modifications may be made to the above-described embodiments, without departing from the broad general scope of the present disclosure. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive.

Claims

CLAIMS:

1. A computer-implemented method for facilitating electronic event ticketing, the method comprising:

2. The method of claim 1, further comprising making a digital ticket available to the user in response to the user electing to purchase a ticket.

3. The method of claim 2, wherein making a digital ticket available to the user comprises displaying a digital ticket on the user interface.

4. The method of claim 2 or claim 3, wherein the digital ticket comprises a barcode.

5. The method of anyone of claims 2 to 4, wherein the digital ticket comprises a QR code.

6. The method of any one of claims 1 to 5, wherein the at least one search criterion comprises a geographical location.

7. The method of claim 6, wherein the geographical location is selected based on data received from a GPS module.

8. The method of any one of claims 1 to 7, wherein presenting the user with an option to view real-time video footage captured by a camera comprises presenting the user with an option to purchase access to the real-time video footage.

9. A computing device comprising: at least one processor;

memory accessible to the at least one processor; and

at least one user interface;

wherein the memory stores instructions executable by the at least one processor to cause the computing device to perform the method of any one of claims 1 to 8.

10. A computer-implemented method for facilitating electronic event ticketing, the method comprising:

generating a digital ticket to the at least one event; and

providing the digital ticket to the computing device.

11. The method of claim 10, wherein providing the digital ticket to the computing device comprises emailing the digital ticket.

12. The method of claim 10 or claim 11, wherein providing the digital ticket to the computing device comprises sending the digital ticket via MMS.

13. The method of any one of claims 10 to 12, wherein providing the digital ticket to the computing device comprises making the digital ticket available for download from a URL.

14. The method of any one of claims 10 to 13, wherein the at least one search criterion comprises a geographical location.

15. The method of any one of claims 10 to 14, further comprising receiving the real time video footage stream from a camera located in proximity to the at least one event.

16. The method of claim 15, further comprising receiving the real-time video footage stream from a camera located in proximity to the at least one event via an image processing and handling server.

17. A server system comprising:

at least one server; and

at least one database accessible to the at least one server;

wherein the database stores instructions executable by the at least one server to cause the server to perform the method of any one of claims 10 to 16.

18. A system for facilitating electronic event ticketing, the system comprising:

the server of claim 17; and

at least one computing device of claim 9.

19. The system of claim 18, further comprising a device comprising a scanner, the scanner configured to scan the digital ticket provided to the computing device.

20. The system of claim 19, wherein the device is configured to communicate with the at least one server to determine whether the ticket is valid.

21. The system of any one of claims 18 to 20, further comprising a camera configured to capture at least one of still images and video footage.

22. The system of claim 19, wherein the camera is configured to captured at least one of still images and video footage and to transmit the captured images and/or video footage to the at least one server.

23. A computer-implemented method for facilitating electronic event ticketing, the method comprising:

receiving at least one search criterion from a user interface;

24. A computer-implemented method for facilitating electronic event ticketing, the method comprising:

generating a digital ticket to the at least one event; and

providing the digital ticket to the computing device.

25. The steps, features, integers, components, sub-components, systems, sub systems, devices, structures, assemblies and apparatus disclosed herein or indicated in the specification of this application individually or collectively, and any and all combinations of two or more of said steps, features, integers, components, sub components, systems, sub-systems, devices, structures, assemblies and apparatus.