REAL-TIME SHARING OF INFORMATION CAPTURED FROM DIFFERENT VANTAGE POINTS IN A VENUE

Real-time sharing of imagery captured from different vantage points at a venue is provided. At least one of images and video are captured at different locations and different vantage points in a venue during an event. The images or video are temporarily stored on a server. A spectator requests at least one of images or video from a location and vantage point. If images or video captured at the requested location or vantage point are stored on the server, then a list of the images or video are displayed on a mobile imaging device operated by the spectator requesting the images or video. The spectator selects an image or video from the list, and the image or video is displayed on the mobile device.

DETAILED DESCRIPTION

In one general embodiment, a method that includes capturing images at different locations and from different vantage points in a venue during an event and storing the images on a server. The method continues with selecting a vantage point in the venue and determining if images captured at the selected location or vantage point are stored on the server. If images captured at the vantage point are stored on the server, then displaying a list of the images on a mobile device. The method then selects at least one image from the list and displays the image on the mobile device.

In another general embodiment a method includes capturing at least one of images and video at different locations and from different vantage points in a venue during an event, with at least a portion of the images or video captured using mobile imaging devices. The method continues with uploading the images or video to a server for temporary storage during the event, selecting at least one of a location and vantage point in the venue, and determining if images or video captured at the selected location or vantage point are stored on the server. If images or video captured at the selected location or vantage point are stored on the server, the method then displays a list of the images or video on a mobile device, selects at least one image or video from the list, and displays the image or video on the mobile device. if images or video captured at the selected location or vantage point are not stored on the server, the method then sends a request for capturing images or video at the selected location or vantage point.

In further general embodiment, a system that includes a venue for hosting an event, where the event viewable from a plurality of vantage points in the venue, and vouchers for spectators of the event, with each voucher including machine-readable optical code. The system also includes a plurality of mobile imaging devices, each mobile imaging device including a display capable of reading the optical code for associating a mobile imaging device with the voucher and for displaying images and video. The optical code invokes downloading of venue data to the mobile imaging device that includes spectator location data for identifying locations of mobile imaging devices determined by the associated voucher. The system further includes capturing at least one of images and video at a plurality of spectator locations and from different vantage points using a plurality of mobile imaging devices, such that images or video of the event are captured from a plurality of vantage points throughout the venue, and temporarily storing images or video on a server during the event. In the system, a spectator then requests at least one of images or video from a spectator location and vantage point. The system then determines if images or video captured at the selected spectator location or vantage point are stored on the server. If images or video captured at the requested spectator location or vantage point are stored on the server, the system then displays a list of the images or video on a mobile device of the spectator requesting the images or video, the spectator selects at least one image or video from the list, and displays the image or video on the display of their mobile imaging device. If images or video captured at the requested spectator location or vantage point are not stored on the server, then a request for capturing images or video to a spectator located proximate to the selected spectator location or vantage point is sent.

For purposes of describing the embodiments disclosed herein, two elements are considered to be coupled when one element is able to send an electrical signal to another element. The electrical signal may represent, for example but not limited to, data, operating commands, status information, or electrical power, or any combination of these electrical signals. A coupling may be implemented by wired or wireless connection means.

As illustrated in the Figures, there is shown generally at100, an exemplary embodiment of a system for temporarily gathering, storing, and sharing information, such as images and video captured during an event. In a general embodiment of the system100, at least one of images and video are captured at different locations and from different vantage points and at different times in a venue and stored on a server for the duration of an event. One or more spectators may request either images or video, or both, from a vantage point in the venue and which were captured at a desired point in time. If images or video captured at the requested vantage point and time are stored on the server, then a list of the available images or video are displayed on a mobile device operated by the spectator requesting the images or video. The spectator selects an image or video from the list, and the image or video is displayed on the spectator's mobile imaging device. If no images or video captured at the requested vantage point and time are stored on the server, then the spectator may send a request to other users of the system100for images or video captured at the requested vantage point and time to be uploaded to the server. The spectator may then display the available images or video on their mobile device.

As illustrated inFIG. 1andFIG. 2of the drawings, in one general embodiment the system100includes a venue, shown generally at102, for hosting an event104, a server106for storing data, and more than one remote mobile device108. In a preferred embodiment, the remote mobile devices108include both a display110and a camera112(best seen inFIG. 3) to allow the mobile device108to capture and display either images114or video, or both. Only images114are shown in the Figures, for ease of discussion only. As referred to herein, a spectator116comprises any individual who observes an event104occurring in the venue102. Optionally, a spectator116may comprise a group of individuals observing an event104occurring in the venue102who share a mobile device108.

In a general embodiment, the venue102may comprise any suitable place or location where events104are held. For example, the venue102may comprise a music venue suitable for events104, such as concerts or musical performances and may vary substantially in size. In some embodiments, the venue102may be any suitable music venue ranging from an indoor concert hall to an outdoor arena. In other embodiments, the venue102may comprise an indoor or outdoor place or location where sporting events are held. Examples of sporting event venues include: indoor or outdoor sports stadiums, sports arenas, baseballs parks, ice hockey arenas, motorsport venues, multi-purpose stadiums and similar sports venues. In the embodiments, the venue102may comprise any suitable place or location where events104are held.

As defined herein, an event104may comprise any observable occurrence. An exemplary event104may comprise: a type of gathering a such as a marriage ceremony, a sports competition, a convention or conference, a happening such as an artistic performance, a musical performance, a media event that attracts coverage by media, or a corporate or business function, among many other well-known types of events104. For ease of discussion only, the venue102discussed hereinafter, comprises a sports stadium and the event104occurring in the venue102comprises a sports event occurring on a field118of the venue102.

In a general embodiment, the venue102is organized into several different sections120, with each section120configured with one or more rows122of one or more seats124, as illustrated inFIG. 2. The venue102may optionally comprise more than one level to provide spectators116different vantage points with which to view the event104and to provide increased audience capacity of the venue102. An exemplary venue102may include a lowermost or field level126, and an uppermost or grandstand level128. One or more levels, such as a main level130, may be situated between the field level126and grandstand level128.

Additionally, broadcast cameras132may be positioned about the venue102to capture video or still images of an event104occurring in the venue102. The broadcast cameras132may be in fixed locations in the venue102and may be controlled remotely in some embodiments. For example, a broadcast team for a television network (not shown) may control positioning and repositioning one or more of the broadcast cameras132for transmitting desired video and still images captured by the cameras132across a television network (not shown). Additionally, video and still images captured by the cameras132may also be displayed on monitors134in the venue102.

As illustrated inFIG. 1andFIG. 2, in some embodiments, a server106may be provided for storing images114or video of an event104captured in the venue102. In a general embodiment, the server106may comprise a known computer server coupled to a network136of the venue102. In some embodiments, the network136may comprise a Local Area Network (LAN) contained within the venue102. In optional embodiments, the network136may comprise a LAN connected to external networks, such as the Internet138. The server106may be either located within the venue102or located remotely, depending on the networking scheme of the server106.

In a general embodiment, the server106includes a processor140for running a known operating system (not shown) and memory142for temporary data storage. The server106also includes a data storage system144. In some embodiments, the data storage system144may comprise a plurality of storage devices, such as a known RAID system, providing terabytes of data storage. The processor140is connected to memory142, which may comprise volatile data storage, via memory data and address lines146and to the data storage system144by data bus148.

In some embodiments, both images114and/or video of an event104captured by spectators116and the broadcast cameras132during the event104may be stored on the sever106during the event. In alternative embodiments, only images114and/or video of the event104captured by spectators116during the event104are stored on the sever106.

In some embodiments, images114and/or video of the event104captured by spectators116and the broadcast cameras132during the event104are deleted from the server106upon the conclusion of the event104. In optional embodiments, either the images114and/or video of the event104captured by spectators116or the images114and/or video captured by the broadcast cameras132during the event104are deleted from the server106upon the conclusion of the event104. In alternative embodiments, images114and/or video of the event104captured by either spectators116or the broadcast cameras132are deleted from the server106at some predetermined time after the conclusion of the event104. In a preferred embodiment, at least one of the images114and/or video of the event104captured by either spectators116or the broadcast cameras132are deleted from the server106after the conclusion of the event104, to reduce the data stored on the server106and provide sufficient data storage space for images114and/or video from subsequent events104.

As illustrated inFIGS. 1-3, and particularly toFIG. 3, in exemplary embodiments, one or more of remote mobile devices108may comprise a known mobile device such as a smartphone108. In optional embodiments, the one or more of remote mobile devices108may comprise a mobile computing device, such as a known tablet computer108T. In preferred embodiments, the mobile devices108may comprise suitable, known mobile devices such as smartphones108or tablet computers108T that are capable of capturing and displaying either photos or video, or both and communicating with a network. In smartphone embodiments of the mobile device108, the smartphone108is preferably capable of both telecommunications and wireless data transfer between the device108and a network, such as the LAN136and the Internet138. In tablet embodiments of the mobile device108T, the tablet108T is preferably capable of wireless data transfer between the device108and a network, such as the LAN136and the Internet138.

In the embodiments, the mobile device108includes a housing150that retains the display110. Optionally, the display110may comprise a touchscreen display110to allow a user to input and manipulate data, as well as view data via the touchscreen110. In further optional embodiments, the mobile device108may be configured with both the touchscreen display110and keyboard (not shown). In such an embodiment, the user my input and manipulate data using either or both the keyboard and touchscreen110. Additionally, each remote mobile device108may include a home button152that is also retained in the housing150. The home button152is provided for displaying a home menu (not shown) on the touchscreen110, and may provide additional known functionalities for the mobile device108.

As illustrated inFIG. 3, in general embodiments, each mobile device108includes a processor154for processing data, a memory156, a communications module158, and an on-board power source160, such as a battery. In preferred embodiments, each mobile device108additionally includes both a camera112to allow the mobile device108to capture either images114or video, or both, and a display110for displaying images114, video, and other data. In some embodiments, the processor154is connected to the memory156via memory data and address lines162, to the communications module158by a data bus164, to the camera112via data lines166, and to the display110via data lines168. The memory156may comprise both volatile and nonvolatile data storage, as is known.

In general embodiments, the communications module158provides data transmission and voice communications between the mobile device108and external networks. The communications module158may comprise a component of the processor154or may comprise stand-alone circuitry, as shown inFIG. 3. The communications module158is capable of wirelessly connecting the mobile device108to external networks, such as the LAN136and Internet138. In an exemplary embodiment, the communications module158comprises a known Wi-Fi® transmitter and receiver which provides high-speed data transmission between the mobile device108and LAN136and/or Internet138. Preferably, the communications module158provides data transmission rates sufficient to allow a user to browse websites and access other data on the LAN136and/or Internet138.

In optional embodiments, the communications module158may be configured with a short-range component170. The short-range component170facilitates short-range wireless data transmission for connection to the LAN136, using known technologies such as Bluetooth®. Known telecommunications circuitry172may be provided in smartphone embodiments of the mobile device108, for providing telecommunications functionality. In some embodiments, the telecommunications circuitry172may be coupled to the processor154and/or to the communications module158, allowing the processor154to control the functions of the telecommunications circuitry172, as is known in the art. Alternatively, the telecommunications circuitry172may be directly controlled by a user actuating the telecommunications circuitry172via the display110. Often, the telecommunications circuitry172is controlled by both the processor154and by a user (not shown) of the mobile device108.

An antenna174to facilitate transmission of radio frequency signals may be coupled to the telecommunications circuitry172and to the communications module158. The antenna174is provided to facilitate transmission of radio frequency signals for both data and telecommunications transmissions.

In some embodiments, both data180and application software182may be stored in the memory156. Application software182intended for use on mobile devices, such as smartphones108and tablets108T, is known in the art as an “app”. An app182comprises software which is specifically written for mobile devices and is designed to perform specific tasks. The “app” abbreviation represents both the smaller program size and smaller scope of the application software182. Examples of apps182include media players, for playing music and videos, and weather apps for displaying the current weather on the mobile device108. One or more apps182are typically provided with the mobile device108/108T and additional apps182may be purchased separately by a user.

In preferred embodiments, one such app182comprises a code scanner app182SC for reading optical code, such as barcode or Quick Response Code184(shown inFIG. 4). Quick Response Code184is known in the art as a “QR” code and comprises a type of matrix barcode that is an optical, machine-readable label that consists of black modules that are arranged in a square pattern on a white background. The information encoded in the QR Code184may comprise one or more of four standardized types of data including: numeric, alphanumeric, byte, and binary, as known in the art. Typically, metadata from the QR Code184directs a browser app182B on the mobile device108to a website. Once the browser app182B is navigated to the desired website, information relevant to the QR Code184is displayed on the mobile device's display110.

As illustrated inFIG. 3andFIG. 4, in the embodiments, the code scanner app182SC is invoked for reading a QR Code184. Metadata contained in the QR Code184is read by the code scanner app182SC which then invokes another app182on the mobile device108. In some embodiments, the metadata read from the QR Code184may invoke an automatic download of information regarding the venue102to the mobile device108. In some embodiments, the information regarding the venue102may be stored on the server106and downloaded therefrom. In alternative embodiments, the metadata read from the QR Code184may direct the browser app182B of the mobile device108to a website that provides information regarding the venue102. In an optional embodiment, the metadata read from the QR Code184may invoke a venue app182V which provides information regarding the venue102.

Referring now toFIG. 1andFIG. 2, in the embodiments, information regarding the venue102may include a diagram186(shown as a two-dimensional diagram inFIG. 1), commonly referred to as a “seating chart”, of the venue102, showing the various levels126-130, sections120, and seats122of the venue102. Optionally, the seating chart186of the venue102may comprise a three-dimensional diagram and may provide graphical representation of a spectator's vantage point from a particular seat124in a particular section120of the venue102, as is known.

Additional information regarding the venue102may include location of the broadcast cameras132, exit information, vendors, emergency personnel, and other pertinent information regarding the venue102. Once information regarding the venue102, such as the seating chart186, is displayed on the touchscreen display110of the spectator's mobile device108, they may manipulate the seating chart186using the display110. For example, the spectator116may pinch and drag to increase or decrease the magnification level, known in the art as “zoom in” and “zoom out” of the seating chart186displayed on the display110. The spectator116may then select a seat124in desired section120of the venue102. Once the seat124is selected, they may then view a graphical representation of the vantage point of the venue and field118from the selected seat124.

As illustratedFIGS. 1,2, and4, if a spectator116desires to observe a particular event104occurring in the venue102, they typically must first obtain a voucher190to gain entry into the venue102for the particular event104. The voucher190may comprise a token, such as a piece of paper that the spectator116physically possesses and presents to personnel at the venue102who grant spectators116access to the venue102for the duration of the event104, upon validation of the voucher190. Alternatively, voucher190may be obtained electronically by the spectator116and displayed on the display110the mobile device108that the spectator116possesses. The voucher190typically grants the spectator116access to the venue102for the duration of the event104for observing, or in some instances participating in, the particular event104. The voucher190may provide the spectator116access to any or all available sections120of the venue102, or a particular section120, or a particular seat124in a particular section120of the venue102, depending on the venue102and type of event104occurring. Most frequently, the voucher190entitles the spectator116to a particular seat124in a particular section120of the venue102for the duration of the event104.

In some embodiments, if a spectator116desires to observe a particular event104occurring in the venue102, they typically obtain a voucher190to gain entry into the venue102. The spectator116presents the voucher190to personnel or devices, such as a known QR code scanner (not shown), to gain entry into the venue102for the duration of the event104. In optional embodiments, the voucher190may be an electronic voucher190with its QR Code184displayed on the display110of the spectator's mobile device108. The QR code184on the voucher190is scanned by the scanner, which reads the metadata contained in the QR code184and displays information regarding the voucher190to an operator of the scanner. This information may include confirmation that the voucher190is indeed valid for the event104and venue location information to which the voucher190corresponds. The venue location information may include the section120, row122, and seat124to which the voucher190corresponds, thus indicating to the spectator116their assigned seat124for the event104.

As illustrated inFIG. 2, in the embodiments, one or more seats124may be configured with an identification device192. The identification device192may be provided to indicate the exact position of the seat124in the venue102. In a preferred embodiment, the identification device192comprises a known Radio-frequency identification tag (RFID) that uses radio-frequency electromagnetic fields to transfer data from the RFID tag192attached to a seat124, for the purposes of automatically identifying the location and position of the seat124in the venue102.

Referring to the drawings Figures, and particularly toFIG. 5, a flowchart of an exemplary embodiment of a method for temporarily gathering, storing, and sharing information, such as images and video captured during an event in accordance with an exemplary embodiment of the invention, is shown generally at200. The process200starts with start block202. In process block204, each spectator116presents a voucher190to personnel or devices, to gain entry into the venue102for the duration of the event104. Spectators116procure vouchers190for the event104using well known methods. In the embodiments, the voucher190may comprise a token, such as a piece of paper that the spectator116physically possesses or may be electronic and displayed on the display110the mobile device108that the spectator116possesses. In process block206, the voucher190, is validated and the spectator116is granted access to the venue102for the duration of the event104. In typical embodiments, the voucher190entitles the spectator116to a particular seat124in a particular row122of a section120of the venue102to which the voucher190corresponds.

The method200continues to process block208, where the QR code184on the voucher190is scanned and the code scanner app182SC is invoked to read the voucher's QR Code184. In some embodiments, in process block208QR Code184read by the code scanner app182SC which optionally invokes another app182on the mobile device108or may invoke an automatic download of information regarding the venue102to the mobile device108, as previously discussed. In some embodiments, the QR Code184may invoke the venue app182V, which displays and provides interaction with information regarding the venue102, such as the seating chart186and other venue information. The spectator116may use the venue app182V to navigate their way to their assigned seat124, shown in process block210.

In process block212, an event104is underway in the venue102and spectators116may capture images114and/or video using the camera112of their mobile device108. As images114and/or video are captured, they are automatically time-stamped by the mobile device108, as known in the art. As images114and/or video are captured, spectators116may choose to upload the images114and/or video to the server106, in process block214. Images114and/or video captured by the broadcast cameras132may also be uploaded to the server106and are available to view by spectators116. Spectators116may upload the images114and/or video to the server106using the venue app182V on their mobile device108or, optionally, may use other known means. Additionally, as images114and/or video are uploaded to the server106, data indicating the particular seat124, row122, and section120provided by the RFID tag192attached to the seat124, is attached to the images114and/or video as they are uploaded.

In process block216, a spectator116may desire to view a particular portion of the event104from a vantage point other than their own vantage point from their assigned seat124. A spectator116may desire to view a particular portion of the event104from a vantage point other than their own vantage point at any time for the duration of the event104. For example, a spectator116is sitting in the first seat124, of the third row122of a section120, such as section 3 (shown inFIG. 1andFIG. 2) of the venue102. They determine they want to view a particular portion of the event104from a vantage point other than theirs in the venue102.

In process block218, the spectator116ascertains from which vantage point they'd like to view the particular portion of the event104. In some embodiments, they may view the venue's seating chart186to ascertain from which vantage point they'd like to view the particular portion of the event104. For example, they may be viewing a sporting event and they desire to see a play that occurred on the end of the field118at a distance to their seat124. They may view the seating chart186and determine that they want to view the desired play from a section120, such as section 57 (shown inFIG. 1andFIG. 2) of the venue102. Optionally, they may also desire to view the play from a particular seat124in a particular section122in the desired section. They also know that the desired play occurred a two minutes in the past, so a particular time period in the recent past is selected in process block220.

The spectator116may then navigate to the server106using the venue app182V on their mobile device108, or known means, in process block222. In process block224, the spectator116then inputs the desired section120, such as section 57, of the venue102and any other information for viewing images114and/or video captured from the desired vantage point and time, so that they may view the desired portion of the event104from the desired vantage point and time.

In decision block226it is determined if images114and/or video images114and/or video captured from the desired vantage point and time are uploaded to the server106. If images114and/or video captured from the desired vantage point and time are uploaded to the server106, then a listing196of images114(shown inFIG. 1) and/or video captured from the desired vantage point and time are displayed on the display110of the spectator's mobile device108, in process block228. In process block230, the spectator116may then scroll through the listing196, select an image114or video, and then display the image114or video on the display110of their mobile device108.

In decision block232the spectator116determines if they want to view an additional image114or video from captured from the desired vantage point and time. If the spectator116determines they want to view an additional image114or video from captured from the desired vantage point and time, then the process returns to decision block226, where it is determined if images114and/or video images114and/or video captured from the desired vantage point and time are uploaded to the server106.

If the spectator116determines they do not want to view an additional image114or video, then the method200continues to process block234. If the spectator116determines they want to view an additional image114or video from captured from a different vantage point or time or both, the process returns to decision block226, where it is determined if images114and/or video images114and/or video captured from the desired vantage point and time are uploaded to the server106.

Returning to decision block226, if it is determined images114and/or video images114and/or video captured from the desired vantage point and time are not uploaded to the server106, then the spectator116sends a request to the system100for images114and/or video taken from the desired vantage point and time to be uploaded to the server106, in process block236. In process block238, one or more spectators116located in the desired section120may receive the request. The request may specify seat124and row122in optional embodiments. In process block240, a one or more spectators116located in the desired section120that have captured images114and/or video from the desired vantage point and at the desired time, they may then upload the desired images114and/or video to the server106. The method200then continues to process block234, where the event104concludes. In process block242, images114and/or video of the event104captured by spectators116and the broadcast cameras132during the event104are deleted from the server106upon the conclusion of the event104, as discussed previously. In optional embodiments, images114and/or video of the event104captured by either spectators116or broadcast cameras132are deleted from the server106at some predetermined time after the conclusion of the event104. In a preferred embodiment, at least one of the images114and/or video of the event104captured by either spectators116or the broadcast cameras132are deleted from the server106after the conclusion of the event104, to reduce the data stored on the server106and provide sufficient data storage space for images114and/or video from subsequent events104. The method200then ends at end block244.

Those skilled in the art will appreciate that various adaptations and modifications can be configured without departing from the scope and spirit of the embodiments described herein. Therefore, it is to be understood that, within the scope of the appended claims, the embodiments of the invention may be practiced other than as specifically described herein.