Facial recognition for event venue cameras

Abstract

An event venue with a performance area (e.g., a sport field or auditorium stage) and an eventgoer area (e.g., stadium seating or bleachers) may include a set of eventgoer cameras trained on various sections of the eventgoer area and a set of performance cameras trained on the performance area. The event venue may also include sensors. When an event occurrence (e.g., a goal or touchdown) is detected using the cameras and/or sensors, at least one photo or video of the event occurrence may be captured by the performance cameras, and at least one photo or video of the eventgoer reaction may be captured using the eventgoer cameras. Facial recognition may then be used to identify particular eventgoers in each photo or video. Identified eventgoers can then receive photos or videos in which they are identified along with performance photos or videos that were captured at roughly the same time.

Claims

1. A computer-implemented method for event venue camera usage, the method comprising: storing one or more reference photographs in a memory, the one or more reference photographs depicting at least a face of an eventgoer; receiving sensor data from a collision camera located in an event venue during a sporting event; detecting a collision involving a predetermined visually recognizable object in a performance area of the event venue based on computerized visual collision detection using the received sensor data, wherein the collision corresponds to a gameplay occurrence during the sporting event; triggering capture of a performance visual media of the collision in the performance area of the event venue during the sporting event using a performance camera whose view includes at least a portion of the performance area; triggering capture of an eventgoer visual media of an eventgoer area of the event venue using an eventgoer camera whose view includes at least a portion of the eventgoer area at a same time during the sporting event as the capture of the performance visual media of the collision, wherein the eventgoer camera is distinct from the performance camera, wherein the eventgoer area is distinct from the performance area; recognizing that a face detected within the eventgoer visual media matches the face of the eventgoer as depicted in the stored one or more reference photographs; sending, to a user device associated with the eventgoer, a confirmation request that includes at least a subset of the eventgoer visual media and that requests a confirmation that the face detected within the eventgoer visual media is the face of the eventgoer; receiving, from the user device, the confirmation that the face detected within the eventgoer visual media is the face of the eventgoer; and transmitting the eventgoer visual media and the performance visual media to the user device associated with the eventgoer.

2. The method of claim 1, wherein the performance visual media includes a video frame.

3. The method of claim 1, wherein the eventgoer visual media includes a video frame.

4. The method of claim 1, wherein detecting the collision is also based on an indication that a sound is detected at a microphone, further comprising receiving the indication that the sound is detected via the microphone.

5. The method of claim 1, wherein the collision camera is the performance camera.

6. The method of claim 1, wherein detecting the collision is also based on an indication that pressure is detected at a predetermined area via a pressure sensor, further comprising receiving the indication that pressure is detected at the predetermined area via the pressure sensor.

7. The method of claim 1, wherein the eventgoer visual media includes a photograph.

8. The method of claim 1, further comprising saving the eventgoer visual media to a network storage device accessible by the user device associated with the eventgoer.

9. The method of claim 1, further comprising printing the eventgoer visual media.

10. The method of claim 1, further comprising receiving payment information from the user device associated with the eventgoer.

11. A system for event venue camera usage, the system comprising: a memory that stores one or more reference photographs depicting at least a face of an eventgoer; a collision camera located in an event venue during a sporting event, wherein the collision camera produces sensor data during the sporting event; a performance camera whose view includes at least a portion of a performance area of the event venue during the sporting event; an eventgoer camera that is distinct from the performance camera and whose view includes at least a portion of an eventgoer area of the event venue that is distinct from the performance area; and a processor of an eventgoer photo network device, wherein execution of instructions stored in the memory by the processor causes the eventgoer photo network device to: detect a collision involving a predetermined visually recognizable object in the performance area of the event venue based on computerized visual collision detection using the sensor data, wherein the collision corresponds to a gameplay occurrence during the sporting event, capture a performance visual media of the collision in the performance area of the event venue during the sporting event using the performance camera, capture, at a same time during the sporting event as the capture of the performance visual media of the collision, an eventgoer visual media of the eventgoer area of the event venue using the eventgoer camera, recognize that a face detected within the eventgoer visual media matches the face of the eventgoer as depicted in the stored one or more reference photographs, send, to a user device associated with the eventgoer, a confirmation request that includes at least a subset of the eventgoer visual media and that requests a confirmation that the face detected within the eventgoer visual media is the face of the eventgoer, receive, from the user device, the confirmation that the face detected within the eventgoer visual media is the face of the eventgoer, and transmit the eventgoer visual media and the performance visual media to the user device associated with the eventgoer.

12. The system of claim 11, wherein the performance visual media includes a video frame.

13. The system of claim 11, wherein the eventgoer visual media includes a video frame.

14. The system of claim 11, wherein detecting the collision is also based on an indication that a sound is detected at a microphone, further comprising the microphone.

15. The system of claim 11, wherein the collision camera is the performance camera.

16. The system of claim 11, wherein detecting the collision is also based on an indication that pressure is detected at a predetermined area via a pressure sensor, further comprising the pressure sensor.

17. The system of claim 11, wherein the eventgoer visual media includes a photograph.

18. The system of claim 11, further comprising a network storage device accessible by the user device associated with the eventgoer, the network storage device to receive the eventgoer visual media from the eventgoer photo network in response to receipt of a payment from the user device to the eventgoer photo network.

19. The system of claim 11, further comprising a printer to print the eventgoer visual media in response to receipt of payment information from the user device to the eventgoer photo network.

20. A non-transitory computer-readable storage medium, having embodied thereon a program executable by a processor to perform a method for event venue camera usage, the method comprising: storing one or more reference photographs in a memory, the one or more reference photographs depicting at least a face of an eventgoer; receiving sensor data from a collision camera located in an event venue during a sporting event; detecting a collision involving a predetermined visually recognizable object in a performance area of the event venue based on computerized visual collision detection using the received sensor data, wherein the collision corresponds to a gameplay occurrence during the sporting event; triggering capture of a performance visual media of the collision in the performance area of the event venue during the sporting event using a performance camera whose view includes at least a portion of the performance area; triggering capture of an eventgoer visual media of an eventgoer area of the event venue using an eventgoer camera whose view includes at least a portion of the eventgoer area at a same time during the sporting event as the capture of the performance visual media of the collision, wherein the eventgoer camera is distinct from the performance camera, wherein the eventgoer area is distinct from the performance area; recognizing that a face detected within the eventgoer visual media matches the face of the eventgoer depicted in the stored one or more reference photographs; sending, to a user device associated with the eventgoer, a confirmation request that includes at least a subset of the eventgoer visual media and that requests a confirmation that the face detected within the eventgoer visual media is the face of the eventgoer; receiving, from the user device, the confirmation that the face detected within the eventgoer visual media is the face of the eventgoer; and transmitting the eventgoer visual media and the performance visual media to the user device associated with the eventgoer.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 illustrates an event venue camera ecosystem.

(2) FIG. 2 is a flow diagram illustrating exemplary ticket purchase and user profile operations.

(3) FIG. 3 is a flow diagram illustrating exemplary graphical user interfaces of camera interactions of an eventgoer photo application.

(4) FIG. 4 is a flow diagram illustrating exemplary operations of a photo trigger software.

(5) FIG. 5 is a flow diagram illustrating exemplary operations of an eventgoer face finder software.

(6) FIG. 6 illustrates an exemplary graphical user interface for a post-game portal.

(7) FIG. 7 is a flow diagram illustrating exemplary operations of a photo trigger software.

(8) FIG. 8 illustrates an exemplary overall method of the present invention as described herein.

(9) FIG. 9 illustrates an exemplary overall method of the present invention as described herein.

(10) FIG. 10 is a block diagram of an exemplary computing device that may be used to implement an embodiment of the present invention.

DETAILED DESCRIPTION

(11) An event venue with a performance area (e.g., a sport field or auditorium stage) and an eventgoer area (e.g., stadium seating or bleachers) may include a set of eventgoer cameras trained on various sections of the eventgoer area and a set of performance cameras trained on the performance area. The event venue may also include sensors. When an event occurrence (e.g., a goal or touchdown) is detected using the cameras and/or sensors, at least one photo or video of the event occurrence may be captured by the performance cameras, and at least one photo or video of the eventgoer reaction may be captured using the eventgoer cameras. Facial recognition may then be used to identify particular eventgoers in each photo or video. Identified eventgoers can then receive photos or videos in which they are identified along with performance photos or videos that were captured at roughly the same time.

(12) FIG. 1 illustrates an event venue camera ecosystem.

(13) The event venue camera ecosystem of FIG. 1 includes an event venue 100. The event venue 100 may be any type of event venue used to host any type of event, public or private. For instance, the event venue may be a venue for any type of entertainment or cultural events that are presented at a theater, gymnasium, church, stadium, or other facility to a group of people. Such events include a wide variety of sporting events such as football (American and Global), baseball, basketball, soccer, ice hockey, lacrosse, rugby, cricket, tennis, track and field, golf, cycling, motor sports such as automobile or motorcycle racing, horse racing, Olympic games, and the like; cultural events such as concerts, music festivals, plays, or the opera, and the like; religious events; and more permanent exhibitions such as a museum, historic home, and the like.

(14) The event venue 100 of FIG. 1 includes two performance cameras 118, which are cameras trained on a performance area of the event venue, such as a field or court of a sports venue or a stage of an auditorium or theatre or lecture hall or a pulpit of a church or political/legislative/judicial building. The event venue 100 of FIG. 1 also includes six eventgoer cameras 120, which are cameras that are each trained on one or more eventgoers in one or more eventgoer-camera-view areas. Eventgoer-camera-view areas may include areas that include eventgoers in bleachers, stadium seats, auditorium seats, concert seats, lecture hall seats, standing room floors, or some combination thereof.

(15) The entire eventgoer area of event venue 100 of FIG. 1 is divided into six eventgoer sections, identified as section 104, section 106, section 108, section 110, section 112, and section 114. These may be physically separated sections, such as separate bleacher sections or separate balconies or separate seating sections or separate standing room floors, or they may be symbolic divisions (e.g., representing eventgoer-camera-view areas, fractional or geographical divisions of the event venue eventgoer area, ticket-price divisions based on different seats prices in certain eventgoer sections, or arbitrary divisions). In the event venue camera ecosystem of FIG. 1, each eventgoer section includes a single eventgoer camera of the set of eventgoer cameras 120, but in other cases an eventgoer section may lack a eventgoer camera or have more than one eventgoer camera.

(16) The eventgoer cameras 120 and performance cameras 118 may be cameras capable of taking photographs, video, or both. The photographs and/or video recordings captured by the eventgoer cameras 120 and performance cameras 118 may be captured over a light capture spectrum that includes at least part of the visible light spectrum, and may also (or alternately) include at least part of the infrared light spectrum or ultraviolet light spectrum. The eventgoer cameras 120 and performance cameras 118 may also capture sound through microphones, and may include other sensors (e.g., motion sensors). Each camera of the eventgoer cameras 120 and performance cameras 118 may record its captured camera feed on a memory system 720, a mass storage system 730, a portable storage system 740, or an analog visual storage medium such as a videotape or a negative. Each camera of the eventgoer cameras 120 and performance cameras 118 may transmit data, such as photograph data or video/audio data, via a wired or wireless transceiver.

(17) The event venue 100 of FIG. 1 also includes a set of transmitters 122. Each transmitter of the transmitters 122 may optionally be paired with a specific eventgoer camera of the eventgoer cameras 120, or may be independent of the eventgoer cameras 120, or may alternately be missing entirely from the event venue camera ecosystem. The transmitters may be used to transmit camera feed data from one or more of the eventgoer cameras 120 and/or one or more of the performance cameras 118 to one or more user devices 140 used by eventgoers.

(18) The transmitters 122 may be wireless transmitters capable of transmitting data wirelessly using one or more of a variety of wireless communication technologies. For example, each transmitter of the transmitters 122 may wirelessly transmit data using a Wi-Fi connection module, a 3G/4G/LTE cellular connection module, a Bluetooth connection module, a Bluetooth low energy connection module, Bluetooth Smart connection module, a near field communication (NFC) module, a radio wave communications module, a microwave communications module, a magnetic induction transmitter, a magnetic resonance transmitter, an electromagnetic radiation transmission module, a visible light communication (VLC) transmission lamp/laser/module, a speaker (e.g., audible sound transmitter, ultrasonic transmitter, infrasonic transmitter, with or without noise cancelling features), or some combination thereof. Each transmitter of the transmitters 122 may include any number of sub-transmitters.

(19) The event venue 100 of FIG. 1 also includes various event sensors 102. The event sensors 102 may include a microphone to identify a particular sound-based event occurrence (e.g., cheering from a crowd of eventgoers). The event sensors 102 may also include a thermometer to identify a particular heat-based event occurrence (e.g., fireworks or sparklers). The event sensors 102 may also include a speed detector to identify a particular speed-based event occurrence (e.g., a pre-determined speed is surpassed by a racer or athlete). The event sensors 102 may also include a barometer, a humidity sensor, a pressure sensor (e.g., to detect footsteps over a particular area or a ball/puck/Frisbee entering a goal/hole/basket), a light sensor, a motion sensor, a timer, a collision sensor, or another type of sensor. Some of these sensors may work in conjunction with the eventgoer cameras 120 and performance cameras 118; for example, a collision sensor can use computer vision and motion tracking techniques applied to the camera feeds of performance cameras 118 to detect collision-based event occurrence (e.g., a goal/touchdown/basket is scored, a foul/tackle/brawl occurs, a pass is caught or intercepted).

(20) The event venue 100 of FIG. 1 also includes a beacon 124, which may be a router or bridge or other type of network connectivity device. The beacon 124 may connect at least subsets of the various devices associated with the event venue 100 (e.g., the performance cameras 118, the eventgoer cameras 120, the transmitters 122, the event venue sensors 102) to each other and/or to a network connection 190. The network connection 190 may be an Internet connection 190 or an intranet connection 190 to a Local Area Network (LAN) or to a Wireless Local Area Network (WLAN) or to a Municipal Area Network (MAN) or to a Wide Area Network (WAN) through the network connection 190, the beacon 124 can connect the event venue 100 to a ticketing service 130, an event venue system 160, and a user device 140.

(21) The event venue camera ecosystem of FIG. 1 includes the user device 140. The user device 140 may be a computing device 1000 or a device with a subset of components that might be found in a computing device 1000, and may for example be a smartphone device, a tablet device, a laptop computer device, a portable media player device, a portable video game console device, or a portable e-book reader device.

(22) Each user device 140 may be capable of receiving and/or transmitting wireless data through a communication transceiver 150, which may include communication modules such as those described in relation to the beacon 124 of the event venue 100, and may connect to the network connection 190.

(23) Each user device 140 may also include a memory 148, which may include a memory system 1020, a mass storage system 1030, a portable storage system 1040, or some combination thereof. The user device 140 may store various data structures and software elements in the memory 148. Some of these software elements may include an operating system 142, an eventgoer photo software application 144 (e.g., which may interface with the eventgoer photo network 162 of the event venue system 160), and a wireless transmission decoder 146. The user device 140 may also include a camera 152 that is capable of taking photos and/or videos.

(24) The event venue camera ecosystem of FIG. 1 includes the ticketing service 130. The ticketing service 130 may include one or more computer systems 1000, which may be connected together in a network (e.g., LAN or WLAN) or distributed throughout the Internet. The ticketing service 130 systems may be connected to the network connection 190 through one or more communication transceivers 132, which may include communication modules such as those described in relation to the beacon 124 of the event venue 100.

(25) The ticketing service 130 may allow users to the ticketing service 130 to purchase event tickets using a ticketing graphical user interface (GUI) 134, which may be provided through a website or a software application running on a user device 140, for example. The computer systems included as part of the ticketing service 130 may be used to host network-based resources for the ticketing graphical user interface (GUI) 134 and/or provide an application programming interface (API) for software applications running on user devices 140.

(26) The event venue camera ecosystem of FIG. 1 includes the event venue system 160. The event venue system 160 may be associated with the event venue 100 or with an owner of the event venue 100 or with a manager of an event held at the event venue 100. The event venue system 160 may include one or more computer systems 1000, which may be connected together in a network (e.g., LAN or WLAN) or distributed throughout the Internet. The event venue system 160 may be used to execute an eventgoer photo network 162, which may be connected to the network connection 190 through one or more communication transceivers 164, which may include communication modules such as those described in relation to the beacon 124 of the event venue 100. At least a subset of the event venue system 160 may optionally be located at the event venue 100.

(27) The eventgoer photo network 162 may include a variety of software elements and data structures. In particular, the eventgoer photo network 162 may include a post-event portal 166, which may be a software application and/or website that include a graphical user interface (GUI) allowing eventgoers to view eventgoer photos taken (e.g., via one or more eventgoer cameras 120) of themselves in conjunction with event occurrence photos taken (e.g., via one or more performance cameras 118) of particular event occurrences (e.g., event occurrences that took place at roughly the same time or a similar time as the eventgoer photo so as to show the eventgoer's reaction to the event occurrence). The post-event portal 166 may also include or be associated with a photo ops section 168 that may notify the eventgoer regarding when the next photo of the eventgoer is scheduled to be taken (e.g. via one or more eventgoer cameras 120).

(28) The eventgoer photo network 162 may also include a wireless software 170, which may manage transmission of camera feed data (e.g., photos, videos, audio) from the eventgoer cameras 120 and performance cameras 118 to the user devices 140.

(29) The eventgoer photo network 162 may also include an eventgoer face finder software 172, which may identify faces of particular eventgoers within photos or videos taken by one or more of the eventgoer cameras 120, or by the performance cameras 118 if any eventgoers are visible in those photos or videos. In particular, the eventgoer face finder software 172 may use facial recognition software, feature recognition software, and other types of computer vision software. The eventgoer face finder software 172 may recognize the face of an eventgoer based on one or more previously given photos of the eventgoer's face (e.g., generated by cameras within the event venue 100 upon entry by the eventgoer or uploaded by the eventgoer when purchasing the ticket to the event or when completing a user profile for the post-event portal 166 and/or the ticketing service 130).

(30) The eventgoer photo network 162 may also include a photo trigger software 174, which may detect event occurrences by using the performance cameras 118, the eventgoer cameras 120, the event venue sensors 102, or some combination thereof. For example, the photo trigger software 174 may determine that a photo should be taken based on a visually detected collision (e.g., a goal/touchdown/basket is scored, a foul/tackle/brawl occurs, a pass is caught or intercepted), based on a sound (e.g., a crowd of eventgoers cheering, a new song starts playing, a buzzer or whistle is heard), based on crowd movements (e.g., a crowd of eventgoers performs a wave crowd movement or other visual cheer, or a performer or eventgoer performs a crowd-surfing maneuver), based on a timed schedule (e.g., an absolute schedule defining clock times or a relative schedule defining time interval lengths), based on a manual input by a manager or administrator or eventgoer, or based on some combination thereof.

(31) The eventgoer photo network 162 may also include a payment system 176, which may allow the eventgoer photo network 162 to accept payments from eventgoers electronically via credit card inputs, debit card inputs, bank account inputs, or electronic payment account (e.g., PayPal, VenMo, Stripe, Apple Pay, Google Wallet/Pay, Amazon Payments, Facebook Payments) inputs, or scanned/photographed checks.

(32) The eventgoer photo network 162 may also include a photo database 178, which may store camera feed data (e.g., images, videos, audio, timestamps, metadata) from performance cameras 118 and eventgoer cameras 120. The eventgoer photo network 162 may also include a user database 180, which may store user profile information from the eventgoer photo software application 144 of the user device 140. One or more reference photos that the eventgoer face finder software may use to locate particular a eventgoer's face in the camera feed photos may be stored in the user database 180 alongside the user profile data, but may also (or alternately) be stored in the photo database 178.

(33) FIG. 2 is a flow diagram illustrating exemplary ticket purchase and user profile operations.

(34) At step 205, a user using a user device 140 purchases a ticket for an event via the ticketing service 130. The ticket may be purchases using a ticketing GUI 134 of the ticketing service 130. The ticketing GUI 134 may include a ticket details section 245 identifying a date, time, and price of a ticket, as well as a seating section section 250 identifying a particular eventgoer section of the event venue, and a seat number section 255 identifying a particular seat number. The ticketing GUI 134 finally includes a buy button 260 allowing the user to buy the ticket or tickets with the identified characteristics.

(35) At step 210, the user may be prompted at the user device 140 to buy and/or download the eventgoer photo software application 144. The eventgoer photo software application 144 may cost money or may be free, and may be obtained from a software repository such as an application store or an app store, or may be contained within a website.

(36) At step 215, the user uses the user device 140 to download, install, and launch the eventgoer photo software application 144.

(37) An exemplary eventgoer photo software application profile entry GUI 220 is illustrated in FIG. 2. The eventgoer photo software application profile entry GUI 220 includes a complete your profile section 225 identifying a name, email address, seat number, eventgoer section, and ticket ID associated with the user's profile. The eventgoer photo software application profile entry GUI 220 also includes a facial recognition reference photo section 230 allowing the user to upload a recently taken or stored photo of the user's face that can then be used by the eventgoer face finder software 172 of the eventgoer photo network 162. The eventgoer photo software application profile entry GUI 220 also includes a billing info section 235 allowing the user to input information related to the use of the payment system 176 under the user's profile/account. The eventgoer photo software application profile entry GUI 220 also includes a next button 265 that completes entry of the user's profile/account information.

(38) The information input into the eventgoer photo software application profile entry GUI 220 may then be stored in the user database 180 of the eventgoer photo network 162.

(39) Once the next button 265 of the eventgoer photo software application profile entry GUI 220 is pressed, the eventgoer photo software application 140 may go to an eventgoer photo software application profile complete GUI 240, in which a message is displayed identifying that the user's profile is complete, and to check back after the event for the user's photos.

(40) FIG. 3 is a flow diagram illustrating exemplary graphical user interfaces of camera interactions of an eventgoer photo application.

(41) The eventgoer photo software application 144 may include multiple GUIs for various operations and purposes related.

(42) The eventgoer photo software application 144 may include a GUI 305 that identifies that the user is currently at an event at event venue 100. GUI 305 allows the user to edit his/her user profile (e.g., see profile entry GUI 220 of FIG. 2), access the post-event portal 166, or identify and/or interact with one or more of the eventgoer cameras 120 with or without transmitters 122.

(43) The eventgoer photo software application 144 may include a GUI 310 that identifies that the user device 140 running the eventgoer photo software application 144 is currently searching for a transmitter signal for one or more transmitters of the transmitters 122. The GUI 310 may follow from a press of the Tsmtr Cams button of GUI 305.

(44) The eventgoer photo software application 144 may include a GUI 315 that identifies that a camera has been found, which may optionally have a transmitter. The GUI 315 then identifies the camera as Camera 1 of Eventgoer Section 3, and identifies that the next planned photo opportunity will occur in five minutes. The GUI 315 may have a more ops button that then identifies other photo opportunities. The GUI 315 may follow from the GUI 310.

(45) The eventgoer photo software application 144 may include a GUI 320 that identifies multiple nearby photo opportunities and when they will occur. For example, the GUI 320 identifies that Camera 3 of Eventgoer Section 2 will take a photo in 10 minutes, that a camera at the Bud Light Booth will take a photo in 30 seconds, and that a Balcony Camera 2 in a (Balcony) Eventgoer Section 6 will take a photo in 5 minutes. Each identified camera photo opportunity notification may include a corresponding more button for more information. The GUI 320 may follow from a press of the more ops button of GUI 315.

(46) The eventgoer photo software application 144 may include a GUI 325 that identifies more information about a particular selected camera. For example, the GUI 325 of FIG. 3 includes more information about the Balcony Camera 2 in a (Balcony) Eventgoer Section 6, identifies that the next planned photo opportunity will be in 5 minutes, and identifies a reminder notification relevant to that camera (Reminder: don't forget to turn around and look up Reminder: don't forget to turn around and look up) that in some cases may be customizable and trigger a notification at the user device 140 when the photo opportunity time approaches. The GUI 325 may follow from a press of the more button next to Balcony Cam 2, Sec 6: 5 min of GUI 315.

(47) FIG. 4 is a flow diagram illustrating exemplary operations of a photo trigger software.

(48) At step 405, the event venue seniors 102 (e.g., optionally in conjunction with the performance cameras 118 and/or eventgoer cameras 120) can detect an event occurrence, such as an eventgoer crowd cheer, a kickoff, a touchdown/goal, an eventgoer crowd chant, a scheduled photo opportunity (e.g., based on a clock or timer), or any other event occurrence described previously.

(49) At step 410, one or more eventgoer cameras of the eventgoer cameras 120 (e.g., identified by camera numbers 1 through N) take one or more photos or videos for each of a set of one or more eventgoer sections (e.g., identified by section numbers 1 through N), which are paired with a time stamp either marked on each photo/video itself or included within the metadata of each photo/video.

(50) At step 415, one or more performance cameras of the performance cameras 118 (e.g., identified by camera numbers 1 through N) take one or more photos or videos of the performance area 116, which are paired with a time stamp either marked on each photo/video itself or included within the metadata of each photo/video.

(51) At step 420, the images/videos, camera data (e.g., image/video metadata and data identifying each camera by number and/or location), and time stamp data are stored in the photo database 178 of the eventgoer photo network 162 at the event venue system 160.

(52) At step 425, the cameras may reset if necessary and prepare for the next event occurrence.

(53) FIG. 5 is a flow diagram illustrating exemplary operations of an eventgoer face finder software.

(54) At step 505, a first image (e.g., a photograph or a video frame from one of the cameras of the set of eventgoer cameras 120 or of the set of performance cameras 118) is retrieved from the photo database 178.

(55) At step 510, the first image is scanned using a first pass of a facial recognition algorithm to detect human faces within in the image.

(56) At step 515, the camera data can be analyzed to determine an eventgoer section number that the camera's viewing area includes, and in some cases, the camera feed data can also be analyzed to determine individual seat numbers and who should be sitting in them based on the tickets sold.

(57) At step 520, user data is retrieved from the user database 180, including user reference photos of users' faces.

(58) At step 525, the first image, and the human faces detected within it at step 510, are compared to the user reference face photos that were pulled from the user database 180 in step 520.

(59) At step 530, the eventgoer face finder software 172 determines whether there was at least one match found in the comparison of step 525.

(60) If there were no matching faces detected at step 530, then at step 555, the next image (e.g., the next photograph or video frame) from the photo database 178. As specified in step 560, the operations of FIG. 5 are then repeated for all images in the photo database 178.

(61) If there was at least one matching face detected at step 530, then at step 535, the first image is tagged with the associated user's name, username, email, phone number, account, profile identifier, or other profile information. The tag may be a marking on the first image, information stored in the photo database 178, or information stored in metadata associated with the first image.

(62) At step 540, the face tags are stored, in the form of an updated image (e.g., if the tag is in the form of a marking on the first image or information stored in metadata associated with the first image) and/or an updated entry in the photo database 178 (e.g., if the tag is in the form of information stored in the photo database 178).

(63) At step 545, the tagged photo is delivered to tagged users, and in particular, to user devices 140 belonging to the tagged users. The tagged images may be delivered directly to the user devices 140 via one or more of the transmitters 122, either relatively immediately or after the event is over. The tagged images may also or alternately be uploaded, at step 550, to the post-game portal 166.

(64) After step 545 or step 550, the eventgoer face finder software 172 may perform step 555, in which it retrieves the next image (e.g., the next photograph or video frame) from the photo database 178. As specified in step 560, the operations of FIG. 5 are then repeated for all images in the photo database 178.

(65) FIG. 6 illustrates an exemplary graphical user interface for a post-game portal.

(66) The GUI 600 of the post-game-portal 166 of FIG. 6 includes a variety of GUI elements. In particular, the GUI 600 includes a sign-in section 605, allowing a user to sign in using sign-in credentials such as a username and password (alternate sign-in sections can request an email and password, or a certificate signed by a certificate authority, or a biometric scan).

(67) The GUI 600 includes a Face Finder Tagged You section 610, in which an image from the photo database 178 that depicts one or more eventgoers, one of which was identified by the eventgoer face finder software 172 to match a reference photo of the user, is presented. An Is this You? section is also presented, allowing confirmation from the user via a Yes, Add to Album button 645 or negation via a No, Not Me button 650. Images that are confirmed by the user as depicting the user can then be added to a multimedia album associated with the user. If the image is a frame of a video, the entire video can be added to the multimedia album associated with the user. Other frames of the video then may or may not require separate confirmation via similar Is this You? 620 queries.

(68) A field at same time section 615 may include an image or video that is also presented to the user, which may show a photo, a video, or a video frame of the performance area 116 as captured by one or more of the performance cameras 118 at substantially the same time as the image in the Face Finder Tagged You section 610 was captured. The field at same time section 615 may provide context for the Face Finder Tagged You section 610; for example, the field at same time section 615 may show a photo of an exciting goal or touchdown or song finale, and the Face Finder Tagged You section 610 may show a photo of the user reacting excitedly. The images or video featured in the field at same time section 615 may be saved with a save button 655, printed with a print button 660, or a print may be purchased via a buy a print button 665.

(69) A view album button 625 may then be provided in order to give the user the ability to view the entire multimedia album associated with the user. The multimedia album associated with the user may be stored at the event venue system 160 (e.g., at the photo database 178 and/or the user database 180) and/or at the user device 140, and may include photos in which the user's face was identified and/or may include videos in which the user's face was identified in one or more frames of the video.

(70) A photo ops button 630 may transfer the user to a photo opportunities GUI 635. The photo opportunities GUI 635 may then identify other images, videos, or video frames from various scheduled photos or videos taken by eventgoer cameras 120, as identified in the GUI 320 of the eventgoer photo app 144, for example. The photo opportunities GUI 635 may identify a camera (e.g., Balcony Cam 2) of the eventgoer cameras 120, and may include a is this you? interface 640 with a yes or no option similar to the Face Finder Tagged You section 610. The photo opportunities GUI 635 may then include options to buy, save or print (or buy a print) via a sales interface 670.

(71) The payment system 176 described in relation to FIG. 1 may be tied to the save button 655, the print button 660, the buy a print button 665, the Yes, Add to Album button 645, the buy/save/print sales interface 670, or some combination thereof.

(72) The Face Finder Tagged You section 610, the field at same time section 615, and the photo opportunities GUI 635 may each also include previous and next buttons, or timeline interfaces, or album interfaces, or carousel-style interfaces, or scrolling interfaces, or touch/swipe interfaces, each of which can be used to cycle from one image/video to the next. In situations where videos are presented, video controls, such as pause, play, fast-forward, rewind, skip, and volume may also be presented as part of these interfaces.

(73) FIG. 7 is a flow diagram illustrating exemplary operations of a photo trigger software.

(74) At step 705, a first camera is selected of the eventgoer cameras 120. At step 710, camera data is retrieved for the first camera, the camera data including for example, a location of the first camera, a camera viewing area of the camera, a direction or heading or angle that the camera is facing, an alphanumeric identifier of the camera, history data regarding previous photos and/or videos taken by the camera (e.g., optionally along with when the photos/videos were taken, what triggered the capture of the photos/videos, and an identification of any faces found in the photos/videos by the eventgoer face finder software 172).

(75) At step 715, a most recent photo opportunity time (identified as T.sub.1) of the first camera may be determined. At step 720, a frequency (identified as F) is determined based on historical use, desired number of photos, or some combination thereof. At step 725, a next photo opportunity time (identified as T.sub.2) may be calculated and/or scheduled for the first camera based on the sum of the most recent photo opportunity time (identified as T.sub.1) with the frequency (identified as F). At step 730, other nearby photo opportunities using the first camera (e.g., after moving or refocusing it) or using different cameras of the eventgoer cameras 120 may be determined.

(76) Any of steps 705, 710, 720, 725, or 730 may lead to step 735.

(77) At step 735, an exemplary first camera is identified along with some identifier data (e.g., Camera #2), camera location data (e.g., Section 5), photography location data (e.g., nearby photo opportunities: balcony), last photo opportunity time T.sub.1 (e.g., 5:05 P.M.), a photo frequency F (e.g., every 30 minutes), and the calculated next photo opportunity time T.sub.2 (e.g., 5:35 P.M.).

(78) At step 740, the camera feed data from the first camera may be converted into a format that may be transmitted by a transmitter N 750, which may be one of a set of one or more transmitters 122. The camera feed data may include photos, videos, video frames, as well as camera data as described in step 710 through step 730 (e.g., which may be marked up in the photos/videos, stored as metadata, or some combination thereof). In some cases, no conversion is needed, as the camera feed data may already be in a format that may be transmitted by the transmitter N 750, in which case step 745 may follow from step 735. At step 745, the camera feed data converted in step 740 may be sent to transmitter N 750, where it is then transmitted. One or more user devices 140 may thereafter receive the transmitted camera feed data.

(79) At step 755, which may follow after transmission of the camera feed data of the first camera via the transmitter N 750 in step 745, a next camera is selected from the set of eventgoer cameras 120 (or, in some cases, performance cameras 118). The steps between 705 and 755 may then be repeated over the entire set of eventgoer cameras 120 and/or performance cameras 118.

(80) FIG. 8 illustrates an exemplary overall method of the present invention as described herein.

(81) At step 810, the method includes providing an eventgoer photo network 162 containing a post-event portal 166, an eventgoer face finder software 172, a photo trigger software 174, a user database 180, a photo database 178; and a ticketing service 130, an event venue 100 containing eventgoer cameras 1-N 120 corresponding with seating sections 1-N (e.g., sections 104-114), performance cameras 1-N 118 and an emergency beacon (e.g., a fire alarm or police signal or paramedic signal), stadium sensors 102, and a user device(s) 140 each containing a eventgoer photo app 144.

(82) At step 820, the method includes allowing a user to purchase event venue tickets via ticketing service 130.

(83) At step 830, the method includes allowing a user to complete a profile using eventgoer photo software application 144, including a reference photo of user's face (e.g., see facial recognition reference photo 230) and store data in user database 180.

(84) At step 840, the method includes sensing event venue events using event venue sensors 102 and/or performance cameras 118.

(85) At step 850, the method includes photographing users in sections 1-N via eventgoer cameras 1-N 120, and simultaneously photographing game play via performance cameras 1-N 118.

(86) At step 860, the method includes storing photographs in photo database 178 including metadata of camera, time stamp, and event data.

(87) At step 870, the method includes matching photographed faces with reference photos uploaded by user, and based on location of a user's seat and a location of the eventgoer camera(s) 120.

(88) At step 880, the method includes pairing user photographed faces with game play photos with substantially the same or similar time stamp.

(89) At step 890, the method includes allowing user to accept or reject match, allowing user to choose amongst paired gameplay photos, allowing user to print, save, or purchase prints of matched and paired photos.

(90) FIG. 9 illustrates an exemplary overall method of the present invention as described herein.

(91) At step 910, the method includes providing wireless software 170 in eventgoer photo network, wireless decoder 146 in eventgoer photo app on user device, and wireless transmitters 122 for each eventgoer camera of the eventgoer cameras 120 and/or for each performance camera of the performance cameras 118 (optionally one or more transmitters 122 may be associated with more than one camera).

(92) At step 920, the method includes allowing user to retrieving wireless data from a crown camera N of the eventgoer cameras 120 or a performance camera N of the performance cameras 118.

(93) At step 930, the method includes decoding wireless camera feed data with wireless decoder 146 of the eventgoer photo app 144 on user device 140.

(94) At step 940, the method includes displaying wireless camera feed data (e.g., including section, next photo op, nearby cameras) on user device 140.

(95) At step 950, the method includes photographing a user based upon photo opportunities scheduled by the wireless software 170.

(96) At step 960, the method includes allowing a user to accept or reject face matches, allowing user to choose amongst paired gameplay photos, allowing user to print, save, or purchase prints of matched and paired photos (e.g., see interfaces of FIG. 6).

(97) FIG. 10 illustrates an exemplary computing system 1000 that may be used to implement an embodiment of the present invention. The computing system 1000 of FIG. 10 includes one or more processors 1010 and memory 1010. Main memory 1010 stores, in part, instructions and data for execution by processor 1010. Main memory 1010 can store the executable code when in operation. The system 1000 of FIG. 10 further includes a mass storage device 1030, portable storage medium drive(s) 1040, output devices 1050, user input devices 1060, a graphics display 1070, and peripheral devices 1080.

(98) The components shown in FIG. 10 are depicted as being connected via a single bus 1090. However, the components may be connected through one or more data transport means. For example, processor unit 1010 and main memory 1010 may be connected via a local microprocessor bus, and the mass storage device 1030, peripheral device(s) 1080, portable storage device 1040, and display system 1070 may be connected via one or more input/output (I/O) buses.

(99) Mass storage device 1030, which may be implemented with a magnetic disk drive or an optical disk drive, is a non-volatile storage device for storing data and instructions for use by processor unit 1010. Mass storage device 1030 can store the system software for implementing embodiments of the present invention for purposes of loading that software into main memory 1010.

(100) Portable storage device 1040 operates in conjunction with a portable non-volatile storage medium, such as a floppy disk, compact disk or Digital video disc, to input and output data and code to and from the computer system 1000 of FIG. 10. The system software for implementing embodiments of the present invention may be stored on such a portable medium and input to the computer system 1000 via the portable storage device 1040.

(101) Input devices 1060 provide a portion of a user interface. Input devices 1060 may include an alpha-numeric keypad, such as a keyboard, for inputting alpha-numeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys. Additionally, the system 1000 as shown in FIG. 10 includes output devices 1050. Examples of suitable output devices include speakers, printers, network interfaces, and monitors.

(102) Display system 1070 may include a liquid crystal display (LCD), a plasma display, an organic light-emitting diode (OLED) display, an electronic ink display, or another suitable display device. Display system 1070 receives textual and graphical information, and processes the information for output to the display device. The display system 1070 may include touchscreen input capabilities, such as capacitive touch detection.

(103) Peripherals 1080 may include any type of computer support device to add additional functionality to the computer system. For example, peripheral device(s) 1080 may include a modem or a router.

(104) The components contained in the computer system 1000 of FIG. 10 are those typically found in computer systems that may be suitable for use with embodiments of the present invention and are intended to represent a broad category of such computer components that are well known in the art. Thus, the computer system 1000 of FIG. 10 can be a personal computer, hand held computing device, telephone, mobile computing device, workstation, server, minicomputer, mainframe computer, or any other computing device. The computer can also include different bus configurations, networked platforms, multi-processor platforms, etc. Various operating systems can be used including Unix, Linux, Windows, Macintosh OS, Palm OS, Android, iOS, and other suitable operating systems.

(105) While various flow diagrams provided and described above may show a particular order of operations performed by certain embodiments of the invention, it should be understood that such order is exemplary (e.g., alternative embodiments can perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

(106) The foregoing detailed description of the technology has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology, its practical application, and to enable others skilled in the art to utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claim.