KR102593616B1 - Operation method of the sound monitoring system - Google Patents

Abstract

The present invention includes the steps of, when a broadcast server requests registration of usage history information for a main broadcast sound source, the monitoring server transmits, to a network management server, creation request information for creating a block for registration of the usage history information; When the network management server confirms that the broadcast server and the monitoring server are mutually designated networks based on the creation request information, transmitting a registration permission signal of the block to the monitoring server and receiving the registration permission signal , Provides a method of operating a sound source monitoring system including the steps of the monitoring server executing a chain code for creation of the block and registering the usage history information in the block.

Description

Operation method of the sound monitoring system {Operation method of the sound monitoring system}

The present invention relates to a method of operating a sound source monitoring system, and more specifically, to a method of operating a sound source monitoring system that facilitates copyright settlement and distribution of sound sources when distributed on a blockchain-based network.

Currently, the music industry's interest in broadcast music, or broadcast music, is increasing.

Broadcast music is music inserted into a broadcasting company's broadcast content. For example, it may be a piano solo song that elevates an actor's sad emotions while showing them in a scene of a drama, and all music inserted in the broadcasting company's drama content. It can be said to be broadcast music.

Broadcast music, like regular music, is a creative work, and there are rights holders such as lyricists and composers who own the rights to the music, and all rights holders can receive copyright settlement and distribution in proportion to the use of the music.

In the form of music rights, the music rights holder exercises the rights alone, but it is inefficient because it costs a lot of money and time, so the rights to one's music can usually be entrusted to a trust management organization.

In addition, a trust management organization can exercise the music rights on behalf of the music rights, and in transparent settlement and distribution of broadcast music, a usage history aggregation system that satisfies all broadcast music users (mainly broadcasters), trust management organizations, and music rights holders is needed.

Recently, in the process of receiving copyright settlement and distribution for the main distribution sound source, that is, broadcast music, it is difficult to implement an accurate monitoring system, so settlement and distribution are being done haphazardly. Therefore, research is being conducted to determine accurate settlement and distribution for broadcast music. I'm doing it.

The purpose of the present invention is to provide a method of operating a music source monitoring system that facilitates copyright settlement and distribution of music sources on a blockchain-based network.

Additionally, the purpose of the present invention is to provide a method of operating a sound source monitoring system that can prevent omission of information on the use of sound sources during main distribution.

The objects of the present invention are not limited to the objects mentioned above, and other objects and advantages of the present invention that are not mentioned can be understood by the following description and will be more clearly understood by the examples of the present invention. Additionally, it will be readily apparent that the objects and advantages of the present invention can be realized by the means and combinations thereof indicated in the patent claims.

The operating method of the sound source monitoring system according to the present invention is that, when a broadcast server requests registration of usage history information for a main broadcast sound source, the monitoring server sends creation request information to the network to create a block for registration of the usage history information. Transmitting to a management server, when the network management server confirms that the broadcast server and the monitoring server are mutually designated networks based on the creation request information, transmitting a registration permission signal of the block to the monitoring server, and When receiving the registration permission signal, the monitoring server may execute a chain code for creating the block and register the usage history information in the block.

The creation request information may include a user code and user name using the broadcast server, and a monitoring organization code and monitoring organization name using the monitoring server.

The step of transmitting the registration permission signal includes transmitting the user code, the user name, the monitoring group code, and the monitoring group name to the mutually designated network in which the user code, the user name, the standard monitoring group code, and the monitoring group name are preset. You can check if it is the same as the organization name.

The chain code may be a smart contract between the broadcast server and the monitoring server for generating and monitoring the usage history information.

The usage history information includes the content transmission date including the main distribution sound source, content channel code, content code, content start and end time, start and end time of the main distribution sound source, and a unique identifier of the main distribution sound source. May include UCI (Universal Content Identifier) code.

After the step of registering in the block, when a request is made to modify the usage history information from the broadcast server, the monitoring server executes the chain code to modify and register the usage history information, and changes the usage history registered in the block. A step of modifying information may be further included.

After the step of modifying the usage history information, the network management server may register correction information including a modification date, modification time, and modification content for the modification of the usage history information in the block.

When requesting an inquiry of the usage history information from a trust management server, the monitoring server transmits inquiry request information for inquiry of the usage details information to the network management server, wherein the network management server sends the inquiry request information. Based on this, if the trust management server and the monitoring server confirm that they are mutually designated networks, transmitting an inquiry approval signal for the usage history information to the trust management server, the trust management server executing a chain code for the inquiry When execution of the step and the chain code is completed, the network management server may further include transmitting the usage history information to the trust management server.

The operating method of the music source monitoring system according to the present invention is to generate information on the use of sound sources when playing by making the accurate monitoring results, usage details, and settlement method of the use of sound sources when playing on a blockchain-based network transparent. There is an advantage.

In addition, the method of operating the sound source monitoring system according to the present invention can check music information, rights management information, and information about copyright holders of the sound source at the time of main distribution, and can be used as raw data for transparent settlement and distribution of copyright fees. There is an advantage.

Meanwhile, the effects of the present invention are not limited to the effects mentioned above, and various effects may be included within the range apparent to those skilled in the art from the contents described below.

Figure 1 is a system block diagram showing a sound source monitoring system according to the present invention.
Figures 2 and 3 are flow charts showing the operation method of the sound source monitoring system according to the present invention.

Since the present invention can make various changes and have various embodiments, specific embodiments will be described in detail with reference to the drawings. However, this is not intended to limit the present invention to specific embodiments, and should be understood to include all changes, equivalents, and substitutes included in the spirit and technical scope of the present invention. While describing each drawing, similar reference numerals are used for similar components.

Terms such as first, second, A, and B may be used to describe various components, but the components should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, a first component may be named a second component without departing from the scope of the present invention, and similarly, the second component may also be named a first component. The term and/or includes any of a plurality of related description items or a combination of a plurality of related description items.

When a component is referred to as being “connected” or “connected” to another component, it should be understood that it may be directly connected to or connected to that other component, but that other components may exist in between. something to do. On the other hand, when it is mentioned that a component is “directly connected” or “directly connected” to another component, it should be understood that there are no other components in between.

The terms used in this application are only used to describe specific embodiments and are not intended to limit the invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the technical field to which the present invention pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and unless explicitly defined in the present application, should not be interpreted in an ideal or excessively formal sense. No.

Throughout the specification and claims, when it is said that a part includes a certain component, this does not mean that other components are excluded, but that other components may be further included, unless specifically stated to the contrary.

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the attached drawings.

Figure 1 is a system block diagram showing a sound source monitoring system according to the present invention.

Referring to FIG. 1, the sound source monitoring system 100 may include a broadcasting server 110, a monitoring server 120, a trust management server 130, and a network management server 140.

The broadcast server 110 may include a broadcasting company and a personal broadcasting platform that uses broadcast music (hereinafter referred to as 'main sound source'). Here, the main sound source may be an abbreviation for the main sound source, background sound source, and signal sound source included in the broadcast music.

Here, the broadcasting server 110 can play or output the sound source during main distribution, and the broadcasting server 110 provides usage history information about the sound source during main distribution to the monitoring server 120 in order to play or output the sound source during main distribution. You may request registration.

That is, the broadcasting server 110 may request the network management server 140 to create a block that can register the usage history information of the main distribution sound source in order to use the main distribution sound source.

Here, the broadcasting server 110 and the monitoring server 120 may be in a mutually designated network contract for use and monitoring of sound sources during main distribution.

The monitoring server 120 may be an organization or organization that can monitor the usage details of sound sources during main distribution.

When the broadcasting server 110 requests registration of usage history information for the main distribution sound source, the monitoring server 120 generates a block for registering the usage history information of the main distribution sound source and sends the creation request information to the network management server 140. ) can be requested.

The creation request information may include, but is not limited to, a user code and user name using the broadcast server 110, and a monitoring organization code and monitoring organization name using the monitoring server 120.

Afterwards, when receiving a registration permission signal transmitted from the network management server 140, the monitoring server 120 can execute the chain code for the creation of the block and register the usage history information about the sound source in the block. there is.

The chain code may be a smart contract between the broadcast server 110 and the monitoring server 120 for generating and monitoring usage history information, but is not limited thereto.

The usage history information includes the content transmission date including the main broadcast sound source, content channel code, content code, content start and end time, start and end time of the main broadcast sound source, and UCI for the unique identifier of the main broadcast sound source. (Universal Content Identifier) code may be included.

In addition, the UCI code is a service currently provided by the Korea Copyright Commission and is the only and permanent national standard identification system assigned to content. By assigning a UCI identifier to sound source content, data information and distribution channels can be effectively identified.

The monitoring server 120 may input detailed information about items included in the usage history information registered in the block.

At this time, the detailed information may include sound source information, rights information, management information, usage information, and normal information about the main distributed sound source.

The sound source information includes the unique identifier, song name, and album of the main distribution sound source, the rights information includes the copyright holder and contract details, the management information includes the business operator, settlement code, and song code, and the usage information includes the business operator. , service and sound source usage information, and the settlement information may include the amount, but is not limited thereto.

When the broadcasting server 110 requests a modification of the usage history information for the main broadcast sound source, the monitoring server 120 may execute the chain code to register a correction to the usage history information for the main distribution sound source.

The chain code may be a smart contract between the broadcast server 110 and the monitoring server 120 for generating and monitoring usage history information, but is not limited thereto.

Thereafter, the monitoring server 120 may modify and register the usage history information registered in the block.

The trust management server 130 provides the main distribution sound source to the broadcast server 110 and manages copyright settlement and distribution of the main distribution sound source.

The trust management server 130 may request the monitoring server 120 to inquire about the usage history information of the sound source during main distribution.

At this time, when the monitoring server 120 receives a request for inquiry of the usage history information from the trust management server 130, it may transmit inquiry request information for inquiry of the usage history information to the network management server 140.

Thereafter, the trust management server 130 can query the usage history information transmitted from the network management server 140 after executing the chain code for the inquiry.

The network management server 140 can perform and manage the blockchain-based network configuration, that is, the approval process for blocks between the broadcast server 110, the monitoring server 120, and the trust management server 130.

First, when registering the usage history information of the main broadcast sound source, when the network management server 140 receives the creation request information from the monitoring server 120, the broadcasting server 110 and the monitoring server based on the creation request information (120) can check whether a mutually designated network is formed.

That is, the network management server 140 sends the user code, user name, monitoring group code, and monitoring group name included in the creation request information to the mutually designated network, the standard user code, standard user name, standard monitoring group code, and You can check whether the name of the standard monitoring organization is the same.

Thereafter, when the broadcasting server 110 and the monitoring server 120 are confirmed to be the mutually designated network, the network management server 140 may transmit the registration permission signal for block creation to the monitoring server 120.

When modifying the usage history information of the main distribution sound source, the network management server 140 can check the chain code executed by the monitoring server 120 to register the correction of the usage history information of the main distribution sound source.

Thereafter, as described above, the monitoring server 120 may modify and register the usage history information.

In addition, the network management server 140 may register correction information including the modification date, modification time, and modification content for the modification of the usage history information in the block, but is not limited to this.

Finally, when receiving inquiry request information for the usage history information of the main broadcast sound source from the monitoring server 130, the network management server 140 operates the monitoring server 120 and the trust management server based on the inquiry request information ( You can check whether 130) is a mutually designated network.

Thereafter, when the network management server 140 confirms that the monitoring server 120 and the trust management server 130 are mutually designated networks, the network management server 140 may transmit an approval signal for inquiry of usage history information to the trust management server 130.

At this time, the trust management server 130 can execute the chain code when receiving the inquiry approval signal, and when the chain code execution is completed, the network management server 140 transmits the usage history information to the trust management server 130. can do.

Here, the block in which the usage history information of the sound source is registered may include a hash value of the data to ensure integrity, and when the trust management server 130 or the broadcasting server 110 receives the usage history information, The integrity of the data can be confirmed by comparing the received record with the hash value included in the block.

Figures 2 and 3 are flow charts showing the operation method of the sound source monitoring system according to the present invention.

Referring to FIG. 2, the monitoring server 120 of the sound source monitoring system 100 generates a block to register the use history information when requesting registration of usage history information for the main broadcast sound source from the broadcasting server 110. Creation request information may be transmitted to the network management server 140 (S110).

That is, when the broadcasting server 110 requests registration of usage history information for the main distribution sound source, the monitoring server 120 generates a block for registering the usage history information of the main distribution sound source and sends the creation request information to the network management server. You can request it at (140).

The creation request information may include, but is not limited to, a user code and user name using the broadcast server 110, and a monitoring organization code and monitoring organization name using the monitoring server 120.

When the network management server 140 of the sound source monitoring system 100 confirms that the broadcasting server 110 and the monitoring server 120 are mutually designated networks based on the creation request information, the network management server 140 registers the block with the monitoring server 120. A permission signal can be transmitted (S120).

That is, when the network management server 140 receives the creation request information from the monitoring server 120, the broadcasting server 110 and the monitoring server 120 check whether a mutually designated network is formed based on the creation request information. You can.

The network management server 140 connects the user code, user name, monitoring group code, and monitoring group name included in the creation request information to the mutually designated network where the reference user code, standard user name, standard monitoring group code, and standard monitoring group name are preset. You can check if it is the same as the organization name.

Thereafter, when the broadcasting server 110 and the monitoring server 120 are confirmed to be the mutually designated network, the network management server 140 may transmit the registration permission signal for block creation to the monitoring server 120.

When receiving the registration permission signal, the monitoring server 120 may execute the chain code for creating the block and register the usage history information in the block (S130).

That is, when receiving a registration permission signal transmitted from the network management server 140, the monitoring server 120 can execute the chain code for the creation of the block and register the usage history information about the sound source in the block. there is.

The chain code may be a smart contract between the broadcast server 110 and the monitoring server 120 for generating and monitoring usage history information, but is not limited thereto.

The usage history information includes the content transmission date including the main broadcast sound source, content channel code, content code, content start and end time, start and end time of the main broadcast sound source, and UCI for the unique identifier of the main broadcast sound source. (Universal Content Identifier) code may be included.

In addition, the UCI code is a service currently provided by the Korea Copyright Commission and is the only and permanent national standard identification system assigned to content. By assigning a UCI identifier to sound source content, data information and distribution channels can be effectively identified.

The monitoring server 120 may input detailed information about items included in the usage history information registered in the block.

After step (S130), the monitoring server 120 executes the chain code to register the modification of the usage history information when requesting modification of the usage history information from the broadcast server 110 and uses the usage details registered in the block. History information can be modified (S140).

Thereafter, the network management server 140 may register correction information including the modification date, modification time, and modification content regarding the modification of the usage history information in the block (S150).

That is, when a request is made to modify the usage history information for the main broadcast sound source from the broadcasting server 110, the monitoring server 120 may execute the chain code to register a correction to the usage history information for the main distribution sound source.

The chain code may be a smart contract between the broadcast server 110 and the monitoring server 120 for generating and monitoring usage history information, but is not limited thereto.

Thereafter, the monitoring server 120 may modify and register the usage history information registered in the block.

Referring to FIG. 3, when the monitoring server 120 of the sound source monitoring system 100 requests an inquiry about the usage history information of the main distribution sound source from the trust management server 130, it sends inquiry request information for inquiry of the usage history information. can be transmitted to the network management server 140 (S210).

If the trust management server 130 and the monitoring server 120 confirm that they are mutually designated networks based on the inquiry request information, the network management server 140 sends an approval signal for inquiry of the usage history information to the trust management server 130. Can be transmitted (S220).

The trust management server 130 executes the chain code for the inquiry (S230). When execution of the chain code is completed, the network management server 140 may transmit the usage history information to the trust management server 130 (S240).

That is, the trust management server 130 provides the main distribution sound source to the broadcast server 110 and manages copyright settlement and distribution of the main distribution sound source.

The trust management server 130 may request the monitoring server 120 to inquire about the usage history information of the sound source during main distribution.

At this time, when the monitoring server 120 receives a request for inquiry of the usage history information from the trust management server 130, it may transmit inquiry request information for inquiry of the usage history information to the network management server 140.

The network management server 140 may check whether the monitoring server 120 and the trust management server 130 are mutually designated networks based on the inquiry request information.

Thereafter, when the monitoring server 120 and the trust management server 130 confirm that they are mutually designated networks, the network management server 140 may transmit an inquiry approval signal for use history information to the trust management server 130.

The trust management server 130 can query the usage history information sent from the network management server 140 after executing the chain code for the inquiry.

The features, structures, effects, etc. described in the embodiments above are included in at least one embodiment of the present invention and are not necessarily limited to only one embodiment. Furthermore, the features, structures, effects, etc. illustrated in each embodiment can be combined or modified and implemented in other embodiments by a person with ordinary knowledge in the field to which the embodiments belong. Therefore, contents related to such combinations and modifications should be construed as being included in the scope of the present invention.

The above description is merely an illustrative explanation of the technical idea of the present invention, and various modifications and variations will be possible to those skilled in the art without departing from the essential characteristics of the present invention. Accordingly, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention, but are for illustrative purposes, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be interpreted in accordance with the claims below, and all technical ideas within the equivalent scope should be construed as being included in the scope of rights of the present invention.

Claims (8)

When a broadcast server requests registration of usage history information for a main broadcast sound source, the monitoring server transmits, to a network management server, creation request information for creating a block for registration of the usage history information;
When the network management server confirms that the broadcast server and the monitoring server are mutually designated networks based on the creation request information, transmitting a registration permission signal of the block to the monitoring server; and
When receiving the registration permission signal, the monitoring server executes a chain code for the creation of the block and registers the usage history information in the block,
The above creation request information is,
Containing a user code and user name using the broadcast server, and a monitoring organization code and monitoring organization name using the monitoring server,
How the sound source monitoring system operates. delete According to claim 1,
The step of transmitting the registration permission signal is,
Checking whether the user code, the user name, the monitoring organization code, and the monitoring organization name are the same as the reference user code, reference user name, reference monitoring organization code, and reference monitoring organization name of the preset mutually designated network,
How the sound source monitoring system operates. According to claim 1,
The chain code is,
A smart contract between the broadcast server and the monitoring server for generating and monitoring the usage history information,
How the sound source monitoring system operates. According to claim 1,
The above usage history information is,
Content transmission date including the main broadcast sound source, content channel code, content code, content start and end time, start and end time of the main broadcast sound source, and UCI (Universal Content Identifier) for a unique identifier of the main broadcast sound source. containing code,
How the sound source monitoring system operates. According to claim 1,
After registering in the block,
When requesting modification of the usage history information from the broadcasting server, the monitoring server further includes executing the chain code to register correction of the usage history information and modifying the usage history information registered in the block. doing,
How the sound source monitoring system operates. According to claim 6,
After the step of modifying the above usage history information,
The network management server registers correction information including modification date, modification time, and modification content for modification of the usage history information in the block,
How the sound source monitoring system operates. According to claim 1,
When a trust management server requests inquiry of the usage history information, the monitoring server transmits inquiry request information for inquiry of the usage history information to the network management server;
When the network management server confirms that the trust management server and the monitoring server are mutually designated networks based on the inquiry request information, transmitting an inquiry approval signal for the use history information to the trust management server;
The trust management server executing a chain code for the inquiry; and
When execution of the chain code is completed, further comprising the step of the network management server transmitting the usage history information to the trust management server,
How the sound source monitoring system operates.