WO2018093361A1

WO2018093361A1 - Automated commemorative capture of a display/broadcast at an event

Info

Publication number: WO2018093361A1
Application number: PCT/US2016/062226
Authority: WO
Inventors: Bradley C. Geer
Original assignee: BLEACHR LLC
Current assignee: BLEACHR LLC
Priority date: 2016-11-16
Filing date: 2016-11-16
Publication date: 2018-05-24
Anticipated expiration: 2019-05-16

Abstract

The present invention is a method and a system for automated commemorative capture and storage of a display or broadcast of a content item at an event in a forum. The display might be on a scoreboard, and the capture might be done by a camera. The display, capture, and storage are controlled by an event management facility (EMF). The content item might be transmitted by, and received from a portable smart device of a fan through the fan social network, or by an advertiser. The commemorative recording is evidence that the display actually occurred in compliance with expectations.

Description

Automated Commemorative Capture of a

Display/Broadcast at an Event

Field of the Invention

[0001] The present invention relates to requested automated capture of displays or broadcasts at a forum event.

Summary of the Invention

[0002] For various reasons, display at an event of particular content upon an electronic scoreboard, sound system, or other display device in the forum where the event is being held, might be requested. The content might originate, for example, from an individual attendee, a fan social network, an advertiser, event management, a performer, or a performer organization. Event management might be obligated to display the content, for example, by contract. A fan might want a copy of the recording to commemorate the event— for example, a "Happy Birthday" message to a child, displayed during a sporting event. A display might be paid for by an advertiser or a fan, or might be awarded to a fan for winning some competition. In any case, event management might want to capture the scoreboard broadcast, maybe to fulfill a request, or for proof that the broadcast occurred according to expectations (e.g., timing, content). Given appropriate specified parameters, the display event can be performed and recorded; the content and the commemorative recording can be stored in a commemorative database; and the recording can be transmitted to an intended recipient— all automatically.

Brief Description of the Drawings

[0003] Figure 1 is a schematic diagram of an exemplary system for automated commemorative scoreboard capture.

[0004] Figure 2 is a flowchart for an exemplary system for automated commemorative scoreboard capture.

[0005] Figure 3 is a schematic diagram of an exemplary event management facility for a system for automated commemorative scoreboard capture.

[0006] Figure 4 is a schematic diagram of an exemplary fan networking system.

[0007] Figure 5 is a schematic diagram of an exemplary scoreboard commemorative database maintained in storage by an event management facility.

[0008] Figure 6 is a block diagram illustrating exemplary source devices for content of a display /broadcast using a scoreboard or other device.

[0009] Figure 7 is a block diagram illustrating exemplary requestors for display of content on a scoreboard, in an exemplary system for automated capture of event displays or broadcasts.

[0010] Figure 8 is a block diagram illustrating exemplary types of content to be displayed/broadcast on a scoreboard or other device, for commemorative automated capture. [0011] Figure 9 is a block diagram illustrating exemplary types of consideration to event management, for display of content on a scoreboard or other display /broadcast device.

[0012] Figure 10 is a block diagram illustrating possible types of triggers that might start or stop display and/or capture of content presented on a scoreboard or other device.

[0013] Figure 11 is a block diagram illustrating some scoreboard system components in an exemplary system for automated capture of event displays or broadcasts.

[0014] Figure 12 is a block diagram illustrating possible capture parameters that might specify particular capture devices and specify their settings.

[0015] Figure 13 is a block diagram illustrating parameters that might be used, alone or in combination, to determine whether a person is treated by the FNS and EMF as a qualified "fan" for purposes of an automated system for capture of event displays or broadcasts.

[0016] Figure 14 is a block diagram illustrating exemplary components of a portable smart device that includes a software application which supports geofencing and a fan networking system.

Detailed Description of Exemplary Embodiments

[0017] This description provides embodiments of the invention intended as exemplary applications. The reader of ordinary skill in the art will realize that the invention has broader scope than the particular examples described here. It should be noted from the outset that drawings, and elements depicted by the drawings, may not be to scale. Generally, reference numbers are keyed to the drawing of first appearance. For example, reference number 220 would appear first in Fig. 2; and 460, in Fig. 4. Each such reference will be described at least once, ordinarily in connection with the figure of first appearance. For clarity of the drawings, a given reference number that appears in a second figure will not necessarily be described a second time. By some step in a process being done "automatically" we mean that that particular step is executed under control of a processing system, without human intervention.

[0018] For various reasons, some person or entity (i.e., a requestor 700) might desire or request event management to record a public display at an event. Fig. 1 is schematic diagram of an exemplary system for automated capture of event displays/broadcasts. The forum that hosts a performance may have various display /broadcast devices 100, such as electronic scoreboards 101 and other electronic signage, sound systems 103, and pyrotechnics devices. The display /broadcast content 110 might include, for example, a still image, a video clip, an audio clip, text, fireworks, smoke, lighting effects, or any plurality or combination thereof. Note that throughout this document, we may sometimes use the word "scoreboard", such as in "scoreboard commemorative database". That word should be construed broadly to include other types of devices for display or broadcast at events.

[0019] Content 110 might be provided by one or more source devices 120, and might be provided for display /broadcast in digital or analog form. Exemplary source devices 120 include a portable smart device (PSD) 122 of a fan 160 or other attendee, some recording system within the forum 126 itself, such as a drone 124 (i.e., an unmanned aerial vehicle) filming some aspect of the event, or a still or video camera 131, or an EMF 140. A source device 120 might be a content recording device, such as a camera or microphone, or it might be some storage device where content 110 was previously saved. Content 110 items might be combined in any way for broadcast/display.

[0020] Automated capture of scoreboard display events is ultimately under control of an event management facility (EMF) 140. The EMF 140 may have a server 142 to execute logic (i.e., software and hardware, in some combination) to facilitate that controlling role. The EMF 140 may have storage 144 that saves information about, for example: the event, the capture devices, the qualified fans, the broadcasting devices, the broadcast content, the commemorative recording, workflow and parameters related to display or capture, rules for qualification to display or capture, and any other information to automated content broadcasting and capture.

[0021] Communication among various components in Fig. 1 might utilize one or more communication system 150, of any type and any implementing hardware or software. We will regard a combination of communication systems 150 as a communication system 150. In Fig. 1, lines typified by line 151 indicate communication among systems or devices.

[0022] Fig. 2 is an exemplary flowchart for an exemplary system for automated capture of scoreboard broadcast events. After the start 200, the system receives 210 information about the requestor 700 that is requesting the broadcast and capture; receives 220 the content 110 for the broadcast; and receives 225 any recording parameters or workflow 504 for controlling the display and/or capture. A trigger 1000 is received 230 that causes the scoreboard system 102 to broadcast the content 110. Another trigger 1000 is received that causes EMF 140 to initiate 250 capture of the broadcast. Triggers 1000 are received that cause 240 the system to stop capturing the broadcast and to stop broadcasting the content 110. The commemorative recording 503 of the content 110 as broadcast is stored in a database 300. Transmittal of the

commemorative recording 503 to the requestor is initiated 260, and the process ends 299. Note that Fig. 2 describes steps in an exemplary embodiment of the invention. In other embodiments, steps might be ordered differently, some steps might be omitted, or other steps might be added.

[0023] Fig. 3 is a schematic diagram of some relevant components of an exemplary EMF 140. The hardware and software components might be colocated, or they might be distributed. A given functionality might be implemented in a single device, or some collection of devices, possibly at multiple locations.

[0024] The EMF 140 may have various control systems. The control systems are executed by a processing system 310. The processing system 310 may include one or more of the following: a hardware processor, a server 142, user interface devices such as a monitor 146 and keyboard 148, and storage 144. Each control system may have access to one or more communication systems 150 through a respective interface, which includes a hardware interface. Each control system has logic, implemented in some combination specific to its task of hardware and software. The logic may in part by executed by the processing system 310. [0025] In particular, an EMF 140 may have a source device control system 320 that causes one or more source devices 120 to generate or otherwise provide content. For example, the source device control system 320 might cause a drone 124 to fly over the forum and capture something interesting about the performance or some fans. The source device control system 320 may also receive content 110, processing parameters, and workflow from source devices 120. The source device control system 320 interacts (i.e., sends and receives commands, data, and/or content 110) with the source device 120 through a source device interface 121.

[0026] An EMF 140 may also provide and/or manage a fan

networking system (FNS) 400, using a FNS control system 330.

Qualification as a fan 160 attending an event is described in connection with Fig. 13. An FNS might do some or all of the following: (1) provide a software FNS app 1310 that can execute on a PSD 122 and that, in conjunction with the EMF 140, provides services to fans attending the event, which relate to the event, to event performers, or to event management; (2) determines or approximates the geolocation of a PSD 122 of a fan, possibly using the executing software application in conjunction with GPS or other geolocation hardware and logic;

(3) determines whether the fan is "qualified" as attending an event, possibly using the geolocation of their PSD 122 relative to boundaries of the forum in which the event is being held, and using event timing status (e.g., the event is about to start, the event is ongoing, or the event has recently ended); and (4) provides access to a fan social network, executed over a FNS 400, whereby the fan can send or receive data (e.g., text, photos, videos) in communication with other fans and with the EMF 140. The FNS control system 330 interacts through a FNS interface 331 with a fan 160 through the software application executing on their PSD 122.

[0027] Unless otherwise clear from the context, henceforth in this document we will use the word "fan" as a synonym for a "qualified" fan— someone who is running the specific FNS app 1310 on their PSD 122, and satisfies other requirements for qualification, as specified and enforced by the EMF 140. As illustrated by Fig. 4, FNS 400 allows fans 160 to communicate (arrows 420) with the EMF 140. The FNS 400 may also allow fans 160 to communicate with each other (dashed arrow 420), through the EMF 140, or directly in some embodiments under specified circumstances.

[0028] The PSD 122 may serve as a source device 120 that provides content 110 for display /broadcast. For example, a fan 160 might enter a photograph captured by the PSD 122 at the event into a contest managed by the EMF 140. The fans 160 interacting through the FNS 400 might vote, ultimately selecting a winning photograph. That

photograph might then be displayed on the scoreboard 101, possibly with the name or an image of the winning fan 160. The fan 160 might then receive, from the EMF 140 through the FNS 400, a photograph of the scoreboard 101, taken by the automated system, to commemorate the event. That commemorative photo itself might be sent back to the fan 160 through the FNS 400. Alternatively, a fan 160 to pay for some text message (e.g., "Laura, will you marry me? Bob") to be displayed on the scoreboard 101). That message could be entered into the PSD 122 application, and transmitted through the FNS 400 to the EMF 140, along with some form of electronic payment. Again, a photograph of the scoreboard 101 display is made, and returned via the FNS 400 to the fan 160. Note that displayed and captured content 110 might include information identifying a particular fan 160 or a requestor 700.

[0029] An EMF 140 may include a scoreboard control system 340, which through a scoreboard communication interface 341, causes content 110 to be displayed on the scoreboard 101 through a scoreboard system 102. The EMF 140 may include a broadcast/display control system 350, which through a broadcast/display communication interface 350, causes content 110 to be displayed/broadcast on other types of display /broadcast devices 100. In any case, the EMF 140 may transmit triggers 1000 to the display /broadcast device 100 to start or end display /broadcast.

[0030] An EMF 140 may include a capture device control system 360, which through a capture device communication interface 361,

automatically causes the capture, by photograph, video, audio capture, or other record, of content 110 displayed/broadcast, on behalf of a requestor 700, on a scoreboard 101 or other display /broadcast device 100. The EMF 140 may send triggers to start/end capture by the capture device 130.

[0031] An EMF 140 may include a commemorative record

transmission control system 370, which through a commemorative record transmission interface 371, automatically transmits a

commemorative recording 503 made by the capture device control system 360 to a requestor 700 or attendee at an event.

[0032] The EMF 140 may have tangible electronic storage 144 that includes software processing logic 301, such as instructions to be executed by a processing system 310, and any data read, written, or otherwise required by the control systems to carry out their desired functionality. In particular, the EMF 140 maintains a scoreboard commemorative database 300, which contains any data pertinent to display /broadcast using scoreboard 101 or other display /broadcast device 100 broadcasts, and automated capture or other form of capture thereof.

[0033] The EMF 140 may include workflow and parameters for formatting digital images and videos for various aspects of its functions. Such formatting might include: formatting of source content for display /broadcast; formatting of captured data for commemorative recording; and formatting of commemorative recording for

transmission.

[0034] Fig. 5 is a schematic diagram of an exemplary scoreboard commemorative database 300 maintained in storage 144 by an EMF 140. The database 300 would typically be stored by one or more servers 142. For any system request for display and capture, such data might include, for example: requestor information 501 including, for example, requestor 700 identity and contact information; the content 110 to display or broadcast; software for processing automated system requests in general (e.g., by type of display, by type of capture device), and workflow 504 documenting how to process this request in particular (e.g., a particular type of camera or location in the forum from which a photograph of the scoreboard 101 should be taken; or processing for the various possible avenues of distribution of a commemorative recording 503, such as email, text, distribution through a FNS 400, or conventional mail or carrier); the commemorative recording 503 or other commemorative capture of the displa /broadcast; timing information 505 about when the content should be displayed, for how long, and which triggers will cause broadcast/capture to start/stop. The database 300 may also contain information regarding consideration 506 or compensation, which will be described further in connection with Fig. 9, as well as any relevant contractual information. In general, the database 300 might include any information relating to any of the figures herein.

[0035] Fig. 6 is a block diagram illustrating exemplary source devices 120 for content 110 of a display /broadcast using a scoreboard 101 or other display /broadcast device 100. The display /broadcast devices 100 include, for example, a PSD 122, a still camera 630, a video camera 620, or a drone-mounted camera 640. A source device 120 might also be, for example, a keyboard, a touchscreen, or a sound recording device or information previously saved in storage. The provider of such content 110 might be a fan 160, an advertiser 740, event management, a performer, or performer/team management. In general, the

person/entity generating the content 110, the person/entity requesting the display /broadcast, and the person/entity requesting

commemorative capture of the display/broadcast, might be the same or different. Fig. 7 illustrates some possible requestors 700 of automated commemorative capture. These include a fan 160; team management 720; event management 730; or an advertiser 740. In some

embodiments, the commemorative capture may be automatically transmitted to the requestor 700— for example, a commemorative video, which captures a scoreboard 101 public broadcast of a fan 160 video, and which is transmitted electronically by the EMF 140 through the FNS 400 to the PSD 122 of the fan 160. [0036] Fig. 8 is a block diagram illustrating exemplary types of content 110 to be displayed/broadcast on a scoreboard 101 or other display /broadcast device 100, for automated commemorative capture. The content 110 item might be fan content 810, such as text, a photo, or a video. The content 110 might be an advertisement 830, an event management or team management video 820, or some audio 840 recording. The fan 160 might display the video on a monitor 1440 of a PSD 122, or store the video in storage 1470.

[0037] Fig. 9 is a block diagram illustrating exemplary types of consideration to event management, for display of content on a scoreboard or other display /broadcast device. Management might receive some form of payment 910 from a requestor 700. If the requestor 700 is a fan 160, the payment 910 may be transmitted through the PSD 122, via FNS 400, and received by the EMF 140. The payment 910 might be monetary, or it could be some form of fan 160 "points" or other credit. Fan points might be earned by event attendance, purchases, and/or winning games or contests. A fan 160 might win the right to a commemorative capture as an award 930 for winning such a game or contest. A display /broadcast might simply be done by event/team management for general interest, but recorded to commemorate that something significant happened (e.g., "Cubs Win the World Series!"). Government or a league organization might require certain displays to be made during an event for legal reasons, or for public safety.

[0038] As shown in Fig. 2, triggers 1000 may start a

display /broadcast, stop a display /broadcast, start commemorative capture, and/or stop commemorative capture. Fig. 10 illustrates some exemplary types of triggers 1000 that might be used for any or all of these tasks. The triggers 1000 may be utilized in workflow 504, timing information 505, and processing logic 301. A trigger 1000 may be sent to a display /broadcast device 100 or a capture device 130. A timer 1010 waits for a specific interval of time— for example, an elapsed interval after display starts to begin capture; an elapsed interval after the start of an event to begin display; an elapsed interval after display starts to end display; or an elapsed interval after capture starts to end capture. A clock 1020 can specify a particular time (which possibly includes a date) to trigger a display or capture event. Manual triggers are also possible, such as notice 1030 from event management; notice 1040 from the scoreboard control system 340; or notice 1050 through the FNS 400 from a fan 160 or group of fans 160.

[0039] Fig. 11 is a block diagram illustrating is a block diagram illustrating some scoreboard system 102 components in an exemplary system for automated capture of event displays or broadcasts. The scoreboard system 102 may include a scoreboard 101 and a sound system 103, under control of a source device control system 320 that communicates with the scoreboard system 102 through a scoreboard communication interface 341. The scoreboard system 102 may include a communication interface 1140, whereby the scoreboard system 102 communicates with the EMF 140. Note that the configuration of the scoreboard 101 shown in Fig. 11 applies analogously to other types of display /broadcast device 100, such as a video board, a video wall, a speaker, or a monitor.

[0040] Fig. 12 is a block diagram illustrating possible capture parameters 1200 that might specify particular capture devices and specify their settings for capturing display /broadcast of content 110. There might be several devices available that could capture a particular scoreboard 101 or other display commemoratively. For example, there might be several cameras throughout a sports venue, and each camera might have multiple settings to control the capture appearance.

Exemplary capture parameters 1200 include capture device type 1210, device location 1220, pan-tilt-zoom settings 1230 (for a camera), and timing settings 1240. The capture parameters 1200 may be stored in database 300, and used by the processing system 310 in the capture.

[0041] Fig. 13 is a block diagram illustrating parameters, alone or in any combination, that might be used by the FNS 400 in collaboration with the EMF 140, to determine whether a person is treated as a qualified fan 160 for purposes of an automated system for capture of event displays or broadcasts. For example, does the person have the FNS app 1310 installed and running on their smart device? Is their PSD location 1320 determined automatically by the EMF 140 to be within boundaries previously specified by the EMF 140, as sensed by, for example, a GPS system? Is event timing 1330 appropriate? For example, is the fan 160 within the forum while the event is actually underway there, or during an interval chosen by event management (and enforced by the EMF 140) before or after the event? Is the fan 160 actually participating 1340 in the FNS 400 at the moment?

[0042] Fig. 14 is a block diagram illustrating exemplary components of a PSD 122 that includes a software application that supports geofencing and a fan networking system. The PSD 122 is a portable electronic device (e.g., a smart phone, a tablet computer, a camera, or a small portable computer) that includes a processing system 1460 having a hardware processor. The PSD 122 includes a user interface 1400 that may utilize various hardware controls, such as a touchscreen monitor 1440. In addition to user interaction, the monitor 1440 may also be used for display of digital images, which may be transferred to or from the PSD 122 using a network interface 1430, or captured by the PSD 122 with a hardware camera 1420. The processing system 1460 executes a FNS software app 1471, stored in tangible hardware storage 1470, that communicates via the network interface 1430 with the EMF 140 and/or with other fans 160 who are participating in the FNS 400. The network interface 1430 may be any kind of wired and/or wireless

communication system (which itself may be a combination of any kinds of communication systems). Such communications might include transfers in either direction of content 110 (e.g., photos, videos, text, audio tracks— whether real time or not); geolocation information;

information related to contests or games; currency or virtual currency, such as fan "points"; social networking data; advertising; event information; or team information. The storage 144 may include any data or all data appropriate to the FNS 400, as well as to the FNS software app 1471, the EMF 140 and functionality of the PSD 122 itself.

[0043] Of course, many variations of the above method are possible within the scope of the invention. The present invention is, therefore, not limited to all the above details, as modifications and variations may be made without departing from the intent or scope of the invention. Consequently, the invention should be limited only by the following claims and equivalent constructions.

Claims

What Is Claimed Is: A method, comprising:

a) receiving through an electronic communication system

(i) a request to display or broadcast content at an

event in a forum, and

(ii) timing information that constrains timing of the display or broadcast, or the timing of recording of the display or broadcast;

b) receiving electronically a first trigger to start displaying or broadcasting the content;

c) displaying or broadcasting the content to attendees of the event using a hardware device in the forum;

d) receiving electronically a second trigger, not necessarily distinct from the first trigger, to start recording the display or broadcast for a commemorative record of the display or broadcast; and

e) automatically recording the display or broadcast and

storing the commemorative record in tangible electronic storage.

The method of claim 1, further comprising:

f ) under control of an event management system,

automatically transmitting the commemorative record electronically, directed to an attendee of the event.

3. The method of claim 2, wherein the attendee has qualified as a fan attending the event, with a fan networking system managed by an event management facility.

4. The method of claim 1, wherein the commemorative record is a photograph or a video recording of a scoreboard or other electronic display of the forum.

5. The method of claim 1, wherein a third trigger, to stop recording, is transmitted, based upon a hardware clock or timer, at a time determined by an interval relative to the start of displaying or broadcasting the content.

6. The method of claim 1, wherein

(i) the hardware device is an electronic scoreboard or monitor; and

(ii) the recording step uses a camera.

7. The method of claim 6, wherein the display or broadcast

includes information identifying a particular attendee at the event.

8. The method of claim 1, wherein the second trigger is generated automatically by a processing system of an event management facility.

9. The method of claim 8, wherein the request is received by an event management facility, which includes a hardware processor, and which manages a fan networking system.

10. The method of claim 9, wherein the request is received from a portable smart device through the fan networking system.

11. The method of claim 9, wherein the content is received from an advertiser.

12. The method of claim 9, wherein the content is received from a fan that has qualified by the event management system as attending the event, and wherein qualification as a fan requires that

a) a portable smart device (PSD) of the fan is running an application that facilitates connection to a fan networking system, managed by an event management facility and associated with the event,

b) the PSD is determined by an automated geolocation

system to be located within specified boundaries related to the forum, and

c) the time of qualification is within an interval, associated with the event, specified for receipt of such content.

13. The method of claim 12, wherein the display or broadcast

includes identification of the fan.

14. The method of claim 12, wherein the display or broadcast is awarded to the fan because the fan has won a contest or game conducted through the fan networking system by the event management system. The method of claim 9, further comprising:

f ) receiving, through the electronic communication system, compensation from a requestor for the display or broadcast.

The method of claim 9, wherein the compensation is based upon points or other credit earned by an attendee of the event from the event management facility by activities of the fan associated with one or more events.

The method of claim 1, further comprising:

f ) transmitting the content by a portable smart device

through a fan networking system.

The method of claim 1, further comprising:

f ) capturing the content by an unmanned aerial vehicle

during the event for the display or broadcast.

A system, comprising:

a) an event management facility, including:

(i) a processing system, which includes a hardware processor;

(ii) tangible electronic storage, which includes a

scoreboard commemorative database;

(iii) a fan networking control system, whereby fan

portable smart devices can transfer electronic content with each other and with the event management facility over a communication network;

(iv) a display-broadcast control system, that controls display of content using a hardware display or broadcast device to attendees of an event in a forum;

(v) a capture device control system, that upon

electronic request automatically captures into the database a commemorative recording of some content displayed or broadcast at the event, and;

(vi) a respective communication system interface for each control system, not necessarily pairwise distinct;

wherein each control system is implemented in logic that includes software and tangible hardware.

20. The system of claim 19, wherein the display or broadcast device is an electronic scoreboard, and the capture device is a camera.

21. The system of claim 19, wherein the storage commemorative database includes, for each of a plurality of content items:

(A) the content item,

(B) identifying information of a requestor that requested display or broadcast of the content,

(C) timing information, which governs when content display or broadcast will start, how long the display or broadcast will last, when the recording will start, and how long the recording will last, and

(D) workflow information, which specifies a device that will display or broadcast the content, and a device that will capture and record the content.

22. The system of claim 21, wherein the workflow information

includes parameters governing automatically electronic transmission of the commemorative record to the requestor.

23. The system of claim 22, wherein the wherein the event

management system transmits the commemorative record to the requestor as required by the parameters.

24. The system of claim 21, wherein the storage commemorative database further includes, for each of a plurality of content items:

(E) information regarding consideration to the event management facility for display or broadcast of the content.

25. The system of claim 24, wherein the storage commemorative database further includes, for each of a plurality of content items:

(F) information regarding consideration to the event management facility for recording a commemorative recording of the display or broadcast. The system of claim 21, wherein the content item includes a digital photograph or image.

The system of claim 21, wherein the content item includes a video recording.

The system of claim 19, further comprising:

b) a plurality of portable smart devices (PSD) that are

connected to a fan networking system (FNS), which is under control of the fan networking control system; and c) a first PSD in the plurality, such that the FNS

(i) determines that the PSD satisfies a plurality of rules defined in the EMF for display or broadcasting at an event in a forum, and for capture in a commemorative recording in the database,

(ii) displays or broadcasts an item of content received from the PSD during the event, and

(iii) automatically captures the display or broadcast in commemorative recording, and stores the commemorative recording in the database.

The system of claim 19, further comprising:

b) a display-broadcast device that, upon request from the display-broadcast control system, displays or broadcasts content item to attendees at an event in the forum; c) a capture device that, upon request from the capture device control system, automatically captures or records in a commemorative recording the display or broadcast of the content item and transmits the commemorative recording to the EMF, which stores the commemorative recording in the database.

30. The system of claim 29, further comprising:

d) a source device control system and a source device control system interface, that controls a source device that obtains content, during one of the events in the forum, for a display or broadcast using the display-broadcast control system that is captured using the capture device control system.

The system of claim 30, wherein the source device is an unmanned aerial vehicle.