Method for generating and providing lighting effects

Abstract

A user terminal that produces lighting effects for videos provided through a VOD service includes a communication unit for communicating with a server and a receiving device, a memory, and a processor electrically connected to the communication unit and the memory, and the processor is configured to acquire related information and playing time of the video, request and receive at least one piece of metadata from the server based on the related information, identify first metadata corresponding to the playing time from the at least one piece of metadata, generate a lighting control signal based on the first metadata, and transmit the lighting control signal to the receiving device.

Description

[Technical Field]

[0001] The present disclosure relates to a method for generating and providing lighting effects in conjunction with videos provided by a VOD service, and more particularly, to a method for using a receiving device and / or a user terminal to provide lighting effects for videos provided by a VOD service in a receiving device.

[0002] The present disclosure also relates to a method for generating and providing lighting effects in coordination with performance videos streamed in real time, and more particularly, to a method for using a receiving device and / or a user terminal to generate lighting effects for performance videos streamed in real time in a receiving device. [Background technology]

[0003] Generally, a light emitting device (or lighting device) can refer to a device that reflects, refracts, and transmits light from a light source to achieve the purpose of illumination. Light emitting devices can be classified into indirect light emitting devices, semi-indirect light emitting devices, general diffuse light emitting devices, semi-direct light emitting devices, and direct light emitting devices according to the light distribution.

[0004] With the advancement of technology, light emitting devices are being used in a variety of applications. For example, light emitting devices can be installed on the exterior walls of buildings to create a media facade that embodies media functions. For another example, light emitting devices can be used as portable cheering goods at performance venues, such as sporting events and concerts, where the illuminance level is below a certain level. Portable cheering goods can be used as a means for large numbers of spectators to cheer on a group at a performance venue, achieving excellent cheering effects. In addition, portable cheering goods can be controlled via a relay device installed at the performance venue to emit lighting in colors that correspond to various stage effects (e.g., lighting effects) of the performance, thereby enhancing immersion in the performance.

[0005] However, if viewers are watching real-time streaming videos (e.g., performance footage) from a remote location rather than at the venue, or if they are watching filmed videos or performance footage in a non-real-time manner, such as through a VOD service, it may be difficult to achieve such a cheering effect.

[0006] Therefore, in order to specifically solve the above problems, there is a need for a method to control portable cheering goods carried by viewers so that viewers in remote locations or viewers of VOD videos can experience the same lighting effects as in an actual concert hall. Summary of the Invention [Problem to be solved by the invention]

[0007] The problem to be solved by the present disclosure relates to a method for generating and providing a control signal for producing lighting effects in a receiving device in conjunction with a video provided by VOD.

[0008] The problem to be solved by the present disclosure also relates to a method for generating and providing a control signal for producing lighting effects in a receiving device in coordination with performance video streamed in real time.

[0009] The problems to be solved by the present disclosure are not limited to those described above, and other problems not mentioned will be clearly understood by those skilled in the art from the following description. [Means for solving the problem]

[0010] In order to solve the above-mentioned problems, a user terminal for producing lighting effects for videos provided through a VOD service according to the present disclosure includes a communication unit for communicating with a server and a receiving device, a memory, and a processor electrically connected to the communication unit and the memory, wherein the processor is configured to acquire content-related information and playing time of the video, request and receive at least one piece of metadata from the server based on the related information, identify first metadata corresponding to the playing time from the at least one piece of metadata, generate a lighting control signal based on the first metadata, and transmit the lighting control signal to the receiving device.

[0011] In addition, a method for creating lighting effects for videos provided through a VOD service according to the present disclosure may include the steps of: a user terminal acquiring content-related information and a playing time of the video; the user terminal requesting at least one piece of metadata from a server based on the related information; the user terminal receiving the at least one piece of metadata from the server; the user terminal identifying first metadata corresponding to the playing time from the at least one piece of metadata and generating a lighting control signal based on the first metadata; and the user terminal transmitting the lighting control signal to a receiving device.

[0012] According to an exemplary embodiment of the present disclosure, the above-described exemplary embodiment may be a computer program stored on a computer-readable recording medium to cause the computer to execute a lighting control method.

[0013] In addition, a user terminal that creates lighting effects for performance footage provided through live streaming according to the present disclosure may include a communication unit for communicating with a server and a receiving device, a memory, and a processor electrically connected to the communication unit and the memory.

[0014] The processor can acquire performance information and playing time of the performance video, request first metadata corresponding to a first stage from the server based on the performance information, download the first metadata from the server, check stage information being performed in real time during the performance, and in response to the first stage being performed during the performance, generate a light-emitting control signal based on the playing time and the first metadata, and transmit the light-emitting control signal to the receiving device.

[0015] The processor can receive URL information of the first metadata from the server for downloading the first metadata, and can request the server to download the first metadata based on the URL information of the first metadata.

[0016] The user terminal may further include a display, and the processor may be further configured to receive input of the playing time from a user via the display.

[0017] The processor can poll the server for live stage information at regular time intervals to check the stage information being performed in real time during the performance, and receive a response from the server.

[0018] The processor may be further configured to download second metadata corresponding to a second stage from the server while the first stage is being performed in the performance, and the second stage may be predetermined to be performed next in order after the first stage.

[0019] Furthermore, a method for producing lighting effects for performance videos provided through live streaming according to the present disclosure may include the steps of: a user terminal acquiring performance information and playing time of the performance video; the user terminal requesting first metadata corresponding to a first stage from a server based on the performance information; the user terminal downloading the first metadata from the server; the user terminal checking information on stages being performed in real time during the performance; the user terminal generating a lighting control signal based on the playing time and the first metadata in response to the first stage being performed during the performance; and the user terminal transmitting the lighting control signal to a receiving device.

[0020] The step of the user terminal downloading the first metadata from the server may include the steps of the user terminal receiving URL information of the first metadata from the server, and the user terminal requesting the server to download the first metadata based on the URL information of the first metadata.

[0021] The step of acquiring the playing time may include a step of the user terminal receiving an input of the playing time from a user via a display.

[0022] The step of the user terminal checking the stage information being performed in real time during the performance may include the step of the user terminal polling the server for live stage information at regular time intervals and receiving a response from the server.

[0023] The method may further include a step in which, while the first stage is being performed in the performance, the user terminal downloads second metadata corresponding to a second stage from the server, and the second stage may be predetermined to be performed next after the first stage.

[0024] The first metadata may include at least one of color information and a time code.

[0025] The performance information may include at least one of a performance ID, a performance name, a performance date and time, and at least one piece of stage information.

[0026] The step of the user terminal generating a light-emitting control signal may include the steps of: if the user terminal acquires a new playing time, requesting the server to download third metadata corresponding to the new playing time based on the newly acquired playing time; and generating the light-emitting control signal based on the newly acquired playing time and the third metadata.

[0027] The receiving device may include a processor, a memory, and a light emitting unit, and the processor may be configured to cause the light emitting unit to emit light of a hue according to the light emission control signal.

[0028] The receiving device is characterized in that it is a toy that includes at least one joint whose position is adjustable and a processor, and further includes at least one of a drive motor for driving the at least one joint, a light-emitting unit, or a speaker, and the processor may be configured to receive at least one of the light-emitting control signal, the operation control signal, or the sound control signal from the user terminal, and to, when receiving the light-emitting control signal, cause the light-emitting unit to emit light of a color corresponding to the light-emitting control signal, when receiving the operation control signal, drive the at least one joint to perform a specified operation, and when receiving the sound control signal, output sound corresponding to the sound control signal from the speaker.

[0029] Other specific details of the present disclosure are included in the detailed description and drawings. [Effects of the Invention]

[0030] The method of generating and providing lighting effects disclosed herein allows a user terminal to download metadata corresponding to a VOD video, and based on that, generates a control signal for producing lighting effects for the video using a receiving device, thereby increasing the immersiveness of viewing a performance.

[0031] In addition, the method of generating and providing lighting effects disclosed herein allows a user terminal to download metadata corresponding to video provided through live streaming, and based on that, generates a control signal for producing lighting effects for the performance video using a receiving device, thereby increasing the immersiveness of viewing the performance.

[0032] The effects of the present disclosure are not limited to the effects described above, and other effects not mentioned herein will be clearly understood by those skilled in the art from the following description. [Brief explanation of the drawings]

[0033] [Figure 1] FIG. 1 is a conceptual diagram illustrating a metadata generation system according to an embodiment of the present disclosure. [Figure 2] 1 is a conceptual diagram illustrating a lighting effect production system according to an embodiment of the present disclosure. [Figure 3] 1 illustrates a performance timeline according to an exemplary embodiment of the present disclosure. [Figure 4] 10 illustrates a performance information screen according to an exemplary embodiment of the present disclosure. [Figure 5] 10 illustrates a signal flow chart between a server, a user terminal, and a receiving device according to one embodiment of the present disclosure. [Figure 6] 10 illustrates a signal flow chart between a server, a user terminal, and a receiving device according to one embodiment of the present disclosure. [Figure 7] 10 illustrates a signal flow chart between a server, a user terminal, and a receiving device according to one embodiment of the present disclosure. [Figure 8] 1 illustrates an application screen according to an exemplary embodiment of the present disclosure. [Figure 9] FIG. 2 is a block diagram illustrating a user terminal according to an exemplary embodiment of the present disclosure. [Figure 10] FIG. 2 is a block diagram illustrating a receiving device according to an exemplary embodiment of the present disclosure. [Figure 11] 1 illustrates a toy-shaped receiving device according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0034] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the following detailed description of the embodiments in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, and may be embodied in various different forms. The embodiments are provided solely to ensure completeness of the disclosure and to fully teach the scope of the disclosure to those skilled in the art to which the disclosure pertains. The present disclosure is defined by the scope of the claims.

[0035] The terms used in this disclosure are for the purpose of describing the embodiments and are not intended to limit the disclosure. In this disclosure, the singular can also include the plural unless otherwise specified in the phrase. The terms "may comprise" and / or "comprising" used in the disclosure do not exclude the presence or addition of one or more other components in addition to the referenced components. The same reference numerals refer to the same components throughout the disclosure, and "and / or" can include each and every combination of one or more of the referenced components. Although terms such as "first," "second," etc. are used to describe various components, it should be understood that these components are not limited by these terms. These terms are used merely to distinguish one component from another. Therefore, it should be understood that a first component referred to below can also be a second component within the technical spirit of the present disclosure.

[0036] The word "exemplary" is used in this disclosure to mean "serving as an example or illustration." Any embodiment described in this disclosure as "exemplary" should not necessarily be construed as preferred or advantageous over other embodiments.

[0037] Embodiments of the present disclosure may be described in terms of functions or blocks that perform functions. Blocks in the present disclosure, which may be referred to as "modules" or "modules," may be physically embodied by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memories, passive electronic components, active electronic components, optical components, hardwired circuits, etc., and may optionally be driven by firmware and software. Furthermore, the term "module" as used in the present disclosure refers to software, hardware elements such as FPGAs, or ASICs, and may perform certain functions. However, the term "module" is not limited to software or hardware. A "module" may be configured to exist on an addressable storage medium or to execute one or more processors. Thus, by way of example, a "module" may include elements such as software elements, object-oriented software elements, class elements, and task elements, as well as processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided in the elements and "modules" may be combined into fewer elements and "modules" or further separated into additional elements and "modules."

[0038] Embodiments of the present disclosure may be implemented using at least one software program executing on at least one hardware device and capable of performing network management functions to control elements.

[0039] Spatially relative terms such as "below," "beneath," "lower," "above," and "upper" may be used to easily describe the relationship of one component to another, as shown in the drawings. Spatially relative terms should be understood to include different orientations of components in use or operation in addition to the orientation shown in the drawings. For example, if a component shown in the drawings is inverted, a component described as "below" or "beneath" another component may be positioned "above" the other component. Thus, the exemplary term "below" may include both an orientation of below and above. Components may be oriented in other directions, whereby the spatially relative terms may be interpreted accordingly.

[0040] Unless otherwise defined, all terms (including technical and scientific terms) used in this disclosure will be used in the sense that they are commonly understood by those of ordinary skill in the art to which this disclosure belongs. Furthermore, terms defined in commonly used dictionaries will not be interpreted ideally or excessively unless clearly and specifically defined.

[0041] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0042] Meanwhile, the video according to the present disclosure is a video of specific content, and the specific content refers to an event attended by a large audience, such as a performance, an event, or a lecture. In the following description, in order to more clearly and specifically explain the present disclosure, it is assumed that the content is a performance event. Of course, the content according to the present disclosure is not limited to performances, and may include any event attended by a large audience. Furthermore, the content-related information may be performance information, which will be described below.

[0043] FIG. 1 is a conceptual diagram illustrating a metadata generation system according to an embodiment of the present disclosure.

[0044] 1, a metadata generation system 10 according to an embodiment of the present disclosure may include a timecode generation device 100, a stage production device 110, a metadata generation device 120, and / or a server 130. In one embodiment, the stage production device 110 may include a simulator 115 for expressing, planning, and designing a scenario.

[0045] In one embodiment, the time code generating device 100 may include a laptop computer, a speaker, and / or a mixer. The time code generating device 100 may generate SMPTE time code for synchronizing stage effects. The time code generating device 100 of FIG. 1 is illustrative, and embodiments of the present disclosure are not limited thereto.

[0046] In one embodiment, the stage production device 110 may generate control signals for stage production in a performance venue. Stage equipment (e.g., sound equipment, lighting equipment) installed in the performance venue may provide various performance effects (e.g., sound effects, lighting effects) based on the control signals from the stage production device 110. For example, the stage production device 110 may be one of electronic devices and / or PC software such as MA Lighting grandMA2, grandMA3, ETC EOS, ETC ION, ETC GIO, Chroma Q Vista, High End HOG, High End Full boar, Avolites Sapphire, Avolites Tiger, Chamsys MagicQ, Obsidian control systems Onyx, Martin M6, Martin M1, Nicolaudie Sunlite, ESA, ESA2, Lumidesk, SunSuite, Arcolis, Daslight, LightRider, MADRIX, DJLIGHT STUDIO, DISCO-DESIGNER VJ STUDIO, Stagecraft, Lightkey, etc.

[0047] The stage production device 110 may include a simulator 115 for producing lighting effects. The simulator 115 may be an electronic device that performs a virtual simulation to produce lighting effects, software running on an electronic device, or a combined device that combines software and an electronic device. For example, a user may input electronic signals corresponding to a scene to be produced to the simulator 115, and the simulator 115 may convert the input electronic signals to conform to the protocol of the stage production device 110 so that the signals can be operated by the stage production device 110, and provide the converted signals to the stage production device 110.

[0048] In an exemplary embodiment, the stage production device 110 may include suitable software or computer programs that enable control of the stage equipment. For example, the stage production device 110 may include, as exemplary protocols for controlling the stage equipment, DMX512, RDM, Art-Net, sACN, ETC-Net2, Pathport, Shownet, or KiNET. The stage production device 110 may transmit data signals (e.g., lighting control signals) in a suitable format, such as DMX512, Art-Net, sACN, ETC-Net2, Pathport, Shownet, or KiNET.

[0049] In an exemplary embodiment, the stage production device 110 may include multiple input / output ports. The stage production device 110 may include input / output ports that correspond to or are associated with specific data signal formats or protocols. For example, the stage production device 110 may include a first port dedicated to the input / output of DMX512 and RDM data, and a second port dedicated to the input / output of Art-Net, sACN, ETC-Net2, Pathport, Shownet, and KiNET data. The DMX512, RDM, Art-Net, sACN, ETC-Net2, Pathport, Shownet, and KiNET protocols are well-known control protocols for stage lighting equipment. According to an exemplary embodiment, the stage production device 110 may provide more flexible control of the stage equipment using control protocols such as DMX512, RDM, Art-Net, sACN, ETC-Net2, Pathport, Shownet, and KiNET.

[0050] In one embodiment, a performance director can generate control data in advance for at least the lighting effects to be produced in the actual performance using the stage production device 110. If the performance consists of multiple stages, control data corresponding to each of the multiple stages can be generated. The control data can be understood as having been generated in advance for the lighting production of that stage in the actual performance venue.

[0051] In one embodiment, the metadata generating device 120 may include a laptop computer. The metadata generating device 120 may receive a time code from the time code generating device 100. The metadata generating device 120 may receive control data from the stage production device 110. The metadata generating device 120 may synchronize the time code and the control data to generate metadata for the stage. The metadata generating device 120 may transmit the generated metadata to the server 130.

[0052] In one embodiment, the metadata may include an identification number, a time code, and color information (e.g., RGBW data) of the lighting effect. The metadata structure is merely exemplary, and the embodiments of the present disclosure are not limited thereto. For example, the first identification number (e.g., #1) may indicate the first lighting effect (e.g., the first lighting effect) performed on the stage. Specifically, the first identification number may be mapped to the time codes indicating when the first lighting effect was performed and when it ended, as well as the color information of the first lighting effect. The identification number may be incremented by one each time a lighting effect is changed. Each identification number may be mapped to the time codes indicating when the corresponding lighting effect (e.g., the second lighting effect, the third lighting effect, etc.) was performed and when it ended, as well as the color information of the corresponding lighting effect.

[0053] In one embodiment, the metadata may be identified by time codes corresponding to the start and end of the scene. For example, the start of the metadata may be the time code when the lighting effect corresponding to the first identification number is played. For example, the end of the metadata may be the time code when the lighting effect corresponding to the last identification number is played.

[0054] In one embodiment, the server 130 can receive metadata from the metadata generating device 120 and store the received metadata in a database (DB). For example, the server 130 can provide performance data to the stage production device 110 via a wired network such as a coaxial cable or a wired LAN (Local Area Network) (e.g., Ethernet). For example, the server 130 can provide performance data to the stage production device 110 in the form of packets over a mobile communication network established using a standard mobile communication method. For example, the database (DB) stored in the server 130 can be physically transferred to the stage production device 110 using a storage medium such as a portable disk.

[0055] In one embodiment, if multiple scenes are produced in a single performance, multiple metadata corresponding to each scene may be generated. The multiple metadata (e.g., first metadata, second metadata, etc.) may be generated based on a continuous series of time codes or based on unique time codes.

[0056] In one embodiment, after a first performance ends, a second performance may continue. In this case, the first performance may correspond to first metadata, and the second performance may correspond to second metadata. For example, the end timecode of the first metadata may match the start timecode of the second metadata. As another example, after the performance corresponding to the first metadata ends, the start timecode of the second metadata may be a unique timecode that is unrelated to the end timecode of the first metadata. In the following, it is assumed that multiple metadata are generated based on a continuous series of timecodes.

[0057] FIG. 2 is a conceptual diagram illustrating a lighting effect production system according to an embodiment of the present disclosure.

[0058] Referring to FIG. 2, a lighting effect production system 20 according to an embodiment of the present disclosure may include a performance venue 200, a trigger device 210, a server 220, a user terminal 230, and / or a receiving device 240.

[0059] In one embodiment, a user can watch videos through the user terminal 230. For example, the videos can be performance videos at the performance venue 200, videos on a video sharing platform (for example, YouTube), etc. TM ) and media content (e.g., music videos, animations, dramas). In the following description, in order to more clearly and specifically explain the present disclosure, it is assumed that the video is a performance video. Naturally, the video according to the present disclosure is not limited to performance videos, and the related information of the video may be performance information as described below.

[0060] In one embodiment, lighting effects based on pre-generated control data can be produced in the performance hall 200. The director can transmit control signals based on the pre-generated control data to the stage equipment using the stage production equipment 110 installed in the performance hall 200. For example, the lighting equipment can provide lighting effects (e.g., light emission) based on the control signals.

[0061] In one embodiment, a performance timeline may be defined as a time period from the start to the end of an actual performance in the performance venue 200. At least one stage may be performed on the performance timeline, and a break may exist between at least one stage. For example, the break may be a time for a host to make an announcement or a time for preparation for the next performance.

[0062] In one embodiment, the trigger device 210 can trigger at least one piece of metadata on a performance timeline corresponding to a stage produced in the performance venue 200. The trigger device 210 can generate performance production information in which the at least one piece of metadata is synchronized with the performance timeline based on the time of the trigger.

[0063] Referring to Figure 3, a performance timeline 300 may indicate a time period during which at least one performance was performed at the performance venue 200. The performance timeline 300 may be expressed in the form of local standard time (e.g., KST) and / or UNIX time. According to the embodiment of Figure 3, it may be understood that four performances (e.g., a first performance, a second performance, a third performance, and a fourth performance) were performed at the performance venue 200. There may be break times between the first and second performances and between the third and fourth performances.

[0064] In one embodiment, the stages (e.g., first stage, second stage, third stage, fourth stage) to be performed in real time in the performance venue 200 may be predetermined. Thus, in the actual performance, the director can perform lighting effects according to the predetermined order of the stages. Control data for performing lighting effects for each stage may be based on the metadata generated in FIG. 1.

[0065] The trigger device 210 can trigger metadata corresponding to the time when each stage was performed in the performance timeline 300. For example, the first metadata can be triggered at the time when the first stage was performed (13:01:00:000). For example, the second metadata can be triggered at the time when the second stage was performed (13:09:01:000). For example, the third metadata can be triggered at the time when the third stage was performed (13:15:00:000). For example, the fourth metadata can be triggered at the time when the fourth stage was performed (13:24:05:000).

[0066] The trigger device 210 can generate performance production information 310 in which at least one piece of metadata is synchronized with the performance timeline based on the time of the trigger. In one embodiment, the at least one piece of metadata can have a predefined time code that is not related to the performance timeline 300.

[0067] In one embodiment, the trigger device 210 can map the time code of at least one piece of metadata to the performance timeline 300. For example, the trigger device 210 can map the time code of the second piece of metadata (00:05:01:000) to the performance time of the second stage (13:09:01:000) on the performance timeline 300.

[0068] 2, the trigger device 210 can transmit the generated performance production information to the server 220. The server 220 can store the received performance production information in a database as performance information together with various other information related to the performance (e.g., performance name, performance date and time, sponsor name). The description of the server 220 can be referenced in the description of the server 130 in FIG. 1, but the servers 220 and 130 may be separate servers located physically separated from each other.

[0069] Referring to FIG. 4, performance information stored in the server 220 can be provided as shown in screen 400 via an administrator interface.

[0070] Referring to screen 400, the performance production information may include various information related to the performance, such as a performance ID, a performance name, an English version of the performance name, a performance category, a performance location, a performance date and time, and stage information.

[0071] In screen 400, the performance category may indicate whether the performance is provided to users via real-time streaming or VOD service. In this disclosure, performance video may be understood as video provided via VOD service after the actual performance has ended. Also, in this disclosure, performance video may be understood as video of a performance that is performed live at a performance venue and provided to users in remote locations via streaming.

[0072] On the screen 400, the stage information may display detailed information about multiple stages performed in the performance. Each stage information may include information about the KST time and UNIX time when the stage performance started.

[0073] In one embodiment, the first stage 410, the second stage 412, and the third stage 414 may be considered to have started at 12:43:29, 12:43:34, and 12:43:43 local time (KST), respectively. The fourth stage 416 may be considered to have been scheduled for performance but not yet been performed. When the fourth stage 416 is performed, the trigger device 210 may transmit the start time of the performance to the server and update the screen 400.

[0074] 2, a user can view a performance video from the performance venue 200 through a VOD service or a live streaming service at a remote location. For example, a user can view a performance video from the performance venue 200 on a user terminal 230 or a separate electronic device (not shown) equipped with a display.

[0075] In one embodiment, a user can use the user terminal 230 and the receiving device 240 to experience the same cheering effect as in the concert hall while watching the performance video. The specific configurations of the user terminal 230 and the receiving device 240 will be described later.

[0076] In one embodiment, the user terminal 230 may be an electronic device such as, but not limited to, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a wearable device (e.g., a smart watch, smart glass, or a head mounted display (HMD)).

[0077] In one embodiment, the receiving device 240 may include a light-emitting element such as a liquid crystal display (LCD) or a light-emitting diode (LED), or may be connected to a light-emitting element. The receiving device 240 may be any electronic device capable of wireless communication, such as a small cheering prop carried by spectators at a performance venue such as a sports stadium or concert. For example, the receiving device 240 may be a mobile phone, a wireless receiving device, a lighting stick, a lighting bar, a lighting ball, a lighting panel, or a fixture with a wirelessly controllable light source attached. In the present disclosure, the receiving device 240 may also be referred to as a lighting device, a receiver, a controlled device, a slave, or a slave lighting device. The receiving device 240 may also include a wearable device that can be attached to and / or worn on a part of the body, such as the wrist or chest.

[0078] In one embodiment, the user terminal 230 may receive at least one piece of metadata for creating lighting effects from the server 220. In one embodiment, the at least one piece of metadata may be received in a JSON (Java Script Object Notation) format. In another embodiment, the at least one piece of metadata may be received in a URL (Uniform Resource Locator) format.

[0079] In one embodiment, the user terminal 230 can acquire the playing time of the performance video that the user is viewing. The playing time may refer to the point in time on the performance timeline where the user is currently viewing the scene. The playing time may be the same as the actual time at the performance venue, or may be slower than the actual time at the performance venue due to data transmission delays over the network. For example, the user terminal 230 can acquire the playing time from an electronic device (e.g., the user terminal or an external electronic device) on which the user is viewing the performance video. For example, the user terminal 230 can receive the playing time input from the user via a display.

[0080] In one embodiment, the user terminal 230 may identify metadata (e.g., first metadata) corresponding to a playing time from the at least one piece of received metadata. For example, the first metadata may indicate at least one lighting effect. The user terminal 230 may generate a lighting control signal based on the first metadata. For example, the lighting control signal may correspond to a lighting effect to be performed on the stage for a specified time from the playing time.

[0081] In one embodiment, the user terminal 230 can acquire information about a live performance currently being performed at the performance venue 200 and download metadata corresponding to a performance currently being performed or scheduled to be performed at the performance venue 200 from the server 220. The user terminal 230 can generate a lighting control signal based on the downloaded metadata. For example, the lighting control signal can correspond to a lighting effect to be performed at the performance for a specified time from the play time.

[0082] In one embodiment, the user terminal 230 may transmit the generated light emitting control signal to the receiving device 240. The receiving device 240 may emit light in a color according to the light emitting control signal via a light emitting unit.

[0083] In one embodiment, when the user terminal 230 acquires a new playing time, the user terminal 230 may identify metadata (e.g., second metadata) corresponding to the playing time from among the at least one piece of received metadata, and generate a lighting control signal based on the second metadata. The user terminal 230 may transmit the newly generated lighting control signal to the receiving device 240.

[0084] For a detailed description of the operations of the server 220, the user terminal 230, and the receiving device 240, please refer to the description of FIGS.

[0085] FIG. 5 illustrates a signal flow diagram between the server 220, the user terminal 230, and the receiving device 240, according to one embodiment of the present disclosure.

[0086] In one embodiment, the user terminal 230 may include a software development kit (SDK) 500 and an application 505. For example, the SDK 500 and the application 505 may be stored in a memory of the user terminal 230. In one embodiment, the SDK 500 may be distributed by a developer of the metadata generation system. In one embodiment, the application 505 may be understood to be an application related to viewing videos (e.g., performance videos). The operations of the SDK 500 and the application 505 in FIG. 5 may be understood to be substantially performed by a processor of the user terminal 230.

[0087] In one embodiment, the application 505 may request synchronization from the SDK 500 (510). For example, the application 505 may transmit performance information (e.g., performance ID) of the performance currently being viewed by the user to the SDK 500 for synchronization. The application 505 may identify performance information of the performance video currently being played on the user terminal 230 or obtain performance information from an external electronic device currently playing the performance video.

[0088] In response to the synchronization request, the SDK 500 may check the status of a network (e.g., cellular, Bluetooth) (512) and request a status check from the receiving device 240 (514). The receiving device 240 may transmit a status check signal to the SDK 500. For example, the status check signal may indicate that the receiving device 240 is able to establish a wireless network connection (e.g., Bluetooth) with the SDK 500.

[0089] The SDK 500 can transmit (518) a status confirmation signal for the receiving device 240 to the application 505 and check (520) the status of the server 220. For example, the SDK 500 can check that the user terminal 230 can communicate with the server 220 via a stable network.

[0090] The SDK 500 may request a wireless network connection (e.g., Bluetooth) from the receiving device 240 (522). In response to the request for a wireless network connection, the receiving device 240 may wirelessly connect to the user terminal 230 (524).

[0091] The SDK 500 may check the connection status of the receiving device 240 with the application 505 (526). For example, the SDK 500 may transmit a signal to the application 505 indicating that the user terminal 230 is wirelessly connected to the receiving device 240.

[0092] The application 505 can request a lighting effect from the SDK 500 (530). The lighting effect may refer to a lighting effect currently being performed in the performance video being viewed by the user.

[0093] The SDK 500 may request at least one piece of metadata from the server 220 in response to the lighting production request (532). The server 220 may transmit at least one piece of metadata to the SDK 500 in response to the metadata request (534). In one embodiment, if the performance production information for the performance being viewed by the user includes multiple pieces of stage information, the server 220 may transmit multiple pieces of metadata corresponding to each of the multiple pieces of stage information. The at least one piece of metadata may be data based on the JSON format.

[0094] The application 505 can transmit 540 the playing time to the SDK 500. The playing time can refer to the point in time on the performance timeline at which the user is currently viewing the scene.

[0095] In one embodiment, the user terminal 230 can receive a playing time input from a user via a display. Referring to FIG. 8 , a screen 600 can be understood as a screen of the application 505 displayed via the display of the user terminal 230. The user can input the playing time via an input area 610. For example, the user can check the time displayed in the video of the performance they are watching and input it in the input area 610.

[0096] Referring again to FIG. 5, the SDK 500 may identify metadata corresponding to a playing time from among the at least one piece of metadata and generate a control signal based on the identified metadata (542).

[0097] The SDK 500 may transmit the control signal to the receiving device 240 (544). The receiving device 240 may cause the light emitting unit to emit light of a color according to the light emitting control signal. Operations 540 to 544 may be repeated until the performance video ends (546).

[0098] The application 505 can confirm that the performance video has ended and request the SDK 500 to end the lighting effect (548).

[0099] Referring to FIG. 6, the same parts as those in FIG. 5 will be omitted from the description.

[0100] The SDK 500 may request first metadata from the server 220 (630). It may be understood that no performance is being performed at the performance venue 200 when the SDK 500 requests the first metadata from the server 220. The first metadata request signal may include performance information (e.g., a performance ID). The first metadata may be metadata corresponding to a predetermined stage (e.g., the first stage) to be performed first in the performance. The server 220 may transmit a URL of the first metadata to the SDK 500 based on the performance information (632). The SDK 500 may request the server 220 to download the first metadata based on the URL of the first metadata (634). The SDK 500 may download the first metadata from the server 220 (636).

[0101] The SDK 500 may poll the server 220 for live performance information (640). This may be understood as an operation to check whether the next performance (e.g., the first performance) has started. The server 220 may transmit a response to the polling of the live performance information to the SDK 500 (642). If the first performance has not started in the performance hall 200, the SDK 500 may repeat operations 640 to 642 at regular time intervals (644). For example, the SDK 500 may repeat operations 640 to 642 at random time intervals of 3 to 5 seconds to distribute traffic concentrated on the server (544).

[0102] 7, once the first performance begins, the SDK 500 may receive a response (549) to the polling (547) indicating that the first performance has begun. In one embodiment, once the first performance begins, the administrator of the server 220 may update the performance production information stored in the server 220. For example, the administrator may update the stage information area on the screen 400 of FIG. 4. In another embodiment, the performance production information may be updated automatically by a program (e.g., a Windows-based program) installed on the server 220. The program may be linked to the system 20 of the performance venue 200.

[0103] The application 505 can transmit 550 a playing time to the SDK 500. The playing time can refer to the point in time on the performance timeline at which the user is currently watching the scene.

[0104] In one embodiment, the user terminal 230 can receive a playing time input from a user via a display. Referring to FIG. 8 , a screen 600 can be understood as a screen of the application 505 displayed via the display of the user terminal 230. The user can input the playing time via an input area 610. For example, the user can check the time displayed in the video of the performance they are watching and input it in the input area 610.

[0105] 7, the SDK 500 may generate a light-emitting control signal according to the first metadata based on the playing time (552). The SDK 500 may transmit the light-emitting control signal to the receiving device 240 (554). The receiving device 240 may cause the light-emitting unit to emit a color according to the light-emitting control signal. Operations 550 to 554 may be repeated until the first stage performance is completed (556).

[0106] Operations 560 to 566 may be performed while a first stage is being performed in the performance hall 200. The SDK 500 may request second metadata from the server 220 (560). Operation 560 may be understood as downloading metadata in advance for performing lighting effects for the second stage. The server 220 may transmit a URL of the second metadata to the SDK 500 based on performance information (562). The SDK 500 may request the server 220 to download the second metadata based on the URL of the first metadata (564). The SDK 500 may download the second metadata from the server 220 (566).

[0107] The SDK 500 may poll the server 220 for live performance information (570). This may be understood as an operation to check whether the next performance (e.g., the second performance) has started. The server 220 may transmit a response to the polling of the live performance information to the SDK 500 (572). If the performance of the second performance has not started in the performance hall 200, the SDK 500 may repeat operations 570 to 572 at regular time intervals. For example, the SDK 500 may repeat operations 570 to 572 at random time intervals of 3 to 5 seconds to distribute traffic concentrated on the server (574).

[0108] The above-described operations related to the first stage (operations 546 to 574) may be repeated until all stages (e.g., first to fourth stages) previously determined for the performance have been performed. In one embodiment, when the performances for all stages have been performed, the application 505 may request the SDK 500 to end the lighting performance (580).

[0109] FIG. 9 is a block diagram illustrating a user terminal 230 according to an exemplary embodiment of the present disclosure.

[0110] The user terminal 230 may include a processor 700 , a communication unit 710 , a memory 720 and / or a display 730 .

[0111] The processor 700 may control the overall operation of the user terminal 230, and more specifically, the operation of other components constituting the user terminal 230. The processor 700 may be embodied as a general-purpose processor, a dedicated processor, an application processor, or the like. In an exemplary embodiment, the processor 700 may be embodied as an arithmetic processor (e.g., a central processing unit (CPU), a graphic processing unit (GPU), an application processor (AP), etc.) including a dedicated logic circuit (e.g., a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.), but is not limited thereto.

[0112] The communication unit 710 can communicate with various types of external devices through various types of communication methods, and may include at least one of a WiFi (Wireless-Fidelity) chip, a Bluetooth (Bluetooth trademark) chip, a wireless communication chip, an NFC (Near Field Communication) chip, and an RFID (Radio Frequency Identification) chip.

[0113] According to the mobile communication technology of the present disclosure, the communication unit 710 can transmit and receive radio signals to and from at least one of a base station, an external terminal, and an external server over a mobile communication network established by a technical standard or communication method (e.g., GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), CDMA2000 (Code Division Multi Access 2000), EV-DO (Enhanced Voice-Data Optimized or Enhanced Voice-Data Only), WCDMA (Wideband CDMA), HSDPA (High Speed ​​Downlink Packet Access), HSUPA (High Speed ​​Uplink Packet Access), LTE (Long Term Evolution), LTE-A (Long Term Evolution-Advanced), etc.).

[0114] Furthermore, examples of wireless technologies disclosed herein include WLAN (Wireless LAN), Wi-Fi (Wireless Fidelity), Wi-Fi (Wireless Fidelity) Direct, DLNA (Digital Living Network Alliance), WiBro (Wireless Broadband), WiMAX (World Interoperability for Microwave Access), HSDPA (High Speed ​​Downlink Packet Access), HSUPA (High Speed ​​Uplink Packet Access), LTE (Long Term Evolution), and LTE-A (Long Term Evolution-Advanced).

[0115] Furthermore, the communication technology of the present disclosure may include technology that supports communication using at least one of Bluetooth (Bluetooth registered trademark), RFID (Radio Frequency Identification), Infrared Data Association (IrDA), UWB (Ultra WideBand), ZigBee, NFC (Near Field Communication), Wi-Fi (Wireless Fidelity), Wi-Fi Direct, Wireless USB (Wireless Universal Serial Bus), TTL (Transistor-Transistor Logic), USB, IEEE1394, Ethernet, MIDI (Musical Instrument Digital Interface), RS232, RS422, RS485, Optical Communication, and Coaxial Cable Communication technologies.

[0116] The memory 720 may be a local storage medium that supports various functions of the user terminal 230. The memory 720 may store data and instructions for operation of the user terminal 230. At least a portion of such application programs may be downloaded from an external device (e.g., the server 100) via wireless communication. The application programs may be stored in the memory 720, installed on the user terminal 230, and driven to perform operations (or functions) by the processor 700 of the user terminal 230. In one embodiment, the memory 720 may include the SDK 500 and application 505 of FIG. 5.

[0117] The memory 720 may be a dynamic random access memory (DRAM) such as a double data rate synchronous dynamic random access memory (DDRS DRAM), a low power double data rate (LPDDR) SDRAM, a graphics double data rate (GDDR) SDRAM, a Rambus dynamic random access memory (RDRAM), a DDR2 SDRAM, a DDR3 SDRAM, a DDR4 SDRAM, etc.

[0118] However, embodiments of the present disclosure are not necessarily limited thereto. In an exemplary embodiment, the memory 720 may be implemented as a writable non-volatile memory, which must retain data even when power to the stage production device 110 is cut off and can reflect changes. However, without being limited thereto, the memory 720 may be implemented as a flash memory, an EPROM, an EEPROM, a resistive memory cell such as a resistive RAM (ReRAM), a phase change RAM (PRAM), a magnetic RAM (MRAM), a spin-transfer torque MRAM (MRAM), a conductive bridging RAM (CBRAM), a ferroelectric RAM (FeRAM), or various other types of memory. Alternatively, the memory 720 may be implemented by various types of devices, such as an embedded multimedia card (eMMC), universal flash storage (UFS), Compact Flash (CF), Secure Digital (SD), MicroSecure Digital (Micro-SD), Mini Secure Digital (Mini-SD), extreme Digital (xD), or Memory Stick. For convenience of explanation in this disclosure, all instruction information is described as being stored in one memory 720, but this is not limiting, and the memory 720 may include multiple memories.

[0119] The display 730 displays (outputs) information processed in the user terminal 230. For example, the display 730 can display execution screen information of an application program (for example, an application) running on the device, or UI (User Interface) or GUI (Graphical User Interface) information based on such execution screen information.

[0120] FIG. 10 is a block diagram illustrating a receiving device according to an exemplary embodiment of the present disclosure.

[0121] The receiving device 240 may include a processor 800, a communication unit 810, a memory 820, and a light emitting unit 830. Descriptions of the processor 800, the communication unit 810, and the memory 820 may refer to the descriptions of the processor 700, the communication unit 710, and the memory 720 in FIG.

[0122] The light emitting unit 830 may include one or more light source elements, and the light source elements may be, for example, light emitting diodes (LEDs), etc. The light emitting unit 830 may output light of various colors according to RGB color information using the light source elements.

[0123] In one embodiment, the processor 800 can receive a control signal from the user terminal 230 via the communication unit 810 and cause the light emitting unit 830 to emit a color according to the light emitting control signal.

[0124] FIG. 11 illustrates a toy-shaped receiving device according to an exemplary embodiment of the present disclosure.

[0125] In one embodiment, the receiving device 240 may be embodied in a toy shape, such as a transforming robot 900. The shape of the transforming robot 900 is merely an example, and the embodiments of the present disclosure are not limited thereto.

[0126] In one embodiment, the transforming robot 900 may be comprised of a head 905, a torso 910, and at least one limb 910, 912, 914, 916. The transforming robot 900 may include a plurality of joints 920, 922, 924, 926 connecting the torso 910 and the at least one limb 910, 912, 914, 916. The transforming robot 900 may also include a plurality of end portions 930, 932, 934, 936 attached to the at least one limb 910, 912, 914, 916.

[0127] In one embodiment, the transforming robot 900 may include at least one light-emitting unit (e.g., light-emitting unit 830 in FIG. 8 ). For example, the at least one light-emitting unit may be disposed at at least one of the joints 920, 922, 924, and 926. For example, the at least one light-emitting unit may be disposed at at least one of the end portions 930, 932, 934, and 936. The attachment position of the at least one light-emitting unit in FIG. 9 is merely exemplary, and the embodiments of the present disclosure are not limited thereto. For example, the at least one light-emitting unit may be attached to the center of the torso 910 of the transforming robot 900.

[0128] In one embodiment, the transforming robot 900 is not limited to the robot form shown in FIG. 9 and can be transformed into various forms. In one embodiment, the positions of the joints 920, 922, 924, and 926 of the transforming robot 900 may be adjustable. For example, the joints 920, 922, 924, and 926 can be moved and / or rotated in various directions to guide changes in the overall shape of the transforming robot 900. For example, the transforming robot 900 can be transformed into another form (e.g., a car or a train) by manipulating the positions of the joints 920, 922, 924, and 926 in the robot form.

[0129] In one embodiment, the transforming robot 900 may include a processor, a communication unit, a drive motor operatively coupled to the plurality of joints 920, 922, 924, and 926, and a battery electrically connected to the drive motor. Hereinafter, it may be understood that the operation of the transforming robot 900 is substantially performed by the processor.

[0130] In one embodiment, the transforming robot 900 may include a memory. At least one performance scenario may be stored in the memory of the transforming robot 900. The at least one performance scenario may be stored in the memory during the production stage of the transforming robot 900, or may be received from the server 220 via the user terminal 230 and stored in the memory.

[0131] In one embodiment, the transforming robot 900 can receive a control signal instructing one of at least one performance scenario from the user terminal 230. For example, the control signal may be generated based on metadata received by the user terminal 230 from the server 220, or may be generated independently by the application 505 installed on the user terminal 230.

[0132] In one embodiment, the transforming robot 900 can perform a performance scenario stored in a memory based on a control signal. For example, the transforming robot 900 can use drive motors to perform movements (e.g., swinging arms, walking) according to the performance scenario. For example, the transforming robot 900 can use the drive motors to move multiple joints 920, 922, 924, and 926, and emit light of a specified color using light-emitting units.

[0133] In one embodiment, the transforming robot 900 may further include a speaker. The transforming robot 900 can receive an audio control signal from the user terminal 230. The transforming robot 900 can output a specified sound through the speaker based on the control signal.

[0134] In one embodiment, the transforming robot 900 may include a separate button for performing a specified action. The transforming robot 900 may receive user input through the button. The transforming robot 900 may perform an action according to a performance scenario in response to the button input without receiving a control signal. The performance scenario may be pre-stored in the memory of the transforming robot 900.

[0135] The steps of a method or algorithm described in connection with the embodiments of the present disclosure may be embodied directly in hardware, in a software module executed by hardware, or in a combination thereof. The software module may reside in Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Flash Memory, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium well known in the art to which the present disclosure pertains.

[0136] Various embodiments of the present disclosure may be embodied as software including one or more instructions stored in a machine-readable storage medium (e.g., memory). For example, a processor (e.g., processor 330, 440) of the device may retrieve and execute at least one of the one or more stored instructions from the storage medium. This may enable the device to be operated to perform at least one function according to the retrieved at least one instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term "non-transitory storage medium" simply means a tangible device that does not contain a signal (e.g., electromagnetic waves), and does not distinguish between data being stored semi-permanently and data being stored temporarily in the storage medium. For example, the "non-transitory storage medium" may include a buffer in which data is temporarily stored.

[0137] According to one embodiment, methods according to various embodiments disclosed in this disclosure may be provided in a computer program product. The computer program product may be traded as a commodity between a seller and a buyer. The computer program product may be distributed in the form of a device-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)) or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product (e.g., a downloadable app) may be at least temporarily stored or temporarily generated in a device-readable storage medium, such as the memory of a manufacturer's server, an application store server, or an intermediary server.

[0138] Although the embodiments of the present disclosure have been described above with reference to the accompanying drawings, it should be understood by those skilled in the art that the present disclosure can be embodied in other specific forms without changing the technical spirit or essential characteristics thereof. Therefore, it should be understood that the above-described embodiments are illustrative in all respects and are not limiting.

Claims

1. In a user terminal that produces lighting effects for videos provided through a VOD service, a communication unit for communicating with the server and the receiving device; Memory and a processor electrically connected to the communication unit and the memory, The processor: Acquire relevant information and playing time of the video; requesting and receiving at least one piece of metadata from the server based on the related information; Identifying first metadata corresponding to the playing time from the at least one piece of metadata, and generating a light emission control signal based on the first metadata; configured to transmit the light emission control signal to the receiving device; User terminal.

2. further comprising a display; The processor: further configured to receive input of the playing time from a user via the display. The user terminal of claim 1 .

3. the at least one metadata includes at least one of color information and a time code; The user terminal according to claim 2 .

4. The related information includes performance information, The performance information includes at least one of a performance ID, a performance name, a performance date and time, and at least one piece of stage information. The user terminal according to claim 3.

5. At least one piece of metadata is predefined for each of the at least one piece of venue information.

5. The user terminal according to claim 4.

6. A method for producing lighting effects for videos provided through a VOD service, The user terminal acquires the content related information and playing time of the video; The user terminal requests at least one piece of metadata from a server based on the related information; receiving, by the user terminal, the at least one piece of metadata from the server; The user terminal identifies first metadata corresponding to the playing time from the at least one piece of metadata, and generates a light emission control signal based on the first metadata; The user terminal transmits the light emission control signal to a receiving device. method.

7. the step of acquiring the playing time includes a step of receiving, by the user terminal, an input of the playing time from a user via a display; The method of claim 6.

8. the at least one metadata includes at least one of color information and a time code; The method of claim 7.

9. The related information includes performance information, The performance information includes at least one of a performance ID, a performance name, a performance date and time, and at least one piece of stage information. The method of claim 8.

10. the at least one piece of metadata is predefined for each of the at least one piece of venue information; 10. The method of claim 9.

11. The step of generating the light emission control signal by the user terminal includes: If the user terminal acquires a new playing time, generating the light emission control signal based on the newly acquired playing time; and when the video ends, the user terminal interrupts the lighting performance. The method of claim 10.

12. The at least one metadata is data based on the JSON format. The method of claim 11.

13. the receiving device includes a processor, a memory, and a light emitting unit; the processor is configured to cause the light-emitting unit to emit light of a hue according to the light-emission control signal; The method of claim 12.

14. The receiving device at least one articulation unit whose position is adjustable and a processor; The toy further includes at least one of a drive motor for driving the at least one joint, a light-emitting unit, and a speaker, The processor: receiving at least one of the light emission control signal, the operation control signal, or the sound control signal from the user terminal; When the light emission control signal is received, the light emitting unit emits light of a color according to the light emission control signal; When the motion control signal is received, the at least one joint is driven to perform a designated motion; When the audio control signal is received, the speaker is configured to output audio according to the audio control signal. The method of claim 12.

15. A user terminal that produces lighting effects for performance videos provided through live streaming, a communication unit for communicating with the server and the receiving device; Memory and a processor electrically connected to the communication unit and the memory, The processor: Acquire performance information and playing time of the performance video, requesting first metadata corresponding to a first performance from the server based on the performance information; downloading the first metadata from the server; Check the stage information that will be produced in real time during the performance, generating a light emission control signal based on the playing time and the first metadata in response to the first stage being performed in the performance; configured to transmit the light emission control signal to the receiving device; User terminal.

Images